docs.oracle.com Location... · 2010-11-24 · This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are

Oracle Communications Network Charging and Control

Product: OCNCC 4.3 Component: Location Capabilities Pack

Technical Guide S’ware version: Release 1.0.5 Guide version: 05.00

Release date: December 2010

Status: Approved

Commercial In Confidence

Copyright Location Capabilities Pack Technical Guide, Release 1.0.5

05.00

Copyright © 2010, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license 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. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

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 software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software 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 applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software 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 expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Page ii Location Capabilities Pack Technical Guide


Contents

Copyright ............................................................................. Error! Bookmark not defined. About this Document ........................................................................................................... v Document Conventions ...................................................................................................... vi

Chapter 1

System Overview

Overview .............................................................................................................................. 1 What is Location Capability Pack? ...................................................................................... 2 Normalisation and Denormalisation..................................................................................... 4 Statistics .............................................................................................................................. 5

Chapter 2

Configuration

Overview .............................................................................................................................. 7 Configuration Overview ....................................................................................................... 8 eserv.config Configuration ................................................................................................... 9 Configuring the acs.conf on the SCP ................................................................................ 27

Chapter 3

Administrative Tasks

Overview ............................................................................................................................ 29 Stopping and Starting ........................................................................................................ 30 Data Encoding ................................................................................................................... 31 Conversions - lcpConversionLoader ................................................................................. 32

Chapter 4

Background Processes

Overview ............................................................................................................................ 33 locApp ................................................................................................................................ 34 javaLcpConversionLoader.sh ............................................................................................ 35 liblcpacschassis ................................................................................................................. 36 liblcpalarms ........................................................................................................................ 37 liblcpati ............................................................................................................................... 38 liblcpatimnp ........................................................................................................................ 39 liblcpCurrentLocProcessor ................................................................................................ 40 liblcpmacronodes ............................................................................................................... 41 liblcpposreq ........................................................................................................................ 42 liblcpsri ............................................................................................................................... 43 liblcpsriimsi ........................................................................................................................ 44 liblcpsrimsrn ....................................................................................................................... 45

Chapter 5

Troubleshooting

Overview ............................................................................................................................ 47 Common Troubleshooting Procedures .............................................................................. 48

Continued on next page

Location Capabilities Pack Page iii Technical Guide


Page iv Location Capabilities Pack Technical Guide

Chapter 6

System Alarms

Overview ............................................................................................................................ 51 Alarm Topic Description .................................................................................................... 52 LCP Alarms ........................................................................................................................ 54

Chapter 7

Pre-installation

Overview ............................................................................................................................ 65 Installation Pre-requisites .................................................................................................. 66 Preparing the System ........................................................................................................ 67

Chapter 8

Installation

Overview ............................................................................................................................ 69 Loading the Distribution File .............................................................................................. 70 Installing LCP on an SCP .................................................................................................. 71 Installing LCP on an SMS .................................................................................................. 78 Checking the Installation ................................................................................................... 85

Chapter 9

Removal Overview ............................................................................................................................ 87 Removing LCP from an SCP ............................................................................................. 88 Removing LCP from an SMS ............................................................................................ 91

Appendix Overview ............................................................................................................................ 97 Glossary of Terms ............................................................................................................. 99 Index ................................................................................................................................ 103


About this Document The scope of this document includes all the information required to install, configure and administer the Location Capabilities Pack (LCP) application.

Scope

This guide was written primarily for system administrators and persons installing, configuring and administering the LCP application. However, sections of the document may be useful to anyone requiring an introduction to the application.

Audience

A solid understanding of UNIX and a familiarity with IN concepts are an essential pre-requisite for safely using the information contained in this technical guide. Attempting to install, remove, configure or otherwise alter the described system without the appropriate background skills, could cause damage to the system; including temporary or permanent incorrect operation, loss of service, and may render your system beyond recovery.

Pre-requisites

Although it is not a pre-requisite to using this guide, familiarity with the target platform would be an advantage.

This manual describes system tasks that should only be carried out by suitably trained operators.

The following documents are related to this document: Related documents

• LCP User Guide • IS-41 IS-848 Position Request Specification • GSM 03.32 MAP Specification

Location Capabilities Pack Page v Technical Guide


Document Conventions Before you start using this guide, it is important to understand the terms and typographical conventions used in the documentation.

Typographical conventions

Specialised terms and acronyms are defined in the Glossary at the end of this guide.

Formatting convention Type of information Special Bold Items you must select such as menu options,

or names of tabs. Emphasis within text. Names of database tables and fields.

Italics Name of a document, chapter, topic or other publication.

Button The name of a button to click or a key to press. Example: To close the window, either click Close or press Esc.

Key+Key Key combinations for which the user must press and hold down one key and then press another. Example: Ctrl+P, or Alt+F4.

Monospace Text that you must type and examples of code or standard output.

variable Used to indicate variables or text that should be replaced.

menu option > menu option > Used to indicate the cascading menu option to be selected, or the location path of a file. Example: Operator Functions > Report Functions Example: /IN/html/SMS/Helptext/

hypertext link Used to indicate a hypertext link on an HTML page.

The following icons are used as visual cues to draw attention to important information.

Icons

Note: Indicates useful and complementary information. Explanation, comment, or short expansion of the text object that is intended to catch your attention.

Tip: Indicates practical but non-essential information that makes the solution easier to use or operate (e.g. keyboard shortcut, alternative way to perform a step in a procedure, etc).

Warning: Indicates a caution. If this information is ignored, it could cause possible and irreversible damage to the equipment, data or software.

Page vi Location Capabilities Pack Technical Guide


Chapter 1

System Overview Overview

This chapter provides a high-level overview of the application. It explains the basic functionality of the system and lists the main components.

Introduction

It is not intended to advise on any network or service implications of the product.

This chapter contains the following topics.

What is Location Capability Pack? .................................................................. 2 Normalisation and Denormalisation ................................................................ 4 Statistics .......................................................................................................... 5

In this chapter

Location Capabilities Pack Page 1 Technical Guide

Chapter 1 Commercial In Confidence

What is Location Capability Pack? The Location Capability Pack (LCP) is a set of software components used by other applications to look up the location of mobile devices.

Introduction

The LCP consists of these components: Components

• Location Module (locApp) • MAP ATI plugin • IS-41 POSREQ plugin • SRI-MSRN plugin • SRI-IMSI plugin • LCP ACS components (4 feature nodes and 1 action handler) • Database tables, and • Management screens.

The key component of the LCP is the Location Module. The calling application passes the MSISDN of a mobile device to the Location Module. The Location Module looks up the current location of the mobile device and returns its locational reference to the calling application as a Cell ID/ Area ID or as a circle of uncertainty.

Location Module

The Location Module uses modular communication plugins to communicate with Location Servers on customer networks. It provides the following plugins:

Plugins

• MAP ATI • IS-41 POSREQ • SRI-MSRN, and • SRI-IMSI.

Additional SMS management screens are delivered as part of the LCP to allow the provisioning and management of locational entities in the database (for example: converting data from Cell ID to circles of uncertainty in X,Y,R format).

Provisioning and management

The LCP also enables ACS-based customer applications to use the Location Module by providing the additional feature nodes:

Feature nodes

• Set My Zone will set a subscriber's Home and Work zones • In The Zone checks if a mobile device is currently in a pre-defined zone • Store My Location stores locational data for use by other nodes, and • Store My Network ID stores the IMSI retrieved for a supplied MSISDN.


Page 2 Location Capabilities Pack Technical Guide

Commercial In Confidence Chapter 1

What is Location Capability Pack?, Continued

Here is an overview of how the LCP functions (interaction with the HLR). The Location Application sends location queries to the HLR.

Overview diagram

This diagram shows the architecture overview of the LCP. The Location Module is the locApp and is extendable by taking plugins to communicate with different Location Servers. Four feature nodes in ACS allow existing services to integrate with the LCP by simply dragging and dropping the nodes.

Architectural overview



Normalisation and Denormalisation Normalisation and Denormalisation allow for incoming and outgoing numbers to be selected by their prefix and then have numbers stripped or added (as prefix) if necessary. Normalisation can be applied to all numbers in an incoming IDP request or an MSISDN stored in a buffer. Denormalisation can be applied to all numbers returned from the IN.

Introduction

The LCP feature nodes will attempt to denormalise the MSISDN number stored in the MSISDN Source to Query profile buffer, using the standard acs rules in the acs.conf file.

Denormalisation rules

If no matching rule is found, the HLR query will be constructed using a default Nature of Address (NoA) value of 4.

The NoA (nature of address) is a classification to determine in what realm (Local, National or International) a given phone number resides, for the purposes of routing and billing.

Nature of address

Details vary between different implementations of phone systems, but the following table is representative:

Dialled Digits NOA (NOC, NON) Definition 477 9425 1 → Subscriber Number within Local Telephone

Exchange

4 477 9425 3 → National Number within Country Telephone Exchange

64 4 477 9425 4 → International Number within World Telephone Exchange

477 9425 2 → UNKNOWN Numbering Scheme rule → Subscriber

0 4 477 9425 2 → UNKNOWN Numbering Scheme rule → National

00 64 4 477 9425 2 → UNKNOWN Numbering Scheme rule → International



Statistics LCP statistics are generated by each SCP, and then transferred at periodic intervals to the Service Management Platform (SMP) for permanent storage and analysis.

Introduction

An existing statistics system (smsStats) provides functions for the collection of basic statistical events. This is provided in the Oracle SMS application. Refer to the SMS Technical Guide for details.

The following statistics are gathered. Note that they all belong to the LCP application ID.

Statistics gathered

Statistic ID Description LCP_1 Total number of location requests made (and received by the

locApp).

LCP_2 Number of requests via MAP ATI plugin.

LCP_3 Number of cache hits.

LCP_4 Negative responses from Location Servers (such as HLR).

LCP_5 In The Zone macro node In-Zone hits.

LCP_6 In The Zone macro node Out-of-zone hits.

LCP_7 Set My Zone macro node “zone shape added”.

LCP_8 Set My Zone macro node “Too many zones”.

LCP_9 Location responses received (by the locApp) in <= 1 second.

LCP_10 Location responses received (by the locApp) in > 1 second and <= 2 seconds.

LCP_11 Location responses received (by the locApp) in > 2 seconds and <= 3 seconds.



LCP_14 Location responses received (by the locApp) in > 5 seconds.

LCP_15 Number of requests via IS41 POSREQ plugin.

LCP_16 Number of locations stored using the ‘Store My Location’ node. LCP_17 Number of requests set using the SRI plugin



Location Capabilities Pack Page 7

Chapter 2

Configuration Overview

This chapter explains how to configure the application. Introduction


Configuration Overview ................................................................................... 8 eserv.config Configuration............................................................................... 9 Configuring the acs.conf on the SCP ............................................................ 27

In this chapter

Technical Guide


Configuration Overview The following SCP configuration files are required for this product: SCP

configuration files Configuration File Description

eserv.config The Oracle configuration file. All configuration for the LCP is under the section “LCP”.

SLEE.cfg The SLEE configuration file. This is where to configure the SLEE to run locApp.

acs.conf The ACS configuration file. This is where to configure ACS to load the LCP macro nodes and action handlers.

Note: The LCP package installation will prompt for user input where required (including the configuration file values) and create useable start-up files and configuration files. The SLEE and ACS configuration file will also be updated automatically to include the LCP configurations. For more details on configuring the SLEE and ACS, please refer to the SLEE Technical Guide and ACS Technical Guide.

Note: Configuration details are also held in the SMF database, and are configured using the SMS Java Administration screens.



eserv.config Configuration The eserv.config file is a shared configuration file, from which many Oracle applications read their configuration. Each Oracle machine (USMS and UAS) has its own version of the configuration file, containing configuration relevant to that machine. The configuration file contains many different parts or sections; each application reads the parts of the eserv.config file that contains data relevant to it.

Introduction

It is located in the following directory: /IN/service_packages/

The eserv.config file format allows hierarchical groupings, and most applications make use of this to divide up the options into logical groupings.

To organize the configuration data within the eserv.config file, some sections are nested within other sections. Configuration details are opened and closed using either { } or [ ].

Configuration file format

• Groups of parameters are enclosed with curly brackets - { } • An array of parameters is enclosed in square brackets - [ ] • Comments are prefaced with a # at the beginning of the line

To list things within a group or an array, elements must be separated by at least one comma or at least one line break. Any of the following formats may be used, as in this example:

{ name="route6", id = 3, prefixes = [ "00000148", "0000473"] } { name="route7", id = 4, prefixes = [ "000001049" ] }

or { name="route6"

id = 3 prefixes = [

"00000148" "0000473"

] } { name="route7"

id = 4 prefixes = [

"000001049" ]

}

or { name="route6"

id = 3 prefixes = [ "00000148", "0000473" ]

} { name="route7", id = 4

prefixes = [ "000001049" ] }

Most applications come with an example eserv.config configuration in a file called eserv.config.example in the root of the application directory, for example:

eserv.config files delivered

/IN/service_packages/eserv.config.be_example




eserv.config Configuration, Continued

Open the configuration file on your system using a standard text editor. Do not use text editors such as MS Word, that attach control characters. These can be, for example, Microsoft DOS or Windows line termination characters (for example: ^M), which are not visible to the user, at the end of each row. This will cause file errors when the application tries to read the configuration file.

Editing the file

Always keep a backup of your file before making any changes to it. This will ensure you have a working copy which you can return to if necessary.

Here is an example of the LCP section of the eserv.config file. Example eserv.config file

LCP = { # Here lies all LCP related # config oracleUserAndPassword=/ timerIF=”Timer”

actionHandlers = {

locAppSK=15 normalisedNumbers = false convertForHLR = false

}

atiPlugin = { performanceReportPeriod = 127 timestampFormat = "%D %T[usec:3]" generateEDR = true gsmScfAddress=441234567890 gsmScfMapNOA = 1 # tcapIF=”Tcap” origSSN = 0 destSSN = 0 # cellIdPadCharacter = 'F'

}

posreqPlugin = { scfPC=2443 scfSSN=6 hlrSSN=5 mscMktId=14656 mscSwId=1 tcapIF=”Tcap” forwardToMsc=true

} atiMnpPlugin = {

mnpDbAddress = "1,1,55555" gsmScfAddress = "1234" gsmScfMapNOA = 1 tcapIF = "hlrIF" origSSN = 1234 destSSN = 1235

}

sriPlugin = { gmscAddress = "441234567890" gmscMapNOA = 1 tcapIF = "Tcap" origSSN = 1234 destSSN = 1235 destSccpNOA = 3





Example eserv.config file (continued)

mapNOA = 1 mapVersion = 3 hlrGt = "1,1,333"

}

currentLocation = { Map_Uncertainty_constant_C=10 Map_Uncertainty_constant_x=0.1 LocationNumberLength=15

}

locApp = { cacheSize=500000 responseDeadline=2 cacheExpiry=600 concatenateLocInfo=true flushPeriod = 13 maxNum = 10000 destDir = "/IN/xyz-timestamp_abc/LCP/edr" tempDir = "/IN/xyz-timestamp_abc/LCP/tmp" filePrefix = ""

} }

