A Textbook of Electrical Technology Volume I Basic Electrical Engineering B L Theraja

DBS3900 WiMAX
V300R002C03
Feature Configuration Guide
Issue 03
Date 2010-03-19
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: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2010. 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 the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Proprietary and Confidential

DBS3900 WiMAX
Feature Configuration Guide Contents
Contents
About This Document.....................................................................................................................1

1 HARQ...........................................................................................................................................1-1
1.1 Overview of HARQ........................................................................................................................................1-2
1.2 Availability of HARQ.....................................................................................................................................1-4
1.3 Description of HARQ......................................................................................................................................1-5
1.3.1 Principles of HARQ...............................................................................................................................1-5
1.3.2 HARQ Types..........................................................................................................................................1-6
1.3.3 HARQ Processing in the Signaling Plane..............................................................................................1-7
1.3.4 HARQ Processing in the User Plane......................................................................................................1-8
1.3.5 HARQ Allocation Algorithm and Buffer Management.......................................................................1-10
1.3.6 Power Control and AMC Processing for HARQ Links.......................................................................1-10
1.4 Operations Related to HARQ........................................................................................................................1-10
1.4.1 Activating the HARQ Feature..............................................................................................................1-11
1.4.2 Deactivating the HARQ Feature..........................................................................................................1-12
1.5 Maintenance Information of HARQ.............................................................................................................1-12
1.6 Reference Information of HARQ..................................................................................................................1-14
2 Multi-Antenna............................................................................................................................2-1
2.1 Overview of Multi-Antenna ...........................................................................................................................2-2
2.2 Availability of Multi-Antenna.........................................................................................................................2-4
2.3 Description of Multi-Antenna.........................................................................................................................2-5
2.3.1 Key Multi-Antenna Technologies..........................................................................................................2-5
2.3.2 Strategy of Multi-Antenna Applications................................................................................................2-9
2.4 Operations Related to Multi-Antenna.............................................................................................................2-9
2.4.1 Activating the Multi-Antenna Feature...................................................................................................2-9
2.4.2 Deactivating the Multi-Antenna Feature..............................................................................................2-12
2.5 Maintenance Information of Multi-Antenna.................................................................................................2-13
2.6 Reference Information of Multi-Antenna......................................................................................................2-14
3 Power Control and AMC..........................................................................................................3-1

3.1 Overview of Power Control and AMC...........................................................................................................3-2
3.2 Availability of Power Control and AMC........................................................................................................3-4
3.3 Description of Power Control and AMC.........................................................................................................3-4
3.4 Operations Related to Power Control and AMC.............................................................................................3-7
Issue 03 (2010-03-19) Huawei Proprietary and Confidential i

DBS3900 WiMAX
Contents Feature Configuration Guide
3.4.1 Activating the Power Control and AMC Feature...................................................................................3-7

3.4.2 Deactivating the Power Control and AMC Feature...............................................................................3-8
3.5 Maintenance Information of Power Control and AMC..................................................................................3-9
3.6 Reference Information of Power Control and AMC.....................................................................................3-10
4 Idle Mode.....................................................................................................................................4-1
4.1 Overview of Idle Mode ..................................................................................................................................4-2
4.2 Availability of Idle Mode ...............................................................................................................................4-4
4.3 Description of Idle Mode................................................................................................................................4-5
4.3.1 Entering the Idle Mode...........................................................................................................................4-5
4.3.2 Paging.....................................................................................................................................................4-7
4.3.3 Updating Location..................................................................................................................................4-8
4.3.4 Exiting the Idle Mode...........................................................................................................................4-12
4.4 Operations Related to Idle Mode..................................................................................................................4-15
4.4.1 Activating the Idle Mode Feature.........................................................................................................4-15
4.4.2 Deactivating the Idle Mode Feature.....................................................................................................4-16
4.5 Maintenance Information of Idle Mode........................................................................................................4-17
4.6 Reference Information of Idle Mode.............................................................................................................4-18
5 QoS................................................................................................................................................5-1
5.1 Overview of QoS.............................................................................................................................................5-2
5.2 Availability of QoS.........................................................................................................................................5-4
5.3 Description of QoS..........................................................................................................................................5-4
5.3.1 QoS Network Model..............................................................................................................................5-5
5.3.2 QoS Application Objects and Parameters..............................................................................................5-5
5.3.3 QoS Transmission Control...................................................................................................................5-11
5.4 Operations Related to QoS............................................................................................................................5-12
5.4.1 Activating the QoS Feature..................................................................................................................5-12
5.4.2 Deactivating the QoS Feature..............................................................................................................5-15
5.5 Maintenance Information of QoS..................................................................................................................5-16
5.6 Reference Information of QoS......................................................................................................................5-16
6 Handover......................................................................................................................................6-1
6.1 Overview of Handover....................................................................................................................................6-2
6.2 Availability of Handover.................................................................................................................................6-3
6.3 Description of Handover.................................................................................................................................6-3
6.3.1 Application Scenario..............................................................................................................................6-4
6.3.2 Ordinary Handover.................................................................................................................................6-4
6.3.3 Fast Ranging Handover..........................................................................................................................6-9
6.4 Operations Related to Handover...................................................................................................................6-14
6.4.1 Activating the Handover Feature.........................................................................................................6-15
6.4.2 Deactivating the Handover Feature......................................................................................................6-16
6.5 Maintenance Information of Handover.........................................................................................................6-17
6.6 Reference Information of Handover..............................................................................................................6-20
ii Huawei Proprietary and Confidential Issue 03 (2010-03-19)

DBS3900 WiMAX
Feature Configuration Guide Contents
7 Security Mechanism ................................................................................................................. 7-1

7.1 Overview of Security Mechanism...................................................................................................................7-2
7.2 Availability of Security Mechanism...............................................................................................................7-3
7.3 Description of Security Mechanism................................................................................................................7-4
7.3.1 Static SA and Dynamic SA....................................................................................................................7-5
7.3.2 Procedures of Security Mechanism........................................................................................................7-6
7.3.3 Authentication Capability Negotiation...................................................................................................7-7
7.3.4 Identity Authentication...........................................................................................................................7-9
7.3.5 Key Management.................................................................................................................................7-10
7.3.6 Management Message Authentication.................................................................................................7-14
7.3.7 Air Interface Data Encryption .............................................................................................................7-14
7.4 Operations Related to Security Mechanism..................................................................................................7-16
7.4.1 Activating the Security Mechanism Feature........................................................................................7-16
7.4.2 Deactivating the Security Mechanism Feature.....................................................................................7-17
7.5 Maintenance Information of Security Mechanism........................................................................................7-17
7.6 Reference Information of Security Mechanism............................................................................................7-19
8 PHS................................................................................................................................................8-1
8.1 Overview of PHS............................................................................................................................................8-2
8.2 Availability of PHS.........................................................................................................................................8-3
8.3 Description of PHS..........................................................................................................................................8-4
8.3.1 PHS Capability Negotiation...................................................................................................................8-4
8.3.2 Payload Header Suppression and Restoration Processing.....................................................................8-5
8.4 Operations Related to PHS..............................................................................................................................8-7
8.4.1 Activating the PHS Feature....................................................................................................................8-7
8.4.2 Deactivating the PHS Feature................................................................................................................8-8
8.5 Maintenance Information of PHS...................................................................................................................8-8
8.6 Reference Information of PHS........................................................................................................................8-9
9 BS Resource Wholesale.............................................................................................................9-1
9.1 Overview of BS Resource Wholesale.............................................................................................................9-2
9.2 Availability of BS Resource Wholesale..........................................................................................................9-3
9.3 Description of BS Resource Wholesale..........................................................................................................9-4
9.3.1 Network Architecture.............................................................................................................................9-4
9.3.2 Access Authority Control.......................................................................................................................9-5
9.3.3 Transmission Resource Control.............................................................................................................9-7
9.4 Operations Related to BS Resource Wholesale..............................................................................................9-8
9.4.1 Activating the BS Resource Wholesale Feature.....................................................................................9-8
9.4.2 Deactivating the BS Resource Wholesale Feature.................................................................................9-9
9.5 Maintenance Information of BS Resource Wholesale....................................................................................9-9
9.6 Reference Information of BS Resource Wholesale.......................................................................................9-13
10 Network Discovery & Selection/Re-Selection..................................................................10-1

10.1 Overview of ND&S.....................................................................................................................................10-2
Issue 03 (2010-03-19) Huawei Proprietary and Confidential iii

DBS3900 WiMAX
Contents Feature Configuration Guide
10.2 Availability of ND&S.................................................................................................................................10-3

10.3 Description of ND&S..................................................................................................................................10-4
10.3.1 Principles of ND&S...........................................................................................................................10-4
10.3.2 Deployment Scenario of ND& S........................................................................................................10-7
10.4 Operations Related to ND&S......................................................................................................................10-9
10.4.1 Activating the ND&S Feature............................................................................................................10-9
10.4.2 Deactivating the ND&S Feature......................................................................................................10-10
10.5 Maintenance Information of ND&S..........................................................................................................10-10
10.6 Reference Information of ND&S..............................................................................................................10-11
11 Dynamic Service Flow...........................................................................................................11-1

11.1 Overview of Dynamic Service Flow...........................................................................................................11-2
11.2 Availability of Dynamic Service Flow........................................................................................................11-3
11.3 Description of Dynamic Service Flow........................................................................................................11-4
11.3.1 Network Architecture.........................................................................................................................11-4
11.3.2 Principles............................................................................................................................................11-5
11.4 Operations Related to Dynamic Service Flow............................................................................................11-7
11.4.1 Activating the Dynamic Service Flow Feature..................................................................................11-8
11.4.2 Deactivating the Dynamic Service Flow Feature...............................................................................11-8
11.5 Maintenance Information of Dynamic Service Flow..................................................................................11-8
11.6 Reference Information of Dynamic Service Flow....................................................................................11-10
12 Load Balancing.......................................................................................................................12-1
12.1 Overview of Load Balancing......................................................................................................................12-2
12.2 Availability of Load Balancing...................................................................................................................12-3
12.3 Description of Load Balancing...................................................................................................................12-4
12.3.1 Load Balancing Control Thresholds..................................................................................................12-5
12.3.2 Load Update.......................................................................................................................................12-5
12.3.3 Load Admission Control....................................................................................................................12-6
12.3.4 Service Flow Rate Control.................................................................................................................12-7
12.3.5 Load Balancing Handover..................................................................................................................12-8
12.4 Operations Related to Load Balancing......................................................................................................12-10
12.4.1 Activating the Load Balancing Feature............................................................................................12-10
12.4.2 Deactivating the Load Balancing Feature........................................................................................12-11
12.5 Maintenance Information of Load Balancing...........................................................................................12-11
12.6 Reference Information of Load Balancing................................................................................................12-14
iv Huawei Proprietary and Confidential Issue 03 (2010-03-19)

DBS3900 WiMAX
Feature Configuration Guide Figures
Figures
Figure 1-1 SAW hybrid ARQ solution.................................................................................................................1-5

Figure 1-2 Principles of HARQ............................................................................................................................1-6
Figure 1-3 HARQ processing flow chart in the user plane..................................................................................1-9
Figure 2-1 Transmit matrix of Matrix A..............................................................................................................2-5
Figure 2-2 Transmit matrix of Matrix B..............................................................................................................2-6
Figure 2-3 Principle of four-antenna CDD...........................................................................................................2-6
Figure 2-4 CDD transmission mode.....................................................................................................................2-7
Figure 2-5 Transmit matrix of Matrix A..............................................................................................................2-7
Figure 2-6 Transmit matrix of Matrix B..............................................................................................................2-8
Figure 2-7 Principle of uplink CSM.....................................................................................................................2-8
Figure 4-1 Network reference model of the idle mode feature............................................................................4-2
Figure 4-2 SS/MS-initialed process for entering the idle mode...........................................................................4-6
Figure 4-3 BS-initialed process for entering the idle mode.................................................................................4-7
Figure 4-4 Paging process....................................................................................................................................4-8
Figure 4-5 Secure location update process...........................................................................................................4-9
Figure 4-6 Unsecured location update process...................................................................................................4-11
Figure 4-7 Process for exiting the idle mode when the timer expires................................................................4-13
Figure 4-8 Process for exiting the idle mode before the timer expires..............................................................4-14
Figure 5-1 External interfaces of the WiMAX.....................................................................................................5-5
Figure 6-1 Handover scenarios.............................................................................................................................6-4
Figure 6-2 MS-initiated handover process...........................................................................................................6-5
Figure 6-3 BS-initiated handover process............................................................................................................6-7
Figure 6-4 MS-initiated Fast Ranging handover process...................................................................................6-10
Figure 6-5 BS-initiated Fast Ranging handover process....................................................................................6-12
Figure 7-1 SA allocation......................................................................................................................................7-6
Figure 7-2 Procedures..........................................................................................................................................7-7
Figure 7-3 Procedure for negotiating authentication capabilities.........................................................................7-8
Figure 7-4 Procedure for generating keys..........................................................................................................7-11
Figure 7-5 Message authentication procedure....................................................................................................7-14
Figure 7-6 Procedure for obtaining the TEK .....................................................................................................7-16
Figure 8-1 Payload header suppression for an SDU............................................................................................8-6
Figure 8-2 Payload header suppression and restoration.......................................................................................8-6
Figure 9-1 Network architecture for the BS resource wholesale feature.............................................................9-5
Issue 03 (2010-03-19) Huawei Proprietary and Confidential v

DBS3900 WiMAX
Figures Feature Configuration Guide
Figure 10-1 Process for implementing ND&S...................................................................................................10-4

Figure 10-2 Network topology of NAP sharing.................................................................................................10-7
Figure 10-3 Process for implementing NAP sharing.........................................................................................10-8
Figure 11-1 Network architecture of MS-initiated dynamic service flows........................................................11-5
Figure 11-2 Process of MS-initiated dynamic service flows..............................................................................11-6
Figure 11-3 Creating dynamic service flows (MS-initiated)..............................................................................11-7
Figure 12-1 Handover between intra-sector carriers..........................................................................................12-7
Figure 12-2 Scenario of the handover between sector carriers..........................................................................12-8
Figure 12-3 Process of the handover between sector carriers ...........................................................................12-9
vi Huawei Proprietary and Confidential Issue 03 (2010-03-19)

DBS3900 WiMAX
Feature Configuration Guide Tables
Tables
Table 1-1 NEs involved in the HARQ feature.....................................................................................................1-4

Table 1-2 Version that supports the HARQ feature.............................................................................................1-4
Table 1-3 Parameters related to the MOD CARRIERBLOCKFLAG command...............................................1-12
Table 1-4 Parameters related to the MOD ULCHANPARA command.............................................................1-13
Table 1-5 Parameters related to the MOD DLCHANPARA command.............................................................1-13
Table 1-6 Parameters related to the MOD OFDMACAPABILITAY command...............................................1-13
Table 1-7 Parameters related to the MOD MACCAPABILITY command.......................................................1-13
Table 1-8 Parameters related to the MOD RRMSOFT command.....................................................................1-14
Table 2-1 NEs involved in the multi-antenna feature...........................................................................................2-4
Table 2-2 Version that support the multi-antenna feature....................................................................................2-5
Table 2-3 Parameters related to the MOD RRMSWITCH command................................................................2-12
Table 2-5 Parameters related to the MOD SECTOR command.........................................................................2-13
Table 2-6 Parameters related to the MOD OFDMACAPABILITY command..................................................2-13
Table 2-8 Parameters related to the MOD RRMSOFT command.....................................................................2-14
Table 3-1 NEs involved in the power control and AMC feature..........................................................................3-4
Table 3-2 Version that supports the power control and AMC feature.................................................................3-4
Table 3-3 Parameters related to the MOD RRMSWITCH command..................................................................3-9
Table 3-4 Parameters related to the MOD ULAMCTHRESH command............................................................3-9
Table 3-5 Parameters related to the MOD DLAMCTHRESH command..........................................................3-10
Table 3-6 Parameters related to the MOD ULPERTHRESH command............................................................3-10
Table 4-1 NEs involved in the idle mode feature.................................................................................................4-4
Table 4-2 Version that supports the idle mode feature.........................................................................................4-5
Table 4-3 Parameters of the MOD MACCAPABILITY command.................................................................4-17
Table 4-4 Parameters of the ADD PAGINGINF command.............................................................................4-17
Table 4-5 Performance measurement items related to the idle mode feature.....................................................4-17
Table 5-1 NEs involved in the QoS feature..........................................................................................................5-4
Table 5-2 Version that supports the QoS feature.................................................................................................5-4
Table 5-3 Typical applications and parameters of QoS........................................................................................5-6
Table 5-4 Parameters related to BE starvation prevention.................................................................................5-11
Table 6-1 NEs involved in the handover feature..................................................................................................6-3
Table 6-2 Version that supports the handover feature..........................................................................................6-3
Issue 03 (2010-03-19) Huawei Proprietary and Confidential vii

DBS3900 WiMAX
Tables Feature Configuration Guide
Table 6-3 Parameters related to the ADD NBR command.................................................................................6-17

Table 6-4 Parameters related to the RMV NBR command................................................................................6-17
Table 6-5 Parameters related to the ADD TRIGGER command.......................................................................6-17
Table 6-7 Parameters related to the MOD HOPARA command........................................................................6-18
Table 6-9 Performance counters related to the handover feature.......................................................................6-19
Table 7-1 NEs involved in the security mechanism feature.................................................................................7-4
Table 7-2 Versions that support the security mechanism feature.........................................................................7-4
Table 7-3 Parameters related to the MOD ENCRYPTCAP command..............................................................7-18
Table 7-5 Parameters related to the MOD BSCFG command...........................................................................7-18
Table 7-6 Parameters related to the MOD PKMCFG command........................................................................7-18
Table 7-7 Parameter related to the MOD MIXCFG command..........................................................................7-18
Table 7-8 Performance counters related to the security mechanism feature......................................................7-19
Table 8-1 NEs involved in the PHS feature.........................................................................................................8-3
Table 8-2 Version that supports the PHS feature.................................................................................................8-4
Table 8-3 Parameters related to the MOD CARRIERLICENSEINFO command...............................................8-8
Table 8-4 Parameters related to the MOD MACCAPABILITY command.........................................................8-9
Table 9-1 NEs involved in the BS resource wholesale feature............................................................................9-3
Table 9-2 Version that supports the BS resource wholesale feature....................................................................9-4
Table 9-3 Parameters related to the MOD CARRIERLICENSEINFO command...............................................9-9
Table 9-4 Parameters related to the ADD WHOLESALE command................................................................9-10
Table 9-5 Parameters related to the ADD LGCPORT and MOD LGCPORT commands.................................9-10
Table 9-6 Parameters related to the ADD IPPATH command...........................................................................9-10
Table 9-7 Parameters related to the RMV WHOLESALE command................................................................9-11
Table 9-8 Parameters related to the RMV IPPATH command..........................................................................9-11
Table 9-9 Parameters related to the RMV LGCPORT command......................................................................9-11
Table 9-10 Performance counters related to the BS resource wholesale feature...............................................9-12
Table 10-1 NEs involved in the ND&S feature..................................................................................................10-3
Table 10-2 Version that supports the ND&S feature.........................................................................................10-4
Table 10-3 Parameters related to the ADD NSP command.............................................................................10-10
Table 10-4 Parameter related to the RMV NSP command..............................................................................10-10
Table 10-5 Parameters related to the MOD NSP command.............................................................................10-10
Table 10-6 Parameter related to the LST NSP command................................................................................10-11
Table 10-7 Parameter related to the MOD BTSINFO command.....................................................................10-11
Table 10-8 Performance counters related to the ND&S feature.......................................................................10-11
Table 11-1 NEs involved in the MS-initiated dynamic service flow.................................................................11-4
Table 11-2 Version that supports the dynamic service flow feature..................................................................11-4
Table 11-3 Parameters related to the MOD MSCFG command........................................................................11-9
Table 11-4 Parameters related to the MOD CARRIERLICENSEINFO command...........................................11-9
Table 11-5 Performance counters related to the dynamic service flow feature.................................................11-9
viii Huawei Proprietary and Confidential Issue 03 (2010-03-19)

DBS3900 WiMAX
Feature Configuration Guide Tables
Table 12-1 NEs involved in the load balancing feature.....................................................................................12-3

Table 12-2 Version that supports the load balancing feature.............................................................................12-4
Table 12-3 Parameters related to the MOD CARRIERBLOCKFLAG command...........................................12-12
Table 12-4 Parameters related to the MOD RRMSWITCH command............................................................12-12
Table 12-5 Parameters related to the MOD LOADCTRLPARA command....................................................12-12
Table 12-6 Performance counters related to the load balancing feature..........................................................12-13
Issue 03 (2010-03-19) Huawei Proprietary and Confidential ix

DBS3900 WiMAX
Feature Configuration Guide About This Document
About This Document
Overview
This document describes the WiMAX BS features in terms of the definitions, principles, service
flows, and implementation.
Product Version
The following table lists the product version related to this document.
Product Name Product Version
DBS3900 WiMAX V300R002C03
Intended Audience
This document is intended for:
l Network planning engineers
l System engineers
l Commissioning engineers
l Network operators
Change History
Version Change History
03 (2010-03-19) This is the third commercial release.

Compared with 02 (2010-01-10), this release
consists changes in the following chapters:
l Load Balancing
Issue 03 (2010-03-19) Huawei Proprietary and Confidential 1

DBS3900 WiMAX
About This Document Feature Configuration Guide
Version Change History
02 (2010-01-10) This is the second commercial release.

Compared with 01 (2009-10-25), this release
consists changes in the following chapters:
l Load Balancing
l BS Resource Wholesale
01 (2009-10-25) This is the first commercial release.
Organization
1 HARQ
This section describes the Hybrid Automatic Repeat Request (HARQ), which is a hybrid
Automatic Repeat Request (ARQ) technology that uses Forward Error Correction (FEC) to
improve the communications reliability. This provides an overview of the HARQ feature. In an
adverse radio channel environment, the HARQ technology enables the system to adapt to
channel fading and rapid interference environment change, hence, effectively decreasing the
error rate in data transmission. This document describes the basic concepts, functions, and
settings of the HARQ feature.
2 Multi-Antenna
Multi-antenna is a technology that uses multiple antennas at the transmitter and receiver. Multi-
antenna systems can be categorized into single input multiple output (SIMO) diversity, multiple
input single output (MISO) diversity, and multiple input multiple output (MIMO) diversity. This
chapter describes the basic concepts, functions, and implementation method of the multi-antenna
feature.
3 Power Control and AMC
Power control and AMC algorithms are core algorithms of WiMAX. The MS and BS cooperate
over the R1 interface to achieve power control and AMC. This chapter describes the basic
concepts, functions, and implementation method of the power control and AMC feature.
4 Idle Mode
Idle mode is a mature technology developed for optimum allocation of network resources and
reduction in power consumption of an MS. This document describes the basic concepts,
functions, and settings of the idle mode feature.
5 QoS
The WiMAX BS can provide users with five different Quality of Service (QoS) levels. Users
need to choose the desired QoS level when subscribing to services. This chapter describes the
basic concepts, functions, and implementation method of the QoS feature.
6 Handover
WiMAX defines five application scenarios, namely, fixed, nomadic, portable, mobile, and full
mobile. To meet the requirements for the wireless DSL and combine the fixed and mobile
2 Huawei Proprietary and Confidential Issue 03 (2010-03-19)

DBS3900 WiMAX
application scenarios, the handover technology is used so that service continuity can be achieved.
This chapter describes the basic concepts, functions, and implementation of the handover feature.
7 Security Mechanism
As an emerging wireless broadband technology, the WiMAX brings security problems because
of open transmission channels. For example, unauthorized MSs access the WiMAX network,
air interface data is intercepted or changed, and signaling is changed or forged. Therefore,
subscribers and devices accessing the wireless network must be authenticated, the security and
integrity of data should be guaranteed, and signaling should be verified.
8 PHS
The payload header suppression (PHS) is a method of suppressing static packet headers. This
chapter describes the basic concepts about, functions of, and implementation of the PHS feature.
9 BS Resource Wholesale
The BS resource wholesale feature enables a BS to control the access authority, access
bandwidth, and traffic of multiple retailer domains. It facilitates the allocation of bandwidth for
multiple retailer domains under the coverage of the same BS. This chapter describes the concepts,
functions, and operations related to the BS resource wholesale feature.
10 Network Discovery & Selection/Re-Selection
Network discovery & selection/re-selection (ND&S) refers to a function based on which the
MS/SS selects the network service provider (NSP). This chapter describes the basic concepts,
functions, and operations of the ND&S feature.
11 Dynamic Service Flow
The WiMAX system that supports dynamic service flows can dynamically initiate and terminate
the creation and release of service flows. This chapter describes the basic concepts, functions,
and settings of the dynamic service flow feature.
12 Load Balancing
During network entry and service implementation, the BS balances the load of carriers to
minimize congestion on sector carriers. This chapter describes the basic concepts, functions, and
implementation of the load balancing feature.
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, which 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.

DBS3900 WiMAX
About This Document Feature Configuration Guide
Symbol Description
Indicates a potentially hazardous situation, which if not

avoided,could result in equipment damage, data loss,
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.
General Conventions
The general conventions that may be found in this document are defined as follows.
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 Examples of information displayed on the screen are in
Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

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

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
4 Huawei Proprietary and Confidential Issue 03 (2010-03-19)

DBS3900 WiMAX
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, 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 Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
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 Operations
The mouse operations that may be found in this document are defined as follows.
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.

DBS3900 WiMAX
Feature Configuration Guide 1 HARQ
1 HARQ
About This Chapter
This section describes the Hybrid Automatic Repeat Request (HARQ), which is a hybrid
Automatic Repeat Request (ARQ) technology that uses Forward Error Correction (FEC) to
improve the communications reliability. This provides an overview of the HARQ feature. In an
adverse radio channel environment, the HARQ technology enables the system to adapt to
channel fading and rapid interference environment change, hence, effectively decreasing the
error rate in data transmission. This document describes the basic concepts, functions, and
settings of the HARQ feature.
1.1 Overview of HARQ

This section describes the definition, purpose, specifications, and impact of the HARQ feature.
1.2 Availability of HARQ
This section describes the network elements (NEs) involved in and version information about
the HARQ feature.
1.3 Description of HARQ
This section describes the principles and types of HARQ, principles of CC-HARQ, and power
control and AMC processing for links. The CC-HARQ feature involves the processing for
network access and service setup in the signaling plane, processing for the UL and DL HARQ
in the user plane, HARQ allocation management, and buffer management.
1.4 Operations Related to HARQ
This section describes how to activate and deactivate the HARQ feature.
1.5 Maintenance Information of HARQ
This section describes the parameters and performance measurement items related to the HARQ
feature.
1.6 Reference Information of HARQ
The protocol that the HARQ feature complies with is IEEE 802.16-2004/Cor2/D3 with latest
SRD and WiMAX Forum Network Architecture Release 1.2.0.
Issue 03 (2010-03-19) Huawei Proprietary and Confidential 1-1

DBS3900 WiMAX
1 HARQ Feature Configuration Guide
1.1 Overview of HARQ

This section describes the definition, purpose, specifications, and impact of the HARQ feature.
Definition
HARQ is a PHY/MAC-layer hybrid ARQ technology that uses forward error correction (FEC).
After HARQ is enabled, the transmitter decides whether to retransmit a data packet according
to the received ACK or NACK message from the receiver. If data retransmission is required,
the receiver combines the data packet with the previously received packet and then retransmits
the data packet for error correction decoding.
Through data retransmission, the receiver can obtain the time diversity gain, coding gain, and
power gain to enhance the decoding performance and spectrum efficiency and intensify coverage
effect.
Purpose
Featuring the advantages of both FEC and ARQ, HARQ is aimed at improving signal
transmission quality and information reliability. In an adverse radio environment, HARQ can
reduce the impact of channel fading and interference fluctuation, thereby achieving high system
gains, lowering the BER, and improving data transmission performance.
Specifications
The Huawei specifications of the HARQ feature are described as follows:
l A maximum of 16 HARQ channels can be allocated to each DL subscriber and a maximum
of eight HARQ channels can be allocated to each UL subscriber. The supported highest
HARQ capability set is HARQ set 5.
l A DL single-subscriber frame supports a maximum of five DL HARQ subbursts, and an
UL single-subscriber frame supports a maximum of two UL HARQ subbursts.
Impact
l HARQ improves spectrum efficiency and enhances coverage.
l The data retransmission and combination during HARQ increase transmission delay to a
small extent.
l Relation between the HARQ feature and other features:
– −The HARQ feature is related to power control and AMC feature. HARQ and AMC
are used together to combat the fading of radio channels and time-variable interference.
AMC provides rough and slow adaptive control within a large dynamic range. HARQ
provides precise and fast adaptive control within a small dynamic range.
– −HARQ is related to the QoS feature. During service setup, the BS decides whether
HARQ is enabled for a connection according to the service flow parameter for QoS
feature.
1-2 Huawei Proprietary and Confidential Issue 03 (2010-03-19)

DBS3900 WiMAX
Terms
Term Definition
Stop-and-wait The transmitter processes another data block only after the previously
mechanism transmitted data block is correctly received.
Selective For an incorrect data block, the transmitter retransmits the check bits
retransmission first. If error occurs again, the transmitter retransmits the entire data
block.
Chase combing The transmitter transmits system information and redundancy

information, and the receiver corrects errors in the data packet. If any
error bit fails to be corrected, the receiver sends a packet requesting
retransmission from the transmitter. Then, the transmitter uses the same
error correction code and includes the same redundancy information in
the retransmitted packet as that the previously packet uses and includes.
After receiving an error packet, the receiver does not discard the error
packet, but directly decodes the retransmitted code words or combines
the retransmitted code words with buffered code words, and then
decodes them.
Incremental The data transmitted by the transmitter for the first time contains system
Redundancy information and some redundancy information. The retransmitted data,
however, does not contain system bit information except new
redundancy information. After the receiver receives an error packet, it
does not discard the error packet but combines the error packet with the
retransmitted redundancy information and then decodes the combined
information.
Abbreviations and Acronyms

Abbreviation
and Acronym Expansion
ARQ Automatic Retransmission Request
AMC Automatic Modulation Control
BS Base Station
CC Chase Combining
CTC Convolutional Turbo Code
DSA/DSC Dynamic Service Addition/Change
FEC Forward Error Correction
HARQ Hybrid Automatic Retransmission Request
IR Incremental Redundancy
MAC Medium Access Control

DBS3900 WiMAX
Abbreviation
MS Mobile Station
PDU Protocol Data Unit
SAW Stop And Wait
SS Subscriber Station
1.2 Availability of HARQ

This section describes the network elements (NEs) involved in and version information about
the HARQ feature.
NEs Involved
The HARQ feature requires the coordination of the SS/MS, BS, and M2000. Table 1-1 lists the
NEs involved in the HARQ feature.
Table 1-1 NEs involved in the HARQ feature
AAA DHCP
SS/MS BS ASN-GW Server Server M2000
√ √ - - - -
NOTE
In Table 1-1, √ is used to mark NEs that are involved in this feature, and - is used to mark NEs that are
not involved in this feature.
Version Support
Table 1-2 lists the version that supports the HARQ feature.
Table 1-2 Version that supports the HARQ feature
Product Version
BS DBS3900 WiMAX V300R002C03
License Restriction
The usage of the HARQ feature is not controlled by a license.

DBS3900 WiMAX
1.3 Description of HARQ

This section describes the principles and types of HARQ, principles of CC-HARQ, and power
control and AMC processing for links. The CC-HARQ feature involves the processing for
network access and service setup in the signaling plane, processing for the UL and DL HARQ
in the user plane, HARQ allocation management, and buffer management.
1.3.1 Principles of HARQ

This section describes the principles of HARQ. To understand the HARQ feature, you need to
know how HARQ works. HARQ is defined by the IEEE 802.16e standard. It is applied to the
air link between the BS and MS/SS. The HARQ feature is a hybrid Stop and Wait (SAW) ARQ
solution that enables retransmission of error data to decrease the impact of error bits on ongoing
services.
1.3.2 HARQ Types
In the IEEE 802.16e standard, two types of HARQs are defined: CC-HARQ and IR-HARQ.
1.3.3 HARQ Processing in the Signaling Plane
HARQ processing in the signaling plane involves the initial network entry of the MS, handover,
idle-mode network reentry, location update, and service flow setup.
1.3.4 HARQ Processing in the User Plane
The BS performs HARQ processing in the user plane on the PHY layer and MAC layer.
1.3.5 HARQ Allocation Algorithm and Buffer Management
The HARQ allocation algorithm and buffer management are performed on the PHY layer and
MAC layer of the BS.
1.3.6 Power Control and AMC Processing for HARQ Links
This section describes AMC processing for DL HARQ and power control and AMC processing
for UL HARQ.
1.3.1 Principles of HARQ

This section describes the principles of HARQ. To understand the HARQ feature, you need to
know how HARQ works. HARQ is defined by the IEEE 802.16e standard. It is applied to the
air link between the BS and MS/SS. The HARQ feature is a hybrid Stop and Wait (SAW) ARQ
solution that enables retransmission of error data to decrease the impact of error bits on ongoing
services.
After a transmitter sends a packet to the receiver, it sends the next packet only when it receives
the ACK message from the receiver. If the transmitter fails to receive the ACK message, it
retransmits the packet that fails to be received, as shown in Figure 1-1.
Figure 1-1 SAW hybrid ARQ solution

DBS3900 WiMAX
Both the UL and DL over the R1 interface of the WiMAX network support the HARQ. DL
HARQ: After a base station (BS) sends a HARQ data packet, the MS responds with the ACK
or NACK message based on whether the correct data packet is received. UL HARQ: After an
MS sends an HARQ data packet, the BS decides whether to retransmit according whether the
UL decoding is correct.
HARQ enables selective retransmission of error data to decrease the impact of error codes over
the channel on services. Figure 1-1 shows how HARQ is implemented at the base station side
(the HARQ implementation at the MS side is similar).
Figure 1-2 Principles of HARQ
1.3.2 HARQ Types

In the IEEE 802.16e standard, two types of HARQs are defined: CC-HARQ and IR-HARQ.
When the CC-HARQ is adopted and data retransmission is required, the transmitter uses the
same modulation and coding (MC) mode to retransmit the burst. After the receiver receives the
data, it combines the data with its previously received one to raise the Signal Noise Ratio (SNR)
before decoding, hence, increasing the probability of correct decoding.
When the IR-HARQ is adopt and data retransmission is required, the transmitter can use different
MC mode and can add redundancy information different from previous one to the error
correction (EC) block for data retransmission. After the receiver receives the data, it combines

DBS3900 WiMAX
the data with its previously received one to raise the SNR or adds redundancy information to
the decoding code, hence, increasing the probability of correct decoding. The IR-HARQ feature
performance is slightly better than the CC-HARQ feature performance but requires higher
hardware capability.
According to the WiMAX Forum Mobile System Profile Release 1.0, the base station must
support the CC-HARQ feature that uses Convolutional Turbo Code (CTC) coding and need not
support the IR-HARQ feature. Hence, this document describes mainly the functions and working
principles of the CC-HARQ feature.
1.3.3 HARQ Processing in the Signaling Plane

