Ericsson AUC With Complete HLR MML Guide

Ericsson AUC(Authentication Center)R12.0 Cartridge Guide

Second EditionAugust 2008

Oracle Communications ASAP™ Cartridge 1.0.0 GA Release for Ericsson AUC R12.0

Copyright and Trademark Information

Copyright © 1992, 2008, Oracle and/or its affiliates. All rights reserved.Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

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.

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.

Ericsson AUC (Authentication Center) R12.0 Cartridge Guide iii

Contents1. Cartridge Overview ...................................................................................... 1

Cartridge content ................................................................................................................... 1Prerequisites ......................................................................................................................... 2About this guide .................................................................................................................... 2Services, features, and options ............................................................................................. 3Hardware and software requirements ................................................................................... 3Network element (NE) interface ............................................................................................ 3ASAP version ........................................................................................................................ 4Connecting to the NE ............................................................................................................ 4Related documentations ....................................................................................................... 4

2. Installing and Testing the Cartridge ........................................................... 5Downloading the cartridge .................................................................................................... 5Starting ASAP ....................................................................................................................... 6Installing the cartridge using scripts ...................................................................................... 7Uninstalling the cartridge using scripts .................................................................................. 7Testing the cartridge installation ........................................................................................... 8

Configuring loopback and live mode parameters ........................................................... 8Modifying T_ERIC-AUC_R12-0_HOST.xml ................................................................... 9Testing the installation .................................................................................................. 10

Deployment of the cartridge using Studio ........................................................................... 11Uninstallation and Undeployment of the cartridge using Studio .......................................... 12

3. Atomic Service Description Layer (ASDL) Commands .......................... 13ASDL commands ................................................................................................................ 14

A_ERIC-AUC_R12-0_CREATE_KEY-DATA ................................................................ 15A_ERIC-AUC_R12-0_CREATE_KEY-DATA-RB ......................................................... 16A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER .......................................................... 17A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER-RB .................................................... 18A_ERIC-AUC_R12-0_DELETE_KEY-DATA ................................................................ 20A_ERIC-AUC_R12-0_DELETE_SUBSCRIBER ........................................................... 21A_ERIC-AUC_R12-0_GET_KEY-DATA ....................................................................... 21A_ERIC-AUC_R12-0_GET_KEY-DATA-RB ................................................................. 23A_ERIC-AUC_R12-0_GET_SUBSCRIBER ................................................................. 24A_ERIC-AUC_R12-0_GET_SUBSCRIBER-RB ........................................................... 25A_ERIC-AUC_R12-0_MODIFY_KEY-DATA ................................................................ 26A_ERIC-AUC_R12-0_MODIFY_KEY-DATA-RB .......................................................... 27A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER ........................................................... 28A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER-RB ..................................................... 29

User exit types .................................................................................................................... 30Understanding user exit type XML files ........................................................................ 31

User defined ASDL exit types ............................................................................................. 32UserExitType.xml ................................................................................................................ 36

iv Oracle Corporation

4. Service Definition ....................................................................................... 53CSDL commands ................................................................................................................ 54

C_ERIC-AUC_R12-0_CREATE_KEY-DATA ............................................................... 55C_ERIC-AUC_R12-0_CREATE_SUBSCRIBER .......................................................... 56C_ERIC-AUC_R12-0_DELETE_KEY-DATA ................................................................ 57C_ERIC-AUC_R12-0_DELETE_SUBSCRIBER ........................................................... 58C_ERIC-AUC_R12-0_GET_KEY-DATA ....................................................................... 58C_ERIC-AUC_R12-0_GET_SUBSCRIBER ................................................................. 59C_ERIC-AUC_R12-0_MODIFY_KEY-DATA ................................................................ 60C_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER ........................................................... 61

5. Configuring ASAP to Support Additional NE Instances ........................ 63Extracting source files ......................................................................................................... 66

Loading a new XML file ................................................................................................ 67

Ericsson AUC (Authentication Center) R12.0 Cartridge Guide 1

1

Cartridge Overview

ASAP cartridges are discrete software components that are developed for the ASAP product. An ASAP cartridge offers specific domain behavior on top of the core ASAP software, and provides the configuration that supports a set of services on a network element (NE).

An ASAP cartridge is not a stand-alone component, but operates in conjunction with the ASAP core product. ASAP cartridges offer the following benefits:

Reduced Time to Market - time to market of new services is reduced through simplified development, implementation, and extension of cartridges on customer sites.Extendable - cartridges can be extended to include additional services and components that deliver business value, without requiring changes to the original cartridge.Simplified Effort - the effort and technical knowledge that is required to perform customizations is reduced.Ease of Installation - cartridges can be installed into an ASAP environment without interfering with the existing install base.

An ASAP cartridge can be used to configure ASAP to provision the following:

NEs from a specific vendor, such as Nortel or Lucent.Technologies, such as Asynchronous Transfer Mode (ATM) and Frame Relay switches, or Internet Protocol (IP) routers.Services that are supported on the NE, such as ATM, IP Virtual Private Networks (VPN), Wireless, or Optical.

An ASAP cartridge supports a particular set of services on an NE. These services are independent of customer-specific service definitions. Professional Services or systems integrators can perform extensions to the cartridge to support customer-specific requirements.

Cartridge contentAn ASAP cartridge contains the following:

Sample NE configurationA set of scripts, such as State Tables or Java methods

Cartridges are designed for a specific technology, software load, and service.

Chapter 1: Cartridge Overview

2 Oracle Corporation

A set of atomic actions in the form of Atomic Service Description Layer (ASDL) commandsA set of Common Service Description Layer (CSDL) commands that form meaningful servicesSample work ordersInstallation scripts

PrerequisitesSystem integrators such as managers, designers, programmers, and testers who are responsible for the adaptation and integration of ASAP-based solutions should use this manual as a reference. It assumes that readers possess the following skills:

A knowledge of ASAP programming conceptsA good working knowledge of the UNIX operating systemA thorough understanding of service and network provisioningFamiliarity with telecommunications

About this guideThis guide provides a detailed description of the Ericsson AUC cartridge. It contains overview and technical information to assist with extending and integrating the cartridge into a customer environment.

The scope of this guide includes ASAP as it pertains to the use of this cartridge. It is not intended to be a complete ASAP reference guide.

For additional information when using this cartridge, refer to the following supporting documentation:

Activation documentation set—for detailed information on the ASAP component.

The Ericsson AUC cartridge provides the ASAP service configuration and network element (NE) interface to support provisioning of the AUC Subscriptions on NE_ERIC-AUC_R12-0-HOST NEs.

Services, features, and options


Services, features, and optionsThis cartridge supports the following services:

Hardware and software requirementsThe following sections contain the high-level software and hardware environment requirements for provisioning AUC Subscriptions product on authentication center including:

Network element (NE) interfaceASAP version

Network element (NE) interfaceThe following database tables in SARM are configured to support the NE configuration:

tbl_host_cllitbl_clli_routetbl_comm_param

Table 1: Supported services

Service Description

Create AUC Subscriber This service creates a subscriber in the authentication center.

Delete AUC Subscriber This service deletes a subscriber in the authentication center.

Get AUC Subscriber This service queries for a subscriber in the authentication center.

Modify AUC Subscriber This service modifies a subscriber in the authentication center.

Create AUC Key Data This service creates the key data in the authentication center.

Delete AUC Key Data This service deletes the key data in the authentication center.

Get AUC Key Data This service queries the key data in the authentication center.

Modify AUC Key Data This service modifies the key data in the authentication center.

Chapter 1: Cartridge Overview


tbl_resource_pooltbl_ne_config

ASAP versionThis cartridge was developed and tested using ASAP 5.

For more information on the operating environment of this ASAP version, refer to the ASAP 5 Release Record.

