sjzl20091238-ZXMBW AGW (V3 (1) .08.10) Configuration Guide PDF

ZXMBW AGW
WiMAX Wireless Access Gateway

Configuration Guide
Version 3.08.10
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2006 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason

R1.0 03/30/2009 First Edition
R1.1 05/10/2009 Update
Serial Number: sjzl20091238

Contents
Preface............................................................... i
AGW Data Configuration Introduction ...............1
Network Planning ........................................................... 1
AGW Data Configuration Flow........................................... 4
AGW Data Configuration Modes ........................................ 6
AGW Physical Data Configuration .................... 11
Creating AGW Exchanges................................................11
AGW Hardware Data Configuration...................................17
Introduction to Hardware Data Configuration.................17
Configuring a Rack.....................................................21
Configuring a Shelf ....................................................23
Configuring a Unit......................................................29
Configuring a Module .................................................35
AGW IP Protocol Stack Configuration .............. 45
Introduction to IP Protocol Stack Configuration ..................45
Configuring Physical Interface .........................................46
Configuring Logical Interface...........................................51
Loading AGW Version Files .............................. 59
Flow of Loading Version Files...........................................60
Loading OMP Version Files ..............................................61
Configuring Version Files Path .....................................61
Creating OMP Ini File .................................................65
Configuring OMP Board Booting Parameters ..................66
Loading Version Files..................................................76
AGW Local Office Data Configuration............... 79
Activating License..........................................................79
Configuring AGW Exchanges Capacity...............................81
Configuring AGW Exchanges Attributes .............................84
AGW Load Sharing Configuration..................... 87
Introduction to Load Sharing Configuration .......................87
Configuring SMP Control Interface Load Sharing ................90
Configuring GGUP Media Interface Load Sharing ................93
AGW Service Data Configuration ..................... 97
Configuring IP Address ...................................................97
Configuring IP Address Under DHCP Relay Mode ............97
Configuring IP Address Under DHCP Proxy Mode ............99
Configuring Profile ....................................................... 102
Configuring DHCP Relay Profile .................................. 102
Configuring Radius Profile ......................................... 104
Configuring DHCP Proxy Profile.................................. 106
Configuring FA ............................................................ 108
Configuring NSP .......................................................... 110
Configuring Charging Data ............................................ 113
Configuring Charging Template .................................. 113
Configuring Payment Mode ....................................... 115
Configuring Service Flow .............................................. 117
AGW Data Synchronization Configura-
tion ............................................................... 125
Introduction to Data Synchronization Configuration .......... 125
Synchronizing All Tables ............................................... 125
Synchronizing Changed Tables....................................... 127
AGW Service Function Configuration
Instances ...................................................... 131
MIP Access Function Configuration ................................. 131
Introduction to MIP Access Function Configuration ......... 131
Configuring MIP Access Function................................ 134
Simple IP Access Function Configuration ......................... 140
Introduction to Simple IP Access Function
Configuration .................................................. 140
Configuring Simple IP Access Function Under DHCP
Proxy Mode..................................................... 141
Configuring Simple IP Access Function Under DHCP
Relay Mode ..................................................... 155
Charging Function Configuration .................................... 163
Introduction to Accounting Function Configura-
tion ............................................................... 163
Configuring Offline Charging Function......................... 164
Configuring Online Charging Function ......................... 167
Handover Function Configuration ................................... 171
Introduction to Handover Function Configuration.......... 171
Configuring Handover Function .................................. 172
Paging Function Configuration ....................................... 176
Introduction to Paging Function Configuration.............. 176
Configuring Paging Function ...................................... 178
Figures .......................................................... 185
Tables ........................................................... 191
List of Glossary.............................................. 195
Preface
Purpose This manual provides procedures and guidelines for configuring

Operation and Maintenance Center (OMC) in ZXMBW AGW WiMAX
Wireless Access Gateway.
Intended This manual is intended for engineers and technicians who perform
Audience configuration activities through ZXMBW AGW WiMAX OMC.
Prerequisite Skill To use this manual effectively, users should have a general under-
and Knowledge standing of wireless telecommunications technology. Familiarity
with the following is helpful:
� The ZXMBW AGW WiMAX system and its components
� Local operations
What Is in This This manual contains the following chapters:
Manual
Chapter Summary
Chapter 1, AGW Data This chapter introduces the network planning,

Configuration Introduc- configuration flow and configuration method
tion for AGW data configuration.
This chapter introduces how to configure

AGW physical data, including creating ex-
Chapter 2, AGW Physi-
changes, configuring a rack, configuring a
cal Data Configuration
shelf, configuring a unit and configuring a
module.
Chapter 3, Loading This chapter introduces how to load AGW ver-

AGW Version Files sion files.
Chapter 4, AGW Local This chapter introduces how to configure

Office Data Configura- AGW local office data, including activating
tion Licence, configuring office capacity.
This chapter introduces how to configure

Chapter 5, AGW Load AGW load sharing, including configuring
Sharing Configuration control interface load sharing and media
interface load sharing.
Chapter 6, AGW Service This chapter introduces AGW service data

Data Configuration configuration.
This chapter introduces AGW IP protocol

Chapter 7, AGW IP Pro-
stack configuration, including configuring R3
tocol Stack Configura-
and R6 interface and the IP address of each
tion
interface.
Chapter 8, AGW Data

This chapter introduces AGW data synchroni-
Synchronization Con-
zation configuration.
figuration
Chapter 9, AGW Serv-

This chapter introduces AGW service function
ice Function Configura-
configuration instances.
tion Instances
Confidential and Proprietary Information of ZTE CORPORATION i

ZXMBW AGW Configuration Guide
This page is intentionally blank.
ii Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
AGW Data Configuration

Introduction
Table of Contents
Network Planning ............................................................... 1
AGW Data Configuration Flow............................................... 4
AGW Data Configuration Modes ............................................ 6
Network Planning
Description When configuring AGW system, IP addresses related to other NEs
of WiMAX system are involved. So the network planning and IP
addresses allocation of the whole WiMAX system should be com-
pleted before configuring AGW.
Schematic Network planning schematic diagram of WiMAX system is as shown
Diagram of in Figure 1.
Network Planning
Confidential and Proprietary Information of ZTE CORPORATION 1

FIGURE 1 NETWORK PLANNING SCHEMATIC DIAGRAM OF WIMAX SYSTEM
Network Address Network address planning of WiMAX system is as shown in Figure

Planning 2 and Table 1.
FIGURE 2 INTERFACES AND ADDRESSES CONFIGURED BY EXCHANGES
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 AGW Data Configuration Introduction
Parameters in Figure 2 are introduced as follows:

� Interfaces and addresses need to configure are divided into:
i. 192.168.*.* OMC related addresses
ii. 20.*.*.* R3, R6 interface physical addresses
iii. 1.3.*.* R3, R6 media interface and signaling interface addresses
� Other items need to configure are as follows:
� R3 media interface/signaling interface address1.3.25.161
� R6 media interface address 1.3.25.160
� R6 signaling interface address1.3.25.159
TABLE 1 WIMAX SYSTEM NETWORK ADDRESS PLANNING INTRODUCTION
Interface IP Address Connected

NE Interface Introduction
Name (Example) Device
It is the physical inter-

face, used for commu-
nication with AGW R6
GGLP board of interface address, which
BSC IPCF Address 20.1.25.1
AGW should be in the same
network segment with
the configured R6 inter-
face address.
It is the physical inter-

face, which should be in
R6 Interface
20.1.25.100 IPCF of BSC the same network seg-
Address
ment with the configured
IPCF address of BSC.
R6 Interface
Signaling In- It is the logical
1.3.25.159
terface Ad- interface
dress
R6 Interface
It is the logical
Media Inter- 1.3.25.160
interface
face Address
AGW R3 interface does not dif-

R3 Interface
ferentiate signaling inter-
Media/Signal- It is the logical
1.3.25.161 face from media inter-
ing interface interface
face, and only configures
Address
a logical address
Used for communication

with AAA, and it should
R3 Interface
20.2.25.100 AAA be in the same network
Address
segment with the config-
ured AAA address

with HA, and it should be
R3 Interface
20.3.25.100 HA in the same network seg-
Address
ment with the configured
HA address

Interface IP Address Connected

NE Interface Introduction
Name (Example) Device

with DHCP, and it
R3 Interface should be in the same
20.4.25.100 DHCP
Address network segment with
the configured DHCP
address
IP Address of X means the exchanges

129.0.31.X AGW OMC server
OMC2 Port number
Cluster Serv-
AAA Server 20.2.25.1 AGW R3 interface
ice Address
DHCP Server 20.4.25.1 AGW R3 interface
HA 20.3.25.18 AGW R3 interface
DBIO/ZTE
192.168.52.134
Gateway
192.168.51.253 AGW OMC server

Alarm Box
192.168.51.254 AAA OMC server
Interface with
192.168.51.129
AGW OMC client
OMC Server AGW
Interface with
129.0.31.129
OMP board

Flow
Description Certain sequence should be obeyed when configuring AGW office
data.

Data Configura- AGW data configuration flow is as shown in Figure 3.

tion Flow
FIGURE 3 AGW DATA CONFIGURATION FLOW
1. Creating Exchanges
Creating exchanges is to create a management object with
AGW NE as the unit.
Exchange is the basic management unit of network manage-
ment system, and a set of AGW device is a exchange. A switch
should be created before configuring other data. Confirm ex-
change number and exchange type when creating it, and they
can not be modified once configured. Please pay attention to
exchange during creation.
2. Configuring Hardware Data
Physical configuration includes creating the rack, the shelf, the
module and unit of the board, its purpose is to manage all hard-
ware resources by background network management system
under a exchange.
3. Configuring IP Protocol Stack
Configuring IP protocol stack includes defining all physical in-
terfaces and logical interfaces involved in AGW system, config-
uring IP address and routing information for every interface. It
is used to transmit the signaling of signaling interface and the
data of media interface for R3 interface, R6 interface and AGW.
4. Loading Version Files

The version files are not loaded after installing hardware for
physical boards. Load the software of corresponding version
manually.
5. Configuring Local Office Data
It includes activating License and defining AGW service pro-
cessing capability.
6. Configuring Load Sharing
When multi SMP and GGUP boards are configured in AGW ex-
change, in order to optimize the capability of the board for
processing signaling interface data and media interface data
maximally, it requires to configure load sharing of SMP for pro-
cessing signaling interface data and GGUP for processing media
interface data.
7. Configuring AGW Service Data
Configuring AGW service data to support Simple IP and MIP
accessing function, and accomplish handover, paging, pre-pay
and post-pay function.
It includes configuring IP address, Profile, HA, NSP and ac-
counting data.
8. Configuring Data Synchronization
Data synchronization is to synchronize the data configured by
AGW background to foreground OMP.

Modes
Description OMC server of AGW provides two kinds to data configuration
modes, which are shown as follows.
� Command Line Configuration Mode
It means to input command lines in MML terminal interface to
accomplish data configuration.
� Interface Parameter Configuration Mode
It means to configure parameters in MML terminal interface to
accomplish data configuration.
First enter command terminal interface before configuring data.
Click Views > MML Terminal in ZTE OMC, MML Terminal main
window appears. The left pane of the window is navigation tree,
and the right pane is attributes window, as shown in Figure 4.

FIGURE 4 MML TERMINAL
The node root on upper left pane stands for network management
server node, and it is the actual root node. The node under root
node means subnetwork, it is created when creating the first ex-
change, and there should be only one subnetwork under network
management server node. Other exchanges are created under it,
no more other subnetworks are generated.
Introduction Inputting command lines is realized in command inputbox on lower
for Inputting right pane. Figure 5 is the example for inputting command ADD
Command Lines NE:ID=5,TYPE=AGW,STATE=0,NAME=AGW-5;.

FIGURE 5 ADD NE
Introduction Besides configuring data by inputting command lines, the same

for Inputting operations can be done by inputting parameters in textbox, as
Parameters in shown in Figure 6.
Textbox

FIGURE 6 INPUTTING PARAMETERS IN TEXTBOX
Introduction The operation procedures introduced here are command lines. Af-
for Command ter inputting commands in command inputbox, press F5 key or
Execution click Execute (F5) button to execute them.
After executing the commands, the execution results or informa-
tion read by the commands are displayed in Command Execute
Result field, as shown in Figure 7.

FIGURE 7 ADD NE COMMAND EXECUTE RESULT

Chapter 2
AGW Physical Data

Configuration
Table of Contents
Creating AGW Exchanges ...................................................11
AGW Hardware Data Configuration.......................................17
Creating AGW Exchanges

Prerequisites � Foreground and background are connecting normally.
� OMC server and client are connecting normally.
� Foreground devices are operating normally.
� OMC server is running normally.
� Oracle database is working normally.
Context This topic introduces the detailed procedures for creating AGW ex-
changes.
Under initial status, there is no exchange information in network
management system, and creating exchanges is the first step for
configuring exchange data.
Steps 1. Click Start > Programs > ZXMBW-AGW (OMM) > Run
Client, then OMC client starts automatically, and interface as
shown in Figure 8 appears.

FIGURE 8 USER LOGIN INTERFACE
Parameters in Figure 8 are explained in Table 2.
TABLE 2 PARAMETERS IN LOGIN INTERFACE
Parameter Explanation Example
It is admin as
User Name User name for user login
default
Corresponding password for the It is empty as

Password
user name default
Server Address OMC server address 192.168.51.129
2. According to the network planning in Table 1, input the server

IP address to be connected, user name, and password, and
then click OK button to login ZTE OMC, as shown in Figure 9.

Chapter 2 AGW Physical Data Configuration
FIGURE 9 AGW OMC INTERFACE
3. Click Views > MML Terminal , interface as shown in Figure

10 appears.

FIGURE 10 MML TERMINAL
4. Click System Maintenance > Network Element Manage-

ment > Create Network Elements (ADD NE) in MML Com-
mand from MML-Tree, as shown in Figure 11.

FIGURE 11 ADD NE COMMAND PARAMETERS CONFIGURATION
TABLE 3 ADD NE COMMAND PARAMETERS CONFIGURATION EXPLANATION
Parameter Explanation Configuration Introduction Example
It is the ID of the exchanges.

It is mandatory.
NE ID It is the unique ID for 5
Value range: Integer of 1~255
a exchange.
It means the NE types

that the exchange to be
It is mandatory.
Exchange created can manage.
Select AGW from the AGW
Type Currently only AGW type
pull-down list.
NE can be managed by
AGW exchanges.
It is optional.
Vendor It means vendor name. Value range: Character string
no more than 50 characters
It is optional.
User-defined It means the self-defined
State user state. Value range: Integer of
0~65535

It is optional.
It means the self-defined
Position Value range: Character string
user position.
It is optional.
It means the self-defined
User Label Value range: Character string AGW-5
user label.
5. Input parameters as per the examples in Table 3.

6. Press F5 key or click Execute (F5) button to execute the com-
mands.
END OF STEPS
Result If the command is executed successfully, then AGW NE with ex-

change number being 5 is created, and following information ap-
pears, as shown in Figure 12.
FIGURE 12 ADD AGW-5 EXCHANGE SUCCESSFULLY

AGW Hardware Data

Configuration
Introduction to Hardware Data
Configuration
Description This topic introduces AGW physical data configuration process, in-
cluding configuring a rack, a shelf, a module and a unit.
Physical configuration should be completed once a exchange is cre-
ated, and physical configuration is the basis for configuring other
data of AGW system.
Configuring physical data is to define physical hardware informa-
tion and other data information closely related to hardware, in-
cluding defining the rack, the shelf and the resources boards. It
can add, delete and query the physical resources and logical re-
sources (such as adding or deleting the module, the rack, the shelf
and the board) inside the configured exchange.
AGW Boards Type Hardware of AGW system is composed of the boards of following
types.
� SMP (Signaling Main Processor Board)
SMP is in charge of processing all application layer signaling
and routing protocol, and carries out Socket transmission and
receiving, signaling coding and decoding, flow control, media
interface control and user management.
� OMP (Operation & Maintenance Processing Board)
OMP is system master control node, including OMP and RPU
two modules.
� OMP provides external OMC interface.
� RPU accomplishes routing information maintenance, rout-
ing table generation and distribution and dynamic routing
protocol processing on system network processing unit.
� UIM (Universal Interface Module)
UIM is in charge of inner message transmission to realize sig-
naling interface Ethernet switching and media interface level 2
Ethernet switching.
� GGLP (Line Processor of GE interface)
GGLP mainly realizes data linear velocity processing, including
data packet identification, classification and distribution, en-
capsulation, decapsulation, table look-up and route forward-
ing.
� GGUP (GTP-U Processor)
GGUP realizes the functions like basic IP packet header, GRE
message processing, message filter, user data message for-
warding, accounting collection and reporting.
� PSN (Packet Switch Network Board)

PSN realizes media interface IP data message switching in level

1 switching.
AGW Shelf For AGW system, single-shelf or multi-shelf should be decided ac-
Configuration cording to traffic.
� For single-shelf configuration, back plane adopts BPSNE.
Single-shelf configuration for boards in level 1 switching sub-
rack is as shown in Figure 13.
FIGURE 13 STANDARD CONFIGURATION FOR AGW SINGLE-SHELF (BPSNE)
� For multi-shelf configuration, the back plane adopts BPSNE +

BCTC (Backplane of ConTrol Center).
Dual-shelf configuration of AGW is shown in Figure 14 and Fig-
ure 15.
FIGURE 14 TYPICAL CONFIGURATION FOR AGW DUAL-SHELF (BCTC)

FIGURE 15 TYPICAL CONFIGURATION FOR AGW DUAL-SHELF (BPSNE)
Introduction The function and configuration of every board is listed in Table 4

to Board and Table 5. Here it is the recommended value in this manual,
Configuration of the hardware configuration in actual situation is configured as per
AGW Network items specified in business contract.
TABLE 4 AGW FRONT BOARD CONFIGURATION
Redun-
Logical
Name dancy Quantity Function Remarks
Board
Mode
Single-shelf network:
boards can be
Line 2 (Single- Provide external Giga- inserted in slot 1~6
Pro- shelf) bit Ethernet interface, in BPSNE shelf
Load
GGLP cessor and each GGLP board
Sharing 4 (Dual- Dual-shelf network:
of GE in- provides 4 GE (Gigabit
terface shelf) Ethernet) interfaces Boards can be
inserted in slot 1~6
in BPSNE shelf
boards can be
N+M 2 (Single-
GTP-U in BPSNE shelf
Backup shelf) Provide user data pro-
GGUP Pro- Dual-shelf network:
(Cold 8 (Dual- cessing for AGW
cessor Boards can be
standby) shelf)
and slot 9–14 in
BPSNE shelf
2 (Single- Switch network board

Packet shelf) for level switching, Fixed to be inserted
Load
PSN Switch realizes media inter- in slot 7 and slot 8 in
Sharing 8 (Dual-
Network face IP switch in level 1 BPSNE shelf
shelf) switching

Redun-
Logical
Name dancy Quantity Function Remarks
Board
Mode
boards can be
Opera- inserted in slot
Realize operation and
tion & 2 (Single- 11 and slot 12 in
maintenance function,
Mainte- shelf) BPSNE shelf
1+1 and accomplish IP pro-
OMP nance
Backup 2 (Dual- tocol stack configura- Dual-shelf network:
Pro-
shelf) tion and dynamic route Boards can be
cessing
protocol processing inserted in slot
Board
11 and slot 12 in
BCTC shelf
boards can be
inserted in slot 9,
Signal- 2 (Single- slot 10, slot 13 and
1+1 Realize the processing
ing Main shelf) slot 14 in BPSNE shelf
Backup for all signaling of AGW,
SMP Pro-
(Hot 10 (Dual- and support board ex- Dual-shelf network:
cessing
standby) shelf) pansion Boards can be
Board
inserted in slot 1~8,
slot 13, and slot 14
in BCTC shelf
boards can be
inserted in slot
15 and slot 16 in
Univer- 2 (Single-
Realize boards inter- BPSNE shelf
sal In- 1+1 shelf)
UIM connection in the shelf Dual-shelf network:
terface Backup 4 (Dual- (signaling and media) Boards can be
Module shelf)
inserted in slot 9,
slot 10 in BCTC shelf
and slot 15 and slot
16 in BPSNE shelf
Note:
Theoretically, GGLP and GGUP can be mixed inserted in slot 1~6,
but for the sequence of installation, it is better to inert by certain
order. Usually GGLP board is inserted on left, and GGUP is inserted
on right.
TABLE 5 AGW SINGLE-SHELF REAR BOARD CONFIGURATION
Logical
Quantity Function Remarks
Board
Realize that GGLP provide ex-

ternal debugging interface
RGEP_4/RGE IF GGLP board with copper Usually it is not required to config-
1
P_2 ,Please use RGEP_4, if GGLP ure
board with fiber, Please
use RGEP_2

Logical
Quantity Function Remarks
Board
Realize that PSN provides ex- Usually it is not required to config-

RPSN 1
ternal debugging interface ure
Realize that UIM provides ex-

RUIM2 1 Can only be inserted in slot 15
ternal interface
Realize that UIM provides ex-

RUIM3 1 Can only be inserted in slot 16
ternal interface
Realize that OMP provides ex- Can be inserted in slot 11 and slot
RMPB 2
ternal interface 12
Configuring a Rack
Prerequisites � OMC server and client are connecting normally.
� AGW exchanges has been created.
Context Configuring a rack means to add a logical rack corresponding to
the foreground in physical configuration of OMC client.
A exchange can configure one or more racks, and standard con-
figuration configures only one rack.
Since OMP board must be configured in shelf 2 or rack 1, if the ex-
change adopts standard configuration (configuring only one rack),
then the rack must be configured as rack 1.
In practical configuration, after adding exchange (AGW NE) suc-
cessfully, system adds a rack numbered as 1 automatically.
Steps 1. Click AGW Command > System Management > Device
Management > Rack Management > Create Rack (ADD
RACK) in MML Command from MML-Tree, and interface as

