Академический Документы
Профессиональный Документы
Культура Документы
AAA Server
Billing
Version 3.06.11
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@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 CORPORATION 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 disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. 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
Document
ZXMBW AAA AAA Server Billing
Name
Document Revision
Product Version V3.06.11 R1.0
Number
Equipment
Serial No. sjzl20073190
Installation Date
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good
Fair
Average
Poor
Bad
N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good
Fair
Average
Poor
Bad
N/A
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction
Make it more concise/brief
Improve the Contents
Add more step-by-step procedures/tutorials
Improve the organization
Add more troubleshooting information
Include more figures
Make it less technical
Your
Add more examples
Add more/better quick reference aids
suggestions for
Add more detail
Improve the index
improvement of
this
Other suggestions
documentation __________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.
Contents
Chapter 1.......................................................................... 1
Chapter 2........................................................................ 17
Bill Data.......................................................................... 17
Overview ........................................................................... 17
Usage Data Record (UDR) .................................................... 17
Additional Billing Record ...................................................... 21
UDR Format ....................................................................... 21
Bill Format .........................................................................29
Detailed Bill ........................................................................33
Normal Bill .........................................................................34
Chapter 3........................................................................ 37
Bill Transmission............................................................ 37
Overview ...........................................................................37
Bill Transmission .................................................................37
Configuring FTP Site ............................................................37
Setting FTP Site ..................................................................40
Appendix A ..................................................................... 45
Abbreviations ................................................................. 45
Glossary.......................................................................... 49
Figures............................................................................ 51
Table............................................................................... 53
Index .............................................................................. 55
About This Manual
Purpose
This manual provides the information of AAA Server billing
system.
Intended Audience
This manual is intended for engineers and technicians who
perform operation activities on AAA Server billing system.
Chapter Summary
Chapter 1, Billing Introduces the billing process and billing
System system configuration.
Chapter 2, Bill Data Introduces the bill format and types.
Chapter 3, Bill Introduces the procedure for bill
Transmission transmission and setting FTP site.
Related Documentation
The following documentation is related to this manual:
ZXMBW AAA (V3.06.11) AAA Server Technical Description
ZXMBW AAA (V3.06.11) AAA Server Hardware Installation
ZXMBW AAA (V3.06.11) AAA Server Software Installation
ZXMBW AAA (V3.06.11) AAA Server Agent
ZXMBW AAA (V3.06.11) AAA Server Configuration
ZXMBW AAA (V3.06.11) AAA Server Routine Maintenance
ZXMBW AAA (V3.06.11) AAA Server Performance Monitoring
and Alarm Information
Conventions
Typographical ZTE documents employ the following typographical conventions.
Conventions
TABLE 2 TYPOGRAPHICAL CONVENTIONS
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens
and company name.
Constant width Text that you type, program code, files and
directory names, and function names.
Billing System
Overview
Introduction This chapter briefly introduces the billing process and billing
system configuration.
Contents This chapter contains the following topics.
AAA Server
Introduction Authentication, Authorization and Accounting (AAA) server is
main functional entity that performs major functions related to
subscriber’s billing details.
Functions AAA Server functions are as follows:
Authentication
Authorization
Accounting
Original Bill Generation
FTP Bill Generation
Bill Generation
AAA Server functions are used to generate the bills, a brief
introduction about the bill generation is explained below.
AGW keeps the subscriber message and sends the UDR to AAA
Server. AAA Server saves the UDR into database and then
generates the bill after some time.
AAA sends a billing response message to AGW as it receives and
verifies details about the message. AAA keeps this billing
message in the temporary bill list. After a certain cycle, AAA
generates the original bill and FTP bill and the accounting system
collects all bills from FTP directory of the AAA Server. The
original bill is stored as a bill.
Interval for AAA to generate Usage Data Records (UDRs) and the
FTP billing files is 300 to 1800 seconds, with 300 seconds as the
default setting.
Billing System
Introduction In ZXMBW system, there is no specific node for billing server
and services are charged by AAA Server.
Structure Billing system structure is shown in Figure 1.
FTP
TCP/ IP
DBIO
Service
Agent
FI G U R E 2 AC C O U N T I N G S YS T E M I N T E RF AC E S
END OF STEP
END OF STEP
END OF STEPS
Parameter Description:
Parameter Description
It is the time taken AAA to
Value generate bill and its range is from
60~3600. Default value is 300.
Parameter Description:
Parameter Description
It is duration up to which the bill
Value remain saved on database and its
range is from 1~3 in months
Parameter Description:
Parameter Description
It is the type of bill format and its
value is 0 or 1. where 0 stands
Value
for normal bill and 1 stands for
detailed bill
Parameter Description:
Parameter Description
Description Brief introduction of attribute
It represents vendor number
corresponding to attribute type.
Vendor ID
For non-vendor’s custom, fill 0 in
this field
It represents the vendor custom
Vendor Type
attribute type
Switch flag indicating whether the
Enumeration or not
attribute is enumerated
Parameters Description:
Parameter Description
Original Bill Path It is the path for original bill
generation. Default path is
“\AAA install disk\BillSave\”.
FTP Bill Path It is the path for FTP bill
generation. Default path is
“\AAA install disk\BillBillBak\”
3. Enter or browse the Original Bill Path and FTP Bill Path in
respective fields and then click OK button on ZXPDSS
install Configure dialog box as shown in Figure 20.
Bill Data
Overview
Introduction This chapter briefly introduces the bill format and billing types.
Contents This chapter contains the following topics.
UDR Format
Introduction A UDR uses the same billing format as an additional billing
record. The billing format is the definition of the formats of
billing properties, including type, length and format of each
property.
Description Type description UDR and additional billing record fields is given
in Table 8.
Maxim
um Form Billing Special
Item Parameter Type
Load at Field Value
Length
A. Mobile terminal ID
Calling- 460030
A1 MSID 31 15 String Station- 900100
Id 001
Maxim
um Form Billing Special
Item Parameter Type
Load at Field Value
Length
26/1
51(r
efer 861330
A2 MDN to 20 String MDN 010000
the 1
table
note)
26/5 073100
A3 ESN 19 String ESN
2 01
B. User ID
Framed
IP-
B1 IP Address 8 4 -IP- 10.0.0.1
addr
Address
Network
Access UserNa
B2 1 64 String 163
Identifier(N me
AI)
0:gener
al;
26/1 USER_T 1:PPC;
B3 User Type 1 String
52 YPE 2:WVPN
; 3:
IVPN
B4 NAI Flag 26/0 3 String NAIFlag
0:local;
1:
interpro
vincial
roaming
in; 2:
interpro
vincial
roaming
Roaming Roamin out
B5 26/0 1 String
Flag g Flag
3:
internati
onal
roaming
in;
internati
onal
roaming
out
C. Session ID
Maxim
um Form Billing Special
Item Parameter Type
Load at Field Value
Length
ASCII
string of
Acct- session
Account
C1 44 8 String Session ID
Session ID
-Id
e.g.,MB
000041
ASCII
string of
Correlation 26/4 Correlat associat
C2 8 String ed ID
ID 4 ion_Id
e.g.,MA
00005N
3GPP2_
Session 26/4 Integ 0=false,
C3 4 Session
Continue 8 er 1=true
_cont
D. Infrastructure ID
Home
MIP Home IP- Agent
D1 26/7 4
Agent (HA) addr Attribut
e
NAS-
AGW/FA IP- 194.136
D2 4 4 IP-
Address addr .81.93
Address
3GPP2_
IP-
D3 Serving PCF 26/9 4 PCF
addr
IP_Addr
Connect
SID +
NID +
Base_ID
in as
serial
mode to
form a
number;
26/1 3GPP2_ each
D4 BSID 12 String
0 BSID part is
encoded
by four
hexadeci
mal
number
ASCII
capital
characte
rs
E. Area code ID
Maxim
um Form Billing Special
Item Parameter Type
Load at Field Value
Length
The
lowest
16 bits
store
the user
zone ID
(UZID),
the
lower 15
bits
store
the user
zone
3GPP2_ system
26/1 Integ
E1 User Zone 4 User_I ID
1 er
D (UZSID)
, and
the
highest
bits are
usually
zero.
UZID
and
UZSID
are
defined
in IS-
638-B.
F. Dialog state
Forward 26/1 Integ 3GPP2_
F1 4
Mux Option 2 er FMUX
Reverse Mux 26/1 Integ 3GPP2_
F2 4
Option 3 er RMUX
Service 26/1 Integ 3GPP2_
F5 4
Option 6 er SO
0=Prima
Forward 26/1 Integ 3GPP2_ ry,
F6 4
Traffic Type 7 er FTYPE 1=Seco
ndary
Reverse
0=Prima
Traffic
26/1 Integ 3GPP2_ ry,
F7 Type(Primar 4
8 er RTYPE 1=Seco
y,
ndary
Secondary
Maxim
um Form Billing Special
Item Parameter Type
Load at Field Value
Length
0=no
fundame
ntal,
Fundamenta 26/1 Integ 3GPP3_
F8 4 1=5ms
l Frame Size 9 er FSIZE
frame,
2=20ms
frame
Forward
26/2 Integ 3GPP2_
F9 Fundamenta 4
0 er FRC
l RC
Reverse
26/2 intege 3GPP2_
F10 Fundamenta 4
1 r RRC
l RC
1=Simpl
IP 26/2 Integ 3GPP2_ e IP,
F11 4
Technology 2 er IP_Tech 2=Mobil
e IP
0=no
tunnel1
= non-
encrypti
Compulsory 3GPP2_
26/2 Integ on
F12 Tunnel 4 Comp_
3 er tunnel2
Indicator Flag
=
encrypti
on
tunnel
stop
record
cause:
0=unkn
own1=P
PP/Servi
ce
3GPP2_ overtim
Release 26/2 Integ
F13 4 Reason e2=Han
Indicator 4 er
_Ind doff
3=PPP
protocol
fails
4=PPP
abnorm
al
release
Frame
DCCH Frame size:
26/5 intege 3GPP2_
F14 Format(0/5/ 4
0 r F_Size 0/5/20m
20ms)
s
G. Session activity
Maxim
um Form Billing Special
Item Parameter Type
Load at Field Value
Length
Number
Data Octet
Acct- of bytes
Count Integ
G1 43 4 Output- transmit
(Terminatio er
Octets ted to
n)
user
Number
Data Octet
Acct- of bytes
Count Integ
G2 42 4 Input- transmit
(Originating er
Octets ted by
)
user
3GPP2_
Bad PPP
26/2 Integ Bad_Fr
G3 Frame 4
5 er ame_C
Count
ount
Event_
G4 Event Time 55 4 Time Timesta
mp
3GPP2_
26/4 Integ
G8 Active Time 4 Active_
9 er
Time
Number of 3GPP2_
26/3 Integ
G9 Active 4 Num_A
0 er
Transitions ctive
SDB Octet 3GPP2_
Count 26/3 Integ SDB_In
G10 4
(Terminatin 1 er put_Oct
g) ets
SDB Octet 3GPP2_
Count 26/3 Integ SDB_O
G11 4
(Originating 2 er utput_
) Octets
Number of 3GPP2_
26/3 Integ
G12 SDBs(Termi 4 NumSD
3 er
nating) B_Input
3GPP2_
Number of
26/3 Integ NumSD
G13 SDBs(Origin 4
4 er B_Outp
ating)
ut
Number
of bytes
received
3GPP2_
by the
Number of Num_B
26/4 Integ HDLC
G14 bytes 4 ytes_Re
3 er layer of
received ceived_
AGW in
Total
the
reverse
direction
Maxim
um Form Billing Special
Item Parameter Type
Load at Field Value
Length
Number
of bytes
of
registrat
3GPP2_ ion
Mobile_ request
In-Bound
IP_Sign message
Mobile IP 26/4 Integ
G15 4 aling_I and
Signal-ing 6 er
n- agent
Octet Count
Bound_ request
Count message
transmit
ted by a
mobile
station
Number
of bytes
of
registrat
ion
3GPP2_ respons
Mobile_ e
Out-bound
IP_Sign message
Mobile IP 26/4 Integ
G16 4 aling_O and
Signal-ing 7 er
ut- agent
Octet Count
Bound_ publishi
Count ng
message
transmit
ted to a
mobile
station
I. Quality of service
Maxim
um Form Billing Special
Item Parameter Type
Load at Field Value
Length
0=Best
Effort
10=AF1
1
12=AF1
2
14=AF1
3
18=AF2
1
20=AF2
2
IP Quality of
26/3 Integ 3GPP2_ 22=AF2
I1 Service 4
6 er IP_QOS 3
(QoS)
26=AF3
1
28=AF3
2
30=AF3
3
34=AF4
1
36=AF4
2
38=AF4
3 46=EF
Lowest
4 bits
store
the QoS
Airlink
3GPP2_ priorities
Quality of 26/3 Integ
I4 4 Air_Prio defined
Service(QoS 9 er
rity in IS-
)
2000-A
user
profile
file
Y. Specific parameter of air link record
1=Conn
ection
Setup
3GPP2_
2=Activ
Airlink 26/4 Integ Airlink_
Y1 4 e Start
Record Type 0 er Record
3=Activ
_Type
e Stop
4=SDB
Record
3GPP2_
R-P Session 26/4 Integ R-
Y2 4
ID 1 er P_Sessi
on_ID
Maxim
um Form Billing Special
Item Parameter Type
Load at Field Value
Length
3GPP2_
Airlink Airlink_
26/4 Integ
Y3 Sequence 4 Sequen
2 er
Number ce_Nu
mber
0=Mobil
3GPP2_
e
Mobile Mobile_
Originat
Originated/ Termin
26/4 Integ ed
Y4 Mobile 4 ated_O
5 er 1=Mobil
Terminated riginate
e
Indicator d_Indic
Termina
ator
ted
Z. Container
Account
ing
Z1 Container 26/6 Variable String
Contain
er
Bill Format
Introduction An original file adopts ASCII text format. Properties for each Bill
are arranged in sequence. Properties are separated by ‘\t”. At
time of generating Bill record if any corresponding property is
empty, use ‘\t’ to separate directly without any characters
between next property.
One row in a file is a billing record. Billing records are separated
by line feed characters and written in sequence in the Bill. The
file length is not fixed.
Record items of each billing record are corresponding with
properties of billing formats. The definition, format and length of
each property should meet the specification of billing format.
Maximum
Property Name Remarks
Length
Serial numbers. CHAR (10) Continuous Bill serial number
Accounting Status CHAR (10) 1=start bill; 2=end bill; 3=
Type(40) middle bill; 4=after merging
MSID(31) CHAR (15) IMSI,MIN,IRM
IP Address(8) CHAR (15) such as 172.1.12.3
Maximum
Property Name Remarks
Length
Fundamental Frame CHAR (10) Basic channel frame size:
Size(26/19) 0=unsure,1=5,2=20ms
Forward CHAR (10) Forward basic resource level
Fundamental
RC(26/20)
Reverse CHAR (10) Reverse basic resource level
Fundamental
RC(26/21)
IP CHAR (10) IP technology type:
Technology(26/22) 1=Simple IP 2=Mobile IP
Compulsory Tunnel CHAR (10) Forced tunnel type
Indicator(26/23) 0=no tunnel;1=unsafe tunnel
2=safe tunnel
Release CHAR (10) Cause of transmitting Accounting
Indicator(26/24) stop
DCCH Frame CHAR (20) Special format for controlling
Format(26/50) channel frame
Data Octet Count CHAR (10) Number of bytes transmitted to
(Terminating)(43) user
Data Octet Count CHAR (10) Number of bytes transmitted by
(Originating)(42) user
Bad PPP Frame CHAR (10) Bad frame deserted by PSDN.
Count,(26/25)
Event Time(55) CHAR (10) The start time in start Bill, the
stop time in stop Bill, second
number since 00:00:00 of
January 1st, 1970
Active Time(26/49) CHAR (10) Session duration calculated by
PCF end (in seconds)
Number of Active CHAR (10) Switching times from dormancy
Transitions(26/30) to active in one PPP connection
SDB Octet Count CHAR (10) Number of bytes user received
(Terminating)(26/31 through SDB (short data burst)
) mode
SDB Octet Count CHAR (10) Number of bytes user sent
(Originating) through SDB (short data burst)
(26/32) mode
Number of SDBs CHAR (10) Times that user received SDB
(Terminating) (short data burst)
(26/33)
Number of SDBs CHAR (10) Times that user sent SDB (short
(Originating) data burst)
(26/34)
Number of HDLC CHAR (10) HDLC received by AGW (bytes of
layer bytes advanced data link layer)
received(26/43)
Maximum
Property Name Remarks
Length
In-Bound Mobile IP CHAR (10) Signaling traffic of mobile IP,
Signaling Octet bytes of MIP signaling user
Count(26/46) received
Outbound Mobile IP CHAR (10) Signaling traffic of mobile IP,
Signaling Octet bytes of MIP signaling user sent
Count(26/47)
IP Quality of Service CHAR (10) User quality level code of IP
(QOS)(26/36) network (most are Best Effort at
present)
Airlink Quality of CHAR (10) Wireless link quality code
Service
(QOS)(26/39)
Airlink Record CHAR (10) 1=establish connection;2=start
Type(26/40) activate;3=end activate;4=SDB
record
R-P Session CHAR (10) R-P session ID
ID(26/41)
Airlink Sequence CHAR (10) Wireless link serial number
Number(26/42)
Mobile Originated / CHAR (10) 0=start;1=end
Mobile Terminated
Indicator(26/45)
MDN CHAR(20) User mobile phone number
User Type CHAR(1) 0:general;1:PPC;2:WvPN;3:IVPN
NAI home location CHAR(3) CDMA city code
ID
Roaming ID CHAR (1) 0:local;1:interprovincial roaming
in;2:interprovincial roaming out
3:international roaming
in;4:international roaming out
(default: judge by IMSI)
ESN(26/52) CHAR(19) Mobile phone electronic serial
number
Unused CHAR (10) Reserved
Unused CHAR (10) Reserved
Billing container Length
(26/6)
Line feed 1 ‘\n’
Bill Types AAA System supports two types of Bill formats. These two types
of formats are as follows:
Detailed Bill
Normal Bill
Detailed Bill
Bill Name Structure of detailed bill name is as follows:
AMMDDHHMMnnn.acc
A stands for A100, MM for month, DD for day, HH for hour, MM
for minute and nnn for 3-digit serial number of a bill file (001-
999). For example, the name of a Bill file generated on 2004-11-
4 10:22:09 is “A11041022089.acc”.
Bill Format Format of detailed bill is as follows:
2006-11-4 10:22:09
Acct-Authentic = RADIUS
Acct-Session-Id = ZTE25587
Acct-Status-Type = Start
Calling-Station-Id = 460030907310004
Correlation_Id = ZTE35647
Framed-IP-Address = 10.10.0.50
NAS-IPv4-Address = 194.136.81.83
NAS-Port-Type = CDMA2000
Beginning Session = True
3GPP2_BSID = 000D00010000
3GPP2_Comp_Flag = no tunnel
Event_TimeStamp = 1070014404
3GPP2_FMUX = 1
3GPP2_FRC = 2
3GPP2_FISZE = 20ms frame
3GPP2_FTYPE = Primary
3GPP2_F_SIZE = 0
3GPP2_IP_Tech = Simple IP
3GPP2_PCF IP_Addr = 194.136.81.220
3GPP2_RMUX = 1
3GPP2_R-P_Session_ID = 0
3GPP2_RRC = 3
3GPP2_RTYPE = Primary
3GPP2_SO = 33
3GPP2_User_ID = 0
MDN = 13100000001
NAIFlag = 000
USER_TYPE = 0
ESN = 12345678
UserName = sleep
Normal Bill
Bill Name Structure of normal bill name is as follows:
File type + file generated time (accurate to
year/month/date/hour/minute) + serial number (4 digits)
The file type is four digits: First is roaming flag (0: non-roaming;
1: roaming in; 2 roaming out), Second is service type flag (0:
general; 1: PPC; 2:WVPN; 3:IVPN), and the two digits are
reserved digits. For example, “00002004101310330023.acc”
stands for a local bill of a general user, generated on 2004-10-
13 10:33.
Bill Format Format of normal bill is as follows:
A Bill file consists of file header part and file body part. Format
of Bill header is shown in Table 10.
Maximum
Property Name Remarks
Length
Record type CHAR (2)CHAR(2) First record=01
File number CHAR (4)CHAR(4) Sort from 001 and reset
after sorting
File version number CHAR (2) 00
Date on which the CHAR (8) YYYYMMDD
file is generated.
First session date CHAR (8) YYYYMMDD
First session time CHAR (6) HHMMSS
Last session date CHAR (8) YYYYMMDD
Last session time CHAR (6) HHMMSS
Number of file CHAR (10) Right align, add 0 on the left
records Right justified and left filled
with 0s
Line feed CHAR (1)CHAR(1)
Example:
010001002006041920060419171228200604191712340000000004
1 1 450030907310001 10.1.0.1 dns
123><=r8 12345678 0 194.136.81.7
194.136.81.220 0 1
0 2000 1500 1145437948 400
0
First row is bill head and every row which begins with number is
one billing record. Billing records are separated by new line
denotation, and written consecutively in CDR. The length of bills
are indefinite.
Original CDRs adopts ASCII text format, the attribute values of
CDRs are arranged in sequence. The attributes are separated by
"\t". When generating billing records, if the corresponding
attribute value is null, then the attributes are directly separated
by list separator, there is no other signs between list separators.
Bill Transmission
Overview
Introduction This chapter briefly introduces the procedure for bill transmission
and setting FTP site for bill transmission.
Contents This chapter contains the following topics.
Bill Transmission
Billing server is connected with the collecting machine of the
billing center through a network cable. Bills are transmitted to
billing center through FTP protocol. Set the billing server as an
FTP server using FTP service process of system. Billing center
can access billing server and collects the generated bills. At
present, Bills are transmitted through FTP.
Parameters Description:
Parameter Description
Description It is brief introduction of FTP
site
IP Address It is the IP address of server
for storing bill
TCP Port It the TCP port number.
Default value is 21.
Parameter Description:
Parameter Description
Local path It is the path of storing bill
7. Enter or browse the Local Path and select Read, Write and
Log visits check boxes as shown in Figure 27.
8. Click Directory Security tab on Default FTP Site
(Stopped) properties dialog box as shown in Figure 25.
Abbreviations
Abbreviation Description
3
3G The third generation mobile communications
A
AAA Authentication, Authorization and Accounting
AAL2 ATM Adaptation Layer type 2
AAL5 ATM Adaptation Layer type 5
ACK Acknowledgement
AH Authentication Header
ASN Access Service Network
ASP Application Service Provider
ASN-GW Access Service Network Gateway
ATM Asynchronous Transfer Mode
B
BSS Base Station Subsystem
C
CHAP Challenge Handshake Authentication Protocol
CHUB Control HUB
CM Configuration Management
COA Care Of Address
CPLD Complex Programmable Logic Device
D
DB Database
DBA Database Agent
DBIO Database Input & Output
DBS Database Subsystem
DHCP Dynamic Host Configuration Protocol
Abbreviation Description
DHCP Server Dynamic Host Configuration Protocol Server
DRC Data Rate Control
E
EMS Element Management System
F
FA Foreign Agent
FE Fast Ethernet
FISU Fill-in Signaling Unit
G
GDSN General Data Serving Node
GE Giga Ethernet
GLI GE Line Interface
GPRS General Packet Radio Service
GRE Generic Routing Encapsulation
H
HA Home Agent
HLR Home Location Register
HSSL High Speed Serial Link
I
ICMP Internet Control Message Protocol
IETF Internet Engineering Task Force
IKE Internet Key Exchange
IMSI International Mobile Subscriber Identity
IPCP IP Control Protocol
IPSec IP Security
Ipv6 IP Version 6
IRM International Roaming MIN
Internet Security Association and Key
ISAKMP
Management Protocol
L
L2TP Layer2 Tunnel Protocol
LAN Local Area Network
LCP Link Control Protocol
LSSU Link Status Signaling Unit
M
MIP Mobile IP
MS Mobile Station
Abbreviation Description
MSID Mobile Station Identifier
MSIN Mobile Station Identification Number
MSISDN Mobile Station ISDN number
N
NAI Network Access Identifier
NCP Network Control Protocol
NE Network Element
NGN Next Generation Network
NMC Network Management Center
NMS Network Management Subsystem
O
OMC Operations & Maintenance Center
OMM Operation Maintenance Module
P
PAP Password Authentication Protocol
PPP Point to Point Protocol
PPTP PPP Tunnel Protocol
PSI PCF Session Identity
Q
QoS Quality of Service
R
RADIUS Remote Authentication Dial In User Service
RSVP Resource Reservation Protocol
S
STM Synchronous Transfer Mode
T
TCP Transfer Control Protocol
TOS Type Of Service
U
UDP User Datagram Protocol
UDR User Data Record
UMTS Universal Mobile Telecommunication System
V
VPN Virtual Private Network
VTP Virtual Tunnel Protocol
Abbreviation Description
W
WAN Wide Area Network
WDP Wireless Datagram Protocol
WDSS Wireless Data Services System
WIN Wireless Intelligent Network
WVPN Wireless Virtual Private Network
Home IP Home network providing the user with IP-based data services,
Network serving as the route home network of user NAI. This network
can be enterprise private network, public ISP access network or
cdma2000 network.
Intermediate Intermediate AAA, located in an intermediate network, is in
AAA security relationships with the service AAA and home AAA. It is
used to safely transmit AAA messages between the service AAA
and home AAA. In some cases, there may be more than one
intermediate AAA between the service AAA and the home AAA.
Visitor AAA AAA server resident on the visiting access provision network.