Connecting to the NEThe cartridge uses the Telnet over TCP/IP protocol.

Related documentationsThis cartridge was developed according to the following Network Element Provisioning Specifications:

None


2

Installing and Testing the Cartridge

This chapter describes the following procedures related to installing and testing the cartridge:

Downloading the cartridgeInstalling the cartridge using scriptsUninstalling the cartridge using scriptsTesting the cartridge installationDeployment of the cartridge using StudioUninstallation and Undeployment of the cartridge using Studio

Downloading the cartridgeBefore you can install the cartridge, you must use the internet to download the cartridge’s TAR file from Oracle’s Customer Portal.

Use the following instructions to download, then unTAR the TAR file.

To download the TAR file

1. Login to Oracle MetaLink internet home page (http://www.metalink.oracle.com).

2. Download the cartridge patch to your workstation.

To unTAR the TAR file

1. On your workstation, create a repository directory—the naming of which is your choice.mkdir <repository dir>

2. Copy the TAR file into the repository directory.

3. Untar EricssonAUC_12_X_X_R1_0_0.<buildId>.tar.tar xvf EricssonAUC_12_X_X_R1_0_0.<buildId>.tar

The directory structure in the repository directory should look like the following illustration. (this illustration describes the minimum required structure; you can enhance this directory structure with additional directories based on your requirements and deliverables). <repository_directory>

/README/installCartridge/uninstallCartridge

Chapter 2: Installing and Testing the Cartridge


/EricssonAUC_R12_0.sar

Starting ASAPBefore installing the cartridge, ensure that ASAP is running.

To start ASAP

1. To start ASAP, execute the following script:start_asap_sys -d

2. Ensure the ASAP Daemon (DAEM$ENV_ID) is running by checking the ASAP status using the ASAP script “status”.

3. Check whether the WebLogic instance for this ASAP environment is running. If not, start the WebLogic instance.

The ASAP Administration Guide contains more information on starting ASAP, the ASAP Daemon, and WebLogic.

Installing the cartridge using scripts


Installing the cartridge using scriptsRun the installation script installCartridge to install the cartridge. The script executes the following tasks:

Configures the Ericsson AUC-specific NE using the SACT. Deploys the Ericsson AUC cartridge service model (only if the Ericsson AUC service model is not yet deployed) using the Service Activation Deployment Tool (SADT).Copies the Ericsson AUC-specific jar files to the ASAP environment.Loads the sample work orders to the SRP database.

For information on the SACT and the SADT, refer to the ASAP Administration Guide.

To install the cartridge

1. Run the installCartridge script. At the prompt, type:installCartridge EricssonAUC_R12_0.sar

2. The script prompts you for the values of the following WebLogic login parameters:

WebLogic HostnameWebLogic HTTP PortWebLogic Login User IDWebLogic Login Password

The script loads the NEP-NE configuration and the CSDL-ASDL configuration to the SARM database, and loads sample work orders to the SRP database. The script also copies the cartridge-specific jar files and cpp library file to the ASAP environment.

3. Copy studio_2_6_0.jar file to the $ASAP_BASE/lib directory.

4. Add ${ASAP_BASE}/lib/studio_2_6_0.jar to the CLASSPATH in the JInterpreter file under $ASAP_BASE/programs directory.

5. Restart ASAP to upload the cartridge configuration into ASAP.

Uninstalling the cartridge using scriptsRun the uninstallation script uninstallCartridge to uninstall the Ericsson AUC cartridge. The script executes the following tasks:

Unconfigures Ericsson AUC-specific NEs using the SACT. Undeploys the Ericsson AUC cartridge service model (only if the Ericsson AUC service model is already deployed) using the Service Activation Deployment Tool (SADT). Removes the Ericsson AUC-specific jar files and cpp library file from the ASAP environment.

For more information on the SACT and the SADT, refer to the ASAP Administration Guide.



To uninstall the cartridge

1. Run the uninstallCartridge script. At the prompt, type:uninstallCartridge EricssonAUC_R12_0.<timestamp>.sar

2. The script prompts you for the values of the following parameters:

WebLogic HostnameWebLogic HTTP PortWebLogic Login User IDWebLogic Login Password

The script unloads the NEP-NE configuration and CSDL-ASDL configuration from SARM database. It also removes the cartridge specific jar files and cpp library file from the ASAP environment.

Testing the cartridge installationTo test this cartridge installation, you need to know about the network element (NE), services, and basic Activation configuration. You may need to perform adjustments to provision a service for a specific NE, network, or connectivity configuration.

You can test the cartridge installation using one of the following methods:

Loopback mode—does not actually connect to or send commands to the NE.Live mode—connects to and sends commands to a live NE.

Configuring loopback and live mode parametersSet the following variables to test the cartridge in loopback or live testing modes.

Loopback mode

Set the following parameter to test the cartridge in loopback mode.

Table 2: Loopback Mode Parameter Settings

Configuration Variable Parameter Settings Location

LOOPBACK_ON 1 (default setting) ASAP.cfg

Testing the cartridge installation


Live mode

Set the following parameter to test the cartridge in live mode.

Communication parameters

The following are the list of parameters for the sample NE configuration XML used by SACT.

Modifying T_ERIC-AUC_R12-0_HOST.xmlUse the following procedure to modify T_ERIC-AUC_R12-0_HOST.xml.

Table 3: Live Mode Parameter Settings

Configuration Variable Parameter Settings Location

LOOPBACK_ON 0 ASAP.cfg

Table 4: Communication parameters

param_label param_value param_desc

HOST_IPADDR 127.0.0.1 The host name or IP Address of the remote NE.

PORT 5000 Port number to connect on remote NE host.

OPEN_TIMEOUT 20 Connection timeout in seconds.

READ_TIMEOUT 30 Read timeout in seconds.

HOST_USERID user Login User Name.

HOST_PASSWORD password Password for the User.

PROMPT < Provisioning prompt.

LOGIN_PROMPT USERCODE: Login prompt from the NE

PASSWORD_PROMPT PASSWORD: Password prompt from the NE

DOMAIN_PROMPT DOMAIN: Domain prompt from the NE

DOMAIN_PASSWORD pthlr1d Domain password for the NE

RESPONSELOG TRUE Flag to turn off or on Response log.

PRINT_REPLY FALSE Flag to turn off or on reply in ASCII format.



To modify T_ERIC-AUC_R12-0_HOST.xml

1. Create a new source directory. You can give this directory any appropriate, meaningful name you want to.

mkdir <new_source_directory>

2. Copy EricssonAUC_R12_0.sar to this new source directory.

cp EricssonAUC_R12_0.sar ./<new_source_directory>

3. Change directory to <new_source_directory>.cd <new_source_directory>

4. Un-jar EricssonAUC_R12_0.sar. This extracts the contents of the sar file.

jar xvf EricssonAUC_R12_0.sar

5. Edit <new_source_directory> T_ERIC-AUC_R12-0_HOST.xml in with the appropriate changes.

6. Create a new sar file at the <new_source_directory> level. CreateSar $PWD

7. Uninstall the cartridge using EricssonAUC_R12_0.sar. (That is, use the original sar file that you copied in Step 2 above—see “Uninstalling the cartridge using scripts” on page 7 for uninstallation instructions).

8. After you uninstall the cartridge, rename the sar file, so you have a backup copy of it.

9. Copy the new sar file from <new_source_directory>.

10. Reinstall the cartridge (see “Installing the cartridge using scripts” on page 7 for installation instructions).

Testing the installationThe following procedure describes the steps required to test the cartridge installation in loopback mode. We recommend that you perform the initial cartridge installation test in loopback mode.

To test in loopback mode

1. Stop ASAP by typing the following command at the UNIX prompt:stop_asap_sys -d

2. Ensure loop back mode is on. See “Loopback mode” on page 8 for a description of how to set the loop back parameter to “On”.

3. Start ASAP by typing:start_asap_sys -d

4. Send the sample work orders through the SRP Emulator by typing:

Deployment of the cartridge using Studio


run_suite $SRP <ctrl_password> <suite name>

You can locate the suite names by typing:grep SUITE * | grep -v END

A list of all available suites appears.

For more information on the SRP Emulator, refer to the ASAP Administration Guide.

5. Verify the status of the sample work orders by typing:asap_utils -d l

All successful work orders returns to the 104 state.

To view the sample work orders provided with this cartridge, refer to the Ericsson AUC cartridge source.

Viewing the sample work orders

You find the sample work orders under the SampleWorkOrders directory in the sar file. The following procedure describes how to view the sample work orders.

To view the sample work orders

1. Create a repository directory, copy the sar file to the new directory and un-jar the sar file, as described by Step 1 through Step 4 in “Modifying T_ERIC-AUC_R12-0_HOST.xml” on page 9.

2. Locate and view the sample work order files.

Deployment of the cartridge using StudioBefore installing the cartridge, ensure weblogic and ASAP are started and running.

The following are the steps involved:

1. Open Studio in design perspective. Choose Import from the File menu and select Activation Archive (SAR) under Studio Wizards to import the sar file. Browse for the path to the sar file and click Finish.

2. Create a new Service Activation Project.

3. Define a new NE Entity, based on the NE Template contained in the cartridge provided by Oracle.

4. Ensure that the primary pool of the newly created NE is different from the NE template primary pool. You can modify it, if necessary.

5. Ensure that the test work order provided with the cartridge targets the newly defined NE. If not, then modify the test work orders file(s).



6. Create a new Activation Environment Project from the Studio menu. (Use Studio help for more information).

7. Create Activation Environment inside the Activation Environment Project and configure the Connection Details tab with your Environment ID, Activation version and weblogic data.

8. Connect to your environment using the Connect button.

9. Select the Cartridge tab of the Activation Environment and click Add to add your projects to the environment. The cartridge and the newly created Service Activation should appear in the Cartridges list.

10. Deploy the NetworkActivation (NA) cartridge provided by Oracle. (No NE information is to be deployed with this cartridge, therefore it isn’t necessary to deploy the NEP map info).

11. First Deploy the Service Activation (SA) project as follows:

On the Cartridge tab, select the necessary SA cartridge and press the Deploy button.Select the NEP Map tab of the Activation Environment. Choose the necessary NEP server from the drop-down box of the Network Element Processors.(Use Studio help for more information).Select the SA cartridge from the Network Element Processor Map and click the Deploy button.

12. Verify the SADT console to confirm the installation

13. Go to ASAP environment.

14. Copy studio_2_6_0.jar file to the $ASAP_BASE/lib directory.

15. Add ${ASAP_BASE}/lib/studio_2_6_0.jar to the CLASSPATH in the JInterpreter file under $ASAP_BASE/programs directory.

16. Restart ASAP in order to start working with the cartridge.

Uninstallation and Undeployment of the cartridge using Studio

The following are the steps involved:

1. Connect to your environment using the Connect button.

2. Select the necessary cartridge from the Environment Cartridge list in Studio and click the Undeploy button.

3. Verify the Environment Cartridge list. The Check Box with the name of the cartridge that is disabled should be unchecked.


3

Atomic Service Description Layer (ASDL) Commands

ASDL commands represent a set of atomic actions that ASAP can perform on a network element (NE). ASAP can combine ASDLs to create meaningful services (CSDLs) within a cartridge.

This chapter presents detailed information on the ASDL parameters that we provide with this cartridge. The following table lists and describes the type of parameter information that is included.

Table 5: ASDL parameter information

Item Description

Parameter Name Identifies the parameter that is configured for the stated service.

Description Describes the parameter.

Range Describes or lists the range of values that can be used to satisfy this parameter.

Default Value Configures a default value for the parameter so that it is not mandatory for the upstream system to provide a value.

Chapter 3: Atomic Service Description Layer (ASDL) Commands


For a detailed description of the Required and Optional parameter classifications, refer to the ASAP Administration Guide.

ASDL commandsThis cartridge provides the following ASDL commands:

Type Indicates one of the following parameter types:

S—Scalar, specifies the parameter label transmitted on the ASDL command. Scalar parameters are conventional name-value pair parameters.C—Compound, specifies the base name of the compound parameter transmitted on the ASDL command. A compound parameter contains structures or arrays of information that are represented by a particular structure name or compound parameter name. Each compound parameter can contain a large number of elements. If you use compound parameters, you only require a single entry in the ASAP translation tables to call the compound parameter and all its associated parameter elements.I—Indexed, identifies a parameter that contains a sequential numerical index value to tell the SARM that it should execute the same operation (for example, an ASDL command) for all occurrences of that index. Consequently, if there are several options on a particular CSDL command (OPT1, OPT2, OPT3, etc.), you can specify the OPT parameter as an indexed parameter. When you specify the OPT parameter as an indexed parameter, the SARM generates several occurrences of that same ASDL command and each command has a different value for the option being transmitted to the NEP.

For more information on parameter types, refer to the ASAP Developer Reference.

Class Indicates one of the following parameter classifications:

R—Required scalar parameterO—Optional scalar parameterC—Required compound parameterN—Optional compound parameterM—Mandatory indexed parameterI—Optional indexed parameterS—Parameter count


Item Description

ASDL commands


A_ERIC-AUC_R12-0_CREATE_KEY-DATAA_ERIC-AUC_R12-0_CREATE_KEY-DATA-RBA_ERIC-AUC_R12-0_CREATE_SUBSCRIBERA_ERIC-AUC_R12-0_CREATE_SUBSCRIBER-RBA_ERIC-AUC_R12-0_DELETE_KEY-DATAA_ERIC-AUC_R12-0_DELETE_SUBSCRIBERA_ERIC-AUC_R12-0_GET_KEY-DATAA_ERIC-AUC_R12-0_GET_KEY-DATA-RBA_ERIC-AUC_R12-0_GET_SUBSCRIBERA_ERIC-AUC_R12-0_GET_SUBSCRIBER-RBA_ERIC-AUC_R12-0_MODIFY_KEY-DATAA_ERIC-AUC_R12-0_MODIFY_KEY-DATA-RBA_ERIC-AUC_R12-0_MODIFY_SUBSCRIBERA_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER-RB

A_ERIC-AUC_R12-0_CREATE_KEY-DATAThis service creates the key data in AUC.

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningKeyData.createKeyData

Table 6: A_ERIC-AUC_R12-0_CREATE_KEY-DATA

Parameter Name Description RangeDefault Value

Type Class

MCLI Remote network element name

S R

A4KEY A4 key S R

KIND A4 key indicator. S R

A4IND A4 algorithm indicator S O

AKATYPE Authentication and Key Agreement (AKA) type.

S O



MML commandsThis method implements the AUC Create Key Data MML Command

AGKDI:KIND=%KIND,A4KEY=%A4KEY[,A4IND=%A4IND][,AKATYPE=%AKATYPE];

Where

%KIND is A4 key indicator

%A4IND is A4 algorithm indicator

%A4KEY is A4 Key

%AKATYPE is Authentication and Key Agreement (AKA) type

Output parameters

Return as CSDL parameter:

A_ERIC-AUC_R12-0_CREATE_KEY-DATA_UDET=<user defined exit type>

Return as Info parameter:

A_ERIC-AUC_R12-0_CREATE_KEY-DATA_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_CREATE_KEY-DATA-RBRollback service for Delete Key data.

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningKeyData.createKeyDataRb

Table 7: A_ERIC-AUC_R12-0_CREATE_KEY-DATA-RB


Type Class


S R

OLD_A4KEY A4 key S O

OLD_KIND A4 key indicator. S R

OLD_A4IND A4 algorithm indicator S O

OLD_AKATYPE Authentication and Key Agreement (AKA) type.

S O

ASDL commands


MML commandsThis method implements the Rollback service for Delete AUC Key Data MML Command

AGKDI:KIND=%OLD_KIND,A4KEY=%OLD_A4KEY[,A4IND=%OLD_A4IND][,AKATYPE=%OLD_A

KATYPE];

Where

%OLD_KIND is A4 key indicator

%OLD_A4IND is A4 algorithm indicator

%OLD_A4KEY is A4 Key

%OLD_AKATYPE is Authentication and Key Agreement (AKA) type

Output parameters


A_ERIC-AUC_R12-0_CREATE_KEY-DATA-RB_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_CREATE_KEY-DATA-RB_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_CREATE_SUBSCRIBERThis service creates a subscriber in the Authentication Center (AUC). The subscriber must be created on the AUC before the subscription is added on the AUC.

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningSub.createSubscriber

Table 8: A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER


Type Class


S R

IMSI International Mobile Subscriber Identity (IMSI).

S R

EKI Encrypted subscriber authentication key (Ki).

S R




MML commandsThis method implements the Create AUC Subscriber MML Command.

AGSUI:IMSI=%IMSI,EKI=%EKI,KIND=%KIND,[A3A8IND=%A3A8IND |

FSETIND=%FSETIND][,A4IND=%A4IND];

Where:

%IMSI is IMSI

%EKI is EKI value


%A3A8IND is Algorithm parameter value

%FSETIND is Function set indicator, Application System dependent parameter, used only for WCDMA


Output parameters


A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER-RBRollback service for the Delete Subscriber service in the Authentication Center (AUC).

A3A8IND A3 A8 algorithm indicator.

S O

FSETIND Function set indicator. S O

A4IND A4 algorithm indicator. S O

Table 8: A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER


Type Class

ASDL commands


It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningSub.createSubscriberRb

MML commandsThis method implements the Rollback service for Delete AUC Subscriber.

AGSUI:IMSI=%IMSI,EKI=%OLD_EKI,KIND=%OLD_KIND,[A3A8IND=%OLD_A3A8IND |

FSETIND=%OLD_FSETIND][,A4IND=%OLD_A4IND];

Where:

%OLD_IMSI is IMSI

%OLD_EKI is EKI value


%OLD_A3A8IND is Algorithm parameter value

%OLD_FSETIND is Function set indicator, Application System dependent parameter, used only for WCDMA


Table 9: A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER-RB


Type Class


S R

OLD_IMSI International Mobile Subscriber Identity (IMSI).

S R

OLD_EKI Encrypted subscriber authentication key (Ki).

S R

OLD_KIND A4 key indicator. S R

OLD_A3A8IND A3 A8 algorithm indicator.

S O

OLD_FSETIND Function set indicator. S O

OLD_A4IND A4 algorithm indicator. S O



Output parameters


A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER-RB_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER-RB_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_DELETE_KEY-DATAThis service deletes the key data in AUC.

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningKeyData.deleteKeyData

MML commandsThis method implements the AUC Delete Key Data MML Command

AGKDE:KIND=%KIND[,A4IND=%A4IND][,AKATYPE=%AKATYPE];

Where:



%AKATYPE is Authentication and Key Agreement (AKA)type

Output parameters


Table 10: A_ERIC-AUC_R12-0_DELETE_KEY-DATA


Type Class


S R




S O

ASDL commands


A_ERIC-AUC_R12-0_DELETE_KEY-DATA_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_DELETE_KEY-DATA_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_DELETE_SUBSCRIBERThis service deletes the subscriber in the Authentication Center (AUC).

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningSub.deleteSubscriber

MML commandsThis method implements the Delete AUC Subscriber MML Command.

AGSUE:IMSI=%IMSI;

Where:

%IMSI is IMSI

Output parameters


A_ERIC-AUC_R12-0_DELETE_SUBSCRIBER_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_DELETE_SUBSCRIBER_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_GET_KEY-DATAThis service queries the key data in AUC.

Table 11: A_ERIC-AUC_R12-0_DELETE_SUBSCRIBER


Type Class


S R


S R



It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningKeyData.getKeyData

MML commandsThis method implements the get AUC Key Data MML Command

AGKDP:KIND=%KIND[,A4IND=%A4IND][,SUBSCH][,AKATYPE=%AKATYPE];

Where




%SUBSCH Subscribers changed, this is an Application System dependent parameter, could be restricted to use with KIND parameters

defined for GSM

Output parameters


A_ERIC-AUC_R12-0_GET_KEY-DATA_UDET=<user defined exit type>


Table 12: A_ERIC-AUC_R12-0_GET_KEY-DATA


Type Class


S R



SUBSCH To display number of subscribers whose Encrypted subscriber authentication key (Ki) has been changed.

S O


S O

ASDL commands


A_ERIC-AUC_R12-0_GET_KEY-DATA_RETURN_INFO="Success" or <error_code>:<error_description>

RETURN_INFO Data_parameters

A_ERIC-AUC_R12-0_GET_KEY-DATA-RBThis service queries the key data in AUC for Rollback Services.

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningKeyData.getKeyDataRb

MML commandsThis method implements the get Key Data AUC MML Command for Rollback services.

AGKDP:KIND=%KIND[,A4IND=%A4IND][,SUBSCH][,AKATYPE=%AKATYPE];

Where




%SUBSCH Subscribers changed, this is an Application System dependent parameter, could be restricted to use with

Table 13: A_ERIC-AUC_R12-0_GET_KEY-DATA-RB


Type Class


S R



SUBSCH To display number of subscribers whose encrypted subscriber authentication key (Ki) has been changed.

S O


S O



KIND parameters defined for GSM

Output parameters


A_ERIC-AUC_R12-0_GET_KEY-DATA-RB_UDET=<user defined exit type>

OLD_<data_parameters>


A_ERIC-AUC_R12-0_GET_KEY-DATA-RB_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_GET_SUBSCRIBERThis service queries for the subscriber data in the Authentication Center (AUC).

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningSub.getSubscriber

MML commandsThis method implements the Get AUC Subscriber data MML Command.

AGSUP:IMSIS=%IMSI[,AKATYPE=%AKATYPE];

Where:

%IMSI is IMSI


IMSIS "ALL" Value is not supported for this implementation

Table 14: A_ERIC-AUC_R12-0_GET_SUBSCRIBER


Type Class


S R

IMSIS International Mobile Subscriber Identity (IMSI) series.

S R

AKATYPE Authentication and Key Agreement (AKA) type

S O

ASDL commands


Output parameters


A_ERIC-AUC_R12-0_GET_SUBSCRIBER_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_GET_SUBSCRIBER_RETURN_INFO="Success" or <error_code>:<error_description>

RETURN_INFO_<data_parameters>

A_ERIC-AUC_R12-0_GET_SUBSCRIBER-RBQuery for Rollback services in the Authentication Center (AUC).

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningSub.getSubscriberRb

MML commandsThis method implements the Get AUC Subscriber data MML Command for Rollback Services.

AGSUP:IMSIS=%IMSI;

Where:

%IMSI is IMSI

IMSIS "ALL" value is not supported for this implementation

Table 15: A_ERIC-AUC_R12-0_GET_SUBSCRIBER-RB


Type Class


S R


S O

IMSI International Mobile Subscriber Identity (IMSI) series.

S O


S O



Output parameters


A_ERIC-AUC_R12-0_GET_SUBSCRIBER-RB_UDET=<user defined exit type>

OLD_<data_parameters>


A_ERIC-AUC_R12-0_GET_SUBSCRIBER-RB_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_MODIFY_KEY-DATAThis service modifies the key data in the AUC.

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningKeyData.modifyKeyData

MML commandsThis method implements the modify AUC Key Data MML Command

AGKDC:KIND=%KIND,A4KEY=%A4KEY[,A4IND=%A4IND][,AKATYPE=%AKATYPE];

Where



%A4KEY is A4 Key

Table 16: A_ERIC-AUC_R12-0_MODIFY_KEY-DATA


Type Class


S R

A4KEY A4 key S O




S O

ASDL commands



Note:If user did not provided any values other than KIND parameter,cartridge will send the following MML command

AGKDC:CONTINUE;

Output parameters


A_ERIC-AUC_R12-0_MODIFY_KEY-DATA_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_MODIFY_KEY-DATA_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_MODIFY_KEY-DATA-RBRollback of Modify Key Data service in the AUC.

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningKeyData.modifyKeyDataRb

MML commandsThis method implements the Rollback service for Modify AUC Key Data MML Command

Table 17: A_ERIC-AUC_R12-0_MODIFY_KEY-DATA-RB


Type Class


S R

OLD_A4KEY A4 key S O

OLD_KIND A4 key indicator. S O

OLD_A4IND A4 algorithm indicator S O

OLD_AKATYPE Authentication and Key Agreement (AKA) type.

S O

A4KEY A4 key S O



AGKDC:KIND=%OLD_KIND,A4KEY=%OLD_A4KEY[,A4IND=%OLD_A4IND][,AKATYPE=%OLD_AKATYPE];

Where



%OLD_A4KEY is A4 Key

%OLD_AKATYPE is Authentication and Key Agreement (AKA) type

Output parameters


A_ERIC-AUC_R12-0_MODIFY_KEY-DATA-RB_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_MODIFY_KEY-DATA-RB_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBERThis service modifies the subscriber in the AUC.

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningSub.modifySubscriber

MML commandsThis method implements the Modify AUC Subscriber data MML Command.

Table 18: A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER


Type Class


S R


S O

AMF Authentication management field

S O

FSETIND Function set indicator S O

ASDL commands


AGSUC:IMSIS=%IMSI,AMF=%AMF,FSETIND=%FSETIND;

Where:

%IMSIS is IMSI

%AMF is AMF

%FSETIND is Function set indicator, Application System dependen parameter, used for WCDMA

Output parameters


A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER_RETURN_INFO="Success" or <error_code>:<error_description>

A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER-RBRollback modification of the subscriber in the AUC.

It is implemented by the Java method: com.metasolv.cartridge.oss.eric_auc_r12_0.prov.AUCProvisioningSub.modifySubscriberRb

Table 19: A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER-RB


Type Class


S R

OLD_IMSIS IMSI digit string 1- 15 digits.

S O

OLD_AMF Authentication Management Field.

S O

OLD_FSETIND Function set indicator, value 0 - 15.

S O

OLD_IMSI IMSI digit string 1- 15 digits.

S O



MML commandsThis method implements Rollback service for Modify AUC subscriber data MML command.

AGSUC:IMSIS=%OLD_IMSIS,AMF=%OLD_AMF,FSETIND=%OLD_FSETIND;

Where:

%OLD_IMSIS is IMSI

%OLD_AMF is old AMF

%OLD_FSETIND is old Function set indicator, Application System dependent parameter, used for WCDMA

Output parameters


A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER-RB_UDET=<user defined exit type>


A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER_RETURN-RB_INFO="Success" or <error_code>:<error_description>

User exit typesUser exit types allow cartridge developers and systems administrators to map ASDL exit codes to one of the predefined base exit types. Base exit types determine the product behavior. Cartridges map return codes and status values from a network element to a user defined exit type.

Regular expressions (regex) are used to perform pattern searches on responses from network elements. The pattern is stored in "tbl_user_err" in the SARM database. The user exit type contains a regex pattern that is applied at runtime.

Regular expressions enable users to associate a series of responses to a specific base type. For example, a regular expression "6" can identify a pattern where any response with the character "6" followed by any number of characters will translate to base type of FAIL.

Regular expressions can also allow very specific searches within a response from a network element. Regular expressions are typically compiled before being executed. Compilation produces a binary version of the expression and ensures that the syntax of the regular expression is correct. This compilation occurs using SACT\SADT when user exit types are deployed into ASAP. If the syntax is deemed to be incorrect during compilation, SADT displays an error message and the deployment of the user exit type will fail.

For more information on pattern matching, refer to the ASAP Developer Reference and the ASAP Administration Guide.

User exit types


Understanding user exit type XML files…<userDefinedExitType>

<neDescriptor><softwareLoad>DYNAMIC_SL</softwareLoad><technology>DYNAMIC_VENDOR-DYNAMIC_TECH</technology>

</neDescriptor>

<searchPattern>SUCCESS.</searchPattern>1

<userType>U_SUCCEED</userType>2

<baseType>SUCCEED</baseType>3

<description>The ASDL provisioning was successful</description></userDefinedExitType><userDefinedExitType>

<searchPattern>90.</searchPattern><userType>U_FAIL</userType><baseType>FAIL</baseType><description>The ASDL failed - fail the current order

and stop processing.</description></userDefinedExitType><userDefinedExitType>

<searchPattern>101-110[201-215]</searchPattern>4

<userType>U_SOFT_FAIL</userType><baseType>SOFT_FAIL</baseType><description>The ASDL has encountered a soft failure. Processing will

continue.</description></userDefinedExitType><userDefinedExitType>

<searchPattern>801-850</searchPattern>5

<userType>U_MINOR_ERROR</userType><baseType>SOFT_FAIL</baseType><description>The ASDL has encountered a soft failure. Processing will

continue.</description></userDefinedExitType><userDefinedExitType>

<searchPattern>251-275&&[^261-265]</searchPattern>6

1. Pattern searches accommodate situations in which responses from the device contain small variantsthat represent the same meaning. The user type contains an associated search pattern that is appliedat runtime. Using regular expressions, you can default a series of responses. For example a regularexpression "90." can specify a pattern where any response with the character "90" followed by anycharacter will translate to base type of FAIL. If the regular expression is defined as "90*", then anyresponse with the character "90" followed by any number of characters will translate to base type ofFAIL

2. The user type that the search pattern maps to.3. The base type that maps to the user type.4. 101 to 110 and 201 to 215 will translate to a base type of SOFT_FAIL5. 801-850 will translate to a base type of SOFT_FAIL. Note that the user type differs from the previ-

ous range.



<userType>U_DELAYED_FAIL</userType><baseType>DELAYED_FAIL</baseType><description>The ASDL has failed during provisioning.</description>

</userDefinedExitType><userDefinedExitType>

<neDescriptor><softwareLoad>BCS36</softwareLoad><technology>NORTEL_DMS</technology><neVendor>Nortel</neVendor>

</neDescriptor><searchPattern>*.</searchPattern><userType>U_MAINTAIN</userType><baseType>MAINTENANCE</baseType><description>The ASDL will Wait until the NE comes out of

Maintenance Mode</description></userDefinedExitType>

The previous code sample shows some typical search pattern examples. Some additional examples follow:

^.*\b(one|two|three)\b.*$ = matches a complete line of text that contains any of the words "one", "two" or "three"^(?=.*?\bone\b)(?=.*?\btwo\b)(?=.*?\bthree\b).*$ matches a complete line of text that contains all of the words "one", "two" and "three""[^"\r\n]*" matches a single-line string that does not allow the quote character to appear inside the string.\b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b matches any IP address.

