Oracle Communications EAGLE · Oracle® Communications EAGLE EIR User's Guide E54351-01 Revision A July 2014

Oracle® CommunicationsEAGLEEIR User's Guide

E54351-01 Revision A

July 2014

Oracle® Communications EIR User's GuideCopyright © 1993, 2014,

Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictionson use and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free.If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing iton behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,any programs installed on the hardware, and/or documentation, delivered to U.S. Government end usersare "commercial computer software" pursuant to the applicable Federal Acquisition Regulation andagency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptationof the programs, including any operating system, integrated software, any programs installed on thehardware, and/or documentation, shall be subject to license terms and license restrictions applicable to theprograms. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applicationsthat may create a risk of personal injury. If you use this software or hardware in dangerous applications,then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures toensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused byuse of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarksof their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarksare used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of AdvancedMicro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services. OracleCorporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to youraccess to or use of third-party content, products, or services.

Table of Contents

Chapter 1: Introduction ................................................................................8Overview.................................................................................................................................................9Scope and Audience..............................................................................................................................9Manual Organization.............................................................................................................................9Documentation Admonishments.......................................................................................................10My Oracle Support (MOS)..................................................................................................................10Emergency Response...........................................................................................................................11Related Publications............................................................................................................................11Documentation Availability, Packaging, and Updates..................................................................11Locate Product Documentation on the Oracle Technology Network Site...................................12

Chapter 2: Feature Description..................................................................13Equipment Identity Register Overview............................................................................................14EIR Call Flows......................................................................................................................................15

EIR List Determination............................................................................................................18EIR Protocol..........................................................................................................................................19

Check_IMEI Message Handling............................................................................................20EIR List Log File...................................................................................................................................21Additional EIR Data Files...................................................................................................................22EIR S13/S13' Interface Support..........................................................................................................23

EIR S13 Connection States......................................................................................................24S13 Supported Messages.........................................................................................................26S13 Supported AVPs................................................................................................................27EIR S13/S13' Interface Support - ECA Message Encoding................................................29EIR S13/S13' Interface Support Result Codes......................................................................30

Hardware Requirements.....................................................................................................................31MPS/EPAP Platform...........................................................................................................................32

Chapter 3: EAGLE EIR Commands..........................................................33EAGLE 5 Commands for EIR.............................................................................................................34

EAGLE 5 EIR GSM Options Commands..............................................................................34EAGLE 5 EIR Service Selector Commands...........................................................................37EAGLE 5 Feature Control Commands..................................................................................38

iiiE54351-01 Revision A, July 2014

EIR S13/S13' Interface Support Commands........................................................................38

Chapter 4: EIR Configuration....................................................................43Introduction..........................................................................................................................................44EPAP Entity Provisioning...................................................................................................................44System Prerequisites............................................................................................................................44EIR Feature Prerequisites....................................................................................................................45EIR Configuration Procedure.............................................................................................................46Enabling and Turning On the EIR Feature.......................................................................................47Provisioning the EIR Local Subsystem.............................................................................................48

Adding the EIR Subsystem Application...............................................................................48Removing the EIR Subsystem Application..........................................................................49

Changing the State of a Subsystem Application.............................................................................50Taking the Subsystem Application Online...........................................................................51Taking the Subsystem Application Offline..........................................................................52

Provisioning the EIR Service Selectors..............................................................................................53Adding an EIR Service Selector..............................................................................................53Removing a Service Selector...................................................................................................54Changing an Existing Non-EIR Service Selector to an EIR Service Selector...................55

Changing the EIR Options..................................................................................................................56Configuring EIR S13/S13’ Interface Support...................................................................................57Activating the EIR Local Subsystem.................................................................................................58

Chapter 5: EIR Measurements...................................................................60EIR Measurements...............................................................................................................................61

Chapter 6: Maintenance..............................................................................64EIR Alarms............................................................................................................................................65EIR UIMs...............................................................................................................................................66Maintenance Commands....................................................................................................................70

rept-stat-sccp.............................................................................................................................71EAGLE 5 ISS Debug Commands.......................................................................................................71Status Reporting and Problem Identification...................................................................................72

EPAP Status and Alarm Reporting........................................................................................74Glossary...............................................................................................................................76

ivE54351-01 Revision A, July 2014

List of Figures

Figure 1: EIR Call Flow....................................................................................................................................16

vE54351-01 Revision A, July 2014

List of Tables

Table 1: Admonishments................................................................................................................................10

Table 2: Example of Individual IMEIs...........................................................................................................16

Table 3: Logic for IMEIs in Multiple Lists....................................................................................................17

Table 4: Additional Files.................................................................................................................................22

Table 5: S13 State..............................................................................................................................................24

Table 6: S13 Event and State Transition Table.............................................................................................25

Table 7: S13 Messages supported by Eagle 5...............................................................................................26

Table 8: AVPs Supported by S13....................................................................................................................27

Table 9: Mapping of EIR database Response and ECR Result..................................................................30

Table 10: Supported Result Codes.................................................................................................................30

Table 11: Commands used for EIR................................................................................................................34

Table 12: GSMOPTS Options for EIR............................................................................................................34

Table 13: Individual IMEI List Determination.............................................................................................35

Table 14: Commands for EIR S13/S13' Interface Support feature............................................................38

Table 15: Table DEIROPTS options...............................................................................................................39

Table 16: Table DCONN options...................................................................................................................40

Table 17: REPT-STAT-DEIR Pegs..................................................................................................................42

Table 18: System Prerequisites.......................................................................................................................44

Table 19: EIR Feature Prerequisite.................................................................................................................45

Table 20: EIR Local Subsystem Prerequisites...............................................................................................48

Table 21: Subsystem Allow/Inhibit...............................................................................................................58

Table 22: Pegs for Per System EIR Measurements......................................................................................61

viE54351-01 Revision A, July 2014

Table 23: EIR S13/S13' Interface Support Measurement Registers...........................................................62

Table 24: DEIR Measurement Reports..........................................................................................................63

Table 25: EIR UAMs.........................................................................................................................................65

Table 26: EIR UIMs...........................................................................................................................................66

Table 27: UIM format for EIR S13/S13' Support Feature...........................................................................68

Table 28: Maintenance Commands................................................................................................................70

Table 29: Status Reporting for EPAP-Related Features..............................................................................72

viiE54351-01 Revision A, July 2014

Chapter

1Introduction

This chapter provides a brief description of the EIRfeature of the Oracle Communications EAGLE. The

Topics:

• Overview.....9 chapter also includes the scope, audience, and• Scope and Audience.....9 organization of the manual; how to find related

publications; and how to contact Oracle forassistance.

• Manual Organization.....9• Documentation Admonishments.....10• My Oracle Support (MOS).....10• Emergency Response.....11• Related Publications.....11• Documentation Availability, Packaging, and

Updates.....11• Locate Product Documentation on the Oracle

Technology Network Site.....12

8E54351-01 Revision A, July 2014

Overview

This manual describes the Equipment Identity Register (EIR) feature of Oracle CommunicationsEAGLE. The EIR feature is used to reduce the number of GSM mobile handset thefts by providing amechanism to assist network operators in preventing stolen or disallowed handsets from accessingthe network. This control is accomplished by comparing the International Mobile Equipment Identity(IMEI) that is provided during handset registration to a set of three lists provided by the networkoperator:

• Black - Mobile Stations (MS) on the Blacklist will be denied access to the network• White - MSs on the Whitelist will be allowed access to the network• Gray - MSs on the Graylist will be allowed on the network, but may be tracked

EIR is an optional feature on EAGLE, and can be turned on but not off after the feature is enabledusing a feature access key. EIR is mutually exclusive with LNP in the system, unless the Dual ExAPConfiguration feature is enabled.

Scope and Audience

This manual is intended for anyone responsible for installing, maintaining, and using the EIR featureon Oracle Communications EAGLE. Users of this manual and the others in the EAGLE family ofdocuments must have a working knowledge of telecommunications and network installations.

Manual Organization

This document is organized into the following chapters:

• Introduction contains general information about the EIR documentation, the organization of thismanual, and how to get technical assistance.

• Feature Description provides a functional description of the EIR feature, including networkperspectives, assumptions and limitations, a database overview, Service Module card provisioningand reloading, EIR user interface, and an audit overview.

• EAGLE EIR Commands describes the EAGLE commands that can be used for EIR featureconfiguration functions.

• EIR Configuration provides procedures for configuring the EIR feature for use in EAGLE.

• EIR Measurements describes EIR-related measurements, measurements reports, and methods ofcollection.

• Maintenance describes EIR-related UAMs and UIMs, commands that can be used for maintenancefunctions; and status and alarm reporting for EAGLE, Oracle Communications EAGLE ApplicationProcessor Provisioning (EPAP), Service Module cards, services, and the local subsystem.


IntroductionEIR User's Guide

Documentation Admonishments

Admonishments are icons and text throughout this manual that alert the reader to assure personalsafety, to minimize possible service interruptions, and to warn of the potential for equipment damage.

Table 1: Admonishments

DescriptionIcon

Danger:

(This icon and text indicate the possibility ofpersonal injury.)

Warning:

(This icon and text indicate the possibility ofequipment damage.)

Caution:

(This icon and text indicate the possibility ofservice interruption.)

Topple:

(This icon and text indicate the possibility ofpersonal injury and equipment damage.)

My Oracle Support (MOS)