Here are the global parameters for LCP. Global parameters

Since they are reusable across the all LCP components they are in the top level LCP configuration section.

oracleUserAndPassword

Syntax: oracleUserAndPassword = <root> Description: Sets the Oracle login. Optionality: Optional Default: "/" Example: oracleUserAndPassword = "/"

timerIF

Syntax: timerIF = <str> Description: The SLEE timer interface handle. Type: String Optionality: Optional Default: "Timer"





The actionHandlers section contains the LCP ACS action handler (liblcpacschassis (on page 36)) configuration.

actionHandlers

locAppSK

Syntax: locAppSK = <int> Description: Specifies the service key of the location application. Type: Integer Optionality: Mandatory Default: 15

normalisedNumbers

Syntax: normalisedNumbers = <true|false> Description: Whether to retrieve normalised or un-normalised

called/calling numbers. Type: Boolean Optionality: Optional (default used if not set) Allowed: true Use the normalised number from the ACS call

context. false Do not use normalised numbers.

Default: false Notes: Setting to true doesn't invoke the ACS denormalisation rules.

convertForHLR

Syntax: convertForHLR = <true|false> Description: If set to true, it will normalise the incoming IDP digits then

denormalise them. Type: Boolean Optionality: Optional Allowed: true

false Default: false Notes: • If the configuration option for convertForHLR in the

acs.conf is set to 1, special denormalisation rules in the • acs.conf file are used from the LcpCustomNoA (on page

28) section. If it is set to 0, the global denormalisation rules are used.

• If the normalisedNumbers parameter is set to false, and convertForHLR is set to true, it will normalise the incoming number and then denormalise it. If both parameters are set to true, then convertForHLR will only denormalise the number before sending to the HLR.

Example: convertForHLR = false





actionHandlers (continued)

Example actionHandlers = {

locAppSK=15 normalisedNumbers = false convertForHLR = false

}

The atiPlugin section contains the configuration for the locApp ATI plugin (liblcpati (on page 38)).

atiPlugin

gsmScfAddress

Syntax: gsmScfAddress = "<scf value>" Description: Specifies what the GSM SCF Address should be set to for

the ATI queries. Type: String Optionality: Mandatory Default: None Example: gsmScfAddress = "12324"

gsmScfMapNOA

Syntax: gsmScfMapNOA = <NOA type value> Description: . Type: Integer Optionality: Optional (default used if not set). Default: 1 Example: gsmScfMapNOA = 1

tcapIF

Syntax: tcapIF = <str> Description: Specifies the Tcap Interface SLEE handle that the plugin

uses. Type: String Optionality: Mandatory Default: None Example: tcapIF = "hlrIF"

origSSN

Syntax: origSSN = <origin SSN> Description: The originating SSN. Type: Integer Optionality: Optional (default used if not set). Default: 0 Example: origSSN = 1234






atiPlugin (continued)

destSSN

Syntax: destSSN = <dest SSN> Description: The destination SSN. Type: Integer Optionality: Optional (default used if not set). Default: 0 Example: destSSN = 1234

cellIdPadCharacter

Syntax: cellIdPadCharacter = "<pad character>" Description: The character to use to pad the cellID value to the correct

length. Type: String Optionality: Optional (default used if not set). Default: F Example: cellIdPadCharacter = "0"

performanceReportPeriod

Syntax: performanceReportPeriod = <int> Description: Determines the period (in seconds) after which a new

performance report will be generated. Type: Integer Optionality: Optional (default used if not set). Default: 0 Notes: • The report must be consistently aligned with the system

clock on the UAS. To achieve this, only an integer value that can be computed to be a factor of 60 or 3600, must be used.

• This period is aligned with system clock instead of the application starting time.

• No EDRs will be generated when set to default of 0 seconds.

• The first performance report after SLEE startup may differ to that which is configured for the performanceReportPeriod, depending on when the SLEE was started within the clock aligned performance period.

Example: performanceReportPeriod = 127





atiPlugin (continued)

timestampFormat

Syntax: timestampFormat = <str> Description: Specifies the format of timestamps in the EDR.

Type: String Optionality: Optional (default used if not set). Default: “%D %T” which is translated into, for example, 02/08/10

22:12:56Notes: • To specify the format of timestamps in the EDR. The

strftime function will be used to format timestamps. Users need to check the strftime man page (Solaris) to determine the supported format.

• In addition, usec can be logged in EDR if "[usec:XX]" is included in the formating string, where XX is an interger number. Accepted values are from 1 to 6.

• Values less than 1 or greater than 6 will be set to 6 automatically.

Example: timestampFormat = "%D %T[usec:3]"

generateEDR

Syntax: generateEDR = <bool> Description: Determines whether an EDR record should be generated or

not. Type: Boolean Optionality: Optional (default used if not set). Allowed: • true

• false Default: false Example: generateEDR = <false>

Example atiPlugin = {

performanceReportPeriod = 127 timestampFormat = "%D %T[usec:3]" generateEDR = true gsmScfAddress=441234567890 gsmScfMapNOA = 1 # tcapIF=”Tcap” origSSN = 0 destSSN = 0 # cellIdPadCharacter = 'F'

}




The posreqPlugin section contains the configuration for the locApp POSREQ plugin (liblcpposreq (on page 42)).

posreqPlugin

scfPC

Syntax: scfPC = <int> Description: Specifies what the SCF SCCP addresses should be set to for

the POSREQ queries. Optionality: Mandatory Example: scfPC = 2443

scfSSN

Syntax: scfSSN = <int> Description: Specifies what the SCF SCCP addresses should be set to for

the POSREQ queries. Type: Integer Optionality: Mandatory Example: scfSSN = 6

hlrSSN

Syntax: hlrSSN = <int> Description: Specifies what the HLR SCCP addresses should be set to for

the POSREQ queries. Optionality: Mandatory Example: hlrSSN = 5

mscMktId

Syntax: mscMktld = <int> Description: MSC Market ID. Specifies the originating MSCID sent in the

POSREQ query. Type: Integer Optionality: Mandatory Example: mscMktld = 14656

mscSwId

Syntax: mscSwld = <int> Description: MSC Switch ID. Specifies the originating MSCID sent in the

POSREQ query. Type: Integer Optionality: Mandatory Example: mscSwld = 1






posreqPlugin (continued)

tcapIF



forwardToMsc

Syntax: forwardToMsc = <bool> Description: Controls whether the POSREQ plugin should:

• allow the HLR to forward the request to the MSC (true), or

• send the request to the MSC. Type: Boolean Optionality: Optional Allowed: true, false Example: forwardToMsc = false

Example Here is an example posreqPlugin configuration.

posreqPlugin = { scfPC=2443 scfSSN=6 hlrSSN=5 mscMktId=14656 mscSwId=1 tcapIF=”Tcap” forwardToMsc=true

}




The atimnpPlugin section contains the configuration for MNP USSD call-back and the ATI MNP plugin (liblcpatimnp (on page 39)).

atimnpPlugin

mnpDbAddress

Syntax: mnpDbAddress = <global title> Description: The GSM MNP DB global title, used as the destination GT in

ATI messages. Type: String Optionality: Mandatory Default: None Notes: Values must be comma separated and in one of the following

forms:

• Form a: "1,<noa>,<BCD address digits>" • Form b: "2,<trans type>,<BCD address digits>" • Form c: "3,<trans type>,<num plan>,<BCD address

digits>" (only BCD encoding scheme is supported)

• Form d: "4,<trans type>,<num plan>,<noa>,<BCD address digits>" (only BCD encoding scheme is supported)

Example: mnpDbAddress = "1,1,55555"

gsmScfAddress

Syntax: gsmScfAddress = "<scf value>" Description: Specifies what the GSM SCF Address should be set to for

the ATI queries. Type: String Optionality: Mandatory Default: None Example: gsmScfAddress = "12324"

gsmScfMapNOA

Syntax: gsmScfMapNOA = <NOA type value> Description: . Type: Integer Optionality: Optional (default used if not set). Default: 1 Example: gsmScfMapNOA = 1





atimnpPlugin (continued)

tcapIF



origSSN

Syntax: origSSN = <origin SSN> Description: The originating SSN. Type: Integer Optionality: Optional (default used if not set). Default: 147 Example: origSSN = 1234

destSSN

Syntax: destSSN = <dest SSN> Description: The destination SSN. Type: Integer Optionality: Optional (default used if not set). Default: 6 Example: destSSN = 1235

Example Here is an example atimnpPlugin configuration.

atiMnpPlugin = { mnpDbAddress = "1,1,55555" gsmScfAddress = "1234" gsmScfMapNOA = 1 tcapIF = "hlrIF" origSSN = 1234 destSSN = 1235

}

The sriPlugin section contains the configuration for the locApp plugins: sriPlugin

• SRI-MSRN (liblcpsrimsrn (on page 45)) and • SRI-IMSI (liblcpsriimsi (on page 44)).






sriPlugin (continued)

gmscAddress

Syntax: gmscAddress = <int> Description: Specifies the 'Gateway MSC Address' that is added to the

SRI message sent by the plugin. Type: Integer Optionality: Mandatory Notes: If you are using liblcpsrimsrn (on page 45), this parameter

should be set to the GT of the UAS. Example: gmscAddress = 441234576890

gmscMapNOA

Syntax: gmscMapNOA = <NOA type value> Description: . Type: Integer Optionality: Optional (default used if not set). Default: 1 Example: gmscMapNOA = 1

tcapIF



origSSN

Syntax: origSSN = <SSN> Description: The originating SSN to add to the header of the SRI

messages. Type: Integer Optionality: Optional (default used if not set). Default: 0 Notes: Needed as LCP ignores the hss settings. Example: origSSN = 1234






destSSN

Syntax: DestSSN = <SSN> Description: The destination SSN to add to the header of the SRI

messages. Type: Integer Optionality: Optional (default used if not set). Default: 0 Notes: Adding the SSN to the header means it isn't forced to 6 for

the HLR. Example: destSSN = 1235

destSccpNOA

Syntax: destSccpNOA = <noa> Description: Override the NOA from SCCP in the IDP, and set this value

instead on messages to locApp. Type: Integer Optionality: Optional (default used if not set). Default: 4 for international, 3 otherwise. Example: destSccpNOA = 4

mapNOA

Syntax: mapNOA = <noa> Description: Override the NOA from MAP in the IDP, and set this value

instead on messages to locApp. Type: Integer Optionality: Optional (default used if not set). Default: 1 for international, 2 otherwise. Example: mapNOA = 1

mapVersion

Syntax: mapVersion = <ver> Description: The version of MAP to use in SRI messages. Type: Integer Optionality: Optional (default used if not set). Allowed: 2 Use MAP 2.

3 Use MAP 3. Default: 3 Example: mapVersion = 3





hlrGt

Syntax: hlrGt = <global title> Description: The HLR address. Type: String Optionality: Optional (default used if not set). Default: Subscriber's MSISDN is used as the HLR address. Notes: Values must be comma separated and in one of the following

forms:

• Form a: "1,<noa>,<BCD address digits>" • Form b: "2,<trans type>,<BCD address digits>" • Form c: "3,<trans type>,<num plan>,<BCD address

digits>" (only BCD encoding scheme is supported)

• Form d: "4,<trans type>,<num plan>,<noa>,<BCD address digits>" (only BCD encoding scheme is supported)

Example: hlrGt = "1,1,333"

Example sriPlugin = {

gmscAddress = "441234567890" gmscMapNOA = 1 tcapIF = "Tcap" origSSN = 1234 destSSN = 1235 destSccpNOA = 3 mapNOA = 1 mapVersion = 3 hlrGt = "1,1,333"

}

The currentLocation section contains the configuration for liblcpCurrentLocProcessor (on page 40) to process MapGeographicalInformation.

currentLocation

For more details on these, refer to GSM 03.32.

Map_Uncertainty_constant_C

Syntax: Map_Uncertainty_constant_C = <int> Description: Used to process MapGeographicalInformation. Type: Integer Optionality: Optional Example: Map_Uncertainty_constant_C = 10





currentLocation (continued)

Map_Uncertainty_constant_x

Syntax: Map_Uncertainty_constant_x = <int> Description: Used to process MapGeographicalInformation. Type: Integer, floating-point Optionality: Optional Example: Map_Uncertainty_constant_x = 0.1

LocationNumberLength

Syntax: LocationNumberLength = <int> Description: This specifies the allowed length for an INAP Location

Number. If the length does not match this value then the current location is not valid.

Type: Integer Optionality: Optional Default: 15 Example: LocationNumberLength = 15

Example currentLocation = {

Map_Uncertainty_constant_C=10 Map_Uncertainty_constant_x=0.1 LocationNumberLength=15

}

The locAPP section contains the parameters controlling the locApp (on page 34). locAPP

cacheSize

Syntax: cacheSize = <int> Description: Controls how many location responses the locApp caches. Type: Integer Optionality: Optional Notes: The minimum cache space consumed is 50 MB

(50*1024*1024 bytes). If you are using the SRI plugin (liblcpsrimsrn (on page 45)) you should always set this parameter to have no cache (0), as the MSRN is no longer valid after the call is connected.

Example: cacheSize = 500000






locAPP (continued)

cacheExpiry ; 25475-

Syntax: cacheExpiry = <secs> Description: The number of seconds before a cached entry is considered

“too old” and a new request must be made if the cached entry is queried.

Type: Integer Optionality: Optional Notes: If you are using the SRI plugin (liblcpsrimsrn (on page 45))

you should always set this parameter to never cache (0), as the MSRN is no longer valid after the call is connected.

Example: cacheExpiry = 600