For more information on search patterns, refer to http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html.

For more information on user exit types, refer to chapter 3 of the ASAP Developer Reference.

User defined ASDL exit typesThe following table lists the user defined ASDL exit types.

6. 251 to 275 but not 261 to 265 will translate to a base type of DELAYED_FAILURE.

Table 20: User defined ASDL exit types

Search pattern User_type Base_type Description

((?s).)*EXECUTED((?s).)*

ERAUC_EXECUTED SUCCEED Provisioning command successful

((?s).)*END((?s).)* ERAUC_END SUCCEED Process end

User defined ASDL exit types


((?s).)*ProvCartridgeException((?s).)*

ERAUC_PROVCARTEXCEP FAIL The NE command was denied due to Provisioning cartridge Exception

((?s).)*IOException((?s).)*

ERAUC_IOEXCEPTION RETRY_DIS

The NE command was denied due to IO exception

((?s).)*TelnetException((?s).)*

ERAUC_TELNETEXCEP RETRY_DIS

The NE command was denied due to telnet exception

((?s).)*Generic Exception((?s).)*

ERAUC_GENERICEXCEP FAIL The NE command was denied due to generic exception

< ERAUC_LOOPBACK_OK SUCCEED Loopback succeed prompt

((?s).)*ANSWER PRINTOUT((?s).)*