MOS (https://support.oracle.com) is your initial point of contact for all product support and trainingneeds. A representative at Customer Access Support (CAS) can assist you with MOS registration.

Call the CAS main number at 1-800-223-1711 (toll-free in the US), or call the Oracle Support hotlinefor your local country from the list at http://www.oracle.com/us/support/contact/index.html. When calling,make the selections in the sequence shown below on the Support telephone menu:

1. Select 2 for New Service Request2. Select 3 for Hardware, Networking and Solaris Operating System Support3. Select 2 for Non-technical issue

You will be connected to a live agent who can assist you with MOS registration and provide SupportIdentifiers. Simply mention you are a Tekelec Customer new to MOS.

MOS is available 24 hours a day, 7 days a week, 365 days a year.



https://support.oracle.com

http://www.oracle.com/us/support/contact/index.html

Emergency Response

In the event of a critical service situation, emergency response is offered by the Customer AccessSupport (CAS) main number at 1-800-223-1711 (toll-free in the US), or by calling the Oracle Supporthotline for your local country from the list at http://www.oracle.com/us/support/contact/index.html. Theemergency response provides immediate coverage, automatic escalation, and other features to ensurethat the critical situation is resolved as rapidly as possible.

A critical situation is defined as a problem with the installed equipment that severely affects service,traffic, or maintenance capabilities, and requires immediate corrective action. Critical situations affectservice and/or system operation resulting in one or several of these situations:

• A total system failure that results in loss of all transaction processing capability• Significant reduction in system capacity or traffic handling capability• Loss of the system’s ability to perform automatic system reconfiguration• Inability to restart a processor or the system• Corruption of system databases that requires service affecting corrective actions• Loss of access for maintenance or recovery operations• Loss of the system ability to provide any required critical or major trouble notification

Any other problem severely affecting service, capacity/traffic, billing, and maintenance capabilitiesmay be defined as critical by prior discussion and agreement with Oracle.

Related Publications

For information about additional publications that are related to this document, refer to the RelatedPublications Reference document, which is published as a separate document on the Oracle TechnologyNetwork (OTN) site. See Locate Product Documentation on the Oracle Technology Network Site for moreinformation.

Documentation Availability, Packaging, and Updates

Tekelec provides documentation with each system and in accordance with contractual agreements.For General Availability (GA) releases, Tekelec publishes a complete EAGLE 5 ISS documentation set.For Limited Availability (LA) releases, Tekelec may publish a documentation subset tailored to specificfeature content or hardware requirements. Documentation Bulletins announce a new or updatedrelease.

The Tekelec EAGLE 5 ISS documentation set is released on an optical disc. This format allows for easysearches through all parts of the documentation set.

The electronic file of each manual is also available from the Tekelec Customer Support site. This siteallows for 24-hour access to the most up-to-date documentation, including the latest versions of FeatureNotices.



http://www.oracle.com/us/support/contact/index.html

https://secure.tekelec.com/OA_HTML/ibuhpage.jsp

Printed documentation is available for GA releases on request only and with a lead time of six weeks.The printed documentation set includes pocket guides for commands and alarms. Pocket guides mayalso be ordered separately. Exceptions to printed documentation are:

• Hardware or Installation manuals are printed without the linked attachments found in the electronicversion of the manuals.

• The Release Notice is available only on the Customer Support site.

Note: Customers may print a reasonable number of each manual for their own use.

Documentation is updated when significant changes are made that affect system operation. Updatesresulting from Severity 1 and 2 Problem Reports (PRs) are made to existing manuals. Other changesare included in the documentation for the next scheduled release. Updates are made by re-issuing anelectronic file to the customer support site. Customers with printed documentation should contacttheir Sales Representative for an addendum. Occasionally, changes are communicated first with aDocumentation Bulletin to provide customers with an advanced notice of the issue until officiallyreleased in the documentation. Documentation Bulletins are posted on the Customer Support site andcan be viewed per product and release.

Locate Product Documentation on the Oracle Technology Network Site

Oracle customer documentation is available on the web at the Oracle Technology Network (OTN)site, http://docs.oracle.com. You do not have to register to access these documents. Viewing these filesrequires Adobe Acrobat Reader, which can be downloaded at www.adobe.com.

1. Log into the Oracle Technology Network site at http://docs.oracle.com.2. Under Applications, click the link for Communications.

The Oracle Communications Documentation window opens with Tekelec shown near the top.3. Click Oracle Communications Documentation for Tekelec Products.4. Navigate to your Product and then the Release Number, and click the View link (the Download

link will retrieve the entire documentation set).5. To download a file to your location, right-click the PDF link and select Save Target As.



http://docs.oracle.com

http://www.adobe.com

http://docs.oracle.com

Chapter

2Feature Description

This chapter provides a functional description ofthe EIR feature, including network perspectives,

Topics:

• Equipment Identity Register Overview.....14 assumptions and limitations, a database overview,• EIR Call Flows.....15 Service Module card provisioning and reloading,

EIR user interface, and an audit overview.• EIR Protocol.....19• EIR List Log File.....21• Additional EIR Data Files.....22• EIR S13/S13' Interface Support.....23• Hardware Requirements.....31• MPS/EPAP Platform.....32


Equipment Identity Register Overview

A handset theft problem exists in GSM networks in many countries. A person obtains a legitimatesubscription to a network, and then obtains a legitimate IMSI, MSISDN, and SIM card. The personinitially buys an inexpensive handset and then steals a better handset from another subscriber. Afterthe handset is stolen, the thief replaces the SIM card with a legitimate SIM card. Because the SIM cardand subscriber information contained on the SIM card (IMSI, MSISDN) are legitimate, the phone willoperate and the network operator cannot determine that the subscriber is using a stolen handset. Inaddition to individual handset theft, organized groups stealing entire shipments of mobile handsetsfrom warehouses and sell these handsets on the Black Market.

The Equipment Identity Register (EIR) is a network entity used in GSM networks that stores lists ofIMEI numbers, which correspond to physical handsets (not subscribers). The IMEI is used to identifythe actual handset, and is not dependent upon the International Mobile Subscriber Identity (IMSI),Mobile Station International ISDN Number (MSISDN), or the Subscriber Identity Module (SIM). TheIMSI, MSISDN, and SIM are all subscriber-specific, and move with the subscriber when purchasinga new handset. The IMEI is handset-specific.

The EIR feature can be used to reduce the number of GSM mobile handset thefts by providing amechanism that allows network operators to prevent stolen or disallowed handsets from accessingthe network. This control is accomplished by comparing the International Mobile Equipment Identity(IMEI) that is provided during handset registration to the following set of three lists provided by thenetwork operator:

• Black - Mobile Stations (MS) on the Blacklist are denied access to the network

• Gray - MSs on the Graylist are allowed on the network, but may be tracked

• White - MSs on the Whitelist are allowed access to the network

The EPAP Real Time Database (RTDB) stores the Whitelist, Graylist, and Blacklist of IMEI numbers.The RTDB is downloaded to Service Module cards in EAGLE. When a subscriber roams to a new MSCor VLR location, the handset attempts registration with the MSC or VLR. Before the MSC registers thesubscriber with the VLR, it may send a query to the EAGLE for EIR status of the handset. EAGLEreturns a response indicating whether the IMEI is allowed, disallowed, or not valid. If the IMEI isallowed, the MSC completes registration; otherwise, registration is rejected.

The RTDB may also contain associations between individual IMEIs and IMSIs. This can provide afurther level of screening by directly associating a particular IMEI with a particular IMSI. Thisassociation is used in the following way:

• If an IMEI is found on a Blacklist, an additional check of the IMSI could then be made.

• If the IMSI from the handset matches the IMSI provisioned with the IMEI, this would override theBlacklist condition, and allow registration to continue. This could be used to protect against mistakenBlacklist entries in the database, or to prevent unauthorized "handset sharing". This associationcould also be used in other ways.

The IMSI Range Logic Support feature includes an IMSI range check logic prior to an IMEI lookup inthe database. This check prevents low ARPU users from using certain devices, in addition to the EIRstolen handset check.

The EIR feature is mutually exclusive with LNP, unless the Dual ExAP Configuration feature is enabled.


Feature DescriptionEIR User's Guide

EIR Call Flows

When a handset roams into a new MSC/VLR area, it attempts a registration procedure with the VLR.In a network without the EIR function, this procedure results in the VLR sending a location updatemessage to the HLR, providing the HLR with the current MSC location of the Mobile Station(MS)/handset. When the EIR function is deployed in a network, this registration procedure isinterrupted in order to validate the IMEI of the MS/handset attempting to register before completingthe registration procedure and updating the HLR.

In the network with EIR, the MSC/VLR sends a MAP_CHECK_IMEI message to the EAGLE 5requesting EIR processing before sending a location update to the HLR. This message contains, at aminimum, the IMEI of the MS attempting registration. It may also contain the IMSI of the subscriberwhose SIM card is currently being used in the MS/handset. Upon receipt of this message, the EIRfeature searches the White, Gray, and Black Lists for a match on the IMEI. The EIR feature then returnsa response to the MSC. Depending upon the result of the search, the response contains either theEquipment Status of the MS/handset (whether the IMEI for the MS/handset is allowed or not, basedon its status in the White, Gray, or Black Lists), or a User Error (invalid or unknown IMEI). The MSCthen either continues the registration procedure (if the IMEI is allowed), or rejects it (if the IMEI isdisallowed, invalid, or unknown).

If the IMSI is also included in the message, EIR attempts to match this IMSI to one provisioned withthe IMEI before sending a response to the MSC. A match on IMSI in this case overrides any Black Listcondition found based on the IMEI match alone, and causes a response of MS allowed.

Figure 1: EIR Call Flow illustrates the steps of the following EAGLE 5 EIR call flow process.

1. The MS/handset roams into a new serving MSC/VLR area, and begins the registration procedurewith the Base Station (BS).

2. The BS begins the registration procedure with MSC/VLR.

3. Before allowing the MS/handset to register on the network, and before updating the HLR withthe new MSC information, the MSC launches a MAP_CHECK_IMEI message to the EAGLE 5 forEIR feature processing. This message is either MTP-routed directly to the point code of the EAGLE5 and the EIR local subsystem, or is GT-routed and the EAGLE 5 performs global title translationon the message to its own point code and the EIR local subsystem.

4. EIR retrieves the IMEI and/or IMSI from the message and searches the EIR information in theRTDB for a match. See Table 2: Example of Individual IMEIs and Table 3: Logic for IMEIs in MultipleLists. This search may result in the IMEI being on one or more of the White, Gray, or Black Lists,or it may result in an invalid or unknown IMEI (no match). It may also result in an invalid IMSI-IMEIcombination. Based on the results of the search, the EAGLE 5 returns a MAP_CHECK_IMEI_ackcontaining either the Equipment Status (IMEI allowed or not allowed), or a User Error (invalid orunknown IMEI).

5. (Not shown). The MSC either rejects or completes the registration attempt, depending on theinformation returned from EIR.



Figure 1: EIR Call Flow

The RTDB EIR information contains lists of IMEIs, and an indication as to the list where they arelocated. There are two types of IMEIs: Individual IMEIs (Table 2: Example of Individual IMEIs) andranges of IMEIs (Table 3: Logic for IMEIs in Multiple Lists). The Individual IMEIs are searched first. TheIMEI entries in this list may also contain an association to an IMSI. If no individual IMEI match isfound, IMEI ranges are searched.

EIR can support up to 32 million individual IMEIs. A total of up to 100,000 IMEI ranges are supported.The maximum EAGLE 5 RTDB capacity for all EPAP service features, including EIR, G-Flex, andG-Port, is 120 million individual numbers. Entries for these other services (MSISDNs for G-Port orIMSIs for G-Flex), reduce the available capacity for IMEIs. Also, if IMSIs are entered for the IMSI Checkoption of EIR, those entries will also reduce the available IMEI capacity.

Note:

For extended database capability, refer to the 120M DN and 120M IMSIs via Split Database feature(Part Number: 893-0398-01) in Database Administration Manual - Global Title Translation.

Table 2: Example of Individual IMEIs

Black ListGray ListWhite ListIMSI (optional)IMEI

YesNoNo49586725689412512345678901234

NoYesNo234567890123456

YesYesNo49876523576823

NoYesYes49586756587423668495868392048

YesYesYes29385572695759



As shown in Table 2: Example of Individual IMEIs, it is possible for a given IMEI to be on more than onelist (on the White List, and also on the Gray and/or Black List). The logic illustrated by Table 3: Logicfor IMEIs in Multiple Lists is used to determine which answer to return in the CHECK_IMEI response,determined by which list or lists the IMEI is on. Table 3: Logic for IMEIs in Multiple Lists also showsthree possible EIR Response Types. The EIR Response Type is a system-wide EIR option that isconfigured by the user. The combination of the setting of the EIR Response Type, the list or lists inwhich the IMEI is located, and the optional IMSI check determines the response that is returned tothe querying MSC.

Table 3: Logic for IMEIs in Multiple Lists

EIR Response TypePresence in List

Type 3Type 2Type 1BlackGrayWhite

in White Listin White Listin White ListX

in Gray Listin Gray Listin Gray ListXX

in Black Listin Black Listin Black ListXXX

in Black Listin Black listin Black ListXX

unknownin Gray Listin Gray ListX

unknownin Black Listin Black ListXX

unknownin Black Listin Black ListX

unknownunknownin White List

Example Scenarios

Example 1

1. A CHECK_IMEI is received with IMEI = 49876523576823, no IMSI in message.

2. An individual IMEI match is found (Table 2: Example of Individual IMEIs, entry 3), indicating thatthe IMEI is on the Gray and Black Lists. The EIR Response Type is set to Type 3, and an IMSI isnot present.

3. Table 3: Logic for IMEIs in Multiple Lists indicates that the required response is Unknown.

4. EIR formulates a CHECK_IMEI error response with Error = 7 unknownEquipment.

Example 2

Example 2 is the same as Example 1, except that the setting of the EIR Response Type is re-provisionedby the operator to Type 2.

1. A CHECK_IMEI is received with IMEI = 49876523576823, no IMSI in message.

2. An individual IMEI match is found (Table 2: Example of Individual IMEIs, entry 3), indicating thatthe IMEI is on the Gray and Black Lists. The EIR Response Type is set to Type 2, and an IMSI isnot present.



3. Table 3: Logic for IMEIs in Multiple Lists indicates that the required response is Black Listed.

4. EIR formulates a CHECK_IMEI response with Equipment Status = 1 blackListed.

Example 3

1. A CHECK_IMEI is received with IMEI = 12345678901234, and IMSI = 495867256894125.

2. An individual IMEI match is found (Table 2: Example of Individual IMEIs, entry 1) indicating thatthe IMEI is on the Black List.

3. The EIR Response Type is set to Type 1.

4. Table 3: Logic for IMEIs in Multiple Lists indicates that the normally required response would beBlack Listed, however; because an IMSI is present in the message, and the IMEI is on the Black List,the IMSI is compared to the IMSI entry in the database for this IMEI.

5. In this case, the IMSI in the RTDB matches the IMSI in the query, thus the Black Listed condition iscancelled.

6. EIR formulates a CHECK_IMEI response with Equipment Status = 0 whiteListed.

Example 4

1. A CHECK_IMEI is received with IMEI = 12345678901234, and IMSI = 495867256894125.

2. An individual IMEI match is found (Table 2: Example of Individual IMEIs, entry 1), indicating thatthe IMEI is on the Black List.

3. The EIR Response Type is set to Type 1.

4. Table 3: Logic for IMEIs in Multiple Lists indicates that the normally required response would beBlack Listed, however; because an IMSI is present in the message, and the IMEI is on the Black List,the IMSI is compared to the IMSI entry in the RTDB for this IMEI.

5. In this case, the IMSI in the RTDB does not match the IMSI in the query, the Black Listed conditionis maintained.

6. EIR formulates a CHECK_IMEI response with Equipment Status = 1 blackListed.

EIR List Determination

If the EIR Global Response configuration option is set (with the eirgrsp parameter of the chg-gsmoptscommand) to a value other than off, the IMEI is treated as being on the list indicated by the EIR GlobalResponse option, regardless of the actual status of the IMEI. No list logic processing is performed onthe IMEI.

If the EIR Global Response option is set to off, the individual IMEIs are searched first. If no match isfound, the range IMEIs are searched next. If the IMEI is found only on the White List after either search,the list logic processing is complete, and the White List status of the IMEI is sent to the MSC.

Black List Processing

If the IMEI is found on the Black List after either search, list logic processing continues based on theEIR Response Type, set by the eirrsptype parameter of the chg-gsmopts command. If the EIR ResponseType is type 3, and the IMEI is not also found on the White List, the status of the IMEI is unknown.



If the IMEI is also found on the White List, or if the EIR Response Type is either type 1 or 2, the valueof the IMSI Check option, set with the eirimsichk parameter of the chg-gsmopts command, is checked.If the IMSI check option is on, and the IMSI is present in the message, the RTDB is searched for theIMSI. If there is a match for the IMSI, the status of the IMEI is determined to be “White with Override.”If there is no match for the IMSI, the status of the IMEI is determined to be “Black with IMSI MatchFailed.” If the value of the IMSI Check option is off, the status of the IMEI is determined to be "on theBlack List".

Gray List Processing

If the IMEI is found on the Gray List after either search, list logic processing continues based on theEIR Response Type, set by the eirrsptype parameter of the chg-gsmopts command. If the EIR ResponseType is type 3, and the IMEI is not also found on the White List, the status of the IMEI is unknown.

If the IMEI is also found on the White List, or if the EIR Response Type is either type 1 or 2, the statusof the IMEI is determined to be "on the Gray List".

EIR Protocol

The EAGLE 5 supports the EIR capability point code type and a local subsystem that is entered intothe MAP table. The EIR local subsystem has a mate subsystem, and a concerned point code groupassigned to it. ANSI, ITU-I, and ITU-N point codes are supported in the MAP table. The EIR subsystemcannot be set to Load Shared mode (as end nodes do not perform load sharing), but is set to Dominantor Solitary mode.

Messages for Local Subsystems

The message arrives at the EIR subsystem as Rt-on-SSN or Rt-on-GT. If the message arrives asRt-on-SSN, it must contain either the EAGLE 5 true point code or the EIR capability point code in theDPC field of the message, and EAGLE 5 EIR subsystem number in the Called Party Subsystem fieldof the message. If EIR query has the EAGLE 5 capability point code for the DPC, then the EAGLE 5processes the message, but is not able to divert this message in the event of subsystem failure.

If a message arrives at the EIR subsystem as Rt-on-GT, it should also contain a service selector thattranslates to the EIR subsystem. These messages also contain one of EAGLE 5 capability point codesin the DPC field. The EAGLE 5 also processes the message if it has the EAGLE 5 true point code forthe DPC, but it is not able to divert these messages in the event of subsystem failure.

If the EIR local subsystem is offline and the mated subsystem is available, the Routing Indicator isused to determine whether to reroute:

• If the message arrived Rt-on-SSN, the message is not rerouted to the mate. In this case, EAGLE 5is acting as an end node, and end nodes do not reroute. If the return on error option is set, theEAGLE 5 generates a UDTS, otherwise it will discard the message.

• If the message arrived on Rt-on-GT, the message is rerouted to the mated subsystem. In this case,the EAGLE 5 is acting as both STP and SCP, and STPs do reroute messages.



Multiple Local Subsystems

The EAGLE 5 supports provisioning Capability Point Codes (CPCs) for two or more local subsystems,allowing local subsystems for two or more EPAP-related features to operate at the same time in thesystem. For example, local subsystems for the ATINP feature and the EIR feature can coexist in thesystem.

Though queries meant for any local system will still be processed if they are sent with DPC = STPCPC, it is strongly recommended not to use the STP CPC for such queries. Instead, the CPC for theappropriate subsystem should be used as the DPC of the message. For instance, for LNP queries usethe LNP CPC, not the STP CPC; for EIR queries, use the EIR CPC, and so on.

MTP and SCCP Management to Support EIR

If the EIR local subsystem is offline, the EAGLE 5 sends SSPs that cause the Rt-on-SSN message to bediverted to the mate subsystem. These do not cause the Rt-on-GT messages to be diverted. In orderto make other nodes divert Rt-on-GT traffic to the mate, the EAGLE 5 will send response method TFPsto the OPC of the message, when messages arrive Rt-on-GT for one of the EIR Capability Point Codesand the result of translation is the EAGLE 5 EIR subsystem. This TFP should cause the OPC to diverttraffic to the mate. If a message arrives Rt-on-GT for the EAGLE 5 True Point Code, the EAGLE 5 willnot generate a TFP. Therefore, nodes that send Rt-on-GT traffic to the EAGLE 5 should use an EIRCapability Point Code, not the EAGLE 5 True Point Code.

If the EAGLE 5 receives an RSP (Route Set Test Message - Prohibited) for an EIR Capability PointCode, and the EIR subsystem is offline, the EAGLE 5 does not reply. If the EAGLE 5 receives an RSR(Route Set Test Message - Restricted) for an EIR Capability Point Code, and the EIR subsystem isoffline, the EAGLE 5 replies with a TFP concerning the Capability Point Code. When the EIR subsystemis online, RSRT replies to both RSRs and RSPs for an EIR Capability Point Code with a TFA.

Check_IMEI Message Handling

When the CHECK_IMEI message is received by protocol, the, IMSI (if active) and SVN are parsedfrom the MSU. Because different vendors place the IMSI information in different locations within themessage, the decoder searches for the IMSI in multiple locations.

Once the required data is parsed, a lookup is performed in the RTDB to determine the response typefor the IMEI/IMSI combination.

The appropriate response message is sent to the originating MSC.

Encoding Errors

When a Response is generated, it is sent based on the CgPA information in the incoming message.However, some conditions may prevent the EAGLE 5 ISS from generating the response. Most of theerrors involve GTT on the CgPA; if the incoming data is Rt-on-SSN, the number of potential errors ismuch smaller.

Whenever an encoding error is detected, the Response message is discarded.

Data Collection

See EIR Measurements for a description of the measurements collected for the EIR feature.

The rept-stat-sccp command output displays EIR subsystem status, EIR summary and cardstatistics, and CPU usage related to EIR. See rept-stat-sccp.



EIR List Log File

The EIR feature allows for detection and logging of subscribers using handsets that have been BlackListed or Grey Listed by a service provider. These messages are generated by the EAGLE 5 ISS andforwarded to the MPS platform for later retrieval. Messages may be forwarded from any of theprovisioned Service Module cards. Messages will be received and logged independently by both MPSservers.

The files are located in the/var/TKLC/epap/free filesystem and named as follows:eirlog_hostname.csv

Where:

hostname = the hostname of the MPS server that recorded the log.

Each entry in the EIR log file contains information about the caller and handset, a timestampdocumenting the time the server received the log entry, and a unique identifier used for comparisonwith the mate server. See EIR List Log Format for more information about the format of the file and thefields within the file.

The log file is available via Secure FTP using theappuser user.

The EIR log file will contain the last 2 million entries received from the EAGLE 5 ISS. This file may bedeleted through the EPAP GUI "Manage Files & Backups" screen.

EIR Log File Serviceability

The file system used by EIR Log Files is approximately 35 GB in size and is used for all of the followingin addition to storing EIR log files:

• UI Configuration database backup

• Provisioning database backup

• Real-time database backup

• System log file captures

When the file system reaches 80% of it's total capacity a minor alarm is raised. A major alarm is raisedat 90%. All of the files in this partition are managed from the Debug->Manage Logs & Backups screenon the GUI.

EIR Log entries are delivered to and stored on the MPS using a "best effort" approach. The followingthree major factors impact the successful delivery of a log entry:

• Service Module card connectivity: Service Module cards have a limited buffer for storage of EIRlog entries. If the data cannot be delivered, it is discarded.

• UDP Broadcast: A Service Module card will broadcast a log entry to both MPS servers. Althoughexperience shows this broadcast method on a private network to be highly reliable, it is notguaranteed.

• MPS server availability: If an MPS server is down or unreachable, log entries are not collected andstored. Hourly log entries may be later compared with those collected on the mate MPS serverusing the entry's unique identifier.



EIR List Log Format

The export IMEI Black List hits file consists of CSV entries separated by newlines. Each entry containsthe following fields:

• Time/Date stamp: This field represents the time at which the MPS server received the entry fromthe Service Module card. The time is generated by the MPS using the configured system time. Itwill be formatted as yyyyMMddhhmmss (year, month, day, hour, minute, second).

• Source Identifier: This field is an IP address that uniquely identifies the Service Module card thatsent the log entry. This field can be used in combination with the Source Sequence Number tocorrelate log entries with those on the mate MPS server.

• Source Sequence Number: This field is an integer that uniquely identifies the entry per sourceService Module card. This field can be used in combination with the Source Identifier to correlatelog entries with those on the mate MPS server.

• IMSI: International Mobile Subscriber Identity for this entry

• IMEI: International Mobile Equipment Identity for this entry

• Response Code: The following response codes are possible (2 and4 are invalid values):

—0: Indicates that the IMEI is Black Listed.

—1: Indicates that the IMEI is Gray Listed.

—3: Indicates that the IMEI was Black Listed, but the IMSIs matched resulting in a White ListOverride.

—5: Indicates that the IMEI was Black Listed and the IMSIs did not match resulting in Black ListContinues.

For example, If an MPS server receives entry id 1234 on July 15, 2003 at exactly 4:36 PM from a ServiceModule card provisioned at address 192.168.120.1 indicating that Black Listed subscriber 9195551212using handset 12345678901234 was detected, the following entry is created:

20030715163600,192.168.61.1,1234,9195551212,12345678901234,0

Additional EIR Data Files

This feature makes significant use of the /var/TKLC/epap/free file system. The following files may bepresent:

Table 4: Additional Files

CleanupCreationSizeData Type

ManualOn demand atupgrade

< 1K eachUI Configurationdatabase backup



CleanupCreationSizeData Type


Up to 12 GB each depending on theamount of customer data and thesize of the transaction logs

Provisioning databasebackup


4 GB eachReal-time databasebackup

ManualOn demand bycustomer service

5-20 MB or more depending oncore files, and overall life of system.

System log file captures

ManualManual by customerDepends on the amount ofcustomer data. Less than 100MBper million instances

EIR Export

Automatic aftertransferred tocustomer

Scheduled bycustomer

Depends on the amount ofcustomer data. Less than 100MBper million instances

EIR Auto Export (newfor EIR)

ManualManual (FSTP)Determined by customer needPDBI Import

Automatic afterdata imported

Manual (FSTP)Determined by customer needPDBI Auto Import (newfor EIR)

Automatic aftertransferred tocustomer

AutomaticIf no errors, very small. May be upto double the PDBI Auto Importfile size worst case

PDBI Auto Importresults (new for EIR)

Automatic.There should be

AutomaticAssuming no more than 360,000updates per hour from the EAGLE

EIR blacklist logs (newfor EIR)

approximately25 logs at most.

5 ISS, each file will be no more than25MB

EIR S13/S13' Interface Support

Equipment Identity Register (EIR) is a database containing records of all mobile stations that areallowed or banned in a network. Generally, the banned mobile stations have been declared lost orstolen. Each mobile station is identified by its International Mobile Equipment Identity (IMEI). Whena mobile station is detected by the network, the Mobility Management Entity (MME) or Serving GPRSSupport Node (SGSN) requests the IMEI of the mobile station, which is sent to the EIR for authorization.

The EIR S13/S13' Interface Support feature allows EIR to support the S13 and S13' Diameter interfacesfor these messages. By supporting the S13/S13' interfaces, Diameter requests can be received by anEAGLE card and processed by EIR, and then a response transmitted back to the requester.

EIR S13/S13' Interface Support Limitations

• An E5-SM8G-B card running DEIRHC GPL (S13 card) is required to support the EIR S13/S13'Interface Support feature.



• If the S13 card loses EPAP connection, the cable of the S13 card must be manually moved to theother EPAP and the S13 card must be reprovisioned with the address of the new EPAP.

• An S13 card can process traffic using a stale database.

• If the Signaling network interface on an S13 card goes down, the S13 traffic corresponding to thatinterface will be affected.

• An external load balancer is needed to support load-balancing of Diameter messages.

• Relay and proxy modes are not included.

• The response is returned on the same Diameter connection on which the request was received.

• The EIR S13/S13' Interface Support feature does not support E5-MS or FTRA for the new commandsassociated with the EIR S13/S13' Interface Support feature (Diameter EIR/DEIR).

EIR S13 Connection States

S13 Diameter connections maintain a state machine on the S13 Card. The states in Table 5: S13 Stateare maintained for each diameter connection.

Table 5: S13 State

DescriptionState

SCTP association is set to OPEN=NO and SCTP socket is closed.CLOSED

SCTP connection is not established. Initial stateINACTIVE

SCTP Connection is established. Ready to accept Capability Exchange RequestOPEN

Ready to process ECR messagesACTIVE

Transit state to process outstanding messages before moving to Inactive stateCLOSING

Waiting for remote to send DWAPENDING

An event on the S13 diameter connection causes the transitions between these states. Table 6: S13 Eventand State Transition Table depicts the events that cause a state transition and action taken on a particularevent.

The S13 Diameter connection is CLOSED initially when OPEN is set to NO for the associated SCTPconnection. When OPEN is changed to YES using the chg-assoc command, the Diameter connectionis set to INACTIVE state, and attempts to change the SCTP connection status to UP by exchangingSCTP related messages (INIT/INIT-ACK). When the SCTP connection is established, the Diameterconnection moves to the OPEN state and waits for a CER message from the peer. If an Invalid CERor any message other than CER is received in the OPEN state, the message is discarded and the SCTPconnection is closed by sending an abort to the peer. If a Valid CER is received in the OPEN state, aCEA response is formatted per the connection configuration and is sent to the peer. The Diameterconnection moves to the ACTIVE state and is able to receive and process ECR messages. If the SCTPconnection is locally closed (by changing OPEN=NO), the corresponding Diameter connection sendsa DPR to the peer and waits for an Acknowledgement (DPA) from the peer, and the Td timer is started.



The SCTP connection continues to process the outstanding messages on the Diameter connection untilthe DPA message is received or the Td timer expires. In both cases, the Diameter connection and SCTPconnection are closed. If the diameter connection is in the INACTIVE state or the OPEN state, manuallyclosing the local connection moves the state back to CLOSED.

Table 6: S13 Event and State Transition Table

New StateActionEventCurrent State

INACTIVEStop Any running timerTransport Connectiondisconnected

Any State

INACTIVEDiscard MessageReceive Any messageINACTIVE

OPENNoneTransport Connectionestablished

INACTIVE

CLOSEDNoneManually Close LocalConnection

INACTIVE

INACTIVESend CEA with Error CauseDisconnect Transport

Invalid CEROPEN

INACTIVESilently Discard MessageDisconnect Transport

Any Message other than CEROPEN

ACTIVESend CEA with SUCCESS StartTw timer

Valid CEROPEN

CLOSEDNoneManually Close LocalConnection

OPEN

ACTIVESend ECA Restart Tw timerECR messageACTIVE

ACTIVESend DWA Restart Tw timerDWR messageACTIVE

ACTIVEDiscard Message and senderror response

Any message other than ECR/ DWR / DWA / DPR

ACTIVE

ACTIVESilently discard messageCER messageACTIVE

ACTIVESend DPA with Error CauseInvalid DPR messageACTIVE

INACTIVESend DPA Stop all timersDisconnect Transport

Valid DPR messageACTIVE

ACTIVESend DWR Restart Tw timerTw timer Expiry #1ACTIVE

PENDINGSend DWR Restart Tw timerTw timer Expiry #2ACTIVE

CLOSINGSend DPR Stop Tw timer StartTd timer

Manually Close LocalConnection

ACTIVE

CLOSINGSend ECA messageECR messageCLOSING



New StateActionEventCurrent State

INACTIVEDisconnect TransportDPA messageCLOSING

INACTIVEDisconnect TransportDPR messageCLOSING

CLOSEDWait for Td DisconnectTransport

NoneCLOSING

ACTIVERestart Tw TimerDWA MessagePENDING

ACTIVESend ECA Restart Tw TimerECR MessagePENDING

CLOSINGSend DPR Stop Tw timer StartTd timer

Tw timer Expiry #3PENDING

INACTIVESend DPA Stop all timersDisconnect Transport

DPR MessagePENDING

CLOSINGSend DPRManually Close LocalConnection

PENDING

Stop Tw timer

Start Td timer

S13 Supported Messages

Diameter messages are classified as requests or responses. The Diameter request and response messagesin Table 7: S13 Messages supported by Eagle 5 are processed by the EAGLE 5. The S13 card processesonly these messages and sends a 3001 response for all unsupported Diameter request messages.

Table 7: S13 Messages supported by Eagle 5

DescriptionEagleBehavior

CommandCode

ShortName

Message Name

Exchanged between peersto discover the identity

Receive257CERCapability Exchange Request

Send257CEACapability Exchange Answer and capabilities of thepeer.

These messages areexchanged between peers

Recv / Send -Both

282DPRDisconnect-Peer-Request

when they agree toRecv / Send -Both

282DPADisconnect-Peer-Answer disconnect the transportlayer connection.

These messages check thestatus of connection

Recv / Send -Both

280DWRDevice-Watchdog-Request

between two peers whenRecv / Send -Both

280DWADevice-Watchdog-Answer no traffic has beenexchanged between them.



DescriptionEagleBehavior

CommandCode

ShortName

Message Name

These messages areexchanged on S13/S13'

Receive324ECRME-Identity-Check-Request

Send324ECAME-Identity-Check-Answer interface betweenMME/SGSN and EIRdatabase to track thelost/stolen handset.

S13 Supported AVPs

The Diameter Attribute Value Pairs (AVPs) supported on the S13 card are shown in Table 8: AVPsSupported by S13.

Table 8: AVPs Supported by S13

DescriptionAVPCode

AVP Name

This AVP contains the list of applicationIDs supported. The value of the

258AUTH-APPLICATION-ID

Auth-Application-Id AVP in ECR/ECAmust match the Application Id present inthe Diameter message header.

This AVP is present in the ECR messageand specifies whether the state for a

277AUTH_SESSION_STATE

particular session is to be maintained.These values are supported:

• - STATE_MAINTAINED 0• - NO_STATE_MAINTAINED 1

This AVP contains the Realm to which themessage is to be routed. This is a

283DESTINATION_REALM

mandatory AVP in an ECR message. Thevalue will be checked against the localRealm value configured in the IPHOSTtable.

This AVP is included in a DPR requestmessage to inform the peer of the reason

273DISCONNECT_CAUSE

for its intention to shut down the transportconnection. It is of type Enum andsupports these values:

• Rebooting - 0• Busy - 1• Do_not_want_to_talk_to_you - 2



DescriptionAVPCode

AVP Name

Disconnect cause to be specified inoutgoing DPR message is configured inDEIROPTS table.

This mandatory AVP in the ECA messagecontains the status of equipment after

1445EQUIPMENT_STATUS

performing EIR database lookup (Blacklist,Whitelist, Greylist, or Unknown).

The Error message AVP contains thehuman readable text of error result codeto be sent to the peer.

281ERROR-MESSAGE

This is a grouped AVP and provides thedebugging information when a request is

279FAILED_AVP

rejected or not fully processes due toerroneous information in a specified AVP.

This AVP contains IP addresses of theoriginator of the Diameter message.

257HOST_IP_ADDRESS

Note: Only one instance of this AVP issupported. All other instances arediscarded.

This AVP contains the IMEI of the specificequipment.

1402IMEI

The Origin Host AVP contains thehostname of the originator of the Diameter

264ORIGIN_HOST

message. The value is checked against theremote host value configured in theIPHOST table.

This AVP contains the Realm of theoriginator of the Diameter message. The

296ORIGIN_REALM

value is checked against the remote Realmvalue configured in the IPHOST table.

This AVP contains the vendor assignedname of the product. Product Name to be

269PRODUCT_NAME

specified in outgoing message isconfigured in DEIROPTS table.

Note: This is a mandatory AVP in CER.

If any Proxy-Info AVP is present in therequest, it is added to the answer message

284PROXY-INFO

in the same order as it is present in therequest.



DescriptionAVPCode

AVP Name

If this AVP is present in the request, it isadded to the answer message in the sameorder as it is present in the request.

282ROUTE-RECORD

This AVP indicates whether a particularrequest was completed successfully or anerror occurred.

268RESULT_CODE

If this AVP is present in the requestmessage, copy the same session ID in theresponse message.

263SESSION-ID

The mandatory grouped AVP of the ECRmessage contains IMEI and software

1401TERMINAL_INFORMATION

version. The IMEI AVP value is used forEIR database lookup.

This AVP contains the IMSI of the specificequipment. The IMSI value along withIMEI is used for database lookup.

1USER_NAME

This AVP contains the predefined IANAvalue assigned to the Diameter Software

266VENDOR_ID

vendor. For CEA message outgoing fromEagle 5, this parameter is set to 0.

This grouped AVP in the CEA messagecontains these AVPs:

260VENDOR_SPECIFIC_APPLICATION_ID

• - vendor-id avp - Vendor Id to bespecified in outgoing message is 10415.

• - auth-application-id - auth-application-id to be specified inoutgoing message is configured inDEIROPTS table as APPLID.

EIR S13/S13' Interface Support - ECA Message Encoding

After the Equipment status is determined, the ECA message with the following details is send to theoriginator of the request.

• Common information• Session-ID, Route-record or Proxy-Info AVP: If the Session-ID, Route-record or Proxy-Info AVP is

present in the ECR message, they are appended in the same order as presented in the requestmessage. A maximum of ten Route-record and Proxy-Info AVPs can be copied from the requestmessage.

• Result-Code and Equipment-Status AVPs: Result-Code and Equipment-Status AVPs are populatedas shown in Table 9: Mapping of EIR database Response and ECR Result.



Table 9: Mapping of EIR database Response and ECR Result

ME-Check-Identity Response

Equipment-StausResult CodeEIR Response

WHITELISTED (0)DIAMETER_SUCCESSin Whitelist

BLACKLISTED (1)DIAMETER_SUCCESSin Blacklist

GREYLISTED (2)DIAMETER_SUCCESSin Graylist

NADIAMETER_ERROR_EQUIPMENT_UNKNOWNUnknown*

EIR S13/S13' Interface Support Result Codes

Table 10: Supported Result Codes

Error-Message AVPValues

Readable ValueResult CodeValue

Text String

diameter successDIAMETER_SUCCESS2001

diameter Command notsupported

DIAMETER_COMMAND_UNSUPPORTED3001

diameter is busyDIAMETER_TOO_BUSY3004

diameter application notsupported

DIAMETER_APPLICATION_UNSUPPORTED3007

Note: Only EIRApplication ID issupported

invalid bits in diameterheader

DIAMETER_INVALID_HDR_BITS3008

unknown peerDIAMETER_UNKNOWN_PEER3010

diameter avp notsupported

DIAMETER_AVP_UNSUPPORTED5001

diameter successDIAMETER_SUCCESS2001

diameter Command notsupported

DIAMETER_COMMAND_UNSUPPORTED3001

diameter is busyDIAMETER_TOO_BUSY3004



Error-Message AVPValues

Readable ValueResult CodeValue

Text String

diameter application notsupported

DIAMETER_APPLICATION_UNSUPPORTED3007

Note: Only EIRApplication ID issupported

invalid avp valueDIAMETER_INVALID_AVP_VALUE5004

Note: Received invalidIMEI or IMSI value

missing avpDIAMETER_MISSING_AVP5005

Diameter ResourceExceeded

DIAMETER_RESOURCES_EXCEEDED5006

diameter avp occurs toomany times

DIAMETER_AVP_OCCURS_TOO_MANY_TIMES5009

no common applicationDIAMETER_NO_COMMON_APPLICATION5010

diameter version notsupported

DIAMETER_UNSUPPORTED_VERSION5011

invalid avp lengthDIAMETER_INVALID_AVP_LENGTH5014

invalid message lengthDIAMETER_INVALID_MESSAGE_LENGTH5015

unknown equipmentDIAMETER_ERROR_EQUIPMENT_UNKNOWN5422

Hardware Requirements

EPAP-related features that perform an RTDB lookup require Service Module cards (DSM cards,E5-SM4G cards, or E5-SM8G-B cards) running the VSCCP application. The EAGLE 5 ISS can beequipped with up to 32 (31+1) Service Module cards.

Features that do not perform an RTDB lookup require Service Module cards only for GTT processingthat might be performed for the feature. These features can coexist in systems with EPAP, but do notrequire an EPAP connection.



MPS/EPAP Platform

Oracle provides the Multi-Purpose Server (MPS) platform as a subsystem of the Oracle CommunicationsEAGLE. The MPS provides support for EPAP-related features that perform Real Time Database (RTDB)lookups.

The MPS is composed of hardware and software components that interact to create a secure andreliable platform. For details about the MPS hardware, refer to Application B Card Hardware andInstallation Guide. The MPS provides the means of connecting the customer provisioning applicationwith the EAGLE and accepts the customer number portability data, while accommodating numbersof varying lengths.

The Oracle Communications EAGLE Application Processor Provisioning (EPAP) is software that runson the MPS hardware platform. EPAP collects and organizes customer provisioning data, and forwardsthe data to the EAGLE Service Module cards. For detailed information about EPAP, refer toAdministration Guide for EPAP.

In this manual, Service Module card refers to a DSM card, an E5-SM4G card, or an E5-SM8G-B cardunless a specific card is required. For more information about the supported cards, refer to HardwareReference. DSM cards are not supported with Oracle Communications EAGLE Application B Card(E5-APP-B) based EPAP systems.



Chapter

3EAGLE EIR Commands

This chapter contains brief descriptions of theEAGLE commands that can be used forconfiguration of the EIR feature.

Topics:

• EAGLE 5 Commands for EIR.....34


EAGLE 5 Commands for EIR

This chapter describes the EAGLE 5 commands that are used for the configuration of the EIR feature.

Refer to Commands Manual for complete descriptions of the commands, including parameter names,valid values, and output examples for the commands.

Table 11: Commands used for EIR

CommandsType

ent/rtrv-serial-numSystem Serial Number

ent/dlt/rtrv/alw/inh/init/rept-stat-cardCard

chg/rtrv-feat, enable/chg/rtrv-ctrl-featFeature Control

chg/rtrv-sidEAGLE 5 ISS STP Self Identification

chg/dlt/ent/rtrv-mapMated Application (MAP)

chg/dlt/ent/rtrv-ss-applSubsystem Application

chg/dlt/ent/rtrv-srvselService Selector

chg/rtrv-gsmoptsEIR GSM Options

alw/inh-map-ssLocal Subsystem Activation

chg/dlt/ent/rept-stat/rtrv-assocSCTP Associations in Table IPAPSOCK

dlt/ent/rtrv-ip-hostIP Host Table

chg/rtrv-th-almAlarm Thresholds

EAGLE 5 EIR GSM Options Commands

The GSM Options (gsmopts) commands are used to change and report on the values of one or moreof the system-level processing options maintained in the GSMOPTS table. All values are assignedinitially to system defaults at STP installation time, and they can be updated later using thechg-gsmopts command.

The options described in Table 12: GSMOPTS Options for EIR apply to EIR.

Table 12: GSMOPTS Options for EIR

DescriptionRangeParameter

EIR IMSI Check statusOFF or ONEIRIMSICHK

EIR Response TypeTYPE1, TYPE2, TYPE3EIRRSPTYPE

EIR Global Response statusOFF, WHITELST, GRAYLST, BLKLST,UNKNOWN

EIRGRSP


EAGLE EIR CommandsEIR User's Guide

The EIRIMSICHK (EIR IMSI Check status) parameter is used to indicate whether or not the IMSI willbe used when determining if an IMEI is to be Black Listed. If this parameter is on and an IMEI is foundon the Black List, then the corresponding IMSI is retrieved. If the IMSI found in the message matchesthe IMSI retrieved, then the IMEI is considered to be on the White List. If the IMSIs do not match orthe IMSI is not found, then the IMEI will remain Black Listed.

The EIRRSPTYPE parameter is used to determine the EIR Response Type. The Response Type is usedto determine how the lists are searched, as shown in Table 13: Individual IMEI List Determination.

Table 13: Individual IMEI List Determination

MSU ResultEquipmentStatus

LOG Entry ResultLOGEntry

ResultType

IMSIMatch

IMSICheck

WhiteList

GrayList

BlackList

0White with IMSIOverride

N1YYNNY


N2YYNNY

Return Error=7UnknownN3YYNNY

1Black with IMSIFailed

Y1NYNNY


Y2NYNNY

Return Error=7UnknownN3NYNNY

1BlackY1DCNYNY

1BlackY2DCNYNY

1BlackY3DCNYNY


N1YYYNY


N2YYYNY


N3YYYNY

1BlackY1DCNNYY

1BlackY2DCNNYY

Return Error=7UnknownN3DCNNYY


Y1YYNYY





ResultType

IMSIMatch

IMSICheck

WhiteList

GrayList

BlackList


Y2YYNYY


Y3YYNYY

2GrayY1DCYNYN

2GrayY2DCYNYN

Return Error=7Unknown3DCYNYN

2GrayY1DCDCYYN

2GrayY2DCDCYYN

2GrayY3DCDCYYN

0WhiteN1DCDCYNN

0WhiteN2DCDCYNN

0WhiteN3DCDCYNN

0WhiteN1DCDCNNN

Return Error=7UnknownN2DCDCNNN

Return Error=7UnknownN3DCDCNNN

1BlackY1DCNYYY

1BlackY2DCNYYY

1BlackY3DCNYYY


N1YYYYY


N2YYYYY


N3YYYYY


N1NYYYY


N2NYYYY





ResultType

IMSIMatch

IMSICheck

WhiteList

GrayList

BlackList


N3NYYYY

For EIR Response Types 1 or 2, the IMEI searches are handled in the following manner:

• If the IMEI is found in the Black List table, the search stops without searching the White and GrayList tables. The IMEI is considered Black Listed regardless of IMEI’s presence on the White or GrayList tables.

• If the IMEI is found in the Gray List table, but not found in the Black List table, the search stopswithout searching the White List table. The IMEI is considered Gray Listed regardless of the IMEI’spresence on the White List table.

For EIR Response Type 3, the IMEI searches are handled in the following manner:

• The White List table is searched first. If the IMEI is not found in the White List table, the IMEI istreated as unknown - no other table searches need to be performed.

• If the IMEI is found in the White List table, the Black List table is searched next. If the IMEI is inthe White and Black List tables, the IMEI is considered Black Listed - no need to search the GrayList table.

• If the IMEI is found in White List table, but not in the Black List table, the Gray List table is searched.If the IMEI is in the White and Gray list tables, the IMEI is considered Gray Listed. If the IMEI isin the White List table, but not in the Gray List table, the IMEI is considered White Listed.

The EIRGRSP parameter is used to turn on the EIR Global Response Type. The Global Response Typeis used to override the response that is normally sent back to the MSC. The default is set to OFF. Whenset to OFF, the normal list logic is applied to the IMEI. If the Global Response Type is set to somethingother than OFF, then there is no list logic processing and the corresponding response is sent to theMSC.

EAGLE 5 EIR Service Selector Commands

The EIR service selector (srvsel) commands are used to enter, delete, change, and display the serviceselectors required to change a service entry for a DSM service entry.

• The EIR service is eir.

• EIR supports ANSI, ITU-I, and ITU-N Global Title Indicators.

The Global Title Indicator (GTI) value can be either 2 or 4. The Numbering Plan and Nature ofAddress Indicator cannot be specified when the GTI is 2, and must be specified when the GTI is 4.

• EIR does not support the Service Nature of Address or the Service Numbering Plan.

• The Subsystem Number (SSN) must be defined in the MAP table, and supports the asterisk (*)value.



EAGLE 5 Feature Control Commands

The chg/rtrv-feat commands are used to turn on and display the on/off status of features, suchas the GTT feature, that are controlled with feature bits. After a feature that is controlled with a featurebit is turned on, the feature cannot be turned off.

The enable/chg/rtrv-ctrl-feat commands are used to enable, turn on, and display the statusof features that are controlled by feature access keys. The feature access key is based on the featurepart number and the serial number of the system that uses the feature, making the feature access keysite-specific. When a feature is enabled by entering the enable-ctrl-feat command with thefeature part number and feature access key, the feature is recognized by the system. Other actionsmight be required to make the feature fully operational, such as turning the feature on, installinghardware, and provisioning information in database tables.

Some features can be enabled with a temporary part number and feature access key for a limited trialof the feature. When the trial period expires, the feature must be enabled with a permanent part numberand feature access key to continue use of the feature.

EIR S13/S13' Interface Support Commands

The commands in Table 14: Commands for EIR S13/S13' Interface Support feature support the EIR S13/S13'Interface Support feature.

Table 14: Commands for EIR S13/S13' Interface Support feature

DescriptionCommand

configures S13-specific optionschg-deiropts

displays S13-specific optionsrtrv-deiropts

configures Diameter connection and flow control by entering Diameterconnection values associated to a particular association in tableIPAPSOCK

ent-dconn

changes Diameter connection and flow control configuration valueschg-dconn

deletes Diameter connectiondlt-dconn

displays Diameter connection status and flow control datartrv-dconn

displays S13 card statisticsrept-stat-deir

Table DEIROPTS

The chg-deiropts and rtrv-deiropts commands configure and display the EIR S13/S13' InterfaceSupport options of the virtual table DEIROPTS, which is part of table EGLEOPTS. The table DEIROPTSoptions are shown in Table 15: Table DEIROPTS options.



Table 15: Table DEIROPTS options

DescriptionValuesName

IMSI CheckOFFDEIRIMSICHK

The IMSI Check specifies whether IMSI is usedwhen determining if an IMEI is to be blacklisted.

ON

If this option is set to ON and an IMEI is foundon the Blacklist, then the corresponding IMSI willbe retrieved. If the IMSI found in the messagematches the IMSI retrieved, then the IMEI isconsidered to be on the Whitelist. If the IMSIs donot match or the IMSI is not found, then the IMEIwill remain blacklisted.

Default value is OFF.

S13 Response TypeTYPE1DEIRRSPTYPE

The S13 Response Type is used to determine howthe lists are to be searched.

TYPE2

TYPE3Default value is TYPE1.

S13 Global Response TypeOFFDEIRGRSP

The S13 Global Response Type is used to overridethe response that is sent to the MME or SGSN.

WHITELST

GRAYLST When S13 Global Response Type is set to OFF,the normal list logic is applied to the IMEI. If theBLKLSTS13 Global Response Type is set to any valueUNKNOWN except OFF, then list logic processing is notperformed and the corresponding response is sentto the MME or SGSN.

Default value is OFF.

Congestion Error3004CONGERR

This is the value in the result code Attribute ValuePair (AVP) of the response sent at the time of

5006

congestion. If the incoming messages on the cardrunning the DEIRHC GPL exceed the card orconnection capacity and the card is not able toprocess the messages, the messages are discardedand the card responds with the configured valuein the result code.

• 3004 - DIAMETER_TOO_BUSY [default value]• 5006 - DIAMETER RESOURCES EXCEEDED

S13 local Vendor IDunsigned32VENDID

All outgoing messages that require Vendor ID inVENDOR_SPECIFIC_APPLICATION_ID use this




configured value. Because only the value 10415is supported, the CEA message contains 10415 asthe Vendor Id in the response.

Default value is 0.

Product Namealphanumeric stringPRODUCT

The configured value contains thevendor-assigned name for the product. Alloutgoing messages that require the Product NameAVP use this configured value.

Default value is NONE.

Authentication Application IDunsigned32APPLID

The configured Application ID should match theAuth-Application-Id (AVP Code 258) value in theVendor-Specific-Application-ID AVP. Currently,only 16777252 APPLID is supported by EAGLE5 and this parameter cannot be changed.

Default value is 16777252.

Disconnect CauseREBOOTING (0)DPRCAUSE

The Disconnect Cause in all DPR messagesgenerated by EAGLE 5 use this value.

BUSY (1)

DO_NOT_WANT_TO_TALK(2) Default value is DO_NOT_WANT_TO_TALK (2).

Table DCONN

The ent-dconn, chg-dconn, dlt-dconn, and rtrv-dconn commands configure and display theEIR S13/S13' Interface Support options of the table DCONN, which supports the provisioninginformation associated with the Diameter connection. The table DCONN options are shown in Table16: Table DCONN options.

Table 16: Table DCONN options


Diameter Connection Namealphanumeric stringDCNAME

The Diameter Connection Name identifies the Diameterconnection linked to an association. This option ismandatory.

Association Namealphanumeric stringANAME

This name identifies the association configured in theassociation table with the Diameter adapter. This option ismandatory.




Reserved TPSinteger from 100 to8000, inclusive

RSVDTPS

This is the guaranteed TPS for a connection. Total RSVDTPSon a card cannot exceed 8000.


Max TPSinteger from 100 to8000, inclusive

MAXTPS

The unused S13 card capacity is allocated among theconnections that have exceeded their RSVDTPS values upto the limit of MAXTPS value provisioned for the particularconnection.


Diameter Watchdog Timer6sec - 30secTW

Default value is 6sec.

Diameter Peer Disconnect Timer1sec - 10secTD

Default value is 3sec.

REPT-STAT-DEIR Command

The rept-stat-deir command displays the overall status of the Diameter EIR S13/S13' service onthe EAGLE 5. This command is similar to the rept-stat-sccp and rept-stat-sip commands.The Diameter connection status is displayed in the Status field when the rept-stat-deir commandis entered with the dcname parameter. The possible values for Diameter Status parameter are:

• UP - The Diameter connection status is up and active. This status supports the following Diameterconnection states: Active, Closing, Pending.

• DOWN - The Diameter connection status is down or closed. This status supports the followingDiameter connection states: Inactive, Open, Closed.

The rept-stat-deir command can be entered with or without parameters. If the rept-stat-deircommand is entered without parameters, the displayed consists of a per diameter card status, TPS oneach S13 card, total S13 statistics, and alarms associated with the Diameter EIR S13/S13' service in theDEIR ALARM STATUS field. The following parameters can be entered with the rept-stat-deircommand:

• loc - Diameter card location for which card status, overall card TPS, and per-connection cardstatistics are reported

• peakreset - Reset peak values for a card or a specified Diameter connection• mode - Overall S13 TPS and per diameter connection statistics in the EAGLE 5 displayed; allowed

value: perf• dcname - Diameter connection name, which is the unique logical name assigned to each diameter

connection; output display: status, TPS, and statistics of the specified Diameter connection

The rept-stat-deir command displays the pegs shown in Table 17: REPT-STAT-DEIR Pegs.



Table 17: REPT-STAT-DEIR Pegs

ConditionPegs

Messages which fall in these categories:SUCCESS

• Success response• IMEI Lookup failure and DEIRRSPTYPE=TYPE1

Messages which fall in these categories:ERROR

• Decoding error• Unsupported messages

Messages which fall in these categories:WARNING

• IMEI Lookup failure and DEIRRSPTYPE=TYPE2 or TYPE3• Unknown equipment is sent in response

Number of message discarded due to congestionOVERFLOW

Total number of messages received: Success + Error + Warningmessages

TOTAL MSGS

PASS Commands supported by S13 card

The S13 card supports the following PASS commands:

• ARP - displays and modifies the Internet to Ethernet address translation tables used by the addressresolution protocol

• ASSOCRTT - displays round-trip statistics for a given association• CPUM - displays CPU utilization• MSUCOUNT - displays MSU count for particular association and routes, including S13/S13'

protocol• NETSTAT - displays network statistics from the IP stack• NSLOOKUP - returns the IP address for a specified hostname, or returns a hostname for a specified

IP address• PING - tests for the presence of hosts on the network• SCTP - displays MSU count and current state of specific association• SYSSTAT - display system buffer, CPU configuration, and database-related information• TRACEROUTE - returns/traces the complete path a message has taken to reach the destination



Chapter

4EIR Configuration

This chapter identifies prerequisites and proceduresfor configuration of the EIR feature in the EAGLE5 ISS.

Topics:

• Introduction.....44• EPAP Entity Provisioning.....44• System Prerequisites.....44• EIR Feature Prerequisites.....45• EIR Configuration Procedure.....46• Enabling and Turning On the EIR Feature.....47• Provisioning the EIR Local Subsystem.....48• Changing the State of a Subsystem

Application.....50• Provisioning the EIR Service Selectors.....53• Changing the EIR Options.....56• Configuring EIR S13/S13’ Interface Support.....57• Activating the EIR Local Subsystem.....58


Introduction

This chapter describes prerequisites and procedures for configuration of the EIR feature on the EAGLE5 ISS.

The Equipment Identity Register (EIR) feature is configured on the EAGLE 5 ISS and on the EPAP (inassociation with either the G-Flex or G-Port feature). This chapter covers the EAGLE 5 ISS configurationonly. Refer to the EPAP Administration Manual and EPAP Entity Provisioning in this manual forinformation about EPAP configuration.

EIR Configuration Procedure lists the steps for enabling and turning on the feature, and for theprovisioning required for the feature. Each step contains a link or reference to information andprocedures to use to complete the step. Feature provisioning can be performed only after the EIRfeature is turned on.

Note: The EIR feature is optional and must be purchased from Tekelec before it can be used in yoursystem. If you are not sure whether you have purchased a specific feature, contact your Tekelec Salesor Account Representative.

EPAP Entity Provisioning

It is recommended that EPAP entity (SP or RN) administration not be done until after the point codeand/or subsystem number has been entered into the EAGLE 5 ISS MAP table.

• EPAP-administered entity data can possibly become out-of-sync with the EAGLE 5 ISS MAP tablewhen the creation of point codes and/or subsystem numbers in the MAP table is performed afterEPAP database administration.

• If this mismatch is discovered in real-time operations, a UIM (such as SCCP did not route -DPC not in MAP tbl or SCCP did not route - SS not in MAP tbl) is sent to theEAGLE 5 ISS maintenance terminal.

System Prerequisites

Before any feature that is described in this manual can be enabled, the prerequisites listed in Table 18:System Prerequisites are required in the system.

Table 18: System Prerequisites

Verification and ProvisioningPrerequisite

Note: The serial number cannot be changed afterit is entered and locked in the system.

The system serial number must be correct andlocked.

For new installations, the system is shipped withan unlocked serial number. The serial number can

Locate the serial number for the system on a labelaffixed to the control shelf (1100).


EIR ConfigurationEIR User's Guide

Verification and ProvisioningPrerequisiteEnter the rtrv-serial-num command todisplay the serial number and its locked status.

be changed if necessary and must be locked afterthe system is on-site.

For systems that are being upgraded, the serialnumber is usually already verified and locked.

Verify that the displayed serial number is correctfor the system.

If no serial number is displayed, enter theent-serial-num command (without the lockparameter) to provision the serial number thatappears on the control shelf label. Enter thertrv-serial-num command and verify that theserial number was entered correctly.

Enter the ent-serial-num command with thelock=yes parameter to lock the serial number inthe system.

Enter the rept-stat-card:appl=vsccpcommand to list the Service Module cards in thesystem.

A sufficient number of Service Module cards mustbe equipped.

Some features require only E5-SM4G cards andcannot use DSM cards. See specific featureprerequisites, if any, in this section.

If more cards or cards of a different type areneeded, refer to the procedures in the DatabaseAdministration Manual - GTT to add ServiceModule cards or remove DSM cards.Refer to the Dimensioning Guide for EPAP Advanced

DB Features for information on the dimensioningrules and the database capacity requirements forEPAP-related features.

Enter the rtrv-feat command to display theGTT feature status.

The GTT feature must be on in the system.

Some features require an additional GTT-relatedfeature such as EGTT. See the specific featureprerequisites in this section.

If the GTT feature is on, the gtt=on entry appearsin the output.

If the gtt=off entry appears in the output, use theprocedures in the Database Administration Manual- GTT to turn on and provision the GTT featureand any other GTT-related features and functionsthat will be used in the system.

EIR Feature Prerequisites

Before the EIR feature can be enabled, the following prerequisites are required in the system:

Table 19: EIR Feature Prerequisite

Verification and ProvisioningPrerequisite

Enter the rtrv-stpopts command.The ANSIGFLEX system option cannot be set toYes.



Verification and ProvisioningPrerequisiteVerify that the ANSIGFLEX entry does not appearin the command output or that the ANSI GFLEXentry shows a value of No.

Enter the rtrv-ctrl-feat command.The LNP feature cannot be on in the system.

If the LNP feature is on, shown with a quantitygreater than zero for the LNP ported TNs entryin the command output, the feature described inthis manual cannot be enabled.

EIR Configuration Procedure

The EAGLE 5 configuration of the Equipment Identity Register (EIR) feature consists of the followingsteps. The steps contain links and references to detailed procedures and information needed to completeeach step.

1. Verify, and provision if needed, the system prerequisites. See System Prerequisites.2. Verify, and provision if needed, the feature prerequisites. See EIR Feature Prerequisites.3. Enable the EIR feature, set system STP options, and turn on the EIR feature. See Enabling and Turning

On the EIR Feature.4. Change the self identification of the EAGLE 5 node to include true point codes and EIR capability

point codes. Refer to the procedures in Database Administration Manual - SS7.5. Refer to the procedures in Database Administration Manual - Global Title Translation to provision the

following items:

• Translation types and mappings• Mated Application (MAP) table entries for the EIR feature that contain the EAGLE 5 ANSI,

ITU-I, and ITU-N true point codes, the EIR capability point codes, and the EIR subsystemnumber. Only solitary and dominant loadsharing are supported.

The EIR subsystem can have a mate subsystem and a concerned point code group assigned to itin the MAP table.

If multiple point code types for EIR are provisioned in the MAP table, then the point code type forthe Subsystem Out-of-Service Request message (SOR) is determined using the following order:

1. ANSI2. ITU-N3. ITU-N Spare4. ITU-I5. ITU-I Spare

6. Provision the state and subsystem number for the EIR local subsystem application. See Adding theEIR Subsystem Application.

7. Provision the service selector mechanism to route MSUs to the EIR subsystem. See Provisioning theEIR Service Selectors.

The EIR service is eir.



The Translation Type and Subsystem Number are the values assigned for the EIR local subsystemwhen the MAP table entries were defined. See Step 5 in this procedure. The asterisk value (*) forthe Subsystem Number is supported for the EIR subsystem.

EIR supports ANSI, ITU-I, and ITU-N Global Title Indicators.

• The gtii/gtin/gtin24 value can be either 2 or 4.• If the gtii/gtin/gtin24 value is 2, the np, nai, npv, or naiv parameters cannot be specified with

the ent-srvsel command.• If the gtii/gtin/gtin24 value is 4, either the np and nai or the npv and naiv parameters must be

specified with the ent-srvsel command.

EIR does not support the Service Nature of Address or the Service Numbering Plan.

8. Provision GSM options, including the EIR Global Response status, EIR Response Type, and EIRIMSI Check status options. See Changing the EIR Options.

9. Activate the EIR local subsystem. See Activating the EIR Local Subsystem.10. Configure the Measurements Platform feature or the E5-OAM Integrated Measurements feature

if measurements are to be collected for EIR.

Refer to the procedures in the Database Administration Manual - System Management for configuringthe Measurements Platform feature, the E5-OAM Integrated Measurements feature, and the EAGLEOA&M IP Security feature in the EAGLE 5. OAM-based measurements reports are not availablefor EIR.

Enabling and Turning On the EIR Feature

This procedure is used to enable and turn on the EIR feature in the EAGLE 5 ISS.

• The EIR feature must be enabled using the EIR feature part number 893012301 and a feature accesskey.

Note: Controlled features must be purchased before you can receive a feature access key to use toenable the feature. If you are not sure if you have purchased a feature and received the featureaccess key, contact your Tekelec Sales Representative or Account Representative.

The feature access key is based on the EIR feature part number and the serial number of the system,making the feature access key site-specific.

When the EIR feature is enabled, it is permanently enabled. The EIR feature cannot be temporarilyenabled.

• After the EIR feature has been enabled, the EIR feature must be turned on using the chg-ctrl-featcommand with the EIR feature part number and the status=on parameter.

1. Enable the EIR feature. Enter the enable-ctrl-feat command with the EIR feature part number893012301and the FAK.

2. Turn on the EIR feature on. Enter the chg-ctrl-feat command with the EIR feature part number893012301 and the status=on parameter.

3. Verify the changes. Enter the rtrv-ctrl-feat command with part number 893012301.

rlghncxa03w 10-06-30 21:16:37 GMT EAGLE5 42.0.0



The following features have been permanently enabled:Feature Name Partnum Status QuantityHC-MIM SLK Capacity 893012707 on 64EIR 893012301 on ------

4. Back up the changes using the chg-db:action=backup:dest=fixed command.These messages should appear, the active Maintenance and Administration Subsystem Processor(MASP) appears first:

BACKUP (FIXED) : MASP A - Backup starts on active MASP.BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.BACKUP (FIXED) : MASP A - Backup starts on standby MASP.BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Provisioning the EIR Local Subsystem

The following procedures in this section are used to add or remove a local subsystem application:

• Adding the EIR Subsystem Application• Removing the EIR Subsystem Application

See the procedures in Changing the State of a Subsystem Application to take the subsystem applicationonline or offline.

Note: The EAGLE 5 ISS supports the operation of two or more local subsystems for EPAP-relatedfeatures in the system at one time. For example, the local subsystems for INP and EIR can coexist inthe system.

Adding the EIR Subsystem Application

This procedure is used to define the EIR subsystem application. The subsystem application can betaken online when it is defined or later in the configuration process (see Changing the State of a SubsystemApplication).

Before the EIR local subsystem can be added to the database, the following prerequisites must existin the system:

Table 20: EIR Local Subsystem Prerequisites

VerificationPrerequisite

Enter the rtrv-ctrl-feat command.The EIR feature must be enabled and turned on.

If the EIR entry with Status of on does not appearin the output, see the Enabling and Turning On theEIR Feature procedure.

Enter the rtrv-ss-appl command.The application specified by the appl parameter(eir) cannot already be in the database.



VerificationPrerequisiteIf the EIR entry appears in the output , thisprocedure cannot be performed.

Only one subsystem number for the applicationcan be defined, and must be used for all pointcode types assigned to the local subsystem.

EAGLE 5 ISS true point codes and EIR capabilitypoint codes must be defined, and entered in theMated Application (MAP) table with a subsystemnumber to be used for the EIR subsystemapplication. Enter the rtrv-sid command, and verify that

the true and capability point codes (PCI and PCNfields) needed for the feature are correct. Ifchanges are required, refer to the procedures inthe Database Administration Manual - SS7.

Enter the rtrv-map command, and verify that theMAP table entries include EAGLE 5 ISS true pointcode and the SSN for the EIR local subsystem. Ifchanges are required, refer to the procedures inthe Database Administration Manual – Global TitleTranslation for provisioning solitary and dominantmated applications.

The example in this procedure reserves the subsystem number 100 for the EIR application and setsthe EIR application status to online.

1. Add the EIR application and subsystem number, using the ent-ss-appl command.

If the stat=online parameter is not specified, the status defaults to offline.

2. Verify the changes; enter the rtrv-ss-appl command.

tekelecstp 10-07-25 08:02:22 EST EAGLE5 42.0.0 APPL SSN STAT EIR 100 online

SS-APPL TABLE IS 25% FULL (1 OF 4);

3. Back up the changes using the chg-db:action=backup:dest=fixed command.The following messages should appear; the active Maintenance and Administration SubsystemProcessor (MASP) appears first:

BACKUP (FIXED): MASP A - Backup starts on active MASP.BACKUP (FIXED): MASP A - Backup on active MASP to fixed disk complete.BACKUP (FIXED): MASP A - Backup starts on standby MASP.BACKUP (FIXED): MASP A - Backup on standby MASP to fixed disk complete.

Removing the EIR Subsystem Application

This procedure is used to remove a subsystem application from the database. The subsystem applicationto be removed must be in the database and the subsystem must be out of service.



1. Display the subsystem number for the EIR local subsystem application in the database; enter thertrv-ss-appl command.

2. Display the operating status of the EIR subsystem; enter the rept-stat-sccp command.If the subsystem is out of service, shown by an entry containing OOS-MT-DSBLD for the subsystemin the rept-stat-sccp output, go to Step 5.

3. Place the EIR subsystem application out of service. Enter the inh-map-ss command and specifythe EIR subsystem number displayed in Step 1.inh-map-ss:ssn=100

rlghncxa03w 10-06-28 14:42:38 GMT EAGLE5 42.0.0Inhibit map subsystem command sent to all SCCP cards.Command Completed.

4. Verify that the EIR subsystem is out of service by entering the rept-stat-sccp command.

If the local subsystem is not out of service, return to Step 3 and enter the inh-map-ss commandwith the force=yes parameter specified.

5. Remove the local subsystem application from the database, by entering the dlt-ss-appl command.

When this command has successfully completed, the following message appears:

rlghncxa03w 09-04-05 17:34:20 EST EAGLE 41.0.0DLT-SS-APPL: MASP A - CAUTION: DELETED APPL SSN MAY BE REFERENCED BY GTT ENTRYDLT-SS-APPL: MASP A - COMPLTD;

6. Verify the changes; enter the rtrv-ss-appl command.7. Back up the changes using the chg-db:action=backup:dest=fixed command.

The following messages should appear, the active Maintenance and Administration SubsystemProcessor (MASP) appears first:


Changing the State of a Subsystem Application

The procedures in this section are used to set the state of an existing subsystem application to eitheronline or offline.

The online or offline status of the subsystem application is shown in the STAT field of thertrv-ss-appl command output.

The rept-stat-sccp command displays the operating state (in or out of service) of the subsystem.

If the subsystem application is to be taken online, the subsystem application must be offline.



When the subsystem is taken online (regardless of how the subsystem was taken offline), the EAGLE5 ISS sends SNR/SSA. A UAM is generated, indicating that the subsystem is ALLOWED.

If the subsystem application is to be taken offline, the subsystem application must be online. Thesubsystem must be taken out of service (OOS-MT-DSBLD) with the inh-map-ss command beforeit can be taken offline.

A subsystem application can be taken offline using coordinated state change, or forced offline withoutusing coordinated state change.

When the inh-map-ss command is entered for the subsystem, a coordinated shutdown is attempted.If the coordinated shutdown fails, a UIM is generated, indicating that the shutdown failed. If the forceparameter is specified, the subsystem is forced to shut down; a coordinated shutdown is not performed.

For coordinated state change, SCMG sends an SOR message to the mated subsystem and will start aTcoord timer (30 seconds). If SCMG receives an SOG message from the mated subsystem before theTcoord timer expires, SCMG will broadcast SSPs to the concerned point code group, send SBR/SSP,and take the subsystem offline. A UAM is generated, indicating that the subsystem is PROHIBITED.If the SOG is not received before Tcoord expires, then the inhibit request is denied and a UIM is generated.

When the subsystem is taken offline without coordinated state change, the EAGLE 5 ISS sendsSBR/SSPs. A UAM is generated, indicating that the subsystem is PROHIBITED.

When the EAGLE 5 ISS receives an SOR message from its mated subsystem, it will reply with an SOGmessage if both of the following conditions are met. If either of these conditions is not met, the EAGLE5 ISS will not reply to the SOR message.

• The local subsystem is available• The total load on the DSM subsystem is less than 45% of its capacity

Taking the Subsystem Application Online

Use the procedure in this section to take the subsystem application online.

1. Verify the state of the subsystem application - online or offline, by entering the rtrv-ss-applcommand.

tekelecstp 08-07-25 08:02:22 EST EAGLE5 42.0.0 APPL SSN STAT EIR 11 offline


If the EIR subsystem is online, this procedure does not need to be performed.

2. Display the operating status of the subsystem by entering the rept-stat-sccp command.3. Take the subsystem application online. Enter the chg-ss-appl command with the nstat=online

parameter.chg-ss-appl:appl=eir:nstat=online

4. Verify the changes by entering the rtrv-ss-appl command.

tekelecstp 08-07-25 08:02:22 EST EAGLE5 42.0.0 APPL SSN STAT EIR 11 online




5. Back up the new changes using the chg-db:action=backup:dest=fixed command.The following messages appear, the active Maintenance and Administration Subsystem Processor(MASP) appears first.


Taking the Subsystem Application Offline

Use the procedure in this section to take a subsystem application offline.

1. Verify the online or offline state of the subsystem application, by entering the rtrv-ss-appl command.

tekelecstp 08-07-25 08:02:22 EST EAGLE 42.0.0 APPL SSN STAT EIR 11 online


If the EIR subsystem application is offline, this procedure does not need to be performed.

2. Verify the operating status of the subsystem by entering the rept-stat-sccp command.3. Place the subsystem out of service. Specify the subsystem number displayed in the output in Taking

the Subsystem Application Online.inh-map-ss:ssn=11

rlghncxa03w 08-06-28 14:42:38 GMT EAGLE 42.0.0 Inhibit map subsystem command sent to all SCCP cards. Command Completed.;

4. Verify that the subsystem is out of service, by entering the rept-stat-sccp command.5. Take the subsystem offline. Enter the chg-ss-appl command with the nstat=offline parameter.

chg-ss-appl:appl=eir:nstat=offline

6. Verify the changes by entering the rtrv-ss-appl command.

tekelecstp 08-07-25 08:02:22 EST EAGLE 42.1.0 APPL SSN STAT EIR 11 offline


7. Back up the new changes using the chg-db:action=backup:dest=fixed command.



The following messages appear, the active Maintenance and Administration Subsystem Processor(MASP) appears first.


Provisioning the EIR Service Selectors

The procedures in this section describe how to add, change, and remove a service selector. Theinformation is indicated that is specific to EIR.

Refer to the Commands Manual for complete descriptions of the commands used in these procedures,including parameter names, valid values, and output examples for the commands.

Adding an EIR Service Selector

This procedure is used to add a service selector for the EIR feature.

The EIR feature must be enabled and turned on before an EIR service selector can be added.

1. Verify that the EIR feature is enabled and turned on, by entering the rtrv-ctrl-feat command.

If the EIR feature is enabled and turned on, the status of the EIR feature is on

rlghncxa03w 10-06-30 21:15:37 GMT EAGLE5 42.0.0The following features have been permanently enabled:Feature Name Partnum Status QuantityHC-MIM SLK Capacity 893012707 on 64EIR 893012301 on ----;

• If the EIR feature is enabled and turned on, continue with Step 2.• If the EIR feature is not enabled or turned on, go to the Enabling and Turning On the EIR Feature

procedure to enable and turn on the EIR feature. Then continue with Step 2.

2. Display the EIR service selectors in the database, using the rtrv-srvsel:serv=eir command.


GTII TT NP NAI SSN SNP SNAI SERV4 1 e214 intl 3 ---- ----- eir4 2 e214 intl * ---- ----- eir

SRV SELECTOR table is (4 of 20992) 1 % full;

3. Add the EIR service selector using the ent-srvsel command.

For example, enter a command like these:

ent-srvsel:serv=eir:tt=35:ssn=100:gtin=4:np=e214:nai=natl



ent-srvsel:serv=eir:tt=57:ssn=75:gtin=2

4. Verify the changes; enter the rtrv-srvsel command with the parameters and values used inStep 3.

rtrv-srvsel:serv=eir:tt=35:ssn=100:gtin=4:np=e214:nai=intl


GTIN TT NP NAI SSN SNP SNAI SERV4 35 e214 natl 100 ---- ----- eir


rtrv-srvsel:serv=eir:tt=57:ssn=75:gtin=2


GTIN TT NP NAI SSN SNP SNAI SERV2 57 --- ---- 75 ---- ----- eir


5. Back up the changes using the chg-db:action=backup:dest=fixed command.



Removing a Service Selector

This procedure is used to remove a service selector from the database.

1. Display the service selectors in the database, using the rtrv-srvsel command.

The serv, gtii, gtin, gtin24, tt, ssn, np, nai, npv, and naiv parameter values can be used to limit theamount of information displayed with the rtrv-srvsel command.

2. Remove the service selector from the database, using the dlt-srvsel command.

To remove a service selector, the gtii/gtin/gtin24, tt, and ssn parameter values must beentered as shown in the rtrv-srvsel output.

For example, enter a command like these:

dlt-srvsel:serv=eir:tt=35:ssn=100:gtin=4:np=e214:nai=natl

dlt-srvsel:serv=eir:tt=57:ssn=75:gtin=2



3. Verify the changes; enter the rtrv-srvsel command with the parameters and values used inStep 2.

4. Back up the changes, using the chg-db:action=backup:dest=fixed command.



Changing an Existing Non-EIR Service Selector to an EIR Service Selector

This procedure is used to change a non-EIR service selector to an EIR service selector for the EIRfeature.

The only parameters that can be changed using this procedure are:

:nserv – New DSM service type, EIR

:nsnp – An EIR service selector cannot contain an SNP value; if the service selector being changedcontains an SNP value, this value must be changed to none with this parameter.

:nsnai – An EIR service selector cannot contain an SNAI value; if the service selector being changedcontains an SNAI value, this value must be changed to none with this parameter.

The chg-srvsel command requires that the gtii/gtin/gtin24, tt, np, nai, npv, naiv, ssn, and servparameters be specified with the values shown in the rtrv-srvsel output for the service selectorbeing changed. If you want to change any of these parameter values for an EIR service selector, usethe Removing a Service Selector procedure to remove the existing service selector. Then use the Addingan EIR Service Selector procedure to add the new EIR service selector with the new parameterinformation.

1. Display the service selectors in the database using the rtrv-srvsel command.

rlghncxa03w 03-06-28 14:42:38 GMT EAGLE5 42.0.0GTII TT NP NAI SSN SNP SNAI SERV4 1 e214 intl 3 --- --- eir4 1 e214 intl 4 e164 intl gport4 1 e214 intl 5 e164 intl smsmr4 2 e214 intl * --- --- eir

GTIN TT NP NAI SSN SNP SNAI SERV2 75 --- --- 57 --- --- eir4 4 e214 natl 34 e164 intl gflex4 9 e214 natl 250 e164 intl gflex4 35 e214 natl 100 --- --- eir


• If the rtrv-srvsel output in Step 1 does not show any EIR service selectors, continue withStep 2.

• If the rtrv-srvsel output in Step 1 shows at least one EIR service selector, go to Step 3.



2. Verify that the EIR feature is enabled and turned on; enter the rtrv-ctrl-feat command.

• If the EIR feature is not enabled (does not appear in the command output ) or is not turned on,go to the Enabling and Turning On the EIR Feature procedure to enable and turn on the EIR feature.Then continue with Step 3.

• If the EIR feature is enabled and turned on, continue with Step 3.

3. Change the service selector, using the chg-srvsel command.For example, enter a command like the following one:

chg-srvsel:gtin=4:tt=4:np=e214:nai=natl:ssn=34:nsnp=none:nsnai=none:nserv=eir

If the snp or snai parameter values are shown as dashes in the rtrv-srvsel output, theseparameters cannot be specified with the chg-srvsel command. If the gtii/gtin/gtin24 parametervalue is 2, the np, nai, npv, and naiv parameters cannot be specified with the chg-srvselcommand.

If the gtii/gtin/gtin24 parameter value is 4, either the np and nai, or the npv and naivparameters must be specified with the chg-srvsel command. The np and nai parameters can bespecified in place of the npv and naiv parameters, and the npv and naiv parameters can be specifiedin place of the np and naiv parameters so long as parameter values be specified correspond to thevalues shown in the rtrv-srvsel output.

The gtii/gtin/gtin24, tt, ssn, np, nai, npv, or naiv parameters cannot be changed in this procedure.To change these parameters, use the Removing a Service Selector procedure to remove the serviceselector. Then use the Adding an EIR Service Selector procedure to re-enter the service selector as anEIR service selector.

4. Verify the changes; enter the rtrv-srvsel command with the parameters and values that wereused in Step 3.

5. Back up the changes using the chg-db:action=backup:dest=fixed command.

The following messages should appear; the active Maintenance and Administration SubsystemProcessor (MASP) appears first:


Changing the EIR Options

This procedure is used to change the EIR Global Response status, EIR Response Type, and EIR IMSICheck status option values with the chg-gsmopts command. The chg-gsmopts command usesthese parameters to detect circular routing in the system. See EAGLE 5 EIR GSM Options Commands.

Refer to the chg-gsmopts command description in the Commands Manual for valid parameter values,input examples, and rules for entering the command correctly.



1. Verify that the EIR feature is enabled and turned on; enter the rtrv-ctrl-feat command.

rlghncxa03w 09-06-29 16:40:40 EST EAGLE5 41.1.0 The following features have been permanently enabled: Feature Name Partnum Status Quantity HC-MIM SLK Capacity 893012707 on 64 EIR 893012301 on ----;

• If the EIR feature is not enabled (the EIR entry does not appear in the output) or is not turnedon, go to the Enabling and Turning On the EIR Feature procedure to enable and turn on the EIRfeature. Then continue with Step 2.

• If the EIR feature is enabled and turned on, continue with Step 2.

2. Display the status of the EIR options; enter the rtrv-gsmopts command.3. Change the EIR options by entering the chg-gsmopts command with at least one of the EIR option

parameters.4. Verify the changes; enter the rtrv-gsmopts command.5. Back up the changes using the chg-db:action=backup:dest=fixed command.

These messages should appear; the active Maintenance and Administration Subsystem Processor(MASP) appears first:

BACKUP (FIXED) : MASP A - Backup starts on active MASP.BACKUP (FIXED) : MASP A - Backup on active MASP to fixed disk complete.BACKUP (FIXED) : MASP A - Backup starts on standby MASP.BACKUP (FIXED) : MASP A - Backup on standby MASP to fixed disk complete.

Configuring EIR S13/S13’ Interface Support

This procedure configures the EIR S13/S13’ Interface Support feature. Step 5 through Step 8 configurethe DEIR connection.

1. Enable the EIR S13/S13’ Interface Support feature with the enable-ctrl-feat command.

enable-ctrl-feat:partnum=893042401:fak=<FeatureAccessKey>

2. Turn on the EIR S13/S13’ Interface Support feature with the chg-ctrl-feat command.

chg-ctrl-feat:partnum=893042401:status=on

3. Provision the S13 card (DEIRHC).

ent-card:loc=1101:type=dsm:appl=deirhc

4. Configure Port A and B of the S13 card.

chg-ip-lnk:port=a:submask=255.255.255.0:mcast=yes:ipaddr=192.168.120.11:loc=1101:duplex=full:speed=100

chg-ip-lnk:port=b:submask=255.255.255.0:mcast=no:ipaddr=10.248.13.11:loc=1101:duplex=full:speed=100

5. Enter the HOST information.



ent-ip-host:host=hss:ipaddr=10.248.13.11:type=local:realm=abcdefg.com

ent-ip-host:host=lmno:ipaddr=10.248.13.9:type=remote:realm=lmnopq.com

ent-ip-host:host=lmno3:ipaddr=10.248.13.3:type=remote:realm=lmnopq.com

6. Enter the SCTP Association.

ent-assoc:aname=assoc1:lhost=hss:lport=5555:rhost=lmno:rport=5556

ent-assoc:aname=assoc2:lhost=hss:lport=5557:rhost=lmno3:rport=5558

7. Enter the Diameter Connection.

ent-dconn: dcname=dcon1:aname=assoc1

ent-dconn: dcname=dcon2:aname=assoc2

8. Open the Diameter Connection.

chg-assoc:aname=assoc1:open=yes

chg-assoc:aname=assoc2:open=yes

Activating the EIR Local Subsystem

The procedure in this section explains how to activate the EIR local subsystem.

When all feature configuration is complete, the EIR subsystem application must taken online and thelocal subsystem must be activated to allow it to begin operation.

When the local subsystem operating state is Inhibited, the chg-ss-appl command can be used tochange the online or offline database state of the subsystem. The rtrv-ss-appl command displaysthe online or offline provisioned value.

When the first Service Module card is loaded, the local subsystem operating state tells whether thesubsystem should be considered allowed (online) or inhibited (offline). This is a database state. If thecommand is accepted, then the change is made to the tables and can be read after an init-syscommand is entered to initialize the system.

When the Service Module cards are in-service and the subsystem application is online, thealw/inh-map-ss commands can be used to change the dynamic operating state of the local subsystemto allowed or inhibited. The inh-map-ss command does not necessarily force a state change, becauseit can fail if the mate does not send an SOG. The force=yes parameter must be specified to bypass theSOR/SOG exchange and inhibit immediately. (There is no rtrv-map-ss command.)

The procedures in Changing the State of a Subsystem Application explain how to take a local subsystemonline and offline.

Table 21: Subsystem Allow/Inhibit

OnlineOfflineCommand\ Subsystem State

Attempts to make the localsubsystem active.

Command is rejected because thesubsystem must be online to bein the Allowed state.

alw-map-ss



OnlineOfflineCommand\ Subsystem State

Attempts to inhibit the localsubsystem. Use of the force=yes

Command accepted, but noaction because offline impliesinhibited.

inh-map-ss

parameter bypasses theSOR/SOG exchange and inhibitsimmediately.

No change to local subsystemstatus in the database.

Changes local subsystem statusto online.

chg-ss-appl:appl=eir:nstat=online

Changes local subsystemdatabase status to offline.

Command is rejected because thesubsystem must be inhibited togo offline.

chg-ss-appl:appl=eir:nstat=offline

1. Display the online/offline status of the EIR subsystem application, by entering the rtrv-ss-applcommand.

tekelecstp 08-07-25 08:02:22 EST EAGLE5 39.2.0 APPL SSN STAT EIR 11 offline


2. Change the EIR subsystem status to online.chg-ss-appl:appl=eir:nstat=online

3. Enter the command to allow the EIR subsystem to begin operation.alw-map-ss:ssn=<EIR ssn>

integrat40 08-05-24 10:37:22 EST EAGLE5 39.2.0 Allow map subsystem command sent to all SCCP cards. Command Completed.;

4. Display and verify the operating status of the EIR subsystem, by entering the rept-stat-sccpcommand.



Chapter

5EIR Measurements

This chapter describes measurements that can becollected and generated for the EIR feature.

Topics:

• EIR Measurements.....61


EIR Measurements

The EAGLE 5 Measurements system supports the collection and retrieval of measurements related tothe EIR feature. The EIR measurements can be collected and reported with either of the followingcollection methods:

• The Measurements Platform feature enabled and the Measurements Platform collection option on

• The E5-OAM Integrated Measurements feature enabled and on and the E5-OAM IntegratedMeasurements collection option on

15 Minute Measurements collection can be used with Measurements Platform or E5-OAM IntegratedMeasurements.

OAM-based measurements collection is not available for EIR.

Refer to Measurements for descriptions of collection methods, measurements, and measurementsreports.

Refer to Commands Manual for descriptions of the commands used to enable and turn on features, turnon measurements collection options, and schedule and generate measurements reports.

Refer to the procedures in Database Administration Manual - System Management to configure theMeasurements Platform feature or E5-OAM Integrated Measurements feature and the EAGLE OA&MIP Security feature for use with EIR.

The EIR feature must be enabled to provision scheduling of the EIR measurements reports. The EIRfeature must be turned on for full measurements collection functions to operate for the feature.

Table 22: Pegs for Per System EIR Measurements describes eight measurement registers that are usedspecifically for the EIR feature. The registers are reported in two Per System reports for the EIR entitytype: Hourly Maintenance Measurements (MTCHEIR) and Daily Maintenance Measurements(MTCDEIR). The data for these registers originates on the Service Module cards.

For IMEIs present in multiple lists, the appropriate measurement peg is determined by the logic inTable 3: Logic for IMEIs in Multiple Lists and the outcome of the IMSI Check.

Table 22: Pegs for Per System EIR Measurements

UnitTypeDescriptionEvent Name

Peg countSystemTotal number of MAP_CHECK_IMEI messagesreceived.

IMEIRCV

Peg countSystemTotal number of searches that resulted in a matchwith a "White Listed" IMEI.

WHITEIMEI

Peg countSystemTotal number of searches that resulted in a matchwith a "Gray Listed" IMEI.

GRAYIMEI

Peg countSystemTotal number of searches that resulted in a matchwith a "Black Listed" IMEI.

BLACKIMEI


EIR MeasurementsEIR User's Guide

UnitTypeDescriptionEvent Name

Peg countSystemTotal number of searches that resulted in a matchwith a "Black Listed" IMEI, but were allowed dueto IMSI Check match.

BLKALIMEI

Peg countSystemTotal number of searches that resulted in a matchwith a "Black Listed" IMEI, and the IMSI in thedatabase did not match the IMSI in the message.

BLKNALIMEI

Peg countSystemTotal number of searches that resulted in a matchwith an "unknown" IMEI.

UNKNIMEI

Peg countSystemTotal number of searches that resulted in no matchin the database.

NOMTCHIMEI

Measurement Registers for EIR S13/S13' Support Feature

Eight new measurement registers are added for the EIR S13/S13' Interface Support feature and aresupported on a per Diameter connection basis. These new measurement registers listed in Table 23:EIR S13/S13' Interface Support Measurement Registers are supported only with the Measurements Platformfeature enabled and the Measurements Platform option on. The data for these registers originate fromthe S13 cards running DEIRHC GPL. The existing SCTPASSOC and SCTPCARD measurement registersare also supported by the DEIRHC GPL.

Table 23: EIR S13/S13' Interface Support Measurement Registers

DescriptionRegister

Total number of ME-Identity-Check requests (ECR) received by the EIRECRRCV

Total number of searches that resulted in a match with a whitelisted IMEIWHITEIMEI

Total number of searches that resulted in a match with a graylisted IMEIGRAYIMEI

Total number of searches that resulted in a match with a blacklisted IMEIBLACKIMEI

Total number of searches that resulted in a match with a blacklisted IMEI, butwere allowed due to IMSI Check match

BLKALIMEI

Total number of searches that resulted in a match with a blacklisted IMEI, andthe IMSI in the database did not match the IMSI in the message

BLKNALIMEI

Total number of searches that resulted in a match with an Unknown IMEIUNKNIMEI

Total number of searches that resulted in no match in the databaseNOMTCHIMEI

Measurement Reports for EIR S13/S13' Support Feature

The new measurement registers are reported in new DEIR SYS and DEIR DCONN measurementreports: Hourly Maintenance Measurements on S13 System (MTCHDEIR) and Daily MaintenanceMeasurements on S13 System (MTCDDEIR). The MTCHDEIR and MTCDDEIR reports are transferredto an FTP server.



Table 24: DEIR Measurement Reports

Reportssupportedon GPLs

DisplayRetentionPeriodReporting modesReport

MCP /MCPHC /OAMHC

FTP24 hours forHourly data

7 days for Dailydata

Hourly

Daily

On-demand,Scheduled(MTCHDEIR/MTCDDEIR)

DEIR SYS SystemWide report Hourly(60 minute) andDaily (24 hour)

MCP /MCPHC /OAMHC

FTP24 hours forHourly data

7 days for Dailydata

Hourly

Daily

On-demand,Scheduled(MTCHDEIR/MTCDDEIR)

DEIR DCONNreport Hourly (60minute) and Daily(24 hour)



Chapter

6Maintenance

This chapter describes commands and reports thatcan be used for EIR maintenance, including statusreporting and problem identification.

Topics:

• EIR Alarms.....65• EIR UIMs.....66• Maintenance Commands.....70• EAGLE 5 ISS Debug Commands.....71• Status Reporting and Problem Identification.....72


EIR Alarms

Table 25: EIR UAMs lists the UAMs that specifically support the EIR feature. All EIR-related UAMsare generated to the Maintenance Output Group.

Refer to Unsolicited Alarm and Information Messages for complete descriptions and corrective proceduresfor all UAMs.

Refer to EPAP Alarms and Maintenance on the E5-APP-B Platform or EPAP Alarms on the T1200 Platformfor descriptions and corrective procedures for MPS-related alarms.

Table 25: EIR UAMs

Message TextSeverityUAM ID

EIR Subsystem is not availableCritical0455

EIR Subsystem is disabledCritical0456

EIR Subsystem normal, card(s) abnormalMinor0457

EIR Subsystem is availableNone0458

EIR Subsystem is removedNone0459

DEIR System is not availableCritical0483

DEIR System normal, card(s) abnormalMajor0484

DEIR System is availableNormal0485

DEIR Threshold -Level1 exceededMinor0486

DEIR Threshold -Level2 exceededMajor0487

DEIR Threshold Condition ClearedNormal0488

DEIR capacity exceededCritical0489

DEIR normalNormal0490

Connection TPS exceedMajor0491

Connection TPS normalNormal0492

Diameter Connection DownMajor0493

Diameter Connection UPNormal0494

Diameter Connection ClosedNormal0495

DEIR System is removedNormal0496


MaintenanceEIR User's Guide

EIR UIMs

Table 26: EIR UIMs lists the UIMs that specifically support the EIR feature. Refer to Unsolicited Alarmand Information Messages for complete descriptions of all UIM text, formats, and recovery procedures.

Table 26: EIR UIMs

RecoveryDescriptionTextUIM

NoneAn inh-map-ss command is alreadyentered and queued.

Inh EIR SS requestalreadyoutstanding

1030

Enter the inh-map-ss commandwith the force parameter.

The inh-map-ss command wasunsuccessful in taking the EIRsubsystem off-line.

Failure InhibitingEIR SS

1031

NoneThe EIR subsystem received aCheck-IMEI message in which the

Invalid Length forMap IMEIParameter

1102

Map IMEI parameter had an invalidlength.

NoneThe EIR subsystem received aCheck-IMEI message in which theMap IMEI parameter is not present

LSS:No Map IMEIParameter present

1103

For information about eirgrsp,refer to the chg-gsmoptscommand in Commands Manual

The EIR Global Response Type is on.The EIR Global Response Type is setby the chg-gsmopts command andthe eirgrsp parameter.

GSMOPTS: EIRGlobal Response isON

1306

For information about eirgrsp,refer to the chg-gsmoptscommand in Commands Manual.

The EIR Global Response Type is off.The EIR Global Response Type is setby the chg-gsmopts command andthe eirgrsp parameter.

GSMOPTS: EIRGlobal Response isOFF

1307

Diameter message parsing FAILS.Diameter msgdecode failed

1133

Examples:

• ECR Message does not have IMEIAVP or value in IMEI AVP.

• CER Message does not havemandatory AVP present.

• DPR message received does nothave disconnect cause AVPpresent.

Output Group: LINK

Diameter message Encoding FAILS.Output Group: LINK

Diameter msgencode failed

1134



RecoveryDescriptionTextUIM

Diameter message was received whichis not supported in the EAGLE 5 or

Invalid DiameterMsg received

1135

an error exists in Diameter messageheader. Output Group: LINK

Total Diameter message lengthspecified in diameter header does not

Invalid DiameterMsg length

1136

match with the actual diametermessage length. Output Group: LINK

AVP decoding failed. Output Group:LINK

Diameter AVPDecode Fail

1137

ConnectionRefused

1138 • Origin host and Origin RealmAVPs in CER message does notmatch with the host and realmvalues provisioned in theIPAPSOCK table.

• Source IP Address of the CERmessage does not match with theIP Address present in theHost-IP-Address AVP.

Error Cause:

• Origin Host Mismatch• Origin Realm Mismatch• IP Address Mismatch• No common application

Output Group: LINK

DEIR Global Response is set toWhitelist/Graylist/Blacklist/Unknown

DEIR GlobalResponse is ON

1139

from OFF in DEIROPTS table. OutputGroup: APSS

DEIR Global Response is set to OFFfrom

DEIR GlobalResponse is OFF

1140

Whitelist/Graylist/Blacklist/Unknownin DEIROPTS table. Output Group:APSS

UIM Format for EIR S13/S13' Support Feature

The UIMs added for the EIR S13/S13' Interface Support feature are displayed in the format shown inTable 27: UIM format for EIR S13/S13' Support Feature. The maximum length of origin host/originrealm/AVP code and error to be displayed in the UIM is 32 bytes.



Table 27: UIM format for EIR S13/S13' Support Feature

UIM format for EIR S13/S13' Support Feature

RPT_DEIR_MSG (I-85)Literal



UIM format for EIR S13/S13' Support Feature

1 2 3 4 5 6 7 8

Format

12345678901234567890123456789012345678901234567890123456789012345678901234567890

xxxx.xxxx CARD cccc,ppp INFO ’text’ DCNAME= xxxxxxxxxxxxxxx Command Code = xxxx Error Cause=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

xxxx.xxxx CARD cccc,ppp INFO ’text’ DCNAME= xxxxxxxxxxxxxxx Command Code = xxxx Origin Realm= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Error Cause=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

xxxx.xxxx CARD cccc,ppp INFO ’text’ DCNAME= xxxxxxxxxxxxxxx Command Code = xxxx Origin Host= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Error Cause=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

1 2 3 4 5 6 7 8

OutputExamples

12345678901234567890123456789012345678901234567890123456789012345678901234567890

0014.1133 CARD 1103,B INFO Diameter msg decode failed DCNAME= Con1 Command Code = 324 Error Cause= Unsupported appl id

Report Date:10-10-12 Time:16:20:19

1 2 3 4 5 6 7 812345678901234567890123456789012345678901234567890123456789012345678901234567890

0014.1138 CARD 1103,B INFO Connection Refused DCNAME= Con3 Command Code = 324 (R) IP Address=10.248.4.5 Error Cause= IP Addr Mismatch

Report Date:03-22-13 Time:16:20:19



Maintenance Commands

The following commands can be used for maintenance when an EPAP-related feature is on.

Refer to Commands Manual for complete descriptions of the commands, including parameters, validparameter values, rules for using the commands, and output examples.

Table 28: Maintenance Commands

DescriptionCommand

Reports the status of system entities, including cards. The output includes thenumber of Service Module cards that are in service (IS-NR) and how manyare in another state (IS-ANR, OOS-MT, OOS-MT-DSBLD).

rept-stat-sys

Reports operating status of services and subsystems, CPU usage, and ServiceModule card status. When the loc parameter is specified, the command displays

rept-stat-sccp

detailed card traffic statistics, including cards that are denied SCCP service.See the section in this manual that describes the use of the rept-stat-sccpcommand.

Displays the overall status of the EPAP application running on the MPS(multi-purpose server). Command output for the various reports of this

rept-stat-mps

command include overall MPS alarm status and card status, and status for aspecific Service Module card when a feature is on.

Includes a summary of any trouble notifications (UAMs) for local subsystems,cards, and linksets. The severity of each alarm is indicated in the output report.

rept-stat-trbl

Displays the alarm counts and totals for local subsystems and Service Moculecard/EPAP IP links.

rept-stat-alm

Displays the status information for the EAGLE 5 ISS databases. This includesthe level information for each Service Module card, and for the active and

rept-stat-db

standby EPAP RTDB. The command reports database exception status suchas corrupted, incoherent, or inconsistent, as well as providing the birth datesand levels. It shows the status of each PDB and RTDB when an EPAP-relatedfeature is enabled.

Retrieves table use capacity summary information. For each table listed, thenumber of table entry elements in use and the total allowed number of table

rtrv-tbl capacity

elements is presented, along with a percent (%) full value. Information isshown for some tables only if the feature that uses the table is enabled.

The inh-card command is used to change the operating state of the cardfrom In-Service Normal (IS-NR) to Out-of-Service Maintenance-Disabled

inh-card/alw-card

(OOS-MT-DSBLD). A craftsperson then can test the card or physically removeit from the shelf.

The alw-card command is used to change the card from OOS-MT-DSBLD(Out-of-Service Maintenance-Disabled) to IS-NR (In-Service Normal) if cardloading is successful.



DescriptionCommand

Used to allow and inhibit reporting of alarms for a given device, includingthe Service Module card ports. The commands allow both Port A and Port B

inh-alm/unhb-alm

to be specified. Inhibited alarms will not generate UAMs or cause alarmindicators to be turned on. All rept-stat-xxx commands continue to displaythe alarms with an indication that the device has its alarms inhibited.

Retrieves Entity data, DN data, IMEI data, IMSI data, TN data, NPANXX data,and LRN data from the RTDB on an active Service Module card.

rtrv-data-rtdb

If the loc parameter is specified and the target card is an active Service Modulecard, the RTDB data is retrieved from that card.

If the loc parameter is not specified, the RTDB data is retrieved on the activeService Module card that has the lowest IMT address.

The RTDB status on the active Service Module card can be coherent orincoherent.

rept-stat-sccp

The rept-stat-sccp command provides statistics for Service Module cards and for the servicesthat execute on the cards. The statistics can be displayed for all Service Module cards, or for a specifiedcard.

Refer to the Commands Manual for a description of the rept-stat-sccp command, includingparameter names, valid values, and output examples for the command.

EIR Feature Statistics

The rept-stat-sccp command counts and displays the following statistics when the EIR featureis enabled and turned on (WARNINGS and FORWARD TO GTT are not reported for EIR):

• TOTAL = the total number of messages that contain a CheckIMEI MAP Operation.• SUCCESS = the number of messages that passed CheckIMEI processing• ERRORS = the number of messages that were not counted in SUCCESS.

EAGLE 5 ISS Debug Commands

The Commands Manual contains descriptions of debug commands that can be used in assessing andmodifying system status and operation. Most of the debug commands are used only under the directionof Tekelec support personnel.

Refer to the Commands Manual for a complete description of the debug commands, including theent-trace command.

The ent-trace command can be used for EIR to provide a trap-and-trace function for MSUs on theService Module cards.

• Trap Message will be performed on a Query message with:

• A decode error, and Trace-On-Error set



• IMEI match• IMSI match• SSP• GT

• Because the Response message will not contain the IMEI or IMSI information, it will be trapped ifthe Query message was trapped.

Caution: This command can cause OAM to reset if too many MSUs are trapped.

A trace must be set on all Service Module cards; specify the card=sccp-all parameter. Use a repetitionparameter (rep) to control the number of MSUs that are trapped.

The 14-digit IMEI is a trapping field. MSUs are trapped only when the SDS count (REP) is positive. Ifa Query and Response are both trapped, that is 2 SDS counts.

MSUs that satisfy any trigger criteria are trapped on the Service Module card, forwarded to OAM,and displayed.

Status Reporting and Problem Identification

EAGLE 5 commands can be used to obtain status and statistics for the EAGLE 5 system, the EPAPsystems, system devices including Service Module cards, EPAP-related features, local subsystems,and SCCP services.

Refer to Commands Manual for complete descriptions of the commands, including parameters andvalid values, rules for using the commands correctly, and output examples.

Refer to Unsolicited Alarm and Information Messages for descriptions and recovery procedures for UAMsand UIMs.

Refer to EPAP Administration Manual for descriptions of EPAP functions and operation.

Refer to EPAP Alarms on the T1200 Platform or EPAP Alarms and Maintenance on the E5-APP-B Platformfor descriptions and recovery procedures for EPAP alarms.

Refer to the appropriate Feature Manual for information about the functions and operation ofEPAP-related features.

Table 29: Status Reporting for EPAP-Related Features

CommandReports, Status, and Statistics

EAGLE 5 ISS

rept-stat-sysMaintenance Status Report - indicates whetherMaintenance, Routing, and SCCP Baselines havebeen established.

rept-stat-sysAlarms and operating state for system devices,including Service Module ( "SCCP") cards.




rept-stat-almUnsolicited Alarm Messages (UAMs) andUnsolicited Information Messages (UIMs)

rept-stat-trbl

EPAP/MPS (from the EAGLE 5 ISS)

rept-stat-mpsEPAP code version and operating state for eachEPAP.

rept-stat-mpsMPS hexadecimal alarm strings for the active andstandby EPAPs.

rept-stat-mpsOperating state and alarm status of equippedService Module cards and their DSM ports andIP connections. rept-stat-mps:loc=<Service Module card location>

rept-stat-mps:loc=<Service Modulecard location>

Amount of memory used by the RTDB on thespecified card, as a percent of available ServiceModule card memory.

rept-stat-dbEPAP Provisioning Database (PDB), EPAP RealTime Database (RTDB), and Service Module card

rept-stat-db:db=mpsRTDB status information - Coherent, birthdate(date and time of creation), and exception(condition when a problem was detected).

Service Module Cards, EPAP-Related Features, Services, Local Subsystems

rept-stat-sccpStatus of the Service Module cards, and theservices executing on the cards for EPAP-relatedfeatures that are turned on. Includes ServiceReport, Subsystem Report, and Alarm Status;Total Service Statistics.

rept-stat-mps:loc=<Service Modulecard location>

Operating state and alarm status of equippedService Module cards and their DSM ports andIP connections; EPAP-related feature status percard.

rept-stat-sysAlarms and operating state for Service Module ("SCCP") cards.

rept-stat-mps

rept-stat-sccpAny cards that are denied SCCP service.

rept-stat-sccp:loc=<Service Modulecard location>

Detailed view of the status of SCCP servicesprovided by the specified Service Module card.Includes Card Alarm Status, Card ServiceStatistics

rept-stat-sccp:mode=perfGeneral SCCP traffic performance for ServiceModule cards. Message rates for TVGperformance.




rept-stat-sccpStatistics for EPAP-related feature localsubsystems - Subsystem Report

rept-stat-sccpStatistics for EPAP-related features

EPAP Status and Alarm Reporting

Because EPAP has no direct means of accepting user input or displaying output messages on EAGLE5 ISS terminals, EPAP maintenance, measurements, and status information are routed through aService Module card. EPAP sends two types of messages to the Service Module card: EPAP MaintenanceBlocks and DSM Status Requests and DSM Status Messages. Each message type is discussed in thefollowing sections.

EPAP Maintenance Blocks

The EPAP forwards all status and error messages to the Service Module cards in maintenance blocks.Maintenance blocks are asynchronously sent whenever the EPAP has something to report. The statusinformation that is displayed when a rept-stat-mps command is issued includes information thatcame from the maintenance blocks.

The active EPAP generates and sends maintenance blocks to the primary Service Module card. Onemaintenance block is sent as soon as the IP link is established between the active EPAP and the primaryService Module card. Additional maintenance blocks are sent whenever the EPAP needs to report anychange in status or error conditions. The information returned in maintenance blocks is included inthe output of the rept-stat-mps and rept-stat-sccp commands.

The EPAP sends maintenance blocks that contain at least the following information:

• Status of EPAP 'A' - actual states are active, standby, and down (inoperative). Maintenance blocksinclude a field for this information so that it can be available for the output of the rept-stat-mpscommand.

• Status of EPAP 'B' - actual states are active, standby, and down (inoperative). Maintenance blocksinclude a field for this information so that it can be available for the output of the rept-stat-mpscommand.

• Identification of Active EPAP - a field to identify the active EPAP.

• Congestion Indicator - an indicator showing provisioning link congestion. The link between theEPAPs and the external source of provisioning data can become congested in high-provisioningtraffic situations. When this occurs and subsequently as the congestion clears, the EPAP sendsmaintenance blocks to the Service Module card.

• Alarm Conditions - an error code field. If the EPAP needs to report an alarm condition, it puts anappropriate UAM identifier in this field.

• Current MPS Database Size - a field indicating the current RTDB size. The Service Module carduses this information to calculate the percentage of memory used by the RTDB.



DSM Status Requests and DSM Status Messages

When the EPAP needs to know the status of a Service Module card, it sends a DSM Status Request toall Service Module cards, and each Service Module card returns its status to the EPAP.

Service Module cards send a DSM Status Message to the EPAP when any the following events occurin the Service Module card:

• The Service Module card is booted.

• The Service Module card receives a DSM Status Request message from the EPAP

• The Service Module card determines that it needs to download the entire RTDB; for example, theService Module card determines that the RTDB needs to be downloaded because it is totallycorrupted, or a craftsperson requests that the RTDB be reloaded. The Service Module card sendsa Full Download Request message to the EPAP

• The Service Module card starts receiving RTDB downloads or updates. When a Service Modulecard starts downloading the RTDB or accepting updates, it sends a DSM Status Message informingthe EPAP of the first record received. This helps the EPAP keep track of downloads in progress.

The DSM Status Message provides the following information to the EPAP:

• DSM Memory Size. When the Service Module card is initialized, it determines the amount ofmemory present. The EPAP uses the value to determine if the Service Module card has enoughmemory to hold the RTDB.

Refer to the Dimensioning Guide for EPAP Advanced DB Features for important information on thedimensioning rules and the Service Module card database capacity requirements.

• Load Mode Status. This indicator indicates whether or not a sufficient number of the IS-NR(In-Service Normal) LIMs have access to SCCP services.



Glossary

C

Calling Party Address - The pointcode and subsystem number that

CgPA

originated the MSU. This pointcode and subsystem number arecontained in the calling partyaddress in the SCCP portion of thesignaling information field of theMSU. Gateway screening uses thisinformation to determine if MSUsthat contain this point code andsubsystem number area allowed inthe network where the EAGLE islocated.

Capability Point CodeCPC

A capability point code used by theSS7 protocol to identify a group offunctionally related STPs in thesignaling network.

Comma-separated valuesCSV

The comma-separated value fileformat is a delimited data formatthat has fields separated by thecomma character and recordsseparated by newlines (a newlineis a special character or sequenceof characters signifying the end ofa line of text).

D

Destination Point Code - DPCrefers to the scheme in SS7

DPC

signaling to identify the receivingsignaling point. In the SS7 network,the point codes are numericaddresses which uniquely identifyeach signaling point. This point


D

code can be adjacent to the EAGLE,but does not have to be.

E

Equipment Identity RegisterEIR

A network entity used in GSMnetworks, as defined in the 3GPPSpecifications for mobile networks.The entity stores lists ofInternational Mobile EquipmentIdentity (IMEI) numbers, whichcorrespond to physical handsets(not subscribers). Use of the EIRcan prevent the use of stolenhandsets because the networkoperator can enter the IMEI of thesehandsets into a 'blacklist' andprevent them from being registeredon the network, thus making themuseless.

EAGLE Provisioning ApplicationProcessor

EPAP

Features that require EPAPconnection and use the Real Time

EPAP-related features

Database (RTDB) for lookup ofsubscriber information.

• ANSI Number PortabilityQuery (AINPQ)

• ANSI-41 AnalyzedInformationQuery – no EPAP/ELAP(ANSI41 AIQ)

• Anytime Interrogation NumberPortability (ATI NumberPortability, ATINP)

• AINPQ, INP, G-Port SRI Queryfor Prepaid, GSM MAP SRIRedirect, IGM, and ATINPSupport for ROP

• A-Port Circular RoutePrevention (A-Port CRP)


GlossaryEIR User's Guide

E

• Equipment Identity Register(EIR)

• G-Flex C7 Relay (G-Flex)• G-Flex MAP Layer Routing

(G-Flex MLR)• G-Port SRI Query for Prepaid• GSM MAP SRI Redirect to

Serving HLR (GSM MAP SRIRedirect)

• GSM Number Portability(G-Port)

• IDP A-Party Blacklist• IDP A-Party Routing• IDP Relay Additional

Subscriber Data (IDPR ASD)• IDP Relay Generic Routing

Number (IDPR GRN)• IDP Service Key Routing (IDP

SK Routing)• IDP Screening for Prepaid• INAP-based Number Portability

(INP)• Info Analyzed Relay Additional

Subscriber Data (IAR ASD)• Info Analyzed Relay Base (IAR

Base)• Info Analyzed Relay Generic

Routing Number (IAR GRN)• Info Analyzed Relay Number

Portability (IAR NP)• INP Circular Route Prevention

(INP CRP)• IS41 Mobile Number Portability

(A-Port)• IS41 GSM Migration (IGM)• MNP Circular Route Prevention

(MNPCRP)• MO-based GSM SMS NP• MO-based IS41 SMS NP• MO SMS Generic Routing

Number (MO SMS GRN)• MO- SMS B-Party Routing• MO SMS IS41-to-GSM

Migration• MT-based GSM SMS NP



E

• MT-based GSM MMS NP• MT-based IS41 SMS NP• MTP Routed Messages for

SCCP Applications (MTP Msgsfor SCCP Apps)

• MTP Routed GatewayScreening Stop Action(MTPRTD GWS Stop Action)

• Portability Check for MO SMS• Prepaid IDP Query Relay (IDP

Relay, IDPR)• Prepaid SMS Intercept Phase 1

(PPSMS)• Service Portability (S-Port)• S-Port Subscriber

Differentiation• Triggerless ISUP Framework

Additional Subscriber Data (TIFASD)

• Triggerless ISUP FrameworkGeneric Routing Number (TIFGRN)

• Triggerless ISUP NumberPortability (TIF NP)

• Triggerless ISUP FrameworkNumber Substitution (TIF NS)

• Triggerless ISUP FrameworkSCS Forwarding (TIF SCSForwarding)

• Triggerless ISUP FrameworkSimple Number Substitution(TIF SNS)

• Voice Mail Router (V-Flex)

F

File Transfer ProtocolFTP

A client-server protocol that allowsa user on one computer to transferfiles to and from another computerover a TCP/IP network.

Feature Test Plan

G



G

Gigabyte — 1,073,741,824 bytesGB

GSM Flexible numberingG-Flex

A feature that allows the operatorto flexibly assign individualsubscribers across multiple HLRsand route signaling messages,based on subscriber numbering,accordingly.

GSM Mobile Number PortabilityG-Port

A feature that provides mobilesubscribers the ability to changethe GSM subscription networkwithin a portability cluster, whileretaining their original MSISDN(s).

Global System for MobileCommunications

GSM

A second generation digital PCSmobile phone standard used inmany parts of the world.

Global Title TranslationGTT

A feature of the signalingconnection control part (SCCP) ofthe SS7 protocol that the EAGLEuses to determine which servicedatabase to send the query messagewhen an MSU enters the EAGLEand more information is needed toroute the MSU. These servicedatabases also verify calling cardnumbers and credit card numbers.The service databases are identifiedin the SS7 network by a point codeand a subsystem number.

Graphical User InterfaceGUI



G

The term given to that set of itemsand facilities which provide theuser with a graphic means formanipulating screen data ratherthan being limited to characterbased commands.

H

Home Location RegisterHLR

A component within the SwitchingSubsystem of a GSM network. TheHLR database is the centraldatabase within the GSMarchitecture. This is whereinformation about the mobilecommunications subscribers whoare assigned to a specific locationarea is stored. The subscriber datais used to establish connections andcontrol services. Depending on thenetwork size, the number ofsubscribers and the networkorganization, a number of HLRscan exist within a GSM network.

I

International Mobile EquipmentIdentifier

IMEI

International Mobile SubscriberIdentity

IMSI

A unique internal network IDidentifying a mobile subscriber.International Mobile StationIdentity

Intelligent PeripheralIP

Internet Protocol

IP specifies the format of packets,also called datagrams, and theaddressing scheme. The networklayer for the TCP/IP protocol suite



I

widely used on Ethernet networks,defined in STD 5, RFC 791. IP is aconnectionless, best-effort packetswitching protocol. It providespacket routing, fragmentation andre-assembly through the data linklayer.

Integrated Services DigitalNetwork

ISDN

Integrates a number of services toform a transmission network. Forexample, the ISDN networkintegrates, telephony, facsimile,teletext, Datex-J, video telephonyand data transfer services,providing users with variousdigital service over a singleinterface: voice, text, images, andother data.

Integrated Signaling SystemISS

L

Local Number PortabilityLNP

The ability of subscribers to switchlocal or wireless carriers and stillretain the same phone number.

Local SubsystemLSS

M

Mated Application PartMAP

Mobile Application Part

An application part in SS7signaling for mobilecommunications systems.

Maintenance and AdministrationSubsystem Processor

MASP



M

The Maintenance andAdministration SubsystemProcessor (MASP) function is alogical pairing of the GPSM-II cardand the TDM card. The GPSM-IIcard is connected to the TDM cardby means of an Extended BusInterface (EBI) local bus.

The MDAL card contains theremovable cartridge drive andalarm logic. There is only oneMDAL card in the Maintenanceand Administration Subsystem(MAS) and it is shared between thetwo MASPs.

Megabyte — A unit of computerinformation storage capacity equalto 1,048, 576 bytes.

MB

Multi-Purpose ServerMPS

The Multi-Purpose Server providesdatabase/reload functionality anda variety of high capacity/highspeed offboard database functionsfor applications. The MPS residesin the General Purpose Frame.

Messages Per Second

A measure of a message processor’sperformance capacity. A messageis any Diameter message (Requestor Answer) which is received andprocessed by a message processor.

Mobile StationMS

The equipment required forcommunication with a wirelesstelephone network.

Mobile Switching CenterMSC



M

An intelligent switching system inGSM networks. This systemestablishes connections betweenmobile communicationssubscribers.

Mobile Station InternationalSubscriber Directory Number

MSISDN

The MSISDN is the networkspecific subscriber number of amobile communications subscriber.This is normally the phone numberthat is used to reach the subscriber.Mobile Subscriber IntegratedServices Digital Network [Number]Mobile Station InternationalSubscriber Directory Number. Theunique, network-specific subscribernumber of a mobilecommunications subscriber.MSISDN follows the E.164numbering plan; that is, normallythe MSISDN is the phone numberthat is used to reach the subscriber.

Message Signal UnitMSU

The SS7 message that is sentbetween signaling points in the SS7network with the necessaryinformation to get the message toits destination and allow thesignaling points in the network toset up either a voice or dataconnection between themselves.The message contains the followinginformation:

• The forward and backwardsequence numbers assigned tothe message which indicate theposition of the message in thetraffic stream in relation to theother messages.



M

• The length indicator whichindicates the number of bytesthe message contains.

• The type of message and thepriority of the message in thesignaling information octet ofthe message.

• The routing information for themessage, shown in the routinglabel of the message, with theidentification of the node thatsent message (originating pointcode), the identification of thenode receiving the message(destination point code), and thesignaling link selector which theEAGLE uses to pick which linkset and signaling link to use toroute the message.

O

Originating Point CodeOPC

Within an SS7 network, the pointcodes are numeric addresses whichuniquely identify each signalingpoint. The OPC identifies thesending signaling point.

P

Provisioning Database InterfacePDBI

The interface consists of thedefinition of provisioning messagesonly. The customer must write aclient application that uses thePDBI request/response messagesto communicate with the PDBA.

R

Routing NumberRN

The number provided by theFreephone Service Provider (FSP)



R

to the Access Service Provider(ASP) to enable a pre-determinedrouting of traffic to a specificnetwork/carrier/customer.

Route Set Test - Prohibited messageRSP

Remote Signaling Point

Represents an SS7 network node(point code) that signaling must besent to. An RSP has an SS7 domain(ANSI, ITUI, ITUN), a point code,and an optional Adjacent ServerGroup.

Remote Signaling Point

A logical element that represents aunique point code within aparticular SS7 domain with whichthe SS7 application's LocalSignaling Point interacts.

Reset RequestRSR

Route Set Test – Restricted message

Real Time DatabaseRTDB

S

Service Control PointSCP

Service Control Points (SCP) arenetwork intelligence centers wheredatabases or call processinginformation is stored. The primaryfunction of SCPs is to respond toqueries from other SPs byretrieving the requestedinformation from the appropriatedatabase, and sending it back to theoriginator of the request.



S

DSM, E5-SM4G, or E5-SM8G-Bcard that contains the Real Time

Service Module card

Database (RTDB) downloadedfrom an EPAP or ELAP system.

Subscriber Identity ModuleSIM

An ID card the size of a credit cardfor GSM network subscribers, andis typically referred to as a chipcard or smartcard.

Subsystem Out-of-Service GrantSOG

Service Order Gateway

Support of Optimal RoutingSOR

System Out of Service Request

Service ProviderSP

Signaling Point

A set of signaling equipmentrepresented by a unique point codewithin an SS7 domain.

SubsystemSS

Supplementary Services

Signal Transfer PointSTP

The STP is a special high-speedswitch for signaling messages inSS7 networks. The STP routes coreINAP communication between theService Switching Point (SSP) andthe Service Control Point (SCP)over the network.

Spanning Tree Protocol

T



T

TransFer Allowed (Msg)TFA

TransFer Prohibited (Msg)TFP

A procedure included in thesignaling route management(functionality) used to inform asignaling point of the unavailabilityof a signaling route.

TekelecTKLC

U

Unsolicited Alarm MessageUAM

A message sent to a user interfacewhenever there is a fault that isservice-affecting or when aprevious problem is corrected. Eachmessage has a trouble code and textassociated with the troublecondition.

User Datagram ProtocolUDP

Unitdata Transfer ServiceUDTS

An error response to a UDTmessage.

User InterfaceUI

V

Visitor Location RegisterVLR

A component of the switchingsubsystem, within a GSM network.The switching subsystem includesvarious databases which storeindividual subscriber data. One ofthese databases is the HLR



V

database or Home LocationRegister; and the VLR is another.

Virtual Location Register



Documents

Oracle Communications EAGLE · Oracle® Communications EAGLE EIR User's Guide E54351-01 Revision A July 2014