responseDeadline

Syntax: responseDeadline = <int> Description: The number of seconds before the locApp considers a

request as timed out. Type: Integer Optionality: Optional Default: 2 Example: responseDeadline = 2

concatenateLocInfo

Syntax: concatenateLocInfo = <bool> Description: Controls how the locApp will treat CELL_RAW type

responses. Type: Boolean Optionality: Optional Allowed: true, false Notes: If the LocationNumber is present in the response, it will be

pre-pended to the CellID before it is returned to the macro node.

Example: concatenateLocInfo = true





locAPP (continued)

flushPeriod

Syntax: flushPeriod = <int> Description: Determines the period (in seconds) after which a new EDR

file will be created.

Type: Integer Optionality: Optional (default used if not set). Default: 0 Notes: No EDR files will be generated when set to default of 0

seconds. Example: flushPeriod = 60

maxNum

Syntax: maxNum = <int> Description: This is used to configure the maximum number of EDR

records written in a single EDR file. Type: Integer Optionality: Optional (default used if not set). Default: 10,000 Notes: A new EDR file will be generated according to the

flushPeriod or maxNum, whichever target is reached first. Example: maxNum = 1000

destDir

Syntax: destDir = <str> Description: The destination directory where the output EDR files are

stored eventually. Type: String Optionality: Optional (default used if not set). Default: /IN/service_packages/LCP/edr Notes: If multiple locApp instances are running simultaneously, the

destDir holding the final EDR files can be the same for all instances.

Example: destDir = "/IN/xyz-timestamp_abc/LCP/edr"




locAPP (continued)

tempDir

Syntax: tempDir = <str> Description: The directory where the output EDR files are stored

temporarily. Type: String Optionality: Optional (default used if not set). Default: /tmp Notes: EDR files leftover from previous failed/aborted instances of

locApp can also be recovered from this directory. Example: tempDir = "/IN/xyz-timestamp_abc/LCP/tmp"

filePrefix

Syntax: filePrefix = <str> Description: This prefix is used to to specify the prefix of the name of an

EDR file. The name of an EDR file consists of filePrefix, PID, and timestamp.

Type: String Optionality: Optional (default used if not set). Default: "" Example: filePrefix = "abc"

Example Here is an example of the locAPP configuration.

locApp = { cacheSize=500000 responseDeadline=2 cacheExpiry=600 concatenateLocInfo=true flushPeriod = 13 maxNum = 10000 destDir = "/IN/xyz-timestamp_abc/LCP/edr" tempDir = "/IN/xyz-timestamp_abc/LCP/tmp" filePrefix = ""

}

If you change the configuration file, then you must restart the appropriate parts of the service to enable the new options to take effect.

Loading eserv.config configuration changes



Configuring the acs.conf on the SCP The acs.conf file must be configured to enable LCP to use custom denormalisation rules. All necessary configuration is done at installation time by the configuration script; this section is for information only.

Introduction

The ACS configuration file is located /IN/service_packages/ACS/etc/acs.conf

Refer to the ACS Technical Guide for details on ACS configuration.

Note: It is not recommended to change the values of this section. Please contact the Oracle support prior to attempting any modification to configuration data.

Example LCP section

Here's an example of the LCP configuration in the acs.conf file. acsChassis # Checking for LCP denormalisation rules useCustomLCPNotificationNoARules 1: LcpCustomNoA DenormalisationRule (000620,4,3,E,7) DenormalisationRule (000,4,3,E) DenormalisationRule (1077,2,0,0) DenormalisationRule (1055,2,0,0) DenormalisationRule (0,3,1,E,2) DenormalisationRule (495,2,0,E):




Configuring the acs.conf on the SCP, Continued

Here are the parameters required for configuring LCP in the acs.conf: Parameters

useCustomLCPNotificationNoARules

Syntax: useCustomLCPNotificationNoARules <int> Description: Determines whether the incoming numbers are denormailsed

using global denormalisation rules or LCP specific rules defined in the LcpCustomNoA section.

Type: Integer Optionality: Optional (default used if not set). Allowed: • 0 - global denormalisation rules

• 1 - LCP specific rules Default: 0 Notes: The convertForHLR parameter in the eserv.config file

must be enabled for this to take effect. Example: useCustomLCPNotificationNoARules 1

LcpCustomNoA

Syntax: LcpCustomNoA

<DenormalisationRule 1>

<...>

<DenormalisationRule 2>:

Description: Defines the custom denormalisation rules available to LCP to normalise or denormalise the incoming IDP digits.

Type: Array Optionality: Optional Example: LcpCustomNoA

DenormalisationRule (000600,1,2,E,3) DenormalisationRule (495,1,0,E):



Chapter 3

Administrative Tasks Overview

This chapter provides the procedures for administering the LCP application. Introduction


Stopping and Starting .................................................................................... 30 Data Encoding ............................................................................................... 31 Conversions - lcpConversionLoader ............................................................. 32

In this chapter



Stopping and Starting The locApp is a SLEE application, therefore it is started along with the rest of the SLEE applications and interfaces.

The locApp

After installation of the package lcpScp, the SLEE start-up and configuration files (as specified at install time) will be updated to instruct the SLEE to start the locApp.

For more details on how to start the SLEE, refer to the SLEE Technical Guide.

As the LCP ACS components are simply shared libraries (ACS plugin), they are started along with slee_acs. The slee_acs startup and configuration files (as specified at lcpScp install time) are updated by the lcpScp package install scripts, to allow the LCP ACS components to be integrated into ACS.

The LCP ACS components

For more details on how to configure slee_acs (and the macro node/action plugin), refer to the ACS Technical Guide.

Follow these steps to turn DEBUG on and off. Turning DEBUG on and off

Step Action 1 Set the UNIX environment variable DEBUG to LCP or all, e.g.:

DEBUG=LCP; export DEBUG

Note: Specifying the all DEBUG section will display all sections of debug. This is the most verbose debug level, so using the LCP section is recommended when specifically checking the LCP service. To turn off debug, the DEBUG environment variable must be unset.

2 Restart the SLEE to make the new setting effective.



Data Encoding According to 3GPP TS 04.08, the coding of Cell ID and LAI (without taking the country code and network code into account) are specified per local administration. As such, the Cell ID and LAI are treated as numbers. Note that if the number of digits received is less than 4, then the Cell ID or LAI will be left padded with ‘F’.

ATI Cell ID/LAI encoding

Example:

• Cell ID/LAI received is 1234: No padding is done • Cell ID/LAI received is 12: Cell ID/LAI is padded to FF12 • Cell ID/LAI received is 12345: Cell ID/LAI is unchanged.

The U-CA-IS41 (cdmagw) encodes the Serving Cell ID and MSCID (Location Number) using the following encoding scheme. This has been arbitrarily created to suit the processing of such data and does not follow any set standards other than those defined by Oracle.

IS41 MSCID (Location Number) & serving Cell ID encoding

Depending on the LCP.locApp.concatenateLocInfo parameter (on page 24), the data returned from the locApp will contain one of the following encoding schemes:

The returned location data will be concatenated using the following format:

• Location Number – 9 digits (zero padded) • Serving Cell ID – 6 digits (zero padded)

If the configuration item specifies not to concatenate (or the response does not contain the Location Number), the following format will be used:

• Serving Cell ID – 6 digits (zero padded)

Example:

• Location Number & Serving Cell ID: 014566114000300 • Serving Cell ID: 000401

No encoding of the MSRN (Mobile Station Roaming Number) is performed. SRI-MSRN encoding

The number is an E.164 and is handled in the form that is received by the SRI plugin.

Example: MSRN - (16 digits max) - 00441473289900

No encoding of the IMSI (International Mobile Subscriber Identifier) is performed. SRI-IMSI encoding



Conversions - lcpConversionLoader The Conversion Bulk Loader enables you to load conversion data from text files. Files can contain data for updating by area ID or by cell ID, but not both. The table will allow a maximum of 1 million records.

Conversion bulk loader

The conversion import files are text files with one entry per line. Whitespace (space or tab) is allowed between fields.

Import file format

There are two formats possible on each line:

1 <id>,<X>,<Y>,<R> Insert or update an entry with this <id>. If the id already exists, it is updated with the new <X>, <Y> and <R> values.

2 <id> Delete the entry with this <id>.

The bulk loader is started by hand by the “smf_oper” user as follows: Bulk importing using command line lcpConversionLoader {-m M} [-c cellFile] [-a areaFile] [-o

outputFile] [-u user/password] • “-m” (mode) must be specified. M =

“R” = replacement (insert into empty database or replace all existing rows), “U” = update (update existing data).

• One or both of the “-c” and “-a” options must be specified. The “-m” mode applies to both files if both files are specified.

• If the “-o” option is not specified, output is to the standard output or standard error, whichever is appropriate.

• The “-u” option specifies the Oracle login details. This defaults to “/”.

For details on how to bulk import conversions using the LCP maintenance screens, refer to the LCP User's Guide.

Bulk importing using screens



Chapter 4

Background Processes Overview

This chapter explains the processes which run automatically as part of the application. These processes are started automatically by one of the following:

Introduction

• inittab • crontab, or • SLEE.

Note: This chapter also includes some plugins to background processes which do not run independently.


locApp............................................................................................................ 34 javaLcpConversionLoader.sh ........................................................................ 35 liblcpacschassis ............................................................................................. 36 liblcpalarms ................................................................................................... 37 liblcpati........................................................................................................... 38 liblcpatimnp ................................................................................................... 39 liblcpCurrentLocProcessor ............................................................................ 40 liblcpmacronodes .......................................................................................... 41 liblcpposreq ................................................................................................... 42 liblcpsri........................................................................................................... 43 liblcpsriimsi .................................................................................................... 44 liblcpsrimsrn .................................................................................................. 45

In this chapter



locApp locApp is the main LCP process. It addition to its own processing, it supports plugins. The plugin can either be chosen by the applications using LCP or else the default configuration will be used.

Purpose

This binary is located on UASs. Location

locApp is a SLEE Application and is started during SLEE initialisation. The lines in the SLEE.cfg which start the locApp are:

Startup

APPLICATION=locApp locApp.sh /IN/service_packages/LCP/bin 1 1 SERVICE=locApp 1 locApp locApp SERVICEKEY=INTEGER 123 locApp

Note: The above settings are defaults and may vary. For instructions about starting and stopping locApp, see the SLEE Technical Guide.

For more information about how locApp is configured, see locAPP (on page 23). Configuration



javaLcpConversionLoader.sh javaLcpConversionLoader.sh is the shell script the LCP screens use to run the lcpConversionLoader (see "Conversions - lcpConversionLoader" on page 32).

Purpose

This binary is located on USMSs. Location



liblcpacschassis This slee_acs plugin implements the chassis actions which are used by the LCP macro nodes when they need to interact with elements outside the control plan.

Purpose

This library is located on UASs. Location

If liblcpacschassis is configured in acs.conf, it is made available to slee_acs when slee_acs is initialised. It is included in the acsChassis section of acs.conf in a ChassisPlugin entry.

Startup

acsChassis ChassisPlugin liblcpacschassis.so

liblcpacschassis is configured in eserv.config. For more information about how to configure this library, see actionHandlers (on page 12).

Configuration



liblcpalarms liblcpalarms provides the alarms definitions. Purpose

This binary is located on both UASs and USMSs. Location

This binary has no specific configuration. Configuration



liblcpati liblcpati supports the Any Time Interrogation message on GSM networks. The ATI message is used to determine the location of a mobile subscriber.

Purpose


liblcpati is configured in eserv.config. For more information about how to configure this library, see atiPlugin (on page 13).

Configuration



liblcpatimnp This is ATIMNP plugin, which sends ATIs to a MNP DB (whose GT must be specified in eserv.config at atimnpPlugin (on page 18)) to retrieve the msisdn and routing number of the called party.

Purpose


liblcpatimnp is configured in eserv.config. For more information about how to configure this library, see atimnpPlugin (on page 18).

Configuration



liblcpCurrentLocProcessor liblcpCurrentLocProcessor processes MapGeographicalInformation. Purpose

For more details on these, refer to GSM 03.32.


liblcpCurrentLocProcessor is configured in eserv.config. For more information about how to configure this library, see currentLocation (on page 22).

Configuration



liblcpmacronodes This slee_acs plugin provides the LCP macro nodes. There are no configuration file settings for these macro nodes, they are all configured in the Control Plan Editor node configuration screens.

Purpose

For more information about macro node libraries, see ACS Technical Guide.

For more information about the CPE, see CPE User's Guide.


If liblcpmacronodes is configured in acs.conf, it is made available to slee_acs when slee_acs is initialised. It is included in the acsChassis section of acs.conf in a MacroNodePluginFile entry as follows:

Startup

acsChassis MacroNodePluginFile liblcpmacronodes.so

This binary has no specific configuration. Configuration



liblcpposreq POSREQ plugin. Supports the PositionRequest message. Purpose


liblcpposreq is configured in eserv.config. For more information about how to configure this library, see posreqPlugin (on page 16).

Configuration



liblcpsri SRI plugin. Supports the Send Routing Information message. Purpose


liblcpsri is configured in eserv.config. For more information about how to configure this library, see sriPlugin (on page 19).

Configuration



liblcpsriimsi SRI plugin. Supports the Send Routing Information message and records the resulting IMSI. The plugin extracts digits from the MSISDN parameter of the ATI Responses.

Purpose


liblcpsriimsi is configured in eserv.config. For more information about how to configure this library, see sriPlugin (on page 19).

Configuration



liblcpsrimsrn SRI plugin. Supports the Send Routing Information message and records the resulting MSRN.

Purpose


liblcpsrimsrn is configured in eserv.config. For more information about how to configure this library, see sriPlugin (on page 19).

Configuration




Chapter 5

Troubleshooting Overview

This chapter explains common troubleshooting procedures and problem symptoms.

Introduction

If the problem is not solved after consulting this chapter, contact Level 1 support. You will be asked to describe the failure in detail, together with any error messages that may have been displayed at the time of failure.


Common Troubleshooting Procedures ......................................................... 48

In this chapter

Technical Guide


Common Troubleshooting Procedures This topic provides instructions for completing common troubleshooting procedures.

Introduction

You can check which processes are running using the standard UNIX command: ps. To find processes being run by Oracle software, you can grep for the string 'oper', which will display all processes being run by the application operator accounts (for example, acs_oper, ccs_oper and smf_oper).