ERAUC_ANSWER_PRNTOUT SUCCEED AUC answer printout

((?s).)*NOT EXECUTED((?s).)*

ERAUC_NOT_EXECUTED FAIL AUC not executed

((?s).)*PARTLY EXECUTED((?s).)*

ERAUC_PART_EXECUTED FAIL AUC partly executed

((?s).)*ORDERED((?s).)*

ERAUC_ORDERED FAIL AUC ordered

((?s).)*((?s).)*FAULT CODE 2((?s).)*

ERAUC_FCODE_2 FAIL AUC Fault Code 2

((?s).)*((?s).)*FAULT CODE 3((?s).)*


((?s).)*FAULT CODE 4((?s).)*


((?s).)*FAULT CODE 5((?s).)*


((?s).)*FAULT CODE 6((?s).)*


((?s).)*FAULT CODE 7((?s).)*






((?s).)*FAULT CODE 8((?s).)*


((?s).)*FAULT CODE 9((?s).)*


((?s).)*FAULT CODE 10((?s).)*


((?s).)*FAULT CODE 11((?s).)*


((?s).)*FAULT CODE 12((?s).)*


((?s).)*FAULT CODE 13((?s).)*


((?s).)*FAULT CODE 14((?s).)*


((?s).)*FAULT CODE 19((?s).)*