FIGURE 16 ADD RACK COMMAND PARAMETERS CONFIGURATION
TABLE 6 ADD RACK COMMAND PARAMETERS CONFIGURATION EXPLANATION
Name Explanation Configuration Introduction Example
It is mandatory
Rack It is the rack Value range: Integer of 1~15
1
No. number Rack number is configured by
DIP switch on the back plane
It is optional
It is the user de- Value range: character
Alias
fined rack name string with no more than
50 characters
2. Configure parameters according to examples in Table 6.

3. Press F5 key or click Execute (F5) button to execute com-
mands.
END OF STEPS
Result For single-shelf configuration, system prompts that the rack No.
to be added already exists, as shown in Figure 17.

FIGURE 17 RACK CONFIGURATION PROMPT FOR SINGLE-SHELF CONFIGURATION
Configuring a Shelf
Prerequisites � OMC client and server are connecting normally.
� AGW exchange has been created.
� The rack has been configured under corresponding exchange.
Context This topic introduces the procedure to add a logical shelf corre-
sponding to the foreground in physical configuration of OMC client.
When AGW adopts standard configuration (Single-shelf configura-
tion), pay attention to the following items.
� Shelf type should select BPSNE shelf (Packet Switch Shelf).
� Since OMP board must be configured on shelf 2 of rack 1, if the
exchange adopts standard configuration (configures only one
rack), then firstly create shelf numbered as 2.
Steps 1. Click AGW Command > System Management > Device
Management > Shelf Management > Create Shelf (ADD
SHELF) in MML Command from MML-Tree, and interface as

FIGURE 18 ADD SHELF PARAMETERS CONFIGURATION
TABLE 7 ADD SHELF COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Param-
Explanation Configuration Introduction Example
eter
It is mandatory, and configured by

Rack No. It is the rack number DIP switch on back plane 1
Value range: integer of 1~15
It is mandatory, and configured by

Shelf No. It is the shelf number DIP switch on back plane 2
Value range: integer of 1~4
It is mandatory, and select from the

pull-down list, including four options:
Means the corresponding
type of the configured shelf � BCTC. control shelf
Shelf If the exchange is � BUSN, common shelf

single-shelf, then this BPSNE
Type � BPSNE, level 1 IP switch shelf
parameter must be
configured as BPSNE � BGSN, Gigabit command shelf
(Level 1 IP switch shelf)
Configure the shelf type as per board
type in corresponding slot

Param-
eter
Whether it is center BPSNE

It is configured when the
exchange is multi-shelf
configuration, the details
are listed as follows:
� If it is dual-shelf inter- It is optional, and select from pull-down
connection, then con- list, including the following options:
Center
BPSNE figure both as center � NO (Not Center BPSNE)
BPSNE
� YES (Center BPSNE)
� If it is multi-shelf inter-
connection, only one
center BPSNE is re-
quired to configure,
and others are inter-
connected with it
It is optional, and select form

the pull-down list, including the
Shelf Ver- Means the version of the following options:
sion shelf � BGSN080600
� BGSN060801
It is optional
Means user defined shelf
Alias Value range: character string with
name
2. Configure parameters as per the examples in Table 7.

mands.
END OF STEPS
Result If commands are executed successfully, an interface indicating

successful configuration appears.
Postrequisite Click AGW Command > System Management > Device Man-
agement > Module Management > Show Module (SHOW
MODULE) in MML Command from MML-Tree, and the OMP
numbered as 1 and RPU numbered as 2 have been created
successfully, as shown in Figure 19.

FIGURE 19 OMP MODULE AND RPU MODULE CREATING SUCCESSFULLY
After shelf 2 of rack 1 has been created, OMP board is generated

automatically (OMP module and RPU module on OMP board are
also generated), and it can be queried in rackchart management
window. Click Views > Daily Maintenance > AGW > Rackchart
Management, then OMP board is displayed on corresponding slot,
as shown in Figure 20.

FIGURE 20 OMP BOARD CREATED SUCCESSFULLY
Right-click OMP board icon in Figure 20, click Board Config Info...
from the prompted shortcut options, then select Module No. as 1
in Please select Module No. interface, then interface as shown
in Figure 21 appears, and attribute of Module 1 is OMP.

FIGURE 21 QUERY ATTRIBUTE OF MODULE 1
Select Module No. as 2 in Please select Module No. interface,

the interface as shown in Figure 22 appears, and attribute of mod-
ule 2 is RPU.

FIGURE 22 QUERY ATTRIBUTE OF MODULE 2
Configuring a Unit
� The rack and shelf under corresponding exchange have been
configured.
Context This topic introduces the procedure to configure a unit of AGW
system.
Configuring a unit is to configure the logical boards corresponding
to a slot.
The units need to configure in AGW system include UIM, PSN, GGLP
and GGUP. The configuration for each unit should be made under
the OMP module, which means the homing module for each unit
is OMP module.
When creating a unit, UIM unit must be created firstly before cre-
ating PSN unit, and other units can be created ant any sequence.

Corresponding module and unit is generated automatically after a

board is created, no need to create manually. All sub-units sup-
ported by each board is generated too, and it can be quoted di-
rectly during subsequent data configuration.
Steps 1. Add UIM unit. Click AGW Command > System Management
> Device Management > Unit Management > Create Unit
(ADD UNIT) in MML Command from MML—Tree, as shown
in Figure 23.
FIGURE 23 ADD UNIT COMMAND PARAMETERS CONFIGURATION
TABLE 8 ADD UNIT COMMAND PARAMETERS CONFIGURATION EXPLANATION
Configuration
Introduction
Mandatory
Parameters configuration
format is rack-shelf-slot,
and rack is in the range
Physical location of config- of 1~15, shelf is in the
Unit Location ured UIM unit in AGW sys- range of 1~4 and slot is in 1-2-15
tem the range of 1~17.
For the detailed information
for physical location of
every board, please refer
to Table 9.

Configuration
Introduction
Mandatory
Homing Module No. of the Input the homing OMP
Module No. 1
unit module number of this unit
The default value is 1
Optional
Unit No. Corresponding Unit No. 15
Value Range: 1~200
Mandatory
Mother board type corre- For the mother board UIM
Unit Type type corresponded to
sponded to the unit (UIM2_GCS_755)
every board, please refer
to Table 9.
Mandatory
Select backup mode
according to unit type
Select from the pull-down
list, including:
� NO (No backup)
� ONEPLUSONE (1+1
backup)
Backup mode used by � LOADSHARE (Load shar- ONEPLUSONE
Backup Mode
every unit ing backup) (1+1 backup)
� BACKTOBACK (Back-to-
back backup)
� NPLUSONE (N+1
backup)
� ONETOONE (1:1
backup)
For the details, please
refer to Table 9.
When Backup Mode is set

to be any one except NO,
Backup Unit slot used for backup unit 16
this parameter must be con-
figured
UIM Attribute UIM Attribute Optional, use default value
SDTB Attrib-
SDTB Attribute Optional, use default value
ute
APBE/IMA At-
APBE/IMA Attribute Optional, use default value
tribute
T1/E1 Attrib- T1/E1 Attribute

Optional, use default value
ute Use default value
Clock Base Clock Base Optional, use default value

Configuration
Introduction
Optional, select from

pull-down list, including
two options:
� COM (Common board)
� CTL (Control transmit
board)
Control Attrib-
Control Transmit board When the newly added unit
ute
is GGLP, this parameter
must be configured as
CTL (Control transmit
board), otherwise it can
not receive and transmit
control interface signaling
messages.
Channel Configuration
Channel Mode Optional, use default value
Mode
SGBP Attrib-
SGBP Attribute Optional, use default value
ute
Optional
When the board is UIM
UIM Clock De- board, this parameter must
Clock Detection Parameter be configured as NO (UIM
tection
NOT-CLKdetect), and
it may be unconfigured
for other boards.
Fiber Multi-
Fiber Multiplexed Struc-
plexed Struc- Optional, use default value
ture
ture
T network attribute of the

TNET Attribute Optional, use default value
UIM unit
TDM Bus Type TDM Bus Type Optional, use default value
E3/T3 Attrib-
E3/T3 Attribute Optional, use default value
ute
Data Mode Data Mode Optional, use default value
Optional
User self-defined logical Value range: Character
Alias
board name strings with not more than
50 characters.
Corresponding board type and backup modes are explained in

Table 9.

TABLE 9 CORRESPONDING BOARD TYPE AND BACKUP MODE PARAMETERS CONFIGURATION

INTRODUCTION
Name Corresponding Slot Board Type Backup Mode
ONEPLUSONE
UIM Slot 15 and 16 UIM (UIM2_GCS_755)
(1+1 backup)
LOADSHARE (Load
PSN Slot 7 and 8 PSN4V
sharing backup)
Slot 1, 2, 3, 4, 5 and 6 (usually

GGLP GGLP (XPB_GGLP) No (No backup)
slot 1 and 2)
Slot 1, 2, 3, 4, 5 and 6 (usually

GGUP GGUP (XPB_GGUP) No (No backup)
slot 4and 5)
Caution:
� When configuring backup mode for GGUP board, usually it
is set to be NO (No backup). But in practical situation, GGUP
board provides N+M cold backup mode. N stands for ac-
tive board number, and M stands for standby board num-
ber. GGUP boards compete for logical board number after
powering on, those get logical board number obtain basic
resources and work normally, those not get logical board
number work as standby board. When one active board is
faulty, system control select one from standby board au-
tomatically and take over the faulty one. The take-over is
carried out through logical board number to ensure logical
board is still available.
� PSN board is used for level 1 switch of GGLP and GGUP.
When configuring PSN board, no matter whether there is
actual standby board for it or not, the standby board must
be configured. When adding the first PSN unit, set Backup
Unit as the unit number of another PSN, then network
management completes the configuration of the two PSN
units.
2. Input parameters according to the examples in Table 8.

mands.
4. Execute the above-mentioned steps to add all boards.
END OF STEPS
Result After adding a unit, query the configured boards through click-
ing Views > Daily Maintenance > Rackchart Management,
as shown in Figure 24.

FIGURE 24 ALL BOARDS ARE CREATED SUCCESSFULLY
Postrequisite After boards are added, modify the attribute of GE interface of

subunits.
Note:
Modify the attribute of GE interface of subunits only fit for GGLP
board with fiber, If GGLP Board with copper as actual situation ,
then no need to modify.
� For newly added GGLP board, port operation mode for subunits
is copper, modify it to fiber manually.
GGLP provides 4 external GE interfaces, corresponding to sub-
units 9~12. Change the operation mode of subunit 9~12 of
GGLP board to be fiber.
� Modify the GE Hypotaxis of subunit 9~12 of GGLP board to be
invalid.
Operation procedures are introduced as follows.
1. Modify attributes of subunit of GGLP board. Click AGW Com-
mand > System Management > Device Management >

Sub-Unit Management > Modify Sunit (SET SUNIT) in

MML Command from MML-Tree, as shown in Figure 25.
FIGURE 25 SET SUNIT COMMAND PARAMETERS CONFIGURATION

mands.
Configuring a Module
� Rack and shelf has been configured under corresponding ex-
change.
Context This topic introduces the procedure to configure a module.
Physical boards in AGW NEs include GGLP, GGUP, OMP, SMP, UIM
and PSN. All boards are divided into modules and units according
to their function.
GGLP, GGUP, UIM and PSN are defined as unit, while OMP and SMP
are defined as module (RPU module is on OMP board).
In actual network, exchange can plan how to configure a module
according to user capacity.

� If the capacity is small, then configure only OMP module and

RPU module, without SMP module. Now OMP module provides
SMP module function. OMP and RPU module are created au-
tomatically when creating BPSNE type shelf (They are on OMP
board, and module 1 is OMP module, and module 2 is RPU
module).
Operations under this situation are as follows.
i. Add SMP module attributes in OMP module.
ii. Configure board IP address of OMP module and OMC net-
work management server IP address.
� If the capacity is large, then three types of module should be
created: OMP, RPU and SMP.
OMP and RPU module is automatically created when creating
BPSNE type shelf (They are on OMP board, module 1 is OMP
module and module 2 is RPU module), and SMP module should
be created.
Operations under this situation are as follows.
i. Add SMP module attributes in OMP module (Now this opera-
tion is used to enable OMP module with signaling function).
ii. Configure the board IP address of OMP module and OMC
network management server IP address.
iii. Add SMP module.
Note:
Creating SMP module should be after creating UIM unit,
otherwise it can not be created successfully.
Steps 1. Configure attributes of OMP module. Click AGW Command

> System Management > Device Management > Mod-
ule Management > Modify Module (SET MODULE) in MML
Command from MML-Tree, as shown in Figure 26.
Caution:
After modify the attributes of OMP module of AGW to be
omp&smp, reset OMP board after creating OMP ini files. It is
because that ini files includes OMP module attributes, the
foreground starts related processes according to it.

FIGURE 26 SET MODULE PARAMETERS CONFIGURATION
TABLE 10 SET MODULE COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory
Module No. range is 1~127
Module Unique module No.
OMP module number is fixed to be 1, RPU 1
No. in the exchange
module number is fixed to be 2, and other
added module number begins from 3.
Mandatory
� When AGW configures OMP module and SMP
module at the same time, in order to ena-
ble OMP module with signaling capability, this
parameter is recommended to configure as
Module omp&smp.
Module attributes omp&smp
Type
� When AGW system uses single OMP module,
module 1 should accomplish the function of
OMP and SMP. Now SMP module attributes
should be added to module 1, which means
this parameter must configured as omp&smp.

Optional
Select from the pull-down list, including:
CPU Corresponding � If board type is common X86, then select X86 X86
Type mother board type (X86 CPU)
� If board type is X86_2, then select CEN-
TRINO (CENTRINO CPU)
CMP
Mod- CMP module pro- Optional
ule Ca- cessing capability Value range: Integer in the range of 1~100
pacity
Optional
User self-defined
Alias Value range: Character string with not
module name
more than 50 characters
2. Input parameters according to examples in Table 10.

mands. if command execution is successful, then following
information appears, as shown in Figure 27.
FIGURE 27 MODIFY OMP ATTRIBUTES SUCCESSFULLY
4. Configure IP address for OMP board to connect to OMC server.

Click AGW Command > System Management > Local
Office Management > Local Office Global Data Manage-

ment > Set Global Data OMP Configuration (SET OMP)

in MML Command from MML-Treeas shown in Figure 28.
FIGURE 28 SET OMP COMMAND PARAMETERS CONFIGURATION
TABLE 11 SET OMP COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory, input IP address complies

IP address for fore- with IPV4 address format
OMP Back-
ground OMP board For example, the format is
ground IP 172.18.5.1
connects to back- 172.18.5.office number, and the
Address
ground OMC server last digit is the office number of
this AGW exchange
Subnet mask of the

OMP Back- IP address for fore-
Mandatory, input IP address complies
ground IP ground OMP board 255.255.255.0
with IPV4 address format
Mask connects to back-
ground OMC server
Gateway of the IP Mandatory, input IP address complies

address for fore- with IPV4 address format
OMP to OMC
ground OMP board If gateway is not configured, then it 172.18.5.129
Gateway
connects to back- can be configured as the IP address
ground OMC server of OMC server.
OMC Server
IP address of OMC Mandatory, input IP address complies
SUBNET 172.18.5.129
server with IPV4 address formant
Address


mands. If commands are executed successfully, then following
FIGURE 29 CONFIGURE OMP ATTRIBUTES SUCCESSFULLY
7. Create and configure SMP module. Click AGW Command >

System Management > Device Management > Module
Management > Create Module (ADD MODULE) in MML

FIGURE 30 ADD MP PARAMETERS CONFIGURATION (ADD SMP MODULE)
TABLE 12 ADD MP COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Parame-
ter
Physical board Mandatory

location informa-
Location tion of this SMP The format is rack-shelf-slot, rack value 1-2-13
module in the range is 1~15, shelf value range is 1~4,
system slot value range is 1~17.
Mandatory
corresponding Module number range is 3~127
Module No. of
SMP module Since OMP module number is fixed to be
Module No. 1, RPU module number is fixed to be 2, 3&4
It is the unified then SMP module number should start
module number from 3. There are two CPUs of SMP board,
in the exchange corresponding to 3 and 4, and they can be
added at the same time in this command.
Mandatory
Module 1 Module 1 type on
This parameter must select SMP when SMP
Type this board
creating SMP module
Optional
Module 2 Module 2 type on
If only configure a CPU on the board, this SMP
Type this board
parameter may be unconfigured

Parame-
ter
Optional
Mother board Select from the pull-down list
type correspond- � If board type is X86, then this parame-
CPU Type X86
ing to this mod- ter select X86
ule
� If board type is X86_2, then this param-
eter select CENTRINOCENTRINO CPU
Optional
Select from pull-down list
Backup Backup mode for � Option NO means no backup ONEPLUSONE
Mode this module � Option ONEPLUSONE means 1+1 (1+1 Backup)
backup. if it is selected, then SMP
board is automatically added on backup
slot.
Optional
Module 1 User self-defined
User Alias module 1 name Value range: Character string with not
Optional
Module 2 User self-defined
User Alias module 2 name Value range: Character strings with not

mands. If the commands are successfully executed, then fol-
lowing information appears, as shown in Figure 31.

FIGURE 31 ADD SMP MODULE SUCCESSFULLY
END OF STEPS
Result Configuring a module is successfully complete.


Chapter 3
AGW IP Protocol Stack

Configuration
Table of Contents
Introduction to IP Protocol Stack Configuration ......................45
Configuring Physical Interface .............................................46
Configuring Logical Interface...............................................51
Introduction to IP Protocol
Stack Configuration
Description This topic introduces the IP protocol stack configuration for AGW
system, including the physical address and logical address for the
interfaces of AGW NE, which is used to realize the signaling inter-
face and media interface messages forwarding between R3 inter-
face, R6 interface and inner AGW.
Interface Type of There are two kinds of interface types for AGW system.
AGW System
� Physical Interface
Physical interface is also called real interface, the main external
interfaces for AGW NE include R6 interface and R3 interface.
� R6 interface is the interface between BSC (Base Station
Controller) and AGW, belongs to internal interface of WiMAX
system access service network ASN.
� R3 interface is the interface between AGW and AAA, HA and
DHCP, belongs to the interface between WiMAX system ac-
cess service network ASN and connectivity service network
CSN.
� Logical Interface
Logical interface is the address used for signaling interface
and media interface messages forwarding between modules
in AGW system, including R6 signaling interface, R6 media in-
terface, R3 signaling interface and R3 media interface.
� R6 Signaling interface
A unique R6 interface signaling address is configured for a
AGW exchange.

BSC carries out signaling interaction with AGW through this

address, realize the connection of R6 signaling interface
information flow.
� R6 Media Interface
GGUP board is used to receive and process user media in-
terface data distributed by GGLP board, and AGW config-
ures a R6 media interface address for each active GGUP
(It may also configure all R6 media interface address on all
active GGUP board as a same address).
� R3 Signaling Interface
AGW assigns a R3 signaling interface address for each
GGUP board individually ( Each R3 signaling interface
address on GGUP board can be the same as R6 signaling
interface address on the board, but the R3 signaling inter-
face address on each GGUP board can not be the same).
� R3 Media Interface
Media interface address of R3 interface is used for CoA
address of MIP function (message forwarding address for
AGW and HA), AGW assigns a individual R3 media interface
address for each GGUP board, and the R3 media interface
address should not be the same on each GGUP board.
Note:
Strictly, R3 interface does not differentiate media interface and
signaling interface messages, so the media interface address
and signaling interface address for R3 interface usually are set
to be the same.
Interface Board The interface board type for AGW system is GGLP, and provides 4
Type of AGW external GE interfaces.
System
Configuring Physical
Interface
� Physical data configuration has been completed.
Context This topic introduces the procedure to configure the real interfaces
and their addresses involved in AGW system.
According to the introduction in Table 1 and Figure 2, the real in-
terfaces required to configure are listed as follows.
1. Configure the R6 real interface used for communication be-
tween AGW and BS.

Chapter 3 AGW IP Protocol Stack Configuration

tween AGW and HA.
tween AGW and AAA.
4. Configure R3 real interface used for communication between
AGW and DHCP.
Steps 1. Configure the R6 real interface for communication between
AGW and BS. Click AGW Command > IP Stack Configu-
ration > Interface Commands > Interface Management
> Enter Interface Mode (INTERFACE) in MML Command
from MML-Tree, as shown in Figure 32.
FIGURE 32 INTERFACE COMMAND PARAMETERS CONFIGURATION
TABLE 13 INTERFACE COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory
The default value is 1
It means subsystem
Sub-System Value range: integer in the range of 0
number
1~255
It is usually the default value
It means the homing Mandatory

OMP module number for
Default value is 1
Module the GGLP board where 1
the physical interface Value range: integer in the range of
belongs 1~65535

It means the unit Mandatory

number of GGLP board
Value range: integer in the range of
where the interface
Unit 1~65535 1
belongs, that is the slot
number of the board on Input the slot number of GGLP
the rack according to the actual situation.
Means the subunit

number of the GGLP Mandatory
Sub-Unit 1
board where the The value is fixed to be 1
interface belongs
Means the physical port Mandatory

number of the interface
Port There are four GE interfaces on GGLP 1
board where the physical
interface belongs board, and value range is 1~4