HARQ processing in the signaling plane involves the initial network entry of the MS, handover,
idle-mode network reentry, location update, and service flow setup.
The HARQ parameter renegotiation processes during MS handover, idle-mode network reentry,
and location update are similar to the parameter negotiation process during the initial network
entry of the MS. The following describes the HARQ parameter negotiation process during the
initial network entry of the MS.
1. HARQ parameter configuration during sector carrier setup
The HARQ related parameter configuration at the BS side is performed on the M2000 or
Web LMT. The HARQ parameter configuration procedure is described as follows:
(1) On the M2000 or Web LMT, configure the OFDMA support capability parameter of
the BS. This parameter indicates the HARQ support capability of the BS. The HARQ
related OFDMA support capability parameters are:
l Modulation Mode: The BIT#4 (the fifth bit from the least significant bit to the
most significant bit) set to 1 is one of the prerequisites for enabling the HARQ.
When the BIT#4 is set to 0, HARQ is disabled.
l Demodulation Mode: The BIT#5 (the sixth bit from the least significant bit to the
most significant bit) set to 1 is one of the prerequisites for enabling the HARQ.
When the BIT#5 is set to 0, HARQ is disabled.
l Uplink Control Support: HARQ retransmission requires the UL ACK channel
to transmit the DL ACK or NACK message. The BIT#2 (the third bit from the
least significant bit to the most significant bit) set to 1 indicates supporting the UL
ACK channel and enabling the HARQ. When the BIT#2 is set to 0, HARQ is
disabled.
(2) During sector carrier setup, the BS decides whether to enable the HARQ function
according to the HARQ capability parameters and records the decision for the sector.
The result is used during the network entry negotiation of the MS.
2. SBC processing procedure during the initial network entry of the MS
During the initial network entry of the MS, whether the BS supports the HARQ function
is negotiated through the SS basic capability (SBC) processing procedure. The SBC
processing procedure is described as follows:
(1) The MS initiates the SBC processing procedure to negotiate whether to support the
HARQ function by sending a message to the BS.
(2) The BS negotiates with the MS on whether to support the HARQ parameters HARQ
Buffer Capability, Number of UL/DL HARQ Channels, and Maximum Number
Of Bursts Per Frame Capability In HARQ according to the HARQ Chase indicator
bit in parameters Modulation Mode and Demodulation Mode. Through negotiation,
the BS decides whether to enable HARQ for a connection, the number of HARQ

DBS3900 WiMAX
channels to be used, and whether to enable the PDU SN subheader in MAC Header
and Extended Subhead Support.
l HARQ Buffer Capability: The value of this parameter indicates the maximum
size of buffer that a sub-burst can occupy. The value of this parameter impacts the
transmission rate of the MS that enables the HARQ function.
l Number of UL/DL HARQ Channels: The value of this parameter needs to be
negotiated between the BS and the MS and set to the smallest value supported by
the BS and the MS. The value of this parameter and the value of HARQ Buffer
Capability together determine the peak rate of the MS that enables the HARQ.
l Maximum Number Of Bursts Per Frame Capability In HARQ: The value of
this parameter indicates the maximum number of bursts in each frame supported
by the HARQ. The value of this parameter impacts the number of MSs that a frame
can process synchronously.
(3) The BS saves the negotiation result. The DSA processing procedure during service
setup is started.
3. DSA processing procedure during service setup
During the service setup, whether the BS supports the HARQ function is negotiated through
the Dynamic Service Addition (DSA) procedure. The DSA processing procedure is
described as follows:
(1) The BS decides whether to enable HARQ according to MS service flow QoS
parameters, negotiated Number of UL/DL HARQ Channels and HARQ Buffer
Capability supported by the MS during SBC processing procedure, and service flow
delay threshold of the BS.
(2) The BS saves related negotiation parameters and sets up the HARQ connection
according to the negotiation parameters.
1.3.4 HARQ Processing in the User Plane

The BS performs HARQ processing in the user plane on the PHY layer and MAC layer.
Figure 1-3 shows the HARQ processing flow chart in the user plane.

DBS3900 WiMAX
Figure 1-3 HARQ processing flow chart in the user plane
The HARQ processing in the user plane is classified into DL processing in the user plane and
UL processing in the user plane.
1. HARQ DL processing in the user plane
As shown in Figure 1-3, the BS packs, fragments, and then assembles the data packets
from the classifier into a subburst, adds the CRC16 code, performs coding and modulation,
and then sends the subburst to the MS.
After an HARQ ACK Delay for DL Burst, the MS responds with an ACK or NACK
message through the ACK channel. The BS demodulates the message on the ACK channel,
and then performs HARQ allocation according to the demodulation result.
HARQ ACK Delay for DL Burst: It indicates the time an MS takes to responds with an
ACK or NACK message after receiving a sub-burst. The value of this parameter impacts
data transmission performance and system overhead over the air interface.
2. HARQ UL processing in the user plane
During UL processing in the user plane, the MS sends HARQ data according to the MAP
message sent by the BS. Then, the BS demodulates UL data. If the BS receives HARQ data
for the first time, its demodulation module decodes the data. If the BS receives the
retransmitted HARQ data, it combines the retransmitted data with the previously received
one and overwrites the original data in the buffer. Then, the decoding module performs
data decoding. The BS decides whether to allocate related resources for the retransmission
of the next frame of HARQ data according to the decoding result.

DBS3900 WiMAX
1.3.5 HARQ Allocation Algorithm and Buffer Management

The HARQ allocation algorithm and buffer management are performed on the PHY layer and
MAC layer of the BS.
Where,
l The PHY layer supports fast ACK channel demodulation and UL buffer management.
l The MAC layer supports HARQ burst allocation and DL buffer management.
The BS uses the HARQ ACK Delay for DL Burst parameter in the UCD message to define
how soon an MS responds with an ACK or NACK message after receiving a DL sub-burst.
The BS performs fast ACK channel demodulation for the ACK or NACK message received
from the MS, performs HARQ allocation according to the demodulation result and
retransmission times, and decides whether to empty the buffer corresponding to the DL HARQ
subchannel.
1.3.6 Power Control and AMC Processing for HARQ Links

This section describes AMC processing for DL HARQ and power control and AMC processing
for UL HARQ.
AMC Processing for the DL HARQ

The BS supports AMC processing for the DL HARQ, including the DL AMC processing for an
MS that uses both HARQ links and non-HARQ links. The demodulation thresholds of HARQ
and non-HARQ connections are different. Therefore, different AMC outer-loop thresholds are
used.
The MAC layer selects the DL modulation and coding mode for the HARQ connection according
to the DL outer-loop threshold and the CINR measured by the MS.
Power Control and AMC Processing for the UL HARQ

The BS supports power control and AMC processing for the UL HARQ, including UL power
control and AMC processing for an MS that uses both DL HARQ links and non-HARQ links.
The MAC layer periodically adjusts the UL outer-loop threshold for enabling an HARQ link
according to the CRC16 result on the PHY layer.
The MAC layer selects the UL modulation and coding mode and calculates the UL power control
result according to the UL outer-loop threshold and the CINR and RSSI measurement result on
the PHY layer.
1.4 Operations Related to HARQ

This section describes how to activate and deactivate the HARQ feature.
1.4.1 Activating the HARQ Feature

This section describes how to activate the HARQ feature. On the M2000 or Web LMT, you can
perform related configurations on the BS to activate the HARQ feature.
1.4.2 Deactivating the HARQ Feature

DBS3900 WiMAX
This section describes how to deactivate the HARQ feature. You can deactivate the HARQ
feature by setting demodulation mode parameter BIT#5 and modulation mode parameter BIT#4
to 0.
1.4.1 Activating the HARQ Feature