((?s).)*FAULT CODE 29((?s).)*


((?s).)*FAULT CODE 30((?s).)*


((?s).)*FAULT CODE 42((?s).)*


((?s).)*FAULT CODE 50((?s).)*


((?s).)*FAULT CODE 51((?s).)*


((?s).)*FAULT CODE 52((?s).)*


((?s).)*FAULT CODE 53((?s).)*




User defined ASDL exit types


((?s).)*FAULT CODE 54((?s).)*


((?s).)*FAULT CODE 55((?s).)*


((?s).)*FAULT CODE 56((?s).)*


((?s).)*FAULT CODE 57((?s).)*


((?s).)*FAULT CODE 58((?s).)*


((?s).)*FAULT CODE 59((?s).)*


((?s).)*FAULT CODE 60((?s).)*


((?s).)*FAULT CODE 61((?s).)*


((?s).)*FAULT CODE 62((?s).)*


((?s).)*FAULT CODE 63((?s).)*


((?s).)*FAULT CODE 67((?s).)*


((?s).)*FAULT CODE 68((?s).)*


((?s).)*FAULT CODE 69((?s).)*


((?s).)*FAULT CODE 70((?s).)*


((?s).)*FAULT CODE 71((?s).)*






UserExitType.xml<?xml version="1.0" encoding="UTF-8"?><com:modelEntity xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:com="http://www.mslv.com/studio/core/model/common" xmlns:_1="http://www.mslv.com/studio/core/model/common" xmlns:ude="http://www.mslv.com/studio/activation/model/userDefinedExitType" xmlns="http://www.mslv.com/studio/activation/model/userDefinedExitType" xsi:type="ude:userDefinedExitTypes" name="EricssonAUC_R12_0_userExitTypes"> <com:displayName>EricssonAUC_R12_0_userExitTypes</com:displayName> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*EXECUTED((?s).)*</ude:searchPattern> <ude:userType>ERAUC_EXECUTED</ude:userType> <ude:baseType>SUCCEED</ude:baseType> <ude:description>Provisioning command successful.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*END((?s).)*</ude:searchPattern> <ude:userType>ERAUC_END</ude:userType> <ude:baseType>SUCCEED</ude:baseType> <ude:description>Process end.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior>