Checking current processes

Note: Some processes which are required for proper functioning may be run by other users, including root or the user which runs the webserver.

Example command: ps -ef | grep oper

For more information about the ps command, see the system documentation for the ps command.

You can also check how much of the processor a process is using by running the standard UNIX tool: top. If you have some baseline measurements, you will be able to compare it with the current load.

Example command: top

Tip: Some processes should only have one instance. If there are two or more instances, this may indicate a problem. For example, there will usually only be one timerIF running on each UAS. For more information about which processes should be running on each node, check the Process List for each node in Installation.

To check the details of an installed package, use the pkginfo command. Checking installed packages Example command: pkginfo -l smsSms

Example output: This is an example of the output of the example command above. PKGINST: smsSms NAME: Oracle smsSms CATEGORY: application ARCH: sun4u VERSION: 3.1.0 VENDOR: Oracle PSTAMP: smsNode20041020104925 INSTDATE: Oct 20 2004 13:15 EMAIL: [email protected] STATUS: completely installed FILES: 348 installed pathnames 39 directories 89 executables 152448 blocks used (approx)

For more information about the pkginfo utility, see the system documentation.

A number of services and functions rely on access to the Oracle database. To check that Oracle is available to a service, check the following:

Checking Oracle

1 Use sqlplus to check that you can log into Oracle with the username and password the service is using to connect (these can usually be found in the service's configuration file).




Common Troubleshooting Procedures, Continued

Checking Oracle (continued)

Example command: sqlplus smf/smf 2 Where the tables required for a service are known, use SQL queries to check

that: the tables exist, and they have appropriate content.

For more information about SQL queries, see the Oracle documentation.

Network connectivity will affect any process which requires communication between two different network addresses.

Checking network connectivity

Network connectivity should support ssh sessions between the two machines experiencing the problem.

If you can open an ssh session between the two machines, check the following before contacting Level 1 support with details:

• If the address of either of the machines specified in the Node Management screens is a hostname, check that the hostnames used in the ssh sessions are the hostnames specified in the Node Management screen.

If you cannot ssh, check the following before contacting Level 1 support with details:

• Check that the hostname is resolving correctly in the DNS. • Check that the physical network connection is working correctly. • Check that the inetd and sshd are running. • Check that sshd is listening on the expected port. • Check that the smf_oper and acs_oper accounts are not locked, and that the

username and password combinations being used are correct.

Replication may be failing for the following reasons: Replication

• ssh keys have not been correctly set up between origin and destination machines.

• The destination node has been incorrectly set up in the Node Management screens of the SMS Java screens.

• Oracle is not running correctly. • A new replication.cfg file has not been created after a change. • replication.cfg may not be successfully copying to the destination machine (an

error should display when the Create Config File button on the Node Management screens is clicked).

• The partition on the destination machine where the data is being replicated to may be full.

• The updateLoader on the destination machine may be running incorrectly. • The destination database may be substantially out of sync with the SMF. Run

a resync.




Common Troubleshooting Procedures, Continued

One of the significant areas where faults can occur and be remedied is in the configuration of processes. Configuration files can be edited by any standard text editor. A backup of the existing configuration file should always be taken before editing a configuration file.

Checking configuration files

For more information about the configuration files used in this application, see Configuration.

For more information about the configuration file for a specific program or tool, see the section named after the binary in question.



Chapter 6

System Alarms Overview

This chapter explains the alarms which may be generated by the application, probable causes and recommended responses.

Introduction


Alarm Topic Description ................................................................................ 52 LCP Alarms ................................................................................................... 54

In this chapter



Alarm Topic Description Alarms on each configured node are written to the syslog and are then captured by the smsAlarmDaemon for entry in the SMF database.

Alarm generation

For management of these alarms, refer to the SMS Technical Guide.

This table describes the alarms severity levels. Severity levels

Level Abbr Description Critical C These alarms are raised when the application has encountered

an error which indicates that the system is unable to function.

Error E These alarms indicate the application has encountered a serious problem completing a necessary task and could not complete the task.

Warning W Warnings are raised to indicate the application encountered a problem completing a non-mission critical task.

Notice N Notices are raised to indicate that the application has completed a task successfully.

Alarms usually follow this format: Alarm format

Mon DD 24:MM:SS <hostname> <process name>: [ID <alarmID> user.<severity>] <process>(PID) <SEVERITY>: <Alarm text with possible variables>

Where:

Variable Description Mon DD Month and date the alarm was logged.

24:MM:SS Time the alarm was logged in 24 hour format.

hostname Name of the machine on which the alarm was generated.

process name Name of the process which logged the alarm.

alarmID ID number of the alarm.

severity Alarm severity.

process Name of the process which logged the alarm.

PID Process ID of the process which logged the alarm.

SEVERITY Alarm severity. Alarm text Alarm text. This may include variables such as node number.

Note: In some cases the entire alarm text is generated from variables.

Note: Some alarms from some subsystems may have a different format. Example: This text shows an smsMaster alarm about pending update queues. Mar 30 13:34:54 prodsmp1 smsMaster: [ID 953149 user.warning] smsMaster(17833) WARNING: Pending queue now above 15 (Worst Node 317)




Alarm Topic Description, Continued

For more information about the SMS Alarms subsystem, see the SMS Technical Guide.

Further information

For more information about creating and maintaining the SMS Alarm Relay rule set, see the SMS User's Guide.



LCP Alarms This topic lists the alarms for locApp and macro nodes. Note that only severity Warning and above are listed.

Introduction

This table defines the critical error messages for locApp and the macro nodes. Critical errors

Alarm Text Reason Remedy LCP-0017: Failed to find timer interface. Name:

locApp starting up. Unable to find the timer interface.

Check the timer interface name passed to the locApp. If the default timer name is used, check the SLEE configuration file.

LCP-0019: Uncaught std::length_error

Contact Oracle support team.

LCP-0020: Uncaught std::domain_error


LCP-0021: Uncaught std::out_of_range


LCP-0022: Uncaught std::invalid_argument


LCP-0023: Uncaught std::logic_error


LCP-0024: Uncaught std::range_error


LCP-0025: Uncaught std::overflow_error


LCP-0026: Uncaught std::underflow_error


LCP-0027: Uncaught std::runtime_error


LCP-0028: Uncaught std::bad_alloc


LCP-0029: Uncaught std::bad_exception


LCP-0030: Uncaught std::bad_cast


LCP-0031: Uncaught std::bad_typeid


LCP-0032: Uncaught std::ios_base::failure


LCP-0033: Uncaught std::exception


LCP-0034: Unknown exception caught.


LCP-0038: Received reply to unknown request.





LCP Alarms, Continued

Critical errors (continued)

Alarm Text Reason Remedy LCP-0101: Out of memory trying to create an instance of LocActionHandle.

Check if the memory is growing uncontrollably. If so there may be a memory leak and contact the Oracle support team.

LCP-0102: Out of memory trying to create an instance of LocEventHandle.


LCP-0105: Out of memory trying to create an instance of LocationReportRequest.


LCP-0107: SLEE exception caught:


This table defines the error messages for locApp and macro nodes. Errors

Alarm Text Reason Remedy LCP-0001: shm_open(3RT)

locApp fails to start up. The locApp is unable to obtain the shared memory. Following the alarm text is a brief description of why the shm_open operation failed.

Consult the shm_open online manual page for more details.

LCP-0002: mmap(2) locApp fails to start up. The locApp is unable to memory map the file descriptor returned by shm_open. Following the error test will be a brief description of why the mmap operation fails.

Consult the mmap online manual page for more details.

LCP-0005: ftruncate(3C)

locApp fails to start up. The locApp is unable to set the shared memory size to that it requires to.

Check the ftruncate online manual and the kernel parameter.

LCP-0016: getopt error. Status:

locApp starting up. Incorrect command line option passed to locApp. Where possible the error message includes the offending option.

LCP-0055: Dialogue already exist for an location interaction.







Errors (continued)

Alarm Text Reason Remedy LCP-0056: ATI plugin: Invoke ID not found.

Incorrect invoke ID is returned in the ATI reply.


LCP-0057: ATI plugin: unable to find TCAP interface

The ATI plugin cannot locate the TCAP Interface.

Check configuration section LCP.atiPlugin and check the SLEE configuration file.

LCP-0058: ATI plugin config: gsmScfAddress not set.

The option gsmScfAddress is not set in LCP.atiPlugin in eserv.config.

LCP-0059: ATI plugin config: tcapIF not set.

The option tcapIF is not set in LCP.atiPlugin in eserv.config.

LCP-0063: Unable to gettimeofday from SleeApplicationAPI. Error code is:


LCP-0064: gettimeofday(3c)

Unable to get the time. The error will include a brief description on why the gettimeofday operation failed.

Consult the gettimeofday online manual for more detail.

LCP-0065: Initialisation failed. Exiting.

The locApp failed to start up. Check the previous error log entry for details why initialisation failed.

LCP-0067: dlopen(3DL) error Error:LCP-0068: dlsym (3DL) error

Unable to open the plugin shared library. The error text will include why the operations dlopen and dlsym failed.

LCP-0076: Unable to connect to oracle using login:

Unable to connect Oracle using the login specified.

Check that the login is correct.

LCP-0077: semget(2) error

Unable to get the semaphore required for the locApp.

Check the error description and consult the semget online manual.

LCP-0078: ftok(3c) error

Unable to turn the file specified into a key to use by semget.

Check the error description and consult the ftok online manual for more detail.

LCP-0079: semop(2) error

Unable to change the semaphore value.

Check the error description and consult the semop online manual for more detail.

LCP-0082: signal(3C) error.

Unable to set the signal handler. Contact the Oracle support team.

LCP-0084: No plugin found for the MSISDN.

Unable to find a plugin for the MSISDN specified.

Check the table lcp_mapping for MSISDN to plugin mapping.

LCP-0085: Conversion data not found.

Unable to find conversion for either cell ID or LAI.

Check the table lcp_conversion for cell ID/LAI to x,y,r mapping.





Errors (continued)

Alarm Text Reason Remedy LCP-0086: Oracle error.

Internal Oracle error. Contact Oracle support team.

LCP-0087: No plugin configured.

No plugin are configured for the locApp.

LCP-0088: Unable to create dialog to TCAP interface.

Check that the TCAP interface is running.

LCP-0089: Invalid statistics counter specified.

Check that the LCP statistics counters are replicated to the SCP.

LCP-0090: Failed to log stats. Statistics ID:

Check that the statistics daemon has loaded the statistic ID (try the stats subsystem log file).

LCP-0091: MAP2 error - system failure.

Map 2 errors returned by the HLR

LCP-0092: MAP2 error - data missing.


LCP-0093: MAP2 error - unexpected data value.


LCP-0094: MAP2 error - ATI not allowed.


LCP-0095: ACS Macro node registration failed. Fast key:

Unable to register the macro node. The offending fast key is listed.

Check acs_fn_type for the fast key and macro node configuration.

LCP-0098: Location Action Registration failed.

The LCP ACS chassis action has failed to register with ACS.

Check for previous log entries on why this has occurred.

LCP-0100: Unable to obtain an instance of SLEE Application API.

Check that the SLEE is running correctly.

LCP-0103: Location Action Handler: No locApp service key set (locAppSK).

The option locAppSK is not set in section LCP.actionHandlers.

LCP-0104: Location Action Handler: Unable to create dialog to locApp.

Check that the service key is set correctly and locApp is up and running.

LCP-0106: Unable to register dialog with ACS Chassis.

The event handler has failed to register.






Errors (continued)

Alarm Text Reason Remedy LCP-0108: Location Action Event Handler: No outstanding action when event handler invoked.


LCP-0109: Location Action Event Handler: Incorrect event type received.

LCP-0110: Location Event Handler: Dialog closed before response received.

LCP-0112: ATI plugin: config section LCP.atiPlugin not found.

Mandatory configuration sections or options not found.

Check eserv.config.

LCP-0113: LCP Action Handler: config section LCP.actionHandler not found:


Check eserv.config.

LCP-0116: LCP current location processor: Config section LCP.currentLocation not found.


Check eserv.config.

LCP-0117: LCP current location processor: option "Map_Uncertainty_constant_C" not set.


Check eserv.config.

LCP-0118: LCP current location processor: option "Map_Uncertainty_constant_x" not set.


Check eserv.config.

LCP-0119: In The Zone: No node parameter set.

In The Zone parameter encoding/decoding error.


LCP-0120: In The Zone: Parameter parsing error.

In The Zone parameter encoding/decoding error.


LCP-0121: Set My Zone: No node parameter set.

Set My Zone parameter encoding/decoding error.


LCP-0122: Set My Zone: Parameter parsing error.

Set My Zone parameter encoding/decoding error.






Errors (continued)

Alarm Text Reason Remedy LCP-0123: Incorrect action type received.


LCP-0134: fopen(3c) Unable to open the file /tmp/lcp-semkey.

Check the error description for more details.

LCP-0135: Incorrect number of results retuned from locApp.

locApp has returned results that are not what was asked.

LCP-0136: System Failure.

OSA error codes.

LCP-0137: Unauthorised network.

OSA error codes.

LCP-0138: Unauthorised application.

OSA error codes.

LCP-0139: Unknown Subscriber.

OSA error codes.

LCP-0140: Absent Subscriber.

OSA error codes.

LCP-0141: Position method failure.

OSA error codes.

LCP-0142: Non-originating/terminating end detected.

Node parameter decoding failure. Contact Oracle support team.

LCP-0143: Out of bound status detected.


LCP-0145: Set My Zone node: Unable to add zone shape.

CmnProfileUpdate error. Contact Oracle support team.

LCP-0147: Bad parameter string specified .

Parameter decoding failed. Contact Oracle support team.

LCP-0148: LCP Set My Zone: Profile update error.

ACS profile update action failed. Check previous log entries for a possible cause. (Is the replication interface running?)

LCP-0149: Non-existent plugin specified.

Location query received with bad plugin specified.

LCP-0150: LCP nodes: Geographical Position information not available.

In The Zone node did not receive required Geographical Information in response from locApp.

Check mapping information is correct.

LCP-0151: Store My Location: Geographical Position not currently supported.

Store My Location node does not support Geographical Information received in response from locApp.

Verify that the HLR has returned the required information.





Errors (continued)

Alarm Text Reason Remedy LCP-0152: Store My Location: Serving Cell information not available.

Store My Location cannot process a response that doesn’t contain a CellID.

Verify that the HLR/MSC has returned the required information.

LCP-0153: Store My Location: Invalid buffer number selected.

The Store My Location node cannot store the information in the selected context buffer – it is invalid.


LCP-0154: Store My Location: No node parameter set.


LCP-0155: Store My Location: Parameter parsing error.


LCP-0157: POSREQ plugin: config section LCP.posreqPlugin not found.


Check eserv.config.

LCP-0158: POSREQ plugin config: ‘scfPC’ SCF PC address not set.

The option scfPC is not set in LCP.posreqPlugin in eserv.config.

Contact network support for correct value.

LCP-0159: POSREQ plugin config: ‘scfSSN’ SCF PC address not set.

The option scfSSN is not set in LCP.posreqPlugin in eserv.config.


LCP-0160: POSREQ plugin config: ‘hlrSSN’ SCF PC address not set.

The option hlrSSN is not set in LCP.posreqPlugin in eserv.config.


LCP-0161: POSREQ plugin config: tcapIF not set.

The option tcapIF is not set in LCP.posreqPlugin in eserv.config.

LCP-0163: POSREQ plugin: unable to find TCAP interface

The POSREQ plugin cannot locate the Tcap Interface.

Check configuration section LCP.posreqPlugin and check the SLEE configuration file.

LCP-0164: POSREQ plugin: Unable to create dialog to TCAP interface.


LCP-0173: POSREQ plugin: IS41 Error - Missing Parameter

IS41 MSC/HLR POSREQ error.

LCP-0174: POSREQ plugin: IS41 Error - Feature Inactive





Errors (continued)

Alarm Text Reason Remedy LCP-0175: POSREQ plugin: IS41 Error - Parameter Error


LCP-0176: POSREQ plugin: IS41 Error - Operation Sequence Problem


LCP-0180: POSREQ plugin config: 'mscMktId' MSC Market-ID not set.

The option mscMktId is not set in LCP.posreqPlugin in eserv.config.


LCP-0181: POSREQ plugin config: 'mscSwId' MSC Switch-ID not set.

The option mscSwId is not set in LCP.posreqPlugin in eserv.config.


LCP-0183: SRI plugin: config section LCP.sriPlugin not found.


Check eserv.config.

LCP-0184: SRI plugin config: tcapIF not set.

The option tcapIF is not set in LCP.sriPlugin in eserv.config.

LCP-0185: SRI plugin config: ‘gmscAddress’ not set.

The option gmscAddress is not set in LCP.sriPlugin in eserv.config.


LCP-0186: SRI plugin: unable to find TCAP interface.

The SRI plugin cannot locate the Tcap Interface.

Check configuration section LCP.sriPlugin and check the SLEE configuration file.

LCP-0187: SRI plugin: Unable to create dialog to TCAP interface.


This table defines the warning messages for locApp and macro nodes. Warnings

Alarm Text Reason Remedy LCP-0007: Cached location more recent

The result retrieved from the Location Server is older than the cached result. The clocks on the machines could be out of synch.

LCP-0014: Unknown command line option







Warnings (continued)

Alarm Text Reason Remedy LCP-0015: Missing argument for


LCP-0070: Invalid cache size


LCP-0071: Invalid cache entry expiry time


LCP-0049: Location query timed out.

The query to the Location Server is timed out.

LCP-0074: Invalid responde deadline

Invalid command command value set.

LCP-0080: Too many plugin defined.

More than 10 plugins are specified in lcp_plugin.

LCP-0096: node(s) failed to register with ACS.

Final error message detailing the macro nodes which have failed to register with ACS.

LCP-0133: Unable to process the current location.

Bad current location received by the locApp.


LCP-0144: Bad shape definition in profile encountered.

Check the profile to ensure the shape encoding is correct.


LCP-0165: POSREQ plugin: No MSStatus or Cell ID returned.

The response received back from the HLR/MSC does not contain the required parameters.


LCP-0166: POSREQ plugin: No MSC Routing Address returned.

The response received back from the HLR does not contain the required parameter.


LCP-0167: POSREQ plugin: Unknown TCAP component type received.

The POSREQ plugin cannot handle the response received back from the HLR/MSC.


LCP-0168: POSREQ plugin: Unknown Invoke ID received.

Incorrect invoke ID is returned in the POSREQ reply.






Warnings (continued)

Alarm Text Reason Remedy LCP-0169: POSREQ plugin: TCAP ABORT received.

The POSREQ plugin received a TCAP ABORT while waiting for a response from the HLR/MSC, this may indicate a network failure.


LCP-0170: POSREQ plugin: Event from unknown dialog received.

The response received by the POSREQ plugin was unexpected.


LCP-0172: Invalid handle retrieved for Slee Dialog.

The locApp cannot find the specified SLEE dialog in its internal dialog map.


LCP-0188: SRI plugin: TCAP ABORT received.

The SRI plugin received a TCAP ABORT while waiting for a response from the HLR/MSC, this may indicate a network failure.


LCP-0189: SRI plugin: Unknown Invoke ID received.

Incorrect invoke ID is returned in the SRI reply.


LCP-0190: SRI plugin: Unknown TCAP primitive type received.

The SRI plugin cannot handle the response received back from the HLR/MSC.


LCP-0191: SRI plugin: Unknown TCAP component type received.

The SRI plugin cannot handle the response received back from the HLR/MSC.


LCP-0192: SRI plugin: Event from unknown dialog received.

The response received by the SRI plugin was unexpected.


LCP-0193: SRI plugin: No MSRN returned.

The response received back from the HLR/MSC does not contain the required parameters.


ATIMNP plugin: NO MNP DB Address given, check the eserv.config file.

The option mnpDbAddress is not set in LCP atimnpPlugin (on page 18) in eserv.config.

Check the eserv.config file.



Chapter 7

Pre-installation Overview

This chapter explains the pre-installation configuration requirements of the application.

Introduction


Installation Pre-requisites .............................................................................. 66 Preparing the System .................................................................................... 67

In this chapter

Technical Guide


Installation Pre-requisites Check that your Oracle version is correct. Checking Oracle

version As acs_oper (or whichever user is appropriate) logon to sqlplus as "/", e.g.:

bash-2.05$ sqlplus /

The resulting messages show the Oracle version in use:

SQL*Plus: Release 9.2.0.4.0 - Production on Fri Jul 22 06:55:45 2005

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:

Oracle9i Release 9.2.0.4.0 - 64bit Production

JServer Release 9.2.0.4.0 - Production

Use the pkginfo utility to check the versions of Oracle application packages on each node.

Checking Oracle application versions - cmn

For more information about:

• which versions are required, see the list under the machine name in this topic. • using pkginfo, see Checking installed packages (on page 48).

Check that your Solaris version is correct. The version required is listed under the machine names in this topic.

Checking software on Solaris

Example commands: You can check your Solaris version by using the commands:

• uname -r, and

• pkginfo

For more information about finding out your Solaris version, see your Solaris documentation.



Preparing the System It is recommended that you check the kernel parameters on the system to ensure the system is optimally configured.

Introduction

The following parameters are described in the respective Technical guides. However, they are collated here for reference.

Checking ernel parameters

K

Note: Actual kernel parameters may be greater than those listed here.

Follow these steps to check the Kernel parameters for Solaris 9.

Step Action 1 Log in as root.

2 Type cat /etc/system

3 Check the parameters are set to at least the minimum values. 4 Change the parameters as required using the following command from

/etc/system.




Chapter 8

Installation Overview

This chapter explains how to install the application. Introduction


Loading the Distribution File .......................................................................... 70 Installing LCP on an SCP .............................................................................. 71 Installing LCP on an SMS ............................................................................. 78 Checking the Installation ............................................................................... 85

In this chapter

You need to Install LCP on both the SCP and SMS. Installation order

Install on the SCP, then the SMS - so that the data is replicated to the SCP after the SMS has been installed.

Technical Guide


Loading the Distribution File Before you can install the application packages, you must load them in an installation directory on the correct machines. This procedure copies and registers packages from the distribution file on to the system.

Introduction

You must repeat this procedure on every machine. If your application packages have already been loaded, you do not have to complete this procedure.

This procedure copies the distribution file into the /tmp directory. The installation procedure assumes that the /tmp directory has been used.

Installation directory

Follow these steps to load the distribution file. Procedure

Step Action 1 Ensure you are logged onto the machine as root.

2 Copy the distribution file into the /tmp directory. The application's distribution file will be distributed on either CD or from an FTP location. If you do not either have a CD or know the correct FTP location, please contact your Oracle contact. The packages are often distributed in one large compressed file (for example, sms.tar.gz).

3 Check whether the distribution file is compressed (zipped). You can usually determine this by the file extension: .gz or .tgz will mean the file is compressed. Occasionally, the file extension will be incorrect, or the file will fail to uncompress or untar. If it is available, you can use the file command to attempt to determine the type of file by checking its contents. If the distribution file is: • not compressed, go to Step 4. • compressed, uncompress the file. Example commands: • gunzip <filename>, or • gzip –d <filename>

Where: <filename> is the distribution file

Result: This uncompresses the distribution file. 4 If the distribution file is:

• .pkg file, no further actions are required to load the distribution file. • a tar ball, untar the distribution. Example command: tar –xvf <filename> • Where:

<filename> is the uncompressed distribution file. Result: Untarring unzips the packages into the /tmp directory and will create an install sub-directory.

During installation, the installation script will overwrite any previously installed files in /IN/service_packages and /IN/html. If you want to keep these files, move them before starting the installation.

Before you begin



Installing LCP on an SCP The table below provides a sample of the text displayed during an lcpScp package install on the UAS machine.

Installing lcpScp

Script Output Action pkgadd -d lcpScp Type this command to start the

installation.

Processing package instance <lcpScp> from </volA/packages/LCP> LCP SCP installation (sun4u) 1.0.0 Oracle The selected base directory </IN/service_packages/LCP> must exist before installation is attempted.

This output displays: • the location of the installation script• the version of the software that is

being installed, and • information about the steps being

performed by the script.

Do you want this directory created now [y,n,?,q]

Type y to continue with the installation.If you type anything other than y, the script will abort.

Using </IN/service_packages/LCP> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package.

This output indicates the directory LCP will be installed into. No action is required.

Do you want to continue with the installation of <lcpScp> [y,n,?]

Type y to continue with the installation.

Installing LCP SCP installation as <lcpScp> ## Executing preinstall script. NOTE: Installing lcpScp into /IN/service_packages/LCP NOTE: Creating account lcp_oper ## Installing part 1 of 1. /IN/service_packages/LCP/bin/locApp /IN/service_packages/LCP/bin/removeLcpSem.sh /IN/service_packages/LCP/db/install/create/SCP

The installation will continue.




Installing LCP on an SCP, Continued


Installing lcpScp (continued)

Script Output Action ... ... /IN/service_packages/LCP/lib/liblcpmacronodes.so /IN/service_packages/LCP/lib/liblcpposreq.so [ verifying class <none> ] ## Executing postinstall script. * lcpScp installation script ./lcpScp.conf.sh * installing into /IN/service_packages/LCP

NOTE: Please enter a password for lcp_oper in order to unlock the account for remote access.

Type the UNIX password for lcp_oper user

passwd: password successfully changed for lcp_oper * The configuration of lcpScp Database will now begin. Access to the LCP technical guide is recommended.

The password will be assigned to the lcp_oper user and the installation will continue.

* Please enter the password for the SCP user on the SCP instance (default: X) [?]

Type: • the Oracle password for SCP user,

or • press Enter to accept the default

(where X is the default password).

* Please enter the password for the SYSTEM user on the SCP instance (default: X) [?]

Type: • the Oracle password for SYSTEM

user, or • press Enter to accept the default


* Please enter the password for the SYS user on the SCP instance (default: X) [?]

Type: • the Oracle password for SYS user,








Script Output Action * Adding LCP to existing SCP database NOTE: Creating LCP tables for database SCP .... NOTE: Creating LCP triggers for database SCP .... * lcpScp database tables were installed. ******************************************* * NOTE: lcpScp SCP Database installation complete ******************************************* * The configuration of Location Application (locApp) and the plugins will now begin. Access to the LCP and SLEE technical guides are recommended.

Result: The database will be installed onto the SCP instance

Please enter the SLEE startup file name (default: /IN/service_packages/SLEE/bin/slee.sh) [?]

Type: • the name of the SLEE startup file,

or • press Enter to accept the default.

* Updating SLEE startup file... * SLEE startup file update successful

The SLEE startup file will be updated for LCP.

Please enter the SLEE configuration file name (default: /IN/service_packages/SLEE/etc/SLEE.cfg) [?]

Type: • the name of the SLEE

configuration file, or • press Enter to accept the default. Result: Questions will be asked to determine defaults for the LCP application.

Please enter the SLEE service key of the Location Application (locApp) (default: 15) [?]

Type: • the SLEE service key for LCP

(locApp), or • press Enter to accept the default.

Please enter the number of locApp instances to run (default: 1) [?]

Type: • the number of locApp instances, or• press Enter to accept the default.

* Updating SLEE configuration file... * SLEE configuration file update successful. * Creating locApp startup file... * locApp startup file creation successful.

The SLEE configuration file will be updated for LCP.






Script Output Action Please enter the eserv.config file name (default: /IN/service_packages/eserv.config) [?]

Type: • the name of the eserv.config

configuration file, or • press Enter to accept the default.

* Creating locApp configuration answer file... * locApp configuration answer file creation successful.

The config filenames will be stored in an answer file for use during un-installation.

Please enter the timer interface handle (default: Timer) [?]

Type: • the name of the SLEE timer

interface, or • press Enter to accept the default.

Please enter the cache size (number of responses) locApp caches (default: 100000) [?]

Type: • the size of the locApp cache, or • press Enter to accept the default.

Please enter the cache expiry timer (default: 600) [?]

Type: • the time for cache entry expiry, or • press Enter to accept the default

(10 mins).

Please enter the response deadline in seconds (default: 2) [?]

Type: • the deadline for a response from

the HLR/MSC for a location request, or

• press Enter to accept the default (2 secs).

* locApp Plugin configuration... 0...All Plugins 1...GSM ATI Plugin 2...IS41 POSREQ Plugin 3...GSM SRI Plugin

The eserv.config will be updated for the locApp with the chosen values.

Please choose which plugins to configure. [?]

Type 0, 1, 2, or 3 – depending on the required plugin configuration.

* You have chosen plugin configuration: 0 Result: The installation continues using the selected plugin configuration. In this example, configuration 0 was chosen, to display the script for installing all plugins. If you chose one plugin, you will not be prompted to install any other plugin.






Script Output Action Please enter the configuration for the GSM ATI plugin... For the next section of configuration, access to the GSM 29.002 and GSM 03.32 is recommended.

Beginning of installation of the ‘GSM ATI' plugin.

Please enter the GSM SCF address for the ATI plugin [?]

Type the GSM SCF (global title) address for the SCP, for example ‘441234555666’ (Refer to your network support department for more information).

Please enter the Tcap interface handle [?] Type the name of the HLR TCAP interface (refer to your SLEE TCAP interface technical guide for more information).

Please enter the constant "C" for location uncertainty as specified in GSM 03.32 [?]

Type the “C” constant to use during conversion from ATI Cell IDs to Geographical Locations (refer to GSM standard 03.32 for guidance on the value to enter).

Please enter the constant "x" for location uncertainty as specified in GSM 03.32 [?]

Type the “X” constant to use during conversion from ATI Cell IDs to Geographical Locations (refer to GSM standard 03.32 for guidance on the value to enter).

End of installation of the ‘GSM ATI' plugin.

Please enter the configuration for the IS41 POSREQ plugin...

Beginning of installation of the ‘IS41 POSREQ' plugin.

Please enter the IS41 SCF PC address for the POSREQ plugin [?]

Type the IS-41 PC (point code) address for the SCP, for example ‘12’ (Refer to your network support department for more information).

Please enter the IS41 SCF SSN address for the POSREQ plugin [?]

Type the IS41 SSN (subsystem number) address for the SCP, for example ‘5’ (Refer to your network support department for more information).

Please enter the IS41 HLR SSN address for the POSREQ plugin [?]

Type the IS-41 SSN (subsystem number) address for the SCP, for example ‘6’ (Refer to your network support department for more information).






Script Output Action Please enter the IS41 MSC Market ID for the POSREQ plugin [?]

Type the IS-41 Originating MSC ID (Market ID part), for example '14656' (Refer to your network support department for more information).

Please enter the IS41 MSC Switch ID for the POSREQ plugin [?]

Type the IS-41 Originating MSC ID (Switch ID part), for example ‘1’ (Refer to your network support department for more information).

Please enter the Tcap interface handle [?] Type the name of the HLR/MSC TCAP interface (refer to your SLEE TCAP interface technical guide for more information).

End of installation of the ‘IS41 POSREQ' plugin.

Please enter the configuration for the GSM SRI plugin... For the next section of configuration, access to the GSM 29.002 and GSM 03.32 is recommended.

Beginning of installation of the ‘GSM SRI' plugin.

Please enter the GMSC address for the SRI plugin [?] Type the GMSC (global title) address for the SCP, for example ‘441234567890’ (Refer to your network support department for more information).

Please enter the Tcap interface handle [?] Type the name of the HLR/MSC TCAP interface (refer to your SLEE TCAP interface technical guide for more information).

Updating eserv.config (/IN/service_packages/eserv.config) used by locApp and the plugins... eserv.config update successful. locApp configuration completed successfully. The configuration of LCP ACS components will now begin.Access to the LCP and ACS technical guides are recommended. Note that the replication interface is required for the Set My Zone node. Updating acs_oper .profile-scp file for LCP shared libraries... /IN/service_packages/ACS/.profile-scp updated successfuly.

The eserv.config file will be updated with the chosen values and the installation will continue.






Script Output Action Please enter the slee_acs configuration file. (default: /IN/service_packages/ACS/etc/acs.conf) [?]

Type: • the name of the ACS configuration

file, or • press Enter to accept the default.

* Updating slee_acs configuration file... * /IN/service_packages/ACS/etc/acs.conf updated successfuly. * Updating eserv.config (/IN/service_packages/eserv.config)... * /IN/service_packages/eserv.config updated successfully. * lcpScp has been fully installed in /IN/service_packages/LCP

The ACS configuration file will be updated and the installation will continue.

Installation of <lcpScp> was successful. The lcpScp package has been successfully installed and configured. Any other message will indicate a failed installation. Refer to the install log file for more information.


Installing LCP on an SMS The table below provides a sample of the text displayed during an lcpSms package install on a single (i.e. unclustered database) USMS machine.

Installing lcpSms on a single USMS

Script Output Action pkgadd -d lcpSms Type this command to start the

installation.

Processing package instance <lcpSms> from </global/dg-smf1/shared/packages/LCP> LCP SMS installation (sun4u) 1.0.0 Oracle The selected base directory </IN/service_packages/LCP> must exist before installation is attempted.





Type y (to create the directory).


The installation will continue in the newly created directory.

Do you want to continue with the installation of <lcpSms> [y,n,?]

Type y (to continue with the installation).

Installing LCP SMS installation as <lcpSms> ## Executing preinstall script. NOTE: Installing lcpSms into /IN/service_packages/LCP NOTE: Creating account lcp_oper ## Installing part 1 of 1. /IN/html/LCP/error/1.LCP_CONVERSION__PK /IN/html/LCP/error/1.LCP_MAPPING__PK


...

... /IN/service_packages/LCP/lib/cmnInstallLib.sh /IN/service_packages/LCP/lib/liblcpalarms.so [ verifying class <none> ] ## Executing postinstall script. * lcpSms installation script ./lcpSms.conf.sh * installing into /IN/service_packages/LCP




Installing LCP on an SMS, Continued


Installing lcpSms on a single USMS (continued)

Script Output Action NOTE: Please enter a password for lcp_oper in order to unlock the account for remote access.

Type the UNIX password for lcp_oper user.

passwd: password successfully changed for lcp_oper * The configuration of lcpSms Database will now begin. Access to the LCP technical guide is recommended.


* Please enter the password for the SMF user on the SMF1 instance (default: X) [?]

Type: • the Oracle password for the SMF

user (on the SMF1 database instance), or

• press Enter to accept the default (where X is the default password).

* Please enter the password for the SYSTEM user on the SMF1 instance (default: X) [?]

Type: • the Oracle password for the

SYSTEM user (on the SMF1 database instance), or


* LCP Plugin configuration... 0...All Plugins 1...GSM ATI Plugin 2...IS41 POSREQ Plugin 3...GSM SRI Plugin

Please choose which plugins to configure. [?]

Type 0, 1, 2 or 3 – depending on the required plugin configuration.

* You have chosen plugin configuration: 0 Result: The installation continues using the selected plugin configuration.

Is the database instance on a remote node ? Type: • n if the database is locally

installed, or • y if the database is on a remote

node.

Enter the ORACLE datafile path on the remote node (e.g. /volB/oracle/data/dbf1)

Result: If the database is on a remote node, you see this prompt. Type the path to the Oracle data files (refer to SMS Technical Guide for more information).





Installing lcpSms on a single USMS (continued)

Script Output Action * Add tables to database SMF1 now? [y,n,?]

Type y (to add the database tables to the SMF1 instance of the database).

* Adding LCP to existing SMF database NOTE: Creating LCP tables for database SMF1 .... NOTE: Creating LCP triggers for database SMF1 .... NOTE: Creating LCP screen permissions .... NOTE: Creating LCP replication for database SMF1 .... NOTE: Creating LCP statistics definitions .... NOTE: Creating LCP macro nodes for database SMF1 .... NOTE: Installing Home and Work zones, and default plugin .... NOTE: Installing POSREQ plugin .... * lcpSms database tables were installed.

The database will be configured and the installation will continue.

* Creating LCP profiles * Creating /IN/service_packages/LCP/.profile-sms ****************************************************************** * NOTE: lcpSms SMF Database installation complete ****************************************************************** * The configuration of lcpSms Java / Html will now begin. Access to the LCP technical guide is recommended. * Adding java archives to sms html file /IN/html/sms.html * Java archives added to sms html file ****************************************************************** * NOTE: lcpSms SMF Java / Html installation complete ****************************************************************** * lcpSms has been fully installed in /IN/service_packages/LCP

Installation of <lcpSms> was successful. The lcpSms package has been successfully installed and configured. Any other message will indicate a failed installation. Refer to the install log file for more information.




The table below provides a sample of the text displayed during an lcpSms package install on a clustered USMS installation.

Installing lcpSms on a clustered USMS

Script Output Action pkgadd -d lcpSms Type this command to start the

installation.

Processing package instance <lcpSms> from </global/dg-smf1/shared/packages/LCP> LCP SMS installation (sun4u) 1.0.0 Oracle The selected base directory </IN/service_packages/LCP> must exist before installation is attempted.





Type y (to create the directory).


The installation will continue in the newly created directory.

Do you want to continue with the installation of <lcpSms> [y,n,?]

Type y (to continue with the installation).

Installing LCP SMS installation as <lcpSms> ## Executing preinstall script. NOTE: Installing lcpSms into /IN/service_packages/LCP NOTE: Creating account lcp_oper ## Installing part 1 of 1. /IN/html/LCP/error/1.LCP_CONVERSION__PK /IN/html/LCP/error/1.LCP_MAPPING__PK ... ... /IN/service_packages/LCP/lib/cmnInstallLib.sh /IN/service_packages/LCP/lib/liblcpalarms.so [ verifying class <none> ] ## Executing postinstall script. * lcpSms installation script ./lcpSms.conf.sh * installing into /IN/service_packages/LCP







Installing lcpSms on a clustered USMS (continued)

Script Output Action NOTE: Please enter a password for lcp_oper in order to unlock the account for remote access.

Type the UNIX password for lcp_oper user.

passwd: password successfully changed for lcp_oper * The configuration of lcpSms Database will now begin. Access to the LCP technical guide is recommended.


* NOTE: The smsSms package has been installed in CLUSTERED mode. * The LCP tables should only be added to the SMF database * if this node is the primary node of the cluster.

Installation for Clustered mode.

* Is this node the primary node of the cluster?

• y (if this is the primary node in the cluster,

• n if this is the secondary node) Result: The database element of the package will be installed on the primary node only.

* Please specify the ORACLE_SID to use when configuring the database. (default: SMF1) [?]

Type the name of the ORACLE_SID for the current node, or press <enter> to accept the default.







SYSTEM user (on the SMF1 database instance), or


* LCP Plugin configuration... 0...All Plugins 1...GSM ATI Plugin 2...IS41 POSREQ Plugin 3...GSM SRI Plugin






Script Output Action Please choose which plugins to configure. [?]

Type 0, 1, 2 or 3 – depending on the required plugin configuration.

* You have chosen plugin configuration: 3 Result: The installation continues using the selected plugin configuration.

This is a clustered SMS installation. You must now enter the raw partitions that should be used to create the LCP_DATA and LCP_INDEX tablespaces, e.g. /dev/did/rdsk/d15s0 and d15s1

Please enter the raw partition that should be used to create the LCP_DATA tablespace [?]

Type the name of the raw device on which to store the LCP_DATA tablespace (refer to the Oracle sizing spreadsheet for more information).

Please enter the raw partition that should be used to create the LCP_INDEX tablespace [?]

Type the name of the raw device on which to store the LCP_INDEX tablespace (refer to the Oracle sizing spreadsheet for more information).

If the database is clustered and this is: • the primary node, you need to add

tables to the database. • the secondary node, the

installation will skip straight to creating LCP profiles.

* Add tables to database SMF1 now? [y,n,?]

Type y (to add the database tables to the SMF1 instance of the database).

* Adding LCP to existing SMF database NOTE: Creating LCP tables for database SMF1 .... NOTE: Creating LCP triggers for database SMF1 .... NOTE: Creating LCP screen permissions .... NOTE: Creating LCP replication for database SMF1 .... NOTE: Creating LCP statistics definitions .... NOTE: Creating LCP macro nodes for database SMF1 .... NOTE: Installing Home and Work zones, and default plugin .... NOTE: Installing POSREQ plugin .... * lcpSms database tables were installed.

The database will be configured and the installation will continue.






Script Output Action * Creating LCP profiles * Creating /IN/service_packages/LCP/.profile-sms ****************************************************************** * NOTE: lcpSms SMF Database installation complete ******************************************************************

* The configuration of lcpSms Java / Html will now begin. Access to the LCP technical guide is recommended. * Adding java archives to sms html file /IN/html/sms.html * Java archives added to sms html file ****************************************************************** * NOTE: lcpSms SMF Java / Html installation complete ****************************************************************** * lcpSms has been fully installed in /IN/service_packages/LCP

Installation of <lcpSms> was successful. The lcpSms package has been successfully installed and configured. Any other message will indicate a failed installation. Refer to the install log file for more information.


Checking the Installation Once the installation is complete, refer to this checklist to ensure that installation has been successful.

Checklist

Step Action Check 1 On the USMS, check that the following tables are available:

• LCP_CONVERSION • LCP_MAPPING • LCP_PLUGIN

2 On the USMS, check that replication groups are available for the above tables from the Replication tab in the SMS user screens and a configuration file can be generated.

3 On the UAS, check that the following tables are available: • LCP_CONVERSION • LCP_MAPPING • LCP_PLUGIN

4 On the UAS, check that the following has been inserted into SLEE.cfg (note that the parameters will vary depending on the installation): APPLICATION=locApp locApp.sh /IN/service_packages/LCP/bin 1 1 SERVICE=locApp 1 locApp locApp SERVICEKEY=INTEGER 13 locApp

5 Check that the following line is in acs.conf under the acsChassis section (note the two spaces at the beginning of the line): MacroNodePluginFile liblcpmacronodes.so

As the locApp starts, it creates a file /tmp/lcp-semkey containing the semaphore key that it uses. This semaphore is removed before the SLEE starts up (the command to remove the semaphore is inserted to the SLEE startup script and run just before the binary sleeStartup is invoked).

Location Application semaphore

If, for whatever reason, the semaphore is not removed and the locApp is not starting up correctly, examine content of the file and remove the semaphore by using the Unix program ipcs.

For more details on ipcs, see man -s1 ipcs.

All the LCP shared libraries reside in /IN/service_packages/LCP/lib. They are described below.

Shared libraries

Name Description liblcpati.so The locApp ATI plugin.

liblcpposreq.so The locApp POSREQ plugin.

liblcpsrimsrn.so The locApp SRI-MSRN plugin.

liblcpsriimsi.so The locApp SRI-IMSI plugin.

liblcpalarms.so The LCP alarms library. This library contains all the alarm texts.




Checking the Installation, Continued


Shared libraries (continued)

Name Description liblcpacschassis.so The LCP ACS chassis action handler.

Responsible for sending location queries/processing location responses from the locApp. It is also responsible for retrieving the calling party and called party number and NoA from the ACS Chassis context (as these values are not available at the Engine level).

liblcpCurrentLocProcessor.so The library contains information on how to process the current location. Currently it understands how to process Cell ID, LAI, LocationNumber and MapGeographicInformation as the current location. GSM 24.008 states that the coding of the Cell ID and LAI is the responsibility of the administration. Currently the Current Location Processor only supports Cell ID and LAI coded as BCD digits.

liblcpmacronodes.so The LCP ACS macro nodes. The library contains the feature nodes: • “In The Zone”, • “Set My Zone” and • “Store My Location”.


Chapter 9

Removal Overview

This chapter explains how to remove the application. Introduction


Removing LCP from an SCP ........................................................................ 88 Removing LCP from an SMS ........................................................................ 91

In this chapter



Removing LCP from an SCP The table below provides a sample of the text displayed during an lcpScp package removal from the UAS machine.

Removing lcpScp

Script Output Action pkgrm lcpScp Type this command to start removal.

The following package is currently installed: lcpScp LCP SCP installation (sun4u) 1.0.0

Do you want to remove this package? [y,n,?,q]

Type y (to remove the package, n to abort the removal).

## Removing installed package instance <lcpScp> This package contains scripts which will be executed with super-user permission during the process of removing this package.

Do you want to continue with the removal of this package [y,n,?,q]

Type y (to continue with the package removal).

## Verifying package dependencies. ## Processing package information. ## Executing preremove script. The unconfiguration of Location Application (locApp) will now begin. Loading locApp configuration answer file...locApp configuration answer file loaded successfully. Undoing changes to eserv.config... eserv.config updated successfully. Undoing changes to SLEE startup file... SLEE startup file updated successfully. Undoing changes to SLEE configuration file... SLEE configuration file updated successfully.

Removal will continue.

Removing locApp startup file... File removed successfully. locApp unconfiguration completed successfully. The unconfiguration of LCP ACS components will now begin. Loading LCP ACS component configuration answer file... LCP ACS component configuration answer file loaded successfully.




Removing LCP from an SCP, Continued


Removing lcpScp (continued)

Script Output Action Undoing changes made to ACS configuration file... ACS configuration file updated successfully. Undoing changes made to ACS .profile-scp file... ACS .profile-scp updated successfully. LCP ACS component unconfiguration successful. The unconfiguration of lcpScp Database will now begin. Access to the LCP technical guide is recommended.

* Please enter the password for the SCP user on the SCP instance (default: X) [?]

Type: • the Oracle password for SCP user,



* Please enter the password for the SYSTEM user on the SCP instance (default: X) [?]

Type: • the Oracle password for SYSTEM

user, or • press Enter to accept the default


NOTE: Removing LCP triggers for database SCP .... NOTE: Removing LCP tables for database SCP .... * lcpScp database objects were removed.

Removal will continue.

****************************************************************** * NOTE: lcpScp SCP Database removal complete ****************************************************************** ## Removing pathnames in class <none> /IN/service_packages/LCP/tmp <non-empty directory not removed> /IN/service_packages/LCP/lib/liblcpposreq.so ... ...



Removing LCP from an SCP, Continued


Removing lcpScp (continued)

Script Output Action /IN/service_packages/LCP/bin/acsComponentsInstall.sh /IN/service_packages/LCP/bin <non-empty directory not removed> ## Executing postremove script. NOTE: Removing user & base directory. ## Updating system information.

Removal of <lcpScp> was successful. The lcpScp package has been successfully removed. Any other message will indicate a failed removal. Refer to the install log file for more information.


Removing LCP from an SMS Note that prior to removing the lcpSms package from the SMS, please ensure that you have backed-up and removed the call plans that use any of the LCP macro nodes (In The Zone, Set My Zone, Store My Location). These call plans will be invalidated during package removal and may cause unexpected results if an attempt is made to use them. Refer to the CPE User's Guide for more information on call plan backup and removal procedures.

Before removing lcpSms

The table below provides a sample of the text displayed during an lcpSms package removal from a single (unclustered) SMS machine.

Removing lcpSms from a single SMS

Script Output Action pkgrm lcpSms Type this command to start removal.

The following package is currently installed: lcpSms LCP SMS installation (sun4u) 1.0.0



## Removing installed package instance <lcpSms> This package contains scripts which will be executed with super-user permission during the process of removing this package.



## Verifying package dependencies. ## Processing package information. ## Executing preremove script. The unconfiguration of lcpSms Java / Html will now begin. Access to the LCP technical guide is recommended. * Removing jar file references for LCP screens from /IN/html/sms.html * Removing /IN/html/LCP

****************************************************************** * NOTE: lcpSms SMF Java / Html removal complete ****************************************************************** The unconfiguration of lcpSms Database will now begin. Access to the LCP technical guide is recommended.




Removing LCP from an SMS, Continued


Removing lcpSms from a single SMS (continued)

Script Output Action Is the database instance on a remote node ? Type:

• n if the database was locally installed, or

• y if the database was installed on a remote node







MANAGER user (on the SMF1 database instance), or


NOTE: Removing LCP macro nodes .... NOTE: Removing LCP statistics definitions .... NOTE: Removing LCP replication for database SMF1 .... NOTE: Removing LCP screen permissions .... NOTE: Removing LCP triggers for database SMF1 .... NOTE: Removing LCP tables for database SMF1 .... * lcpSms database objects were removed.

The database removal will continue

* NOTE: lcpSms SMF Database removal complete ****************************************************************** ## Removing pathnames in class <none> /IN/service_packages/LCP/tmp /IN/service_packages/LCP/log/javaLcpConversionLoader ... ... /IN/html/LCP/error /IN/html/LCP ## Executing postremove script. NOTE: Removing user & base directory. ## Updating system information.




Removing lcpSms from a single SMS (continued)

Script Output Action Removal of <lcpSms> was successful. The lcpSms package has been

successfully removed. Any other message will indicate a failed removal. Refer to the install log file for more information.

The table below provides a sample of the text displayed during an lcpSms package removal from a clustered SMS installation.

Removing lcpSms from a clustered SMS

Script Output Action pkgrm lcpSms Type this command to start removal.

The following package is currently installed: lcpSms LCP SMS installation (sun4u) 1.0.0



## Removing installed package instance <lcpSms> This package contains scripts which will be executed with super-user permission during the process of removing this package.



## Verifying package dependencies. ## Processing package information. ## Executing preremove script. The unconfiguration of lcpSms Java / Html will now begin. Access to the LCP technical guide is recommended. * Removing jar file references for LCP screens from /IN/html/sms.html * Removing /IN/html/LCP ****************************************************************** * NOTE: lcpSms SMF Java / Html removal complete ****************************************************************** The unconfiguration of lcpSms Database will now begin. Access to the LCP technical guide is recommended.






Removing lcpSms from a clustered SMS (continued)

Script Output Action * NOTE: The smsSms package has been installed in CLUSTERED mode. * The LCP tables should only be removed from the SMF * database if this node is the primary node of the cluster.

* Is this node the primary node of the cluster?

Type: • y if this is the primary node in the

cluster, • n if this is the secondary node If this is: • the primary node, the database

element will be removed from the primary node only.

• the secondary node, the package removal will skip to removing pathnames.

* Please specify the ORACLE_SID to use when configuring the database. (default: SMF1) [?]

If this is the primary node, you see this script. Type: • the name of the ORACLE_SID for

the current node, or • press Enter to accept the default.







MANAGER user (on the SMF1 database instance), or






Removing lcpSms from a clustered SMS (continued)

Script Output Action NOTE: Removing LCP macro nodes .... NOTE: Removing LCP statistics definitions .... NOTE: Removing LCP replication for database SMF1 .... NOTE: Removing LCP screen permissions .... NOTE: Removing LCP triggers for database SMF1 .... NOTE: Removing LCP tables for database SMF1 .... * lcpSms database objects were removed. * NOTE: lcpSms SMF Database removal complete ******************************************************************

The database removal will continue

## Removing pathnames in class <none> /IN/service_packages/LCP/tmp /IN/service_packages/LCP/log/javaLcpConversionLoader ... ... /IN/html/LCP/error /IN/html/LCP ## Executing postremove script. NOTE: Removing user & base directory. ## Updating system information.

Removing pathnames.

Removal of <lcpSms> was successful. The lcpSms package has been successfully removed. Any other message will indicate a failed removal. Refer to the install log file for more information.



Appendix

Overview

This appendix contains the following topics. In this appendix

Glossary of Terms ......................................................................................... 99 Index ............................................................................................................ 103

Technical Guide


Glossary of Terms

Advanced Control Services configuration platform. ACS

Any Time Interrogation - this process is used on a GSM network to interrogate the HLR for location and or subscriber information.

ATI

Country Code. Prefix identifying the country for a numeric international address. CC

Transport level ink between two peers, providing for multiple sessions. Connection

Control Plan Editor (previously Call Plan Editor) - software used to define the logic and data associated with a call - e.g. "if the subscriber calls 0800 nnnnnn from a phone at location xxx then put the call through to bb bbb bbbb".

CPE

Unix utility for scheduling tasks. cron

File used by cron. crontab

Database DB

Detection Point DP

Event Detail Record EDR

Note: Previously CDR. The industry standard for CDR is EDR (Event Detail Record). Over time EDR will replace CDR in the Oracle documentation.

FDA

First Delivery Attempt - the delivery of a short message directly to the SME rather than relaying it via the MC.

File Transfer Protocol - protocol for electronic transfer of files FTP

Gateway MSC. The first MSC which handles a call. For a MOC, this is the caller’s attached MSC. For an MTC, this is the first non-transit MSC in the subscriber’s network that receives the inbound call.

GMSC

General Packet Radio Service - employed to connect mobile cellular users to PDN (Public Data Network- for example the Internet).

GPRS

Global System for Mobile communication. GSM

It is a second generation cellular telecommunication system. Unlike first generation systems, GSM is digital and thus introduced greater enhancements such as security, capacity, quality and the ability to support integrated services.



Global Title. GT

The GT may be defined in any of the following formats: • Type 1: String in the form "1,<noa>,<BCD address digits>" • Type 2: String in the form "2,<trans type><BCD address digits>" • Type 3: String in the form "3,<trans type>,<num plan>,<BCD address digits>" • Type 4: String in the form "4,<trans type>,<num plan>,<noa>,<BCD address

digits>"

The contents of the Global Title are defined in the Q713 specification, please refer to section 3.4.2.3 for further details on defining Global Title.

The Home Location Register is a database within the HPLMN (Home Public Land Mobile Network). It provides routing information for MT calls and SMS. It is also responsible for the maintenance of user subscription information. This is distributed to the relevant VLR, or SGSN (Serving GPRS Support Node) through the attach process and mobility management procedures such as Location Area and Routing Area updates.

HLR

Home PLMN HPLMN

HyperText Markup Language, a small application of SGML used on the World Wide Web.

HTML

It defines a very simple class of report-style documents, with section headings, paragraphs, lists, tables, and illustrations, with a few informational and presentational items, and some hypertext and multimedia.

INAP message: Initial DP (Initial Detection Point) IDP

International Mobile Subscriber Identifier. A unique identifier allocated to each mobile subscriber in a GSM and UMTS network. It consists of a MCC (Mobile Country Code), a MNC (Mobile Network Code) and a MSIN (Mobile Station Identification Number).

IMSI

The IMSI is returned by the HLR query (SRI-SM) when doing FDA. This tells the MSC exactly who the subscriber is that the message is to be sent to.

Intelligent Network IN

Intelligent Network Application Part - a protocol offering real time communication between IN elements.

INAP

Initial Detection Point - INAP Operation. This is the operation that is sent when the switch reaches a trigger detection point.

Initial DP

Interim Standard 41 is a signaling protocol used in cellular telecommunications systems. It deals with the signalling between the MSC and other network elements for the purpose of handovers and roaming etc.

IS-41

Integrated Services Digital Network - set of protocols for connecting ISDN stations. ISDN

ISDN User Part - part of the SS7 protocol layer and used in the setting up, management, and release of trunks that carry voice and data between calling and called parties.

ISUP

International Telecommunication Union ITU



Location Capabilities Pack - set of software components used by other applications to look up the location of mobile devices.

LCP

Mobile Application Part - a protocol which enables real time communication between nodes in a mobile cellular network. A typical usage of the protocol would be for the transfer of location information from the VLR to the HLR.

MAP

Message Centre. Also known as SMSC. MC

Mobile Country Code. In the location information context, this is padded to three digits with leading zeros. Refer to ITU E.212 ("Land Mobile Numbering Plan") documentation for a list of codes.

MCC

Mobile Network Code. The part of an international address following the mobile country code (MCC), or at the start of a national format address. This specifies the mobile network code, i.e. the operator owning the address. In the location information context, this is padded to two digits with a leading zero. Refer to ITU E.212 ("Land Mobile Numbering Plan") documentation for a list of codes.

MNC

Mobile Number Portability MNP

Managed Object Class MOC

Mobile Station MS

Mobile Switching Centre. Also known as a switch. MSC

Mobile Station Identification Number. MSIN

Mobile Station ISDN number. Uniquely defines the mobile station as an ISDN terminal. It consists of three parts; the country code (CC), the national destination code (NDC) and the subscriber number (SN).

MSISDN

Mobile Station Roaming Number MSRN

Mobile Terminated MT

Mobile Terminated Call. The part of the call associated with a subscriber receiving an inbound call.

MTC

Message Transfer Part (part of the SS7 protocol stack). MTP

Nature Of Address - a classification to determine in what realm (Local, National or International) a given phone number resides, for the purposes of routing and billing.

NOA

Oracle Corporation Oracle

Open Service Access provides a standard interface through which developers can design services that may interact with functions within the network.

OSA

Point Code. The Point Code is the address of a switching point. PC

Public Land Mobile Network PLMN



Page 102 Location Capabilities Pack

IS-41 Position Request - process used in the IS-41 network to interrogate the HLR for location and subscriber information.

POSREQ

Signalling Connection Control Part (part of the SS7 protocol stack). SCCP

Service Control Function - this is the application of service logic to control functional entities in providing Intelligent Network services.

SCF

Service Control Point. Also known as UAS. SCP

Standard Generalized Markup Language. The international standard for defining descriptions of the structure of different types of electronic document.

SGML

Serving GPRS Support Node SGSN

Service Logic Execution Environment SLEE

Short Message Entity - an entity which may send or receive Short Messages. It may be located in a fixed network, a mobile, or an SMSC.

SME

Service Management Platform (also referred to as USMS). SMP

Short Message Service. SMS

Service Number SN

Structured Query Language - a database query language. SQL

Send Routing Information - This process is used on a GSM network to interrogate the HLR for subscriber routing information.

SRI

A Common Channel Signalling system used in many modern telecoms networks that provides a suite of protocols which enables circuit and non circuit related information to be routed about and between networks. The main protocols include MTP, SCCP and ISUP.

SS7

Subsystem Number. An integer identifying applications on the SCCP layer. SSN

Transaction Capabilities Application Part – layer in protocol stack, message protocol.

TCAP

Universal Application Server - hardware on which applications run. UAS

Universal Service Management System hardware platform. USMS

Unstructured Supplementary Service Data - a feature in the GSM MAP protocol that can be used to provide subscriber functions such as Balance Query and Friends and Family Access.

USSD

Visitor Location Register - contains all subscriber data required for call handling and mobility management for mobile subscribers currently located in the area controlled by the VLR.

VLR

Technical Guide


Index

2 cacheExpiry • 24

A

About this Document Audience • v Pre-requisites • v Related documents • v Scope • v

ACS • 2 actionHandlers • 36

eserv.config Configuration • 12 Alarm format

Alarm Topic Description • 52 Alarm generation

Alarm Topic Description • 52 Alarm Topic Description

Alarm format • 52 Alarm generation • 52 Further information • 53 Severity levels • 52

API • 57 Architectural overview

What is Location Capability Pack? • 3 ATI • 2 ATI Cell ID/LAI encoding

Data Encoding • 31 atimnpPlugin • 39, 63

eserv.config Configuration • 18 atiPlugin • 38

eserv.config Configuration • 13 Audience

About this Document • v

B

Before removing lcpSms Removing LCP from an SMS • 91

Before you begin Loading the Distribution File • 70

Bulk importing using command line Conversions - lcpConversionLoader • 32

Bulk importing using screens Conversions - lcpConversionLoader • 32

C

cacheSize • 23 CC • 101 CDR • 99 cellIdPadCharacter • 14 Checking configuration files

Common Troubleshooting Procedures • 50 Checking current processes

Common Troubleshooting Procedures • 48

Checking installed packages • 66 Common Troubleshooting Procedures • 48

Checking Kernel parameters Preparing the System • 67

Checking network connectivity Common Troubleshooting Procedures • 49

Checking Oracle Common Troubleshooting Procedures • 48

Checking Oracle application versions - cmn Installation Pre-requisites • 66

Checking Oracle version Installation Pre-requisites • 66

Checking software on Solaris Installation Pre-requisites • 66

Checking the Installation Checklist • 85 Location Application semaphore • 85 Shared libraries • 85

Checklist Checking the Installation • 85

Common Troubleshooting Procedures Checking configuration files • 50 Checking current processes • 48 Checking installed packages • 48 Checking network connectivity • 49 Checking Oracle • 48 Introduction • 48 Replication • 49

Components What is Location Capability Pack? • 2

concatenateLocInfo • 24, 31 Configuration

liblcpacschassis • 36 liblcpalarms • 37 liblcpati • 38 liblcpatimnp • 39 liblcpCurrentLocProcessor • 40 liblcpmacronodes • 41 liblcpposreq • 42 liblcpsri • 43 liblcpsriimsi • 44 liblcpsrimsrn • 45 locApp • 34

Configuration file format eserv.config Configuration • 9

Configuration Overview SCP configuration files • 8

Configuring the acs.conf on the SCP Example LCP section • 27 Introduction • 27 Parameters • 28

Connection • 102 Conversion bulk loader

Conversions - lcpConversionLoader • 32 Conversions - lcpConversionLoader • 35



Bulk importing using command line • 32 Bulk importing using screens • 32 Conversion bulk loader • 32 Import file format • 32

convertForHLR • 12 CPE • 41 Critical errors

LCP Alarms • 54 cron • 99 crontab • 33 currentLocation • 40

eserv.config Configuration • 22

D

Data Encoding ATI Cell ID/LAI encoding • 31 IS41 MSCID (Location Number) & serving

Cell ID encoding • 31 SRI-IMSI encoding • 31 SRI-MSRN encoding • 31

DB • 18 Denormalisation rules

Normalisation and Denormalisation • 4 destDir • 25 destSccpNOA • 21 destSSN • 14, 19, 21 Document Conventions

Icons • vi Typographical conventions • vi

DP • 100

E Editing the file

eserv.config Configuration • 10 EDR • 15 Errors

LCP Alarms • 55 eserv.config Configuration

actionHandlers • 12 atimnpPlugin • 18 atiPlugin • 13 Configuration file format • 9 currentLocation • 22 Editing the file • 10 eserv.config files delivered • 9 Example eserv.config file • 10 Global parameters • 11 Introduction • 9 Loading eserv.config configuration changes

• 26 locAPP • 23 posreqPlugin • 16 sriPlugin • 19

eserv.config files delivered eserv.config Configuration • 9

Example • 13, 15, 17, 19, 22, 23, 26 Example eserv.config file

eserv.config Configuration • 10 Example LCP section

Configuring the acs.conf on the SCP • 27

F FDA • 100 Feature nodes

What is Location Capability Pack? • 2 filePrefix • 26 flushPeriod • 25 forwardToMsc • 17 FTP • 70 Further information

Alarm Topic Description • 53

G

generateEDR • 15 Global parameters

eserv.config Configuration • 11 GMSC • 76 gmscAddress • 20 gmscMapNOA • 20 GPRS • 100 GSM • v gsmScfAddress • 13, 18 gsmScfMapNOA • 13, 18 GT • 18

H

HLR • 3 hlrGt • 22 hlrSSN • 16 HPLMN • 100 HTML • vi

I Icons

Document Conventions • vi IDP • 4 Import file format

Conversions - lcpConversionLoader • 32 IMSI • 2 IN • v INAP • 23 Initial DP • 100 Installation directory

Loading the Distribution File • 70 Installation order

Overview • 69 Installation Pre-requisites

Checking Oracle application versions - cmn • 66

Checking Oracle version • 66 Checking software on Solaris • 66

Installing LCP on an SCP Installing lcpScp • 71

Installing LCP on an SMS



Installing lcpSms on a clustered USMS • 81 Installing lcpSms on a single USMS • 78

Installing lcpScp Installing LCP on an SCP • 71

Installing lcpSms on a clustered USMS Installing LCP on an SMS • 81

Installing lcpSms on a single USMS Installing LCP on an SMS • 78

Introduction Common Troubleshooting Procedures • 48 Configuring the acs.conf on the SCP • 27 eserv.config Configuration • 9 LCP Alarms • 54 Loading the Distribution File • 70 Normalisation and Denormalisation • 4 Preparing the System • 67 Statistics • 5 What is Location Capability Pack? • 2

IS-41 • v IS41 MSCID (Location Number) & serving Cell

ID encoding Data Encoding • 31

ISDN • 100 ISUP • 102 ITU • 101

J javaLcpConversionLoader.sh

Location • 35 Purpose • 35

L LCP • v LCP Alarms

Critical errors • 54 Errors • 55 Introduction • 54 Warnings • 61

LcpCustomNoA • 12, 28 liblcpacschassis • 12

Configuration • 36 Location • 36 Purpose • 36 Startup • 36

liblcpalarms Configuration • 37 Location • 37 Purpose • 37

liblcpati • 13 Configuration • 38 Location • 38 Purpose • 38

liblcpatimnp • 18 Configuration • 39 Location • 39 Purpose • 39

liblcpCurrentLocProcessor • 22

Configuration • 40 Location • 40 Purpose • 40

liblcpmacronodes Configuration • 41 Location • 41 Purpose • 41 Startup • 41

liblcpposreq • 16 Configuration • 42 Location • 42 Purpose • 42

liblcpsri Configuration • 43 Location • 43 Purpose • 43

liblcpsriimsi • 19 Configuration • 44 Location • 44 Purpose • 44

liblcpsrimsrn • 19, 20, 23, 24 Configuration • 45 Location • 45 Purpose • 45

Loading eserv.config configuration changes eserv.config Configuration • 26

Loading the Distribution File Before you begin • 70 Installation directory • 70 Introduction • 70 Procedure • 70

locApp • 23 Configuration • 34 Location • 34 Purpose • 34 Startup • 34

locAPP • 34 eserv.config Configuration • 23

locAppSK • 12 Location

javaLcpConversionLoader.sh • 35 liblcpacschassis • 36 liblcpalarms • 37 liblcpati • 38 liblcpatimnp • 39 liblcpCurrentLocProcessor • 40 liblcpmacronodes • 41 liblcpposreq • 42 liblcpsri • 43 liblcpsriimsi • 44 liblcpsrimsrn • 45 locApp • 34

Location Application semaphore Checking the Installation • 85

Location Module What is Location Capability Pack? • 2

LocationNumberLength • 23



M

MAP • v Map_Uncertainty_constant_C • 22 Map_Uncertainty_constant_x • 23 mapNOA • 21 mapVersion • 21 maxNum • 25 MC • 99 MCC • 100 MNC • 100 MNP • 18 mnpDbAddress • 18 MOC • 99 MS • 10 MSC • 16 mscMktId • 16 mscSwId • 16 MSIN • 100 MSISDN • 2 MSRN • 2 MT • 100 MTC • 99 MTP • 102

N

Nature of address Normalisation and Denormalisation • 4

NOA • 4 Normalisation and Denormalisation

Denormalisation rules • 4 Introduction • 4 Nature of address • 4

normalisedNumbers • 12

O

Oracle • ii oracleUserAndPassword • 11 origSSN • 13, 19, 20 OSA • 59 Overview

Installation order • 69 Overview diagram

What is Location Capability Pack? • 3

P Parameters

cacheExpiry • 24 cacheSize • 23 cellIdPadCharacter • 14 concatenateLocInfo • 24 Configuring the acs.conf on the SCP • 28 convertForHLR • 12 destDir • 25 destSccpNOA • 21 destSSN • 14, 19, 21 filePrefix • 26

flushPeriod • 25 forwardToMsc • 17 generateEDR • 15 gmscAddress • 20 gmscMapNOA • 20 gsmScfAddress • 13, 18 gsmScfMapNOA • 13, 18 hlrGt • 22 hlrSSN • 16 LcpCustomNoA • 28 locAppSK • 12 LocationNumberLength • 23 Map_Uncertainty_constant_C • 22 Map_Uncertainty_constant_x • 23 mapNOA • 21 mapVersion • 21 maxNum • 25 mnpDbAddress • 18 mscMktId • 16 mscSwId • 16 normalisedNumbers • 12 oracleUserAndPassword • 11 origSSN • 13, 19, 20 performanceReportPeriod • 14 responseDeadline • 24 scfPC • 16 scfSSN • 16 tcapIF • 13, 17, 19, 20 tempDir • 26 timerIF • 11 timestampFormat • 15 useCustomLCPNotificationNoARules • 28

PC • 60 performanceReportPeriod • 14 PLMN • 100 Plugins

What is Location Capability Pack? • 2 POSREQ • 2 posreqPlugin • 42

eserv.config Configuration • 16 Preparing the System

Checking Kernel parameters • 67 Introduction • 67

Pre-requisites About this Document • v

Procedure Loading the Distribution File • 70

Provisioning and management What is Location Capability Pack? • 2

Purpose javaLcpConversionLoader.sh • 35 liblcpacschassis • 36 liblcpalarms • 37 liblcpati • 38 liblcpatimnp • 39 liblcpCurrentLocProcessor • 40 liblcpmacronodes • 41 liblcpposreq • 42




liblcpsri • 43 liblcpsriimsi • 44 liblcpsrimsrn • 45 locApp • 34

R

Related documents About this Document • v

Removing LCP from an SCP Removing lcpScp • 88

Removing LCP from an SMS Before removing lcpSms • 91 Removing lcpSms from a clustered SMS •

93 Removing lcpSms from a single SMS • 91

Removing lcpScp Removing LCP from an SCP • 88

Removing lcpSms from a clustered SMS Removing LCP from an SMS • 93

Removing lcpSms from a single SMS Removing LCP from an SMS • 91

Replication Common Troubleshooting Procedures • 49

responseDeadline • 24

S SCCP • 16 SCF • 13 scfPC • 16 scfSSN • 16 Scope

About this Document • v SCP • 5 SCP configuration files

Configuration Overview • 8 Severity levels

Alarm Topic Description • 52 SGML • 100 SGSN • 100 Shared libraries

Checking the Installation • 85 SLEE • 8 SME • 99 SMP • 5 SMS • vi SMSC • 101 SN • 101 SQL • 49 SRI • 2 SRI-IMSI encoding

Data Encoding • 31 SRI-MSRN encoding

Data Encoding • 31 sriPlugin • 43, 44, 45

eserv.config Configuration • 19 SS7 • 100 SSN • 13

Startup liblcpacschassis • 36 liblcpmacronodes • 41 locApp • 34

Statistics Introduction • 5 Statistics gathered • 5

Statistics gathered Statistics • 5

Stopping and Starting The LCP ACS components • 30 The locApp • 30 Turning DEBUG on and off • 30

T TCAP • 56 tcapIF • 13, 17, 19, 20 tempDir • 26 The LCP ACS components

Stopping and Starting • 30 The locApp

Stopping and Starting • 30 timerIF • 11 timestampFormat • 15 Turning DEBUG on and off

Stopping and Starting • 30 Typographical conventions

Document Conventions • vi

U

UAS • 9 useCustomLCPNotificationNoARules • 28 USMS • 9 USSD • 18

V VLR • 100

W

Warnings LCP Alarms • 61

What is Location Capability Pack? Architectural overview • 3 Components • 2 Feature nodes • 2 Introduction • 2 Location Module • 2 Overview diagram • 3 Plugins • 2 Provisioning and management • 2

docs.oracle.com Location... · 2010-11-24 · This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are

Documents