This command means to enter the port numbered as
0–1–1–1–1, which means to set R6 real interface to the first
GE interface on the GGLP board with slot number as 1.
mands, and the interface as shown in Figure 33 appears.
FIGURE 33 ENTER INTERFACE MODE

Caution:
MML commands under interface mode are different from the
MML commands under normal mode.
4. Confirm the current port number under interface mode. Click

AGW Command > IP Stack Configuration > Show Cur-
rent Mode (SHOW MODE) in MML Command from the MML-
Tree, make sure that it enters configured port 0–1–1–1–1, as
shown in Figure 34.
FIGURE 34 QUERY PORT UNDER CURRENT MODE
5. Configure IP address for R6 physical interface. Click AGW

Command > IP stack Configuration > Interface Com-
mands > Interface Management > Create IP Address
Of Interface (ADD IP ADDRESS) in MML Command from
MML-Tree, as shown in Figure 35.

FIGURE 35 ADD IP ADDRESS COMMAND PARAMETERS CONFIGURATION
TABLE 14 ADD IP ADDRESS COMMAND PARAMETERS CONFIGURATION INTRODUCTION

(CONFIGURING R6 INTERFACE ADDRESS OF AGW WITH BS SIDE)
Configuration
Introduction
Mandatory, input IP address

complies with IPV4 format
It means the IP address of
IP Refer to the planning 20.1.25.100
this interface
introduction in Network
Planning.
It means the subnet mask Mandatory

Subnet Mask of the IP address of this Input IP address complies 255.255.255.0
interface with IPV4 format
Mandatory
Broadcast Ad- It means the broadcast ad-
Input IP address complies 255.255.255.255
dress dress of this interface
with IPV4 format
Optional
CORBA ID It means CORBA ID Input integer in the range
of 1~65535.

mands.
8. After command is executed, R6 interface physical address is
configured successfully. Click AGW Command > IP Stack

Configuration > Exit Mode (EXIT) in MML Command from

MML-Tree.
mands and exit interface mode.
10. After address is configured, save online configuration data.
Click AGW Command > IP Stack Configuration > IP Stack
Tools > Save Online Configuration Data (SAVE ONLINE-
DATA) in MML Command from MML-tree, as shown in Figure
36.
FIGURE 36 SAVE ONLINEDATA COMMAND
END OF STEPS
Result Configuring physical interface is successfully complete.

Postrequisite Configure other physical interfaces according to above-mentioned
steps. Address planning of the interface can refer to the planning
introduction in Table 1.
� R3 interface address between AGW and AAA server.
� R3 interface between AGW and HA.
� R3 interface between AGW and DHCP server.
Configuring Logical Interface



Context This topic introduces the procedure to configure the logical inter-
faces and their addresses involved in AGW system, and add these
interfaces to physical interfaces.
Logical interfaces address are the addresses used for signaling
interface and media interface messages forwarding between the
modules inside AGW. After configure logical interface addresses,
usually add them to physical interfaces, so as to enable these ad-
dresses to forward messages between modules inside AGW sys-
tem.
According to the introduction in Table 1 and Figure 2, the config-
ured logical interfaces are listed as follows.
� R6 signaling interface address.
� R6 media interface address.
� R3 media/ signaling interface address.
Note:
Since media interface address and signaling interface address of
R3 interface can be the same, these two addresses are not differ-
entiated in the subsequent steps, and is described as R3 interface
address hereafter.
Steps 1. Configure R6 signaling interface address. Click AGW Com-

mand > System Management > Local Office Manage-
ment > Signaling Plane Parameter Management > R6
Signaling IP Address Management > Set R6 Signaling
IP Address in MML Command from MML-Tree, as shown in
Figure 37.
FIGURE 37 SET SIGIP R6 COMMAND PARAMETERS CONFIGURATION
Parameter in Figure 37 is explained in Table 15.

TABLE 15 SET SIGIP R6 COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Means R6 signaling IP
R6 Signaling Mandatory, refer to the planning
address, it is unique for 1.3.25.159
IP Address in Table 1.
a AGW exchange.

mands.
4. Assign R6 media interface address and R3 interface address
for GGUP logical board.
i. Click AGW Command > System Management > Ca-
pacity management > User Plane Load Sharing >
Logical UP Management > Create Logical UP Board
(ADDLOGICUP) in MML Command from MML-Tree, as
shown in Figure 38.
FIGURE 38 ADD LOGICUP COMMAND PARAMETERS CONFIGURATION
TABLE 16 ADD LOGICUP COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory
Logical It means logical board num-
Input integer in the range 1
Board No. ber of GGUP board
of 1~255

Means R6 media interface

IP address assigned for
each GGUP board, and it
Media R6 complies with IPV4 format
is logical address. 1.3.25.160
Address Refer to the planning introduction
The R6 media interface
in Network Planning.
address for each GGUP
logical board can be the same

Means R3 signaling interface complies with IPV4 format
R3 Address 1.3.25.161
and media interface address Refer to the planning introduction
in Network Planning
ii. Input parameters according to the examples in Table 16.

iii. Press F5 key or click Execute(F5) button to execute the
commands.
5. Add logical addresses into physical addresses.
i. Enter Interface Mode. Click AGW Command > IP Stack
Configuration > Interface Commands > Interface
Management > Create (Enter) Loopback Interface
(INTERFACE LOOPBACK) in MML Command from
FIGURE 39 INTERFACE LOOPBACK COMMAND PARAMETERS CONFIGURATION
Parameter in Figure 39 is explained in Table 17.

TABLE 17 INTERFACE LOOPBACK COMMAND PARAMETERS CONFIGURATION INTRODUCTION (R3

MEDIA INTERFACE ADDRESS)
Param-
eter
Port of the phys- Mandatory

Port 1
ical interface Input integer in the range of 1~128.

iii. Press F5 key or click Execute (F5) button to execute com-
mands, and interface as shown in Figure 40 appears.
FIGURE 40 ENTER INTERFACE CONFIGURATION MODE
iv. Add R3 address into physical address. Click AGW

Command > IP Stack Configuration > Interface
Commands > Interface Management > Create IP
Address Of Interface (ADD IP ADDRESS) in MML

FIGURE 41 ADD IP ADDRESS COMMAND PARAMETERS CONFIGURATION
TABLE 18 ADD IP ADDRESS COMMAND PARAMETERS CONFIGURATION INTRODUCTION