((?s).)*FORMAT ERROR((?s).)*

ERAUC_FORMAT_ERROR FAIL AUC Format Error

((?s).)*FUNCTION BUSY((?s).)*

ERAUC_FUNCTION_BUSY RETRY_DIS

AUC Function Busy

((?s).)*UNREASONABLE VALUE((?s).)*

ERAUC_UNREASON_VALUE FAIL AUC Unreasonable Error



UserExitType.xml


<ude:searchPattern>((?s).)*ProvCartridgeException((?s).)*</ude:searchPattern> <ude:userType>ERAUC_PROVCARTEXCEP</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>The NE command was denied due to Provisioning cartridge Exception.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*IOException((?s).)*</ude:searchPattern> <ude:userType>ERAUC_IOEXCEPTION</ude:userType> <ude:baseType>RETRY_DIS</ude:baseType> <ude:description>The NE command was denied due to IO exception.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*TelnetException((?s).)*</ude:searchPattern> <ude:userType>ERAUC_TELNETEXCEP</ude:userType> <ude:baseType>RETRY_DIS</ude:baseType> <ude:description>The NE command was denied due to telnet exception.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*Generic Exception((?s).)*</ude:searchPattern> <ude:userType>ERAUC_GENERICEXCEP</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>The NE command was denied due to generic exception.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern><</ude:searchPattern> <ude:userType>ERAUC_LOOPBACK_OK</ude:userType> <ude:baseType>SUCCEED</ude:baseType> <ude:description>Loopback succeed prompt.</ude:description>



</ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*ANSWER PRINTOUT((?s).)*</ude:searchPattern> <ude:userType>ERAUC_ANSWER_PRNTOUT</ude:userType> <ude:baseType>SUCCEED</ude:baseType> <ude:description>AUC answer printout.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*NOT EXECUTED((?s).)*</ude:searchPattern> <ude:userType>ERAUC_NOT_EXECUTED</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC not executed.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*PARTLY EXECUTED((?s).)*</ude:searchPattern> <ude:userType>ERAUC_PART_EXECUTED</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC partly executed.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*ORDERED((?s).)*</ude:searchPattern> <ude:userType>ERAUC_ORDERED</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC ordered.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 2((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_2</ude:userType>

UserExitType.xml


<ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 2, The A4 key indicator is not defined.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 3((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_3</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 3, the A4 Key indicator is in use by at least one mobile subscriber.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 4((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_4</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 4, the A3/A8 algorithm indicator is not supported.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 5((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_5</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 5, Storage shortage in the IMSI analysis file.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 6((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_6</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 6, storage shortage in the subscription data file.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType>



<ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 7((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_7</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 7, the IMSI is already subscribed.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 8((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_8</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 8, the IMSI given is a prefix of another IMSI already subscribed.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 9((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_9</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 9, there is an IMSI prefix of the IMSI given.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 10((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_10</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 10, a Key data operation is in progress.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior>

UserExitType.xml


<ude:searchPattern>((?s).)*FAULT CODE 11((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_11</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 11, the IMSI has not been subscribed.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 12((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_12</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 12, a time out has ocurred during A4KEY encryption. </ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 13((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_13</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 13, a subscription operation is in progress.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 14((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_14</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 14, the maximum number of subscriptions allowed has been exceeded.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 19((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_19</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 19, no Key data change is in progress.</ude:description>



</ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 29((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_29</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 29, the FSET does not support OP.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 30((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_30</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 30, an OP change is in progress.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 43((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_43</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 43, the A3A8 does not support OP.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 50((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_50</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 50, the area has not been initiated for the specific roaming area.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology>

UserExitType.xml


<ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 51((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_51</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 51, Storage shortage in the data file.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 52((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_52</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 52, IMSI type stored does not match with the command parameter.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 53((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_53</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 53, MSISDN type stored does not match with the command parameter.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 54((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_54</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 54, Storage congestion in file for storage of characterized areas.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 55((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_55</ude:userType> <ude:baseType>FAIL</ude:baseType>



<ude:description>AUC Fault Code 55, PLMN bearer capability number is not defined.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 56((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_56</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 56</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 57((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_57</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 57</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 58((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_58</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 58</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 59((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_59</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 59</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior>

UserExitType.xml


<ude:searchPattern>((?s).)*FAULT CODE 60((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_60</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 60</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 61((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_61</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 61</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 62((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_62</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 62</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 63((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_63</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 63</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 67((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_67</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 67</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology>



<ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 68((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_68</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 68</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 69((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_69</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 69</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 70((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_70</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 70</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 71((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_71</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 71</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FORMAT ERROR((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FORMAT_ERROR</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC parameter was incorrectly specified. </ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType>

UserExitType.xml


<ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FUNCTION BUSY((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FUNCTION_BUSY</ude:userType> <ude:baseType>RETRY_DIS</ude:baseType> <ude:description>AUC Function Busy.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*UNREASONABLE VALUE((?s).)*</ude:searchPattern> <ude:userType>ERAUC_UNREASON_VALUE</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC parameter was specified with an unreasonable value.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 1((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_1 </ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 1, The A4 key indicator is already defined.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 15((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_15</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 15, the A4 algorithm indicator is not supported.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 16((?s).)*</ude:searchPattern>



<ude:userType>ERAUC_FCODE_16</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 16, a Key data change is in progress.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 17((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_17</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 17, a Key data change is pending.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 20((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_20</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 20, a customer Key operation is in progress.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 25((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_25</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 25, the parameter is not supported by this exchange.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 27((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_27</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 27, the function set indicator is not supported.</ude:description> </ude:userDefinedExitType>

UserExitType.xml


<ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 32((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_32</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 32, an AKA algorithm change is in progress.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 33((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_33</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 33, an AKA algorithm change is pending.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 40((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_40</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 40, a subscription data change is pending.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 45((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_45</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 45, a BOP change is in progress.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad>



</ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 26((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_26</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 26, the parameter value is not supported by this exchange.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 24((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_24</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 24, functionality connected to the command is not supported by the exchange.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 34((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_34</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 34, the WCDMA IMSI series is not defined.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 36((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_36</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 36, there are no WCDMA subscribers defined in the AUC.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 37((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_37</ude:userType> <ude:baseType>FAIL</ude:baseType>

UserExitType.xml


<ude:description>AUC Fault Code 37, there are no WCDMA subscribers associated to the specified FSET.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 41((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_41</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 41, no subscription data change is pending.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 39((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_39</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 39, a subscription data change is in progress.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*FAULT CODE 18((?s).)*</ude:searchPattern> <ude:userType>ERAUC_FCODE_18</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC Fault Code 18, no Key data change is pending.</ude:description> </ude:userDefinedExitType> <ude:userDefinedExitType> <ude:networkElementDescriptior> <ude:vendor>ERIC</ude:vendor> <ude:technology>AUC</ude:technology> <ude:softwareLoad>R12-0</ude:softwareLoad> </ude:networkElementDescriptior> <ude:searchPattern>((?s).)*COMMAND RESTRICTED((?s).)*</ude:searchPattern> <ude:userType>ERAUC_CMD_RESTRICTED</ude:userType> <ude:baseType>FAIL</ude:baseType> <ude:description>AUC not accepted, command restricted.</ude:description> </ude:userDefinedExitType></com:modelEntity>




4

Service Definition

The Ericsson AUC cartridge contains a set of CSDLs that map to one or more ASDL commands. You can also create additional CSDLs that map to existing and newly-created ASDLs. An upstream system can assemble any of these CSDL commands onto a work order for provisioning.

This chapter presents detailed information on the CSDL parameters that we provide in this cartridge. The following table lists and describes the type of parameter information that is included.


Item Description

Parameter Name Identifies the parameter that is configured for the stated service.

Description Describes the parameter.

Range Describes or lists the range of values that can be used to satisfy this parameter.

Default Value Configures a default value for the parameter so that it is not mandatory for the upstream system to provide a value.

Chapter 4: Service Definition


For a detailed description of the Required and Optional parameter classifications, refer to the ASAP Administration Guide.

CSDL commandsThis cartridge provides the following CSDL Commands:

Type Indicates one of the following parameter types:

S—Scalar, specifies the parameter label transmitted on the ASDL command. Scalar parameters are conventional name-value pair parameters.C—Compound, specifies the base name of the compound parameter transmitted on the ASDL command. A compound parameter contains structures or arrays of information that are represented by a particular structure name or compound parameter name. Each compound parameter can contain a large number of elements. If you use compound parameters, you only require a single entry in the ASAP translation tables to call the compound parameter and all its associated parameter elements.I—Indexed, identifies a parameter that contains a sequential numerical index value to tell the SARM that it should execute the same operation (for example, an ASDL command) for all occurrences of that index. Consequently, if there are several options on a particular CSDL command (OPT1, OPT2, OPT3, etc.), you can specify the OPT parameter as an indexed parameter. When you specify the OPT parameter as an indexed parameter, the SARM generates several occurrences of that same ASDL command and each command has a different value for the option being transmitted to the NEP.

For more information on parameter types, refer to the ASAP Developer Reference.

Class Indicates one of the following parameter classifications:

R—Required scalar parameterO—Optional scalar parameterC—Required compound parameterN—Optional compound parameterM—Mandatory indexed parameterI—Optional indexed parameterS—Parameter count


Item Description

CSDL commands


C_ERIC-AUC_R12-0_CREATE_KEY-DATAC_ERIC-AUC_R12-0_CREATE_SUBSCRIBERC_ERIC-AUC_R12-0_DELETE_KEY-DATAC_ERIC-AUC_R12-0_DELETE_SUBSCRIBERC_ERIC-AUC_R12-0_GET_KEY-DATAC_ERIC-AUC_R12-0_GET_SUBSCRIBERC_ERIC-AUC_R12-0_MODIFY_KEY-DATAC_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER

C_ERIC-AUC_R12-0_CREATE_KEY-DATAThis service creates the key data in AUC.

Mapping to ASDLs

The following table illustrates the CSDL to ASDL mapping for this service.

Table 22: C_ERIC-AUC_R12-0_CREATE_KEY-DATA


Type Class


A4KEY A4 key S R


S O


NE_ID_ERIC-AUC Remote network element name

S R

Table 23: CSDL to ASDL Mapping

CSDL ASDL

C_ERIC-AUC_R12-0_CREATE_KEY-DATA A_ERIC-AUC_R12-0_CREATE_KEY-DATA



C_ERIC-AUC_R12-0_CREATE_SUBSCRIBERThis service creates a subscriber in Authentication Center (AUC). The subscriber must be created on the AUC before the subscription is added in AUC.

Mapping to ASDLs


Table 24: C_ERIC-AUC_R12-0_CREATE_SUBSCRIBER


Type Class

A3A8IND A3 A8 algorithm indicator.

S O


EKI Encrypted subscriber authentication key (Ki).

S R

FSETIND Function set indicator. S O


S R



S R


CSDL ASDL

C_ERIC-AUC_R12-0_CREATE_SUBSCRIBER A_ERIC-AUC_R12-0_CREATE_SUBSCRIBER

CSDL commands


C_ERIC-AUC_R12-0_DELETE_KEY-DATAThis service deletes the key data in AUC.

Mapping to ASDLs


Table 26: C_ERIC-AUC_R12-0_DELETE_KEY-DATA


Type Class



S O



S R


S O


CSDL ASDL

C_ERIC-AUC_R12-0_DELETE_KEY-DATA A_ERIC-AUC_R12-0_GET_KEY-DATA-RB

A_ERIC-AUC_R12-0_DELETE_KEY-DATA



C_ERIC-AUC_R12-0_DELETE_SUBSCRIBERThis service deletes a subscriber in Authentication Center (AUC).

Mapping to ASDLs


C_ERIC-AUC_R12-0_GET_KEY-DATAThis service gets the key data in AUC.

Table 28: C_ERIC-AUC_R12-0_DELETE_SUBSCRIBER


Type Class


S O


S R


S O


S R


CSDL ASDL

C_ERIC-AUC_R12-0_DELETE_SUBSCRIBER A_ERIC-AUC_R12-0_GET_SUBSCRIBER-RB

A_ERIC-AUC_R12-0_DELETE_SUBSCRIBER

Table 30: C_ERIC-AUC_R12-0_GET_KEY-DATA


Type Class


CSDL commands


Mapping to ASDLs


C_ERIC-AUC_R12-0_GET_SUBSCRIBERThis service queries for the subscriber in Authentication Center (AUC).


S O



S R

SUBSCH To display number of subscribers whose Encrypted subscriber authentication key (Ki) has been changed.

S O


CSDL ASDL

C_ERIC-AUC_R12-0_GET_KEY-DATA A_ERIC-AUC_R12-0_GET_KEY-DATA

Table 32: C_ERIC-AUC_R12-0_GET_SUBSCRIBER


Type Class


S O


S R

Table 30: C_ERIC-AUC_R12-0_GET_KEY-DATA


Type Class



Mapping to ASDLs


C_ERIC-AUC_R12-0_MODIFY_KEY-DATAThis service modifies the key data in AUC.


S R


CSDL ASDL

C_ERIC-AUC_R12-0_GET_SUBSCRIBER A_ERIC-AUC_R12-0_GET_SUBSCRIBER

Table 34: C_ERIC-AUC_R12-0_MODIFY_KEY-DATA


Type Class


A4KEY A4 key S O


S O



S R


S O

Table 32: C_ERIC-AUC_R12-0_GET_SUBSCRIBER


Type Class

CSDL commands


Mapping to ASDLs


C_ERIC-AUC_R12-0_MODIFY_SUBSCRIBERThis service modifies the subscriber in AUC.


CSDL ASDL

C_ERIC-AUC_R12-0_MODIFY_KEY-DATA A_ERIC-AUC_R12-0_GET_KEY-DATA-RB

A_ERIC-AUC_R12-0_MODIFY_KEY-DATA

Table 36: C_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER


Type Class


S O

AMF Authentication management field

S O

FSETIND Function set indicator S O


S O


S O


S R



Mapping to ASDLs



CSDL ASDL

C_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER A_ERIC-AUC_R12-0_GET_SUBSCRIBER-RB

A_ERIC-AUC_R12-0_MODIFY_SUBSCRIBER


5

Configuring ASAP to Support Additional NE Instances

You can configure ASAP to support the NE_ERIC-AUC_R12-0-HOST - NEP configuration using the Service Activation Configuration Tool (SACT). Refer to the ASAP Administration Guide for more information.

Below is an example of the Activation.Configuration.XML file for the Ericsson AUC cartridge.

<?xml version="1.0" encoding="UTF-8"?><activationConfig xmlns="http://www.metasolv.com/ServiceActivation/

2003/ActivationConfig" xmlns:cfg="http://www.mslv.com/studio/acti-vation/model/config" xmlns:route="http://www.mslv.com/studio/acti-vation/model/routing" xmlns:sm="http://www.metasolv.com/ServiceActivation/2003/ServiceModel" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<connectionPool name="ERAUCPOL"> <device name="T_ERIC-AUC_R12-0_HOST_conn_1"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_2"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_3"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_4"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_5"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_6"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_7"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device>

Chapter 5: Configuring ASAP to Support Additional NE Instances


<device name="T_ERIC-AUC_R12-0_HOST_conn_8"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_9"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_10"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_11"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_12"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_13"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_14"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_15"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> <device name="T_ERIC-AUC_R12-0_HOST_conn_16"> <environment>DEVELOPMENT</environment> <lineType>TELNET_CONNECTION</lineType> </device> </connectionPool> <element name="T_ERIC-AUC_R12-0_HOST"> <vendor>ERIC</vendor> <technology>AUC</technology> <softwareLoad>R12-0</softwareLoad> <nepServerName>$NEP</nepServerName> <primaryPool>ERAUCPOL</primaryPool> <maximumConnections>16</maximumConnections> <dropTimeout>2</dropTimeout> <spawnThreshold>10</spawnThreshold> <killThreshold>8</killThreshold> <routingElement name="NE_ERIC-AUC_R12-0-HOST"/> <communicationParameter> <label>HOST_IPADDR</label> <value> <value>127.0.0.1</value> </value> <description>The host name or IP Address of the remote

NE.</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter>


<communicationParameter> <label>PORT</label> <value> <value>5000</value> </value> <description>Port number to connect on remote NE host.</

description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>OPEN_TIMEOUT</label> <value> <value>20</value> </value> <description>Connection timeout in seconds.</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>READ_TIMEOUT</label> <value> <value>30</value> </value> <description>Read timeout in seconds.</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>HOST_USERID</label> <value> <value>user</value> </value> <description>Login User Name.</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>HOST_PASSWORD</label> <value> <value>password</value> </value> <description>Password for the User.</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>PROMPT</label> <value> <value><</value> </value> <description>Provisioning prompt.</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>LOGIN_PROMPT</label> <value> <value>USERCODE:</value> </value> <description>Login prompt from the NE</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter>



<communicationParameter> <label>PASSWORD_PROMPT</label> <value> <value>PASSWORD:</value> </value> <description>Password prompt from the NE</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>DOMAIN_PROMPT</label> <value> <value>DOMAIN:</value> </value> <description>Domain prompt from the NE</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>DOMAIN_PASSWORD</label> <value> <value>pthlr1d</value> </value> <description>Domain password for the NE</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>RESPONSELOG</label> <value> <value>TRUE</value> </value> <description>Flag to turn off or on Response log.</

description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> <communicationParameter> <label>PRINT_REPLY</label> <value> <value>FALSE</value> </value> <description>Flag to turn off or on reply in ASCII

format.</description> <lineType>TELNET_CONNECTION</lineType> </communicationParameter> </element></activationConfig>

Extracting source filesBefore you can access an XML file to modify it, you must extract it from the .sar file. Use the following procedure to extract source files from the sar file.

To extract source files

1. Create a repository directory. Copy the .sar file to the new directory and un-jar the sar file.

2. After you un-jar the sar file, you can access the XML files.

Extracting source files


Loading a new XML fileWhen you finish modifying an XML file, you must create a new sar file, then restart the cartridge using the new file.

Follow the instructions in “Testing the cartridge installation” on page 8, for directions on how to load a new XML file.



Date post:	13-Nov-2014
Category:	Documents
Upload:	mclesika
View:	7,105 times
Download:	15 times

Ericsson AUC With Complete HLR MML Guide

Documents