This section describes how to activate the HARQ feature. On the M2000 or Web LMT, you can
perform related configurations on the BS to activate the HARQ feature.
Context
The HARQ parameter configuration on the BS side is as follows:
NOTE
Before performing the HARQ parameter configuration on the BS side, ensure that the sector carrier is in
deactivated state. Step 2 to step 6 of the following configuration steps are not in a particular sequence.
Procedure
Step 1 Run MOD CARRIERBLOCKFLAG to deactivate the sector carrier.
For example:
MOD CARRIERBLOCKFLAG: SECTORID=0, CARRIERID=0, BLOCKFLAG=Blocked;
Step 2 Run MOD OFDMACAPABILITY to enable the HARQ UL/DL modulation mode,
demodulation mode, MAP capability, and UL ACK channel support. Modulation mode enabled
(BIT#4 set to 1) and demodulation mode enabled (BIT#5 set to 1) are the prerequisites for
enabling the HARQ.
For example:
MOD OFDMACAPABILITY: SECTORID=0, CARRIERID=0, DEMODULATION=37, MODULATION=20,
ULCTRLSUPP=4, OFDMAMAPCAP=6;
Step 3 Run MOD MACCAPABILITY to enable the BS to support the PDU SN extended subheader,
to set the BS-supported HARQ buffer size (5142 bits are recommended), and to set the HARQ-
supported maximum number of subbursts (49 is recommended) in a frame.
For example:
MOD MACCAPABILITY: SECTORID=0, CARRIERID=0, HEADERTYPESUPP=327647, EXTCAP=1,
HARQCHASEBUFCAP=5142, MAXBURINHARQ=49;
Step 4 Run MOD ULCHANPARA to configure the UL/DL HARQ maximum retransmission times,
HARQ DL ACK delay, and UL mode in the public area.
For example:
MOD ULCHANPARA: SECTORID=0, CARRIERID=0, HARQDELAYFORDLBURST=1, ULHARQMAXRETRAN=4,
RNGREGIONTYPE=3SYMBOLS1IRPR;
Step 5 Run MOD DLCHANPARA to configure the DL HARQ maximum retransmission times.
For example:
MOD DLCHANPARA: SECTORID=0, CARRIERID=0, HARQACKDELAYFORULBURST=1,
DLMAXHARQRETRAN=4;
Step 6 Run MOD RRMSOFT to enable the service flow priority threshold and service flow delay
threshold on the BS side. HARQ can be enabled for the service flow only when the previous
two thresholds are smaller than those thresholds in the QoS parameters set for the MS.
For example:
MOD RRMSOFT: PARANO=21, VALUE=0;

DBS3900 WiMAX
Step 7 Run MOD CARRIERBLOCKFLAG command to deactivate the sector carrier.
For example:
MOD CARRIERBLOCKFLAG: SECTORID=0, CARRIERID=0, BLOCKFLAG=Unblocked;
----End
1.4.2 Deactivating the HARQ Feature

This section describes how to deactivate the HARQ feature. You can deactivate the HARQ
feature by setting demodulation mode parameter BIT#5 and modulation mode parameter BIT#4
to 0.
Procedure
Step 1 Run MOD CARRIERBLOCKFLAG to deactivate the sector carrier.
For example:
Step 2 Run MOD OFDMACAPABILITY to set demodulation mode parameter BIT#5 and
modulation mode BIT#4 to 0 to deactivate the HARQ feature.
For example:
MOD OFDMACAPABILITY: SECTORID=0, CARRIERID=0,
DEMODULATION=5,MODULATION=4,ULCTRLSUPP=2,OFDMAMAPCAP=6;
Step 3 Run MOD CARRIERBLOCKFLAG command to deactivate the sector carrier.
For example:
MOD CARRIERBLOCKFLAG: SECTORID=0, CARRIERID=0, BLOCKFLAG=Unblocked;
----End
1.5 Maintenance Information of HARQ

This section describes the parameters and performance measurement items related to the HARQ
feature.
Parameters
Table 1-3, Table 1-4, Table 1-5, Table 1-6, Table 1-7, and Table 1-8 list the parameters related
to the HARQ feature.
Table 1-3 Parameters related to the MOD CARRIERBLOCKFLAG command
ID Name
SECTORID Sector ID
CARRIERID Carrier ID
BLOCKFLAG Block flag

DBS3900 WiMAX
Table 1-4 Parameters related to the MOD ULCHANPARA command

ID Name
SECTORID Sector ID
HARQDELAYFORDLBURST HARQ delay frames for the downlink burst
ULHARQMAXRETRAN Maximum retransmission times of the uplink

HARQ
Table 1-5 Parameters related to the MOD DLCHANPARA command

ID Name
SECTORID Sector ID
HARQACKDELAYFORULBURST HARQ ACK delay frames for uplink BURST
DLMAXHARQRETRAN Maximum retransmission times of downlink

HARQ
Table 1-6 Parameters related to the MOD OFDMACAPABILITAY command

ID Name
SECTORID Sector ID
DEMODULATION Demodulation mode
MODULATION Modulation mode
ULCTRLSUPP Uplink control support
OFDMAMAPCAP OFDMA MAP capability
Table 1-7 Parameters related to the MOD MACCAPABILITY command

ID Name
SECTORID Sector ID
HEADERTYPESUPP MAC header and extended subheader support

DBS3900 WiMAX
ID Name
HARQCHASEBUFCAP HARQ chase combining and initial ranging

buffer size
EXTCAP Extended subheader capability
MAXBURINHARQ Maximum number of burst per frame

capability in HARQ
Table 1-8 Parameters related to the MOD RRMSOFT command

ID Name
PARANO Software parameter number
Performance Counters
The performance counters related to the HARQ feature are as follows:
l Total Number of HARQ Retransmission Times
l Total Number of HARQ Transmission Times
1.6 Reference Information of HARQ

The protocol that the HARQ feature complies with is IEEE 802.16-2004/Cor2/D3 with latest

DBS3900 WiMAX
Feature Configuration Guide 2 Multi-Antenna
2 Multi-Antenna
About This Chapter
Multi-antenna is a technology that uses multiple antennas at the transmitter and receiver. Multi-
antenna systems can be categorized into single input multiple output (SIMO) diversity, multiple
input single output (MISO) diversity, and multiple input multiple output (MIMO) diversity. This
chapter describes the basic concepts, functions, and implementation method of the multi-antenna
feature.
2.1 Overview of Multi-Antenna

This section describes the definition, purpose, specifications, and impact of the multi-antenna
feature.
2.2 Availability of Multi-Antenna
This section describes the license of and version information about the multi-antenna feature
and the involved network elements (NEs).
2.3 Description of Multi-Antenna
This section describes the principles and application strategy of the key multi-antenna
technologies.
2.4 Operations Related to Multi-Antenna
This section describes how to activate and deactivate the multi-antenna feature.
2.5 Maintenance Information of Multi-Antenna
This section describes the parameters and performance counters related to the multi-antenna
feature.
2.6 Reference Information of Multi-Antenna
The protocol that the multi-antenna feature complies with is IEEE 802.16-2004/Cor2/D3 with
latest SRD and WiMAX Forum Network Architecture Release 1.2.0.

DBS3900 WiMAX
2 Multi-Antenna Feature Configuration Guide
2.1 Overview of Multi-Antenna

This section describes the definition, purpose, specifications, and impact of the multi-antenna
feature.
Definition
The IEEE 802.16e system supports multiple multi-antenna technologies, including downlink
transmitter diversity (such as Matrix A and CDD), space division multiplexing (such as Matrix
B), uplink multi-antenna receiver (such as MRC), and uplink collaborative MIMO (such as
collaborate spatial multiplex: CSM).
l If the BS uses two transmit antennas, two-antenna Matrix A or Matrix B transmission mode
can be adopted. Two-antenna CDD transmission mode can be adopted for common
channels like the Preamble.
l If the BS uses four transmit antennas, Matrix A+CDD or Matrix B+CDD transmission can
be adopted. For common channels like the Preamble, four-antenna CDD transmission can
be adopted.
l If the terminal supports demodulation under Matrix A or Matrix B, the BS transmits signals
in these two MIMO modes to the terminal.
The multi-antenna technologies are defined as follows:

l Downlink transmitter diversity: The BS uses multiple antennas for transmission. Signals
are processed (such as STC) by the transmitter and then sent through multiple antennas.
Using transmitter diversity can achieve the diversity gain and the power gain from multi-
antenna transmission.
l Downlink space division multiplexing: Different streams are transmitted through the same
time and frequency resources. These streams are identified with their antennas. Using space
division multiplexing can achieve multiplexing gain.
l Uplink multi-antenna receiver: It is also called diversity receive. It is the most frequently
used signal receive mode in mobile communications systems. The BS receives data from
different antennas and combines them to counteract the fading effect. Through diversity
receiving, array gain and diversity gain can be obtained.
l Uplink CSM: It is a transmit mode. In this transmit mode, multiple SSs that are identified
with their transmit antennas use the same time and frequency resources. Using this
technology can achieve multiplexing gain.
Purpose
The multi-antenna technology can help significantly increase the system capacity or expand the
coverage without increasing the bandwidth so that the spectrum resources can be fully used or
the number of sites can be reduced. With this technology, the customers can reduce the CAPEX
for the WiMAX market and protect their investment, thus bringing better service experience to
their subscribers.
Specifications
System peak throughput:

DBS3900 WiMAX
l Under the configuration of 4T4R, the peak downlink throughput in each sector carrier is
45 Mbit/s. Conditions: 10 MHz bandwidth, PUSC/all sc, 35:12 subframe ratio, and Matrix
B.
l Under the configuration of 4T4R, the peak uplink throughput in each sector carrier is 10
Mbit/s. Conditions: 10 MHz bandwidth, PUSC/all sc, 26:21 subframe ratio, and CSM.
Impact
Multi-antenna technologies do not affect each other. When used together with other features,
the multi-antenna feature has the following impacts on the system.
Two-antenna Matrix A and two-antenna Matrix B:
l On the signaling system: The system must support the MAP format of MIMO.
l On Zone management: The system must support the allocation and management of the STC
Zone.
Four-antenna Matrix A + CDD and four-antenna Matrix B + CDD:
l On the signaling system: The system must support the MAP format of MIMO.
l On Zone management: The system must support the allocation and management of the STC
Zone.
Terms
Term Definition
Throughput Throughput is the maximum transmission rate that a measured object

can reach without packet loss. The measured object may be a system, a
piece of equipment, a connection, or a service type. Throughput can be
measured by bandwidth.
Space-time Space-time coding (STC) is a signal coding technology that can be used
coding to obtain enhanced data transmission rates. It combines the space
transmitted signals and time transmitted signals. In essence, it is a two-
dimension (space dimension and time dimension) processing method. In
a new-generation communication system, space diversity achieved
through multiple transmit and receive antennas raises the system
capacity and information rate. Meanwhile, different signals are
transmitted in different timeslots by the same antenna, and therefore
receive diversity can be implemented at the receiver end. In this way,
diversity and coding gains are obtained to achieve high-speed
transmission. This technology is used in 3G communications systems to
increase spectrum utilization.
mTnR The BS or SS has m transmit antennas and n receive antennas.
m*n The uplink or downlink links have m transmit antennas and n receive
antennas.

DBS3900 WiMAX
Acronyms and Abbreviations

Acronym and
Abbreviation Expansion
MS Mobile Station
CSM Collaborative Spatial Multiplexing
CDD Cyclic Delay Diversity
MIMO Multi Input Multi Output
OFDM Orthogonal Frequency Division Multiplex
OFDMA Orthogonal Frequency Division Multiple Access
BS Base Station
STC Space Time Coding
MRC Maximum Ratio Combining
2.2 Availability of Multi-Antenna

This section describes the license of and version information about the multi-antenna feature
and the involved network elements (NEs).
NEs Involved
The multi-antenna feature requires the interoperation between the SS/MS and the BS. Table
2-1 lists the NEs involved in the multi-antenna feature.
Table 2-1 NEs involved in the multi-antenna feature
AAA DHCP
√ √ - - - √
NOTE
In Table 2-1, √ is used to mark the NEs that are involved in the feature, and - is used to mark the NEs
that are not involved in the feature.
Version Support
Table 2-2 lists the version that support the multi-antenna feature.

DBS3900 WiMAX
Table 2-2 Version that support the multi-antenna feature

Product Version
License Restriction
The usage of the multi-antenna feature is controlled by a license.
2.3 Description of Multi-Antenna

This section describes the principles and application strategy of the key multi-antenna
technologies.
2.3.1 Key Multi-Antenna Technologies

The major multi-antenna application is based on the MIMO + CDD transmit mode and MRC/
CSM receive mode.
2.3.2 Strategy of Multi-Antenna Applications
This section describes the strategy of multi-antenna applications supported by the current
Huawei WiMAX BSs.
2.3.1 Key Multi-Antenna Technologies

The major multi-antenna application is based on the MIMO + CDD transmit mode and MRC/
CSM receive mode.
Downlink MIMO
Downlink MIMO is a multi-antenna open-loop technology in which multiple antennas are used
to transmit signals without knowing downlink channel condition. The WiMAX system profile
defines that the major downlink MIMO technologies are Matrix A and Matrix B with vertical
coding.
In Matrix A, the two links of transmitted signals are content-related. Under the impact (reflection
and refraction) of physical space environment, a transmitted signal is dispersed into multiple
signals with different phases. In optimum conditions, two receiving signals may be combined
into one signal with the power doubled. In this way, the receiving diversity can increase by 3
dB to enhance the system coverage. Figure 2-1 shows the transmit matrix of Matrix A.
Figure 2-1 Transmit matrix of Matrix A
In the scenario of Matrix A transmission, the recommended number of receive antennas at the
receiver side is two or more. Although only one antenna can also demodulate data, such
configuration is not recommended because the performance is poor.

DBS3900 WiMAX
Matrix B: Different streams are transmitted through two antennas over the same time and
frequency resources. Figure 2-2 shows the transmit matrix of Matrix B.
Figure 2-2 Transmit matrix of Matrix B
In the scenario of Matrix B transmission, the receiver must be equipped with two or more receive
antennas to demodulate data because it must separate the two streams using the same resources.
Matrix B cannot provide diversity gain. Instead, it brings space multiplexing gain because two
streams use the same time and frequency resources. The performance of Matrix B can be ensured
when the signal-to-noise ratio is high and the channels of the two channels of the two streams
must be uncorrelated.
The system can perform self-adaptive switching between Matrix A and Matrix B through the
adaptive MIMO switching (AMS) algorithm, which helps maximize the spectrum gain.
Downlink CDD
CDD is implemented through the transmission of data duplicate with different delays through
different antennas. This technology can provide diversity gain and improve performance. The
IEEE 802.16e standard specifies that the downlink preambles and the first downlink zone cannot
use STC coding. However, the CDD can be used to improve the demodulation performance of
the common channel, thus improving the coverage of common channels. With the CDD
technology, the power gain can be obtained from multi-antenna transmission. In the scenario of
channel fading, this technology can even bring a small amount of diversity gain. In the scenario
of LOS, no diversity gain can be obtained.
Figure 2-3 shows principle of CDD.
Figure 2-3 Principle of four-antenna CDD
Downlink MIMO + CDD

For downlink non-STC Zone, CDD can be used to obtain diversity gain. The CDD technology
can also logically combine multiple physical antennas into a virtual antenna, thus implementing
four-antenna downlink MIMO, that is, Matrix A + CDD and Matrix B + CDD.

DBS3900 WiMAX
There are two modes of four-antenna downlink transmission.

1. The Preamble and data on common channels are transmitted in CDD mode. Figure 2-4
shows the transmission mode.
Figure 2-4 CDD transmission mode
2. Transmission mode of traffic channel. On the traffic channel, the four-antenna MIMO +
CDD transmission mode is Matrix A+CDD/Matrix B+CDD self-adaptive switching.
l Figure 2-5 shows the mapping between the Matrix A + CDD baseband data and antenna.
l Figure 2-6 shows the mapping between the Matrix B + CDD baseband data and antenna.
Figure 2-5 Transmit matrix of Matrix A

DBS3900 WiMAX
Figure 2-6 Transmit matrix of Matrix B
Uplink Multi-Antenna Technologies

There are two uplink multi-antenna technologies.
1. Uplink diversity receiving. Uplink receive diversity is the most commonly used multi-
antenna technology. The BTS performs coherent combination for the signals received by
multiple antennas. In this way, array gains and four-way receiver diversity are obtained.
The receive algorithm is maximum ratio combining (MRC). In MRC, coherent combination
is performed for the signals received by multiple antennas. Through MRC, array gains and
diversity gains can be obtained.
2. Uplink CSM. In uplink CSM, the same time or frequency resources are scheduled for two
terminals equipped with respectively a single transmit antenna. The BS uses multiple
antennas to receive signals, thus distinguishing between subscribers and improving uplink
capacity. Figure 2-7 shows principle of uplink CSM.
Figure 2-7 Principle of uplink CSM

DBS3900 WiMAX
2.3.2 Strategy of Multi-Antenna Applications

This section describes the strategy of multi-antenna applications supported by the current
Huawei WiMAX BSs.
With the MIMO license, the BS does not use MIMO transmission by default regardless of the
four-antenna or two-antenna transmission configuration.
l If the MS does not support MIMO or the downlink transmission is implemented in a non-
STC Zone, CDD is used. The system reserves a Zone dedicated for this transmission mode.
The MSs in this Zone automatically select the CDD mode to transmit data.
l If the MS supports Matrix A and Matrix B, the system determines the MIMO mode to be
used according to the actual channel conditions. The switching between Matrix A and
Matrix B is performed automatically.
The performance of a four-antenna system varies with the scenario.

l If the scenario is sensitivity-limited, the four-antenna configuration can significantly
improve the performance.
l If the scenario is interference-limited, the four-antenna configuration contributes little to
performance improvement.
The multi-antenna feature supports four-antenna rollback and restoration.

l If the BS uses the configuration of 4T4R, the system can automatically reduce the antenna
specifications to 2T2R or 1T1R when one or more receive/transmit paths are faulty. When
all the paths are faulty, the system automatically deactivates sector carriers. After the fault
is rectified, the system automatically uses 1T1R, 2T2R, or 4T4R.
l If the BS uses the configuration of 2T2R by default, the system can automatically reduce
the antenna specifications to 1T1R when a certain receive/transmit path is faulty. When all
the paths are faulty, the system automatically deactivates sector carriers. After the fault is
rectified, the system automatically uses 1T1R or 2T2R.
2.4 Operations Related to Multi-Antenna

This section describes how to activate and deactivate the multi-antenna feature.
2.4.1 Activating the Multi-Antenna Feature

This section describes how to activate the MIMO function and the CSM function.
2.4.2 Deactivating the Multi-Antenna Feature
This section describes how to deactivate the multi-carrier feature and the CSM function.
2.4.1 Activating the Multi-Antenna Feature

This section describes how to activate the MIMO function and the CSM function.
Prerequisite
l The M2000 has issued the license to the NE.
l The basic configurations related to sector carriers have been implemented.

DBS3900 WiMAX
Context
l You can set the parameters through the Web LMT or the M2000.
l The MOD command parameters used in steps 2 to 5 and step 7 can be modified only after
sector carriers are deactivated. The modifications take effect after the sector carriers are
activated again.
Procedure
Step 1 Query and set the license information.
1. Run the LST CARRIERLICENSEINFO command to query the information of the license
of a carrier.
Example:
LST CARRIERLICENSEINFO: SECTORID=0, CARRIERID=0;
2. Run the MOD CARRIERLICENSEINFO command to set the four-antenna MIMO

control parameters and two-antenna MIMO control parameters for a carrier.
Example:
MOD CARRIERLICENSEINFO: SECTORID=0, CARRIERID=0, TWOANTENNAMIMO=ON,
FOURANTENNAMIMO=ON;
Step 2 Query and set the numbers of transmit antennas and receive antennas of a BS.
1. Run the LST SECTOR command to query the numbers of the transmit antennas and
receive antennas of a sector.
Example:
LST SECTOR: SECTORID=0;
2. Run the MOD SECTOR command to set the numbers of the transmit antennas and receive
antennas of a sector.
Example:
MOD SECTOR: SECTORID=0, TXANTNUM=4, RXANTNUM=4;
NOTE
The values of TXANTNUM and RXANTNUM can be 2 or 4.
Step 3 Query and set the antenna mode of a BS.

1. Run the LST CARRIERBASICINFO command to query the antenna mode of a sector
carrier.
Example:
LST CARRIERBASICINFO: SECTORID=0, CARRIERID=0;
2. Run the MOD CARRIERBASICINFO command to set the antenna mode of a sector
carrier.
Example:
MOD CARRIERBASICINFO: SECTORID=0, CARRIERID=0, ANTBITMAP=4T4R;
NOTE
The actual value range of ANTBITMAP is from 0 to 2. The value 0 means using the antennas A and
B of a 4T4R RRU to set up a 2T2R configuration. The value 1 means using the antennas C and D of
a 4T4R RRU to set up a 2T2R configuration. The value 2 means using the antennas A, B, C, and D
of a 4T4R RRU to set up a 4T4R configuration.
Step 4 Query and set the iCSD switch.

1. Run the LST RRMSOFT command to query the iCSD switch.
Example:
LST RRMSOFT: PARANO=47;

DBS3900 WiMAX
2. Run theMOD RRMSOFT command to set parameter 47 to 1.

Example:
NOTE
Parameter 47 indicates the iCSD switch. The value 0 means that the function is disabled, and the
value 1 means that the function is enabled.
Step 5 Query and set the STC Zone capability of a BS.

1. Run the LST CARRIERZONEINFO command to query the STC Zone capability of the
BS.
Example:
LST CARRIERZONEINFO: SECTORID=0, CARRIERID=0;
2. Run the MOD CARRIERBASICINFO and MOD CARRIERZONEINFO commands

to set the STC Zone capability of the BS.
Step 6 Query and set the MIMO and the AMS switches.
1. Run the LST RRMSWITCH command to query the MIMO switch of a sector carrier.
Example:
LST RRMSWITCH: SECTORID=0, CARRIERID=0;
2. Run the MOD RRMSWITCH command to set the MIMO switch of a sector carrier.
Example:
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, DLAMCSWITCH=ON, DLMIMOSWITCH=ON,
DLAMSSWITCH=ON, MIMOBAMCSWITCH=ON;
Step 7 Activate the uplink CSM function.

1. Run the LST OFDMACAPABILITY command to query the BS's capability in MIMO
negotiation.
Example:
LST OFDMACAPABILITY: SECTORID=0, CARRIERID=0;
2. Run the MOD OFDMACAPABILITY command to set the BS's capability in MIMO
negotiation.
Example:
MOD OFDMACAPABILITY: SECTORID=0, CARRIERID=0, MODULATIONMIMOSUPP=64;
3. Activate the uplink CSM function. To activate the uplink CSM function, run MOD
RRMSWITCH to set Switch of uplink CSM to ON.
Example:
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, ULCSMSWITCH=ON;
Step 8 Query and set the rollback and restoration switch for the multi-antenna feature.
1. Run the LST RRMSOFT command to query the rollback and restoration switch for the
multi-antenna feature.
Example:
LST RRMSOFT: PARANO=112;
2. Run the MOD RRMSOFT command to set parameter 112 to 1.

Example:
NOTE
Parameter 112 is the rollback and restoration switch for the multi-antenna feature. The value 0 means
that the function is disabled, and the value 1 means that the function is enabled.
----End

DBS3900 WiMAX
2.4.2 Deactivating the Multi-Antenna Feature

This section describes how to deactivate the multi-carrier feature and the CSM function.
Procedure
Step 1 To deactivate the downlink MIMO feature, run MOD RRMSWITCH to set Switch of
downlink MIMO to OFF. To deactivate the Matrix A and Matrix B adaptive function, set
Switch of the AMS algorithm on the downlink to OFF.
Example:
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, DLMIMOSWITCH=OFF, DLAMSSWITCH=OFF;
Table 2-3 lists the parameters related to the command.
Table 2-3 Parameters related to the MOD RRMSWITCH command
ID Name Value Range
SECTORID Sector ID 0, 1, 2, 3, 4, 5
CARRIERID Carrier ID 0, 1
DLMIMOSWITCH Switch of downlink MIMO On: 1 (enabled); OFF: 0

(disabled)
DLAMSSWITCH Switch of the AMS algorithm On: 1 (enabled); OFF: 0

on the downlink (disabled)
Step 2 To deactivate the uplink CSM function, run MOD RRMSWITCH to set Switch of uplink
CSM to OFF.
NOTE
If the command does not take effect, deactivate the sector carrier, and then activate it again.
Example:
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, ULCSMSWITCH=OFF;
Table 2-4 lists the parameters related to the command.
ID Name Value Range
SECTORID Sector ID 0, 1, 2, 3, 4, 5
CARRIERID Carrier ID 0, 1
ULCSMSWITCH Switch of uplink CSM On: 1 (enabled); OFF: 0

(disabled)
----End

DBS3900 WiMAX
2.5 Maintenance Information of Multi-Antenna

This section describes the parameters and performance counters related to the multi-antenna
feature.
Parameters
Table 2-5, Table 2-6, Table 2-7, and Table 2-8 list the parameters related to the multi-carrier
feature.
Table 2-5 Parameters related to the MOD SECTOR command
ID Name
SECTORID Sector ID
TXANTNUM Number of transmit antennas
RXANTNUM Number of receive antennas
Table 2-6 Parameters related to the MOD OFDMACAPABILITY command
ID Name
SECTORID Sector ID
DEMODULATION Demodulation mode
MODULATION Modulation mode
DEMODULATIONMIMO- Supported MIMO demodulation mode

SUPP
MODULATIONMIMOSUPP Supported MIMO modulation mode
ID Name
SECTORID Sector ID
DLMIMOSWITCH Switch of downlink MIMO
DLAMSSWITCH Switch of the AMS algorithm on the downlink
ULCSMSWITCH Switch of uplink CSM

DBS3900 WiMAX
Table 2-8 Parameters related to the MOD RRMSOFT command

ID Name
PARANO Software parameter No.
VALUE Software parameter value
None.
2.6 Reference Information of Multi-Antenna

The protocol that the multi-antenna feature complies with is IEEE 802.16-2004/Cor2/D3 with

DBS3900 WiMAX
Feature Configuration Guide 3 Power Control and AMC
3 Power Control and AMC
About This Chapter
Power control and AMC algorithms are core algorithms of WiMAX. The MS and BS cooperate
over the R1 interface to achieve power control and AMC. This chapter describes the basic
concepts, functions, and implementation method of the power control and AMC feature.
3.1 Overview of Power Control and AMC

This section describes the definition, purpose, specifications, and impact of the power control
and AMC feature.
3.2 Availability of Power Control and AMC
This section describes the network elements (NEs) involved in the power control and AMC
feature and the earliest versions that support this feature.
3.3 Description of Power Control and AMC
According to the IEEE 802.16 REV2 standard, the WiMAX system supports only uplink power
control, that is, only the transmit power of the MS is controlled. Uplink AMC is used as the
supplement to uplink power control.
3.4 Operations Related to Power Control and AMC
This section describes how to activate and deactivate the power control and AMC feature.
3.5 Maintenance Information of Power Control and AMC
This section describes the parameters and performance measurement items related to the power
control and AMC feature.
3.6 Reference Information of Power Control and AMC
The protocol that the power control and AMC feature complies with is IEEE 802.16-2004/Cor2/
D3 with latest SRD and WiMAX Forum Network Architecture Release 1.2.0.

DBS3900 WiMAX
3 Power Control and AMC Feature Configuration Guide
3.1 Overview of Power Control and AMC

This section describes the definition, purpose, specifications, and impact of the power control
and AMC feature.
Definition
Power control is a process in which the MS or BS uses certain rules to adjust and control the
transmit power according to the change in the channel condition and the power of the received
signal. In the WiMAX system, power control is implemented mainly to control the transmit
power of the MS.
AMC is used to determine a coding and modulation mode that is suitable for the channel quality
and the system capacity.
Purpose
The purpose of power control is to keep terminal transmit power to the lowest level that can
ensure the throughput of the terminal. This mechanism reduces power consumption and the
interference to other terminals.
In AMC, an appropriate MCS is chosen according to channel quality and system capacity. In
this way, data transmission efficiency is maximized, and a high rate is achieved.
When the power control and AMC functions are both used, the system average throughput can
be improved, and the transmission quality can be ensure. When the system capability is limited,
the primary goal is to lower the PER to the target value and minimize reverse interference.
Specifications
This feature supports uplink closed-loop power control, uplink open-loop power control, uplink
AMC, and downlink AMC.
This feature supports the following uplink MCSs:
l QPSKCC1/2
l QPSKCC3/4
l 16QAMCC1/2
l 16QAMCC3/4
l QPSKCTC1/2
l QPSKCTC3/4
l 16QAMCTC1/2
l 16QAMCTC3/4
This feature supports the following downlink MCSs:

l QPSKCC1/2
l QPSKCC3/4
l 16QAMCC1/2
l 16QAMCC3/4

DBS3900 WiMAX
l 64QAMCC1/2
l 64QAMCC2/3
l 64QAMCC3/4
l QPSKCTC1/2
l QPSKCTC3/4
l 16QAMCTC1/2
l 16QAMCTC3/4
l 64QAMCTC1/2
l 64QAMCTC2/3
l 64QAMCTC3/4
l 64QAMCTC5/6
NOTE
Not all MCSs must be used.
Impact
None.
Terms
Term Definition
Uplink An uplink is a channel on which data is transmitted from the terminal to

the BS.
Downlink A downlink is a channel on which data is transmitted from the BS to the

terminal.

Acronym and
AMC Adaptive Modulation and Coding
BS Base Station
BWA Broadband Wireless Access
CINR Carrier to Interference and Noise Ratio
FEC Forward Error Correction
MC Modulation and Coding
MCS Modulation Coding Scheme
MS Mobile Station

DBS3900 WiMAX
Acronym and
PER Packet Error Rate
3.2 Availability of Power Control and AMC

This section describes the network elements (NEs) involved in the power control and AMC
feature and the earliest versions that support this feature.
NEs Involved
The power control and AMC feature requires the joint work of the SS/MS and the BS. Table
3-1 lists the NEs involved in the power control and AMC feature.
Table 3-1 NEs involved in the power control and AMC feature
AAA DHCP
√ √ - - - √
NOTE
Version Support
Table 3-2 lists the version that supports the power control and AMC feature.
Table 3-2 Version that supports the power control and AMC feature
Product Version
BS DBS3900 V300R002C03
License Restriction
The usage of this feature is not controlled by a license.
3.3 Description of Power Control and AMC

According to the IEEE 802.16 REV2 standard, the WiMAX system supports only uplink power
control, that is, only the transmit power of the MS is controlled. Uplink AMC is used as the
supplement to uplink power control.

DBS3900 WiMAX
Power Control
By control mode, power control is classified into closed-loop power control and open-loop power
control. Closed-loop power control is further classified into inner-loop power control and outer-
loop power control.
l Closed-loop power control
The BS measures the signal quality on the uplink and sends power control instructions to
the MS.
– Inner-loop power control
The BS measures the signal quality on the uplink and adjusts the transmit power of the
MS according to CINR Target Value.
– Outer-loop power control
The BS adjusts the uplink AMC thresholds according to the PER.
l Open-loop power control
In an open-loop power control, the terminal determines its transmit power according to the
path loss. If the uplink path loss is high, the terminal increases its transmit power. If the
path loss is low, the terminal decreases its transmit power.
Uplink Inner-Loop Power Control
In inner-loop power control, the BS compares the measured CINR on the uplink with CINR
Target Value to determine the quality of the uplink signal.
l When the measured CINR on the uplink is greater than CINR Target Value, that is, the
quality of the uplink signal is good, the BS instructs the MS to lower its transmit power.
l When the measured CINR on the uplink is smaller than CINR Target Value, that is, the
quality of the uplink signal is poor, the BS instructs the MS to raise its transmit power.
The BS sends the adjusted value to the MS over the air interface.
NOTE
You can run the MOD ULAMCTHRESH command to set CINR Target Value for all the MSs under a
carrier. Here, the default value is recommended. For details, see 3.4.1 Activating the Power Control and
AMC Feature.
Uplink Outer-Loop Power Control

In outer-loop power control, the BS measures the actual value of the PER and adjusts the values
of CINR Target Value, CINR Up Threshold, and CINR Low Threshold for the MS according
to the values of PER Target Value for different services. CINR Up Threshold and CINR Low
Threshold after adjustment are used for decision on inner-loop power control and AMC so that
the measured values of the PER for different services are close to the values of PER Target
Value for different services.
Different target PERs are set for different QoS classes. If the target value is too small, the quality
of the services can be better ensured but more power is consumed. If the value is too great, the
quality of the services cannot be ensured but the power consumption is low. This value, therefore,
must help balance QoS and power consumption so that QoS can be ensured with the lowest
power consumption.

DBS3900 WiMAX
NOTE
l Different service scheduling types (UGS, ertPS, rtPS, nrtPS, and BE services) have different values of
PER Target Value.
l You can run the MOD ULPERTHRESH command to set PER Target Value for all the MSs under
a carrier. Here, the default value is recommended. For details, see 3.4.1 Activating the Power Control
and AMC Feature.
The thresholds are adjusted by steps. The adjustments are accumulated. CINR threshold
currently used for inner-loop power control and AMC = Initial value of CINR Target Value or
CINR Low Threshold or CINR Up Threshold for all the MSs under a carrier + Accumulated
adjusted value
l If the measured the PER is higher than PER Target Value, you can infer that CINR Target
Value, CINR Low Threshold, or CINR Up Threshold is too low. In such case, the BS
automatically raises CINR Target Value, CINR Low Threshold, or CINR Up
Threshold for the MS.
l If the measured value of the PER is smaller than PER Target Value, the CINR Target
Value, CINR Low Threshold, or CINR Up Threshold is too high, and the BS
automatically lowers CINR Target Value, CINR Low Threshold, or CINR Up
Threshold for the MS.
This process is outer-loop power control.
Uplink Open-Loop Power Control
The MS adjusts its transmit power according to the quality of the downlink signal. Open-loop
power control is fast and causes fewer overheads on the air interface. The drawback of open-
loop power control is low precision.
Change Between Uplink Power Control Modes
The uplink power control mode can be changed between closed-loop power control and open-
loop power control. Closed-loop power control is precise but slow and requires more overheads
on the air interface. Open-loop power control is imprecise but requires fewer overheads on the
air interface and is faster.
A change between the uplink power control modes is originated by the BS or MS. When the
change is originated by the BS, the BS sends the PMC-RSP message to the MS, and the MS
responds with the PMC-REQ message acknowledging, the receipt of the change instruction.
When the MS receives the PMC-RSP message that indicates the power control mode of the MS
changing from closed-loop power control to open-loop power control, the MS can start uplink
data transmission only if it has received the UL noise and interference level IE message.
AMC
Uplink AMC
The basic principle of uplink AMC is that the BS instructs the MS to use a low MCS when the
measured CINR is below the CINR Low Threshold for the FEC. The BS instructs the MS to
use a high-level MCS when the measured CINR is above CINR Up Threshold for the FEC.
NOTE
You can run the MOD ULAMCTHRESH command to set CINR Lower Threshold and CINR Upper
Threshold for all the MSs under a carrier. Here, the default values are recommended. For details, see 3.4.1
Activating the Power Control and AMC Feature.
Generally, uplink inner-loop power control is used together with AMC. In this way, power
control is implemented to adjust the actual CINR, and MCS is adjusted so that the uplink CINR

DBS3900 WiMAX
of the MS stays in the required range. Uplink inner-loop power control and uplink AMC are
implemented at the same time. When the uplink signal is poor, the MCS is lowered or the transmit
power of the MS is raised to ensure correct signal demodulation on the uplink. When the uplink
signal becomes good, the MCS is raised or the transmit power of the MS is lowered to ensure
correct signal demodulation on the uplink.
If the values of the upper CINR threshold, lower CINR threshold, and target CINR threshold of
an MCS is too great, a low MCS may be used when the demodulation on the higher MCS is still
possible, resulting in the decrease of throughput. If the values are too small, an MCS may be
used to transmit data even when it is unable to support the demodulation, resulting in high PER,
which seriously affect the service quality.
Downlink AMC
Closed-loop power control is used together with the mode of the MS requesting the MCS. The
MS reports the downlink CINR, and the BS determines the downlink MCS. If the value of the
parameter DownLink MS AMC Switch is set to ON, the system prefers the downlink MCS
reported by the MS. If the MS does not report the MCS, the BS determines the downlink MCS.
If the value of the parameter DownLink MS AMC Switch is set to OFF, the BS determines
the downlink MCS.
NOTE
You can run the MOD RRMSWITCH command to configure the value of the parameter DownLink MS
AMC Switch.
You can run the MOD DLAMCTHRESH command to set CINR Lower Threshold and CINR Upper
Threshold for all the MSs under a carrier. Here, the default values are recommended. For details, see 3.4.1
Activating the Power Control and AMC Feature.
3.4 Operations Related to Power Control and AMC

This section describes how to activate and deactivate the power control and AMC feature.
3.4.1 Activating the Power Control and AMC Feature

This section describes how to activate the power control and AMC feature. On the M2000 or
Web LMT, you can run relevant MML commands to set specific parameters to activate the power
3.4.2 Deactivating the Power Control and AMC Feature
This section describes how to deactivate the power control and AMC feature. On the M2000 or
web LMT, you can run an associated MML command to deactivate the power control and AMC
feature.
3.4.1 Activating the Power Control and AMC Feature

This section describes how to activate the power control and AMC feature. On the M2000 or
Web LMT, you can run relevant MML commands to set specific parameters to activate the power
Procedure
l Activate uplink inner-loop power control

DBS3900 WiMAX
1. To activate uplink inner-loop power control, run the MOD RRMSWITCH command,
with the value of the parameter UpLink Power Control Mode
(ULPWRCTRLMODE) set to INNERLOOP.
l Activate uplink outer-loop power control.
1. To activate uplink outer-loop power control, run the MOD RRMSWITCH command,
with the value of the parameter UpLink Outer Loop Power Control Switch
(ULOUTERLOOPPOWERSWITCH) set to ON.
2. If necessary, run the MOD ULPERTHRESH command to change the target PER
value and maximum adjustment step of each service. Generally, the default value is
recommended.
For example, the target PER and maximum adjustment step of the BE service are
BePer Target Value (BEPERTARGET) and BePer Maximum Adjust Step
(BEMAXADJSTEP) respectively.
l Activate uplink open-loop power control.
1. Run the MOD RRMSWITCH command, with the value of the parameter UpLink
Power Control Mode (ULPWRCTRLMODE) set to
OPENLOOP_RETENTION or OPENLOOP_RESET so that when a terminal
enters or re-enters the network, the BS sends a PMC-RSP message and change the
mode to open-loop mode.
l Activate uplink AMC.
1. To activate uplink AMC, run the MOD RRMSWITCH command, with the value of
the parameter UpLink AMC Switch (ULAMCSWITCH) set to ON.
2. If necessary, run the MOD ULAMCTHRESH command to modify the initial values
of the parameters CINR Target Value (CINRTARGET), CINR Up Threshold
(CINRUPTHRE), CINR Low Threshold (CINRLOWTHRE), and Maximum
Adjust Step(MAXADJUSTSTEP) for all the MSs under a carrier. Generally, the
default value is recommended.
l Activate downlink AMC.
1. To activate downlink AMC, run the MOD RRMSWITCH command, with the value
of the parameter DownLink AMC Switch (DLAMCSWITCH) set to ON.
2. If necessary, run the MOD DLAMCTHRESH command to modify the initial values
of the parameters CINR Up Threshold (CINRUPTHRE), and CINR Low
Threshold (CINRLOWTHRE) for all the MSs under a carrier. Generally, the default
value is recommended.
----End
3.4.2 Deactivating the Power Control and AMC Feature

This section describes how to deactivate the power control and AMC feature. On the M2000 or
web LMT, you can run an associated MML command to deactivate the power control and AMC
feature.
Procedure
l Deactivate uplink inner-loop power control.
1. To deactivate uplink inner-loop power control, run the MOD RRMSWITCH
command, with the value of the parameter UpLink Power Control Mode
(ULPWRCTRLMODE) set to OFF.

DBS3900 WiMAX
l Deactivate uplink AMC.

1. To deactivate uplink AMC, run the MOD RRMSWITCH command, with the value
of the parameter UpLink AMC Switch (ULAMCSWITCH) set to OFF.
l Deactivate uplink outer-loop power control.
1. To deactivate uplink outer-loop power control, run the MOD RRMSWITCH
command, with the value of the parameter UpLink Outer Loop Power Control
Switch (ULOUTERLOOPPOWERSWITCH) set to OFF.
l Deactivate uplink open-loop power control.
1. Run the MOD RRMSWITCH command, with the value of the parameter UpLink
Power Control Mode (ULPWRCTRLMODE) set to OFF so that the BS does not
initiate any power control and change the mode to open-loop mode.
l Deactivate downlink AMC.
1. To deactivate downlink AMC, run the MOD RRMSWITCH command, with the
value of the parameter DownLink AMC Switch (DLAMCSWITCH) set to OFF.
----End
3.5 Maintenance Information of Power Control and AMC

This section describes the parameters and performance measurement items related to the power
Parameters
Table 3-3, Table 3-4, Table 3-5, and Table 3-6 list the parameters related to the power control
and AMC feature.

ID Name
ULPWRCTRLMODE UL power control mode
ULOUTERLOOPPOWERSWITCH Switch for the uplink outer-loop power control
ULAMCSWITCH Switch for uplink AMC
DLAMCSWITCH Switch for downlink AMC
Table 3-4 Parameters related to the MOD ULAMCTHRESH command

ID Name
CINRTARGET Target CINR value
CINRUPTHRE CINR up threshold
CINRLOWTHRE CINR low threshold
MAXADJUSTSTEP Maximum adjustment step

DBS3900 WiMAX
Table 3-5 Parameters related to the MOD DLAMCTHRESH command

ID Name
CINRLOWTHRE CINR low threshold
CINRUPTHRE CINR up threshold
MIMOACINRUPTHRE CINR up threshold for MIMO A
MIMOACINRLOWTHRE CINR low threshold for MIMO A
MIMOBCINRUPTHRE CINR up threshold for MIMO B
MIMOBCINRLOWTHRE CINR low threshold for MIMO B
Table 3-6 Parameters related to the MOD ULPERTHRESH command

ID Name
BEPERTARGET Target PER for BE service
NRTPSPERTARGET Target PER for nrtPS service
RTPSPERTARGET Target PER for rtPS service
ERTPSPERTARGET Target PER for ertPS service
UGSPERTARGET Target PER for UGS service
None.
3.6 Reference Information of Power Control and AMC

The protocol that the power control and AMC feature complies with is IEEE 802.16-2004/Cor2/

DBS3900 WiMAX
Feature Configuration Guide 4 Idle Mode
4 Idle Mode
About This Chapter
Idle mode is a mature technology developed for optimum allocation of network resources and
reduction in power consumption of an MS. This document describes the basic concepts,
functions, and settings of the idle mode feature.
4.1 Overview of Idle Mode

This section describes the definition, purpose, specifications, and impact of the idle mode feature.
4.2 Availability of Idle Mode
This section describes the license and version information about the idle mode feature and the
involved network elements (NEs).
4.3 Description of Idle Mode
The idle mode feature provides functions of idle mode entry, paging, location update, and idle
mode exiting.
4.4 Operations Related to Idle Mode
This section describes how to activate and deactivate the idle mode feature.
4.5 Maintenance Information of Idle Mode
This section describes the parameters and performance measurement items related to the idle
mode feature.
4.6 Reference Information of Idle Mode
The protocol that the idle mode feature complies with is IEEE 802.16-2004/Cor2/D3 with latest

DBS3900 WiMAX
4 Idle Mode Feature Configuration Guide
4.1 Overview of Idle Mode

This section describes the definition, purpose, specifications, and impact of the idle mode feature.
Definition
The Idle mode is a mechanism that allows an SS/MS to move within a paging group formed by
multiple BSs without the need to register with a specific BS. After the SS/MS enters the idle
mode, it can periodically receive broadcast messages on the downlink. The BS removes all the
link information of the SS/MS and keeps the connection information of the SS/MS only on the
paging controller.
Purpose
For the SS/MS, the SS/MS in idle mode only needs to periodically receive the broadcast
messages from the BS. When it roams to another cell, no handover process is triggered, thus
reducing the consumption of air interface resource and lowering the power of the SS/MS.
For a BS, the idle mode feature can be used to save the resources wasted on handovers triggered
by SSs/MSs that roam across the border between BSs without any ongoing service.
Network Reference Model

Figure 4-1 shows the network reference model of the idle mode feature.
Figure 4-1 Network reference model of the idle mode feature
The BS incorporates a PA, and the ASN-GW incorporates a PC/LR.
A PG is a logical group consisting of multiple BSs. A BS can belong to multiple PGs.

DBS3900 WiMAX
The PA interacts with the SS/MS through the R1 interface and interacts with the PC through the
R6 interface.
Specifications
A sector supports three paging groups.
A paging group can support a maximum of eight paging offsets.
Impact
The idle mode feature saves air interface resources and network resources and improves network
capacity.
The idle mode feature reduces the power of an SS/MS.
The introduction of the idle mode feature makes the delay caused by service activation longer.
Terms
Term Definition
Paging It is the mechanism of instructing an SS/MS in idle mode to quit idle

mode or to update the location through a message broadcast over the air
interface.
Paging Group It is a logical group consisting of multiple BSs. In the coverage of a

paging group, an SS/MS does not need to set up an air interface link to
a specific BS, and the BS can still periodically page this SS/MS and
instruct it to perform location update or network re-entry through
broadcast messages. A PG is generally managed and deployed by the
network management system and is identified with a PG ID.
Paging Controller It is the function entity that implements the idle mode feature, and is used
to store the status and operation parameters of the SSs/MSs in idle mode
and manage the paging of the SSs/MSs in idle mode. PCs can be
categorized into two types: anchor PC and relay PC.
Paging Cycle It is a period of paging completed through paging message broadcast.
Paging Offset It is the paging frame offset and is used together with a paging cycle to
determine the number of frames of a paging message.
Paging Agent It is a functional entity provided by the BS and is used to implement

functions related to idle mode, such as paging SSs/MSs periodically and
instructing SSs/MSs to enter or quit idle mode or perform location
update.
Location Register It is associated with a functional entity. It is used to store the status and
operation data of SSs/MSs in idle mode.
Location Update An SS/MS in idle mode reports its current location to the network. When
the SS/MS detects the change of paging group or is powered off, a
location update is triggered.

DBS3900 WiMAX
Term Definition
Anchor PC An SS/MS in idle mode is associated with only one PC, which is called
the anchor PC. An anchor PC has the information related to SSs/MSs in
idle mode, controls idle mode procedures, and updates SS/MS locations.
Relay PC In idle mode, the existence of one or more other PCs is allowed. Such
PC is called a relay PC. A relay PC is used to forward control messages
between the anchor PC and the PA.
Acronym and Abbreviation

Acronym and
Abbreviation Description
SS/MS Subscriber Station/Mobile Station
BS Base Station
PA Paging Agent
PG Paging Group
PC Paging Controller
LR Location Register
LU Location Update
4.2 Availability of Idle Mode

This section describes the license and version information about the idle mode feature and the
involved network elements (NEs).
NEs Involved
Table 4-1 lists the NEs involved in the idle mode feature.
Table 4-1 NEs involved in the idle mode feature
AAA DHCP
√ √ √ √ - -
NOTE
In Table 4-1, √ indicates that the NE is involved in this feature, and - indicates that the NE is not involved
in this feature.

DBS3900 WiMAX
Version Support
Table 4-2 lists the version that supports the idle mode feature.
Table 4-2 Version that supports the idle mode feature
Product Version
License Restriction
The usage of the idle mode feature is not controlled by a license.
4.3 Description of Idle Mode

The idle mode feature provides functions of idle mode entry, paging, location update, and idle
mode exiting.
4.3.1 Entering the Idle Mode

This section describes the process in which an SS/MS enters the idle mode.
4.3.2 Paging
This section describes the paging process initiated by the ASN-GW.
4.3.3 Updating Location
This section describes the SS/MS location update process.
4.3.4 Exiting the Idle Mode
This section describes the process in which the SS/MS exits the idle mode.
4.3.1 Entering the Idle Mode

This section describes the process in which an SS/MS enters the idle mode.
After the SS/MS enters the idle mode, the BS notifies this event to the paging controller and
sends the connection information (for example, the context related to the SBC process, the
context related to security, and the service flow information) to the paging controller for storage.
At the same time, the BS initiates a management resource holding timer. Before this timer
expires, the BS should retain the connection information of the MS. After the timer expires, the
BS should delete the connection information and release R6 interface resources.
The SS/MS enters the idle mode in the following situations:

l The SS/MS sends the BS a message to request entering the idle mode.
l The BS instructs the SS/MS to enter the idle mode if there is no UL or DL data related to
the SS/MS.
SS/MS-Initiated Process for Entering the Idle Mode

Figure 4-2 shows the SS/MS-initiated process for entering the idle mode.

DBS3900 WiMAX
Figure 4-2 SS/MS-initialed process for entering the idle mode
1. The SS/MS sends the BS a DREG-REQ message to request entering the idle mode. The
message contains the capability requested by the SS/MS for retaining the information
related to the SS/MS in idle mode.
l If there is UL or DL data related to the SS/MS, the BS performs 2.
l If there is no UL or DL data related to the SS/MS, the BS performs 4.
NOTE
The capability for retaining the information related to the SS/MS in idle mode is configured through the
IdleModeRetainInf parameter, which specifies the resource retaining policy supported by the BS. When
the SS/MS enters the idle mode, the BS negotiates with the SS/MS according to the setting of this
parameter, and then saves the required information to the paging controller according to the negotiation
results.
The default value of this parameter is 127. If this parameter is set to 0, the SS/MS is not allowed to enter
the idle mode.
2. The BS sends the SS/MS a DREG-CMD message to notify the SS/MS of the later request
for entering the idle mode at expiration of the REQ-duration.
3. After the REQ-duration expires, the SS/MS sends the BS a DREG-REQ message to request
entering the idle mode.
4. The BS determines that the SS/MS can enter the idle mode, and sends an
IM_Entry_State_Change_Req message to the ASN-GW.
5. The ASN-GW responds to the BS with an IM_Entry_State_Change_Rsp message.
6. The BS sends a DREG-CMD message to the SS/MS. The message contains the paging-
related parameters and the capability requested by the SS/MS for retaining the information
related to the SS/MS in idle mode.
7. The BS sends an IM_Entry_State_Change_Ack message to the ASN-GW. After receiving
this message, the ASN-GW acknowledges that the SS/MS enters the idle mode.
8. The SS/MS enters the idle mode and releases the resources.
BS-Initiated Process for Entering the Idle Mode

Figure 4-3 shows the BS-initiated process for entering the idle mode.

DBS3900 WiMAX
Figure 4-3 BS-initialed process for entering the idle mode
1. When the BS decides that the SS/MS should enter the idle mode, the BS sends an
IM_Entry_State_Change_Req message to the ASN-GW.
2. The ASN-GW sends an IM_Entry_State_Change_Rsp message to the BS.
3. The BS sends a DREG-CMD message to the SS/MS. The message contains the paging-
related parameters and the SS/MS (in idle mode) information retaining capability supported
by the BS.
NOTE
The capability for retaining the information related to the SS/MS in idle mode is configured through the
IdleModeRetainInf parameter, which specifies the resource retaining policy supported by the BS. When
the SS/MS enters the idle mode, the BS negotiates with the SS/MS according to the setting of this
parameter, and then saves the required information to the paging controller according to the negotiation
results.
The default value of this parameter is 127. If this parameter is set to 0, the SS/MS is not allowed to enter
the idle mode.
4. The SS/MS responds to the BS with a DREG-REQ message and enters the idle mode.
5. The BS sends an IM_Entry_State_Change_Ack message to the ASN-GW. After receiving
this message, the ASN-GW acknowledges that the SS/MS enters the idle mode.
6. The SS/MS enters the idle mode and releases the resources.
4.3.2 Paging
This section describes the paging process initiated by the ASN-GW.
Paging is a process in which a broadcast message is sent to notify an SS/MS in idle mode of
location update or network re-entry when the location information of the SS/MS needs to be
updated or there is data related to the SS/MS on the ASN-GW.
Paging Process
Figure 4-4 shows the paging process.

DBS3900 WiMAX
Figure 4-4 Paging process
1. The ASN-GW starts the paging process by sending a Paging_Announce message to all BSs
in the paging group.
l If the value of Paging Cause in the Paging_Announce message is 0x01, SS/MS location
update is required.
l If the value of Paging Cause in the Paging_Announce message is 0x02, the SS/MS is
instructed to exit the idle mode and re-enter the network.
2. After receiving the Paging Announce message, the BS sends an MOB_PAG-ADV message
to the SS/MS. The number of frames used for sending the MOB_PAG-ADV message is
determined by the PagingCycle and PagingOffset parameters. The interval for monitoring
windows during a paging period is determined by the PagingIntervallen parameter.
NOTE
l PagingCycle: specifies a period in which the BS sends paging messages and completes a paging
process. If this parameter is set to an excessively high value, the paging delay prolongs. If this
parameter is set to an excessively low value, the system overhead and the SS/MS power consumption
increase.
l PagingOffset: specifies the paging frame offset. It is used with the paging period to determine the
number of frames for sending a broadcast paging message over the air interface. If this parameter is
set to an excessively low or high value, the paging success ratio decreases.
l PagingIntervallen: specifies the interval for monitoring windows during a paging period. The
parameter is measured in frames. Each frame is 5 ms. If this parameter is set to an excessively high
value, the MS power consumption increases. If this parameter is set to an excessively low value, the
paging capacity decreases.
3. Based on the value of Action Code in the MOB_PAG-ADV message that is received, the
SS/MS determines whether to perform location update or to exit the idle mode and re-enter
the network.
l If the value of Action Code is 0b01, the SS/MS performs location update.
l If the value of Action Code is 0b10, the SS/MS exits the idle mode and re-enters the
network.
4.3.3 Updating Location

This section describes the SS/MS location update process.
Location update refers to the reporting of the current position of an SS/MS in idle mode to the
network.
The location update process can be initiated by the SS/MS or the ASN-GW.

DBS3900 WiMAX
l When the paging group changes, the timer expires, or the SS/MS is powered off, the SS/
MS in idle mode initiates a location update.
l The ASN-GW can also initiate an SS/MS location update through paging.
Location update can be classified into secure location update and unsecured location update.
l When a valid secure context exists between the SS/MS and the BS, that is, the BS receives
a valid authentication key (AK), a secure location update is performed. After the secure
location update, the SS/MS is still in idle mode.
l When no valid secure context exists between the SS/MS and the BS, that is, the BS does
not receive any valid AK, an unsecured location update is performed. An unsecured location
update is actually a location update failure. After an unsecured location update, the SS/MS
exits the idle mode and re-enters the network.
Secure Location Update Process

Figure 4-5 shows the secure location update process.
NOTE
If the ASN-GW initiates the location update, the process starts from 1.
If the SS/MS initiates the location update, the process starts from 3.
Figure 4-5 Secure location update process

DBS3900 WiMAX
NOTE
increase.
3. The SS/MS sends a distance measurement code to the BS in the allocated distance
measurement area to measure the distance.
4. The BS sends an RNG-RSP message to the SS/MS.
l If the value of Raging Status in the RNG-RSP message is continue, the process returns
to 3.
l If the value of Raging Status in the RNG-RSP message is success, the process goes to
5.
5. The SS/MS sends the BS an RNG-REQ message to indicate a location update.
6. The BS sends the ASN-GW a LU-Req message to request a location update.
7. The ASN-GW responds to the BS with the LU-Rsp message to approve the location update.
8. The BS verifies the RNG_REQ message successfully and sends the SS/MS an RNG_RSP
message to indicate a successful location update.
9. The BS sends a CMAC_Key_Count_Update message to the ASN-GW for the update of
CMAC Key Count.
10. The ASN-GW responds to the BS with a CMAC_Key_Count_Update_Ack message.
11. The BS sends the ASN-GW a LU-Cnf message to indicate a successful location update.
Unsecured Location Update Process

Figure 4-6 shows the unsecured location update process.
NOTE
If the ASN-GW initiates the location update, the process starts from 1.
If the SS/MS initiates the location update, the process starts from 3.

DBS3900 WiMAX
Figure 4-6 Unsecured location update process
NOTE
increase.
l If the value of Raging Status in the RNG-RSP message is continue, the process returns
to 3.
l If the value of Raging Status in the RNG-RSP message is success, the process goes to
5.

DBS3900 WiMAX
5. The SS/MS sends the BS an RNG-REQ message to indicate a location update.

6. The BS sends the ASN-GW a LU-Req message to request a location update.
7. The ASN-GW sends the LU_Rsp message to the BS.
8. In one of the following conditions, the BS sends the SS/MS an RNG_RSP message to
indicate a location update failure.
l The ASN-GW sends the LU_Rsp message to reject the location update.
l The LU_Rsp message does not contain the SS/MS-related secure context.
l The BS fails to verify the CMAC of the RNG_REQ message.
9. The BS sends the ASN-GW a LU-Cnf message to indicate a location update failure.
10. The SS/MS starts to exit the idle mode and re-enter the network.
4.3.4 Exiting the Idle Mode

This section describes the process in which the SS/MS exits the idle mode.
When the SS/MS enters the idle mode, the BS starts a management resource holding timer for
the SS/MS. The process for the SS/MS to exit the idle mode varies according to whether the
timer expires.
After entering the idle mode, the SS/MS exits the idle mode and re-enters the network in the
following situations:
l There is UL data on the SS/MS side, or the user of the SS/MS runs commands manually
to request exiting the idle mode.
l There is DL data related to the SS/MS on the ASN-GW side, the paging controller pages
the BS in the paging group and instructs the BS to broadcast a paging message, and thus
the SS/MS is instructed to exit the idle mode.
Process for Exiting the Idle Mode When the Timer Expires
Figure 4-7 shows the process for exiting the idle mode when the timer expires.
NOTE
If the ASN-GW instructs the SS/MS to exit the idle mode, the process for exiting the idle mode starts from 1.
If the SS/MS actively exits the idle mode, the process for exiting the idle mode starts from 3.

DBS3900 WiMAX
Figure 4-7 Process for exiting the idle mode when the timer expires
2. After receiving the Paging Announce message, the BS sends the SS/MS an MOB_PAG-
ADV message to instruct the SS/MS to exit the idle mode and re-enter the network. The
number of frames used for sending the MOB_PAG-ADV message is determined by the
PagingCycle and PagingOffset parameters. The interval for monitoring windows during
a paging period is determined by the PagingIntervallen parameter.
NOTE
increase.
set to an excessively low or high value, the paging success rate decreases.
l If the value of Raging Status contained in the RNG-RSP message is continue, the
process returns to 3.

DBS3900 WiMAX
l If the value of Raging Status contained in the RNG-RSP message is success, the process
goes to 5.
5. The SS/MS sends an RNG-REQ message to the BS for network re-entry from the idle mode.
6. The BS sends an IM_Exit_State_Change_Req message to the ASN-GW after the BS
decides that the management resource holding timer expires.
7. The ASN-GW responds to the BS with an IM_Exit_State_Change_Rsp message.
8. The BS obtains the SS/MS-related context to verify the validity of the SS/MS, and then
constructs and sends an RNG-RSP message to the SS/MS.
9. The BS sends the ASN-GW a Path_Reg_Req message to request the establishment of data
links.
10. The ASN-GW sends a Path_Reg_Rsp message to the BS.
CMAC Key Count.
13. When network re-entry is complete, the BS sends the ASN-GW a Path_Reg_Ack message
to acknowledge the establishment of data links.
Process for Exiting the Idle Mode Before the Timer Expires
Figure 4-8 shows the process for exiting the idle mode before the timer expires.
NOTE
If the ASN-GW instructs the SS/MS to exit the idle mode, the process for exiting the idle mode starts from 1.
If the SS/MS actively exits the idle mode, the process for exiting the idle mode starts from 3.
Figure 4-8 Process for exiting the idle mode before the timer expires.

DBS3900 WiMAX
2. After receiving the Paging Announce message, the BS sends the SS/MS an MOB_PAG-
ADV message to instruct the SS/MS to exit the idle mode and re-enter the network. The
number of frames used for sending the MOB_PAG-ADV message is determined by the
PagingCycle and PagingOffset parameters. The interval for monitoring windows during
a paging period is determined by the PagingIntervallen parameter.
NOTE
increase.
number of frames for a broadcast paging message over the air interface. If this parameter is set to an
excessively low or high value, the paging success rate decreases.
l If the value of Raging Status contained in the RNG-RSP message is continue, the
process returns to 3.
l If the value of Raging Status contained in the RNG-RSP message is success, the process
goes to 5.
5. The SS/MS sends an RNG-REQ message to the BS for network re-entry from the idle mode.
6. The BS sends an RNG_RSP message to the SS/MS if the management resource holding
timer does not expire.
7. The BS sends the ASN-GW an IM_Exit_State_Change_Req message, which indicates that
the SS/MS exits the idle mode.
8. The ASN-GW responds to the BS with an IM_Exit_State_Change_Rsp message.
CMAC Key Count.
4.4 Operations Related to Idle Mode

This section describes how to activate and deactivate the idle mode feature.
4.4.1 Activating the Idle Mode Feature

This section describes how to activate the idle mode feature. You can activate the idle mode
feature on a web LMT or the M2000.
4.4.2 Deactivating the Idle Mode Feature
This section describes how to deactivate the idle mode feature. You can deactivate the idle mode
4.4.1 Activating the Idle Mode Feature

This section describes how to activate the idle mode feature. You can activate the idle mode

DBS3900 WiMAX
Procedure
Step 1 Run the DSP CARRIERSTATUS command to query the status of carriers.
l If carriers are unblocked, run the MOD CARRIERBLOCKFLAG to block the carriers.
l If carriers are blocked, go to Step 2.
Step 2 Run the MOD MACCAPABILITY command to configure MOBFEATURESUPP.

Example:
MOD MACCAPABILITY: SECTORID=0, CARRIERID=0, MOBFEATURESUPP=5;
NOTE
The value range of MOBFEATURESUPP is 0 to 7.

The BS supports the idle mode feature when MOBFEATURESUPP is set to 4, 5, 6, and 7.
Step 3 Run the MOD CARRIERBLOCKFLAG command to unblock carriers.
Step 4 Run the ADD PAGINGINF command to add a paging group for the BS.
Parameters to be configured in this command are SectorID, CarrierID, PagingGroupID,

PagingControllerID, PagingCycle, PagingOffset, PagingIntervallen, and
IdleModeRetainInf. The configuration of PagingGroupID, PagingCycle, and PagingOffset
must be consistent with the configuration of corresponding parameters of the PG on the ASN-
GW.
----End
4.4.2 Deactivating the Idle Mode Feature

This section describes how to deactivate the idle mode feature. You can deactivate the idle mode
Procedure
Step 1 Run the DSP CARRIERSTATUS command to query the status of carriers.
l If carriers are unblocked, run the MOD CARRIERBLOCKFLAG command to block the
carriers.
l If carriers are blocked, go to Step 2.
Step 2 Run the MOD MACCAPABILITY to configure MOBFEATURESUPP.

Example:
NOTE

When the MOBFEATURESUPP parameter is set to 0, 1, 2, or 3, you can infer that the BS does not support
the idle mode feature.
Step 3 Run the MOD CARRIERBLOCKFLAG command to unblock carriers.
----End

DBS3900 WiMAX
4.5 Maintenance Information of Idle Mode

This section describes the parameters and performance measurement items related to the idle
mode feature.
Related Parameters
Table 4-3 and Table 4-4 list the parameters related to the idle mode feature.
Table 4-3 Parameters of the MOD MACCAPABILITY command

Parameter Description
SECTORID Sector ID
MOBFEATURESUPP Support for mobility
Table 4-4 Parameters of the ADD PAGINGINF command

Parameter Description
CarrierID Carrier ID
SectorID Sector ID
PagingGroupID PG ID
PagingControllerID PC ID
PagingCycle Paging cycle
PagingOffset Paging offset
PagingIntervallen Paging interval
PagingAnnounceTimer Paging announcement timer
IdleModeRetainInf Resource reservation flag
Related Performance Measurement Items

Table 4-5 lists the performance measurement items related to the idle mode feature.
Table 4-5 Performance measurement items related to the idle mode feature
Item Description
Idle entry success times See Times of Successful MS-Initiated Entry to Idle Mode.
triggered by MS

DBS3900 WiMAX
Item Description
Idle entry success times See Times of Successful BS-Initiated Entry to Idle Mode.
triggered by BS
Idle entry rejected times by See Times When the MS Rejects BS-Initiated Entry to Idle
MS times Mode.
Times of the BS sending See Times of Sending Paging Message from BS.
paging messages
Location update times due See Times of Normal Location Update.

to normal
Location update times due See Times of Location Update in Power-off Mode.
to power off
Location update success See Times of Successful Location Update.

times
Re-entry network times See Times of Network Re-Entry from Idle Mode.
from idle
Re-entry network success See Times of Successful Network Re-Entry from Idle Mode.
times from idle
4.6 Reference Information of Idle Mode

The protocol that the idle mode feature complies with is IEEE 802.16-2004/Cor2/D3 with latest

DBS3900 WiMAX
Feature Configuration Guide 5 QoS
5 QoS
About This Chapter
The WiMAX BS can provide users with five different Quality of Service (QoS) levels. Users
need to choose the desired QoS level when subscribing to services. This chapter describes the
basic concepts, functions, and implementation method of the QoS feature.
5.1 Overview of QoS

This section describes the definition, purpose, specifications, and impact of the QoS feature.
5.2 Availability of QoS
This section describes the network elements (NEs) involved in the QoS feature and the version
that supports the QoS feature.
5.3 Description of QoS
The Huawei WiMAX BS provides an end-to-end QoS solution, including the QoS mechanism
of the R1 and R6 interfaces.
5.4 Operations Related to QoS
This section describes how to activate and deactivate the QoS feature.
5.5 Maintenance Information of QoS
This section describes the parameters and performance counters related to the QoS feature.
5.6 Reference Information of QoS
The protocols that the QoS feature complies with are IEEE 802.16-2004/Cor2/D3 with latest

DBS3900 WiMAX
5 QoS Feature Configuration Guide
5.1 Overview of QoS

This section describes the definition, purpose, specifications, and impact of the QoS feature.
Definition
QoS is an end-to-end processing mechanism used to guarantee the quality of communication
services. On a WiMAX network, QoS ensures that users obtain expected service levels in terms
of the packet loss rate, delay, jitter, and bandwidth. The QoS feature supported by the Huawei
WiMAX solution is deployed over the R1 and R6 interfaces.
Purpose
QoS is used to guarantee the end-to-end service quality. When the network is congested, QoS
guarantees reliable data transmission of important services and ensures efficient use of network
resources.
QoS offers operators with effective control over the use of network resources. With QoS, the
network supports existing and emerging multimedia services and applications. At the same time,
the network can distinguish between services and provide corresponding quality guarantee. In
this way, multiple services such as voice, video, and data can be converged on the same network.
With QoS, operators can divide users into detailed groups and provide user-specific
differentiated and value-added services. In this manner, the network becomes more profitable
and competitive, thus gaining a big market share.
Specifications
The IEEE 802.16e standard defines five service flow QoS scheduling types, that is, the UGS,
ertPS rtPS, nrtPS, and BE.
Impact
None.
Terms
Term Definition
Throughput Throughput is the maximum transmission rate of the tested object

(system, equipment, connection, service type) when no packet is
discarded.
Latency Latency refers to the time it takes for the original data to go through a
series of processing steps such as coding, to be transmitted through the
channel, to arrive at the receiver, and to be decoded.

DBS3900 WiMAX
Term Definition
Jitter Generally, signals are not simply transmitted on communication

channels from the transmitter to the receiver in a point-to-point manner.
Instead, signals may be amplified or forwarded by repeaters. There is a
process of storing, processing, and forwarding. In addition, the network
conditions affect the transmission of signals. Therefore, the delay in the
same service flow varies. The variation of packet delay is known as
packet jitter.
Packet loss rate Because of the limited buffer size of network switching equipment and
the interfering signals on the transmission links, packets may get lost on
the transmission links. The packet loss rate is the ratio of the number of
lost packets to the number of transmitted packets. The packet loss rate
is an important yardstick for measuring the quality of communication
links.
Service flow A service flow is a unidirectional transmission service that is provided

by the MAC layer and used to transmit packets. A service flow may be
a downlink or uplink service flow and provides specific QoS functions.
Each service flow can be described with a set of QoS parameters, such
as delay, jitter, and throughput.
IP PATH IP path is a logical link with virtual bandwidth. The logical link is carried
on the physical link in the IP network. IP path is a mechanism to perform
access control for transmission resources.

Acronym or
QoS Quality of Service
MS Mobile Station
BS Base Station
UGS Unsolicited grant service
rtPS Real-time polling service
ertPS Extended rtPS
nrtPS Non-real-time polling service
BE Best effort
TOS Type of Service
DSCP Differentiated Service Code Point

DBS3900 WiMAX
5.2 Availability of QoS

This section describes the network elements (NEs) involved in the QoS feature and the version
that supports the QoS feature.
NEs Involved
The QoS feature requires the joint work of the SS/MS, BS, and ASN-GW. If authentication is
required, the AAA server must be configured. Table 5-1 lists the NEs involved in the QoS
feature.
Table 5-1 NEs involved in the QoS feature
ASN AAA DHCP

SS/MS BS -GW Server Server M2000
√ √ √ √ - -
NOTE
In Table 5-1, √ is used to mark the NEs that are involved in this feature, and - is used to mark the NEs
that are not involved in this feature.
Version Support
Table 5-2 lists the version that supports the QoS feature.
Table 5-2 Version that supports the QoS feature
Product Version
License Restriction
The usage of the QoS feature is not controlled by a license.
5.3 Description of QoS

The Huawei WiMAX BS provides an end-to-end QoS solution, including the QoS mechanism
of the R1 and R6 interfaces.
The IEEE802.16e defines the QoS mechanism of the R1 interface in the WiMAX system. The
QoS mechanism specifies the association between data packets on the MAC layer and a
connection-oriented service flow. Each service flow is granted QoS parameters such as the
service type, delay, jitter, and data rate. Efficient management and scheduling of service flows
guarantees the satisfaction of QoS requirements.

DBS3900 WiMAX
The QoS mechanism of the R6 interface focuses on transmission resources. It involves the
following technologies: mapping between the QoS parameters and the R6 interface transmission
priority, IP Differentiated Service, and IP flow shaping.
5.3.1 QoS Network Model
This section describes the QoS network model in the Huawei WiMAX network.
5.3.2 QoS Application Objects and Parameters
This section describes the QoS application objects and parameters.
5.3.3 QoS Transmission Control
This section describes the QoS transmission control mechanism.
5.3.1 QoS Network Model

This section describes the QoS network model in the Huawei WiMAX network.
The QoS feature is implemented mainly over the R1 and R6 interfaces. Figure 5-1 shows the
subsystems and NE interface relations involved in the QoS feature.
Figure 5-1 External interfaces of the WiMAX
Upon subscription, the QoS profile is configured on the AAA or the gateway. When a subscriber
enters the network and the provisioned service flow is established, the QoS profile is delivered
to the BS. The BS is responsible for service flow management and QoS scheduling.
5.3.2 QoS Application Objects and Parameters

This section describes the QoS application objects and parameters.
QoS Application Objects

l Service-flow-oriented QoS
IEEE802.16e defines five types of service flows: UGS, rtPS, ertPS, nrtPS, and BE.
Different QoS parameters are defined for different types of service flows. The system
implements scheduling according to the types of service flows and QoS parameters, thus

DBS3900 WiMAX
meeting different QoS requirements of the service flows. Table 5-3 lists the typical
applications that are supported by different service types.
Table 5-3 Typical applications and parameters of QoS

QoS Typical Typical Tolerated
Scheduling Typical Bandwidth Delay Jitter
Service Type Service
UGS l E1/T1 50 kbit/s 25 ms N/A

service with a
fixed bit rate
l VoIP without
silence
suppression
rtPS MPEG video 5 kbit/s to 2 N/A 100 ms

service flow Mbit/s
ertPS VoIP with 32 kbit/s to 64 160 ms 5 ms

silence kbit/s
suppression
nrtPS High-bandwidth 10 kbit/s to 2 N/A N/A

FTP service Mbit/s
flow
BE Internet web 2 Mbit/s N/A N/A

browsing
l Subscriber-oriented QoS
Different subscriber priorities are defined to provide differential services for subscribers.
The subscriber priorities are as follows: gold, silver, bronze, and common.
QoS Parameters
In a WiMAX system, QoS parameters are defined to describe the rules for scheduling service
flows on the air interface. Each type of scheduling service corresponds to a set of QoS parameters,
such as the delay, tolerated jitter, and bandwidth. Each type of service has its corresponding QoS
parameter set.
UGS
The UGS supports real-time uplink service flows that transmit fixed-size packets on a periodic
basis.
The BS assigns a fixed bandwidth to the service flows with the service data on a real-time and
periodic basis. In this way, the overheads used for requests from the MSs are reduced, and the
real-time requirements of the service flows are met. Therefore, in a UGS service flow, data is
sent at the bandwidth periodically granted by the BS, and the MS does not request a bandwidth
from the BS.
The QoS parameters of the UGS are as follows:
l Maximum Sustained Traffic Rate (maximum sustaining rate)

DBS3900 WiMAX
This parameter indicates the average peak rate of data service flows. The average uplink
rate of the service flows of an MS cannot exceed the value of this parameter. The BS limits
the downlink rate at the network entry. The value range of this parameter depends on the
transmission capabilities of the air interface and R6 interface and is related to the uplink
and downlink transmission capabilities of the MS. If the value of this parameter is
excessively high or low, the resource management algorithm is implemented to determine
whether the service flow can be successfully established. The higher value the parameter
has, the more resources are to be occupied. When total resources are insufficient, online
subscribers decrease. If the value of the parameter is excessively low, the services are
affected. Based on the current capabilities of the MS and the actual service requirements,
the recommended value range of this parameter is from 256 kbit/s to 8 Mbit/s. Generally,
operators can provide services at different rates, such as 512 kbit/s, 1 Mbit/s, and 2 Mbit/
s.
l Request/Transmission Policy (transmission policy)
This parameter is used to configure the attributes of service flows. In the latest IEEE 802.16e
R2D7, this parameter can indicate the following policies:
– Whether to support the broadcast of bandwidth requests (whether requests for uplink
bandwidth use the opportunities broadcast by the BS)
– Whether to support multicast bandwidth requests (whether requests for uplink
bandwidth use the opportunities multicast by the BS)
– Whether to support piggyback bandwidth requests (whether to use a tag in the protocol
data header of the uplink services to request bandwidth for the MS; if piggyback
bandwidth requests are supported, the uplink resource efficiency is improved)
– Whether to support segmentation (whether to divide service data units (SDUs) that
exceed the available resource length into multiple schedulable SDUs during scheduling;
if segmentation is supported, oversized SDUs can be scheduled quickly)
– Whether to support PHS (whether to support load header compression; if load header
compression is supported, bandwidth is saved because only one load header is
transmitted when the same load and SDUs are transmitted)
– Whether to support packing (whether to merge multiple small SDUs into a large protocol
data unit (PDU); if packing is supported, the number of protocol data headers to be
transmitted is reduced, and bandwidth is saved)
– Whether to support CRC (whether to perform CRC during the transmission of data; if
CRC is supported, the check results are appended to the PDUs)
– Whether to support ROHC (ROHC is an efficient method of compressing RTP/UDP/
IP headers)
In the current versions of Huawei WiMAX base station and ASN-GW, this parameter can
indicate the following policies:
– Whether to support the broadcast of bandwidth requests
– Whether to support piggyback bandwidth requests
– Whether to support segmentation
– Whether to support PHS
– Whether to support packing
– Whether to support CRC
l Maximum Latency (maximum delay time)
This parameter indicates the maximum interval between the reception of a packet at the BS
or MS and the transmission of the packet through the RF part. The lower value the parameter

DBS3900 WiMAX
has, the more resources are to be occupied. When total resources are insufficient, other
services may be affected. If the value of the parameter is excessively high, the customer
satisfaction is affected.
l Tolerated Jitter (maximum tolerated variation time)
This parameter indicates the maximum change in the delay. Generally, signals are not
simply transmitted on communication channels from the transmitter to the receiver in a
point-to-point manner. Instead, signals may be amplified or forwarded by repeaters. There
is a process of storing, processing, and forwarding. In addition, the network conditions
affect the transmission of signals. Therefore, the delay in the same service flow varies. The
Tolerated Jitter parameter indicates the maximum change in the delay that can be
tolerated. The parameter is configured according to the actual services. The lower value
the parameter has, the more resources are to be occupied. When total resources are
insufficient, other services may be affected. If the value of the parameter is excessively
high, the customer satisfaction is affected.
l SDUFLG (SDU flag)
The value of this parameter may be fixed or variable. If the value of this parameter is set
to fixed, the size of the SDU needs to be set. Generally, IP traffic is carried, and the sizes
of IP packets vary. Therefore, the value of this parameter is set to variable.
l SDU Size (SDU size)
If the value of the parameter is excessively high, the BS cannot process data properly or
the MS cannot support the value. If the value of the parameter is excessively low, data
transmission may be affected. The parameter is set on the BS according to the actual
conditions. The default value is recommended.
When the value of the SDU flag parameter is set to fixed, this parameter must be set. The
size of the SDU cannot exceed 254 bytes.
l Unsolicited Grant Interval (Unsolicited Grant Interval)
This parameter indicates the grant interval for a service flow that does not request any grant.
It is a 16-bit unsigned integer. The value range is 0 to 65535 (in milliseconds). If the
parameter is set to a high value, the continuity of real-time services is affected. If the
parameter is set to a low value, the bandwidth is wasted.
rtPS
The real-time polling service (rtPS) supports real-time uplink service flows that transmit
variable-size packets on a periodic basis, for example, the MPEG video service flow.
In the rtPS, the BS offers real-time, periodic, and unicast request opportunities, which enable
the service flow to inform the BS of its variable requirements for bandwidth on a periodic basis.
In this manner, the BS can grant variable burst bandwidth on a periodic basis for the service
flow to transmit variable-size packets. The rtPS requires more request overheads than the UGS
but supports variable grant sizes for the optimum data transmission efficiency.
The QoS parameters of the rtPS are as follows:
l Minimum Reserved Traffic Rate (minimum guaranteed rate)

This parameter indicates the minimum data rate reserved by the service flow. The BS offers
the bandwidth required by the minimum data rate reserved by the service flow. If the
bandwidth required by the service flow is less than the reserved bandwidth, the BS can use
the remaining part of the reserved bandwidth for other purposes. The higher value the
parameter has, the more resources are occupied. When total resources are insufficient,

DBS3900 WiMAX
online subscribers decrease. If the value of the parameter is excessively low, the services
are affected.
l SDUFLG (SDU flag)
l Maximum Traffic Burst (Maximum burst length)
Burst transmission is a type of intermittent data transmission mode. In burst transmission,
data generated at a low rate is buffered by the transmitter. When the buffered data is enough
to form a data group, the data is transmitted at a rate dozens of times faster than the rate at
which the data is generated. The receiver buffers the received data and forwards the data
to subscribers at normal rates. The maximum burst length is determined by the buffering
capabilities and maximum sustained service rate. Within a proper range, an increase in the
buffers raises the transmission rate.
l Traffic Priority (optional) (Flow Priority)
This parameter indicates the priority of the same service flow. For two service flows
identical in all QoS parameters except the priority, the service flow with a higher priority
has a lower delay and a higher buffering priority. For service flows with different QoS
parameters, the priorities are not determined by the priority parameter when the priority
parameter conflicts with the QoS parameters.
ertPS
The extended real-time polling service (ertPS) is designed to support real-time service flows
that generate variable-size packets on a periodic basis, such as VoIP with silence suppression.
The ertPS is a scheduling mechanism that builds on the efficiency of both the UGS and the rtPS.
The BS offers unicast grants in an unsolicited manner like in UGS, thus reducing the delay of
requests for bandwidth. UGS allocations are fixed in size, whereas ertPS allocations are dynamic.
The BS can provide periodic uplink bandwidth allocations that can be used for requesting
bandwidth and data transmission. By default, the sizes of allocations correspond to the current
value of the parameter Maximum Sustained Traffic Rate of the service flow. The MS may request
a change in the size of the uplink allocation by using the Extended Piggyback Request field of
the grant management subheaders or the BR field of the MAC signaling headers, or by sending
a codeword over the channel quality indicator channel (CQICH). The BS does not change the
size of uplink allocations until it receives another request for bandwidth change from the MS.
The QoS parameters of the ertPS are as follows:

This parameter indicates the minimum data rate reserved by the service flow. The BS offers
the bandwidth required by the minimum data rate reserved by the service flow. In the ertPS,
the reserved traffic rate is generally set to the same value as the maximum sustained traffic
rate. On the downlink, bandwidth is allocated according to the data amount but cannot
exceed the maximum sustained traffic rate. On the uplink, the maximum sustained traffic
rate is always allocated. If the remaining bandwidth of the BS is below the maximum
sustained traffic rate when a service flow is established, the service flow cannot be
successfully established.

DBS3900 WiMAX

l Tolerated Jitter (maximum tolerated variation time)
l SDUFLG (SDU flag)
l Unsolicited Grant Interval (Unsolicited Grant Interval)
nrtPS
The non-real-time polling service (nrtPS) is designed to support non-real-time uplink service
flows that transmit variable-size packets on a non-periodic basis, such as high-bandwidth FTP
service flows.
The BS offers unicast polls on a regular basis, which ensures that the service flow receives
request opportunities even during network congestion. The service flow can also send requests
for bandwidth in a competitive manner.
The QoS parameters of the nrtPS are as follows:
If the bandwidth required by the service flow is less than the reserved bandwidth, the BS
can use the remaining part of the reserved bandwidth for other purposes.
l SDUFLG (SDU flag)
BE
The best-effort (BE) service is designed to offer best-effort transmission and has the lowest
priority.
A BE service flow can use transmission opportunities offered by unicast polls or send bandwidth
requests in a competitive manner. The probability of the BE service flow using opportunities
offered by unicast polls depends on the load on the network. If the load on the network is light,
the BE service flow may probably have transmission opportunities. If the load on the network
is heavy, the probability of transmission opportunities is slim or even none. Therefore, when
transmitting BE service flows, the MS cannot rely on transmission opportunities offered by
unicast polls. The network does not guarantee the QoS for BE service flows.
The QoS parameters of the BE service are as follows:
l SDUFLG (SDU flag)

DBS3900 WiMAX
BE starvation prevention
In actual situations, the BE service may be starved.
To prevent the BE service from starvation, the algorithm switch and the rate of reserved resources
are configured. This prevention method is applicable to the BE service instead of a specific BE
service flow. That is, the setting of the resource reservation rate for the BE service is based on
the total number of resources.
The following table lists the parameters related to BE starvation prevention.
Table 5-4 Parameters related to BE starvation prevention
Parameter Description Default Value Remarks
AntiBEStavSwicher BE starvation OFF This is a carrier-level

prevention switch parameter. It can be
modified only after
the carrier is
deactivated.
LBE_UL Rate of uplink load 5% This is a carrier-level

reserved for the BE parameter. It can be
service modified only after
the carrier is
deactivated.
LBE_DL Rate of downlink 15% This is a carrier-level

load reserved for the parameter. It can be
BE service modified only after
the carrier is
deactivated.
5.3.3 QoS Transmission Control

This section describes the QoS transmission control mechanism.
The QoS transmission control mechanism defines the mapping relation between the transmission
bearer priorities and the WiMAX R6 interface transmission resource configuration and traffic.
It addresses many problems, for example, how to guarantee the service QoS, bandwidth utility
rate, and user fairness in the scenarios such as fixed transmission bandwidth, dynamically
changing bandwidth, branching transmission, and load balance. The QoS transmission control
involves the transmission differentiated service, transmission admission control, and
transmission overload control.
Differentiated Transmission Service

In the differentiated transmission service, different priorities are assigned to the user data,
including five types of scheduling service data, signaling data, and maintenance data. This
enables different transmission priorities. Under the circumstance of network congestion, the
traffic with higher priority will take precedence in transmission.

DBS3900 WiMAX
Differentiated transmission services use two types of rules. One is based on the priority indicator
in TOS field of the IP header; the other is the DSCP value in TOS. Currently, only the latter rule
is supported.
Transmission Admission Control

Transmission admission control: Uplink and downlink admission control is implemented
according to the admission thresholds of different types and levels of services. High-priority
services (such as the UGS) of high-priority users (such as handover users) are admitted on a
preferential basis. The number of admitted users is limited with the aim of guaranteeing the
quality of ongoing services.
Transmission Overload Control

In the case of system overload, the transmission overload control mechanism enables the system
to remove low-priority service connections according to the transmission overload threshold and
clearance threshold. When the system load becomes normal, the system congestion is
automatically and quickly cleared.
5.4 Operations Related to QoS

This section describes how to activate and deactivate the QoS feature.
5.4.1 Activating the QoS Feature

If authentication is carried out, you need to activate the QoS feature over the R1 interface through
the graphic user interface (GUI) of the Web Management Access System (WMAS) on the AAA.
For details, see the documentation delivered with the AAA. If authentication is not carried out,
you need to run relevant commands on the gateway to activate the QoS feature over the R1
interface. For details, see the documentation delivered with the gateway. You need to run MML
commands on the M2000 or the LMT of the WiMAX BS to activate the QoS feature over the
R6 interface.
5.4.2 Deactivating the QoS Feature
The QoS is a mandatory feature. Deactivating this feature renders all the WiMAX SSs on the
network unable to transmit any service data. You are advised not to deactivate this feature.
5.4.1 Activating the QoS Feature

If authentication is carried out, you need to activate the QoS feature over the R1 interface through
the graphic user interface (GUI) of the Web Management Access System (WMAS) on the AAA.
For details, see the documentation delivered with the AAA. If authentication is not carried out,
you need to run relevant commands on the gateway to activate the QoS feature over the R1
interface. For details, see the documentation delivered with the gateway. You need to run MML
commands on the M2000 or the LMT of the WiMAX BS to activate the QoS feature over the
R6 interface.
Procedure
l Run the relevant commands on the AAA or the gateway to activate the QoS feature over
the R1 interface. Assume that the commands are run on the gateway.
Data Collection

DBS3900 WiMAX
– QoS template of a service flow

– Template index: 1
– Direction (upward or downward): UPWARD
– Media stream type: VOD
– Scheduling type: UGS
– Transmission policy:
NOBCREQ-0&NOPIGGYBACK-0&NODEFRAG-0&NOSUPPRESS-0&NOPA
CK-0&NOCRC-0 (No transmission policy is adopted.)
– SDU flag: Variable
– Maximum sustained traffic rate: 1,171,200 bit/s
– Minimum sustained traffic rate: 1,171,200 bit/s
– Tolerated jitter: 50 ms
– Maximum latency: 5 ms
– Template index: 2
– Direction (upward or downward): DOWNWARD
– Downlink paging flag: ENABLE (Paging is enabled.)
– Media stream type: VOD
– Scheduling type: UGS
– Transmission policy:
NOBCREQ-0&NOPIGGYBACK-0&NODEFRAG-0&NOSUPPRESS-0&NOPA
CK-0&NOCRC-0 (No transmission policy is adopted.)
– SDU flag: Variable
– Maximum sustained traffic rate: 1,171,200 bit/s
– Minimum sustained traffic rate: 1,171,200 bit/s
– Tolerated jitter: 50 ms
– Maximum latency: 5 ms
– Parameters of the classifier
– Classifier index: 1
– Protocol type: TCP
– Mask of the destination IP address: 255.255.255.0
– Destination IP address: 10.1.1.1
– Mask of the source IP address: 255.255.255.0
– Source IP address: 10.2.2.2
– Lower threshold of the IP service type/DSCP: 0
– Upper threshold of the IP service type/DSCP: 240
– Mask of the IP service type/DSCP: 255
– Classifier index: 2
– Protocol type: TCP
– Mask of the destination IP address: 255.255.255.0
– Destination IP address: 10.10.10.1

DBS3900 WiMAX
– Mask of the source IP address: 255.255.255.0

– Source IP address: 10.20.20.2
– Lower threshold of the IP service type/DSCP: 0
– Upper threshold of the IP service type/DSCP: 240
– Mask of the IP service type/DSCP: 255
– Template of a service flow
– Class number of the service flow: 1, 2
– Direction (upward or downward): UPWARD, DOWNWARD
– Classifier priority: priority 1 for the classifier with index 1; priority 2 for the classifier
with index 2
– QoS template index: 1
– QoS priority: 6 (Value range: 0 to 7. A greater number indicates a higher priority of
the service flow.)
l Configure four subscriber levels on AAA: gold, silver, bronze, and common. For details
on configuration methods, see the documentation delivered with the AAA. By default, all
subscribers are configured as common subscribers.
l According to various operation policies, on the M2000 or the LMT of the WiMAX BS, run
the MOD QOSFACTOR command to configure the priority weight factor for each gold,
silver, bronze, and common subscriber.
By default, the priority weight factors for gold, silver, bronze, and common subscribers are
4, 3, 2, and 1 respectively.
l Run MML commands on the M2000 or the LMT of the WiMAX BS to activate the QoS
feature over the R6 interface.
When activating the QoS feature over the R6 interface, you need to configure the logical
interface for transmission, the IP path, and the priorities of differential services. In addition,
the transmission differentiated service, transmission admission control function, and
transmission overload control function can be configured to meet requirements of the
customer.
1. Run the ADD LGCPORT command to configure the logical interface.
Example:
ADD LGCPORT: CN=0, SRN=0, SN=7, LPN=6, SSN=0, PT=ETH, PN=1, TXBW=150000,
RX
BW=150000, TXCBS=200000, TXEBS=200000, TXSSW=OFF, RTMP=6, TXRTFC=26,
RXRTFC=24;
2. Run the ADD IPPATH command to configure the QoS parameters of the IP PATH
and logical interface (R6 interface).
Example:
ADD IPPATH: PATHID=128, CN=0, SRN=0, SN=6, LPN=0, LOCALIP="172.16.12.251",
PEERIP="192.168.1.155", PATHTYPE=ANY, PATHCHK=ENABLED;
NOTE
The IP path is configured for a specific logical interface, the IP address of the BS is the interface IP
address, and the IP address of the gateway is the physical or logical IP address of the gateway.
3. Run the SET DIFPRI command to configure the priorities of differentiated services.

DBS3900 WiMAX
NOTE
l Configuring the priorities of differentiated services refers to specifying the DSCP priorities of
services. If this step is not performed, the system uses the default DSCP priorities for services.
l The configuration of differentiated services takes effect after the BS is restarted.
For example, to configure the priorities of differentiated services (priority rule: DSCP,
signaling priority: 48, VLAN priority for signaling: 6, OAM priority:32, OAMVLAN
priority: 3, OAM FTP priority: 1, OAM FTP VLAN priority: 0), run the following
command:
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, SIGVLANPRI=6, OAMPRI=32,
OAMVLANPRI=4, OAMFTPPRI=1, OAMFTPVLANPRI=0, DT1PRI=46, DT1VLANPRI =6
, DT2PRI=34, DT2VLANPRI=4, DT3PRI=46, DT3VLANPRI=6, DT4PRI=10,
DT4VLANPRI=1, DT5PRI=18, DT5VLANPRI=2, DT6PRI=26, DT6VLANPRI=3, DT7PR
I=0, DT7VLANPRI=0;
4. Run the SET TACALG command to configure transmission admission control.
For example, you need to configure transmission admission control. The uplink and
downlink admission thresholds of high-priority subscribers (handover subscribers)
are 85%, and those of new subscribers are 75%. That is, when the system load is less
than 75%, all subscribers can access the network; when the system load is between
75% and 85%, only high-priority subscribers can access the network; when the system
load is greater than 85%, no subscriber can access the network. When the value of
USERDATATYPE5GBR is set to 100, the current bandwidth is reserved for non-
real-time services such as BE services.
SET TACALG: TRMULCACSWITCH=ON, TRMDLCACSWITCH=ON, TRMULVIPUSERCACTH=85,
TRMULUSERCACTH=85, TRMDLVIPUSERCACTH=75, TRMDLUSERCACTH=75,
USERDATATYPE5GBR=100, USERDATATYPE1ACTFACTOR=100,
USERDATATYPE2ACTFACTOR=100, USERDATATYPE3ACTFACTOR=100,
USERDATATYPE4ACTFACTOR=100, USERDATATYPE5ACTFACTOR=100;
5. Run the SET TOLCALG command to configure transmission overload control.
For example, to configure the overload control switch (uplink overload control switch:
disabled, downlink overload control switch: enabled, threshold for triggering uplink
overload control: 100%, threshold for releasing uplink overload control: 0%, latency
of triggering overload control: 0 ms, overload control period: 100s, and number of
service flows periodically released after overload: 0), run the following command:
SET TOLCALG: TRMULOLCSWITCH=OFF, TRMDLOLCSWITCH=ON, TRMULOLCTRIGTH=100,
TRMULO
LCRELTH=0, TRMDLOLCTRIGTH=100, TRMDLOLCRELTH=0, TRMOLCTIMETRG=0,
TRMOLCACTIONPRD
=100, TRMOLCRELBEARERNUM=0;
----End
Verifying the QoS Feature

You need to enter the network with a WiMAX MS/SS, and check whether service flows can be
established. If service flows can be established, the QoS feature is successfully activated. If
service flows cannot be established, the QoS feature fails to be activated.
5.4.2 Deactivating the QoS Feature

The QoS is a mandatory feature. Deactivating this feature renders all the WiMAX SSs on the
network unable to transmit any service data. You are advised not to deactivate this feature.

DBS3900 WiMAX
5.5 Maintenance Information of QoS

This section describes the parameters and performance counters related to the QoS feature.
Parameters
For the parameters related to the QoS feature, see the documents of the WASN9770.
For the performance counters related to the QoS feature, see Times of Deregistration due to
Carrier Caused by BS Device Fault.
5.6 Reference Information of QoS

The protocols that the QoS feature complies with are IEEE 802.16-2004/Cor2/D3 with latest

DBS3900 WiMAX
Feature Configuration Guide 6 Handover
6 Handover
About This Chapter
WiMAX defines five application scenarios, namely, fixed, nomadic, portable, mobile, and full
mobile. To meet the requirements for the wireless DSL and combine the fixed and mobile
application scenarios, the handover technology is used so that service continuity can be achieved.
This chapter describes the basic concepts, functions, and implementation of the handover feature.
6.1 Overview of Handover

This section describes the definition, purpose, specifications, and impact of the handover feature.
6.2 Availability of Handover
This section describes the license and version information of the handover feature and the
network elements (NEs) involved.
6.3 Description of Handover
This section describes the application scenarios and handover processes.
6.4 Operations Related to Handover
This section describes how to activate and deactivate the handover feature.
6.5 Maintenance Information of Handover
This section describes the parameters and performance counters related to the handover feature.
6.6 Reference Information of Handover
The protocols that the handover feature complies with are IEEE 802.16-2004/Cor2/D3 with

DBS3900 WiMAX
6 Handover Feature Configuration Guide
6.1 Overview of Handover

This section describes the definition, purpose, specifications, and impact of the handover feature.
Definition
Handover refers to the process in which the MS in the communication state hands over from
one carrier to another carrier.
Currently, the product supports only the hard handover.
Purpose
The purpose of handovers is to provide better service quality and ensure service continuity.
Specifications
Each BS can be configured with up to 30 neighbor cells.
Each sector carrier can be configured with 9 trigger messages.
Impact
After the handover feature is activated, the possibility of service interruption caused by network
disconnection when the MS moves is reduced, and the call drop rate is also reduced.
Terms
Term Definition
BSID It is used uniquely for identifying the BS.

BSID(48bit)=OperatorId(24bit)+SiteId(16bit)+SectorId(4bit)+CarrierId
(4bit)

Acronym and Abbreviation Expansion
DSL Digital Subscriber Line
HO HandOver
BS Base Station
BTS Base Transceiver Station
MS Mobile Station
SBS Serving Base Station
TBS Target Base Station

DBS3900 WiMAX
6.2 Availability of Handover

This section describes the license and version information of the handover feature and the
network elements (NEs) involved.
NEs Involved
The handover feature requires that the SS/MS and the BS work together. Table 6-1 lists the NEs
involved in the handover feature.
Table 6-1 NEs involved in the handover feature
AAA DHCP
√ √ √ √ √ √
NOTE
Version Support
Table 6-2 lists the version that supports the handover feature.
Table 6-2 Version that supports the handover feature
Product Version
License Restriction
The usage of the handover feature is controlled by the license.
6.3 Description of Handover

This section describes the application scenarios and handover processes.
6.3.1 Application Scenario

This section describes the application scenarios of handovers.
6.3.2 Ordinary Handover
According to the object that initiates a handover, handovers are classified into BS-initiated
handovers and MS-initiated handovers.

DBS3900 WiMAX
6.3.3 Fast Ranging Handover

Fast Ranging is used to accelerate network re-entry during a handover. The serving BS instructs
the target BS to actively allocate bandwidth for the MS to send the RNG-REQ message so that
the time for network re-entry is reduced. According to the object that initiates a handover,
handovers are classified into BS-initiated handovers and MS-initiated handovers.
6.3.1 Application Scenario

This section describes the application scenarios of handovers.
When the MS moves, the serving BS may change.
According to the spanning scope, handover scenarios are classified into intra-BS handovers,
inter-BS handovers, and inter-ASN-GW handovers. As shown in Figure 6-1, 1 is the intra-BS
handover under different sectors, 2 is the inter-BS handover under the same ASN-GW, and 3 is
the inter-BS handover under different ASN-GWs.
Figure 6-1 Handover scenarios
6.3.2 Ordinary Handover

According to the object that initiates a handover, handovers are classified into BS-initiated
handovers and MS-initiated handovers.
MS-Initiated Handover
The MS can initiate a handover request according to the trigger configured by the BS. The request
message carries the list of target BSs.

DBS3900 WiMAX
Figure 6-2 shows the MS-initiated handover process.
Figure 6-2 MS-initiated handover process
1. When the MS receives a neighbor broadcast message, it obtains the neighbor cell
parameters and conditions for triggering handovers and scanning according to the
information in the DCD message and neighbor broadcast message.
l The value range of TRIGGERTYPE is 0 to 3.
– 0: CINR
– 1: RSSI
– 2: RTD
– 3: reserved temporarily
l The value range of TRIGGERFUNCTION is 0 to 7.
– 1: The trigger conditions are met when the measured value of the neighbor BS is
higher than the specified value.
– 2: The trigger conditions can be met when the measured value of the neighbor BS
is lower than the specified value.
– 3: The trigger conditions can be met when the difference between the measured value
of the neighbor BS and that of the serving BS is higher than the specified value.
– 4: The trigger conditions can be met when the difference between the measured value
of the neighbor BS and that of the serving BS is lower than the specified value.
– 5: The trigger conditions can be met when the measured value of the serving BS is
higher than the specified value.

DBS3900 WiMAX
– 6: The trigger conditions can be met when the measured value of the serving BS is
lower than the specified value.
– 0 and 7: reserved temporarily
l TRIGGERACTION determines the actions to be initiated by the MS, such as scanning,
scanning reporting, and handover initiating when the trigger conditions are met. The
value range is 0 to 7.
– 1: The MS sends the MOB_SCN-REP message when the triggering conditions are
met.
– 2: The MS sends the MOB_MSHO-REQ message when the triggering conditions
are met.
– 3: The MS sends the MOB_SCN-REQ message when the triggering conditions are
met.
– 0, 4, 5, 6, and 7: reserved temporarily
l TRIGGERVALUE is used to define the trigger threshold for controlling the scanning,
scan reporting, and handover.
l TRIGGERAVERDURATION is used to define the average interval measured by the
trigger type for controlling the scanning, scanning reporting, and handover. If the value
of this parameter is set too low, the measured value within the trigger interval may be
inaccurate. If the value of this parameter is set too high, the handover may not be
performed timely in case of sharply fluctuating signals.
2. When the MS finds that the downlink signal quality meets the conditions for triggering
scanning, it initiates the scanning.
3. The MS obtains the neighbor BSs for handovers through negotiation.
When the neighbor signals scanned by the MS meet the trigger conditions, the MS initiates
a handover request to a neighbor BS through the serving BS and ASN-GW. Based on the
admission decision, the neighbor BS reports to the serving BS through the ASN-GW about
whether to allow the MS to perform a handover. The serving BS recommends several
neighbor BSs for handovers.
4. The MS sends a handover indication, and the serving BS sends a confirmation message to
the target BS selected by the MS through the ASN-GW.
5. The MS performs CDMA code adjustment on the target BS.
6. The MS initiates a network re-entry request on the target BS by sending the RNG_REQ
message.
7. The target BS responds to the MS by sending the RNG-RSP message, containing the
indication bits for handover optimization. The indication bits are used to indicate how to
simplify the process of network re-entry. The value range is 0x15ff, 0x15fb/0x15bb,
0x0538, or 0x2538. The settings of the handover optimization mode have impacts on the
indication bits for handover optimization.
The meaning of the indication bits for handover optimization is described as follows:
l 0x15ff: This indicates that the network re-entry process is optimized. In this case,
HoEnhanceSwitch is set to HoProcAllOpti, and the MS meets the requirements for
optimized network re-entry.
l 0x15fb/0x15bb: The TEK is updated in the network re-entry process. In this case,
HoEnhanceSwitch is set to UpdateTek, and the MS meets the requirements for
network re-entry by TEK update.
l 0x0538: The network re-entry process is not optimized, and the IP address is relet. In
this case, NoHoEnhanceAction is set to OmitRefreIp.

DBS3900 WiMAX
l 0x2538: The network re-entry process is not optimized, and the IP address is updated.
In this case, NoHoEnhanceAction is set to RefreshIp.
NOTE
If NoHoEnhanceAction is set to AbortMS and the handover process cannot be optimized, the target BS
directly sends the RNG-RSP message to the MS so that the MS exits the network.
8. After the MS successfully re-enters the network through the target BS, the target BS informs
the serving BS that the handover is complete.
BS-Initiated Handover
The BS initiates a handover according to the uplink CINR, uplink PER, and load.
Figure 6-3 shows the BS-initiated handover process.
Figure 6-3 BS-initiated handover process
If the uplink CINR, uplink PER, or system load reaches the scanning threshold, the serving BS
initiates the scanning to obtain the downlink signal quality and sends the MOB_SCN_RSP
message, asking the MS to report the scanning result. After the scanning is complete, the MS
reports the scanning result, and the serving BS decides whether to initiate a handover according
to the scanning result.
1. The serving BS determines whether the uplink CINR and uplink PER meets the trigger
conditions.

DBS3900 WiMAX
When the uplink signal CINR is below SCANCINRBADTHRESH, or the uplink PER is
above SCANPERBADTHRESH, the serving BS instructs the MS to initiate the scanning
of neighbor cells.
l SCANCINRBADTHRESH: If the value of this parameter is set too low, the scanning
and handover cannot be performed timely. In this case, the MS is disconnected from
the network because of poor signal quality. If the value of this parameter is set too high,
the MS performs the scanning frequently. In this case, the services are affected and the
CPU is occupied.
l SCANPERBADTHRESH: If the value of this parameter is set too low, the MS
performs the scanning frequently so that the services are affected and the CPU is
occupied. If the value of this parameter is set too high, the scanning and handover cannot
be performed timely. The MS may be disconnected from the network when the signal
quality is poor.
NOTE
ULCINRHOSWITCH and ULPERHOSWITCH can be enabled at the same time. In this case, the
BS triggers a handover by using the method whose condition are met first.
2. The MOB_SCN_RSP message sent by the serving BS to the MS contains
SCANDURATION, SCANINTERVAL, and SCANITERATION.
l SCANINTERVAL: This parameter is used to define the interval of scanning a neighbor
BS. If the value of this parameter is set too low, another scanning process is performed
before services recover. In this case, scheduling is not performed on services in time.
If the value of this parameter is set too high, the entire scanning duration is too long,
and thus the handover opportunity is missed.
l SCANDURATION and SCANITERATION: The two parameters are calculated
through the two parameters SCANMINFRAMEPERBS and MAXDLY.
– SCANDURATION: This parameter is used to define the duration of a neighbor BS.
If the value of the parameter is set too low, the MS cannot scan any neighbor cell.
If the value of the parameter is set too high, the service interruption duration may
get longer.
– SCANITERATION: This parameter is used to define the iteration of scanning a
neighbor BS. If the value of the parameter is set too low, the MS cannot scan all
neighbor cells. If the value of the parameter is set too high, service processing is
affected, that is, the more the number of iteration times is, the longer the service
interruption duration is.
– SCANMINFRAMEPERBS: This parameter is mainly related to the capacity of the
MS. The value range is 0 to 255.
When there are multiple types of MSs, use the maximum value among them so that
each MS can scan neighbor cells.
– MAXDLY: This parameter is a QoS parameter configured on the ASN-GW side.
3. When the scanning is complete, the MS reports the scanning result to the serving BS by
sending the MOB_SCN_RPT message.
4. The serving BS determines the neighbor BSs for handovers for the MS through negotiation.
Based on the scanning result, the serving BS determines whether to initiate a handover.
When the scanning result reaches HOCINRTHRESH or HOPERTHRESH, the serving
BS sends a handover request to candidate BSs through the ASN-GW. Based on the
admission decision, the neighbor BS reports to the serving BS through the ASN-GW about
whether to allow the MS to perform a handover. The serving BS recommends several
neighbor BSs for handovers.

DBS3900 WiMAX
l HOCINRTHRESH: If the value of this parameter is set too low, the handover is
performed frequently, and the signal quality of the target BS is not good. If the value
of this parameter is set too high, the serving BS cannot find the target BS that meets the
conditions for initiating a handover.
l HOPERTHRESH: If the value of this parameter is set too low, the handover is
6. The MS performs CDMA code adjustment on the target BS.
7. The MS initiates a network re-entry request on the target BS by sending the RNG_REQ
message.
NOTE
6.3.3 Fast Ranging Handover

Fast Ranging is used to accelerate network re-entry during a handover. The serving BS instructs
the target BS to actively allocate bandwidth for the MS to send the RNG-REQ message so that
the time for network re-entry is reduced. According to the object that initiates a handover,
handovers are classified into BS-initiated handovers and MS-initiated handovers.
MS-Initiated Handover
The MS can initiate a handover request according to the trigger configured by the BS. The request
message carries the list of target BSs.
Figure 6-4 shows the MS-initiated Fast Ranging handover process.

DBS3900 WiMAX
Figure 6-4 MS-initiated Fast Ranging handover process
1. When receiving a neighbor broadcast message, the MS obtains the neighbor cell parameters
and conditions for triggering handovers and scanning according to the information in the
DCD message and neighbor broadcast message.
The trigger-related parameters are the same as those for ordinary handovers. For details,
see MS-Initiated Handover.
2. If the MS finds that the downlink signal quality meets the trigger conditions for scanning,
the MS initiates the scanning. If neighbor signals meet the trigger conditions, the MS sends
the MOB_MSHO_REQ message to the BS for a handover.
3. The serving BS negotiates with the target BS for handover admission. The target BS
forwards the admission result to the serving BS.
4. After receiving the HO_RSP messages sent by neighbor BSs, the serving BS sends the
MOB_BSHO_RSP message to the MS according to the reports from neighbor BSs. In this
way, the serving BS can recommend several neighbor BSs for handovers. The serving BS
carries the relative frame number of Action Time in the MOB_BSHO-RSP message.
Action Time: This parameter indicates the time (or the number of frames) from the frame
in which the message is sent to the moment when the target BS allocates the
Fast_Ranging_IE message. This parameter can be automatically calculated or configured
by the system. The value range is 0 or 4–16. The value 0 indicates that the Fast_Ranging_IE
is not allocated.

DBS3900 WiMAX
l If the value of Action Time is set too low, the BS may not be ready to send the
Fast_Ranging_IE or the MS is not ready to receive the Fast_Ranging_IE.
l If the value of Action Time is set too high, the handover latency greatly increases.
5. The source BS responds to the target BS by sending the HO_ACK message. If the Fast
Ranging switch of the source BS is set to ON, the HO_ACK message contains Action
Time.
7. When the absolute frame number is Action Time, the target BS allocates the
Fast_Ranging_IE to the MS by sending the UL_MAP message.
8. After receiving the Fast_Ranging_IE, the MS sends the RNG_REQ message using the
Fast_Ranging_IE.
NOTE
BS-Initiated Handover
The BS initiates a handover according to the uplink CINR, uplink PER, and load.
Figure 6-5 shows the BS-initiated Fast Ranging handover process.

DBS3900 WiMAX
Figure 6-5 BS-initiated Fast Ranging handover process
If the uplink CINR, uplink PER, or system load reaches the scanning threshold, the BS initiates
the scanning to obtain the downlink signal quality and sends the MOB_SCN_RSP message,
asking the MS to report the scanning result. After the scanning is complete, the MS reports the
scanning result, and the BS decides whether to initiate a handover according to the scanning
result.
1. The BS determines whether the uplink CINR and uplink PER meet the trigger conditions.
When the uplink CINR is lower than SCANCINRBADTHRESH, or the uplink PER is
higher than SCANPERBADTHRESH, the BS instructs the MS to initiate the scanning
for neighbor cells.
l SCANCINRBADTHRESH: If the value of this parameter is set too low, the scanning
and handover cannot be performed timely. In this case, the MS is disconnected from
the network because of poor signal quality. If the value of this parameter is set too high,
the MS performs the scanning frequently. In this case, the services are affected and the
CPU is occupied.
l SCANPERBADTHRESH: If the value of this parameter is set too low, the MS
performs the scanning frequently so that the services are affected and the CPU is
occupied. If the value of this parameter is set too high, the scanning and handover cannot

DBS3900 WiMAX
be performed timely. The MS may be disconnected from the network when the signal
quality is poor.
NOTE
ULCINRHOSWITCH and ULPERHOSWITCH can be enabled at the same time. In this case, the
BS triggers a handover by using the method whose condition are met first.
2. The MOB_SCN_RSP message sent by the BS to the MS contains SCANDURATION,
SCANINTERVAL, and SCANITERATION.
l SCANINTERVAL: This parameter is used to define the interval of scanning a neighbor
BS. If the value of this parameter is set too low, another scanning process is performed
before services recover. In this case, scheduling is not performed on services in time.
If the value of this parameter is set too high, the entire scanning duration is too long,
and thus the handover opportunity is missed.
l SCANDURATION and SCANITERATION: The two parameters are calculated
through the two parameters SCANMINFRAMEPERBS and MAXDLY.
– SCANDURATION: This parameter is used to define the duration of a neighbor BS.
If the value of the parameter is set too low, the MS cannot scan any neighbor cell.
If the value of the parameter is set too high, the service interruption duration may
get longer.
– SCANITERATION: This parameter is used to define the iteration of scanning a
neighbor BS. If the value of the parameter is set too low, the MS cannot scan all
neighbor cells. If the value of the parameter is set too high, service processing is
affected, that is, the more the number of iteration times is, the longer the service
interruption duration is.
– SCANMINFRAMEPERBS: This parameter is mainly related to the capacity of the
MS. The value range is 2 to 20.
When there are multiple types of MSs, use the maximum value among them so that
each MS can scan neighbor cells.
– MAXDLY: This parameter is a QoS parameter configured on the ASN-GW side.
3. When the scanning is complete, the MS reports the scanning result to the BS by sending
the MOB_SCN_RPT message.
4. The serving BS determines the neighbor BSs for handovers for the MS through negotiation.
Based on the scanning result, the BS determines whether to initiate a handover. When the
scanning result reaches HOCINRTHRESH or HOPERTHRESH, the serving BS sends
a handover request to candidate BSs through the ASN-GW. Based on the admission
decision, the neighbor BS reports to the serving BS through the ASN-GW about whether
to allow the MS to perform a handover.
l HOCINRTHRESH: If the value of this parameter is set too low, the handover is
l HOPERTHRESH: If the value of this parameter is set too low, the handover is
5. After receiving the HO_RSP messages sent by neighbor BSs, the serving BS sends the
MOB_BSHO_REQ message to the MS according to the reports from neighbor BSs. In this
way, the serving BS can recommend several neighbor BSs for handovers. The serving BS
carries the relative frame number of Action Time in the MOB_BSHO-RSP message.

DBS3900 WiMAX
Action Time: This parameter indicates the time (or the number of frames) from the frame
in which the message is sent to the moment when the target BS allocates the
Fast_Ranging_IE message. This parameter can be automatically calculated or configured
by the system. The value range is 0 or 4–16. The value 0 indicates that the Fast_Ranging_IE
is not allocated.
l If the value of Action Time is set too low, the BS may not be ready to send the
Fast_Ranging_IE or the MS is not ready to receive the Fast_Ranging_IE.
l If the value of Action Time is set too high, the handover latency greatly increases.
6. The source BS responds to the target BS by sending the HO_ACK message. If the Fast
Ranging switch of the source BS is set to ON, the HO_ACK message contains Action
Time.
8. When the absolute frame number is Action Time, the target BS allocates the
Fast_Ranging_IE to the MS by sending the UL_MAP message.
9. After receiving the Fast_Ranging_IE, the MS sends the RNG_REQ message using the
Fast_Ranging_IE.
NOTE
6.4 Operations Related to Handover

This section describes how to activate and deactivate the handover feature.
6.4.1 Activating the Handover Feature

This section describes how to activate the handover feature. You can activate the handover
feature on the Web LMT or the M2000.
6.4.2 Deactivating the Handover Feature

DBS3900 WiMAX
This section describes how to deactivate the handover feature. You can deactivate the handover
feature on the web LMT or the M2000.
6.4.1 Activating the Handover Feature

This section describes how to activate the handover feature. You can activate the handover
feature on the Web LMT or the M2000.
Prerequisite
l The basic configurations of sector carriers have been implemented.
Context
l You can perform step 2 only after the sector carrier is deactivated. The modification takes
effect after the sector carrier is activated.
l Handover requires configuration of neighbor cells. Currently, a maximum of 30 neighbor
cells is supported.
l To activate MS-initiated handovers, you need to perform steps 1 to 4. To activate BS-
initiated handovers, you need to perform steps 1 to 5.
NOTE
To activate the Fast Ranging handover, you need to perform step 6.
Procedure
1. Run the LST CARRIERLICENSEINFO command to query the license information
about the corresponding carrier.
Example:
2. Run the MOD CARRIERLICENSEINFO command to set the handover control item of
the carrier.
Example:
MOD CARRIERLICENSEINFO: SECTORID=0, CARRIERID=0, MOBILITY=ON;
Step 2 Run the MOD MACCAPABILITY command to set MOBFEATURESUPP.

Example:
NOTE

The BS supports the handover feature when MOBFEATURESUPP is set to 1, 3, 5, or 7.
Step 3 Query the neighbor cell configuration and add the information about the neighbor cell relations.
1. Run the LST NBR command to query the configured neighbor cells.
2. Run the ADD NBR command to add the information about the neighbor cell relations.
Example:
ADD NBR: CBSID="0000-2E00-6400", NBRBSID="0000-2E00-7000";
Step 4 Query and configure the trigger information.

DBS3900 WiMAX
1. Run the LST TRIGGER command to query the trigger information.

2. Run the ADD TRIGGER command to configure the trigger information.
Example:
ADD TRIGGER: SECTORID=0, CARRIERID=0,TRIGGERID=0, TRIGGERTYPE=0,
TRIGGERFUNCTION=6, TRIGGERACTION=3, TRIGGERVALUE=46, TRIGGERAVERDURATION=10;
Step 5 Query and set the parameters related to the scanning and BS-initiated handover.
1. Run the LST HOPARA command to query the parameters related to the BS-initiated
handover.
NOTE
To query LOADHOSWITCH, run the LST RRMSWITCH command.

2. Run the MOD HOPARA command to set ULCINRHOSWITCH,
ULPERHOSWITCH, and DIFFREQPRIORHOSWITCH to ON, and set
SCANDURATION and SCANMINFRAMEPERBS. Run the MOD RRMSWITCH
command to set LOADHOSWITCH to ON.
Example:
MOD HOPARA: SECTORID=0, CARRIERID=0, ULCINRHOSWITCH=ON, ULPERHOSWITCH=ON,
DIFFREQPRIORHOSWITCH=ON, INTERLEAVINGINTERVAL=50, SCANMINFRAMEPERBS=10;
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, LOADHOSWITCH=ON;
NOTE
l When the value of DIFFREQPRIORHOSWITCH is set to ON, the MS initiates a handover

on the inter-frequency carrier with the best signal quality.
l When the value of DIFFREQPRIORHOSWITCH is set to OFF, the MS initiates a handover
on the carrier with the best signal quality from all intra-frequency carriers and inter-frequency
carriers.
Step 6 Run the MOD SIGENHCFG command to set the information about the Fast Ranging handover.
Example:
MOD SIGENHCFG: FASTRANGINGENABLE=ON;
----End
6.4.2 Deactivating the Handover Feature

This section describes how to deactivate the handover feature. You can deactivate the handover
feature on the web LMT or the M2000.
Context
l You can perform step 1 only after the sector carrier is deactivated. The modification takes
effect after the sector carrier is activated.
Procedure
Step 1 Run the MOD MACCAPABILITY command to set MOBFEATURESUPP.
Example:
NOTE

The BS does not support the handover feature when MOBFEATURESUPP is set to 0, 2, 4, or 6.
Step 2 Run the RMV NBR command to remove the information about the neighbor cell relations so
that the MS cannot find target neighbor cells for handovers.

DBS3900 WiMAX
Example:
RMV NBR: CBSID="0000-2E00-6400", NBRBSID="0000-2E00-7000";
Step 3 Run the MOD HOPARA command to set ULCINRHOSWITCH, ULPERHOSWITCH, and
DIFFREQPRIORHOSWITCH to OFF. Run the MOD RRMSWITCH command to set
LOADHOSWITCH to OFF.
----End
6.5 Maintenance Information of Handover

This section describes the parameters and performance counters related to the handover feature.
Parameters
Table 6-3, Table 6-4, Table 6-5, Table 6-6, Table 6-7, and Table 6-8 list the parameters related
to the handover feature.
Table 6-3 Parameters related to the ADD NBR command
ID Name
CBSID Central BSID
NBRBSID Neighbor BSID
Table 6-4 Parameters related to the RMV NBR command
ID Name
CBSID Central BSID
NBRBSID Neighbor BSID
Table 6-5 Parameters related to the ADD TRIGGER command
ID Name
SECTORID Sector ID
TRIGGERID Trigger ID
TRIGGERTYPE Trigger type
TRIGGERFUNCTION Trigger function
TRIGGERACTION Trigger action
TRIGGERVALUE Trigger value

DBS3900 WiMAX
ID Name
TRIGGERAVERDURATION Trigger duration

ID Name
SECTORID Sector ID
MOBMODESUPP Mobility support
Table 6-7 Parameters related to the MOD HOPARA command

ID Name
SCANCINRBADTHRESH Uplink CINR-triggered scan threshold
SCANPERBADTHRESH Uplink PER-triggered scan threshold
HOCINRTHRESH Uplink CINR-triggered outgoing threshold
HOPERTHRESH Uplink PER-triggered outgoing threshold
HODIFFREQTHRESH Inter-frequency outgoing threshold
ULCINRHOSWITCH Uplink CINR handover decision switch
ULPERHOSWITCH Uplink PER handover decision switch
DIFFREQPRIORHOSWITCH Inter-frequency priority handover switch

ID Name
LOADHOSWITCH Load balance hard handover switch
Table 6-9 lists the performance counters related to the handover feature.

DBS3900 WiMAX
Table 6-9 Performance counters related to the handover feature

Counter Description
Number of MS-initiated See Number of MS-Initiated Handover Requests.

handover requests
Number of successful See Times of Successful Handover Responses from BS.

responses by the BS to
handover requests
Number of MS-initiated See Times of Handover Execution Triggered by MS.

handover implementation
times
Number of BS-initiated See Number of BS-Initiated Handover Requests.

handover requests
Number of MS-initiated See Times of Handover Cancellation Initiated by MS.

handover cancellation times
Number of incoming See Number of Incoming Handover Requests.

handover requests
Number of successful See Times of Successfully Responding to Incoming Handover.

responses to incoming
handovers
Number of prepared See Times of Ready Incoming Handover Execution.

incoming handovers
Number of successful DP See Times of Successful Data Path Establishment for Incoming
setup for incoming Handover.
handovers
Number of ranging requests See Number of Ready Incoming Handover Ranging Requests.
for prepared incoming
handovers
Number of ranging requests See Number of Unready Incoming Handover Ranging

for unprepared incoming Requests.
handovers
Number of successful See Times of Successfully Responding to Incoming Handover

responses to ranging for Ranging.
incoming handovers
Number of complete See Times of Completing Incoming Handover.

incoming handovers
Number of context requests See Number of Incoming Handover Context Requests.

for incoming handovers
Number of successful See Number of Successful Context Requests for Incoming

context requests for Handover.
incoming handovers

DBS3900 WiMAX
6.6 Reference Information of Handover

The protocols that the handover feature complies with are IEEE 802.16-2004/Cor2/D3 with

DBS3900 WiMAX
Feature Configuration Guide 7 Security Mechanism
7 Security Mechanism
About This Chapter
As an emerging wireless broadband technology, the WiMAX brings security problems because
of open transmission channels. For example, unauthorized MSs access the WiMAX network,
air interface data is intercepted or changed, and signaling is changed or forged. Therefore,
subscribers and devices accessing the wireless network must be authenticated, the security and
integrity of data should be guaranteed, and signaling should be verified.
7.1 Overview of Security Mechanism

This section describes the definition, purpose, specifications, and impact of the security
mechanism feature.
7.2 Availability of Security Mechanism
This section describes the network elements (NEs) involved in and version information of the
security mechanism feature.
7.3 Description of Security Mechanism
This section describes the functions provided by the security mechanism feature.
7.4 Operations Related to Security Mechanism
The operations related to the security mechanism feature involve activating and deactivating the
feature.
7.5 Maintenance Information of Security Mechanism
This section describes the parameters and performance counters related to the security
mechanism feature.
7.6 Reference Information of Security Mechanism
The protocols that the security mechanism feature complies with are IEEE 802.16-2004/Cor2/

DBS3900 WiMAX
7 Security Mechanism Feature Configuration Guide
7.1 Overview of Security Mechanism

This section describes the definition, purpose, specifications, and impact of the security
mechanism feature.
Definition
With the security mechanism feature, identity authentication, management message
authentication, and air interface data encryption are performed for preventing unauthorized
subscribers from accessing the network and for ensuring the security and integrity of the data
and messages between the MS and the BS.
Purpose
l Device authentication and subscriber authentication can effectively prevent unauthorized
subscribers and devices from accessing the WiMAX network, occupying resources, and
using the services provided by the WiMAX network.
l Through the CMAC, management message authentication ensures the validity of
management messages, prevents the messages from changes or forgery, and thus avoids
replay attacks.
l Air interface data encryption ensures the security of the data transmitted over the air
interface to prevent subscriber data from interception or changes.
Specifications
l Supporting the authentication procedures specified in the PKMv2 protocol
l Supporting EAP-based authentication on devices and subscribers
l Supporting CMAC-based authentication on air interface messages
l Supporting air interface data encryption through the CCM_128AES algorithm
l Supporting the authentication-free mode
In authentication-free mode, management message authentication and air interface data
encryption are unavailable.
Impact
When air interface data encryption is performed, the data transmission delay is prolonged.
Terms
Term Definition
Replay attack An attacker captures a message over the air interface, and then repeatedly
sends the BS this message for attacks.

DBS3900 WiMAX

Acronym and
Abbreviation Description
AAA Authentication, Authorization and Accounting
AES Advanced Encryption Standard algorithm
AK Authentication/Authorization Key
BS Base Station
CA Certificate Authority
CBC-MAC Cipher Block Chaining Message Authentication Code
CCM Counter with Cipher Block Chaining-Message Authentication Code
CMAC Cipher-based Message Authentication Code
DHCP Dynamic Host Configuration Protocol
EAP Extensible Authentication Protocol
KEK Key Encryption Key
MS Mobile Station
MSK Master Session Key
PDU Protocol Data Unit
PMK Pairwise Master Key
PSK Pre-Shared Key
SA Security Association
TEK Traffic Encryption Key
7.2 Availability of Security Mechanism

This section describes the network elements (NEs) involved in and version information of the
NEs Involved
The implementation of the security mechanism feature requires the cooperation between the SS/
MS, BS, M2000, and AAA. Table 7-1 lists the NEs involved in the security mechanism feature.

DBS3900 WiMAX
Table 7-1 NEs involved in the security mechanism feature
SS/MS BS ASN-GW AAA Server DHCP Server M2000
√ √ √ √ - √
NOTE
In Table 7-1, √ indicates the NE that is involved in the feature, and - indicates the NE that is not involved
in the feature.
Version Support
Table 7-2 lists the versions that support the security mechanism feature.
Table 7-2 Versions that support the security mechanism feature
NE Version
License Restriction
To use the air interface data encryption provided by the security mechanism feature, you need
to apply for a license.
7.3 Description of Security Mechanism

This section describes the functions provided by the security mechanism feature.
With this feature, the following functions are available:
l Device authentication and subscriber authentication

l Key management
l Management message authentication
l Air interface data encryption
7.3.1 Static SA and Dynamic SA

This section describes the applications of the static security association (SA) and dynamic SA.
7.3.2 Procedures of Security Mechanism
This section describes the procedures of the security mechanism feature.
7.3.3 Authentication Capability Negotiation
During the initial network entry, the MS needs to negotiate authentication capabilities with the
BS and ASN-GW to determine whether to perform authentication and which authentication
policy to use, if required.
7.3.4 Identity Authentication

DBS3900 WiMAX
If authentication is required after authentication capability negotiation, identity authentication

must be performed on the MS during the network entry, handover, and activation in idle mode,
AK lifetime expiry.
7.3.5 Key Management
Key management involves generating, allocating, and updating keys.
7.3.6 Management Message Authentication
The message authentication is based on the CMAC, preventing the messages over the air
interface from changes or forgery.
7.3.7 Air Interface Data Encryption
The WiMAX base station supports CCM_128AES encryption. The algorithm for data encryption
and authentication is CCM_128AES, and the algorithm for TEK encryption is
WRAP_AES_128KEY.
7.3.1 Static SA and Dynamic SA

This section describes the applications of the static security association (SA) and dynamic SA.
SA Classification
The SA refers to the security information that is shared by the BS and the MS and is used for
communication encryption. The SA includes key information and encryption algorithms.
SAs are classified into three types:
l Primary SA
l Static SA
l Dynamic SA
Rules of Using SAs

After the MS accesses the network, the BS creates an SA through the three-way SA/TEK
handshake with the MS. The provisioned service flow uses the primary SA, and the dynamic
service flow uses the static SA, dynamic SA, or primary SA as required.
If the static SA and dynamic SA are required, you must run the MOD SA command to enable
them.
l If the value of STASASWITCH is set to ON, the static SA can be used. If the value is set
to OFF, the static SA cannot be used.
l If the value of DYNSASWITCH is set to ON, the dynamic SA can be used. If the value
is set to OFF, the static SA cannot be used.
NOTE
The limitation on the number of SAs supported by each MS is as follows:

l Each MS supports a maximum of 16 SAs, including static SAs, dynamic SAs, and primary SAs.
l Each MS supports a maximum of 14 dynamic SAs.
l The rules for allocating SAs to the network-initiated dynamic service flows are as follows:
– During the establishment of dynamic service flows, the dynamic SA is preferred. If the
dynamic SA is disabled, the BS checks whether the static SA is enabled. If the static
SA is enabled, the static SA is used. If the static SA is disabled, the primary SA is
allocated to the dynamic service flow, as shown in Figure 7-1.

DBS3900 WiMAX
Figure 7-1 SA allocation
– If the number of established dynamic service flows is greater than the number of
dynamic SAs supported by the MS, the static SA is preferred. If static SA is disabled,
the BS allocates the primary SA to the dynamic service flow.
l According to the SA type requested by the MS, the BS allocates the SA to the dynamic
service flow initiated by the MS. The SA allocation complies with the following rules:
– If the MS requests the static SA and primary SA, the BS allocates them to the dynamic
service flow.
– If the dynamic service flow initiated by the MS has used the dynamic SA, the BS
generates a new dynamic SA and then allocates the new dynamic SA to the dynamic
service flow.
– If the number of established dynamic service flows is greater than the number of
dynamic SAs supported by the MS, the static SA is preferred. If the static SA is disabled,
the BS allocates the primary SA to the dynamic service flow.
– If the MS initiates a dynamic service flow but does not specify an SA type, the dynamic
SA is preferred. If the dynamic SA is disabled, the BS allocates a static SA to the
dynamic service flow. If the static SA is disabled, the BS allocates a primary SA to the
dynamic service flow.
7.3.2 Procedures of Security Mechanism

This section describes the procedures of the security mechanism feature.
This feature involves authentication policy negotiation, identity authentication, key

management, management message authentication, and air interface data encryption, as shown
in Figure 7-2.

DBS3900 WiMAX
Figure 7-2 Procedures
NOTE
Management message authentication is a procedure for adding the CMAC value at the end of each message
after the AK, CMAC_KEY_U, and CMAC_KEY_D are generated.
1. During the initial network entry, the MS needs to negotiate with the ASN-GW about
whether to perform identity authentication and about authentication policies. If there is no
need to perform identity authentication, the subsequent procedures are not performed.
2. The X.509 digital certificate is used for implementing EAP-based authentication on devices
between the MS and the AAA server. EAP-based authentication on subscribers is
implemented through the user name and password.
3. Key management is implemented between the MS, the BS, the ASN-GW, and the AAA
server by exchanging messages, including the generation of the AK, CMAC_KEY_U,
CMAC_KEY_D, KEK, TEK, and SA.
4. The communication between the BS and the MS is implemented according to the encryption
capabilities that are negotiated.
7.3.3 Authentication Capability Negotiation

During the initial network entry, the MS needs to negotiate authentication capabilities with the
BS and ASN-GW to determine whether to perform authentication and which authentication
policy to use, if required.
Procedure for Negotiating Authentication Capabilities

Figure 7-3 shows the procedure for negotiating authentication capabilities between the MS, the
BS, and the ASN-GW.

DBS3900 WiMAX
Figure 7-3 Procedure for negotiating authentication capabilities
1. The MS sends the BS the SBC_REQ message with the authentication capabilities of the
MS.
2. After obtaining the authentication capabilities of the MS, the BS sends the ASN-GW the
MS_PreAttachment_Req message, indicating that a new MS has accessed the network and
an authentication policy needs to be negotiated.
3. The ASN-GW responds to the BS with the MS_PreAttachment_Rsp message with the
authentication capabilities supported by the ASN-GW.
4. The BS negotiates with the ASN-GW and MS according to their authentication capabilities,
and sends the SBC_RSP message to the MS.
5. The BS sends the MS_PreAttachment_Ack message to the ASN-GW, informing the ASN-
GW of the negotiation results and authentication policies.
Parameters
NOTE
l If the ASN-GW is set to the authentication-free mode, the MS must be set to the authentication-free
mode. Otherwise, the MS fails to access the network.
l If the ASN-GW is set to the forcible authentication mode, the MS must support the PKMv2 protocol,
the single EAP-based authentication, and the CMAC-based authentication on messages. Otherwise,
the MS fails to access the network.
l If the ASN-GW is set to the negotiation authentication mode:
l The MS must be set to the single EAP-based authentication mode when supporting the PKMv2
protocol, the single EAP-based authentication, and the CMAC-based authentication on messages.
l The MS must be set to the authentication-free mode when supporting the PKMv2 protocol, the
authentication-free mode, and the CMAC-based authentication on messages.
l The MS fails to access the network when not supporting the PKMv2 protocol or the CMAC-based
authentication on messages.
MS Authentication Capabilities
Before network entry, the PKM protocol version, authentication mode, and MAC message
authentication mode must be configured for the MS. During the network entry, the MS sends
the SBC_REQ messages with the authentication capabilities that are configured for the MS. MS
authentication capabilities vary according to the MS type and configuration method. For details,
see the documents associated with the MS.

DBS3900 WiMAX
BS Authentication Capabilities
Currently, the BS supports only the authentication procedures specified in the PKMv2 protocol
and the CMAC-based authentication on messages. No configuration is required. You can run
the LST MACCAPABILITY command to query the BS authentication capabilities.
l If the value of PKM Version Support (PKMVERSUPP) is 2, it indicates that the
authentication procedures specified in the PKMv2 protocol are supported.
l If the value of Mac Message Authentication Mode (MACMODE) is 32, it indicates that
the CMAC-based authentication on messages is supported.
WASN9770 Authentication Capabilities
If the ASN-GW uses Huawei WASN9770, the following authentication modes are supported:
l Authentication-free mode: No device authentication or subscriber authentication is
required for the MS that accesses the network through the WASN9770, and thus the MS
is directly registered.
l Forcible authentication mode: Authentication must be performed on the MS that accesses
the network through the WASN9770.
l Negotiation authentication mode: Negotiation is performed according to MS authentication
capabilities, and then the MS is set to authentication-free mode or single EAP-based
authentication mode according to the negotiation results.
7.3.4 Identity Authentication

If authentication is required after authentication capability negotiation, identity authentication
must be performed on the MS during the network entry, handover, and activation in idle mode,
AK lifetime expiry.
Classification
Identity authentication involves the authentication on the identities of the subscriber and device.
During the network entry, the MS reports the subscriber identity to instruct whether to perform
the subscriber authentication and device authentication. The Huawei product supports the
authentication-free mode. Therefore, during the network entry, the MS needs to negotiate
authentication policies with the equipment at the network side to determine whether to perform
authentication. If there is no need to perform identity authentication, the MS can be directly
registered without device authentication or subscriber authentication.
Device Authentication
l Bidirectional authentication between the MS and the WiMAX network
Device authentication involves the procedures in which the WiMAX network authenticates
the validity of the MS and the MS authenticates the validity of the WiMAX network.
– The WiMAX network authenticates the validity of the MS to check whether the MS is
authorized by the operator. This prevents unauthorized MSs from accessing the network.
– The MS authenticates the validity of the WiMAX network to check whether the network
is valid for providing the subscriber with services. If the WiMAX network authenticates
the validity of the MS but the MS does not authenticate the validity of the WiMAX
network, the invalid WiMAX network can intercept the secret information of the
subscriber, such as the certificate and password. This harms the valid operator's
interests.

DBS3900 WiMAX
l Basic principles
Through the X.509 digital certificate, EAP-based authentication on devices is implemented
between the MS and the AAA server at the network side. Before delivery, the MS and the
AAA server are respectively configured with a unique X.509 digital certificate by their
manufactures. The certificate proves the identity of the certificate owner.
The X.509 digital certificate is required for device authentication. The operator needs to
construct a CA center to provide the certificate or purchase the certificate from a third-party
CA center.
l Authentication process
1. Before network entry, the MS checks whether the AAA server has a valid X.509 digital
certificate to see whether the WiMAX network is valid.
2. After the MS validates that the WiMAX network to be accessed is valid, through the
BS and ASN-GW, the MS sends its X.509 digital certificate to the AAA server for
authentication. The MS can access the network only after the AAA server
acknowledges that the MS is valid.
Subscriber Authentication
Subscriber authentication prevents unauthorized subscribers from network entry, uses service
encryption to prevent the information of authorized subscribers from interception, and ensures
that the services with secret information (such as the e-commerce service and e-banking service)
can be securely transmitted over the air interface.
Subscriber authentication is based on the EAP. The MS and the AAA server must be configured
with the user name and password, which must be checked when the MS accesses the network.
7.3.5 Key Management

Key management involves generating, allocating, and updating keys.
Generating Keys
After the MS passes identity authentication, the AAA server, ASN-GW, BS, and MS generate
the related keys, such as the MSK, PMK, AK, CMAC_KEY_U, CMAC_KEY_D, KEK, and
TEK, by following the procedure shown in Figure 7-4.

DBS3900 WiMAX
Figure 7-4 Procedure for generating keys
In the preceding figure, the related NEs generate the MSK, PMK, AK, AK context,
CMAC_KEY_U, CMAC_KEY_D, and KEK from 1 to 4. 5 to 7 refer to the three-way SA/TEK
handshake, through which the BS and MS confirm that they have the same AK. Then, the BS
uses the negotiated encryption capabilities to generate the TEK and create the SA.
1. After the MS passes identity authentication, the AAA server generates the shared MSK for
the main session and sends it to the ASN-GW.
2. The ASN-GW generates the PMK based on the MSK, and then generates the AK and AK
context based on the MSID and BSID. Then, the ASN-GW sends the AK and AK context
to the BS.
3. The BS generates keys such as the CMAC_KEY_U, CMAC_KEY_D, and KEK according
to the AK context, and starts the LifeTime timer of the AK.
l The KEK is used for encrypting and decrypting the TEK.
l The TEK is the air interface encryption key. It is used for encrypting the services flows
between the BS and the MS.
l The CMAC_KEY_U and CMAC_KEY_D are used for calculating the CMAC value
for MAC management messages.
4. The MS generates the MSK, PMK, AK, AK context, CMAC_KEY_U, CMAC_KEY_D,
and KEK.

DBS3900 WiMAX
5. The BS sends the MS the PKM_RSP/SA_TEK_Challenge message with the values of BS

Random, AKSN, AKID, AK Lifetime, and CMAC.
6. The MS responds with the PKM_REQ/SA_TEK_Request message containing the
encryption capabilities supported by the MS. The CMAC value is added at the end of the
message.
NOTE
If the BS does not receive the SA_TEK_Request message within the duration specified by Duration
of the SA-CHALLENGE timer after transmitting the SA_TEK_Challenge message, the BS
retransmits the SA_TEK_Challenge message. If the times of retransmitting the SA_TEK_Challenge
message reach the value of Number of retries of sending the SA-Challenge message, the BS
requests the MS to exit the network.
7. The BS creates the SA, and sends the PKM_RSP/SA_TEK_Response message with the
MS Random, BS Random, AKID, AKSN, and encryption capability negotiation result to
the MS. The CMAC value is added at the end of the message.
The encryption capability negotiation result is one of the following:
l If there is an intersection of encryption capabilities, the negotiation result is that
encryption is supported, and the TEK and TEKLifeTime are generated.
l If there is no intersection of encryption capabilities, the negotiation result is that
encryption is not supported.
NOTE
You are advised to set the following parameters under the guidance of Huawei engineers. Run the MOD
BSCFG command to set the parameters.
l Duration of the SA-CHALLENGE timer (SAChallengeTimer): specifies the duration for which
the BS waits for the SA_TEK_Request message from the MS after sending the SA_TEK_Challenge
message. The recommended value is 1000 ms.
l If the value of this parameter is great, the duration for which the BS waits for the SA_TEK_Request
message is long. As a result, the network entry success rate of the MS increases. The network entry
delay, however, is increased and system resources are wasted if the value is excessively great.
l If the value of this parameter is small, the duration for which the BS waits for the SA_TEK_Request
message is short. As a result, system resources are saved but the network entry success rate of the
MS decreases.
l Number of retries of sending the SA-Challenge message (SAChallengeRetry): specifies the times
for which the BS retransmits the SA-Challenge message. The recommended value is 3.
l If the value of this parameter is great, it increases the times for which the BS retransmits the
SA_TEK_Challenge message to the MS when the BS does not receive the SA_TEK_Request
message. As a result, the success rate of network entry increases. However, when the MS or link
is exceptional, the system resources are wasted if the BS retransmits the SA_TEK_Challenge
message excessive number of times.
l If the value of this parameter is small, it decreases the times for which the BS retransmits the
SA_TEK_Challenge message to the MS when the BS does not receive the SA_TEK_Request
message. As a result, system resources are saved but the network entry success rate of the MS
decreases.
l Number of retries of sending the SA-TEK-Request message (SATEKRequestRetry): specifies the
times for which the BS retransmits the SA_TEK_Request message. The recommended value is 3.
l If the value of this parameter is great, the success rate of network entry increases but system
resources are wasted if the MS or link is exceptional.
l If the value of this parameter is small, system resources are saved but the network entry success
rate of the MS decreases.
Updating the AK
The MS initiates re-authentication a period before the AK lifetime expires. If the re-
authentication succeeds, the MS and BS generate new AKs. The new AKs and original AKs

DBS3900 WiMAX
coexist for a period. After the three-way SA/TEK handshake is complete, the original AKs are
replaced by the new ones.
If the re-authentication fails, the procedure ends but the MS is not immediately instructed to exit
the network. Then, the BS continues to use the original AK to perform the CMAC verification
on the MS. When the AK lifetime expires, the BS checks the AK. If the BS fails to update the
AK (no AK is available currently), the MS is instructed to exit the network.
The period, when the MS initiates re-authentication in advance, is specified by the Buffer
duration of re-authorization before the AK lifetime expires parameter (AuthGraceTime).
NOTE
The recommended value of this parameter is 600s. You are advised to set the parameter under the guidance
of Huawei engineers. Run the MOD PKMCFG command to set the parameter.
l If the value of this parameter is great, the MS initiates re-authentication a longer period in advance,
and the system security and authentication success rate are improved. The AK, however, is frequently
updated if the MS initiates the re-authentication very early. As a result, system resources are wasted.
l If the value of this parameter is small, the MS initiates re-authentication a shorter period in advance,
that is, initiating the re-authentication is postponed. As a result, system resources are saved. The system
security and authentication success rate, however, become lower if the MS initiates the re-
authentication very late.
Updating the TEK

When TEK life time (TEKLifetime) expires, the BS updates the TEK. The BS maintains the
new TEK and original TEK at the same time to ensure the availability of the TEK. The original
TEK is replaced by the new one immediately when the original one expires, and then another
new TEK is generated.
The MS requests a new TEK a period before the TEK lifetime expires. This period is called
Buffer duration for re-questing the TEK process before the TEK lifetime expires
(TekGraceTime).
Assume that there are two TEKs: TEK0 (original) and TEK1 (new), and that the MS uses TEK0.
When failing to request a new TEK, the MS continues to use TEK0 until the TEK0 lifetime
expires. When detecting that the TEK0 lifetime expires, the BS encrypts data through TEK1
regardless of whether the MS obtains TEK1, and generates another new TEK (TEK2). At this
moment, TEK1 is the original one, and TEK2 is the new one.
NOTE
You are advised to set TEKLifetime and TekGraceTime under the guidance of Huawei engineers. Run
the MOD PKMCFG and MOD MIXCFG commands to set them.
l If the value of TEKLifetime is great, the TEK lifetime is long but the system security is affected.
l If the value of TEKLifetime is small, the TEK lifetime is short but the system security is improved.
If the TEK lifetime is too short, the TEK is frequently updated. As a result, system resources are wasted.
l The value of TekGraceTime must be smaller than half the value of TEKLifetime.
l If the value of TekGraceTime is great, the MS requests a new TEK a longer period in advance and
the TEK update success rate increases. The TEK, however, is frequently updated when the value of
TekGraceTime is excessively great. As a result, system resources are wasted.
l If the value of TekGraceTime is small, the MS requests a new TEK a shorter period in advance and
system resources are saved. The TEK update success rate, however, decreases when the value of
TekGraceTime is excessively small. If the TEK lifetime expires and the BS fails to update the TEK,
the MS uses the latest TEK to encrypt data.

DBS3900 WiMAX
7.3.6 Management Message Authentication

The message authentication is based on the CMAC, preventing the messages over the air
interface from changes or forgery.
The message authentication based on the CMAC is the procedure in which the sender generates
a CMAC value according to the CMAC algorithm and adds the CMAC value at the end of a
message; the receiver calculates a CMAC value according to the received message and checks
whether this CMAC value is the same as the CMAC value carried in the received message. If
they are the same, the check is passed. Otherwise, the check fails, and thus the message is
considered invalid and is discarded.
After the BS and MS generate the AK, CMAC_KEY_U, CMAC_KEY_D, and KEK, the
messages exchanged between the BS and the MS should be authenticated, as shown in Figure
7-5.
Figure 7-5 Message authentication procedure
7.3.7 Air Interface Data Encryption

The WiMAX base station supports CCM_128AES encryption. The algorithm for data encryption
and authentication is CCM_128AES, and the algorithm for TEK encryption is
WRAP_AES_128KEY.
Principles of Air Interface Data Encryption

The sender adds the authentication information to the data to be sent. Then, the receiver verifies
the received data according to the received authentication information to ensure that the data is
intact.

DBS3900 WiMAX
NOTE
The sender encrypts the PDU payload whose header is a common header.
The CCM_128AES is the 128-bit AES encryption algorithm in CCM mode. During encryption
and decryption, data is authenticated in CCM mode.
l CCM
CCM is a universal encryption mode that uses block algorithms. Combining the advantages
of CBC mode in terms of authentication and the advantages of the CTR mode in terms of
confidentiality, the CCM mode provides the guarantee of consistency and security for data
encryption.
– Consistency means that any modification performed on the data during transmission
can be detected.
– Security means that the ciphertext is difficult to decrypt to the plaintext during
transmission.
l AES-CCM
AES-CCM is an encryption method that uses AES as the block encryption algorithm to
encrypt data in CCM mode.
AES-CCM supports encryption and decryption. The sender performs the following
operations to encrypt the plaintext:
1. Performing AES-CBC calculation on the plaintext, key, and additional data to obtain
the CBC-MAC
2. Performing AES-CTR encryption on the CBC-MAC, plaintext, and key to generate
the final ciphertext
The AES-CCM decryption process is the inverse of the encryption process. That is, perform
AES-CTR calculation, and then perform AES-CBC calculation to decrypt the ciphertext
to plaintext.
l WRAP_AES_128KEY encryption algorithm
The WRAP_AES_128KEY encryption algorithm is used for encrypting and decrypting the
TEK, ensuring the security of the TEK when it is transmitted over the air interface.
Encryption input and decryption output require the plaintext to be transmitted and the
integrity check value, which is used for checking the integrity of the plaintext.
Air Interface Data Encryption/Decryption Through the TEK

During the three-way SA/TEK handshake, the MS reports the data encryption capabilities of its
own through the SA_TEK_REQ message, and the BS negotiates with the MS according to the
data encryption capabilities of its own.
l If there is no need to perform data encryption, the MS does not request the TEK and no
protection is provided for the data over the air interface.
l If data encryption is required, the MS requests the TEK from the BS. Then, the BS sends
the TEK to the MS. The data between the MS and the BS is encrypted through the TEK.
This ensures the security of the data over the air interface.
Figure 7-6 shows the procedure in which the MS obtains the TEK.

DBS3900 WiMAX
Figure 7-6 Procedure for obtaining the TEK
1. The MS sends the BS the PKM_REQ/Key_Request message to request the TEK. The
message includes the values of AKSN, SAID, and CMAC.
2. After receiving the PKM_REQ/Key_Request message, the BS verifies the CMAC.
l If the CMAC verification is passed and the value of SAID is valid:
(1) The BS searches for the AK that corresponds to the AKSN carried in the
PKM_REQ/Key_Request message, and encrypts the TEK.
(2) The BS sends the MS the PKM_RSP/Key_Reply message carrying the values of
SAID, AKSN, old TEK parameters, new TEK parameters, and CMAC.
l If the CMAC verification is not passed, the PKM_REQ/Key_Request message is
discarded.
l If the value of AKSN is invalid, the PKM_REQ/Key_Request message is discarded.
l If SAID is unauthorized, the CCM sends the PKM_RSP/Key_Reject message to the
MS.
7.4 Operations Related to Security Mechanism

The operations related to the security mechanism feature involve activating and deactivating the
feature.
7.4.1 Activating the Security Mechanism Feature

The activation of the security mechanism feature refers to activating the air interface data
encryption. Whether to activate other functions of this feature depends on negotiation results.
7.4.2 Deactivating the Security Mechanism Feature
Deactivating the security mechanism feature is an action in which the air interface data
encryption function is disabled. Whether to deactivate other functions of this feature depends
on negotiation results.
7.4.1 Activating the Security Mechanism Feature

The activation of the security mechanism feature refers to activating the air interface data
encryption. Whether to activate other functions of this feature depends on negotiation results.

DBS3900 WiMAX
Prerequisite
l During network entry, the result of the negotiation between the MS and the equipment on
the network side must be that authentication is supported.
l The license file is obtained.
Procedure
Step 1 Run the MOD SA command to configure the switch for enabling the static SA and dynamic SA.
l If DYNSASWITCH is set to ON, the dynamic SA is available. If DYNSASWITCH is set
to OFF, the dynamic SA is unavailable.
l If STASASWITCH is set to ON, the static SA is available. If STASASWITCH is set to
OFF, the static SA is unavailable.
Step 2 Run the MOD ENCRYPTCAP command to configure the data encryption capability set for
the BS.
To set CCM_128AES to the algorithm for data encryption and authentication, and to set
WRAP_AES_128KEY to the algorithm for TEK encryption, run the following command:
MOD ENCRYPTCAP: EncryptTabIndex=0, DataEncryptAlg=2, DataAuthAlg=1,
TekEncryptAlg=4;
Step 3 Run the MOD CARRIERLICENSEINFO command to set AIRITFENCRYPT to ON. Then,
the air interface data encryption function is activated for the sector carrier.
MOD CARRIERLICENSEINFO: SECTORID=0, CARRIERID=1, AIRITFENCRYPT=ON;
----End
7.4.2 Deactivating the Security Mechanism Feature

Deactivating the security mechanism feature is an action in which the air interface data
encryption function is disabled. Whether to deactivate other functions of this feature depends
on negotiation results.
Procedure
Step 1 Run the MOD CARRIERLICENSEINFO command to set AIRITFENCRYPT to OFF.
Then, the air interface data encryption function is deactivated for the sector carrier.
MOD CARRIERLICENSEINFO: SECTORID=0, CARRIERID=1, AIRITFENCRYPT=OFF
----End
7.5 Maintenance Information of Security Mechanism

This section describes the parameters and performance counters related to the security
mechanism feature.
Parameters
Table 7-3, Table 7-4, Table 7-5, Table 7-6 and Table 7-7 list the parameters related to the

DBS3900 WiMAX
Table 7-3 Parameters related to the MOD ENCRYPTCAP command
ID Name
ENCRYPTTABINDEX Encrypt table index
DATAENCRYPTALG Data Encrypt flag
DATAAUTHALG DATAAUTHALG
TEKENCRYPTALG TEK Encrypt flag
ID Name
PKMVERSUPP PKM Version Support
MACMODE Mac Message Authentication Mode
Table 7-5 Parameters related to the MOD BSCFG command
ID Name
SAChallengeTimer Duration of the SA-CHALLENGE timer
SAChallengeRetry Number of retries of sending the SA-Challenge

message
SATEKRequestRetry Number of retries of sending the SA-TEK-Request

message
Table 7-6 Parameters related to the MOD PKMCFG command
ID Name
TekGraceTime Buffer duration for re-questing the TEK process before

the TEK expires
AuthGraceTime Buffer duration of re-authorization before the AK

expires
Table 7-7 Parameter related to the MOD MIXCFG command
ID Name
TEKLifetime TEK life time

DBS3900 WiMAX
Table 7-8 lists the performance counters related to the security mechanism feature.
Table 7-8 Performance counters related to the security mechanism feature

Counter Description
MS originated authentication times See Times of MS Authorization in Initial Network

Entry.
MS originated authentication success See Times of Successful MS Authorization in

times Initial Network Entry.
PKMv2 SA-TEK-Challenge times sent See Times of Sending PKMv2 SA-TEK-Challenge

by BS by BS.
PKMv2 SA-TEK-Request times See Times of Receiving PKMv2 SA-TEK-Request

received by BS by BS.
PKMv2 SA-TEK-Response times sent See Times of Sending PKMv2 SA-TEK-Response

by BS by BS.
RE AUTH REQUEST TIMES See Times of MS-Initiated Re-Authorization.
RE AUTH SUCCESS TIMES See Times of Successful MS-Initiated Re-

Authorization.
7.6 Reference Information of Security Mechanism

The protocols that the security mechanism feature complies with are IEEE 802.16-2004/Cor2/

DBS3900 WiMAX
Feature Configuration Guide 8 PHS
8 PHS
About This Chapter
The payload header suppression (PHS) is a method of suppressing static packet headers. This
chapter describes the basic concepts about, functions of, and implementation of the PHS feature.
8.1 Overview of PHS

This section describes the definition, purpose, specifications, and impact of the PHS feature.
8.2 Availability of PHS
This section describes the network elements (NEs) involved in the PHS feature and the versions
that support the PHS feature.
8.3 Description of PHS
This section describes PHS capability negotiation, payload header suppression, and payload
header restoration.
8.4 Operations Related to PHS
This section describes how to activate and deactivate the PHS feature.
8.5 Maintenance Information of PHS
This section describes the parameters and performance counters related to the PHS feature.
8.6 Reference Information of PHS
The PHS feature complies with IEEE 802.16-2004/Cor2/D3 with latest SRD and WiMAX Forum
Network Architecture Release 1.2.0.

DBS3900 WiMAX
8 PHS Feature Configuration Guide
8.1 Overview of PHS

This section describes the definition, purpose, specifications, and impact of the PHS feature.
Definition
PHS is used to suppress payload headers. After PHS is enabled, only the constant content of the
packet headers is suppressed by the sender according to the suppression rule, and only the varied
contents of the packet header is transmitted. The receiver then restores the packet according to
the suppression rule. PHS is an optional feature on the convergence sublayer (CS) layer and is
enabled for connections.
Purpose
To improve transmission efficiency and save bandwidth.
Specifications
The BS supports a maximum of three PHS rules for each provisioned service flow and dynamic
service flow. If the GW sends more than three classifier rules, the BS creates the PHS rules of
the top three priorities.
Impact
After the PHS feature is enabled, transmission efficiency over the air interface is enhanced.
Terms
Term Definition
Classifier A classifier is a set of matching criteria. It consists of classifier priority

and protocol-related criteria (such as the IP address) for mapping data
packets.
Service flow A service flow is an MAC-layer-based unidirectional transmission

service. It is used to transmit data packets, and is characterized by a set
of QoS parameters , such as latency, jitter, and throughput.
Provisioned In the mechanism of provisioned service flows, the WiMAX system sets
service flow up all the service flows and reserves some resources according to the
service type regardless of whether the subscriber initiates these services.
Dynamic Service A dynamic service flow is different from a provisioned service flow. In
Flow the mechanism of dynamic service flows, traffic flows are established
and resources over R1 and R6 interfaces are occupied only when service
data transmission is required. After a call is complete, the occupied
resources over R1 and R6 interfaces are released immediately.
Therefore, compared with the mechanism of provisioned service flows,
the mechanism of dynamic service flows is more efficient at resource
allocation.

DBS3900 WiMAX

Abbreviation
CID Connection IDentifier
PHS Payload Header Suppression
PHSI Payload Header Suppression Index
PHSF Payload Header Suppression Field
PHSS Payload Header Suppression Size
PHSV Payload Header Suppression Valid
PHSM Payload Header Suppression Mask
MS Mobile Station
BS Base Station
CS Convergence Sublayer
TLV Type Length Value
SDU Server Data Unit
GW GateWay
8.2 Availability of PHS

This section describes the network elements (NEs) involved in the PHS feature and the versions
that support the PHS feature.
NEs Involved
The NEs involved in the PHS feature are the SS/MS, BS, ASN-GW, AAA Server, and M2000.
Table 8-1 lists the NEs involved in the PHS feature.
Table 8-1 NEs involved in the PHS feature

AAA DHCP
√ √ √ √ - √

DBS3900 WiMAX
NOTE
Version Support
Table 8-2 lists the version that supports the PHS feature.
Table 8-2 Version that supports the PHS feature
Product Version
License Restriction
The usage of the PHS feature is controlled by the license.
8.3 Description of PHS

This section describes PHS capability negotiation, payload header suppression, and payload
header restoration.
PHS capability negotiation, payload header suppression, and payload header restoration are
required for the implementation of the PHS on the BS side.
8.3.1 PHS Capability Negotiation
This section describes the negotiations on payload header suppression (PHS) capability.
Negotiations on PHS capability are performed in the REG process, for service flows, in
handovers, and in network reentry from idle mode.
8.3.2 Payload Header Suppression and Restoration Processing
This section describes the process of suppressing and restoring payload headers.
8.3.1 PHS Capability Negotiation

This section describes the negotiations on payload header suppression (PHS) capability.
Negotiations on PHS capability are performed in the REG process, for service flows, in
handovers, and in network reentry from idle mode.
PHS Capability Negotiation During REG Process

The MS and the BS need to negotiate on PHS support capability by sending the REG_REQ
message and the REG_RSP message.
In the REG_REQ and REG_RSP processes, the BS negotiates with the MS on whether the MS
supports the PHS feature. When the PHS license is disabled, the negotiation result in the REG
process is that the MS does not support the PHS feature.
In the added PHSSUPPTYPE field of the BS, the capability of sectors for supporting the PHS
feature is specified.

DBS3900 WiMAX
NOTE
PHSSUPPTYPE indicates the suppression type of the payload header. Its value range is 0-3. Value 0
indicates that header suppression is not supported; value 1 indicates that ATM header suppression is
supported; value 2 indicates that packet header suppression is supported; value 3 indicates that ATM header
suppression and packet header suppression are supported.
When the PHS license is enabled, the negotiation result in the REG process is that the PHS
feature is supported only when it is supported by both the MS and the BS.
PHS Capability Negotiation for Service Flow

PHS is an optional feature. The PHS feature is enabled for the service connection only when the
negotiation result in the REG process is that the PHS feature is supported by both the MS and
the BS and bit 4 of the Request/Transmission Policy parameter TLV indicates that the PHS
feature is supported.
PHS Capability Negotiation in Handover

In the network reentry process after a handover, the target BS may not support the PHS feature.
Therefore, whether the MS can use the PHS feature must be negotiated during the network entry
on the target BS side.
If the PHS rule is specified in the handover related message, and the source BS and the target
BS have the same capability for supporting the PHS feature, an optimized handover process can
be used. That is, the SBC, REG, and DSA processes on the target BS side can be omitted, and
the PHS rule does not need to be sent again.
If the PHS rule is not specified in the handover related message, an initial network entry process
is required after the handover. In the DSA process of the initial network entry process, whether
to enable the PHS feature for the connection is negotiated and the PHS rule is sent.
PHS Capability Negotiation in Network Reentry from Idle Mode

When an MS reenters the network from idle mode, the target BS may not support the PHS feature.
Therefore, whether the MS can use the PHS feature must be negotiated during the MS network
reentry from idle mode.
If the PHS rule is specified in the related message during the network reentry of the MS from
idle mode, and the source BS where the MS is in idle mode and the target BS where the MS
reenters the network from idle mode have the same capability for supporting the PHS feature,
an optimized network reentry from idle mode process can be used. That is, the SBC, REG, and
DSA processes on the target BS side can be omitted, and the PHS rule does not need to be
specified again.
If the PHS rule is not specified in the message related to the network reentry of the MS from
idle mode, an initial network entry process is required when the MS reenters the network from
idle mode. In the DSA process of the initial network entry process, whether to enable the PHS
feature for the connection is negotiated and the PHS rule is sent.
8.3.2 Payload Header Suppression and Restoration Processing

This section describes the process of suppressing and restoring payload headers.
After an SDU is conducted payload header suppression (PHS) according to the PHS rule, a one-
byte PHSI is added. Figure 8-1 shows the PHS for an SDU.

DBS3900 WiMAX
Figure 8-1 Payload header suppression for an SDU
Huawei WiMAX payload header suppression and restoration are conducted on the BS side, as
shown in Figure 8-2.
Figure 8-2 Payload header suppression and restoration
A PHS rule consists of the payload header suppression index (PHSI), Payload Header
Suppression field (PHSF), payload header suppression mask (PHSM), payload header
suppression size (PHSS), and payload header suppression valid (PHSV) information.
l PHSI: is used to index a specific PHS rule. A PHSI value uniquely identifies a service flow.
Its valid value range is 1-255. Value 0 is a special case, which indicates that PHS is not
enabled for the SDU.
l PHSF: is a string of bytes containing the data payload header information to be suppressed.
In fact, it is a snapshot of the uncompressed data packet header. It contains compressed
bytes and uncompressed bytes. If the PHSF changes, the corresponding PHS rule needs to
be updated accordingly. The length of a PHSF is represented by the PHSS field.
l PHSM: indicates whether a byte in the PHSF requires suppression. Each bit in the PHSM
corresponds to one byte in the PHSF. Value 1 of a bit in the PHSM indicates that the sender
needs to suppress the corresponding byte in the PHSF. Value 0 of a bit in the PHSM
indicates that the sender does not need to suppress the corresponding byte in the PHSF.

DBS3900 WiMAX
This field is used to indicate suppression of some fields (such as IP version number filed
and IP header size field) that remain constant in the transmission. However, for those fields,
such as verification and CRC field and serial number field, whose values may change in
the transmission, suppression is not required. The length of this field is round up (PHSS/
8) bytes. The most significant bit (MSB) in the PHSM field corresponds to the first byte in
the PHSF field or in the uncompressed packet. If this PHSM type/length/value (TLV) is
not included, it indicates that all bytes are to be compressed.
l PHSS: is the total number of bytes in the PHSF. Its length is one byte, and its valid value
range is 1-255. A PHS rule must contain the PHSS TLV.
l PHSV: indicates to the sender whether the packet header contents are to be verified before
the sender performs suppression. If the PHSV field is set to 0 or the PHSV TLV is not
included in the service flow, the sender needs to compare the suppressed bytes in the PHSF
with the corresponding bytes in the packet header. If the verification fails, that is, the sender
finds that the contents are inconsistent, the packet header is not suppressed. Only the sender
may need to perform PHS verification.
8.4 Operations Related to PHS

This section describes how to activate and deactivate the PHS feature.
8.4.1 Activating the PHS Feature

This section describes how to activate the PHS feature. You can log in to the Web LMT or the
M2000 to activate the PHS feature.
8.4.2 Deactivating the PHS Feature
This section describes how to deactivate the PHS feature. You can log in to the Web LMT or
the M2000 to deactivate the PHS feature.
8.4.1 Activating the PHS Feature

This section describes how to activate the PHS feature. You can log in to the Web LMT or the
M2000 to activate the PHS feature.
Prerequisite
l Corresponding licenses are allocated by the M2000 to the NEs.
l Configurations related to the sector carriers of the BS are complete.
Context
The PHS feature is controlled by a license. If the PHS license is not allocated, the PHS feature
cannot be enabled. If the PHS license is allocated but the related configuration is not complete
or incorrect, the PHS feature cannot be enabled. If the PHS license is allocated and the related
configuration is correct, the PHS feature can be enabled.
Procedure
Step 1 Query and configure the license information.
Example of the command:

DBS3900 WiMAX
2. Run the MOD CARRIERLICENSEINFO command to configure PHS feature.

MOD CARRIERLICENSEINFO: SECTORID=0, CARRIERID=0, VOIPENHANCE=ON;
Step 2 Run the MOD MACCAPABILITY command to set the value of PHSSUPPTYPE.
MOD MACCAPABILITY: SECTORID=0, CARRIERID=0, PHSSUPPTYPE=2;
NOTE
----End
8.4.2 Deactivating the PHS Feature

This section describes how to deactivate the PHS feature. You can log in to the Web LMT or
the M2000 to deactivate the PHS feature.
Procedure
Step 1 Run the MOD MACCAPABILITY command to set PHSSUPPTYPE to 0.
MOD MACCAPABILITY: SECTORID=0, CARRIERID=0, PHSSUPPTYPE=0;
NOTE
----End
8.5 Maintenance Information of PHS

This section describes the parameters and performance counters related to the PHS feature.
Parameters
Table 8-3 and Table 8-4 describe the parameters related to the PHS feature.
Table 8-3 Parameters related to the MOD CARRIERLICENSEINFO command

ID Name
SECTORID Sector ID
VOIPENHANCE VOIP Enhance

DBS3900 WiMAX

ID Name
SECTORID Sector ID
PHSSUPPTYPE Payload Head Suppression Type
None.
8.6 Reference Information of PHS

The PHS feature complies with IEEE 802.16-2004/Cor2/D3 with latest SRD and WiMAX Forum
Network Architecture Release 1.2.0.

DBS3900 WiMAX
Feature Configuration Guide 9 BS Resource Wholesale
9 BS Resource Wholesale
About This Chapter
The BS resource wholesale feature enables a BS to control the access authority, access
bandwidth, and traffic of multiple retailer domains. It facilitates the allocation of bandwidth for
multiple retailer domains under the coverage of the same BS. This chapter describes the concepts,
functions, and operations related to the BS resource wholesale feature.
9.1 Overview of BS Resource Wholesale
This section describes the definition, purpose, specifications, and impact of the BS resource
wholesale feature.
9.2 Availability of BS Resource Wholesale
This section describes the network elements (NEs) involved in, license restriction about, and
version information about the BS resource wholesale feature.
9.3 Description of BS Resource Wholesale
This section describes the network architecture and the implementation of the BS resource
wholesale feature.
9.4 Operations Related to BS Resource Wholesale
This section describes how to activate and deactivate the BS resource wholesale feature.
9.5 Maintenance Information of BS Resource Wholesale
This section describes the parameters and performance counters related to the BS resource
wholesale feature.
9.6 Reference Information of BS Resource Wholesale
This section describes the reference information of the BS resource wholesale feature. The BS
resource wholesale feature complies with IEEE 802.16-2004/Cor2/D3 with latest SRD and
WiMAX Forum Network Architecture Release 1.2.0.

DBS3900 WiMAX
9 BS Resource Wholesale Feature Configuration Guide
9.1 Overview of BS Resource Wholesale

This section describes the definition, purpose, specifications, and impact of the BS resource
wholesale feature.
Definition
The BS resource wholesale feature enables a network operator to wholesale the network
resources to virtual operators. In this way, virtual operators can expand the number of subscribers
and provide services by renting the network resources from the network operator without
building the entire network. The network operator that wholesales the network resources and
the virtual operator that rents network resources from the network operator are called the network
wholesaler and the network retailer respectively.
Currently, the BS resource wholesale feature is applicable only to the fixed access scenario. It
must be used with the handover control function of the ASN-GW (the mobility of subscribers
is set to handover disabled on the ASN-GW or AAA).
Purpose
To separate network deployment and network operation; to help the network wholesaler to fully
utilize its BS resources and gain more profits; to help the network retailer to expand the number
of subscribers by renting BS resources without building the entire network and to cut the cost
in network investment.
Specifications
A BMPT supports the configuration of a maximum of eight retailers. You can increase the
number of retailers by adding the UTRP. Each UTRP supports the configuration of a maximum
of eight retailers. A BS can support the configuration of a maximum of 48 retailers.
Currently, the BS supports only wholesale of the bandwidth resources over the R6 interface.
Impact
None.
Terms
Term Definition
Wholesaler Network vendor, who sells the network resources wholesale. The
wholesaler's network consists of BS, GW, and CSN equipment, and
provides basic network functions, such as subscriber access, flow
convergence, network connection and control, QoS guarantee, billing, and
management. The wholesaler pays more attention to the network
construction, optimization, and operation and maintenance of the entire
WiMAX network in order to provide a high-performance WiMAX
network.

DBS3900 WiMAX
Term Definition
Retailer Network retailer, who rents the network from the wholesaler to run business
and provides services to end users. The retailer pays more attention to sales
channel development, subscriber management, and provision of rich
services and applications to subscribers.

Acronym and
AAA Authentication, Authorization and Accounting
AP Access Point
ASN-GW ASN Gateway
BOSS Business and Operation Support System
BS Base Station
CSN Connectivity Service Network
DNS Domain Name Server
ISP Internet Service Provider
NAI Network Access Identifier
NMS Network Management System
WIMAX Worldwide Interoperability for Microwave Access
9.2 Availability of BS Resource Wholesale

This section describes the network elements (NEs) involved in, license restriction about, and
version information about the BS resource wholesale feature.
NEs Involved
The BS resource wholesale feature requires the coordination of the SS/MS, BS, and ASN-GW.
Table 9-1 lists the NEs involved in the BS resource wholesale feature.
Table 9-1 NEs involved in the BS resource wholesale feature
AAA DHCP
SS/MS BS ASN-GW Server Server DNS Server M2000
- √ √ √ - - √

DBS3900 WiMAX
NOTE
The BS resource wholesale feature is supported only when the ASN-GW equipment is from
Huawei.
Version Support
Table 9-2 lists the version that supports the BS resource wholesale feature.
Table 9-2 Version that supports the BS resource wholesale feature
Product Version
License Restriction
The usage of the BS resource wholesale feature is controlled by the license.
9.3 Description of BS Resource Wholesale

This section describes the network architecture and the implementation of the BS resource
wholesale feature.
9.3.1 Network Architecture

This section describes the network architecture for the BS resource wholesale feature. The
network architecture for the BS resource wholesale feature is determined by the business mode
and work division of the wholesaler and retailer.
9.3.2 Access Authority Control
This section describes access authority control. The wholesaler's network controls the access
authority of subscribers during the subscriber access process based on the retailer domain that
the subscriber belongs to. If the wholesaler does not allow the access of a subscriber of a retailer,
the BS rejects the access request of the subscriber.
9.3.3 Transmission Resource Control
This section describes transmission resource control. Transmission resource control involves
access bandwidth control and user-plane flow control.

This section describes the network architecture for the BS resource wholesale feature. The
network architecture for the BS resource wholesale feature is determined by the business mode
and work division of the wholesaler and retailer.

DBS3900 WiMAX
Figure 9-1 shows the network architecture for the BS resource wholesale feature. The part on
the left of the dashed line is the wholesaler's network, and the part on the right is the retailer
network.
Figure 9-1 Network architecture for the BS resource wholesale feature
l The wholesaler's network consists of the BS, ASN-GW, and CSN. It provides basic network
functions, such as subscriber access, flow convergence, network connection and control,
QoS guarantee, billing, and management.
l The retailer network can include the CSN. The retailer rents the network from the
wholesaler to run business and provides services to end users. The retailer also provides
network support functions, such as subscriber management, authentication, authorization,
and billing.
NOTE
The CSN can be composed of NEs such as AAA, DNS, DHCP, BOSS, and NMS depending on the business
mode and the work division.
If the wholesaler owns an OSS/BSS system managed on the basis of authority and domain, the
retailer does not need to deploy other network equipment, however, needs to install the client
of the OSS/BSS and log in to the OSS/BSS system of the wholesaler's network through the client
to control its user groups. An OSS/BSS system can be a BOSS system or an AP Manager system.
9.3.2 Access Authority Control

This section describes access authority control. The wholesaler's network controls the access
authority of subscribers during the subscriber access process based on the retailer domain that
the subscriber belongs to. If the wholesaler does not allow the access of a subscriber of a retailer,
the BS rejects the access request of the subscriber.
The process of access authority control is as follows:

DBS3900 WiMAX
1. Determine whether to enable the BS resource wholesale function according to the status of
the wholesale license switch and the access authority control table.
l If the license switch is disabled, the BS resource wholesale function is disabled.
l If the license switch is enabled, whether to enable the access authority control function
of the BS resource wholesale feature is determined on the basis of the access authority
control table. If the access authority control table is blank, access authority control is
not performed. If the access authority control table is not blank, access authority control
is performed.
2. The BS obtains the domain name of the network retailer where the MS belongs from the
network access identifier (NAI).
The BS needs to obtain the MS NAI from the ASN-GW to implement access authority
control of the MS.
l If the BS obtains the MS NAI, it performs access authority control of the MS.
l If the BS does not obtain the MS NAI, it rejects the access of the MS.
The NAI can be in the formats of username@H_RETAILER and H_RETAILER!
username@V_RETAILER. Where, the domain name after @ is used for access authority
control.
3. Perform access authority control according to the access authority control table.
The access authority control information of each retailer in the access authority control
table configured on the M2000 or Web LMT is described as follows:
l RETAILERID: network retailer ID. Its valid value range is 1-253.
l REALM: network retailer domain name. It is a string whose maximum length is 255
characters. The string can be made up of only letters, numbers, and dots.
l MAXUSERNUM: BS-allowed maximum number of subscribers that can access the
retailer network.
l BSIDARRY: BSID that the retailer has access authority on. The configuration of this
parameter is optional.
– If this parameter is not configured, the access authority is controlled on the basis of
the granularity of BSs.
– If this parameter is configured, the access authority is based on the granularity of
BSIDs (sector carriers). A maximum of 12 BSIDARRYs can be configured. The
length of each BSIDARRY is 14 characters, and the input format of the BSIDARRY
is XXXX-XXXX-XXXX.
The process of access authority control is as follows:
(1) Check whether the operator domain where the MS belongs is in the access authority
control table. If the operator domain is not in the access authority control table, the
access of the MS is rejected. If the operator domain is in the access authority control
table, go to the next step.
(2) Check whether the retailer is configured with the BSIDARRY. If the retailer is not
configured with the BSIDARRY, the access of the MS is allowed. If the retailer is
configured with the BSIDARRY, go to the next step.
(3) Check whether the configured BSIDARRY of the retailer includes any BSID that has
made access requests.
l If the BSIDARRY does not include any BSID that has made access requests,
determine whether to perform an inter-frequency assignment for the MS. If other
carriers that the MS has access authority on exist in the same sector, the MS is

DBS3900 WiMAX
assigned an inter-frequency BSID that the MS has access authority on. If no carrier
that the MS has access authority on exists in the sector, the access of the MS is
rejected.
l If the BSIDARRY includes any BSID that has made access requests, determine
whether the number of subscribers that accessed the retailer network exceeds the
configured value of MAXUSERNUM. If the number of subscribers that accessed
the retailer network exceeds the configured value, the access of the MS is rejected.
If the number of subscribers that accessed the retailer network equals to or is
smaller than the configured value, the access of the MS is allowed.
MAXUSERNUM: retailer-allowed maximum number of subscribers.
9.3.3 Transmission Resource Control

This section describes transmission resource control. Transmission resource control involves
access bandwidth control and user-plane flow control.
l The wholesaler's network controls the access bandwidth of subscribers on the BS during
the subscriber access process based on the retailer domain where the subscriber belongs.
l When a subscriber of a retailer network accesses the wholesaler operator network, if the
total amount of interface bandwidth configured for a BS in the retailer network exceeds the
subscribed bandwidth, UL traffic flow control over the R6 interface is performed. (DL flow
control over the R6 interface is implemented by Huawei ASN-GW.)
The process of transmission resource control is as follows:
1. UL and DL access bandwidth over the R6 interface is controlled on the basis of the
subscribed bandwidth parameters TXBW and RXBW.
Service flow admission is controlled by only the logical port of the retailer where the
subscriber belongs. If the logical port resources of a retailer are insufficient, the access of
subscribers is rejected even though other logical ports have sufficient bandwidth for the
subscriber access.
l RETAILERID: It is 0 by default (indicating that the BS resource wholesale feature is
not applied), and access control based on UL/DL bandwidth over the R6 interface is not
performed. If it is a non-0 value, access control is performed on the basis of UL/DL
bandwidth over the R6 interface.
l TXBW: It represents the transmit bandwidth of the logical port. Its value range is
64-150000.
l RXBW: It represents the receive bandwidth of the logical port. Its value range is
64-150000.
l TXCBS: It represents the permitted size of data bursts sent over the logical port. It is
set according to the bandwidth parameter in network planning. Its value must not be
smaller than the traffic of the transmit bandwidth in 1s (that is, TXBW x 1s). The value
of TXCBS is two times of that of TXBW.
2. UL flow control over the R6 interface is implemented on the basis of the subscribed
bandwidth of the retailer.
In fact, one retailer is mapped to one logical port. UL bandwidth over the R6 interface is
controlled on the basis of logical ports. Therefore, UL flow control is performed on the
basis of the subscribed bandwidth of the retailer.
Flow control is performed mainly for non-real-time services, such as nrtPS services and
BE services. When transmission bandwidth over the R6 interface is insufficient, flow

DBS3900 WiMAX
shaping and congestion control are conducted to guarantee high usage of transmission
bandwidth over the R6 interface and the fairness between subscribers.
9.4 Operations Related to BS Resource Wholesale

This section describes how to activate and deactivate the BS resource wholesale feature.
9.4.1 Activating the BS Resource Wholesale Feature

This section describes how to activate the BS resource wholesale feature. You can activate the
BS wholesale feature on the M2000 or the Web LMT.
9.4.2 Deactivating the BS Resource Wholesale Feature
This section describes how to deactivate the BS resource wholesale feature. You can deactivate
the BS wholesale feature on the M2000 or the Web LMT.
9.4.1 Activating the BS Resource Wholesale Feature

This section describes how to activate the BS resource wholesale feature. You can activate the
BS wholesale feature on the M2000 or the Web LMT.
Procedure
Step 1 Query and set license information.
1. Run LST CARRIERLICENSEINFO to query the license information about the
corresponding carrier.
Example:
LST CARRIERLICENSEINFO:;
NOTE
If the control item WHOLESALE of a carrier is ON, the BS resource wholesale feature can be enabled
for all other carriers.
2. Run MOD CARRIERLICENSEINFO to configure BS resource wholesale parameters.
Example:
MOD CARRIERLICENSEINFO: SECTORID=0, CARRIERID=0, WHOLESALE=ON;
Step 2 Configure data.

1. Run ADD WHOLESALE to add the access authority of the retailer.
Example:
ADD WHOLESALE: RETAILERID=3, REALM="HUAWEI", MAXUSERNUM = 100,
BSIDARRY1="0123-1234-2200", BSIDARRY2="0123-1234-2210",
BSIDARRY3="0123-1234-2220", BSIDARRY4="0123-1234-2201",
BSIDARRY5="0123-1234-2211";
NOTE
If BSIDARRY is not included, the access authority is controlled on the basis of the granularity of BSs. If
BSIDARRY is included, the access authority is based on the granularity of BSIDs (sector carriers).
Run MOD WHOLESALE to modify the access authority of the retailer.
2. Run ADD LGCPORT to configure the logical port (UL/DL bandwidth over the R6
interface).
Example:
ADD LGCPORT: CN=0, SRN=0, SN=6, LPN=0, SSN=0, PT=ETH, PN=0, TXBW=10000,
RXBW=10000, TXCBS=20000, TXEBS=20000;

DBS3900 WiMAX
3. Run ADD IPPATH to configure the IPPATH of the retailer.

Example:
ADD IPPATH: PATHID=0, CN=0, SRN=0, SN=6, LPN=0, LOCALIP="172.17.16.200",
PEERIP="7.7.7.7", PATHTYPE=QOS, DSCP=63, RETAILERID =3;
NOTE
The value of RETAILERID must be consistent with that configured in the ADD WHOLESALE
command. Otherwise, the BS resource wholesale feature cannot be enabled successfully.
----End
9.4.2 Deactivating the BS Resource Wholesale Feature

This section describes how to deactivate the BS resource wholesale feature. You can deactivate
the BS wholesale feature on the M2000 or the Web LMT.
Procedure
Step 1 Run RMV WHOLESALE to delete the access authority of the retailer.
Example:
RMV WHOLESALE: RETAILERID=1;
Step 2 Delete the transmission configuration.

1. Run RMV IPPATH to delete the parameter IPPATH of the retailer.
Example:
RMV IPPATH: PATHID=0;
2. Run RMV LGCPORT to delete the unnecessary logical port.

Example:
RMV LGCPORT: CN=0, SRN=0, SN=6, LPN=2;
NOTE
After deleting the retailer information, modify the transmission configuration. The modification may cause
the subscribers of the retailer to exit the network. Therefore, you must perform the modification when
there are few subscribers.
----End
9.5 Maintenance Information of BS Resource Wholesale

This section describes the parameters and performance counters related to the BS resource
wholesale feature.
Parameters
Table 9-3, Table 9-4, Table 9-5, Table 9-6, Table 9-7, Table 9-8, and Table 9-9 list the
parameters related to the BS resource wholesale feature.

ID Name
SECTORID Sector ID

DBS3900 WiMAX
ID Name
WHOLESALE WHOLESALE
Table 9-4 Parameters related to the ADD WHOLESALE command

ID Name
RETAILERID Retailer ID
REALM Realm
MAXUSERNUM MAX User NUM
BSIDARRY BSID with access right
Table 9-5 Parameters related to the ADD LGCPORT and MOD LGCPORT commands
ID Name
CN Cabinet No.
SRN Subrack No.
SN Slot No.
LPN Logical Port No.
SSN Subslot No.
PT Port Type
PN Port No.
TXBW TX Bandwidth
RXBW RX Bandwidth
TXCBS TX Committed Burst Size
TXEBS TX Excessive Burst Size
Table 9-6 Parameters related to the ADD IPPATH command

ID Name
PATHID IP Path ID
CN Cabinet No.
SRN Subrack No.

DBS3900 WiMAX
ID Name
LOCALIP Local IP
PEERIP Peer IP
PATHTYPE IP Path Type
DSCP Differential Service Code
PATHCHK IP Path Check Flag
Table 9-7 Parameters related to the RMV WHOLESALE command

ID Name
Table 9-8 Parameters related to the RMV IPPATH command

ID Name
PATHID IP Path ID
Table 9-9 Parameters related to the RMV LGCPORT command

ID Name
CN Cabinet No.
SRN Subrack No.
SN Slot No.
Table 9-10 lists the performance counters related to the BS resource wholesale feature.

DBS3900 WiMAX
Table 9-10 Performance counters related to the BS resource wholesale feature

Counter Description
network entry failure times due to no getting for See Number of Initial Network Entry
MS NAI Failures due to No MS NAI Obtained.
network entry failure times due to no permitting See Number of Initial Network Entry
Failures due to No Access Permission.
re-entry failure times for idle due to not getting See Number of Failures in Network Re-
for MS NAI Entry from Idle Mode due to No MS NAI
Obtained.
re-entry failure times in idle mode because of no See Number of Failures in Network Re-
permitting Entry from Idle Mode due to No Access
Permission.
Times of entry failure due to no access right and See Number of Network Entry Failures
freq. assign due to Inter-Frequency Assignment
Caused by No Access Permission.
The failure times of admission due to UL See Number of Admission Failures due to
transmission resource limited Limited UL Transmission Resources.
The failure times due to DL transmission resource See Number of Admission Failures due to
limited Limited DL Transmission Resources.
Real-time traffic Packets transmitted by IP Path See Number of Real-Time Traffic

Packets Transmitted by IP Path.
Real-time traffic Bytes transmitted by IP Path See Number of Real-Time Traffic Bytes
Transmitted by IP Path.
Real-time traffic Packets received by IP Path See Number of Real-Time Traffic

Packets Received by IP Path.
Real-time traffic Bytes received by IP Path See Number of Real-Time Traffic Bytes
Received by IP Path.
Non-Realtime traffic Packets transmitted by IP See Number of Non-Real-Time Traffic

Path Packets Transmitted by IP Path.
Non-Realtime traffic Bytes transmitted by IP See Number of Non-Real-Time Traffic

Path Bytes Transmitted by IP Path.
Non-Realtime traffic Packets received by IP Path See Number of Non-Real-Time Traffic

Packets Received by IP Path.
Non-Realtime traffic Bytes received by IP Path See Number of Non-Real-Time Traffic

Bytes Received by IP Path.

DBS3900 WiMAX
9.6 Reference Information of BS Resource Wholesale

This section describes the reference information of the BS resource wholesale feature. The BS
resource wholesale feature complies with IEEE 802.16-2004/Cor2/D3 with latest SRD and
WiMAX Forum Network Architecture Release 1.2.0.

DBS3900 WiMAX
Feature Configuration Guide 10 Network Discovery & Selection/Re-Selection
10 Network Discovery & Selection/Re-

Selection
About This Chapter
Network discovery & selection/re-selection (ND&S) refers to a function based on which the
MS/SS selects the network service provider (NSP). This chapter describes the basic concepts,
functions, and operations of the ND&S feature.
10.1 Overview of ND&S

This section describes the definition, purpose, specifications, and impact of the ND&S feature.
10.2 Availability of ND&S
This section describes the network elements (NEs) involved in the ND&S feature and the version
that supports the ND&S feature.
10.3 Description of ND&S
This section describes the principle and deployment scenario of the ND&S feature.
10.4 Operations Related to ND&S
This section describes how to activate and deactivate the ND&S feature.
10.5 Maintenance Information of ND&S
This section describes the parameters and performance counters related to the ND&S feature.
10.6 Reference Information of ND&S
The protocols that the ND&S feature complies with are the IEEE 802.16-2004/Cor2/D3 with
latest SRD and the WiMAX Forum Network Architecture Release 1.2.0.

DBS3900 WiMAX
10 Network Discovery & Selection/Re-Selection Feature Configuration Guide
10.1 Overview of ND&S

This section describes the definition, purpose, specifications, and impact of the ND&S feature.
Definition
ND&S refers to a function based on which the WiMAX MS/SS detects and selects the network
access provider (NAP) and network service provider (NSP).
Purpose
An NAP with frequency resources has requirements for leasing the access service network
(ASN). An NSP without frequency resources has requirements for renting the ASN to expand
the number of users. This kind of requirement is the wholesale service. Each time the MS/SS is
powered on, it may receive signals from multiple BSs, which belong to different NAPs. An NAP
can have more than one NSP. Therefore, the MS/SS discovers and selects all available NAPs
and NSPs through the ND&S feature.
The ND&S feature supports flexible networking. When NAP sharing is adopted, an NAP can
provide access services for multiple NSPs.
The ND&S feature is the prerequisite for the network wholesale feature. Network operators can
provide network wholesale services through the ND&S feature.
The coexistence of multiple NSPs provides more opportunities for end users to select their
favorite networks and services.
Specifications
Each BS supports a maximum of 30 NSPs.
Impact
The NAI construction in the roaming feature must be consistent with that in the ND&S feature.
Terms
Term Definition
ND&S Network discovery & selection/re-selection
Wholesa Network vendor, who sells the network resources wholesale. The network of a
ler wholesaler consists of the BS, GW, and CSN, and provides basic network
functions such as subscriber access, flow convergence, network connection and
control, QoS guarantee, billing, and management. The wholesaler pays more
attention to network establishment, optimization, and operation and maintenance
of the entire WiMAX network in order to provide a high-performance WiMAX
network.
BSID BS ID (48 bits) = operator ID (24 bits) + site ID (16 bits) + sector ID (4 bits) +
carrier ID (4 bits)

DBS3900 WiMAX

Acronym and
AAA Authentication Authorization

Accounting
ASN Access Service Network
ASN-GW Access Service Network Gateway
ASP Application Service Provider
BS Base Station
CSN Connectivity Service Network
DHCP Dynamic Host Configuration

Protocol
HA Home Agent
MS/SS Mobile Station/Subscriber Station
NAP Network Access Provider
NSP Network Service Provider
NAI Network Access Identifier
10.2 Availability of ND&S

This section describes the network elements (NEs) involved in the ND&S feature and the version
that supports the ND&S feature.
NEs Involved
The ND&S feature requires the support from the SS/MS, BS, ASN-GW, AAA, and M2000.
Table 10-1 lists the NEs involved in the ND&S feature.
Table 10-1 NEs involved in the ND&S feature
√ √ √ √ - √
NOTE
that are not involved in this feature. The SS/MS must support the ND&S feature.

DBS3900 WiMAX
Version Support
Table 10-2 lists the version that supports the ND&S feature.
Table 10-2 Version that supports the ND&S feature

Product Version
BS DBS3900 V300R002C03
License Restriction
The usage of the ND&S feature is controlled by a license.
10.3 Description of ND&S

This section describes the principle and deployment scenario of the ND&S feature.
10.3.1 Principles of ND&S

This section describes the principles of the ND&S feature. The process of ND&S consists of
four tasks: NAP discovery, NSP discovery, NSP enumeration and selection, and ASN
attachment.
10.3.2 Deployment Scenario of ND& S
This section describes the deployment scenario of NAP sharing for ND&S. NAP sharing is a
technology based on which the network of an NAP are shared by multiple NSPs.
10.3.1 Principles of ND&S

This section describes the principles of the ND&S feature. The process of ND&S consists of
four tasks: NAP discovery, NSP discovery, NSP enumeration and selection, and ASN
attachment.
Figure 10-1 shows the process for implementing ND&S.
Figure 10-1 Process for implementing ND&S

DBS3900 WiMAX
1. NAP discovery: After an MS/SS is powered on, it searches the ASN for the list of available
NAPs and obtains the NAP ID, that is, operator ID.
The BS in the ASN broadcasts the DL_MAP message in each frame that carries the BS ID
field. The MS/SS scans and synchronizes the downlink channels of the BS one by one based
on the configuration information, and then abstracts the most significant 24 bits from the
BS ID field in the DL_MAP message, that is, NAP ID.
NOTE
l BS ID (48 bits) = Operator ID (24 bits) + Site ID (16 bits) + Sector ID (4 bits) + Carrier ID (4
bits)
l The most significant 24 bits indicate the operator ID, that is, NAP ID. The operator ID identifies
the owner of the ASN, and it is provided by the network operator.
l The least significant 24 bits indicate the BS ID. The foremost one bit indicates the NSP ID Flag.
The MS/SS can determine whether the ND&S function is enabled according to the range of the
site ID.
l The value range of the site ID in the BSID is 32768 to 65535 (b1000000000000000 to
b1111111111111111). Set the NSP Identifier Flag indicator in the BSID to 1 and enable the
functions of ND&S.
l The value range of the site ID in the BSID is 0 to 32767 (b0000000000000000 to
b0111111111111111). Set the NSP identifier flag indicator in the BSID to 0 and disable the
functions of ND&S.
The objective of NAP discovery is to enable the MS/SS to lock an appropriate frequency
for communication with the BS.
The method of NAP discovery is as follows:
l The MS/SS scans frequencies and decodes the DL_MAP message sent by the BS.
l The MS/SS obtains the NAP ID in the BS ID field, and the deployment mode.
2. NSP discovery: The MS/SS detects the list of all the NSPs (list of NSP IDs) that are
connected to the specified NAP.
On the WiMAX network, one NAP supports one or more NSPs. NSP discovery refers to
a process in which the MS/SS searches for all available NSP IDs and NSP realm names on
the network side.
NOTE
The NSP information contains three fields:

l NSP ID (a 24-bit globally unique identifier): The MS/SS determines whether it is served by the
home NSP or visited NSP based on the NSP ID.
l NSP realm (NSP realm name, an ASCII string): The maximum length defined in the standard is
256 octets. Currently, the maximum length defined in the AAA is 40 octets. The MS/SS uses the
NSP realm to construct an appropriate NAI character string.
l NSP name: The maximum length defined in the standard is 256 octets. Currently, the maximum
length defined in Huawei products is 40 octets. When a subscriber selects the NSP manually,
NSP names are displayed on the MS/SS. In the case of automatic NSP selection, NSP names are
not required.
The objectives of NSP discovery are as follows:
l To enable the MS/SS to obtain the list of all the NSPs that are directly connected to the
NAP
l To enable the MS/SS to display NSP names for subscribers to select during manual NSP
selection
NSP discovery is performed in two modes, which are as follows:
l Static discovery: The mapping relation between the NAP ID and the NSP ID is
configured before the delivery of an MS/SS. In this way, the MS/SS can find the network

DBS3900 WiMAX
of the NSP that it subscribes to according to the mapping relation after it completes
NAP discovery.
l Dynamic discovery
– By using the SBC message
After the NSP list is updated, the BS updates the value of NSP Change Count
TLV in the DCD message and instructs the MS/SS to obtain the new NSP list from
the network side. The MS/SS sends an SBC-REQ message to the BS, and then the
network side returns the SBC-RSP message that carries the new NSP list.
– By using the SII-ADV message
After the NSP list is updated, the BS broadcasts the new NSP list in the SII-ADV
message.
3. NSP enumeration and selection: The MS/SS displays the NSP list so that the subscriber
can select an appropriate NSP.
After the MS/SS obtains the NSP list associated with the NAP, an NSP can be selected in
manual selection mode or in automatic selection mode.
l Manual selection mode: The MS/SS displays the available NSPs, and then the subscriber
can select an NSP from them.
l Automatic selection mode: The MS/SS automatically selects an NSP according to the
configured priority. No human operation is required.
4. ASN attachment: The MS/SS obtains the specified NSP realm to construct a correct NAI.
ASN attachment refers to a process in which the MS/SS provides its own identifier and the
home NSP realm.
The NAI can be constructed in the following ways:
l In the non-roaming scenario, the MS/SS uses the home NSP realm and user name to
construct the NAI and accesses the network. The ASN-GW obtains the routing
information according to the NAI realm.
l In the roaming scenario, the MS/SS uses the visited NSP realm and user name to
construct the NAI and accesses the network. The ASN-GW obtains the routing
information according to the NAI realm.
The objective of ASN attachment is to enable the MS/SS to notify the network side of the
selected NSP. The MS/SS requests the network side to route all the authentication messages
to the network (CSN) of the selected NSP.
The process of ASN attachment is as follows:
(1) The MS/SS obtains the realm name of the selected NSP ID if the mapping relation
between the NSP ID and the NSP realm is not configured on the MS/SS.
(2) The MS/SS constructs a correct NAI.
(3) The MS/SS sends the authentication message carrying the NAI to the ASN. Then, the
ASN-GW determines the AAA to which the authentication message is routed on the
basis of the realm name in the NAI.
NOTE
l The NSP belongs to a home NAP. After the NSP is selected, the NAP is selected.
l In the case of dynamic NSP discovery and selection, the manual or automatic NSP selection
mode is set on the MS/SS by the subscriber.

DBS3900 WiMAX
10.3.2 Deployment Scenario of ND& S

This section describes the deployment scenario of NAP sharing for ND&S. NAP sharing is a
technology based on which the network of an NAP are shared by multiple NSPs.
Deployment Scenario of NAP Sharing

Figure 10-2 shows the network topology of NAP sharing.
Figure 10-2 Network topology of NAP sharing
The WiMAX network can be classified into two networks, that is, ASN (provided by the NAP)
and CSN (provided by the NSP). Theoretically, the two networks can be provided by different
network operators. That is, the NAP provides the BS and ASN-GW for the radio network access
function, and the NSP provides the AAA, HA, and DHCP server for the service connections.
The NAP and NSP are network operators. Each of them has a globally unique identifier. The
identifier of the NAP is NAP ID, and that of the NSP is NSP ID.
In the WiMAX network, an ASN can be connected to multiple CSNs. Therefore, the network
must provide the NAP ID list and the NSP ID list for the MS/SS to select.
The deployment scenario of NAP sharing refers to the scenario in which the NAP wholesales
NAP resources to other NSPs. In this scenario, the R3 interface must be open, and the ASN can
be connected to multiple CSNs.
Implementation of NAP Sharing

Figure 10-3 shows the process for implementing NAP sharing.

DBS3900 WiMAX
Figure 10-3 Process for implementing NAP sharing
1. The MS/SS abstracts the BS ID from the DL_MAP message to obtain the NAP ID and
deployment mode. If the value of NSP Identifier Flag is 1, it indicates the NAP sharing
scenario. That is, the functions of ND&S are enabled.
2. The BS sends to the MS/SS the DCD message carrying the NSP Change Count TLV field.
Then, the MS/SS checks whether the NSP list is changed according to the NSP Change
Count TLV field and updates the NSP list if required.
The NSP Change Count is unique in the NAP ID range. If the MS/SS has accessed the
networks of multiple NAPs, the MS/SS stores the NAP ID of each NAP and the
corresponding NSP Change Count and NSP list.
3. After the MS/SS finds any change in the NSP list, it sends the SBC-REQ message to the
BS. Then, the BS responds with the SBC-RSP message carrying the new NSP list, or the
BS broadcasts the new NSP list in the SII-ADV message to the MS/SS.
4. The MS/SS selects an NSP from the NSP list.
When the auto mode is set on the MS/SS, the MS/SS automatically selects an NSP from
the NSP list according to the priority.
When the manual mode is set on the MS/SS, the MS/SS displays the NSP names in the
NSP list that is obtained during the NSP discovery process so that the subscriber can select
the NSP from the NSP list.
5. The MS/SS constructs an NAI according to the selected NSP and sends it to the ASN-GW.
When the MS/SS is in the home NSP realm, that is, at least one NSP ID in the NSP list that
is broadcast by the BS is the same as the home NSP ID stored in the MS/SS, the MS/SS is
aware of its home NSP and can be directly connected to the network of the home NSP
through the network of the NAP. In this case, the NAI format is username@homeRealm.
When the MS/SS is in the roaming area, that is, the NSP list that is broadcast by the BS
does not contain the home NSP ID stored in the MS/SS, the MS/SS cannot be directly
connected to the network of the home NSP through the network of the NAP. The MS/SS
can be connected to the network of the home NSP only through the network of a visited
NSP. In this case, the NAI format is homeRealm!username@visitedRealm.

DBS3900 WiMAX
6. The ASN-GW forwards the information to the corresponding NSP according to the NAI.
Then, the MS/SS initiates the network entry process.
10.4 Operations Related to ND&S

This section describes how to activate and deactivate the ND&S feature.
10.4.1 Activating the ND&S Feature

This section describes how to activate the ND&S feature. You can log in to the Web LMT or
the M2000 to activate the ND&S feature.
10.4.2 Deactivating the ND&S Feature
This section describes how to deactivate the ND&S feature. You can log in to the Web LMT or
the M2000 to deactivate the ND&S feature.
10.4.1 Activating the ND&S Feature

This section describes how to activate the ND&S feature. You can log in to the Web LMT or
the M2000 to activate the ND&S feature.
Prerequisite
l Sector carriers can be activated.
Procedure
Step 1 Run the MOD BTSINFO command to set the BSID so that the BS can support the ND&S
feature.
Example:
MOD BTSINFO: OPERATORID=46, SITEID=32768;
NOTE
The value range of the site ID in the BSID is 32768 to 65535, and the functions of ND&S are enabled.
Running this command may change the BS ID. After the network planning, however, the BS ID cannot be
changed unless necessary. Therefore, the network planning personnel needs to set the BS ID according to
the requirement of network planning for ND&S during the initial configuration.

Example:
2. Run the MOD CARRIERLICENSEINFO command to set the ND&S control items of
the carrier.
Example:
MOD CARRIERLICENSEINFO: SECTORID=0, CARRIERID=0, WHOLESALE =ON;
Step 3 Run the ADD NSP command to add an NSP.

Example:
ADD NSP: NSPID=3, NSPNAME="huawei", NSPREALM="huawei.com";
----End

DBS3900 WiMAX
10.4.2 Deactivating the ND&S Feature

This section describes how to deactivate the ND&S feature. You can log in to the Web LMT or
the M2000 to deactivate the ND&S feature.
Procedure
Step 1 Run the RMV NSP command to clear the information about the NSP. In this way, the NDS
feature can be disabled.
Example:
RMV NSP: NSPID=3;
----End
10.5 Maintenance Information of ND&S

This section describes the parameters and performance counters related to the ND&S feature.
Parameters
Table 10-3, Table 10-4, Table 10-5, Table 10-6, and Table 10-7 list the parameters related to
the ND&S feature.
Table 10-3 Parameters related to the ADD NSP command
ID Name
NSPID NSP ID
NSPNAME NSP Name
NSPREALM NSP Realm
Table 10-4 Parameter related to the RMV NSP command
ID Name
NSPID NSP ID
Table 10-5 Parameters related to the MOD NSP command
ID Name
NSPID NSP ID
NSPNAME NSP Name
NSPREALM NSP Realm

DBS3900 WiMAX
Table 10-6 Parameter related to the LST NSP command

ID Name
NSPID NSP ID
Table 10-7 Parameter related to the MOD BTSINFO command

ID Name
OPERATORID NSP ID
SITEID Site ID
Table 10-8 lists the performance counters related to the ND&S feature.
Table 10-8 Performance counters related to the ND&S feature

Counter Description
Network Entry Success Rate See Initial Network Entry Success Rate.
Network Entry Failure Times due to No See Number of Initial Network Entry Failures due
Getting for MS NAI to No MS NAI Obtained.
Network Entry Failure Times Due to No See Number of Initial Network Entry Failures due
Permitting to No Access Permission.
10.6 Reference Information of ND&S

The protocols that the ND&S feature complies with are the IEEE 802.16-2004/Cor2/D3 with
latest SRD and the WiMAX Forum Network Architecture Release 1.2.0.

DBS3900 WiMAX
Feature Configuration Guide 11 Dynamic Service Flow
11 Dynamic Service Flow
About This Chapter
The WiMAX system that supports dynamic service flows can dynamically initiate and terminate
the creation and release of service flows. This chapter describes the basic concepts, functions,
and settings of the dynamic service flow feature.
11.1 Overview of Dynamic Service Flow

This section provides the definition, purpose, specifications, and impact of the dynamic service
flow feature.
11.2 Availability of Dynamic Service Flow
his section describes the network elements involved in and version information about the
dynamic service flow feature.
11.3 Description of Dynamic Service Flow
This section describes the dynamic service flow in detail. The dynamic service flow feature is
applied to the VoIP services of Huawei WiMAX network. Huawei WiMAX system uses
dynamic service flows to carry VoIP services. That is, when a subscriber picks up the phone, an
ertPS service flow is established to carry VoIP services. When the subscriber hangs up, the
service flow is deleted and related system resources are released immediately.
11.4 Operations Related to Dynamic Service Flow
This section describes how to activate and deactivate the dynamic service flow feature.
11.5 Maintenance Information of Dynamic Service Flow
This section describes the parameters and performance counters configured on the BS for the
11.6 Reference Information of Dynamic Service Flow
The dynamic service flow feature complies with IEEE 802.16-2004/Cor2/D3 with latest SRD
and WiMAX Forum Network Architecture Release 1.2.0.

DBS3900 WiMAX
11 Dynamic Service Flow Feature Configuration Guide
11.1 Overview of Dynamic Service Flow

This section provides the definition, purpose, specifications, and impact of the dynamic service
flow feature.
Definition
A dynamic service flow is different from a provisioned service flow. In the mechanism of
provisioned service flows, the WiMAX system sets up all the service flows and reserves some
resources based on the service type regardless of whether the subscriber initiates these services.
When a large amount of resources are reserved, the admission of other MSs may fail due to lack
of necessary resources. In this case, the radio resource usage is significantly decreased and the
user experience is affected.
In the mechanism of dynamic service flows, service flows are created and resources over R1
and R6 interfaces are occupied only when service data transmission is required. After a session
is complete, the occupied resources over R1 and R6 interfaces are released immediately.
Therefore, compared with the mechanism of provisioned service flows, the mechanism of
dynamic service flows is more efficient at resource allocation.
Purpose
To achieve resource sharing, enhance the usage of system resources (especially air interface
resources), and expand the network capacity.
Specifications
None.
Impact
Term Definition
Service flow A service flow is an MAC-layer-based unidirectional transmission service. It

is used to transmit data packets, and is characterized by a set of QoS
parameters , such as latency, jitter, and throughput.
Classifier A classifier is a set of matching criteria. It consists of classifier priority and

protocol-related criteria (such as the IP address) for mapping data packets.
Terms
None.

DBS3900 WiMAX

Abbreviation
AAA Server Authentication, Authorization and Accounting Server
BS Base Station
SBC Session Border Controller
ASN-GW Access Service Network Gateway
SS/MS Subscriber Station/Mobile Station
AF Application Function
P-CSCF Proxy-Call Session Control Function
IMS IP Multimedia Subsystem
SIP Session Initiation Protocol
VOIP Voice over IP
BE Best effort
ertPS Extended rtPS
rtPS Real-time polling service
UGS Unsolicited grant service
DSA Dynamic service addition
DSC Dynamic service change
DSD Dynamic service deletion
DSx Dynamic service addition, change, or deletion
PHS Payload Header Suppression
11.2 Availability of Dynamic Service Flow

his section describes the network elements involved in and version information about the
Network Elements Involved

Table 11-1 lists the network elements (NEs) involved in the MS-initiated dynamic service flow
feature.

DBS3900 WiMAX
Table 11-1 NEs involved in the MS-initiated dynamic service flow
√ √ √ - - -
NOTE
In Table 11-1, √ is used to mark NEs that are involved in the feature, and - is used to mark NEs that are
not involved in the feature. If the mechanism of MS-initiated dynamic service flow is adopted, make ensure
that the MS is able to send messages to initiate dynamic service flows.
Version Support
Table 11-2 lists the version that supports the dynamic service flow feature.
Table 11-2 Version that supports the dynamic service flow feature
Product Version
BS DBS3900 V300R002C03
License Restriction
The dynamic service flow feature is controlled by a license.
11.3 Description of Dynamic Service Flow

This section describes the dynamic service flow in detail. The dynamic service flow feature is
applied to the VoIP services of Huawei WiMAX network. Huawei WiMAX system uses
dynamic service flows to carry VoIP services. That is, when a subscriber picks up the phone, an
ertPS service flow is established to carry VoIP services. When the subscriber hangs up, the
service flow is deleted and related system resources are released immediately.

This section describes the typical network architecture of MS-initiated dynamic service flows
by taking the VoIP service as an example.
11.3.2 Principles
This section describes the process of MS-initiated dynamic service flow creation and deletion

This section describes the typical network architecture of MS-initiated dynamic service flows
Figure 11-1 shows the typical network architecture of MS-initiated dynamic service flows.

DBS3900 WiMAX
Figure 11-1 Network architecture of MS-initiated dynamic service flows
11.3.2 Principles
This section describes the process of MS-initiated dynamic service flow creation and deletion

DBS3900 WiMAX
Dynamic Service Flow
Figure 11-2 Process of MS-initiated dynamic service flows
1. An MS enters the network. During the network entry process, the WiMAX system
provisions one pair of BE service flows and one pair of nrtPS service flows. Usually, the
BE service flows are used to bear DHCP data and data services, and the nrtPS service flows
are used to carry session initiation protocol (SIP) signaling.
2. After the MS enters the network, it obtains the MSIP and the IP address of the Proxy-Call
Session Control Function (P-CSCF) through the DHCP process.
l MSIP is the IP address assigned to the MS.
l Only after the MS obtains the IP address of the P-CSCF, it can initiate the SIP
registration at the P-CSCF.
3. The MS can initiate SIP sessions only after it completes SIP registration and authentication
processes.
4. When the MS originates a session, it triggers the WiMAX system to create dynamic service
flows. See Creating Dynamic Service Flows.
5. After the session ends, the MS initiates a process to delete dynamic service flows and release
the resources occupied over the R1 and R6 interfaces. See Deleting Dynamic Service
Flows.
Creating Dynamic Service Flows

Figure 11-3 shows the process of creating dynamic service flows after the MS originates a VoIP
call.

DBS3900 WiMAX
Figure 11-3 Creating dynamic service flows (MS-initiated)
1. An MS calls another MS by sending an SIP INVITE message.

2. The called MS returns a 180 Ringing message to the calling MS. At the same time, the
incoming call rings, and the ring-back tone is sent through a BE service flow.
3. The called MS answers the call, and the called MS sends back a 200 OK message to the
calling MS.
4. The calling MS and the called MS construct a DSA_REQ message based on the provisioned
information and the information interpreted from the SIP message, and then send the
DSA_REQ message to the BS to request the creation of dynamic service flows. The MS,
BS, and ASN-GW interact with each other, process related messages, and then create UL
ertPS service flows and DL ertPS service flows over the R1 and the R6 interfaces.
5. The calling MS and called MS use these created ertPS service flows to bear the VoIP call.
Deleting Dynamic Service Flows

When any party of a session ends the session, the WiMAX system deletes the dynamic service
flow.
1. The MS that initiates the ending of the session sends a DSD_REQ message requesting the
deletion of the corresponding ertPS service flows. The MS, BS, and ASN-GW interact with
each other, and then delete corresponding ertPS service flows over the R1 and R6 interfaces.
At the same time, the MS that ends the session sends the SIP BYE message to the MS on
the other side.
2. After the MS on the other side detects the SIP BYE message, it requests for the deletion of
the corresponding ertPS service flows. Then, the MS, BS, and ASN-GW interact with each
other, and then delete the corresponding ertPS service flows over the R1 and R6 interfaces.
11.4 Operations Related to Dynamic Service Flow

This section describes how to activate and deactivate the dynamic service flow feature.

DBS3900 WiMAX
11.4.1 Activating the Dynamic Service Flow Feature

This section describes how to activate the dynamic service flow function.
11.4.2 Deactivating the Dynamic Service Flow Feature
This section describes how to configure the license control item to deactivate the dynamic service
flow function.
11.4.1 Activating the Dynamic Service Flow Feature

This section describes how to activate the dynamic service flow function.
Prerequisite
l The valid license file with enhanced VoIP functions is obtained and sent from the M2000
to the BS.
l The basic configurations of the BS are complete and the BS can run normally.
Procedure
Step 1 Run MOD CARRIERLICENSEINFO to set VOIPENHANCE to ON.
----End
11.4.2 Deactivating the Dynamic Service Flow Feature

This section describes how to configure the license control item to deactivate the dynamic service
flow function.
Procedure
Step 1 Run MOD CARRIERLICENSEINFO to set VOIPENHANCE to OFF to deactivate the
enhanced VoIP function, that is, to deactivate the dynamic service flow feature.
NOTE
When the enhanced VoIP function is disabled, the PHS feature is deactivated.
----End
11.5 Maintenance Information of Dynamic Service Flow

This section describes the parameters and performance counters configured on the BS for the
Related Parameter
Table 11-3 and Table 11-4 list the parameters related to the dynamic service flow feature.

DBS3900 WiMAX
Table 11-3 Parameters related to the MOD MSCFG command

Parameter Parameter Parameter Description
ID Name
T8Timeout Timeout time For MS-initiated dynamic service flows: If a BS fails to

of waiting for receive the DSX_ACK message from an MS in a duration
the DSX-ACK specified by T8Timeout after sending the DSX_RSP
message message to the MS, the BS resends the DSX_RSP
message to the MS.
DSxRespRetr Number of
DsxReqRetry indicates the maximum number of times
y retries of
for which the BS resends the DSX_RSP message to the
sending the
MS. After a DSX_RSP message has been sent for the
DSX-RSP
maximum number of times, it is not sent again.
message

Parameter ID Parameter Name
SECTORID Sector ID
VOIPENHANCE Dynamic Service Flow
Related Performance Counter

Table 11-5 describes the performance counters related to the dynamic service flow feature.
Table 11-5 Performance counters related to the dynamic service flow feature
Counter Description
The success rate of UL delete

dynamic traffic flow by MS See MS-Initiated UL DSD Success Rate.
The success rate of DL delete See MS-Initiated DL DSD Success Rate.

dynamic traffic flow by MS
The success times of UL DSD by See Times of Successful MS-Initiated UL DSD.

MS
The success times of DL DSD by See Times of Successful MS-Initiated DL DSD.

MS
The times of uplink Dynamic See Number of MS-Initiated UL DSD Failures due to
Service Deletion (DSD) failures Invalid DSD-REQ.
due to illegal DSD-REQ by MS

DBS3900 WiMAX
Counter Description
The times of uplink Dynamic See Number of MS-Initiated UL DSD Failures due to
Service Deletion (DSD) failures GW Response Timeout or Deletion Prohibition.
due to GW response timeout or
forbid to delete by MS
The times of downlink Dynamic See Number of MS-Initiated DL DSD Failures due to
Service Deletion (DSD) failures Invalid DSD-REQ.
due to illegal DSD-REQ by MS
The times of downlink Dynamic See Number of MS-Initiated DL DSD Failures due to
Service Deletion (DSD) failures GW Response Timeout or Deletion Prohibition.
due to GW response timeout or
forbidding to be deleted by MS
The times of Uplink Dynamic See Times of MS-Initiated UL DSD.

Service Deletion (DSD) attempts
by MS
The times of Downlink Dynamic See Times of MS-Initiated DL DSD.

Service Deletion (DSD) attempts
by MS
The success ratio of UL DSA by MS See MS-Initiated UL DSA Success Rate.
The success ratio of DL DSA by MS See MS-Initiated DL DSA Success Rate.
The success times of UL DSA by See Times of Successful MS-Initiated UL DSA.

MS
The success times of DL DSA by See Times of Successful MS-Initiated DL DSA.

MS
The times of uplink Dynamic See Number of MS-Initiated UL DSA Failures due to
Service Add (DSA) failures due to Invalid DSA-REQ.
illegal DSA-REQ in setup Dynamic
Service by MS
The times of downlink Dynamic See Number of in MS-Initiated DL DSA Failures due
Service Add (DSA) failures due to to Invalid DSA-REQ.
illegal DSA-REQ in setup Dynamic
Service by MS
The times of Uplink Dynamic See Times of MS-Initiated UL DSA.

Service Add (DSA) attempts by MS
The times of Downlink Dynamic See Times of MS-Initiated DL DSA.

Service Add (DSA) attempts by MS
11.6 Reference Information of Dynamic Service Flow

The dynamic service flow feature complies with IEEE 802.16-2004/Cor2/D3 with latest SRD
and WiMAX Forum Network Architecture Release 1.2.0.

DBS3900 WiMAX

DBS3900 WiMAX
Feature Configuration Guide 12 Load Balancing
12 Load Balancing
About This Chapter
During network entry and service implementation, the BS balances the load of carriers to
minimize congestion on sector carriers. This chapter describes the basic concepts, functions, and
implementation of the load balancing feature.
12.1 Overview of Load Balancing

This section describes the definition, purpose, specifications, and impact of the load balancing
feature.
12.2 Availability of Load Balancing
This section describes the network elements (NEs) involved in the load balancing feature, and
the license and version information of the load balancing feature.
12.3 Description of Load Balancing
When carrier load is heavy, system load can be reduced through the decrease in service flow
rates and through the handovers triggered by load balancing, and thus the system can run
normally. When carrier load is light, the service flow rates increase to the QoS-required rates.
12.4 Operations Related to Load Balancing
This section describes how to activate and deactivate the load balancing feature.
12.5 Maintenance Information of Load Balancing
This section describes the parameters and performance counters related to the load balancing
feature.
12.6 Reference Information of Load Balancing
The load balancing feature complies with the IEEE 802.16-2004/Cor2/D3 with latest SRD and
WiMAX Forum Network Architecture Release 1.2.0 protocols.

DBS3900 WiMAX
12 Load Balancing Feature Configuration Guide
12.1 Overview of Load Balancing

This section describes the definition, purpose, specifications, and impact of the load balancing
feature.
Definition
Load balancing is the process of balancing the load between carriers based on carrier load. The
associated operations include admission control, service flow rate control, and load balancing
handover. After the BS is configured with FFR, inter-zone handovers are triggered if the load
of multiple zones is imbalanced.
Purpose
With the load balancing feature, the load of the carriers on the BS and the load of the zones on
the BS are balanced. In this way, efficient usage of system resources prevents a carrier from
enduring heavy load, user perception is improved, and system reliability is enhanced.
Specifications
None.
Impact
Load balancing is a load control method for the system with heavy load. When carrier load is
higher than a specified threshold, new MSs cannot enter the network through this carrier, or the
rates of some service flows are reduced and lower than the QoS-required rates.
Terms
Term Definition
MPR It refers to modulation coding efficiency, which is determined by the

transient MCS mode of an MS when load is updated.
zone A zone consists of multiple time domain resource blocks that are in the same
permutation mode (such as PUSC or PUSC with ALL). A time domain
resource block consists of multiple OFDMA symbols.

Acronym and
BS Base Station
BE Best Effort
CINR Carrier to Interference Noise Ratio

DBS3900 WiMAX
Acronym and
FFR Fractional Frequency Reuse
MPR Modulation order Product code Rate
MCS Modulation Code Scheme
OFDMA Orthogonal Frequency Division Multiple Access
PUSC Partial Usage of Sub-Channels
PUSC 1/3 Partial Usage of Sub-Channels with 1/3 SC
PUSC with All Partial Usage of Sub-Channels with all SC
SBS Serving Base Station
TBS Target Base Station
12.2 Availability of Load Balancing

This section describes the network elements (NEs) involved in the load balancing feature, and
the license and version information of the load balancing feature.
NEs Involved
The load balancing feature requires the cooperation between NEs such as the SS/MS, BS, and
ASN-GW. Table 12-1 lists the NEs involved in the load balancing feature.
Table 12-1 NEs involved in the load balancing feature

AAA DHCP
SS/MS BS ASN-GW Server Server DNS Server M2000
√ √ √ - - - √
NOTE
The ASN-GW must support the forwarding of spare capability messages so that the load of inter-
BS carriers can be shared. In this way, the handover triggered by load balancing can be
implemented between BSs.

DBS3900 WiMAX
Version Support
Table 12-2 lists the version that supports the load balancing feature.
Table 12-2 Version that supports the load balancing feature

Product Version
License Support
The handover triggered by load balancing between BSs (sector carriers) is controlled by the
handover license.
12.3 Description of Load Balancing

When carrier load is heavy, system load can be reduced through the decrease in service flow
rates and through the handovers triggered by load balancing, and thus the system can run
normally. When carrier load is light, the service flow rates increase to the QoS-required rates.
In the FFR network, the inter-zone handovers triggered by load balancing enable the load of
zones to be evenly distributed. In addition, during the inter-zone handover, an MS/SS is handed
over between PUSC 1/3 and PUSC with ALL.
12.3.1 Load Balancing Control Thresholds
associated operations are based on admission control thresholds, service flow rate control
thresholds, and load balancing handover control thresholds.
12.3.2 Load Update
Load update involves updating the load of a BS and sharing the load between BSs. Load update
on a BS is implemented for the load admission control, the service flow control, and the handover
triggered by load balancing between BSs (sector carriers) or zones. The load sharing between
BSs is implemented only for the handover triggered by load balancing between BSs (sector
carriers).
12.3.3 Load Admission Control
When the MS enters the network for the first time or re-enters the network after exiting the idle
mode, or when the MS is handed over to a neighbor cell, the BS performs load admission control.
12.3.4 Service Flow Rate Control
The service flow rate is reduced or restored according to carrier load and service flow rate control
thresholds.
12.3.5 Load Balancing Handover
The handovers triggered by load balance are classified into two types: handovers between sector
carriers and handovers between zones.

DBS3900 WiMAX
12.3.1 Load Balancing Control Thresholds

associated operations are based on admission control thresholds, service flow rate control
thresholds, and load balancing handover control thresholds.
The load at the carrier level is used to evaluate the resource requirement level of each carrier,
and is indicated by the ratio of the resources required by service flows to the resources used by
a carrier for data transmission. The resources required by service flows are evaluated according
to the QoS of each service flow and the MPR of each subscriber. The total resources are evaluated
according to the subframe ratio and system bandwidth.
Load balancing control thresholds contain the following items:
l Admission control thresholds

– NORMALADMITTHRES: load threshold for allowing new MSs to enter the network.
When the sum of the carrier load usage and the load increase amount caused by the
network entry of new MSs is higher than this threshold, new MSs fail to enter the
network for the first time.
– HOADMITTHRES: load threshold for allowing the MS to re-enter the network after
handover or exit from the idle mode. When the sum of the carrier load usage and the
load increase amount caused by the network entry of new MSs is higher than this
threshold, the MS cannot re-enter the network after handover or exit from the idle mode.
l Service flow rate control thresholds
– DECRATESTARTTHRES: load threshold for triggering rate decrease. When the
number of times for which carrier load is higher than this threshold reaches a specified
value, the rates of some service flows are reduced.
– DECRATESTOPTHRES: load threshold for stopping rate decrease, that is, threshold
of expected load after service flow rates decrease. When carrier load decreases to this
threshold, the system stops rate decrease.
– RESRATETHRES: load threshold for restoring the rate. When carrier load is lower
than this threshold, the service flow rates (that have been reduced before) are restored.
l Load balancing handover control thresholds
– HOSTARTTHRES: load threshold for triggering load balancing handovers. When
carrier load is higher than this threshold, load balancing handovers are implemented for
some MSs.
– HOOUTSTOPTHRES: load threshold for stopping load balancing handovers, that is,
threshold of expected load after load balancing handovers are implemented. When
carrier load decreases to this threshold, the system stops load balancing handovers.
The relations between load balancing control thresholds are as follows:

l HOADMITTHRES ≥ NORMALADMITTHRES
l DECRATESTARTTHRES ≥ DECRATESTOPTHRES ≥ RESRATETHRES
l HOSTARTTHRES ≥ HOOUTSTOPTHRES
12.3.2 Load Update

Load update involves updating the load of a BS and sharing the load between BSs. Load update
on a BS is implemented for the load admission control, the service flow control, and the handover
triggered by load balancing between BSs (sector carriers) or zones. The load sharing between

DBS3900 WiMAX
BSs is implemented only for the handover triggered by load balancing between BSs (sector
carriers).
l The load of a BS is updated when the load changes or the load update period arrives.
l Load is shared between BSs when the ASN-GW supports the forwarding of spare capability
messages and the spare capability switch of the BS is set to ON. Load notification between
BSs is supported. There are three modes of load notification between BSs:
– Periodical reporting: Assume that the load update period is T. A BS must report the load
of each carrier sector and each carrier to the neighbor BSs every T.
– Absolute value reporting: When the load of the TBS (the BS that receives the spare
capability message) is higher than the absolute value, the TBS reports its load actively.
– Relative value reporting: When the difference between TBS load fluctuations reaches
the relative value, the TBS reports its load actively.
The modes and parameters of the load notification between BSs are determined by
SPARECAPACITYRPTCHAR, SPARECAPACITYRPTPERIOD,
SPARECAPACITYRPTABSTHRES, and SPARECAPACITYRPTRELTHRES
contained in the spare capability request message, which is sent by the SBS (the BS sends
the spare capability request message).
– SPARECAPACITYRPTCHAR: spare capability request reporting mode. There are
three supported modes: periodical reporting, absolute value reporting, and relative value
reporting.
– SPARECAPACITYRPTPERIOD: spare capability request reporting period. In this
period, a sector carrier reports the load to the neighbor cells that request the spare
capability reporting.
– SPARECAPACITYRPTABSTHRES: absolute value threshold for the spare capability
request. When the total load of the sector carrier exceeds this threshold, the load is
reported to the neighbor cells that request the spare capability reporting.
– SPARECAPACITYRPTRELTHRES: relative value threshold for the spare capability
request. When the difference between the load changes of the sector carrier exceeds this
threshold in a measurement period, the load is reported to the neighbor cells that request
the spare capability reporting.
12.3.3 Load Admission Control

When the MS enters the network for the first time or re-enters the network after exiting the idle
mode, or when the MS is handed over to a neighbor cell, the BS performs load admission control.
If the load of the carrier through which the MS tries to enter the network is heavy and exceeds
the load admission control threshold, the BS performs different-frequency assignment to enable
the MS to enter the network through another intra-sector carrier with light load, as shown in
Figure 12-1. As a result, no MS can enter the network, and the increase in the system load can
be avoided when the system load is already heavy.

DBS3900 WiMAX
Figure 12-1 Handover between intra-sector carriers
Load admission control thresholds (NORMALADMITTHRES and HOADMITTHRES) are

available only when the MS enters the network for the first time or re-enters the network after
exiting the idle mode, or when the MS is handed over to a neighbor cell.
12.3.4 Service Flow Rate Control

The service flow rate is reduced or restored according to carrier load and service flow rate control
thresholds.
l When the load of a single carrier is higher than the value of DECRATESTARTTHRES,
the decrease in the service flow rate is triggered, and thus the rates of some service flows
are reduced until the load decreases to the value of DECRATESTOPTHRES.
l When the load of a single carrier is lower than the value of RESRATETHRES, some or
all of the service flow rates (that have been reduced before) increase to the QoS-required
rates.
The MPR, service type, and service flow QoS-required rate determine the service flow priority
for rate decrease or restoration. The following weight factors respectively determine the impacts
of the MPR, service type, and service flow QoS-required rate on service flow priority calculation.
l WEIGHTFORMPR: weight factor of the MPR during service flow priority calculation.
The value ranges from 1 to 100000.
l WEIGHTFORSFTYPE: weight factor of the service type during service flow priority
calculation. The value ranges from 1 to 100000.
l WEIGHTFORRATE: weight factor of the service flow QoS-required rate during service
flow priority calculation. The value ranges from 1 to 100000.
The recommended values of WEIGHTFORMPR, WEIGHTFORSFTYPE, and

WEIGHTFORRATE are 10000, 10000, and 1 respectively. The impacts of these settings are:
the service flows with the lowest MPR are preferential in the case of carrier overload; the non-
real-time service flows nrtPS and BE are preferential when the MPRs of service flows are the
same; the service flows with high QoS-required rates are preferential when the MPRs and types
of service flows are the same.

DBS3900 WiMAX
12.3.5 Load Balancing Handover

The handovers triggered by load balance are classified into two types: handovers between sector
carriers and handovers between zones.
Handover Between Sector Carriers

The handover between sector carriers is triggered in the following scenarios:
l When the signal quality of the MSs connected to the network deteriorates and the load of
a single carrier reaches the value of HOSTARTTHRES, the BS selects some MSs with
poor signal quality and instructs them to perform scanning. Then, the MSs are handed over
to the sector carrier with light load and good channel signal quality. In this way, the load
of the single carrier decreases.
In this scenario, the handover can be implemented between any two carriers such as intra-
sector carriers and carriers between neighbor sectors or between neighbor BSs. Figure
12-2 shows the scenario of the handover between sector carriers.
l When most of subscribers connected to the network are implementing BE services and the
number of subscribers implementing services increases gradually, handovers are triggered
if the BE satisfaction of the serving carrier is lower than the value of
BESATISFACTIONTHRESH and the number of unsatisfactory BE connections is
greater than the value of BENUMFORLOADHO. In this scenario, the handovers are
implemented only within the BS.
– BESATISFACTIONTHRESH: BE satisfaction threshold for triggering load balancing
handovers for BE subscribers. The value ranges from 0 to 100, and the unit is %.
– BENUMFORLOADHO: number of BE subscribers when load balancing handovers
can be triggered. The value ranges from 0 to 20.
NOTE
When the ASN-GW does not support the forwarding of spare capability messages, the handover between sector
carriers can be implemented only between intra-BS carriers.
Figure 12-2 Scenario of the handover between sector carriers
Figure 12-3 shows the process of the handover between sector carriers.

DBS3900 WiMAX
Figure 12-3 Process of the handover between sector carriers
1. Select MSs for the handover.

Based on the QoS-required rates and MPRs, calculate the priorities of the active MSs on
the carrier. Then, select multiple MSs with the highest priority. The total load of the MSs
is not lower than the amount by which the load of carrier should decrease.
2. Select a maximum of five target carriers for MSs to perform scanning.
l If multiple carriers function as serving carriers, other intra-sector carriers (whose
remaining resources should not be less than the resources requested for the handover)
are selected preferentially as target carriers. If less than five carriers are selected, sort
the other carriers to detect the carrier with the maximum amount of remaining resources
under the prerequisite that the remaining resources are not less than the resources
required for the handover. Then, this carrier is selected preferentially as a target carrier.
l If a single carrier functions as the serving carrier, sort the other carriers to detect the
five carriers with the maximum amount of remaining resources under the prerequisite
that the remaining resources are not less than the required resources for the handover.
Then, the carriers are selected preferentially as the target carriers.
NOTE
In addition, the BE satisfaction difference between the target carrier and the serving carrier must be
not lower than the value of BESATISFTDIFFETHRESHFORLOADHO so that load balancing
handovers can be triggered for BE subscribers.
BESATISFTDIFFETHRESHFORLOADHO: BE satisfaction difference threshold for triggering
load balancing handovers. The value ranges from 0 to 100, and the unit is %.
3. Select the target carrier for the handover, and then initiate the handover.
Based on scanning results, compare the highest downlink CINR value of the target carrier
with the CINR value of the source carrier and the scanning threshold for handovers to
determine the target carrier for the handover.
Inter-Zone Handover
After the BS is configured with FFR, inter-zone handovers are triggered if the load of multiple
zones is imbalanced. In this case, some MSs must be handed over to another zone, and thus the
load of multiple zones is distributed evenly.
In addition, during the inter-zone handover, an MS is handed over between PUSC 1/3 and PUSC
with ALL. The inter-zone handover is triggered in the following conditions:

DBS3900 WiMAX
l When the load in PUSC 1/3 is higher than 80% and the load in PUSC with ALL is lower
than 80%, the MS is handed over from PUSC 1/3 to PUSC with ALL.
l When the load in PUSC with ALL is higher than 90% and the load in PUSC 1/3 is lower
than 70%, the MS is handed over from PUSC with ALL to PUSC 1/3.
12.4 Operations Related to Load Balancing

This section describes how to activate and deactivate the load balancing feature.
12.4.1 Activating the Load Balancing Feature

On the M2000 or the Web LMT, you can perform related configurations on the BS to activate
the load balancing feature.
12.4.2 Deactivating the Load Balancing Feature
On the M2000 or the Web LMT, you can perform related configurations to deactivate the load
balancing feature.
12.4.1 Activating the Load Balancing Feature

On the M2000 or the Web LMT, you can perform related configurations on the BS to activate
the load balancing feature.
Procedure
1. Run the LST CARRIERLICENSEINFO command to query the information of the license
of a carrier.
Example:
2. Run the MOD CARRIERLICENSEINFO command to set the handover control item of
the carrier.
Example:
MOD CARRIERLICENSEINFO: SECTORID=0, CARRIERID=0, MOBILITY=ON;
NOTE
To implement the handover triggered by load balancing between BSs (sector carriers), ensure that the
handover control item in the license is enabled.
Step 2 Run the MOD CARRIERBLOCKFLAG command to deactivate a carrier.

Example:
MOD CARRIERBLOCKFLAG: SECTORID=0, CARRIERID=0, BLOCKFLAG=BLOCKED;
Step 3 Run the MOD RRMSWITCH command to set the load balancing handover switch, rate control
switch, and spare capability switch to on.
Example:
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, LOADHOSWITCH=ON, SFRATECTRLSWITCH=ON,
SPARECAPSWITCH=ON;

DBS3900 WiMAX
NOTE
The following switches are optional:

l Load balancing handover switch: set to on when the handover triggered by load balancing between BSs
(sector carriers) is required.
l Rate control switch: set to on when service flow rate control is required.
l Spare capability switch: set to on when the handover between BSs must be supported.
l Inter-zone handover switch: set to on when the handover between zones must be supported.
Step 4 Run the MOD CARRIERBLOCKFLAG command to activate a carrier.

Example:
MOD CARRIERBLOCKFLAG: SECTORID=0, CARRIERID=0, BLOCKFLAG=UNBLOCKED;
Step 5 Run the MOD LOADCTRLPARA command to change the values of load control parameters.
Example:
MOD LOADCTRLPARA: SECTORID=0, CARRIERID=0, DECRATEPERMITFLAG=0,
WEIGHTFORMPR=10000, WEIGHTFORSFTYPE=10000, WEIGHTFORRATE=1, NORMALADMITTHRES=85,
HOADMITTHRES=90, HOSTARTTHRES=90, HOOUTSTOPTHRES=83, DECRATESTARTTHRES=95,
DECRATESTOPTHRES=88, RESRATETHRES=85, BESATISFACTIONTHRESH=80, BENUMFORLOADHO=5,
BESATISFTDIFFETHRESHFORLOADHO=10;
----End
12.4.2 Deactivating the Load Balancing Feature

On the M2000 or the Web LMT, you can perform related configurations to deactivate the load
balancing feature.
Procedure
Step 1 Run the MOD CARRIERBLOCKFLAG command to deactivate carriers.
Example:
Step 2 Run the MOD RRMSWITCH command to set the load balancing handover switch, rate control
switch, and spare capability switch to OFF.
Example:
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, LOADHOSWITCH=OFF, SFRATECTRLSWITCH=OFF,
SPARECAPSWITCH=OFF;
Step 3 Run the MOD CARRIERBLOCKFLAG command to activate carriers.

Example:
MOD CARRIERBLOCKFLAG: SECTORID=0, CARRIERID=0, BLOCKFLAG=UNBLOCKED;
----End
12.5 Maintenance Information of Load Balancing

This section describes the parameters and performance counters related to the load balancing
feature.
Parameters
Table 12-3, Table 12-4, and Table 12-5 list the parameters related to the load balancing feature.

DBS3900 WiMAX
Table 12-3 Parameters related to the MOD CARRIERBLOCKFLAG command

ID Name
SECTORID Sector ID
BLOCKFLAG Block Flag

ID Name
SECTORID Sector ID
ZONEHOSWITCH Switch of Zone Handover
LOADHOSWITCH Switch of Load Balancing Handover
SFRATECTRLSWITCH Switch of QoS Rate Control
SPARECAPSWITCH Switch of Spare Capacity Report
Table 12-5 Parameters related to the MOD LOADCTRLPARA command

ID Name
SECTORID Sector ID
DECRATEPERMITFLAG Decreasing Rate Flag of Service Flow
WEIGHTFORMPR Weight of MCS for Calculating Priority
WEIGHTFORSFTYPE Weight of Scheduling Type for Calculating Priority
WEIGHTFORRATE Weight of QoS Rate for Calculating Priority
SPARECAPACITYRPTPERIOD Period of Reporting Spare Capacity
SPARECAPACITYRPTCHAR Character of Reporting Spare Capacity
SPARECAPACITYRP- Absolute Threshold of Reporting Spare Capacity

TABSTHRES
SPARECAPACITYRP- Relative Threshold of Reporting Spare Capacity

TRELTHRES
NORMALADMITTHRES Admitting Threshold of New User
HOADMITTHRES Admitting Threshold of Idle and Handover User

DBS3900 WiMAX
ID Name
HOSTARTTHRES Load Threshold of Starting Load Balancing Handover
HOOUTSTOPTHRES Load Threshold of Stopping Load Balancing

Handover
DECRATESTARTTHRES Load Threshold of Starting Decreasing Rate
DECRATESTOPTHRES Load Threshold of Stopping Decreasing Rate
RESRATETHRES Load Threshold of Resuming Rate
BESATISFACTIONTHRESH Threshold of BE Satisfaction
BENUMFORLOADHO BE User Numbers Caused Load Handover
BESATISFTDIFFETHRESHFOR- Threshold of Different of BE Satisfaction Caused

LOADHO Load Handover
Table 12-6 lists the performance counters related to the load balancing feature.
Table 12-6 Performance counters related to the load balancing feature
Counter Description
The times of handoff triggered by uplink load See Number of Handovers Triggered by
equalization UL Load Balancing.
The times of handoff triggered by downlink load See Number of Handovers Triggered by
equalization DL Load Balancing.
The times of uplink sector overload See Times of UL Sector Overload.
The times of downlink sector overload See Times of DL Sector Overload.
Success Count from PUSC 1/3 to PUSC with All See Number of Successful Handovers
in Carrier Load from PUSC Partial to PUSC with All in
Carrier Load.
Success Count from PUSC with All to PUSC 1/3 See Number of Successful Handovers
in Carrier Load from PUSC with All to PUSC Partial in
Carrier Load.
Failure Count from PUSC 1/3 to PUSC with All See Number of Handover Failures from
in Carrier Load PUSC Partial to PUSC with All in Carrier
Load.
Failure Count from PUSC with All to PUSC 1/3 See Number of Handover Failures from
in Carrier Load PUSC with All to PUSC Partial in Carrier
Load.

DBS3900 WiMAX
12.6 Reference Information of Load Balancing

The load balancing feature complies with the IEEE 802.16-2004/Cor2/D3 with latest SRD and
WiMAX Forum Network Architecture Release 1.2.0 protocols.


A Textbook of Electrical Technology Volume I Basic Electrical Engineering B L Theraja

Uploaded by

Copyright:

Available Formats

You might also like

A Textbook of Electrical Technology Volume I Basic Electrical Engineering B L Theraja

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

A Textbook of Electrical Technology Volume I Basic Electrical Engineering B L Theraja

Uploaded by

Copyright:

Available Formats

DBS3900 WiMAX

Feature Configuration Guide

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

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

Trademarks and Permissions

Huawei Proprietary and Confidential

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

3 Power Control and AMC..........................................................................................................3-1

Issue 03 (2010-03-19) Huawei Proprietary and Confidential i

3.4.1 Activating the Power Control and AMC Feature...................................................................................3-7

ii Huawei Proprietary and Confidential Issue 03 (2010-03-19)

7 Security Mechanism ................................................................................................................. 7-1

10 Network Discovery & Selection/Re-Selection..................................................................10-1

Issue 03 (2010-03-19) Huawei Proprietary and Confidential iii

10.2 Availability of ND&S.................................................................................................................................10-3

11 Dynamic Service Flow...........................................................................................................11-1

iv Huawei Proprietary and Confidential Issue 03 (2010-03-19)

Figure 1-1 SAW hybrid ARQ solution.................................................................................................................1-5

Issue 03 (2010-03-19) Huawei Proprietary and Confidential v

Figure 10-1 Process for implementing ND&S...................................................................................................10-4

vi Huawei Proprietary and Confidential Issue 03 (2010-03-19)

Table 1-1 NEs involved in the HARQ feature.....................................................................................................1-4

Issue 03 (2010-03-19) Huawei Proprietary and Confidential vii

Table 6-3 Parameters related to the ADD NBR command.................................................................................6-17

viii Huawei Proprietary and Confidential Issue 03 (2010-03-19)

Table 12-1 NEs involved in the load balancing feature.....................................................................................12-3

Issue 03 (2010-03-19) Huawei Proprietary and Confidential ix

About This Document

Product Name Product Version

DBS3900 WiMAX V300R002C03

03 (2010-03-19) This is the third commercial release.

Issue 03 (2010-03-19) Huawei Proprietary and Confidential 1

Version Change History

02 (2010-01-10) This is the second commercial release.

01 (2009-10-25) This is the first commercial release.

2 Huawei Proprietary and Confidential Issue 03 (2010-03-19)

10 Network Discovery & Selection/Re-Selection

11 Dynamic Service Flow

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Issue 03 (2010-03-19) Huawei Proprietary and Confidential 3

Indicates a potentially hazardous situation, which if not

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

Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

4 Huawei Proprietary and Confidential Issue 03 (2010-03-19)

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"