(CONFIGURING R3 INTERFACE
Configuration
Introduction
Mandatory
Input IP address complies
Means the IP address of the with IPV4 format
IP 1.3.25.161
interface Refer to the planning
Planning.
Mandatory
Means subnet mask of the
Subnet Mask Input IP address complies 255.255.255.255
IP address for this interface
with IPV4 format
Mandatory
Broadcast Ad- Means the broadcast ad-
dress dress for the interface
with IPV4 format
Optional
CORBA ID Means CORBA ID Input integer in the range
of 1~65535
v. Input parameters according to the examples in Table 18.

vi. Press F5 key or click Execute (F5) button to execute com-
mands.

6. Repeat the abovementioned steps to add R6 media interface

address and signaling interface address to physical address.
7. The commands are executed. Click AGW Command > IP
Stack Configuration > Exit Mode (EXIT) in MML Com-
mand from MML-Tree.
8. Press F5 button or click Execute (F5) button to execute com-
mands and exit interface mode.
END OF STEPS
Result Configuring logical interface is successfully complete.


Chapter 4
Loading AGW Version

Files
Table of Contents
Flow of Loading Version Files...............................................60
Loading OMP Version Files ..................................................61

Flow of Loading Version

Files
Operation Flow for The operation flow for loading version files is as listed in Figure 42.
loading Version
Files FIGURE 42 LOADING VERSION FILES OPERATION FLOW
Initializing OMP Configure OMP starting parameters on serial port is to configure

Board some parameters communicated to OMC server when OMP board
starts.
Configuring Configuring version files path is to confirm the version and saving
Version Files Path path for the version files to be loaded.
Creating OMP Ini Creating OMP ini files means to generate a boot file named om-
Files pcfgX.ini on OMC server (X is the corresponding exchange num-
ber, and the file is saved under zxwomc\ums-svr directory of the
server, and OMP FTP this file to local disk).
Loading Version Board operation requires the support of software. Different func-
Files tions can be realized if different software is loaded on the same
physical board. Initially there is no version files on physical boards,
which requires to add manually.

Chapter 4 Loading AGW Version Files
Loading OMP Version Files

Configuring Version Files Path
� Version files are ready.
� Physical configuration and capacity planning configuration
have been completed.
Context The function of configuring version files path is to confirm the path
of the version files to be loaded, so as to map the version files to
version base on OMC server. In version software pack, there are
at least two directories of target_hardware and zxver\front.
� Under target_hardware path, public version files are stored
(Like DSP, FPGA).
� Under zxver\front path, specific service version files are stored
(Stored by NE).
Steps 1. Click Views > Professional Maintenance in OMC main in-
terface, and enter Professional Maintenance interface.
2. Select the exchange to load the version files from the navi-
gation tree on the left pane, click Version Management >
Version Maintenance, and enter Version Maintenance in-
terface, as shown in Figure 43.

FIGURE 43 VERSION MAINTENANCE MAIN INTERFACE
Introduction to the icons in Version Maintenance interface is

explained in Table 19.
TABLE 19 VERSION MAINTENANCE ICONS INTRODUCTION
Icon Introduction
Config Version Path
Load Assigned Version
Optimize Version Files
Synchronize Version Files
Automatic Load Version
Refresh
Close All
Select the version files
Select all version files

Icon Introduction
� Unselected, means use client version base.

� Selected, means to display the versions uploaded to server, which
means no need to configure version files root path on the client.
Import
3. Click Config Version Path button in Version Maintenance

interface, enter Config Version Path interface, as shown in
Figure 44.
FIGURE 44 CONFIG VERSION PATH INTERFACE
4. Right-click the list in Config Version Path interface, and then

click the Create menu. Add a new blank item in Config Ver-
sion Path interface, as shown in Figure 45.

FIGURE 45 CREATE VERSION AND VERSION PATH
5. In Config Version Path interface, double-click Version on

the blank item, input version to be loaded, and make sure it is
the same as the version of version files.
6. In Config Version Path interface, double-click File Path on
the blank item, button appears.
7. Click button, Open interface appears. Select the path for
version files. Click Open button, then version files display on
File Path bar.
8. After setting the path, the path comes into effect only af-
ter saving. In Config Version Path interface, right-click any
item, select the shortcut menu Save. After saving success-
fully, Save Success interface prompts, and click OK button.

Note:
After add, delete or modify version files path, the configura-
tions come into effect only after saving them.
END OF STEPS
Result Configuring version file path is successfully complete.
Creating OMP Ini File

� Version files path has been configured.
Context Creating OMP ini file is to generate a ini file named ompcfgX.ini
(X is the corresponding exchange number) on OMC server.
The configuration file includes the CPU and FPGA version file name
for OMP module normal operation, when configuring OMP through
serial port, this file name should be set. OMP board can obtain
configuration file from OMC server by FTP when starting, and find
the necessary CPU and FPGA version file for starting.
User originates creating OMP ini file operation from client, and
after the operation is successful, system saves OMP version tar-
get on OMC server database, and save the generated configura-
tion file with OMP information under FTP path of OMC server(\zx-
womcs\ums-svr).
Steps 1. In OMC main interface, click Views > Professional Mainte-
nance, and enter Professional Maintenance interface.
2. Select the exchange to load version files, and click Version
Management > Version Maintenance, then Version Main-
tenance interface appears, as shown in Figure 44.
3. In version pull-down list, select the versions to be loaded. In
Version Maintenance interface, all version files correspond-
ing to this version under the root path are displayed.
4. In Version Maintenance interface, press CTRL key and click
the mouse to select the CPU file and FPGA file necessary for
OMP, then right-click the selected version files, click Create
OMP Ini File from prompted shortcut menu.
5. System starts to create OMP ini file, and an information box
appears once it is created successfully.
END OF STEPS

Result Creating OMP ini file is successfully complete.
Configuring OMP Board Booting

Parameters
� Serial port cable are ready.
� Hyper Terminal on debugging computer has been installed.
Context OMP board obtains version files and FPGA (Field Programmable
Gate Array) file from OMC server by FTP for the initial starting.
Configuring OMP booting parameters is to configure some param-
eters used for communication with OMC server through serial port
when OMP board starts, so as to ensure OMP board can commu-
nicate with background OMC server normally.
Starting parameters to be configured includes the following con-
tents:
� IP address and MAC address of OMP board.
� IP address of OMC server.
� Exchange number.
� FTP user name and password.
� OMP board starting mode.
When configuring starting parameters, usually connect debugging
serial port of OMP board (DEBUG-232 port on the lowest part
of rear board RMPB of OMP board) and serial port of debugging
computer (COM port on the PC) through debugging 232 cable
(H-232-006).
After configuring, OMP board should be reset, and it obtains ver-
sion files from OMC server by FTP according to configured starting
parameters, and waits for OMC to transmit data to it.
Steps 1. Connect debugging serial port of OMP (DEBUG2-232 port on
RMPB board) to serial of debugging computer.
2. Click Start > Programs > Accessories > Communications
> Hyper Terminal menu in debugging computer, and enter
Connection Description interface, as shown in Figure 46.

FIGURE 46 HYPER TERMINAL STARTING INTERFACE
3. In Name box, input name for the new connection, and select
icon for it. Click OK button, enter Connect To interface, as
shown in Figure 47.
FIGURE 47 PORT SELECT
4. In Connect using pull-down list, select the serial port con-

nected to the foreground (Here it is COM1 port). click OK but-
ton, enter COM1 Properties interface, as shown in Figure 48.

FIGURE 48 COM1 PROPERTIES CONFIGURATION
5. Click Restore Defaults button, and click OK button, enter

communication connecting status, and reset OMP board.
6. When the prompt Press any key to stop auto-boot as shown
in Figure 49 appears, press any key in 3 seconds to stop OMP
board automatic starting and begin to configure OMP starting
parameters.

FIGURE 49 STOP OMP AUTO STARTING
7. Input password 3glpat as per the prompt, press Enter key,

enter BootMode Selection interface, as shown in Figure 50.
FIGURE 50 BOOTMODE SELECTION

8. Input 1 as the prompt, press Enter key, and enter Config Se-
lection interface, as shown in Figure 51.
FIGURE 51 CONFIG SELECTION
9. Input 1 as per the prompt, select Set Omp or Cmp ’s Omc

Ip.Mac.Gateway and OMC Server IP, and press Enter key,
enter Omp’s Omc Ip Address interface, as shown in Figure 52.
FIGURE 52 ENTER OMP’S OMC IP ADDRESS

10. Input the planned IP address of OMP board 129.0.31.5, and

5 is the office direction number. Press Enter key, enter OMP’s
OMC Mac address interface, as shown in Figure 53.
FIGURE 53 ENTER OMP’S OMC MAC ADDRESS
11. Input the OMP planned MAC address 00.208.208.161.00.X

(X is exchange number), press Enter key, enter OMP’s Gate-
way Ip address interface, as shown in Figure 54.

FIGURE 54 ENTER OMP’S GATEWAY IP ADDRESS
12. Input OMP’s Gateway IP address, press Enter key. If gateway

is not configured, then press Enter to skip this configuration,
and enter Config Selection interface, as shown in Figure 55.
FIGURE 55 CONFIG SELECTION INTERFACE
13. Input 2 as the prompt, press Enter key, and enter OMC Ip
address interface, as shown in Figure 56.

FIGURE 56 OMC IP ADDRESS
14. Input OMC IP address 172.18.5.129, and 5 is the office direc-

tion number, press Enter key, enter FTP user name configura-
tion interface, as shown in Figure 57.
FIGURE 57 FTP CONFIG
15. Input default FTP user name uep, press Enter key, then input
default FTP password uep, and press Enter key, enter FTP path
configuration interface, as shown in Figure 58.

FIGURE 58 OMPCFG FILE NAME
16. Input ini file name ompcfgX.ini (X is the office direction num-
ber) and press Enter key, then input 3 as per the prompt, press
Enter again, enter Set Omp Boot Type interface, as shown in
Figure 59.
FIGURE 59 SET OMP BOOT TYPE INTERFACE

17. Input 0 as per the prompt, press Enter key, and press 4 ac-
cording to the prompt, then press Enter key again, enter Bu-
reau No configuration interface, as shown in Figure 60.
FIGURE 60 SET BUREAU NO.
18. Input office direction number 5, press Enter key, then input 5
according to the prompt, and press Enter key again, return to
BOOT configuration main menu, and enter 3GPlat Boot config-
uration interface, as shown in Figure 61.
FIGURE 61 3GPLAT BOOT

19. Input 0 as per the prompt, press Enter key, and reset OMP
board, then OMP serial port configuration for the new BOOT
version is completed.
END OF STEPS
Result Successfully initialize OMP board, and OMP board downloads ver-
sion file and FPGA file from OMC server after resetting.
Tip:
After OMP starts normally, “RUN” indicator corresponded to OMP
board should flash slowly.
Loading Version Files

� Version file path has been configured.
Context Loading the versions means to load the version files necessary for
foreground board normal operation to foreground OMP board.
Physical board operation requires software support. different func-
tions can be achieved if different operation software is loaded on
the same physical boards. Initially there is no version files for
physical boards, and it should be loaded manually.
When loading version files, the version files of OMP module is
obtained directly from OMC server by FTP, and version files of
other boards (including RPU module) are obtained from OMP when
boards are reset, so the procedures of loading version files are di-
vided into the following steps.
1. Upload
Upload the version files necessary for boards to OMC server
version base from configured version file path.
2. Add to the Foreground
Add the version files in OMC server version base into fore-
ground OMP board.
Since the version files of OMP board is downloaded from bak-
ground OMC server by FTP after OMP board resetting, and it
is not required to add into OMP board. While the version files
for other boards are downloaded from OMP board by FTP, and
they are required to add to the foreground.

3. Activating the Version

Including multicast version files and modify database. Whether
activation is successful or not depends on whether database
operation is successful or not. Multicast may fail because
some boards are not there or are powering on during multicast
process. After boards are reset, it downloads version files
according to OMP database information.
4. Loading Versions for the Boards
When board is reset, it compares whether the existing version
file is consistent with that on OMP board. If inconsistent, then
download new version files from OMP, otherwise use version
files of this board directly.
The version files for the each board are as listed in Table 20. Board
type and FPGA version are configured as per actual situation, it is
only an example here in this manual.
TABLE 20 AGW FOREGROUND VERSION SOFTWARE LIST
Module Foreground Version File Remarks
GGSN_MPX86_MP_X86_ZXMBW-AGW_Z_T.BIN
MP x86 CPU type is X86
MPX86_05_040202_FPGA_105.RBF
GGSN_MPX86_2_MP_P4_ZXMBW-AGW_Z_T.BIN
CPU type is P4 Cen-
MPx86_2
trino
MPX862_04_040704_FPGA_107.RBF
RPUx86 GGSN_MPX86_RPU_X86_ZXMBW-AGW_Z_T.BIN CPU type is X86
CPU type is P4 Cen-

RPUx86_2 GGSN_MPX86_2_RPU_P4_ZXMBW-AGW_Z_T.BIN
trino
GGSN_PSN_PSN_852_ZXMBW-AGW_Z_T.BIN
PSN PSN version file
GGSN_PSN_PSN_860_ZXMBW-AGW_Z_T.BIN
GGSN_CHUB_CHUB_8245_ZXMBW-AGW_Z_T.BIN
CHUB CHUB version file
GGSN_CHUB_CHUB_8260_ZXMBW-AGW_Z_T.BIN
GGSN_XPB_GGLP_XLR_1_ZXMBW-
AGW_VXWORKS_T.BIN
GGLP GGSN_XPB_GGLP_XLR_2_ZXMBW- GGLP version file

AGW_VXWORKS_T.BIN
GGSN_XPB_GGLP_XLR_ZXMBW-AGW_Z_T.BIN
GGSN_XPB_GGUP_XLR_1_ZXMBW-
AGW_VXWORKS_T.BIN
GGUP GGSN_XPB_GGUP_XLR_2_ZXMBW- GGUP version file

AGW_VXWORKS_T.BIN
GGSN_XPB_GGUP_XLR_ZXMBW-AGW_Z_T.BIN
XPB_01_070801_FPGA_104.BIN
XPB FPGA file of XPB
XPB_01_070801_FPGA_GE4FE8_105.BIN

Module Foreground Version File Remarks
GGSN_GUIM_UIM_8260_ZXMBW-AGW_Z_T.BIN
UIM UIM version file
UIM_01_030800_FPGA_TFS_102.BIN
GGSN_UIM_2_UIM_755_ZXMBW-AGW_Z_T.BIN
UIM_2 GGSN_UIM_2_UIM_8260_ZXMBW-AGW_Z_T.BIN UIM_2 version file
UIM2_03_060201_FPGA_UIMT_111.BIN
Steps 1. Select the exchange to load version files in the navigation tree,
and select versions to configure from the Version pull-down
list, through version searching, all version files information to
be loaded appears in load version main interface.
2. Press Ctrl key to select the version files for boards in the fore-
ground, then right-click on them, select Version Batch De-
fault Load.
Tip:
It can be ordered by physical board type, then select the ver-
sion files to be loaded to simplify corresponding version files
searching.
3. After default loading, reset the boards. Then version com-

parison is carried out on every board and obtain the required
version files. After the version files are loaded, it enters nor-
mal operation status, and RUN indicator on board front panel
flashes at the frequency of once per second.
END OF STEPS
Result Details are shown on the screen, and waiting time is related to
selected version quantity, usually it takes 20–30 minutes. After
loading is completed, progress bar closes automatically, on mes-
sage area Hint Message and Error Message bar, the result is
displayed, and confirm that version loading is successful.
Postrequisite After boards are started normally, query board operating version
through version query to confirm the loaded version is correct.

Chapter 5
AGW Local Office Data

Configuration
Table of Contents
Activating License..............................................................79
Configuring AGW Exchanges Capacity...................................81
Configuring AGW Exchanges Attributes .................................84
Activating License
� ums-license.LCS file has been obtained.
Context License configuration data is configured according to the business
contract. System maximum attachment user number and maxi-
mum activated number are decided by License file.
Before configuring exchange capacity, deploy License firstly.
Steps 1. Backup original License file. Enter the directory zxwn-
omcs/zxwomcs/ums-svr/deploy under OMC installation path,
copy ums-license.LCS file to somewhere else.
2. Copy the obtained ums-license.LCS file to the directory zxwn-
omcs/zxwomcs/ums-svr/deploy under OMC installation path,
and overwrite the original file.
3. Restart OMC server.
4. After OMC server is restarted, login OMC client by user admin,
and enter MML Terminal.
5. In MML Command from MML-Tree, click AGW Command >
System Maintenance > Licence Management > Active Li-
cence (ACTIVE LICENSE), as shown in Figure 62.

FIGURE 62 ACTIVE LICENSE COMMAND CONFIGURATION

mands.
END OF STEPS
Result System enters the interface as shown in Figure 63, means License
activation is successful.

Chapter 5 AGW Local Office Data Configuration
FIGURE 63 ACTIVE LICENSE SUCCESSFUL
Configuring AGW
Exchanges Capacity
Context AGW exchange service capacity planning is to define AGW service
processing capability, configure the data capacity in the module.
Exchange capacity must be configured, otherwise users may not
be able to access.
Users are divided into three modes according to MS status for AGW
system.
� Normal Mode

Service flow tunnel of the WiMAX terminal is created between

AGW and BS (Base Station). Data transmission can be carried
out normally.
Users with MS being Normal mode are called activated users.
� Idle Mode
Service flow tunnel of the WiMAX terminal is not created be-
tween AGW and BS. But some data of the terminal is saved in
AGW, like paging group configuration.
Users with MS being Normal mode and Idle mode are called
online users.
� Detached Mode
MS is not accessed, or exits WiMAX network, and service flow
tunnel of the WiMAX terminal is not created between AGW and
BS, and there is no user information in AGW.
Users with MS being Detached mode are called offline users.
Steps 1. In MML Command from MML-Tree, click AGW Command >
System Management > Capacity Layout Management >
Capacity Management > Set AGW Capacity (SET AGW-
CAP) as shown in Figure 64.
FIGURE 64 SET AGWCAP COMMAND PARAMETERS CONFIGURATION
Parameters in Figure 64 are introduced in Table 21.

TABLE 21 SET AGWCAP COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction
Max Static IP Means the max static IP address Optional

1000
Address supported by the office Value range: 1~10000
Max AGW_UP Max activated user number sup- Optional

50000
Session ported by GGUP board Value range: 1~10000
Max activated user number sup- Optional

Max MS 20000
ported by SMP board Value range: 1~50000
Max Dynamic Max dynamic IP address in IP pool Optional

75000
IP Address of GGUP board Value range: 1~150000

mands.
If command is executed successfully, then following informa-
tion appears on OMC interface, as shown in Figure 65.
FIGURE 65 SET AGWCAP COMMAND EXECUTION RESULT
4. Restart AGW board after OMC configuration is complete to fin-

ish AGW exchanges capacity configura
END OF STEPS

Configuring AGW
Exchanges Attributes
� Exchange capacity has been configured.
� Default accessed NSP has been configured, for the details, re-
fer to Configuring NSP.
Context The operation mainly configures the following data.
� Configure user default accessed NSP (Network Service
Provider) for the exchange.
Default NSP access function is that AGW can specify a NSP
as the default NSP for the user. When user is accessing for
registration, AGW judges NAI according to certain rules when
analyzing NAI (Network Access Identifier) reported by MS (Mo-
bile Station). If NSP (NSP is the contents after @ in NAI) is not
carried in NAI message, or system can not identify NSP infor-
mation (NSP is illegal or error) which is carried in NAI, now
AGW adopts the configured default NSP as the current user’s
NSP to complete registration.
� Configure AGW DHCP Proxy IP Address
When users use Simple IP mode to access, and AGW assigning
IP address method is DHCP Proxy, this address is used for AGW
external interaction.
If it is not configured, for Simple IP (DHCP Proxy mode) users,
they can not obtain IP addresses assigned by AGW from local
IP pool.
� Configure using duration of the IP address assigned to Simple
IP (DHCP Proxy mode) users by AGW
For Simple IP (DHCP Proxy mode) users, AGW works as the
agent of DHCP server, and the IP addresses assigned to users
can set a certain using duration. If MS online activating time
exceeds the duration and does not apply to renew the lease,
AGW withdraw the IP address assigned to MS, and user is of-
fline automatically.
Tip:
For Simple IP (DHCP Relay mode) users, since DHCP server
is used to assign IP addresses for users, DHCP server assigns
the corresponding using duration when assigning IP address,
which is no need to configure in AGW OMC.
� Configure resending times and resending interval for R4 and

R6 interface messages.

Configure the messages resending times and resending inter-

val between AGW and BS, and between other AGWs.
Steps 1. In MML Command from MML-Tree, click AGW Command >
System Management > Local Office Management > Lo-
cal Office Attribute Management > Set Local Office AGW
Attribute (SET AGWCFG), as shown in Figure 66.
FIGURE 66 SET AGW CFG COMMAND PARAMETERS CONFIGURATION
TABLE 22 SET AGW CFG COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Default NSP name Mandatory, value range: character

When user is accessing string with not more than
Default NSP AGW, if the NSP carried 64 characters
agw5.com
Name in the messages are The value of this parameter is the
wrong, then AGW uses parameter NSP Name configured
this NSP to access in ADD NSP command.

When user uses Simple

IP mode to access, and
AGW assigning IP address
method is DHCP Proxy, this
address is used for AGW
external interaction. Mandatory, input the IP address
If it is not configured, for complies with IPV4 formant
DHCP Proxy Simple IP (DHCP Proxy It is set to be the signaling interface 1.3.25.159
IP mode) users, they can address of R6 interface for AGW,
not obtain IP address refer to the planning introduction
assigned by AGW from in Network Planning.
local IP pool normally.
It is the same as signaling
receiving & transmitting
address on R6 logical
interface of AGW
No need to configure
NAS ID Means NAS ID Value range: character string with
not more than 32 characters.
R4/R6 Mes- Optional

Means R4 and R6 message
sage Resend 3
resend times Value range: 1~5
Times
R4/R6 Mes- Optional

Means R4 and R6 message
sage Re- 3
resend interval Value range: 1~3
send...
Using duration of the

IP address assigned by
AGW to MS
For Simple IP (DHCP Proxy
mode) users, AGW works
as DHCP proxy, it assigns
IP address to users, and
DHCP the IP address can be Default value: 86400, means
Proxy/Server configured with using 24 hours 86400
IP Lease... duration. If MS online Value range: 60~4294967295
activating time exceeds
the duration and does not
apply to renew the lease,
then AGW withdraws the
IP address assigned to
MS, and user is offline
automatically.

mands.
END OF STEPS
Result Configuring AGW exchanges attributes is successfully complete.

Chapter 6
AGW Load Sharing

Configuration
Table of Contents
Introduction to Load Sharing Configuration ...........................87
Configuring SMP Control Interface Load Sharing ....................90
Configuring GGUP Media Interface Load Sharing ....................93
Introduction to Load Sharing

Configuration
Description Load sharing configuration of AGW includes the following contents.
� Configuring SMP (Processing signaling interface data mes-
sages) Load Sharing
SMP processes user accessing signaling and messages. For
the situation that there are several SMP modules for one AGW
exchange, SMP load sharing should be configured to process
signaling interface data, so as to maximally optimize SMP mod-
ule processing capability.
� Configuring GGUP (Processing media interface data messages)
Load Sharing
GGUP processes user media flow data. For the situation that
there are several GGUP modules (on one or more GGUP boards)
in a AGW exchange, GGUP load sharing should be configured
to process media interface data, so as to maximally optimize
GGUP module processing capability.
Load Sharing Signaling interface data load sharing is to share the signaling data
Principle for messages to SMP logical board evenly for processing according to
SMP Signaling the first service signaling that users initiates to access, as shown
Interface Data in Figure 67.

FIGURE 67 SIGNALING INTERFACE LOAD SHARING BASED ON MSID
All SMP boards of AGW share a R6 signaling address, and AGW

system executes mod calculation by 64 to MSID (Mobile Station
Identifier) carried in R6 signaling interface messages, and then
according to SMP load sharing principle configured by OMC, share
them to each SMP module for processing.
The main task for signaling interface load sharing is to identify user
access service signaling according to access service protocol (ex-
cluding the signaling of assistant modules, such as RADIUS, DHCP,
MIP, and L2TP), and extract the exact user ID from the signaling.
For AGW, user ID is the MSID carried in R6 interface messages.
MSID is the ID assigned to equipment provider, identifying the
user terminal uniquely.
Load Sharing User media interface load sharing is to share users’ media interface
Principle for GGUP messages evenly to UP logical board, as shown in Figure 68.
Media Interface
Data FIGURE 68 USER MEDIA INTERFACE DATA LOAD SHARING

Chapter 6 AGW Load Sharing Configuration
For media interface load sharing, AGW should receive user media
interface messages from R6 interface and R3 interface.
For R6 interface, user media interface messages are encapsulated
in R6 interface tunnel, and the outer layer address of the tunnel is
AGW media interface address.
For user media interface messages received by R6 interface, AGW
shares the load through GRE Key in tunnel encapsulation.
AGW assigns a R6 media interface address for every GGUP board
(can be the same), a R3 interface address (used for MIP FA/COA
address or DHCP signaling address, but every GGUP R3 address
can not be the same).
For R3 interface, media interface messages are differentiated as
Simple IP access mode and Mobile IP access mode. Under Sim-
ple IP mode, user media flow messages are transmitted to AGW
directly; while under MIP mode, user media flow messages are for-
warded through HA, and are encapsulated in IPinIP tunnel. Tunnel
address is the CoA address defined by MIP protocol, and CoA ad-
dress is the media interface communication address (configured
as R3 signaling interface address) provided by AGW to HA.
� For Mobile IP User
MIP user signaling interface messages adopts R3 interface ad-
dress as signaling load sharing, every GGUP uses its own R3
signaling address to receive and transmit MIP signaling. MIP
media interface messages (IPinIP messages) received by R3
logical interface, uses R3 address for IPinIP outer layer en-
capsulation. For the media interface messages received by
R3 interface, load sharing from GGLP to GGUP is accomplished
through R3 address. After the messages are delivered to GGUP
board correctly, it indexes the correct user according to MS IP
address encapsulated in IPinIP tunnel.
� For Simple IP user (DHCP Relay mode)
Through the assignment principle that plan IP pool reason-
ably between AGW and DHCP Server, make sure that the after
specified GGUP board sends DHCP Relay message, the address
applied can be in the range of prediction. Different GGUP is
planned with different address segment, after receiving R3 in-
terface Simple IP media interface messages, it can accomplish
load sharing selection from downlink Simple IP media interface
messages to GGUP board as per the homing address segment
of user address.
� For Simple IP user (DHCP Proxy mode)
AGW divides the IP pool configured locally into small network
segments, and assigns the address segment of DHCP Proxy
type to the corresponding UP board automatically according to
the load of DHCP Relay address segment borne on each UP
board, which realizes even address segment load on each UP
board. When receiving Simple IP media interface messages
from R3 interface, find the correct UP board similarly accord-
ing to the homing address segment of user address, then com-
plete load sharing from downlink Simple IP media interface
messages to GGUP board.

Configuring SMP Control

Interface Load Sharing
� Office capacity configuration is completed.
� SMP module configuration is finished.
� Signaling receiving and transmitting address on R6 logical in-
terface of AGW has been configured.
Context This topic introduces the procedures to configure loading sharing
of SMP control interface data.
Under the situation that there are multi SMP modules in a AGW ex-
change, it requires to share the control interface messages evenly
to each SMP module for processing according to load sharing prin-
ciple, so as to maximally optimize SMP module processing capa-
bility.
All SMP boards of AGW share a R6 signaling address, and AGW
system executes mod calculation by 64 on MSID (Mobile Station
Identifier) carried in R6 signaling interface messages. After that,
it shares them to each SMP module for processing according to
SMP load sharing principle configured by OMC.
Tip:
Mod calculation by 64 means to calculate the remainder of a num-
ber through dividing it by 64, and the remainder range should be
0~63.
SMP load sharing principle includes two assignment modes.

� Continuous distribution
� Average distribution
Here we use the following examples to introduce how the load
sharing on user signaling interface data is accomplished when
there are 3 SMP modules in a exchange under two assignment
principles.
1. Create mpno according to access user’s MSID by default. (Mod
value of user number segment) is all the records of 0, 1, 2, …,
63.
2. Share mpno one by one to specified module. (Three SMP mod-
ule number is 3, 4, 5)
3. If it is set to be continuous distribution mode, then:
� mpno shared on the SMP numbered as 3 is 0, 3, 6, 9, …,
63, means that the SMP processes user control interface
messages numbered as 0, 3, 6, 9, …, 63.


4. If it is set to be average distribution mode, then:
� mpno shared on the SMP numbered as 3 is 0, 1, 2, …, 21,
means this SMP processes user control interface messages
numbered as 0, 1, 2, …, 21.
� mpno shared on the SMP numbered as 4 is 22, 23 …, 42,
numbered as 22, 23 …, 42.
� mpno shared on the SMP numbered as 5 is 43, 44, …, 63,
numbered as 43, 44, …, 63.
Steps 1. Click AGW Command > System Management > Capacity
Layout Management > Control Plane Load Sharing > Init
SMP Share Load (INIT SMP SHARE LOAD) in MML Com-
FIGURE 69 INIT SMP SHARE LOAD PARAMETERS CONFIGURATION

TABLE 23 INIT SMP SHARE LOAD COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory
Means SMP
SMP Module The value of this parameter is the
module num- 3 and 4
No. SMP module No. configured through
ber
ADD MP command.
Mandatory
Select from pull-down list
Option average means to share the user
Means SMP number segment (user MSID address)
Distribution
module load evenly to each SMP for processing continuum
Mode
sharing mode
Option continuum means to share the
user number segment (user MAC
address) continuously and evenly to
each SMP for processing
Means user
self-defined Optional
User Label SMP module Value range: Character string with not
load sharing more than 50 characters
mode name

mands.
If the commands are executed successfully, then following in-
formation appears on OMC, as shown in Figure 70.

FIGURE 70 INIT SMP SHARE LOAD COMMAND RESULT
4. Restart SMP board after OMC configuration is complete to finish

control interface load sharing configuration.
END OF STEPS
Configuring GGUP Media

Interface Load Sharing


� Office capacity configuration is completed.
� SMP module configuration is completed.
Context The configuration sets available GGUP board basic resources
through adding GGUP board logical board number and specifying
a R6 media interface address and a R3 address for each logical
board number.
UP board competes logical board number after powering on, and
the GGUP boards which obtain logical board number gain basic re-
sources and work normally, those do not gain logical board number
work as standby board.
Steps 1. Click AGW Command > System Management > Capacity
Layout Management > User Plane Load Sharing > Log-
ical UP Management > Create Logical UP Board (ADD
LOGICUP) in MML Command from MML-Tree, as shown in
Figure 71.
Parame-
ter
Mandatory
Logical Means logical board number of
Board No. GGUP board
of 1~255

Parame-
ter
Means AGW R6 media

interface IP address, and
it is logical address
Media R6 complies with IPV4 format
Corresponding media interface 1.3.25.160
Address Refer to the planning introduction
address of different logical
board number of GGUP can
be the same

R3 Address Means R3 address 1.3.25.161
Refer to the planning introduction

mands.
4. Create UP board load sharing. Click AGW command > Sys-
tem Management > Capacity Layout Management > User
Plane Load Sharing > UP Loadshare Management > Build
UP Loadshare (BLD UP LOADSHARE) in MML Command
FIGURE 72 BLD UP LOADSHARE COMMAND PARAMETERS CONFIGURATION

mands.

6. Restart GGUP board after OMC configuration is complete to

finish media interface load sharing configuration.
END OF STEPS
Result Configuring GGUP media interface load sharing is complete.

Chapter 7
AGW Service Data

Configuration
Table of Contents
Configuring IP Address .......................................................97
Configuring Profile ........................................................... 102
Configuring FA ................................................................ 108
Configuring NSP .............................................................. 110
Configuring Charging Data ................................................ 113
Configuring Service Flow .................................................. 117
Configuring IP Address
Configuring IP Address Under DHCP
Relay Mode
� Office capacity has been configured.
Context For SimpleIP users, when AGW uses DHCP server to assign IP ad-
dresses for users, then IP address under DHCP Relay mode should
be configured.
Since the IP address under this mode is assigned by DHCP server,
AGW needs only to configure the same address segment with
DHCP locally.
Steps 1. Click AGW Command > Services Management > DHCP
Relay External IP Segment Management > Create DHCP
Relay Address Segment (ADD DHCP RELAY IPSEG) in

FIGURE 73 ADD DHCP RELAY IPSEG COMMAND PARAMETERS CONFIGURATION
TABLE 25 ADD DHCP RELAY IPSEG COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction
Mandatory
Means the ID of IP segment assigned
Segment ID Value range: integer in 1
by DHCP
the range of 1~1024
Mandatory
DHCP Relay DHCP Profile ID related to the IP seg-
Value range: integer in 1
Profile ID ment
the range of 1~4096
Means the start IP address of the

configured IP address segment
As per the address segment Mandatory, input IP ad-
Start IP Ad-
configured on DHCP server, dress complies with IPV4 10.0.0.1
dress
configure same address segment format
on AGW, and assign it to different
GGUP logical boards.
Mandatory, input IP ad-

End IP ad- Means the end IP address of the con-
dress complies with IPV4 10.0.0.254
dress figured IP address segment
format

Subnet mask corresponding to the IP
Mask dress complies with IPV4 255.255.0.0
address segment
format

Chapter 7 AGW Service Data Configuration
Configuration
Introduction
Logical UP
Assigned logical UP board number Mandatory 1
Board No.
Mandatory, select from

pull-down list, including:
� GiAddr
It is a kind of common
mode supported by
DHCP server
Means AGW prompts in the message � Link Selection
Relay Sub-
sent to DCHP that DHCP server use � Ipv4 Subnet Selection
net Selection GiAddr
this address segment to assign ad-
Mode Link Selection and
dress for users
Ipv4 Subnet Selection
modes should be
supported by DHCP
server, and check
onsite DHCP server
manual to judge
whether they can be
used or not
It can not be the address in the ad-

Subnet Se- Mandatory, input IP ad-
dress segment, but it should be in
lection Hint dress complies with IPV4 10.0.1.1
the same subnet with user address
IP format
segment
Optional, input character

Corresponding name of the address
User Alias string with not more than
segment
50 characters

mands.
finish IP address under DHCP relay mode configuration.
END OF STEPS
Result Configuring IP address under DHCP relay mode is successfully

complete.
Configuring IP Address Under DHCP

Proxy Mode

Context For SimpleIP users, when AGW uses local IP pool to assign IP ad-
dresses for users, it requires to configure SimpleIP IP pool and IP
addresses in the IP pool.
Since IP address under this mode is assigned by DHCP server, then
AGW needs only to configure same address segment with DHCP
server locally.
Steps 1. Configure Simple IP pool. Click AGW Command > Services
Management > Simple IP Pool Management > Create IP
Pool (ADD IPPOOL) in MML Command from MML-Tree, as
shown in Figure 74.
FIGURE 74 ADD IPPOOL COMMAND PARAMETERS CONFIGURATION
TABLE 26 ADD IPPOOL COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction
IP Pool ID Means ID of the IP pool Optional 1

Value range: 1~1024
Means the configured IP Mandatory

pool name when user IP Value range: Character IP-
IP Pool Name
address is assigned by string with not more than pool_nsp2.agw5.com
AGW local IP pool 50 characters

Configuration
Introduction
Optional
Value range: 1~254
Homing VPN name of the If the IP pool is in a VPN,
VRF ID then the parameter is
IP pool
set to be the name of
VPN, otherwise no need
to configure

mands.
4. Configure IP address segment in Simple IP pool. Click AGW
Command > Services Management > Simple IP Pool
Management > DHCP Proxy Address Segment Man-
agement > Create DHCP Proxy Address Segment (ADD
DHCP PROXY IPSEG) in MML Command from MM-Tree, as
shown in Figure 75.
FIGURE 75 ADD DHCP PROXY IPSEG COMMAND PARAMETERS CONFIGURATION

TABLE 27 ADD DHCP PROXY IPSEG COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory
Means the config- Value range: Character
ured IP pool name string with not more than
IP Pool when AGW media 50 characters
IPpool_nsp2.agw5.com
Name interface address The value of this parameter
is dynamically as- is the parameter IP Pool
signed locally Name configured in ADD
IPPOOL command
Means the ID of
a IP segment in
the IP pool
Since a IP pool Mandatory
Segment ID may include multi Value range: Integer in the 1
IP segments, this range of 1~1024
parameter identifies
a IP segment in the
same IP pool
Start IP address of
Start IP Ad- Mandatory, input IP address
the configured ad- 10.0.0.1
dress complies with IPV4 format
dress segment
End IP address of
End IP Ad- Mandatory, input IP address
the configured ad- 10.0.0.254
dress complies with IPV4 format
dress segment
Means the subnet

mask corresponding Mandatory, input IP address
Mask 255.255.0.0
to the IP address complies with IPV4 format
segment

mands.
finish IP address under DHCP Proxy mode configuration.
END OF STEPS
Result Configuring IP address under DHCP proxy mode is successfully

complete.
Configuring Profile
Configuring DHCP Relay Profile


Context When AGW uses DHCP server to assign IP addresses for Simple IP
users, it requires to configure DHCP Relay Profile.
Steps 1. Click AGW Command > Services Management > Profile
Management > DHCP Relay Profile Management > Cre-
ate DHCP Relay Profile (ADD DHCP RELAY PROFILE) in
FIGURE 76 ADD DHCP RELAY PROFILE COMMAND PARAMETERS CONFIGURATION
TABLE 28 ADD DHCP RELAY PROFILE COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory
DHCP Relay Means ID of DHCP Proxy
Value range: Input integer in 1
Profile ID Profile
the range of 1~4096.
Mandatory
Server Ad- Means DHCP server IP ad-
dress dress
with IPV4 format

Optional
Input integer in the range
of 1~254
VRF Means VRF ID
If DHCP server belongs to
a VRF, then this parameter
should be configured.

mands.
END OF STEPS
Result Configuring DHCP relay profile is successfully complete.
Configuring Radius Profile

Context Configuring Radius Profile is that when AGW communicates with
AAA server, it requires to configure the data such as Radius server
address, Radius client address, and shared key by server and
client.
AAA server is used for user authentication, identification and ac-
counting management. When user accesses to Wimax network,
AGW should participate user authentication flow, and AGW sends
identification/accounting requests to AAA server. Now AGW works
as a Radius client. AGW sends user name and password to AAA
server, and AAA server carries out authentication and identifica-
tion on user. When it requires to account on user by AAA server,
AGW informs AAA to start or stop accounting.
Management > Radius Profile Management > Create Ra-
dius Profile (ADD RADIUS PROFILE) in MML Command

FIGURE 77 ADD RADIUS PROFILE COMMAND PARAMETERS CONFIGURATION
TABLE 29 ADD RADIUS PROFILE COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Optional
Radius Pro- Means the ID of AAA
file ID server
of 1~4096
Optional
Input integer in the range of 1~254
VRF Means VRF ID
If AAA server belongs to a VRF,
then this parameter should be set
Primer
Means the primary AAA Mandatory, refer to the planning
Server Ad- 20.2.25.1
server address introduction in Network Planning
dress
Mandatory
Primer Means the shared key Input character string with not
Server between AAA primary more than 64 characters 0
Shared Key server and AGW Shared key should be the same
as that configured in AAA
Second
Means the secondary
Server Ad- Mandatory
AAA server address
dress

Mandatory
Second Means the shared key
Server between AAA secondary 1
Server Link Means the timeout time Optional

2
Timeouts (s) of AAA server connection Input integer in the range of 1~3
Server Re- Means AAA server re- Optional

3
send Times sending times Input integer in the range of 2~4
Means the client address

Client Ad- of AAA, it is set to be the Mandatory, refer to the planning
1.3.25.159
dress control interface address introduction in Network Planning
of R6 interface of AGW

mands.
END OF STEPS
Result Configuring radius profile is successfully complete.
Configuring DHCP Proxy Profile

Context When AGW works as DHCP server, uses local IP pool to assign IP
addresses for Simple IP users, it requires to configure DHCP Proxy
Profile.
Management > DHCP Proxy Profile Management > Cre-
ate DHCP Proxy Profile (ADD DHCP PROXY PROFILE) in
MML Command from MML-Tree as shown in Figure 78.

FIGURE 78 ADD DHCP PROXY PROFILE COMMAND PARAMETERS CONFIGURATION
TABLE 30 ADD DHCP PROXY PROFILE COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction
Mandatory, value range:

DHCP Proxy
Means DHCP Proxy Profile ID Input integer in the 1
Profile ID
range of 1~4096
Means active DNS (Domain

Name System) server IP
Optional
address
Active DNS Input IP address
DNS server IP address is 192.168.52.100
Server Address complies with IPV4
decided according to onsite
format
situation, usually provided
by the operator
Optional
Standby DNS Means the standby DNS Input IP address
Server Address server IP address complies with IPV4
format
Means that for Simple IP users Mandatory

Simple IP Pool with DHCP mode, AGW can Value range: Input 3
ID only assign IP address from integer in the range
the configured IP pool of 1~4096


mands.
END OF STEPS
Result Configuring DHCP proxy profile is successfully complete.
Configuring FA
Context When AGW supports MIP access mode, it requires to configure FA
related attributes.
Steps 1. Configure FA related parameters. Click AGW Command >
Services Management > FA Configuration Management
> Set FA Configuration (SET FA) in MML Command from
FIGURE 79 SET FA COMMAND PARAMETERS CONFIGURATION

TABLE 31 SET FA COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Means whether to send AA Optional

Active Send NO (Not to send
after service flow is cre-
AA Select from pull-down list AA actively)
ated under CMIP mode
Means the time interval Optional

AA Send In-
of sending AA under CMIP Unit: Second 60
terval (s)
mode Value range: 1~1800
Means times of sending Optional

AA Seriality
AA continuously under 6
Send Times Value range: 3~10
CMIP mode
Means time duration of

Lifetime, that is under
CMIP mode, the time du-
Register ration that FA allows user Optional
1800
Lifetime (s) a MIP session. When MIP Value range: 1~65535
Lifetime is about to ex-
ceed, MIP user originates
MIP refreshment flow
Means whether to support Optional YES (Support

FA-HA AE
FA-HA AE Select from pull-down list FA-HA AE)
Means whether to inform Optional

WAIT-RRP YES (Support
terminal when HA origi-
Timer (s) Select from pull-down list WAIT-RRP Timer)
nates deregistration

3. Click Execute (F5) button to complete configuring FA.
END OF STEPS
Result If commands are executed successfully, then following information

appears, as shown in Figure 80.

FIGURE 80 SET FA COMMAND PARAMETERS CONFIGURATION RESULT
Configuring NSP
Context NSP (Network Service Providers) means the service network op-
erated by WiMAX service provider, user subscribes with NSP after
accessing and registration, so as to obtain WiMAX service.
After authentication negotiation, AGW sends AuthRelay-EAPTrans-
fer (ID/request) message for user authentication. The purpose for
sending this message is that AGW needs to know which NSP is be-
ing used for user accessing. After AGW receives AuthRelay-EAP-
Transfer (ID/response) message, it obtains NSP in it, then finds
corresponding AAA according to the NSP configuration in AGW
OMC, and transparently transmits user authentication messages.
The operation configures the following data.
� Configure NSP name.
� Configure the access mode for user accessing to this NSP to be
Simple IP or MIP.

Steps 1. Click AGW Command > Services Management > NSP

Management > Create NSP (ADD NSP) in MML Com-
FIGURE 81 ADD NSP COMMAND PARAMETERS CONFIGURATION
TABLE 32 ADD NSP COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory
NSP naming rules are as follows:
� NSP name should be no more
than 64
� can only be composed of num-
ber, character, "." and "-", be-
NSP Name Means NSP server name fore or after "-", it must be nsp1.agw5.com
character or number
� It must comply with a.b for-
mat, a and b means field, the
length of each field is not re-
stricted, but it should be com-
posed of at least two fields.
Optional
Enable QoS Means whether to use
Select from the pull-down list, NO
Map QoS parameter option
including YES and NO

Mandatory
list, including:
� MIP
Means the mode of the Means AGW supports that
user subscribed to the the users subscribed to this
Access Mode NSP access to WiMAX network MIP
NSP accessing WiMAX
network through CMIP or PMIP mode.
� Simple IP
Means AGW supports that
the users subscribed to this
NSP use Simple IP mode to
access WiMAX network.

mands.
END OF STEPS
Result If commands are executed successfully, then following information

appears, as shown in Figure 82.
FIGURE 82 ADD NSP COMMAND RESULT

Configuring Charging Data

Configuring Charging Template
Context Configuring charging template is to configure the charging mode
adopted by AGW when a user accesses a NSP.
Charging mode supported by AGW system includes the following
two types.
� Based on IP Address (IP-session Charging)
IP is the address obtained after MS accesses AGW successfully,
users can carry out messages interaction with the Internet, use
WiMAX service. Under this charging mode, AGW charges the
users as per the IP addresses obtained by MS.
� Based on Service Flow (PD-flow Charging)
Charging based on service flow is that AGW calculates the
resource consumption on each flow through PD-flow ID, and
charges the users. PD-flow ID is distributed by AAA (Under
abnormal situation, if AAA does not distribute, then use the
PD-flow ID locally configured by AGW.
Steps 1. Click AGW Command > Services Management > Charg-
ing Management > Create Charging Template (ADD
CHGTPL) in MML Command from MML-Tree, as shown in
Figure 83.

FIGURE 83 ADD CHGTPL COMMAND PARAMETERS CONFIGURATION
TABLE 33 ADD CHGTPL COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory
Charging Means the ID of charg-
Template ID ing template
the range of 1~31
Means charging mode Optional, select from pull-down

list, including:
� Currently offline
charging supports � IP Session
IP Session and PD Charging mode based on IP
Flow two modes Session is that AGW charges
users according to the IP
Charging � Currently online
addresses obtained by MS. PD Flow
Mode charging supports
only IP Session � PD Flow
mode. So it can Charging based on service
only be set to IP flow is that AGW calculates
Session if charg- resources consumption on
ing mode is online each flow through PD-flow ID
charging and charges users.

mands.
END OF STEPS

Result Configuring charging template is successfully complete.
Configuring Payment Mode

� Charging template has been configured, please refer to for de-
tails.
� Online charging function should be added in License file.
Context Configuring payment mode means to configure user payment
mode and charging granularity.
Charging granularity is the type to measure user communication
resources consumption, including time and flow.
According to user payment situation, AGW supports two payment
mode.
� Offline Accounting
It is the so-called Postpaid Accounting, means to provide ser-
vices for MS firstly and charge user after service is completed.
For offline accounting, AGW currently supports two charging
modes, which are based on PD-Flow and based on IP address.
� Online Accounting
It is the so-called Prepaid Accounting, means the user prepay
and then AGW provides services for MS.
For online accounting, AGW currently supports only to charge
based on IP address.
Steps 1. Click AGW Commands > Services Management > Charg-
ing Management > Set Payment Mode (SET PAYMENT
MODE) in MML Command from MML-Tree, as shown in Fig-
ure 84.

FIGURE 84 SET PAYMENT MODE COMMAND PARAMETERS CONFIGURATION
TABLE 34 SET PAYMENT MODE COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Charging Means the ID of Optional

1
Template ID charging template Input integer in the range of 1~31
Optional, select from pull-down

list, including:
� online
It is the so-called Prepaid Accounting,
means the user prepay and then
AGW provides services for MS.
For online accounting, AGW currently
supports only charging mode
based on IP-Session.
Means the payment � Offline
Payment
mode used by charg- It is the so-called Postpaid both
Mode
ing template Accounting, means to provide
services for MS firstly and charge
user after service is completed.
For offline accounting, AGW supports
two accounting modes, which are
based on PD-Flow and IP address.
� both
Means support online accounting and
offline accounting, and it is decided
whether accounting quota during
AAA authentication is distributed:


if distributed, then adopt online
accounting; if not distributed, then
adopt offline accounting.
Optional, including;
� Flow
Charge user online payment
according to flow
Means Charging
mode � Time
Online Charg- When Payment Charge user online payment Time or
ing Support Mode is set to be according to time Flow
online or both, this � Time or Flow
parameter is valid
Support to charge according to
flow or time. It is decided by
parameters distributed by PPS, if
PPS supports the two modes, then
flow is used on priority.

3. Click Execute (F5) button to complete configuring payment
mode.
END OF STEPS
Result Configuring payment mode is successfully complete.
Configuring Service Flow

Prerequisites � OMC server and client are connecting properly.
� Foreground devices are working properly.
� Oracle database is working properly.
� Physical data configuration is complete.
� Office capacity is configured.
Context When MS initially accesses WiMAX network, it establishes initial
layer 2 connection with AGW, and the establishment of initial layer
2 connection includes following two parts:
1. MS accessing authentication and authorization.
2. Creating data channel between MS and AGW (Creating service
flow).
After MS completes registration negotiation, EAP authentication
and registration, AGW allows the subscriber to access WiMAX net-
work and obtain subscriber’s authorization information from AAA.
AGW establishes a set of data channel between MS and CSN based
on service flow according to MS subscription information delivered
by AAA, and uses it to perform upper layer control signaling trans-
mission for creating IP session and basic data transmission service.
Maximally AGW supports to establish 8 one-way service flows be-
tween a MS and CSN, and all service flows are divided into:

� ISF
An upstream and a downstream service flow established firstly
are called Initial Server Flow (ISF).
� PSF
Other service flows established after ISF establishment are
called Preparation Server Flow (PSF).
Usually after MS accesses WiMAX network successfully, AGW es-
tablishes service flow as per Packet Data Flow ID (PDFID) delivered
by AAA. PDFID is used to identify a service flow delivered by AAA
(This server flow may be a one-way flow or a two-way flow).
Since those flows on which GRE tunnel operations (Creating and
releasing a tunnel) are performed between AGW and BS through
interface R6 are one-way service flows, AGW carries out following
to operations on the PDFID delivered by AAA:
� If AAA delivers a two-way service flow, AGW decomposes it
into two one-way service flows.
� If AAA delivers a one-way service flow, AGW converts it into a
one-way service flow.
AGW uses Server Flow ID (SFID) to identify the converted one-way
service flow, which means, SFID is generated by AGW according
to the PDFID delivered by AAA.
Generally, AGW uses ISF delivered by AAA to establish data chan-
nel, but AGW uses locally configured service flow to establish data
channel under following two situations:
� The ISF delivered by AAA is wrong.
� Information like classifier and QoS is not carried in the PSF
delivered by AAA, but Service Profile ID same as the service
flow configured locally is carried.
Configuring service flow includes following contents:
1. Configuring local service flow QoS Profile.
Configuring local service flow QoS Profile is to configure QoS
Profile correlated to locally configured service flow. If sub-
scribers uses locally configured service flow, it uses locally con-
figured QoS Profile correlated to the local service flow.
2. Configuring local service flow.
3. Configuring the classifier of local service flow.
Management > Service Flow QoS Profile Management >
Creating Service Flow QoS Profile in MML Command, as
shown in Figure 85.

FIGURE 85 ADD SFQOS COMMAND CONFIGURATION
TABLE 35 PARAMETERS IN ADD SFQOS COMMAND CONFIGURATION
Parameter Explanation Configuring Instruction
QoS Profile Optional

QoS Profile ID
ID Value range: Integer in the range of 1~128.
Schedule Mandatory
Schedule Type
Type Select from drop-down list
Traffic Optional
Traffic Priority
Priority Value range: Integer in the range of 0~7.
Max
Sustained
Max Sustained Traffic Rate Optional
Traffic
Rate(bps)
Min Reserved
Traffic Min Reserved Traffic Rate Optional
Rate(bps)
Max Traffic
Max Traffic Burst Optional
Burst(bytes)
Tolerated
Tolerated Jitter Optional
Jitter(ms)

Max
Max Latenc Optional
Latency(ms)
Reduced Optional
Resource Reduced Resource Code
Code Value range: Integer in the range of 0~1.
Unsolicited Optional
Grant Unsolicited Grant Interval
Interval Value range: Integer in the range of 0~65535.
SDU Optional
SDU Size(bytes)
Size(bytes) Value range: Integer in the range of 0~255.
Polling Optional
Polling Interval(ms)
Interval(ms) Value range: Integer in the range of 0~65535.
Optional
User Alias User Alias Value range: Character string with not more
than 50 characters.

mands.
3. Click AGW Command > Services Management > Layer 2
Access Management > Service Flow Management > Cre-
ate Service Flow in MML Command, as shown in Figure 86.
FIGURE 86 ADD SERVFLOW COMMAND

TABLE 36 PARAMETERS IN ADD SERVFLOW COMMAND CONFIGURATION
Optional
Service Flow
Service Flow ID Value range: Character string with not more than
ID
50 characters.
Mandatory, select from pull-down list.

Direction Direction � Upstream
� Downstream
Mandatory
QoS Profile
QoS Profile ID It is the parameter QoS Profile ID configured
ID
through ADD SFQOS command, refer to Table 35.
User Alias User Alias Optional

mands.
5. Click AGW Command > Services Management > Layer
2 Access Management > Packet Classification Rule
Management > Create Packet Classification Rule in MML
Command, as shown in Figure 87.
FIGURE 87 ADD SERVFLOW PKGCLSRULE COMMAND

TABLE 37 PARAMETERS IN ADD SERVFLOW PKGCLSRULE COMMAND CONFIGURATION
Mandatory
Value range: Integer in the range of 1~128.
Service Flow
Service Flow ID It is the parameter Service Flow ID configured
ID
through ADD SERVFLOW command, refer to Table
36.
Classification Mandatory
Classification Rule Index
Rule Index Value range: Integer in the range of 1~3.
Optional
Priority Priority
Optional
Protocol Type Protocol Type
Protocol
Source IP Protocol Type Optional
AddressType
Source IP
Source IP Address Optional
Address
Source IP
Source IP Mask Optional
Mask
Destination
Destination IP Address Optional
IP Address
Destination
Destination IP Mask Optional
IP Mask
Source Optional
Protocol Source Protocol Port
Port(Min) Value range: Integer in the range of 0~65535.
Source Optional
Protocol Source Protocol Port
Port(Max) Value range: Integer in the range of 0~65535.
Destination Optional
Protocol Destination Protocol Port
Port(Min) Value range: Integer in the range of 0~65535.
Destination
Destination Optional
Protocol Port
Protocol Value range: Integer in the range of 0~65535.
Port(Max)
Optional
User Alias User Alias Value range: Character string with not more than
50 characters.


mands.
END OF STEPS


Chapter 8
AGW Data Synchronizat

ion Configuration
Table of Contents
Introduction to Data Synchronization Configuration .............. 125
Synchronizing All Tables ................................................... 125
Synchronizing Changed Tables........................................... 127
Introduction to Data
Synchronization
Configuration
Description This topic introduces how to synchronize the data configured by
AGW background to foreground OMP. After operator configures
data on OMC client, system should send the configured data to
foreground OMP, so as to enable foreground NE to obtain saved
data from OMC server to ensure data consistency of foreground
and background.
Type of Data Data synchronization is to enable data synchronous update be-
Synchronization tween foreground and background (OMC server). Foreground and
background data synchronization uses TCP/IP protocol.
There are two methods for data synchronization, listed as follows.
� Sending All Tables
Usually it is carried out after all the data is configured.
� Sending Changed Table
Usually it is carried out after a single step operation is config-
ured.
Synchronizing All Tables



Context This topic introduces how to synchronize all tables to the fore-
ground.
Steps 1. Click System Maintenance > Data Transmit > Sync Data
(Only used by admin)(SYNA) in MML Command from
FIGURE 88 SYNA COMMAND PARAMETERS CONFIGURATION
TABLE 38 SYNA COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Optional
Means self-defined user
User Name Value range: Character string
name
with not more than 50 characters
Means the type of synchron- Mandatory

Sync Type ALL
ized data Select from the pull-down list
Optional
Means the module to be
Module List No inputting means to select 3&4
synchronized
all modules
Response Means the time duration of

Timeout foreground OMP timeout re- Optional 30
(100ms) sponse

Chapter 8 AGW Data Synchronization Configuration
Save When Means whether to save after

Optional YES
Completed data is synchronized
Sync To Means whether to synchron-

Slave When ize the primary and slave Optional YES
Completed after data is synchronized

mands.
END OF STEPS
Result Synchronizing all tables is successfully complete.
Synchronizing Changed
Tables
Context This topic introduces the procedure to synchronize changed tables
to the foreground.
Steps 1. Click System Maintenance > Data Transmit > Show
Changed Tables (SHOW CHG) in MML Command from

FIGURE 89 SHOW CHG COMMAND PARAMETERS CONFIGURATION

mands.
3. Click System Maintenance > Data Transmit > Sync Data
(Only Used By Admin)(SYNA) in MML Command from

Chapter 8 AGW Data Synchronization Configuration
FIGURE 90 SYNA COMMAND PARAMETERS CONFIGURATION (CHANGED TABLES)
TABLE 39 SYNA COMMAND PARAMETERS CONFIGURATION INTRODUCTION (CHANGED TABLES)
Optional
Means self-defined
User name Value range: Character string with
user name
not more than 50 characters
Means the type of Mandatory

Sync Type CHG
synchronized data Select from the pull-down list
Optional
Means the module to
Module List No inputting means to select 3&4
be synchronized
all modules
Means the time du-

Response
ration of foreground
Timeout Optional 30
OMP timeout re-
(100ms)
sponse
Means whether to
Save When
save after data is Optional YES
Completed
synchronized
Means whether to
Sync To
synchronize the pri-
Slave When Optional YES
mary and slave after
Completed
data is synchronized


mands.
END OF STEPS
Result Synchronizing changed tables is successfully complete.

Chapter 9
AGW Service Function

Configuration Instances
Table of Contents
MIP Access Function Configuration ..................................... 131
Simple IP Access Function Configuration ............................. 140
Charging Function Configuration ........................................ 163
Handover Function Configuration ....................................... 171
Paging Function Configuration ........................................... 176
MIP Access Function

Configuration
Introduction to MIP Access Function
Configuration
Description MIP access function is a method for mobile users to access WiMAX
network. The IP addresses that the users used when accessing for
data communication are stable permanently.
Advantages of MIP MIP is scheme to provide mobile data communication on the global
Access Method Internet. When users use MIP method to access WiMAX network,
they can move freely within network covering range while keeping
same IP address unchanged, and even when MS is crossing AGW,
the service continuity still can be ensured without terminating pre-
vious service. When users require roaming, operator can provide
MIP access method for them.
Types of MIP When users access AGW and create initial service flow, if the ac-
Access Method cess method of user subscribed NSP is MIP (Mobile IP), AGW sup-
ports that user belonging to this NSP access WiMAX network by
MIP method.
MIP access method provided by AGW includes CMIP and PMIP, and
it is decided by the signaling used by user terminal. If terminal
uses DHCP signaling to obtain IP address, then it is PMIP access
method; if terminal uses MIP signaling to obtain IP address, then
it is CMIP access method, the details are listed as follows.
� CMIP (Client Mobile IP) Method

CMIP function means that MIP function is realized on terminal,

and terminal is required to support MIP protocol, then the user
can access WiMAX network with MIP method. This method is
of high requirements on the terminal.
After ISF (Initial Server Flow) is created, CMIP user sends MIP
signaling directly to HA to apply address and request MIP reg-
istration to access corresponding NSP.
� PMIP (Proxy-Mobile IP) Method
PMIP is a kind of method which does not require terminal to
support MIP protocol, and common terminal can access using
MIP. Its MIP function is realized on AGW.
PMIP user sends DHCP registration signaling request for MIP
registration, and AGW originates MIP registration as PMIP
client.
According to the method that AGW assigns IP addresses for
PMIP users, PMIP access it divided into the following two ways.
� PMIP Method Based on DHCP Relay
If AAA server assigns DHCP server address for AGW during
authentication flow, then the user realizes MIP registration
through PMIP method based on DHCP Relay.
� PMIP Method Based on DHCP Proxy
If AAA server does not assign DHCP server address for AGW
during authentication flow, then the user realizes MIP reg-
istration through PMIP method based on DHCP Proxy.
All in all, AGW supports three MIP access methods.
� CMIP Method
Schematic diagram of CMIP method access flow is as shown in
Figure 91.
FIGURE 91 CMIP ACCESS FLOW
� PMIP Method Based on DHCP Relay

Schematic diagram of PMIP method based on DHCP Relay is as
shown in Figure 92.

Chapter 9 AGW Service Function Configuration Instances
FIGURE 92 PMIP METHOD BASED ON DHCP RELAY
� PMIP Method Based on DHCP Proxy

Schematic diagram of PMIP method is as shown in Figure 93.
FIGURE 93 PMIP METHOD BASED ON DHCP PROXY

Configuring MIP Access Function

� Physical data configuration has completed.
Context MIP access function is a method for mobile users to access WiMAX
network. The IP addresses users used for data communication by
this method is stable permanently.
Here we use some examples to introduce how to configure MIP
access function, listed as follows.
1. Configure NSP.
Add a NSP, and configure its name as nsp1.agw5.com, method
for users to access it is MIP.
2. Configure FA Attributes.
When users adopt MIP method to access NSP, it requires to
configure AGW FA attributes in OMC.
3. Configure CoA (Care of Address)
CoA means FA address, and it is the IP address used when AGW
communicates with HA. Configure CoA as R3 media/signaling
interface address in OMC. Every GGUP board participated in
load sharing must configure a CoA.
Steps 1. Click AGW Command > Service Management > NSP Man-
agement > Create NSP (ADD NSP) in MML Command from

Mandatory
� NSP name should be no more
than 64 bits
� can only be composed of num-
ber, character, "." and "-", be-
NSP Name Means NSP server name fore or after "-", it must be nsp1.agw5.com
character or number
� It must comply with a.b for-
mat, a and b means field, the
length of each field is not re-
stricted, but it should be com-
posed of at least two fields.
Optional
Enable QoS Means whether to use
Map QoS parameter option

Mandatory
list, including:
� MIP
Means the mode of the Means AGW supports that the
Access user subscribed to the users subscribed to this NSP
access to WiMAX network MIP
Mode NSP accessing WiMAX
network through CMIP or PMIP mode.
� Simple IP

mands. If commands are executed successfully, then following
FIGURE 95 ADD NSP COMMAND PARAMETERS CONFIGURATION RESULT
4. Configure FA related parameters. Click AGW Command >

Services Management > FA Configuration Management
> Set FA Configuration (SET FA) in MML Command from
MML-tree, as shown in Figure 96.

FIGURE 96 SET FA COMMAND PARAMETERS CONFIGURATION
TABLE 41 SET FA COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Parame-
ter
Means whether to send AA Optional

Active Send NO (Not to send
after service flow is created
AA Select from pull-down list AA actively)
under CMIP mode
Means the time interval Optional

AA Send
of sending AA under CMIP Unit: Second 60
Interval (s)
mode Value range: 1~1800
Means times of sending AA Optional

AA Seriality
continuously under CMIP 6
Send Times Value range: 3~10
mode
Means time duration of

Lifetime, that is under CMIP
mode, the time duration
Register that FA allows user a MIP Optional
1800
Lifetime (s) session. When MIP Life- Value range: 1~65535
time is about to exceed,
MIP user originates MIP re-
freshment flow
Means whether to support Optional YES (Support

FA-HA AE
FA-HA AE Select from pull-down list FA-HA AE)

Parame-
ter
Means whether to inform Optional

WAIT-RRP YES (Support
terminal when HA origi-
Timer (s) Select from pull-down list WAIT-RRP Timer)
nates deregistration

mands to complete configuring FA. If commands are executed
successfully, then following information appears, as shown in
Figure 97.
FIGURE 97 SET FA COMMAND PARAMETERS CONFIGURATION RESULT
7. Configure CoA address according to GGUP logical board. Click

AGW Command > System Management > Capacity Lay-
out Management > User Plane Load Sharing > Logical
UP Management > Create Logical UP Board (ADD LOG-
ICUP) in MML Command from MML-Tree, as shown in Figure
98.

Configuration
Introduction
Mandatory
Logical Board Means logical board number of
No. GGUP board
of 1~255
Means AGW R6 media

interface IP address, and it Mandatory, input IP address
is logical address complies with IPV4 format
Media R6 Ad-
Corresponding media interface Refer to the planning 1.3.25.160
dress
address of different logical introduction in Network
board number of GGUP Planning.
can be the same

R3 Address Means R3 address Refer to the planning 1.3.25.161
Planning.

mands.
END OF STEPS
Result Configuring MIP access function is successfully complete.

Simple IP Access Function

Configuration
Introduction to Simple IP Access
Function Configuration
Description Simple IP access function is a kind of access method for mobile
users to access WiMAX network supported by AGW system. The
IP addresses users used obtained when accessing for data com-
munication is dynamic.
Advantages of For Simple IP accessed users, visit to WiMAX network when cross-
Simple IP Access ing AGW is interrupted. But with Simple IP access method, system
Method needs only to assign IP addresses when users are online; once
users are offline, the IP addresses are released, so the occupied
IP addresses resources under this method are less. When users
do not require to roam, operator can choose Simple IP method to
access them.
In Simple IP services, current visiting AGW or DHCP server assigns
IP address for MS and provide IP route service.
IP Address After users access WiMAX network and create initial service flow, if
Assignment Mode access method of user subscribed NSP is Simple IP, then AGW sup-
under Simple IP ports that users belonging to this NSP access by Simple IP method.
Method
AGW supports two methods of assigning IP addresses for Simple
IP suers, and it is decided by NSP Simple IP authorization mode
configured by OMC, listed as follows.
� Visiting AGW Assigning IP Address (DHCP Proxy Mode)
Configure authorization mode of NSP Simple IP user accessed
as DHCP Proxy in OMC, and MS applies IP address to AGW,
then AGW assigns a free IP address for user from locally con-
figured IP pool, and dispatches to MS. AGW executes DHCP
Proxy function.
Under Simple IP access method, schematic diagram of AGW
assigning IP address for users is shown in Figure 99. In this
flow, AGW simulates as DHCP Server to assign IP addresses
for users.

FIGURE 99 SIMPLE IP (DHCP PROXY) FLOW
� DHCP Server Assigning IP Address (DHCP Relay Mode)

In OMC system, configure authorization mode of NSP Simple IP
user accessed as DHCP Relay, then MS applies IP address from
DHCP server through AGW, and as DHCP client, AGW forwards
MS request message to DHCP server to request to assign an
IP address for user, now AGW executes DHCP Relay function.
Under Simple IP access method, schematic diagram of DHCP
server assigning IP address for users is as shown in Figure 100.
In this flow, AGW executes DHCP Relay function.
FIGURE 100 SIMPLE IP (DHCP RELAY) FLOW
Configuring Simple IP Access

Function Under DHCP Proxy Mode

Context Simple IP access function is a method that AGW system supported

mobile users access WiMAX network. The IP address users ob-
tained for data communication by this access method is dynamic.
Configuring Simple IP access function under DHCP Proxy mode
means that AGW uses local IP pool to assign IP addresses for users.
Here we use examples to introduce how to configure Simple IP
access function under DHCP Proxy mode, and the flow is listed as
follows.
1. Configure NSP.
Add a NSP, configure the NSP name as nsp2.agw5.com, and
the access method used to access it is Simple IP.
2. Configure authorization attributes of the NSP.
Configuring NSP authorization attributes is to configure
whether to assign IP addresses for Simple IP users by AGW
local IP pool or by DHCP server. Here we suppose that AGW
local IP pool assigns IP addresses for users. Configuring
authorization attributes of the NSP includes 4 steps, listed as
follows.
i. Configure Simple IP pool.
When AGW adopts local IP pool to assign IP addresses for
users, it requires to configure AGW local IP pool and corre-
sponding IP addresses in OMC. Here we suppose the con-
figured IP pool name is IPpool_nsp2.agw5.com.
ii. Configure IP segment in IP pool of Simple IP.
Here we suppose the IP segment in configured IP pool is
10.0.0.1~10.0.0.254.
iii. Configure DHCP Proxy Profile.
Configure DNS (Domain Name System) primary/secondary
server IP address used to analyze IP address for AGW lo-
cal IP pool. Here we suppose DNS server IP address is
192.168.52.100.
iv. Configure NSP authorization.
Configuring NSP authorization is to correlate the configured
DHCP Proxy Profile with the NSP. It means to analyze local
IP pool by DNS server.
3. Configure NSP authentication attributes.
During authentication for user access, AGW finds correspond-
ing AAA server for user authentication according to its accessed
NSP. Configuring NSP authentication attributes includes follow-
ing two steps.
i. Configure Radius Profile.
Configuring Radius Profile means to configure the data like
Radius server address, Radius client address and shared
key of server and client when AGW communicates with AAA
server.
ii. Configure NSP Authentication.
Configuring NSP authentication means to correlate the con-
figured Radius Profile with the NSP.
4. Configure AGW Local Office Attributes.

Configure two parameters in AGW local office attributes, which

are DHCP Proxy IP and DHCP Proxy/Server IP Lease.
� Configure AGW DHCP Proxy IP Address
When users use Simple IP method to access and AGW as-
signing IP address method is DHCP Proxy, the address is
used for IP address of AGW external interaction. If the pa-
rameter is not configured, for Simple IP (DHCP Proxy mode)
users, they can not obtain IP address configured by AGW
from local IP pool.
� Configure Using Duration of IP Address That AGW assigns
to Simple IP (DHCP Proxy ) user
For Simple IP (DHCP Proxy mode) users, as DHCP server
agent, AGW assigns IP addresses to suers, and the IP ad-
dresses can be configured with using duration. If MS only
activated time exceeds this duration and does not apply re-
newal, then AGW withdraw the configured IP address from
MS, and users become offline automatically.
Tip:
For Simple IP (DHCP Relay mode) users, since it adopts
DHCP server to assign IP addresses for users, and DHCP
server distributes the corresponding lease duration when
distributing IP addresses, no need to configure it on OMC.
Steps 1. Configure NSP.

i. Add a NSP. Click AGW Command > Services Manage-
ment > NSP Management > Create NSP (ADD NSP) in

Mandatory
– NSP name should be no more
than 64 bits
– can only be composed of
number, character, "." and
NSP Name Means NSP server name "-", before or after "-", it nsp2.agw5.com
must be character or number
– It must comply with a.b for-
mat, a and b means field,
the length of each field is
not restricted, but it should
be composed of at least two
fields.
Optional
Enable QoS Means whether to use QoS
Map parameter option

Mandatory
list, including:
– MIP
Means the mode of the the users subscribed to
Access Mode user subscribed to the NSP this NSP access to WiMAX Simple IP
accessing WiMAX network network through CMIP
or PMIP mode.
– Simple IP

mands.
2. Configure NSP Authorization Attributes.
i. Configure Simple IP pool.
Click AGW Command > Services Management > Sim-
ple IP Pool Management > Create IP Pool (ADD IP-
POOL) in MML Command from MML-Tree, as shown in
Figure 102.
FIGURE 102 ADD IPPOOL COMMAND PARAMETERS CONFIGURATION

TABLE 44 ADD IPPOOL COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction
IP Pool ID Means ID of the IP pool Optional 1

Value rang: 1~1024
Means the configured IP pool Mandatory

IP Pool name when user IP address Value range: Character IP-
Name is assigned by AGW local IP string with not more than pool_nsp2.agw5.com
pool 50 characters
Optional
Value range: 1~254
Homing VPN name of the IP If the IP pool is in a VPN,
VRF ID then the parameter is
pool
set to be the name of
VPN, otherwise no need
to configure
Input parameters according to the examples in Table 44.

Press F5 key or click Execute (F5) button to execute com-
mands.
ii. Configure IP segment in Simple IP pool.
Click AGW Command > Service Management > Simple
IP Pool Management > DHCP Proxy Address Segment
Management > Create DHCP Proxy Address Segment
(ADD DHCP PROXY IPSEG) in MML Command from
FIGURE 103 ADD DHCP PROXY IPSEG COMMAND PARAMETERS CONFIGURATION

TABLE 45 ADD DHCP PROXY IPSEG COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction
Mandatory
Value range: Character
Means the config-
string with not more
ured IP pool name
than 50 characters
IP Pool when AGW media
The value of this IPpool_nsp2.agw5.com
Name interface address
is dynamically as- parameter is the
signed locally parameter IP Pool
Name configured in
ADD IPPOOL command
Means the ID of
a IP segment in
the IP pool
Since a IP pool Mandatory
Segment ID may include multi Value range: Integer in 1
IP segments, this the range of 1~1024
parameter identifies
a IP segment in the
same IP pool
Start IP address of Mandatory, input IP ad-

Start IP Ad-
the configured address complies with IPV4 10.0.0.1
dress
dress segment format
End IP address of the Mandatory, input IP ad-

End IP Ad-
configured address dress complies with IPV4 10.0.0.254
dress
segment format
Means the subnet

mask correspond-
ing to the IP address
format
segment

mands.
iii. Configure DHCP Proxy Profile.
Click AGW Command > Service Management > Profile
Management > > DHCP Proxy Profile Management >
Create DHCP Proxy Profile (ADD DHCP PROXY PRO-
FILE) in MML Command from MML-Tree, as shown in Fig-
ure 104.

FIGURE 104 ADD DHCP PROXY PROFILE COMMAND PARAMETERS CONFIGURATION
TABLE 46 ADD DHCP PROXY PROFILE COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction

DHCP Proxy
Means DHCP Proxy Profile ID Input integer in the 1
Profile ID
range of 1~4096
Means active DNS (Domain

Optional
Name System) server IP address
Active DNS Input IP address
DNS server IP address is decided 192.168.52.100
Server Address complies with IPV4
according to onsite situation,
format
usually provided by the operator
Optional
Standby DNS Means the standby DNS Input IP address
Server Address server IP address complies with IPV4
format
Means AGW local IP pool number Mandatory

Simple IP Pool Its value is the IP Pool ID Value range: Input 1
ID configured in ADD IPPOOL integer in the range
command. of 1~4096


mands.
iv. Configure NSP authorization under Simple IP access
method.
Click AGW Command > Services Management > NSP
Management > Set NSP Authorization (SET NSP AU-
THOR) in MML Command from MML-Tree, as shown in
Figure 105.
FIGURE 105 SET NSP AUTHOR COMMAND PARAMETERS CONFIGURATION
TABLE 47 SET NSP AUTHOR COMMAND PARAMETERS INTRODUCTION
Parame-
ter
Mandatory, NSP naming rules

are as follows:
– NSP name should be not more
than 64 digits
Means NSP server name – Can only be composed of num-
NSP Name Its value is the parameter ber, character, "." and "-". Be- nsp2.agw5.com
NSP Name configured in fore or after "-", it must be
ADD NSP command character or number
– Must comply with a.b format,
a and b means segment, the
length is not restricted, but at
least two segments.

Parame-
ter
Means authorization mode

for assigning IP address
Mandatory, select from pull-down
– Set Parameter Access list, including:
Mode in ADD NSP
command to be Simple – DHCP Relay
IP, means that users Means the IP addresses of
accesses the NSP use Simple IP users accessed
Authoriza- Simple IP mode and the NSP are assigned by
the parameter is valid. DHCP Proxy
tion Mode DHCP server.
– Set Parameter Access – DHCP Proxy
Mode in ADD NSP Means the IP addresses of
command to be MIP, Simple IP users accessed
means that users ac- the NSP are assigned by
cessed the NSP use AGW local IP pool.
MIP mode and it is no
need to configure.
Mandatory, input integer in

the range of 1~4096
– When parameter Authorizat
ion Mode is set to be DHCP
Proxy, its value is the param-
eter DHCP Proxy Profile ID
Authoriza- configured by ADD DHCP
Means the ID of DHCP au-
tion Profile PROXY PROFILE command 1
thorization Profile
ID
– When parameter Authorizat
ion Mode is set to be DHCP Re-
lay, its value is the parameter
DHCP Relay Profile ID con-
figured by ADD DHCP Relay
PROFILE command

mands.
3. Configure NSP Authentication Attributes.
Click AGW Command > Service Management > Profile
Management > Radius Profile Management > Create
Radius Profile (ADD RADIUS PROFILE) in MML Com-

Optional
Radius Pro- Means the ID of AAA
file ID server
of 1~4096
Optional
VRF Means VRF ID
Primer
Means the primary AAA Mandatory, refer to the planning
Server Ad- 20.2.25.1
server address introduction in Network Planning
dress
Mandatory
Primer Means the shared key Input character string with not
Server between AAA primary more than 64 characters 0
Second
Means the secondary
AAA server address
dress

Mandatory
Server Link Means the timeout time Optional

2
Timeouts (s) of AAA server connection Input integer in the range of 1~3

3

1.3.25.159

mands.
ii. Configure NSP authentication.
Management > Set NSP Authentication (SET NSP AU-
THEN) in MML Command from MML-tree, as shown in
Figure 107.
FIGURE 107 SET NSP AUTHEN COMMAND PARAMETERS CONFIGURATION

TABLE 49 SET NSP AUTHEN COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory, input character string

in the range of 1~100 digits
Means NSP server
NSP Name Its value is the parameter nsp2.agw5.com
name
NSP Name configured in ADD
NSP command
Mandatory, input integer in the

Means the ID range of 1~4096
Authentication
of Authentication Its value is the parameter Radius 1
Profile ID
Profile Profile ID configured in ADD
RADIUS PROFILE command

mands.
4. Configure AGW Local Office Attributes.
i. Click AGW Command > System Maintenance > Lo-
cal Office Management > Local Office Attribute Man-
agement > Set Local Office AGW Attribute (SET AG-
WCFG) in MML Command from MML-Tree, as shown in
Figure 108.
FIGURE 108 SET AGW CFG COMMAND PARAMETERS CONFIGURATION

TABLE 50 SET AGW CFG COMMAND PARAMETERS CONFIGURATION INTRODUCTION

Default NSP name
character string with not more
When user is accessing than 64 characters
Default NSP AGW, if the NSP carried
The value of this parameter agw5.com
Name in the messages are
is the parameter NSP Name
wrong, then AGW uses
configured in ADD NSP
this NSP to access
command.
When user uses Simple

IP mode to access, and
AGW assigning IP address
method is DHCP Proxy,
this address is used for
AGW external interaction. Mandatory, input the IP address
complies with IPV4 formant
If it is not configured, for
Simple IP (DHCP Proxy It is set to be the signaling
DHCP Proxy IP interface address of R6 1.3.25.159
mode) users, they can
not obtain IP address interface for AGW, refer to
assigned by AGW from the planning introduction in
local IP pool normally. Network Planning.
It is the same as signaling
receiving & transmitting
address on R6 logical
interface of AGW
No need to configure
NAS ID Means NAS ID Value range: character
string with not more than
32 characters.
R4/R6 Message Means R4 and R6 mes- Optional

3
Resend Times sage resend times Value range: 1~5
R4/R6 Message Means R4 and R6 mes- Optional

3
Resend... sage resend interval Value range: 1~3
Using duration of the

IP address assigned
by AGW to MS
For Simple IP (DHCP
Proxy mode) users, AGW
works as DHCP proxy,
it assigns IP address to
DHCP users, and the IP address Default value: 86400, means
Proxy/Server can be configured with 24 hours 86400
IP Lease... using duration. If MS Value range: 60~4294967295
online activating time
exceeds the duration and
does not apply to renew
the lease, then AGW
withdraws the IP address
assigned to MS, and user
is offline automatically.


mands.
END OF STEPS
Result Configuring simple IP access function under DHCP proxy mode is

successfully complete.
Configuring Simple IP Access

Function Under DHCP Relay Mode
Context Simple IP access function is a method that AGW system supported
mobile users access WiMAX network. The IP address that the users
use to access for data communication is dynamic. Configuring
Simple IP access function under DHCP Relay mode means that
AGW uses DHCP server to assign IP address for users.
Here we use examples to introduces how to configure Simple IP
access function under DHCP Relay mode, the flow is listed as fol-
lows.
1. Configure NSP.
Add a NSP, configure its name as nsp3.agw5.com, and the ac-
cess method used for users access is Simple IP.
2. Configure authorization attributes of the NSP.
Configure NSP authorization attributes is to configure whether
AGW local IP pool or DHCP server assigns IP address for Sim-
ple IP users. Here we suppose DHCP server assigns IP address
for users. Configuring its authorization attributes includes fol-
lowing 4 steps.
i. Configure DHCP Relay external address segment.
Since the IP addresses under this mode is assigned by
DHCP server, AGW needs only to configure same address
segment with DHCP server, and distributes IP address seg-
ments to different GGUP logical boards. Here we sup-
pose configured DHCP Relay external address segment is
10.0.0.110.0.0.254, and distributes it to the GGUP logical
boards numbered as 1.
ii. Configure DHCP Relay Profile.
Configure DHCP server IP address assigning addresses for
users.
iii. Configure NSP authorization.
Configure NSP authorization means to correlate configured
DHCP Relay Profile with the NSP.


During authentication process when users access, AGW finds
the corresponding AAA Server according to users accessed NSP
and authenticates them. Configuring NSP authentication at-
tributes includes two steps, listed as follows.
Configuring Radius Profile means that when AGW commu-
nicates with AAA server, it requires to configure Radius
server address, Radius client address and shared key of
server and client.
ii. Configured NSP authentication.
Configure NSP authentication means to correlate the con-
figured Radius Profile with the NSP.
Steps 1. Configured NSP.
i. Add NSP. Click AGW Command > Services Management
> NSP Management > Create NSP (ADD NSP) in MML

Mandatory
– NSP name should be no
more than 64 bits
– can only be composed of
number, character, "." and
"-", before or after "-", it
NSP Name Means NSP server name must be character or num- nsp3.agw5.com
ber
– It must comply with a.b for-
mat, a and b means field,
the length of each field is
not restricted, but it should
be composed of at least two
fields.
Optional
Enable QoS Means whether to use QoS
Map parameter option
Mandatory
list, including:
– MIP
Means the mode of the user the users subscribed to
Access this NSP access to WiMAX
subscribed to the NSP ac- Simple IP
Mode network through CMIP
cessing WiMAX network
or PMIP mode.
– Simple IP

mands.
2. Configure NSP authorization attributes.
i. Configure DHCP Relay external address segment.
Click AGW Command > Services Management > DHCP
Relay External IP Segment Management > Create
DHCP Relay Address Segment (ADD DHCP RELAY
IPSEG) in MML Command from MML-Tree, as shown in
Figure 110.

FIGURE 110 ADD DHCP RELAY IPSEG COMMAND PARAMETERS CONFIGURATION
TABLE 52 ADD DHCP RELAY IPSEG COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction
Mandatory
Means the ID of IP segment as-
Segment ID Value range: integer in 2
signed by DHCP
the range of 1~1024
Mandatory
DHCP Relay DHCP Profile ID related to the IP
Value range: integer in 2
Profile ID segment
the range of 1~4096
Means the start IP address of the

As per the address segment Mandatory, input IP ad-
Start IP Ad-
configured on DHCP server, dress complies with IPV4 10.0.0.1
dress
configure same address segment format
on AGW, and assign it to different
GGUP logical boards.

Means the end IP address of the
End IP address dress complies with IPV4 10.0.0.254
format

Subnet mask corresponding to the
IP address segment
format

Configuration
Introduction
Logical UP
Assigned logical UP board number Mandatory 1
Board No.
Mandatory, select from

pull-down list, including:
– GiAddr
It is a kind of common
mode supported by
DHCP server
Means AGW prompts in the mes- – Link Selection
Relay Subnet sage sent to DCHP that DHCP – Ipv4 Subnet Selection GiAddr
Selection Mode server use this address segment
to assign address for users Link Selection and
Ipv4 Subnet Selection
modes should be
supported by DHCP
server, and check
onsite DHCP server
manual to judge
whether they can be
used or not
It can not be the address in the

Subnet Selec- address segment, but it should be
dress complies with IPV4 10.0.1.1
tion Hint IP in the same subnet with user ad-
format
dress segment
Optional, input character

Corresponding name of the ad-
User Alias string with not more than
dress segment
50 characters

mands.
ii. Configure DHCP Relay Profile.
Click AGW Command > Services Management > Pro-
file Management > DHCP Relay Profile Management
> Create DHCP Relay Profile (ADD DHCP RELAY PRO-
FILE) in MML Command from MML-Tree, as shown in Fig-
ure 111.

FIGURE 111 ADD DHCP RELAY PROFILE COMMAND PARAMETERS CONFIGURATION
TABLE 53 ADD DHCP RELAY PROFILE COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Parame-
ter
DHCP Re- Mandatory

Means ID of DHCP Proxy
lay Profile Value range: Input integer in the 2
Profile
ID range of 1~4096.
Mandatory
Server Ad- Means DHCP server IP ad-
Input IP address complies with 20.4.25.1
dress dress
IPV4 format
Optional
VRF Means VRF ID
If DHCP server belongs to a VRF, then
this parameter should be configured.

mands.
Click AGW Command > Services Management > Pro-
file Management > Radius Profile Management > Cre-

ate Radius Profile (ADD RADIUS PROFILE) in MML

Optional
Radius Profile Means the ID of AAA
ID server
of 1~4096
Optional
Input integer in the range
VRF Means VRF ID of 1~254
Primer Server Means the primary AAA Mandatory, refer to the planning
20.2.25.1
Address server address introduction in Network Planning
Mandatory
Means the shared key Input character string with not
Primer Server
between AAA primary more than 64 characters 0
Shared Key
server and AGW Shared key should be the same

Second
Means the secondary
AAA server address
dress
Mandatory
Means the timeout time Optional

Server Link
of AAA server connec- 2
Timeouts (s) Input integer in the range of 1~3
tion

3

1.3.25.159

mands.
ii. Configure NSP authentication.
Management > Create NSP (ADD NSP) in MML Com-
FIGURE 113 SET NSP AUTHEN COMMAND PARAMETERS CONFIGURATION

TABLE 55 SET NSP AUTHEN COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory, input character string in

Means NSP server the range of 1~100 digits
NSP Name nsp3.agw5.com
name Its value is the parameter NSP Name
configured in ADD NSP command
Mandatory, input integer in the

Authentica- range of 1~4096
Means the ID of Au-
tion Profile Its value is the parameter Radius 1
thentication Profile
ID Profile ID configured in ADD RADIUS
PROFILE command

mands.
END OF STEPS
Result Configuring simple IP access function under DHCP relay mode is

successfully complete.
Charging Function
Configuration
Introduction to Accounting Function
Configuration
Accounting Accounting is to report the users resources consumption accord-
Function ing to different granularities (time and flow) to AAA, AAA realizes
Introduction expenses calculation, and finally displays it to the users.
Accounting Mode Accounting mode supported by AGW system includes:
� IP-Session Accounting
IP-Session Accounting is that AGW charges users according to
the IP addresses obtained by MS accessing WiMAX network
successfully.
� PD-Flow Accounting
PD-Flow Accounting means that AGW calculates resources con-
sumption on each flow through PD-Flow ID and charge the
users. PD-flow ID is distributed by AAA (Under abnormal sit-
uation, if AAA does not distribute, then use locally configured
PD-flow ID by AGW).
Payment Mode According to user payment situation, AGW supports following two
payment modes:

� Offline charging
It is the so-called Postpaid Accounting, means operator pro-
vides services for users firstly, after services are completed,
then charge users.
For offline charging, AGW supports PD-Flow Accounting and
IP-Session Accounting.
� Online charging
It is the so-called Prepaid Accounting, means users prepay cer-
tain expenses, then operator provides service for them.
For online charging, AGW supports only IP-Session Accounting.
Configuring Offline Charging Function

� NSP data has been configured.
Context Offline charging is a charging method that users use services
firstly, then pay the related expenses.
In WiMAX core network, offline charging means AGW realizes
charging interaction through Radius protocol, reports accounting
information to the uses homing AAA accounting server.
Configuring offline charging function flow is shown as follows.
1. Configuring charging template.
Configure a charging template number as 1, set the charg-
ing mode corresponding to the charging template as IP Ses-
sion, which means to charge the users according to their IP
addresses.
2. Correlate the configured charging template with NSP.
Means if users access this NSP, then AGW adopts its corre-
sponding charging template to charge the users.
Steps 1. Click AGW Command > Service Management > Charg-
ing Management > Create Charging Template (ADD
CHGTPL) in MML Command from MML-Tree, as shown in
Figure 114.

Mandatory
Charging Means the ID of
Template ID charging template
the range of 1~31
Means charging
mode Optional, select from pull-down
list, including:
charging sup- � IP Session
ports IP Session Charging mode based on IP
and PD Flow two Session is that AGW charges
modes users according to the IP
Charging
Mode � Currently online
charging sup- � PD Flow
ports only IP Ses- Charging based on service
sion mode. So it flow is that AGW calculates
can only be set resources consumption on
to IP Session if each flow through PD-flow ID
charging mode is and charges users.
online charging

mands.
4. Configure NSP charging attributes. Click AGW Command >
Services Management > NSP Management > Set NSP

Charging (SET NSP ACCT) in MML Command from MML-

Tree, as shown in Figure 115.
FIGURE 115 SET NSP ACCT COMMAND PARAMETERS CONFIGURATION
TABLE 57 SET NSP ACCT COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory, and NPS naming

rules are listed as follows:
� NSP name length is not more
Means NSP than 64 digits
server name
� Can be composed only of
Its value is
number, character, "." and "-".
NSP Name the parameter nsp.agw5.com
Before or after "-", it must be
NSP Name
number or character.
configured
in ADD NSP � Must comply with a.b format,
command. a and b means segment, the
length is not restricted, but at
least there should be two seg-
ments.
Optional, value range: input

Means the integer in the range of 1~31.
Charging ID of offline Its value is the parameter 1
Template ID charging tem- Charging Template ID
plate configured in ADD CHGTPL
command

6. Press F5 button or click Execute (F5) button to execute com-

mands.
END OF STEPS
Result Configuring offline charging function is successfully complete.
Configuring Online Charging Function

� NSP data has configured.
Context Online charging is that users prepay certain amount as the calling
balance. When a establishing a call, system decides to accept or
deny the call according to users remaining balance. During call-
ing process, system realizes real-time charging and deduct cor-
responding amount from users account. When users balance is
insufficient, system cuts off the call.
Online accounting function is not the basic function provided by
AGW, which is controlled by License. If operator requires to enable
pre-pay function, online accounting function should be enabled in
License file.
Configuring flow of online charging is listed as follows.
1. Configure charging template.
Configure a charging template numbered as 1, set its corre-
sponding charging mode as IP-Session, and charge users ac-
cording to their IP addresses.
2. Configure payment mode and charging unit.
Configure its corresponding payment mode as both online and
offline charging, and configure charging unit as by flow or by
time.
3. Correlate the configured charging template and NSP.
Means if users access the NSP, then AGW adopts its corre-
sponding charging template to charge the users.
Steps 1. Configure charging mode. Click AGW Command > Services
Management > Charging Management > Create Charg-
ing Template (ADD CHGTPL) in MML Command from MML-

Mandatory
Charging Means the ID of charg-
Template ID ing template
the range of 1~31
Means charging mode Optional, select from pull-down

list, including:
charging supports � IP Session
IP Session and PD Charging mode based on IP
Flow two modes Session is that AGW charges
users according to the IP
Charging � Currently online
Mode charging supports
only IP Session � PD Flow
mode. So it can Charging based on service
only be set to IP flow is that AGW calculates
Session if charg- resources consumption on
ing mode is online each flow through PD-flow
charging ID and charges users.

mands.
4. Configure payment mode. Click AGW Command > Services
Management > Charging Management > Set Payment

Mode (SET PAYMENT MODE) in MML Command from MML-

FIGURE 117 SET PAYMENT MODE COMMAND PARAMETERS CONFIGURATION
TABLE 59 SET PAYMENT MODE COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Means the ID of Optional

Charging
charging tem- 1
Template ID Input integer in the range of 1~31
plate
Optional, select from pull-down list, including:

� online
It is the so-called Prepaid Accounting,
means the user prepay and then AGW
provides services for MS.
For online accounting, AGW currently
supports only charging mode based
Means the pay- on IP-Session.
Payment ment mode used � Offline both
Mode by charging tem-
It is the so-called Postpaid Accounting,
plate
means to provide services for MS firstly
and charge user after service is completed.
For offline accounting, AGW supports
two accounting modes, which are based
on PD-Flow and IP address.
� both
Means support online accounting and
offline accounting, and it is decided


whether accounting quota during AAA
authentication is distributed: if distributed,
then adopt online accounting; if not
distributed, then adopt offline accounting.
Optional, including;
� Flow
Charge user online payment ac-
Means Charging cording to flow
mode � Time
Online
When Payment Charge user online payment ac- Time or
Charging
Mode is set to be cording to time Flow
Support
online or both, this
parameter is valid � Time or Flow
Support to charge according to flow
or time. It is decided by parameters
distributed by PPS, if PPS supports the two
modes, then flow is used on priority.

mands.
7. Configure NSP charging attributes. Click AGW Command >
Services Management > NSP Management > Set NSP
Charging (SET NSP ACCT) in MML Command from MML-
FIGURE 118 SET NSP ACCT COMMAND PARAMETERS CONFIGURATION

TABLE 60 SET NSP ACCT COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Mandatory, and NPS naming rules

are listed as follows:
Means NSP � NSP name length is not more
server name than 64 digits
Its value is � Can be composed only of number,
NSP Name the parameter character, "." and "-". Before or nsp.agw5.com
NSP Name after "-", it must be number or
configured character.
in ADD NSP
command. � Must comply with a.b format, a
and b means segment, the length
is not restricted, but at least
there should be two segments.
Optional, value range: input integer

Means the in the range of 1~31.
Charging ID of offline
Its value is the parameter Charging 1
Template ID charging tem-
plate Template ID configured in ADD
CHGTPL command

mands.
END OF STEPS
Result Configuring online charging function is successfully complete.
Handover Function
Configuration
Introduction to Handover Function
Configuration
Description During the process of MS moving, the communication quality with
Severing BS is decreasing, while the communication quality with
Target BS is increasing, so MS releases the service flow with Sev-
ering BS and creates service flow with Target BS to continue data
transmission. The process is called handover.
During the process of MS communicating, handover may happen
in crossing BS, then BS adjacent office configuration should be
made in OMC to ensure normal handover process.

Configuring Handover Function

� Office capacity has configured.
� Parameters R4/R6 message resend times and R4/R6
message resend intveral (s) have been configured.
Context Configuring handover function includes configuring BS adjacent of-
fice and paging group data.
� Configure BS adjacent office
Configure all BS data included in AGW exchange, including BS
number, corresponding ID and forwarding data packet address
and included paging group.
� Configure paging group
Configure paging group related parameters, including paging
cycle, paging interval. When terminal enters IDLE status, AGW
distributes these parameters to MS actively.
Steps 1. Click AGW Command > System Management > Lo-
cal Office Management > Adjacent Office Direction
Management > Paging Group Management > Create
Paging Group (ADD PAGINGGRP) in MML Command from

FIGURE 119 ADD PAGINGGRP COMMAND PARAMETERS CONFIGURATION
TABLE 61 ADD PAGINGGRP COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Means the ID of pag- Mandatory

ing group, a BS can be
Paging Group ID Value range: 1~65535 1
divided into several pag-
ing groups Default value : 800
Optional
Means paging cycle
Paging Cycle (Frame) Value range: 100~10000 200
(frame)
Default value: 2
Optional
Paging Interval Means paging interval
Value range: 1~5 2
(Frame) (frame)
Default value: 3
Means paging retry times

AGW sends paging
messages to MS, if it
exceeds the time but Optional
Paging Retrys without response, then Value range: 1~3 4
AGW resends paging
messages. If resend Default value: 3
times reaches retry
times, then stop sending
paging messages.

Means the duration of

AGW sending paging
messages to BS
AGW sends paging
messages to MS, if
exceeds the time and Optional
Paging Timeout (s) 3
without response from Value range: 3~5
MS, then AGW resends
paging messages. If
resend times reach retry
paging messages.
Mandatory
Means the name of pag- Value range: character
User Alias 1
ing group string with not more than
50 characters.
Caution:
Paging Group ID, Paging Cycle, Paging Interval should be
configured the same as that in wireless side (BS side).

mands.
4. Configure BS adjacent office data. Click AGW Command >
System Management > Local Office Management > Ad-
jacent Office Direction Management > BS Office Manage-
ment > Create BS Office ( ADD BSOFC) in MML Command

FIGURE 120 ADD BSOFC COMMAND PARAMETERS CONFIGURATION
TABLE 62 ADD BSOFC COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction
Means BS num- Optional

BS Office
ber, which is self- 1
Number Value rang: 1~4096
defined by AGW.
Means BS ID,
actually it is
the BS control
Base Station interface address
Mandatory 11-11-11-11-11-11
Office ID It identifies a
unique BS in
whole WiMAX
network.

Configuration
Introduction
Means
corresponding
forward IP
address of BS
Forward Ad- adjacent office.
Mandatory 30.1.136.206
dress The forward
addresses of the
BS belonging to
the same BSC are
the same
Means the
corresponding
paging group of
the BS adjacent Optional
office Value range: 1~65535
Paging Group
Corresponding It is the Paging Group ID 1
No.
paging group of configured through ADD
each BS should be PAGINGGRP command
the same as data
configuration in
wireless side
Mandatory
Means BS adja- Value range: Character
User Alias BS1
cent office name string with not more than
50 characters.

mands.
END OF STEPS
Result Configuring handover function is successfully complete.
Paging Function
Configuration
Introduction to Paging Function
Configuration
Paging Function In order to decrease WiMAX terminal power consumption, when
there is no data to transmit for the terminal, MS or BS may trigger
MS to enter IDLE mode from Normal mode, at this time, there
is no the user’s service flow tunnel between AGW and BS. Once
there is data for user to transmit, AGW informs the user to ext

IDLE mode and enter Normal mode, then start normal service flow
transmission.
The process that AGW actively informs terminal to exit IDLE mode
and enter Normal mode under certain conditions, is called paging.
The triggering condition that AGW originates paging process to
user terminal is listed as follows.
� When MS is at IDLE status, there is downlink data from network
side to transmit to MS.
� When MS is at IDLE status, it exceeds the system configured
Idle Mode Time.
� AGW originates re-authentication flow to users.
Idle Mode Time is a parameter configured in AGW OMC, which
means the time duration that user is at IDLE status.
When the time that user is at IDLE status exceeds the system
configured Idle Mode Time, AGW allows user to carry out following
three flows, and the flow is selected by configuration in OMC.
� AGW originates paging flow.
� AGW originates location update flow.
� AGW originates user network exit flow.
Paging Principle When user is at IDLE status, there is no uplink messages, and it
can only monitor BS broadcast downlink messages in a periodical
interval, and it is not attached to a certain BS but can be paged
by a paging group.
AGW divides multi paging groups logically, the user at IDLE mode
belongs to a paging group. Once AGW requires to page the ter-
minal to exit IDLE mode and enter Normal, it can search the user
according to the homing paging group.
Relationship The range covered by a BS is about physical area concept, while
between Paging the range covered by a paging group is about logical concept, and
Group and BS the relationship between a paging group and a BS is as shown in
Figure 121.
A BS may include multi paging groups, and a BS may also belong
to multi paging groups.

FIGURE 121 RELATIONSHIP BETWEEN A PAGING GROUP AND A BS
Paging Flow The paging flow that AGW actively informs terminal to exit IDLE
mode under certain conditions is listed as follows.
1. Firstly, AGW queries the current MS homing paging group ac-
cording to the location information reported last time by MS.
2. Then, it searches all BS ID in current paging group by paging
group ID.
3. AGW finds its corresponding BSC control interface IP address
according to BS ID, and correlates it to each BSC control inter-
face IP address, then sends a paging request.
Configuring Paging Function

� Parameters R4/R6 message resend times and R4/R6
messgae resend interval (s) have been configured.
Context Configuring paging function includes the following contents.
� Configure BS adjacent office
Configure all BS data included in AGW exchange, including BS
number, corresponding ID and forwarding data packet address
and the included paging group.
� Configure paging group
Configure paging group related parameters, including paging
cycle, paging interval. When the terminal enters IDLE status,
AGW sends these parameters to MS actively.

� Configure Idle Mode Time.

� Configure the AGW handling method when users Idle Mode
Time expires.
A BS adjacent office can include several paging group PGID (maxi-
mally 6), BS adjacent office can create 4096 maximally, and a pag-
ing group can include multi BS adjacent offices (maximally 300).
Steps 1. Click AGW Command > System Management > Local Of-
fice Management > Adjacent Office Direction Manage-
ment > Paging Group Management > Creating Paging
Group (ADD PAGINGGRP) in MML Command from MML-
FIGURE 122 ADD PAGINGGRP COMMAND PARAMETERS CONFIGURATION
TABLE 63 ADD PAGINGGRP COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Means the ID of pag- Mandatory

ing group, a BS can be
Paging Group ID Value range: 1~65535 1
divided into several pag-
ing groups Default value : 800
Optional
Means paging cycle
Paging Cycle (Frame) Value range: 100~10000 200
(frame)
Default value: 2

Optional
Paging Interval Means paging interval
Value range: 1~5 2
(Frame) (frame)
Default value: 3
Means paging retry times

AGW sends paging
messages to MS, if it
exceeds the time but Optional
Paging Retrys without response, then Value range: 1~3 4
AGW resends paging
messages. If resend Default value: 3
times reaches retry
paging messages.
Means the duration of

AGW sending paging
messages to BS
AGW sends paging
messages to MS, if
exceeds the time and Optional
Paging Timeout (s) 3
without response from Value range: 3~5
MS, then AGW resends
paging messages. If
resend times reach retry
paging messages.
Mandatory
Means the name of pag- Value range: character
User Alias 1
ing group string with not more than
50 characters.
Caution:
Parameters Paging Group, Paging Cycle, Paging Interval
should be the same as that in wireless side (BS side).

mands.
4. Configure BS adjacent office data. Click AGW Command >
System Management > Local Office Management > Ad-
jacent Office Direction Management > BS Office Manage-
ment > Create BS Office (ADD BSOFC) in MML Command

FIGURE 123 ADD BSOFC COMMAND PARAMETERS CONFIGURATION
TABLE 64 ADD BSOFC COMMAND PARAMETERS CONFIGURATION INTRODUCTION
Configuration
Introduction
BS Office Num- Means BS number, which is self- Optional

1
ber defined by AGW. Value rang: 1~4096
Means BS ID, actually it is

Base Station the BS address 11-11-11-11-
Mandatory
Office ID It identifies a unique BS in 11-11
whole WiMAX network.
Means corresponding forward

IP address of BS adjacent office.
Forward Ad-
The forward addresses of the Mandatory 30.1.136.206
dress
BS belonging to the same
BSC are the same
Means the corresponding Optional

paging group of the BS
adjacent office Value range: 1~65535
Paging Group It is the Paging Group
Corresponding paging group 1
No. ID configured through
of each BS should be the
same as data configuration ADD PAGINGGRP
in wireless side command

Configuration
Introduction
Mandatory
User Alias Means BS adjacent office name Value range: Character BS1
string with not more
than 50 characters.

mands.
7. Click Views > Professional Maintenance from OMC main
interface, enter professional maintenance interface, as shown
in Figure 124.
FIGURE 124 PROFESSIONAL MAINTENANCE INTERFACE
8. Click the menu Variables Control > AGW Parameter from

navigation tree on the left, enter AGW parameter configuration
interface.
9. Configure parameter Idle Mode Time according to actual sit-
uation, as shown in Figure 125.

FIGURE 125 IDLE MODE TIME PARAMETERS CONFIGURATION
10. Configure parameter Idle Mode Timer Expired according to

actual situation, as shown in Figure 126.

FIGURE 126 IDLE MODE TIMER EXPIRED PARAMETERS CONFIGURATION
TABLE 65 IDLE MODE TIMER EXPIRED PARAMETERS CONFIGURATION INTRODUCTION
Select from pull-down list, includ-

ing:
� Network Exit
Means when user IDLE status
Means that when expires, AGW deletes user
the time that MS data and user is exited
is at IDLE status
Idle Mode � Paging for LU
exceeds the con-
Timer Ex- Paging for LU
figured parameter Means when user IDLE status
pired
Idle Mode Time, expires, AGW pages user and
the handling car- triggers location update flow
ried out by system � Paging for IM Exit
Means when user IDLE status
expires, AGW pages user
and user exits Idle status
and enters Normal status
END OF STEPS
Result Configuring paging function is successfully complete.

Figures
Figure 1 Network Planning Schematic Diagram of WiMAX

system.............................................................. 2
Figure 2 Interfaces and Addresses Configured by Exchanges .... 2
Figure 3 AGW Data Configuration Flow .................................. 5
Figure 4 MML Terminal ........................................................ 7
Figure 5 ADD NE ................................................................ 8
Figure 6 Inputting Parameters in Textbox............................... 9
Figure 7 ADD NE Command Execute Result ...........................10
Figure 8 User Login Interface ..............................................12
Figure 9 AGW OMC Interface...............................................13
Figure 10 MML Terminal......................................................14
Figure 11 ADD NE Command Parameters Configuration..........15
Figure 12 Add AGW-5 Exchange Successfully ........................16
Figure 13 Standard Configuration for AGW Single-shelf
(BPSNE) ...........................................................18
Figure 14 Typical Configuration for AGW Dual-shelf (BCTC) .....18
Figure 15 Typical Configuration for AGW Dual-shelf (BPSNE)....19
Figure 16 ADD RACK Command Parameters Configuration .....22
Figure 17 Rack Configuration Prompt for Single-shelf
Configuration ....................................................23
Figure 18 ADD SHELF Parameters Configuration ...................24
Figure 19 OMP Module and RPU Module Creating Successfully...26
Figure 20 OMP Board Created Successfully............................27
Figure 21 Query Attribute of Module 1 ..................................28
Figure 22 Query Attribute of Module 2 ..................................29
Figure 23 ADD UNIT Command Parameters Configuration ......30
Figure 24 All Boards Are Created Successfully .......................34
Figure 25 SET SUNIT Command Parameters Configuration ......35
Figure 26 SET MODULE Parameters Configuration.................37
Figure 27 Modify OMP Attributes Successfully ........................38
Figure 28 SET OMP Command Parameters Configuration ........39
Figure 29 Configure OMP Attributes Successfully....................40
Figure 30 ADD MP Parameters Configuration (Add SMP
Module)............................................................41

Figure 31 Add SMP Module Successfully ................................43

Figure 32 INTERFACE Command Parameters Configuration ....47
Figure 33 Enter Interface Mode ...........................................48
Figure 34 Query Port Under Current Mode.............................49
Figure 35 ADD IP ADDRESS Command Parameters
Configuration ....................................................50
Figure 36 SAVE ONLINEDATA Command ............................51
Figure 37 SET SIGIP R6 Command Parameters
Configuration ....................................................52
Figure 38 ADD LOGICUP Command Parameters
Configuration ....................................................53
Figure 39 INTERFACE LOOPBACK Command Parameters
Configuration ....................................................54
Figure 40 Enter Interface Configuration Mode ........................55
Figure 41 ADD IP ADDRESS Command Parameters
Configuration ....................................................56
Figure 42 Loading Version Files Operation Flow......................60
Figure 43 Version Maintenance Main Interface ...................62
Figure 44 Config Version Path Interface ................................63
Figure 45 Create Version and Version Path ............................64
Figure 46 Hyper Terminal Starting Interface ..........................67
Figure 47 Port Select..........................................................67
Figure 48 Com1 Properties Configuration ..............................68
Figure 49 Stop OMP Auto Starting........................................69
Figure 50 BootMode Selection .............................................69
Figure 51 Config Selection ..................................................70
Figure 52 Enter OMP’s OMC IP Address .................................70
Figure 53 Enter OMP’s OMC Mac Address ..............................71
Figure 54 Enter OMP’s Gateway IP Address ...........................72
Figure 55 Config Selection Interface.....................................72
Figure 56 OMC IP Address ..................................................73
Figure 57 FTP Config ..........................................................73
Figure 58 Ompcfg File Name ...............................................74
Figure 59 Set Omp Boot Type Interface ................................74
Figure 60 Set Bureau No. ...................................................75
Figure 61 3GPlat Boot ........................................................75
Figure 62 ACTIVE LICENSE Command Configuration ............80
Figure 63 ACTIVE LICENSE Successful ...............................81
Figure 64 SET AGWCAP Command Parameters Configuration...82
Figure 65 SET AGWCAP Command Execution Result .............83

Figures
Figure 66 SET AGW CFG Command Parameters

Configuration ....................................................85
Figure 67 Signaling Interface Load Sharing Based on MSID .....88
Figure 68 User Media Interface Data Load Sharing .................88
Figure 69 INIT SMP SHARE LOAD Parameters Configuration...91
Figure 70 INIT SMP SHARE LOAD Command Result.............93
Configuration ....................................................94
Figure 72 BLD UP LOADSHARE Command Parameters
Configuration ....................................................95
Figure 73 ADD DHCP RELAY IPSEG Command Parameters
Configuration ....................................................98
Figure 74 ADD IPPOOL Command Parameters
Configuration .................................................. 100
Figure 75 ADD DHCP PROXY IPSEG Command Parameters
Configuration .................................................. 101
Figure 76 ADD DHCP RELAY PROFILE Command
Parameters Configuration ................................. 103
Figure 77 ADD RADIUS PROFILE Command Parameters
Configuration .................................................. 105
Figure 78 ADD DHCP PROXY PROFILE Command
Figure 79 SET FA Command Parameters Configuration ......... 108
Figure 80 SET FA Command Parameters Configuration
Result ............................................................ 110
Figure 81 ADD NSP Command Parameters Configuration ..... 111
Figure 82 ADD NSP Command Result ................................ 112
Figure 83 ADD CHGTPL Command Parameters
Configuration .................................................. 114
Figure 84 SET PAYMENT MODE Command Parameters
Configuration .................................................. 116
Figure 85 ADD SFQOS Command Configuration .................. 119
Figure 86 ADD SERVFLOW Command ............................... 120
Figure 87 ADD SERVFLOW PKGCLSRULE Command .......... 121
Figure 88 SYNA Command Parameters Configuration ........... 126
Figure 89 SHOW CHG Command Parameters Configuration
..................................................................... 128
Figure 90 SYNA Command Parameters Configuration
(Changed Tables) ............................................ 129
Figure 91 CMIP Access Flow .............................................. 132

Figure 92 PMIP Method Based on DHCP Relay...................... 133

Figure 93 PMIP Method Based on DHCP Proxy...................... 133
Figure 94 ADD NSP Command Parameters Configuration ..... 135
Figure 95 ADD NSP Command Parameters Configuration
Result ............................................................ 136
Figure 96 SET FA Command Parameters Configuration ......... 137
Figure 97 SET FA Command Parameters Configuration
Result ............................................................ 138
Configuration .................................................. 139
Figure 99 Simple IP (DHCP Proxy) Flow .............................. 141
Figure 100 Simple IP (DHCP Relay) Flow............................. 141
Figure 101 ADD NSP Command Parameters Configuration.... 144
Figure 102 ADD IPPOOL Command Parameters
Configuration .................................................. 145
Figure 103 ADD DHCP PROXY IPSEG Command Parameters
Configuration .................................................. 146
Figure 104 ADD DHCP PROXY PROFILE Command
Figure 105 SET NSP AUTHOR Command Parameters
Configuration .................................................. 149
Configuration .................................................. 151
Figure 107 SET NSP AUTHEN Command Parameters
Configuration .................................................. 152
Figure 108 SET AGW CFG Command Parameters
Configuration .................................................. 153
Figure 109 ADD NSP Command Parameters Configuration.... 156
Figure 110 ADD DHCP RELAY IPSEG Command Parameters
Configuration .................................................. 158
Figure 111 ADD DHCP RELAY PROFILE Command
Configuration .................................................. 161
Figure 113 SET NSP AUTHEN Command Parameters
Configuration .................................................. 162
Configuration .................................................. 165
Figure 115 SET NSP ACCT Command Parameters
Configuration .................................................. 166

Figures

Configuration .................................................. 168
Figure 117 SET PAYMENT MODE Command Parameters
Configuration .................................................. 169
Figure 118 SET NSP ACCT Command Parameters
Configuration .................................................. 170
Figure 119 ADD PAGINGGRP Command Parameters
Configuration .................................................. 173
Figure 120 ADD BSOFC Command Parameters
Configuration .................................................. 175
Figure 121 Relationship between A Paging Group and A BS ... 178
Figure 122 ADD PAGINGGRP Command Parameters
Configuration .................................................. 179
Figure 123 ADD BSOFC Command Parameters
Configuration .................................................. 181
Figure 124 Professional Maintenance Interface .................... 182
Figure 125 Idle Mode Time Parameters Configuration ......... 183
Figure 126 Idle Mode Timer Expired Parameters
Configuration .................................................. 184


Tables
Table 1 WiMAX System Network Address Planning Introduction .. 3

Table 2 Parameters in Login Interface...................................12
Table 3 ADD NE Command Parameters Configuration
Explanation.......................................................15
Table 4 AGW Front Board Configuration ................................19
Table 5 AGW Single-shelf Rear Board Configuration ................20
Table 6 ADD RACK Command Parameters Configuration
Explanation.......................................................22
Table 7 ADD SHELF Command Parameters Configuration
Introduction......................................................24
Table 8 ADD UNIT Command Parameters Configuration
Explanation.......................................................30
Table 9 Corresponding Board Type and Backup Mode
Parameters Configuration Introduction..................33
Table 10 SET MODULE Command Parameters Configuration
Introduction......................................................37
Table 11 SET OMP Command Parameters Configuration
Introduction......................................................39
Table 12 ADD MP Command Parameters Configuration
Introduction......................................................41
Table 13 INTERFACE Command Parameters Configuration
Introduction......................................................47
Table 14 ADD IP ADDRESS Command Parameters
Configuration Introduction (Configuring R6
interface address of AGW with BS side) ................50
Table 15 SET SIGIP R6 Command Parameters Configuration
Introduction......................................................53
Table 16 ADD LOGICUP Command Parameters Configuration
Introduction......................................................53
Table 17 INTERFACE LOOPBACK Command Parameters
Configuration Introduction (R3 Media Interface
Address) ..........................................................55

Table 18 ADD IP ADDRESS Command Parameters

Configuration Introduction (Configuring R3
Interface .................................................... 56
Table 19 Version Maintenance Icons Introduction ...............62
Table 20 AGW Foreground Version Software List ....................77
Table 21 SET AGWCAP Command Parameters Configuration
Introduction......................................................83
Table 22 SET AGW CFG Command Parameters Configuration
Introduction......................................................85
Table 23 INIT SMP SHARE LOAD Command Parameters
Configuration Introduction ..................................92
Introduction......................................................94
Table 25 ADD DHCP RELAY IPSEG Command Parameters
Configuration Introduction ..................................98
Table 26 ADD IPPOOL Command Parameters Configuration
Introduction.................................................... 100
Table 27 ADD DHCP PROXY IPSEG Command Parameters
Configuration Introduction ................................ 102
Table 28 ADD DHCP RELAY PROFILE Command Parameters
Table 29 ADD RADIUS PROFILE Command Parameters
Table 30 ADD DHCP PROXY PROFILE Command
Parameters Configuration Introduction................ 107
Table 31 SET FA Command Parameters Configuration
Introduction.................................................... 109
Table 32 ADD NSP Command Parameters Configuration
Introduction.................................................... 111
Table 33 ADD CHGTPL Command Parameters Configuration
Introduction.................................................... 114
Table 34 SET PAYMENT MODE Command Parameters
Table 35 Parameters in ADD SFQOS Command
Configuration .................................................. 119
Table 36 Parameters in ADD SERVFLOW Command
Configuration .................................................. 121
Table 37 Parameters in ADD SERVFLOW PKGCLSRULE
Command Configuration ................................... 122

Tables
Table 38 SYNA Command Parameters Configuration

Introduction.................................................... 126
Table 39 SYNA Command Parameters Configuration
Introduction (Changed Tables)........................... 129
Introduction.................................................... 135
Table 41 SET FA Command Parameters Configuration
Introduction.................................................... 137
Introduction.................................................... 139
Introduction.................................................... 144
Table 44 ADD IPPOOL Command Parameters Configuration
Introduction.................................................... 146
Table 45 ADD DHCP PROXY IPSEG Command Parameters
Table 46 ADD DHCP PROXY PROFILE Command
Parameters Configuration Introduction................ 148
Table 47 SET NSP AUTHOR Command Parameters
Introduction.................................................... 149
Table 49 SET NSP AUTHEN Command Parameters
Table 50 SET AGW CFG Command Parameters Configuration
Introduction.................................................... 154
Introduction.................................................... 157
Table 52 ADD DHCP RELAY IPSEG Command Parameters
Table 53 ADD DHCP RELAY PROFILE Command Parameters
Table 55 SET NSP AUTHEN Command Parameters
Introduction.................................................... 165
Table 57 SET NSP ACCT Command Parameters Configuration
Introduction.................................................... 166


Introduction.................................................... 168
Table 59 SET PAYMENT MODE Command Parameters
Table 60 SET NSP ACCT Command Parameters Configuration
Introduction.................................................... 171
Table 61 ADD PAGINGGRP Command Parameters
Table 62 ADD BSOFC Command Parameters Configuration
Introduction.................................................... 175
Table 63 ADD PAGINGGRP Command Parameters
Table 64 ADD BSOFC Command Parameters Configuration
Introduction.................................................... 181
Table 65 Idle Mode Timer Expired Parameters

List of Glossary
AAA - Authentication, Authorization, Accounting

AGW - ASN Gateway ASN
ASN - Access Service Network
BCTC - Backplane of ConTrol Center
BS - Base Station
BSC - Base Station Controller
CMIP - Client Mobile IP IP
COA - Care Of Address
CSN - Connectivity Services Network
DHCP - Dynamic Host Configuration Protocol
DNS - Domain Name System
FA - Foreign Agent
FPGA - Field Programmable Gate Arrays
FTP - File Transportation Protocol
GE - Giga Ethernet
GGLP - AGW Line Processor of GE interfaceGi/Gn
GGUP - AGW GTP-U ProcessorGTP-U
GRE - Generic Routing Encapsulation
HA - Home Agent
ISF - Initial Server Flow
L2TP - Layer2 Tunnel Protocol 2
MIP - Mobile IP IP
MSID - Mobile Station Identifier
NSP - Network Service Provider
OMC - Operations & Maintenance Center
OMP - Operation Main Processor
PMIP - Proxy-Mobile IP IP
PSN - Packet Switch Network
RADIUS - Remote Authentication Dial In User Service
RMNIC - Rear Board of Multi-service Network Interface
Card
RMPB - Rear board of Main Processor BoardMP
RPSN - Rear Card for PSN4VPSN
RPU - Router Pocess Unit
RUIM2 - Rear board of UIM (type2)DUIM 2

RUIM3 - Rear board of UIM (type3)DUIM 3

SMP - Service Main Processor
UIM - Universal Interface Module
WiMAX - Worldwide Interoperability for Microware Access

sjzl20091238-ZXMBW AGW (V3 (1) .08.10) Configuration Guide PDF

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

sjzl20091238-ZXMBW AGW (V3 (1) .08.10) Configuration Guide PDF

Uploaded by

Copyright:

Available Formats

ZXMBW AGW

WiMAX Wireless Access Gateway

Copyright © 2006 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision No. Revision Date Revision Reason

Serial Number: sjzl20091238

Purpose This manual provides procedures and guidelines for configuring

Chapter 1, AGW Data This chapter introduces the network planning,

This chapter introduces how to configure

Chapter 3, Loading This chapter introduces how to load AGW ver-

Chapter 4, AGW Local This chapter introduces how to configure

This chapter introduces how to configure

Chapter 6, AGW Service This chapter introduces AGW service data

This chapter introduces AGW IP protocol

Chapter 8, AGW Data

Chapter 9, AGW Serv-

Confidential and Proprietary Information of ZTE CORPORATION i

This page is intentionally blank.

ii Confidential and Proprietary Information of ZTE CORPORATION

AGW Data Configuration

Confidential and Proprietary Information of ZTE CORPORATION 1

FIGURE 1 NETWORK PLANNING SCHEMATIC DIAGRAM OF WIMAX SYSTEM

Network Address Network address planning of WiMAX system is as shown in Figure

FIGURE 2 INTERFACES AND ADDRESSES CONFIGURED BY EXCHANGES

2 Confidential and Proprietary Information of ZTE CORPORATION

Parameters in Figure 2 are introduced as follows:

TABLE 1 WIMAX SYSTEM NETWORK ADDRESS PLANNING INTRODUCTION

Interface IP Address Connected

It is the physical inter-

It is the physical inter-

AGW R3 interface does not dif-

Used for communication

Used for communication

Confidential and Proprietary Information of ZTE CORPORATION 3

Interface IP Address Connected

Used for communication

IP Address of X means the exchanges

DHCP Server 20.4.25.1 AGW R3 interface

HA 20.3.25.18 AGW R3 interface

192.168.51.253 AGW OMC server

AGW Data Configuration

4 Confidential and Proprietary Information of ZTE CORPORATION

Data Configura- AGW data configuration flow is as shown in Figure 3.

Confidential and Proprietary Information of ZTE CORPORATION 5

AGW Data Configuration

6 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 4 MML TERMINAL

Confidential and Proprietary Information of ZTE CORPORATION 7

Introduction Besides configuring data by inputting command lines, the same

8 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 6 INPUTTING PARAMETERS IN TEXTBOX

Confidential and Proprietary Information of ZTE CORPORATION 9

FIGURE 7 ADD NE COMMAND EXECUTE RESULT

10 Confidential and Proprietary Information of ZTE CORPORATION

AGW Physical Data

Creating AGW Exchanges

Confidential and Proprietary Information of ZTE CORPORATION 11

FIGURE 8 USER LOGIN INTERFACE

Parameters in Figure 8 are explained in Table 2.

TABLE 2 PARAMETERS IN LOGIN INTERFACE

Parameter Explanation Example

Corresponding password for the It is empty as

Server Address OMC server address 192.168.51.129