Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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
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.
Revision History
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
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
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
Cluster Serv-
AAA Server 20.2.25.1 AGW R3 interface
ice Address
DBIO/ZTE
192.168.52.134
Gateway
Interface with
192.168.51.129
AGW OMC client
OMC Server AGW
Interface with
129.0.31.129
OMP board
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.
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 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.
Table of Contents
Creating AGW Exchanges ...................................................11
AGW Hardware Data Configuration.......................................17
It is admin as
User Name User name for user login
default
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.
no more than 50 characters
It is optional.
It means the self-defined
User Label Value range: Character string AGW-5
user label.
no more than 50 characters
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
Single-shelf network:
boards can be
inserted in slot 1~6
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)
inserted in slot 1~6
and slot 9–14 in
BPSNE shelf
Redun-
Logical
Name dancy Quantity Function Remarks
Board
Mode
Single-shelf network:
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
Single-shelf network:
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
Single-shelf network:
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.
Logical
Quantity Function Remarks
Board
Logical
Quantity Function Remarks
Board
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.
� Foreground devices are operating normally.
� Oracle database is working 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
shown in Figure 16 appears.
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
Result For single-shelf configuration, system prompts that the rack No.
to be added already exists, as shown in Figure 17.
Configuring a Shelf
Prerequisites � OMC client and server are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working 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
shown in Figure 18 appears.
Param-
Explanation Configuration Introduction Example
eter
Param-
Explanation Configuration Introduction Example
eter
It is optional
Means user defined shelf
Alias Value range: character string with
name
no more than 50 characters
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.
Configuring a Unit
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� AGW exchange has been created.
� 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.
Configuration
Parameter Explanation Example
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
Parameter Explanation Example
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.
SDTB Attrib-
SDTB Attribute Optional, use default value
ute
APBE/IMA At-
APBE/IMA Attribute Optional, use default value
tribute
Configuration
Parameter Explanation Example
Introduction
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
TDM Bus Type TDM Bus Type Optional, use default value
E3/T3 Attrib-
E3/T3 Attribute Optional, use default value
ute
Optional
User self-defined logical Value range: Character
Alias
board name strings with not more than
50 characters.
ONEPLUSONE
UIM Slot 15 and 16 UIM (UIM2_GCS_755)
(1+1 backup)
LOADSHARE (Load
PSN Slot 7 and 8 PSN4V
sharing backup)
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.
Result After adding a unit, query the configured boards through click-
ing Views > Daily Maintenance > Rackchart Management,
as shown in Figure 24.
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 >
Configuring a Module
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� AGW exchange has been created.
� 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.
Note:
Creating SMP module should be after creating UIM unit,
otherwise it can not be created successfully.
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.
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
OMC Server
IP address of OMC Mandatory, input IP address complies
SUBNET 172.18.5.129
server with IPV4 address formant
Address
Parame-
Explanation Configuration Introduction Example
ter
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-
Explanation Configuration Introduction Example
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
more than 50 characters
Optional
Module 2 User self-defined
User Alias module 2 name Value range: Character strings with not
more than 50 characters
END OF STEPS
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.
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
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� 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.
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
Caution:
MML commands under interface mode are different from the
MML commands under normal mode.
Configuration
Parameter Explanation Example
Introduction
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.
END OF STEPS
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.
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.
Mandatory
Logical It means logical board num-
Input integer in the range 1
Board No. ber of GGUP board
of 1~255
Param-
Explanation Configuration Introduction Example
eter
Configuration
Parameter Explanation Example
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
introduction in Network
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-
Input IP address complies 255.255.255.255
dress dress for the interface
with IPV4 format
Optional
CORBA ID Means CORBA ID Input integer in the range
of 1~65535
Table of Contents
Flow of Loading Version Files...............................................60
Loading OMP Version Files ..................................................61
Icon Introduction
Refresh
Close All
Icon Introduction
Import
Note:
After add, delete or modify version files path, the configura-
tions come into effect only after saving them.
END OF STEPS
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.
8. Input 1 as the prompt, press Enter key, and enter Config Se-
lection interface, as shown in Figure 51.
13. Input 2 as the prompt, press Enter key, and enter OMC Ip
address interface, as shown in Figure 56.
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.
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.
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.
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.
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.
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
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
GGSN_XPB_GGLP_XLR_ZXMBW-AGW_Z_T.BIN
GGSN_XPB_GGUP_XLR_1_ZXMBW-
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
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
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.
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.
Table of Contents
Activating License..............................................................79
Configuring AGW Exchanges Capacity...................................81
Configuring AGW Exchanges Attributes .................................84
Activating License
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� Physical data configuration has been completed.
� 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.
Result System enters the interface as shown in Figure 63, means License
activation is successful.
Configuring AGW
Exchanges Capacity
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� Physical data configuration has been completed.
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
Configuration
Parameter Explanation Example
Introduction
Configuring AGW
Exchanges Attributes
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� Physical data configuration has been completed.
� 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.
No need to configure
NAS ID Means NAS ID Value range: character string with
not more than 32 characters.
Table of Contents
Introduction to Load Sharing Configuration ...........................87
Configuring SMP Control Interface Load Sharing ....................90
Configuring GGUP Media Interface Load Sharing ....................93
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.
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.
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
Parame-
Explanation Configuration Introduction Example
ter
Mandatory
Logical Means logical board number of
Input integer in the range 1
Board No. GGUP board
of 1~255
Parame-
Explanation Configuration Introduction Example
ter
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
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� Physical data configuration has been completed.
� 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
MML Command from MML-Tree, as shown in Figure 73.
Configuration
Parameter Explanation Example
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
Configuration
Parameter Explanation Example
Introduction
Logical UP
Assigned logical UP board number Mandatory 1
Board No.
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.
Configuration
Parameter Explanation Example
Introduction
Configuration
Parameter Explanation Example
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
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
Configuring Profile
Configuring DHCP Relay Profile
Prerequisites � OMC server and client are connecting normally.
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-
Input IP address complies 192.168.52.100
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.
Optional
Radius Pro- Means the ID of AAA
Input integer in the range 1
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
Input integer in the range of 1~64
Server between AAA secondary 1
Shared Key server and AGW Shared key should be the same
as that configured in AAA
Configuration
Parameter Explanation Example
Introduction
Optional
Standby DNS Means the standby DNS Input IP address
Server Address server IP address complies with IPV4
format
Configuring FA
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� Physical data configuration has been completed.
� Office capacity has been configured.
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
MML-Tree, as shown in Figure 79.
Configuring NSP
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� Physical data configuration has been completed.
� Office capacity has been configured.
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.
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
Select from the pull-down
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.
Mandatory
Charging Means the ID of charg-
Value range: Input integer in 1
Template ID ing template
the range of 1~31
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.
� 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.
Steps 1. Click AGW Command > Services Management > Profile
Management > Service Flow QoS Profile Management >
Creating Service Flow QoS Profile in MML Command, as
shown in Figure 85.
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.
Optional
Service Flow
Service Flow ID Value range: Character string with not more than
ID
50 characters.
Mandatory
QoS Profile
QoS Profile ID It is the parameter QoS Profile ID configured
ID
through ADD SFQOS command, refer to Table 35.
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
Value range: Integer in the range of 0~255.
Optional
Protocol Type Protocol Type
Value range: Integer in the range of 0~255.
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.
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.
Optional
Means self-defined user
User Name Value range: Character string
name
with not more than 50 characters
Optional
Means the module to be
Module List No inputting means to select 3&4
synchronized
all modules
Synchronizing Changed
Tables
Prerequisites � OMC server and client are connecting normally.
� Foreground devices are operating normally.
� Oracle database is working normally.
� Physical data configuration has been completed.
� Office capacity has been configured.
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
MML-Tree, as shown in Figure 89.
Optional
Means self-defined
User name Value range: Character string with
user name
not more than 50 characters
Optional
Means the module to
Module List No inputting means to select 3&4
be synchronized
all modules
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
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
Mandatory
NSP naming rules are as follows:
� 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
Select from the pull-down list, NO
Map QoS parameter option
including YES and NO
Mandatory
Select from the pull-down
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
Means AGW supports that
the users subscribed to this
NSP use Simple IP mode to
access WiMAX network.
Parame-
Explanation Configuration Introduction Example
ter
Parame-
Explanation Configuration Introduction Example
ter
Configuration
Parameter Explanation Example
Introduction
Mandatory
Logical Board Means logical board number of
Input integer in the range 1
No. GGUP board
of 1~255
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.
Mandatory
NSP naming rules are as follows:
– 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
Select from the pull-down list, NO
Map parameter option
including YES and NO
Mandatory
Select from the pull-down
list, including:
– MIP
Means AGW supports that
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
Means AGW supports that
the users subscribed to this
NSP use Simple IP mode to
access WiMAX network.
Configuration
Parameter Explanation Example
Introduction
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
Configuration
Parameter Explanation Example
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
Configuration
Parameter Explanation Example
Introduction
Optional
Standby DNS Means the standby DNS Input IP address
Server Address server IP address complies with IPV4
format
Parame-
Explanation Configuration Introduction Example
ter
Parame-
Explanation Configuration Introduction Example
ter
Optional
Radius Pro- Means the ID of AAA
Input integer in the range 1
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
Input integer in the range of 1~64
Server between AAA secondary 0
Shared Key server and AGW Shared key should be the same
as that configured in AAA
No need to configure
NAS ID Means NAS ID Value range: character
string with not more than
32 characters.
Mandatory
NSP naming rules are as follows:
– 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
Select from the pull-down list, NO
Map parameter option
including YES and NO
Mandatory
Select from the pull-down
list, including:
– MIP
Means AGW supports that
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
Means AGW supports that
the users subscribed to this
NSP use Simple IP mode to
access WiMAX network.
Configuration
Parameter Explanation Example
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
Configuration
Parameter Explanation Example
Introduction
Logical UP
Assigned logical UP board number Mandatory 1
Board No.
Parame-
Explanation Configuration Introduction Example
ter
Mandatory
Server Ad- Means DHCP server IP ad-
Input IP address complies with 20.4.25.1
dress dress
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.
Optional
Radius Profile Means the ID of AAA
Input integer in the range 1
ID server
of 1~4096
Optional
Input integer in the range
VRF Means VRF ID of 1~254
If AAA server belongs to a VRF,
then this parameter should be set
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
as that configured in AAA
Second
Means the secondary
Server Ad- Mandatory
AAA server address
dress
Mandatory
Second Means the shared key
Input integer in the range of 1~64
Server between AAA secondary 1
Shared Key server and AGW Shared key should be the same
as that configured in AAA
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.
Mandatory
Charging Means the ID of
Value range: Input integer in 1
Template ID charging template
the range of 1~31
Means charging
mode Optional, select from pull-down
list, including:
� Currently offline
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
addresses obtained by MS. PD Flow
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
Mandatory
Charging Means the ID of charg-
Value range: Input integer in 1
Template ID ing template
the range of 1~31
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.
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.
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
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).
Configuration
Parameter Explanation Example
Introduction
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
Parameter Explanation Example
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.
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.
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.
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
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).
Configuration
Parameter Explanation Example
Introduction
Configuration
Parameter Explanation Example
Introduction
Mandatory
User Alias Means BS adjacent office name Value range: Character BS1
string with not more
than 50 characters.
END OF STEPS