Usds Oam Guide

Wireless Intelligent Network (IN)
Unified Subscriber Data Server (USDS) R6.0

OAM Guide
270-710-919R6.0
Issue 3.0
September 2006
Lucent Technologies - Proprietary
This document contains proprietary information of
Lucent Technologies and is not to be disclosed or used except in
accordance with applicable agreements
Copyright 2006 Lucent Technologies
Unpublished and Not for Publication
All Rights Reserved
This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered in
any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or licensing, without
the express written consent of Lucent Technologies and the business management owner of the material.
Notice
Every effort was made to ensure that this information product was complete and accurate at the time of printing. However, information is subject to change.
Mandatory customer information
None
Security statement
In rare instances, unauthorized individuals make connection to the telecommunications network through use of access features.
Trademarks
Adobe Acrobat is a trademark of Adobe Systems, Inc.

PostScript is a trademark of Adobe Systems, Inc.
UNIX is a trademark of X/Open Company, Ltd.
HP is a trademark of Hewlett-Packard Company
HP-UX is a trademark of Hewlett-Packard Company
e-Microsoft Internet Explorer is a trademark of Microsoft Corporation
Oracle and Oracle Enterprise is a trademark of Oracle Corporation
ORBIX is a trademark of IONA Technologies Ltd.
Netscape Enterprise Server is a trademark of Netscape Communication Corporation
Netscape Communicator is a trademark of Netscape Communications Corporation
TimesTen is a registered trademark of TimesTen Performance Software
Sun[TM] and Netra[TM] are trademarks of Sun Microsystems, Inc.
Ordering information
The ordering number for this information product is 270-710-919R6.0. For information on how to order Lucent Technologies information products, see the
About this information product section (Preface) of this document.
Support
Technical support
For technical support on this product, contact Lucent Customer Technical Support at 1-800-WE2CARE (US and Canada) or 001-630-224-4672 (International)

See notice on first page.
Contents
............................................................................................................................................................................................................................................................
Administrative interfaces for USDS OA&M tasks

Administering user accounts on MAS, eSM, and OMC-H
1-2
USDS user accounts on the MAS
1-4
USDS user accounts on the eSM
1-5
USDS user accounts on the OMC-H
1-7
Using MAS administrative interfaces
1-8
Procedure: Access the MAS administrative interfaces
1-10
............................................................................................................................................................................................................................................................
Managing the USDS

The USDS SPAs
2-2
HCF and HDF communications
2-4
Primary HDF status
2-9
Data replication between mated HDF pair
2-11
Customer preference impact on HDF state transition
2-17
Procedure: Back up USDS system
2-19
Procedure: Recover the USDS system
2-21
Procedure: Determine the status of USDS SPAs
2-24
Procedure: Start the USDS SPAs
2-26
Procedure: Stop the USDS SPAs
2-31
............................................................................................................................................................................................................................................................
Managing the USDS databases

USDS data introduction
3-3
Procedure: Back up HDF TimesTen database to disk, tape/DVD
3-6
Recover the HDF TimesTen database from the mated HDF node
3-8
Procedure: Recover the HDF TimesTen database from tape or disk
3-10
Procedure: Recover a subset of HDF TimesTen database from eSM
3-12
Procedure: Access SPA-related data from MAS nodes
3-14
Procedure: Disaster recovery for a HDF pair
3-26
...........................................................................................................................................................................................................................................................
270-710-919R6.0
Issue 3.0, September 2006

See Notice on first page
C O N T E N T S
iii
Load balancing introduction
3-27
Procedure: Execute load balancing from eSM
3-37
Procedure: Run load balancing removal tool
3-47
Procedure: Re-lock the USDS features from the eSM
3-51
Index server introduction
3-54
Procedure: Index server full init- HDF pump
3-56
Procedure: Index server full init-peer pump
3-58
Procedure: Configure RC/V form access permissions
3-60
Procedure: Assign Form Permissions to Restricted WPS Logins
3-61
............................................................................................................................................................................................................................................................
Input and Output messages

Background knowledge
4-3
Input message
4-5
Procedure: Send command from the eSM GUI
4-6
FULLINIT:IS [, CLEANUP |, DFPUMP | CF=a [, UCL]]
4-10
SSD update (ANSI)
4-15
Unique challenge (ANSI)
4-17
Technician initiated VLR refresh (ANSI)
4-19
Technician initiated VLR delete (ANSI)
4-20
CANCEL: MAP (UMTS)
4-21
RECOVER: MAP (UMTS)
4-22
Subscriber Number Report (ANSI/UMTS)
4-24
CALEA delivery function connection test
4-25
DEREG: PRID, HOST (HSS)
4-27
Timestamp update (UMTS)
4-29
Output message
4-31
Procedure: Redirect Omlogs
4-35
Procedure: Configure the severity level for OMLogs
4-42
Procedure: View output message
4-52
............................................................................................................................................................................................................................................................
Monitoring USDS
Monitoring USDS messages
5-2
Monitoring alarms
5-8
Procedure: Locate and clear USDS alarms at DAP
5-16
Procedure: View alarms in log file
5-18
...........................................................................................................................................................................................................................................................
C O N T E N T S
iv

270-710-919R6.0
Procedure: Monitor alarms with "tailer" command
5-20
Procedure: Resolve recurring USDS SPA alarms
5-22
Monitoring error and event messages
5-26
Monitoring USDS overload
5-27
............................................................................................................................................................................................................................................................
Monitoring the SS7 Links

SS7 links
6-2
Procedure: Monitor SS7 DAPs
6-3
............................................................................................................................................................................................................................................................
Using service measurements

Introduction to USDS service measurements
7-2
Enable or disable measurement pegging
7-5
HDF measurements for performance monitoring
7-9
USDS eSM measurement reports
7-11
Procedure: Modify measurements polling on eSM
7-12
Procedure: Create USDS measurement reports on eSM
7-15
............................................................................................................................................................................................................................................................
Custom report
CALEA service report
8-2
WPS service report
8-3
Procedure: Generate custom report on eSM
8-4
............................................................................................................................................................................................................................................................
Using CALEA
CALEA introduction
9-2
Procedure: Assign Form Permissions to Restricted RC/V Logins for CALEA 9-4
Procedure: Verify LTDU connection with USDS from eSM
9-7
Procedure: Configure IPSec keys between USDS and LTDU
9-9
Procedure: Configure IPSec policies between USDS and LTDU
9-13
Procedure: Remove IPSec connection between USDS and LTDU
9-18
............................................................................................................................................................................................................................................................
10
Using split NPA tool for ANSI

Introduction
10-2
Area Code Split Exchange Diskette (ACSED)
10-4
The newNPANXXRangeFile file
10-5
USDS NPA data
10-6
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C O N T E N T S
Performance estimates for split NPA tool
10-8
NPA split tool tasks
10-9
Assumptions and restrictions
10-10
Split NPA tool installation
10-11
Using split NPA tool on eSM
10-12
Using split NPA tool on MAS
10-13
............................................................................................................................................................................................................................................................
11
Using AAA
11-2
Procedure: Access SMT through LMT
11-3
AAA accounting in USDS
11-6
Logs/Alarms of VitalAAA server on USDS
11-8
USS Servers on USDS
11-9
............................................................................................................................................................................................................................................................
USDS service measurements

HCF service measurement sets - Common
A-3
HCF service measurement sets - ANSI
A-8
HCF service measurement sets - UMTS
A-59
HCF service measurement sets - CALEA
A-94
HCF service measurement sets - HSS
A-100
HCF service measurement sets - AAA
A-108
HCF service measurement sets - SMPP
A-109
HDF service measurement sets - Common
A-110
HDF service measurement sets - ANSI
A-114
HDF service measurement sets - UMTS
A-129
HDF measurement sets - HSS
A-149
............................................................................................................................................................................................................................................................
USDS OM logs
System integrity
B-3
HDF measurement
B-21
HCF Index Server
B-22
ANSI Authentication
B-24
ANSI Location Management
B-37
ANSI Call Delivery
B-41
ANSI supplementary service
B-53
...........................................................................................................................................................................................................................................................
C O N T E N T S
vi

270-710-919R6.0
ANSI subscriber data management
B-55
ANSI short message
B-57
ANSI default scenarios
B-59
UMTS framework
B-68
UMTS authentication
B-69
UMTS CAMEL
B-71
HSS overload
B-72
HSS authentication
B-73
HSS feature lock
B-74
HSS call handling
B-75
AAA retrieve template
B-79
SMPP specified
B-80
............................................................................................................................................................................................................................................................
Using UMTS AuC/HSS APIs

UTMS authentication overview
C-3
Developing service provider authentication functions
C-6
AuC authentication function arrays
C-11
Umts_auc_a3_plugin specifications
C-15
C-17
Umts_auc_f1_plugin specifications
C-19
Umts_auc_f1star_plugin specifications
C-21
C-24
C-26
C-28
C-30
C-32
AuC decryption functions
C-34
Decryption function general requirements
C-35
decrypt_amf specifications
C-36
decrypt_k specifications
C-38
initialize_decryptors specifications
C-40
AuC sequence number functions
C-41
Sequence number function general requirements
C-42
generate_sqn specifications
C-43
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C O N T E N T S
vii
check_sqn specifications
C-46
Authentication function example
C-48
............................................................................................................................................................................................................................................................
GL
Glossary
............................................................................................................................................................................................................................................................
IN
Index
...........................................................................................................................................................................................................................................................
C O N T E N T S
viii

270-710-919R6.0
List of figures
............................................................................................................................................................................................................................................................
1-1
Add USDS user on eSM
1-6
1-2
LMT Window with Display Action Page 106
1-9
............................................................................................................................................................................................................................................................
Managing the USDS
2-1
State transition of a SPA
2-3
2-2
The HCF and HDF communications
2-6
2-3
HDF data replication
2-11
............................................................................................................................................................................................................................................................
3-1
Data storage in USDS
3-3
3-2
USDS database interactions
3-4
3-3
PLATFORM MAIN MENU
3-17
3-4
SDHLR SUBSCRIBER DATA
3-18
3-5
Subscriber data example
3-19
3-6
Validating the subscriber data
3-20
3-7
ANSI Directory Number example
3-21
3-8
ANSIAC example
3-22
3-9
IMSI SUBSCRIBER DATA example
3-24
3-10
ANSI PHONE EXTENDED example
3-25
3-11
The eSM launch page
3-38
3-12
The Load Balancing Requests page
3-39
3-13
A new load balancing request
3-40
3-14
The result of a new load balancing request
3-43
3-15
The status of a load balancing request
3-44
...........................................................................................................................................................................................................................................................
270-710-919R6.0

F I G U R E S
ix
3-16
Service Objects status for the load balancing request
3-45
3-17
Load balancing request processing status
3-46
3-18
PLATFORM MAIN MENU
3-63
3-19
SERVICE PACKAGE MANAGEMENT SUBMENU
3-64
3-20
HDF600
3-65
3-21
ANSI GLOBAL DATA
3-66
3-22
Global WPS DATA
3-67
3-23
TERMINAL
3-68
3-24
WPS Data Keyed by IMSI
3-69
3-25
WPS Data Keyed by MIN
3-70
............................................................................................................................................................................................................................................................
4-1
eSM main launch page
4-6
4-2
Commands screen
4-7
4-3
Define the command
4-8
4-4
Refresh button
4-9
4-5
Network Platform Main Menu
4-37
4-6
USL Message Destination Form
4-39
4-7
The Operations, Administration and Maintenance Submenu
4-40
4-8
USL Message Class Definition Form
4-41
4-9
eSM launch page
4-43
4-10
The Service Objects page
4-44
4-11
Searching the existing Service Objects
4-45
4-12
Search Result
4-46
4-13
Page for choosing optional capabilities
4-47
4-14
Page for SDHLR Alarm Table
4-48
4-15
The required fields for the SDHLR Alarm Table
4-49
4-16
SO change request summary
4-50
4-17
Process this work order
4-51
...........................................................................................................................................................................................................................................................
F I G U R E S

270-710-919R6.0
............................................................................................................................................................................................................................................................
Monitoring USDS
5-1
Page 100, Main Menu
5-4
5-2
Page 110, SPA summary
5-5
5-3
Page 1100, SPA Summary 0-29
5-6
5-4
Page 110xx, SPA xx Machine Summary
5-7
5-5
High level alarm resolution process
5-9
5-6
Determining overload for HCF nodes and HDF nodes
5-28
5-7
RC/V form 1.3
5-32
............................................................................................................................................................................................................................................................
6-1
DAP main window
6-4
6-2
107 - SS7 System status
6-5
6-3
107XX - SS7 local boards
6-5
6-4
107XXY - MTP2E1/MTP2T1 links
6-6
............................................................................................................................................................................................................................................................
7-1
The Service Administration page
7-13
7-2
The Measurements Sets page
7-13
7-3
The Measurement Set detail Page
7-14
7-4
The Service Tools page
7-16
7-5
The Reports page
7-17
7-6
The Measurement Report page
7-17
7-7
The Report Status page
7-18
............................................................................................................................................................................................................................................................
Custom report
8-1
The eSM launch page
8-4
8-2
The Services page
8-5
8-3
The HDF Service page
8-6
8-4
The Custom Reports page
8-6
8-5
The Define Custom Report Parameters page
8-7
...........................................................................................................................................................................................................................................................
270-710-919R6.0

F I G U R E S
xi
8-6
The Report page
8-8
8-7
The Custom Report Requested page
8-9
8-8
The Custom Report page
8-10
8-9
The Report Order page of WPS service report
8-11
............................................................................................................................................................................................................................................................
Using CALEA
9-1
NETWORK PLATFORM MAIN MENU
9-2
OPERATIONS, ADMINISTRATION AND MAINTENANCE

SUBMENU9-15
9-3
IPSEC PARAMETERS FORM
9-16
9-4
9-19
9-5
OPERATIONS, ADMINISTRATION AND MAINTENANCE

SUBMENU9-20
9-6
9-14
9-21
............................................................................................................................................................................................................................................................
10
............................................................................................................................................................................................................................................................
11
Using AAA
11-1
Server Management Tool
11-4
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
USDS OM logs
............................................................................................................................................................................................................................................................
C-1
Authentication process overview
C-2
Service provider function development process
C-10
C-3
API operation, F1 example
C-12
C-3
...........................................................................................................................................................................................................................................................
F I G U R E S
xii

270-710-919R6.0
List of tables
............................................................................................................................................................................................................................................................
1-1
Example user roles and account needs
1-2
............................................................................................................................................................................................................................................................
Managing the USDS
2-1
2-5
2-2
Missed heartbeat responses
2-7
2-3
Omlogs for heartbeat failure
2-8
2-4
Example - Automatic replication recovery
2-13
2-5
Output messages - Manual replication recovery
2-15
2-6
Data in "DF Infor" for latest primary HDF
2-18
............................................................................................................................................................................................................................................................
3-1
User level subscriber key
3-28
3-2
Address level subscriber keys for ANSI
3-28
3-3
Address level subscriber keys for UMTS
3-29
3-4
Address level subscriber keys for ANSI/UMTS dual mode subscribers
3-29
3-5
Address level subscriber keys for HSS subscribers
3-29
3-6
Terminal level subscriber keys for ANSI
3-30
3-7
Terminal level subscriber keys for UMTS
3-30
3-8
Terminal level subscriber keys for ANSI/UMTS dual mode subscribers
3-30
3-9
Terminal level subscriber keys for HSS subscribers
3-31
3-10
Global configurations for load balancing
3-34
3-11
Fields description for load balancing request
3-41
............................................................................................................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

T A B L E S
xiii
4-1
Sample output message
4-32
4-2
Message class supported in USDS.
4-35
4-3
Fields explanation in form 2.1.
4-38
4-4
Fields explanation in form 2.2
4-41
............................................................................................................................................................................................................................................................
Monitoring USDS
5-1
Overload levels
5-30
5-2
Message queue overload levels
5-31
5-3
Field description for RC/V form 1.3
5-32
5-4
Actions corresponding to overload levels on HCF nodes
5-34
5-5
Examples of overload messages
5-36
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
7-1
Field descriptions for form 2.4
7-6
7-2
Measurement control fields in "ANSI Global" for ANSI protocol
7-7
7-3
Measurement control fields in "HLR SYS" for UMTS protocol
7-7
7-4
Related RTU(s)
7-9
7-5
Data in "Global Parameter" for HDF measurements
7-10
............................................................................................................................................................................................................................................................
Custom report
............................................................................................................................................................................................................................................................
Using CALEA
9-1
Fields on the "Define the Command" page
9-2
Algorithm key lengths
9-8
9-10
............................................................................................................................................................................................................................................................
10
10-1
Fields affected by a MIN split.
10-6
10-2
Field affected by a MDN split.
10-7
............................................................................................................................................................................................................................................................
11
Using AAA
...........................................................................................................................................................................................................................................................
T A B L E S
xiv

270-710-919R6.0
............................................................................................................................................................................................................................................................
A-1
HCF Overload
A-3
A-2
MSGH
A-4
A-3
Index Server
A-5
A-4
ANSI RegCanc Retry
A-8
A-5
ANSI MWN
A-8
A-6
ANSI multiple SMSC
A-9
A-7
ANSI SS
A-10
A-8
ANSI SS 2
A-12
A-9
ANSI SS 3
A-14
A-10
ANSI LBS
A-16
A-11
ANSI_LBS2
A-18
A-12
ANSI Circuit Mode Data
A-19
A-13
ANSI LM MSInact
A-20
A-14
ANSI LM RegCanc
A-22
A-15
ANSI LM RegNot
A-24
A-16
ANSI SDM QualReq
A-26
A-17
ANSI SDM QualDir
A-28
A-18
ANSI CD RoutReq
A-30
A-19
ANSI CD LocReq
A-32
A-20
ANSI CD TransNum
A-35
A-21
ANSI CD TransNum2
A-37
A-22
ANSI AC
A-38
A-23
ANSI AC2
A-40
A-24
ANSI OTAF
A-42
A-25
ANSI_NPA
A-44
A-26
ANSI_NPA2
A-46
A-27
ANSI_NE1 ~ ANSI NE50
A-48
A-28
ANSI_OVLD_DROP
A-57
...........................................................................................................................................................................................................................................................
270-710-919R6.0

T A B L E S
xv
A-29
ANSI_MISC
A-57
A-30
HCF Service Measurements
A-60
A-31
BASIC_SERVICE1
A-62
A-32
Authentication
A-64
A-33
SS Activations
A-66
A-34
SS Deactivations
A-68
A-35
SS Interrogations
A-70
A-36
UMTS_CAMEL
A-71
A-37
UMTS_CNL.
A-73
A-38
MAP_MSGS_SNT
A-74
A-39
MAP_MSGS_RCVD
A-75
A-40
MAP_MSGS_FAIL
A-76
A-41
UMTS_SMS
A-77
A-42
UMTS_SRI
A-78
A-43
UMTS_SS
A-80
A-44
UMTS_UL
A-82
A-45
GSM_USR_AFR
A-84
A-46
UMTS_USR_AFR
A-86
A-47
UMTS_NE1 ~ UMTS NE50
A-88
A-48
UMTS_OVLD_DROP
A-93
A-49
CALEA_SERVSYS_S
A-94
A-50
CALEA_SERVSYS_F
A-95
A-51
CALEA_TERMATT_S
A-95
A-52
CALEA_TERMATT_F
A-96
A-53
CALEA_REDIR_S
A-96
A-54
CALEA_REDIR_F
A-97
A-55
CALEA_CNNTST_S
A-98
A-56
CALEA_CNNTST_F
A-99
A-57
MAP IMS
A-100
...........................................................................................................................................................................................................................................................
T A B L E S
xvi

270-710-919R6.0
A-58
HSS Cx
A-101
A-59
HSS Sh
A-102
A-60
Cx SAR
A-104
A-61
Cx Mix
A-106
A-62
IMS_OVLD_DROP
A-107
A-63
AAA
A-108
A-64
SMPP
A-109
A-65
Service
A-110
A-66
Overload
A-111
A-67
Load Balance
A-112
A-68
Overload Drop
A-113
A-69
ANSI Suc Transcnt
A-115
A-70
ANSI Suc CD Msgcnt
A-117
A-71
ANSI Suc DC Msgcnt
A-120
A-72
ANSI Suc CD Msglen
A-123
A-73
ANSI Suc DC Msglen
A-125
A-74
UMTS Suc Transcnt
A-130
A-75
UMTS CD Msgcnt
A-133
A-76
UMTS DC Msgcnt
A-137
A-77
UMTS CD Msglen
A-141
A-78
UMTS DC Msglen
A-144
A-79
HSS Suc Transcnt
A-149
A-80
HSS Suc CD Msgcnt
A-150
A-81
HSS Suc DC Msgcnt
A-151
A-82
HSS Suc CD Msglen
A-152
A-83
HSS Suc DC Msglen
A-153
............................................................................................................................................................................................................................................................
USDS OM logs
B-1
System Integrity
B-2
HDF measurement
B-3
B-21
...........................................................................................................................................................................................................................................................
270-710-919R6.0

T A B L E S
xvii
B-3
HCF Index Server
B-22
B-4
ANSI Authentication
B-24
B-5
Location Management
B-37
B-6
Call Delivery
B-41
B-7
Supplementary Service
B-53
B-8
Subscriber Data Management
B-55
B-9
Short Message
B-57
B-10
ANSI Default Scenarios
B-59
B-11
UMTS Framework
B-68
B-12
UMTS Authentication
B-69
B-13
UMTS CAMEL
B-71
B-14
HSS Overload
B-72
B-15
HSS Authentication
B-73
B-16
HSS Feature Lock
B-74
B-17
HSS Call Handling
B-75
B-18
AAA OMlogs
B-79
B-19
SMPP OMlogs
B-80
............................................................................................................................................................................................................................................................
C-1
Authentication description
C-4
C-2
AuC API general requirements
C-7
C-3
AuC authentication arrays
C-11
C-4
a3 Value definitions
C-15
C-5
a8 value definitions
C-17
C-6
f1 value definitions
C-19
C-7
f1star value definitions
C-21
C-8
C-24
C-9
C-26
C-10
C-28
C-11
C-30
...........................................................................................................................................................................................................................................................
T A B L E S
xviii

270-710-919R6.0
C-12
C-32
C-13
C-34
C-14
decrypt_amf value descriptions
C-36
C-15
decrypt_k value definitions
C-38
C-16
C-41
C-17
generate_sqn value definitions for UMTS HLR
C-43
C-18
check_sqn value definitions for UMTS HLR
C-46
...........................................................................................................................................................................................................................................................
270-710-919R6.0

T A B L E S
xix
...........................................................................................................................................................................................................................................................
T A B L E S
xx

270-710-919R6.0
About this information product
............................................................................................................................................................................................................................................................
Purpose
Issue information
Intended audience
How to use this

information product
This manual introduces the basic Operations, Administration and Maintenance

(OA&M) tasks that are needed for Unified Subscriber Data Server (USDS)
R6.0.
This is the third issue of this information product.
This document is intended for the maintenance personnel of the USDS
product, as well as technical support of Lucent Technologies.
This document contains the following chapters:
Chapter 1, Administrative interfaces for USDS OA&M tasks provides a high
level description of various administrative interfaces that are available for
USDS OA&M tasks.
Chapter 2, Managing the USDS provides a high level introduction to the
procedures to manage USDS R6.0 SPAs.
Chapter 3, Managing the USDS databases provides the procedures and
related information on how to manage database in USDS R6.0.
Chapter 4, Input and Output messages provides the description of Input
Message (IM) / Output Message (OM) supported in USDS R6.0.
............................................................................................................................................................................................................................................................
270-710-919R6.0
xxi
Chapter 5, Monitoring USDS provides the background information

and procedures on how to monitor USDS R6.0.
Chapter 6, Monitoring the SS7 Links provides the background
information and procedures on how to monitor Signaling System 7
(SS7) links.
Chapter 7, Using service measurements provides the procedure and
related information on how to use Service Measurements in USDS
R6.0.
Chapter 8, Custom report describes the custom reports available to
eSM users during service installation.
Chapter 9, Using CALEA provides the procedure and related
information on how to use CALEA function in USDS R6.0.
Chapter 10, Using split NPA tool for ANSI provides information on
split Numbering Plan Area (NPA) tool in USDS R6.0.
Chapter 11, Using AAA provides information on how to use AAA on
USDS R6.0.
Appendix A, USDS service measurements provides the detailed lists
for the service measurements supported in USDS R6.0.
Appendix B, USDS OM logs provides the detailed lists for the OM
Logs supported in USDS R6.0.
Appendix C, Using UMTS AuC/HSS APIs describes how to use
UMTS AuC APIs to develop the authentication functions.
Scope of this information
product
Conventions
The scope of this information product is limited to USDS R6.0. For

detailed information on related platforms or external system
components, see related customer documentation.
This guide uses the following conventions:
Caution
Actions that can result in loss of service or damage to the software
product are indicated by this style.
Example:
...........................................................................................................................................................................................................................................................
xxii

270-710-919R6.0
CAUTION
Removing the active unit will stop all service.
Important
Actions that can result in problems or confusing states, if they are not
followed precisely are indicated by this style.
Example:
You must wait for the associated output message
before you proceed to the next step.
Important!
Others
Command conventions:
The commands executed in the subshell are preceded with a

less-than symbol (<).
Example: <rcv:menu;
The commands executed in the Unix console are preceded

with a greater-than symbol (>).
Example: >subshl
The command sequences using the GUI always use the

greater-than symbol (>) to indicate command progression.
Example: Service Objects Page>New Service Object Page
Constant Width typeface is used for the following:
System-generated responses displayed on your screen.

Example:
REQUEST TIMED OUT.
Literals used in text including command names, file names

and path names.
Example: /dev/tmp.
Recent Change and Verify (RC/V) form names, status, and

display page names.
Example: 102- ECP Processor Display page.
Constant width bold typeface is used for required keyboard

input.
Example: Enter ECP.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

xxiii
Constant width italic is used for placeholders for user-defined

input (variables).
Example: ls -l file_name.
Bold typeface is used for the following:
Related documents
Required selections from menus or status display pages.

Example: 102- ECP Processor Display page.
Italic typeface is used for the Titles of other documents.

Example: AUTOPLEX, Cellular Telecommunications Systems
System 1000 OUTPUT MESSAGES (401-610-057).
Other USDS documents
Unified Subscriber Data Server (USDS) R6.0 Product Overview

(270-710-917R6.0)
Unified Subscriber Data Server (USDS) R6.0 Installation Guide

(270-710-918R6.0)
Unified Subscriber Data Server (USDS) R6.0 Data and

Provisioning Guide - Common (270-710-920R6.0)

Provisioning Guide - ANSI (270-710-921R6.0)

Provisioning Guide - UMTS (270-710-922R6.0)
SUnified Subscriber Data Server (USDS) R6.0 Data and

Provisioning Guide - HSS (270-710-923R6.0)
MAS documents
MAS Customer Software Installation Guide (270-700-175)
MAS User Reference Guide (270-700-176)
MAS Maintenance Guide (270-700-169)
MAS System Description (270-710-655)
MAS Planning and Engineering Guide (270-700-174)
MAS System Administration Guide (270-700-167)
MAS Services Administration Guide (270-710-652)
eSM documents
Decision Graph Editor (270-710-126)
Introduction (270-720-330)
Security Administration (270-720-331)
Provisioning Concepts (270-720-332)
...........................................................................................................................................................................................................................................................
xxiv

270-710-919R6.0
Application Administration (270-720-333)
Monitoring the System (270-720-334)
Operating and Maintaining the System (270-720-335)
System Alarms (270-720-336)
Test Query (270-720-337)
View Administration (270-720-338)
Announcement Management (270-720-339)
Bulk Provisioning (270-720-340)
Service Version Management (270-720-343)
OMC-H documents
Command Line Interface (401-380-081R7.0)
Configuration Management (401-380-078R7.0)
Fault Management (401-380-077R7.0)
Graphical User Interface (401-380-082R7.0)
Managed Object Descriptions (401-380-080R7.0)
Performance Management (401-380-079R7.0)
System Administration (401-380-075R7.0)
System Installation (401-380-084R7.0)
System Overview (401-380-083R7.0)
Site Preparation (401-382-210)
Hardware Installation (401-380-818)
VitalAAA documents
To enroll in training
courses
VitalAAA Quick Start Guide (QuickStart.pdf under

/vendorpackages/NavisRadius/navisAAA/doc)
VitalAAA User's Guide and Reference

(http://www.vitalaaa.com/docs/index.html)
VitalAAA Server Management Tool Manual (365-360-001 or

SMT.pdf under /vendorpackages/NavisRadius/navisAAA/doc)
Documents for VitalAAA Plugins can be found under the directory

/vendorpackages/NavisRadius/navisAAA/doc/plugins.
Sample policy flow files can be found under the directory

/vendorpackages/NavisRadius/navisAAA/run/samples.
To obtain course descriptions, schedules, and enrollment information

for Lucent Technologies training courses, call the following numbers:
...........................................................................................................................................................................................................................................................
270-710-919R6.0

xxv
How to comment
In the United States and Canada, Call 1-888-LUCENT8
In other countries, call 1-630-224-4672
To comment on this information product, go to the Online Comment

Form (http://www.lucent-info.com/comments/) or mail your comments
to the Comments Hotline (comments@lucent.com).
...........................................................................................................................................................................................................................................................
xxvi

270-710-919R6.0
Administrative interfaces for USDS

OA&M tasks
Overview
............................................................................................................................................................................................................................................................
Purpose
This chapter introduces the procedures to create required accounts on

the MiLife Application Server (MAS), Enhanced Service Manager
(eSM), and Operations and Maintenance Center - HLR (OMC-H).
Important! As eSM and OMC-H have Graphic User Interfaces
(GUI), you can access and use the interface following the online
navigation buttons. However, eSM user interface and OMC-H user
interface details are not covered in this chapter.
Contents
This chapter contains the following sections:

1-2
1-4
1-5
1-7
1-8
Access the MAS administrative interfaces
1-10
............................................................................................................................................................................................................................................................
270-710-919R6.0

1 - 1
Administering user accounts on MAS, eSM, and

OMC-H

............................................................................................................................................................................................................................................................
Overview
USDS administrators need accounts on appropriate platforms to

perform the OAM tasks. To control and monitor the user activities,
different users or user groups are created with separate accounts. USDS
administrators use the:
MAS platform and the capabilities of its associated Solaris

operating system to manage MAS user accounts
eSM platform and security management function to manage eSM

user accounts
OMC-H platform and its administrators GUI to manage OMC-H

accounts.
Table 1-1, "Example user roles and account needs" (1-2) shows various
types of USDS users and associated account types.
Table 1-1
Example user roles and account needs
User role
MAS
account(s)
eSM
account(s)
OMC-H
account(s)
Operator
One per
assigned MAS
One per OMC-H
Maintainer
One per
assigned MAS
One per OMC-H
Service
provisioner
One per
assigned MAS
One per eSM,

with complete
data access
One per OMC-H
Subscriber data
provisioner
One per eSM,

with subscriber
data access
Corporate
provisioner
One per eSM,

with corporate
data access
End user
provisioner
One per
Subscriber, with
highly restricted
data and task
access
...........................................................................................................................................................................................................................................................
1 - 2

270-710-919R6.0
Administering user accounts on MAS, eSM, and

OMC-H
For more information, refer to:
MAS System Administration Guide (270-700-167)
eSM Security Administration (270-720-331)
System Administration (401-380-075R7.0).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

1 - 3

............................................................................................................................................................................................................................................................
Overview
The MAS Solaris operating system provides the capabilities required to

manage user accounts. You must have the root access to perform user
account tasks such as:
Create, modify, or delete user account data
Manage passwords
Define and configure user classes
Enable or disable user command logging.
Each MAS is delivered with two preconfigured users:
root
ainet
The ainet is the default MAS user, with permission to execute most but
not all of MAS commands. If you need to perform sensitive tasks, you
need to log on as root.
For more information on the user account management tasks, refer to
the MAS System Administration Guide (270-700-167).
...........................................................................................................................................................................................................................................................
1 - 4

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview
The eSM supports three types of users:
Provisioner - has access to the data via GUI.
End user - has limited permission and access to the smallest subset
of data.
Upstream - has access to the data via CORBA interface.
In the eSM, the parameters set to control user privileges are:
Service(s) or view(s).
Task(s).
The eSM user accounts are quite complex to create, as they have
several components as follows:
User group
Task group
Owner and/or owner group
User.
Figure 1-1, "Add USDS user on eSM" (1-6), depicts a high level
process for adding an USDS user to eSM.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

1 - 5
Figure 1-1
Add USDS user on eSM
For information on the user account management tasks, refer to eSM

Security Administration (270-720-331).
...........................................................................................................................................................................................................................................................
1 - 6

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview
The OMC-H provides the capabilities to manage user accounts. You

must have the system administrator access to perform user account
tasks.
For more information on the user account management tasks, refer to
the System Administration (401-380-075R7.0).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

1 - 7

............................................................................................................................................................................................................................................................
Overview
The MAS administration tasks are performed through the terminals

delivered with the MAS machines or remotely though the Remote
Maintenance Terminal (RMT).
For each MAS machine, the user workstation (terminal) displays the
following windows:
UNIX Console window
Local Maintenance Terminal (LMT) window
Web Browser
When you log on to the user workstation, it automatically displays the

UNIX console and LMT windows for the MASs it serves.
The UNIX console interface provides a Solaris (UNIX) shell. Use this
window to execute the scripts, for security, backup and recovery, and
other functions, and also to access the MAS subshell.
The LMT or RMT contains the following information:
System Status Line, which displays machine name, software

version, and current time
Summary Status Area, which provides critical indicators for

alarms
Display Action Page (DAP) Command Line, which allows the

user to access other DAPs
DAP Identification Line, which identifies the current DAP being

displayed
Control and Display Page Area, which provides specific hardware

and software status information
Input Command Area, which allows the user to input shell

commands
Input/Output Message Area, which provides messages in response

to commands that were entered
Graphical Function Keys, which enable you to move between the

command areas (only available on LMT).
Figure 1-2, "LMT Window with Display Action Page 106" (1-9) shows
an LMT window with DAP 106.
...........................................................................................................................................................................................................................................................
1 - 8

270-710-919R6.0
Figure 1-2
MAS administrative tools
LMT Window with Display Action Page 106
The MAS provides five principal administrative tools:
The User System Language Interface (USLI) provides a textbased OA&M interface. USLI commands, or Input Messages,
helps you monitor platform and service status, administer
services, manage alarms, update software, etc. The USLI
commands can be executed in the Unix console, LMT or RMT.
USLI output messages provide information on status, alarms, and
command execution results.
UNIX scripts are available for security, backup and recovery, and
other functions.
A form-based Recent Change and Verify (RC/V) system helps you

provision message logs, billing, measurements, scheduled events,
and external interfaces.
DAPs help you view hardware and software status. Numerical

DAP poke commands helps you diagnose problems and perform
maintenance functions.
A Web Browser interface helps you view hardware and software

status. The Web interface allows you to invoke maintenance
functions from graphical images representing system components,
and manage system alarms and status indicators.
For more information on MAS administrative interfaces, refer to MAS

System Administration Guide (270-700-167).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

1 - 9
Procedure: Access the MAS administrative interfaces

............................................................................................................................................................................................................................................................
Overview
Purpose
Before you begin
Steps
After the MAS machine is started, the Maintenance Terminal (MT)

window automatically opens a console window and an LMT window.
You can use the following steps to open more LMTs and toggle
between LMT and UNIX console.
This procedure explains how to access the MAS user administrative
interfaces for USDS OA&M tasks.
You must have permission to log on to the MAS to complete this
procedure.
Complete the following steps to access different administrative
interfaces to a MAS.
...........................................................................................................................................................................
Select the option you want from the following table and go to the
referenced step:
If you want to...
Then proceed to...
Open an LMT window from the MT

(optional).
Step 2
Toggle between DAP and USLI in an

LMT window.
Step 3
Access a MAS UNIX console.
Step 4
Access a MAS subshell prompt.
Step 5
...........................................................................................................................................................................
To open a LMT window from the MT (optional):

By default, the LMT window is opened for use automatically. But you
can close it by double-clicking the left-upper corner of the window.
You can open a LMT window manually as follows:
Right-click on an open area of the MT workspace. Select the menu
option to open a LMT window to the MAS you want to work on.
Result: LMT to the selected MAS is displayed.
...........................................................................................................................................................................................................................................................
1 - 10

270-710-919R6.0
...........................................................................................................................................................................
To toggle between the numerical DAP poke prompt and the USLI
prompt in an open DAP window, press F3.
Result: Every time F3 is pressed, the prompt is toggled from its
current location to the DAP or USLI.

Hint: Use F1 to "roll up" the DAP window to allow more scrolling
area for USLI. F1 alternates the DAP window display area.
...........................................................................................................................................................................
To access a MAS UNIX prompt, log on as ainet.

Result: The UNIX prompt is displayed.
Hint: Type [exit] at the UNIX prompt. The window resumes to the
login prompt.
...........................................................................................................................................................................
To access a MAS subshell prompt:
Complete Step 4.
At the MAS UNIX prompt, type the following command:
>subshl
Result: The subshl prompt is displayed.
Hint: To exit subshl and return to UNIX prompt, type [quit] at the
subshl prompt.
Important! For convenience, execute UNIX commands in the
subshell with the MAS exc:unix command, as shown in the
following example:
< exc:unix="ls -l"
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

1 - 11
...........................................................................................................................................................................................................................................................
1 - 12

270-710-919R6.0
Managing the USDS
Overview
............................................................................................................................................................................................................................................................
Purpose
Contents
This chapter introduces the procedures to manage the USDS SPA on

the MAS.
The USDS SPAs
2-2
2-4
Primary HDF status
2-9
2-11
2-17
Back up USDS system
2-19
Recover the USDS system
2-21
Determine the status of USDS SPAs
2-24
Start the USDS SPAs
2-26
Stop the USDS SPAs
2-31
............................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 1
The USDS SPAs
Managing the USDS
The USDS SPAs

............................................................................................................................................................................................................................................................
Overview
The USDS application is delivered to the MAS platform in Service

Package Applications (SPAs). The SPA is an executable software
module that provides telephony and/or data services to a network. A
SPA is delivered in the form of a tar file. This tar file contains the files
and information necessary to install and run the SPA on the MAS.
SPA tar files are normally placed in the MAS platform directory
/etc/SU prior to installation. The tar file name indicates the SPA name
and its version.
In the USDS R6.0, two SPAs run in the MAS nodes:
HDF600-service_logic.full.tar: Contains data and logic that are

needed to perform the HLR Data Function (HDF) of the USDS. It
is referred to as HDF SPA (and the MAS hosting this SPA is called
HDF node) in this document.
HCF600-service_logic.full.tar: Contains data and logic that are

needed to perform the HLR Control Function (HCF) of the USDS.
It is called HCF SPA (and the MAS hosting this SPA is called
HCF node) in this document.
For more information on HDF and HCF concepts, refer to Unified

Subscriber Data Server (USDS) R6.0 Product Overview (270-710917R6.0).
SPA states
A SPA has the following states:
Equipped (EQP): The SPA's configuration data has been installed

on the network element.
Manual Out of Service (MOOS): The SPA's process is running but

cannot receive call traffic. This state is achieved manually.
Out of Service (OOS): Similar to MOOS, but the state is achieved

by SPA itself when "SPA Control" is enabled. However, you need
to remember that the OOS is a transient state.
In Service (IS): The SPA's process is running and it can receive

call traffic.
Disabled (DIS): The SPA's configuration data has not been

completely installed or it is deleted on the network element. This
is an abnormal state that rarely occurs.
...........................................................................................................................................................................................................................................................
2 - 2

270-710-919R6.0
The USDS SPAs
Managing the USDS
Figure 2-1, "State transition of a SPA" (2-3) shows the normal state
transition of a SPA.
Figure 2-1
State transition of a SPA
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 3
Managing the USDS

............................................................................................................................................................................................................................................................
Overview
This topic provides an overview of OA&M impacting concepts related

to communications among the HCF nodes, HDF nodes, eSM, and the
external system.
Primary HDF
HDF nodes are configured in mated pairs. A mated pair serves specific
range of subscribers. The HDF node that is currently being provisioned
by the eSM is referred to as the primary HDF.
The eSM initially chooses a primary HDF node based on the alphabetic
order of the HDF node names. The name that appears first in
alphabetical order is selected as the primary initially, and whenever the
eSM recovers from an initialization.
If the primary HDF node fails, the eSM makes the mate HDF node as
the new primary.
When the failed primary HDF node recovers, it becomes the new
secondary HDF.
A primary HDF:
Secondary HDF
Responds to the service requests received from the HCF nodes
Receives data changes from the eSM
Receives data updates from its mate
Updates the secondary (mated) HDF node when the external

system or the eSM modifies USDS data
Updates eSM when the external system changes Customer

Originated Recent Change (CORC) data in this node.
A secondary HDF is a HDF node whose mate is currently assigned a

primary status.
A secondary HDF:
Responds to service requests received from the HCF nodes
Receives data updates from its mate
Updates the eSM when the external system modifies CORC data
in this node
Updates the primary (mated) HDF node when the external system
modifies USDS data.
...........................................................................................................................................................................................................................................................
2 - 4

270-710-919R6.0

HCF
Managing the USDS
HCF nodes host the service logic that interfaces USDS to external
signaling systems.
HCF nodes:
Communications examples
Receive service requests from the external signaling system
Process the HLR service logic
Request service data from the HDF nodes and send updated data
to the HDF nodes
Send call processing result to the external network element.
Table 2-1, "HCF and HDF communications" (2-5) provides examples

of HCF and HDF communications.
Table 2-1
Communications example
diagram
When...
Then...
HCF node receives a dynamic

update from the external
system.
HCF node sends the message to the

corresponding HDF node, which updates
its mate.
HDF node updates a CORC

field.
HDF node updates its mate and sends the

update to the eSM.
HCF node receives a service

request from the external
system.
HCF node sends the request to a

corresponding HDF node assigned to
serve the requesting subscriber.
HDF node responds to a

service request from a HCF
node.
HDF node responds directly to the

requesting HCF node.
Figure 2-2, "The HCF and HDF communications" (2-6) illustrates the
communications between the eSM, HCF nodes, HDF nodes, and the
external system. The figure depicts that:
HCF nodes send service requests to either HDF node in a pair
HCF nodes send dynamic updates from the external system to

either of the HDF nodes
Either of the HDF nodes can send CORC data updates to eSM
The eSM sends provisioning updates to only the primary HDF

node in a pair
The HDF node in one pair updates its mate.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 5
Managing the USDS
Figure 2-2
Heartbeat messages
among USDS complex
The HCF and HDF communications
In-service HCFs and HDFs exchange heartbeat information in

messages internal to USDS so that each is informed that the others are
up and running.
The HCF or HDF notifies MAS of a heartbeat failure each time it
recognizes that an associated HCF or HDF has failed to send a preconfigure number of successive heartbeat messages.
When a USDS component recognizes a loss of heartbeats from a
previously active component, it initiates actions to bypass the stopped
component by re-routing traffic internally.
...........................................................................................................................................................................................................................................................
2 - 6

270-710-919R6.0
Managing the USDS
Table 2-2
Missed heartbeat responses
When...
Then...
HCF or HDF detects a

configured number of
successive missed heartbeat
messages from an associated
HCF or HDF.
The detecting module considers the

associated HCF or HDF to have failed out of service, and stops sending service
requests to the failed unit.
(The configured number is

typically 3.)
HCF detects failure of one of
a mated pair of HDFs.
The HCF switches all service activities to

the mate HDF.
HCF detects failure of all its

associated HDFs.
The HCF generates a critical alarm and

stops handling service messages until at
least one associated HDF is available.
HDF detects failure of an

associated HCF.
The HDF stops sending data to the failed

HCF.
The MAS receives a failure

notification.
The MAS indicates resulting SPA state

changes in output messages, DAP
updates, and alarms.
Additionally, heartbeat failures generate alarm messages that are

retrieved by the OMC-H. OMC-H aggregates the messages from all
USDS HCFs and HDFs to provide a system view of USDS.
USDS heartbeat failure messages sent to the MAS are stored in /sn/log/
OMlog0 and /sn/log/OMlog1.
The OMlog files used to store SPA output messages hold many
different kinds of messages. You can identify heartbeat failures by
searching the OMlog files for message texts listed in Table 2-3,
"Omlogs for heartbeat failure" (2-8).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 7
Managing the USDS
Table 2-3
Omlogs for heartbeat failure
Message text
Indication
APPLICATION FAILOVER;
NOWBECOMING
PRIMARY HDF MATE
The reporting HDF detected heartbeat

failure of the primary HDF and is taking
over as the primary HDF.
Note: Omlog ID:10009

Both HDF=<number>, AND
MATE HDF ARE OOS,
CAN'T ACCESS DB
The HCF Index Server detected that the

HDF represented by <number> and its
mate are OOS.

HCF LOST
CONNECTIVITY TO ALL
HDFS, BLOCKING SS7
LINKS
The reporting HCF lost connectivity to

all its associated HDFs. It blocked its SS7
links, so no service requests can be made
to this HCF.

PUTTING HDF <node_id>
INTO OOS STATE
REASON: MISSED <n>
HEARTBEATS
Note: Where <n> represents
the configured number.
Omlog ID:10101
The reporting HCF detected the

configured number of consecutive
heartbeat failures for the HDF
represented by <node_id>. The HCF
considers that HDF is out of service.The
HCF will not use the HDF for service
requests until its state changes to IS (in
service).
...........................................................................................................................................................................................................................................................
2 - 8

270-710-919R6.0
Primary HDF status
Managing the USDS
Primary HDF status

............................................................................................................................................................................................................................................................
Overview
In a mated pair, the primary status is assigned to the HDF node that
receives provisioning data from a provisioning system, like eSM, RCV
etc.
If both HDF nodes in the pair are in service when the eSM is selecting a
primary, the primary HDF will be chosen based on the alphabetic order
of the HDF node names. A primary HDF is the HDF node that the eSM
is currently communicating to. Circumstances may arise when the
primary status of a HDF change.
The secondary HDF in service automatically changes into the primary
HDF when:
The primary HDF software or hardware fails
The primary HDF becomes isolated from USDS due to network

problems
The primary HDF is removed from service by the MAS platform

or by a technician's Input Message
The TimesTen database of the primary HDF fails.
In USDS R6.0, changing the primary status between a HDF node and
its mate is done automatically if any of the above conditions occurs.
You can change the primary HDF manually only by removing the
current primary HDF from service.
When a HDF node becomes the primary HDF, it will remain the
primary status even after the mate HDF node recovers from its failure
condition.
HDF role transition
There is at most one primary HDF in a mated pair. Only IS HDF can be
primary. A HDF in any other state can only be secondary.
Typically, the HDF which becomes an IS first takes up the primary role.
Secondary-IS HDF takes up primary role if the original primary-IS
HDF changes to non-IS
In case secondary-IS HDF receives two or more provisioning messages
from eSM/RCV, the original primary-IS HDF should change to
secondary-IS and then the original secondary-IS HDF takes over the
primary role.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 9
Primary HDF status
Managing the USDS
Note: Only IS HDF can process provisioning messages.
In some special cases, for example, if two HDFs start up at

exactly the same time and both HDFs are primary, a
predefined algorithm is used to decide which HDF remains
primary.
Note: The predefined algorithm works such that the HDF whose
logical name appears first in the alphabetical listing will remain
primary. This algorithm is consistent with the one used by eSM to
pick one HDF as primary when eSM starts up.
...........................................................................................................................................................................................................................................................
2 - 10

270-710-919R6.0
Managing the USDS

............................................................................................................................................................................................................................................................
The HDFs operate as active-active mated pairs. When USDS data

changes in a HDF, it updates its mate HDF using TimesTen replication
capability.
As the USDS system operates, HDF data is changed by:
eSM provisioning activity
Customer Originated Recent Change (CORC)
Normal system operation.
Mated HDFs need to have their data changes synchronized so that they
both accurately represent the current state of the system and its
subscribers.
When a HDF's data is changed, it updates its mate as illustrated in
Figure 2-3, "HDF data replication" (2-11). The figure depicts MASmanaged replication as follows:
The updated HDF's changes are sent to a log file.
The log file changes are sent to the mate HDF as other operations
permit.
The mate HDF's database is updated.
Figure 2-3, "HDF data replication" (2-11), illustrates only one direction
for the sake of simplicity.
Figure 2-3
HDF data replication
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 11
Managing the USDS
USDS data changes in one HDF are stored in a TimesTen log file
before they are sent to the mate HDF. HDF data can go out of sync with
its mate when the log file fills up due to any circumstance that causes
the mate HDF to be unavailable, including:
HDF failure
HDF in maintenance out of service state
Network problems
MAS platform software problems
Under most conditions, the MAS platform software automatically

recovers replication when the problem is resolved.
The platform provides a prompt if technician intervention is required.
...........................................................................................................................................................................
CAUTION
It is very important to verify which HDF failed
replication, and which reported the failure. Attempting
to recover replication on the wrong HDF will result in
loss of service and the need to recover static and
dynamic data on both mated HDFs.
When data replication fails, the secondary HDF moves to OOS status,
and the primary HDF continues its operation. This strategy ensures data
consistency as only one HDF is working.
If the date replication fails and primary HDF is not IS, to decide if the
secondary HDF must be changed to IS becomes difficult. It depends
not only on the context, but also on the customer preference which is
depicted in detail in "Customer preference impact on HDF state
transition" (2-17).
Table 2-4, "Example - Automatic replication recovery" (2-13),
describes a scenario for replication failure with automatic recovery.
...........................................................................................................................................................................................................................................................
2 - 12

270-710-919R6.0

Table 2-4
Managing the USDS
Example - Automatic replication recovery
When...
Then...
The detecting HDF generates the
following output message:
HDF DETECTED TIMESTEN
DATABASE REPLICATION FAILURE
(PRIMARY HDF MATE)
CONTINUING OPERATION
Note: Omlog ID- 10004
The secondary HDF generates the
A primary HDF MAS detects

replication failure

DATABASE REPLICATION
FAILURE\n(SECONDARY HDF
MATE) SUSPENDING OPERATION
UNTIL REPLICATION RECOVERS
The reporting HDF is the HDF that is in
service. The mate HDF is the HDF that
has failed replication.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 13
When...
Managing the USDS
Then...
RECOVERY (PRIMARY HDF MATE)
The mate HDF recovers

replication automatically.
The secondary HDF generates the

RECOVERY\n(SECONDARY HDF
MATE) RESUMING OPERATION
The messages indicate that replication is
recovered in the mate HDF and normal
active-active operation is restored. The
detecting HDF continues to operate as the
primary.
Table 2-5, "Output messages - Manual replication recovery" (2-15),

describes a scenario for replication failure with manual recovery.
...........................................................................................................................................................................................................................................................
2 - 14

270-710-919R6.0

Table 2-5
Managing the USDS
Output messages - Manual replication recovery
When...
Then...
A primary HDF MAS detects

replication failure.

DATABASE REPLICATION FAILURE
(PRIMARY HDF MATE)
The reporting HDF is the HDF that is in
service. The mate HDF is the HDF that
has failed replication.
The mate HDF fails to

recover replication before the
detecting HDF's TimesTen
log file reaches 75% capacity.
The MAS platform for the detecting HDF

generates an alarm and the following two
output messages:
Since Replication has not restarted, all
transactions will be merged into the
database
Run the command "TTstartreplicate " on
the Replication Peer machine when
replication comes back
When you see this

set of output messages, perform
OA&M as required to restore the
failed HDF. Then, perform
"TTstartreplicate" on the failed
HDF as directed in "Recover the
HDF TimesTen database from the
mated HDF node" (3-8).
Important!
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 15
Managing the USDS
When...
Then...
You perform the procedure

on the failed HDF.
Replication recovers, including:

The entire HDF database is copied from
the primary HDF to the mate.
MAS generates interim output
messages as the process completes.
Technician restarts the failed MAS.
The mate HDF recovers

replication and restarts.

RECOVERY
(PRIMARY HDF MATE)
The message indicates that replication is
recovered in the mate HDF and normal
active-active operation is restored. The
detecting HDF continues to operate as the
primary.
...........................................................................................................................................................................................................................................................
2 - 16

270-710-919R6.0
Customer preference impact on HDF state

transition
Managing the USDS

............................................................................................................................................................................................................................................................
Overview
Normal HDF state transition follows the SPA state transition process as
depicted in SPA states. But since HDF nodes are in mated pairs, their
state transition may depend on its mate's state and role to a large extent.
Customer preference
impact on HDF state
transition
If the data replication fails and the mated HDF's state is not IS,
deciding if the HDF should be changed to IS and also which HDF must
be selected for this transition becomes difficult. The decision depends
not only on the context, but also on the customer preference.
From USDS R6.0, a new attribute "Customer Preference" is added into
table "Global Parameter" to indicate the customer's preference and
record the context respectively. "Customer Preference" can be
configured from eSM to take one of the following values:
1 = Avoid Data Inconsistency. If the two HDFs cannot decide which
has the latest data, both remain in non-IS, waiting for the manual
operation.
This option takes data as the top priority.
2 = Minimize Service Down Time. Unless both the HDFs are down,
there is always at least one HDF In-Service, even at the cost of losing
latest data.
This option takes service as top priority.
3 = Maximize Data Consistency and Minimize Service Down Time
(Default Value). USDS automatically decides which HDF should be IS
and attempts to let the HDF with latest data in service. However, there
may be cases (though very rare) when the USDS makes the wrong
decision.
This option expects a good balance between the data and service.
The data which is used to judge which HDF has the latest data (i.e. the
latest primary HDF) is provided in "Latest primary HDF" (2-18).
If the customer prefers option 1 or 3, SPA might decide to stay in the
OOS state, while the customer might want to bring SPA to IS manually.
A send:text command is provided for this purpose:
<SND:TEXT="ForceToLive",rk=HDF600;
This command forces an OOS HDF to move to IS state.

...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 17
Customer preference impact on HDF state

transition
Latest primary HDF
Managing the USDS
The HDF internal table "DF Infor" is introduced to record which HDF
is the latest primary HDF. There is at most one record in this table and
its data is replicated between the two-mated HDFs and cannot be
provisioned from eSM. Initially, when HDF is newly installed, no
record exists in table "DF Infor". At this time, HDF treats itself as the
latest primary. When a HDF becomes primary, it updates/inserts (if no
record is present) a record into this table.
Table 2-6, "Data in "DF Infor" for latest primary HDF" (2-18) indicates
which HDF is the latest primary HDF. This table can only be updated
by primary HDF and cannot be provisioned from the eSM.
Table 2-6
Data in "DF Infor" for latest primary HDF
Attribute Name
Description
Index
Table key
Primary DF
Primary HDF Site Name
Change Primary Time
Change Primary HDF Time
...........................................................................................................................................................................................................................................................
2 - 18

270-710-919R6.0
Back up USDS system
Managing the USDS
Procedure: Back up USDS system

............................................................................................................................................................................................................................................................
Purpose
Use this procedure to create a complete backup of the MAS software

and databases, including USDS SPA and its associated data, on tape,
disk or DVD.
This procedure backs up all SPA(s), databases and
system software in the MAS node. It is not SPA-specific.
Important!
Before you begin
Ensure that you have:
Got the root access to the MAS node.
Set the "TAPE_CAPACITY" in

/opt/config/data/bkup_tape_capacity to 33000000 for Netra 1280s
(for using with DDS-4/DAT72 tapes).
Done a full back up to disk before back up to tape or back up to

DVD.
Prepared the right tape, disk or DVD.

Important!
Steps
1.
The tape drive in Netra 1280s cannot write to DDS-2 or older

tapes. On Netra 1280, DDS-4/DAT72 tapes are used. On
Netra 440, DVD-RW or DVD-R format DVDs are used.
2.
Currently, only Netra 440 supports the back up to DVD.
3.
Refer to section "Performing basic DVD operation" in

Chapter 5 Backup of MAS Maintenance Guide (270-700169) to format the DVD before backing up data into the DVD
disc.
4.
A full back up includes Database, Application and System

back up. Full back up should be performed after any software
installation and before any back up to tape and DVD.
Complete the following procedure using MAS user documentation for

detailed information:
...........................................................................................................................................................................
Open a UNIX subshl or DAP USLI window to the MAS you want to
back up. For more information, refer to "Access the MAS
administrative interfaces" (1-10).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 19
Back up USDS system
Managing the USDS
...........................................................................................................................................................................
To back up the system to disk, continue with Step 3. To back up the

system to tape, continue with Step 4. To back up to DVD, continue with
Step 5.
A back up to disk must be done before back up to tape
or back up to DVD can be done.
Important!
...........................................................................................................................................................................
Complete the following procedures from Chapter 5 Backup of MAS

Maintenance Guide (270-700-169):
Backup Application to Disk
Backup Database to Disk
Backup System to Disk
...........................................................................................................................................................................
Complete the following procedures from Chapter 5 Backup of MAS

Backup Application to Tape
Backup Database to Tape
Backup System to Tape
...........................................................................................................................................................................
Complete the following procedure from Chapter 5 Backup of MAS

Backup Application to DVD
Backup Database to DVD
Backup System to DVD
...........................................................................................................................................................................
To back up another MAS, repeat the above steps.

END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
2 - 20

270-710-919R6.0
Managing the USDS
Procedure: Recover the USDS system

............................................................................................................................................................................................................................................................
Purpose
Use this procedure to recover the MAS software and databases,

including USDS SPA and its associated data, after a MAS failure.
This procedure recovers all MAS SPA(s), databases and system
software. It is not SPA-specific.
...........................................................................................................................................................................
CAUTION
Recovery procedures are service impacting. Verify the
situation and the recovery data source(s) with Lucent
Technologies technical support before performing
recovery procedures.
...........................................................................................................................................................................
CAUTION
Do not stop or interrupt the recovery process during
its execution.
Before you begin
Got the root access to the console of the MAS node.
Got the tape media or DVD that store a previously created "all"
backup.
Set the "TAPE_CAPACITY" in

/opt/config/data/bkup_tape_capacity to 33000000 for Netra 1280s
(for using with DDS-4/DAT72 tapes).
Important!
Steps
The tape drive in Netra 1280s cannot write to DDS-2 or older

tapes. On Netra 1280, DDS-4/DAT72 tapes are used. On Netra
440 DVD-RW or DVD-R format DVDs are used.
Currently, only Netra 440 supports the recovery from DVD.
Complete the following procedure to recover a MAS node, including

the SPA and its associated data from disk, tape or DVD.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 21
Managing the USDS
...........................................................................................................................................................................
Open a UNIX subshl or DAP USLI window to the MAS you want to
recover. See "Access the MAS administrative interfaces" (1-10) for
reference.
...........................................................................................................................................................................
To recover the system from disk, continue with Step 3. To recover the
system from tape, continue with Step 4. To recover the system from
DVD, continue with Step 5.
...........................................................................................................................................................................
Complete the following procedures from Chapter 6 Recovery of MAS

Recover System from Disk
Note: Type the command "Start" to mount MAS file systems.
Recover Database from Disk
Note: Skip /etc/Astart in this procedure.
Recover Application from Disk
Note: Execute /etc/Astart at the end.

...........................................................................................................................................................................
Complete the following procedures from Chapter 6 Recovery of MAS

Recover System from Tape
Note: Enter the command "Start" to mount MAS file systems.
Recover Database from Tape
Recover Application from Tape

...........................................................................................................................................................................
Complete the following procedure from Chapter 6 Recovery of MAS

Recover System from DVD
Note: Type the command "Start" to mount MAS file systems.

...........................................................................................................................................................................................................................................................
2 - 22

270-710-919R6.0
Managing the USDS
Recover Database from DVD
Recover Application from DVD

...........................................................................................................................................................................
To recover another MAS, repeat the above steps.

END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 23
Managing the USDS
Procedure: Determine the status of USDS SPAs

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Reference
Steps
Use this procedure to determine the status of HCF SPA/HDF SPA. You
may need to determine the status of HCF SPA/HDF SPA before
proceeding with troubleshooting procedures.
Ensure that you have got the MAS customer documentation for
reference.
For SPA states, see "SPA states" (2-2)
Perform the following steps to determine the status of HCF SPA/HDF
SPA.
In the procedure, <USDS_HCF or USDS_HDF>
represents the actual name of the USDS SPA.
Important!
...........................................................................................................................................................................
CAUTION
At each step, wait for the result of an Input Message
before continuing to the next step.
...........................................................................................................................................................................
Open a UNIX subshl or DAP USLI window to the MAS that hosts the
SPA you want to start. For help, refer to procedure "Access the MAS
...........................................................................................................................................................................
Determine the SPAs state by typing the following command:

< OP: STATUS, SPA=<USDS_HCF or USDS_HDF>;
Example: OP: STATUS, SPA=HCF600;

Result: The MAS returns the SPA's status which is one of the
following:
DIS - "INSTALL: SPA, CONFIG" command execution

failed and the SPA is not installed.
...........................................................................................................................................................................................................................................................
2 - 24

270-710-919R6.0
Managing the USDS
EQP - The SPA is loaded on the MAS and configured, but it

is not running and is not available for service.
MOOS - The SPA is running but is not available for service,
which is brought manually.
OOS - The SPA is running but is not available for service,
which is brought by SPA itself.
IS - The SPA is running and processing service requests.
...........................................................................................................................................................................
To determine the status of another SPA, return to Step 2.

END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 25
Start the USDS SPAs
Managing the USDS
Procedure: Start the USDS SPAs

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Steps
Use this procedure to start a stopped HCF or HDF SPA. A SPA could
be stopped because:
It was taken out of service by a MAS process
It was taken out of service by a maintenance procedure
A hardware failure occurred.
Ensure that you:
Are working with the correct SPA
Have collected the MAS customer documentation for reference.
Perform the following steps to start a HCF or HDF.

In the procedure, <USDS_HCF or USDS_HDF>
Important!
...........................................................................................................................................................................
CAUTION
...........................................................................................................................................................................
SPA you want to start. For help, refer to procedure "Access the MAS
...........................................................................................................................................................................
Determine the SPAs state by typing the following command in the

subshell:
<OP: STATUS, SPA=<USDS_HCF or USDS_HDF>;

Result: An output similar to the following example is displayed:
+++ SGLCF23 2005-09-07 17:40:15 MAINT /SA055 #000336 as001 LEAD >
OP STATUS SPA HCF600
...........................................................................................................................................................................................................................................................
2 - 26

270-710-919R6.0
Start the USDS SPAs
Managing the USDS
SPA NAME: HCF600

SPA STATE: EQP
NET/INT SSN [STATE]: 256 [DIS];
END OF REPORT #000336++-
If the SPA state is...
Then go to...
EQP
Step 3
MOOS
Step 5
DIS
The state "DIS" indicates that a failure

occurred when INSTALL: SPA,
CONFIG was run. You cannot start the
SPA until INSTALL:SPA,CONFIG is
executed successfully.
IS
The state "IS" indicates that SPA is

running and processing service requests.
...........................................................................................................................................................................
At the subshell command line, type the following command:

< INSTALL: SPA = <USDS_HCF or USDS_HDF>, PROC;
Example: INSTALL: SPA = HCF600, PROC;

Result: An output similar to the following is displayed.
INSTALL PROC SPA HCF600 IN PROGRESS
0 of 1 COMPLETE
END OF REPORT #000514++<
M INSTALL PROC,SPA HCF600 COMPLETE - SUMMARY REPORT:
OPERATION
STATUS
----------------------------------------------------SPA PROCESS INSTALLATION: SUCCEEDED
SPA DATA READ ERRORS:
0
REGISTRATION ERRORS:
0
END OF REPORT #000519++...........................................................................................................................................................................
Verify the SPA's status by typing the following command in the

subshell:
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 27
Start the USDS SPAs
Managing the USDS
Result: The SPA state should be in the MOOS state, as indicated by
a message similar to the following example:

SPA NAME: HCF600
SPA STATE: MOOS
NET/INT SSN [STATE]: 256 [OOS];
PROCESS
---------HCF600
CC
STATE
DEBUGGER
----------------as001 ACTIVE
INACTIVE
END OF REPORT #000353++...........................................................................................................................................................................
At the subshell command line, type the following command:

<RST: SPA=<USDS_HCF or USDS_HDF>;
Example: RST: SPA=HCF600;

Result: A message similar to the following is displayed.
M RST SPA HCF600 COMPLETED SUCCESSFULLY
Note: After the execution, the SPA is brought to OOS state actually,
which is a transient state. When the SPA confirms it is capable of
receiving traffic again, it will set its state to IS automatically.
...........................................................................................................................................................................
Verify the SPA's state by typing the following command in the subshell:

Result: The SPA state should be in the IS state, as indicated by a
message similar to the following example:

SPA NAME: HCF600
SPA STATE: IS
NET/INT SSN [STATE]: 256 [IS];
PROCESS
CC
STATE
DEBUGGER
...........................................................................................................................................................................................................................................................
2 - 28

270-710-919R6.0
Start the USDS SPAs
Managing the USDS
---------HCF600
---as001
------ACTIVE
-------INACTIVE
END OF REPORT #000392++...........................................................................................................................................................................
[Optional] Verify that the DAP for the associated SPA indicates that its
status is IS.
...........................................................................................................................................................................
For a HCF node, identify the state of the local links by typing the
following command in the subshell:
< OP:SLK=LOCAL;
Example: An output message similar to the following example is
displayed:
...........................................................................................................................................................................
If the SS7 link is active, but is not in the IS state ("LINK

AVAILABILITY STATE" currently is "UNAVAILABLE"), confirm
whether it is manually inhibited for SPA restart. If yes, then it must be
uninhibited by typing the following command in the subshell:
< ALW:SLK=a-b-c;
Note: "a-b-c" identifies a unique link. For more detailed information,

refer to Part I: Input Messages, MAS User Reference Guide (270-700176).
displayed:
< ALW:SLK=0-1-1; PF
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 29
Start the USDS SPAs
Managing the USDS
+++ HLR_CF10 2005-12-13 16:27:14 MAINT /S4742 #000209 as099 LEAD >
M ALW SLK=0-1-1 COMPLETED SUCCESSFULLY
END OF REPORT #001468++...........................................................................................................................................................................
10
Verify the "LINK AVAILABILITY STATE" is changed to

"AVAILABLE" by the following command:
< OP:SLK=LOCAL;
displayed:
...........................................................................................................................................................................
11
To start another SPA, return to Step 1.

END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
2 - 30

270-710-919R6.0
Stop the USDS SPAs
Managing the USDS
Procedure: Stop the USDS SPAs

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to stop a HCF or HDF SPA. Following are the
reasons for stopping a SPA:
The process is not operating correctly.
To perform a hardware repair or upgrade.
To completely remove a SPA and reinstall it, contact Lucent

Technologies technical support.
Ensure that you are stopping the SPA on the correct MAS.
Collect the MAS customer documentation for reference.
...........................................................................................................................................................................
CAUTION
Stopping a SPA on the wrong MAS can result in
degraded or interrupted service.
...........................................................................................................................................................................
CAUTION
Steps
Perform the following steps to stop a HCF SPA or HDF SPA.

Important! In the procedure, <USDS_HCF or USDS_HDF>
...........................................................................................................................................................................
Open a UNIX subshl or DAP USLI window to the MAS from which
you want to stop a SPA. For help, refer to procedure "Access the MAS
...........................................................................................................................................................................
On one HFC node, identify the state of the local links by typing the
following command in the subshell:
< OP:SLK=LOCAL;
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 31
Stop the USDS SPAs
Managing the USDS
Example: The output message is similar to the following example:
...........................................................................................................................................................................
If the "LINK AVAILABILITY STATE" is AVAILABLE, block the link

using the following command:
< INH:SLK=a-b-c;
Note: "a-b-c" identifies a unique link. For more detailed information,

refer to Part I: Input Messages, MAS User Reference Guide (270-700176).
Example: INH:SLK=0-1-1;
Result: An output message similar to the following example is
displayed:
If a failure is encountered during the execution of the

step, check if this is the last in-service link in the link set. If yes,
bring up one or more links in the same link set at other HCFs before
retrying to inhibit the link that had the failure.
Important!
...........................................................................................................................................................................
Verify if the "LINK AVAILABILITY STATE" is changed to

"UNAVAILABLE" by the following command:
< OP:SLK=LOCAL;
...........................................................................................................................................................................................................................................................
2 - 32

270-710-919R6.0
Stop the USDS SPAs
Managing the USDS
displayed:
...........................................................................................................................................................................
Repeat Step 3 until all the local links to the HCF node are inhibited.
...........................................................................................................................................................................
Repeat Step 2 to Step 5 to ensure the local links of all the HCF nodes
are inhibited.
...........................................................................................................................................................................
Identify the SPA's state by typing the following command in the

subshell:

Result: The MAS displays the SPA's state in a message similar to
the following example:

SPA NAME: HCF600
SPA STATE: IS [or OOS, or MOOS, or EQP]
SSN [STATE]: 256 [IS]; [or OOS, or MOOS, or EQP]
PROCESS
CC
STATE
DEBUGGER
----------
----
-------
--------
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 33
Stop the USDS SPAs
Managing the USDS
HCF600
as001
ACTIVE
INACTIVE
If the SPA state is...
Then go to...
IS
Step 8
OOS
Step 8
MOOS
Step 11
EQP
The state "EQP" indicates that the SPA

has already been stopped.
DIS
The state "DIS" indicates that a failure

occurred when INSTALL: SPA, CONFIG was run.
...........................................................................................................................................................................
Remove the SPA from service by typing the following command in the
subshell:
<RMV: SPA=<USDS_HCF or USDS_HDF>
Example: RMV: SPA=HCF600;

Result: The MAS responds with a confirmation prompt similar to
the following.
RMV: SPA REMOVES NEW CALL TRAFFIC, CONTINUE Y OR N?
...........................................................................................................................................................................
Press [Y] to remove the SPA from service.

Result: The following output message indicates the SPA is out of
service:
RMV SPA <USDS_HCF or USDS_HDF> COMPLETED SUCESSFULLY
...........................................................................................................................................................................
10
Verify the SPA state is MOOS by typing the following command in the
subshell:


SPA NAME: HCF600
SPA STATE: MOOS
...........................................................................................................................................................................................................................................................
2 - 34

270-710-919R6.0
Stop the USDS SPAs
Managing the USDS
SSN [STATE]: 256 [OOS];

PROCESS
CC
STATE
----------
----
HCF600
as001
DEBUGGER
-------
--------
ACTIVE
INACTIVE
...........................................................................................................................................................................
11
Stop the SPA by typing the following command in the subshell:

<DELETE: SPA=<USDS_HCF or USDS_HDF>, PROC;
Example: DELETE: SPA=HCF600, PROC;


DELETE: SPA REMOVES SPA PROCESS, CONTINUE Y OR N?
...........................................................................................................................................................................
12
Press [Y] to stop the SPA.

Result: The following output indicates the SPA is stopped:
DELETE PROC SPA <USDS_HCF or USDS_HDF> COMPLETED
SUCESSFULLY
...........................................................................................................................................................................
13
Verify the SPA state is EQP by typing the following command in the
subshell:
<OP: STATUS, SPA=<USDS_HCF>;


SPA NAME: HCF600
SPA STATE: EQP
SSN [STATE]: 256 [DIS];
The SPA is stopped.
END OF STEPS
...........................................................................................................................................................................
Related procedures
Procedure "Start the USDS SPAs" (2-26) is related to starting the SPAs.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

2 - 35
Stop the USDS SPAs
Managing the USDS
...........................................................................................................................................................................................................................................................
2 - 36

270-710-919R6.0
Overview
............................................................................................................................................................................................................................................................
Purpose
Contents
This chapter introduces the procedures related to the USDS database

management.
3-3
Back up HDF TimesTen database to disk, tape/DVD
3-6
Recover the HDF TimesTen database from the mated HDF

node
3-8
Recover the HDF TimesTen database from tape or disk
3-10
Recover a subset of HDF TimesTen database from eSM
3-12
Access SPA-related data from MAS nodes
3-14
Disaster recovery for a HDF pair
3-26
3-27
Execute load balancing from eSM
3-37
Run load balancing removal tool
3-47
Re-lock the USDS features from the eSM
3-51
3-54
............................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 1
Index server full init- HDF pump
3-56
Index server full init-peer pump
3-58
Configure RC/V form access permissions
3-60
Assign Form Permissions to Restricted WPS Logins
3-61
...........................................................................................................................................................................................................................................................
3 - 2

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview
The data stored in USDS complex is shown in Figure 3-1, "Data

storage in USDS" (3-3)
Figure 3-1
Data storage in USDS
Each HDF SPA maintains a copy of static and dynamic USDS data in
the MAS TimesTen database. The database contains subscriber data
used by the service logic processing.
Tasks that are associated with HDF database maintenance include:
Backing up the TimesTen database to tape /DVD and disk
Recovering the TimesTen database from the mate HDF node
Recovering the TimesTen database from tape or disk
Recovering a subset of the TimesTen database from the eSM
Accessing SPA-related data from MAS node
Performing disaster recovery of a HDF pair
Load balancing for HDF pairs
Relocking USDS features
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 3
Each HCF SPA maintains a copy of Index Server routing data. It is also
stored in TimesTen database. This database contains the routing
information from HCF nodes to find the correct HDF nodes. The HCF
nodes maintain the Index Server data. Normally, it does not need
manual interactions, except for the following situations:
USDS database
interactions for service
data
Index Server full initialization for the first HCF node in the
complex
Index Server peer pump in case of failure recovery
Figure 3-2, "USDS database interactions" (3-4) shows the components

that store or modify USDS service related data.
Figure 3-2
USDS database interactions
Following points are depicted in the above figure:
The eSM stores the "golden" copy of USDS data
When provisioners modify USDS data, the eSM copy and the
primary HDF copy are updated
Updates flow through the primary HDF to its mate
...........................................................................................................................................................................................................................................................
3 - 4

270-710-919R6.0
Database interactions
impact to maintenance
HCF nodes update HDF dynamic database entries as a part of

normal system operations
When the system updates dynamic HDF entries, the
HDF node updates its mate
HDF node updates the eSM (CORC fields only)
Understanding USDS database interactions helps you decide which

database recovery tasks to perform. The database interactions indicate
that at any given point of time there may be slight mismatches between
eSM data and HDF data. As a result:
The eSM copy is the latest one from a provisioning perspective.

So, its data is typically more reliable if you are concerned about
the static data associated with subscribers and system
configurations.
Important! To recover USDS data from the eSM using the eSM
"Load Active Data" capability, you must use the "HDF-BypassValidation, Version 600" view to create all load requests.
Database backups
HDF-generated backups stored on tape or disk capture a snapshot

of the entire database at a specific point of time, and they are most
desirable for restoring the HDF nodes to a known state after
significant system outages.
The HDF copy is most up-to-date from a dynamic data

perspective.
To be fully prepared for database recovery, you need to make periodic

backups of the HDF databases. Backup procedures are provided by the
MAS built-in OA&M support.
The detailed procedures to create backups and recover the system from
backups are described in the MAS Maintenance Guide (270-700-169).
Backup of eSM database is important to your HDF database recovery
strategy. The procedures for making eSM backups and restoring eSM
from backups are described in the eSM user documentation.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 5
Back up HDF TimesTen database to disk, tape/

DVD
Procedure: Back up HDF TimesTen database to disk, tape/DVD

............................................................................................................................................................................................................................................................
Purpose
Use this procedure to make a backup copy of the HDF's TimesTen data
to tape or disk. To make a complete set of HDF tape or disk backup,
you must perform this procedure for each HDF node in the system.
This high level procedure is not intended to replace the
detailed procedures in the MAS platform user documentation.
Important!
Important!
A backup to disk must be done before a backup to
tape/DVD.
Before you begin
To perform this procedure, you must have root access to the console of
the MAS via LMT or a command line interface.
The "TAPE_CAPACITY" in
/opt/config/data/bkup_tape_capacity is set to 33000000 for Netra
1280s (for using with DDS-4/DAT72 tapes). The tape drive in Netra
1280s cannot write to DDS-2 or older tapes. On Netra 1280, DDS4/DAT72 tapes are used.
Important!
Refer to section "Performing basic DVD operation" in

Chapter 5 Backup of MAS Maintenance Guide (270-700-169) to
format the DVD before backing up data into the DVD disc.
Important!
Steps
Perform the following procedure, using MAS user documentation for

details, to back up HDF data to tape or disk:
Important!
You must complete this procedure for each HDF node.
...........................................................................................................................................................................
Access a command line interface to the HDF whose data you want to
back up to tape or disk. Refer to "Access the MAS administrative
interfaces" (1-10) as required.
...........................................................................................................................................................................
Complete the "Procedure: Backup TimesTen Database to Disk",

"Procedure: Backup TimesTen Database to DVD" or "Procedure:
Backup TimesTen Database to Tape" from the "Backup" section of the
MAS Maintenance Guide (270-700-169).
...........................................................................................................................................................................................................................................................
3 - 6

270-710-919R6.0
Back up HDF TimesTen database to disk, tape/

DVD
Important! At least one complete "Full back up to disk" is needed

after a new SU is installed (refer to Procedure: "Back up USDS
system" (2-19). Otherwise, backup TimesTen to disk/tape/DVD will
fail.
...........................................................................................................................................................................
Exit the command line interface accessed in Step 1.

...........................................................................................................................................................................
To back up another HDF TimesTen database, return to

Step 1.
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 7
Recover the HDF TimesTen database from the

mated HDF node
Recover the HDF TimesTen database from the mated HDF node
............................................................................................................................................................................................................................................................
Overview
The HDF nodes are deployed as mated pairs with bi-directional

replications. If one of the HDF nodes fails, the mated HDF can be used
to restore the TimesTen data.
Important! This procedure is recommended to recover one failed
HDF node if the other HDF node is alive in the mated pair.
There is a FAILTHRESHOLD provided by TimesTen to indicate

whether the replication can be recovered automatically from the
surviving HDF node.
Automatic recovery: If the failed HDF node is restarted before

the FAILTHRESHOLD has been reached on the surviving HDF
node, you can restart the failed system and get the data
synchronizing automatically from the surviving HDF node to the
failed HDF node.
Manual recovery: If the failed HDF node is restarted after the

FAILTHRESHOLD has been reached on the surviving HDF node,
the failed HDF data store must be copied again from the surviving
HDF using the command "TTstartreplicate" scripts. The command
"TTstartreplicate" needs to be executed on the failed HDF and not
the surviving HDF. After that, the failed HDF mate gets
recovered.
You can check the FAILTHRESHOLD by running the following

subshell command on the surviving HDF node:
<op: status, ttrepl
Result: An output similar to the following example is displayed.

+++ ISQUAD_DF11 2004-06-22 16:46:48 MAINT /X1043 #000109 as011
LEAD >
M TIMESTEN REPLICATION STATUS:
LOCAL HOST: ISQUAD_df11
DATASTORE: tt41data
NETWORK STATE: NORMAL
REPLICATION STATE: UNEQ
LOG SIZE STATE: NORMAL
REPLICATION MATE HOST: ISQUAD_df12
DATASTORE: tt41data
REPLICATION STATE: UNEQ
...........................................................................................................................................................................................................................................................
3 - 8

270-710-919R6.0
Recover the HDF TimesTen database from the

mated HDF node
If the "LOG SIZE STATE:" is "NORMAL", the failed HDF node can
be automatically recovered.
Note: Command "TTstartreplicate" must not be executed on HDF node
in IS state. For example, when replication is shut down or failed, USDS
will keep the primary HDF in service and pull secondary HDF down to
OOS. Then "Ttstartreplicate" can be only run on the secondary HDF to
sync up the data in TimesTen, otherwise, data loss will occur.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 9
Recover the HDF TimesTen database from tape

or disk
Procedure: Recover the HDF TimesTen database from tape or disk

............................................................................................................................................................................................................................................................
Purpose
Use this procedure to restore the USDS data in HDF TimesTen

database to a known state as archived in a MAS tape or disk backup.
Important! Use this procedure only to recover one of the HDF
nodes if both nodes in one pair have crashed. There may be conflict
in data between the mated pair if this procedure is used to recover
both HDF nodes in one pair.

detailed procedures in the MAS platform user documentation.
Important!
Before you begin
Steps
Determine which data recovery source best resolves your current

data recovery needs. In typical cases, the disk backup copy is the
most recent backup, while the tape backup copy represents a
slightly older snapshot of the data.
If you choose to recover from tape, acquire the tape cartridge you
want to use for the recovery procedure. Ensure that you use the
tape that was previously created from the failed MAS node.
To perform this procedure, you must have root access to the

console of the MASs via LMT or a command line interface.
Perform the following steps to restore HDF data from tape or disk.
Recovery procedures are service impacting. Verify the
situation and the recovery data source(s) with Lucent Technologies
technical support before performing recovery procedures.
Important!
...........................................................................................................................................................................
Access a command line interface to the HDF node whose data you
want to restore from tape or disk. Refer to "Access the MAS
administrative interfaces" (1-10) as required.
...........................................................................................................................................................................
Complete the "Procedure: Recovery Timesten Database from Tape" or

the "Procedure: Recovery TimesTen Database from Disk" from the
"Recovery" section of the MAS Maintenance Guide (270-700-169).
...........................................................................................................................................................................
Exit the command line interface accessed in Step 1.
...........................................................................................................................................................................................................................................................
3 - 10

270-710-919R6.0
Recover the HDF TimesTen database from tape

or disk
...........................................................................................................................................................................
To recover another HDF TimesTen database, repeat the above steps.

END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 11
Recover a subset of HDF TimesTen database

from eSM
Procedure: Recover a subset of HDF TimesTen database from eSM

............................................................................................................................................................................................................................................................
Purpose
Use this procedure to recover HDF data from the "golden" copy stored
on the eSM.
Recover HDF data from the eSM when you want to restore a known
subset of USDS data to all HDF nodes, rather than restoring all the data
for selected HDF nodes.
This procedure can only recover the static data provisioned from eSM.
It cannot recover the dynamic data.
Due to performance constraints on the provisioning
interface, it is not possible to recover large sets of HDF subscriber
data from the eSM. Mass data recovery should be accomplished by
recovering data from a known HDF (refer to "Recover the HDF
TimesTen database from the mated HDF node" (3-8)) or recovering
from Timesten Database Backup (refer to "Recover the HDF
TimesTen database from tape or disk" (3-10).
Important!

detailed procedures in the eSM user documentation.
Important!
Before you begin
You must have eSM access and permission to perform the Load Active
Data task to complete this procedure. For procedure details, refer to the
online eSM user documentation.
You must be aware of the requirement to use the "HDF-BypassValidation, Version 600" view for all USDS Load Active Data requests.
Steps
Perform the following steps to recover HDF data from the eSM.
...........................................................................................................................................................................
CAUTION
Recovering HDF data from the eSM updates both the
HDF nodes with the selected eSM data. Verify the
situation and the eSM "Load Active Data" data
...........................................................................................................................................................................................................................................................
3 - 12

270-710-919R6.0
Recover a subset of HDF TimesTen database

from eSM
selections with Lucent Technologies technical

support before proceeding.
...........................................................................................................................................................................
Open a browser window to eSM in a system having eSM access and

log on. Your eSM user account must allow you to perform the "Load
Active Data" task.
Result: The eSM launch page is displayed. From this point on,
consult the online eSM help for details about recovering HDF data
with the Load Active Data task.
...........................................................................................................................................................................
Select "Service Tools > Load Active Data Requests".

Result: The Load Active Data Requests page is displayed.
...........................................................................................................................................................................
Follow the eSM user documentation procedure to create a Load Active

Data request for the data you want to recover on both HDF nodes.
...........................................................................................................................................................................
WARNING
To recover USDS data from the eSM using the eSM
"Load Active Data" capability, you must use the
"HDF-Bypass-Validation, Version 600" view to
create all load requests. Failure to use the bypass
validation view will result in failure of the load
active data request, extending the period of time
required to recover HDF databases.
Result: The new request is displayed in the Load Active Date
Requests table. The download will be performed at the time

scheduled in the Load Active Data request.
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 13
Procedure: Access SPA-related data from MAS nodes

............................................................................................................................................................................................................................................................
Overview
This section describes a USLI command RCV: MENU,SPA, which

helps to access SPA-related data in RC/V menu mode.
RCV:MENU,SPA (or SPA RCV in short) provides a simple
provisioning interface in MAS. It is expected that this interface will be
used for the occasional examination of SPA data and performing simple
updates to SPA data and not for the normal USDS provisioning. USDS
has a number of large and complex tables. This capability does not
provide cross table provisioning and sophisticated service views that
are available from the eSM. This feature supports reviewing, inserting,
updating and deleting of the physical database tables and logical view
tables.
SPA RCV supports three modes:
Physical view ([100] SERVICE PACKAGE MANAGEMENT

SUBMENU): shows the SPA database in a manner similar to
HDF-Standard view as seen from the eSM. This view includes all
the HDF data tables, including System Data tables, Global Data
tables and Subscriber Data tables.
Subscriber logical view ([6001]SDHLR 600 SUBSCRIBER

INFORMATION): merges the User Profile, ICH Service Profile,
ANSI A Profile, ANSI B Profile, Common A Profile, Common
Phone, ANSI Phone into a logical view that is similar to the HDFLT-SHLR-Standard from eSM. This view only contains
Subscriber Data. To manage System Data and Global Data, you
need to use the physical view.
The logical view is different from HDF-LT-SHLR-Standard view
in that it does not include the fields in table "ANSIAC" and "ANSI
Directory Number". So, to provision (insert, update, delete) a
complete subscriber from logical view, you need to complete the
provisioning of the following submenus:
[6001] SDHLR 600 SUBSCRIBER INFORMATION:

subscriber logical view
[6002] SDHLR 600 AUTHENTICATION DATA: a link to

ANSIAC table in the physical view
[6003] SDHLR 600 SUBSCRIBER DN TO MIN

INFORMATION: a link to "ANSI Directory Number" table
in the physical view
[6005] SDHLR 600 (EXTENDED) SUBSCRIBER DATA: a

link to "ANSI Phone Extended" table in the physical view
...........................................................................................................................................................................................................................................................
3 - 14

270-710-919R6.0
IMSI based subscriber logical view ([6004] SDHLR 600 IMSI

SUBSCRIBER INFORMATION): this logical view is for those
who use IMSI as the key to the subscribers. This view only
contains Subscriber Data.
MIN based subscriber logical table without DN([6006] SDHLR

600 SUBSCRIBER INFORMATION WITHOUT DN): this
logical view is for customers who use MIN as key and do not want
to provision DN with the subscribers.
Special instructions:
The logical table for subscriber data inserts DN inside the logical
table if it is a primary DN and does not use the physical table
"ANSI Directory Number" to insert the primary DN. For other DN
types, for instance, data DN or fax DN, it must be inserted through
the table "ANSI Directory Number".
If the service provider uses the logical view table to do an Insert,

and this Insert operation finds some existing records in one or
more related tables (ICHSVCPROFILE, ANSIBPROFILE, and
USERPROFILE) that are not included on the logical view, the
related table(s) with the existing record will be "skipped" and will
not be modified. OMLog (ID=10701) will be printed with the
table name for which the record was skipped.
If the service provider uses logical view to do a Delete, and if a

related record that is referenced by the logical view does not exist
in the TimesTen database, the SPA will still send successful ACK
to RC/V, but will have OMlog (ID=10701) printed with the table
name for which there was no record.
When a data change is made in a HDF via SPA RC/V, the change
is replicated to the other HDF in the HDF pair.
Global data broadcast is supported with this feature. That is, when
a global data is changed with this feature, the change will be
broadcast to all HCFs.
For changes made in the USDS SPA with this feature, the USDS
SPA performs any SPA specific notification or updates (index
server, other SPA processes and subscriber data post update
procedure).
If two users are using this feature simultaneously and operating on

the same data, the feature cannot guarantee that the data is updated
successfully, since one user's changes may overwrite the changes
of the other user.
Data changes by RC/V will be logged in OMLog.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 15
Important! It is strongly recommended that the service data be

modified through eSM. Only use this interface to manage the
service data when you fully understand the results of the operation.
Ensure the data integrity before use of this function as the
validations in SPA RC/V are incomplete compared with eSM.
This feature does not include any additional

functionality to send data updates to the eSM. There is no CORC
mechanism available for changes made with this feature.
Important!
Important! When global data is changed via this feature, there is

no automated real-time mechanism to broadcast the change to the
other HDF pairs. Thus, the HDF pairs can go out of sync with
respect to this changed data. Therefore, the service provider must be
cautioned when modifying global data with this feature.
Purpose
Use this procedure to insert a subscriber via RCV:MENU, SPA using

the logical view.
Important!
Before you begin
Follow similar steps to delete or update a subscriber.
To perform this procedure, you must have root access to the console of
the HDF nodes via LMT or UNIX console.
Steps
...........................................................................................................................................................................
SPA you want to access. For help, refer to "Access the MAS
administrative interfaces" (1-10)
...........................................................................................................................................................................
Type the following command in the subshell:

<RCV: MENU, SPA;
Result: The PLATFORM MAIN MENU screen is displayed, as
shown in Figure 3-3, "PLATFORM MAIN MENU" (3-17).
...........................................................................................................................................................................................................................................................
3 - 16

270-710-919R6.0

Figure 3-3
PLATFORM MAIN MENU
...........................................................................................................................................................................
Type [6001] or [SDHLR 600 SUBSCRIBER INFORMATION] to

access the logical view for subscriber:
Result: A prompt for operations is displayed:
Enter Database Operation
I=Insert R=Review U=Update D=Delete:
...........................................................................................................................................................................
Press [I] to insert a subscriber.

Result: The SDHLR SUBSCRIBER DATA screen is displayed, as
shown in Figure 3-4, "SDHLR SUBSCRIBER DATA" (3-18).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 17

Figure 3-4
SDHLR SUBSCRIBER DATA
...........................................................................................................................................................................
Fill the fields in this table, as shown in Figure 3-5, "Subscriber data
example" (3-19), Go through all the pages in this table and fill in the
data according to your needs.
...........................................................................................................................................................................................................................................................
3 - 18

270-710-919R6.0

Figure 3-5
Subscriber data example
...........................................................................................................................................................................
At the end of this table, the prompt for operations is displayed. Press
[V] for validation, as shown in Figure 3-6, "Validating the subscriber
data" (3-20)
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 19

Figure 3-6
Validating the subscriber data
...........................................................................................................................................................................
Press [I] to insert the record if the data is valid; otherwise check the
errors and repeat Step 5 ~ Step 6.
Result: The record is inserted.
...........................................................................................................................................................................
To insert more records, repeat Step 5~ Step 7. Otherwise, return to the

main menu by pressing [<].
Result: The control returns to NETWORK PLATFORM MAIN
MENU.
...........................................................................................................................................................................
Type [6003] or [SDHLR 600 SUBSCRIBER DN TO MIN

INFORMATION] to provision the directory number for subscriber:
I=Insert R=Review U=Update D=Delete QR=QueryR QU=QueryU
QD=QueryD:
...........................................................................................................................................................................................................................................................
3 - 20

270-710-919R6.0
...........................................................................................................................................................................
10

Result: The DIRECTORY NUMBER menu is displayed.
...........................................................................................................................................................................
11
Fill in the fields in this table, for example, as shown in Figure 3-7,
"ANSI Directory Number example" (3-21)
Figure 3-7
ANSI Directory Number example
Hint: The ICH Service Profile ID field must be the same value as the
subscriber's MIN value in subscriber logical view.
For each type of DN (Data DN, Fax DN or Analog
Fax DN), one record is needed in this table.
Important!
...........................................................................................................................................................................
12
Validate and insert the record.

...........................................................................................................................................................................
13
To insert more record in this table, repeat Step 11 ~ Step 12. Other
wise, press [<] to return to the main menu.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 21
Result: The control returns to NETWORK PLATFORM MAIN
MENU.
...........................................................................................................................................................................
14
Type [6002] or [SDHLR 600 AUTHENTICATION DATA] to

provision the authentication data for the subscriber:
QD=QueryD:
...........................................................................................................................................................................
15

Result: The ANSIAC menu is displayed.
...........................................................................................................................................................................
16
"ANSIAC example" (3-22)
Figure 3-8
ANSIAC example
...........................................................................................................................................................................................................................................................
3 - 22

270-710-919R6.0
Hint: The UserProfileID field must be the same value as the

subscriber's MIN value in subscriber logical view.
...........................................................................................................................................................................
17

...........................................................................................................................................................................
18
To insert more record in this table, repeat Step 16 ~ Step 17.

...........................................................................................................................................................................
19
Type [6004] or [SDHLR 600 IMSI SUBSCRIBER

INFORMATION] to provision the IMSI based subscriber data:
I=Insert R=Review U=Update D=Delete:
...........................................................................................................................................................................
20

Result: The IMSI SUBSCRIBER DATA menu is displayed.
...........................................................................................................................................................................
21
Fill the fields in this table, as shown in Figure 3-9, "IMSI

SUBSCRIBER DATA example" (3-24)
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 23

Figure 3-9
IMSI SUBSCRIBER DATA example
...........................................................................................................................................................................
22

...........................................................................................................................................................................
23
To insert more record in this table, repeat Step 21 ~ Step 22.

...........................................................................................................................................................................
24
Type [6005] or [SDHLR 600 (EXTENDED) SUBSCRIBER DATA]

to provision the data of Lucent Proprietary features for the subscriber:
I=Insert R=Review U=Update D=Delete QR=QueryR
QU=QueryU
QD=QueryD:
...........................................................................................................................................................................
25

Result: The ANSI PHONE EXTENDED menu is displayed.
...........................................................................................................................................................................................................................................................
3 - 24

270-710-919R6.0
...........................................................................................................................................................................
26
"ANSI PHONE EXTENDED example" (3-25)
Figure 3-10
ANSI PHONE EXTENDED example
...........................................................................................................................................................................
27

...........................................................................................................................................................................
28
To insert more records in this table, repeat Step 26 ~ Step 27.

END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 25
Disaster recovery for a HDF pair
Procedure: Disaster recovery for a HDF pair

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to recover a HDF pair from a failure that requires
either the HDF software or the TimesTen database to be reloaded from
tape.
Ensure that you have the backup data in tape for this HDF pair.
Steps
...........................................................................................................................................................................
Recover the system on both HDF nodes from disk/tape (refer to

Procedure: "Recover the USDS system" (2-21).
You can recover the TimesTen database on one HDF
node from its mate after the other node recovers data from disk/
tape/DVD. (Refer to "Recover the HDF TimesTen database from
the mated HDF node" (3-8)).
Important!
...........................................................................................................................................................................
Allow some time for all the HCF nodes to correct their index server
routing data. The data will be corrected via self-healing. When
messages arrive at the HCF nodes for the subscribers homed on the
recovered HDF nodes, the HCF node sends out message to all the HDF
pairs if it does not have the routing data for the target subscriber. The
recovered HDFs will reply the request with its node ID. The HCF
nodes will update its index server database to remember the routing
information for this subscriber.
Note: In this disaster case, the dynamic data of subscribers (on the
failed HDF pair) may need manual cancellations (via input message
SND: TEXT="ANSICNLVLR: MIN=a|IMSI=b ", RK=m) followed by new
registrations.
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
3 - 26

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview
Load balancing enables service providers to move subscriber data from

one HDF pair to another within the USDS complex. The migration of
subscriber data is based on Service Object Keys. During the migration
procedure, HDFs continue to process calls for the subscriber being
moved. When migration completes, the source HDFs update eSM and
Index Servers in HCFs to reflect the changes.
Load balancing functionality may be used in the following situations:
One pair of HDFs is "running hot", i.e., handling too much

transaction traffic for the set of subscribers they support.
Too many subscribers are accumulating on one pair of HDFs.
A new HDF pair is added into the complex by service providers,

which require mass migration of subscribers from an existing
HDF pairs to the new one to make effective use of its capacity.
Load balancing operations are initiated from the eSM. Since eSM does
not contain the dynamic data to be moved from one Network Element
(NE) pair to another, it sends a service command to the target NE to
trigger the actual process of data moving. Load balancing can only be
performed on non-child categories but the child capabilities can be
used when picking up the capability and attribute for matching the
prefixes. However, they are mapped back to the Service Objects in the
parent category.
As one load balancing request may involve tens of thousands of
subscribers to be moved, the NE will break the subscriber list into
smaller subsets (100 subscribers per subset by default) and only move
one subset at a time. As each subset of data is processed, a service
command response is sent back to the eSM indicating whether the
current subset succeeded or failed to be moved. If the chunk is
successfully moved, the eSM updates the network element group
assigned to the service object and all its service data records to the
target network element group. The final complete indication is included
in the service command response for the last subset of data after the
operation is completely finished.
Note: The number of subscribers in each load balance subset can be
configured through "Block Size for Sub Balanc" in "Global Parameter"
table. The default value, 100, is recommended by Lucent. Contact
Lucent support before changing this value.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 27
Important! Load Balancing only supports moving subscribers

between HDF pairs within the same USDS complex. Load
Balancing does not support moving subscribers between HDF pairs
in different USDS complexes.
Load balancing input file
The load balancing operation moves the subscriber data by subscriber

keys. The selection criteria key values are stored in the load balancing
input file under $SMSVAR/loadbalance/in/ directory.
On eSM, there are more selections for "Capability" and "Attribute"
which can be used as selection criteria. But there is a performance
impact if a non-indexed attribute is selected as the input attribute. To
avoid performance issues, USDS R6.0, recommends using the
following types of keys selection criteria:
User level subscriber key:
Table 3-1, "User level subscriber key" (3-28) shows the User level
subscriber key:
Table 3-1
User level subscriber key
Category name
Capability name
Key name
User Profile
User Profile
UserProfileID
Address level subscriber key:
Table 3-2, "Address level subscriber keys for ANSI" (3-28) shows the
address level subscriber key for American National Standards Institute
(ANSI) subscribers:
Table 3-2
Address level subscriber keys for ANSI
Category name
Capability name
Key name
ICH Service Profile
ICH Service Profile
ICH Service Profile ID
ICH Service Profile
ANSI A Profile
ICH Service Profile
Common A Profile
ICH Service Profile
Directory Number

DN
Table 3-3, "Address level subscriber keys for UMTS" (3-29) shows the
address level subscriber key for Universal Mobile Telecommunications
Service (UMTS) subscribers:
...........................................................................................................................................................................................................................................................
3 - 28

270-710-919R6.0
Table 3-3
Address level subscriber keys for UMTS
Category name
Capability name
Key name
ICH Service Profile
ICH Service Profile
ICH Service Profile
UMTS A Profile
ICH Service Profile
Common A Profile
ICH Service Profile
Bearer Services
ICH ServiceProfile ID
MSISDN
Table 3-4, "Address level subscriber keys for ANSI/UMTS dual mode
subscribers" (3-29) shows the address level subscriber key for ANSI/
UMTS dual mode subscribers:
Table 3-4
Address level subscriber keys for ANSI/UMTS dual

mode subscribers
Category name
Capability name
Key name
ICH Service Profile
ICH Service Profile
ICH Service Profile
ANSI A Profile
ICH Service Profile
Common A Profile
ICH Service Profile
Directory Number
ICH Service Profile IDDN
ICH Service Profile
UMTS A Profile
ICH Service Profile
Bearer Services
ICH ServiceProfile ID
MSISDN
Table 3-5, "Address level subscriber keys for HSS subscribers" (3-29)
shows the address level subscriber key for HSS subscribers:
Table 3-5
Address level subscriber keys for HSS subscribers
Category name
Capability name
Key name
PUID PROFILE
PUID PROFILE
PUIDProfID
PUID PROFILE
PUID DEVICE ASSOC
PUIDProfID
PUID PROFILE
REPOSITORYDATA
PUIDProfID
PUID PROFILE
PUID DEVICE ASSOC
NaiID
PUID PROFILE
PUID PROFILE
UserName
COMMON PUID
PROFILE
CommonPUIDProf IFC
CommonPUIDProfID
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 29
Category name
Capability name
Key name
PUID PROFILE
PUID PROFILE
CommonPUIDProfID
PUID PROFILE
PUID PROFILE
DomainID
Terminal level subscriber key:
Table 3-6, "Terminal level subscriber keys for ANSI" (3-30) shows the
terminal level subscriber key for ANSI subscribers:
Table 3-6
Terminal level subscriber keys for ANSI
Category name
Capability name
Key name
Terminal
ANSI Phone
IMSI
MIN
Terminal
Common Phone
IMSI
MIN
Table 3-7, "Terminal level subscriber keys for UMTS" (3-30) shows
the terminal level subscriber key for UMTS subscribers:
Table 3-7
Terminal level subscriber keys for UMTS
Category name
Capability name
Key name
Terminal
UMTS Phone
IMSI
Terminal
Common Phone
IMSI
Table 3-8, "Terminal level subscriber keys for ANSI/UMTS dual mode
subscribers" (3-30) shows the terminal level subscriber key for ANSI/
UMTS dual mode subscribers:
Table 3-8
Terminal level subscriber keys for ANSI/UMTS dual

mode subscribers
Category name
Capability name
Key name
Terminal
ANSI Phone
IMSI
MIN
Terminal
UMTS Phone
IMSI
Terminal
Common Phone
IMSI
MIN
...........................................................................................................................................................................................................................................................
3 - 30

270-710-919R6.0
Table 3-9, "Terminal level subscriber keys for HSS subscribers" (3-31)
shows the terminal level subscriber key for HSS subscribers.
Table 3-9
Terminal level subscriber keys for HSS subscribers
Category name
Capability name
Key name
Terminal
IMS NETWORK ACCESS

ID
NaiID
Terminal
IMS Authentication
NaiID
Terminal
IMS NETWORK ACCESS

ID
DomainID
Terminal
IMS PRID PROFILE
NaiID
Terminal
IMSINTWKASSOC
NaiID
Terminal
IMS NETWORK ACCESS

ID
UserName
Note: Attention must be paid to the HSS subscriber key while

performing HSS load balance.
The best way to load balance HSS subscribers is based on the

UserProfileID since it is unique; though it is not meaningful for
HSS subscribers.
UserName is not unique as it does not include the DomainID

component of the address. If load balance HSS subscribers are
based on UserName, remember that a given UserName can be
used by different subscribers in different domains, and the
subscribers in all domains will be evaluated against the selection
criteria.
Other possible ways to do HSS load balance are based on NaiID,

PUIDProfID or CommonPUIDProfID. But there will be some
performance impact on eSM when searching for related records.
Since many subscribers share the same DomainID, it is

recommended not to use DomainID as a key to perform HSS load
balance.
The load balancing operation moves the subscriber
data in the unit of user. Irrespective of the key specified, the load
balancing operation will find and move all the data related to a user
according to the USDS data model and the key reference
relationship of subscriber tables.
Important!
For example, if a load balancing request is created using the
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 31
terminal level key, IMSI, the USDS finds the address level data
related to this terminal (the Core ICH Service Profile, Directory
Number, ANSI B Profile, etc.) and the user level data related to this
terminal (the User Profile of the Core ICH Service Profile.
Special attention must be given to a user who has multiple ICH
Service Profile, or multiple A Profile or multiple Terminals. If the
load balancing selection criteria matches one profile or terminal for
a user, all profiles and terminals for the user are moved to the target
NE.
The input file supports the following format:
Prefix: the input file contains a list of one or more prefix values
that can match all the subscriber data in a range. For example,
3212300 applies to subscriber data in the range
3212300000~3212300999 for Mobile Identification Number
(MIN) (which is a 10-digit string).
Note: The eSM always treats the input file as a list of prefixes. A prefix
matches values equal to the prefix followed by zero or more digits.
Input file examples
Exact Matches (All entries in input file are exact matches): This
treats the input values as exact key match when selecting service
object keys from the eSM database. For example, 1234567890,
matches the Mobile Identification Number (MIN) which is exactly
equal to 1234567890.
Example1: Prefix list matching a single subscriber key value

The following file contains a single prefix value that matches one
subscriber IMSI.
333331365132211
Example2: Prefix List matching a range of subscriber key values
The following file contains a prefix that match a range of subscriber
MIN from 3212300000 to 3212300999. 3212300 is the prefix for the
subscriber range.
3212300
Example3: Prefix List matching a list of subscriber key values
The following file contains a list of prefixes that match subscriber
MINs.
3212300101
...........................................................................................................................................................................................................................................................
3 - 32

270-710-919R6.0
3212300103
3212300106
3212300107
3212300109
3212300121
3212300125
3212300128
3212300137
3212300139
3212300150
3212300154
3212300167
3212300198
3212300201
3212300203
3212300211
3212300212
3212300215
3212300217
3212300223
3212300225
Example4: Prefix List matching a combination of ranges and
individual subscriber key values
The following file contains a list of prefix that matches subscriber
MIN: 3212300000 ~ 3212300323.
32123000
32123001
32123002
321230030
321230031
3212300320
3212300321
3212300322
3212300323
Global configuration for
load balancing
There are global flags in the Global Parameter Capability to configure

the load balancing operations, as shown in Table 3-10, "Global
configurations for load balancing" (3-34):
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 33
Table 3-10
Global configurations for load balancing
Attribute name
Description
Load Bal Continue on Fail
Indicates whether the load balancing

should continue when there is a failure in
this process.
Block Size for Sub Balanc
The block size for subscriber records in

the Secure File Transfer Protocol (SFTP) files transmitted from the source
HDF node to the target HDF node.
Before performing the load balancing operations from eSM, configure

the two flags according to the site requirements.
Configure the delay timer
for HDF node
HDF will send a response to eSM when each subset of subscriber data
is moved to the destination HDF. Since HDF processing speed is
usually faster than that of eSM, the load balancing response messages
will get cumulatively collected in the eSM end. To avoid this,
DF_MOV_DELAY_TIME in USDS Local Configuration Data for
each HDF node can be configured to the real situation.
Note: The actual value should be tuned by Lucent Engineer according
to site configuration (for example, eSM speed).
Follow the below procedure to configure delay timer for HDF node:
Steps
...........................................................................................................................................................................
Log on to one HDF node as root.

...........................................................................................................................................................................
Type the following command to set USDS Local Configuration Data

path
> export HLRCFG=/sn/sps/HDF600/bin
...........................................................................................................................................................................
Type the following command to update DF_MOV_DELAY_TIME in

USDS Local Configuration Data
> /sn/sps/HDF600/bin/cfgupd -u -p DF_MOV_DELAY_TIME
Result: The following message is displayed:

YOU WILL BE CHANGING THE PARAMETER DF_MOV_DELAY_TIME
...........................................................................................................................................................................................................................................................
3 - 34

270-710-919R6.0
HIT CR IF YOU WISH A VALUE TO REMAIN THE SAME

PRESENT PARAM TYPE = NUMBER (int)
CHANGE TYPE? ('S'|'s', 'N'|'n', 'D'|'d', CR):
...........................................................................................................................................................................
Press [Enter] to continue:

Result: The following outputs is displayed:
PRESENT VALUE = 0
CHANGE (new value or CR - use "" for NULL STRING)? :
...........................................................................................................................................................................
Enter DF_MOV_DELAY_TIME, for example [500].

Note: the value range for DF_MOV_DELAY_TIME is 0~5000, the
unit is millisecond.
Result: The following output is displayed:
SUCCESSFULLY updated DF_MOV_DELAY_TIME
...........................................................................................................................................................................
Check DF_MOV_DELAY_TIME value in USDS Local Configuration

Data with the following command:
> /sn/sps/HDF600/bin/cfgdisp -p DF_MOV_DELAY_TIME
Result: Output similar to the following example is displayed:
PARAMETER NAME:
DF_MOV_DELAY_TIME
VALUE:
500
...........................................................................................................................................................................
7
Load balancing removal
tool
Repeat Step 1 - Step 6 to configure the delay timer for each HDF node.
In some rare error cases during HDF load balancing, there will be two
types of log files generated by the source HDF:
User list that might be duplicated in the target HDF.
When the source HDF does not receive any response from
the target HDF during load balancing, the source HDF will
consider the chunk of subscribers failed to be moved to the
target HDF and will not execute the deletion of the records.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 35
But if the successful response from the target HDF is lost or

the target HDF is too slow to finish its processing before
timer expires in the source HDF, the chunk of subscribers
might already be inserted into the target HDF successfully. In
such cases, the chunk of subscribers will be left in the target
HDF as duplicate records.
User list that is duplicated in source HDF
When a chunk of subscribers have been moved to the target

HDF successfully, but fail to be deleted in the source HDF,
the chunk of subscribers are left in the source HDF as
duplicate records.
These duplicate subscriber records cannot be managed by eSM and

might cause problems in HCF index server, which will lead index
server to route call traffic to the HDF with legacy data. A tool is
designed to delete those duplicate records in source or target HDF
nodes. For the detailed procedure on usage of load balancing removal
tool, refer to Procedure: "Run load balancing removal tool" (3-47).
...........................................................................................................................................................................................................................................................
3 - 36

270-710-919R6.0
Procedure: Execute load balancing from eSM

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to execute the load balancing from the eSM GUI.
Got permission for this task on the eSM.
Created the input file.
Verified the global configuration for load balancing.

This high-level procedure is not intended to replace
the eSM documentation. You may need to reference the Load
Balancing sections of the eSM Application Administration manual
to complete the detailed steps not provided in this procedure.
Important!
...........................................................................................................................................................................
CAUTION
If a HCF node is down during the load balancing
process, a manual full init (or peer pump) of the HCF
should be done after it returns to service. The HCF
node will update the index server routing data that it
missed during the load balancing.
For manual full init, refer to "FULLINIT:IS [, CLEANUP
|, DFPUMP | CF=a [, UCL]]" (4-10).
Steps
...........................................................................................................................................................................
Log on to the eSM host, and load the input file to the following
directory: $SMSVAR/loadbalance/in
Result: The input file is loaded to the eSM host.
Hint: This step can be skipped to use a remote machine when creating
the load balancing request.
Note: The input file is removed from $SMSVAR/loadbalance/in upon
successful
completion of the Load Balancing request.
__________________________________________________________
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 37
...........................................................................................................................................................................
Log on to the eSM GUI and click Continue.

Result: The eSM launch page is displayed.
...........................................................................................................................................................................
From the eSM launch page, select Service Tools>Load Balancing

Requests, as shown in Figure 3-11, "The eSM launch page" (3-38).
Figure 3-11
The eSM launch page
Result: The Load Balancing Requests page is displayed.

...........................................................................................................................................................................
From the Load Balancing Requests page, click the New icon at the
upper right corner of the table, as shown in Figure 3-12, "The Load
Balancing Requests page" (3-39):
...........................................................................................................................................................................................................................................................
3 - 38

270-710-919R6.0
Figure 3-12
The Load Balancing Requests page
Result: The New Load Balancing Request page is displayed.

...........................................................................................................................................................................
Fill in the fields on this page according to Table 3-11, "Fields

description for load balancing request" (3-41). Figure 3-13, "A new
load balancing request" (3-40) lists an example of the load balancing
request.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 39
Figure 3-13
A new load balancing request
Hint: The Selection Criteria specifies the key range of the subscriber
data to be migrated. For example, to use the User profile ID as
subscriber key, choose "USERPROFILE" in Capability list and
"UserProfileID" in Attribute list. Then specify the file that stores the
list of "UserProfileID" information. The input file can be located on
eSM or on a remote machine.
...........................................................................................................................................................................................................................................................
3 - 40

270-710-919R6.0
Table 3-11
Fields description for load balancing request
Field name
Description
Request Name
A unique name for the new load balancing

request.
Service
The service name on the eSM. For USDS R6.0,

it is HDF-Standard, Version 600.
Category
The category name of the subscriber data to be

moved. The Load Balancing selection criteria
may be a key from the User Profile, ICH Service
Profile or Terminal category, but the category
specified in the Load Balancing Request will
always be the User Profile, which is the parent
category for the User and the smallest unit of
data that can be moved.
Source NE Group
The source NE Group name for the subscriber

data to be moved.
Target NE Group
The destination NE Group name for the

subscriber data to be moved.
Start Time
The starting time of this load balancing task. It

can be future time or current time. If it is a future
time, the load balancing request will be
scheduled.
Selection Criteria Capability
The Capability containing the key of the

subscriber data to be moved.
Selection Criteria Attribute
The key of the subscriber data to be moved.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 41
Field name
Description
Selection Criteria Input File
The file that stores the values of the keys

specified by the "Capability" field and the
"Attribute" field.
If the file is stored on eSM locally, select the
From File On eSM check box, and specify the
File Name from the drop down list.
If the file is stored on remote machine, select the
From File On Other Machine check box and
specify the following fields:
File Name: the input file name.

Remote Login Id: the FTP login ID on
the remote machine.
Password: the FTP password on the
remote machine.
Host Name/IP Address: the IP address
or host name of the remote machine.
Remote Directory: the directory where
the input file is stored on the remote
machine.
...........................................................................................................................................................................
Click Next to process the new load balancing request.

Result: A new load balancing request is created, as shown in
Figure 3-14, "The result of a new load balancing request" (3-43).
...........................................................................................................................................................................................................................................................
3 - 42

270-710-919R6.0
Figure 3-14
The result of a new load balancing request
...........................................................................................................................................................................
Refresh the Load Balancing Request page to get the latest status of
this process.
Result: The new status is displayed, as shown in Figure 3-15, "The
status of a load balancing request" (3-44).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 43
Figure 3-15
The status of a load balancing request
Note: After the load-balancing request is executed successfully, the

input file stores on the eSM will be deleted automatically. You have to
back it up manually in case it is of any use. The input file will not be
deleted under the following execution status:
Invalid
Scheduled
Failed
Partial Succeeded
...........................................................................................................................................................................
(Optional) View the Service Objects affected by this load balancing

request by clicking the View Service Object Status link from the Load
Balancing Request page.
Result: The Service Objects affected by this load balancing request
are displayed, as shown in Figure 3-16, "Service Objects status for

the load balancing request" (3-45).
...........................................................................................................................................................................................................................................................
3 - 44

270-710-919R6.0
Figure 3-16
Service Objects status for the load balancing

request
Hint: Return to the Load Balancing Request page by clicking the load
balancing request name.
There are several status for the load balancing request,
as shown in Figure 3-17, "Load balancing request processing
status" (3-46).
Important!
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 45
Figure 3-17
Load balancing request processing status
Note: Load balancing stores a list User Profiles that were successfully
moved in the /cust_use/sdhlr/MOVSUB_Success.log file on the Source
HDF. This file may be useful if a load balancing command does not
complete with a "Successful" state.
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
3 - 46

270-710-919R6.0
Procedure: Run load balancing removal tool

............................................................................................................................................................................................................................................................
Purpose
If there are duplicated record log files generated for the source HDF or
the target HDF, the removal tool must be run immediately after load
balance. Remove data in the target HDF and Remove data in the source
HDF describes how to use this tool to manually delete duplicated
records in the target HDF and the source HDF. "Error handling for the
removal tool" (3-49) describes how to continue with the manual
deletion if removal tool fails during the first run.
Before you begin
Go to directory /cust_use/sdhlr/ of the source HDF to check whether

there are any duplicate record log generated for the source HDF and the
target HDF.
Check database and resolve any issues that cause load balancing
failure.
Remove data in the target

HDF
During load balancing, the target HDF sends a response to the source
HDF after the records are inserted into the target HDF successfully. If
the source HDF does not receive the response, OM log will report the
following error:
"LB:MOVE:Timeout - no response from target HDF within given time. The
following subscribers failed to be moved, there may need to delete them from the
target DB manually: "
To list all UserProfileIDs whose relative records might be duplicated in

the target HDF, an error log file is generated in the source HDF named
as:
/cust_use/sdhlr/lb_target_error_YYYY_mm_dd_HH_MM_SS
YYYY_mm_dd_HH_MM_SS indicates the time when the first

timeout occurs during load balancing operation.
YYYY: year (Range: 1900-2050, 4 digit)
mm: month (Range: 01-12, 2 digit)
dd: day (Range: 1-31, 2 digit)
HH: hour (Range: 00-23, 2 digit)
MM: minute (Range: 00-59, 2 digit)
SS: second (Range: 00-59, 2 digit)
Removal in target HDF includes two steps:

...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 47
Steps
...........................................................................................................................................................................
Copy target error file from source HDF to target HDF.

> scp /cust_use/sdhlr/
lb_target_error_YYYY_mm_dd_HH_MM_SS
$TARGET_DF:/cust_use/sdhlr/
Note: $TARGET_DF is the target HDF host name.
...........................................................................................................................................................................
Execute removal tool on target HDF.

> cd /sn/sps/DF600/bin/
> ./DeleteSub.pl -f /cust_use/sdhlr/
lb_target_error_YYYY_mm_dd_HH_MM_SS -s
where:
Remove data in the source

HDF
-f <input file name> specifies the input file name.
-s indicates that this tool will stop when an error is encountered.
The source HDF deletes records after the target HDF sends a response.
If the deletion failed in the source HDF, OM log will report the
following error:
"LB:DELETE:Fail - error occurred during the deletion of subscribers. The
following subscribers moved successfully but need to be deleted manually on
source HDF:"
To list all UserProfileIDs whose relative records is duplicated in the

source HDF, an error log file is generated in the source HDF named as:
/cust_use/sdhlr/lb_source_error_YYYY_mm_dd_HH_MM_SS
YYYY_mm_dd_HH_MM_SS indicates the time when the first

deletion failure occurs during load balancing operation.
YYYY: year (Range: 1900-2050, 4 digit)
mm: month (Range: 01-12, 2 digit)
dd: day (Range: 1-31, 2 digit)
HH: hour (Range: 00-23, 2 digit)
MM: minute (Range: 00-59, 2 digit)
SS: second (Range: 00-59, 2 digit)
Removal in source HDF:

> cd /sn/sps/HDF600/bin/
...........................................................................................................................................................................................................................................................
3 - 48

270-710-919R6.0
> ./DeleteSub.pl -f /cust_use/sdhlr/

lb_source_error_YYYY_mm_dd_HH_MM_SS -s
Error handling for the
removal tool
If the tool runs successfully, it deletes all duplicated records and prints
summary information on the screen and in log file /DeleteSub.log. But
in some error cases, i.e. database in an abnormal state, manual deletion
of duplicate records may also fail. Follow the procedure below for the
three error cases which may occur during manual deletion.
A.
If the removal tool reports an error message as follows

"Error: execute select statements error
Error: log file in DeleteSub.log
Check the DB to find the reason and then run this commad:
./DeleteSub.pl -f re_run_key.lst -s"
Then, execute the following steps:
Check the database and resolve the problem
Execute the following command:

> ./DeleteSub.pl -f re_run_key.lst -s
B.
If the removal tool reports an error message as follows:

"Error: execute delete statements error
Please check the DB to find the reason first, then run this commad:
ttIsql -v 4 -connStr "DSN=tt41data" -f "re_run_delete.sql""
Execute the following command and save output messages

into the log file (.i.e del.log):
> ttIsql -v 4 -connStr "DSN=tt41data" -f
"re_run_delete.sql" >del.log 2>&1
C.
Search for the error messages in the log file.

> grep "Error Code" del.log
If no "Error Code" is found, the command is executed

successfully. Else, check the database to find the root cause for
each "Error Code", and repeat step 2 and 3 until no "Error Code"
exists.
If the removal tool reports an error message as follows:
"Error: execute select and delete statements error
Please check the DB to find the reason first, then run this command:
ttIsql -v 4 -connStr "DSN=tt41data" -f "re_run_delete.sql"
and run this command :
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 49
./DeleteSub.pl -f re_run_key.lst -s"
Execute the following command and save output messages

into the log file (.i.e del.log):
> ttIsql -v 4 -connStr "DSN=tt41data" -f
"re_run_delete.sql" >del.log 2>&1
Search for the error messages in the log file.

> grep "Error Code" del.log
If no "Error Code" is found, then this command has been
executed successfully. Else, check the database to find the
root cause for each "Error Code", and repeat step 2 and 3
until no "Error Code" exists.
Execute the following command:

> ./DeleteSub.pl -f re_run_key.lst -s
...........................................................................................................................................................................................................................................................
3 - 50

270-710-919R6.0
Procedure: Re-lock the USDS features from the eSM

............................................................................................................................................................................................................................................................
Purpose
Before you begin

Reference
Use this procedure to relock USDS features on HCF nodes/HDF nodes/

eSM from the eSM.
Get the feature keys before executing the procedure.
For more information, refer to Chapter 4 SMS Administration Menu,
eSM Operating and Maintaining the System (270-720-335).
Steps
...........................................................................................................................................................................
Log on to the eSM server as sms.

...........................................................................................................................................................................
Type the following command to start the System Administration

Menu:
>smsadm
Result: The System Administration Menu is displayed.
...........................................................................................................................................................................
Type [2] Service Administration.

Result: The Service Administration Menu is displayed.
...........................................................................................................................................................................
Type [16] Service Feature Administration.

Result: The Service Feature Administration Menu is displayed.
...........................................................................................................................................................................
Type [7] Lock Service Features on MAS/eSM.

Result: Prompts to fill the following fields appear one by one.
Enter Service Name: <Service_Name> (HDF or HCF)
Enter Version Name: 600
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 51
Enter comma separated list of MAS name(s) (Hit enter for all):
<Your NE Name>.
Result: The feature status for this service and a prompt for the
feature number to be re locked appear.

<Your NE Name> are names of the NEs created on the
eSM for the target MASs.
Important!
...........................................................................................................................................................................
Enter the feature number to be re locked. For example, enter [7] for the
ANSI41 feature.
Enter feature number: [0] 7
Result: A prompt to enter the Feature Key is displayed.
...........................................................................................................................................................................
Enter the Feature Key for this feature.

Result: The new status for all the features for this service appears.
Feature 7 -- ANSI41 is marked as locked. You are asked to select

the operation:
Operation (l - lock, a - apply, q - quit): [l]
Note: At this time, the feature is not really locked on the eSM or the
MAS, it is just marked as re locked. You need to apply the feature
relock request to the eSM and the MAS as described in Step 8.
...........................................................................................................................................................................
To relock more features, press [l] and repeat Step 6 - Step 7. To apply
the feature-relocking request to the eSM and the MAS, type [a].
Result: A summary similar to the following example is displayed:
Summarizing feature changes...
7. ANSI41 -Locked
Do you want to apply the feature locks (y/n)?
...........................................................................................................................................................................
Press [y] to continue with the operation.

Result: Messages similar to the following example is displayed:
Applying features to MAS
...........................................................................................................................................................................................................................................................
3 - 52

270-710-919R6.0
Locking feature ANSI41

... ...
Generating forms
*****Form Generation*****
1:Generate forms in English (Default)
Please enter the choice ('q' to quit,'u' to parent screen):
Important! This process may take some time, wait until the
prompt for form generation appears.
...........................................................................................................................................................................
10
Press [1] to generate form for this service.

Result: A message similar to the following example is displayed:
/extra/sms02/smsapp/classes/com/lucent/sms/FormGenerator/PageGenerator/
formgenerator.ksh -svc HDF -version 600 -locale en
......
Creating status file: /usr/tmp/gen27972
Ok:Service has no custom rules
*****Form Generation*****
1:Generate forms in English (Default)
Please enter the choice ('q' to quit,'u' to parent screen):
...........................................................................................................................................................................
11
Press [u] to go to the parent menu.

Result: The service is re locked and control returns the Service
Feature Administration Menu.

This step must be executed to relock the service, as the
feature-relocking process will automatically lock the service for
Work Order processing.
Important!
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 53

............................................................................................................................................................................................................................................................
Overview
In a distributed USDS complex, a range of subscriber data is

provisioned to a selected HDF pair. A subscriber's data is not resident
on all HDFs in the system.
When a service request arrives at a HCF, that HCF must route the
request to one of the two HDFs (a pair) that hold data for the requesting
subscriber. For each HCF, an index server maintains and provides the
required routing data to the HCF.
The Index Server in each HCF obtains and maintains data that
describes all subscriber-to-HDF assignments and HDF routing
information.
The index server performs the following primary functions:
Maintain a subscriber-to-HDF relationship mapping database
Manage load sharing across paired HDFs
Provide HDF routing information to HCF
The index server maintains the following mappings:
IMSI to HDF route (primary/secondary HDF nodes)
MSISDN/MDN to HDF route (primary/secondary HDF nodes)
MIN to HDF route (primary/secondary HDF nodes)
Public User Identity (PUID) to HDF route (primary/secondary

HDF nodes)
Private User Identity (PRID) to HDF route (primary/secondary

HDF nodes)
The data is stored in a TimesTen database resident on each HCF, which

is backed up to a local disk automatically to allow quick recovery
during an initialization.
The index server has two routing strategies for the two HDFs in a mate:
Round robin: route one request to primary HDF, another to the

secondary HDF, distributing request in a round robin manner. It is
the default configuration.
Local preference: always route the request to one HDF (in a

mate) that is local to the HCF node hosting the index server.
...........................................................................................................................................................................................................................................................
3 - 54

270-710-919R6.0
The USDS configuration file controls the configuration of routing

method. Contact Lucent technical support to change the default
configuration.
Index server full
initialization
When an index server is initialized for the first time on a HCF, it is

called a full initialization process (or full init for short). There are two
configurations for index server full initialization:
Automatic: the index server triggers the full initialization

automatically when the HCF SPA is up and running. It is default
configuration.
Manual: the index server triggers the full initialization by manual

Input Message.
Full init supports two modes:
HDF pump: Get the entire index server routing data from the
HDF nodes by sending requests to them.
Peer pump: Get the index server routing data from the existing
HCF nodes that already have the index server data populated. It
can save a lot of time compared with the full init method.
After HDF pump or peer pump process, a re-sync process will be

triggered. The re-sync process gets updates from HDF pairs based on
the timestamp stored for each HDF pair.
Index server self healing
During the normal operation of the USDS complex, if the index server
detects errors in its routing database for specific subscribers, it triggers
the self-healing process.
The following situations trigger self-healing:
The index server received request for a subscriber, but it does not
have that subscribers routing data.
The index server has routing data for the subscriber, but it is
wrong.
In both cases, the index server sends requests to all the HDF pairs to get
the correct routing information. The HDF nodes that host the subscriber
data send response to the index server with the correct HDF ID.
To avoid re-trigger the self-healing process in a short time, the
subscriber is marked out during a configured time interval.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 55
Procedure: Index server full init- HDF pump

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to do a manual full init of index server with HDF
pump.
Ensure that you have permission to full initialize the index server.
...........................................................................................................................................................................
CAUTION
Full init is service-impacting. Ensure that you perform
this procedure on the correct HCF node. This method
is used mainly for the first HCF node in the USDS
complex. Use peer pump or self-healing to recover
index servers in other situations.
Steps
...........................................................................................................................................................................
Access a command line interface to the HCF that needs the index
server full init. Refer to "Access the MAS administrative interfaces"
(1-10) as required.
...........................................................................................................................................................................
At the prompt, type the following command:

<fullinit:is
Result: An output similar to the following examples is displayed:

fullinit:is; Will initiate Index Server FULL INIT
procedure, CONTINUE Y OR N? y;
IP - IS FULL INIT SENT TO HCF SPA, WAITING FOR
RESPONSE
+++ ISQUAD_CF12 2004-10-20 11:21:18 MAINT /HLR008
#000211 as02 LEAD >
M FULLINIT IS
IS FULL INIT Initiated, Please check OMlog for
progress
HLR INDEX SERVER FULL INIT INITIATED
...........................................................................................................................................................................................................................................................
3 - 56

270-710-919R6.0
...........................................................................................................................................................................
Check Omlog to monitor the process of the full init. Exit MAS node
when it is done.
Note: For more information on FULL:INIT command, refer to
FULLINIT:IS [, CLEANUP |, DFPUMP | CF=a [, UCL]].
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 57
Procedure: Index server full init-peer pump

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to do a manual full init of index server through peer
pump.
Ensure that you have permission to do the peer pump for the index
server.
Steps
...........................................................................................................................................................................
Access a command line interface to the HCF that need the index server
full init. Refer to "Access the MAS administrative interfaces" (1-10) as
required.
...........................................................................................................................................................................
At the prompt, type the following command:

<fullinit:is, cf=<Source_HCF>
Result: An output similar to the following examples is displayed:

<fullinit:is,cf=hlrcf8; Will initiate Index Server FULL INIT procedure,
CONTINUE Y OR N? y; IP - IS FULL INIT SENT TO HCF SPA, WAITING
FOR RESPONSE
+++ HLRCF4 2004-12-20 11:21:18 MAINT /HLR008 #000211
as02 LEAD >
M FULLINIT IS CF=HLRCF8
IS FULL INIT Initiated, Please check OMlog for progress
END OF REPORT #000211++...........................................................................................................................................................................
Check Omlog to monitor the process of the peer pump. Exit MAS node
when it is done.
When a remote HCF is specified as the source HCF
for peer pump, it must be a local HCF. Otherwise, the parameter
[UCL] must be specified to ensure the success of peer pump
procedure.
Important!
...........................................................................................................................................................................................................................................................
3 - 58

270-710-919R6.0
Note: For more information on FULL:INIT command, refer to

FULLINIT:IS [, CLEANUP |, DFPUMP | CF=a [, UCL]].
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 59
Configure RC/V form access permissions
Procedure: Configure RC/V form access permissions

............................................................................................................................................................................................................................................................
Overview
Restricted logins are prohibited from RC/V forms access by default.

Access permissions must be explicitly assigned for each form and login
user.
Creating restricted RC/V

Logins
Refer to Updating RC/V SPA data, Recent Change and Verify (270780-422) for information on creating restricted logins.
Assigning Form Access

Permissions
By default, a restricted RC/V user is prohibited from a form, which

means the system administrator must explicitly indicate to which form
the restricted user has access and which operations are permitted on
that form.
The files that need to be edited to grant form access to restricted logins
have the suffix ".fi" for form interface. The default file path is:
/sn/sps/HDF600/datamodel/ODIN/.
The key word "restricted_operations_for:" is used in the form interface
files immediately proceeding the tables to specify forms access
permissions for specific login IDs. This keyword is entered as follows:
restricted_operations_for: LOGIN [review] [insert] [update]
[delete];
Note:
Insert the restricted operations keyword on a new line just prior to

the line beginning with tables.
On the same line, add the restricted login ID followed by one or

more operations; review, insert, update, or delete.
"review": the permission to view a form
"update", "insert" or "delete" follow the "review": the

permission to update, to add, or to delete a record of the form.
End the new line with a semicolon (;).
Refer to Updating RC/V SPA data, Recent Change and Verify (270780-422) for information on creating restricted logins.
...........................................................................................................................................................................................................................................................
3 - 60

270-710-919R6.0
Assign Form Permissions to Restricted WPS

Logins
Procedure: Assign Form Permissions to Restricted WPS Logins

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Perform this procedure when you want to apply form access

permissions to restricted WPS login user.
You need to determine the following:
The name of the restricted login user
The names of the form interface files
The type(s) of access to be assigned.
Actions
...........................................................................................................................................................................
Log on to the HDF node as root.

...........................................................................................................................................................................
Create a standard UNIX login user for WPS login user.

Example: Use the following commands to create a login user:
> useradd -d /sn -s /sn/rc/res_sh wpsusr
> passwd wpsusr
Note: The special login shell /sn/rc/res_sh gives the login user wpsusr
the capability of launching the RCV:MENU,SPA without access to any
data.
...........................................................................................................................................................................
Go to the directory /sn/sps/HDF600/datamodel/ODIN/ and locate the

form interface files for editing.
Note: The following form interface files should be modified:
WPS_GLBDATA.fi
WPS_IMSI_SUBDATA.fi
WPS_MIN_SUBDATA.fi
...........................................................................................................................................................................
Add access for a restricted login to file "WPS_GLBDATA.fi":

Note: For table "WPS_GLBDATA", the WPS login user has the
"review" permission only.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 61

Logins
Example: Following line will be added:
restricted_operations_for: wpsusr review;

...........................................................................................................................................................................
Save and exit the file "WPS_GLBDATA.fi

...........................................................................................................................................................................
Add access for a restricted login to file "WPS_IMSI_SUBDATA.fi":

Note: For table "WPS_IMSI_SUBDATA", the WPS login user has the
"review" and "update" permissions.
Example: Following line will be added:
restricted_operations_for: wpsusr review update;

...........................................................................................................................................................................
Save and exit the file "WPS_IMSI_SUBDATA.fi".

...........................................................................................................................................................................
Add access for a restricted login to file "WPS_MIN_SUBDATA.fi":

Note: For table "WPS_MIN_SUBDATA", the WPS login user has the
"review" and "update" permissions.
Example: The following line will be added:
restricted_operations_for: wpsusr review update;

...........................................................................................................................................................................
Save and exit the file "WPS_MIN_SUBDATA.fi".

...........................................................................................................................................................................
10
Access the HDF node with WPS login user.

Example: wpsusr, which is created in the above steps
Note: The steps below will verify if the restricted permissions assigned
to WPS login user correctly.
...........................................................................................................................................................................
11
Open a UNIX subshl by the following command:

>subshl
...........................................................................................................................................................................
12
Start the SPA RC/V menu by the following command:
...........................................................................................................................................................................................................................................................
3 - 62

270-710-919R6.0

Logins
<RCV:MENU,SPA;
Result: The "PLATFORM MAIN MENU" screen is displayed as
shown in Figure 3-18, "PLATFORM MAIN MENU" (3-63).

Figure 3-18
PLATFORM MAIN MENU
...........................................................................................................................................................................
13
Type [100] or [SERVICE PACKAGE MANAGEMENT

SUBMENU] to access submenu:
Result: The "SERVICE PACKAGE MANAGEMENT
SUBMENU" screen is displayed as shown in Figure 3-19,

"SERVICE PACKAGE MANAGEMENT SUBMENU" (3-64).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 63

Logins
Figure 3-19
SERVICE PACKAGE MANAGEMENT SUBMENU
...........................................................................................................................................................................
14
Type [2] or [HDF600] to access the "HDF600" submenu.

Result: The "HDF600" screen is displayed as shown in Figure 3-20,
"HDF600" (3-65).
...........................................................................................................................................................................................................................................................
3 - 64

270-710-919R6.0

Logins
Figure 3-20
HDF600
...........................................................................................................................................................................
15
Type [3] or [ANSI GLOBAL DATA] to access the forms under ANSI
global category:
Result: The "ANSI GLOBAL DATA" screen is displayed as shown
in Figure 3-21, "ANSI GLOBAL DATA" (3-66).

Note: Form list in the category is visible but only one form "Global
WPS Data" can be accessed.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 65

Logins
Figure 3-21
ANSI GLOBAL DATA
...........................................................................................................................................................................
16
Type [23] or [Global WPS DATA] to access the form:

Result: The "Global WPS DATA" screen is displayed as shown in
Figure 3-22, "Global WPS DATA" (3-67) and only "review"

permission is allowed.
...........................................................................................................................................................................................................................................................
3 - 66

270-710-919R6.0

Logins
Figure 3-22
Global WPS DATA
...........................................................................................................................................................................
17
Press [<] to return to the upper level menu.

...........................................................................................................................................................................
18
Type [12] or [TERMINAL] to access the forms under terminal

category:
Result: The "TERMINAL" screen is displayed as shown in
Figure 3-23, "TERMINAL" (3-68).

Note: Only "WPS Data Keyed by IMSI" and "WPS Data Keyed by
MIN" can be accessed.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 67

Logins
Figure 3-23
TERMINAL
...........................................................................................................................................................................
19
Type [23] or [WPS Data Keyed by IMSI] to access the form:

Result: The "WPS Data Keyed by IMSI" screen is displayed as
shown in Figure 3-24, "WPS Data Keyed by IMSI" (3-69) with

"review" and "update" permissions allowed.
...........................................................................................................................................................................................................................................................
3 - 68

270-710-919R6.0

Logins
Figure 3-24
WPS Data Keyed by IMSI
...........................................................................................................................................................................
20
Type [24] or [WPS Data Keyed by MIN] to access the form:

Result: The "WPS Data Keyed by MIN" screen is displayed as
shown in Figure 3-25, "WPS Data Keyed by MIN" (3-70) with

"review" and "update" permissions allowed.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

3 - 69

Logins
Figure 3-25
WPS Data Keyed by MIN
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
3 - 70

270-710-919R6.0
Overview
............................................................................................................................................................................................................................................................
Purpose
This chapter describes USDS-specific technician Input Messages and

USDS-specific Output Messages.
Performing USDS operational tasks requires the
knowledge of MAS Input and Output Messages (IM/OM). This
guide does not cover MAS platform messages. For MAS
Input/Output Messages, refer to the MAS User Reference Guide
(270-700-176).
Important!
Contents
This chapter contains the following sections

4-3
Input message
4-5
Send command from the eSM GUI
4-6
4-10
SSD update (ANSI)
4-15
4-17
4-19
4-20
............................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 1
CANCEL: MAP (UMTS)
4-21
RECOVER: MAP (UMTS)
4-22
4-24
4-25
4-27
4-29
Output message
4-31
Redirect Omlogs
4-35
Configure the severity level for OMLogs
4-42
View output message
4-52
...........................................................................................................................................................................................................................................................
4 - 2

270-710-919R6.0
............................................................................................................................................................................................................................................................
Overview
In the USDS system, there are platform IM/OM and application level
IM/OM. The platform level IM/OM is not within the scope of this
guide.
Application level Input Messages help the maintenance personnel to
manage the USDS service.
Application level Output Messages indicate either:
The results of application-specific Input Messages, or
Some application event has occurred.
Technical personnel can use the information in Output Messages to

help them in diagnosing and maintaining the USDS system.
Platform support
Conventions
The MAS platform provides the support required for USDS-specific

Input and Output Messages:
You can enter Input Messages at the LMT USLI.
Output Messages appear:
In the scrolling area of the LMT.
In the Output Message log files, /sn/log/OMlog0 or

/sn/log/OMlog1
At a printer, if equipped.
The following conventions are used in this module:

Input message text
Input Message text is shown in a bold font. Generic Input Message text
is shown in all upper case to match MAS conventions, however most
Input Message text can be entered in upper or lower case. Filenames
and other information that are case sensitive must be entered as
required. See specific Input Messages for additional details as required.
An example of Input Message is given below.
OP: STATUS, SPA=HCF600;
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 3
Square brackets [ ]
Optional parameters are enclosed in square brackets, as shown in the

following example.
RMV: SPA=a [,UCL];
In the above example, SPA is required, whereas UCL is optional. You

can use one or more optional parameters.
"OR" symbol |
When several selections exist for a parameter, but only one selection is
allowed, the available selections are separated by the "OR" symbol.
The "OR" symbol, also known as the "pipe" symbol, is illustrated in the
following example:
RECOVER: MAP [, ALL| [, STARTIMSI=a, ENDIMSI=b] [, VLR=c]] [, UCL]
In the above example, you can use ALL or an International Mobile

Subscriber Identity (IMSI) range, but not both.
...........................................................................................................................................................................................................................................................
4 - 4

270-710-919R6.0
Input message
Input message
............................................................................................................................................................................................................................................................
Input message
components
USDS Input Messages follow the same basic format as MAS platform
Input Messages. The basic format is as follows:
OPERATOR: UNIT, PARAMETER (S);
where:
Operator represents a verb that indicates the kind of action you

want the MAS to perform, for example "OP" (output) or "RMV"
(remove).
A colon separates the operator from UNIT.
UNIT represents the object on which you want the operator verb
to act. For USDS purposes, the unit will typically be
"SPA=<spa_name>". Where <spa_name> represents the actual
name of the HCF SPA or HDF SPA.
A comma separates UNIT from any additional parameters - if

required or optional parameters are used.
Parameters represent extensions to the Input Message. They can

be mandatory or optional.
The semicolon indicates the end of a message. It is the signal that

indicates that MAS should process the request. The semicolon
given at the end of an input message format indicates that, when
the input message has been entered with all the appropriate
variables and options, the user must type a semicolon or press
[RETURN].
Command keyword strings that contain special characters (such as

_ or /) or blanks must be enclosed in double quotation marks (" ").
For example, fullinit:is,cf="hlr_df1001".
Input messages are executed in subshell in MAS.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 5
Procedure: Send command from the eSM GUI

............................................................................................................................................................................................................................................................
Purpose
This procedure shows you how to send commands (Input Message)

from the eSM GUI. In this procedure, we take SSD Update as an
example.
detailed procedures in your eSM user documentation.
Important!
Before you begin
You must have eSM access and permission to complete this procedure.
Steps
Perform the following steps to create and run an SSD update command.
...........................................................................................................................................................................
From a Web browser window, log on to the eSM and enter the eSM
main launch page displayed in Figure 4-1, "eSM main launch page"
(4-6).
Figure 4-1
eSM main launch page
...........................................................................................................................................................................
Click Commands to enter the eSM Command Order interface.
...........................................................................................................................................................................................................................................................
4 - 6

270-710-919R6.0
Figure 4-2
Commands screen
Result: The Commands screen is displayed, listing any previously
created command orders as shown in Figure 4-2, "Commands

screen" (4-7).
...........................................................................................................................................................................
Click on the starburst icon to create a New Command.

Result: The Define the Command screen is displayed as shown in
Figure 4-3, "Define the command" (4-8).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 7
Figure 4-3
Define the command
...........................................................................................................................................................................
On this page:
Select the Service (HDF-Standard, Version 600) and the

Category (System Data) from the command drop-down list.
Select SSD_Update_WithMIN (SSD_Update_WithIMSI or

SSD_Update_WithMDN).
Type in a valid subscriber MIN in the MIN field (The MIN must
be a 10-digit numeric string).
From the list of Distribute to NE list, select the network element

that will be excluded for the command. Use the arrow keys to
move the NE to the Exclude column.
Provide this command order with a unique Command Order

Name (must be a 1 to 14 digit numeric string).
...........................................................................................................................................................................
Click Finish.
...........................................................................................................................................................................................................................................................
4 - 8

270-710-919R6.0
Figure 4-4
Refresh button
Result: The Command screen is displayed. The command order
information is downloaded to the Network Elements and online

status messages are returned to the eSM. Click Refresh as shown in
Figure 4-4, "Refresh button" (4-9), the command result will display.
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 9
FULLINIT:IS [, CLEANUP |, DFPUMP | CF=a

[, UCL]]

............................................................................................................................................................................................................................................................
Description
This IM is used to initiate Index Server data downloading when the

HCF SPA encounters failure. The IM must be mainly used for manual
mode of index server full init and peer pump procedures, and it can also
be used for some scenarios of failure recovery.
This IM has two uses:
FULLINIT:IS [, CLEANUP |, DFPUMP]: Full initialize the

index server routing data on the HCF node by getting required
information from all the HDF pairs in the USDS complex.
The optional parameter "CLEANUP" is used to indicate

whether the HCF SPA must clean up all the index server data
unconditionally before index server data downloading is
initiated.
The optional parameter "DFPUMP" is used to indicate

whether the HCF SPA must reload all data from HDF pairs
and prohibit peer pump.
FULLINIT:IS, CF=a [, UCL]: Full initialize the index server

routing data on the HCF node by getting data from the specified
source HCF node. This is a peer pump scenario. The parameter
"CF" specifies the source HCF where to get the index server data.
The optional parameter "UCL" indicates whether to do the

peer pump unconditionally. Under normal conditions, the
source HCF (a) is a local HCF to the HCF on which this IM
is executed. If the specified source HCF is a remote HCF, the
optional parameter "UCL" is needed. Otherwise, this IM will
fail.
Important!
This command can only be executed on HCF nodes.
To reduce the impact on the peer HCF, the command

FULLINIT:IS, CF=a [, UCL] cannot be executed more than once
for the same [CF=a], if the first command is still in execution.
Important!
Important!
Do not [UCL] parameter for low cost configurations in
this release.
Message Format
This IM is structured as follows:

FULLINIT:IS [, CLEANUP |, DFPUMP |CF=a [, UCL]]
...........................................................................................................................................................................................................................................................
4 - 10

270-710-919R6.0

[, UCL]]
Parameters
The parameters include:

Parameter
Description
CLEANUP
Indicates whether the HCF SPA will

clean up all the index server data
unconditionally before index server data
downloading is initiated.
DFPUMP
Indicates whether the HCF SPA will

reload all data from HDF pairs and
prohibit peer pump.
CF=a
Specifies the source HCF where to get

the index server data during the peer
pump scenario.
UCL
Indicates whether to do the peer pump

unconditionally.
Note: Parameter "CLEANUP" cannot be used together with "CF=a"

and "UCL". "CF=a" and "UCL" can be used together.
Example
Related output
< FULLINIT:IS
The possible results are as follows:
1.
Index Server FULL INIT procedure is initiated successfully by the

HCF SPA:
< fullinit:is; Will initiate Index Server FULL INIT procedure, CONTINUE Y
OR N? y;
IP - IS FULL INIT SENT TO HCF SPA, WAITING FOR RESPONSE
+++ ISQUAD_CF12 2004-10-20 11:21:18 MAINT /HLR008 #000211 as02
LEAD >
M FULLINIT IS
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 11

[, UCL]]
2.
Index Server FULL INIT procedure cannot be initiated because

the HCF SPA has been "In Service":
OR N? y;
LEAD >
M FULLINIT IS
IS FULL INIT Not initiated because HCF SPA is in service
HLR INDEX SERVER FULL INIT FAILED
3.

the HCF SPA has been involved in another FULL INIT procedure:
< fullinit:is,cleanup; Will initiate Index Server FULL INIT procedure,
CONTINUE Y OR N? y;
LEAD >
M FULLINIT IS CLEANUP
IS FULL INIT Not initiated because a FULL INIT has been in progress
4.
Fail to start FULL INIT procedure by the HCF SPA:

CONTINUE Y OR N? y;
LEAD >
IS FULL INIT Not initiated due to internal errors
...........................................................................................................................................................................................................................................................
4 - 12

270-710-919R6.0

[, UCL]]
5.

the HCF SPA has been involved in another Index Server Peer
Pump procedure:
CONTINUE Y OR N? y;
LEAD >
IS FULL INIT Not initiated because a Peer Pump has been in progress
6.
Fail to communicate with the HCF SPA:

OR N? y; RL - INTERNAL ERROR
7.
One HCF is initiated successfully by HCF SPA. The command is

used to designate the host name of one HCF to do Peer Pump. The
HCF SPA on the HCF is in service and has the same version (not
in upgrade procedure). The HCF can be remote only if UCL
option is specified:
< fullinit:is,cf="hlrcf8"; Will initiate Index Server FULL INIT procedure,
FOR RESPONSE
+++ HLRCF4 2004-12-20 11:21:18 MAINT /HLR008 #000211 as02 LEAD >
8.
Invalid HCF host name for Index Server FULL INIT procedure:
< fullinit:is,cf="hlrdf4"; Will initiate Index Server FULL INIT procedure,
FOR RESPONSE
+++ HLRCF4 2004-12-20 11:21:18 MAINT /HLR008 #000211 as02 LEAD
>
M FULLINIT IS CF=HLRDF4
IS FULL INIT Not initiated because the hostname is NOT a valid CF
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 13

[, UCL]]
9.
A local HCF is expected for Index Server FULL INIT procedure

while a remote HCF is specified as the source HCF:
< fullinit:is,cf="hlrcf9"; Will initiate Index Server FULL INIT procedure,
FOR RESPONSE
IS FULL INIT Not initiated because a local CF is expected for Peer Pump, use
UCL option for remote CF
10. Invalid HCF to do Peer Pump for Index Server FULL INIT
procedure, e.g. In OOS state:
< fullinit:is,cf="hlrcf9",ucl; IP - IS FULL INIT SENT TO HCF SPA,
WAITING FOR RESPONSE
M FULLINIT IS CF=HLRCF9 UCL
IS FULL INIT Not initiated because the CF is an INVALID target for Peer
Pump
...........................................................................................................................................................................................................................................................
4 - 14

270-710-919R6.0
SSD update (ANSI)
SSD update (ANSI)

............................................................................................................................................................................................................................................................
Description
Shared Secret Data (SSD) Update command is provided at the MAS

and eSM to initiate an SSD Update procedure for an authentication
capable Mobile Station (MS). The SSD Update procedures are used to
ensure that SSD is identical in both Authentication Center (AC) and
MS. It is used only for ANSI.
The SSD Update command results in an Authentication Directive
Invoke message sent by the AC/Home Location Register (HLR) to the
Mobile Switching Center (MSC)/Visitor Location Register (VLR).The
subsequent messages of BaseStationChallenge and AuthStatus Report
requests are sent from the Serving-MSC/VLR to HLR/AC that report
the SSD Update result.
This input command can accept IMSI, MIN or Mobile Directory
Number (MDN) as valid MS identifiers.
Important!
Message format
This command can only be executed on HDF nodes.
The SSD Update command is structured as follows:

SND: TEXT="ANSISSDUPD: MIN=a | IMSI=b| MDN=c", RK=m
Parameters

Parameter
Description
MIN=a
MIN of the subscribers who will have SSD Updates.
IMSI=b
IMSI of the subscribers who will have SSD

Updates.
MDN=c
MDN of the subscribers who will have SSD

Updates.
RK=m
The Routing Key (RK) where the message will be

routed. For USDS R6.0, it is HDF600.
Example: < SND: TEXT="ANSISSDUPD:
MIN=4109197623",RK=HDF600
Related output
Here is an example of its output message:

+++ HLR_DF1 2004-02-27 20:48:32 ANSIAC#999999 as001 LEAD >
HLR ANSI AC
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 15
SSD update (ANSI)
message=AUTH:AC:SSD:Success -received AuthenticationStatusReport

INVOKE from MSC/VLR with SSDUpdateReport and UniqueChallengeReport
parameters both equal to 3 Message Id=32001;
subscriber informations:MIN =4109197623; MSCID =000208 ESN =12345678
...........................................................................................................................................................................................................................................................
4 - 16

270-710-919R6.0

............................................................................................................................................................................................................................................................
Description
The Unique Challenge command is provided at the MAS and eSM to

initiate a Unique Challenge procedure for an authentication capable
MS. The Unique Challenge procedure is used for an AC to select the
Random Number and to challenge MS so that it verifies the MS's SSD.
It is used only for ANSI.
This command results in an AuthenticationDirective operation Invoke
sent by the AC/HLR to the MSC/VLR. Subsequent message for
AuthStatusReport requests are sent from the Serving-MSC/VLR to
HLR/AC, to report the Unique Challenge result.
The technician input command can accept IMSI, MIN or MDN as valid
MS identifiers.
Important!
Message format
The Unique Challenge command is structured as follows:

SND: TEXT="ANSIUNICHALL: MIN=a| IMSI=b| MDN=c ", RK=m
Parameters

Parameter
Description
MIN=a
MIN of the subscribers who will have Unique

Challenge.
IMSI=b
IMSI of the subscriber who will have Unique

Challenge.
MDN=c
MDN of the subscriber who will have Unique

Challenge.
RK=m
The Routing Key where the message will be routed.

For USDS R6.0, this is HDF600.
Example: < SND: TEXT="ANSIUNICHALL, MIN=4109197623",
RK=HDF600
Related output
Here is an example of its output message:

+++ HLR_CF11 2004-03-01 13:42:23 ANSIAC
#999999 as001 LEAD
HLR ANSI AC
message=AUTH:AC:UniChal:Success -received AuthenticationStatusReport
INVOKE from MSC/VLR with UniqueChallengeReport parameter equal to 3
Message Id=32013;
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 17
subscriber informations:MIN =4109197623; MSCID =000208 ESN =12345678

...........................................................................................................................................................................................................................................................
4 - 18

270-710-919R6.0

............................................................................................................................................................................................................................................................
Description
Technician Initiated VLR Refresh is provided at the MAS and eSM to

refresh a VLR record (i.e., send a Qualification Directive Invoke
message to the VLR). It is used only for ANSI.
This command can accept IMSI and MIN as subscriber identifier.
Important!
Message format
The Technician Initiated VLR Refresh command is structured as

follows:
SND: TEXT="ANSIREFVLR: MIN=a|IMSI=b", RK=m
Example: <SND:
TEXT="ANSIREFVLR:MIN=0902060006",rk=HDF600;
Related output
Parameters
+++ HLR_1405 2004-11-19 16:07:44 INECHO

#000069 as001 LEAD >
SND TEXT="ANSIREFVLR:MIN=0902060006" RK=HDF600 OK
END OF REPORT #000069+++++ HLR_1405 2004-11-19 16:07:50 SDHLR
#999999 as001 LEAD >
HCF ANSISCVLRUPD OPERATION
message= Service Command Succeed -(REFRESH VLR REQUEST FOR
MIN=[0902060006],
MDN=[0902060006] COMPLETED) With Correlation ID (NA)
Message Id=39914; MIN =0902060006;

Parameter
Description
MIN=a
MIN of the subscribers who will have

Technician Initiated VLR Refresh.
IMSI=b
IMSI of the subscribers who will have

Technician Initiated VLR Refresh.
RK=m
The Routing Key where the message will

be routed. For USDS R6.0, this is
HDF600.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 19

............................................................................................................................................................................................................................................................
Description
Technician Initiated VLR Delete is provided at the MAS and eSM to

delete a VLR record. It is used only for ANSI.
This Input Message can accept IMSI or MIN as subscriber identifier
Important!
Message format
The Technician Initiated VLR Delete command is structured as

follows:
SND: TEXT="ANSICNLVLR: MIN=a|IMSI=b ", RK=m
Example: <SND:TEXT="ANSICNLVLR:MIN=0902060006",rk=
HDF600;
Related output
Parameters
+++ HLR_DF2 2004-09-20 12:54:20 INECHO

#000018 as001 LEAD >
SND TEXT="ANSICNLVLR:MIN=0902060006" RK=HDF600 OK
END OF REPORT #000018+++++ HLR_DF2 2004-09-20 12:54:25 MAINT
#000214 as001 LEAD >
HCF ANSISCVLRUPD OPERATION
message= Service Command Succeed -(DELETE VLR REQUEST FOR
MIN=[0902060006], M
DN=[13302060006] COMPLETED) With Correlation ID (NA)
Message Id=39914; MIN =0902060006;

Parameter
Description
MIN=a
MIN of the subscribers who will have

Technician Initiated VLR Delete.
IMSI=b
IMSI of the subscribers who will have

Technician Initiated VLR Delete.
RK=m
The Routing Key where the message will

be routed. For USDS R6.0, this is
HDF600.
...........................................................................................................................................................................................................................................................
4 - 20

270-710-919R6.0
CANCEL: MAP (UMTS)
CANCEL: MAP (UMTS)

............................................................................................................................................................................................................................................................
Description
CANCEL: MAP manually cancels subscribers' location information in

VLRs and Serving GPRS Support Nodes (SGSNs).
The CANCEL: MAP Input Message should be used only during
maintenance windows (periods of time when service requests are low
and resource-intensive maintenance procedures are allowed)
established by your local practices.
Important!
In all CANCEL: MAP Input/Output Message

information, references to "VLR" apply to both VLR and SGSN.
Important!
Message format
The CANCEL: MAP Input Message is structured as follows:

CANCEL: MAP STARTIMSI=a [,ENDIMSI=b] [,UCL]
Parameters

Parameter
Description
STARTIMSI=a
(a) represents the required starting IMSI.

If only STARTIMSI is specified, or if (a)
and (b) are the same, only one IMSI is
cancelled.
ENDIMSI=b
(b) represents an optional ending IMSI

used to specify a range of IMSIs used to
cancel.
UCL
The "unconditional" option. When used,

it bypasses the "WILL CANCEL ALL
IMSIs IN RANGE SPECIFIED,
CONTINUE Y OR N?" warning message
and starts the data update immediately.
Example: < CANCEL: MAP, STARTIMSI=234021000005,

ENDIMSI=234021000006, UCL
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 21
RECOVER: MAP (UMTS)
RECOVER: MAP (UMTS)

............................................................................................................................................................................................................................................................
Description
RECOVER: MAP recovers the corrupt or un-synchronized dynamic

subscriber information.
The RECOVER: MAP IM should be used infrequently, and only within
the fault recovery or other maintenance strategy. Lucent recommends
that RECOVER: MAP be used only during maintenance windows
established by your local practices, or in response to service outages.
Important!
Message format
The RECOVER: MAP Input Message is structured as follows:

RECOVER: MAP [, ALL|, STARTIMSI=a, [ENDIMSI=b] [,
VLR=c]| , SGSN=d][,UCL]
Parameters

Parameter
Description
ALL
Selects all system IMSIs for the dynamic

data update process.
STARTIMSI=a, ENDIMSI=b
An optional range of IMSIs. If a range is

selected, it must include both a valid start
IMSI (a) and end IMSI (b). If this option
is used, only IMSIs in the specified range
are reset. If (a) and (b) are the same, only
the specified IMSI is reset.
VLR=c
A specific VLR identified by the string

"c". If this option is used, only the IMSIs
associated with the specified VLR are
reset. The VLR option can be used alone,
or in conjunction with an IMSI range.
SGSN=d
A specific SGSN identified by the string

"d". If this option is used, only the IMSIs
associated with the specified SGSN are
reset. The SGSN option can be used
alone, or in conjunction with an IMSI
range but it cannot be used with VLR
synchronously.
...........................................................................................................................................................................................................................................................
4 - 22

270-710-919R6.0
RECOVER: MAP (UMTS)
Parameter
Description
UCL

it bypasses the "ARE YOU SURE?"
warning message and starts the data
update immediately.
Example: <RECOVER: MAP, STARTIMSI=310454000176,

ENDIMSI=310454000177, UCL
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 23

............................................................................................................................................................................................................................................................
Description
Subscriber Number Report (SUBNUMREPT) command is provided at

the MAS and eSM to issue a request to report the subscriber count
status.
Important!
Message format
The subscriber number report command is structured as follows:

SND: TEXT=" SUBNUMREPT ", RK=m
Parameters

Parameter
Description
RK=m
The Routing Key where the message

will be routed. For USDS R6.0, it is
HDF600
Example: < SND: TEXT="SUBNUMREPT",RK=HDF600

Related output
Below is an example of the output message:

+++ HLR_DF1 2005-12-11 20:48:32 SDHLRDF
HDF SUBSCRIER REPORT
ANSI/UMTS
Subscribers: 4
Active_Subs: 1 Inactive_Subs: 3
#999999 as001 LEAD >
Message Id=10031;
...........................................................................................................................................................................................................................................................
4 - 24

270-710-919R6.0

............................................................................................................................................................................................................................................................
Description
CALEA Delivery Function Connection Test is provided for LMT and

eSM to perform Communications Assistance Law Enforcement Act
(CALEA) Delivery Function Connection Test for an ANSI or UMTS
user.
Important!
To execute this send text command from eSM GUI,

you must use HDF-CALEA, Version600 view.
Important!
Message format
The CALEA Delivery Function Connection Test command is

structured as follows:
SND: TEXT="ANSICNNTST: DF_IP=a, DF_Port=b,
MIN=c|IMSI=d, MEMO=e, HCF_ID=f", RK=m (for ANSI)
SND: TEXT="CNNTST: DF_IP=a, DF_Port=b, IMSI=c,
MEMO=e, HCF_ID=f", RK=m (for UMTS)
Parameters

Parameter
Description
DF_IP=a
Represents the target Lucent Technology

Delivery Unit (LTDUs) IP address, can
be formatted in IPV4, IPV6 or IPV4 and
IPV6 mixed formats.
DF_Port=b
Represents the target LTDU's IP port.
MIN=c
Represents an optional MIN used to

specify the cell phone traced.
IMSI=d
Represents an optional IMSI used to

specify the cell phone traced. If both MIN
and IMSI appear, MIN has the higher
priority.
MEMO=e
Represents an optional memorandum

string to be sent to the target LTDU
specified by DF_IP and DF_PORT. The
max size of e is 26. e with size larger than
26 will be trimmed and the 26 characters
to the left will be kept.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 25
HCF_ID=f
Represents an optional HCF_ID to

specify which HCF the command request
should be sent to. Otherwise the
command should be sent to all registered
HCFs.
RK=m
The Routing Key (RK) where the

message will be routed.
...........................................................................................................................................................................................................................................................
4 - 26

270-710-919R6.0

............................................................................................................................................................................................................................................................
Description
This IM sends RTR message to Serving Call Session Control Function

(S-CSCF) to de-register user. This IM provides flexibility to de-register
a user manually when necessary. It is used only for Home Subscriber
Server (HSS).
Important!
When using this IM, the service provider or technician

should ensure that the user is registered or unregistered at the SCSCF.
Important!
Message format
This IM is structured as follows:

DEREG: PRID=a [,PUID=b], HOST=c [,UCL]
Parameters

Parameter
Description
PRID=a
(a) represents the required Private User

ID (PRID) of the user.
PUID=b
(b) represents the optional Public User ID

(PUID) of the user. If it is specified, all
the PUIDs that are implicitly registered
with this PUID will be de registered.
HOST=c
(c) represents the required S-CSCF host

Fully Qualified Domain Name (FQDN),
which is case insensitive. The length
should be [5~96]
UCL

it bypasses the "Will Deregister the user,
CONTINUE Y OR N?" warning message
and starts the de-registration
immediately.
Example: <DEREG: PRID= "PR83621@lucent.com",
HOST="lucent.com"..
Related output
< DEREG:PRID="PR83621@lucent.com",HOST="lucent.com"; Will Deregister

the user, CONTINUE Y OR N? Y; IP - DEREGISTER INITITATED
+++ HLR_CF1405 2005-01-14 17:36:11 MAINT /HSS002 #000822 as001
LEAD >
M DEREG PRID="PR83621@lucent.com" HOST="lucent.com"
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 27
HSS DEREGISTER SUCCESSFULLY

...........................................................................................................................................................................................................................................................
4 - 28

270-710-919R6.0

............................................................................................................................................................................................................................................................
Description
For the super-charger USDS-HLR (UMTS) when the global service

data is changed, the timestamp value(s) is updated accordingly. The
update is automatically done when provisioning data from eSM. But in
some peculiar conditions, the timestamp is not updated and the
timestamp update command should be used to perform the updation.
The timestamp update command for global data is used in the
following conditions:
When updating global data from eSM, the timestamp of that

updated global table will be reset automatically; when updating
global data from RC/V, timestamp cannot be updated. Execute the
command: snd:text="TIMESTAMP:NAME=GLBL",rk=HCF600
on HCF or execute same command to one active HDF on eSM to
update the timestamp of all global tables.
In general, HDF restart does not cause the change of stored data.
However, if both HDFs in a pair crash, the customer needs to send
the command:
snd:text="TIMESTAMP:NAME=GLBL",rk=HCF600 on HCF or
execute the same command to one active HDF on eSM to update
the timestamp.
When provisioning global data on eSM, if you choose to force
merge and then reload data from eSM, timestamp of global data
cannot be updated. Execute the command
execute same command to one active HDF on eSM to update the
timestamp of global table.
After executing load active data on eSM, execute the command
execute same command to one active HDF on eSM to update the
timestamp of global table. If the load active data is scheduled for
future execution, the service command should also be scheduled
accordingly.
The timestamp update for feature lock (RTU) is used when locking/
unlocking the following RTUs. The command
snd:text="TIMESTAMP:NAME=<rtu name>",rk=HCF600 on HCF or
same command to one active HDF on eSM need to be executed to sync
the timestamp.
The RTU name in the command can be:
CUG
AOCC
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 29
Message format
Parameters
CAMEL
PDPC3
PDPC4
PDPC5
PDPC6
PLMN_SPECSS
<SND:TEXT="TIMESTAMP:NAME=GLBL",RK=HDF600;
<SND:TEXT="TIMESTAMP:NAME=<rtu
name>",RK=HDF600;
Parameter
Description
NAME =a
For timestamp update for global data:
GLBL
For timestamp update for RTUs:
RK=m
CUG
AOCC
CAMEL
PDPC3
PDPC4
PDPC5
PDPC6
PLMN_SPECSS
The Routing Key (RK) where the

message will be routed.
Example: <
SND:TEXT="TIMESTAMP:NAME=GLBL",RK=HCF600;
Example: <SND:TEXT="TIMESTAMP:NAME=CUG",RK=HDF
600;
...........................................................................................................................................................................................................................................................
4 - 30

270-710-919R6.0
Output message
Output message
............................................................................................................................................................................................................................................................
Overview
This section describes USDS-specific typical Output Messages.

USDS SPAs generate different types of Output Message, for example,
Alarm, Events, Errors. This section provides general information on
Output Message.
For information on how to view and deal with alarms,
refer to Chapter 5, "Monitoring USDS".
Important!
For a complete set of OM log supported by USDS

R6.0, refer to Appendix B, "USDS OM logs".
Important!
This module does not describe MAS platform messages. For MAS
Input/Output Messages, refer to the MAS User Reference Guide (270700-176).
This section assumes the standard MAS-formatted
header and trailer that surround each Output Message. It does not
repeat the MAS-formatted header and trailer for each Output
Message.
Important!
Output message
components
This section describes the format of Output Messages. The numbers in

parentheses are given for field number reference only and do not
appear in the actual Output Messages.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 31
Output message
Table 4-1
Sample output message
(1)
+++ HLR_CF21
(2)
(3)
2004-05-07
10:51:56
(4)
(5)
MAINT
/MS012
(7)
(8)
(9)
as000
LEAD
SEG#1
(10)
**
(6)
#001910
(11)
REPT INIT REQUESTED
(12)
Field 1
The reporting MASs logical name. The report begins with a +++,
which indicates that this is the start of the message.
Field 2
The date format. The default is YYYY-MM-DD where:
YYYY = year
MM = month
DD = day
Field 3
The time format. The default is HH-MM-SS where:
HH = hour
MM = minutes
SS = seconds
Field 4
The message class, defines the routing destinations for the Output
Messages and are defined in RC/V Form 2.2: USL MESSAGE CLASS
DEFINITION FORM. For more information, refer to Message Class or
the MAS User Reference Guide (270-700-176).
...........................................................................................................................................................................................................................................................
4 - 32

270-710-919R6.0
Output message
Field 5
The Output Message Database (OMDB) key points to an output
message format that is defined in RC/V Form 2.3: USL OUTPUT
MESSAGE DEFINITION FORM.
Field 6
The sequence number is a sequential number between 000001 and
999999 per report destination or message class type. MAS reserves the
number 999999 for special circumstances.
Field 7 (optional)
Segment number. Extremely long messages are output in segments
with identifying numbers that indicate the order in which the outputs
have to be assembled.
Field 8
The logical name of the host processor that generated the message.
HCF = asXXX in field 8
HDF = asXXX in field 8
Note: The actual logical name can be accessed in /sn/msgh/msghosts

file.
Field 9
The status of the host processor. The following status indicators may
display:
ACT = Active
LEAD = Lead processor
UNK = Unknown
Field 10 (optional)
Alarm state or additional information. If used, this field starts line 2 of
the Output Message, and can include one of the following:
*a - a message that may need operators action
*m - a message that is generated by manual request
*C - a critical alarm
** - a major alarm
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 33
Output message
* - a minor alarm
Field 11
The body of the Output Message, one or more lines of text.
Field 12
The sequence number is associated with the header. The end of the
report is followed by a ++-, which indicates that the message contains
no more information.
...........................................................................................................................................................................................................................................................
4 - 34

270-710-919R6.0
Redirect Omlogs
Procedure: Redirect Omlogs

............................................................................................................................................................................................................................................................
Overview
By default, the Omlogs of the USDS SPA are stored in /sn/log/OMlog0

or /sn/log/OMlog1. However, the USDS provides the options to
redirect part of the Omlogs for the following scenarios:
ANSI Call Delivery
ANSI Registration
ANSI Authentication
Load Balancing
Traffic Analysis Measurement
Combo HSS HDF Omlogs
ANSI PDLS
UMTS PDLS
IMS PDLS
AAA PDLS
SMPP PDLS
Table 4-2, "Message class supported in USDS." (4-35) lists the

message class associated with the scenarios
Table 4-2
Message class supported in USDS.
Message class
Scenarios
SPA
ANSIRL
ANSI Call Delivery
HCF
ANSIRT
ANSI Registration
HCF
ANSIAC
ANSI Authentication
HCF and HDF
SDHLRLB
Load balancing
HCF and HDF
APMEAS
Traffic analysis measurements
HCF
SDHLRDF
Combo HSS HDF Omlogs
HDF
SDHLRA
ANSI PDLS
HCF
SDHLRU
UMTS PDLS
HCF
SDHLRI
IMS PDLS
HCF
SDHLRG
AAA PDLS
HCF
SDHLRM
SMPP PDLS
HCF
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 35
Redirect Omlogs
Message class
Scenarios
SPA
SDHLR
Other scenarios
HCF
RC/V forms related to this procedure are:
Purpose
USL MESSAGE DESTINATION FORM (Form 2.1)
USL MESSAGE CLASS DEFINITION FORM (Form 2.2)
Use this procedure to redirect part of the Omlogs supported by the

USDS.
This procedure is not to replace the detailed
procedures provided by MAS platform. For more information on
the configuration of output message, refer to Chapter 5 of MAS
Recent Change and Verify, 270-780-422.
Important!
Steps
...........................................................................................................................................................................
Log on to the MAS node with root.

...........................................................................................................................................................................
Enter the subshell by the following command:

>subshl
...........................................................................................................................................................................
Start the RC/V menu by the following command:

<RCV:MENU;
Result: The NETWORK PLATFORM MAIN MENU is
displayed, as shown in Figure 4-5, "Network Platform Main Menu"

(4-37).
...........................................................................................................................................................................................................................................................
4 - 36

270-710-919R6.0
Redirect Omlogs
Figure 4-5
Network Platform Main Menu
...........................................................................................................................................................................
Type [2.1] to access the USL MESSAGE DESTINATION FORM.

Result: The prompt for the operations to this form is displayed.
...........................................................................................................................................................................
Press [I] to insert a new record.

Result: The USL MESSAGE DESTINATION FORM is
displayed.
...........................................................................................................................................................................
Enter the fields in this form, as shown in Table 4-3, "Fields explanation
in form 2.1." (4-38).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 37
Redirect Omlogs
Table 4-3
Fields explanation in form 2.1.
Fields
Value or description
DEST
Identifies the routing destination of the

output message. This value is referred in
form 2.2.
For example, ACLG
LOGICALDEV
Identifies the file name for a log file. File

names other than NULL must be
uniquely paired with an output message.
All log files go under /sn/log. (Only logs
can be stored under this directory.) Up to
50 characters.
For example: aclog
CHANNELTYPE
Identifies the process that receives the

output message.
The LOG process receives the output
message if a log file is named in the
previous field. Otherwise, any existing
process may be used.
Up to 12 characters.
For example: LOG (for log file).
LOGHSIZE
Defines a size limit for a log file (in

bytes). The size is specified as half the
size of the log file.
Up to seven digits, range: 0 to 9999999.
For example: 6000000
DAILY
Specifies whether the destination log file

should be switched daily (at midnight).
By default (DAILY = N), destination log
files are switched only when they reach a
maximum size (as specified in field four).
By setting DAILY = Y, the destination
log file will be switched at midnight
regardless of whether the log file has
reached maximum size.
For example: N
...........................................................................................................................................................................................................................................................
4 - 38

270-710-919R6.0
Redirect Omlogs
Fields
MAX # FILES
Specifies the number of log files that will

be created.
Example: If the MAX # FILES field
equals three, logfile0, logfile1, and
logfile2 will be created.
Messages will be sent to log files in a
cyclic pattern: logfile0 first, logfile1
second, logfile2 third, logfile0 fourth,....
Up to two digits, range: 2 to 20.
Default is 2.
For example: 2
Figure 4-6
USL Message Destination Form
Result: A new record is created, as shown in Figure 4-6, "USL
Message Destination Form" (4-39).

...........................................................................................................................................................................
Press [I] to insert this record.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 39
Redirect Omlogs
...........................................................................................................................................................................
Press [<] to go to the OPERATIONS, ADMINISTRATION AND

MAINTENANCE SUBMENU.
Result: The OPERATIONS, ADMINISTRATION AND
MAINTENANCE SUBMENU is displayed, as shown in

Figure 4-7, "The Operations, Administration and Maintenance
Submenu" (4-40).
Figure 4-7
The Operations, Administration and Maintenance

Submenu
...........................................................................................................................................................................
Type [2] to go to the USL MESSAGE CLASS DEFINITION

FORM.
Result: The prompt for the operations to this form is displayed.
...........................................................................................................................................................................
10
Press [I] to insert a new record.

Result: The USL MESSAGE CLASS DEFINITION FORM is
displayed.
...........................................................................................................................................................................................................................................................
4 - 40

270-710-919R6.0
Redirect Omlogs
...........................................................................................................................................................................
11
Enter the fields in this form, as shown in Table 4-4, "Fields explanation
in form 2.2" (4-41).
Table 4-4
Fields explanation in form 2.2
Fields
MESSAGE CLASS
Identifies the output message class. Refer

to the overview section of this procedure
for more information on the message
classes supported by the USDS.
For example, ANSIAC.
DESTINATION0
~
Identify the routing destinations (defined

in the USL MESSAGE DESTINATION
FORM 2.1) for the output message.
For example, ACLG
DESTINATION9
Result: A new record is created, as shown in Figure 4-8, "USL
Message Class Definition Form" (4-41).

Figure 4-8
USL Message Class Definition Form
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 41
Procedure: Configure the severity level for OMLogs

............................................................................................................................................................................................................................................................
Overview
The USDS allows administrator to provision severity level for each

service logic OM Log messages. The severity levels are Critical, Major,
Minor, Manual, Action and Information (from high to low).
Purpose
Use this procedure to configure the severity level for USDS OMLogs.
As this procedure involves provisioning data from the
eSM, we take the HDF-Standard view as an example.
Important!
Before you begin
Steps
Got the ID for the OMlogs from Appendix B, "USDS OM logs" of

this book.
Got the access to eSM GUI.
Unlocked the RTU named "OMLog".
Defined the network element and network element group for the
SYSTEM category from eSM.
Perform the following step to configure the severity of OMLogs.

...........................................................................................................................................................................
Log on to the eSM GUI and go to the eSM launch page.

Result: The eSM launch page is displayed, as shown in Figure 4-9,
"eSM launch page" (4-43).
...........................................................................................................................................................................................................................................................
4 - 42

270-710-919R6.0

Figure 4-9
eSM launch page
...........................................................................................................................................................................
From the eSM launch page, go to the Service Objects page by clicking
the Service Objects icon.
Result: The Service Objects page is displayed, as shown in
Figure 4-10, "The Service Objects page" (4-44).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 43

Figure 4-10
The Service Objects page
The following procedure shows an example that

already has a SYSTEM Service Object. If you did not create such a
SO, you need to follow the eSM instructions to create a new one.
Important!
...........................................................................................................................................................................
Search for the existing Service Object on the Service Objects page, as
shown in Figure 4-11, "Searching the existing Service Objects" (4-45).
...........................................................................................................................................................................................................................................................
4 - 44

270-710-919R6.0

Figure 4-11
Searching the existing Service Objects
Result: The Service Object is displayed, as shown in Figure 4-12,
"Search Result" (4-46).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 45

Figure 4-12
Search Result
...........................................................................................................................................................................
If the capability named "SDHLR Alarm Table" is already provisioned,

update the table by clicking on its name. Otherwise, add this capability
by clicking the asterisk icon on this page.
Result: The Choose Optional Capabilities page is displayed, as
shown in Figure 4-13, "Page for choosing optional capabilities"

(4-47).
...........................................................................................................................................................................................................................................................
4 - 46

270-710-919R6.0

Figure 4-13
Page for choosing optional capabilities
...........................................................................................................................................................................
Click Next to go to the SDHLR Alarm Table.

Result: The page for SDHLR Alarm Table is displayed, as shown
in Figure 4-14, "Page for SDHLR Alarm Table" (4-48).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 47

Figure 4-14
Page for SDHLR Alarm Table
...........................................................................................................................................................................
On the SDHLR Alarm Table, fill in the Message IDs (refer to

Appendix B for the Message ID of each Omlogs) and corresponding
severities, as shown in Figure 4-15, "The required fields for the
SDHLR Alarm Table" (4-49). Click Add to insert this record.
The example in this procedure is 32001, which
indicates that the SSD Update is successful.
Important!
...........................................................................................................................................................................................................................................................
4 - 48

270-710-919R6.0

Figure 4-15
The required fields for the SDHLR Alarm Table
...........................................................................................................................................................................
To add more records, repeat Step 6.

...........................................................................................................................................................................
Click Next to go to the next page.

Result: A summary page is displayed for review purposes.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 49

Figure 4-16
SO change request summary
...........................................................................................................................................................................
Follow the eSM online instruction to process this Service Object, as

shown in Figure 4-17, "Process this work order" (4-51).
Result: This SO is updated to set the severity level of OMLog
32001.
...........................................................................................................................................................................................................................................................
4 - 50

270-710-919R6.0

Figure 4-17
Process this work order
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

4 - 51
View output message
Procedure: View output message

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Output message sources
View log file alarm

messages
Use this procedure to view the SPA-related output messages.

You must have access to the MAS LMT and printer (optional) to
perform this task.
SPA-generated output messages are collected by each MAS and are
stored in /sn/log/OMlog0 and /sn/log/OMlog1.
The following procedure is to be completed to view the output
messages, which exist in OMlog0 or OMlog1.
...........................................................................................................................................................................
Open a MAS UNIX window for which you want to view output
messages.
...........................................................................................................................................................................
Move to the appropriate directory by typing the following command:

>cd /sn/log
...........................................................................................................................................................................
View output message by typing the following command:

>vi OMlog0 (OMlog1)
...........................................................................................................................................................................
Analyze output messages for the information you need.

...........................................................................................................................................................................
When you have finished viewing the messages, quit the file(s) and exit
the UNIX window.
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
4 - 52

270-710-919R6.0
Monitoring USDS
Overview
............................................................................................................................................................................................................................................................
Purpose
Contents
This chapter introduces the procedures to monitor the USDS.

5-2
Monitoring alarms
5-8
Locate and clear USDS alarms at DAP
5-16
View alarms in log file
5-18
Monitor alarms with "tailer" command
5-20
Resolve recurring USDS SPA alarms
5-22
5-26
5-27
............................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 1
Monitoring USDS

............................................................................................................................................................................................................................................................
Overview
Operations monitoring functions are supported by the MAS platform in

USDS R6.0. MAS receives messages from HCF SPAs and HDF SPAs
regarding:
Alarms. Indicators of operational faults that result from crossing

operational thresholds.
Events. Transient operational occurrences that do not indicate a

problem unless they occur in large numbers within a short time.
Errors. Indicators of software processing problems.
Heartbeat failures. Messages that indicate USDS application

health.
Overload. Messages that indicate if a HCF SPA or HDF SPA is

having trouble meeting service requests.
The MAS platform software receives operations-related messages from

the USDS R6.0 application and makes them accessible to USDS
administrators.
For USDS R6.0, there are two methods to monitor operations-related
messages:
1.
2.
Monitor general SPA status from the MAS DAPs.

Analyze Output Messages in MAS log files, on-screen, or on
printers.
About MAS log files
The following subtopics summarize key concepts regarding the usage

of MAS log files. For more detailed information, refer to the MAS
System Administration Guide (270-700-167).
Log file organization
Log files are located in the /sn/log directory of each MAS machine.
Most of the log files exist as pairs. For example, the OMlog0 and
OMlog1. The MAS alternates between log files that exist as pairs when
the in-use file reaches its maximum capacity.
When the MAS switches to the alternate log file, it recreates the log file
by removing the previously stored data.
Searching log files
You can review log files:
By scrolling through the file with UNIX "cat".
With the UNIX vi text editor.
...........................................................................................................................................................................................................................................................
5 - 2

270-710-919R6.0
Monitoring USDS
With the UNIX grep command.
For more information, refer to the MAS User Reference Guide (270700-176) and the UNIX system man pages for cat, grep, and vi.
Saving log files
It may be helpful to store archive copies of log files for use in

troubleshooting or for future reference. You can save log files to disk or
tape manually using the UNIX cp (copy) command or other methods.
For detailed information to save log files, refer to the related UNIX
system man page.
...........................................................................................................................................................................
CAUTION
Do not save copies of log files to /sn/log as it reduces
the space for log files.
USDS SPA-related DAPs
Press [F3] in the MAS DAPs. After "CMD<" command prompt, type
the corresponding number. For Page110xx, xx is the SPA number in
1100 page.
USDS administrators need to use the following MAS DAPs:
Page 100, Main Menu (Figure 5-1, "Page 100, Main Menu" (5-4))
Page 110, SPA Summary (Figure 5-2, "Page 110, SPA summary"
(5-5))
Page 1100, SPA Summary 0-29 (Figure 5-3, "Page 1100, SPA
Summary 0-29" (5-6))
Page 110xx, SPA xx Machine Summary (Figure 5-4, "Page 110xx,

SPA xx Machine Summary" (5-7))
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 3
Monitoring USDS
Figure 5-1
Page 100, Main Menu
...........................................................................................................................................................................................................................................................
5 - 4

270-710-919R6.0
Monitoring USDS
Figure 5-2
Page 110, SPA summary
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 5
Monitoring USDS
Figure 5-3
Page 1100, SPA Summary 0-29
...........................................................................................................................................................................................................................................................
5 - 6

270-710-919R6.0
Monitoring USDS
Figure 5-4
Related tasks
Page 110xx, SPA xx Machine Summary
Procedures associated with USDS alarms include:
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 7
Monitoring alarms
Monitoring USDS
Monitoring alarms
............................................................................................................................................................................................................................................................
Overview
For USDS R6.0, you can monitor alarms from the OMC-H. If no
OMC-H is available, you can monitor alarms by viewing MAS DAPs
and by viewing and analyzing the Output Messages available onscreen, at a printer, or in log files stored on the MAS:
1.
2.
Each MAS DAP provides visual summaries of the MAS,

including SPA (HCF or HDF) status and alarm status.
Output messages hold the detailed information that indicates the
cause of the alarm.
As USDS SPAs operate, they generate Output Messages that the MAS
receives, acts on if required, and stores. If a message indicates an alarm
condition, MAS delivers it in the following forms:
An output message delivered to the LMT (if connected to the

alarmed SPA).
An updated DAP.
An output message stored in a log file.
A printed message (optional).
An audible or visual indication of an alarm condition (optional).
OMC-H.
The MAS platform provides support for audible and
visual alarms that can be implemented as required.
Important!
Often messages will scroll by too quickly to be evaluated on screen. In

most cases you can find and evaluate alarm messages by viewing log
files or printouts.
This topic provides USDS-specific information about how to use the
MAS platform to monitor alarms. Figure 5-5, "High level alarm
resolution process" (5-9) depicts a high level process for resolving
USDS alarms.
...........................................................................................................................................................................................................................................................
5 - 8

270-710-919R6.0
Monitoring alarms
Monitoring USDS
Figure 5-5
Alarms in USDS
1.
High level alarm resolution process
Alarm to report the OSS status of USDS SPA
Alarming object
applState
Alarming type
processingErrorAlarm
Probable cause
applicationSubsystemfailure
Severity alarms
critical (if <new_state> is not in-service),

or cleared (if <new_state> is in-service)
Additional text
USDS-HLR application state changed to

<new_state>
2.
Alarm to report the overload status of USDS
Alarming object
applOverloadLevel
Alarming type
qualityOfServiceAlarm
Probable cause
congestion
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 9
Monitoring alarms
Monitoring USDS
Severity alarms
critical (if <new_level> is 4), or

major (if <new_level> is 3), or
minor (if <new_level> is 2), or
cleared (if <new_level> is 1)
Additional text
USDS-HLR application overload level

changed to <new_level> (where
<new_level> is from 1 to 4)
3.
Alarm to report the overload status of SS7 traffic
Alarming object
ss7OverloadLevel
Alarming type
Probable cause
congestion
Severity alarms

Additional text
ss7 overload level changed to

<new_level> (where <new_level> is
from 1 to 4)
4.
Alarm to report the overload status of Diameter protocol related

traffic
Alarming object
diameterOverloadLevel
Alarming type
Probable cause
congestion
Severity alarms

Additional text
Diameter protocol overload level

5.
Alarm to report the connectivity between HCF and HDF
Alarming object
hcfHdfConnStatus-<indexnumber>
...........................................................................................................................................................................................................................................................
5 - 10

270-710-919R6.0
Monitoring alarms
Monitoring USDS
Alarming type
communicationsAlarm
Probable cause
Receive failure
Severity alarms
major (if <new_state> is down), or

cleared (if <new_state> is up)
Additional text
connectivity with HDF <host_name> is

<new_state> (where <hostname> is the
HDF host name, <new_state> is up or
down)
6.
Alarm to report the loss of primary HDF in a HDF pair
Alarming object
hcfHdfConnPrimaryDf-<indexnumber>
Alarming type
communicationsAlarm
Probable cause
Receive failure
Severity alarms
minor or cleared
Additional text
Cannot find In Service primary HDF for

HDF pairs of <hostname1> and
<hostname2> (where <hostname1> and
<hostname2> are the host name of HDFs)
Note
In the following situations, this alarm

does not necessarily mean that one of the
HDFs has failed:
During a switching over for HDF roles,
HCF will send alarm to report there is no
in-service primary HDF in a pair since
the two HDFs both are in secondary state
for a very short time. After the state
transition finished normally, HCF will
send another alarm to clear the former
one.
If the primary HDF is shutdown or
reboot, in the short period before the
secondary HDF detects the primary
HDFs non-existence and takes over the
primary role. HCF will also send an
alarm. When primary HDF is restored,
HCF will send another alarm to clear the
former one.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 11
Monitoring alarms
Monitoring USDS
7.
Alarm to report the connection status of mated pairs
Alarming object
hdfMateConnStatus
Alarming type
communicationsAlarm
Probable cause
Receive failure
Severity alarms

Additional text
connectivity with mate HDF is

<new_state> (where <new_state> is up or
down)
8.
Alarm to report the data replication status between mated HDFs
Alarming object
hdfMateDataReplicationState
Alarming type
communicationsAlarm
Probable cause
softwareError
Severity alarms

clear (if <new_state> is up)
Additional text
HDF detected Timesten Database

replication is <new_state> (where
<new_state> is up or down)
9.
Alarm to report the connection status of HDF and HCF
Alarming object
hdfHcfConnStatus-<indexnumber>
Alarming type
communicationsAlarm
Probable cause
Receive failure
Severity alarms

Additional text
connectivity with HCF <host_name> is

<new_state> (where <hostname> is the
HCF host name, <new_state> is up or
down)
...........................................................................................................................................................................................................................................................
5 - 12

270-710-919R6.0
Monitoring alarms
Monitoring USDS
10. Alarm to indicate the failure of HDF pairs

Alarming object
hcfHdfConnDfPair-<indexnumber>
Alarming type
communicationsAlarm
Probable cause
Information missing
Severity alarms
Critical (if <new_state> is down and

mate <current_state> is down), or
Additional text
HDF pairs of <hostname1> and

<hostname2> is Out Of Service. (where
<hostname1> and <hostname2> are the
host name of HDFs)
11. Alarm to indicate the change of primary HDF

Alarming object
HdfPrimaryDf
Alarming type
Probable cause
Severity alarms
major (if mate <new_state> is down), or

cleared (if mate<new_state) is up)
Additional text
HDF <host_name> is the new Primary

HDF
12. Alarm to indicate the network connection failure between HCF

nodes. This alarm is sent when all the HCFs can communicate
with master ss7 node but cannot communicate with each other.
Alarming object
ss7Segment
Alarming type
Probable cause
Severity alarms
Critical (if ss7 segmentation happened),

or Cleared (if ss7 segmentation
recovered)
Additional text
SS7 segmentation <state> (where state is

happened or recovered)
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 13
Monitoring alarms
Monitoring USDS
13. Alarm to indicate the HDF simplex detected.

Alarming object
hdfSimplex
Alarming type
Probable cause
Severity alarms
major (1~5 hours after simplex happens),

or critical (5 hours after simplex
happens), or cleared (if HDF simplex is
cleared)
Additional text
HDF SIMPLEX DETECTED ON

NODE%s DUE TO ITS MATE GOING
DOWN
14. Alarm to indicate the congestion of HDF corc queue.

Alarming object
applCorcOverloadLevel
Alarming type
Probable cause
congestion
Severity alarms
critical (<Percentage> >=98), or major (if

<Percentage> >= 90), or cleared (if
<Percentage> < 90)
Additional text
HDF Corc Queue is occupied

<Percentage>% (where <Percentage>
can be 0~100)
Following alarms are sent by HCF:
Applstate
ApplOverloadLevel
HcfHdfConnStatus-<index_number>
HcfHdfConnPrimaryDf
HcfHdfConnDfPair
ss7Segment
Following alarms are sent by HDF:
Applstate
ApplOverloadLevel
hdfHcfConnStatus-<index_number>
hdfMateConnStatus
hdfPrimaryDf
...........................................................................................................................................................................................................................................................
5 - 14

270-710-919R6.0
Monitoring alarms
Monitoring USDS
hdfMateDataReplicationState
hdfSimplex
applCorcOverloadLevel
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 15
Monitoring USDS

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to identify a USDS SPA alarm and clear it from the
MAS DAP UI.
You must have access and permission for MAS LMT to perform
this procedure.
You must access the appropriate application server and open a

DAP window to it before you can perform this procedure.
Procedure references
This procedure assumes you are aware of the SPA alarm. You might
need the MAS documentation to provide additional information about
the DAP User Interface (UI).
Steps
Perform the following steps to locate and clear USDS SPA alarm(s) at
the MAS LMT DAP.
<USDS_HCF or USDS_HDF> represents the name of the alarmed
USDS SPA in the following procedure.
...........................................................................................................................................................................
Access DAP Page 100. (example see Figure 5-1, "Page 100, Main
Menu" (5-4)).
Result: Page 100 is displayed.
...........................................................................................................................................................................
Verify that the SPA alarm indicator is lit in the Summary Status area
near the top of page 100. If there is no alarm, exit this procedure.
...........................................................................................................................................................................
Access DAP 110, the SPA status summary page. (example see
Figure 5-2, "Page 110, SPA summary" (5-5)).
Result: Page 110 is displayed.
...........................................................................................................................................................................................................................................................
5 - 16

270-710-919R6.0
Monitoring USDS
...........................................................................................................................................................................
Clear SPA alarms using one of the following options.

To...
Then
Clear all SPA alarms
Enter command 500
Clear only the critical SPA

alarms
Enter command 510
Clear only the major SPA

alarms
Enter command 520
Clear only the minor SPA

alarms
Enter command 530
View more details for a HCF

or HDF SPA
Enter command 110xx, where xx

represents the number of SPA on the
1100 page. Clear the alarm at the 110xx
page using the desired command.
You must return to

110 to clear the alarms.
Important!
...........................................................................................................................................................................
Verify that the SPA alarm does not return. If the alarm returns, refer to
the Related procedure below.
END OF STEPS
...........................................................................................................................................................................
Related procedure
If the alarm returns, continue the procedure "Resolve recurring USDS

SPA alarms" (5-22).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 17
Monitoring USDS

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Alarm message sources
View log file alarm

messages
Use this procedure to view the SPA-related alarm output messages,

which help you to resolve recurring alarms.
You must have access to the MAS LMT and printer (optional) to
perform this task.
SPA-generated alarm messages are collected by each MAS and are
stored in /sn/log/OMlog0 and /sn/log/OMlog1.
The following procedure is to be completed in order to review the
alarm messages, which exist in OMlog0 or OMlog1.
...........................................................................................................................................................................
Open a MAS UNIX window to the MAS for which you want to view
alarm messages.
...........................................................................................................................................................................
Move to the appropriate directory by entering the following command:

>cd /sn/log
...........................................................................................................................................................................
Search the desired log file for the SPA alarm messages. The SPA alarm
messages are provided in "REPT SPA" format. For example, type the
following command:
>vi OMlog0(OMlog1)
Search files for the REPT messages (use "/" in "vi" command model),
which meet the following criteria:
Generated by a HCF or HDF
Prefixed by *, **, or *C.
...........................................................................................................................................................................
Analyze output messages for the information that helps you to identify
the cause of recurring SPA alarms. Examples of such information
includes:
...........................................................................................................................................................................................................................................................
5 - 18

270-710-919R6.0
Monitoring USDS
Messages that indicate large number of alarms in a specific SPA.
Messages that indicate large number of alarms in a specific time

span.
Multiple messages with the same or related information in the

message body.
...........................................................................................................................................................................
When you have finished viewing the messages, quit the file(s) and exit
the UNIX window.
END OF STEPS
...........................................................................................................................................................................
Related procedures
To resolve recurring SPA alarms, perform the procedure "Resolve

recurring USDS SPA alarms" (5-22).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 19
Monitoring USDS

............................................................................................................................................................................................................................................................
Purpose
Before you begin
This procedure shows you how to monitor SPA-related alarm output

messages, which are written to an OMlog file.
You must have access to the MAS LMT to perform this task.
Alarm message sources
The SPA-generated alarm messages are collected by each MAS and are
stored in /sn/log/OMlog0 and /sn/log/OMlog1. You can view the MAS
updates for a currently active file using the "tailer" command.
"tailer" a log file
Complete the following steps to view an alarm message updates for the
currently active files named OMlog0 or OMlog1.
...........................................................................................................................................................................
Open a UNIX window to the MAS for which you want to monitor
alarm messages.
...........................................................................................................................................................................
Move to the proper directory by entering by the following command:

>cd /sn/log
...........................................................................................................................................................................
Type the "tailer" command. For example:

>tailer OM
Result: MAS updates the currently active file OM log (OMlog0 or
OMlog1) and this is displayed on screen.

...........................................................................................................................................................................
Monitor the new messages for appearances of HCF or HDF messages

that indicate alarm conditions (prefixed by *, **, or *C).
...........................................................................................................................................................................
When you have finished viewing the message updates, stop the tailer
command by typing the following command:
>Ctrl-c
...........................................................................................................................................................................................................................................................
5 - 20

270-710-919R6.0
Monitoring USDS
(Hold down the control key and press [c])

Result: The log file is no longer updated on screen.
...........................................................................................................................................................................
Exit the UNIX window.

END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 21
Monitoring USDS

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Definition
Procedure assumptions
Resolve recurring USDS

SPA alarm
This procedure helps you to resolve the recurring USDS SPA alarms.
Perform procedure "Locate and clear USDS alarms at DAP"

(5-16)
Perform procedure "View alarms in log file" (5-18)
Open a UNIX subshl window for the MAS(s) in question.
Recurring SPA alarms are alarms that:
Return soon after being cleared from a DAP
Cannot be cleared from a DAP
Occur in unusual numbers
This procedure assumes that you have identified the recurring USDS
SPA alarm and you know:
Which SPA is generating an alarm.
Whether the cause is internal or external to the SPA (based on the

alarm message body text).
Whether the alarm is occurring in only one, or more than one, or

in all of the associated MAS.
Perform the following steps to resolve a recurring SPA alarm, where

the <USDS_HCF or USDS_HDF> represents those SPAs, which have
the recurring alarm.
...........................................................................................................................................................................
Assess the alarm's characteristics identified during the alarm message

analysis.
If...
Then...
The alarm is external to the

SPA
Troubleshoot the system or component

indicated by the alarm message text,
using the documentation provided by that
system or component.
The alarm is occurring in all

instances of the SPA
Assess the hardware and software

installation and configuration with your
Lucent Technologies support staff.
...........................................................................................................................................................................................................................................................
5 - 22

270-710-919R6.0
Monitoring USDS
If...
Then...
The alarm is internal to the

SPA and is not occurring in
every instance of the SPA
In conjunction with your Lucent

Technologies support staff, restart the
SPA by proceeding to Step 2.
WARNING
Restarting a wrong instance of a SPA can stop the
USDS service. Do not perform this procedure
unless another instance of a SPA is in service and
is performing properly, or unless you have been
directed to perform this procedure by the technical
support staff.
Wait for each step to complete, before you continue
with the next step or you start with another MAS process.
Important!
...........................................................................................................................................................................
Determine the state of an alarmed SPA by typing the following

command in the subshell:
<OP: STATUS, SPA=<USDS_HCF or USDS_HDF>

Result: A response similar to the below example is displayed.
SPA NAME: HCF600
SPA STATE: IS [or OOS, or MOOS, or EQP]
If the SPA is in service (IS) state, then proceed to Step 3.

If the SPA is in out of service (OOS) state, then proceed to Step 3.
If the SPA is in manual out of service (MOOS) state, then proceed
to Step 5.
If the SPA is in equipped (EQP) state, proceed to Step 7.
...........................................................................................................................................................................
Move SPA to the out of service state by the following command:

<RMV: SPA=<USDS_HCF or USDS_HDF>
Example: RMV: SPA=HCF600;

...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 23
Monitoring USDS

RMV:SPA REMOVES NEW CALL TRAFFIC, CONTINUE Y OR N?
...........................................................................................................................................................................
Press [Y] to remove the SPA from service.

Result: The following output message shows a SPA is out of
service:
RMV SPA =<USDS_HCF or USDS_HDF> COMPLETED SUCESSFULLY
The SPA is MOOS.

...........................................................................................................................................................................
Move the SPA into the equipped state by entering the following
command:
<DELETE: SPA =<USDS_HCF or USDS_HDF>, PROC;
Example: DELETE: SPA=HCF600, PROC;


DELETE:SPA REMOVES SPA PROCESS, CONTINUE Y OR N?
...........................................................................................................................................................................
Press [Y] to stop the SPA.

Result: All SPA processes are stopped on the selected MAS. The
SPA state changes to the equipped (EQP). The following output

message shows the SPA that is stopped:
DELETE PROC SPA <USDS_HCF or USDS_HDF> COMPLETED
SUCESSFULLY
...........................................................................................................................................................................
Restart the SPA by typing the following command:

<INSTALL: SPA=<USDS_HCF or USDS_HDF>, PROC;
Example: INSTALL: SPA=HCF600, PROC;

Result: A message similar to the following is displayed. The SPA
moves to the manual out of service (MOOS) state.

M INSTALL PROC,SPA HCF600 COMPLETE - SUMMARY REPORT:
OPERATION
STATUS
...........................................................................................................................................................................................................................................................
5 - 24

270-710-919R6.0
Monitoring USDS
-----------------------------SPA PROCESS INSTALLATION:

-----------------------SUCCEEDED
0
0
...........................................................................................................................................................................
Restore the SPA to service by typing the following command:

<RST: SPA=<USDS_HCF or USDS_HDF>;
Example: RST: SPA=HCF600;

Result: A message similar to the following is displayed:
M RST SPA HCF600 COMPLETED SUCCESSFULLY
Note: After the execution, the SPA is brought to OOS state. When the
SPA is sure it is capable of receiving traffic again, it will set its state to
IS automatically.
...........................................................................................................................................................................
Verify the SPA state by typing the following command:


Result: The SPA state should be IS (in service), as indicated by a
message similar to the following.

SPA NAME: HCF600
SPA STATE: IS
...........................................................................................................................................................................
10
Monitor the SPA to see if the alarm recurs. If the alarm recurs or you
cannot successfully restart the SPA, perform additional corrective
actions as recommended by the Lucent Technologies support staff.
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 25
Monitoring USDS

............................................................................................................................................................................................................................................................
Overview
When USDS SPAs run on MAS, they can generate errors and event
messages through the MAS OA&M interfaces. These errors and event
messages are intended for use during problem analysis.
Error and event messages are stored in the MAS log files.
Error messages
Error messages can be generated as a result of problems such as SPA,

system, data errors, and invalid user input. These error messages often
reflect transient circumstances and are usually disregarded unless they
occur in huge numbers. Since error messages relate to software
operations, they are generally not meaningful to the USDS users.
Event messages
An event is something that occurs within a system. An event does not

necessarily indicate a problem, but is an indication of events. Event
messages can be indicators for a healthy system operation. However,
event can also indicate problems. Examples of event messages that can
indicate problems include:
Notification of an undesired response to the USDS request.
Notification that a MAS timer expired before it could respond to

an USDS request.
USDS R6.0 uses brevity control feature supported by MAS platform to

reduce the likelihood of queue overload and loss of other message or
impact to other system functions. You can set the thresholds for the
specific OM logs, but there is a limit on the maximum number of
message-specific brevity control. One can only set:bcntl to the
maximum number of process-message-specific OMs. For the details of
command set:bcntl, refer to MAS User Reference Guide (270-700-176).
You may notice USDS event messages when you review the alarm or
overload messages in the following log files:
/sn/log/OMlog0
/sn/log/OMlog1
For more information on each event message, refer to "USDS OM

logs" (B-1).
Note: For USDS troubleshooting, refer to Chapter 8: Using traps and
traces of MAS Service Administration Guide, 270-710-652.
...........................................................................................................................................................................................................................................................
5 - 26

270-710-919R6.0
Monitoring USDS

............................................................................................................................................................................................................................................................
Overview
Being a distributed system, USDS needs an overall overload control

strategy to remain stable and reliable. USDS monitors SS7 traffic/
DIAMETER related overload conditions to safeguard USDS operations
during periods of unusually high traffic or resource shortage.
During overload conditions, the USDS has three primary
responsibilities:
Maintain system integrity (do not crash).
Continue processing database queries/transactions at the required

rate.
Report the overload condition to the proper maintenance system/

center.
In USDS R6.0, overload control strategy is divided into two functions:

HDF overload control and HCF overload control. Both HDFs and
HCFs monitor overload status for incoming messages and throttle the
traffic when overload occurs.
Important! Once overload is identified, it should be recorded and
forwarded to administrative or engineering staff in accordance with
local practices.
Overload is determined in different ways for HCF nodes and HDF

nodes, as illustrated in Figure 5-6, "Determining overload for HCF
nodes and HDF nodes" (5-28):
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 27
Monitoring USDS
Figure 5-6
Determining overload for HCF nodes and HDF

nodes
HDF:
HDF determines its overload level by monitoring the occupancy

rate of its incoming HCF message queue and internal queue.
HDF chooses the maximum level (incoming message queue or

internal queue) as the HDF overload level.
HDF drops message based on DBCOM message priority and

current HDF overload level.
Corresponding alarms for HDF overload is issued to indicate the

overload state.
HDF overload level is sent to HCF via heartbeat.
HCF:
Index Server in HCF receives the overload level for each HDF
node via heartbeat, then route the DBCOM messages to the HDF
with lowest overload level.
...........................................................................................................................................................................................................................................................
5 - 28

270-710-919R6.0
Monitoring USDS
Index Server decides whether to drop the message based on the

DBCOM message priority and HDF overload level received.
PDLS Service Dispatcher (SD) in HCF implements overload

control for ANSI41, UMTS and IMS separately.
PDLS SD considers the following factors deciding the HCF

overload level:
USDS overload levels
PDLS queue overload level

SS7 system overload level
SSN overload level
DIAMETER overload level (HSS only)
On SPA level, USDS uses five overload levels, as shown in Table 5-1,
"Overload levels" (5-30). The following table only lists the default
values. Those values can be configured from eSM in table "Global
Parameter".
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 29
Monitoring USDS
Table 5-1
Overload levels
Level
Lower limit for each

level (default) (% of
full capacity)
Description
Under 60
Normal operating
condition, not an
overload state
60
Generates an
informational overload
message.
Information level
70
Generates a minor alarm

message.
Minor level
80
Generates a major alarm

message.
Major level
90
Generates a critical alarm

message.
Critical level
The percentage given in the table for an overload level is the lower
limit for the level. For instance, 79% is overload level 2 and 80% is
overload level 3.
HCF/HDF message queue
overload level
HCF and HDF message queue overload level have the same definition
as follows.
...........................................................................................................................................................................................................................................................
5 - 30

270-710-919R6.0
Monitoring USDS
Table 5-2
Message queue overload levels
Level
Lower limit for each level (% of full

capacity)
Under 60
60
70
80
90
Note: Queue occupancy values are averaged over a brief period of time
to avoid changing the overload status constantly because of momentary
changes in the message load.
SSN overload level of MAS
platform
The MAS platform provides SSN overload control for SPAs. HCFs will
use this information to determine the protocol-specific overload levels
(ANSI overload level, UMTS overload level and IMS overload level,
etc).
In RC/V form 1.3 - SPMAN SSN Resource Management Form, service
provider can define the maximum number of messages that are allowed
in the predefined time interval, as shown in Figure 5-7, "RC/V form
1.3" (5-32).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 31
Monitoring USDS
Figure 5-7
RC/V form 1.3
Table 5-3
Field description for RC/V form 1.3
Field
Description
SSN
Subsystem Number
SSN COMPUTE
INTERVAL
The time interval between calculating the

number of messages delayed. Default
value is 10 (seconds)
SSN MAX CALL LEVEL 0

~
The SSN overload level for MAS

platform, 8 levels in total.
MAS platform defines 8 levels for SSN overload control. A certain

algorithm will make it conform to the HCF overload level definition.
In configuring RC/V form 1.3, many factors must be taken into
consideration: hardware equipment, system configuration, protocol
supported and the traffic requirement. Lucent field engineers provide
support to calculate and test the actual config value. The following is
just an example with assumptions:
...........................................................................................................................................................................................................................................................
5 - 32

270-710-919R6.0
Monitoring USDS
Suppose in an ANSI network, only SSN 6 and SSN 10 are configured.

The average traffic is 2200TPS with the CPU utility is 75%, among
which 65% of total traffic goes to SSN 6 and 35% goes to SSN 10. If
we choose the lab-based 150% average traffic (that is 3300TPS) as the
max, then the values for RC/V form 3.1 can be provisioned like this:
SS7 system overload level

of MAS platform
SSN
10
SSN COMPUTE INTERVAL
10
10
200
100
400
200
600
300
800
400
1000
500
1200
600
1400
700
1600
800
System overload is the overload level across platforms (including all

SSN traffic). When system overload occurs, the system overload level
is passed to the USDS application, where it is used to determine the
HCF overload level.
MAS platform defines 15 levels for system overload control. A certain
algorithm will make it conform to the HCF overload level definition
with the consideration that SS7 system overload, which are usually
resulted from S7SCH message queue overload, weighs on the USDS
overload.
DIAMETER overload level

of MAS platform (HSS only)
DIAMETER overload control, which consists of Cx overload level and

Sh overload level, is provided by MAS platform. When DIAMETER
overload occurs, it is passed to the USDS application, where it is used
to determine the HCF overload level.
MAS platform defines eight levels for DIAMETER overload control. A
certain algorithm will make it conform to the HCF overload level
definition.
Overload strategy on HDF

nodes
HDF monitors the incoming message queue and the internal queue for
overload level. Then, it uses the max ones as HDF overload level.
When in an overload status, HDF compares the HDF overload level
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 33
Monitoring USDS
with message priority and decides if message should be dropped. On

the other hand, HDF overload level is sent to HCFs with heartbeat,
there it is used by Index Server to determine whether to discard
DBCOM messages with certain priority.
Overload strategy on HCF
nodes
There are two components that handle overload control in HCF: Index
Server and PDLS SD.
Index Server receives the HDF overload level from heartbeat.

Then it compares HDF overload level with message priority to
decide whether to forward the message to HDF or to return as
error. Index Server also has the responsibility to select the node
with lower overload level in HDF pair for HDF query access.
To determine the overload levels per protocol, PDLS SD uses

platform-provided SS7 system overload, SSN overload,
DIAMETER overload and SPA provided HCF message queue
overload level to calculate the value.
For ANSI/UMTS HCF overload level, the ultimate overload level are
the max ones of PDLS queue overload level, SS7 system overload level
and SSN overload level.
Note: Taking UMTS HCF overload level as example, overload levels
with SSN value equals to 6 and 10 should be considered.
For HSS HCF overload level, the ultimate overload level are the max
ones of PDLS queue overload level, SSN overload level and
DIAMETER overload level.
SD compares the message priority with decided HCF overload level. If
message overload level is greater than SSN overload level, the message
is processed, otherwise, it is returned as an error.
Table 5-4
Actions corresponding to overload levels on HCF

nodes
Level

level (default)
Actions at HCF
node
Under 60
All messages are

processed.
60
All messages are

processed.
2 (minor alarm)
70
Messages set to
priority 2 or lower are
filtered out and will not
be processed.
...........................................................................................................................................................................................................................................................
5 - 34

270-710-919R6.0
Monitoring USDS
Table 5-4
Overload alarms and

output messages
Actions corresponding to overload levels on HCF

nodes
Level

level (default)
Actions at HCF
node
3 (major alarm)
80
Messages set to
be processed.
4 (critical alarm)
90
Messages set to
be processed.
Overload can trigger alarms in MAS nodes and OMC-H. The alarm
related to overload is:
Alarming object
applOverloadLevel
Alarming type
Probable cause
congestion
Severity alarms

Additional text
USDS-HLR application overload level

Overload messages are stored in /sn/log/OMlog0 and /sn/log/OMlog1

on MAS nodes.
Table 5-5, "Examples of overload messages" (5-36), lists some
examples of overload messages. For more information, refer to
Appendix B, "USDS OM logs".
...........................................................................................................................................................................................................................................................
270-710-919R6.0

5 - 35
Monitoring USDS
Table 5-5
Examples of overload messages
Message text
Indication
HDF OVLD INCREASED

FROM <old_num> TO
<new_num>
The overload level increased.
Where: <old_num> and

<new_num> are single-digit
numeric values from 0 to 4.
HDF OVLD ABATED
FROM <old_num> TO
<new_num>
The overload level decreased.
Where: <old_num> and

<new_num> are single-digit
numeric values from 0 to 4.
...........................................................................................................................................................................................................................................................
5 - 36

270-710-919R6.0
Overview
............................................................................................................................................................................................................................................................
Purpose
Contents
This chapter explains how to monitor the SS7 links and SS7 link status
with DAPs.
SS7 links
6-2
Monitor SS7 DAPs
6-3
............................................................................................................................................................................................................................................................
270-710-919R6.0

6 - 1
SS7 links
SS7 links
............................................................................................................................................................................................................................................................
Overview
USDS HCF nodes are connected to other network entities via SS7
links. The SS7 links transport all messages between the USDS and the
external system(s) that it serves.
SS7 connectivity and OA&M capabilities are provided by the MAS
platform. The purpose of this topic is to introduce how to monitor the
status of SS7 link. For more information on SS7 link OA&M, refer to
the MAS User Reference Guide (270-700-176).
MAS documentation refers to SS7 links using terms
such as LSs (link sets), LKs (links), SLKs (SS7 links), and LINK
(link).
Important!
The MAS supports SS7 link monitoring by providing:
Monitoring SS7 Links in

USDS
DAPs that indicate
Status for the circuit boards that provide electrical and

physical connections for SS7 links
Status for the SS7 links associated with the circuit boards
SS7 overload status
SS7 process status
SS7 port details
Input messages in the form of command line and DAP "poke"

commands
Output messages generated as the result of input messages
OMlog0/OMlog1 message history
To monitor SS7 link in USDS, you need to:
Have LMT windows open to all target HCF nodes to monitor SS7
links with DAPs.
Input SS7 maintenance messages on one or more HCF nodes,

depending upon the task.
Review the OMlog files on all target HCF nodes to get a snapshot
of SS7-related output messages.
...........................................................................................................................................................................................................................................................
6 - 2

270-710-919R6.0
Monitor SS7 DAPs
Procedure: Monitor SS7 DAPs

............................................................................................................................................................................................................................................................
Purpose
Use this procedure to monitor SS7 link status with DAPs.

Only HCF nodes are connected to the external system
with SS7 links.
Important!
Before you begin
You must have access to all HCF LMTs to perform this procedure.
This procedure is a high-level pointer to MAS
capabilities that are documented in the MAS System Administration
Guide (270-700-167) and MAS User Reference Guide (270-700176).
Important!
Monitoring SS7 DAPs
Perform the following steps to monitor SS7 links.

...........................................................................................................................................................................
Access the LMTs as required and open the DAP windows to each of the
HCF nodes you want to monitor.
Result: DAP page 100, Main Menu is displayed in each window.
You can monitor overall status of SS7 from the Main Menu page.
SS7 alarms are displayed on the summary bar at the top of the page.
...........................................................................................................................................................................
View other DAPs as required to obtain more information about SS7

links.
To...
View DAP
Obtain information on the

status of the SS7 SCH Status.
Figure 6-2, "107 - SS7 System status"

(6-5)
Obtain the status of all local

boards on the machine.
Figure 6-3, "107XX - SS7 local boards"

(6-5)
XX: NODE ID
Obtain the detailed status of a

specific MTP2E1/MTP2T1
configured link.
Figure 6-4, "107XXY - MTP2E1/

MTP2T1 links" (6-6)
XX: NODE ID
Y: BOARD
...........................................................................................................................................................................................................................................................
270-710-919R6.0

6 - 3
Monitor SS7 DAPs
Figure 6-1
DAP main window
...........................................................................................................................................................................................................................................................
6 - 4

270-710-919R6.0
Monitor SS7 DAPs
Figure 6-2
107 - SS7 System status
Figure 6-3
107XX - SS7 local boards
...........................................................................................................................................................................................................................................................
270-710-919R6.0

6 - 5
Monitor SS7 DAPs
Figure 6-4
107XXY - MTP2E1/MTP2T1 links
...........................................................................................................................................................................
(Optional) Close windows and exit the LMT.

END OF STEPS
...........................................................................................................................................................................
Related information
For specific information on Using Display Action Pages, refer to the

MAS System Administration Guide (270-700-167).
...........................................................................................................................................................................................................................................................
6 - 6

270-710-919R6.0
Overview
............................................................................................................................................................................................................................................................
Purpose
This chapter introduces the background information for the service

measurements of USDS.
This module only covers measurements that are
generated by the USDS HCF SPAs and the HDF SPAs. For
platform-related measurements, refer to the MAS Maintenance
Guide (270-700-169).
Important!
Contents

7-2
7-5
7-9
7-11
Modify measurements polling on eSM
7-12
Create USDS measurement reports on eSM
7-15
............................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 1

............................................................................................................................................................................................................................................................
Overview
The MAS platform and the USDS SPAs peg and store counts of their
activities which are collected by the MAS at regular intervals.
You can use the MAS platform and service measurements to analyze
MAS and USDS behavior and troubleshoot problems.
Measurements are collected by MAS platform, reported in log files,
stored in the platform database or as a file. They can be deleted by the
platform, or by the remote collector.
There are three types of MAS measurements:
Platform measurements - platform resource usage and platform

process measurements
Service measurements - from the SPAs
Subscriber measurements - per SPA subscriber measurements
In USDS R6.0 HCF and HDF SPAs, only service measurements are
defined. There is no subscriber measurement currently.
Service measurements are defined in the SPA code through the
Enhanced Services Authoring Environment (eSAE: A Lucent
Technologies structured work environment that consists of graphic
workstations, programs, compilers, and tools for designing,
developing, and testing new services that execute on a platform. The
eSAE is an advanced application development environment) tools.
Measurement definition files are delivered as part of the SPA tar file
created on the eSAE.
Service measurements are stored in the platform database.
Service measurement reports can be generated after the measurements
have been collected.
Examples of USDS measurements are as follows:
Successful MAP-related requests and responses per supported

MAP operation
Unsuccessful MAP-related requests and responses per supported

MAP operation
MAP error responses, per supported MAP operation
Successful authentication-related requests and responses
...........................................................................................................................................................................................................................................................
7 - 2

270-710-919R6.0
Logging
Collection intervals
Unsuccessful authentication-related requests and responses.
The measurement count report is logged in /sn/log/measlog0 and

/sn/log/measlog1 on each MAS. When one log file is filled up, the log
is written to the paired log file, in which existing data is overwritten.
Each MAS collection interval is configurable to:
5 minutes
15 minutes (default MAS setting, expressed as 900 seconds)
30 minutes
One hour
One day
Note: Refer to detail configuration in RC/V form 2.4, in which the

listed intervals above are represented as TRFC5, TRFC15, TRFC30,
PLNTHR and PLNT24 separately.
Reports
Each HCF node and HDF node provides scheduled application

summary measurement reports that include:
Generating entity (specific USDS component's unique identity)
Local reporting time
Start time
End time
File name with date and time included in its name
Reason for specific count.
This information precedes the measurement log each time the interval
log is retrieved by the eSM.
USDS provides three ways to view the measurement reports:
View on MAS by opening measlog0/measlog1 files from a UNIX

window.
View on MAS using op:meas command
For more information about using the op:meas command, see

Chapter 23 OP input messages of MAS User Reference
Guide, 270-700-176.
View measurement report from the eSM.
Note: For service measurements to work, a Service Object

must be defined on the eSM for the HCF service.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 3
For more information on using the eSM Report capability,

refer to the eSM GUI online user assistance and the
following sections.
...........................................................................................................................................................................................................................................................
7 - 4

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview
Both the MAS platform and USDS SPA provide methods to enable and
disable the service measurement pegging.
The MAS platform controls the pegging of measurement via

RC/V Form 2.4 MEASUREMENT INTERVAL FORM.
Table 7-1, "Field descriptions for form 2.4" (7-6) lists the fields in
this form
...........................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 5
Table 7-1
Field descriptions for form 2.4
Field
Description
MEASUREMENT TABLE
NAME
Identifies the name of the measurement

table. For the table names supported by
the USDS, refer to Appendix A, "USDS
service measurements" of this book.
COLLECTING PROCESS
Identifies the platform process or SPA

process that collects the associated
measurement table.
Note: For HDF SPA, the process is
HDF600.
Note: For HCF SPA, the processes can
be HCF600, PDLSAx, PDLSUx,
PDLSIx, PDLSGx, PDLSM1 and CIF (x
represents 1 to 3. It depends on the actual
deployment also).
COLLECTION INTERVAL
Identifies the time interval between data

collections. Changing this parameter
redefines how frequently a particular
measurement table is collected.
REPORT FILE
Identifies the name of the formatting file.

The UNIX file that is named in this field
is run to report the measurements in this
file.
GENERATE FILE
Defines whether data of the measurement

table will be stored in the flat files under
the directory /sysdata1/meas_files.
INHIBITED
Defines whether a measurement interval

can be specified and stored.
To disable the measurement pegging to the database, set the

"INHIBITED" field to "Y" for specific measurement table.
Note: If you want to enable/disable the measurement pegging for a
specific measurement table, you need to "inhibit" all the records in RC/
V Form 2.4 related to that measurement table.
Important! The modification to form 2.4 only applies to the
specific MAS node. It does not apply to the whole USDS complex.
...........................................................................................................................................................................................................................................................
7 - 6

270-710-919R6.0
The USDS SPA also provides method to turn on/ turn off the
pegging of per-NE measurement. Service provider can provision
the "ANSI Global" table (for ANSI protocol) or "HLR SYS" table
(for UMTS protocol) via eSM to manage the measurement
collections, as shown in Table 7-2, "Measurement control fields in
"ANSI Global" for ANSI protocol" (7-7) and Table 7-3,
"Measurement control fields in "HLR SYS" for UMTS protocol"
(7-7).
Table 7-2
Measurement control fields in "ANSI Global" for

ANSI protocol
Fields
Description
NE1 MSCID
~
NE50 MSCID
The MSCID of the network elements for

which the USDS will collect
measurements.
NE1 Meas Allowed

~
NE50 Meas Allowed
Measurement collection flag.
Table 7-3
If set to yes, USDS will support a system

level measurement count pegging table
for the corresponding Network Element
during call processing.
Measurement control fields in "HLR SYS" for UMTS

protocol
Fields
Description
NE Global Title 1
~
NE Global Title 50
The Global Title of the network elements

for which the USDS will collect
measurements.
NE Meas Allowed 1
~
NE Meas Allowed 50
Measurement collection flag.

If set to yes, USDS will support a system
level measurement count pegging table
for the corresponding Network Element
during call processing.
To enable the collection of per NE measurement, set the field "NEx

Meas Allowed" (for ANSI) or "NE Meas Allowed x" (for UMTS) to
"Y". As the eSM can distribute the request to multiple nodes in the
USDS complex, it is a centralized method to control the service
measurements.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 7
Important! This method only applies to HCF per NE

measurement and not global measurement tables. The actual effect
of the provisioning depends on the NEs included in the NE group
that this Service Object applies to.
...........................................................................................................................................................................................................................................................
7 - 8

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview
This feature captures the measurements of the transactions (a

transaction is defined as an incoming/outgoing SS7 message and its
associated response/acknowledgement) sent from the HCF to the HDF.
This internal message mix is useful for troubleshooting and future
traffic forecasting.
In the USDS complex, every HCF node captures protocol specific
measurement counts locally for a pre-defined time interval. This
information must be collected for every HDF node separately on a per
message basis. Once the time interval elapses, this measurements log
data is transferred to respective HDF nodes for further processing. In
effect, every HCF node would send the measurement data to every
HDF node in the same USDS complex. Once HDF node receives this
information from every HCF node, it adds the respective measurement
counts and stores the aggregated measurement counts in a log file on
disk and PostgreSQL database.
Note: For the detailed measurements supported by this feature, refer to
Appendix A, "USDS service measurements" of this book.
Configure the HDF

measurements
Table 7-4, "Related RTU(s)" (7-9) lists the feature locks (RTUs) that
are related to this feature. To enable this feature, the related RTU must
be unlocked.
Table 7-4
Related RTU(s)
RTU name
RTU description
ANSI41
RTU for the ANSI-41 protocol.
UMTS
RTU for supporting the UMTS protocol
HSS
RTU for Home Subscriber Server (HSS)

services
Table 7-5, "Data in "Global Parameter" for HDF measurements" (7-10)

contains the global configuration of for this feature. To enable this
feature, the data listed in this table must be provisioned properly from
the eSM.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 9

Table 7-5
OMlog related to this

feature
Data in "Global Parameter" for HDF measurements
Attribute name
Description
Meas_Flag_ANSI
Indicates if ANSI-41 traffic analysis

measurements are activated on the
USDS. Select "true" for this field to
enable this feature.
HCF_Meas_Interval
The interval at which measurement

would be sent to HDF nodes from the
HCF nodes. It is suggested that this value
is less than the field "COLLECTION
INTERVAL" of RC/V form 2.4.
Meas_Flag_UMTS
Indicates if GSM/UMTS traffic analysis

Meas_Flag_HSS
Indicates if HSS traffic analysis

Every HCF node tracks the traffic measurement counters on per HDF
node basis for an interval as specified by field "HCF Meas Interval".
Once this measurement interval expires, every HCF node sends those
traffic measurement counters to every HDF node that it communicated
with during that measurement interval. The HCF node retains a copy of
those traffic measurement counts in its own log file on disk as well. By
default, the log file for the measurements gathered by the HCF nodes is
stored in /sn/log/apmeaslog. The service provider can redirect this log
file to other directories. For detailed steps to redirect the log files, refer
to section "Redirect Omlogs" (4-35).
There are also regular Omlogs to record the error during the sending
and receiving of measurements counts between the HCF and the HDF.
For detailed information of the Omlogs, refer to Appendix B, "USDS
OM logs".
...........................................................................................................................................................................................................................................................
7 - 10

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview
eSM measurement
aggregation
The eSM provides the capability to poll the measurements data from
MAS and create reports for the collected data.
For USDS R6.0, the MAS service-related measurements are collected
periodically by the eSM-initiated polling.
The eSM reporting capability aggregates the collected service
measurement data at the SPA level (HCF or HDF).
For more information on the MAS measurements for HCF SPAs and
HDF SPAs, refer to Appendix A, "USDS service measurements".
eSM measurement data

reports
The eSM provides the capability to create, display, and delete USDS
service measurement data reports. You can create reports for:
HCF service measurements data
HDF service measurements data.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 11
Procedure: Modify measurements polling on eSM

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to modify the eSM's measurement data polling

interval.
Ensure that you have login permission on eSM.
Important! This high-level procedure is not intended to replace
the eSM documentation. You may need the eSM documentation to
complete the detailed steps not provided in this procedure.
Steps
Complete the following steps to modify the eSM polling interval for a
measurement set.
...........................................................................................................................................................................
Log on to the eSM GUI and click Continue.

...........................................................................................................................................................................
Select the Services Administration.

Result: The Services Administration page is displayed, as shown
in Figure 7-1, "The Service Administration page" (7-13).
...........................................................................................................................................................................................................................................................
7 - 12

270-710-919R6.0
Figure 7-1
The Service Administration page
...........................................................................................................................................................................
At the Services Administration page, click Measurement Sets.

Result: The Measurement Sets page is displayed, as shown in
Figure 7-2, "The Measurements Sets page" (7-13).

Figure 7-2
The Measurements Sets page
...........................................................................................................................................................................
At the Measurement Sets page, in the Set Name column, select the
measurement set for which you want to modify the polling interval.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 13
Result: The Measurement Set details page is displayed, as shown
in Figure 7-3, "The Measurement Set detail Page" (7-14).

Figure 7-3
The Measurement Set detail Page
...........................................................................................................................................................................
At the Measurement Sets detail page, enter the desired polling interval
in the Polling Interval box.
Hint: The value of polling interval in the Polling Interval box must be
any multiple of SCP Collection Interval.
...........................................................................................................................................................................
Click Submit to make the measurement set polling interval take effect.
Result: The polling interval change is submitted.
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
7 - 14

270-710-919R6.0
Procedure: Create USDS measurement reports on eSM

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to generate and view USDS service measurements

data stored on the eSM in a report.
Ensure that you have the related permission for this task on the eSM.
Important! This high-level procedure is not intended to replace
eSM documentation. You may need the eSM documentation to
Steps
Perform the following steps to generate and view an USDS service

measurement data report.
...........................................................................................................................................................................
Log on to eSM GUI and click Continue.

...........................................................................................................................................................................
Click Service Tools.

Result: The Service Tools page is displayed, as shown in
Figure 7-4, "The Service Tools page" (7-16).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 15

Figure 7-4
The Service Tools page
...........................................................................................................................................................................
At the eSM service tools page, click Reports.

Result: The Reports page is displayed, as shown in Figure 7-5,
"The Reports page" (7-17).
...........................................................................................................................................................................................................................................................
7 - 16

270-710-919R6.0

Figure 7-5
The Reports page
...........................................................................................................................................................................
Select the Reports Menu icon and choose Measurement Reports and
then Service Measurements from the drop-down list.
Result: The Measurement Report page is displayed, as shown in
Figure 7-6, "The Measurement Report page" (7-17).

Figure 7-6
The Measurement Report page
...........................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 17
...........................................................................................................................................................................
Select the service (HCF-Standard, Version 600), set associated report

parameters, and select Submit.
Hint: "Selected Measurement Sets" option allows only the designated
measurement sets to be reported.
Hint: "Absolute" or "Relative" option will prompt you two methods to
indicate the time range.
Hint: Select the "Format: Formatted" option to receive a more
readable report. Select "Format: Plain Text" option to receive an
abbreviated report.
Result: The Report Status page is displayed, as shown in Figure 7-7,
"The Report Status page" (7-18).
Figure 7-7
The Report Status page
...........................................................................................................................................................................
Click Refresh in your browser window periodically to monitor report

status. When you observe Status: Complete, view the report by
selecting the link or icon next to the status indicator.
...........................................................................................................................................................................................................................................................
7 - 18

270-710-919R6.0
Result: The report is displayed in a new window. Following is an

example with the "Format" option set to "Formatted":
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

7 - 19
...........................................................................................................................................................................................................................................................
7 - 20

270-710-919R6.0
Custom report
Overview
............................................................................................................................................................................................................................................................
Purpose
Custom reports are made available to eSM users during service

installation. Currently, there are two kinds of custom reports in USDS
service: CALEA service report and WPS service report.
This chapter introduces custom reports in the USDS.
Contents

8-2
WPS service report
8-3
Generate custom report on eSM
8-4
............................................................................................................................................................................................................................................................
270-710-919R6.0

8 - 1
Custom report

............................................................................................................................................................................................................................................................
Overview
CALEA users can run CALEA service report to detect any mismatch in
the CALEA data.
The CALEA service report outputs all CALEA targets (MSID) if one
of the following mismatches is encountered:
All records in CALEA table whose GTRACEON flag in

COMMONPHONE table are FALSE.
All records in CALEA table, whose IMSI and MIN are NOT in
COMMONPHONE table.
All records are marked for CALEA in COMMON PHONE, whose

IMSI and MIN are NOT in CALEA table.
All records in CALEA table whose Target_Type marked 'BOTH

IMSI and MIN', but IMSI and DF_IPaddr are not in CALEA_eSM
table.
All records in CALEA table whose Target_Type marked 'BOTH

IMSI and MIN', but MIN and DF_IPaddr are not in CALEA_eSM
table.
All records in CALEA table whose Target_Type marked 'MIN

ONLY', but the IMSI and DF_IPaddr EXIST in CALEA_eSM
table.
All records in CALEA table whose Target_Type marked 'MIN

ONLY', but the MIN and DF_IPaddr are NOT in CALEA_eSM
table.
All records in CALEA table whose Target_Type marked 'IMSI

ONLY', but the MIN and DF_IPaddr EXIST in CALEA_eSM
table.
All records in CALEA table whose Target_Type marked 'IMSI

ONLY', but the IMSI and DF_IPaddr are NOT in CALEA_eSM
table.
Note:
1.
2.
The report is to inform the craft personnel that there is a mismatch

in the CALEA data. The report is informative only, and a manual
corrective action is necessary to keep the CALEA data in sync.
The eSM does not delete any CALEA data on its own.
The report can only be viewed via the CALEA login/password.
...........................................................................................................................................................................................................................................................
8 - 2

270-710-919R6.0
WPS service report
Custom report
WPS service report

............................................................................................................................................................................................................................................................
Service Providers are able to generate reports from the eSM containing
the following information:
Number of WPS subscribers assigned a specific priority level in

the range 0 through 5
Number of WPS subscribers assigned in a range of priority levels,

e.g., 2 through 4
Number of WPS subscribers assigned for a discrete list of priority

levels, e.g., 1, 3, 5.
List of WPS subscribers including MIN / IMSI and MDN and

their priority, for a specific priority level
List of WPS subscribers including MIN / IMSI and MDN and

their priority, for all priority levels.
Note: This reporting capability is allowed only for users with read
access or read and update access to WPS subscriber data.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

8 - 3
Custom report
Procedure: Generate custom report on eSM

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to generate custom report on the eSM.

Ensure that you have the related permission for this task on the eSM.
Important!
Note: Take WPS service report as an example in the following

steps.
Steps
...........................................................................................................................................................................
Log on to eSM GUI and click Continue.

Result: The eSM launch page is displayed, as shown in Figure 8-1,
"The eSM launch page" (8-4)

Figure 8-1
The eSM launch page
...........................................................................................................................................................................................................................................................
8 - 4

270-710-919R6.0
Custom report
...........................................................................................................................................................................
Select Service Administration->Services.

Result: The Services page is displayed, as shown in Figure 8-2,
"The Services page" (8-5)

Figure 8-2
The Services page
...........................................................................................................................................................................
Select the Service Name HDF

Result: The HDF Service page is displayed, as shown in
Figure 8-3, "The HDF Service page" (8-6)
...........................................................................................................................................................................................................................................................
270-710-919R6.0

8 - 5
Custom report
Figure 8-3
The HDF Service page
...........................................................................................................................................................................
Click Custom Report

Result: The Custom Reports page is displayed, as shown in
Figure 8-4, "The Custom Reports page" (8-6)

Figure 8-4
The Custom Reports page
...........................................................................................................................................................................................................................................................
8 - 6

270-710-919R6.0
Custom report
...........................................................................................................................................................................
Select the Service (HDF-WPS-Subscriber, Version 600 or HDFWPS-Subscriber-ReadOnly, Version 600 for WPS service report;
HDF-CALEA, Version 600 for CALEA service report), and click the
star sign on the right side of the Custom Reports page.
Result: The Define Custom Report Parameters page is displayed,
as shown in Figure 8-5, "The Define Custom Report Parameters
page" (8-7)
Figure 8-5
The Define Custom Report Parameters page
...........................................................................................................................................................................
Choose the Format, Output, Execution Mode, and click Next to

continue.
Result: The Report page is displayed, as shown in Figure 8-6, "The
Report page" (8-8)

Note: CALEA service report does not have a Report page and will go
to the Custom Report Requested page directly.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

8 - 7
Custom report
Figure 8-6
The Report page
...........................................................................................................................................................................
Enter the WPS Priority Level (specific priority levels in the range 0
through 5 separated by commas, e.g.,1,3,5 or a range of priority levels,
e.g., 2-5), and click Next to continue.
Result: The Custom Report Requested page is displayed, as
shown in Figure 8-7, "The Custom Report Requested page" (8-9)
...........................................................................................................................................................................................................................................................
8 - 8

270-710-919R6.0
Custom report
Figure 8-7
The Custom Report Requested page
...........................................................................................................................................................................
Click Go to this Custom Report icon.

Result: The Custom Report page is displayed as shown in
Figure 8-8, "The Custom Report page" (8-10). Refresh the page
until the Status changes to Complete.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

8 - 9
Custom report
Figure 8-8
The Custom Report page
...........................................................................................................................................................................
Click Status icon.

Result: The Report Order page is displayed in a new window as
shown in Figure 8-9, "The Report Order page of WPS service

report" (8-11). Following is an example with the "Format" option
set to "Plain Text":
...........................................................................................................................................................................................................................................................
8 - 10

270-710-919R6.0
Custom report
Figure 8-9
The Report Order page of WPS service report
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

8 - 11
Custom report
...........................................................................................................................................................................................................................................................
8 - 12

270-710-919R6.0
Using CALEA
Overview
............................................................................................................................................................................................................................................................
Purpose
Contents
This chapter introduces how to use CALEA in the USDS.

CALEA introduction
9-2
Assign Form Permissions to Restricted RC/V Logins for

CALEA
9-4
Verify LTDU connection with USDS from eSM
9-7
Configure IPSec keys between USDS and LTDU
9-9
Configure IPSec policies between USDS and LTDU
9-13
Remove IPSec connection between USDS and LTDU
9-18
............................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 1
CALEA introduction
Using CALEA
CALEA introduction
............................................................................................................................................................................................................................................................
Overview
The CALEA is a U.S. statute that requires telecommunications vendors

to meet all the requirements in the TIA/EIA Standards J-STD-025. The
following types of information are provided to law enforcement
agencies:
Call content: the content of both parties of the target's voice calls
and/or data calls is transmitted over a Call Content Channel
(CCC).
Call-identifying information: call events that occur during the

processing of a call are transmitted over Call Data Channels.
These messages provide information to the Law Enforcement
Agency (LEA) about the target's location, number dialed, calling
party, redirecting number, and so on.
CALEA provides lawful surveillance of targets (mobile users) in the

telecommunication network under court control. Its function can be
divided into five functional components:
Access Function
Delivery Function
Collection Function
Service Provider Administration Function
Law Enforcement Administration Function.
When the USDS is equipped with the CALEA capability, it supports

the Access Function. For a given and provisioned CALEA target, the
USDS sends call identifying information to the Delivery Function.
Call-identifying information is formatted into discrete messages, called
CALEA messages. The information supplied by the USDS to the
separate Delivery Function equipment is further passed on to the
Collection Function. In turn, the Collection Function allows the Law
Enforcement Authorities to use this information and/or with a
combination of other appropriate call-content related information
collected from other network nodes, like SGSN/GGSN and/or MSC/
VLR.
The USDS interfaces with the Delivery Function over "d" interface. It
is Call Data Channels (CDCs) over TCP/IP.
...........................................................................................................................................................................................................................................................
9 - 2

270-710-919R6.0
CALEA introduction
Using CALEA
The eSM equips service provider with the CALEA data provisioning
capabilities under secure mode. The function of the provisioning
interface is to insert, delete and read the CALEA data associated with
the targeted mobile subscribers.
When a subscriber is provisioned with CALEA data, the subscriber is
marked as a CALEA target in the USDS subscriber profile.
As events occur for a wireless subscriber, if the subscriber profile
indicates the subscriber is the CALEA target, the USDS query the
CALEA database for the IP Address and Port Number and
Memorandum tuples associated with the target MSID. The HLR
application sends call-identifying messages to every Delivery Function
indicated by the CALEA database.
The USDS allows up to 20,000 CALEA targets to be provisioned and
simultaneously active.
CALEA data can only be provisioned from eSM with
the customer view named HDF-CALEA. Service provider must
ensure that only authorized user can access this view.
Important!
To configure the connection between USDS and

Lucent Technologies Delivery Units (LTDUs), refer to related
document (comcode 109561092) for the detailed configuration
procedure. Ensure that in file $SMSHOME/smsapp/config/
LtduConfig.xml on eSM, the field "viewName" is "HDF-CALEA",
and the field "versionName" matches that of the installed HDF
service.
Important!
For the input message related to this feature, refer to "CALEA delivery
function connection test" (4-25).
For the OMlog related to this feature, refer to "HCF service
measurement sets - CALEA" (A-94).
For the RTU and data need to be provisioned, refer to Provision
protocol independent features, Unified Subscriber Data Server (USDS)
R6.0. Data Provisioning Guide - Common (270-710-920R6.0)
...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 3
Assign Form Permissions to Restricted RC/V

Logins for CALEA
Using CALEA
Procedure: Assign Form Permissions to Restricted RC/V Logins for

CALEA
............................................................................................................................................................................................................................................................
Purpose
Specially, restricted logins are required on the USDS to limit access to

CALEA data. Perform this procedure when you want to apply form
access permissions to CALEA user.
Note:
Before you begin
Restricted logins are prohibited from RC/V forms access by

default. Access permissions must be explicitly assigned for each
form and login user.
For restricted login for CALEA, there is a special shell /sn/cr/

calea_sh provided by MAS, by default.
The name of the restricted login user
The names of the form interface files
The type(s) of access to be assigned
Steps
...........................................................................................................................................................................
Log on to the HDF node as root.

...........................................................................................................................................................................
Go to the directory /sn/cr/ and verify whether the file "calea_sh" exists.
If not, the script must be created with the following lines as its contents:
TERM=
while [ -z "${TERM}" ]
do
echo "TERM=\c"
read TERM
done
export TERM
exec /sn/cr/smssh -i /sn/imdb/CALEAlmt
exit 0
...........................................................................................................................................................................
Change the permissions mode of the shell file "calea_sh".

> chmod 755 calea_sh
...........................................................................................................................................................................................................................................................
9 - 4

270-710-919R6.0

Logins for CALEA
Using CALEA
...........................................................................................................................................................................
Create a standard UNIX login user for CALEA.

Note: By default, the MAS system has a build-in user "caleausr" for
CALEA.
Example: Use the following commands to create a login user:
> useradd -d /sn -s /sn/cr/calea_sh caleausr
> passwd caleausr
...........................................................................................................................................................................
(Optional) if the new login user already exists, modify the file /etc/
passwd to link the existed user to the shell file "calea_sh".
Example: Modify the line as follows:
existed_caleausr:x:31034:1::/sn:/sn/cr/calea_sh
...........................................................................................................................................................................
Go to the directory /sn/sps/HDF600/datamodel/ODIN/ and locate the

form interface files for editing.
Note:
For USDS configuration without eSM, the following form

interface files should be modified:
HDF_CALEA_DF.fi
HDF_GLOBAL_DATA1.fi
For USDS configuration equipped with eSM, only

"HDF_GLOBAL_DATA1.fi" should be modified.
...........................................................................................................................................................................
Add access for a restricted login to file "HDF_GLOBAL_DATA1.fi":

Note: For table "HDF_GLOBAL_DATA1", the CALEA user has the
"review" and "update" permissions. No access permissions will be
granted to other users.
Example: The following lines will be added:
restricted_operations_for: caleausr review, update;

restricted_operations_for: all_others ;
...........................................................................................................................................................................
Save and exit the current form interface file.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 5

Logins for CALEA
Using CALEA
...........................................................................................................................................................................
If eSM is not equipped, add access for a restricted login to file

"HDF_CALEA_DF.fi":
Note: For table "HDF_CALEA_DF", the CALEA user has the
"review" permission only. No access permissions will be granted to
other users.
Example: The following lines will be added:
restricted_operations_for: caleausr review;

restricted_operations_for: all_others ;
...........................................................................................................................................................................
10
Save and exit the current form interface file.

...........................................................................................................................................................................
11
Log off and log on again using the restricted user to verify the result.
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
9 - 6

270-710-919R6.0
Using CALEA
Procedure: Verify LTDU connection with USDS from eSM

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to verify LTDU Connection with USDS.

Ensure that you have appropriate permissions on eSM.
Important!
Steps
...........................................................................................................................................................................
Log on to eSM with CALEA permissions.

...........................................................................................................................................................................
At the eSM GUI, click Commands.

Result: The eSM Commands page is displayed.
...........................................................................................................................................................................
Click the star sign above the table to create a new Command
Result: The Define the Command page is displayed.
...........................................................................................................................................................................
Set up the Commands parameters and click Finish. Refer to Table 9-1,
"Fields on the "Define the Command" page" (9-8).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 7

Table 9-1
Using CALEA
Fields on the "Define the Command" page
Field Name
Description
Service
This field must be HDF-CALEA,

Version 600. (Mandatory).
Category
This field must be SYSTEM DATA.

(Mandatory)
Command
Three commands are allowed
ANSICNNTSTWithIMSI
ANSICNNTSTWithMIN
UMTSCNNTSTWithIMSI
Select one of them according to your

requirement.
Priority
It is used to identify the priority of the

Command being created. (Mandatory)
Delete Method
Determines how the created Command

must be removed from eSM. (Mandatory)
IMSI
The IMSI that will be surveilled.

(Optional)
MIN
The MIN that will be surveilled.

(Optional)
DF_IP
IP address of delivery function.

(Mandatory)
DF_port
Port number of the delivery function.

(Mandatory)
MEMO
Comment field. (Optional)
HCF_ID
Determines the HCFs that will send

messages to LTDUs. (Optional)
Network Elements
This field determines the HDFs to which

eSM will send messages. (Mandatory)
Command Order Name
Name of the defined command order.
...........................................................................................................................................................................
Review the command result and log off from eSM.

END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
9 - 8

270-710-919R6.0
Using CALEA
Procedure: Configure IPSec keys between USDS and LTDU

............................................................................................................................................................................................................................................................
USDS supports secure communications with LTDU using IPSec

mechanism provided by MAS platform. LTDU performs the role of
Delivery Function via "d" interface. All call-identifying CALEA
messages are delivered from each HCF node to LTDU over secured
TCP/IP channels. Currently USDS uses IPSec keys and policies for
ESP (Encapsulating Security Payload) transport modes for secure
connections with LTDU.
Note: To configure IPSec connections between USDS and a single
LTDU, execute the steps in this procedure and Configure IPSec policies
between USDS and LTDU procedure. If more than one LTDU exists,
repeat the above procedures for each LTDU.
For updating IPSec keys, remove the old connections and then add new
ones with the new keys.
For more information on IPSec related commands, refer to Solaris
document on Sun website.
Purpose
Before you begin
Use this procedure to manually configure Security Associations (SA)

with keys for ESP secure transport IPsec modes of operation. Since
SAs are uni-directional, two SAs are needed for bi-directional support.
As a routine practice, this procedure should be run once a week to
refresh the key values. This is done to guard against potential
weaknesses of algorithm and keys, and limit the potential damage of an
exposed key.
Local system IP address (for example, HCF machines)
Local system encryption keys
Remote system IP address (for example, the LTDU)
Remote system encryption keys
Security Parameters Indices (SPIs)
Encryption algorithm
Keys are security sensitive and must only be shared
with the endpoint systems with access restricted to "root" account.
Handling and delivery of these keys requires attention to security. A
distinct key is required for each end point. These key values must
Important!
...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 9
Using CALEA
be generated as randomly as possible to make them difficult to

comprehend. The /usr/sbin/ipseckey tool rejects weak keys.
Key can be generated using the following command. The value for
"count" can be changed to generate the required bytes of keys. For
the following command, with "count=16", a 16 bytes key can be
generated. For more information on the following command, refer
to Solaris document on Sun website
dd if=/dev/random bs=1 count=16 | od -X
16+0 records in
16+0 records out
0000000 e79b3f8e 48a35b9e d46e8bee 1c0cf932
0000020
Table 9-2, "Algorithm key lengths" (9-10) provides the key value
lengths required for each algorithm.
Table 9-2
Algorithm key lengths
Algorithm
IPSec usage
Key value
length
MD51
Authentication Header (AH)
28 bits (16 bytes)
SHA-1
AH
160 bits (20

bytes)
DES
Encapsulation Security Payload

(ESP)
64 bits (8 bytes)
3DES
ESP
192 bits (24

bytes)
BLOWFISH
ESP
34 to 443 bits (5
to 56 bytes)
AES
ESP
128 bits (16

bytes)
Note: Current LTDU version only supports MD5, DES and 3DES
which will be used during configuration.
Steps
...........................................................................................................................................................................
Log on to UNIX console as root.
...........................................................................................................................................................................................................................................................
9 - 10

270-710-919R6.0
Using CALEA
Note that the console access is immune to IP configuration errors and

therefore provides a more reliable access during this procedure.
...........................................................................................................................................................................
At the UNIX prompt, set the TERM variable to match your terminal
emulator. For example:
TERM=vt100
...........................................................................................................................................................................
Save the current SA parameters to a backup file.

/usr/sbin/ipseckey -s /etc/inet/secret/ipseckeys.bak
...........................................................................................................................................................................
To manually update existing SA parameters, the SA must first be

deleted and then added with the desired parameters.
To delete an individual SA, execute the following command,

/usr/sbin/ipseckey delete SA_type spi Security_parameter_index dst
Dest_name
where:
SA_type is "esp" for Encapsulating Security Payload.
Security_parameter_index is the identifier number of the

individual SA as found in the /etc/inet/secret/ipseckeys.bak
file.
Dest_name is the destination host name of the SA.
To delete all SAs, execute the following command.

/usr/sbin/ipseckey flush
...........................................................................................................................................................................
To add one or more ESP transport mode policies, invoke the interactive
administrative environment, type the following commands for each
desired policy to add two SAs - one for each direction, and save the
parameters to the configuration file.
Multiple entries are needed for multi-homed systems - one for each
local / destination IP address supported combination.
Note: For more information on its usage, refer to the IPSeckey UNIX
manual page.
>/usr/sbin/ipseckey
...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 11
Using CALEA
> ipseckey> add esp spi Security_parameter_index_C src Remote_sys_name dst

Local_sys_name encralg ESP_alg encrkey Local_sys_encr_key
> ipseckey> add esp spi Security_parameter_index_D src Local_sys_name dst
Remote_sys_name encralg ESP_alg encrkey Remote_sys_encr_key
> ipseckey> save all /etc/inet/secret/ipseckeys
> ipseckey> quit
where:
ESP_alg is the encryption algorithm: DES or 3DES.
Security_parameter_index_C and Security_parameter_index_D

are unique identifiers for individual SAs used to communicate
between systems. The values are arbitrary but must match end-toend. Range is 1 to 4294967295.
For LTDU side, only 8 digits octets are supported for SPI:
Local_sys_encr_key and Remote_sys_encr_key are the local and

remote encryption keys represented in hexadecimal.
Local_sys_name is the network host name translation of the local

LEAD IP address from /etc/inet/hosts file. For the following
example, "SDHLR1" is the host name of interface ce0.
Remote_sys_name is the network host name translation of the

remote system IP address entry in the /etc/inet/hosts file. For the
following example, "LTDU1" is the hostname of the LTDU.
Example:
ipseckey> add esp spi 13574304src LTDU1 dst SDHLR1 encralg DES
encrkey AB34567890ABCDEF
ipseckey> add esp spi 16615400src SDHLR1 dst LTDU1 encralg DES
encrkey 432516958A44CD3D
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
9 - 12

270-710-919R6.0
Configure IPSec policies between USDS and

LTDU
Using CALEA
Procedure: Configure IPSec policies between USDS and LTDU

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to manually configure IPSec policies on the MAS to

enable ESP secure transport IPSec mode of operation for IP services.
This procedure is only required to insert IPSec policies.
Remote system name and IP address
ESP algorithm
Steps
...........................................................................................................................................................................
Log on to the UNIX console as root.

...........................................................................................................................................................................
TERM=vt100
...........................................................................................................................................................................
Using a text editor, edit the /etc/inet/hosts file to append the IP address
translation for the remote system. If multiple addresses are required, set
a separate entry and a locally unique name for each remote system IP
address.
Remote_sys_IP_addressRemote_sys_name
where:
Remote_sys_IP_address is the IP address associated with the

interface of the remote system in dotted-decimal notation. For
example, 10.2.123.12.
Remote_sys_name is the network host name of the remote system
Static IP address assignments are required. DNS

entries dependency is not supported since name service may not be
available during the system recovery phase that establishes IPSec
protocol.
Important!
...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 13

LTDU
Using CALEA
...........................................................................................................................................................................
At the LMT or subshl message prompt, enter an RC/V session by

typing the following command:
rcv:menu;
Result: The NETWORK PLATFORM MAIN MENU is displayed
as shown in Figure 9-1, "NETWORK PLATFORM MAIN MENU"

(9-14).
Figure 9-1
...........................................................................................................................................................................
Select option [2], OPERATIONS, ADMINISTRATION AND

MAINTENANCE SUBMENU is displayed as shown

in.Figure 9-2, "OPERATIONS, ADMINISTRATION AND
MAINTENANCE SUBMENU" (9-15)
...........................................................................................................................................................................................................................................................
9 - 14

270-710-919R6.0

LTDU
Figure 9-2
Using CALEA
OPERATIONS, ADMINISTRATION AND

MAINTENANCE SUBMENU
...........................................................................................................................................................................
Select option [17], IPSEC PARAMETERS FORM.

Result: Enter Database Operation
QD=QueryD :
...........................................................................................................................................................................
Type [I] and press Enter.

Result: The IPSEC PARAMETERS FORM is displayed as shown
in Figure 9-3, "IPSEC PARAMETERS FORM" (9-16).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 15

LTDU
Figure 9-3
Using CALEA
...........................................................................................................................................................................
Enter the appropriate values for the following parameters:
REMOTE HOST NAME: Type the name of the remote host as

entered in the /etc/hosts file in Step 3.
REMOTE PORT NUMBER: Type [0] as policy is applicable

irrespective of the remote port number.
Note: The LTDU does not support setting up the connection using
port number. Retain this field as [0].
LOCAL PORT NUMBER: Type [0] as policy is applicable
irrespective of the local port number.
Note: The LTDU does not support setting up the connection using
port number. Retain this field as [0].
AH AUTHENTICATION ALGORITHM: Type [NONE] as the
value for the Authentication Header algorithm.
Note: The LTDU does not support AH, so set the value of this
field to "NONE".
ESP ENCRYPTION ALGORITHM: Enter the Encapsulating
Security Payload encryption algorithm, DES, 3DES or NONE.
Note: Only DES and 3DES here can be used because LTDU only
supports these two encryption algorithms.
...........................................................................................................................................................................................................................................................
9 - 16

270-710-919R6.0

LTDU
Using CALEA
...........................................................................................................................................................................
Ensure the information entered is correct and type [i] and press Enter.
...........................................................................................................................................................................
10
Type [<] and press Enter to return.

...........................................................................................................................................................................
11
Type [!] and press Enter to log off from the RC/V menu.
...........................................................................................................................................................................
12
Restart HCF SPA, once the IPSec policy is changed, to avoid the
latched TCP/IP socket.
At the LMT or subshl message prompt, perform the following:
<rmv:spa=HCF600
Result: The result is displayed as follows:

RMV:SPA REMOVES NEW CALL TRAFFIC, CONTINUE Y OR N? (enter Y)
RMV SPA HCF600 COMPLETED SUCCESSFULLY
<DELETE:PROC,SPA=HCF600;

DELETE:SPA REMOVES SPA PROCESS, CONTINUE Y OR N? (enter Y)
DELETE PROC SPA HCF600 COMPLETED SUCCESSFULLY
<install:proc,spa=HCF600;

INSTALL PROC,SPA HDF600 COMPLETE - SUMMARY REPORT:
OPERATION
STATUS
----------------------------------------------------------------------SPA PROCESS INSTALLATION:
SUCCEEDED
0
0
<rst:spa=HCF600;

RST SPA HDF600 COMPLETED SUCCESSFULLY
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 17
Remove IPSec connection between USDS and

LTDU
Using CALEA
Procedure: Remove IPSec connection between USDS and LTDU

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to manually remove IPSec connections between

USDS and LTDU.
Remote system name and IP address
Security Parameters Indices (SPIs)
ESP algorithm
Steps
...........................................................................................................................................................................
Log on to the UNIX console as root.

...........................................................................................................................................................................
TERM=vt100
...........................................................................................................................................................................
Save the current SA parameters to a backup file.

/usr/sbin/ipseckey -s /etc/inet/secret/ipseckeys.bak
...........................................................................................................................................................................
To delete an individual SA, execute the following command,

/usr/sbin/ipseckey delete SA_type spi Security_parameter_index dst Dest_name
where:
SA_type is "esp" for Encapsulating Security Payload.
Security_parameter_index is the identifier number of the

individual SA as found in the /etc/inet/secret/ipseckeys.bak file.
Dest_name is the destination host name of the SA.
...........................................................................................................................................................................
To delete all SAs, execute the following command.

/usr/sbin/ipseckey flush
...........................................................................................................................................................................................................................................................
9 - 18

270-710-919R6.0

LTDU
Using CALEA
...........................................................................................................................................................................
At the LMT or subshl message prompt, enter an RC/V session by

typing the following command:
rcv:menu;
Result: The NETWORK PLATFORM MAIN MENU is
displayed as shown in Figure 9-4, "NETWORK PLATFORM

MAIN MENU" (9-19).
Figure 9-4
...........................................................................................................................................................................
Select option [2], OPERATIONS, ADMINISTRATION AND

MAINTENANCE SUBMENU is displayed as shown in

Figure 9-5, "OPERATIONS, ADMINISTRATION AND
MAINTENANCE SUBMENU" (9-20).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 19

LTDU
Figure 9-5
Using CALEA
OPERATIONS, ADMINISTRATION AND

MAINTENANCE SUBMENU
...........................................................................................................................................................................
Select option [17], IPSEC PARAMETERS FORM.

Result: Enter Database Operation
QD=QueryD :
...........................................................................................................................................................................
Type [QD] and press Enter.

Result: The IPSEC PARAMETERS FORM is displayed as shown
in Figure 9-6, "IPSEC PARAMETERS FORM" (9-21).
...........................................................................................................................................................................................................................................................
9 - 20

270-710-919R6.0

LTDU
Figure 9-6
Using CALEA
Locate the record you want to remove, and type [d] to remove it.
...........................................................................................................................................................................
10
Type [<] and press Enter to return.

...........................................................................................................................................................................
11
Type [!] and press Enter to log off from the RC/V menu.
...........................................................................................................................................................................
12
Restart HCF SPA, once the IPSec policy is changed, to avoid the
latched TCP/IP socket.
At the LMT or subshl message prompt, perform the following steps:
<rmv:spa=HCF600

RMV:SPA REMOVES NEW CALL TRAFFIC, CONTINUE Y OR N? (enter Y)
RMV SPA HCF600 COMPLETED SUCCESSFULLY
<DELETE:PROC,SPA=HCF600;

...........................................................................................................................................................................................................................................................
270-710-919R6.0

9 - 21

LTDU
Using CALEA
DELETE:SPA REMOVES SPA PROCESS, CONTINUE Y OR N? (enter Y)

DELETE PROC SPA HCF600 COMPLETED SUCCESSFULLY
<install:proc,spa=HCF600;

INSTALL PROC,SPA HDF600 COMPLETE - SUMMARY REPORT:
OPERATION
STATUS
----------------------------------------------------------------------------SPA PROCESS INSTALLATION:
SUCCEEDED
0
0
<rst:spa=HCF600;

RST SPA HDF600 COMPLETED SUCCESSFULLY
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
9 - 22

270-710-919R6.0
10
Overview
............................................................................................................................................................................................................................................................
Purpose
Contents
This chapter introduces information on split Numbering Plan Area

(NPA) tool in the USDS.
Introduction
10-2
10-4
10-5
USDS NPA data
10-6
10-8
10-9
10-10
10-11
10-12
10-13
............................................................................................................................................................................................................................................................
270-710-919R6.0

10 - 1
Introduction
Introduction
............................................................................................................................................................................................................................................................
Background
The rapid growth in cellular telephones, pagers, faxes, and Internet

services has fueled an increased demand for PSTN lines. This
unprecedented demand for new lines reduces the exchanges available
in some area codes. When an area code, also known as a NPA, uses the
available supply of exchanges, it is scheduled for an NPA split.
Alternatively, the service provider can overlay a new NPA on the same
geographic area as existing NPAs. However, this approach requires
modifying a seven-digit dialing to ten-digit dialing for local calls.
Therefore, implementing an NPA split is the best solution for the
service provider.
Defining NPA split
An NPA split is the process of splitting and moving a part of the

exchanges in an existing area code to a new area code. On moving the
exchanges, the area code is freed up for future use.
For a certain period, known as the Permissive Dialing Period (PDP),
the old and new area codes are dialed for the exchanges involved in an
NPA split. Once the period expires, the new NPA is dialed for the
exchanges.
USDS NPA split tool
Lucent Technologies provides an NPA split tool that processes

information from an input file containing the NPA split data. The tool
allows a service provider to implement an NPA split within USDS data
tables.
During the PDP, the service provider uses the USDS NPA split tool to
split the exchanges. Exchanges split from the old area code are
reassigned to new subscribers (i.e., new pager, fax, or phone lines).
USDS NPA split tools can run on eSM and MAS platform.
Tool run on eSM
eSM provisioning tasks must be suspended before running the tool.

Then it updates the Oracle database directly and old MDN/MIN
with new MDN/MIN for each affected subscriber.
Tool run on MAS platform (HCF)
Service provider only needs to run the NPA split tool on one HCF
machine. The messages that contain the old MDN/MIN and new
MDN/MIN will inform HDFs to update TimesTen database. Then
HDFs will inform all HCFs to update the Index Server at the same
time.
...........................................................................................................................................................................................................................................................
10 - 2

270-710-919R6.0
Introduction
Input files
The data used to implement an NPA split is provided as an input file to

the USDS NPA split tool. The NPA split data is included in either of the
following files:
ACSED file
newNPANXXRangeFile file
...........................................................................................................................................................................................................................................................
270-710-919R6.0

10 - 3

............................................................................................................................................................................................................................................................
The Traffic Routing Administration (TRA) group of Telcordia

Technologies, Inc. provides a quarterly report to registered service
providers containing information about NPA splits. The information is
included in data files of the Area Code Split Exchange Diskette
(ACSED). These files provide the source information to implement
NPA splits.
The ASCED file identifies the following for each exchange involved in
an NPA split:
The old area code and exchange (old NPA-NXX)
The new area code and exchange (new NPA-NXX)
The Permissive Dialing Date (PDD) that marks the beginning of

the PDP
The Mandatory Dialing Date (MDD) that marks the end of the
PDP
...........................................................................................................................................................................................................................................................
10 - 4

270-710-919R6.0

............................................................................................................................................................................................................................................................
The newNPANXXRangeFile is a text file created by the service

provider as an alternative to the ACSED file.
The newNPANXXRangeFile is structurally similar to the ACSED file,
but is simpler. The newNPANXXRangeFile identifies the following for
each exchange involved in an NPA split:
The old area code and exchange (old NPA-NXX)
The new area code and exchange (new NPA-NXX)

The newNPANXXRangeFile must contain NPA split
data for one old area code.
Important!
...........................................................................................................................................................................................................................................................
270-710-919R6.0

10 - 5
USDS NPA data
USDS NPA data

............................................................................................................................................................................................................................................................
Table 10-1, "Fields affected by a MIN split." (10-6) lists the fields that
are affected by a MIN split
Table 10-1
Fields affected by a MIN split.
Field name
Database/Table
MIN
ANSIPHONE
CoreICHSp
MIN
COMMONPHONE
UserProfileID
UserProfileID
USERPROFILE
MIN
ANSIAC
UserProfileID
ICHServiceProfileID
ICHSVCPROFILE
UserProfileID
LSDefault_MIN
ICHServiceProfileID
COMMONAPROFILE
ICHServiceProfileID
ANSIAPROFILE
ICHServiceProfileID
ANSIBPROFILE
MIN
ICHServiceProfileID
DIRECTORY_NUMBER
MIN
ANSIPHONE_Extended
MIN
CALEA
MIN
CALEA_eSM
MIN
AAA_MSID_ASSOC
MIN
IMSINTWKASSOC
Table 10-2, "Field affected by a MDN split." (10-7) lists the fields that
are affected by a MDN split.
...........................................................................................................................................................................................................................................................
10 - 6

270-710-919R6.0
USDS NPA data
Table 10-2
Field affected by a MDN split.
Field name
Database/Table
DN
DIRECTORY_NUMBER
The NPA Split Tool searches the databases or tables for the fields and
replaces the old NPA value with the new value.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

10 - 7

............................................................................................................................................................................................................................................................
The USDS split NPA tool can handle up to 100,000 subscribers within
a maximum time frame of 4 hours.
Service providers must suspend USDS service
provisioning while implementing the NPA split. The split NPA tool
must be run only during the non-peak hours.
Important!
...........................................................................................................................................................................................................................................................
10 - 8

270-710-919R6.0

............................................................................................................................................................................................................................................................
Tasks for NPA split on eSM
Implementing an NPA split on eSM involves the following three

primary tasks:
Extract MDN/MIN list from USDS databases/tables
Update old MDN/MIN to new MDN/MIN and all related fields
Update FA related fields after NPA split
In addition to the above tasks, the NPA split tool can also back out
updated NPA data from the USDS databases/tables.
Tasks for NPA split on MAS
Implementing an NPA split on MAS involves the following four

primary tasks:
Extract MDN/MIN list from USDS databases/tables
Update old MDN/MIN to new MDN/MIN and update all related

fields. It will update HDF database and HCF index server at the
same time
Update FA related fields after NPA split
Query "Last_Used_NPA" field after NPA split (optional)
In addition to the above tasks, the NPA split tool can also back out
updated NPA data from the USDS databases/tables.
Service providers can run query script at any time but
it is recommended to run it during non-peak hours to avoid
performance impact.
Important!
...........................................................................................................................................................................................................................................................
270-710-919R6.0

10 - 9

............................................................................................................................................................................................................................................................
The FTN fields are not updated by the split NPA tool.
Multiple instances of the split NPA tool is not allowed to run

concurrently.
If the database becomes corrupt during NPA split, the customer

can restore the database to its original status using the backup
data.
The ACSED and newNPANXXRangeFile does not provide NPA

split data for multiple old area codes. Only one old area code will
be contained in these files.
There should be no subscribers within new NPANXX range

before running the Split-NPA tool.
There is no scheduled work order for Split-NPA affected

subscribers on eSM. Otherwise these work orders will fail after
NPA split on eSM.
For ANSI users provisioned with ANSI logical table view,

UserProfileID and CHServiceProfileID equal to MIN.
For "User Mobility" users provisioned with HDF-Standard view,

UserProfileID and CHServiceProfileID have no relationship with
MIN.
For users in the old NPANXX ranges of ACSED and

newNPANXXRangeFile, they should ALL be provisioned with
ANSI logical table view or HDF-Standard view. Customers
should indicate this in the configuration file.
If customer uses the ANSI logical table view, Split-NPA tool will
update UserProfileID and ICHServiceProfileID for ANSI related
tables not including tables for other protocols because there will
be no records for other protocols for the same user.
If customer uses HDF-Standard view, Split-NPA tool will only

update MIN fields, and not include UserProfileID and
CHServiceProfileID.
All HCFs and HDFs should be in IS state when running the SplitNPA tool.
Split-NPA tool does not work if USDS works as a standalone AC.
No audit capability is provided to check for data consistency

across the platforms.
...........................................................................................................................................................................................................................................................
10 - 10

270-710-919R6.0

............................................................................................................................................................................................................................................................
File to be untared
Created directory
On eSM
npasplit_esm.tar
npasplit_esm
On MAS
npasplit_mas.tar
npasplit_mas
For detailed procedure on how to install NPA split tool, refer to MOP
input for ANSI Split-NPA tools.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

10 - 11

............................................................................................................................................................................................................................................................
For detailed procedure on how to use NPA split tool on eSM, refer to
MOP input for ANSI Split-NPA tools.
...........................................................................................................................................................................................................................................................
10 - 12

270-710-919R6.0

............................................................................................................................................................................................................................................................
For detailed procedure on how to use NPA split tool on MAS, refer to
MOP input for ANSI Split-NPA tools.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

10 - 13
...........................................................................................................................................................................................................................................................
10 - 14

270-710-919R6.0
11
Using AAA
Overview
............................................................................................................................................................................................................................................................
Purpose
Contents
This chapter provides information on how to use AAA on USDS.

11-2
Access SMT through LMT
11-3
11-6
11-8
USS Servers on USDS
11-9
............................................................................................................................................................................................................................................................
270-710-919R6.0

11 - 1
Using AAA
............................................................................................................................................................................................................................................................
Overview
USDS AAA is composed of the following three components:
VitalAAA server on HCF to process AAA requests/responses
PDLSG on HCF acting as data access gateway for AAA server to

HDF database
HDF processes on HDF for managing and accessing USDS

databases.
To manage AAA services, the AAA servers located on the HCFs need
to be managed. The AAA server on HCF is VitalAAA, a commercial
AAA server of the Lucent product line.
In USDS R6.0, VitalAAA is integrated into the USDS architecture to
provide AAA functionalities. VitalAAA provides a Service
Management Tool (SMT) for managing and monitoring its AAA
functionalities.
SMT
SMT is a fully graphical remote configuration, management, and

monitor interface. It is used to configure and manage the VitalAAA
server in the Lucent USDS. It can be used to manage all aspects of the
server operations. The SMT also displays real-time statistical
information from the AAA server and the USS server systems.
SMT is a standalone application that is started and run independent of
the VitalAAA server. The type of hardware/OS platform is irrelevant as
you can run the SMT on any platform which may or may not be the
same platform as the VitalAAA server.
In USDS, SMT is installed on MAS LMT for the OA&M operations of
the VitalAAA server.
...........................................................................................................................................................................................................................................................
11 - 2

270-710-919R6.0
Using AAA
Procedure: Access SMT through LMT

............................................................................................................................................................................................................................................................
Purpose
Before you begin
Use this procedure to access SMT in LMT for managing the VitalAAA
server.
Got the access to MAS LMT.
AAA HCF nodes have been configured correctly for SMT access
and SMT has been installed on the MAS LMT for that AAA HCF
node. (If not, refer to Procedure: Configuring the AAA HCF nodes
to communicate with the SMT on LMT, Unified Subscriber Data
Server (USDS) R6.0 Installation Guide)
Got the administrator login for the SMT to access the VitalAAA
server on USDS.
Steps
...........................................................................................................................................................................
Log on to LMT according to Procedure: Access the MAS administrative

interfaces to access a MAS UNIX console.
Result: A UNIX console is displayed.
...........................................................................................................................................................................
Start SMT by typing the following command:

>cd /vendorpackages/NavisRadius/navisAAA/bin
>./nrsmt
Result: A pop-up window "Server Management Tool" is displayed

as shown in Figure 11-1, "Server Management Tool" (11-4).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

11 - 3
Using AAA
Figure 11-1
Server Management Tool
...........................................................................................................................................................................
Enter the administrator login as "User Name" and password as

"Password", select the "Connect to a Configuration Server" check box,
enter the IP address of the HCF on which the VitalAAA server is
running. The default user name/password is NR/NR
Result: The SMT is connected with the configuration server on the
AAA HCF. Now, you can manage and monitor the AAA
functionalities using SMT.
...........................................................................................................................................................................................................................................................
11 - 4

270-710-919R6.0
Using AAA
Refer to VitalAAA Server Management Tool Manual

(SMT.pdf under /vendorpackages/NavisRadius/navisAAA/doc/) for
detailed common operations of SMT.
Important!
END OF STEPS
...........................................................................................................................................................................
...........................................................................................................................................................................................................................................................
270-710-919R6.0

11 - 5
Using AAA

............................................................................................................................................................................................................................................................
Overview
VitalAAA server provides several accounting interfaces:
Text files: random or fixed length records with user definable

record formatting (AV Pairs, comma delimited, column delimited,
etc.
VitalAAA can write the accounting records to a detail file using

the Lucent accounting format (as established in Livingston
RADIUS 1.16). This is compatible with all Lucent and Ascent
RADIUS servers and is supported by most billing and accounting
systems. However, custom file formats can also be defined.
SQL: Write accounting records to a SQL compliant database.

There is no limit on the schema and an example schema is also
provided.
Proxy: Records may be forwarded to one or more remote servers.

Attributes may be inserted, deleted, or modified prior to
forwarding.
The treating of accounting records is subject to customer requirement.

Items such as format of the file, the number of concurrently opened
files, and the selection of the data actually saved in the CDR must be
able to be customized on individual customer basis.
The accounting interfaces implemented in VitalAAA server policy
flows through different PolicyFlow Plug-ins. Refer to VitalAAA Plugin documents for more details.
AAA Accounting Records
on USDS
For VitalAAA server that is integrated in USDS, it is recommended

that /acct_rec partition is used to store the accounting records. This
partition is preserved over retrofit and provides support for additional
OMs. However, it is not required and the customer may define an
alternative partition to store records or treat the records in other ways
(databases or remote servers).
Refer to Procedure: Unlocking AAA feature and configuring VitalAAA
Server for AAA HCF nodes, Unified Subscriber Data Server (USDS)
R6.0 Installation Guide for the configuration of the AAA accounting
records.
An Output Message is displayed if the AAA server is started and the
recommended accounting records partition, /acct_rec, is not available.
REPT AAA /acct_rec PARTITION IS NOT DEFINED.
...........................................................................................................................................................................................................................................................
11 - 6

270-710-919R6.0
Using AAA
An Output Message is displayed if the disk partition containing

VitalAAA accounting records has exceeded the "minor alarm water
mark". This OM has a minor default alarm level.
REPT AAA ACCOUNTING RECORDS DISK PARTITION a FULL
Where a indicates the percent the /acct_rec partition is full

An Output Message is displayed if the disk partition containing
VitalAAA accounting records has exceeded the "major alarm water
mark". This OM has a major default alarm level.
REPT AAA ACCOUNTING RECORDS DISK PARTITION a FULL
Where a indicates the percent the /acct_rec partition is full
...........................................................................................................................................................................................................................................................
270-710-919R6.0

11 - 7
Using AAA

............................................................................................................................................................................................................................................................
Overview
VitalAAA server provides excellent logging capabilities. Log levels

can be changed quickly or controlled by arbitrary request contents. Log
outputs can be sent to various channels, including databases, files,
syslog servers, SNMP Traps or external commands. When local files
are used, file roll-over can be automatically controlled by time, date or
file size. Refer to Chapter 10 "Message Logging", "VitalAAA Server
Management Tool Manual" for more detailed information.
VitalAAA server logs on

USDS
The default logs of VitalAAA server are stored under the "run"
directory in the VitalAAA installation directory (on MAS, it is /
vendorpackages/NavisRadius/navisAAA). The default log file for
VitalAAA server is policy.log, and for VitalAAA Configuration Server
is smt.log.
On USDS AAA HCF nodes, the VitalAAA server logs are redirected to
other files:
VitalAAA Server log is redirected to /sn/log/vendorlog/aaa.log
Configuration Server log is redirected to /sn/log/vendorlog/

aaaguiserver.log
The log files are cleaned up via the CLR:LOGFILE CEP. This CEP can
be scheduled to run every three hours from the Timed Scheduling RCV
Form.
Refer to Procedure: Unlocking AAA feature and configuring VitalAAA
Server for AAA HCF nodes, Unified Subscriber Data Server (USDS)
R6.0 Installation Guide for detailed configuration procedures.
VitalAAA Server Alarms
VitalAAA allows configuration to determine which log messages will

be sent to the OMlog. Log messages belong to a log level. If a log level
(i.e. ERROR) is configured to be sent to the OMlog, all log messages of
that level will be sent to the OM log. Refer to Service Management
Tool Manual for configuration details.
...........................................................................................................................................................................................................................................................
11 - 8

270-710-919R6.0
USS Servers on USDS
Using AAA
USS Servers on USDS

............................................................................................................................................................................................................................................................
Overview
The USS (Universal State Server) is an in-memory database optimized

to track network-resource usage. It interacts with the VitalAAA Server
to maintain usage counts and enforce resource limits within the
network.
Configuring USS Servers

on USDS
The standard USDS configuration for AAA is two HDFs and two
HCFs. On the two HCF machines, there will be two VitalAAA Servers
to handle the AAA traffic. But there should be only one USS instance
on a HCF node to maintain a single picture of the session state. Both
the AAA servers on the two HCF nodes communicate with this USS
instance. The other USS instance on another HCF node can be a faulttolerance option. The secondary USS can take over if the primary USS
becomes unavailable.
For more information on how to configure a high-availability USS,
refer to VitalAAA Server Management Tool Manual. Some sample
policy flows for high availability USS are available in /
vendorpackages/NavisRadius/navisAAA/run/samples/quick-starthauss.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

11 - 9
USS Servers on USDS
Using AAA
...........................................................................................................................................................................................................................................................
11 - 10

270-710-919R6.0
Overview
............................................................................................................................................................................................................................................................
Purpose
This chapter provides detailed description for the measurement sets

that are supported in both USDS R6.0 HCF SPA and HDF SPA.
Only service measurements of USDS are covered in
this chapter. For platform measurements, refer to MAS System
Administration Guide, (270-700-167).
Important!
Contents

A-3
A-8
A-59
A-94
A-100
A-108
A-109
A-110
A-114
A-129
............................................................................................................................................................................................................................................................
270-710-919R6.0

A - 1
A-149
...........................................................................................................................................................................................................................................................
A - 2

270-710-919R6.0

............................................................................................................................................................................................................................................................
HCF Overload
Table A-1, "HCF Overload" (A-3) contains HCF node overload status
related measurements. This table is called HCF_MEAS_OVERLOAD
in MAS database.
Table A-1
MSGH
HCF Overload
DB Name
[View Attribute Name]
Description
MAP_Msg_Discard_OL
[MAP Msgs Discard Overload]
The number of MAP messages

discarded due to overload
Overload_Level_1
[Overload Level 1]
The number of times reached Level

1 overload
Overload_Level_2
[Overload Level 2]

2 overload
Overload_Level_3
[Overload Level 3]

3 overload
Overload_Level_4
[Overload Level 4]

4 overload
Overload_Level_5
[Overload Level 5]

5 overload
Table A-2, "MSGH" (A-4) pegs the number of Message Handler

(MSGH) messages that are sent and received by the HCF process,
which includes messages that go between HCF and HDF, HCF and
HCF. This table is called HCF_MEAS_MSGH in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 3

Table A-2
Index Server
MSGH
DB Name
Description
Msgh_msg_from_CF
[Msgh_msg_from_CF]
The total number of MSGH messages

originated from the HCF.
Msgh_msg_to_CF
[Msgh_msg_to_CF]
The total number of MSGH messages

terminated to the HCF.
Msgh_msg_sz_rcvd
[Msgh_msg_sz_rcvd]
The total size (in Kbytes) of MSGH

message received by the HCF.
msgh_msg_sz_sent
[msgh_msg_sz_sent]
The total size (in Kbytes) of MSGH

message sent by the HCF.
Table A-3, "Index Server" (A-5) contains index server related

measurements. This table is called HCF_MEAS_INDEXSERVER in
MAS database.
...........................................................................................................................................................................................................................................................
A - 4

270-710-919R6.0

Table A-3
Index Server
DB Name
Description
a_in_Bad_imsi_list
[Bad IMSI attempts]
Counts of keys found in Bad_imsi_list
a_in_Bad_dn_list
[Bad DN attempts]
Counts of keys found in Bad_dn_list
a_in_Bad_min_list
[Bad MIN attempts]
Counts of keys found in Bad_min_list
a_in_Bad_prid_list
Counts of keys found in Bad_prid_list
a_in_Bad_puid_list
Counts of keys found in Bad_puid_list
a_in_Bad_aaanai_list[Bad
AAA NAI attempts]
Counts of keys found in Bad_aaanai_list
na_in_imsi_mapping
[IMSI NA in mapping table]
Counts of IMSI not found in the mapping

table
na_in_dn_mapping
[DN NA in mapping table]
Counts of Directory Number (DN) not

found in the mapping table
na_in_min_mapping
[MIN NA in mapping table]
Counts of MIN not found in the mapping

table
na_in_prid_mapping
Counts of PRID not found in the mapping

table
na_in_puid_mapping
Counts of PUID not found in the

mapping table
na_in_aaanai_mapping[AAA
NAI NA in mapping table]
Counts of AAA NAI not found in the

mapping table
na_imsi_in_HDF
[IMSI NA in HDF]
Counts of IMSI keys found in the

mapping table but not on HDF
na_dn_in_HDF
[DN NA in HDF]
Counts of DN keys found in the mapping

table but not on HDF
na_min_in_HDF
[MIN NA in HDF]
Counts of MIN keys found in the

na_prid_in_HDF
Counts of PRID keys found in the

na_puid_in_HDF
Counts of PUID keys found in the

...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 5
DB Name
Description
na_aaanai_in_HDF[AAA
NAI NA in HDF]
Counts of AAA NAI keys found in the

imsi_self_healing_request
[IMSI self-healing request]
Counts of self healing broadcasts sent out

for IMSI from HCF
dn_self_healing_request
[DN self-healing request]

for DN from HCF
min_self_healing_request
[MIN self-healing request]

for MIN from HCF
prid_self_healing_request

for PRID from HCF
puid_self_healing_request

for PUID from HCF
aaanai_self_healing_req[AA
A NAI self-healing request]

for AAA NAI from HCF
imsi_self_healing_rsp
[IMSI self-healing rsp]
Counts of self healing responses received

for IMSI at HCF
dn_self_healing_rsp
[DN self-healing rsp]

for DN at HCF
min_self_healing_rsp
[MIN self-healing rsp]

for MIN at HCF
prid_self_healing_rsp

for PRID from HCF
puid_self_healing_rsp

for PUID from HCF
aaanai_self_healing_rsp[AA
A NAI self-healing rsp]

for AAA NAI at HCF
imsi_self_healing_failure
[IMSI self-healing failure]
Counts of IMSI not found due to no

response from Self-Healing polls
dn_self_healing_failure
[DN self-healing failure]
Counts of DN not found due to no

min_self_healing_failure
[MIN self-healing failure]
Counts of MIN not found due to no

prid_self_healing_failure
[PRID self-healing failure]
Counts of PRID not found due to no

...........................................................................................................................................................................................................................................................
A - 6

270-710-919R6.0
DB Name
Description
puid_self_healing_failure
[PUID self-healing failure]
Counts of PUID not found due to no

aaanai_self_healing_fail[AA
A NAI self-healing failure]
Counts of AAA NAI not found due to no

peer_pump_success
[Peer Pump Success]
Counts of successful attempts for peer

pump
peer_pump_attempts
[Peer Pump Attempts]
Counts of attempts for peer pump
imsi_fail_add_fraudlist
[imsi_fail_add_fraudlist]
Count of failures for adding new fraud

IMSI into fraud list due to full fill of
IMSI
dn_fail_add_fraudlist
[dn_fail_add_fraudlist]

DN into fraud list due to full fill of DN
min_fail_add_fraudlist
[min_fail_add_fraudlist]

MIN into fraud list due to full fill of MIN
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 7

............................................................................................................................................................................................................................................................
ANSI RegCanc Retry
Table A-4, "ANSI RegCanc Retry" (A-8) contains

RegistrationCancellation Invoke (REGCANC) retry related
measurements. This table is called HCF_MEAS_ANSI_REGCANRTY
in MAS database.
Table A-4
ANSI MWN
ANSI RegCanc Retry
DB Name
Description
Fail_RegCancRe_Timeout
[RegCanc Retry-Timeout]
Number of unsuccessful
RegistrationCancellation retries due to
the timeout
Suc_RegCancRe
[Successful RegCanc Retry]
Number of successful
RegistrationCancellation retries
Fail_RegCancRe_notTimeout
[RegCanc Retry-RetErr]
RegistrationCancellation retries due to
any reason other than the timeout
Total_RegCancRe
[Total RegCanc Retry]
Number of all RegistrationCancellation

retries
Table A-5, "ANSI MWN" (A-8) contains Message Waiting Number

(MWN) related measurements. This table is called
HCF_MEAS_ANSI_MWN in MAS database.
Table A-5
ANSI MWN
DB Name
Description
Suc_MsgDir
[Successful MsgDir]
Number of successful MessageDirective

processed
Fail_MsgDir
[Unsucc MsgDir]
MessageDirective processed
Suc_InfoDir
[Successful InfoDir]
InformationDirective processed
Fail_InfoDir
[Unsucc InfoDir]
InformationDirective processed
...........................................................................................................................................................................................................................................................
A - 8

270-710-919R6.0

ANSI multiple SMSC
Table A-6, "ANSI multiple SMSC" (A-9) contains multiple Short

Message Service Center (SMS-C) related measurements. This table is
called HCF_MEAS_ANSI_MSMSC in MAS database.
Table A-6
ANSI SS
ANSI multiple SMSC
DB Name
Description
Suc_SMSNoti
[Successful SMSNOT]
Number of successful SMSNotification

processed
Fail_SMSNoti
[Unsucc SMSNOT]
SMSNotification processed
Suc_SMSReq
[Successful SMSReq]
Number of successful SMSRequest

processed
Fail_SMSReq
[Unsucc SMSReq]
Number of unsuccessful SMSRequest

processed
Suc_SMSNotiRelay
[Successful SMSNOT Relay]
Number of successful SMSNotification

relay processed
Fail_SMSNotiRelay
[Unsucc SMSNOT Relay]
SMSNotification relay processed
Suc_SMSReqRelay
[Successful SMSReq Relay]
Number of successful SMSRequest relay

processed
Fail_SMSReqRelay
[Unsucc SMSReq Relay]

relay processed
Suc_Surv_Req
[Suc_Surv_Req]
Number of successful SurvReq processed
Fail_Surv_Req
[Fail_Surv_Req]
Number of unsuccessful SurvReq

processed
Fail_SMSReq_Timeout
[Fail_SMSReq_Timeout]

processed due to timeout.
Table A-7, "ANSI SS" (A-10) contains Supplementary Services (SS)

related measurements. This table is called HCF_MEAS_ANSI_SS in
MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 9

Table A-7
ANSI SS
DB Name
Description
Suc_FeatReq
[Succ FeatReq]
Number of successful FeatureRequest

processed
Fail_FeatReq
[Unsucc FeatReq]
Number of unsuccessful FeatureRequest

processed
Suc_CFB_DeAct
[Succ CFB DeActivation]

processed for Call Forwarding Busy
(CFB) deactivation
Fail_CFB_DeAct
[Unsucc CFB DeActivation]

processed for CFB deactivation
Suc_CFB_Reg
[Succ CFB Registration]

processed for CFB registration
Fail_CFB_Reg
[Unsucc CFB Registration]

processed for CFB registration
Suc_CFNA_Act
[Succ CFNA Activation]

processed for Call Forwarding No
Answer (CFNA) activation
Suc_CFB_Act
[Succ CFB Activation]

processed for CFB activation
Fail_CFB_Act
[Unsucc CFB Activation]

processed for CFB activation
Fail_CFNA_Act
[Unsucc CFNA Activation]

processed for CFNA activation
Suc_CFNA_DeAct
[Succ CFNA DeActivation]

processed for CFNA deactivation
Fail_CFNA_DeAct
[Unsucc CFNA
DeActivation]

processed for CFNA deactivation
Suc_CFNA_Reg
[Succ CFNA Registration]

processed for CFNA registration
Fail_CFNA_Reg
[Unsucc CFNA Registration]

processed for CFNA registration
OTFI_AnnListReadFail
[Unsucc OTFI AnnList Read]
Number of FeatureRequests, which read

One Time Feature Indicator (OTFI)
Announcement List Table while this table
is not populated
...........................................................................................................................................................................................................................................................
A - 10

270-710-919R6.0
ANSI SS 2
DB Name
Description
Suc_PACA
[Succ PACA]
Number of on demand Priority Access

and Channel Assignment (PACA) feature
activation requests successfully
processed
Fail_PACA
[Unsucc PACA
Number of on demand PACA feature

activation requests unsuccessfully
processed.
Suc_MODIFY
[Suc_MODIFY]
The number of MODIFY operation was

processed successfully and a Modify
RETURN RESULT was sent back by
HLR.
Fail_MODIFY
[Fail_MODIFY]
The number of MODIFY operation was

processed unsuccessfully a Modify
RETURN ERROR was sent back or
message timeout.
Fail_FeatReq_Timeout
[Fail_FeatReq_Timeout]

Table A-8, "ANSI SS 2" (A-12) contains Supplementary Service

related measurements. This table is called HCF_MEAS_ANSI_SS2 in
MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 11

Table A-8
ANSI SS 2
DB Name
Description
Suc_CFU_Act
[Succ CFU Activation]

processed for CFU activation
Fail_CFU_Act
[Unsucc CFU Activation]

processed for CFU activation
Suc_CFU_DeAct
[Succ CFU DeActivation]

processed for CFU deactivation
Fail_CFU_DeAct
[Unsucc CFU DeActivation]

processed for CFU deactivation
Suc_CFU_Reg
[Succ CFU Registration]

processed for CFU registration
Fail_CFU_Reg
[Unsucc CFU Registration]

processed for CFU registration
Suc_CFD_Act
[Succ CFD Activation]

processed for Call Forwarding Default
(CFD) activation
Fail_CFD_Act
[Unsucc CFD Activation]

processed for CFD activation
Suc_CFD_DeAct
[Succ CFD DeActivation]

processed for CFD deactivation
Fail_CFD_DeAct
[Unsucc CFD DeActivation]

processed for CFD deactivation
Suc_CFD_Reg
[Succ CFD Registration]

processed for CFD registration
Fail_CFD_Reg
[Unsucc CFD Registration]

processed for CFD registration
Suc_HCC_ORREQ
[Succ HCC ORREQ]
Number of successful Home Customer

Care related OriginationRequest
responses
Fail_HCC_ORREQ
[Unsucc HCC ORREQ]
Number of unsuccessful Home Customer

Care related OriginationRequest
responses
Suc_SEARCH
[Succ Search]
Number of successful SEARCH

processed
...........................................................................................................................................................................................................................................................
A - 12

270-710-919R6.0
ANSI SS 3
DB Name
Description
Fail_SEARCH
[Unsucc Search]
Number of unsuccessful SEARCH

processed
Table A-9, "ANSI SS 3" (A-14) contains Supplementary Service

related measurements. This table is called HCF_MEAS_ANSI_SS3 in
MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 13

Table A-9
ANSI SS 3
DB Name
Description
Suc_Relay_ORREQ[Succ
Relay ORREQ]
Number of OriginationRequest
successfully relayed to MSCs
Fail_Relay_ORREQ[Unsucc
Relay ORREQ]
Number of OriginationRequest
unsuccessfully relayed to MSCs
Suc_Relay_RUIDIR[Succ
Relay RUIDIR]
Number of
RemoteUserInteractionDirective
successfully relayed to MSCs
Fail_Relay_RUIDIR[Unsucc
Relay RUIDIR]
Number of
Suc_Relay_FEATREQ[Succ
Relay FEATREQ]
Number of FeatureRequest successfully

relayed to MSCs
Fail_Relay_FEATREQ[Unsu
cc Relay FEATREQ]
Number of FeatureRequest
Suc_SPINA_FEATREQ_Act[
Succ SPINA FEATREQ Act]
Number of Subscriber PIN Access

(SPINA) feature activation request
successfully processed
Fail_SPINA_FEATREQ_Act
[Unsucc SPINA FEATREQ
Act]
Number of SPINA feature activation

request unsuccessfully processed
Suc_SPINA_FEATREQ_De
Act
[Succ SPINA FEATREQ
DeAct]
Number of SPINA feature deactivation

request successfully processed
Fail_SPINA_FEATREQ_De
Act
DeAc]
Number of SPINA feature deactivation

request unsuccessfully processed
Suc_SPINA_FEATREQ_PIN
[Succ SPINA FEATREQ
PIN]
Number of SPINA PIN change request

successfully processed
Fail_SPINA_FEATREQ_PIN
PIN]
Number of SPINA PIN change request

unsuccessfully processed
Suc_ORREQ
[Succ ORREQ]
OriginationRequest processed
...........................................................................................................................................................................................................................................................
A - 14

270-710-919R6.0
ANSI LBS
DB Name
Description
Fail_ORREQ
[Unsucc ORREQ]
OriginationRequest processed
Suc_PosReq
[Succ PosReq]
Number of successful PositionRequest

processed
Fail_PosReq
[Unsucc PosReq]
Number of unsuccessful PositionRequest

processed
Suc_Relay_PosReq
[Succ Relay PosReq]
Number of PositionRequest successfully

relayed
Fail_Relay_PosReq
[Unsucc Relay PosReq]
Number of PositionRequest
unsuccessfully relayed
Suc_RUIDIR
[Suc_RUIDIR]
processed
Fail_RUIDIR
[Fail_RUIDIR]
processed
Fail_Relay_PosReq_NORI
[Fail_Relay_PosReq_NORI]
Number of unsuccessful relaying of

PositionRequest Invoke send failure as
the routing information cannot be fetched
from global data.
Table A-10, "ANSI LBS" (A-16) contains Location Based Service

(LBS) related measurements. This table is called
HCF_MEAS_ANSI_LBS in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 15

Table A-10
ANSI LBS
DB Name
Description
Suc_LCSPReq
[Succ LCSPReq]
LCSParameterRequest processed
Fail_LCSPReq_MS
[Unsucc LCSPReq MS]
LCSParameterRequest with the error
code set to "MSID/HLRMismatch"
Fail_LCSPReq_RS
[Unsucc LCSPReq RS]
code set to "ResourceShortage"
Fail_LCSPReq_ONS
[Unsucc LCSPReq ONS]
code set to "OperationNotSupported"
Fail_LCSPReq_MP
[Unsucc LCSPReq MP]
code set to "MissingParameter"
Fail_LCSPReq_PE
[Unsucc LCSPReq PE]
code set to "ParameterError"
Fail_LCSPReq_SF
[Unsucc LCSPReq SF]
code set to "SystemFailure"
Fail_LCSPReq_UPV
[Unsucc LCSPReq UPV]
code set to
"UnrecognizedParameterValue"
Fail_LCSPReq_UM
[Unsucc LCSPReq UM]
code set to "UnrecognizedMDN"
LCSPReq_Inactive
[LCSPReq Inactive]
Number of LCSParameterRequest with

denied reason as "inactive"
LCSPReq_NotSup
[LCSPReq NotSup]
Number of LCSParameterRequest with

denied reason as
"PositionDeterminationNotSupported"
Suc_SNREQ
[Succ SNREQ]
StatusNotificationRequest processed
...........................................................................................................................................................................................................................................................
A - 16

270-710-919R6.0
ANSI_LBS2
DB Name
Description
Fail_SNREQ_MS
[Unsucc SNREQ MS]
StatusNotificationRequest with error
Fail_SNREQ_RS
[Unsucc SNREQ RS]
Fail_SNREQ_ONS
[Unsucc SNREQ ONS]
Fail_SNREQ_MP
[Unsucc SNREQ MP]
Fail_SNREQ_PE
[Unsucc SNREQ PE]
Fail_SNREQ_SF
[Unsucc SNREQ SF]
Fail_SNREQ_UPV
[Unsucc SNREQ UPV]
code set to
"UnrecognizedParameterValue"
Fail_SNREQ_UM
[Unsucc SNREQ UM]
Table A-11, "ANSI_LBS2" (A-18) contains Location Based Service

related measurements. This table is called HCF_MEAS_ANSI_LBS2
in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 17

Table A-11
ANSI_LBS2
DB Name
Description
Fail_LCSPReq_UMIN
[Fail_LCSPReq_UMIN]
LCSParameterRequest with error code
set to "UnrecognizedMIN"
Fail_LCSPReq_UIMSI
[Fail_LCSPReq_UIMSI]
LCSParameterRequest with error code
set to "UnrecognizedIMSI"
Table A-12, "ANSI Circuit Mode Data" (A-19) contains Circuit Mode
Data (CMD) related measurements. This table is called
HCF_MEAS_ANSI_CMD in MAS database.
...........................................................................................................................................................................................................................................................
A - 18

270-710-919R6.0

Table A-12
ANSI LM MSInact
DB Name
Description
Suc_Fax5CallTerm
[Succ Fax5 CallTerm]
Number of successful Fax Service option

5 call terminations
Fail_ADS12CallTerm
[Unsucc ADS12 CallTerm]
Number of unsuccessful Asynchronous

Data Service option 12 call terminations
Suc_ADS12CallTerm
[Succ ADS12 CallTerm]
Number of successful Asynchronous

Fail_ADS4CallTerm
[Unsucc ADS4 CallTerm]
Number of unsuccessful Asynchronous

Suc_ADS4CallTerm
[Succ ADS4 CallTerm]
Number of successful Asynchronous

Fail_Fax5CallTerm
[Unsucc Fax5 CallTerm]
Number of unsuccessful Fax Service

option 5 call terminations
Suc_Fax13CallTerm
[Succ Fax13 CallTerm]
Number of successful Fax Service option

13 call terminations
Fail_Fax13CallTerm
[Unsucc Fax13 CallTerm]
Number of unsuccessful Fax Service

option 13 call terminations
Total_1NumPerServCallTerm
[Total 1NumPerServCallTerm]
Number of attempts for "one number per

service" call terminations
Total_2StageDialCallTerm
[Total 2StageDialCallTerm]
Number of attempts for "two-stage

dialing" call terminations
Total_PrearrangedCallTerm
[Total PrearrangedCallTerm]
Number of attempts for prearranged call

terminations
Table A-13, "ANSI LM MSInact" (A-20) contains Location

Management-MSInactive related measurements. This table is called
HCF_MEAS_ANSI_LM_MSINACT in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 19

Table A-13
ANSI LM MSInact
DB Name
Description
Suc_MSInact
[Succ MSInactive]
Number of successful MSInactive

processed
Fail_MSInact
[Unsucc MSInact]
Number of unsuccessful MSInactive

processed
Fail_MSInact_EC_PE
[MSInact ParamError]

processed with the error code set to
"Parameter Error"
Fail_MSInact_EC_SF
[MSInact SystemFailure]

"System Failure"
Fail_MSInact_EC_MP
[MSInact Missing Param]

"Missing Parameter"
Suc_MSInact_DT_NU
[Succ MSInact DeregNotUsed]

with the de-registration type set to
"Not Used"
Suc_MSInact_DT_Unspec
[Succ MSInact DeregUnspec]

with the de registration type set to
"Deregister for an Unspecified
Reason"
Suc_MSInact_DT_ADM
[Succ MSInact DeregAdmin]

"Deregister for an Administrative
Reason"
Suc_MSInact_DT_PD
[Succ MSInact DeregPowerDn]

"Deregister due to MS Power Down"
Fail_MSInact_DT_NU
[Fail MSInact DeregNotUsed

"Not Used"
Fail_MSInact_DT_Unspec
[Fail MSInact DeregUnspec]

"Unspecified Reason"
Fail_MSInact_DT_ADM
[Fail MSInact DeregAdmin]

"Administrative Reason"
...........................................................................................................................................................................................................................................................
A - 20

270-710-919R6.0
ANSI LM RegCanc
DB Name
Description
Fail_MSInact_DT_PD
[Fail MSInact DeregPowerDn]

"MS Power Down"
Suc_MSInact_Relay
[Succ MSInact Relay]
Number of successfully relayed

MSInactive
Fail_MSInact_Relay_RE
[Unsucc MSInact Relay Error]
Number of unsuccessfully relayed

MSInactive due to "RETURN
ERROR"
Fail_MSInac_Relay_Timeout
[Unsucc MSInact Relay Timeout]
Number of unsuccessful relayed

MSInactive due to operation timeout
Stray_MSInactive
[Stray MSInactive]
Number of stray MSInactive.
Fail_MSInact_Timeout
[Fail_MSInact_Timeout]
Number of unsuccessful MS Inactive

Table A-14, "ANSI LM RegCanc" (A-22) contains Location

Management - RegCanc related measurements. This table is called
HCF_MEAS_ANSI_LM_REGCANC in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 21

Table A-14
ANSI LM RegCanc
DB Name
Description
Suc_RegCanc
[Succ RegCanc]
RegistrationCancellation processed
Fail_RegCanc
[Unsucc RegCanc]
Fail_RegCanc_Timeout
[RegCanc Timeout]
due to operation timeout
Fail_RegCanc_EC_UE
[RegCanc UnrecognizedESN]
with the error code set to
"Unrecognized ESN"
Fail_RegCanc_EC_OSP
[RegCanc OpSeqProblem]
with the error code set to "Operation
Sequence Problem"
Fail_RegCanc_EC_RS
[RegCanc Resource Shortage]
with the error code set to "Resource
Shortage"
Fail_RegCanc_EC_ONS
[RegCanc OpNotSupported]
with the error code set to "Operation
Not Supported"
Fail_RegCanc_EC_PE
[RegCanc ParamError]
with the Error Code set to "Parameter
Error"
Fail_RegCanc_EC_SF
[RegCanc SystemFailure]
with the Error Code set to "System
Failure"
Fail_RegCanc_CD_NU
[RegCanc Denied NotUsed]
Number of denied
with the CancellationDenied set to
"Not Used"
...........................................................................................................................................................................................................................................................
A - 22

270-710-919R6.0
ANSI LM RegNot
DB Name
Description
Fail_RegCanc_CD_MA
[RegCanc Denied MulAccess]
Number of denied
"Multiple Access"
Fail_RegCanc_CD_B
[RegCanc Denied Busy]
Number of denied
"Busy"
Fail_RegCanc_No_RI
[Fail_RegCanc_No_RI]
Number of unsuccessful Registration

Cancellation Invoke send failure
triggered by REGNOT as the routing
information cannot be fetched from
global data.
Table A-15, "ANSI LM RegNot" (A-24) contains Location

Management - RegNot related measurements. This table is called
HCF_MEAS_ANSI_LM_REGNOT in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 23

Table A-15
ANSI LM RegNot
DB Name
Description
Suc_RegNot
[Succ RegNot]
RegistrationNotification processed
Fail_RegNot
[Unsucc RegNot]
RegistrationNotification processed
Fail_RegNot_ADR_DA
[RegNot Delinquent Account]
Number of denied
RegistrationNotification with the error
code set to "Delinquent Account"
Fail_RegNot_ADR_ISN
[RegNot InvalidESN]
Number of denied
code set to "Invalid Serial Number"
Fail_RegNot_ADR_SU
[RegNot StolenUnit]
Number of denied
code set to "Stolen Unit"
Fail_RegNot_ADR_DU
[RegNot DupUnit]
Number of denied
code set to "Duplicate Unit"
Fail_RegNot_ADR_UDN
[RegNot UnassignedDN]
Number of denied
code set to "Unassigned Directory
Number"
Fail_RegNot_ADR_Unspec
[Fail RegNot Unspec]
Number of denied
code set to "Unspecified Reason"
Fail_RegNot_ADR_MA
[RegNot MultipleAccess]
Number of denied
code set to "Multiple Access"
Fail_RegNot_ADR_NA
[RegNot NotAuthorizedMSC]
Number of denied
code set to "Not Authorized for the
MSC"
Fail_RegNot_ADR_MAP
[RegNot MissingAuthenParam]
Number of denied
code set to "Missing Authentication
Parameters"
...........................................................................................................................................................................................................................................................
A - 24

270-710-919R6.0
ANSI SDM QualReq
DB Name
Description
Fail_RegNot_ADR_TTM
[RegNot TermTypMismatch]
Number of denied
code set to "Terminal Type Mismatch"
Fail_RegNot_ARL
[Unsucc RegNot ARL]
RegistrationNotification due to a
negative list entry or the absent of a
positive list entry for the visited
MSCID (Authorized Roaming List)
Suc_RegNot_Relay
[Succ RegNot Relay]
Number of successfully relayed

RegistrationNotification
Fail_RegNot_Relay_RE
[Unsucc RegNot Relay Error]

RegistrationNotification due to
RETURN ERROR
Fail_RegNot_Relay_Timeout
[Unsucc RegNot Relay Timeout]

RegistrationNotification due to
operation timeout
EOI_Map_RegNot
[EOI Map RegNot]
Number of attempts to use Default

Extended Origination Indicator (EOI)
Mapping value when sending
subscriber profile in
Fail_RegNot_Timeout
[Fail_RegNot_Timeout]
Number of times a registration

notification message was processed
unsuccessfully due to access HLR data
time out.
Table A-16, "ANSI SDM QualReq" (A-26) contains Subscriber Data

Management - QualReq related measurements. This table is called
HCF_MEAS_ANSI_QUALREQ in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 25

Table A-16
ANSI SDM QualReq
DB Name
Description
Suc_QualReq
[Succ QualReq]
QualificationRequest processed
Fail_QualReq_ADR_DA
[QualReq Delinquent Account]
QualificationRequest processed with
the error code set to "Delinquent
Account"
Fail_QualReq_ADR_ISN
[QualReq InvalidESN]
the error code set to "Invalid Serial
Number"
Fail_QualReq_ADR_SU
[QualReq StolenUnit]
the error code set to "Stolen Unit"
Fail_QualReq_ADR_DU
[QualReq DuplicateUnit]
the error code set to "Duplicate Unit"
Fail_QualReq_ADR_UDN
[QualReq UnassignedDN]
the error code set to "Unassigned
Directory Number"
Fail_QualReq_ADR_Unspec
[Fail QualReq Unspec]
the error code set to "Unspecified"
Fail_QualReq_ADR_MA
[QualReq MultipleAccess]
the error code set to "Multiple Access"
Fail_QualReq_ADR_NA
[QualReq NotAuthorizedMSC]
the error code set to "Not Authorized
for the MSC"
Fail_QualReq_ADR_MAP
[QualReqMissingAuthenParam]
the error code set to "Missing
Authentication Parameter"
...........................................................................................................................................................................................................................................................
A - 26

270-710-919R6.0
DB Name
Description
Fail_QualReq_ADR_TTM
[QualReq TermTypMismatch]
the error code set to "Terminal Type
Mismatch"
Suc_ServProfReq
[Succ Service Profile]
Number of successful Service Profile

Request processed
Fail_ServProfReq_EC_ONS
[ServProf OpNotSupported]
Number of unsuccessful Service

Profile Request processed with the
error code set to
"OperationNotSupported"
Fail_ServProfReq_EC_PE
[ServProf ParamError]

error code set to "ParameterError"
Fail_ServProfReq_EC_UM
[ServProf UnrecognizedMIN]

error code set to "UnrecognizedMIN"
Fail_ServProfReq_EC_UE
[ServProf UnrecognizedESN]

error code set to "UnrecognizedESN"
EOI_Map_QualReq
[EOI Map QaulReq]
Number of attempts for using Default

EOI Mapping value when sending
QualificationRequest Return Result
Fail_QualReq_Timeout
[Fail_QualReq_Timeout]
Number of unsuccessful Qualification

Request processed due to timeout.
Since Service Profile Request is IS41 Revision A

defined MAP message, unrecognizedIMSI is not supported.
Important!
ANSI SDM QualDir
Table A-17, "ANSI SDM QualDir" (A-28) contains Subscriber Data

Management - QualDir related measurements. This table is called
HCF_MEAS_ANSI_QUALDIR in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 27

Table A-17
ANSI SDM QualDir
DB Name
Description
Suc_QualDir
[Succ QualDir]
QualificationDirective processed
Fail_QualDir_EC_UM
[QualDir UnrecognizedMIN]
QualificationDirective processed with
the error code set to "Unrecognized
MIN"
Fail_QualDir_EC_UI
[QualDir UnrecognizedIMSI]
IMSI"
Fail_QualDir_EC_UE
[QualDir UnrecognizedESN]
ESN"
Fail_QualDir_EC_RS
[QualDir Resource Shortage]
the error code set to "Resource
Shortage"
Fail_QualDir_EC_ONS
[QualDir OpNotSupported]
the error code set to "Operation Not
Supported"
Fail_QualDir_EC_PE
[QualDir Parameter Error]
the error code set to "Parameter Error"
Fail_QualDir_EC_SF
[QualDir System Failure]
the error code set to "System Failure"
Fail_QualDir_EC_UPV
[QualDir UnregParamValue]
Parameter Value"
Fail_QualDir_EC_MP
[QualDir Missing Parameter]
the error code set to "Missing
Parameter"
...........................................................................................................................................................................................................................................................
A - 28

270-710-919R6.0
ANSI CD RoutReq
DB Name
Description
Fail_QualDir_ADR_DA
[QualDir DeliquentAccount]
QualificationDirective with the error
code set to "Delinquent Account"
Fail_QualDir_ADR_SU
[QualDir StolenUnit]
the error code set to "Stolen Unit"
Fail_QualDir_ADR_DU
[QualDir DuplicateUnit]
the error code set to "Duplicate Unit"
Fail_QualDir_ADR_NA
[QualDir NotAuthorizedMSC]
the error code set to "Not Authorized for
this MSC"
EOI_Map_QualDir
[EOI Map QualDir]
Number of attempts for using Default

EOI Mapping value when sending
QualificationDirective Invoke
Fail_QualDir_NO_RI
[Fail_QualDir_NO_RI]
Number of unsuccessful Qualification

Directive Invoke send failure triggered
by eSM provisioning or FEATREQ as
the routing information cannot be
fetched from global data.
Table A-18, "ANSI CD RoutReq" (A-30) contains Call Delivery RoutReq related measurements. This table is called
HCF_MEAS_ANSI_CD_ROUTREQ in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 29

Table A-18
ANSI CD RoutReq
DB Name
Description
Suc_RoutReq
[Succ RoutReq]
Number of successful RoutingRequest

processed
Fail_RoutReq_EC_UM
[RoutReq UnrecognizedMIN]
RoutingRequest processed with the error
code set to "Unrecognized MIN"
Fail_RoutReq_EC_UI
[RoutReq Unrecognized IMSI]
code set to "Unrecognized IMSI"
Fail_RoutReq_EC_UE
[RoutReq UnrecognizedESN]
code set to "Unrecognized ESN"
Fail_RoutReq_EC_RS
[RoutReq Resource Shortage]
code set to "Resource Shortage"
Fail_RoutReq_EC_ONS
[RoutReq OpNotSupported]
code set to "Operation Not Supported"
Fail_RoutReq_EC_PE
[RoutReq ParameterError]
code set to "Parameter Error"
Fail_RoutReq_EC_SF
[RoutReq SystemFailure]
code set to "System Failure"
Fail_RoutReq_EC_UPV
[RoutReq UnregParamValue]
code set to "Unrecognized Parameter
Value"
Fail_RoutReq_EC_MP
[RoutReq Missing Parameter]
code set to "Missing Parameter"
Fail_RoutReq_ADR_Inact
[RoutReq Inactive]
RoutingRequest processed with the
access denied reason set to "Inactive"
Fail_RoutReq_ADR_Busy
[RoutReq Busy]
access denied reason set to "Busy"
...........................................................................................................................................................................................................................................................
A - 30

270-710-919R6.0
ANSI CD LocReq
DB Name
Description
Fail_RoutReq_ADR_NPR
[RoutReq No Page Response]
access denied reason set to "No Page
Response"
Fail_RoutReq_ADR_Una
[RoutReq Unavailable]
access denied reason set to
"Unavailable"
Fail_RoutReq_Reject
[RoutReq Reject]
RoutingRequest REJECT received
Suc_ServiceReq
[Succ Service Request]
Number of successful ServiceRequest

processed
Fail_ServiceReq
[Unsucc Service Request]
Number of unsuccessful ServiceRequest

processed
TLDNs_Received
[TLDNs_Received]
The number of times a TLDN is

received in Routing Request Return
Result successfully
Fail_RoutReq_NO_RI
[Fail_RoutReq_NO_RI]
RoutingRequest Invoke send failure
triggered by LOCREQ as the routing
information could not be fetched from
global data.
Table A-19, "ANSI CD LocReq" (A-32) contains Call Delivery LocReq related measurements. This table is called
HCF_MEAS_ANSI_CD_LOCREQ in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 31

Table A-19
ANSI CD LocReq
DB Name
Description
Suc_LocReq
[Succ LocReq]
Number of successful LocationRequest

processed
Fail_LocReq_EC_ONS
[LocReq OpNotSupported]
LocationRequest processed with the error
code set to "Operation Not Supported"
Fail_LocReq_EC_PE
[LocReq ParameterError]
code set to "Parameter Error"
Fail_LocReq_EC_SF
[LocReq SystemFailure]
code set to "System Failure"
Fail_LocReq_EC_UPV
[LocReq UnregParamValue]
code set to "Unrecognized Parameter
Value"
Fail_LocReq_EC_MP
[LocReq Missing Parameter]
code set to "Missing Parameter"
Total_ModiCSStatusInCD
[Total ModifyCSStatusInCD]
Number of attempts that HLR changes

Mobile CS Status to Inactive during call
delivery when receiving RoutingRequest
INVOKE
Fail_LocReq_ADR_UDN
[LocReq UnassignedDN]
LocationRequest processed with the
access denied reason set to "Unassigned
Directory Number"
Fail_LocReq_ADR_Inact
[LocReq Inactive]
access denied reason set to "Inactive"
Fail_LocReq_ADR_Busy
[LocReq Busy]
access denied reason set to "Busy"
Fail_LocReq_ADR_TD
[LocReq Termination Denied]
access denied reason set to "Termination
Denied"
...........................................................................................................................................................................................................................................................
A - 32

270-710-919R6.0
DB Name
Description
Fail_LocReq_ADR_NPR
[LocReq No Page Response]
access denied reason set to "No Page
Response"
Fail_LocReq_ADR_Una
[LocReq Unavailable]
access denied reason set to "Unavailable"
Fail_LocReq_ADR_RJM
[LocReq Rejected by MS]
access denied reason set to "Service
Rejected by MS"
Fail_LocReq_ADR_RJS
[LocReq Rejected by System]
Rejected by the System"
Fail_LocReq_ADR_STM
[LocReq ServType
Mismatch]
access denied reason set to "Service Type
Mismatch"
Fail_LocReq_ADR_SD
[Fail_LocReq_ADR_SD]
Denied"
Suc_InfoDirAfterCF
[Succ InfoDir After CF]
InformationDirective INVOKE messages
after Call forwarding
Fail_InfoDirAfterCF
[Unsucc InfoDir After CF]
InformationDirective INVOKE messages
after Call forwarding
Total_Blocked_by_ANI
[Total Blocked by ANI]
Number of blocked calls of ANI

screening
Fail_LocReq_Timeout
[Fail_LocReq_Timeout]
Number of unsuccessful Location

Fail_InfoDir_NO_RI
[Fail_InfoDir_NO_RI]
Number of Unsuccessful Information

Directive Invoke send failure triggered
by LOCREQ or TRANUMREQ as the
routing information could not be fetched
from global data.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 33

ANSI CD TransNum
Table A-20, "ANSI CD TransNum" (A-35) contains Call Delivery TRANUMREQ related measurements. This table is called
HCF_MEAS_ANSI_TRANSNUM in MAS database.
...........................................................................................................................................................................................................................................................
A - 34

270-710-919R6.0

Table A-20
ANSI CD TransNum
DB Name
Description
Fail_TraNum_EC_PE
[TraNum ParameterError]
TransferToNumberRequest
"Parameter error"
Fail_TraNum_EC_ONS
[TraNum OpNotSupported]
"Operation Not Supported"
Fail_TraNum_EC_UE
[TraNum UnrecognizedESN]
"Unrecognized ESN"
Fail_TraNum_EC_UI
[TraNum UnrecognizedIMSI]
"Unrecognized IMSI"
Fail_TraNum_EC_UM
[TraNum UnrecognizedMI]
"Unrecognized MIN"
Suc_TraNum
[Succ TraNum]
processed
Fail_TraNum_AcD_NoPageRsp
[TraNum AccDeniedNoPageRsp]
processed - AccessDeniedReason is
NoPageResponse
Fail_TraNum_AcD_Busy
[TraNum AccDeniedBusy]
processed - AccessDeniedReason is
Busy
Fail_TraNum_EC_PE[Fail_TraNu
m_EC_PE]
"Parameter Error"
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 35
ANSI CD TransNum2
DB Name
Description
Fail_TraNum_Timeout
[Fail_TraNum_Timeout]
TransferToNumber Request
Table A-21, "ANSI CD TransNum2" (A-37) contains Call Delivery TRANUMREQ related measurements. This table is called
HCF_MEAS_ANSI_TRANSNUM2 in MAS database.
...........................................................................................................................................................................................................................................................
A - 36

270-710-919R6.0

Table A-21
ANSI AC
ANSI CD TransNum2
DB Name
Description
Total_TraNum_RR_NU
[TraNum RedirRsn NotUsed]
Number of TransferToNumberRequest
with redirection reason set to "Not
Used"
Total_TraNum_RR_NA
[TraNum RedirRsn NoAnswer]
with redirection reason set to "No
Answer"
Total_TraNum_RR_U
[TraNum RedirRsn Uncond]
with redirection reason set to
"Unconditional"
Total_TraNum_RR_B
[TraNum RedirRsn Busy]
with redirection reason set to "Busy"
Total_TraNum_RR_NPR
[TraNum RedirRsn NoPageRsp]
with redirection reason set to "No
Page Response"
Total_TraNum_RR_Una
[TraNum RedirRsn Unavail]
"Unavailable"
Total_TraNum_RR_UnR
[TraNum RedirRsn UnRoute]
"Unroutable"
Total_TraNum_RR_CA
[TraNum RedirRsn CallAcept]
with redirection reason set to "Call
Accepted"
Total_TraNum_RR_CR
[TraNum RedirRsnCallRefuse]
with redirection reason set to "Call
Refused"
Table A-22, "ANSI AC" (A-38) contains ANSI authentication related

measurements. This table is called HCF_MEAS_ANSI_AC in MAS
database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 37

Table A-22
ANSI AC
DB Name
Description
HSA_AuthFailOverride
[HSA Auth Fail Override]
Number of global authentication

failure overriding in the Home
Service Area (HSA) of a mobile
TSA_AuthFailOverride
[TSA Auth Fail Override]

failure overriding in the Traveller
Service Area (TSA) of a mobile
RSA_AuthFailOverride
[RSA Auth Fail Override]

failure overriding in the Roamer
Service Area (RSA) of a mobile
HSA_AuthFailAccessDenied
[HSA Auth Fail Access Denied]
Number of times global

authentication failures occurred for
a mobile in its HSA where access
to the network was denied
TSA_AuthFailAccessDenied
[TSA_AuthFail Access Denied]

a mobile in its TSA when access to
the network was denied
RSA_AuthFailAccessDenied
[RSA Auth Fail Access Denied]

a mobile in its RSA where access
to the network was denied
HSA_AuthFailAuthrMismatch
[HSA Auth Fail AUTHR Mismatch]

requests failures due to AUTHR
mismatch in a mobiles HSA
(failures not overridden)
HSA_AuthFailRandcMismatch
[HSA Auth Fail RANDC Mismatch]

requests failures due to RANDC
mismatch in a mobiles HSA
TSA_AuthFailAuthrMismatch
[TSA Auth Fail AUTHR Mismatch]

mismatch in a mobiles TSA
TSA_AuthFailRandcMismatch
[TSA Auth Fail RANDC Mismatch]

mismatch in a mobiles TSA
...........................................................................................................................................................................................................................................................
A - 38

270-710-919R6.0
ANSI AC2
DB Name
Description
RSA_AuthFailAuthrMismatch
[RSA Auth Fail AUTHR Mismatch]

mismatch in a mobiles RSA
RSA_AuthFailRandcMismatch
[RSA Auth Fail RANDC Mismatch]

mismatch in a mobiles RSA
Suc_GlobalChallenge
[Suc Global Challenge]
Number of successful global

challenges authentication attempts
Fail_GlobalChallenge
[Fail Global Challenge]
Number of unsuccessful global

challenges authentication attempts
Fail_AUTHREQ_Timeout
[Fail_AUTHREQ_Timeout]
Number of unsuccessful Auth

Fail_AUTHDIR_Relay_NORI
[Fail_AUTHDIR_Relay_NORI]
Authentication Directive Invoke
relay send failure as the routing
information could not be fetched
from global data.
Fail_AUTHDIR_OTASP_NORI
[Fail_AUTHDIR_OTASP_NORI]
Authentication Directive Invoke
triggered by OTASPREQ send
failure as the routing information
could not be fetched from global
data.
Table A-23, "ANSI AC2" (A-40) contains ANSI authentication related

measurements. This table is called HCF_MEAS_ANSI_AC2 in MAS
database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 39

Table A-23
ANSI AC2
DB Name
Description
IndeterminateAutoSSDUpd
[Indeterminate Auto SSD Upd]
Number of automatic SSD updates

that were not attempted or failed to
respond
IndeterminateManSSDUpd
[Indeterminate Manual SSD Upd]
Number of manual SSD updates that

were not attempted or failed to
respond
Suc_AutoSSDUpd
[Suc Auto SSD Upd]
Number of successful automatic SSD

updates attempts
Fail_AutoSSDUpd
[Fail Auto SSD Upd]
Number of automatic SSD updates

attempts that failed
Fail_ManSSDUpd
[Fail_ManSSDUpd]
Number of manual SSD updates

Suc_ManSSDUpd
[Suc Manual SSD Upd]
Number of successful manual SSD

updates attempts
Suc_AkeyExchange
[Suc Akey Exchange]
Number of successful A-Key

exchange attempts
Fail_AkeyExchange
[Fail Akey Exchange]
Number of A-Key exchange attempts

that failed
Suc_AuthMsgRelay2AC
[Suc Auth Msg Relay2AC]
Total number of successful relays of

authentication messages from HLR to
external AC
Fail_AuthMsgRelay2AC
[Fail Auth Msg Relay2AC]
Total number of unsuccessful relays

of authentication messages from HLR
to external AC
Fail_AuthMsgTimeout
[Fail Auth Msg Time-out]
Total number of timeout conditions

happened during Authentication
message processing
IndeterminateUniChallenge
[Indeterminate UniChallenge]
Number of unique challenges that

were not attempted or failed to
respond
Suc_UniChallenge
[Suc UniChallenge]
Number of successful unique

challenges attempts
Fail_UniChallenge
[Fail UniChallenge]
Number of unique challenges

...........................................................................................................................................................................................................................................................
A - 40

270-710-919R6.0
ANSI OTAF
DB Name
Description
SSDUpd_Fail_Exceed[SSDUpd_
Fail_Exceed]
Number of times that the SSD update

failure count exceeds the defined
count.
Table A-24, "ANSI OTAF" (A-42) contains OTAF related

measurements. This table is called HCF_MEAS_ANSI_OTAF in MAS
database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 41

Table A-24
ANSI OTAF
DB Name
Description
Suc_GenPrimeKey
[Suc Generate PrimeKey]
Number of successful attempts to

generate prime key
Fail_GenPrimeKey
[Fail Generate PrimeKey]
Number of unsuccessful attempts

to generate prime key
Suc_GenPubEncryption
[Suc Generate PubEncryption]

generate public encryption values
Fail_GenPubEncryption
[Fail Generate PubEncryption]

to generate public encryption
values
Suc_GenAkeyMSPartialkey
[Suc Generate Akey MSPartialkey]

generate A-Key and MSPartialKey
Fail_GenAkeyMSPartialkey
[Fail Generate Akey MSPartialkey]

to generate A-Key and
MSPartialKey
Suc_SSDUpd_AkeyExchg
[Suc SSDUpd in AkeyExchg]

update SSD as a part of A-Key
exchange procedure
Fail_SSDUpd_AkeyExchg
[Fail SSDUpd in AkeyExchg]

to update SSD as a part of A-Key
exchange procedure
Suc_CommitAkey_AkeyExchg
[Suc Commit Akey in AkeyExchg]

commit A-Key as a part of A-Key
exchange procedure
Fail_CommitAkey_AkeyExchg
[Fail Commit Akey in AkeyExchg]

to commit A-Key as a part of AKey exchange procedure
Suc_RelResource_AkeyExchg
[Suc RelResource in AkeyExchg]
Number of Release Resource that

were executed successfully as a
part of A-Key exchange operation
by AC
Suc_AkeyExchange
[Suc_AkeyExchange]
Number of successful A-Key

exchange attempts
Fail_AkeyExchange
[Fail_AkeyExchange]
Number of A-Key Exchange

...........................................................................................................................................................................................................................................................
A - 42

270-710-919R6.0

ANSI_NPA
Table A-25, "ANSI_NPA" (A-44) contains Split NPA related

measurements. This table is called HCF_MEAS_ANSI_NPA in MAS
database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 43

Table A-25
ANSI_NPA
DB Name
Description
Suc_SplitNPA_LocReq
[Suc SplitNPA LocReq]
Number of successful Split National

Destination Code (NDC)/Numbering
Plan Area (NPA) check performed for
LocationRequest message
Fail_SplitNPA_LocReq
[Fail SplitNPA LocReq]
Number of unsuccessful Split NDC/NPA

check performed for LocationRequest
message
Suc_SplitNPA_Search
[Suc SplitNPA Search]
Number of successful Split NDC/NPA

check performed for Search message
Fail_SplitNPA_Search
[Fail SplitNPA Search]

check performed for Search message
Suc_SplitNPA_AuthReq
[Suc SplitNPA AuthReq]

check performed for
AuthenticationRequest message
Fail_SplitNPA_AuthReq
[Fail SplitNPA AuthReq]

check performed for
AuthenticationRequest message
Suc_SplitNPA_BSCHALL
[Suc SplitNPA BSCHALL]

check performed for
BaseStationchallenge message
Fail_SplitNPA_BSCHALL
[Fail SplitNPA BSCHALL]

check performed for
BaseStationchallenge message
Suc_SplitNPA_AFReport
[Suc SplitNPA AFReport]

check performed for
AuthenticationFailureReport message
Fail_SplitNPA_AFReport
[Fail SplitNPA AFReport]

check performed for
AuthenticationFailureReport message
Suc_SplitNPA_ASReport
[Suc SplitNPA ASReport]

check performed for
AuthenticationStatusReport message
Fail_SplitNPA_ASReport
[Fail SplitNPA ASReport]

check performed for
AuthenticationStatusReport message
...........................................................................................................................................................................................................................................................
A - 44

270-710-919R6.0
ANSI_NPA2
DB Name
Description
Suc_SplitNPA_FeatReq
[Suc SplitNPA FeatReq]

check performed for FeatureRequest
message
Fail_SplitNPA_FeatReq
[Fail SplitNPA FeatReq]

check performed for FeatureRequest
message
Suc_SplitNPA_MSInactive
[Suc SplitNPA MSInactive]

check performed for MSInactive message
Fail_SplitNPA_MSInactive
[Fail SplitNPA MSInactive]

check performed for MSInactive message
Suc_SplitNPA_ServProReq
[Suc_SplitNPA_ServProReq]
Number of Successful Split NDC/NPA

service Checking performed for
ServiceProfileRequest message
Fail_SplitNPA_ServProReq[
Fail_SplitNPA_ServProReq]

Checking performed for
ServiceProfileRequest message
Suc_SplitNPA_SurvRequest[
Suc_SplitNPA_SurvRequest]

SurveillanceRequest message
Fail_SplitNPA_SurvRequest[
Fail_SplitNPA_SurvRequest]

SurveillanceRequest message
Table A-26, "ANSI_NPA2" (A-46) contains Split NPA related

measurements. This table is called HCF_MEAS_ANSI_NPA2 in MAS
database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 45

Table A-26
ANSI_NPA2
DB Name
Description
Suc_SplitNPA_OrReq
[Suc SplitNPA OrReq]

check performed for OriginationRequest
message
Fail_SplitNPA_OrReq
[Fail SplitNPA OrReq]

check performed for OriginationRequest
message
Suc_SplitNPA_OTASPReq
[Suc SplitNPA OTASPReq]

check performed for Over-The-Air
Service Provisioning (OTASP) Request
message
Fail_SplitNPA_OTASPReq
[Fail SplitNPA OTASPReq]

check performed for OTASP Request
message
Suc_SplitNPA_QualReq
[Suc SplitNPA QualReq]

check performed for
QualificationRequest message
Fail_SplitNPA_QualReq
[Fail SplitNPA QualReq]

check performed for
QualificationRequest message
Suc_SplitNPA_RegNot
[Suc SplitNPA RegNot]

check performed for
RegistrationNotification message
Fail_SplitNPA_RegNot
[Fail SplitNPA RegNot]

check performed for
RegistrationNotification message
Suc_SplitNPA_TranumReq
[Suc SplitNPA TranumReq]

check performed for
TransferToNumberRequest message
Fail_SplitNPA_TranumReq
[Fail SplitNPA TranumReq]

check performed for
TransferToNumberRequest message
Suc_SplitNPA_SMSREQ
[Suc_SplitNPA_SMSREQ]

check performed for SMSRequest
Invokemessage
...........................................................................................................................................................................................................................................................
A - 46

270-710-919R6.0
DB Name
Description
Fail_SplitNPA_SMSREQ
[Fail_SplitNPA_SMSREQ]

check performed for SMSRequest Invoke
message
Suc_SplitNPA_SMSNOT
[Suc_SplitNPA_SMSNOT]

check performed for SMSNotification
Invoke message
Fail_SplitNPA_SMSNOT
[Fail_SplitNPA_SMSNOT]

check performed for SMSNotification
Invoke message
Suc_SplitNPA_POSREQ
[Suc_SplitNPA_POSREQ]

check performed for POSREQ message
Fail_SplitNPA_POSREQ
[Fail_SplitNPA_POSREQ]

check performed for POSREQ message
Suc_SplitNPA_LPREQ
[Suc_SplitNPA_LPREQ]

check performed for LPREQ message
Fail_SplitNPA_LPREQ
[Fail_SplitNPA_LPREQ]

check performed for LPREQ message
Suc_SplitNPA_SNREQ
[Suc_SplitNPA_SNREQ]

check performed for SNREQ message
Fail_SplitNPA_SNREQ
[Fail_SplitNPA_SNREQ]

check performed for SNREQ message
This section lists ANSI per NE measurement tables for 50 NEs. They
are called HCF_MEAS_ANSI_NE1~HCF_MEAS_ANSI_NE50 in
MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 47

Table A-27
DB Name
Description
ENABLE
[ENABLE]
To sync the global data with measlog
SUC_REGNOT
[SUC_REGNOT]
per-NE measurement for successful

RegistrationNotification Invoke
(REGNOT)
UNSUC_REGNOT
[UNSUC_REGNOT]
per-NE measurement for unsuccessful

REGNOT
UNSUC_REGNOT_DA
[UNSUC_REGNOT_DA]

REGNOT with
AuthorizationDeniedReason set to
"Delinquent Account"
UNSUC_REGNOT_ISN
[UNSUC_REGNOT_ISN]
per-NE measurement of unsuccessful

RETNOT with
"Invalid Serial Number"
UNSUC_REGNOT_SU
[UNSUC_REGNOT_SU]

REGNOT with
"Stolen Unit"
UNSUC_REGNOT_DU
[UNSUC_REGNOT_DU]

REGNOT with
"Duplicate Unit"
UNSUC_REGNOT_UDN
[UNSUC_REGNOT_UDN]

REGNOT with
"Unassigned DN"
UNSUC_REGNOT_NA
[UNSUC_REGNOT_NA]

REGNOT with
AuthorizationDeniedReason set to "Not
Authorized for the MSC"
UNSUC_REGNOT_MAP
[UNSUC_REGNOT_MAP]

REGNOT with
"Missing Authentication Parameter"
...........................................................................................................................................................................................................................................................
A - 48

270-710-919R6.0
DB Name
Description
UNSUC_REGNOT_TTM
[UNSUC_REGNOT_TTM]

REGNOT with
"Terminal Type Mismatch"
SUC_REGCANC
[SUC_REGCANC]

UNSUC_REGCANC
[UNSUC_REGCANC]

RegistrationCancellation processed due
to not receiving a good return result
REGCANC_TIMEOUT
[REGCANC_TIMEOUT]
per-NE measurement for timeout

SUC_MSINACT
[SUC_MSINACT]

MSInactive processed
UNSUC_MSINACT
[UNSUC_MSINACT]

MSInactive processed
SUC_LOCREQ
[SUC_LOCREQ]

LocationRequest processed
UNSUC_LOCREQ_ONS
[UNSUC_LOCREQ_ONS]

LocationRequest with error code set to
UNSUC_LOCREQ_PE
[UNSUC_LOCREQ_PE]

"Parameter Error"
UNSUC_LOCREQ_SF
[UNSUC_LOCREQ_SF]

"System Failure"
UNSUC_LOCREQ_UPV
[UNSUC_LOCREQ_UPV]

"Unrecognized Parameter Value"
UNSUC_LOCREQ_MP
[UNSUC_LOCREQ_MP]

"Missing Parameter"
SUC_ROUTREQ
[SUC_ROUTREQ]

RoutingRequest processed
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 49
DB Name
Description
UNSUC_ROUTREQ_UM
[UNSUC_ROUTREQ_UM]

RoutingRequest with error code set to
"Unrecognized MIN"
UNSUC_ROUTREQ_UI
[UNSUC_ROUTREQ_UI]

"Unrecognized IMSI"
UNSUC_ROUTREQ_UE
[UNSUC_ROUTREQ_UE]

"Unrecognized ESN"
UNSUC_ROUTREQ_RS
[UNSUC_ROUTREQ_RS]

"Source Shortage"
UNSUC_ROUTREQ_ONS
[UNSUC_ROUTREQ_ONS]

UNSUC_ROUTREQ_PE
[UNSUC_ROUTREQ_PE]

"Parameter Error"
UNSUC_ROUTREQ_SF
[UNSUC_ROUTREQ_SF]

"System Failure"
UNSUC_ROUTREQ_UPV
[UNSUC_ROUTREQ_UPV]

UNSUC_ROUTREQ_MP
[UNSUC_ROUTREQ_MP]

"Missing Parameter"
Route_Req_Busy
[Route_Req_Busy]
per-NE measurement for RoutingRequest

busy
Route_Req_No_Page
[Route_Req_No_Page]

No_Page
Route_Req_Unavailable
[Route_Req_Unavailable]

Unavailable
Route_Req_Inactive
[Route_Req_Inactive]

Inactive
...........................................................................................................................................................................................................................................................
A - 50

270-710-919R6.0
DB Name
Description
SUC_TRANUM
[SUC_TRANUM]

TransferToNumberRequest processed
UNSUC_TRANUM_ONS
[UNSUC_TRANUM_ONS]

with error code set to "Operation Not
Supported"
UNSUC_TRANUM_SF
[UNSUC_TRANUM_SF]

with error code set to "System Failure"
UNSUC_TRANUM_UM
[UNSUC_TRANUM_UM]

with error code set to "Unrecognized
MIN"
UNSUC_TRANUM_UI
[UNSUC_TRANUM_UI]

IMSI"
UNSUC_TRANUM_UE
[UNSUC_TRANUM_UE]

ESN"
UNSUC_TRANUM_PE
[UNSUC_TRANUM_PE]

with error code set to "Parameter Error"
UNSUC_INFODIR_ACF
[UNSUC_INFODIR_ACF]

InformationDirective Invoke message
after Call Forwarding
SUC_INFODIR_ACF
[SUC_INFODIR_ACF]

InformationDirective Invoke message
after Call Forwarding
SUC_QUALREQ
[SUC_QUALREQ]

QualificationRequest Invoke message
UNSUC_QUALREQ
[UNSUC_QUALREQ]
per-NE measurement for Denied

QualificationRequest
SUC_QUALDIR
[SUC_QUALDIR]

QualificationDirective Invoke
(QUALDIR) processed
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 51
DB Name
Description
UNSUC_QUALDIR_UM
[UNSUC_QUALDIR_UM]

QUALDIR with error code set to
"Unrecognized MIN"
UNSUC_QUALDIR_UI
[UNSUC_QUALDIR_UI]

"Unrecognized IMSI"
UNSUC_QUALDIR_UE
[UNSUC_QUALDIR_UE]

"Unrecognized ESN"
UNSUC_QUALDIR_RS
[UNSUC_QUALDIR_RS]

QUALDIR with error code set to "Rource
Shortage"
UNSUC_QUALDIR_ONS
[UNSUC_QUALDIR_ONS]

UNSUC_QUALDIR_PE
[UNSUC_QUALDIR_PE]

"Parameter Error"
UNSUC_QUALDIR_SF
[UNSUC_QUALDIR_SF]

"System Failure"
UNSUC_QUALDIR_UPV
[UNSUC_QUALDIR_UPV]

UNSUC_QUALDIR_MP
[UNSUC_QUALDIR_MP]

"Missing Parameter"
HSA_AUTH_F_DENY
[HSA_AUTH_F_DENY]
per-NE measurement for access denied in

HSA due to authentication failure
HSA_AUTH_F_ALW
[HSA_AUTH_F_ALW]
per-NE measurement for authentication

failure overriding in HSA
HSA_AUTH_F_AUTHR
[HSA_AUTH_F_AUTHR]
per-NE measurement for global

authentication failure in HSA due to
AUTHR mismatch
TSA_AUTH_F_ALW
[TSA_AUTH_F_ALW]

failure overriding in TSA
...........................................................................................................................................................................................................................................................
A - 52

270-710-919R6.0
DB Name
Description
TSA_AUTH_F_DENY
[TSA_AUTH_F_DENY]

TSA due to authentication failure
RSA_AUTH_F_ALW
[RSA_AUTH_F_ALW]

failure overriding in RSA
RSA_AUTH_F_DENY
[RSA_AUTH_F_DENY]

RSA due to authentication failure
INDETER_MSSDUPD
[INDETER_MSSDUPD]
per-NE measurement for manual SSD

update that is not attempted or failed to
respond
INDETER_UNICHALL
[INDETER_UNICHALL]
per-NE measurement for UNICHALL

that not attempted or failed to respond
SUCC_ASSDUPD
[SUCC_ASSDUPD]
per-NE measurement for successful auto

SSD update
INDETER_ASSDUPD
[INDETER_ASSDUPD]
per-NE measurement for auto SSD

update that is not attempted or failed to
respond
UNSUC_ASSDUPD
[UNSUC_ASSDUPD]

auto SSD update
SUCC_MSSDUPD
[SUCC_MSSDUPD]

manual SSD update
UNSUC_MSSDUPD
[UNSUC_MSSDUPD]

manual SSD update
SUCC_UNICHALL
[SUCC_UNICHALL]

unique challenge
UNSUC_UNICHALL
[UNSUC_UNICHALL]

unique challenge
SUCC_GCHALL
[SUCC_GCHALL]

global challenge
UNSUC_GCHALL
[UNSUC_GCHALL]

global challenge
SSDUpd_Fail_Exceed
[SSDUpd_Fail_Exceed]
per-NE measurement for failure counter

that exceeds the allowed value in SSD
update
UNSUC_AKEY_EXCHG
[UNSUC_AKEY_EXCHG]
per-NE measurement for unsuccessful Akey exchange
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 53
DB Name
Description
Total_RegCancRe
[Total_RegCancRe]
per-NE measurements for all

RegistrationCancellation retries
SUC_REGCANG_RETRY
[SUC_REGCANG_RETRY]

RegistrationCancellation retry
Fail_RegCancRe_Timeout
[Fail_RegCancRe_Timeout]

RegistrationCancellation message retries
due to timeout
Fail_RegCancRe_notTimeout[
Fail_RegCancRe_notTimeout]

RegistrationCancellation message retries
due to any reason other than the timeout
ONE_NUMBER_SERV
[ONE_NUMBER_SERV]
per-NE measurement for "One Number

per Service" call termination
TWO_STAGE_DIAL
[TWO_STAGE_DIAL]
per-NE measurement for "Two Stage

Dialing" call termination
PREARRANGED
[PREARRANGED]
per-NE measurement for pre-arranged

call termination
ANI_screen
[ANI_screen]
per-NE measurement for blocked call for

ANI screening
Succ_RelayORREQ
[Succ_RelayORREQ]
per-NE measurement for successfully

relaying the OriginationRequest
Unsuc_RelayORREQ
[Unsuc_RelayORREQ]
per-NE measurement for unsuccessfully

relaying the OriginationRequest
Succ_RelayRUIDIR
[Succ_RelayRUIDIR]

relaying the
Unsuc_RelayRUIDIR
[Unsuc_RelayRUIDIR]

relaying the
Succ_RUI_Dir
[Succ_RUI_Dir]

RUIDIR
UnSucc_RUI_Dir
[UnSucc_RUI_Dir]

RUIDIR
Succ_RelayFEATREQ
[Succ_RelayFEATREQ]

relaying the FeatureRequest
...........................................................................................................................................................................................................................................................
A - 54

270-710-919R6.0
DB Name
Description
Unsuc_RelayFEATREQ
[Unsuc_RelayFEATREQ]

relaying the FeatureRequest
Succ_Feat_Req
[Succ_Feat_Req]

FeatureRequest processed
UnSucc_Feat_Req
[UnSucc_Feat_Req]
per-NE measurement for times that a

FeatureRequest RETURN RESULT
message was unsuccessfully sent or a
RETURN ERROR was returned
EOI_REGNOT
[EOI_REGNOT]
per-NE measurement for attempts to use

Default EOI Mapping value when
sending subscriber profile in
EOI_QUALREQ
[EOI_QUALREQ]

EOI_QUALDIR
[EOI_QUALDIR]

QualificationDirective
Succ_ORREQ
[Succ_ORREQ]

OriginationRequest
Unsuc_ORREQ
[Unsuc_ORREQ]

OriginationRequest
Succ_RelayPosReq
[Succ_RelayPosReq]

relayed PositionRequest
Unsuc_RelayPosReq
[Unsuc_RelayPosReq]

relayed PositionRequest
Succ_SNREQ
[Succ_SNREQ]

StatusNotificationRequest
Unsuc_SNREQ_MS
[Unsuc_SNREQ_MS]

Unsuc_SNREQ_RS
[Unsuc_SNREQ_RS]

...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 55
DB Name
Description
Unsuc_SNREQ_ONS
[Unsuc_SNREQ_ONS]

Unsuc_SNREQ_MP
[Unsuc_SNREQ_MP]

Unsuc_SNREQ_PE
[Unsuc_SNREQ_PE]

Unsuc_SNREQ_SF
[Unsuc_SNREQ_SF]

Unsuc_SNREQ_UPV
[Unsuc_SNREQ_UPV]

code as "UnrecognizedParameterValue"
Unsuc_SNREQ_UM
[Unsuc_SNREQ_UM]

Stray_MSInactive
[Stray_MSInactive]
per-NE measurement for stray

MSInactive
TLDNs_Received
[TLDNs_Received]
per-NE measurement for times that a

TLDN is received in Routing Request
Return Result successfully
Succ_Serv_Req
[Succ_Serv_Req]

ServiceRequest processed
UnSucc_Serv_Req
[UnSucc_Serv_Req]

ServiceRequest processed
UNSUC_SR_TRANS
[UNSUC_SR_TRANS]
Number of platform indicates that

message cannot be transmitted because
S&R is required while the message
destination cannot support S&R.
SUC_PARM_SUPP
[SUC_PARM_SUPP]
Number of messages that have been

successfully suppressed for some
parameters.
...........................................................................................................................................................................................................................................................
A - 56

270-710-919R6.0

ANSI_OVLD_DROP
Table A-28, "ANSI_OVLD_DROP" (A-57) contains all the ANSI41

messages dropped for SSN overload. This table is called
HCF_MEAS_ANSI_OVLD_DROP in MAS database.
Table A-28
ANSI_MISC
ANSI_OVLD_DROP
DB Name
Description
TOTAL_MSG_COUNT
[TOTAL_MSG_COUNT]
Total number of dropped msg due to

overload
MSG_COUNT_OVLD1
[MSG_COUNT_OVLD1]

overload level 1
MSG_COUNT_OVLD2
[MSG_COUNT_OVLD2]

overload level 2
MSG_COUNT_OVLD3
[MSG_COUNT_OVLD3]

overload level 3
MSG_COUNT_OVLD4
[MSG_COUNT_OVLD4]

overload level 4
Table A-29, "ANSI_MISC" (A-57) contains ANSI miscellaneous

measurements. This table is called HCF_MEAS_ANSI_MISC in MAS
database.
Table A-29
ANSI_MISC
DB Name
Description
WINCAP_EXPANSION
[WINCAP_EXPANSION]
Number of WINCAP Expansion

performed. This measurement is
pegged when WE is successfully
performed
TRIGGER_DISCRIMIN
[TRIGGER_DISCRIMIN]
Number of Trigger Discrimination

performed.This measurement is
pegged when TD is successfully
performed
Suc_SMDPP
[Suc_SMDPP]
Counter of successful SMDPP
Fail_SMDPP
[Fail_SMDPP]
Counter of unsuccessful SMDPP
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 57
Invalid_ESN_MEID
[Invalid_ESN_MEID]
Number of subscriber's ESN/MEID

is in the invalid ESN/MEID table
after perform the Invalid ESN/MEID
check
...........................................................................................................................................................................................................................................................
A - 58

270-710-919R6.0

............................................................................................................................................................................................................................................................
Table A-30, "HCF Service Measurements" (A-60) stores the

measurements for some of UMTS services. This table is called
HCF_MEAS_SERVICE in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 59

Table A-30
DB Name
Description
Fail_ReRegister_HPLMN
[Fail Re-register HPLMN]
The number of times a location update is

unsuccessful when mobile subscriber
attempts to register in Home Public Land
Mobile Network (HPLMN) after roaming
Fail_Roam
[Unsuccessful Roaming]
The number of times mobile subscribers

unsuccessfully complete location update
when attempting roaming outside their
HPLMN
MAP_Close_Recvd
[MAP Close Received]
Number of MAP_Close indications

received
MAP_Close_Sent
[MAP Close Sent]
Number of Map_Close Requests sent
MAP_Notice_Recvd
[MAP Notice Received]
Number of MAP_Notice indications

received
MAP_Open_Recvd
[MAP Open Received]
Number of MAP_Open indications

received
MAP_Open_Sent
[MAP Open Sent]
Number of MAP_Open requests sent
MAP_Open_TO
[MAP Open TO]
Number of timeouts while attempting to

send a MAP message, per indication
MAP_P_Abort_Recvd
[MAP P Abort Received]
Number of Map_P_Abort indications

received
MAP_P_Abort_Sent
[MAP P Abort Sent]
Number of Map_P_Abort indications

sent
MAP_U_Abort_Recvd
[MAP U Abort Received]
Number of MAP_U_Abort indications

received
ReRegister_HPLMN
[Re-register HPLMN]
The number of times a successful

location update is completed when
mobile subscriber registers in HPLMN
after roaming
Suc_LU_HPLMN
[Suc_LU_HPLMN]
Number of successful location update

messages for subscribers in HPLMN
UnSuc_LU_HPLMN
[UnSuc_LU_HPLMN]
Number of unsuccessful location update

messages for subscribers in HPLMN
...........................................................................................................................................................................................................................................................
A - 60

270-710-919R6.0
BASIC_SERVICE1
DB Name
Description
Suc_Roam
[Successful Roaming]

successfully completed location update
procedure when it was roaming outside
its HPLMN
UnSuc_SRI_Overload
[UnSuc_SRI_Overload]
Number of unsuccessful mobile

termination call requests due to overload
condition in both Circuit Switched (CS)
domain and Packet Switched (PS)
domain
UnSuc_SRI_Overload_CS
[UnSuc_SRI_Overload_CS]

condition in CS domain
UnSuc_SRI_Overload_PS
[UnSuc_SRI_Overload_PS]

condition in PS domain
UnSuc_UL_Overload
[UnSuc_UL_Overload]
Number of unsuccessful location updates

due to overload condition in both CS
domain and PS domain
UnSuc_UL_Overload_CS
[UnSuc_UL_Overload_CS]

due to overload condition in CS domain
UnSuc_UL_Overload_PS
[UnSuc_UL_Overload_PS]

due to overload condition in PS domain
UnSuc_Auc_Overload
[UnSuc_Auc_Overload]
Number of times unsuccessful

SendParameters (v1) and
SendAuthenticationInfo (v2) was
processed due to the overload condition
UnSuc_SMS_Overload
[UnSuc_SMS_Overload]
Number of times unsuccessful SRIforSM

was processed due to the overload
condition
Table A-31, "BASIC_SERVICE1" (A-62) contains the number of

times each Basic Service is requested during call terminations. This
table is called as HCF_MEAS_BASIC_SERVICE1 in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 61

Table A-31
BASIC_SERVICE1
DB Name
Description
Basic_Serv_TS11
[Basic_Serv_TS11]
The number of times TS11 is requested

during call terminations
Basic_Serv_TS21
[Basic_Serv_TS21]

Basic_Serv_TS22
[Basic_Serv_TS22]

Basic_Serv_TS23
[Basic_Serv_TS23]

Basic_Serv_TS61
[Basic_Serv_TS61]

Basic_Serv_TS62
[Basic_Serv_TS62]

Basic_Serv_BS20
[Basic_Serv_BS20]
The number of times BS20 is requested

Basic_Serv_BS21
[Basic_Serv_BS21]

Basic_Serv_BS22
[Basic_Serv_BS22]

Basic_Serv_BS23
[Basic_Serv_BS23]

Basic_Serv_BS24
[Basic_Serv_BS24]

Basic_Serv_BS25
[Basic_Serv_BS25]

Basic_Serv_BS26
[Basic_Serv_BS26]

Basic_Serv_BS30
[Basic_Serv_BS30]

Basic_Serv_BS31
[Basic_Serv_BS31]

Basic_Serv_BS32
[Basic_Serv_BS32]

Basic_Serv_BS33
[Basic_Serv_BS33]

...........................................................................................................................................................................................................................................................
A - 62

270-710-919R6.0
Authentication
DB Name
Description
Basic_Serv_BS34
[Basic_Serv_BS34]

Basic_Serv_BS70
[Basic_Serv_BS70]

Basic_Serv_BS27
[Basic_Serv_BS27]

Basic_Serv_BS37
[Basic_Serv_BS37]

Table A-32, "Authentication" (A-64) stores the measurements for

UMTS authentication. This table is called
HCF_MEAS_AUTHENTICATION.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 63

Table A-32
Authentication
DB Name
Description
Cr_Au_Trips_Snt
[Create Au Triplets Snt]
The total number of create (i.e.

previously unused) authentication triplets
that are sent to VLR
Emp_Au_Trip_Snt
[Empty Au Triplets Sent]
The number of times empty

authentication triplets that are sent by the
authentication center to VLR
Emp_UAu_Vctrs_Snt
[Empty UMTS AU Vctrs Snt]
The number of times empty UMTS

authentication vectors that are sent to
VLR
Emp_UFAu_Vtrs_Snt
[Empty UMTS Fold AU
Vctrs Snt]
The number of empty UMTS folded

Release 98 and earlier VLRs for UMTS
subscribers
GSM_Sub_Auth
[GSM Subscribers Au]

that are successfully authenticated in
GSM network
GSM_Sub_Not_Auth
[GSM Subscribers Not Au]

that are unsuccessfully authenticated in
GSM network
NEmp_UAu_Vctrs_Snt
[Non-Emp UMTS AU Vctrs
Snt]
The number of times non-empty UMTS

authentication vectors that are sent
NEmp_UFAu_Vtrs_Snt
[Nemp UMTS Fold AU Vtr
Snt]
The number of non-empty UMTS folded

Release 98 and earlier VLRs for UMTS
subscribers
UMTS_Sub_Auth
[UMTS Subscribers Au]

that are successfully authenticated in
UMTS network
UMTS_Sub_Not_Auth
[UMTS Subscriber Not Au]

that are unsuccessfully authenticated in
the UMTS network
V3_SAI_ReSyn
[V3_SAI_ReSyn]
The number of times v3

SendAuthenticationInfo with the resynchronization parameter that is
received
...........................................................................................................................................................................................................................................................
A - 64

270-710-919R6.0

SS Activations
Table A-33, "SS Activations" (A-66) stores the measurements for

UMTS supplementary services activations. This table is called
HCF_MEAS_SS_ACTIVATIONS in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 65

Table A-33
SS Activations
DB Name
Description
SS_Act_BAIC
[SS Activations BAIC]
The number of successful subscriber

supplementary services activations to bar
all incoming calls
SS_Act_BAOC
[SS Activations BAOC]

all outgoing calls
SS_Act_BIC
[SS Activations BIC]

incoming calls
SS_Act_BIC_ROAM
[SS Activations BIC_ROAM]

incoming calls when roaming outside the
home PLMN country
SS_Act_BOC
[SS Activations BOC]

outgoing calls
SS_Act_BOIC
[SS Activations BOIC]

outgoing international calls
SS_Act_BOIC_exHC
[SS Activations
BOIC_exHC]

outgoing international calls except those
directed to the home PLMN
SS_Act_CFB
[SS Activations CFB]

supplementary services activations for
call forwarding on mobile subscriber
busy
SS_Act_CFNRc
[SS Activations CRNRc]

call forwarding on mobile subscriber not
reachable
SS_Act_CFNRy
[SS Activations CFNRy]

call forwarding on no reply
SS_Act_CFU
[SS Activations CFU]

call forwarding unconditional
...........................................................................................................................................................................................................................................................
A - 66

270-710-919R6.0
SS Deactivations
DB Name
Description
SS_Act_CLIP
[SS Activations CLIP]

Supplementary Services activations for
calling line identification presentation
SS_Act_CLIR
[SS Activations CLIR]

calling line identification restriction
SS_Act_COLP
[SS Activations COLP]

connected line identification presentation
SS_Act_COLR
[SS Activations COLR]

connected line identification restriction
SS_Act_CW
[SS Activations CW]

call waiting
SS_Act_ECT
[SS Activations ECT]

explicit call transfer
SS_Act_HOLD
[SS Activations HOLD]

call hold
SS_Act_MPTY
[SS Activations MPTY]

multiparty
Table A-34, "SS Deactivations" (A-68) stores the measurements for

UMTS supplementary services deactivations. This table is called
HCF_MEAS_SS_DEACT in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 67

Table A-34
SS Deactivations
DB Name
Description
SS_Deact_BAIC
[SS Deactivations BAIC]
The number of subscriber supplementary

services deactivations to bar all incoming
calls
SS_Deact_BAOC
[SS Deactivations BAOC]

services deactivations to bar all outgoing
calls
SS_Deact_BIC
[SS Deactivations BIC]

services deactivations to bar incoming
calls
SS_Deact_BIC_ROAM
[SS Deactivations BIC
ROAM]

services deactivations to bar the
incoming calls when roaming outside the
HPLMN Country
SS_Deact_BOC
[SS Deactivations BOC]

services deactivations to bar outgoing
calls
SS_Deact_BOIC
[SS Deactivations BOIC]

international calls
SS_Deact_BOIC_exHC
[SS Deactivations BOIC
exHC]

international calls except those directed
to a home PLMN
SS_Deact_CFB
[SS Deactivations CFB]

services deactivations used for call
forwarding on mobile subscriber which
are busy
SS_Deact_CFNRc
[SS Deactivations CFNRc]

forwarding on mobile subscriber which
are not reachable
SS_Deact_CFNRy
[SS Deactivations CFNRy]

forwarding on no reply
SS_Deact_CFU
[SS Deactivations CFU]

forwarding unconditional
...........................................................................................................................................................................................................................................................
A - 68

270-710-919R6.0
SS Interrogations
DB Name
Description
SS_Deact_CLIP
[SS Deactivations CLIP]

services deactivations used for calling
line identification presentation
SS_Deact_CLIR
[SS Deactivations CLIR]

services deactivations used for calling
line identification restriction
SS_Deact_COLP
[SS Deactivations COLP]

services deactivations used for connected
line identification presentation
SS_Deact_COLR
[SS Deactivations COLR]

services deactivations used for connected
line identification restriction
SS_Deact_CW
[SS Deactivations CW]

waiting
SS_Deact_ECT
[SS Deactivations ECT]

supplementary services deactivations
which are used for explicit call transfer
SS_Deact_HOLD
[SS Deactivations HOLD]

services deactivations used for call hold
SS_Deact_MPTY
[SS Deactivations MPTY]

services deactivations used for multiparty
Table A-35, "SS Interrogations" (A-70) stores the measurements for

UMTS supplementary services interrogations. This table is called
HCF_MEAS_SS_INTE in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 69

Table A-35
SS Interrogations
DB Name
Description
SS_Intr_ECT
[SS Interrogations ECT]

services interrogations that are used for
explicit call transfer
SS_Intr_BAIC
[SS Interrogations BAIC]

services interrogations to bar all
incoming call
SS_Intr_BIC
[SS Interrogations BIC]

services interrogations to bar incoming
call
SS_Intr_BIC_ROAM
[SS Interrogations BIC
ROAM]

services interrogations to bar incoming
calls when roaming outside the home
PLMN Country
SS_Intr_BOC
[SS Interrogations for Barring
of Outgoing Calls]

services interrogations to bar outgoing
calls
SS_Intr_BOIC
[SS Interrogations BOIC]

international calls
SS_Intr_BOIC_exHC
[SS Interrogations BOIC
exHC]

to the home PLMN
SS_Intr_CFB
[SS Interrogations CFB]

to the home PLMN
SS_Intr_CFNRc
[SS Interrogations CFNRc]

services interrogations for call
forwarding on mobile subscriber who are
not reachable
SS_Intr_CFNRy
[SS Interrogations CFNRy]

forwarding on no reply
SS_Intr_CFU
[SS Interrogations CFU]

forwarding unconditional
...........................................................................................................................................................................................................................................................
A - 70

270-710-919R6.0
UMTS_CAMEL
DB Name
Description
SS_Intr_CLIP
[SS Interrogations CLIP]

services interrogations for calling line
identification presentation
SS_Intr_CLIR
[SS Interrogations CLIR]

services interrogations for calling line
identification restriction
SS_Intr_COLP
[SS Interrogations COLP]

supplementary services interrogations
used for connected line identification
presentation
SS_Intr_COLR
[SS Interrogations COLR]

used for connected line identification
restriction
SS_Intr_CW
[SS Interrogations CW]

used for call waiting
SS_Intr_HOLD
[SS Interrogations HOLD]

used for call hold
SS_Intr_MPTY
[SS Interrogations MPTY]

used for multiparty
SS_Intr_BAOC
[SS Interrogations BAOC]

used to bar all outgoing calls
Table A-36, "UMTS_CAMEL" (A-71) contains the measurements

related to UMTS Customized Applications for Mobile Network
Enhanced Logic (CAMEL) services. This table is called
HCF_MEAS_UMTS_CAMEL in MAS database.
Table A-36
UMTS_CAMEL
DB Name
Description
Camel_SubInter
[Camel_SubInter]
The number of times that the CAMEL

subscription interrogation request was
received via ATI
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 71
UMTS_CNL
DB Name
Description
Succ_Camel_SubInter
[Succ_Camel_SubInter]
The number of times that the successful

CAMEL subscription interrogation request
was processed upon receipt of the SRI and the
HLR sent out ProvideSubscriberInfo
Succ_NIUSSD
[Succ_NIUSSD]

network initiated USSD message
UnstructuredSSRequest/Notify is received and
passed on to the VLR
UnSuc_MIUSSD_gsmSCF
[UnSuc_MIUSSD_gsmSCF]
The number of times that a mobile initiated

USSD message ProcessUnstructuredSS-Data/
Request was received by the HLR and was
rejected by the gsmSCF
ATSI
[ATSI]
The number of times that the ATSI was

received
ATM
[ATM]
The number of times that the ATM was

received
NSDC
[NSDC]
The number of times that the NSDC was sent
Succ_NSDC
[Succ_NSDC]

acknowledgment to NSDC was received
ATI_CurLoc
[ATI_CurLoc]
The number of times that the ATI with current

location was received
UnSuc_ATI_Not_AllowGsm
SCF
[UnSuc_ATI_Not_AllowGsm
SCF]
The number of times that the unsuccessful ATI

with or without current location was received
from not allowed gsmSCF
PSI_With_CurLoc
[PSI_With_CurLoc]
The number of times that the PSI with current

location was sent
Table A-37, "UMTS_CNL." (A-73) contains the measurement for

UMTS cancel location service. This table is called as
HCF_MEAS_UMTS_CNL in MAS database
...........................................................................................................................................................................................................................................................
A - 72

270-710-919R6.0

Table A-37
MAP_MSGS_SNT
UMTS_CNL.
DB Name
Description
Suc_CanLoc
[Suc_CanLoc]
The number of CancelLocation with

positive response
UnSuc_CanLoc
[UnSuc_CanLoc]
The number of CancelLocation that all

the retries failed with timeout or error
responses
CanLoc_ChangeVLR
[CanLoc_ChangeVLR]
Indicates how often a request for location

cancelling is sent to the VLR due to an
updating procedure
UnSuc_CanLoc_SubUnknow
n
[UnSuc_CanLoc_SubUnkno
wn]
Number of unsuccessful cancel location

because the subscriber is not known in
the VLR
UnSuc_CanLoc_SubUnident
[UnSuc_CanLoc_SubUnident
]
The number of cancel location update

procedure was unsuccessful due to
unidentified subscriber indicated by
MAP error "Unidentified Subscriber"
(v1) or "Data missing" v2/v3
UnSuc_CanLoc_NegOutcom
e
[UnSuc_CanLoc_NegOutco
me]
The number of cancel location update

procedure was unsuccessful due to a
negative outcome or HLR timer expiry
CanLoc_ChangeSGSN
[CanLoc_ChangeSGSN]

cancelling was sent to the old SGSN due
to a change of the SGSN
CanLoc_SubAdm
[CanLoc_SubAdm]

cancelling was sent to the SGSN due to
subscriber administration
UnSuc_CanLoc_ChangeSGS
N
[UnSuc_CanLoc_ChangeSG
SN]
Indicates how often the old SGSN has

unsuccessfully cancelled the GPRS
location after a change of SGSN
UnSuc_CanLoc_SubAdm
[UnSuc_CanLoc_SubAdm]
Indicates how often a GPRS location in

the SGSN is unsuccessfully cancelled
upon appropriate subscriber
administration
Table A-38, "MAP_MSGS_SNT" (A-74) stores the MAP messages
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 73
sent by UMTS HLR. This table is called

HCF_MEAS_MAP_MSGS_SNT in MAS database.
Table A-38
MAP_MSGS_RCVD
MAP_MSGS_SNT
DB Name
Description
Auth_Fail_Rpt
[Auth_Fail_Rpt]
The total number of sending MAP

message Authentication_Failure_Reports
Cancel_Loc
[Cancel_Loc]

message Cancel_Locations
Insert_Subs_Data
[Insert_Subs_Data]

message Insert_Subscriber_Data
Delete_Subs_Data
[Delete_Subs_Data]

message Delete_Subscriber_Data
Notif_Term_Rdy
[Notif_Term_Rdy]

message Notify_Terminal_Ready
Purge_MS
[Purge_MS]

message Purge_MS
Provide_Roam_Nmb
[Provide_Roam_Nmb]

message Provide_Roaming_Number
Ready_for_SM
[Ready_for_SM]

message Ready_For_SM
Restore_Data
[Restore_Data]

message Restore_Data
Send_Auth_Info
[Send_Auth_Info]

message
Send_Authentication_Information
Send_Routing_Info
[Send_Routing_Info]

message Send_Routing_Information
Update_Loc
[Update_Loc]

message Update_Location
Update_GPRS_Loc
[Update_GPRS_Loc]

message Update GPRS Location
Table A-39, "MAP_MSGS_RCVD" (A-75) stores the measurements

for MAP messages received in UMTS HLR. This table is called
HCF_MEAS_MAP_MSGS_RCVD in MAS database.
...........................................................................................................................................................................................................................................................
A - 74

270-710-919R6.0

Table A-39
MAP_MSGS_FAIL
MAP_MSGS_RCVD
DB Name
Description
Auth_Fail_Rpt
[Auth_Fail_Rpt]
The total number of receiving MAP

message Authentication_Failure_Reports
Cancel_Loc
[Cancel_Loc]

message Cancel_Locations
Insert_Subs_Data
[Insert_Subs_Data]

message Insert_Subscriber_Data
Delete_Subs_Data
[Delete_Subs_Data]

message Delete_Subscriber_Data
Notif_Term_Rdy
[Notif_Term_Rdy]

message Notify_Terminal_Ready
Purge_MS
[Purge_MSP]

message Purge_MS
Provide_Roam_Nmb
[Provide_Roam_Nmb]

message Provide_Roaming_Number
Ready_for_SM
[Ready_for_SM]

message Ready_For_SM
Restore_Data
[Restore_Data]

message Restore_Data
Send_Auth_Info
[Send_Auth_Info]

message
Send_Routing_Info
[Send_Routing_Info]

message Send_Routing_Information
Update_Loc
[Update_Loc]

message Update_Location
Update_GPRS_Loc
[Update_GPRS_Loc]

Table A-40, "MAP_MSGS_FAIL" (A-76) stores the measurements for

MAP session errors. This table is called
HCF_MEAS_MAP_MSGS_FAIL in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 75

Table A-40
UMTS_SMS
MAP_MSGS_FAIL
DB Name
Description
Auth_Fail_Rpt
[Auth_Fail_Rpt]
The total number of failed MAP message

Authentication_Failure_Report
Cancel_Loc
[Cancel_Loc]

Cancel_Location
Insert_Subs_Data
[Insert_Subs_Data]

Insert_Subscriber_Data
Delete_Subs_Data
[Delete_Subs_Data]

Delete_Subscriber_Data
Notif_Term_Rdy
[Notif_Term_Rdy]

Notify_Terminal_Ready
Purge_MS
[Purge_MSP]

Purge_MS
Provide_Roam_Nmb
[Provide_Roam_Nmb]

Provide_Roaming_Number
Ready_for_SM
[Ready_for_SM]

Ready_For_SM
Restore_Data
[Restore_Data]

Restore_Data
Send_Auth_Info
[Send_Auth_Info]

Send_Routing_Info
[Send_Routing_Info]

Send_Routing_Information
Update_Loc
[Update_Loc]

Update_Location
Update_GPRS_Loc
[Update_GPRS_Loc]
The total number of response failed MAP

Table A-41, "UMTS_SMS" (A-77) contains the measurements related

to SMS services. This table is called HCF_MEAS_UMTS_SMS in
MAS database.
...........................................................................................................................................................................................................................................................
A - 76

270-710-919R6.0

Table A-41
UMTS_SRI
UMTS_SMS
DB Name
Description
SRI_SM
[SRI_SM]
The number of times SRIforSM was

received from a GMSC
UnSuc_SRISM_Susbcrip
[UnSuc_SRISM_Susbcrip]
The number of times unsuccessful

SRIforSM was processed due to
subscription errors (TS21 not
provisioned)
UnSuc_SRISM_LostLoc
[UnSuc_SRISM_LostLoc]

SRIforSM was processed due to lost
location
Ready_for_SMS
[Ready_for_SMS]
The number of
ALERT_SERVICE_CENTRE operations
being sent
Suc_SMS_Alert
[Suc_SMS_Alert]
The number of times successful

AlertServiceCenter was sent to the SC
Ready_for_SMS_MSPresent
[Ready_for_SMS_MSPresent
]
The number of either,

NOTE_SM_PRESENT (Ph1) and/or
READY_FOR_SMS operations being
sent
UnSuc_ReadyforSMS
[UnSuc_ReadyforSMS]

ReadyForSMS was processed and the
HLR returned an error
Table A-42, "UMTS_SRI" (A-78) contains the measurements related to

UMTS SRI. This table is called HCF_MEAS_UMTS_SRI in MAS
database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 77

Table A-42
UMTS_SRI
DB Name
Description
SRI_GMSC
[SRI_GMSC]
The number of times SRI was received

from a GMSC
UnSuc_SRI_ODB
[UnSuc_SRI_ODB]
The number of times unsuccessful SRI/

SRIforGPRS was processed due to ODB
UnSuc_SRI_ODB_CS
[UnSuc_SRI_ODB_CS]
The number of times unsuccessful SRI

was processed due to ODB
UnSuc_SRI_ODB_PS
[UnSuc_SRI_ODB_PS]

UnSuc_SRI_CF
[UnSuc_SRI_CF]

was processed due to HCF errors
UnSuc_SRI_SubCheck_CS
[UnSuc_SRI_SubCheck_CS]

was processed due to subscription check
errors
UnSuc_SRI_Sub
[UnSuc_SRI_Sub]

SRIforGPRS was processed due to
subscriber behavior
UnSuc_SRI_Sub_CS
[UnSuc_SRI_Sub_CS]

was processed due to subscriber behavior
UnSuc_SRI_Sub_PS
[UnSuc_SRI_Sub_PS]

subscriber behavior
UnSuc_SRI_LostLoc
[UnSuc_SRI_LostLoc]

SRIforGPRS was processed due to lost
location (VLR/SGSN Number of MS
Current Location is null)
UnSuc_SRI_LostLoc_CS
[UnSuc_SRI_LostLoc_CS]

was processed due to lost location (VLR
Number of MS Current Location is null)
UnSuc_SRI_LostLoc_PS
[UnSuc_SRI_LostLoc_PS]

location (SGSN Number of MS Current
Location is null)
Succ_MSRN_VLR
[Succ_MSRN_VLR]
The number of times successful PRN

with MSRN was received from the VLR
...........................................................................................................................................................................................................................................................
A - 78

270-710-919R6.0
UMTS_SS
DB Name
Description
Succ_MSRN_GMSC
[Succ_MSRN_GMSC]
The number of times successful SRI with

the received MSRN (PRN) was sent to
the GMSC
Succ_FTN_GMSC
[Succ_FTN_GMSC]
The number of times successful SRI

response with a HCF FTN was sent to
GMSC
Succ_Bar_IC
[Succ_Bar_IC]
The number of times successful barring

of all incoming calls was processed
Succ_Bar_IC_OutHPLMN
[Succ_Bar_IC_OutHPLMN]
The number of times successful barring

of all incoming calls when roaming
outside the HPLMN country was
processed
Succ_SRI_BOR
[Succ_SRI_BOR]
The number of successful MAP SRI for

Basic OR enquiry.
Succ_SRI_ORLCF
[Succ_SRI_ORLCF]

ORLCF enquiry.
Table A-43, "UMTS_SS" (A-80) contains Supplementary Services

related measurements. This table is called HCF_MEAS_UMTS_SS in
MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 79

Table A-43
UMTS_SS
DB Name
Description
RegistPass
[RegistPass]
The number of times successful

RegisterPassword was processed
UnSuc_RegistPass_Sub
[UnSuc_RegistPass_Sub]

RegisterPassword was processed due to
subscriber behavior
UnSuc_Erase_Sub
[UnSuc_Erase_Sub]
The number of times unsuccessful Erase

SS was processed due to subscriber
behavior
UnSuc_Active_Sub
[UnSuc_Active_Sub]
The number of times unsuccessful Active

behavior
UnSuc_Deactive_Sub
[UnSuc_Deactive_Sub]

Deactive SS was processed due to
subscriber behavior
UnSuc_Interrogate_Sub
[UnSuc_Interrogate_Sub]

Interrogate SS was processed due to
subscriber behavior
UnSuc_Regist_Sub
[UnSuc_Regist_Sub]

RegisterSS was processed due to
subscriber behavior
Registrations
[Registrations]
The number of times SS registration is

done for mobile subscribers on HLR
system
Erasures
[Erasures]
The number of times SS Erasure is done

for mobile subscribers on HLR system
Interrogations
[Interrogations]
The number of times interrogation is

done for mobile subscribers on HLR
system
CW_Activations
[CW_Activations]
The number of times the SS Call Waiting

activation is done for mobile subscribers
on HLR system
CW_Deactivations
[CW_Deactivations]
The number of times the SS Call Waiting

deactivation is done for mobile
subscribers on HLR system
...........................................................................................................................................................................................................................................................
A - 80

270-710-919R6.0

UMTS_UL
Table A-44, "UMTS_UL" (A-82) contains measurements related to

UMTS UpdateLocation. This table is called HCF_MEAS_UMTS_UL
in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 81

Table A-44
UMTS_UL
DB Name
Description
UL_HPLMN
[UL_HPLMN]
The number of times location updating is

received from a VLR of the home PLMN
(HPLMN)
UL_VPLMN
[UL_VPLMN]
The number of times location updating is

received from a VLR of another PLMN
(visited PLMN)
GPRS_UL_HPLMN
[GPRS_UL_HPLMN]
The number of times a successful and

unsuccessful GPRS location update
procedure was invoked when mobile
subscriber was in home PLMN
GPRS_UL_VPLMN
[GPRS_UL_VPLMN]
The number of times a successful and

subscriber was in visited PLMN
UL_SubData_VLR
[UL_SubData_VLR]
The number of times a message

containing subscriber data is sent to the
VLR due to location updating
UnSuc_UL_SubData_Neg
[UnSuc_UL_SubData_Neg]
The number of times the VLR could not

deliver subscriber data for a location
update due to negative outcome or HLR
timer expiry
Suc_CallTrace_After_LU
[Suc_CallTrace_After_LU]
The number of times Call Trace was

activated after successful
UpdateLocation and
UpdateGPRSLocation
UnSuc_CallTrace_After_LU
[UnSuc_CallTrace_After_LU
]
The number of times Call Trace was not

UpdateLocation and
UpdateGPRSLocation
UnSuc_UL_HPLMN_Roam
R
[UnSuc_UL_HPLMN_Roam
R]

UpdateLocation was processed in
HPLMN due to roaming restrictions
UnSuc_UL_VPLMN_Roam
R
[UnSuc_UL_VPLMN_Roam
R]

UpdateLocation was processed in
VPLMN due to roaming restrictions
...........................................................................................................................................................................................................................................................
A - 82

270-710-919R6.0
GSM_USR_AFR
DB Name
Description
UL_HPLMN_SC
[UL_HPLMN_SC]
The number of super-charger location

updates (successful and unsuccessful) to
the home PLMN.
UL_VPLMN_SC
[UL_VPLMN_SC]
Number of super-charger location

the visited PLMN.
GPRS_UL_HPLMN_SC
[GPRS_UL_HPLMN_SC]
The number of super-charger GPRS

location updates (successful and
unsuccessful) to the home PLMN.
GPRS_UL_VPLMN_SC
[GPRS_UL_VPLMN_SC]
The number of super-charger GPRS

location updates (successful and
unsuccessful) to the visited PLMN.
Table A-45, "GSM_USR_AFR" (A-84) contains the number of times

mobile subscriber is unsuccessfully authenticated in GSM network per
access type and per re-attempt reason. This table is called
HCF_MEAS_GSM_USR_AFR in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 83

Table A-45
GSM_USR_AFR
DB Name
Description
Call
[Call]
The number of times mobile subscriber is

unsuccessfully authenticated in GSM
network when access type is call
EmergencyCall
[EmergencyCall]

network when access type is emergency
call
LocationUpdating
[LocationUpdating]

network when access type is location
updating
SupplementaryService
[SupplementaryService]

network when access type is
supplementary service
ShortMessage
[ShortMessage]

network when access type is short
message
GPRSAttach
[GPRSAttach]

network when access type is GPRS attach
RoutingAreaUpdating
[RoutingAreaUpdating]

network when access type is routing area
updating
ServiceRequest
[ServiceRequest]

network when access type is service
request
PDPContextAct
[PDPContextAct]

network when access type is PDP context
act
...........................................................................................................................................................................................................................................................
A - 84

270-710-919R6.0
UMTS_USR_AFR
DB Name
Description
PDPContextDeact
[PDPContextDeact]

deact
GPRSDetach
[GPRSDetach]

network when access type is GPRS
detach
Initial_Attempt
[Initial_Attempt]

network at initial attempt
Re_Attempt
[Re_Attempt]

network at reattempt
Table A-46, "UMTS_USR_AFR" (A-86) contains the number of times

mobile subscriber is unsuccessfully authenticated in UMTS network
per access type and per re-attempt reason. This table is called
HCF_MEAS_UMTS_USR_AFR in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 85

Table A-46
UMTS_USR_AFR
DB Name
Description
Call
[Call]

unsuccessfully authenticated in UMTS
network when access type is call
EmergencyCall
[EmergencyCall]

network when access type is emergency
call
LocationUpdating
[LocationUpdating]

network when access type is location
updating
SupplementaryService
[SupplementaryService]

network when access type is
supplementary service
ShortMessage
[ShortMessage]

network when access type is short
message
GPRSAttach
[GPRSAttach]

network when access type is GPRS attach
RoutingAreaUpdating
[RoutingAreaUpdating]

network when access type is routing area
updating
ServiceRequest
[ServiceRequest]

network when access type is service
request
PDPContextAct
[PDPContextAct]

act
...........................................................................................................................................................................................................................................................
A - 86

270-710-919R6.0
DB Name
Description
PDPContextDeact
[PDPContextDeact]

deact
GPRSDetach
[GPRSDetach]

network when access type is GPRS
detach
Initial_Attempt
[Initial_Attempt]

network at initial attempt
Re_Attempt
[Re_Attempt]

network at reattempt
This section lists UMTS per-NE measurement table for 50 NEs. They
are called HCF_MEAS_UMTS_NE1 ~ HCF_MEAS_UMTS_NE50 in
MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 87

Table A-47
DB Name
Description
ENABLE
[ENABLE]
To sync up global data with measlog
SERV_SUC_ROAM
[SERV_SUC_ROAM]
per-NE counts that mobile subscribers

successfully complete location update
procedure when it was roaming outside
its HPLMN
SERV_FAIL_ROAM
[SERV_FAIL_ROAM]
per-NE counts that mobile subscribers

unsuccessfully complete location update
when attempting roaming outside their
HPLMN
SUC_REREG_HPLMN
[SUC_REREG_HPLMN]
per-NE counts that a location update is

successful completed when mobile
subscriber registers in HPLMN after
roaming
FAIL_REREG_HPLMN
[FAIL_REREG_HPLMN]
per-NE counts that a location update is

unsuccessful completed when mobile
subscriber registers in HPLMN after
roaming
SUC_LOCUPD_HPLMN
[SUC_LOCUPD_HPLMN]
per-NE counts for successful location

updates of the subscriber in the Home
PLMN
UNSUC_LOCUPD_HPLMN
[UNSUC_LOCUPD_HPLM
N]
per-NE counts for unsuccessful location

updates of the subscriber in the Home
PLMN per-NE
NE_BASIC_SERVICE
[NE_BASIC_SERVICE]
per-NE counts that Basic Services are

requested during call termination
NE_SUC_CNL
[NE_SUC_CNL]
per-NE counts for CancelLocation with

positive response
NE_UNSUC_CNL
[NE_UNSUC_CNL]
per-NE counts for CancelLocation that all

the retries failed with timeout or error
responses
CanLoc_ChangeVLR
[CanLoc_ChangeVLR]
per-NE counts that a request for location

cancelling is sent to the VLR due to an
updating procedure
...........................................................................................................................................................................................................................................................
A - 88

270-710-919R6.0
DB Name
Description
UnSuc_CanLoc_SubUnknow
n
[UnSuc_CanLoc_SubUnkno
wn]
per-NE counts for unsuccessful cancel

location because the subscriber is not
known in the VLR
CanLoc_ChangeSGSN
[CanLoc_ChangeSGSN]

cancelling was sent to the old SGSN due
to a change of the SGSN
CanLoc_SubAdm
[CanLoc_SubAdm]

cancelling was sent to the SGSN due to
subscriber administration
UnSuc_CanLoc_ChangeSGS
N
[UnSuc_CanLoc_ChangeSG
SN]
per-NE counts that the old SGSN has

unsuccessfully cancelled the GPRS
location after a change of SGSN
UnSuc_CanLoc_SubAdm
[UnSuc_CanLoc_SubAdm]
per-NE counts that a GPRS location in

the SGSN is unsuccessfully cancelled
upon appropriate subscriber
administration
SRI_SM
[SRI_SM]
per-NE counts that SRIforSM was

received from a GMSC
UnSuc_SRISM_Subscrip
[UnSuc_SRISM_Subscrip]
per-NE counts that unsuccessful

SRIforSM was processed due to
subscription errors (TS21 not
provisioned)
UnSuc_SRISM_LostLoc
[UnSuc_SRISM_LostLoc]

SRIforSM was processed due to lost
location
Suc_SMS_Alert
[Suc_SMS_Alert]
per-NE counts that successful

AlertServiceCenter was sent to the SC
RegistPass
[RegistPass]

RegisterPassword was processed
UnSuc_RegistPass_Sub
[UnSuc_RegistPass_Sub]

RegisterPassword was processed due to
subscriber behavior
UnSuc_Erase_Sub
[UnSuc_Erase_Sub]
per-NE counts that unsuccessful Erase SS

was processed due to subscriber behavior
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 89
DB Name
Description
UnSuc_Active_Sub
[UnSuc_Active_Sub]
per-NE counts that unsuccessful Active

behavior
UnSuc_Deactive_Sub
[UnSuc_Deactive_Sub]
per-NE counts that unsuccessful Deactive

behavior
UnSuc_Interrogate_Sub
[UnSuc_Interrogate_Sub]

Interrogate SS was processed due to
subscriber behavior
UnSuc_Regist_Sub
[UnSuc_Regist_Sub]

RegisterSS was processed due to
subscriber behavior
Registrations
[Registrations]
per-NE counts that SS registration is done

Erasures
[Erasures]
per-NE counts that SS Erasure is done for

mobile subscribers on HLR system
Interrogations
[Interrogations]
per-NE counts that interrogation is done

CW_Activations
[CW_Activations]
per-NE counts that the SS Call Waiting

activation is done for mobile subscribers
on HLR system
CW_Deactivations
[CW_Deactivations]
per-NE counts that the SS Call Waiting

deactivation is done for mobile
subscribers on HLR system
UnSuc_SRI_ODB_PS
[UnSuc_SRI_ODB_PS]

UnSuc_SRI_Sub_PS
[UnSuc_SRI_Sub_PS]

subscriber behavior
UnSuc_SRI_LostLoc_PS
[UnSuc_SRI_LostLoc_PS]

location (SGSN Number of MS Current
Location is null)
Succ_MSRN_VLR
[Succ_MSRN_VLR]
per-NE counts that successful PRN with

MSRN was received from the VLR
...........................................................................................................................................................................................................................................................
A - 90

270-710-919R6.0
DB Name
Description
Camel_SubInter
[Camel_SubInter]
per-NE counts that successful CAMEL

received via ATI
Succ_Camel_SubInter
[Succ_Camel_SubInter]
per-NE counts that successful CAMEL

processed upon receipt of the SRI and the
HLR sent out ProvideSubscriberInfo
Succ_NIUSSD
[Succ_NIUSSD]
per-NE counts that successful network

initiated USSD message
UnstructuredSSRequest/Notify is
received and passed on to the VLR
UnSuc_MIUSSD_gsmSCF
[UnSuc_MIUSSD_gsmSCF]
per-NE counts that a mobile initiated

USSD message ProcessUnstructuredSSData/Request that was received by the
HLR and rejected by the gsmSCF.
ATSI
[ATSI]
per-NE counts that ATSI was received
ATM
[ATM]
per-NE counts that ATM was received
NSDC
[NSDC]
per-NE counts that NSDC was sent
Succ_NSDC
[Succ_NSDC]

acknowledgment to NSDC was received
ATI_CurLoc
[ATI_CurLoc]
per-NE counts that ATI with current

location was received
UnSuc_ATI_Not_AllowGsm
SCF
[UnSuc_ATI_Not_AllowGsm
SCF]
per-NE counts that unsuccessful ATI with

or without current location was received
from not allowed gsmSCF
PSI_With_CurLoc
[PSI_With_CurLoc]
per-NE counts that PSI with current

location was sent
UL_HPLMN
[UL_HPLMN]

updating is received from a VLR of the
home PLMN (HPLMN)
UL_VPLMN
[UL_VPLMN]

updating is received from a VLR of
another PLMN (visited PLMN)
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 91
DB Name
Description
GPRS_UL_HPLMN
[GPRS_UL_HPLMN]
per-NE counts that a successful and

subscriber was in home PLMN
GPRS_UL_VPLMN
[GPRS_UL_VPLMN]
per-NE counts that a successful and

subscriber was in visited PLMN
UL_SubData_VLR
[UL_SubData_VLR]
per-NE counts that a message containing

subscriber data is sent to the VLR due to
location updating
UnSuc_UL_SubData_Neg
[UnSuc_UL_SubData_Neg]
per-NE counts that the VLR could not

deliver subscriber data for a location
update due to negative outcome or HLR
timer expiry
Suc_CallTrace_After_LU
[Suc_CallTrace_After_LU]
per-NE counts that Call Trace was

UpdateLocation and
UpdateGPRSLocation
UnSuc_CallTrace_After_LU
[UnSuc_CallTrace_After_LU
]
per-NE counts that Call Trace was not

UpdateLocation and
UpdateGPRSLocation
UL_HPLMN_SC
[UL_HPLMN_SC]

the home PLMN
UL_VPLMN_SC
[UL_VPLMN_SC]

the visited PLMN
GPRS_UL_HPLMN_SC
[GPRS_UL_HPLMN_SC]
Number of super-charger GPRS location

the home PLMN
GPRS_UL_VPLMN_SC
[GPRS_UL_VPLMN_SC]
Number of super-charger GPRS location

the visited PLMN
SUC_BOR
[SUC_BOR]

Basic OR enquiry
...........................................................................................................................................................................................................................................................
A - 92

270-710-919R6.0
UMTS_OVLD_DROP
DB Name
Description
SUC_ORLCF
[SUC_ORLCF]

ORLCF enquiry
Table A-48, "UMTS_OVLD_DROP" (A-93) contains all the UMTS

messages dropped for SSN overload. This table is called
HCF_MEAS_UMTS_OVLD_DROP in MAS database.
Table A-48
UMTS_OVLD_DROP
DB Name
Description
TOTAL_MSG_COUNT
[TOTAL_MSG_COUNT]
Total number of dropped msg due

to overload
MSG_COUNT_OVLD1
[MSG_COUNT_OVLD1]

to overload level 1
MSG_COUNT_OVLD2
[MSG_COUNT_OVLD2]

to overload level 2
MSG_COUNT_OVLD3
[MSG_COUNT_OVLD3]

to overload level 3
MSG_COUNT_OVLD4
[MSG_COUNT_OVLD4]

to overload level 4
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 93

............................................................................................................................................................................................................................................................
To collect the measurement of CALEA, you need to

first provision the table HDF_GLOBAL_DATA. There are 20 fields
(DF1_IPaddr~ DF20_IPaddr), which record the IP addresses for the
measured LTDUs. To provision this data from eSM, you need to use
the HDF-CALEA view.
Important!
CALEA_SERVSYS_S
Table A-49, "CALEA_SERVSYS_S" (A-94) contains Number of

ServingSystem messages that are successfully sent to each Delivery
Function. This table is called HCF_MEAS_CALEA_SERV_SYS_S in
MAS database.
Table A-49
CALEA_SERVSYS_F
CALEA_SERVSYS_S
DB Name
Description
Delivery_Function1
[Delivery_Function1]
Number of ServingSystem messages that

are successfully sent to Delivery
Function 1
Delivery_Function2

Function 2
......
[......]
......
Delivery_Function20

Function 20
Table A-50, "CALEA_SERVSYS_F" (A-95) contains Number of

ServingSystem messages that have failed to be sent to each Delivery
Function. This table is called HCF_MEAS_ CALEA_SERVSYS_ F in
MAS database.
...........................................................................................................................................................................................................................................................
A - 94

270-710-919R6.0

Table A-50
CALEA_TERMATT_S
CALEA_SERVSYS_F
DB Name
Description
Delivery_Function1

have failed be sent to Delivery Function 1
Delivery_Function2

have failed be sent to Delivery Function 2
......
[......]
......
Delivery_Function20

have failed be sent to Delivery Function
20
Table A-51, "CALEA_TERMATT_S" (A-95) contains Number of

TerminationAttempt messages that are successfully sent to each
Delivery Function. This table is called HCF_MEAS_
CALEA_TERMATT _S in MAS database.
Table A-51
CALEA_TERMATT_F
CALEA_TERMATT_S
DB Name
Description
Delivery_Function1
Number of TerminationAttempt
messages that are successfully sent to
Delivery Function 1
Delivery_Function2
Delivery Function 2
......
[......]
......
Delivery_Function20
Delivery Function 20
Table A-52, "CALEA_TERMATT_F" (A-96) contains Number of

TerminationAttempt messages that have failed to be sent to each
Delivery Function. This table is called HCF_MEAS_
CALEA_TERMATT_F in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 95

Table A-52
CALEA_REDIR_S
CALEA_TERMATT_F
DB Name
Description
Delivery_Function1
messages that have failed be sent to
Delivery Function 1
Delivery_Function2
Delivery Function 2
......
[......]
......
Delivery_Function20
Delivery Function 20
Table A-53, "CALEA_REDIR_S" (A-96) contains Number of

Redirection messages that are successfully sent to each Delivery
Function. This table is called HCF_MEAS_CALEA_REDIR_S in
MAS database.
Table A-53
CALEA_REDIR_F
CALEA_REDIR_S
DB Name
Description
Delivery_Function1
Number of Redirection messages that are

successfully sent to Delivery Function 1
Delivery_Function2

......
[......]
......
Delivery_Function20

Table A-54, "CALEA_REDIR_F" (A-97) contains Number of

Redirection messages which have failed to be sent to each Delivery
Function. This table is called HCF_MEAS_CALEA_REDIR_F in
MAS database.
...........................................................................................................................................................................................................................................................
A - 96

270-710-919R6.0

Table A-54
CALEA_CNNTST_S
CALEA_REDIR_F
DB Name
Description
Delivery_Function1
Number of Redirection messages which

have failed to be sent to Delivery
Function 1
Delivery_Function2

Function 2
......
[......]
......
Delivery_Function20

Function 20
Table A-55, "CALEA_CNNTST_S" (A-98) records the CNNTST

which really established a connection with the Delivery Function. This
table is called HCF_MEAS_CALEA_CNNTST_S in MAS database.
Only a CNNTST that passes through the USDS check
and waits for sending to the Delivery Function is thought as an
actual CNNTST.
Important!
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 97

Table A-55
CALEA_CNNTST_F
CALEA_CNNTST_S
DB Name
Description
Delivery_Function1
Records measurement for link between

Delivery Function 1 and the HCF which
is active upon connection test request
from eSM
Delivery_Function2

from eSM
......
[......]
......
Delivery_Function20

from eSM
Table A-56, "CALEA_CNNTST_F" (A-99) records the CNNTSTs that

tried to connect to the Delivery Function but the route is blocked. This
table is called HCF_MEAS_CALEA_CNNTST_F in MAS database.
Only a CNNTST that passes through the USDS check
and waits for sending to the Delivery Function is thought as an
actual CNNTST.
Important!
...........................................................................................................................................................................................................................................................
A - 98

270-710-919R6.0

Table A-56
CALEA_CNNTST_F
DB Name
Description
Delivery_Function1

is blocked upon connection test request
from eSM
Delivery_Function2

from eSM
......
[......]
......
Delivery_Function20

from eSM
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 99

............................................................................................................................................................................................................................................................
MAP IMS
Table A-57, "MAP IMS" (A-100) contains measurements of MAP

message for HSS. This table is called HCF_MEAS_MAP_IMS in
MAS database.
Table A-57
HSS Cx
MAP IMS
DB Name
Description
IMS_SAI_SUCC
[IMS SAI SUCC]
Count of successfully processing

UMTS MAP
SendAuthenticationInfo without
receiving an error
IMS_SAI_ERROR
[IMS SAI ERROR]
Count of unsuccessfully processing

UMTS MAP
SendAuthenticationInfo with error or
timeout
IMS_ATI_SUCC
[IMS ATI SUCC]
Number of processed ATI Messages

successfully
IMS_ATI_ERROR
[IMS ATI ERROR]
Number of ATI errors
IMS_PSI_SUCC
[IMS PSI SUCC]
Number of processed PSI Messages

successfully
IMS_PSI_ERROR
[IMS PSI ERROR]
Number of PSI errors
Table A-58, "HSS Cx" (A-101) records the measurements for HCF Cx
Diameter common service. This table is called HCF_MEAS_HSS_CX
in MAS database.
...........................................................................................................................................................................................................................................................
A - 100

270-710-919R6.0
Table A-58
HSS Sh
HSS Cx
DB Name
Description
CX_UAA_SUCC
[CX UAA SUCC]
The number of successful UAA

messages sent from HSS to I-CSCF
CX_UAA_ERROR
[CX SAA ERROR]
The number of failed UAA messages

sent from HSS to I-CSCF
CX_SAA_SUCC
[CX SAA SUCC]
The number of successful SAA

messages sent from HSS to S-CSCF
CX_SAA_ERROR
[CX SAA ERROR]
The number of failed SAA messages

sent from HSS to S-CSCF
CX_MAA_SUCC
[CX MAA SUCC]
The number of successful MAA

messages sent from HSS to S-CSCF
CX_MAA_ERROR
[CX MAA ERROR]
The number of failed MAA messages

sent from HSS to S-CSCF
CX_LIA_SUCC
[CX LIA SUCC]
The number of successful LIA

messages sent from HSS to I-CSCF
CX_LIA_ERROR
[CX LIA ERROR]
The number of failed LIA messages

sent from HSS to I-CSCF
CX_RTA_SUCC
[CX RTA SUCC]
The number of successful RTA

messages received from S-CSCF
CX_RTA_ERROR
[CX RTA ERROR]
The number of failed RTA messages

received from S-CSCF
CX_PPA_SUCC
[CX PPA SUCC]
The number of successful PPA

messages received from S-CSCF
CX_PPA_ERROR
[CX PPA ERROR]
The number of failed PPA messages

received from S-CSCF
Table A-59, "HSS Sh" (A-102) stores the measurements for HCF Sh
service. This table is called HCF_MEAS_HSS_SH in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 101
Table A-59
HSS Sh
DB Name
Description
SH_PNA_SUCC
[SH PNA SUCC]
The number of successful PNA

messages received from AS
SH_PNA_ERROR
[SH PNA ERROR]
The number of failed PNA messages

received from AS
SH_PNA_CUMULA_SIZE
[SH PNA CUMULA SIZE]
The size of the PNA messages

received from AS during the
measurement interval
SH_PNR_SUCC
[SH PNR SUCC]
The number of PNR messages sent

from HSS to AS successfully
SH_PNR_CUMULA_SIZE
[SH PNR CUMULA SIZE]
The size of the PNR messages sent

from HSS to AS during the
SH_UDA_SUCC
[SH UDA SUCC]
The number of successful UDA

messages sent from HSS to AS
SH_UDA_ERROR
[SH UDA ERROR]
The number of failed UDA messages

sent from HSS to AS
SH_UDA_CUMULA_SIZE
[SH UDA CUMULA SIZE]
The size of the UDA messages sent

SH_UDR_CUMULA_SIZE
[SH UDR CUMULA SIZE]
The size of the UDR messages

SH_UDR_NUM
[SH UDR NUM]
The number of the UDR messages

SH_SNA_SUCC
[SH SNA SUCC]
The number of successful SNA

SH_SNA_ERROR
[SH SNA ERROR]
The number of failed SNA messages

sent from HSS to AS
SH_SNA_CUMULA_SIZE
[SH SNA CUMULA SIZE]
The size of the SNA messages sent

SH_SNR_NUM
[SH SNR NUM]
The number of the SNR messages

...........................................................................................................................................................................................................................................................
A - 102

270-710-919R6.0
Cx SAR
DB Name
Description
SH_SNR_CUMULA_SIZE
[SH SNR CUMULA SIZE]
The size of the SNR messages

SH_PUA_SUCC
[SH PUA SUCC]
The number of successful PUA

SH_PUA_ERROR
[SH PUA ERROR]
The number of failed PUA messages

sent from HSS to AS
SH_PUA_CUMULA_SIZE
[SH PUA CUMULA SIZE]
The size of the PUA messages sent

SH_PUR_NUM
[SH PUR NUM]
The number of the PUR messages

SH_PUR_CUMULA_SIZE
[SH PUR CUMULA SIZE]
The size of the PUR messages

Table A-60, "Cx SAR" (A-104) contains the Cx Diameter SAR

message measurement based on the following received AVPs:
Server-Assignment-Type (for each of 12 enumerated values)
User-Data-Already-Available (0 or 1)
This table is called HCF_MEAS_CX_SAR in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 103
Table A-60
Cx SAR
DB Name
Description
SAT_NO_ASSIGNMENT
[SAT NO ASSIGNMENT]
The number of SAR messages

received with NO_ASSIGNMENT in
Server-Assignment-Type AVP
SAT_REGISTRATION
[SAT REGISTRATION]

received with REGISTRATION in
SAT_RE_REGISTRATION
[SAT REREGISTRATION]

received with RE_REGISTRATION
in Server-Assignment-Type AVP
SAT_UNREGISTERED_USER
[SAT UNREGISTERED USER]

received with
UNREGISTERED_USER in ServerAssignment-Type AVP
SAT_TIMEOUT_DEREG
[SAT TIMEOUT DEREG]

received with
TIMEOUT_DEREGISTRATION in
SAT_USER_DEREG
[SAT USER DEREG]

received with
USER_DEREGISTRATION in
SAT_TIMEOUT_DEREG_STO
R
[SAT TIMEOUT DEREG
STOR]

received with
TIMEOUT_DEREGISTRATION_ST
ORE_SERVER_NAME in ServerAssignment-Type AVP
SAT_USER_DEREG_STOR
[SAT USER DEREG STOR]

received with
USER_DEREGISTRATION_STORE
_SERVER_NAME in ServerAssignment-Type AVP
SAT_ADMI_DEREG
[SAT ADMI DEREG]

received with
ADMINISTRATIVE_DEREGISTRA
TION in Server-Assignment-Type
AVP
...........................................................................................................................................................................................................................................................
A - 104

270-710-919R6.0
Cx Mix
DB Name
Description
SAT_AUTH_FAIL
[SAT AUTH FAIL]

received with
AUTHENTICATION_FAILURE in
SAT_AUTH_TIMEOUT
[SAT AUTH TIMEOUT]

received with
AUTHENTICATION_TIMEOUT in
SAT_DEREG_TOO_MUCH
[SAT DEREG TOO MUCH]

received with
DEREGISTRATION_TOO_MUCH_
DATA in Server-Assignment-Type
AVP
USER_DATA_NOT_AVAIL
[USER DATA NOT AVAIL]

received with
USER_DATA_NOT_AVAILABLE in
User-Data-Already-Available AVP
USER_DATA_ALREADY_AVA
IL
[USER DATA ALREADY
AVAIL]

received with
USER_DATA_ALREADY_AVAILA
BLE in User-Data-Already-Available
AVP
SUPPORT_SiFC
[SUPPORT_SiFC]
The number of SAR messages which

indicate corresponding s-cscf request
feature support of shared IFC.
UNSUPPORT_SiFC
[UNSUPPORT_SiFC]
The number of SAR messages which

indicate corresponding s-cscf does not
request feature support of shared IFC.
Table A-61, "Cx Mix" (A-106) contains the Cx Diameter UAR, MAR
or RTR message measurement based on the following received AVP
respectively:
User-Authorization-Type
SIP-Authentication-Scheme
Deregistration-Reason code
This table is called HCF_MEAS_CX_MIX in MAS database.

...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 105
Table A-61
Cx Mix
DB Name
Description
UAR_UAT_UA_REG
[UAR UAT UA REG]
The number of UAR messages received

with REGISTRATION in UserAuthorization-Type AVP
UAR_UAT_DE_REG
[UAR UAT DE REG]

with DE_REGISTRATION in UserAuthorization-Type AVP
UAR_UAT_REG_CAP
[UAR UAT REG CAP]

with
REGISTRATION_AND_CAPABILITIE
S in User-Authorization-Type AVP
MAR_SCHEME_AKAV1_M
D5
[MAR SCHEME AKAV1
MD5]
The number of MAR messages received

with Digest-AKAv1-MD5 in SIPAuthentication-Scheme AVP
MAR_SCHEME_MD5_A1
[MAR SCHEME MD5 A1]

with Digest-MD5-A1 in SIPAuthentication-Scheme AVP
MAR_SCHEME_MD5_by_
CSCF
[MAR SCHEME MD5 by
CSCF]

with Digest-MD5-by-CSCF in SIPAuthentication-Scheme AVP
RTR_REASON_TERMINAT
ION
[RTR REASON
TERMINATION]
The number of RTR messages sent with

PERMANENT_TERMINATION in
Deregistration-Reason code AVP
RTR_REASON_NEW_ASSI
GNED
[RTR REASON NEW
ASSIGNED]

NEW_SERVER_ASSIGNED in
Deregistration-Reason code AVP
RTR_REASON_SERVER_C
HANGE
[RTR REASON SERVER
CHANGE]

SERVER_CHANGE in DeregistrationReason code AVP
RTR_REASON_REMOVE_
SCSCF
[RTR REASON REMOVE
SCSCF]

REMOVE_S-CSCF in DeregistrationReason code AVP
...........................................................................................................................................................................................................................................................
A - 106

270-710-919R6.0

IMS_OVLD_DROP
Table A-62, "IMS_OVLD_DROP" (A-107)contains all the IMS

message dropped for Diameter stack overload. This table is called
HCF_MEAS_IMS_OVLD_DROP in MAS database.
Table A-62
IMS_OVLD_DROP
DB Name
Description
TOTAL_MSG_COUNT
[TOTAL_MSG_COUNT]

overload
MSG_COUNT_OVLD1
[MSG_COUNT_OVLD1]

overload level 1
MSG_COUNT_OVLD2
[MSG_COUNT_OVLD2]

overload level 2
MSG_COUNT_OVLD3
[MSG_COUNT_OVLD3]

overload level 3
MSG_COUNT_OVLD4
[MSG_COUNT_OVLD4]

overload level 4
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 107

............................................................................................................................................................................................................................................................
Table A-63, "AAA" (A-108) contains the measurement sets for AAA
PDLSs processing the database requests from VitalAAA servers. This
table is called HCF_MEAS_AAA in MAS database.
Table A-63
AAA
SPA DB Name[View
Attribute Name]
Description
REQ_PROFILE_ SUCC[REQ
PROFILE SUCC]
The number of successful AAA

Profile Request processed.
REQ_PROFILE_ UNSUC[REQ
PROFILE UNSUC]
The number of unsuccessful AAA

Profile Request processed
AUTH_VECT_SUCC[AUTH
VECT SUCC]
The number of successful

Authentication Vector Generation
Request processed
AUTH_VECT_UNSUC[AUTH
VECT UNSUC]
The number of unsuccessful

Authentication Vector Generation
Request processed
...........................................................................................................................................................................................................................................................
A - 108

270-710-919R6.0

............................................................................................................................................................................................................................................................
Table A-64, "SMPP" (A-109) contains the measurement sets for SMPP
messages. This table is called HCF_MEAS_SMPP in the MAS
database.
Table A-64
SMPP
SPA DB Name[View
Attribute Name]
Description
Successful_Submit_SM
[Successful_Submit_SM]
Number of submit sm requests sent

from HLR that received a successful
response.
Unsuccessful_Submit_SM
[Unsuccessful_Submit_SM]
Number of submit sm requests sent

from HLR that could not be sent,
timeout, or received a negative
response.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 109

............................................................................................................................................................................................................................................................
Service
Table A-65, "Service" (A-110) contains HDF Service Measurements.

This table is called HDF_MEAS_Service in MAS database.
Table A-65
Overload
Service
DB Name
Description
CORC_Msg_Snt
[CORC Messages Sent]
Number of CORC messages sent

(CHT)
Fail_Prov_Data_Deletes
[Fail Provision Delete]
Number of unsuccessful provisioning

data deletes
Fail_Prov_Data_Inserts
[Fail Provision Insert]

data inserts
Fail_Prov_Data_Reads
[Fail Provision Data Reads]

data reads
Fail_Prov_Data_Updates
[Fail Provision Update]

data updates
Suc_Prov_Data_Deletes
[Suc Provision Data Delete]
Number of successful provisioning

data deletes
Suc_Prov_Data_Inserts
[Suc Provision Data Insert]

data inserts
Suc_Prov_Data_Reads[Suc
Provision Data Reads]

data reads
Suc_Prov_Data_Updates
[Suc Provision Data Update]

data updates
DB_Queries
[Number of DB queries]
Number of HDF DB queries (Network

traffic)
The HDF overload measurements are shown in Table A-66, "Overload"

(A-111). This table is called HDF_MEAS_OVERLOAD in MAS
database.
...........................................................................................................................................................................................................................................................
A - 110

270-710-919R6.0

Table A-66
Load Balancing
Overload
DB Name
Description
Overload_Level_1
[Overload Level 1]
The number of times that Level 1

overload is reached
Overload_Level_2
[Overload Level 2]

overload is reached
Overload_Level_3
[Overload Level 3]

overload is reached
Overload_Level_4
[Overload Level 4]

overload is reached
Overload_Level_5
[Overload Level 5]

overload is reached
Table A-67, "Load Balance" (A-112) contains the measurement related

to load balancing. This table is called HDF_MEAS_Load_Balancing in
MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 111

Table A-67
Load Balance
DB Name
[View Attribute Name
Overload Drop
Description
SubMov_Transfer
[SubMov Transfer]
Number of subscribers that have been

successfully queried out and sent to target
HDF
SubMov_Insert
[SubMov Insert]

successfully inserted into database of
target HDF
SubMov_Delete
[SubMov Delete]

successfully deleted from database of
source HDF
Fail_SubMov_Transfer
[Fail SubMov Transfer]
Number of subscribers that failed to be

queried out and sent to target HDF
Fail_SubMov_Insert
[Fail SubMov Insert]

inserted into database of target HDF
Fail_SubMov_Delete
[Fail SubMov Delete]

deleted from database of source HDF
RecMov_Transfer
[RecMov Transfer]
Number of records that have been

successfully queried out and sent to target
HDF
RecMov_Insert
[RecMov Insert]

successfully inserted into database of
target HDF
RecMov_Delete
[RecMov Delete]

successfully deleted from database of
source HDF
Fail_RecMov_Transfer
[Fail RecMov Transfer]
Number of records that failed to be

queried out and sent to target HDF
Fail_RecMov_Insert
[Fail RecMov Insert]
Number of records that are failed to be

inserted into database of target HDF
Fail_RecMov_Delete
[Fail RecMov Delete]
Number of records that are failed to be

deleted from the database of source HDF
Table A-68, "Overload Drop" (A-113) contains all the DBCOM

messages dropped for HDF overload in HDF``. This table is called
HDF_MEAS_Overload_Drop in MAS database.
...........................................................................................................................................................................................................................................................
A - 112

270-710-919R6.0

Table A-68
Overload Drop
DB Name
Description
Total_Msg_Count[Total Msg
Count]
``Total Message Count`` Total number of

dropped messages due to overload.
Msg_Count_Ovld1[Msg
Count Ovld1]
``Message Count Overload 1``Total

number of dropped msg due to overload
level 1.
Msg_Count_Ovld2[Msg
Count Ovld2]

level 2.
Msg_Count_Ovld3[Msg
Count Ovld3]

level 3.
Msg_Count_Ovld4[Msg
Count Ovld4]

level 4.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 113

............................................................................................................................................................................................................................................................
ANSI Suc Transcnt
Table A-69, "ANSI Suc Transcnt" (A-115) records the measurements

for successful ANSI transactions processed by the HDF. This table is
called HDF_MEAS_ANSI_Transcnt in MAS database.
...........................................................................................................................................................................................................................................................
A - 114

270-710-919R6.0

Table A-69
ANSI Suc Transcnt
DB Name
Description
REGNOT_Suc_Transcnt
[REGNOT Suc Transcnt]

RegistrationNotification transactions
PROFREQ_Suc_Transcnt
[PROFREQ Suc Transcnt]
The number of successful ProfileRequest

transactions
QUALREQ_Suc_Transcnt
[QUALREQ Suc Transcnt]

QualificationRequest transactions
AUTHREQ_Suc_Transcnt
[AUTHREQ Suc Transcnt]

AuthenticationRequest transactions
ASREPORT_Suc_Transcnt
[ASREPORT Suc Transcnt]

AuthenticationStatusReport transactions
AFREPORT_Suc_Transcnt
[AFREPORT Suc Transcnt]

AuthenticationFailureReport transactions
BSCHALL_Suc_Transcnt
[BSCHALL Suc Transcnt]

BaseStationChallenge transactions
COUNTREQ_Suc_Transcnt
[COUNTREQ Suc Transcnt]
The number of successful CountRequest

transactions
OTASPREQ_Suc_Transcnt
[OTASPREQ Suc Transcnt]

OTASPRequest transactions
LOCREQ_Suc_Transcnt
[LOCREQ Suc Transcnt]

LocationRequest transactions
TRANUMREQ_Suc_Transcnt
[TRANUMREQ Suc Transcnt]

TransferToNumberRequest transactions
REREQ_Suc_Transcnt
[REREQ Suc Transcnt]

RedirectionRequest transactions
REDDIR_Suc_Transcnt
[REDDIR Suc Transcnt]

RedirectionDirective transactions
FEATREQ_Suc_Transcnt
[FEATREQ Suc Transcnt]

FeatureRequest transactions
SMSNOT_Suc_Transcnt
[SMSNOT Suc Transcnt]

SMSNotification transactions
SMSREQ_Suc_Transcnt
[SMSREQ Suc Transcnt]
The number of successful SMSRequest

transactions
INFODIR_Suc_Transcnt
[INFODIR Suc Transcnt]

InformationDirective transactions
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 115
ANSI Suc CD Msgcnt
DB Name
Description
MSGDIR_Suc_Transcnt
[MSGDIR Suc Transcnt]

MessageDirective transactions
SEARCH_Suc_Transcnt
[SEARCH Suc Transcnt]
The number of successful Search

transactions
ORREQ_Suc_Transcnt
[ORREQ Suc Transcnt]

OriginationRequest transactions
POSREQ_Suc_Transcnt
[POSREQ Suc Transcnt]

PositionRequest transactions
LPREQ_Suc_Transcnt
[LPREQ Suc Transcnt]

LCSParameterRequest transactions
STATNOTREQ_Suc_Transcnt
[STATNOTREQ Suc Transcnt]

StatusNotificationRequest transactions
MSINACT_Suc_Transcnt
[MSINACT Suc Transcnt]
The number of successful MSInactive

transactions
REGCANC_Suc_Transcnt
[REGCANC Suc Transcnt]

RegistrationCancellation transactions
QUALDIR_Suc_Transcnt
[QUALDIR Suc Transcnt]

QualificationDirective transactions
SERVREQ_Suc_Transcnt
[SERVREQ Suc Transcnt]

ServiceRequest transactions
AUTHDIR_Suc_Transcnt
[AUTHDIR Suc Transcnt]

AuthenticationDirective transactions
ROUTREQ_Suc_Transcnt
[ROUTREQ Suc Transcnt]

RoutingRequest transactions
SMDPP_Suc_Transcnt
[SMDPP Suc Transcnt]
The number of successful SMDPP

transactions
RUIDIR_Suc_Transcnt
[RUIDIR Suc Transcnt]

transactions
MODIFY_Suc_Transcnt
[MODIFY Suc Transcnt]
The number of successful Modify

transactions.
Table A-70, "ANSI Suc CD Msgcnt" (A-117) records the

measurements for successful ANSI CD message count processed by
the HDF node. This table is called HDF_MEAS_ANSI_CD_Msgcnt in
MAS database.
...........................................................................................................................................................................................................................................................
A - 116

270-710-919R6.0

Table A-70
ANSI Suc CD Msgcnt
DB Name
Description
REGNOT_Suc_CD_Msgcnt
[REGNOT Suc CD Msgcnt]
The number of successful DBCom

messages from HCF to HDF for
PROFREQ_Suc_CD_Msgcnt
[PROFREQ Suc CD Msgcnt]

ProfileRequest
QUALREQ_Suc_CD_Msgcnt
[QUALREQ Suc CD Msgcnt]

AUTHREQ_Suc_CD_Msgcnt
[AUTHREQ Suc CD Msgcnt]

AuthenticationRequest
ASREPORT_Suc_CD_Msgcnt[
ASREPORT Suc CD Msgcnt]

AuthenticationStatusReport
AFREPORT_Suc_CD_Msgcnt
[AFREPORT Suc CD Msgcnt]

AuthenticationFailureReport
BSCHALL_Suc_CD_Msgcnt
[BSCHALL Suc CD Msgcnt]

BaseStationChallenge
COUNTREQ_Suc_CD_Msgcnt
[COUNTREQ Suc CD Msgcnt]

CountRequest
OTASPREQ_Suc_CD_Msgcnt
[OTASPREQ Suc CD Msgcnt]

OTASPRequest
LOCREQ_Suc_CD_Msgcnt
[LOCREQ Suc CD Msgcnt]

LocationRequest
TRANUMREQ_Suc_CD_Msgnt
[TRANUMREQ Suc CD
Msgcnt]

REREQ_Suc_CD_Msgcnt
[REREQ Suc CD Msgcnt]

RedirectionRequest
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 117
DB Name
Description
REDDIR_Suc_CD_Msgcnt
[REDDIR Suc CD Msgcnt]

RedirectionDirective
FEATREQ_Suc_CD_Msgcnt
[FEATREQ Suc CD Msgcnt]

FeatureRequest
SMSNOT_Suc_CD_Msgcnt
[SMSNOT Suc CD Msgcnt]

SMSNotification
SMSREQ_Suc_CD_Msgcnt
[SMSREQ Suc CD Msgcnt]

SMSRequest
INFODIR_Suc_CD_Msgcnt
[INFODIR Suc CD Msgcnt]

InformationDirective
MSGDIR_Suc_CD_Msgcnt
[MSGDIR Suc CD Msgcnt]

MessageDirective
SEARCH_Suc_CD_Msgcnt
[SEARCH Suc CD Msgcnt]

Search
ORREQ_Suc_CD_Msgcnt
[ORREQ Suc CD Msgcnt]

OriginationRequest
POSREQ_Suc_CD_Msgcnt
[POSREQ Suc CD Msgcnt]

PositionRequest
LPREQ_Suc_CD_Msgcnt
[LPREQ Suc CD Msgcnt]

LCSParameterRequest
STATNOTREQ_Suc_CD_Msgct
[STATNOTREQ Suc CD
Msgcnt]

MSINACT_Suc_CD_Msgcnt
[MSINACT Suc CD Msgcnt]

MSInactive
...........................................................................................................................................................................................................................................................
A - 118

270-710-919R6.0
ANSI Suc DC Msgcnt
DB Name
Description
REGCANC_Suc_CD_Msgcnt
[REGCANC Suc CD Msgcnt]

RegistrationCancellation
QUALDIR_Suc_CD_Msgcnt
[QUALDIR Suc CD Msgcnt]

SERVREQ_Suc_CD_Msgcnt
[SERVREQ Suc CD Msgcnt]

ServiceRequest
AUTHDIR_Suc_CD_Msgcnt
[AUTHDIR Suc CD Msgcnt]

AuthenticationDirective
ROUTREQ_Suc_CD_Msgcnt
[ROUTREQ Suc CD Msgcnt]

RoutingRequest
SMDPP_Suc_CD_Msgcnt
[SMDPP Suc CD Msgcnt]

SMDPP
RUIDIR_Suc_CD_Msgcnt
[RUIDIR Suc CD Msgcnt]

MODIFY_Suc_CD_Msgcnt
[MODIFY Suc CD Msgcnt]

Modify.
Table A-71, "ANSI Suc DC Msgcnt" (A-120) records the

measurements for successful ANSI DBCom-related message count
processed by the HDF node. This table is called
HDF_MEAS_ANSI_DC_Msgcnt in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 119
Table A-71
ANSI Suc DC Msgcnt
DB Name
Description
REGNOT_Suc_DC_Msgcnt
[REGNOT Suc DC Msgcnt]

messages from HDF to HCF for
PROFREQ_Suc_DC_Msgcnt
[PROFREQ Suc DC Msgcnt]

ProfileRequest
QUALREQ_Suc_DC_Msgcnt
[QUALREQ Suc DC Msgcnt]

AUTHREQ_Suc_DC_Msgcnt
[AUTHREQ Suc DC Msgcnt]

ASREPORT_Suc_DC_Msgcnt
[ASREPORT Suc DC Msgcnt]

AFREPORT_Suc_DC_Msgcnt
[AFREPORT Suc DC Msgcnt]

BSCHALL_Suc_DC_Msgcnt
[BSCHALL Suc DC Msgcnt]

COUNTREQ_Suc_DC_Msgcnt
[COUNTREQ Suc DC Msgcnt]

CountRequest
OTASPREQ_Suc_DC_Msgcnt
[OTASPREQ Suc DC Msgcnt]

OTASPRequest
LOCREQ_Suc_DC_Msgcnt
[LOCREQ Suc DC Msgcnt]

LocationRequest
TRANUMREQ_Suc_DC_Msgcnt
[TRANUMREQ Suc DC Msgcnt]

REREQ_Suc_DC_Msgcnt
[REREQ Suc DC Msgcnt]

RedirectionRequest
...........................................................................................................................................................................................................................................................
A - 120

270-710-919R6.0
DB Name
Description
REDDIR_Suc_DC_Msgcnt
[REDDIR Suc DC Msgcnt]

FEATREQ_Suc_DC_Msgcnt
[FEATREQ Suc DC Msgcnt]

FeatureRequest
SMSNOT_Suc_DC_Msgcnt
[SMSNOT Suc DC Msgcnt]

SMSNotification
SMSREQ_Suc_DC_Msgcnt
[SMSREQ Suc DC Msgcnt]

SMSRequest
INFODIR_Suc_DC_Msgcnt
[INFODIR Suc DC Msgcnt]

MSGDIR_Suc_DC_Msgcnt
[MSGDIR Suc DC Msgcnt]

MessageDirective
SEARCH_Suc_DC_Msgcnt
[SEARCH Suc DC Msgcnt]

Search
ORREQ_Suc_DC_Msgcnt
[ORREQ Suc DC Msgcnt]

OriginationRequest
POSREQ_Suc_DC_Msgcnt
[POSREQ Suc DC Msgcnt]

PositionRequest
LPREQ_Suc_DC_Msgcnt
[LPREQ Suc DC Msgcnt]

LCSParameterRequest
STATNOTREQ_Suc_DC_Msgcnt
[STATNOTREQ Suc DC Msgcnt]

MSINACT_Suc_DC_Msgcnt
[MSINACT Suc DC Msgcnt]

MSInactive
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 121
ANSI Suc CD Msglen
DB Name
Description
REGCANC_Suc_DC_Msgcnt
[REGCANC Suc DC Msgcnt]

QUALDIR_Suc_DC_Msgcnt
[QUALDIR Suc DC Msgcnt]

SERVREQ_Suc_DC_Msgcnt
[SERVREQ Suc DC Msgcnt]

ServiceRequest
AUTHDIR_Suc_DC_Msgcnt
[AUTHDIR Suc DC Msgcnt]

ROUTREQ_Suc_DC_Msgcnt
[ROUTREQ Suc DC Msgcnt]

RoutingRequest
SMDPP_Suc_DC_Msgcnt
[SMDPP Suc DC Msgcnt]

SMDPP
RUIDIR_Suc_DC_Msgcnt
[RUIDIR Suc DC Msgcnt]

MODIFY_Suc_DC_Msgcnt
[MODIFY Suc DC Msgcnt]

Modify.
Table A-72, "ANSI Suc CD Msglen" (A-123) records the

measurements for successful ANSI CD message length processed by
the HDF node. This table is called HDF_MEAS_ANSI_CD_Msglen in
MAS database.
...........................................................................................................................................................................................................................................................
A - 122

270-710-919R6.0

Table A-72
ANSI Suc CD Msglen
DB Name
Description
REGNOT_Suc_CD_Msglen
[REGNOT Suc CD Msglen]
The length of successful DBCom

PROFREQ_Suc_CD_Msglen
[PROFREQ Suc CD Msglen]

ProfileRequest
QUALREQ_Suc_CD_Msglen
[QUALREQ Suc CD Msglen]

AUTHREQ_Suc_CD_Msglen
[AUTHREQ Suc CD Msglen]

ASREPORT_Suc_CD_Msglen
[ASREPORT Suc CD Msglen]

AFREPORT_Suc_CD_Msglen
[AFREPORT Suc CD Msglen]

BSCHALL_Suc_CD_Msglen
[BSCHALL Suc CD Msglen]

COUNTREQ_Suc_CD_Msglen
[COUNTREQ Suc CD Msglen]

CountRequest
OTASPREQ_Suc_CD_Msglen
[OTASPREQ Suc CD Msglen]

OTASPRequest
LOCREQ_Suc_CD_Msglen
[LOCREQ Suc CD Msglen]

LocationRequest
TRANUMREQ_Suc_CD_Msglen
[TRANUMREQ Suc CD Msglen]

REREQ_Suc_CD_Msglen
[REREQ Suc CD Msglen]

RedirectionRequest
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 123
DB Name
Description
REDDIR_Suc_CD_Msglen
[REDDIR Suc CD Msglen]

FEATREQ_Suc_CD_Msglen
[FEATREQ Suc CD Msglen]

FeatureRequest
SMSNOT_Suc_CD_Msglen
[SMSNOT Suc CD Msglen]

SMSNotification
SMSREQ_Suc_CD_Msglen
[SMSREQ Suc CD Msglen]

SMSRequest
INFODIR_Suc_CD_Msglen
[INFODIR Suc CD Msglen]

MSGDIR_Suc_CD_Msglen
[MSGDIR Suc CD Msglen]

MessageDirective
SEARCH_Suc_CD_Msglen
[SEARCH Suc CD Msglen]

Search
ORREQ_Suc_CD_Msglen
[ORREQ Suc CD Msglen]

OriginationRequest
POSREQ_Suc_CD_Msglen
[POSREQ Suc CD Msglen]

PositionRequest
LPREQ_Suc_CD_Msglen
[LPREQ Suc CD Msglen]

LCSParameterRequest
STATNOTREQ_Suc_CD_Msglen
[STATNOTREQ Suc CD Msglen]

MSINACT_Suc_CD_Msglen
[MSINACT Suc CD Msglen]

MSInactive
...........................................................................................................................................................................................................................................................
A - 124

270-710-919R6.0
DB Name
Description
REGCANC_Suc_CD_Msglen
[REGCANC Suc CD Msglen]

QUALDIR_Suc_CD_Msglen
[QUALDIR Suc CD Msglen]

SERVREQ_Suc_CD_Msglen
[SERVREQ Suc CD Msglen]

ServiceRequest
AUTHDIR_Suc_CD_Msglen

[AUTHDIR Suc CD Msglen]
ANSI Suc DC Msglen
ROUTREQ_Suc_CD_Msglen
[ROUTREQ Suc CD Msglen]

RoutingRequest
SMDPP_Suc_CD_Msglen
[SMDPP Suc CD Msglen]

SMDPP
RUIDIR_Suc_CD_Msglen
[RUIDIR Suc CD Msglen]

MODIFY_Suc_CD_Msglen
[MODIFY Suc CD Msglen]

Modify.
Table A-73, "ANSI Suc DC Msglen" (A-125) records the

measurements for successful ANSI DBCom-related message length
processed by the HDF node. This table is called
HDF_MEAS_ANSI_DC_Msglen in MAS database.
Table A-73
ANSI Suc DC Msglen
DB Name
Description
REGNOT_Suc_DC_Msglen
[REGNOT Suc DC Msglen]

...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 125
DB Name
Description
PROFREQ_Suc_DC_Msglen
[PROFREQ Suc DC Msglen]

ProfileRequest
QUALREQ_Suc_DC_Msglen
[QUALREQ Suc DC Msglen]

AUTHREQ_Suc_DC_Msglen
[AUTHREQ Suc DC Msglen]

ASREPORT_Suc_DC_Msglen
[ASREPORT Suc DC Msglen]

AFREPORT_Suc_DC_Msglen
[AFREPORT Suc DC Msglen]

BSCHALL_Suc_DC_Msglen
[BSCHALL Suc DC Msglen]

COUNTREQ_Suc_DC_Msglen
[COUNTREQ Suc DC Msglen]

CountRequest
OTASPREQ_Suc_DC_Msglen
[OTASPREQ Suc DC Msglen]

OTASPRequest
LOCREQ_Suc_DC_Msglen
[LOCREQ Suc DC Msglen]

LocationRequest
TRANUMREQ_Suc_DC_Msglen
[TRANUMREQ Suc DC Msglen]

REREQ_Suc_DC_Msglen
[REREQ Suc DC Msglen]

RedirectionRequest
REDDIR_Suc_DC_Msglen
[REDDIR Suc DC Msglen]

...........................................................................................................................................................................................................................................................
A - 126

270-710-919R6.0
DB Name
Description
FEATREQ_Suc_DC_Msglen
[FEATREQ Suc DC Msglen]

FeatureRequest
SMSNOT_Suc_DC_Msglen
[SMSNOT Suc DC Msglen]

SMSNotification
SMSREQ_Suc_DC_Msglen
[SMSREQ Suc DC Msglen]

SMSRequest
INFODIR_Suc_DC_Msglen
[INFODIR Suc DC Msglen]

MSGDIR_Suc_DC_Msglen
[MSGDIR Suc DC Msglen]

MessageDirective
SEARCH_Suc_DC_Msglen
[SEARCH Suc DC Msglen]

Search
ORREQ_Suc_DC_Msglen
[ORREQ Suc DC Msglen]

OriginationRequest
POSREQ_Suc_DC_Msglen
[POSREQ Suc DC Msglen]

PositionRequest
LPREQ_Suc_DC_Msglen
[LPREQ Suc DC Msglen]

LCSParameterRequest
STATNOTREQ_Suc_DC_Msglen
[STATNOTREQ Suc DC Msglen]

MSINACT_Suc_DC_Msglen
[MSINACT Suc DC Msglen]

MSInactive
REGCANC_Suc_DC_Msglen
[REGCANC Suc DC Msglen]

...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 127
DB Name
Description
QUALDIR_Suc_DC_Msglen
[QUALDIR Suc DC Msglen]

SERVREQ_Suc_DC_Msglen
[SERVREQ Suc DC Msglen]

ServiceRequest
AUTHDIR_Suc_DC_Msglen
[AUTHDIR Suc DC Msglen]

ROUTREQ_Suc_DC_Msglen
[ROUTREQ Suc DC Msglen]

RoutingRequest
SMDPP_Suc_DC_Msglen
[SMDPP Suc DC Msglen]

SMDPP
RUIDIR_Suc_DC_Msglen
[RUIDIR Suc DC Msglen]

MODIFY_Suc_DC_Msglen
[MODIFY Suc DC Msglen]

Modify.
...........................................................................................................................................................................................................................................................
A - 128

270-710-919R6.0

............................................................................................................................................................................................................................................................
UMTS Suc Transcnt
Table A-74, "UMTS Suc Transcnt" (A-130) records the measurements

for successful GSM/UMTS transactions processed by the HDF. This
table is called HDF_MEAS_UMTS_Transcnt in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 129

Table A-74
UMTS Suc Transcnt
SPA DB Name [View

Attribute Name]
Description
UPL_Suc_Transcnt [UPL Suc

Transcnt]

UpdateLocation transactions.
ISD_Suc_Transcnt [ISD Suc

Transcnt]

InsertSubscriberData transactions.
SAI_Suc_Transcnt [SAI Suc

Transcnt]

SendAuthenticationInfo transactions.
AFR_Suc_Transcnt [AFR
Suc Transcnt]

SendAuthenticationFailureReport
transactions.
SendIMSI_Suc_Transcnt
[SendIMSI Suc Transcnt]
The number of successful SendIMSI

transactions.
SRI_Suc_Transcnt [SRI Suc

Transcnt]

SendRoutingInfo transactions.
RegSS_Suc_Transcnt [RegSS
Suc Transcnt]
The number of successful RegisterSS

transactions.
EraSS_Suc_Transcnt [EraSS
Suc Transcnt]
The number of successful EraseSS

transactions.
ActSS_Suc_Transcnt [ActSS
Suc Transcnt]
The number of successful ActivateSS

transactions.
DeactSS_Suc_Transcnt
[DeactSS Suc Transcnt]
The number of successful DeactivateSS

transactions.
RegPW_Suc_Transcnt
[RegPW Suc Transcnt]

RegisterPassword transactions.
IntSS_Suc_Transcnt [IntSS
Suc Transcnt]
The number of successful InterrogateSS

transactions.
PUSSREQ_Suc_Transcnt
[PUSSREQ Suc Transcnt]

ProcessUnstructuredSS-Request
transactions.
USSREQ_Suc_Transcnt
[USSREQ Suc Transcnt]

UnstructuredSS-Request transactions.
USSNOT_Suc_Transcnt
[USSNOT Suc Transcnt]

UnstructuredSS-Notify transactions.
SRS_Suc_Transcnt [SRS Suc

Transcnt]

SendRoutingInfoForSM transactions.
...........................................................................................................................................................................................................................................................
A - 130

270-710-919R6.0
SPA DB Name [View

Attribute Name]
Description
RDS_Suc_Transcnt [RDS
Suc Transcnt]

ReportSMDeliveryStatus transactions.
RSM_Suc_Transcnt [RSM
Suc Transcnt]
The number of successful ReadyForSM

transactions.
RD_Suc_Transcnt [RD Suc

Transcnt]
The number of successful RestoreData

transactions.
PurgeMS_Suc_Transcnt
[PurgeMS Suc Transcnt]
The number of successful PurgeMS

transactions.
ATI_Suc_Transcnt [ATI Suc

Transcnt]

AnyTimeInterrogation transactions.
ATSI_Suc_Transcnt [ATSI
Suc Transcnt]

AnyTimeSubscriptionInterrogation
transactions.
AnyM_Suc_Transcnt [AnyM
Suc Transcnt]

AnyTimeModification transactions.
SP_Suc_Transcnt [SP Suc

Transcnt]

MapSendParameters transactions.
UPLGPRS_Suc_Transcnt
[UPLGPRS Suc Transcnt]

UpdateGprsLocation transactions.
SRIGPRS_Suc_Transcnt
[SRIGPRS Suc Transcnt]

SendRoutingInfoForGprs transactions
FR_Suc_Transcnt [FR Suc

Transcnt]
The number of successful FailureReport

transactions.
CNL_Suc_Transcnt [CNL
Suc Transcnt]

CancelLocation transactions.
DSD_Suc_Transcnt [DSD
Suc Transcnt]

DeleteSubscriberData transactions.
NPG_Suc_Transcnt [NPG
Suc Transcnt]

NoteMSPresentForGPRS transactions.
PRN_Suc_Transcnt [PRN
Suc Transcnt]

ProvideRoamingNumber transactions.
FWCKSSIND_Suc_Transcnt
[FWCKSSIND Suc Transcnt]

ForwardCheckSSIndication transactions
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 131
SPA DB Name [View

Attribute Name]
UMTS CD Msgcnt
Description
NSDM_Suc_Transcnt
[NSDM Suc Transcnt]

NoteSubscriberDataModified
transactions.
PSI_Suc_Transcnt [PSI Suc

Transcnt]

ProvideSubscriberInfo transactions.
AlertSC_Suc_Transcnt
[AlertSC Suc Transcnt]

AlertServiceCenter transactions.
InformSC_Suc_Transcnt
[InformSC Suc Transcnt]

InformServiceCenter transactions.
ATM_Suc_Transcnt [ATM
Suc Transcnt]

ActivateTraceMode transactions.
DTM_Suc_Transcnt [DTM
Suc Transcnt]

DeactivateTraceMode transactions.
SetMWD_Suc_Transcnt
[SetMWD Suc Transcnt]

SetMessageWaittingData transactions.
NoteMP_Suc_Transcnt
[NoteMP Suc Transcnt]

NoteMSPresent transactions.
SRILCS_Suc_Transcnt
[SRILCS Suc Transcnt]

SendRoutingInfoforLCS transactions.
PUSSD_Suc_Transcnt
[PUSSD Suc Transcnt]

ProcessUnstructuredSS-Data
transactions.
GPW_Suc_Transcnt [GPW
Suc Transcnt]
The number of successful GetPassword

transactions.
Table A-75, "UMTS CD Msgcnt" (A-133) records the measurements

for successful GSM/UMTS CD message count processed by the HDF
node. This table is called HDF_MEAS_UMTS_CD_Msgcnt in MAS
database.
...........................................................................................................................................................................................................................................................
A - 132

270-710-919R6.0

Table A-75
UMTS CD Msgcnt
SPA DB Name [View

Attribute Name]
Description
UPL_Suc_CD_Msgcnt [UPL
Suc CD Msgcnt]

UpdateLocation.
ISD_Suc_CD_Msgcnt [ISD
Suc CD Msgcnt]

InsertSubscriberData.
SAI_Suc_CD_Msgcnt [SAI
Suc CD Msgcnt]

SendAuthenticationInfo.
AFR_Suc_CD_Msgcnt [AFR
Suc CD Msgcnt]

AuthenticationFailureReport.
SendIMSI_Suc_CD_Msgcnt
[SendIMSI Suc CD Msgcnt]

SendIMSI.
SRI_Suc_CD_Msgcnt [SRI
Suc CD Msgcnt]

SendRoutingInfo.
RegSS_Suc_CD_Msgcnt
[RegSS Suc CD Msgcnt]

RegisterSS.
EraSS_Suc_CD_Msgcnt
[EraSS Suc CD Msgcnt]

messages from HCF to HDF for EraseSS.
ActSS_Suc_CD_Msgcnt
[ActSS Suc CD Msgcnt]

ActivateSS.
DeactSS_Suc_CD_Msgcnt
[DeactSS Suc CD Msgcnt]

DeactivateSS.
RegPW_Suc_CD_Msgcnt
[RegPW Suc CD Msgcnt]

RegisterPassword.
IntSS_Suc_CD_Msgcnt
[IntSS Suc CD Msgcnt]

InterrogateSS.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 133
SPA DB Name [View

Attribute Name]
Description
PUSSREQ_Suc_CD_Msgcnt
[PUSSREQ Suc CD Msgcnt]

ProcessUnstructuredSS-Request.
USSREQ_Suc_CD_Msgcnt
[USSREQ Suc CD Msgcnt]

UnstructuredSS-Request.
USSNOT_Suc_CD_Msgcnt
[USSNOT Suc CD Msgcnt]

UnstructuredSS-Notify.
SRS_Suc_CD_Msgcnt [SRS
Suc CD Msgcnt]

SendRoutingInfoForSM.
RDS_Suc_CD_Msgcnt [RDS
Suc CD Msgcnt]

ReportSMDeliveryStatus.
RSM_Suc_CD_Msgcnt
[RSM Suc CD Msgcnt]

ReadyForSM.
RD_Suc_CD_Msgcnt [RD
Suc CD Msgcnt]

RestoreData.
PurgeMS_Suc_CD_Msgcnt
[PurgeMS Suc CD Msgcnt]

PurgeMS.
ATI_Suc_CD_Msgcnt [ATI
Suc CD Msgcnt]

AnyTimeInterrogation.
ATSI_Suc_CD_Msgcnt
[ATSI Suc CD Msgcnt]

AnyTimeSubscriptionInterrogation.
AnyM_Suc_CD_Msgcnt
[AnyM Suc CD Msgcnt]

AnyTimeModification.
SP_Suc_CD_Msgcnt [SP Suc

CD Msgcnt]

SendParameters.
...........................................................................................................................................................................................................................................................
A - 134

270-710-919R6.0
SPA DB Name [View

Attribute Name]
Description
UPLGPRS_Suc_CD_Msgcnt
[UPLGPRS Suc CD Msgcnt]

UpdateGprsLocation.
SRIGPRS_Suc_CD_Msgcnt
[SRIGPRS Suc CD Msgcnt]

SendRoutingInfoForGprs.
FR_Suc_CD_Msgcnt [FR
Suc CD Msgcnt]

FailureReport.
CNL_Suc_CD_Msgcnt [CNL
Suc CD Msgcnt]

CancelLocation.
DSD_Suc_CD_Msgcnt [DSD
Suc CD Msgcnt]

DeleteSubscriberData.
NPG_Suc_CD_Msgcnt [NPG
Suc CD Msgcnt]

NoteMSPresentForGPRS.
PRN_Suc_CD_Msgcnt [PRN
Suc CD Msgcnt]

ProvideRoamingNumber.
FWCKSSIND_Suc_CD_Msg
cnt [FWCKSSIND Suc CD
Msgcnt]

ForwardCheckSSIndication.
NSDM_Suc_CD_Msgcnt
[NSDM Suc CD Msgcnt]

NoteSubscriberDataModified.
PSI_Suc_CD_Msgcnt [PSI
Suc CD Msgcnt]

ProvideSubscriberInfo.
AlertSC_Suc_CD_Msgcnt
[AlertSC Suc CD Msgcnt]

AlertServiceCenter.
InformSC_Suc_CD_Msgcnt
[InformSC Suc CD Msgcnt]

InformServiceCenter.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 135
SPA DB Name [View

Attribute Name]
UMTS DC Msgcnt
Description
ATM_Suc_CD_Msgcnt
[ATM Suc CD Msgcnt]

ActivateTraceMode.
DTM_Suc_CD_Msgcnt
[DTM Suc CD Msgcnt]

DeactivateTraceMode.
SetMWD_Suc_CD_Msgcnt
[SetMWD Suc CD Msgcnt]

SetMessageWaittingData.
NoteMP_Suc_CD_Msgcnt
[NoteMP Suc CD Msgcnt]

NoteMSPresent.
SRILCS_Suc_CD_Msgcnt
[SRILCS Suc CD Msgcnt]

SendRoutingInfoforLCS.
PUSSD_Suc_CD_Msgcnt
[PUSSD Suc CD Msgcnt]

ProcessUnstructuredSS-Data.
GPW_Suc_CD_Msgcnt
[GPW Suc CD Msgcnt]

GetPassword.
Table A-76, "UMTS DC Msgcnt" (A-137) records the measurements

for successful GSM/UMTS DBCom-related message count processed
by the HDF node. This table is called
HDF_MEAS_UMTS_DC_Msgcnt in MAS database.
...........................................................................................................................................................................................................................................................
A - 136

270-710-919R6.0

Table A-76
UMTS DC Msgcnt
SPA DB Name [View

Attribute Name]
Description
UPL_Suc_DC_Msgcnt [UPL
Suc DC Msgcnt]

UpdateLocation.
ISD_Suc_DC_Msgcnt [ISD
Suc DC Msgcnt]

SAI_Suc_DC_Msgcnt [SAI
Suc DC Msgcnt]

AFR_Suc_DC_Msgcnt [AFR
Suc DC Msgcnt]

SendIMSI_Suc_DC_Msgcnt
[SendIMSI Suc DC Msgcnt]

SendIMSI.
SRI_Suc_DC_Msgcnt [SRI
Suc DC Msgcnt]

SendRoutingInfo.
RegSS_Suc_DC_Msgcnt
[RegSS Suc DC Msgcnt]

RegisterSS.
EraSS_Suc_DC_Msgcnt
[EraSS Suc DC Msgcnt]

messages from HDF to HCF for EraseSS.
ActSS_Suc_DC_Msgcnt
[ActSS Suc DC Msgcnt]

ActivateSS.
DeactSS_Suc_DC_Msgcnt
[DeactSS Suc DC Msgcnt]

DeactivateSS.
RegPW_Suc_DC_Msgcnt
[RegPW Suc DC Msgcnt]

RegisterPassword.
IntSS_Suc_DC_Msgcnt
[IntSS Suc DC Msgcnt]

InterrogateSS.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 137
SPA DB Name [View

Attribute Name]
Description
PUSSREQ_Suc_DC_Msgcnt
[PUSSREQ Suc DC Msgcnt]

USSREQ_Suc_DC_Msgcnt
[USSREQ Suc DC Msgcnt]

USSNOT_Suc_DC_Msgcnt
[USSNOT Suc DC Msgcnt]

SRS_Suc_DC_Msgcnt [SRS
Suc DC Msgcnt]

RDS_Suc_DC_Msgcnt [RDS
Suc DC Msgcnt]

RSM_Suc_DC_Msgcnt
[RSM Suc DC Msgcnt]

ReadyForSM.
RD_Suc_DC_Msgcnt [RD
Suc DC Msgcnt]

RestoreData.
PurgeMS_Suc_DC_Msgcnt
[PurgeMS Suc DC Msgcnt]

PurgeMS.
ATI_Suc_DC_Msgcnt [ATI
Suc DC Msgcnt]

ATSI_Suc_DC_Msgcnt
[ATSI Suc DC Msgcnt]

AnyM_Suc_DC_Msgcnt
[AnyM Suc DC Msgcnt]

SP_Suc_DC_Msgcnt [SP Suc

DC Msgcnt]

SendParameters.
...........................................................................................................................................................................................................................................................
A - 138

270-710-919R6.0
SPA DB Name [View

Attribute Name]
Description
UPLGPRS_Suc_DC_Msgcnt
[UPLGPRS Suc DC Msgcnt]

UpdateGprsLocation.
SRIGPRS_Suc_DC_Msgcnt
[SRIGPRS Suc DC Msgcnt]

FR_Suc_DC_Msgcnt [FR
Suc DC Msgcnt]

FailureReport.
CNL_Suc_DC_Msgcnt [CNL
Suc DC Msgcnt]

CancelLocation.
DSD_Suc_DC_Msgcnt [DSD
Suc DC Msgcnt]

NPG_Suc_DC_Msgcnt [NPG
Suc DC Msgcnt]

PRN_Suc_DC_Msgcnt [PRN
Suc DC Msgcnt]

FWCKSSIND_Suc_DC_Msg
cnt [FWCKSSIND Suc DC
Msgcnt]

NSDM_Suc_DC_Msgcnt
[NSDM Suc DC Msgcnt]

PSI_Suc_DC_Msgcnt [PSI
Suc DC Msgcnt]

AlertSC_Suc_DC_Msgcnt
[AlertSC Suc DC Msgcnt]

AlertServiceCenter.
InformSC_Suc_DC_Msgcnt
[InformSC Suc DC Msgcnt]

...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 139
SPA DB Name [View

Attribute Name]
UMTS CD Msglen
Description
ATM_Suc_DC_Msgcnt
[ATM Suc DC Msgcnt]

ActivateTraceMode.
DTM_Suc_DC_Msgcnt
[DTM Suc DC Msgcnt]

SetMWD_Suc_DC_Msgcnt
[SetMWD Suc DC Msgcnt]

NoteMP_Suc_DC_Msgcnt
[NoteMP Suc DC Msgcnt]

NoteMSPresent.
SRILCS_Suc_DC_Msgcnt
[SRILCS Suc DC Msgcnt]

PUSSD_Suc_DC_Msgcnt
[PUSSD Suc DC Msgcnt]

GPW_Suc_DC_Msgcnt
[GPW Suc DC Msgcnt]

GetPassword.
Table A-77, "UMTS CD Msglen" (A-141) records the measurements

for successful GSM/UMTS CD message length processed by the HDF
node. This table is called HDF_MEAS_UMTS_CD_Msglen in MAS
database.
...........................................................................................................................................................................................................................................................
A - 140

270-710-919R6.0

Table A-77
UMTS CD Msglen
SPA DB Name [View

Attribute Name]
Description
UPL_Suc_CD_Msglen [UPL
Suc CD Msglen]

UpdateLocation.
ISD_Suc_CD_Msglen [ISD
Suc CD Msglen]

SAI_Suc_CD_Msglen [SAI
Suc CD Msglen]

AFR_Suc_CD_Msglen [AFR
Suc CD Msglen]

SendIMSI_Suc_CD_Msglen
[SendIMSI Suc CD Msglen]

SendIMSI.
SRI_Suc_CD_Msglen [SRI
Suc CD Msglen]

SendRoutingInfo.
RegSS_Suc_CD_Msglen
[RegSS Suc CD Msglen]

RegisterSS.
EraSS_Suc_CD_Msglen
[EraSS Suc CD Msglen]

messages from HCF to HDF for EraseSS.
ActSS_Suc_CD_Msglen
[ActSS Suc CD Msglen]

ActivateSS.
DeactSS_Suc_CD_Msglen
[DeactSS Suc CD Msglen]

DeactivateSS.
RegPW_Suc_CD_Msglen
[RegPW Suc CD Msglen]

RegisterPassword.
IntSS_Suc_CD_Msglen
[IntSS Suc CD Msglen]

InterrogateSS.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 141
SPA DB Name [View

Attribute Name]
Description
PUSSREQ_Suc_CD_Msglen
[PUSSREQ Suc CD Msglen]

USSREQ_Suc_CD_Msglen
[USSREQ Suc CD Msglen]

USSNOT_Suc_CD_Msglen
[USSNOT Suc CD Msglen]

SRS_Suc_CD_Msglen [SRS
Suc CD Msglen]

RDS_Suc_CD_Msglen [RDS
Suc CD Msglen]

RSM_Suc_CD_Msglen
[RSM Suc CD Msglen]

ReadyForSM.
RD_Suc_CD_Msglen [RD
Suc CD Msglen]

RestoreData.
PurgeMS_Suc_CD_Msglen
[PurgeMS Suc CD Msglen]

PurgeMS.
ATI_Suc_CD_Msglen [ATI
Suc CD Msglen]

ATSI_Suc_CD_Msglen
[ATSI Suc CD Msglen]

AnyM_Suc_CD_Msglen
[AnyM Suc CD Msglen]

SP_Suc_CD_Msglen [SP Suc

CD Msglen]

SendParameters.
...........................................................................................................................................................................................................................................................
A - 142

270-710-919R6.0
SPA DB Name [View

Attribute Name]
Description
UPLGPRS_Suc_CD_Msglen
[UPLGPRS Suc CD Msglen]

UpdateGprsLocation.
SRIGPRS_Suc_CD_Msglen
[SRIGPRS Suc CD Msglen]

FR_Suc_CD_Msglen [FR
Suc CD Msglen]

FailureReport.
CNL_Suc_CD_Msglen [CNL
Suc CD Msglen]

CancelLocation.
DSD_Suc_CD_Msglen [DSD
Suc CD Msglen]

NPG_Suc_CD_Msglen [NPG
Suc CD Msglen]

PRN_Suc_CD_Msglen [PRN
Suc CD Msglen]

FWCKSSIND_Suc_CD_Msg
len [FWCKSSIND Suc CD
Msglen]

NSDM_Suc_CD_Msglen
[NSDM Suc CD Msglen]

PSI_Suc_CD_Msglen [PSI
Suc CD Msglen]

AlertSC_Suc_CD_Msglen
[AlertSC Suc CD Msglen]

AlertServiceCenter.
InformSC_Suc_CD_Msglen
[InformSC Suc CD Msglen]

...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 143
SPA DB Name [View

Attribute Name]
UMTS DC Msglen
Description
ATM_Suc_CD_Msglen
[ATM Suc CD Msglen]

ActivateTraceMode.
DTM_Suc_CD_Msglen
[DTM Suc CD Msglen]

SetMWD_Suc_CD_Msglen
[SetMWD Suc CD Msglen]

NoteMP_Suc_CD_Msglen
[NoteMP Suc CD Msglen]

NoteMSPresent.
SRILCS_Suc_CD_Msglen
[SRILCS Suc CD Msglen]

PUSSD_Suc_CD_Msglen
[PUSSD Suc CD Msglen]

GPW_Suc_CD_Msglen
[GPW Suc CD Msglen]

GetPassword.
Table A-78, "UMTS DC Msglen" (A-144) records the measurements

for successful GSM/UMTS DBCom-related message length processed
by the HDF node. This table is called
HDF_MEAS_UMTS_DC_Msglen in MAS database
Table A-78
UMTS DC Msglen
SPA DB Name [View

Attribute Name]
Description
UPL_Suc_DC_Msglen [UPL
Suc DC Msglen]

UpdateLocation.
ISD_Suc_DC_Msglen [ISD
Suc DC Msglen]

...........................................................................................................................................................................................................................................................
A - 144

270-710-919R6.0
SPA DB Name [View

Attribute Name]
Description
SAI_Suc_DC_Msglen [SAI
Suc DC Msglen]

AFR_Suc_DC_Msglen [AFR
Suc DC Msglen]

SendIMSI_Suc_DC_Msglen
[SendIMSI Suc DC Msglen]

SendIMSI.
SRI_Suc_DC_Msglen [SRI
Suc DC Msglen]

SendRoutingInfo.
RegSS_Suc_DC_Msglen
[RegSS Suc DC Msglen]

RegisterSS.
EraSS_Suc_DC_Msglen
[EraSS Suc DC Msglen]

messages from HDF to HCF for EraseSS.
ActSS_Suc_DC_Msglen
[ActSS Suc DC Msglen]

ActivateSS.
DeactSS_Suc_DC_Msglen
[DeactSS Suc DC Msglen]

DeactivateSS.
RegPW_Suc_DC_Msglen
[RegPW Suc DC Msglen]

RegisterPassword.
IntSS_Suc_DC_Msglen
[IntSS Suc DC Msglen]

InterrogateSS.
PUSSREQ_Suc_DC_Msglen
[PUSSREQ Suc DC Msglen]

USSREQ_Suc_DC_Msglen
[USSREQ Suc DC Msglen]

...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 145
SPA DB Name [View

Attribute Name]
Description
USSNOT_Suc_DC_Msglen
[USSNOT Suc DC Msglen]

SRS_Suc_DC_Msglen [SRS
Suc DC Msglen]

RDS_Suc_DC_Msglen [RDS
Suc DC Msglen]

RSM_Suc_DC_Msglen
[RSM Suc DC Msglen]

ReadyForSM.
RD_Suc_DC_Msglen [RD
Suc DC Msglen]

RestoreData.
PurgeMS_Suc_DC_Msglen
[PurgeMS Suc DC Msglen]

PurgeMS.
ATI_Suc_DC_Msglen [ATI
Suc DC Msglen]

ATSI_Suc_DC_Msglen
[ATSI Suc DC Msglen]

AnyM_Suc_DC_Msglen
[AnyM Suc DC Msglen]

SP_Suc_DC_Msglen [SP Suc

DC Msglen]

SendParameters.
UPLGPRS_Suc_DC_Msglen
[UPLGPRS Suc DC Msglen]

UpdateGprsLocation.
SRIGPRS_Suc_DC_Msglen
[SRIGPRS Suc DC Msglen]

...........................................................................................................................................................................................................................................................
A - 146

270-710-919R6.0
SPA DB Name [View

Attribute Name]
Description
FR_Suc_DC_Msglen [FR
Suc DC Msglen]

FailureReport.
CNL_Suc_DC_Msglen [CNL
Suc DC Msglen]

CancelLocation.
DSD_Suc_DC_Msglen [DSD
Suc DC Msglen]

NPG_Suc_DC_Msglen [NPG
Suc DC Msglen]

PRN_Suc_DC_Msglen [PRN
Suc DC Msglen]

FWCKSSIND_Suc_DC_Msg
len [FWCKSSIND Suc DC
Msglen]

NSDM_Suc_DC_Msglen
[NSDM Suc DC Msglen]

PSI_Suc_DC_Msglen [PSI
Suc DC Msglen]

AlertSC_Suc_DC_Msglen
[AlertSC Suc DC Msglen]

AlertServiceCenter.
InformSC_Suc_DC_Msglen
[InformSC Suc DC Msglen]

ATM_Suc_DC_Msglen
[ATM Suc DC Msglen]

ActivateTraceMode.
DTM_Suc_DC_Msglen
[DTM Suc DC Msglen]

...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 147
SPA DB Name [View

Attribute Name]
Description
SetMWD_Suc_DC_Msglen
[SetMWD Suc DC Msglen]

NoteMP_Suc_DC_Msglen
[NoteMP Suc DC Msglen]

NoteMSPresent.
SRILCS_Suc_DC_Msglen
[SRILCS Suc DC Msglen]

PUSSD_Suc_DC_Msglen
[PUSSD Suc DC Msglen]

GPW_Suc_DC_Msglen
[GPW Suc DC Msglen]

GetPassword.
...........................................................................................................................................................................................................................................................
A - 148

270-710-919R6.0

............................................................................................................................................................................................................................................................
HSS Suc Transcnt
Table A-79, "HSS Suc Transcnt" (A-149) records the measurements for
successful HSS transactions processed by the HDF. This table is called
HDF_MEAS_HSS_Transcnt in MAS database.
Table A-79
HSS Suc Transcnt
DB Name[View Attribute
Name]
HSS Suc CD Msgcnt
Description
SAR_SAA_Suc_Transcnt[SA
R/SAA Suc Transcnt]
The number of successful SAR/SAA

transactions
MAR_MAA_Suc_Transcnt[
MAR/MAA Suc Transcnt]
The number of successful MAR/MAA

transactions
UAR_UAA_Suc_Transcnt[U
AR/UAA Suc Transcnt]
The number of successful UAR/UAA

transactions
LIR_LIA_Suc_Transcnt[LIR/
LIA Suc Transcnt]
The number of successful LIR/LIA

transactions
RTR_RTA_Suc_Transcnt[RT
R/RTA Suc Transcnt]
The number of successful RTR/RTA

transactions
PPR_PPA_Suc_Transcnt[PP
R/PPA Suc Transcnt]
The number of successful PPR/PPA

transactions
UDR_UDA_Suc_Transcnt[U
DR/UDA Suc Transcnt]
The number of successful UDR/UDA

transactions
PUR_PUA_Suc_Transcnt[PU
R/PUA Suc Transcnt]
The number of successful PUR/PUA

transactions
SNR_SNA_Suc_Transcnt[SN
R/SNA Suc Transcnt]
The number of successful SNR/SNA

transactions
PNR_PNA_Suc_Transcnt[PN
R/PNA Suc Transcnt]
The number of successful PNR/PNA

transactions
Table A-80, "HSS Suc CD Msgcnt" (A-150) records the measurements

for successful HSS CD message count processed by the HDF node.
This table is called HDF_MEAS_HSS _CD_Msgcnt in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 149
Table A-80
HSS Suc CD Msgcnt
Name]
HSS Suc DC Msgcnt
Description
SAR_SAA_Suc_CD_Msgcnt
[SAR/SAA Suc CD Msgcnt]

messages from HCF to HDF for SAR/
SAA
MAR_MAA_Suc_CD_Msgc
nt[MAR/MAA Suc CD
Msgcnt]

messages from HCF to HDF for MAR/
MAA
UAR_UAA_Suc_CD_Msgcn
t[UAR/UAA Suc CD
Msgcnt]

messages from HCF to HDF for UAR/
UAA
LIR_LIA_Suc_CD_Msgcnt[
LIR/LIA Suc CD Msgcnt]

messages from HCF to HDF for LIR/LIA
RTR_RTA_Suc_CD_Msgcnt[
RTR/RTA Suc CD Msgcnt]

messages from HCF to HDF for RTR/
RTA
PPR_PPA_Suc_CD_Msgcnt[
PPR/PPA Suc CD Msgcnt]

messages from HCF to HDF for PPR/
PPA
UDR_UDA_Suc_CD_Msgcn
t[UDR/UDA Suc CD
Msgcnt]

messages from HCF to HDF for UDR/
UDA
PUR_PUA_Suc_CD_Msgcnt
[PUR/PUA Suc CD Msgcnt]

messages from HCF to HDF for PUR/
PUA
SNR_SNA_Suc_CD_Msgcnt
[SNR/SNA Suc CD Msgcnt]

messages from HCF to HDF for SNR/
SNA
PNR_PNA_Suc_CD_Msgcnt
[PNR/PNA Suc CD Msgcnt]

messages from HCF to HDF for PNR/
PNA
Table A-81, "HSS Suc DC Msgcnt" (A-151) records the measurements

for successful HSS DBCom-related message count processed by the
HDF node. This table is called HDF_MEAS_HSS_DC_Msgcnt in
MAS database.
...........................................................................................................................................................................................................................................................
A - 150

270-710-919R6.0
Table A-81
HSS Suc DC Msgcnt
Name]
HSS Suc CD Msglen
Description
SAR_SAA_Suc_DC_Msgcnt
[SAR/SAA Suc DC Msgcnt]

messages from HDF to HCF for SAR/
SAA
MAR_MAA_Suc_DC_Msgc
nt[MAR/MAA Suc DC
Msgcnt]

messages from HDF to HCF for MAR/
MAA
UAR_UAA_Suc_DC_Msgcn
t[UAR/UAA Suc DC
Msgcnt]

messages from HDF to HCF for UAR/
UAA
LIR_LIA_Suc_DC_Msgcnt[
LIR/LIA Suc DC Msgcnt]

messages from HDF to HCF for LIR/LIA
RTR_RTA_Suc_DC_Msgcnt[
RTR/RTA Suc DC Msgcnt]

messages from HDF to HCF for RTR/
RTA
PPR_PPA_Suc_DC_Msgcnt[
PPR/PPA Suc DC Msgcnt]

messages from HDF to HCF for PPR/
PPA
UDR_UDA_Suc_DC_Msgcn
t[UDR/UDA Suc DC
Msgcnt]

messages from HDF to HCF for UDR/
UDA
PUR_PUA_Suc_DC_Msgcnt
[PUR/PUA Suc DC Msgcnt]

messages from HDF to HCF for PUR/
PUA
SNR_SNA_Suc_DC_Msgcnt
[SNR/SNA Suc DC Msgcnt]

messages from HDF to HCF for SNR/
SNA
PNR_PNA_Suc_DC_Msgcnt
[PNR/PNA Suc DC Msgcnt]

messages from HDF to HCF for PNR/
PNA
Table A-82, "HSS Suc CD Msglen" (A-152) records the measurements

for successful HSS CD message length processed by the HDF node.
This table is called HDF_MEAS_HSS_CD_Msglen in MAS database.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 151
Table A-82
HSS Suc CD Msglen
Name]
HSS Suc DC Msglen
Description
SAR_SAA_Suc_CD_Msglen
[SAR/SAA Suc CD Msglen]

messages from HCF to HDF for SAR/
SAA
MAR_MAA_Suc_CD_Msgle
n[MAR/MAA Suc CD
Msglen]

messages from HCF to HDF for MAR/
MAA
UAR_UAA_Suc_CD_Msgle
n[UAR/UAA Suc CD
Msglen]

messages from HCF to HDF for UAR/
UAA
LIR_LIA_Suc_CD_Msglen[
LIR/LIA Suc CD Msglen]

messages from HCF to HDF for LIR/LIA
RTR_RTA_Suc_CD_Msglen[
RTR/RTA Suc CD Msglen]

messages from HCF to HDF for RTR/
RTA
PPR_PPA_Suc_CD_Msglen[
PPR/PPA Suc CD Msglen]

messages from HCF to HDF for PPR/
PPA
UDR_UDA_Suc_CD_Msgle
n[UDR/UDA Suc CD
Msglen]

messages from HCF to HDF for UDR/
UDA
PUR_PUA_Suc_CD_Msglen
[PUR/PUA Suc CD Msglen]

messages from HCF to HDF for PUR/
PUA
SNR_SNA_Suc_CD_Msglen
[SNR/SNA Suc CD Msglen]

messages from HCF to HDF for SNR/
SNA
PNR_PNA_Suc_CD_Msglen
[PNR/PNA Suc CD Msglen]

messages from HCF to HDF for PNR/
PNA
Table A-83, "HSS Suc DC Msglen" (A-153) records the measurements

for successful HSS DBCom-related message length processed by the
HDF node.
This table is called HDF_MEAS_HSS_DC_Msglen in MAS database.
...........................................................................................................................................................................................................................................................
A - 152

270-710-919R6.0
Table A-83
HSS Suc DC Msglen
Name]
Description
SAR_SAA_Suc_DC_Msglen
[SAR_SAA Suc DC Msglen]

messages from HDF to HCF for SAR/
SAA
MAR_MAA_Suc_DC_Msgle
n[MAR_MAA Suc DC
Msglen]

messages from HDF to HCF for MAR/
MAA
UAR_UAA_Suc_DC_Msgle
n[UAR_UAA Suc DC
Msglen]

messages from HDF to HCF for UAR/
UAA
LIR_LIA_Suc_DC_Msglen[
LIR_LIA Suc DC Msglen]

messages from HDF to HCF for LIR/LIA
RTR_RTA_Suc_DC_Msglen[
RTR_RTA Suc DC Msglen]

messages from HDF to HCF for RTR/
RTA
PPR_PPA_Suc_DC_Msglen[
PPR_PPA Suc DC Msglen]

messages from HDF to HCF for PPR/
PPA
UDR_UDA_Suc_DC_Msgle
n[UDR_UDA Suc DC
Msglen]

messages from HDF to HCF for UDR/
UDA
PUR_PUA_Suc_DC_Msglen
[PUR_PUA Suc DC Msglen]

messages from HDF to HCF for PUR/
PUA
SNR_SNA_Suc_DC_Msglen
[SNR_SNA Suc DC Msglen]

messages from HDF to HCF for SNR/
SNA
PNR_PNA_Suc_DC_Msglen
[PNR_PNA Suc DC Msglen]

messages from HDF to HCF for PNR/
PNA
...........................................................................................................................................................................................................................................................
270-710-919R6.0

A - 153
...........................................................................................................................................................................................................................................................
A - 154

270-710-919R6.0
USDS OM logs
Overview
............................................................................................................................................................................................................................................................
Purpose
This chapter provides the detailed description of OM Logs supported in

USDS.
Only OM Logs of USDS are covered in this chapter.
For platform OM Logs, refer to MAS User Reference Guide (270700-176).
Important!
The %s, %d, %x in the message body are parameters

in the message.
Important!
Contents

System integrity
B-3
HDF measurement
B-21
HCF Index Server
B-22
ANSI Authentication
B-24
B-36
ANSI Call Delivery
B-40
B-52
B-54
............................................................................................................................................................................................................................................................
270-710-919R6.0

B - 1
USDS OM logs
ANSI short message
B-56
B-58
UMTS framework
B-67
UMTS authentication
B-68
UMTS CAMEL
B-70
HSS overload
B-71
HSS authentication
B-72
HSS feature lock
B-73
HSS call handling
B-74
B-78
SMPP specified
B-79
...........................................................................................................................................................................................................................................................
B - 2

270-710-919R6.0
System integrity
USDS OM logs
System integrity
............................................................................................................................................................................................................................................................
Table B-1
System Integrity
Identifier
Message
Description
Default
Severity
10001
HDF UNABLE TO
CREATE/INITIALIZ
E DATABASE
OBJECTS
This message
indicates that the
HDF failed to
create database
objects.
Major
10002
HDF UNABLE TO
CREATE/INITIALIZ
E CHT CORC
OBJECTS
This message
indicates that the
HDF failed to
create the CHT
CORC objects.
Major
10003
HDF DETECTED
TIMESTEN
DATABASE
FAILURE
This message
indicates that the
HDF detected a
TimesTen
database failure.
Critical
10004
HDF DETECTED
TIMESTEN
DATABASE
REPLICATION
FAILURE\n
(PRIMARY HDF
MATE)
CONTINUING
OPERATION\n
This message
indicates that the
HDF detected a
TimesTen
database
replication
failure. But the
primary HDF is
still working.
Information
10005
HDF DETECTED
TIMESTEN
DATABASE
REPLICATION
FAILURE\n
(SECONDARY HDF
MATE)
SUSPENDING
OPERATION UNTIL
REPLICATION
RECOVERS\n
This message
indicates that the
HDF detected
TimesTen
database
replication
failure. The
secondary HDF
stops working.
Major
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 3
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10006
HDF DETECTED
TIMESTEN
DATABASE
REPLICATION
RECOVERY\n(PRIM
ARY HDF MATE)
CONTINUING
OPERATION\n
This message
indicates that the
HDF detected
TimesTen
database
replication
recovery. The
primary HDF is
still working.
Information
10007
HDF DETECTED
TIMESTEN
DATABASE
REPLICATION
RECOVERY\n(SECO
NDARY HDF
MATE) RESUMING
OPERATION\n
This message
indicates that the
HDF detected
TimesTen
database
replication
recovery. The
secondary HDF
is resuming
operation.
Information
10008
HDF REQUESTING
APPLICATION
BOOT
This message
indicates that the
HDF requests
the application
to reboot.
Major
10009
APPLICATION
FAILOVER; NOW
BECOMING
PRIMARY HDF
MATE
This message
indicates that the
secondary HDF
becomes the
primary HDF.
Information
10010
APPLICATION
INTERNAL STATE
CHANGE\n
PREVIOUS STATE
%s, CURRENT
STATE %s
This message
indicates that the
application
internal status
changes.
Information
10011
HDF STARTING UP
AS SECONDARY
HDF MATE
This message
indicates that the
HDF starts up as
the secondary
HDF.
Information
...........................................................................................................................................................................................................................................................
B - 4

270-710-919R6.0
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10012
HDF OVERLOAD
CHANGED FROM
CURRENT LEVEL
%d\nTO NEW
LEVEL %d
This message
indicates that
HDF overload
level changes.
Information
10013
HDF OVLD
ABATED FROM %d
TO %d
This message
indicates the
HDF overload
level decreased.
Information
10014
HDF UNABLE TO
CREATE/INITIALIZ
E HDF STATUS
OBJECTS
This message
indicates that the
HDF failed to
create the HDF
status objects.
Information
10015
HDF UNABLE TO
CREATE/INITIALIZ
E MESUREMENT
OBJECTS
This message
indicates that the
HDF failed to
create the
measurement
objects.
Information
10016
HDF UNABLE TO
CREATE/INITIALIZ
E PRT OBJECTS
This message
indicates that the
HDF failed to
create PRT
objects.
Information
10017
"message=LB:MOVE
:Fail - error occurred
during the moving of
subscribers, reason =
%s. The following
subscribers failed to
be moved: \n%s\n"
This message
indicates that
HDF failed to
move a
subscriber
chunk.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 5
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10018
"message=LB:DELE
TE:Fail - error
occurred during the
deletion of
subscribers. The
following subscribers
moved successfully
but need to be deleted
manually on source
HDF: \n%s\n"
This message
indicates that
HDF failed to
delete a
subscriber
chunk.
Information
10019
"message=LB:MOVE
:Success - The
moved successfully:
\n%s\n"
This message
indicates that
HDF succeed to
Move a
subscriber
chunk.
Information
10020
"message=LB:MOVE
:Timeout - no
response from target
HDF within given
time. The following
subscribers failed to
be moved, there may
need to delete them
from the target DB
manually: \n%s\n"
This message
indicates that
Source HDF
fails to get a
response from
target.
Information
10021
"message=LB:DONE
- load balancing
procedure completed
with no error"
This message
indicates that
HDF completed
a whole load
balancing
procedure with
no error.
Information
10022
"message=LB:DONE
:Partially - load
balancing procedure
completed with error"
This message
indicates that
HDF completed
a whole load
balancing
procedure with
error.
Information
...........................................................................................................................................................................................................................................................
B - 6

270-710-919R6.0
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10023
"message=LB:STOPP
ED - load balancing
procedure stopped,
reason = %s"
This message
indicates that
Load balancing
procedure
stopped.
Information
10024
"message=LB:ISUPD
ATE:Fail - The
failed to be updated in
index server: \n%s\n"
This message
indicates that
Load balancing
update index
server failed.
Information
10025
"message=LB:PARSE
:Fail - The
MOVESUB
command parsing
failed, reason = %s"
This message
indicates that
MOVESUB
command
parsing failed.
Information
10026
"message=LB:START
- Load Balancing is
started by Request
ID(%s), %d
subscribers will be
moved to %s\n"
This message
indicates that
Load Balancing
has started.
Information
10027
"message=LB:DUPR
EQUEST - HDF
received a Load
Balancing request
with the same
CorID(%s) of the ongoing Load Balancing
process, ignore the
request.\n"
This message
indicates that
HDF received a
Load Balancing
request with the
same CorID(%s)
as the on-going
Load Balancing
process, ignore
the request.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 7
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10028
"message=LB:REJEC
T:NEWREQEST There is another ongoing Load
Balancing(CorID:%s)
, new Load Balancing
request(CorID:%s)
cannot proceed.\n"
This message
indicates that
there is another
on-going Load
Balancing(CorI
D:%s) on going.
The new Load
Balancing
request(CorID:
%s) cannot
proceed.
Information
10029
"message=LB:INIT:F
AIL - Load Balancing
init failed due to
following reason:
%s\n"
This message
indicates that
Load Balancing
init failed due to
following
reason.
Information
10031
"message=SNDTEXT
:NEW - New
SNDTEXT message
received:\n%s\n"
This message
indicates that
new SNDTEXT
message is
received:\n%s.
Information
10032
HDF FAILED TO
RECEIVE SITE
HEART BEAT,
REMOTE NODE %s.
This message
indicates that
HDF detected
miss site heart
beat from
remote node.
Information
10033
HDF DETECTED
SPA STATE
CHANGE ON
REMOTE SITE,
HOST %s, OLD
STATE %s, NEW
STATE %s.
This message
indicates that
HDF detected
state change
happened on
remote node.
Information
...........................................................................................................................................................................................................................................................
B - 8

270-710-919R6.0
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10034
HDF FORWARDING
DBCOM MESSAGE
TO MPROC FAILED
This message
indicates HDF
failed to send a
message to the
MPROC for call
processing or
data
provisioning
Information
10035
logs for dump df

status info by
sendtext: dump df,
mate, and cf amount
This message
indicates that
logs for dump df
status info by
sendtext: dump
df, mate, and cf
amount
Information
10036
logs for dump df

status info by
sendtext: CF status
one by one
This message
indicates that
logs for dump df
status info by
sendtext: CF
status one by
one
Information
10037
logs for dump df

status info by
sendtext: node in mate
site one by one
This message
indicates that
logs for dump df
status info by
sendtext: node
in mate site one
by one
Information
10038
HDF detect HCF

supported protocols
changed.
This message
indicates that
HDF detect
HCF supported
protocols
changed.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 9
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10039
HCF detected remote

HCF supported
protocols changed
This message
indicates that
HCF detected
remote HCF
supported
protocols
changed
Information
10041
HDF DETECT
LOCAL MPROC IS
NOT ACIVE.
This message
indicates that
HDF detected
MPROC process
dead on local
node.
Information
10042
HDF DETECT
MPROC QUEUE
OVERLOAD,
OCCUPANCY is %d.
This message
indicates that
HDF detected
MPROC queue
on remote site
overload.
Information
10043
HDF DETECTED
THREAD SANITY
TIMEOUT
This message
indicates that
HDF
DETECTED
THREAD
SANITY
TIMEOUT
Information
10044
HDF DETECTED
CORCLST table in
TimesTen is empty!
This message
indicates that
HDF
DETECTED
CORCLST table
in TimesTen is
empty!
Information
10045
HDF UPDATE
CORCLIST IN
TIMESTEN
This message
indicates that
HDF UPDATE
CORCLIST IN
TIMESTEN
Information
...........................................................................................................................................................................................................................................................
B - 10

270-710-919R6.0
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10046
HDF UPDATE
CORCLIST IN
MEMORY
This message
indicates that
HDF UPDATE
CORCLIST IN
MEMORY
Information
10047
"ANSIMSCID_DYN
AMIC TABLE FOR
MSCID %s UPDATE
OPERATION
ABANDON\nFOR
DF PAIR: DF %s and
DF %s\nAFTER
TRYING %d TIME
S\n"
This message
indicates that
USDS
abandoned
dynamic global
data update
operation.
Information
10101
PUTTING HDF %d
INTO OOS
STATE\nREASON:
MISSED %d
HEARTBEATS\n
This message
indicates that the
HDF goes into
OOS state due to
some reason.
Information
10102
HCF PROCESS INIT

COMPLETE,
REQUESTING
GLOBAL DATA
This message
indicates that the
HCF completes
the INIT process
and it is
requesting
global data from
the HDF.
Information
10103
HDFPAIR %d,%d
CHANGED STATE
FROM %s TO %s\n
This message
indicates that the
listed HDF pair
changes state.
Information
10104
HDF %d CHANGED
STATE FROM %s TO
%s\n
This message
indicates that the
listed HDF
changes state.
Information
10105
HDF %d IS THE
NEW PRIMARY
HDF\n
This message
indicates that the
listed HDF is the
new primary
HDF.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 11
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10106
Primary HDF for

HDF pair %d,%d is
%s
This message
reports the
primary HDF
for the listed
HDF pair.
Information
10107
Cannot find In
Service primary DF
for HDF pair
This message
indicates that the
USDS cannot
find alive
primary HDF
for a HDF pair.
Information
10108
HCF REQUESTING
APPLICATION
BOOT\nREASON:
FAILED TO
CREATE %s
PROCESS
This message
indicates that the
HCF is
requesting for
application
reboot because it
cannot create the
process.
Major
10109
HCF REQUESTING
APPLICATION
BOOT\nREASON:
%s PROCESS
DIED\n
This message
indicates that the
HCF is
requesting for
application
reboot because
the listed
process died.
Major
10110
HCF PROCESS INIT

COMPLETE,
REQUESTING
INDEX SERVER
DATA
This message
indicates that the
HCF INIT
complete, it is
requesting data
from the Index
Server.
Information
10111
HCF REQUESTING
PDLS / CLS
PROCESS
CREATION
This message
indicates that the
HCF is
requesting to
create
PDLS/CLS.
Information
...........................................................................................................................................................................................................................................................
B - 12

270-710-919R6.0
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10112
HCF NUMBER OF
PDLS STARTED =
%d \n
This message
reports the
number of
PDLS started.
Information
10113
HCF NUMBER OF
CLS STARTED = %d
\n
This message
reports the
number of CLS
started.
Information
10114
HCF NUMBER OF
CIF STARTED = %d
\n
This message
reports the
number of CIF
started.
Information
10115
HDF OVLD
INCREASED FROM
%d TO %d\n
This message
indicates that the
HDF overload
level increased.
Information
10116
HDF OVLD
ABATED FROM %d
TO %d\n
This message
indicates that the
HDF overload
level decreased.
Information
10117
SPA MIB STATUS

CHANGED TO BE
OOS
This message
indicates that
SPA MIB status
is changed to
OOS state.
Information
10118
SPA MIB STATUS

CHANGED TO BE
IS
This message
indicates that the
SPA MIB status
is changed to IS
state.
Information
10119
HCF PROCESS INIT

COMPLETE,
REQUESTING
INDEX SERVER
DATA FOR
AUTOMATIC
MODE\n
This message
reports that the
automatic mode
is used for Index
Server FULL
INIT procedure
when HCF SPA
starts up.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 13
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10120
HCF PROCESS INIT

COMPLETE,
PLEASE DO
MANUAL INDEX
SERVER FULL INIT
PROCEDURE
LATER\n
This message
reports that the
manual mode is
used for Index
Server FULL
INIT procedure
when HCF SPA
starts up and
expect that site
personnel will
initiate
"FULLINIT:IS[,
CLEANUP]"
input message
manually soon.
Information
10121
HCF PROCESS INIT

COMPLETE, RESYNCHRONIZING
INDEX SERVER
DATA FOR
MANUAL MODE\n
This message
reports that
Index Server Re
synchronization
will be initiated
automatically
although manual
mode of FULL
INIT procedure
is used when
HCF SPA starts
up.
Information
10122
HCF REQUESTING
INDEX SERVER
DATA FAILED\n
This message
reports that
Index Server
FULL INIT
procedure failed
when HCF SPA
starts up and
expect that site
personnel will
find the root
cause and do
some corrective
action, and then
re-start the HCF
SPA.
Major
...........................................................................................................................................................................................................................................................
B - 14

270-710-919R6.0
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10123
HCF INDEX
SERVER DATA
DOWNLOAD
COMPLETE\n
This message
reports that
Index Server
data download
was completed
successfully
when the HCF
SPA starts up.
Information
10124
HCF EXISTED DUE

TO CONFIGURED
PDLS NUMBER
EXCEED
Max_pdls_per_node\
n
This message
indicates that
HCF existed due
to the
configured
PDLS number
exceeds the
maximum
allowed value.
Information
10125
FIRST DF UP NOW,
WAIT %d SECONDS
FOR DFS TO COME
IN
This message
indicates that the
first DF is up,
still waiting for
a while for other
HDFs.
Information
10126
INDEXSERVER
RESYNCHRONIZE
NOT DONE, WAIT
ANOTHER %d
SECONDS
This message
indicates that the
index server resynchronization
is not done.
Information
10127
HCF REQUESTING
INDEX SERVER
DATA FROM DF %d
(OR ITS MATE)
FAILED\n
This message
indicates that the
HCF's
requesting for an
index server data
resynchronization
failed.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 15
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10128
IS UPDATE SEQ
NUM MAY BE
INCONTINUOUS:
LAST %d
INCRAEMENT %d
CURRENT %d\n
This message
indicates that the
index server data
internal
sequence
number is not
continuous.
Information
10129
HCF REQUESTING
INDEX SERVER
DATA FAILED DUE
TO PEER PUMP
TIMED OUT\n
This message
indicates that
HCF failed to do
a peer pump due
to time out.
Information
10139
INDEX SERVER
PEER PUMP FROM
CF(%d) FAILED,
REASON %s\n
This message
indicates that the
HCF index
server peer
pump failed due
to the listed
reason.
Information
10140
%s: SSN(s) %s
CHANGED TO IS
BECAUSE
BLOCKING
EVENTS CLEARED
This message
indicates that
%s: SSN(s) %s
CHANGED TO
IS BECAUSE
BLOCKING
EVENTS
CLEARED
Major
10141
%s: SSN(s) %s
CHANGED TO OOS
DUE TO
BLOCKING
EVENTS
OCCURRED
This message
indicates that
%s: SSN(s) %s
CHANGED TO
OOS DUE TO
BLOCKING
EVENTS
OCCURRED
Major
...........................................................................................................................................................................................................................................................
B - 16

270-710-919R6.0
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10142
HDF state is manually

change to be BAD
state
This message
indicates that
HDF state is
manually
changed to BAD
state
Information
10143
message="HCF
PROCESS GLOBAL
DATA DOWNLOAD
COMPLETE from
DF, %s\n
This message
indicates that
HCF process
global data
download
complete from
DF.
Information
10301
CLS REQUESTING
APPLICATION
BOOT\nREASON:
%s PROCESS DIED
This message
indicates that the
CLS is
requesting
application
reboot because
some process
died.
Major
10401
PDLS REQUESTING
APPLICATION
BOOT\nREASON:
%s PROCESS DIED
This message
indicates that
PDLS is
requesting
application
reboot because
some process
died.
Major
10402
HCF LOST
CONNECTIVITY
TO ALL HDFS,
BLOCKING SS7
LINKS
This message
indicates that the
HCF lost
connection to all
HDFs, the SS7
links to this
HCF is blocked.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 17
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10403
HCF
CONNECTIVITY
TO HDFS
RESTORED,
BRINGING SS7
LINKS UP
This message
indicates that
HCF resumes
connection to
the HDFs. The
SS7 link to this
HCF is
resuming.
Information
10404
PDLS GLOBAL
DATA DOWNLOAD
COMPLETE.
This message
indicates that the
PDLS global
data download
completes
successfully.
Information
10405
PDLS GLOBAL
DATA DOWNLOAD
FAILURE
This message
indicates that the
PDLS global
data download
failed.
Information
10406
PDLS BIND TO
MAP SUCCESS
This message
indicates that the
PDLS bind to
map
successfully.
Information
10407
THE POINT CODE

CAN NOT BE GOT
This message
indicates the
system can not
get the Point
Code.
Information
10408
"message=FM:Send
out an overlong msg
which is not
supported by
destination (Feature
S&R)"
This message
indicates that an
overlong
message is sent,
but the
destination does
not support
parameter
suppression and
reassembly.
Information
...........................................................................................................................................................................................................................................................
B - 18

270-710-919R6.0
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
10410
message = MAX
SESSION NUMBER
EXCEEDED
This message
indicates that
max session
number in a
PDLS is
exceeded.
Major
10411
message = MAX AO
NUMBER
EXCEEDED
This message
indicates that
max AO number
in a PDLS is
exceeded.
Major
10501
PROH_WAN feature
is not effective due to
network configuration
though feature lock is
on
This message
indicates that
prohibiting
WAN traffic
feature is not
effective due to
network
configuration;
although the
feature lock is
on.
Information
10601
PLATFORM
CARGO TIMER
RESET TO
This message
indicates the
value the
platform cargo
timer is reset to.
Information
10701
message=[%s]
OPERATION ON
[%s]\n\tKEY:[%s]\n\t
RESULT:[%s].
This message
indicates the
result of data
change through
SPA RC/V.
Information
11101
HCF REQUESTING
APPLICATION
BOOT\nREASON:
%s PROCESS
DIED\n
This message
indicates that the
HCF is
requesting
application
reboot because
some process
died.
Major
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 19
System integrity
USDS OM logs
Identifier
Message
Description
Default
Severity
11201
Record Format Trace

Content in OMLog
File
This message
indicates that the
format trace
feature is
activated.
Information
...........................................................................................................................................................................................................................................................
B - 20

270-710-919R6.0
HDF measurement
USDS OM logs
HDF measurement
............................................................................................................................................................................................................................................................
Table B-2
HDF measurement
Identifier
Message
Description
Default
Severity
20001
"message=DfMeas
:HDF - DF %s
(%d) did not
receive meas from
the following
HCFs: \n%s\n"
This message
indicates that the
HDF did not get
measurement
counts from the
HCF listed in the
message.
Minor
20002
"message=DfMeas
:HCF - Meas not
sent to DF. cf id
%d, target df id
%d, target df name
%s, reason %s\n"
This message
indicates that the
HCF failed to send
the measurement
counts to the HDF
listed in the
message.
Minor
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 21
HCF Index Server
USDS OM logs
HCF Index Server

............................................................................................................................................................................................................................................................
Table B-3
HCF Index Server
Identifier
Message
Description
Default
Severity
10201
Both HDF =%d

and MATE HDF
ARE OOS, CAN'T
ACCESS DB\n
This message
indicates that both
HDFs in a HDF
pair are in OOS
state.
Information
10202
INDEX SERVER
FULL INIT
DOWNLOAD
DATA STATUS =
%d \n
This message
reports the status of
index server full
init.
Information
10203
INDEX SERVER
FULL INIT
UPDATE DB
PROGRESS:
%d%% for key %s
of DF %d\n
This message
reports the status of
index server full
init DB update
progress.
Information
10204
INDEX SERVER
FULL INIT
TIMER EXPIRED
%d times\n
This message
indicates that the
Index Sever full init
timer expired.
Information
10205
HCF INIT
PROGESSS,
INDEX SERVER
DATA
DOWNLOAD
COMPLETE
This message
reports that Index
Server data
download
completed
successfully.
Information
10206
INDEX SERVER
DOWNLOAD
FAILED BY ONE
DF %d \n
This message
indicates that Index
Server data re
synchronization
failed on one HDF.
Major
10207
INDEX SERVER
FULL INIT
UPDATE DB
PROGRESS
FROM PEER: %u
/ %u for key: %s\n
This message
reports the number
of records that were
installed into DB
for a kind of key on
the HCF.
Information
10208
"NO DF IN
SERVICE, INDEX
SERVER HAVE
NO DATA TO
DOWNLOAD\n"
This message
indicates that no
HDF in service,
index server has no
data to download.
Information
...........................................................................................................................................................................................................................................................
B - 22

270-710-919R6.0
HCF Index Server
USDS OM logs
10209
HCF TIMEOUT
WAITING FOR
RESPONSE
FROM DF: %s\n
This message
indicates that HCF
timeout occurred
waiting for
response from
HDF.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 23
ANSI Authentication
USDS OM logs
ANSI Authentication
............................................................................................................................................................................................................................................................
Table B-4
ANSI Authentication
Identifier
Message
Description
Default
Severity
32001
"message=AUTH:A
C:SSD:Success received
AuthenticationStatus
Report INVOKE
from MSC/VLR with
SSDUpdateReport
and
UniqueChallengeRep
ort parameters both
equal to 3"
This message
indicates that the
SSD Update is
successful.
Information
"message=AUTH:A
C:SSD:Fail - no
AuthenticationDirect
ive RETURN
RESULT received
from the serving
MSC/VLR for the
SSD update request
after the Inter
Network Element
Timer expired"
This message
indicates that the
SSD Update
failed.
32002
Both
SSDUpdateRepor
t and
UniqueChallenge
Report parameters
in the
AuthenticationSta
tusReport Invoke
from the
MSC/VLR are
equal to "3".
Information
There is no
AuthenticationDir
ective Return
Result from the
serving
MSC/VLR for the
SSD Update
request after the
Inter Network
Element Timer
expired.
...........................................................................................................................................................................................................................................................
B - 24

270-710-919R6.0
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32003
"message=AUTH:A
C:SSD:Fail- received
an
ive Return Error
from the serving
MSC/VLR "
This message
indicates that the
SSD Update
failed.
Information
"message=AUTH:A
C:SSD:Fail- Failed
to receive
BaseStationChalleng
e INVOKE from the
MSC/VLR (SSD not
shared) after the Inter
Network Element
Timer expired"
This message
indicates that the
SSD Update
failed.
"message=AUTH:A
C:SSD:Fail- Failed
to receive %s from
the MSC/VLR When
SSD UPdate
Procedure Time Out,
%s"
This message
indicates that the
SSD Update
failed.
32004
32005
An
AuthenticationDir
ective Return
Error was
received from the
serving
MSC/VLR.
Information
The USDS failed

to receive the
BaseStationChall
enge Invoke from
the MSC/VLR
(SSD not shared)
after the Inter
Network Element
Timer expired.
Information
The USDS failed

to receive %s
from the
MSC/VLR when
SSD Update
Procedure Time
Out.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 25
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32006
"message=AUTH:A
Report INVOKE
from the VLR with
SSDUpdateReport
value = 4"
This message
indicates that the
SSD Update
failed.
Information
"message=AUTH:A
Report INVOKE
from the MSC/VLR
with
UniqueChallengeRep
ort value = 4"
This message
indicates that the
SSD Update
failed.
"message=AUTH:A
SSDUpdateReport or
UniqueChallengeRep
ort with value = 1"
This message
indicates that the
SSD Update or
Unique Challenge
is not attempted.
32007
32008
The USDS
receives an
AuthenticationSta
tusReport Invoke
from the
MSC/VLR with
the
SSDUpdateRepor
t value set to "4".
Information
The USDS
receives an
AuthenticationSta
tusReport Invoke
from the
MSC/VLR with
the
UniqueChallenge
Report value set
to 4.
Information
The USDS
received an
AuthenticationSta
tusReport with
SSDUpdateRepor
t or
UniqueChallenge
Report value set
to 1.
...........................................................................................................................................................................................................................................................
B - 26

270-710-919R6.0
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32009
"message=AUTH:A
SSDUpdateReport or
UniqueChallengeRep
ort with value = 2 (or
isn't present, or value
= 0 unknown). MS is
likely either not
powered up, not
authentication
capable or in a RF
fade"
This message
indicates the SSD
Update or unique
challenge failed.
Information
32010
"message=AUTH:A
C:SSD:Fail- There is
already an
authentication
procedure active/in
progress with the
particular MS in the
AC"
This message
indicates that the
SSD Update
failed because
there is already an
authentication
procedure in
progress with this
MS.
Information
32011
"message=AUTH:A
C:SSD:Fail- internal
errors/inconsistencie
s within the AC"
This message
indicates that the
SSD Update
failed due to the
internal
errors/inconsisten
cies of the AC.
Information
32012
"message=AUTH:A
an
ive Reject from the
serving MSC/VLR"
This message
indicates that the
SSD Update
failed because the
USDS received an
AuthenticationDir
ective Reject from
the serving
MSC/VLR.
Information
The reason may

be that there is no
response to SSD
Update or Unique
challenge or
SSDUpdateRepor
t or
UniqueChallenge
Report is not
present in the
received message.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 27
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32013
"message=AUTH:A
C:UniChal:Success received
Report INVOKE
from MSC/VLR with
UniqueChallengeRep
ort parameter equal
to 3 "
This message
indicates that the
Unique Challenge
is successful.
Information
"message=AUTH:A
C:UniChal:Fail - no
ive RETURN
RESULT received
from the serving
MSC/VLR for the
Unique Challenge
request after the Inter
Network Element
Time Out expired"
This message
indicates that the
Unique Challenge
failed.
"message=AUTH:A
C:UniChal:Fail received an
ive Return Error "
This message
indicates that the
Unique Challenge
failed.
32014
32015
The USDS
received an
AuthenticationSta
tusReport Invoke
from the
MSC/VLR with
the
UniqueChallenge
Report parameter
set to 3.
Information
There is no
AuthenticationDir
ective Return
Result received
from the serving
MSC/VLR for the
unique challenge
request after the
Inter Network
Element Time Out
expired.
Information
The USDS
received an
AuthenticationDir
ective Return
Error.
...........................................................................................................................................................................................................................................................
B - 28

270-710-919R6.0
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32016
"message=AUTH:A
C:UniChal:Fail Failed to receive
Report INVOKE
from the MSC/VLR
When Unique
Challenge Procedure
Time Out"
This message
indicates that the
Unique Challenge
failed.
Information
"message=AUTH:A
C:UniChal:Fail received
Report INVOKE
from the VLR with a
ReportType value
indicating that the
unique challenge
failed "
This message
indicates that the
Unique Challenge
failed.
"message=AUTH:A
C:UniChal:Fail there is already an
authentication
procedure active/in
progress in the AC"
This message
indicates that the
Unique Challenge
failed.
"message=AUTH:A
C:UniChal:Fail internal
errors/inconsistencie
s within the AC"
This message
indicates that the
Unique Challenge
failed.
32017
32018
32019
The USDS failed

to receive the
AuthenticationSta
tusReport Invoke
from the
MSC/VLR before
the Unique
Challenge
Procedure Time
Out.
Information
The USDS
received an
AuthenticationSta
tusReport Invoke
from the VLR
with a ReportType
value indicating
that the unique
challenge failed.
Information
There is already
an authentication
procedure in
progress in the
USDS.
Information
There are internal

errors/inconsisten
cies in the USDS.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 29
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32020
"message=AUTH:A
C:UniChal:Fail received an
ive reject from the
serving MSC/VLR "
This message
indicates that the
Unique Challenge
failed.
Information
"message=AUTH:A
C:GlobalChal:Fail received
AuthenticationFailRe
port with a
ReportType value
indicating that the
Global challenge
failed "
This message
indicates that the
Global Challenge
failed.
32022
"message=AUTH:A
C -Authentication
already in progress
for MS "
This message
indicates that
there is already an
authentication
process in
progress for the
MS.
Information
32023
"message=AUTH:A
C- Authentication
Not active because of
MS is not auth
capable, serving
MSC is not auth
capable or ANSIAC
RTU is locked "
This message
indicates that the
authentication
process is not
active because the
MS is not auth
capable, or the
serving MSC is
not auth capable
or the ANSIAC
RTU is locked.
Information
32021
The USDS
received an
AuthenticationDir
ective Reject from
the serving
MSC/VLR.
Information
The USDS
received an
AuthenticationFai
lReport with the
ReportType value
indicating that the
global challenge
failed.
...........................................................................................................................................................................................................................................................
B - 30

270-710-919R6.0
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32024
"message=AUTH:A
C- Error for Base
Station Challenge
Out of Sequence "
This message
indicates that
there is error in
the
Authentication
process because
the Base Station
Challenge is out
of sequence.
Information
32025
"message=OTASRE
Q:AC-this is an
unrecognized mobile
for OTASP"
This message
indicates that
there is error in
the OTASP
process.
Information
It is an
unrecognized MS
for the OTASP.
32026
"message=OTASRE
Q:AC-the received
ESN is mismatched
for OTASP"
This message
indicates that the
received ESN
mismatches for
OTASP.
Information
32027
"message=OTASRE
Q:AC-missing AKey or SSD values
for OTASP"
This message
indicates that
there are missing
A-Key or SSD
values for OTASP.
Information
32028
"message=OTASRE
Q:AC-service
indicator and action
code are mismatched
for OTASP"
This message
indicates that
service indicator
and action code
mismatch for
OTASP.
Information
32029
"message=OTASRE
Q:ACAUTH_SIGNATUR
E computation the
error for OTASP"
This message
indicates that
AUTH_SIGNAT
URE computation
error for OTASP.
Information
32030
"message=AUTH:A
C- The terminal type
received and the subs
terminal type stored
in the database are
mismatched "
This message
indicates that the
terminal type
received and the
subs terminal type
stored in the
database
mismatch.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 31
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32031
"message=AUTH:A
C:GlobalChal:UserD
efinedReport - Count
Request mismatch is
detected in
Authentication
Failure Report,
Denied=%s "
This message
indicates that
Count Request
mismatch is
detected in
Authentication
Failure Report.
Information
32032
"message=AUTH:A
C:GlobalChal:Fail RANDC mismatch,
Denied=%s "
This message
indicates that the
Global Challenge
failed due to the
RANDC
mismatch.
Information
32033
"message=AUTH:A
C:GlobalChal:Fail AUTHR mismatch,
Denied=%s "
This message
indicates that the
Global Challenge
failed due to the
AUTHR
mismatch.
Information
32034
"message=AUTH:A
C:GlobalChal:Fail Missing
authentication
response parameters,
Denied=%s "
This message
indicates that the
Global Challenge
failed due to
missing
authentication
response
parameters.
Information
32035
"message=AUTH:A
C:GlobalChal:Fail MSID/ESN
mismatch,
Denied=%s "
This message
indicates that the
Global Challenge
failed due to
MSID/ESN
mismatch.
Information
32036
"message=AUTH:A
C:GlobalChal:Fail MSID is either
Delinquent Account,
Stolen Unit, or
Duplicate Unit,
Denied=%s "
This message
indicates that the
Global Challenge
failed because the
MSID is
Delinquent
Account, Stolen
Unit, or Duplicate
Unit.
Information
...........................................................................................................................................................................................................................................................
B - 32

270-710-919R6.0
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32037
"message=AUTH:A
C:GlobalChal:Fail Terminal type
mismatch,
Denied=%s,Terminal
Type in DataBase =
%s, Terminal Type in
message = %s "
This message
indicates that the
Global Challenge
failed due to
terminal type
mismatch.
Information
32038
"message=AUTH:A
C - Authentication
Status Report Out of
Sequence "
This message
indicates that the
AuthenticationSta
tusReport is out of
sequence.
Information
32039
"message=AUTH:A
C:UserDefinedRepor
t - No
Report INVOKE
received from the
MSC/VLR,
Denied=%s "
This message
indicates that
there is no
AuthenticationSta
tusReport Invoke
received from the
MSC/VLR.
Information
32040
"message=AUTH:A
C:UserDefinedRepor
t - Received
Report INVOKE
from VLR with a
ReportType value
other than 3
(success) indicating
that the unique
challenge failed,
ReportType=%d,
Denied=%s "
This message
indicates that the
Unique Challenge
failed because the
received
AuthenticationSta
tusReport Invoke
from the VLR has
a ReportType
value other than 3
(success).
Information
32041
"message=AUTH:A
C:GlobalChal:Fail General failure type,
Denied=%s "
This message
indicates that the
Global Challenge
failed due to some
other reasons not
covered in
messages 3203232027.
Information
32042
"message=AUTH:A
C:SSD:Fail- SSD
Update Fail
Count=%d exceed or
is equal to the SSD
Update Fail
Threshold=%d, and
the service is denied"
This message
indicates that the
SSD update fail
count exceeds or
is equal to the
SSD update fail
threshold. The
service is denied.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 33
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32043
"message=AUTH:A
C:SSD:Fail- CAVE
fails during SSD
updating"
This message
indicates that the
CAVE fails during
SSD Update.
Information
32044
"message=AUTH:A
C:BSC:Fail- CAVE
fails during
BaseStation
Challenge"
This message
indicates that
CAVE fails during
Base Station
Challenge.
Information
32045
"message=AUTH:A
C:UniqueChal:Fail CAVE fails during
Unique Challenge"
This message
indicates that the
CAVE fails during
Unique
Challenge.
Information
32046
"message=OTASRE
Q:AC:OTASPCallEntry
does not exist when
OTASP_Request_Ge
n_AKey received"
This message
indicates that the
OTASPCallEntry
does not exist
when
OTASP_Request_
Gen_AKey is
received.
Information
32047
"message=OTASRE
Q:AC:-Temporary
record with ESN=%x
MEID=%014llx is
removed for time
out"
This message
indicates that the
temporary record
is removed due to
time out.
Information
32048
"message=OTASRE
Q:AC:-Generating
A-Key or public
encryption fails"
This message
indicates that the
process of
generating A-Key
or public
encryption failed.
Information
32049
"message=OTASRE
Q:AC:OTASPREQ.Receive
d.mobile_station_par
tial_key is not
present when
OTASP_Request_Ge
n_Akey received"
This message
indicates that the
OTASPREQ.Rece
ived.mobile_statio
n_partial_key
does not exist
when the
OTASP_Request_
Gen_Akey is
received.
Information
...........................................................................................................................................................................................................................................................
B - 34

270-710-919R6.0
ANSI Authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
32050
"message=OTASRE
Q:AC:SSD_Update_Report
or
Unique_Challenge_
Report fails when
OTASP_Request_Co
mmit_Akey
received"
This message
indicates that the
SSD_Update_Rep
ort or the
Unique_Challeng
e_Report failed
when the
OTASP_Request_
Commit_Akey is
received.
Information
32051
"message=OTASRE
Q:AC:-CAVE input
incorrect during
BaseStation
Challenge"
This message
indicates that the
CAVE input is
incorrect during
Base Station
Challenge.
Information
32052
"message=OTASRE
Q:AC:-CAVE input
incorrect during SSD
Update"
This message
indicates that the
CAVE input is
incorrect during
SSD Update.
Information
32053
"message=OTASRE
Q:AC:-In
OTASPCallEntry
table, A-Key, SSD.a
or SSD.b is not found
during OTASP
commit A-Key"
This message
indicates that in
OTASPCallEntry
table, A-Key,
SSD.a or SSD.b is
not found when
OTASP commits
the A-Key.
Information
32054
"message=OTASRE
Q:AC:-Table
OTASPCallEntry
does not exist when
OTASP_Request_Co
mmit_Akey
received"
This message
indicates that the
table
OTASPCallEntry
does not exist
when the
OTASP_Request_
Commit_Akey is
received.
Information
32055
"message=OTASRE
Q:AC:-OTASP return
error, reason=%x"
This message
indicates that the
OTASP returns
error due to the
listed reason.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 35
USDS OM logs

............................................................................................................................................................................................................................................................
Table B-5
Location Management
Identifier
Message
Description
Default
Severity
32101
"message=LM:RegNot
- receives Registration
Notification message
for a mobile subscriber
whose MSC/VLR
information can't be
determined"
This message
indicates that
the USDS
receives a
Registration
Notification
Invoke
message for a
mobile
subscriber
whose
MSC/VLR
information
cannot be
determined.
Information
32102
"message=LM:RegNot
- receives Registration
whose HSA/TSA/RSA
determined"
This message
indicates that
the USDS
receives a
RegistrationNo
tification
Invoke
message for a
mobile
subscriber
whose
HSA/TSA/RS
A information
cannot be
determined.
Information
...........................................................................................................................................................................................................................................................
B - 36

270-710-919R6.0
USDS OM logs
Identifier
Message
Description
Default
Severity
32103
"message=LM:MSInac
tive - receives
MSInactive message
whose MSC/VLR
information doesn't
match the MSC/VLR
sending MSInactive
(Originating MSCID =
%06x)"
This message
indicates that
the USDS
receives an
MSInactive
Invoke
message for a
mobile
subscriber
whose
MSC/VLR
information
doesn't match
that of the
MSC/VLR
sending out the
MSInactive
Invoke
message.
Information
32104
"message=LM:RegCan
cel receives
RegistrationCancellatio
n Return Result
message with
Cancellation Denied
Type set to Busy for a
Mobile subscriber"
This message
indicates that
the USDS
receives a
RegistrationCa
ncellation
Return Result
message with
the
Cancellation
Denied Type
set to 'Busy' for
a mobile
subscriber.
Information
32105
"message=LM:RegNot
- received the
Registration
and the HLR has the
IMSI support globally
but the database
indicate the serving
MSC is not IMSI
capable, the HLR must
log an error message to
the log file to indicate
the mismatch."
This message
indicates that
the USDS
received a
RegistrationNo
tification
Invoke
message and
the USDS can
support IMSI
but the
database
indicates that
the serving
MSC is not
IMSI capable.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 37
USDS OM logs
Identifier
Message
Description
Default
Severity
32106
"message=LM:RegNot
NDC/NPA(splitedNPA
=%d) checking has
been performed "
This message
indicates that
the NDC/NPA
checking was
done.
Information
32110
"message=LM:RegCan
cel - invoking reason is
DualVLR race
condition detected "
This message
indicates that
the reason for
the
Registration
Cancellation is
Dual VLR
race.
Information
32112
"message=LM:RegCan
cel - receives
RegCancel return error,
reason=%x"
This message
indicates that
the USDS
receives
RegistrationCa
ncellation
Return Error.
Information
32113
"message=LM:RegCan
cel - receives
RegCancel retry return
error, reason=%x"
This message
indicates that
the USDS
receives
RegistrationCa
ncellation
Retry Return
Error.
Information
32114
"message=LM:RegNot
Report - relaying
RegNot failed"
This message
indicates that
the relaying of
RegistrationNo
tification
Invoke
message fails.
Information
32115
"message=LM:MSInac
tive Report- relaying
MSInactive failed"
This message
indicates that
relaying of
MSInactive
fails.
Information
32117
"message=LM:RegNot
Report - relaying
RegNot time out"
This message
indicates that
the relaying of
RegistrationNo
tification
Invoke
message timed
out.
Information
...........................................................................................................................................................................................................................................................
B - 38

270-710-919R6.0
USDS OM logs
Identifier
Message
Description
Default
Severity
32118
message=LM:MSInacti
ve Report - relaying
MSInactive time out"
This message
indicates that
the relaying of
MSInactive
Invoke
message timed
out.
Information
32119
"message=LM:RegNot
- Terminal Type is
mismatched. Terminal
type in DB is %s,
Terminal type received
is %s "
This message
indicates that
Terminal Type
is mismatched
in RegNot
scenario.
Information
32120
"message=LM:RegNot
- Extended MSCID
received (%06X) is not
found in static MSCID
table, will not insert it
into Dynamic MSCID
table."
This message
indicates that
extended
MSCID
received will
not be inserted
into Dynamic
MSCID table
since it is not
found in static
MSCID table.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 39
ANSI Call Delivery
USDS OM logs
ANSI Call Delivery

............................................................................................................................................................................................................................................................
Table B-6
Call Delivery
Identifier
Message
Description
Default
Severity
32201
"message=CH:LocReqreceives Location
Request message for a
mobile subscriber
whose MSC/VLR
determined: %X"
This message
indicates that the
USDS receives
the Location
Request Invoke
message for a
mobile subscriber
whose MSC/VLR
information
cannot be
determined.
Information
32202
"message=CH:LocReqreceives Location
Request message for a
mobile subscriber
whose HSA/TSA/RSA
determined"
This message
indicates that the
USDS receives
the Location
Request Invoke
message for a
mobile subscriber
whose
HSA/TSA/RSA
information
cannot be
determined.
Information
32203
"message=CH:Routing
Req- changes the MS's
CS status to Inactive
during call delivery as
indicated in Routing
Request Result"
This message
indicates the
USDS changes
the MS's Circuit
Service status to
'Inactive' during
call delivery as
indicated in
Routing Request
Return Result.
Information
32204
"message=CH:Routing
Req -Routing Request
message fails for
Routing Request Result
time out"
This message
indicates that the
Routing Request
Invoke message
failed due to
Routing Request
Return Result
timed out.
Information
...........................................................................................................................................................................................................................................................
B - 40

270-710-919R6.0
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description
Default
Severity
32205
"message=CH:Routing
Req -Routing Request
message fails for SS7
error in Routing
Request Result"
This message
indicates that the
Routing Request
Invoke message
failed due to SS7
error in Routing
Request Return
Result.
Information
32206
"message=CH:Routing
Req - can't locate
routing record for %X.
Unable to send the
message"
This message
indicates that the
USDS cannot
locate the
network element
routing record, so
it is unable to
send the message.
Information
32207
"message=CH:Routing
Req - RRT expires
before receiving
Routing Request
Return Result, Return
Error or Reject.
This message
indicates that the
RRT expires
before receiving
Routing Request
Return Result,
Return Error or
Reject.
Information
32208
"message=CH:Routing
Req - can't find HLR's
own E212 address or
PC/SSN information or
originating MSC's
PC/SSN/GTA
information"
This message
indicates that the
USDS cannot find
the HLR's E212
address or
PC/SSN
information or the
originating MSC's
PC/SSN/GTA
information.
Information
32209
"message=CH:LocReq
- receives LOCREQ
with Trigger Type
neither Mobile
Termination nor
Location"
This message
indicates that the
USDS receives
Location Request
with Trigger Type
neither Mobile
Termination nor
Location.
Information
32210
"message=CH:Routing
Req - receives
RoutingReq return
error, reason=%s"
This message
indicates that the
USDS receives
Routing Request
Return Error.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 41
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description
Default
Severity
32211
"message=CH:WinTrig
ger - WIN_Control is
not allowed"
This message
indicates that
WIN_Control is
not allowed.
Information
"message= TALMaximum Message

Length Exceeded"
This message
indicates that
more than 10
trigger lists were
created.
"message= trigger
(name) is destined for
multiple SCF address
and no SIM address is
provisioned for the
subscriber"
This message
indicates that the
trigger was
provisioned to
multiple WIN
Services whose
destinations are
different and no
SIM is
provisioned for
the subscriber.
32212
"message= TAL cannot

be constructed"
This message
indicates
TriggerAddressLi
st was not created
successfully.
"message= More than

one CNID is
provisioned for the
subscriber"
This message
indicates multiple
CNIDs were
provisioned to the
subscriber.
Information
...........................................................................................................................................................................................................................................................
B - 42

270-710-919R6.0
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description

Length Exceeded"
This message
indicates that
more than 10
triggerlists were
created.
"message= trigger
provisioned for the
subscriber"
This message
indicates that the
trigger was
provisioned to
multiple WIN
Services whose
destinations are
different and no
SIM is
provisioned for
the subscriber.
32213

be constructed"
This message
indicates
TriggerAddressLi
st was not created
successfully.
"message= More than

one CNID is
provisioned for the
subscriber"
This message
indicates multiple
CNIDs were
provisioned to the
subscriber.
Default
Severity
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 43
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description

Length Exceeded"
This message
indicates that
more than 10
trigger lists were
created.
"message= trigger
provisioned for the
subscriber"
This message
indicates that the
trigger was
provisioned to
multiple WIN
Services whose
destinations are
different and no
SIM is
provisioned for
the subscriber.
32214
Default
Severity

be constructed".
This message
indicates
TriggerAddressLi
st was not created
successfully
"message= More than

one CNID is
provisioned for the
subscriber"
This message
indicates multiple
CNIDs were
provisioned to the
subscriber.
Information
...........................................................................................................................................................................................................................................................
B - 44

270-710-919R6.0
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description

Length Exceeded"
This message
indicates that
more than 10
trigger lists were
created.
"message= trigger
provisioned for the
subscriber"
This message
indicates that the
trigger was
provisioned to
multiple WIN
Services whose
destinations are
different and no
SIM is
provisioned for
the subscriber.
32215
Default
Severity
Information

be constructed"
This message
indicates
TriggerAddressLi
st was not created
successfully.
"message= More than

one CNID is
provisioned for the
subscriber"
This message
indicates multiple
CNIDs were
provisioned to the
subscriber.
32216
"message=CH:FA Call
- Pilot DN %s, either
UrMob/FlexAlert RTU
is OFF, or User has no
UM subscription"
This message
indicates that for
the listed pilot
DN, either
UrMob/FlexAlert
RTU is OFF, or
User has no UM
subscription
Information
32217
"message=CH:FA Call
- Pilot DN %s, OMSC
not support TL or
MT==1, only 1 out of
%d delivered"
This message
indicates that for t
listed pilot DN,
OMSC does not
not support TL or
MT==1, only 1
out of %d
delivered
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 45
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description
Default
Severity
32218
"message=CH:FA Call
- Pilot DN %s, OMSC
TRANSCAP MT
limited: %d out of %d
dropped"
This message
indicates that for
the listed pilot
DN, OMSC's
TRANSCAP MT
is limited.
Information
32219
"message=CH:FA Call
- Pilot DN %s, FA
Group Max Member
Alert limited: %d out of
%d dropped"
This message
indicates that for
the listed pilot
DN, FA Group
Max Member
Alert limited is
reached.
Information
32220
"message=CH:FA Call
- Pilot DN %s, %d Leg
Dropped due to
message oversize"
This message
indicates that for
the listed pilot
DN, %d leg is
dropped due to
message oversize
Information
32221
"message=CH:FA Call
- Pilot DN %s,
LocationRequest
ReturnResult message
parameter(s) Dropped
due to oversize,
suppressing level %d"
This message
indicates that for
the listed pilot
DN,
LocationRequest
ReturnResult
message
parameter(s) is
dropped due to
oversize.
Information
32222
"message=CH:FA Call
- Pilot DN %s,
TmLiCD RTU is OFF
for non-pseudo FA
group, treat as normal
call, try deliver to
primary terminal"
This message
indicates that for
the listed pilot
DN, TmLiCD
RTU is OFF for
non-pseudo FA
group.
Information
...........................................................................................................................................................................................................................................................
B - 46

270-710-919R6.0
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description
Default
Severity
32223
"message=CH:FA Call
- Pilot DN %s,
TmLiCD RTU is OFF
for pseudo FA group,
only try deliver to
highest priority
member"
This message
indicates that for
the listed pilot
DN, TmLiCD
RTU is OFF for
pseudo FA group.
Information
32224
"message=CH:FA Call
- Pilot DN %s, MSC
transcap MT=0, Call
Termination Denied"
This message
indicates that for
the listed pilot
DN, MSC
transcap MT=0,
Call Termination
is Denied.
Information
32225
"message=CH:FA Call
- Pilot DN %s,
LocationRequest
ReturnResult message
still oversize after
Parameter(s) Dropping,
ReturnError will be
sent instead"
This message
indicates that the
LOCREQ return
result message for
FA call is still
oversize after
parameter
dropping.
Information
32226
"message=Legal
Interception RTU is ON
and Subscriber is Legal
Intercept Target, Failed
to prepend digits due to
global Legal
Interception Digits
NOT provisioned"
This message
indicates that
Legal Interception
RTU is ON and
Subscriber is
Legal Intercept
Target, Failed to
prepend digits
due to global
Legal Interception
Digits NOT
provisioned.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 47
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description
Default
Severity
32227
"message=Subscriber's
WIN Destination
Address Index
%d(value=%d) is not
provisioned in
ANSIdestination table.
Apply destination
index(value=%d) in
WIN service %d as
default."
This message
indicates that
subscriber's WIN
Destination
Address Index is
not provisioned in
ANSIDestination
table. Apply
destination index
xx in WIN service
xx as default.
Information
32228
"message=CH:SERVR
EQ not sent because
%s=0"
This message
indicates that
CNAMIndex
causing no
SERVREQ
message is sent
out. (The SCP 0
OMlog will no
longer be printed)
Information
32231
"message=CH:MAH
Call - Pilot DN %s,
TmLiCD RTU off for
non-pesudo MAH
group"
This message
indicates that
TmLiCD RTU is
off for nonpseudo MAH
group.
Information
32232
"message=CH:MAH
Call - Pilot DN %s,
TmLiCD RTU off for
pesudo MAH group"
This message
indicates that
TmLiCD RTU is
off for pseudo
MAH group.
Information
32233
"message=CH:MAH
Call - Pilot DN %s,
OMSC(%#x) not
support
TerminationList for
non-pesudo MAH
group"
This message
indicates that
OMSC(%#x)
does not support
TerminationList
for non-pseudo
MAH group.
Information
...........................................................................................................................................................................................................................................................
B - 48

270-710-919R6.0
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description
Default
Severity
32234
"message=CH:MAH
Call - Pilot DN %s,
OMSC(%#x) not
support
TerminationList for
pesudo MAH group"
This message
indicates that
OMSC(%#x)
does not support
TerminationList
for pseudo MAH
group.
Information
32235
"message=CH:MAH
Call - Pilot DN %s, no
more slots available"
This message
indicates that no
more slots are
available for
MAH Call.
Information
32236
"message=CH:MAH
Call - PilotNumber isn't
present in
TransferToNumberReq
uest invoke."
This message
indicates that
PilotNumber is
not present in
TransferToNumb
erRequest invoke.
Information
32237
"message=CH:MAH
Call - Pilot DN %s,
BillingId isn't present
in
TransferToNumberReq
uest invoke."
This message
indicates that
BillingId is not
present in
TransferToNumb
erRequest invoke.
Information
32238
"message=CH:MAH
Call - Pilot DN %s,
Unknown MAH Pilot
DN"
This message
indicates that
MAH Pilot DN is
unknown.
Information
32239
"message=CH:MAH
Call - Pilot DN %s,
Unknown MAH
BillingId."
This message
indicates that
MAH BillingId is
unknown.
Information
32240
"message=CH:MAH
Call - Pilot DN %s,
UrMob RTU off or
UMSubscription no for
non-pesudo MAH
group"
This message
indicates that
UrMob RTU off
or
UMSubscription
is not present for
non-pseudo MAH
group.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 49
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description
Default
Severity
32241
"message=CH:MAH
Call - Pilot DN %s, no
such record found in
the
MAH_CALL_DYNA
MIC table"
This message
indicates that no
such record is
found in the
MAH_CALL_D
YNAMIC table.
Information
32242
"message=CH:MAH
Call - Pilot DN %s, not
MAH_Group_Active"
This message
indicates that it is
not
MAH_Group_Ac
tive
Information
32243
"message=CH:FA Call
- Pilot DN %s, not
FA_Group_Active"
This message
indicates that not
FA_Group_Activ
e.
Information
32244
"message=CH:MAH
Call - Pilot DN %s,
UrMob RTU off or
UMSubscription no for
pesudo MAH group"
This message
indicates that
UrMob RTU is
off or
UMSubscription
not present for
pesudo MAH
group.
Information
32245
"message=CH:MAH
Call - Pilot DN %s,
MAH RTU off for nonpesudo MAH group"
This message
indicates that
MAH RTU is off
for non-pesudo
MAH group.
Information
32246
"message=CH:MAH
Call - Pilot DN %s,
MAH RTU off for
pesudo MAH group"
This message
indicates that
MAH RTU is off
for pesudo MAH
group.
Information
32247
"message=CH:MAH
Call - Pilot DN %s,
MAH Call time out. "
This message
indicates the
MAH Call time
out.
Information
...........................................................................................................................................................................................................................................................
B - 50

270-710-919R6.0
ANSI Call Delivery
USDS OM logs
Identifier
Message
Description
Default
Severity
32248
"message=CH:MAH
Call - Pilot DN %s,
PilotNumber isn't FA or
MAH DN."
This message
indicates that
PilotNumber is
not FA or MAH
DN.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 51
USDS OM logs

............................................................................................................................................................................................................................................................
Table B-7
Identifier
Message
Description
Default
Severity
32301
"message=SS:FeatReq:Feature Request Return

Result with
FeatureResult set to
unsuccessful for
unrecognized feature
code. DialedDigits: %s "
This message
indicates that
the USDS
sends
FeatureRequest
Return Result
with
FeatureResult
set to
unsuccessful
for
unrecognized
feature code.
Information
32302
"message=SS:FeatReq:Feature Request Return

Result with
FeatureResult set to
unsuccessful for
unauthorized feature
code. DialedDigits: %s"
This message
indicates that
the USDS
sends
FeatureRequest
Return Result
with
FeatureResult
set to
unsuccessful
for
unauthorized
feature code.
Information
32303
message=SS:Announce
ment:-OTFI
Announcement table
becomes corrupted or
does not exist
This message
indicates that
the OTFI
Announcement
table is
corrupted or it
does not exist.
Information
32304
message=SS:FeatReq:subscriber's CFDS type

is invalid, CFDS
type=%d
This message
indicates that
the subscriber's
CFDS type is
invalid.
Information
32306
message=SS:FeatReq:FTN is invalid, FTN=%s
This message
indicates that
the FTN is
invalid.
Information
...........................................................................................................................................................................................................................................................
B - 52

270-710-919R6.0
USDS OM logs
Identifier
Message
Description
Default
Severity
32307
"message=SS:FeatReq:PREF PILOT DN does

not match Splitted DN,
Original PilotDN=%s"
This message
indicates that
preferred
PILOT DN
does not match
Splitted DN,
Original
PilotDN
Information
32308
"message = Sent Modify

Return Error. error code
= %d; failure reason:
%s"
This message
indicates that
send Modify
return error.
Information
message = Sent Modify

Return Result with
DataResult as
unsuccessful (2). failure
reason: %s"
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 53
USDS OM logs

............................................................................................................................................................................................................................................................
Table B-8
Subscriber Data Management
Identifier
Message
Description
Default
Severity
32401
message=SDM:QualR
eq- Sending
Qualification Request
Return Result message
failed
This message
indicates that
sending
QualificationRequ
est Return Result
message failed.
Information
32402
"message=SDM:QualR
eq- Sending
Qualification Request
Return Error message
failed"
This message
indicates that
sending
QualificationRequ
est Return Error
message failed.
Information
32403
"message=SDM:QualD
ir- Received a return
error for Qualification
Directive INVOKE
message,
errorcode=%d,errortyp
e=%d"
This message
indicates that the
USDS received a
return error for
QualificationDire
ctive Invoke
message.
Information
32404
"message=SDM:QualD
ir- The Qualification
Directive INVOKE
message could not be
sent when invoking a
request"
This message
indicates that the
QualificationDire
ctive Invoke
message could not
be sent.
Information
32405
"message=SDM:QualD
ir- Qualification
Directive INVOKE
sent because the MS is
not active"
This message
indicates that the
QualificationDire
ctive Invoke
message could not
be sent because
the MS is
inactive.
Information
32406
"message=SDM:QualD
ir- Qualification
Directive INVOKE
sent because the MS is
not registered (the
Primary Last Seen
Location is NULL for
the subscriber)"
This message
indicates that the
QualificationDire
ctive Invoke
message could not
be sent because
the MS is not
registered.
Information
...........................................................................................................................................................................................................................................................
B - 54

270-710-919R6.0
USDS OM logs
Identifier
Message
Description
Default
Severity
32407
"message=SDM:QualD
ir- The Qualification
Directive(with
AuthorizationDenied
reason) INVOKE
sent when invoking a
request"
This message
indicates that the
QualificationDire
ctive Invoke (with
AuthorizationDen
ied reason)
message could not
be sent when
invoking a
request.
Information
32408
"message=SDM:QualD
ir- Received a timeout
error for sending a
Qualification Directive
INVOKE message"
This message
indicates that the
USDS received a
timeout error
when sending a
QualificationDire
ctive Invoke
message.
Information
32409
"message=SDM:QualD
ir- Received a close
transaction error for
sending a Qualification
Directive INVOKE
message"
This message
indicates that the
USDS received a
close transaction
error when
sending a
QualificationDire
ctive Invoke
message.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 55
ANSI short message
USDS OM logs
ANSI short message

............................................................................................................................................................................................................................................................
Table B-9
Short Message
Identifier
Message
Description
Default
Severity
32501
"message=SHORT
MESSAGE
CENTER (PC =
%03d%03d%03d,
SSN=%d) NOT
PROVISIONED"
This message
indicates that the
Message Center is
not provisioned.
Information
32502
"message=SHORT
MESSAGE
CENTER (PC =
%03d%03d%03d)
NOT SUPPORT
MDN"
This message
indicates that the
Message Center
does not support
MDN.
Information
32503
"message=MESSA
GE PENDING LIST
FULL"
This message
indicates that the
message pending
list is full.
Information
32504
"message=SHORT
MESSAGE
CENTER (PC =
%03d%03d%03d)
NOTIFIED
FAILED"
This message
indicates that the
identified Message
Center failed to be
notified.
Information
32505
"message=MWD
ENTRY OF SME
(ENTRY INDEX =
%d) TO BE
DELETED"
This message
indicates that the
listed MWD entry
or SME will be
deleted.
Information
32506
"message=MWD
ENTRY OF SME
(ENTRY INDEX =
%d) TO BE
OVERWROTE"
This message
indicates that the
listed MWD entry
or SME will be
overwritten.
Information
32507
"message=SHORT
MESSAGE
CENTER
(GTA=%s) NOT
PROVISIONED"
This message
indicates that the
listed Message
Center is not
provisioned.
Information
32508
"message=SHORT
MESSAGE
CENTER
(GTA=%s) NOT
SUPPORT MDN"
This message
indicates that the
listed Message
Center does not
support MDN.
Information
...........................................................................................................................................................................................................................................................
B - 56

270-710-919R6.0
ANSI short message
USDS OM logs
Identifier
Message
Description
Default
Severity
32509
"message=SMSReq:
- subscriber record
access fails"
This message
indicates that
subscriber record
access fails.
Information
32510
"message=SMDPP:
Sending SMDPP
failed, MC = %d"
This message
indicates that
ANSI SMS
sending SMDPP
failed.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 57
USDS OM logs

............................................................................................................................................................................................................................................................
Table B-10
ANSI Default Scenarios
Identifier
Message
Description
Default Severity
39901
"message= HSA(%d)
NOT VALID "
This message indicates that the HSA

code is invalid.
Information
39902
"message= TSA(%d)
NOT VALID"
This message indicates that the TSA

code is invalid.
Information
39903
"message= the
subscriber's ARL
Positive index or ARL
Negative List index
(%d) points to an
entry in the ARL List
Table that is not
provisioned"
This message indicates that the

subscriber's ARL Positive index or
ARL Negative List index points to an
entry that is not provisioned.
Information
39904
"message= either the

Point Code or
Subsystem Number
(or both) has not been
provisioned for the
HLR"
This message indicates that either the

Point Code or Subsystem Number (or
both) has not been provisioned for the
USDS.
Information
39905
"message= either the

Translation Type or
Global Title Address
(or both) have not
been provisioned for
the HLR"
This message indicates that either the

Translation Type or Global Title
Address (or both) was not provisioned
for the USDS.
Information
39906

Length Exceeded"

Maximum Message Length was
exceeded.
Information
39907
"message= trigger
provisioned for the
subscriber"
This message indicates that the trigger

(name) is destined for multiple SCF
address but no SIM address is
provisioned for the subscriber.
Information
39908
"message= TAL
cannot be
constructed"
This message indicates that the TAL

cannot be constructed.
Information
39909
"message= More than

one CNID is
provisioned for the
subscriber"
This message indicates that more than

one CNID is provisioned for the
subscriber.
Information
...........................................................................................................................................................................................................................................................
B - 58

270-710-919R6.0
USDS OM logs
Identifier
Message
Description
Default Severity
39910
"message= HCC
feature in enabled for
mobile subscriber
(General, Traveller,
Executive), but there
is no valid HCC DN
index"
This message indicates that HCC

feature is enabled for mobile
subscriber (General, Traveler,
Executive), but there is no valid HCC
DN index.
Information
39911
"message= HCC
feature is enabled for
mobile subscriber
(General, Traveller,
Executive), and there
is valid HCC DN
index, but there is no
HCC directory
number associated
with HCC index"
This message indicates that HCC

feature is enabled for mobile
subscriber (General, Traveler,
Executive), and there is valid HCC DN
index, but there is no HCC directory
number associated with the HCC
index.
Information
39912
"message= The
requesting entity's
SCCP address is not
provisioned in the
global authorization
table and the global
flag for requesting
entity authorization is
turned on"

requesting entity's SCCP address is not
provisioned in the global authorization
table but the global flag for requesting
entity authorization is turned on.
Information
39913
"message=
Origination Request
message was
unsuccessfully
relayed to remote
destination or there is
no remote
destination"

OriginationRequest Invoke message
failed to be relayed to the remote
destination or there is no remote
destination.
Information
39914
"message= Service
Command Succeed (%s) With Correlation
ID (%s) "
This message indicates that the service

command succeeded.
Information
39915
"message= Service
Command FailReason: (%s) With
Correlation ID (%s) "
This message indicates that the service

command fails due to the listed reason.
Information
39916
"message= %s
BOUND TO MAP
REQUEST SENT
SUCCESSFULLY"
This message indicates that the USDS

binds to MAP successfully.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 59
USDS OM logs
Identifier
Message
Description
Default Severity
39917
"message=Two-way
GTT routing is
preferred by %s(index
%d) while two-way
GTT is inhibited "
This message indicates that 2-way

GTT routing is preferred while 2-way
GTT is inhibited.
Information
39917_MSC
ID
"message=Two-way
GTT routing is
preferred by
MSC(MSCID %s)
while two-way GTT
is inhibited "

GTT routing is preferred while 2-way
GTT is inhibited.
Information
39918
"message=Two-way
GTT is used as
routing method of
incoming message
while two-way GTT
is inhibited "

GTT is used as routing method of
incoming message while 2-way GTT is
inhibited.
Information
"message=Routing
info missing for %s
%d "
This message indicates that the routing

info is missing.
"message= Routing
info missing for
MSC/VLR %s %s,
Reason: %s"

info is missing due to no static entry, or
no dynamic entry, or invalid PCSSN
indicator, or invalid PCSSN.
"message=Routing
info missing for %s
%s "

info is missing.
39920
"message= Cannot
relay the ORREQ
message because the
SCP address is not
provisioned in the
HLR", DestIndex of
SCP = %d"

cannot relay the OriginationRequest
Invoke message because the SCP
address is not provisioned in the
USDS.
Minor
39921
"message= Cannot
relay the ORREQ
message because of
an error encountered
in the HLR (other
than unprovisioned
SCP address),
DestIndex of SCP =
%d"

cannot relay the OriginationRequest
Invoke message due to an error
encountered in the USDS (other than
unprovisioned SCP address).
Minor
39919
Information
...........................................................................................................................................................................................................................................................
B - 60

270-710-919R6.0
USDS OM logs
Identifier
Message
Description
Default Severity
39922
"message = The timer

ORT expires and no
response has been
received from the
SCP for the relayed
ORREQ message",
DestIndex of SCP =
%d"
This message indicates that the timer

ORT expired and no response were
received from the SCP for the relayed
OriginationRequest Invoke message.
Minor
39923
"message = Cannot
relay the FEATREQ
message because the
SCP address is not
provisioned or some
features are not
supported currently in
the HLR", FScode =
%s, DestIndex of SCP
= %d"

cannot relay the FeatureRequest
Invoke message because the SCP
address is not provisioned in the USDS
or the related feature is unlocked.
Minor
39924
"message = Cannot
relay the FEATREQ
message because of
an error encountered
in the HLR (other
than unprovisioned
SCP address), FScode
= %s, DestIndex of
SCP = %d"

cannot relay the FeatureRequest
Invoke message because of an error
encountered in the USDS.
Minor
39925
"message = The timer

FRRT expires and no
response has been
received from the
SCP for the relayed
FEATREQ message",
FScode = %s,
DestIndex of SCP =
%d"
This message indicates that the timer

FRRT expired and no response was
received from the SCP for the relayed
FeatureRequest Invoke message.
Minor
39926
"message = HLR
returns error (error
code = System
Failure) to the SCP as
a result of
unsuccessful relaying
of
RemoteUserInteractio
nDirective INVOKE
message to the MSC"

returns error (error code = System
Failure) to the SCP as a result of
unsuccessful relaying of
Invoke message to the MSC.
Minor
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 61
USDS OM logs
Identifier
Message
Description
Default Severity
39927
"message =
subscriber's ARL
Positive Index point
an entry in the ARL
List Table that is not
provisioned, ARL
Positive Index=%d"

subscriber's ARL Positive Index points
to an entry that is not provisioned.
Information
39928
"message =
subscriber's ARL
Negative Index point
an entry in the ARL
List Table that is not
provisioned, ARL
Negative Index=%d"

subscriber's ARL Negative Index
points to an entry that is not
provisioned.
Information
39929
"message = send %s
fails"
This message indicates some message

failed to be sent.
Information
39930
"message = in %s
scenario, ESN
mismatch occurs,
ESN in DB=%x, ESN
in message=%x"
This message indicates that ESN

mismatch occurs.
Information
39930_2ES
N
"message = in %s
scenario, ESN
mismatch occurs,
Dynamic ESN in
DB=%x, Fixed ESN
in DB=%x, ESN in
message=%x"
This message indicates that ESN

mismatch occurs in the listed scenario.
Information
39931
"message =
MIN/IMSI/MDN
mismatch"

MIN/IMSI/MDN mismatch or not
provisioned in subscriber's record.
Information
Note: For example, this Omlog can be:

HCF SMS OPERATION
message = MIN/IMSI/MDN
mismatch
Message ID=39931;
subscriber information:MIN
=0902060006;
In this case [0902060006] maybe the

MDN (not MIN) of the subscriber. For
INFODIR, SMSNOT and SMSREQ, if
VMS/SMSC send the MDN of the
subscriber in MIN parameter,
"subscriber information: MIN
=0902060006" is shown in the OM
log, though 090206006 is MDN.
...........................................................................................................................................................................................................................................................
B - 62

270-710-919R6.0
USDS OM logs
Identifier
Message
Description
Default Severity
39932
"message = PACA
authorized subscriber
with 0 priority level"
This message indicates that this is

PACA authorized subscriber with 0
priority level.
Information
39933
"message = RTU of
IMSI is off, but IMSI
is received"
This message indicates that the feature

for supporting IMSI is locked.
Information
39934
"message = RTU of
Lucent extension is
off"
This message indicates that feature for

Lucent extension is locked.
Information
39935
"message = NPA
length is not
provisioned in
database"
This message indicates that the NPA

length is not provisioned in database.
Information
39936
"message = RTU of
Multiple Message
Waiting is off"

Multiple Message Waiting is locked.
Information
39937
"message = RTU of
WINTrigger is off"

WINTrigger is locked.
Information
39938
"message = in %s
scenario, error occurs
for Operation Not
Supported"
This message indicates that error

occurs due to operation-not-supported.
Information
39939
"message = MEID is
received but RTU of
MEID is turned off"
This message indicates that MEID is

received in the message, but USDS
does not support MEID as this feature
is locked.
Information
39940
"message = in %s
scenario, MEID
mismatch
occurs,MEID in
message=%0llx"
This message indicates that the MEID

mismatch occurred in the listed
scenario.
Information
39941
"message= ONE SSN

BOUND TO MAP
SUCCESSFULLY"
This message indicates that one SSN

binds to map successfully.
Information
39942
"message = SS7 Over

IP is used as routing
method of incoming
message while SS7
Over IP is inhibited"
This message indicates that SS7 Over

IP is configured to be the routing
method of incoming message, but this
feature is locked on USDS.
Information
39943
"message = SS7 Over

IP routing is preferred
by %s(index %d)
while SS7 Over IP is
inhibited "

method of the network entity listed in
the message, but this feature is locked
on USDS.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 63
USDS OM logs
Identifier
Message
Description
Default Severity
39943_MSC
ID
"message = SS7 Over

IP routing is preferred
by MSC(MSCID %s)
while SS7 Over IP is
inhibited "

method of the network entity listed in
the message, but this feature is locked
on USDS.
Information
39944
"message =
transport_type 0x%x
currently not
supported "

does not support the transport type
listed in the message.
Information
39945
"message =
parameters have been
successfully
suppressed up to level
%d in msg %s"

parameters have been successfully
suppressed up to the listed level.
Information
39946
"message = all
parameter suppression
levels applied in msg
%s, but msg len still
exceeds max len
allowed"
This message indicates that all

parameter suppression levels are
applied in the listed message, but msg
len still exceeds max len allowed.
Information
39947
"message = Serving
CRBT is authorized
and activated,but
CRBT Routing Digits
is not provisioned for
subscriber,serving
CRBT index is %d"
This message indicates that the serving

CRBT is authorized and activated, but
CRBT Routing Digits is not
provisioned for subscriber.
Information
39948
"message = Sent
Modify Return Result
with DataResult as
unsuccessful (2).
Failure reason: %s"
This message indicates Modify data

operation is unsuccessful.
Information
39949
"message = Sent
Modify Return Error.
Error code = %d;
failure reason: %s"
This message indicates HLR sending

Modify Return Result fails.
Information
...........................................................................................................................................................................................................................................................
B - 64

270-710-919R6.0
USDS OM logs
Identifier
Message
Description
Default Severity
39950
"message =
Subscriber's preferred
language (%d) is not
supported by Service
Provider"
This message indicates the subscriber's

preferred language is not supported by
service provider.
Information
39951
"message = The
mobile equipment
with
MEID(0x%llx)/ESN(
0x%x) in
MSCId(0x%X) and
LocationArea(0x%X)
is restricted by service
provider EIR feature
This message indicates that the mobile

equipment with MEID/ESN in MSCId
and LocationArea is restricted by
service provider EIR feature
Major
39952
"message = The
mobile equipment
with
MEID(0x%llx)/ESN(
0x%x) in
MSCId(0x%X) is
restricted by service

equipment with MEID/ESN in MSCId
is restricted by service provider EIR
feature
Major
39953
"message = The
mobile equipment
with
MEID(0x%llx)/ESN(
0x%x) in
LocationArea(0x%X)
is restricted by service
provider EIR feature"

equipment with MEID/ESN in
LocationArea is restricted by service
Major
39954
"message = The
mobile equipment
with
MEID(0x%llx)/ESN(
0x%x) is restricted by
service provider EIR
feature"

equipment with MEID/ESN is
restricted by service provider EIR
feature
Major
39955
"message = Current
Circle ID is not found,
current MSCID is
%06x
This message indicates that current

circleID is not found for
SMDPP/SMPP.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 65
USDS OM logs
Identifier
Message
Description
Default Severity
39957
"message = The
subscriber is with
stolen mobile"

subscriber possesses a stolen mobile.
Information
39958
"message = Failed to
get Routing info when
sending %s INVOKE
message out because
MSC/VLR (0x%x)
record doesn't exist in
static/dynamic global
table, or MSC/VLR
(0x%x) record doesn't
include valid route
info (PC/SSN or
GTA), etc"
This message indicates that failure to

fetch routing info when sending
INVOKE message out because
MSC/VLR record does not exist in
static/dynamic global table, or
MSC/VLR record does not include
valid route info (PC/SSN or GTA), etc.
Information
...........................................................................................................................................................................................................................................................
B - 66

270-710-919R6.0
UMTS framework
USDS OM logs
UMTS framework
............................................................................................................................................................................................................................................................
Table B-11
UMTS Framework
Identifier
Message
Description
Default
Severity
21301
unable to
negotiate an AC
The message
indicates that the
application
context version is
not supported by
HLR or potential
version
incompatibility.
Information
21302
unable to open a
dialogue
The message
indicates that the
dialogue is refused
for invalid
destination
reference.
Information
21400
message = SS7
Over IP UMTS is
used as routing
method of
incoming
message while
SS7 Over IP
UMTS is
inhibited
The message
indicates that
incoming UMTS
messages uses SS7
over IP as routing
method but the
response message
using SS7 over IP
is inhibited for that
NE.
Information
21401
message = SS7
Over IP UMTS
routing is
preferred in
creating map
session while SS7
Over IP UMTS is
inhibited
The message
indicates that
incoming UMTS
messages uses SS7
over IP as
preferred routing
method but the
response message
using SS7 over IP
is inhibited for that
NE.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 67
UMTS authentication
USDS OM logs
UMTS authentication
............................................................................................................................................................................................................................................................
Table B-12
UMTS Authentication
Identifier
Message
Description
Default
Severity
22001
AUTH:UMTS AuC:
subscriber's IMSI
indicating a 3G AuC
Feature Lock
mismatch
This message
indicates that the
subscriber's IMSI
indicating a 3G
AuC Feature
Lock mismatch.
Information
22002
CANCEL
LOCATION DUE
TO AFR FOR
SUBSCRIBER
%lld\n MAY NOT
HAVE HAPPENED
The message
indicates that the
Cancel Location
on Authentication
Failure flag is set
to "No".
Information
22003
AFR COULD NOT

NULL THE
SUBSCRIBER
DATA FOR
SUBSCRIBER
%lld\n
This message
indicates that no
subscriber record
is associated with
the IMSI.
Information
22004
RECEIVED AFR
WRONG USER
RESPONSE FOR
SUBSCRIBER
%lld\n
This message
indicates that the
USDS received
AFR wrong user
response for the
subscriber.
Information
22005
RECEIVED AFR
WRONG
NETWORK
SIGNATURE FOR
SUBSCRIBER
%lld\n
This message
indicates that the
USDS received
AFR wrong
signature for the
subscriber.
Information
22006
KI decrypt failure
This message
indicates that KI
decrypt failure in
UMTS AuC.
Information
22101
Cancel Location
triggered by Update
Procedure, All retries
to VLR failed
This message
indicates that the
Cancel_Location
was triggered by
the Update
Procedure, all
retries to VLR
failed.
Information
...........................................................................................................................................................................................................................................................
B - 68

270-710-919R6.0
UMTS authentication
USDS OM logs
Identifier
Message
Description
Default
Severity
22102
Cancel Location
triggered by Update
Procedure, All retries
to SGSN failed
This message
indicates that the
Cancel_Location
was triggered by
the Update
Procedure, all
retries to SGSN
failed.
Information
22701
FAIL TO FIND
CORRESPONDING
NE STATIC
RECORD FOR
INTERROGATION
GMSC (GT=%s)\n
This message
indicates the
failure to find
corresponding NE
static record for
interrogation
GMSC.
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 69
UMTS CAMEL
USDS OM logs
UMTS CAMEL
............................................................................................................................................................................................................................................................
Table B-13
UMTS CAMEL
Identifier
Message
Description
Default
Severity
22801
GT (%s) DID
NOT RESPOND
TO NOTE SUB
DATA
MODIFIED REQ
FOR MSISDN
(%s) \n
There is no
response to the
Note_Sub_Data_
Mofified message
for the listed
MSISDN.
Information
...........................................................................................................................................................................................................................................................
B - 70

270-710-919R6.0
HSS overload
USDS OM logs
HSS overload
............................................................................................................................................................................................................................................................
Table B-14
HSS Overload
Identifier
Message
Description
Default
Severity
70401
"message=OL: SYSTEM IS
OVERLOADED
FOR HSS CX
FEATURE"
This message
indicates that
overload for HSS
Cx messages is
reached.
Minor
70402
"message=OL: SYSTEM
OVERLOAD
FOR HSS CX
FEATURE IS
RELEASED"
This message
indicates that
overload for HSS
Cx messages is
cleared.
Minor
70403
"message=OL: SYSTEM IS
OVERLOADED
FOR HSS SH
FEATURE"
This message
indicates that
overload for HSS
Sh messages is
reached.
Minor
70404
"message=OL: SYSTEM
OVERLOAD
FOR HSS SH
FEATURE IS
RELEASED"
This message
indicates that
overload for HSS
Sh messages is
cleared.
Minor
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 71
HSS authentication
USDS OM logs
HSS authentication
............................................................................................................................................................................................................................................................
Table B-15
HSS Authentication
Identifier
Message
Description
Default
Severity
71001
"message=AC:M
AR - Get Invalid
AuthScheme
From the
incoming MAR
"This message
indicates that HSS
cannot get a valid
authentication
scheme from the
incoming MAR
message.
Minor
71002
"message=AC: No Authentication
data for the User
"This message
indicates that the
authentication data
for this user does
not exist in HSS.
Minor
71003
"message=AC:M
AR - Another
Authentication
Already in
progress,
Authenticate
Rejected"
This message
indicates that
authentication is
rejected because
another
authentication is
already in
progress.
Minor
71004
"message=AC: AUTHENTICATI
ON_TIMEOUT/
AUTHENTICATI
ON_FAILURE
"This message
indicates the
authentication
timeouts or the
authentication is
failed.
Minor
71005
HSS AUTH KI
DECRYPT
FAILURE
This message
indicates that Ki
decrypt failure.
Information
...........................................................................................................................................................................................................................................................
B - 72

270-710-919R6.0
HSS feature lock
USDS OM logs
HSS feature lock

............................................................................................................................................................................................................................................................
Table B-16
HSS Feature Lock
Identifier
Message
Description
Default
Severity
72101
"message=FL: HSS FEATURE

IS LOCKED"
This message
indicates that the
HSS feature is
locked
Minor
72102
"message=CH:%
s - %s RTU is off.
"This message
indicates that this
feature's RTU is
turned off
(feature is
locked).
Minor
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 73
HSS call handling
USDS OM logs
HSS call handling

............................................................................................................................................................................................................................................................
Table B-17
HSS Call Handling
Identifier
Message
Description
Default
Severity
72201
"message=CH:D
B:ACCESS Database
Function Access
Error"
This message
indicates that an
error occurs when
accessing the
database.
Minor
72202
"message=CH:D
B:UPD Database
Function Update
Error"
This message
indicates that an
error occurs when
updating the
database.
Minor
72204
"message=CH:Fa
il - Invalid User
received"
This message
indicates that an
invalid user is
received.
Minor
72205
"message=CH:A
VP:MISS - The
%s message
missing AVP %s"
This message
indicates that the
mandatory AVP
is missing in the
incoming
message.
Minor
72206
"message=CH:A
VP:INVALID The %s message
contain invalid
AVP: %s"
This message
indicates that the
incoming
message contain
invalid AVP.
Minor
72207
"message=CH:Fa
il - HSS can't
handle the
message, system
error"
This message
indicates that
HSS cannot
handle the
request
successfully
because of
internal error.
Minor
...........................................................................................................................................................................................................................................................
B - 74

270-710-919R6.0
HSS call handling
USDS OM logs
Identifier
Message
Description
Default
Severity
72208
"message=CH: HSS received

failed Answer
message : %s"
This message
indicates HSS
receive a failed
answer message.
Minor
72209
"message=CH: Reach the MAX

retry count when
send message :
%s"
This message
indicates that the
maximum retry
count is reached
when HSS retries sending the
message.
Minor
72210
"message=CH: Subscriber Data

Error"
This message
indicates that a
subscriber data
error occurs.
Minor
72211
"message=CH:S
AR - The Server
Name in SAR is
Different with the
S-CSCF of the
PUID Stored in
HSS"
This message
indicates that the
Server Name in
SAR message is
different from the
S-CSCF stored in
HSS.
Minor
72212
"message=CH:U
AR - The PUID
doesn't allow
roaming"
This message
indicates that the
roaming of the
PUID is not
allowed.
Minor
72213
"message=CH:U
AR - The PUID
authorization
rejected"
This message
indicates that the
PUID is barred or
not authorized.
Minor
72214
"message=CH:%
s - The PUID is
not registered"
This message
indicates that the
PUID is not
registered.
Minor
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 75
HSS call handling
USDS OM logs
Identifier
Message
Description
Default
Severity
72215
"message=CH:HSS can't handle

%s MAP
message, system
error"
This message
indicates that the
message is not
correct to be
handled.
Minor
72216
"message=CH: %s message
receive MAP %s
error which error
code is %d"
This message
indicates that
HSS receives the
MAP error
message.
Minor
72217
"message=CH: The Command

does not match
the Application
ID(%d)"
This message
indicates that
HSS received
diameter
command
mismatched with
the
applicationID.
Minor
72411
"message=CH:S
AR - The Server
Name in SAR is
Different with the
S-CSCF of the
PUID Stored in
HSS"
This message
indicates that the
Server Name in
SAR message is
different from the
S-CSCF stored in
HSS.
Minor
72412
"message=CH:U
AR - The PUID
doesn't allow
roaming"
This message
indicates that the
roaming of the
PUID is not
allowed
Minor
72413
"message=CH:U
AR - The PUID
authorization
rejected"
This message
indicates that the
PUID is barred or
not authorized.
Minor
72414
"message=CH:%
s - The PUIDis
not registered"
This message
indicates that the
PUID is not
registered.
Minor
...........................................................................................................................................................................................................................................................
B - 76

270-710-919R6.0
HSS call handling
USDS OM logs
Identifier
Message
Description
Default
Severity
72511
"message=CH:%
s - HSS cant
recognize the
requested data"
This message
indicates that
HSS cannot
recognize the
requested data.
Minor
72512
"message=CH:%
s - The operation
is not allowed on
HSS"
This message
indicates that the
operation is not
allowed on HSS.
Minor
72513
"message=CH:P
UR - PUR with
too much server
data"
This message
indicates that the
size of Service
Data in the PUR
message is too
large.
Minor
72514
"message=CH:P
UR - PUR
sequence number
is wrong"
This message
indicates that the
sequence number
in PUR message
is not correct.
Minor
72601
"message=CH:Fa
il:UMTS Update
Location or
ANSI41
Registration
Notification
Trigger IMS
Deregistration
Failed.\nBecause
This subscriber of
UMTS/ANSI41
hasn't associated
PRID of IMS in
SDHLR."
This message
indicate that
UMTS/ANSI
trigger IMS
deregistration
failure
Minor
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 77
USDS OM logs

............................................................................................................................................................................................................................................................
Table B-18
AAA OMlogs
Identifier
Message
Description
Default
Severity
80001
"message=AAA
TEMPLATE ID
%d NOT FOUND
"
This message
indicates that the
template requested
by the AAA Server
does not exist in
AAA_Template
table.
Minor
...........................................................................................................................................................................................................................................................
B - 78

270-710-919R6.0
SMPP specified
USDS OM logs
SMPP specified
............................................................................................................................................................................................................................................................
Table B-19
SMPP OMlogs
Identifier
Message
Description
Default
Severity
90001
"SMPP PDLS
BIND response
from SMSC[%d]
with status[%ls]"
This message
indicates that
SMPP BIND
request to SMSC
[xxx] is responded
with an error status
[yyy] where xxx is
the SMSC index
Information
90002
"SMPP PDLS
BIND timeout for
SMSC[%d]"
This message
indicates that
SMPP BIND
request to SMSC
timeout before
receiving any
response
Information
90003
"SMPP PDLS
BIND failed due
to no SMPPCfg
data"
This message
indicates that
SMPP BIND
request cannot be
sent to SMSC due
to missing
SMPPCfg data
Information
90004
"SMPP PDLS
BIND responded
with
GENERIC_NAC
K by SMSC[%d]"
This message
indicates that
SMPP BIND
request to
SMSC[xxx] is
responded with
GENERIC_NACK
.
Information
90005
"SMPP PDLS
BIND to
SMSC[%d] failed.
Exception info
[%s]"
This message
indicates that
SMPP BIND
request to
SMSC[xxx] failed.
The reason is
indicated by
Exception info
[...].
Information
...........................................................................................................................................................................................................................................................
270-710-919R6.0

B - 79
SMPP specified
USDS OM logs
Identifier
Message
Description
Default
Severity
90006
"SMPP PDLS
ENQUIRE_LINK
to SMSC[%d]
timeout
"This message
indicates that
SMPP PDLS
ENQUIRE_LINK
to SMSC[xxx]
timeout.
Information
...........................................................................................................................................................................................................................................................
B - 80

270-710-919R6.0
Overview
............................................................................................................................................................................................................................................................
Purpose
Contents
This chapter introduces the requirements and guidelines for USDS

system operators to develop the authentication functions for UMTS
HLR and HSS. The authentication algorithm for UMTS HLR and HSS
are the same except the generate_sqn and check_sqn functions.
C-3
C-6
C-11
C-15
C-17
C-19
C-22
C-25
C-28
C-30
C-32
............................................................................................................................................................................................................................................................
270-710-919R6.0

C - 1
C-34
C-36
C-37
C-38
C-40
C-42
C-43
C-44
C-45
C-48
C-50
...........................................................................................................................................................................................................................................................
C - 2

270-710-919R6.0

............................................................................................................................................................................................................................................................
Authentication process
overview
Figure C-1, "Authentication process overview" (C-3) and Table C-1,

"Authentication description" (C-4) provide a high level illustration of
the authentication process.
Figure C-1
Authentication process overview
Table C-1, "Authentication description" (C-4) explains the process

depicted in Figure C-1, "Authentication process overview" (C-3):
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 3
Table C-1
Lucent authentication
functions
Authentication description
When...
Then...
a subscriber requests service.
the serving SGSN/VLR requests

authentication information from USDS
(1).
the HCF receives the request

and passes it to its AuC
(Authentication Center)
capability.
the HCF AuC passes the request to a

HDF's AuC (2).
the HDF AuC receives the

request and passes it to its
AuC (Authentication Center)
capability.
the HDF AuC queries the USDS

subscriber data (3).
the subscriber data is found in

the database.
the database returns subscriber data as

required to the AuC (4).
the AuC receives the

subscriber data.
the AuC makes a call to the

authentication function identified by the
subscriber data (5).
the authentication function

receives subscriber-specific
data in an AuC call.
the authentication function calculates the

required authentication data and returns it
to the HDF AuC (6).
HDF AuC receives

authentication data from the
authentication function.
HDF passes the authentication data to

HCF (7).
the HCF receives the

authentication data.
the HCF returns authentication data to the

requesting SGSN/VLR (8).
USDS provides a set of authentication functions with one default

algorithm for each authentication capabilities to support UMTS and
GSM subscribers.
Using the product-provided authentication functions can eliminate the
learning curve and work effort associated with developing service
provider customized authentication functions.
Lucent provided functions work only as version
number 255. Do not assign this version number for service provider
developed functions.
Important!
The provided authentication functions are associated with position 255

of each authentication function array.
...........................................................................................................................................................................................................................................................
C - 4

270-710-919R6.0
To use the provided authentication function, complete the following:
Provision 255 as a valid version number for each of the system

data authentication version capabilities (ALG3, ALG8, F1,
F1Star, F2, F3, F4, F5).
Provision 255 as the assigned version number for each subscriber.
For UMTS subscriber, set A3 and A8 versions to 0 (zero) and set

all other authentication function version numbers to 255.
For GSM subscriber, set A3 and A8 versions to 255 and set all
other authentication function version numbers to 0 (zero).
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 5
Developing service provider authentication

functions

............................................................................................................................................................................................................................................................
USDS AuC API general

requirements
The service provider developed functions should meet the general

requirements shown in Table C-2, "AuC API general requirements"
(C-7):
...........................................................................................................................................................................................................................................................
C - 6

270-710-919R6.0

functions
Table C-2
AuC API general requirements
Requirement category
Requirement(s)
Compiler
The functions should be compiled with

Sun WorkShop 6 update 2, or a
compatible compiler.
For the functions running on Netra 1280,
it must be 64-bit. For the functions
running on Netra 1400, it must be 32-bit.
Library location and name
The library should be stored on

each HDF's file system at
/sn/sps/HDF600/lib.
The library should be named

libauc_plugins.so.
The library should have its

permissions set to 644 (-rw-r--r-).
Log on to MAS HDFs as ainet to

access the library directory. See
/opt/usrlib/README for more
information about using the
directory.
The software library
will be overwritten if the MAS
platform software is reinstalled or
upgraded to a new version. Verify
the impact of any MAS platform
software changes to the software
library and reload the software
library as required.
Important!
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 7

functions
Requirement(s)
Authentication
The library should include the

following authentication plugins,
using these exact names
Decryption functions
Sequence number functions
Umts_auc_a3_plugin
Umts_auc_a8_plugin
Umts_auc_f1_plugin
Umts_auc_f1star_plugin
Umts_auc_f2_plugin
Umts_auc_f3_plugin
Umts_auc_f4_plugin
Umts_auc_f5_plugin
Each authentication plugin

should include an array of 256
elements.
Each array should include at

least one valid function.
Do not assign a function to

element 0.
The library should include the following

decryption plugins, using these exact
names:
decrypt_amf
decrypt_k
initialize_decryptors.
The library should include the following

sequence number plugins, using these
exact names:
check_sqn
generate_sqn.
...........................................................................................................................................................................................................................................................
C - 8

270-710-919R6.0

functions
Requirement(s)
Returned data
When called by AuC with the required

parameters, each service providerdeveloped function should return the
required authentication data.
Specific data requirements are provided
in the specifications for the individual
plugins and functions.
Development process
Table C-2, "Service provider function development process" (C-10)

provides a high-level process for developing, storing, and testing the
Auc-supporting library.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 9

functions
Figure C-2
Service provider function development process
...........................................................................................................................................................................................................................................................
C - 10

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview
The USDS AuC requires a set of authentication API plugins in three

categories:
Authentication
Decryption
Sequence number.
This section introduces arrays associated with authentication functions.

Authentication arrays
Each array is designed to provide specific authentication data as shown

in Table C-3, "AuC authentication arrays" (C-11).
Table C-3
AuC authentication arrays
Authentication array
Generates
Umts_auc_a3_plugin
SRES data (GSM user).
Umts_auc_a8_plugin
Kc data (GSM user).
Umts_auc_f1_plugin
MAC data (UMTS user).
MACS data (UMTS user).
Umts_auc_f2_plugin
XRES data (UMTS user).
Umts_auc_f3_plugin
CK data (UMTS user).
Umts_auc_f4_plugin
IK data (UMTS user).
Umts_auc_f5_plugin
AK data (UMTS user).
AK data (UMTS user).
Each authentication array name actually represents a

set of 256 functions. Each used function within a set has a unique
name.
Important!
Functions of API
When a subscriber makes a service request, the serving SGSN/VLR

requests authentication data for the subscriber's IMSI.
When the USDS AuC receives the request, it queries its subscriber
database to retrieve the data required to meet the request. The retrieved
data includes:
The authentication function version (array location) to use
Authentication-specific data such as "K," "SQN," or "AMF."
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 11
When AuC receives the database information, it constructs an

authentication function call that includes:
The array name and version number
Input parameter data from the subscriber data
An input parameter containing a random number the AuC

generates per authentication request.
The authentication function performs its calculation(s) and returns the

authentication data required by the selected function.
Figure C-3, "API operation, F1 example" (C-12) depicts the process in
more detail.
Note: The figure ignores the HCF role in authentication in order to
focus on API capabilities.
Figure C-3
General requirements
API operation, F1 example
The authentication functions should meet general requirements

regarding:
Array construction
Plugin functions
Array names
...........................................................................................................................................................................................................................................................
C - 12

270-710-919R6.0
Thread safe
Global data
Time to execute.
Array construction
Should provide a 256-element array of functions for each plugin.
Should provide at least one valid function for each array. Set
unused array elements to zero.
Do not assign a function to element 0 or 255.
The standards for UMTS and GSM authentication functions

require support for 255 function versions of each authentication
plugin (element 0 cannot be assigned). These versions are used to
specify different ways of calculating authentication data for
different subscribers or subscriber groups.
Specify the following data to be provisioned:
The function version numbers that should be provisioned in

system data authentication version capabilities.
The appropriate version numbers to assign to each new

subscriber or subscriber class.
Plugin functions
A plugin function for each non-zero element in every function array

must be developed. At least one valid function for each array must be
provided.
Array names
Arrays should be named exactly as specified in the plugin-specific

sections of this document.
Thread safe
The code that calls authentication functions runs in threads. The

authentication functions should be thread safe.
Global data
Authentication functions cannot use global data.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 13
Execution time
A complete authentication transaction, including all customer

authentication function computations and decryptions should execute
and return required data in 5000 micro seconds or less.
...........................................................................................................................................................................................................................................................
C - 14

270-710-919R6.0
............................................................................................................................................................................................................................................................
Overview
The a3 plugin provides SRES authentication data for GSM users.

When the AuC requires a3 authentication data, it generates a call that
includes:
1.
2.
3.
4.
5.
6.
The required array name, Umts_auc_a3_plugin

Version number
ki value
rand value
required output (sres)
return value (bool).
Call example
Umts_auc_a3_plugin[1]( ki, rand, sres );

Data requirements
Support for a3 AuC calls depends on data described in Table C-4, "a3
Value definitions" (C-15):
Table C-4
Name
a3 Value definitions
Type definition
Description
Umts_auc_a3_plugi
n
The required array name.
[n]
The array size. The AuC call

includes a decimal integer from 1
through 255 that is the pointer into
The array.
ki
const unsigned char*
A 16 octets identification key

value retrieved from subscriber
data.
rand
A 16-octet random number the

AuC generated for this request.
sres
unsigned long&
A 4-octet number generated by

the function.
Return value
bool
Return true if successful, false if

unsuccessful.
Define and set a3 array
The a3 array should be defined and set as follows:
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 15
Important! Make sure to use the plugin name exactly as it is

presented in the example, Umts_auc_a3_plugin, and set the array
size to 256.
Example
The following example shows an a3 array with one function, umtsa3_1:

// a3 example
bool umtsa3_1 ( const unsigned char* ki, const unsigned
char* rand, unsigned long & sres ) { sres = 0xbaadf00d;
return true; }
bool (*Umts_auc_a3_plugin[256]) ( const unsigned char*
ki, const unsigned char* rand, unsigned long & sres ) =
{
0,umtsa3_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0 };
Populate array elements as

desired
Populate array elements 1-254 as desired to match the a3 function

versions you want to support:
Do not populate array element zero or 255.
If assigned to element 255, the function will be overridden by the

Lucent-provided function.
Populate array elements that correspond to the actual version

numbers to be used to provision subscriber authentication data.
Example: The example entry in array element 1 indicates that a call to

Umts_auc_a3_plugin with a version number of 1 will be processed by
function umtsa3_1.
...........................................................................................................................................................................................................................................................
C - 16

270-710-919R6.0
............................................................................................................................................................................................................................................................
Overview
The a8 plugin provides cipher key (kc) authentication data for GSM
users.
AuC a8 call
When the AuC requires a8 authentication data, it generates a call that

includes:
The required array name, Umts_auc_a8_plugin
Version number
ki value
rand value
required output (kc)
Call example
Umts_auc_a8_plugin[1]( ki, rand, kc );

a8 data requirements
Support for a8 AuC calls depends on data described in Table C-5, "a8
value definitions" (C-17):
Table C-5
Name
a8 value definitions
Type definition
Description
Umts_auc_a8_plugin
[n]
The array size. The AuC call includes a

decimal integer from 1 through 255 that
is the pointer into the array.
ki
A 16 octets identification key value

retrieved from subscriber data.
rand
A 16-octet random number the AuC

generated for this request.
kc
unsigned long long&
An 8-octet number generated by the

function.
Return value
bool

unsuccessful.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 17
Define and set a8 array
The a8 array should be defined and set as follows:

Make sure to use the plugin name exactly as it is
presented in the example, Umts_auc_a8_plugin, and set the array
size to 256.
Important!
Example
The following example shows an a8 array with one function, umtsa8_1.

// a8 example
bool umtsa8_1 ( const unsigned char* ki, const unsigned
char* rand, unsigned long long & kc ) { kc =
0xbaadbeefdeadface; return true; }
bool (*Umts_auc_a8_plugin[256]) ( const unsigned char*
ki, const unsigned char* rand, unsigned long long & kc
) =
{
0,umtsa8_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0 };

desired
Populate array elements 1-254 as desired to match the a8 function



numbers to be used to provision subscriber authentication data

Umts_auc_a8_plugin with a version number of 1 will be processed by
function umtsa8_1.
...........................................................................................................................................................................................................................................................
C - 18

270-710-919R6.0
............................................................................................................................................................................................................................................................
Overview
The f1 plugin provides MAC authentication data for UMTS users.

AuC f1 call
When the AuC requires f1 authentication data, it generates a call that

includes:
1.
2.
3.
4.
5.
6.
7.
8.
The required array name, Umts_auc_f1_plugin

Version number
k value
rand value
sqn value
amf value
required output (mac)
Call example
Umts_auc_f1_plugin[1]( k, rand, sqn, amf, mac );

f1 data requirements
Support for f1 AuC calls depends on data described in Table C-6, "f1
value definitions" (C-19).
Table C-6
Name
Type definition
Description
Umts_auc_f1_plugin
[n]
The array size. The AuC call includes

a decimal integer from 1 through 255
that is the pointer into the array.
A 16 octets k value retrieved from

subscriber data.
rand

sqn
const unsigned long long

amf
const unsigned short
A 16-bit number retrieved from

subscriber data.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 19
Name
Type definition
Description
mac
unsigned long long&

function.
Return value
bool

unsuccessful.
Define and set f1 array
The f1 array should be defined and set as follows:

presented in the example, Umts_auc_f1_plugin, and set the array
size to 256.
Important!
Example
The following example shows an f1 array with one function, umtsf1_1

// f1 example
bool umtsf1_1 ( const unsigned char* k, const unsigned
char* rand, const unsigned long long sqn, const
unsigned short amf, unsigned long long & mac )
{ mac = 0x1122334455667788; return true; }
bool (*Umts_auc_f1_plugin[256]) (const unsigned char*
k,const unsigned char* rand,const unsigned long long
sqn,const unsigned short amf, unsigned long long &
mac) =
{
0,umtsf1_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0 };

desired
Populate array elements 1-254 as desired to match the f1 function


...........................................................................................................................................................................................................................................................
C - 20

270-710-919R6.0


Umts_auc_f1_plugin with a version number of 1 will be processed by
function umtsf1_1.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 21
............................................................................................................................................................................................................................................................
Overview
The f1star API provides MACS authentication data for UMTS users.
AuC f1star call
When the AuC requires f1* authentication data, it generates a call that
includes:
The required array name, Umts_auc_f1star_plugin
Version number
k value
rand value
sqn value
amf value
required output (macs)
Call example
Umts_auc_f1star_plugin[1]( ki, rand, sres );

f1star data requirements
Support for f1star AuC calls depends on data described in Table C-7,
"f1star value definitions" (C-22).
Table C-7
Name

Type definition
Description
[n]
The array size. The AuC call

includes a decimal integer from 1
through 255 that is the pointer into
the array.

subscriber data.
rand

sqn
const unsigned long

long

...........................................................................................................................................................................................................................................................
C - 22

270-710-919R6.0
Name
Type definition
Description
amf
A 16-bit number retrieved from

subscriber data.
macs
unsigned long long&

function.
Return value
bool

unsuccessful.
Define and set f1star array
The f1star array should be defined and set as follows:

Important! Make sure to use the plugin name exactly as it is
presented in the example, Umts_auc_f1star_plugin, and set the
array size to 256.
Example
The following example shows an f1* array with one function,

umtsf1star_1:
// f1star example
bool umtsf1star_1 ( const unsigned char* k, const
unsigned char* rand, const unsigned long long sqn,
const unsigned short amf, unsigned long long & macs )
{ macs = 0x8899aabbccddeeff; return true; }
bool (*Umts_auc_f1star_plugin[256]) (const unsigned char*
k,const unsigned char* rand,const unsigned long long
sqn,const unsigned short amf, unsigned long long &
macs) =
{
0,umtsf1star_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0 };

desired

...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 23



Umts_auc_f1star_plugin with a version number of 1 will be processed
by function umtsf1star_1.
...........................................................................................................................................................................................................................................................
C - 24

270-710-919R6.0
............................................................................................................................................................................................................................................................
Overview
The f2 plugin provides XRES authentication data for UMTS users.

AuC f2 call

includes:
Version number
k value
rand value
xres_size value
required output (xres)
Call example
Umts_auc_f2_plugin[1]( k, rand, xres_size, xres );

value definitions" (C-25)
Table C-8
Name
Type definition
Description
Umts_auc_f2_plugin
[n]


subscriber data.
rand

xres_size
const unsigned char
A system variable that defines the

number of octets of xres to use.
xres
unsigned char*
A 4 to 16 octet number generated by the

function.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 25
Name
Type definition
Description
Return value
bool

unsuccessful.

size to 256.
Important!
Example
The following example shows an f2 array with one function, umtsf2_1:

// f2 example
bool umtsf2_1 ( const unsigned char* k, const unsigned
char* rand, const unsigned char xres_size, unsigned
char* xres ) { strcpy ( (char*)xres, "testing xres" );
return true; }
bool (*Umts_auc_f2_plugin[256]) ( const unsigned char* k,
const unsigned char* rand, const unsigned char
xres_size, unsigned char* xres ) =
{
0,umtsf2_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0 };

desired



...........................................................................................................................................................................................................................................................
C - 26

270-710-919R6.0

function umtsf2_1.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 27
............................................................................................................................................................................................................................................................
Overview
The f3 plugin provides a cipher key (ck) for UMTS users.

AuC f3 call

includes:
Version number
k value
rand value
required output (ck)
Call example
Umts_auc_f3_plugin[1]( k, rand, ck );
Table C-9
Name
Type definition
Description
Umts_auc_f3_plugin
[n]


subscriber data.
rand

ck
unsigned char*
A 16 octet cipher key provided by the

function.
Return value
bool

unsuccessful.
...........................................................................................................................................................................................................................................................
C - 28

270-710-919R6.0

size to 256.
Important!
Example
The following example shows an f3 array with one function, umtsf3_1.

// f3 example
bool umtsf3_1( const unsigned char* k, const unsigned
char* rand, unsigned char* ck ) { strcpy( (char*)ck,
"testing ck" ); return true; }
const unsigned char* rand, unsigned char* ck ) =
{
0,umtsf3_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0 };

desired




function umtsf3_1.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 29
............................................................................................................................................................................................................................................................
Overview
The f4 plugin provides an integrity key (ik) for UMTS users.

AuC f4 call

includes:
1.
2.
3.
4.
5.
6.

Version number
k value
rand value
required output (ik)
Call example
Umts_auc_f4_plugin[1]( k, rand, ik );
Table C-10
Name
Type definition
Description
Umts_auc_f4_plugin
[n]


subscriber data.
rand

ik
unsigned char*
A 16 octet integrity key provided by the

function.
Return value
bool

unsuccessful.
...........................................................................................................................................................................................................................................................
C - 30

270-710-919R6.0

size to 256.
Important!
Example

// f4 example
char* rand, unsigned char* ik ) { strcpy( (char*)ik,
"testing ik" ); return true; }
const unsigned char* rand, unsigned char* ik ) =
{
0,umtsf4_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0 };

desired




function umtsf4_1.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 31
............................................................................................................................................................................................................................................................
Overview
The f5 plugin provides an anonymity key (ak) for UMTS users.

AuC f5 call

includes:
1.
2.
3.
4.
5.
6.

Version number
k value
rand value
required output (ak)
Call example
Umts_auc_f5_plugin[1]( k, rand, ak );
Table C-11
Name
Type definition
Description
Umts_auc_f5_plugin
[n]


subscriber data.
rand

ak
unsigned long long&
A 6-octet anonymity key provided by the

function.
Return value
bool

unsuccessful.
...........................................................................................................................................................................................................................................................
C - 32

270-710-919R6.0

size to 256.
Important!
Example

// f5 example
char* rand, unsigned long long & ak ) { ak =
0x123456789abc; return true; }
const unsigned char* rand, unsigned long long & ak ) =
{
0,umtsf5_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0 };

desired

1.
2.
3.


function umtsf5_1.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 33
............................................................................................................................................................................................................................................................
Overview
The f5 plugin provides a Resynch anonymity key (ak) for UMTS users.
AuC f5star call
When the AuC requires f5star authentication data, it generates a call

that includes:
The required array name, Umts_auc_f5star_plugin
Version number
k value
rand value
required output (ak)
return value (bool)
Call example
Umts_auc_f5star_plugin[1]( k, rand, ak );
f5star data requirements
Support for f5star AuC calls depends on data described in Table C-12,
"f5star value definitions" (C-34).
Table C-12
Name
Type definition
Description
[n]


subscriber data.
Rand

Ak
unsigned long long&
A 6-octet Resynch anonymity key

provided by the function.
Return value
bool

unsuccessful.
...........................................................................................................................................................................................................................................................
C - 34

270-710-919R6.0
Define and set f5star array
The f5star array should be defined and set as follows:

Make sure to use the plugin name exactly as it is presented in the
example, Umts_auc_f5star_plugin, and set the array size to 256.
Example
The following example shows an f5 array with one function,

umtsf5star_1.
// f5star example
bool umtsf5star_1( const unsigned char* k, const unsigned
char* rand, unsigned long long & ak ) { ak =
0x123456789abc; return true; }
bool (*Umts_auc_f5star_plugin[256]) ( const unsigned
char* k, const unsigned char* rand, unsigned long long
& ak ) =
{
0,umtsf5star_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0 };

desired
Populate array elements 1-254 as desired to match the f5star function




Umts_auc_f5star_plugin with a version number of 1 will be processed
by function umtsf5star_1.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 35

............................................................................................................................................................................................................................................................
Overview

categories:
1.
2.
3.
Authentication
Decryption
Sequence number.
This section introduces functions associated with decryption.

Decryption functions
Each function is designed to provide a specific decryption task as

shown in Table C-13, "AuC decryption functions" (C-36).
Table C-13
General description
Decryption Function
Purpose
decrypt_amf
Decrypt the AMF parameter (UMTS

only).
decrypt_k
Decrypt the K or Ki subscriber parameter.
initialize_decryptors
Initialize any decryption parameters.

Called before any of the decrypt API is
called.
USDS stores subscriber K/KI (both refer to Identity Key) and AMF
(Authentication and key Management Field) values in an encrypted
form. Functions to decrypt K/KI and AMF and return the decrypted
values to AuC should be provided.
A function should be provided to initialize the decryptor functions
when USDS is started.
...........................................................................................................................................................................................................................................................
C - 36

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview
Encryptor/Decryptor
coordination
Plugin functions
The decryption functions should meet general requirements regarding:
Encryptor/Decryptor coordination
Plugin functions
Function names
Thread safe
Use of global data
Time to execute.
The decryptor algorithm(s) used in the decryptor functions should work

with the encryption algorithm(s) used to encrypt subscriber AMF and
K data provisioned through the eSM.
Three decryption-related functions must be developed:
1.
2.
3.
decrypt_amf
decrypt_k
initialize_decryptors.
Function details are described in the function-specific sections of this

document.
Function names
Functions should be named exactly as specified in the function-specific

sections of this document.
Thread safe
The code that calls decryption functions runs in threads. The functions
should be thread safe.
Global data
Decryption functions can use global data. Note that any use of global
data cannot interfere with the "thread safe" requirement.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 37
............................................................................................................................................................................................................................................................
Overview
The decrypt_amf function decrypts the AMF value stored in

subscriber-specific data.
AuC decrypt_amf call
When the AuC requires AMF decryption, it generates a call that

includes:
The required function name
AMF (encrypted) value
Required output (AMF decrypted value, new_amf).
The function should decrypt and return a plain AMF value.

Call example
decrypt_amf (amf, new_amf );

decrypt_amf data
requirements
Support for decrypt_amf AuC calls depends on data described in

Table C-14, "decrypt_amf value descriptions" (C-38).
Table C-14
Name
decrypt_amf value descriptions
Type definition
decrypt_amf
Description
The required name for the AMF
decryptor.
amf
A 2-octet encrypted number retrieved

from subscriber data.
new_amf
unsigned short&
A 2-octet number - decrypted amf generated by the function.
Return value
bool

unsuccessful.
decrypt_amf example
The following code snippet represents one way of developing a

decrypt_amf function that supports USDS requirements. The function
will access the decryption algorithm you choose.
// AMF decryptor example
bool decrypt_amf( const unsigned short amf, unsigned
short & new_amf )
{
...........................................................................................................................................................................................................................................................
C - 38

270-710-919R6.0
if( amf == 0 ) return false;

new_amf = amf >> 8;
return true;
}
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 39
............................................................................................................................................................................................................................................................
Overview
The decrypt_k function decrypts the K (Identity Key) value stored in

AuC decrypt_k call
When the AuC requires K decryption, it generates a call that includes:
K (encrypted) value
Required output (K decrypted value, new_k).
The function should decrypt K and return a plain K value.

Call example
decrypt_k( k, new_k);
decrypt_k data
requirements
Support for decrypt_k AuC calls depends on data described in

Table C-15, "decrypt_k value definitions" (C-40).
Table C-15
Name
decrypt_k value definitions
Type definition
decrypt_k
Description
The required name for the K decryptor.
A 16-octet encrypted number retrieved

from subscriber data.
new_k
unsigned char*
A 16-octet number - decrypted k generated by the function.
Return value
bool

unsuccessful.
decrypt_k example

decrypt_k function that supports USDS requirements. The function will
access the decryption algorithm you choose.
// K decryptor example
bool decrypt_k( const unsigned char * k, unsigned char *
new_k )
{
if( k[0]==0 && k[1]==0 && k[2]==0 && k[3]==0 && k[4]==0 &&
k[5]==0 && k[6]==0
...........................................................................................................................................................................................................................................................
C - 40

270-710-919R6.0
&& k[7]==0 && k[8]==0 && k[9]==0 && k[10]==0 && k[11]==0
&& k[12]==0
&& k[13]==0 && k[14]==0 && k[15]==0 )
{
return false;
}
memcpy( new_k, k, 16 ); return true;
}
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 41
............................................................................................................................................................................................................................................................
Overview
The initialize_decryptors function initializes decrypt_amf and

decrypt_k each time USDS is started.
AuC initialize_decryptors call
When USDS starts, AuC generates a call to initialize_decryptors.

initialize_decryptors does not have parameters or outputs. The purpose
of the call is to give the decryptors time to initialize. The call includes
only the required function name.
The function should initialize the decryptors.
Call example
initialize_decryptors( );
initialize_decryptor
requirements
initialize_decryptor
example
There are two requirements for this function:
The function should be named initialize_decryptors
The function should return a boolean indicator of success or

failure.
The following code snippet represents one way of developing an

initialize_decryptors function that supports USDS requirements.
// Initialize decryptors signature
bool initialize_decryptors() { return true; }
...........................................................................................................................................................................................................................................................
C - 42

270-710-919R6.0

............................................................................................................................................................................................................................................................
Overview

categories:
1.
2.
3.
Authentication
Decryption
Sequence number.
This section introduces functions associated with sequence numbers

(SQN).
SQN functions
Each function is designed to provide a specific sequence numbering

task as shown in Table C-16, "AuC sequence number functions"
(C-43).
Table C-16
Sequence number general

description
Sequence Number
Function
Purpose
generate_sqn
Generates a new sequence number.
check_sqn
Validates a newly-generated sequence

number.
Functions to generate and check sequence numbers and return the

results to AuC should be provided.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 43

............................................................................................................................................................................................................................................................
Overview
Plugin functions
The sequence number functions should meet general requirements

regarding:
Plugin functions
Function names
Thread safe
Use of global data
Time to execute.
Two sequence number-related functions need to be developed:

1.
2.
generate_sqn
check_sqn.
Function details are described in the function-specific sections of this

document.
Function names
Functions should be named exactly as specified in the functionspecific sections of this document.
Thread safe
The code that calls authentication functions runs in threads. The

sequence number functions should be thread safe.
Global data
Sequence number functions cannot use global data.
...........................................................................................................................................................................................................................................................
C - 44

270-710-919R6.0
............................................................................................................................................................................................................................................................
Overview
The generate_sqn function creates a new USDS SQN value from

AuC generate_sqn call
When the AuC requires a new sequence number, it generates a call that
includes:
Selector
IMSI/NAI
Old SQN (old_sqn)
Required output (a new SQN, new_sqn).
The function should generate and return a new SQN for USDS.
Call example
generate_sqn ( Sqn_selector sel, imsi, old_sqn, new_sqn );

generate_sqn ( Sqn_selector sel, nai, old_sqn, new_sqn );
generate_sqn data
requirements
Support for generate_sqn AuC calls depends on data described in

Table C-17, "generate_sqn value definitions for UMTS HLR" (C-45).
Table C-17
Name
generate_sqn value definitions for UMTS HLR
Type definition
Description
generate_sqn
The required name for the function.
sel
A sequence indicator, one of:
imsi
init (0)
continue (1)
new_batch (2)
The requesting subscriber's IMSI.

A 3-8 octet number of up to 15 TBCD
(Telephony Binary Coded Decimal)
characters, followed by a terminating
semi-octet of 0xF.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 45
Name
Type definition
Description
old_sqn
A 6-octet number, the subscriber's current

SQN.
new_sqn
unsigned long long&
A 6-octet number, the new SQN

calculated by the function.
Return value
bool

unsuccessful.
When to generate_sqn value definitions for HSS, the IMSI must be

replaced by user's NAI (PRID), and type is const char[97].
generate_sqn example

generate_sqn function that supports USDS requirements.
// Sequence # signatures
enum Sqn_selector {
Sqn_init = 0,
Sqn_continue = 1,
Sqn_new_batch = 2
};
// Generate sequence number for UMTS HLR
bool generate_sqn( Sqn_selector sel, const unsigned long
long imsi, const unsigned long long old_sqn, unsigned
long long & new_sqn )
{
unsigned long long new_seq;
unsigned long long new_ind;
unsigned long long old_seq;
unsigned long long old_ind;
unsigned long long max_seq = 1;
unsigned long long max_ind = 1;
unsigned long long ind_mask = 1;
if( sel == Sqn_init )
{
new_seq = 1;
new_ind = 0;
}
else
{
max_seq <<= (SQN_LEN - SQN_IND_bits);
max_ind <<= SQN_IND_bits;
ind_mask = max_ind - 1;
old_seq
old_ind
new_seq
new_ind
=
=
=
=
old_sqn >> SQN_IND_bits;

old_sqn & ind_mask;
(old_seq + 1)%max_seq;
(old_ind + 1)%max_ind;
...........................................................................................................................................................................................................................................................
C - 46

270-710-919R6.0
}
new_sqn = (new_seq << SQN_IND_bits) | (new_ind);
return true;
}
// Generate sequence number for HSS
bool generate_sqn( Sqn_selector sel, const char *NAI,
const unsigned long long old_sqn, unsigned long long &
new_sqn )
{
unsigned long long imsi = 0;
return generate_sqn(sel, imsi, old_sqn, new_sqn );
}
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 47
............................................................................................................................................................................................................................................................
Overview
The check_sqn function validates a newly-generated SQN.

AuC check_sqn call
When the AuC requires new sequence number validation, it generates a

call that includes:
IMSI/NAI
New USDS SQN (next_sqnhe)
Mobile station SQN (new_sqnms)
Return value (indicator of validation, false or true).
The function should return the results of the validation check, true or
false.
Call example
check_sqn (imsi, next_sqnhe, new_sqnms, );

check_sqn (nai, next_sqnhe, new_sqnms);
check_sqn data
requirements
Support for check_sqn AuC calls depends on data described in

Table C-18, "check_sqn value definitions for UMTS HLR" (C-48).
Table C-18
Name
check_sqn value definitions for UMTS HLR
Type definition
check_sqn
Description
The required name for the function.
imsi
The requesting subscriber's IMSI.A 3-8

octet number of up to 15 TBCD
(Telephony Binary Coded Decimal)
characters, followed by a terminating
semi-octet of 0xF.
next_sqnhe
A 6-octet number, the subscriber's SQN

on USDS
new_sqnms
A 6-octet number, the mobile station

SQN.
Return value
bool

unsuccessful.
...........................................................................................................................................................................................................................................................
C - 48

270-710-919R6.0
To check_sqn value definitions for HSS, The IMSI must be replaced by

user's NAI (PRID), and type is const char[97].
check_sqn example

check_sqn function that supports USDS requirements for UMTS HLR.
// Check sequence number
bool check_sqn( const unsigned long long imsi, const
unsigned long long next_sqnhe, const unsigned long
long new_sqnms )
{
unsigned long long seq_he;
unsigned long long seq_ms;
bool rtn;
seq_he = next_sqnhe >> SQN_IND_bits;
seq_ms = new_sqnms >> SQN_IND_bits;
if(SQN_Delta > 0)
{
rtn = ((seq_he > seq_ms) && (seq_he - seq_ms <=
SQN_Delta)) ? true : false;
}
else
{
rtn = (seq_he > seq_ms) ? true : false;
}
return rtn;
}
// Check sequence number for HSS
bool check_sqn( const char *NAI, const Ub8 next_sqnhe,
const Ub8 new_sqnms )
{
unsigned long long imsi = 0;
return check_sqn( imsi, next_sqnhe, new_sqnms );
}
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 49

............................................................................................................................................................................................................................................................
Overview
This section provides an example of service-developed authentication

function software.
Example header file
#ifndef __UMTS_AUC_PLUGIN_H
#define __UMTS_AUC_PLUGIN_H
/*
* FILE NAME: Umts_auc_plugin.h
*
* WHAT: Extern the UMTS AuC plugin functions. These are
defined by the
* HLR customers. These plugin's include f1 - f5 for 3G, a3
and a8 for 2G, sequence
* number generators and decryptors.
*
*/
typedef unsigned char Ub1;
typedef unsigned short Ub2;
typedef unsigned long Ub4;
typedef unsigned long long Ub8;
const int Max_plugins = 256;
// F1 through F5 signatures
extern bool (*Umts_auc_f1_plugin[Max_plugins])(const Ub1*
k,const Ub1* rand,const Ub8 sqn, const Ub2 amf, Ub8&
mac);
extern bool (*Umts_auc_f1star_plugin[Max_plugins]) (const
Ub1* k, const Ub1* rand, const Ub8 sqn, const Ub2 amf,
Ub8& macs);
extern bool (*Umts_auc_f2_plugin[Max_plugins]) (const
Ub1* k, const Ub1* rand,
const Ub1 xres_size, Ub1* xres);
Ub1* k, const Ub1* rand, Ub1* ck);
Ub1* k, const Ub1* rand, Ub1* ik);
Ub1* k, const Ub1* rand, Ub8& ak);
extern bool (*Umts_auc_f5star_plugin[Max_plugins]) (const
Ub1* k, const Ub1* rand, Ub8& ak);
// A3, A8 signatures
extern bool (*Umts_auc_a3_plugin[Max_plugins]) (const
Ub1* ki, const Ub1* rand, Ub4& sres);
extern bool (*Umts_auc_a8_plugin[Max_plugins]) (const
Ub1* ki, const Ub1* rand, Ub8& kc);
// Sequence # signatures
...........................................................................................................................................................................................................................................................
C - 50

270-710-919R6.0
enum Sqn_selector {
Sqn_init = 0,
Sqn_continue = 1,
Sqn_new_batch = 2
};
extern bool generate_sqn( Sqn_selector, const Ub8 imsi,
const Ub8 old_sqn, Ub8& new_sqn );
extern bool check_sqn( const Ub8 imsi, const Ub8 sqnhe,
const Ub8 sqnms );
// Decryptor signatures
extern bool decrypt_k( const Ub1* k, Ub1* new_k );
extern bool decrypt_amf( const Ub2 amf, Ub2& new_amf );
extern bool initialize_decryptors();
#endif
Example.c file
/*
* FILE NAME: Umts_auc_plugin.C
*
* WHAT: Define the default UMTS AuC plugin functions.
These are defined by the
* HLR customers. These plugin's include f1 - f5 for 3G, a3
and a8 for 2G, sequence
* number generators and decryptors.
*
*/
#include "Umts_auc_plugins.h"
#include <string.h>
// F1 through F5 signatures
bool umtsf1_1( const Ub1* k, const Ub1* rand, const Ub8
sqn, const Ub2 amf, Ub8& mac )
{ mac = 0x1122334455667788; return true; }
bool umtsf1star_1( const Ub1* k, const Ub1* rand, const
Ub8 sqn, const Ub2 amf, Ub8& macs )
size, Ub1* xres ) { strcpy ( (char*)xres, "testing
xres" ); return true; }
bool umtsf3_1( const Ub1* k, const Ub1* rand, Ub1* ck ) {
strcpy( (char*)ck, "testing ck" ); return true; }
bool umtsf4_1( const Ub1* k, const Ub1* rand, Ub1* ik ) {
strcpy( (char*)ik, "testing ik" ); return true; }
bool umtsf5_1( const Ub1* k, const Ub1* rand, Ub8& ak ) {
ak = 0x123456789abc; return true; }
bool umtsf5star_1( const Ub1* k, const Ub1* rand, Ub8& ak
) { ak = 0x123456789abc; return true; }
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 51
// Version 2, for PCIT

{ mac = 0x1122334455667788; return true; }
size, Ub1* xres )
{
memset( xres, 16, 0 );
xres[3] = 1;
return true;
}
bool umtsf3_2( const Ub1* k, const Ub1* rand, Ub1* ck ) {
strcpy( (char*)ck, "testing ck" ); return true; }
bool umtsf4_2( const Ub1* k, const Ub1* rand, Ub1* ik ) {
strcpy( (char*)ik, "testing ik" ); return true; }
bool umtsf5_2( const Ub1* k, const Ub1* rand, Ub8& ak ) {
ak = 0x123456789abc; return true; }
bool umtsf5star_2( const Ub1* k, const Ub1* rand, Ub8& ak
) { ak = 0x123456789abc; return true; }
{ mac = 0x1122334455667788; return true; }
size, Ub1* xres ) { strcpy ( (char*)xres, "testing
xres" ); return true; }
bool umtsf3_254( const Ub1* k, const Ub1* rand, Ub1* ck )
{ strcpy( (char*)ck, "testing ck" ); return true; }
bool umtsf4_254( const Ub1* k, const Ub1* rand, Ub1* ik )
{ strcpy( (char*)ik, "testing ik" ); return true; }
bool umtsf5_254( const Ub1* k, const Ub1* rand, Ub8& ak )
{ ak = 0; return true; }
bool umtsf5star_254( const Ub1* k, const Ub1* rand, Ub8&
ak ) { ak = 0; return true; }
bool umtsa3_1( const Ub1* ki, const Ub1* rand, Ub4& sres )
{ sres = 0xbaadf00d; return true; }
bool umtsa8_1( const Ub1* ki, const Ub1* rand, Ub8& kc ) {
kc = 0xbaadbeefdeadface; return true; }
...........................................................................................................................................................................................................................................................
C - 52

270-710-919R6.0
bool umtsa3_254( const Ub1* ki, const Ub1* rand, Ub4&

sres ) { return false; }
bool umtsa8_254( const Ub1* ki, const Ub1* rand, Ub8& kc )
{ return false; }
bool generate_sqn( Sqn_selector sel, const Ub8 imsi,
const Ub8 old_sqn, Ub8& new_sqn )
{
if( sel == Sqn_init )
new_sqn = 1;
else
new_sqn = old_sqn + 1;
return true;
}
bool check_sqn( const Ub8 imsi, const Ub8 next_sqnhe,
const Ub8 new_sqnms )
{ return ( (new_sqnms > next_sqnhe) ? false : true ); }
// Decryptor signatures
bool decrypt_k( const Ub1* k, Ub1* new_k )
{
if( k[0]==0 && k[1]==0 && k[2]==0 && k[3]==0 && k[4]==0 &&
k[5]==0 && k[6]==0
&& k[7]==0 && k[8]==0 && k[9]==0 && k[10]==0 && k[11]==0
&& k[12]==0
&& k[13]==0 && k[14]==0 && k[15]==0 )
{
return false;
}
memcpy( new_k, k, 16 ); return true;
}
bool decrypt_amf( const Ub2 amf, Ub2& new_amf )
{
if( amf == 0 ) return false;
new_amf = amf >> 8;
return true;
}
bool initialize_decryptors() { return true; }
// Define and set the plugin arrays
bool (*Umts_auc_f1_plugin[Max_plugins])(const Ub1*
k,const Ub1* rand,const Ub8 sqn,
const Ub2 amf, Ub8& mac) =
{
0,umtsf1_1,umtsf1_2,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 53
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,umtsf1_254,0 };
bool (*Umts_auc_f1star_plugin[Max_plugins]) (const Ub1*
k, const Ub1* rand,
const Ub8 sqn, const Ub2 amf, Ub8& macs) =
{
0,umtsf1star_1,umtsf1star_2,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,umtsf1star_254,0 };
bool (*Umts_auc_f2_plugin[Max_plugins]) (const Ub1* k,
const Ub1* rand,
const Ub1 xres_size, Ub1* xres) =
{
0,umtsf2_1,umtsf2_2,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,umtsf2_254,0 };
...........................................................................................................................................................................................................................................................
C - 54

270-710-919R6.0

const Ub1* rand, Ub1* ck) =
{
0,umtsf3_1,umtsf3_2,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,umtsf3_254,0 };
const Ub1* rand, Ub1* ik) =
{
0,umtsf4_1,umtsf4_2,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,umtsf4_254,0 };
const Ub1* rand, Ub8& ak) =
{
0,umtsf5_1,umtsf5_2,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 55
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,umtsf5_254,0 };
bool (*Umts_auc_f5star_plugin[Max_plugins]) (const Ub1*
k, const Ub1* rand, Ub8& ak) =
{
0,umtsf5star_1,umtsf5star_2,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,umtsf5star_254,0 };
bool (*Umts_auc_a3_plugin[Max_plugins]) (const Ub1* ki,
const Ub1* rand, Ub4& sres) =
{
0,umtsa3_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,umtsa3_254,0 };
bool (*Umts_auc_a8_plugin[Max_plugins]) (const Ub1* ki,
const Ub1* rand, Ub8& kc) =
{
0,umtsa8_1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
...........................................................................................................................................................................................................................................................
C - 56

270-710-919R6.0
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,umtsa8_254,0 };
...........................................................................................................................................................................................................................................................
270-710-919R6.0

C - 57
...........................................................................................................................................................................................................................................................
C - 58

270-710-919R6.0
Glossary
.........
Acronyms
AC
ANSI
BAIC
BAOC
BOC
BOIC
BOIC-exHC
BS
CALEA
CAMEL
CC
CCF
CFB
CFD
CFNA
CFNRc
CFNRy
CFU
CH
CLIR
COLP
COLR
CORBA
CORC
CS
CSCF
CSI
CW
DAP
DB
DN
DS
ECT
Authentication Center
American National Standards Institute
Barring of All Incoming Calls
Barring of All Outgoing Calls
Barring of Outgoing Calls
Barring of Outgoing International Calls
Barring of International Calls Except those directed to the Home
PLMN Country
Bearer service
Communications Assistance Law Enforcement Act
Customized Applications for Mobile Network Enhanced Logic
Country Code
Conditional Call Forwarding
Call Forwarding on Mobile Subscriber Busy
Call Forwarding Default
Call Forwarding No Answer
Call Forwarding on Mobile Subscriber Not Reachable
Call Forwarding on No Reply
Call Forwarding Unconditional
Call Hold
Calling Line Identification Restriction
Connected Line Identification Presentation
Connected Line Identification Restriction
Common Object Request Broker Architecture
Customer Originated Recent Change Request
Circuit Switched
Call Session Control Function
CAMEL Subscription Information
Call Waiting
Display Action Pages
Database
Directory Number
Data Server
Explicit Call Transfer
...........................................................................................................................................................................................................................................................
270-710-919R6.0

GLOSSARY
GL-1
Enhanced Services Authoring Environment

eSAE
Enhanced Service Manager
eSM
Extended Origination Indicator
EOI
Fully Qualified Domain Name
FQDN
File Transfer Protocol
FTP
General Packet Radio Systems
GPRS
Global Systems for Mobile Communications
GSM
Graphical User Interface
GUI
Home Customer Care
HCC
HLR Control Function
HCF
HLR Data Function
HDF
Home Location Register
HLR
Home Service Area
HSA
Home PLMN
HPLMN
Input Message
IM
IP Multimedia Subsystem
IMS
International Mobile Subscriber Identity
IMSI
Intelligent Network
IN
Internet Protocol
IP
Integrated Services Digital Network
ISDN
Location Based Service
LBS
Local Maintenance Terminal
LMT
Local area Network
LAN
Local Mobile Station Identity
LMSI
Lucent Technologies Delivery Unit
LTDU
Mobile Application Part
MAP
MiLife Application Server
MAS
Mobility Management CAMEL Subscription Information
M-CSI
Mobile Directory Number
MDN
Mobile Identification Number
MIN
Mobile-Station-Not-Reachable-Flag
MNRF
Mobile-Station-Not-Reachable-for-GPRS
MNRG
Multi-party
MPTY
Mobile Station
MS
Mobile Switching Center
MSC
Mobile Switching Center Identifier
MSCID
Message Handler
MSGH
Mobile Station ISDN number
MSISDN
Mobile Station Roaming Number
MSRN
Maintenance Terminal
MT
Mobile Terminated
MT
Message Transfer Part
MTP
Message Waiting Count
MWN
National Destination Code
NDC
Network Element
NE
Network Fault Manager
NFM
Numbering Plan Area
NPA
Operation, Maintenance and Administration
OA&M
Operator Determined Barring
ODB
Output Message
OM
Navis Operations and Maintenance Center - HLR
OMC-H
Output Message Database
OMDB
Operations Support System
OSS
Over-The-Air Service Provisioning
OTASP
...........................................................................................................................................................................................................................................................
GLOSSARY
GL-2

270-710-919R6.0
OTFI
PACA
PC
PC_SSN
PLMN
PRID
PS
PUID
QUALDIR
RC/V
REGCAN
REGNOT
RK
RMT
RSA
S&R
SCF
SD
SDHLR
S-FTP
SGSN
SGW
SHLR
SM
SMS
SMS-C
SPA
SPINA
SRI
SS
SS7
SSD
SSN
SU
TCAP
TCP
TCP/IP
TSA
UG-CSI
UI
UMTS
USDS
USLI
VLR
One Time Feature Indicator

Priority Access and Channel Assignment
Point Code
Point Code and Subsystem Number parameter
Public Land Mobile network
Private User Identity
Packet Switched
Public User Identity
QualificationDirective Invoke message defined in ANSI-41
Recent Change and Verify
RegistrationCancellation Invoke message defined in ANSI-41
RegistrationNotification Invoke message defined in ANSI-41
Routing Key
Remote Maintenance Terminal
Romer Service Area
Segmentation and Reassembly
Service Control Function
Service Dispatcher
Super Distributed Home Location Register
Secure File Transfer Protocol
Serving GPRS Support Node
Signalling Gateway Function
Standalone Home Location Register
Short Message
Short Message Service
Short Message Service Center
Service Package Application
Subsciber PIN Access
Send Routing Information
Signaling System Number 7
Shared Secret Data
Subsystem Number
Software Update
Transaction Capabilities Application Part
Transmission Control Protocol
Transmission Control Protocol / Internet Protocol
Traveling Service Area
USSD General CAMEL Subscription Information
User Interface
Universal Mobile Telecommunications Service
Unified Subscriber Data Server
User System Language Interface
Visited Location Register
......................................................................................................................................................................................................
Numerics
2.5G
2G
2.5 Generation
2nd Generation
...........................................................................................................................................................................................................................................................
270-710-919R6.0

GLOSSARY
GL-3
3G
3G-MSC
3rd Generation
Abbreviation for Third Generation. The collective name
used to describe mobile systems able to support a wide
range of Mobile Internet services, operating with greater
bandwidth.
UMTS Mobile Switching Center
......................................................................................................................................................................................................
Active
In recovery terminology, a state that applies to the system, application instances, or

system resources that applications are dependent on to operate normally. Services
are provided by elements in the "active" state.
API
Application Programming Interface

An open interface that makes it easier for third party developers to create new
applications.
AS
Application Server
A network element in IMS network, used for handling services for user. The
service related data requested by the Application Server is downloaded from HSS.
AUC/AC
Authentication Center
Part of the Home Location Register (HLR) in 3G systems, this performs
computations to verify and authenticate the user of mobile phones.
......................................................................................................................................................................................................
Basic telecommuni-cation service
This term is used as a common reference to both bearer services and teleservices.
Bearer capability
A transmission function that the user equipment requests of the network.(Both

bearer services and teleservices are bearer capabilities.)
Bearer Service
A type of telecommunication service that provides the capability of transmission

of signals between access points.
BSS
Base Station Subsystem

The subsystem of equipment such as transceivers and base station controllers.
These interface to subscriber handsets, and the switched network, which enables
connections to be made between a mobile station and a subscriber on the same, or
...........................................................................................................................................................................................................................................................
GLOSSARY
GL-4

270-710-919R6.0
different network such as the Public Switched Telephone Network (PSTN).

......................................................................................................................................................................................................
CALEA
Communications Assistance for Law Enforcement Act

CALEA was passed in response to rapid advances in telecommunications
technology that have threatened the ability of law enforcement officials to conduct
authorized electronic surveillance.CALEA requires telecommunications carriers to
modify their equipment, facilities, and services to ensure that they are able to
comply with authorized electronic surveillance.
CAMEL
Customized Application of Mobile Enhanced Logic

An ETSI standard for GSM networks that enhances the provisioning of IN
(Intelligent Network) services.
CDMA
Code Division Multiple Access

A technology for digital transmission of radio signals between, for example, a
mobile telephone and a radio base station. In CDMA, a frequency is divided using
codes, rather than in time or through frequency separation. Implemented in 800 and
1900 MHz systems around the world.
Component
A hardware or software entity that is used to initialize, start, stop or recover

processes. In USDS these components are the HDF and HCF.
CORBA
Common Object Request Broker Architecture

Provides standard object-oriented interfaces between ORBs (Object Request
Broker), as well as to external applications and application platforms.
CORC
Customer Originated Recent Change Request

A customer originated change that affects subscriber data.
......................................................................................................................................................................................................
Delay Class
Defines the maximum values for mean delay incurred by the transfer of data in the
GPRS network.
Diameter
The Diameter base protocol is intended to provide an Authentication,

Authorization and Accounting (AAA) framework for applications such as network
access or IP mobility. Diameter is also intended to work in both local AAA and
roaming situations.
...........................................................................................................................................................................................................................................................
270-710-919R6.0

GLOSSARY
GL-5
......................................................................................................................................................................................................
ECT
Explicit Call Transfer

The ECT service allows a subscriber who has two calls, each of which can be an
incoming or outgoing call, to connect the other parties in the two calls and release
the subscribers own connection.
EDGE
Enhanced Data rates for Global Evolution

EDGE is a technology that gives GSM and TDMA similar capacity to handle
services for 3G. EDGE was developed to enable the transmission of large amounts
of data at rates of 384kbit/s.
EMS
Element Management System

An operation, administration and maintenance interface for USDS to handle fault
management, performance management and configuration management. The
interface to USDS is through an SNMP interface. NOTE: Release 1.0 will not
include an EMS in the solution.
eSM
Enhanced Service Manager

A subsystem responsible for service provisioning and data tables installation,
including subscriber, network, and global data for USDS. eSM communicates with
USDS through the CORBA/XML interface.
ETSI
European Telecommunications Standards Institute

ETSI's purpose is to define standards that will enable the global market for
telecommunications to function as a single market.
......................................................................................................................................................................................................
Failover
In recovery terminology, failover is a general term that refers to an automatic

action to activate an application service on an alternate system as a result of a
system resource failure.
Failure
In recovery terminology, failure refers to the detectable manifestation that a fault

has on the normal operation of the system.
Fault
In recovery terminology, fault refers to the actual hardware/software problem. This

could include software bugs, parity errors, CPU failure, etc.
...........................................................................................................................................................................................................................................................
GLOSSARY
GL-6

270-710-919R6.0
......................................................................................................................................................................................................
Generic retrofit
A procedure that will change platform software to a new release of software and
will require that all components of USDS system be rebooted at the same time.
GGSN
Gateway GPRS Support Node

The primary function of the Gateway GPRS Support Node is to provide the
interface between the UMTS network and external PDNs (Packet Data Networks)
such as the Internet, corporate intranets and other GPRS networks. It also manages
routing of data packets to the appropriate Serving GPRS Support Node (SGSN),
and collates billing information for the Charging Gateway.
GPRS
General Packet Radio Service

An enhancement for GSM and TDMA core networks that introduces packet data
transmission. GPRS uses radio spectrum very efficiently and provides users with
"always on" connectivity and greater bandwidth.
GTT
Global Title Translation

A feature that allows the STP to route messages, instead of requiring the MSC to
store all enhanced Control Server (eCS) codes.
......................................................................................................................................................................................................
HCF
HLR Control Function

A USDS subsystem that provides the service logic for call processing and network
communications.
HDF
HLR Data Function

A USDS subsystem responsible for the retrieval and storage of data for call
processing and provisioning.
HLR
Home Location Register

A permanent database used in mobile systems to identify subscribers and to contain
subscriber data related to features and services. Specifically for USDS this
includes:
(1) Subscriber data
(2) Global service data (parameters applicable to all subscribers handled by the
HLR)
(3) Global system data (parameters applicable to the operation of HLR)
...........................................................................................................................................................................................................................................................
270-710-919R6.0

GLOSSARY
GL-7
(4) Service profile.

HSS
Home Subscriber Server

A master database in IMS network to identify subscribers and to contain subscriber
service related data to support CSCF/AS to handle calls/sessions.
The data in database includes:
(1) Subscriber data (identification and Service profile)
(2) Global service data (parameters applicable to all subscribers handled by the
HSS)
(3) Global system data (parameters applicable to the operation of HSS)
......................................................................................................................................................................................................
I-CSCF
Interrogation Call Session Control Function

A Network Element in IMS network, used for assigning S-CSCF for user, and as
gateway/firewall functionality.
IMS
IP Multimedia Subsystem
An IP multimedia and telephony core network. It is defined by 3GPP standards
organizations and based on the IETF protocol (SIP/Diameter). IMS can support IP
to IP sessions over wireline IP, 802.11, 802.16, CDMA packet data, GSM/EDGE/
UMTS packet data and have standardized interfaces between applications, network
layers, and back-office systems. It is essentially access independent.
IMSI
International Mobile Station Identity

An international identifier that permits mobile stations to roam among public
mobile networks located in different countries.
IN
Intelligent Network
The capability in a public telecom network that allows new services to be
developed quickly and introduced on any scale.
Init
In recovery terminology, the state of a system when it is initializing. Upon

successful completion of the initialization, the processor transitions to the
standby state.
IP
Internet Protocol
A data protocol used in the Internet.
ITU-T
...........................................................................................................................................................................................................................................................
GLOSSARY
GL-8

270-710-919R6.0
International Telecommunications Union - Telecom

The ITU Telecommunications Standardization Sector (ITU-T) is responsible for
studying technical and operating questions and issuing recommendations with a
view to standardizing worldwide telecommunications.
......................................................................................................................................................................................................
LMSI
Local Mobile Station Identity

A subscriber identifying number the VLR can create and use to speed up the search
for subscriber data. LMSI is dynamically updated from VLR, stored in
HDF_UMTS_SUB.
......................................................................................................................................................................................................
MAP
Mobile Application Part

Part of the SS7 protocol used in GSM. MAP standards address registration of
roamers and intersystem hand-off procedures.
MAS
MiLife Application Server

The MiLife Application Server is a leading technology edge Application Server for
hosting services at a highest reliability and efficiency.
MDN
Mobile Directory Number

A number identifying a subscribers mobile; currently the same as the MIN.
MIN
Mobile Identification Number

A 10-digit number identifying a subscribers mobile.
MSC
Mobile Switching Center

A switch providing services and co-ordination between mobile users in a
mobile network and external networks.
MSGH
Message Handler
An internal communication mechanism,
communication capability for all processes.
which
provides
the
message
MSISDN
Mobile Station ISDN Number

A number assigned to a mobile subscriber; optionally, one per teleservice and one
...........................................................................................................................................................................................................................................................
270-710-919R6.0

GLOSSARY
GL-9
per bearer service assigned to the subscriber.

Mean Throughput Class
Specifies the average rate at which data is expected to transfer across the GPRS
network.
......................................................................................................................................................................................................
NAM
Network Access Mode

Defines if a subscriber is allowed access to the GPRS network, non-GPRS
network, or both networks.
......................................................................................................................................................................................................
Off-line
In recovery terminology, the state of a system during maintenance. Only the

operating system is running and any HA SW processes controlled by UNIX
initialization are not running in this state.
......................................................................................................................................................................................................
PLMN
Public Land Mobile Network

A mobile network established to provide services.
Peak Throughput Class
Specifies the maximum rate at which data is expected to transfer across the GPRS
network.
Precedence Class
Indicates the relative importance of maintaining service commitments under

abnormal conditions.
......................................................................................................................................................................................................
Quality of Service
The collective effect of service performance which determine the degree of

satisfaction of a user of a service. It is characterised by the combined aspects of
performance factors applicable to all services such as:
Service operability performance
Service accessibility performance
Service retainablity performance
Service integrity performance
Other factors specific to each service.

......................................................................................................................................................................................................
RADIUS
Remote Authentication Dial In User Service

...........................................................................................................................................................................................................................................................
GLOSSARY
GL-10

270-710-919R6.0
Used in mobile networks to authenticate authorized users.

RAN
Radio Access Network

The portion of a mobile network that handles subscriber access, including radio
base stations and concentration nodes.
Redundant Component
Reliability ensuring logical entity with mated pair architecture that gives an
active/active or active/standby architecture.
Reliability Class
Defines the probability of loss of, duplication of, or corruption of PDUs.

RNC
Radio Network Controller

Manages the radio part of the network in UMTS.
Roaming
The ability of a user to access wireless telecommunication services in areas other

than the one(s) where the user is subscribed.
......................................................................................................................................................................................................
SGSN
Serving GPRS Support Node

The SGSN handles the data traffic of users in a geographical service area and is one
of the two types of nodes implemented in a GPRS environment.
Shutdown
In recovery terminology, shutdown is a general term that refers to a manual

action to stop normal process execution and invoke process termination
routines. The resources are relinquished upon termination of the process as
part of the termination procedure.
SMS
Short Message Service

Mobile-to-mobile text messaging in GSM.
SMS-C
Short Message Service Center

Handles management of incoming and outgoing SMS.
Software Update
An update procedure to either platform software or application software, while
...........................................................................................................................................................................................................................................................
270-710-919R6.0

GLOSSARY
GL-11
taking one component of USDS out of service at a time.

SPA
Service Package Application

An executable software module that implements a specific service.
SS7
Signaling System No. 7

The primary interface with customer network elements is via SS7 and each USDS
is a signaling point in the wireless operators network.
SSP
Service Switching Point

A switch that supports the intelligent network protocols and call processing
capabilities.
Standby
In recovery terminology, a state that applies to the system and application

instances. Services are not provided by elements in the "standby" state.
STP
Signal Transfer Point

An intelligent network packet switch that provides the Signalling System 7 (SS7)
network protocol, internet work gateway capabilities, and network surveillance
and maintenance to an intelligent network.
Subscriber
A person or other entity that has a contractual relationship with a service provider
on behalf of one or more users.
Service provider
A person or other entity that has the overall responsibility to provide service(s) to
the users and for negotiating network capabilities associated with the services(s)
provided.
Switchover
In recovery terminology, switchover is a general term that refers to a manual action

to restart an application or switch only that application over to a backup system as
a result of a maintenance operation.
......................................................................................................................................................................................................
TCAP
Transaction Capabilities Application Part. An application-level protocol that in

ANS networks is used as a carrier protocol for the SS7 and X.25 network protocols.
...........................................................................................................................................................................................................................................................
GLOSSARY
GL-12

270-710-919R6.0
TCP/IP
Transmission Control Protocol/Internet Protocol

Usually abbreviated to IP, the 'language' used by the Internet.
TDMA
Time Division Multiple Access

A digital radio technique that divides radio spectrum between users using
"timeslots", rather than (only) frequency separation or codes, used in GSM and
TDMA (IS-136) mobile networks. TDMA is also the term used to describe the
digital enhancement of the AMPS analog standard, formerly known as D-AMPS
(Digital Advanced Multiple Access).
Teleservice
A type of telecommunication service that provides the complete capability,

including terminal equipment functions, for communication between users
according to standardized protocols and transmission capabilities established by
agreement between operators.
......................................................................................................................................................................................................
UMTS
Universal Mobile Telecommunications System

A 3G standard being developed under the auspices of ETSI, and intended mainly
for the evolution of GSM networks.
Unavailable
In recovery terminology, the state of an system, application service or resource

when it is not able to provide service. The processor/server is "unavailable" when
it is powered down due to an autonomous fault or due to a manual request. An
application or resource is "unavailable" when it is NOT running due to a fault
condition.
User-level DN or address
Directory number or address assigned to a user, not to a terminal. This DN could

also belong to some terminal of a user, but for the purpose of call delivery, it is
assigned to a user. A destination address, such as directory number or SIP URL,
has always been assigned to a certain protocol, Protocol A in our definition. Userlevel DN is the DN, which still belongs to Protocol A, but is interpreted as a user
address or a personal address. This is possible since a terminal can have assigned
more than one address, one of which can be used as a user address.
......................................................................................................................................................................................................
VLR
Visitor Location Register

In a cellular telecommunications system, an account that a service provider creates
...........................................................................................................................................................................................................................................................
270-710-919R6.0

GLOSSARY
GL-13
for other service providers within the same Service Package Application (SPA).
......................................................................................................................................................................................................
WIN
Wireless Intelligent Networking

A TIA standard for ANSI-41 networks that enhances the provisioning of IN
(Intelligent Network) services.
...........................................................................................................................................................................................................................................................
GLOSSARY
GL-14

270-710-919R6.0
Index
.............................................................................
AAA Accounting in USDS,

11-6
AAA Retrieve Template, B79
About, v-xxi
Access SMT through LMT,

11-3
Configure RC/V form access

permissions, 3-60
Assign Form Permissions to

Restricted RC/V Logins for
CALEA, 9-4
Configure the severity level

for OMLogs, 4-42
Back up HDF TimesTen

database to disk, tape/DVD,
3-6
Back up USDS system, 2-19
Administering User
Accounts on MAS, eSM,
and OMC-H, 1-2
Backup HDF TimesTen

Database to Tape or Disk,
3-6
Administrative interfaces for

USDS OA&M tasks, 1-1
Backup MASs, 2-19
ANSI Authentication, B-24

ANSI Call Delivery, B-41
CALEA introduction, 9-2
ANSI Default Scenarios, B59
CALEA service report, 8-2
ANSI Short Message, B-57

ANSI Subscriber Data
Management, B-55
ANSI Supplementary
Service, B-53
Customer preference impact

on HDF state transition, 217
.............................................................................
CANCEL
MAP (UMTS), 4-21
Data replication between

mated HDF pair, 2-11
Definition, 5-22
DEREG
PRID, HOST (HSS), 427
Determine the status of
USDS SPAs, 2-24
.............................................................................
CALEA delivery function

connection test, 4-25
ANSI Location
Management, B-37
Custom report, 8-1
.............................................................................
Access SPA-related data

from MAS nodes, 3-14
Alarm Message Sources, 518, 5-20
Create USDS measurement

reports on eSM, 7-15
Assign Form Permissions to

Restricted WPS Logins, 361
About this Document, v-xxi

Access MAS administrative
interfaces, 1-10
Area Code Split Exchange

Diskette (ACSED), 10-4
Disaster Recovery for a HDF

pair, 3-26
.............................................................................
Enable or disable
measurement pegging, 7-5
Collection Intervals, 7-3
Error Messages, 5-26
Configure IPSec keys

between USDS and LTDU,
9-9
eSM Measurement
Aggregation, 7-11
Configure IPSec policies

9-13
eSM Measurement Data

Reports, 7-11
Event Messages, 5-26
............................................................................................................................................................................................................................................................
270-710-919R6.0

I N D E X
I N - I
Execute load balancing from

eSM, 3-37
.............................................................................
.............................................................................
Index server full init-peer

pump, 3-58
Generate custom report on

eSM, 8-4
HCF and HDF

Communications, 2-4
Input and Output Messages,

4-1
HCF Index Server, B-22
Input Message, 4-5
HCF service measurement

sets - AAA, A-108
Introduction to USDS service

measurements, 7-2
HCF Service Measurement

Sets - ANSI, A-8
Logging, 7-3
Logs / Alarms of VitalAAA
server on USDS, 11-8

sets - SMPP, A-109
HDF measurement sets HSS, A-149

HDF measurements for
performance monitoring, 79
HDF service measurement
sets - ANSI, A-114
sets - Common, A-110
sets - UMTS, A-129
HSS Authentication, B-73
.............................................................................
Managing the USDS

databases, 3-1
Managing USDS, 2-1
Modify measurements
polling on eSM, 7-12
Monitor Alarms with "tailer"
Command, 5-20
Monitor SS7 DAPs, 6-3
Monitoring Alarms, 5-8
Monitoring Error and Event
Messages, 5-26
Monitoring SS7 links in
R3.0,6-2, 6-2
HSS Call Handling, B-75
Monitoring the SS7 links, 61
HSS Feature Lock, B-74
Monitoring USDS, 5-1
HSS Overload, B-72
.............................................................................
Monitoring USDS messages,

5-2
Output Message, 4-31
.............................................................................
Performance estimates for

split NPA tool, 10-8
Primary HDF Status, 2-9
Load Balancing
Introduction, 3-27
Log File Organization, 5-2

sets - HSS, A-100
newNPANXXRangeFile file,
10-5
NPA split tool tasks, 10-9
Procedure Assumptions, 522
Locate and Clear USDS

Alarms at DAP, 5-16

sets - Common, A-3
HDF measurement, B-21
.............................................................................

sets - CALEA, A-94
HCF Service Measurement

Sets - UMTS, A-59
.............................................................................
Index server introduction, 354
.............................................................................
Index server full init- HDF

pump, 3-56
Monitoring USDS overload,

5-27
Procedure References, 5-16

.............................................................................
RECOVER
MAP (UMTS), 4-22
Recover, 3-12
Recover a Subset of HDF
TimesTen Database from
eSM, 3-12
Recover a subset of HDF
TimesTen Database from
eSM, 3-12
Recover a subset of HDF
TimesTen database from
eSM, 3-12
Recover HDF TimesTen
Database from Mated HDF
Node, 3-8
Database from Tape or
Disk, 3-10
database from tape or disk,
3-10
Recover the USDS system,
2-21
Redirect Omlogs, 4-35
.........................................................................................................................................................................................................................................................
I N D E X
I N - I I

270-710-919R6.0
Related Procedure, 5-17
Unique Challenge (ANSI),

4-17
Re-lock the USDS features

from the eSM, 3-51
USDS data introduction, 3-3
Remove IPSec connection

9-18
USDS eSM measurement

reports, 7-11
USDS user accounts on the

eSM, 1-5
MAS, 1-4
.............................................................................
Saving Log Files, 5-3

Searching Log Files, 5-2

OMC-H, 1-7
Send command from the

eSM GUI, 4-6
Using AAA, 11-1

Using CALEA, 9-1
SMPP specified, B-80
Using MAS administrative

interfaces, 1-8
Split NPA tool installation,

10-11
Using Service
Measurements, 7-1, 9-1,
10-1
SS7 Links, 6-2

SSD Update (ANSI), 4-15
Start the USDS SPAs, 2-26
Stop the USDS SPAs, 2-31
Using split NPA tool for

ANSI, 10-1
Subscriber Number Report

(ANSI/UMTS), 4-24
Using split NPA tool on eSM,

10-12
System Integrity, B-3
Using split NPA tool on

MAS, 10-13
.............................................................................
Using UMTS AuC/HSS

APIs, C-1
tailer a Log File, 5-20
USS Servers on USDS, 11-9
Technician Initiated VLR

Delete (ANSI), 4-20
Timestamp update (UMTS),

4-29
.............................................................................
UMTS Authentication, B-69

UMTS CAMEL, B-71
UMTS Framework, B-68
WPS service report, 8-3
USDS SPAs, 2-2
Run load balancing removal

tool, 3-47
Technician Initiated VLR

Refresh (ANSI), 4-19
USDS service
measurements, A-1
Resolve recurring USDS

SPA alarms, 5-22
.............................................................................
USDS NPA data, 10-6
Reports, 7-3
View Output Message, 4-52
UTMS authentication
overview, C-3
.............................................................................
Verify LTDU connection

with USDS from eSM, 9-7
View Alarms in Log File, 518
View alarms in Log File, 518
View Log File Alarm
Messages, 5-18
...........................................................................................................................................................................................................................................................
270-710-919R6.0

I N D E X
I N - I I I
.........................................................................................................................................................................................................................................................
I N D E X
I N - I V

270-710-919R6.0

Usds Oam Guide

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Usds Oam Guide

Загружено:

Авторское право:

Доступные форматы

Wireless Intelligent Network (IN)

Unified Subscriber Data Server (USDS) R6.0

Mandatory customer information

Adobe Acrobat is a trademark of Adobe Systems, Inc.

Lucent Technologies - Proprietary

Administrative interfaces for USDS OA&M tasks

USDS user accounts on the MAS

USDS user accounts on the eSM

USDS user accounts on the OMC-H

Using MAS administrative interfaces

Procedure: Access the MAS administrative interfaces

Managing the USDS

HCF and HDF communications

Primary HDF status

Data replication between mated HDF pair

Customer preference impact on HDF state transition

Procedure: Back up USDS system

Procedure: Recover the USDS system

Procedure: Determine the status of USDS SPAs

Procedure: Start the USDS SPAs

Procedure: Stop the USDS SPAs

Managing the USDS databases

Procedure: Back up HDF TimesTen database to disk, tape/DVD

Procedure: Recover the HDF TimesTen database from tape or disk

Procedure: Recover a subset of HDF TimesTen database from eSM

Procedure: Access SPA-related data from MAS nodes

Procedure: Disaster recovery for a HDF pair

Lucent Technologies - Proprietary

Load balancing introduction

Procedure: Execute load balancing from eSM

Procedure: Run load balancing removal tool

Procedure: Re-lock the USDS features from the eSM

Index server introduction

Procedure: Index server full init- HDF pump

Procedure: Index server full init-peer pump

Procedure: Configure RC/V form access permissions

Procedure: Assign Form Permissions to Restricted WPS Logins

Input and Output messages

Procedure: Send command from the eSM GUI

FULLINIT:IS [, CLEANUP |, DFPUMP | CF=a [, UCL]]

SSD update (ANSI)

Unique challenge (ANSI)

Technician initiated VLR refresh (ANSI)

Technician initiated VLR delete (ANSI)

CANCEL: MAP (UMTS)

RECOVER: MAP (UMTS)

Subscriber Number Report (ANSI/UMTS)

CALEA delivery function connection test

DEREG: PRID, HOST (HSS)

Timestamp update (UMTS)

Procedure: Redirect Omlogs

Procedure: Configure the severity level for OMLogs

Procedure: View output message

Procedure: Locate and clear USDS alarms at DAP

Procedure: View alarms in log file

Lucent Technologies - Proprietary

Procedure: Monitor alarms with "tailer" command

Procedure: Resolve recurring USDS SPA alarms

Monitoring error and event messages

Monitoring USDS overload

Monitoring the SS7 Links

Procedure: Monitor SS7 DAPs

Using service measurements