SSC Administration

This chapter provides information and procedures to administer SSC node in PCC deployment.

SSC is an element of Cisco Policy Charging and Control (PCC) solution. SSC acts as an intelligent database for policy services. By acting as a centralized policy software application engine, SSC complements IPCF for converged session handling.

Depending upon the configuration of SSC deployment, administering SSC system involves tasks related to monitoring and administering the interfaces for Sh, Event Notification (EN) and User Data Repository (UDR) applications. SSC uses these interfaces to exchange the subscriber profile or service usage data with respective components of PCC solution as well as with external OSS or BSS. SSC administration also involves tasks related to administering subscriber profile, service plans and data store related to profile and plans.

SSC administration also involves tasks related to security, audit and troubleshooting for the SSC deployment.

This chapter discusses pre-requisites for SSC administration, and covers following sections for SSC administration:

SSC Administration Overview

This section briefly describes SSC administration and monitoring tasks.

In an SSC node deployment scenario all tasks can be divided in following major groups:
  • Administering SSC Node.
  • Provisioning Subscriber and Subscription Information.
  • Monitoring Performance of SSC Node.
  • Monitoring Security of SSC Node.

Administering SSC involves tasks such as administering users, managing the interfaces for various applications such as event notification module, that interact with SSC as well as configuring and monitoring alarms, logs and statistics generated by deployment.

Provisioning subscriber and subscription information includes tasks related to provisioning subscriber profile, notifications and related database objects using methods such as bulk load, SPR APIs, PPT application and Ud interface for external LDAPs. Depending upon your business model SSC can be configured to provision following:
  • Static subscriber profile
  • Dynamic subscriber profile
  • Data or service plans and related add-on
  • Subscription tire
  • Notification template.
As per the deployment requirement SSC can use any of the following provisioning methods or their combination:
  • SSC console.
  • PPT application using XML-RPC interface.
  • External LDAP using Ud interface.
  • SPR provisioning APIs using SOAP/XML.
  • Subscriber Profile Bulk load using shell script and CSV files.
  • Auto provisioning.
Provisioning also includes tasks related to administering profile and usage policy for the subscriber. Tasks such as monitoring and administering subscriber profile and groups as well as subscription plans and data stores related to profile and policy fall under this category.

IMPORTANT:

Profile, plans, group and data store administration tasks are available only when you log-in to SSC Administration Console as a policy administrator or as a user whose credentials include policy administration credentials. For more information refer User Administration section.

Monitoring performance of SSC node includes tasks such as, monitoring system logs and system statistics as well as monitoring system resources using threshold policies.

Monitoring security of SSC node involves tasks such as managing system password, viewing system, SPR and event log audit records, viewing system session information.

Before You Begin SSC Administration

This section includes pre-requisites that must be satisfied and tasks that must be performed before you begin to administer SSC.

This section includes following sub-sections:

Pre-requisites for SSC Administration

This section describes the pre-requisites for administering an SSC.

Following are the pre-requisites for administering SSC:
  • Status of the database, that is being used by the SSC to store subscriber, subscription and policy related data, must be active.
  • Status of IMDB application that is being used by SSC to provide the database grid for the cluster deployment, must be active.
  • Status of SSC application must be active.

    IMPORTANT:

    You can verify the status of database and the IMDB, by executing the script sscdbstatus.sh located in the localhome/ssc/install/spr_install/tools directory.

  • If SSC is deployed in the cluster mode then all the blades in a cluster must be accessible.
  • Sh controller is bound with the host machine as per your IP map, so that SSC application can communicate with other components of PCC solution, such as PPT.
  • Profile controller is bound with the host machine as per your IP map, so that SSC application can communicate with other components of PCC solution, such as PPT.

Ensuring Accessibility of Blade Cluster

Before initiating the administrative tasks for an SSC cluster deployment ensure that the blade cluster is accessible.

To ensure accessibility of a blade cluster:
  1. Ping the host names by referring IP map and ensure that the individual host or blades are reachable.
  2. Check status of the SSC instance on all the blades in cluster. The status should be active on all the blades.
  3. Check status of the database, on the blades that are configured as primary or secondary database using the dbstatus.sh script. Database status should be active.

Binding Sh controller

For SSC to communicate with other components of PCC solution, Sh controller needs to be bound with the host machine as per your IP map.

To bind Sh controller:
  1. Login to the host with root administrative privileges.
  2. Invoke system administrative privileges for the SSC node by issuing following command: 
    su – sscadmin
  3. Execute SSC administration script by issuing following command: 
    ./sscadm
    SSC Administration Console window appears.
  4. Press 1 to access System Administration options.
  5. Press L to access to access List Hosts option. If multiple hosts are available, then select the host machine with which you want to bind the Sh controller.
  6. Press c to access Interface Management option.
  7. Specify the number indicating the Sh controller, for Enter Option. SSC Administration Console binds the Sh controller with the host machine and displays appropriate message.

Binding Profile controller

For SSC to communicate with other components of PCC solution, Profile controller needs to be bound with the host machine as per your IP map.

To bind profile controller:
  1. Login to the host with root administrative privileges.
  2. Invoke system administrative privileges for the SSC node by issuing following command: 
    su – sscadmin
  3. Execute SSC administration script by issuing following command: 
    ./sscadm
    SSC Administration Console window appears.
  4. Press 1 to access System Administration options.
  5. Press L to access to access List Hosts option. If multiple hosts are available, then select the host machine with which you want to bind the Sh controller.
  6. Press c to access Interface Management option.
  7. Specify the number indicating the profile controller, for Enter Option. SSC Administration Console binds the profile controller with the host machine and displays appropriate message.

Controlling Maintenance Mode

This section briefly describes the maintenance mode for the SSC deployment.

During installation, upgrade or trouble shooting, you may need to work on the deployment by manually executing some scripts. An SSC deployment contains various cron jobs and background processes that may interrupt such manual script execution.This can be avoided by using the Maintenance mode. By default this maintenance mode is enabled after successful completion of installation or upgrade procedure.

You need to:
  • Enable the maintenance mode to verify the deployment set-up after any installation or upgrade operation.
  • Disable the maintenance mode after completion of installation, upgrade or troubleshooting activities. This is required for proper functioning of cron jobs and background processes.

Enabling or Disabling Maintenance Mode

To enable to disable the maintenance mode:
  1. Log in with database administrative privileges.
  2. Access the directory /localhome/ssc/tools.
  3. Execute the script maintenanceMode.sh. Following options are available for this script:
    • Status: To view current status of the maintenance mode.
    • Disable: To disable the maintenance mode.
    • Enable: To enable the maintenance mode.
    • Help: To access more information about usage.

Accessing SSC Administration Console

This section describes the prerequisites and procedure to access the SSC administration console.

You can access the SSC Administration Console provided that you satisfy following pre-requisites:
  • SSC has been installed successfully either as a single host or in cluster mode.
  • You have root administrative privileges for the host or the cluster of blades.
  • You have system administrative privileges for the SSC installation.

IMPORTANT:

PuTTY window must be maximized, if PuTTY application is being used to access SSC console.

Using SSC Administration Console

Before initiating the administrative tasks for an SSC cluster deployment using the SSC Administration Console, ensure that you can access this console.

To access SSC administration console:
  1. Login to the host with root administrative privileges.
  2. Invoke system administrative privileges for the SSC node by issuing following command: 
    su – sscadmin
  3. Execute SSC administration script by issuing following command: 
    ./sscadm
    SSC Administration Console window appears.
  4. Specify login and password of appropriate user level. The console displays appropriate status messages in the message window.

Checking Status of SSC Application

This section describes the procedure to view the status of SSC application.

Viewing Status of an SSC Application

All SSC components run as independent processes. SSC allows you to check the status of each such process.

To view status of an SSC application:
  1. Login with SSC Administrative privileges.
  2. Check the status of SSC application instance by issuing following command: 
    ./sscadm
status
    SSC displays current status of its various components such as Heart beat daemon, Login daemon, System manager and Scheduler. For each process the running status indicates that corresponding component is active and running.

    IMPORTANT:

    You can also use the system status option from the SSC Administration Console to view current status of SSC service instance.

Starting SSC Application

This section describes the procedure to start an instance of SSC application.

Starting an SSC Application Instance

All SSC components run as independent processes. SSC provides a script to start or stop an application instance.

To start an SSC application instance:
  1. Login with SSC Administrative privileges.
  2. Start SSC application instance by issuing following command: 
    ./sscadm
start
    SSC initiates its various components such as Heart beat daemon, Login daemon, System manager and Scheduler.
  3. Use status command to ensure that all SSC components are started successfully.

    IMPORTANT:

    You can also use the system status option from the SSC Administration Console to view current status of SSC service instance as well as to start or stop an instance.

Checking Status of IMDB Application

This section describes the procedure to check status of IMDB application.

Viewing Status of IMDB Application

In a cluster deployment of SSC, the In-Memory Data Base (IMDB) application provides a grid that can be used to access the database. Hence, all the instances of this application needs to be active and running for normal functioning of an SSC cluster.

To view status of an IMDB application:
  1. Get the names of IMDB instances, by starting the SSC instance if it is not active by issuing following command: 
    ./sscadm
start
  2. Access the file localhome/ssc/etc/system.cfg from SSC installation directory.
  3. Note the names of IMDB and database instances from the file mentioned in previous step.
  4. To ensure that these instances are active, login with SSC administrative privileges.
  5. Check the status of IMDB instances by issuing following command: 
    ./<IMDB_App>status
    SSC displays a list of active connections to the data store. For each active connection it displays Type of connection, Process Id (PID), Context and Name of the connection along with its Connection Id (ConId). Names of database and IMDB application instances will be displayed here, if these instances are active.
  6. Ensure that a message that indicates that replication agent is running, is displayed while verifying the status of IMDB application using following command: <IMDB_App> status

Bulk Loading Subscriber Profile Data

This section describes the procedure to bulk load subscriber profile data.

Bulk Loading Subscriber Profile Data

This section briefly describes how to execute bulk load operation for profile data.

SSC provides a script to bulk load subscriber profile data, if such data is available in CSV format. Refer to Bulk Load Provisioning feature in Overview chapter for more information regarding structure and nomenclature of the CSV file containing profile data. Enhanced SSC architecture increases the provisioning speed by providing an independent process that caters to provisioning load.

To bulk load subscriber profile data:

  1. Login to SSC deployment with administrative privileges.
  2. Using SSC Administration Console, add subscription tires, data plans and other flags referred in the CSVfile.
  3. Stop SSC application by issuing command./sscadm stop
  4. Login to SSC with database administrator privileges. Stop the IMDB application by executing the script sscimdbshutdown.sh SSC where SSC is the name of data store. This script is located in /localhome/ssc/install/spr_install/tools directory.
  5. Copy the CSV file that you want to upload, to /localhome/ssc directory.
  6. Execute the bulk load script by issuing the command ./ssc/tools/bulk_load_sub –f <.csv file name>.

    IMPORTANT:

    Detailed usage information for the bulk load script can be obtained by executing this script with - h option.

  7. Once the bulk load is complete, verify the subscriber profile data that has been loaded to SSC database. This can be achieved by using the dumpDbdata script as follows/tools/dumpDbdata -c – table spr_sub_plan_bundle – src oracletools/dumpDbdata -c – table spr_sub_msisdn_imsi – src oracle This displays the record count.
  8. Before initiating IMDB (times ten) application, edit the file /localhome/oracle/TimesTen/tt1121/info/sys.odbc.ini Ensure that in the SSC section the parameters PermSize an TempSize has values 3750 and 600 respectively.
  9. Start the IMDB (timesten) application by executing the script sscdbstartup.sh SSC. This script is located in /localhome/ssc/install/spr_install/tools directory.
  10. Refresh IMDB (timesten) application cache by executing the script tt_cache_refersh. sh SSC.
  11. Ensure that the grid is attached properly by executing the script gridnodestatus.sh SSC This script is located in /localhome/ssc/install/spr_install/tools directory. If the grid is not attached then this script attaches it.
  12. Login with SSC administrative privileges and start the SSC application by issuing command ./sscadm start.

Administering SSC Using Console

This section describes the procedures and methods to use the SSC Administration Console, to perform administrative tasks for SSC.

The SSC Administration Console displays current status of an SSC instance as well as starts or stops the SSC instance and displays appropriate messages.

IMPORTANT:

PuTTY window must be maximized, if PuTTY application is being used to access SSC console.

This section includes following sub-sections:

System Status Monitoring

This section describes procedures to view current status of the system along with active tasks related to SSC components and application interfaces as well as message routing table.

Depending upon access privileges for the SSC instance, you can perform following tasks:

Verifying System Status

This section describes how to view system status and start or stop the system.

Viewing System Status

This section describes the procedure to verify the SSC system instance status on SSC node and to start/stop the instance.

To viewing system status:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press a to monitor the status of SSC instance.
  5. Press V to view the current status of the system. It indicates whether this instance of SSC is running or it has stopped. If SSC instance is stopped and you want to start it, press s key. If SSC instance is running and you want to stop it, press the t key.

Viewing Active SSC System Tasks

This section describes how to view active tasks associated with an SSC instance.

Viewing Active Tasks Associated with SSC System Instance

An SSC instance is active when all tasks or processes associated with that instance are active.

To view active SSC system tasks:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press K to monitor the status of processes associated with SSC instance. SSC Administration Console displays the list of SSC base and common component as well as SPR, Ud and event component processes such as sn_hbd, sn, sn_appmgr, sn_shctrl, sn_udctrl, sn_enctrl respectively along with their process id and current status as running or not –running.

Viewing Message Routing Table

This section describes how to view the message routing tables.

Viewing Message Routing Tables

A message routing table displays available routes for a message.

To view message routing tables:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press R to access the message routing table for SSC instance. SSC Administration Console displays the message routing table.

    IMPORTANT:

    Depending upon your access privilege, more routing table information can be generated using the script dumprtbl available in /localhome/ ssc /tools directory.

User Administration

This section describes the procedures to administer the users.

SSC provides pre-defined roles that can be assigned to a user. Each of this user role has different access privileges.

Depending upon your deployment configuration following roles can be assigned to users:
  • Policy Administrator (PA): This role can perform administration tasks for Subscriber Profile Repository (SPR). This role can also add, delete or modify data in the database.
  • Policy Operator (PO): This role can only view subscriber profile and related data in the database.
  • System Administrator (SA): This role can perform all the tasks related to SSC application and deployment specific configurations.
  • System Operator (SO): This role can only view the system configuration.

Depending upon access privileges you can perform following tasks:

Viewing Existing Users

This section describes how to view existing users who can access an SSC instance.

Viewing Existing Users with Assigned Roles

This section describes the procedure to view the existing users who can access SSC node, as well as their configured roles.

To view existing users:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press b to access the user administration options.
  5. Press V to view the user roles configured for your deployment.
  6. Specify the role, to generate a list of users who can access this instance of SSC using the selected role SSC Admin Console displays the list of the users associated with this role.

Adding New User

This section describes how to add a new user.

Adding a New User With Assigned Role

This section describes the procedure to add a User with its assigned role to an SSC node.

To add a new user to an SSC node:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press b to access the user administration options.
  5. Press N to add a new user.
  6. Specify the name of the user.
  7. Specify the password which can be used by this user to access the SSC node.
  8. Specify the role that is to be associated with this user. SSC Administration Console displays the message that the user has been added.

Deleting Existing User

This section describes how delete a user from an SSC node.

Deleting an Existing User From SSC Node

This section describes the procedure to delete a user from an SSC node.

To delete a user from an SSC node:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press b to access the user administration options.
  5. Press t to delete an existing user.
  6. SSC Administration Console invokes the delete user action.
  7. Specify the name of the user that you want to delete. SSC Administration Console deletes the user and displays appropriate message.

Resetting User Password

This section describes how to re-set a user’s password.

Resetting a User Password

This section describes the procedure to re-set a user’s password.

To re-set the password of an existing user:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press b to access the user administration options.
  5. Press R to access change password option.
  6. Specify the name of the user whose password you want to change.
  7. Specify the New password. SSC Administration Console changes the password of the user and displays appropriate message.

Interface Management

This section describes the procedures to administer the host machines and application interfaces that are used by various applications to exchange data with SSC.

SSC uses various network interfaces such as Sp, XML-RPC or FTP to exchange the subscriber profile and session information with other components of the Policy Charging and Control (PCC) solution such as Intelligent Policy Control Function (IPCF), Policy Provisioning Tool (PPT) or Operation Support System (OSS) or Billing Support System (BSS).

Binding an interface with SSC, indicates SSC to associate a task such as Sh application or profile application or event application with a particular server or host machine. If SSC deployment has multiple hosts, then multiple options will appear for binding interfaces.

Binding an interface does not associate an IP address with the task. For associating the IP address with a task, you need to configure IP address for that individual component. For example IP address for Sh application is specified in Sh configuration, where as the bind interface option is used to select the host machine to run the Sh application.

Depending upon SSC deployment configuration, SSC needs to interact with various application interfaces. The bind interface option allows binding of an SSC application interface or one of the SSC components with the host machine.

SSC interface management involves following tasks:

Listing Hosts

This section describes how to list machines that are hosting SSC application.

Listing SSC Host Machines

This section describes the procedure to list machines that are hosting SSC application.

To list hosts:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press c to access the interface management options.
  5. Press L to view the list of hosts configured for SSC node. SSC Administration Console displays information of the hosts machines available for this deployment.

Listing Interface Bindings

This section describes how to list interface bindings

Listing Interface Bindings of SSC Components

This section describes the procedure to list interface bindings used by various components of SSC application.

To list interface bindings:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press c to access the interface management options.
  5. Press t to view the list of bindings configured for SSC node. SSC Administration Console displays the bindings configured for this deployment.

Binding an Interface

This section describes how to bind an application interface of any SSC component with the host machine.

Binding SSC Application Interface With Host Machine

This section describes the procedure to bind an SSC application interface with a host machine.

To bind an interface:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press c to access the interface management options.
  5. Press i to bind the interface. SSC Administration Console displays the bindings configured for this deployment.
  6. Specify the details of binding between the host machine and SSC component. SSC Administration Console binds the interface to the host machine and displays appropriate message.

    IMPORTANT:

    SSC displays appropriate warning message, if some other SSC related task or application is already associated with this machine that you are currently attempting to bind with additional SSC related task or application.

Un-binding an Interface

This section describes how to un-bind an SSC application interface from the host machine.

Un-binding SSC Application Interface From Host Machine

This section describes the procedure to un-bind an SSC application interface from its host machine.

To un-bind an interface:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press c to access the interface management options.
  5. Press u to delete the binding of this interface. SSC Administration Console severs the connection between interface and host machine and displays appropriate message.

    IMPORTANT:

    This option allows you to un-bind an SSC application interface or SSC component from the host machine and isolate that host machine for troubleshooting or maintenance purpose.

SSC Logs Administration

This section provides information about SSC logs.

SSC logs can be used to monitor the availability of various application interfaces and host machines as well as for the troubleshooting issues associated with deployment.

SSC logs are categorized as:
  • Event logs: SSC records information related to events that affect subscriber profile or their service usage. These logs are used to troubleshoot the issues related to profile and service usage of the subscriber. Event logs consist of e-mail and SMS notifications that have been generated by SSC and sent to the subscriber. Following is an example of an event log entry: Timestamp:12-APR-2011 16:31, Module Id:SPR Audit, Event Id: Create Data Plan(15), client_context session_id: 45668734556, user_name: policyadmin, Request: plan_name: plan-2, Response: result_code :0Event logs are stored in a database. Depending upon access privilege, and deployment configuration. You can access these logs using SPR API as well as purge these logs as per requirements.

    IMPORTANT:

    Event logs are also known as audit logs.

  • System logs: SSC also records information related to deployment infrastructure such as web servers and active sessions. System logs are mostly used for administering SSC node and troubleshooting issues related to hardware and software infrastructure of SSC node, such as web servers and associated sessions. System logs can be used to troubleshoot issues related to system performance by analyzing errors and access information related to web servers and AXIS framework.System process logs are stored in file sn_SSC.log. This file can be rotated based on time, size or number of entries, to prevent the log files from growing infinitely. Refer section Changing SSC Log Sink Settings for more information. Following is an example of a system log entry: 11-May-03+14:59:05.226 [sysmgr:1 (24703/18752)] [sysctrl_callback.cpp:329] [info sysmgr 7505] Logged in: user name - SA, role - 10, session id - 1498446599

IMPORTANT:

For more information about system logs, refer to the section Monitoring System Logs.

SSC uses event or audit logs to record information related to:
  • System configuration events.
  • Subscriber Profile Repository (SPR) provisioning events.
  • Subscriber notification logs.
  • Specific logs that are being triggered by the Intelligent Policy Control Function (IPCF) to record specific events related to SSC.
SSC can log e-mail and SMS event notifications that have been generated and sent to the subscriber. The event notification log records time, user id and details of the notification. Subscriber’s preferences determine the events that are being logged. Following events implicitly generate the notifications:
  • Recharge of a data or usage plan.
  • Crossing the threshold associated with the usage of a plan.
  • Resetting of user account at the start of billing cycle.

IMPORTANT:

Billing cycle re-set dates for subscribers and usage threshold levels for configured data plans can be defined using Policy Provisioning Tool (PPT).

IPCF triggers logging in SSC by provisioning the event log actions using event notification (EN) interface between IPCF and SSC.

SSC logs administration involves following tasks:

Changing Sink Settings

The log sink is used to send the SNMP alarms. It is used by the central logging server residing on the management blade. This section describes how to change sink settings.

Changing SSC Log Sink Settings

This section describes the procedure to change sink settings while capturing SSC logs.

To change sink settings:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press d to access log configuration options.
  5. Press K to access sink settings.
  6. Specify maximum size for the individual log file. The range is from 1 to 50 Mb. Maximum size defines upper limit for the size of a log file in MegaBytes (MB).
  7. Specify maximum duration between successive samples. The range is from 1 to 360 minutes. SSC creates a new log file after set duration time is lapsed.
  8. Specify Maximum count. The range is between 0 to 50. Maximum count defines the number of files in which the logs are recorded in rotation.

    IMPORTANT:

    Count zero indicates that the files will not be rotated while recording the logs.

  9. Specify log verbosity as detail, brief or normal. Log verbosity defines the degree of details that are to be recorded while logging values for this parameter. SSC Administration Console updates the sink setting for the log as per the values specified in steps 6 to 9.

Changing Debug Level

This section describes how to change debug levels of the logs that are being captured.

Changing Debug Level For SSC Node

This section describes the procedure to change the Debug level on SSC node.

To change debug level:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press d to access log configuration options.
  5. Press L to access debug level settings.
  6. SSC Administration Console displays existing logging configuration. The log categories correspond to the SSC processes for deployment.
  7. Specify the log category for which you want to change the log level.
  8. Specify the log level. Valid values for the log levels are info, critical, notice, emergency, trace, alert, warning, error and debug. SSC Administration Console assigns updated logging level to the selected logging category.

Changing Session Log Level

This section describers how to change the session log level.

Changing Session Log Level For SSC Node

This section describes the procedure to change the session log level on SSC node.

To change session log level:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press d to access log configuration options.
  5. Press S to change the existing level of session logs.
  6. Specify new logging level. Available levels for session logs are Debug, Info, Warning, Critical and Error.
  7. Specify whether you want to enable or disable the console capture. SSC Administration Console updates session log configuration and displays appropriate message.

Viewing Logging Level Configuration

This section describes how to view logging level configuration.

Viewing Configured Logging Level For SSC Node

This section describes the procedure to view configured logging levels.

To view log level configuration:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press d to access log configuration options.
  5. Press V to view existing log configuration. SSC Administration Console displays the default/configured log level.

    IMPORTANT:

    Currently available logging levels are Debug, Information, Warning, Critical and Error.

Managing Syslog

Syslog protocol is used by SSC network devices such as blades, to send event messages to a logging server, such messages are sent upon activation of associated triggers and used device monitoring and trouble shooing purpose. This section describes how to manage syslog.

Enabling or Disabling Syslog Storage

This section describes the procedure to manage syslog information by enabling or disabling the syslog storage.

To enable or disable the syslog storage:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press d to access log configuration options.
  5. Press M to access manage syslog option.
  6. SSC Administration Console displays whether the syslog option is enabled or disabled, and allows you to change that status by specifying y or n.
  7. If in the previous step, you chose to enable this option then you need to specify name or IP address of the remote computer where you want to store the syslog.
  8. Specify root password for this computer.
  9. SSC Administration Console enables or disables the storage and displays appropriate message in the message window.

SNMP Traps and Alarms Configuration

This section describes the procedures to view and configure the SNMP traps and alarms.

Simple Network Management Protocol (SNMP) traps or alarms, provide information about the network status to system administrators. Alarms can also be used for troubleshooting the issues. Alarms are classified as critical, warning and informational.They mostly indicate the status of various SSC hardware and software components such as chassis, blades, power, I/O and storage modules.

An SSC instance can be configured to generate alarms for following events:
  • Crashing and restarting of processes.
  • Crossing or clearing the threshold by resources.
  • Status change of peers from active to in-active and vice versa.

SNMP traps are sent to the configured SNMP traps receiver. These traps are also stored in the file sn_SSC.log. In the log file the traps can be identified by the keyword alarm.

SNMP traps and alarms configuration involves following tasks:

Configuring SNMP Traps and Alarms Parameters

This section describes how to configure SNMP traps and alarms.

Configuring SNMP Traps and Alarms

This section describes the procedure to configure SNMP traps and alarms.

To set SNMP traps and alarms parameters:
  1. Login with SSC administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press e to access SNMP configuration options.
  5. Press i to view existing SNMP configuration.
  6. Specify the IP address and Port number of the SNMP sever for which you are configuring alarms.

Verifying SNMP Traps and Alarms Configuration

This section describes how to verify SNMP traps and alarms configuration.

Viewing SNMP Traps and Alarms Configuration

This section describes the procedure to verify SNMP traps and alarms configuration.

To view SNMP traps and alarm configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press e to access SNMP configuration options.
  5. Press V to view existing SNMP configuration. SSC Administration Console displays existing SNMP collection server configuration. Such as Port number and server IP address.

Supported SNMP Traps and Alarms

This section describes the list of supported SNMP traps and alarms on SSC node.

Following table lists supported SNMP traps along with their respective ids.
Table 1. SNMP Traps and Object IDs for SSC
Traps Object ID

starSSCEntityStart

starSSCMIBTraps 1

starSSCEntityStop

starSSCMIBTraps 2

starSSCProcessStart

starSSCMIBTraps 3

starSSCProcessStartFail

starSSCMIBTraps 4

starSSCProcessRestartFail

starSSCMIBTraps 5

starSSCFTPServerUnreachable

starSSCMIBTraps 6

starSSCFTPServerReachable

starSSCMIBTraps 7

starSSCShCtrlPeerUp

starSSCMIBTraps 8

starSSCShCtrlPeerDown

starSSCMIBTraps 9

starSSCEnCtrlPeerUp

starSSCMIBTraps 10

starSSCEnCtrlPeerDown

starSSCMIBTraps 11

starSSCSysMgrFailover

starSSCMIBTraps 12

starSSCCpuThresholdCrossed

starSSCMIBTraps 13

starSSCCpuThresholdCleared

starSSCMIBTraps 14

starSSCSwapThresholdCrossed

starSSCMIBTraps 15

starSSCSwapThresholdCleared

starSSCMIBTraps 16

starSSCEnMgrConnFailed

starSSCMIBTraps 17

starSSCEnMgrConnEstablished

starSSCMIBTraps 18

starSSCProcTheshCrossed

starSSCMIBTraps 19

starSSCProcTheshCleared

starSSCMIBTraps 20

starSSCMaxShSessionsCrossed

starSSCMIBTraps 21

starSSCMaxShSessionsCleared

starSSCMIBTraps 22

starSSCMaxPendReqAppMgrCrossed

starSSCMIBTraps 23

starSSCMaxPendReqAppMgrCleared

starSSCMIBTraps 24

starSSCMaxPendReqAppMgrSysCrossed

starSSCMIBTraps 25

starSSCMaxPendReqAppMgrSysCleared

starSSCMIBTraps 26

starSSCSprDown

starSSCMIBTraps 27

starSSCSprUp

starSSCMIBTraps 28

starSSCSprCacheDown

starSSCMIBTraps 29

starSSCSprCacheUp

starSSCMIBTraps 30

starSSCLdapInitFailed

starSSCMIBTraps 31

starSSCLdapInitSuccess

starSSCMIBTraps 32

starSSCProfileConnectionThreshCrossed

StarSSCMIBTraps 33

starSSCProfileConnectionThreshCleared

StarSSCMIBTraps 34

starSSCGeoFailoverStarted

StarSSCMIBTraps 35

starSSCGeoFailoverCompleted

StarSSCMIBTraps 36

starSSCGeoFailoverFailed

StarSSCMIBTraps 37

starSSCRoleChangeFailed

StarSSCMIBTraps 38


IMPORTANT:

For detailed descriptions of SSC traps and alarms, refer to Cisco ASR 5000 Series SNMP MIB Reference.

For alarms related to other software or hardware components of the solution such as CRM/OSS/BSS or IBM Blade Center HT chassis or Cisco UCS C210M1, refer to respective documentation.

Bulk Statistics Configuration

This section describes the procedures to configure the bulk statistics parameters on SSC node.

Depending upon SSC configuration, system statistics can record the information such as:
  • Service level statistics for SSC, IMDB and database services.
  • Database layer parameters.
  • Sh protocol parameters.
  • Subscriber Profile Repository (SPR) API parameters.
Bulk statistics records counters, gauges and fixed value strings for various application schema that are associated with SSC, such as:
  • Sh application.
  • Event notification application.
  • Profile application.

A counter records incremental data cumulatively and rolls over when the limit value is reached. This limit depends upon the data type of the counter. SSC can perform various calculations and record the historical information in form of peak, average or total counters. A gauge records a single value representation of a single instance. A gauge can be used to track particular events in time.

Bulk statistics parameters are useful indicators of system performance.

SSC can be configured to save this information at periodic intervals. This information can be saved in a local directory or on a remote server using FTP.

Bulk statistics configuration for an SSC instance involves following tasks:

IMPORTANT:

Refer to appendices for available event notification, profile and Sh application, bulk statistics schema.

Configuring Bulk Statistics Parameters

This section describes how to configure bulk statistics parameters.

Configuring Bulk Statistics Parameters for SSC Deployment

This section describes the procedure to configure bulk statistics parameters.

To set bulk statistics parameters:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press f to access statistics configuration options.
  5. Press n to configure bulk statistics parameters.
  6. Provide Sample Interval in minutes.

    IMPORTANT:

    Sample interval indicates the time in minutes after which the counters are sampled and written to the file.

    SSC Administration Console displays a message indicating completion of statistical configuration.

Enabling Bulk Statistics Collection

This section describes how to enable bulk statistics collection on an SSC node.

Enabling Bulk Statistics Collection For SSC Deployment

This section describes the procedure to enable bulk statistics collection on an SSC node. Depending upon your deployment configuration, this option may not be available.

To enable bulk statistics collection:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press f to access statistics configuration options.
  5. Press r to enable or disable the bulk statistics configuration depending on available status. SSC Administration Console displays the following message:
    The bulk statistics
feature is disabled. Do you want to enable it? (y/n)
  6. Press y to start the Bulk statistics collection on SSC node or Press n to stop the Bulk statistics collection on SSC node.

Verifying Bulk Statistics Configuration

This section describes how to verify bulk statistics configuration.

Viewing Bulk Statistics Configuration

This section describes the procedure to verify Bulks Statistics collection configuration on SSC node.

To view the bulk statistics configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press f to access statistics configuration options.
  5. Press V to view existing configuration for bulk statistics. SSC Administration Console displays existing bulk statistics configuration parameters such as Sampling interval (in min), FTP interval (in minutes), password, user name, FTP server and the location of the bulk statistics configuration file indicated by the field, Place file at.

Subscriber Profile Repository (SPR) Configuration

This section describers the procedures to access and view the SPR data storage and configure the subscriber identifier in SPR.

SSC uses Subscriber Profile Repository (SPR) data storage along with centralized Policy Charging and Rules Function (PCRF) to implement usage control policies for subscribers. Depending upon your system configuration and services that are being offered, an SPR includes information related to subscriber profile, entitlements and rate plans. SPR can be a standalone database or it can be integrated with exiting subscriber database such as Home Subscriber Server (HSS). An SPR can store information related to subscriber’s profile and activity or session state.

SPR can store following profile related information:
  • IMSI
  • Initial subscriber quality of Service (QoS) profile identifier.
  • MSISDN
  • Mobile 3GPP QoS as defined in home Location Register (HLR)
SPR can store following activity or state related information:
  • Home location
  • Current subscriber QoS profile
  • Current subscriber class Id
  • Service event Id
  • Remaining balance
  • Usage parameters such as volume or time that are being tracked for this service event.
  • Active event queue and usage history
After configuring identifier for the subscriber, the SPR provisioning can accomplished using following methods:
  • Bulk loading subscriber profile.
  • Using SPR APIs and web services.
  • Using XML-RPC interface to communicate with PPT and exchanging parameters such as subscription tires and dynamic profile attributes.
SPR configuration using SSC console involves following tasks:

Configuring Subscriber Identifier in SPR

This section describes how to configure subscriber identifier in SPR.

Configuring Identifier For SPR Subscriber

This section describes the procedure to configure subscriber identifier in SPR.

To configure SPR subscriber identifier:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press g to access SPR configuration option.
  5. Press S to configure identifier for the SPR subscriber.
  6. Specify subscriber identifier, use MSIDN, NAI or IMSI associated with this subscriber as his or her unique identifier. SSC Administration Console configures the identifier for this subscriber and displays appropriate message.

Verifying Subscriber Identifier in SPR

This section describers how to verify a subscriber identifier in SPR.

Verifying Identifier For SPR Subscriber

This section describes the procedure to verify subscriber identifier in SPR.

To verify SPR subscriber identifier:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press g to access SPR configuration option.
  5. Press V to view the identifier for SPR subscriber. SSC Administration Console displays the identifier associated with this subscriber. The identifier is either MSISDN, NAI or IMSI associated with this subscriber.

Configuration Management

This section describes how to manage SSC system configuration.

Depending upon your access privilege for an SSC node, you can configure:
  • Users that can access this deployment with pre-defined privileges.
  • Sh, EN, Ud and other interfaces for exchanging data with other applications such as PPT, IPCF and CRM.
  • Binding of SSC host machine with various application host machines that need to exchange data with SSC.
  • System logs that store values for system parameters.
  • SNMP alarms or traps for various system parameters.
  • Bulk statistics, counters or thresholds that can be used for administering as well as troubleshooting the SSC node.
Configuration management for an SSC instance involves following tasks:

SSC system configuration is saved in XML format. Save Configuration option is used to save or export existing system configuration to an XML format.Whereas Load Con figuration option is used to import a system configuration from XML format, by deleting existing system configuration and loading or using new or imported configuration.

Saving Configuration

This section describes how to save system configuration.

Saving SSC System Configuration

This section describes the procedure to save system configuration.

To save configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press i to access configuration management option.
  5. Press S to save existing configuration.
  6. Specify the filename, along with its relative path from the SSC home directory. Admin Console saves the configuration in a file at specified location and displays appropriate message.

Loading Configuration

This section describes how to load any available system configuration.

Loading SSC System Configuration

This section describes the procedure to load previously saved system configuration.

To load a saved configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press i to access configuration management option.
  5. Press L to load an existing SSC system configuration from the file.
  6. Provide SSC configuration file name which you want to load in SSC system from the existing saved configurations in local directory. SSC Administration Console loads the system configuration described in the file and displays appropriate message.

Profile Controller Configuration

This section describes the procedure to configure the Profile Controller on SSC node.

The profile controller component manages web services using SOAP /XML interfaces that are used to exchange data with external OSS and BSS.

Profile controller configuration contains following tasks:

Configuring Profile Controller

This section describes how to configure a profile controller on an SSC node.

Configuring Profile Controller For SSC Node

This section describes the procedure to configure a profile controller.

To configure the profile controller:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press j to access profile controller configuration option.
  5. Press S to set profile controller configuration.
  6. Specify the IP address of the machine that is hosting the profile controller application.
  7. Specify the port that is to be used to communicate with profile controller application. SSC Administration Console configures the profile controller or displays appropriate error message.

Verifying Profile Controller Configuration

This section describes the procedure to verify the Profile Controller configuration on SSC node.

Verifying Profile Controller configuration For SSC Node

This section describes the procedure to verify the configuration of profile controller.

To verify the Profile Controller configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press j to access profile controller configuration option.
  5. Press V to view existing profile configuration.
  6. SSC Administration Console displays the IP address of the machine hosting the profile controller and the port which can be used to connect to it.

Policy Provisioning Tool (PPT) Configuration

This section describes the procedure to configure the Policy Provisioning Tool (PPT) for SSC deployment.

Policy Provisioning Tool (PPT) is a component of Cisco PCC solution. PPT is a web based client –server application that provides a wizard based interface to configure usage and monitoring policies using various SSC objects such as subscription tires and data plans as well as various IPCF objects such as QoS profile and dynamic rules and PCEF objects such as APN, rules and rule bases. In a PCC deployment PPT may need to communicate with multiple SSC instances. PPT uses XML-RPC protocol for communication with SSC.

PPT application configures subscriber as well as network usage and monitoring policies using following SSC objects:
  • Data plans.
  • SMS and e-mail notification templates.
  • Subscription tires.
  • Dynamic profile attributes.
Depending upon your deployment configuration multiple SSC instances may exchange information with a PPT instance or vice versa. PPT configuration for an SSC instance includes following tasks:

Viewing PPT Configuration

This section describes how to view existing PPT configuration.

Viewing PPT Configuration For SSC Node

This section describes the procedure to view existing PPT configuration.

To view PPT configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press k to access PPT configuration option.
  5. Press V to view existing configuration. SSC Administration Console displays authentication information for PPT controller as well as PPT peer machine configuration parameters such as ip address, name, user name and password.

Configuring PPT Controller (PPTCtrl)

The PPT controller component communicates with external Policy Provisioning Tool (PPT) application using XML-RPC as the communication tool.

Configuring PPT Controller For SSC Node

This section describes the procedure to configure a PPT controller for SSC node.

To configure PPT controller:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press k to access PPT configuration option.
  5. Press P to configure PPT controller.
  6. Specify whether you want to authenticate the PPT instance. SSC Administration Console configures authentication for PPT controller.

Adding PPT Peer

This section describes how to add a PPT peer.

Adding PPT Peer For SSC Node

This section describes the procedure to add a PPT peer for SSC node.

To add a PPT peer:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press k to access PPT configuration option.
  5. Press T to add a PPT peer machine.
  6. Specify the name for PPT peer.
  7. Specify the user name that can used to access this PPT peer.
  8. Specify password to access this machine
  9. Specify the client IP address of the PPT peer machine, with which this SSC instance will be communicating. SSC Administration Console configures PPT client and displays appropriate error message.

Deleting PPT Peer

This section describes how to delete a PPT peer.

Deleting PPT Peer From SSC Deployment

This section describes the procedure to delete a PPT peer from SSC deployment.

To delete a PPT peer:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 1 to access System Administration options.
  4. Press j to access PPT configuration option.
  5. Press r to delete an existing PPT peer machine.
  6. Specify the name of PPT peer machine with which you want to sever communication from this SSC instance.

SSC Home or Roaming Feature Configuration

This section briefly describes how to view and set the home or roaming configuration for the SSC Node.

A home region can be associated with the subscriber profile. Differentiated billing can be provided to subscribers depending upon their usage of the network services from either home region or while they are roaming outside their configured home region.

IMPORTANT:

For more information, refer Roaming Determination Support feature, from the Features and Functionality section of the Overview chapter.

Setting Home or Roaming Configuration for SSC Node

This section describes the procedure to set home or roaming configuration for the SSC node.

To set home or roaming configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 1 to access System Administration options.
  4. Press L to access SSC configuration option.
  5. Press S to access current setting for home or roaming feature. SSC Administration Console displays the current setting of the Home or Roaming feature for this SSC node. You can enable or disable this feature by specifying y or n.

Viewing Home or Roaming Configuration for SSC Node

This section describes the procedure to view home or roaming configuration for the SSC node.

To view home or roaming configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 1 to access System Administration options.
  4. Press L to access SSC configuration option.
  5. Press Vto view current setting for home or roaming feature. SSC Administration Console displays the current setting of the Home or Roaming feature for this SSC node.

    IMPORTANT:

    By default the home orroaming feature is disabled for the SSC node.

Sh Application Configuration

This section describes the procedures to administer the Sh application.

SSC uses Sp interface to query data related to service usage and balance as well as to exchange subscriber profile information with IPCF. Sp interface uses a standard Sh protocol to exchange the XML data with IPCF.

The Sh protocol:
  • Works as an interface between SSC and IPCF.
  • Is a diameter based interface.
  • Requests subscription information related to IP-CAN transport level policies from the SSC database, based on IMSI or MSISDN.

In an SSC deployment a single Sp endpoint can be simultaneously connected to multiple SPR peer servers, for providing load balancing and high availability of profile and usage database. This is achieved by either configuring primary and secondary SPR servers or by using round robin mechanism. Sh application configuration is used for configuring Sh servers and peers for the SSC deployment. This configuration can be used to provide better connection management between the servers and peers. It can also be used to provide load balancing for Sh messages in the deployment. Enhanced SSC architecture supports hierarchal comparison of the SPR attributes. It also provides information about data type and tag attributes.

While administering Sh application you can perform following tasks:

Sh Server Configuration

This section describes the configuration of Sh servers.

While configuring Sh server you perform following tasks:

Configuring Sh Server

This section describes how to configure an Sh server.

Configuring Sh Server Host Machine

This section describes the procedure to configure an Sh server.

To configure Sh Server:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm
  3. Press 2 to access Sh App Admin options.
  4. Press b to access Sh Server Config options.
  5. Press S to configure the Sh server.
  6. Specify the host name of the machine on which you want to configure the Sh server.
  7. Specify the realm for the server.
  8. Specify the IP address for this host machine.
  9. Specify the port that will be used by this server for communicating Sh protocol related messages. SSC Administration Console configures the servers and displays appropriate message.

Deleting Sh Server Configuration

This section describes how to delete an Sh server configuration.

Deleting Sh Server Configuration Form Host Machine

This section describes the procedure to delete an Sh server configuration.

To delete Sh Server Configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access Sh App Admin
  4. Press b to access Sh Server Config options.
  5. Press S to configure the Sh server.
  6. Press t to access the Delete Sh Server option.
  7. Press Y if you want to delete the Sh server. SSC Administration Console deletes the Sh server and displays appropriate message.

    CAUTION:

    Deleting an Sh server deletes all the peers associated with this server.

Verifying Sh Server Configuration

This section describes how to verify theSh sever configuration on SSC node.

Verifying Sh Server Configuration For SSC Instance

This section describes the procedure to verify existing Sh server configuration.

To verify Sh Server Configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access Sh Application Administration (Sh App Admin) option.
  4. Press V to view existing server and peer configuration for Sh application. SSC Administration Console displays Name, IP address, Port number for Sh server and peers along with its realm indicated by associated .com.

    IMPORTANT:

    If Sh server is already configured for your deployment, then SSC Administration Console displays the host name of the machine on which this server is configured.

Sh Peer Configuration

This section describes the configuration of Sh peer server.

While configuring Sh peer servers you perform following tasks:

Adding Sh Peer

This section describes how to add an Sh peer.

Adding Host Machine to Sh Peer Configuration

This section describes the procedure to add an Sh peer.

To add Sh peer Configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access Sh Application Administration (Sh App Admin) option.
  4. Press c access Sh peer configuration (Sh Peer config) options.
  5. Press P to add Sh peer machine.
  6. Specify the Name, Realm and IP address for the Sh peer. SSC Administration Console configures the peer and displays appropriate message.

Viewing Sh Peer

This section describes how to view an Sh peer.

Viewing Sh Peer Configuration

This section describes the procedure to view existing Sh peer configuration.

To view Sh peer Configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access Sh Application Administration (Sh App Admin) option.
  4. Press c access Sh peer configuration (Sh Peer config) options.
  5. Press V to access view peers option. SSC Administration Console displays Sh peer machines configured for your deployment

    IMPORTANT:

    If your session has timed out then, you need to log out and again log in to view Sh peer configuration.

Deleting Sh Peer

This section describes how to delete an Sh peer.

Removing Host Machine From Sh Peer Configuration

This section describes the procedure to delete an Sh peer.

To delete Sh peer Configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access Sh Application Administration (Sh App Admin) option.
  4. Press c access Sh peer configuration (Sh Peer config) options.
  5. Press t to delete an Sh peer.
  6. Specify the Name of the Sh peer, that you want to delete.
  7. Press Y to delete the Sh peer. SSC Administration Console deletes the peer and displays appropriate message.

Administering User Data Repository (UDR)

This section describes the procedures to administer Ud interface.

Subscriber Profile Repository (SPR) stores the subscriber profiles. These profiles are essentially a set of attributes indexed by subscriber identity such as International Mobile Subscriber Identity (IMSI) or Mobile Subscriber ISDN Number (MSISDN). Subscriber profiles can be accessed using various protocols such as Sh, LDAP or SOAP/XML over an Sp interface. If the SPR is implemented using Universal Data Collection (UDC) schema, then User Data Repository (UDR) serves as SPR for such SSC deployments. In such case the profiles are accessed using Ud interface.

The Ud interface can be used to:
  • Exchange data between SSC and HLR or HSS.
  • Facilitate introduction of SSC in an existing deployment.

Ud interface of SSC allows you to introduce SSC in your network and exchange the subscriber profile data with other components of Policy Charging and Control (PCC) solution, such as Customer Relationship Management (CRM), Operation Support System (OSS) or Billing Support System (BSS). This is possible even if these components are storing data in different database formats, provided that the Ud capabilities or Light weight Directory Access Protocol (LDAP) is supported by the data stores that are exchanging the data with SSC.

An SSC instance can be configured as:
  • Ud Server: In this capacity SSC can allow other components of PCC solution to query the profile database. Acting as a server SSC can send the notifications to these component applications when profile data is updated.
  • Ud Client: In this capacity SSC can query and fetch data from other components of PCC solution.

This section includes following sub- sections:

Configuring Server

This section describes the procedures to configure UDR server.

SSC can act as an Ud server, while exchanging the data with other PCC solution components such as CRM and can allow these components to query as well as modify the subscriber usage and profile data stored in SSC.

UDR server configuration involves following tasks:

Adding a UDR Server

This section describes the procedure to add an UDR server.

To add UDR server:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press a access UDR server configuration option.
  5. Press S to add an UDR server to your deployment.
  6. Specify UDR server Id, such as ip address or Fully Qualified Domain Name (FQDN).

    IMPORTANT:

    Server Name or Id should be alphanumeric and less than 32 characters in length.

  7. Specify primary IP of the UDR Server.
  8. Specify Primary UDR server port.
  9. Specify secondary IP of the UDR server.
  10. Specify secondary server UDR port.
  11. Specify whether you want this server to be Ud compliant, by entering y for yes or n for no.
  12. Specify the user name for the UDR.
  13. Specify password for this UDR server.
  14. Specify the UD service url, that is to be used for accessing this server. SSC Administration Console configures the UDR server and displays appropriate message.

Deleting UDR Server

This section describes the procedure to delete an UDR server.

To delete a UDR server:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press a access UDR server configuration option.
  5. Press t to delete an existing UDR server. SSC Administration Console deletes the UDR server and displays appropriate message.

Viewing UDR Server Configuration

This section describes the procedure to view configuration of an existing UDR server.

To view UDR server configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press a access UDR server configuration option.
  5. Press V to view configuration of an existing UDR server. SSC Administration Console displays information such as primary and secondary UDR server Ids, corresponding IP addresses. It also displays whether the given server is Ud compliant or not.

Configuring Search Query

This section describers the procedures to configure a UDR search query, when an SSC instance is acting as a UDR client to query and fetch data from other PCC components.

UDR search query configuration involves following tasks:

Adding UDR Search Query

This section describes the procedure to add an UDR search query.

To add a UDR search query:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press b access UDR search query configuration option.
  5. Press S to add a new search query for the UDR server.
  6. Specify the search query Id.

    IMPORTANT:

    Name or id of the search query should be alphanumeric and less than 32 characters in length.

  7. Specify Base Domain Name (DN) for this query. The query will be executed on this domain only.
  8. Specify the search filter. This is the search criteria.
  9. Specify the output parameters for this query.
  10. Specify whether you want to execute this query or not.
  11. Specify the server Id of the UDR server, on which to execute this query. SSC Administration Console configures the UDR search query and displays appropriate message.

Viewing UDR Search Query

This section describes the procedure to view an existing UDR search query.

To view UDR search query:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press b access UDR search query configuration option.
  5. Press e to view an existing search query. SSC Administration Console displays the list of all existing search queries. For each search query it displays query id, search filter, associated server id, whether this query is to be executed or not and what are the query output parameters.

Deleting UDR Search Query

This section describes the procedure to delete an existing UDR search query.

To delete a UDR search query:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press b access UDR search query configuration option.
  5. Press t to delete an existing search query from the UDR server. SSC Administration Console deletes the search query and displays appropriate message.

Configuring Attribute Map

This section describers the procedures to configure an attribute map Between User Data Repository (UDR) and SSC schema.

An attribute map defines the relationship between attribute types in hierarchical LDAP schema and corresponding columns in the tables of a relational database schema. The map also contains rules that define the procedures for copying or transforming an attribute while exchanging the information between two different data sets.

Attribute map configuration involves following tasks:

Adding UDR-SSC Attribute Map

This section describes the procedure to add an UDR- SSC attribute map.

To add UDR-SSC attribute map:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press c to access UDR attribute map configuration option.
  5. Press S to add a new attribute map for UDR-SSC.
  6. Specify attribute Id, that you want to map with a column in a relational database schema table.
  7. Specify the LDAP attribute that you want to map with an SSC attribute.
  8. Specify the SSC attribute that you want to map with an LDAP attribute.
  9. Specify table name that maps LDAP and SSC attributes for the UDR. SSC Administration Console adds the Ud attribute map and displays appropriate message.

Viewing UDR-SSC Attribute Configuration

This section describes the procedure to view existing UDR -SSC attribute configuration.

To view attribute configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press c to access UDR attribute map configuration option.
  5. Press V to view existing attribute maps. These maps display relationship between LDAP and SSC attributes. SSC Administration Console displays UDR attribute id along with LDAP and SSC UDR attributes and the name of SSC table where these attributes are mapped.

Deleting UDR-SSC Attribute Map

This section describes the procedure to delete an existing UDR-SSC attribute map.

To delete UDR-SSC attribute map:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press c to access UDR attribute map configuration option.
  5. Press t to delete an entry from UDR-SSC attribute map.
  6. Specify id of the attribute that you want to remove from the LDAP-UDR attribute map.
  7. Confirm that you want to delete this attribute configuration. SSC Administration Console deletes the mapping for UDR-LDAP attribute map from the table and displays appropriate message.

Configuring Ud Client

This section describers the procedures to configure an UDR client.

SSC can also act as an Ud client or a front end application for the User Data Repository (UDR) and support multiple target databases. It can read data from LDAP or 3GPP R9 compliant Ud databases.

UDR client configuration involves following tasks:

Viewing UDR Client Configuration

This section describes the procedure to view the configuration of a UDR client.

To view UDR client configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press d to access UDR client configuration option.
  5. Press V to view configuration of all existing UDR clients. SSC Administration Console displays the front-end Id and the service name for all the UD clients configured for your system.

Setting UDR Client Configuration

This section describes the procedure to set the configuration of a UDR client.

To set UDR client configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press d to access UDR client configuration option.
  5. Press C to configure UDR client.
  6. Specify the front-end id. This indicates the front end which you want to set SSC front end.
  7. Specify the service name or subscription, whose information will be exchanged with SSC using this front end. SSC Administration Console configures new Ud client and displays appropriate message.

Configuring Ud Policy

This section describes the procedures to configure Ud polices.

Ud policies are used by the Sh Manager component of SSC to send a message to LDAP interface manager component that fetches the profile from SSC’s LDAP interface.

Following pre-defined Ud policies are available:
  1. Fetch always: This policy will always fetch the user profile, irrespective of its availability in the destination database.
  2. Fetch if absent: This policy will fetch the user profile if it is not available in the destination database.
UDR policy configuration involves following tasks:

Viewing UDR Policy

This section describes the procedure to view an existing UDR policy.

To view UDR policy:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press e to access Ud policy configuration option.
  5. Press p to view existing UDR policies.

Setting UDR Policy

This section describes the procedure to set a UDR policy.

To set UDR policy:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press e to access Ud policy configuration option.
  5. Press Y to set UDR policy.
  6. Specify the number, to indicate the policy that you want to set. For example select 1 to specify fetch always or 2 specify fetch if absent as a UDR policy. SSC Administration Console configures the Ud policy and displays appropriate message.

Configuring Usage Policy

This section describes the procedures to configure policy for exchanging service usage data with UDR.

SSC can receive the service usage related data from User Data Repository (UDR) servers. You can configure a policy either to update the service usage data in SSC from UDR server or to ignore such data from the UDR server.

Usage policy configuration involves following tasks:

Viewing Usage Policy

This section describes the procedure to view usage policy.

To view usage policy:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press f to access usage policy configuration option.
  5. Press P to view existing usage policies for receiving the usage data from User Data Repository (UDR) to SSC. SSC Administration Console displays the configured usage data exchange policy between SSC and UDR.

Setting Usage Policy

This section describes the procedure to set usage policy.

To set usage policy:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press f to access usage policy configuration option.
  5. Press Y to configure policy for updating usage data from UDR.
  6. Specify the usage policy number. Select 1to receive updated usage data from UDR or select 2if you do not want SSC to receive current usage data from the UDR server. SSC Administration Console configures usage policy for UDR data and displays appropriate message.

Configuring UDR Controller

This section describes the procedures to configure UDR controller.

Some CRM deployments communicate with other PCC components using LDAP or Ud interface. SSC can communicate with such deployments by acting as a UDR controller for them. It allows CRM to query or modify the subscriber profile and usage data stored in the SSC data base. By acting as UDR controller, SSC also allows CRM component to register for change notifications from SSC.

UDR controller configuration involves following tasks:

Viewing UDR Controller Configuration

This section describes the procedure to view configuration of an existing UDR controller.

To view UDR controller configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press g to access UDR controller configuration option.
  5. Press V to view configuration of an existing UDR controller. SSC Administration Console displays UDR controller parameters such as, Base DN, password, IP address, Port number and User Name.

Setting UDR Controller Configuration

This section describes the procedure to set configuration of a UDR controller.

To set UDR controller configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press g to access UDR controller configuration option.
  5. Press C to set the controller configuration.
  6. Specify IP address for UDR controller.
  7. Specify the port number which will be used by this UDR controller for communication.
  8. Specify the Base DN for this controller.
  9. Specify the user name which will be used to access this controller.
  10. Specify the password required to access this controller. SSC Administration Console configures the controller with parameters and displays appropriate message.

Configuring Ud Client for CRM

This section describes the procedures to configure a Ud client to exchange data with Customer Relationship Management (CRM) application.

Configuring Ud client for CRM, involves following tasks:

Configuring Ud Client for CRM

This section describes the procedure to configure a Ud client for CRM.

To configure UD client for CRM:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press i to configure a Ud client for CRM.
  5. Press C to access the configuration option for this client.
  6. Specify Id for the front end for this CRM client.
  7. Specify the URL which is required to access this front end.
  8. Specify the port number that will be used for communicating with this front end of CRM client. SSC Administration Console configures the Ud client and displays appropriate message.

Viewing Ud Client Configuration

This section describes the procedure to view configuration of a Ud client.

To view Ud client configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press i to configure a Ud client for CRM.
  5. Press V to view existing configuration for CRM Ud client. SSC Administration Console displays Id for the front end and the URL that is to be used to access this CRM client, along with the port number that is to be used for communicating with this client.

Configuring an Update Query

This section describers the procedures to configure an update query for a UDR server.

Update query configuration involves following tasks:

Adding Update Query

This section describes the procedure to add an update query.

To add an update query:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press j to access update query configuration option.
  5. Press U to add a new update query for the UDR server.
  6. Specify the update query Id.
  7. Specify Base Domain Name (DN) for this query. The query will be executed on this domain only.
  8. Specify the search filter. This is the search criteria.
  9. Specify the output parameters for this query.
  10. Specify whether you want to execute this query or not.
  11. Specify the server Id of the UDR server, on which to execute this query. SSC Administration Console configures the update query and displays appropriate message.

Viewing Update Query

This section describes the procedure to view an existing update query.

To view an update query:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press j to access update query configuration option.
  5. Press p to access view update query option. SSC Administration Console displays a list of all the configured update queries. For each query it displays all the configuration parameters explained in the previous section.

Deleting Update Query

This section describes the procedure to delete an existing update query.

To delete an update query:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access UDR Administration option.
  4. Press j to access update query configuration option.
  5. Press r to delete an existing update query for the UDR server.
  6. Specify the id of an update query that you want to delete. SSC Administration Console deletes the update query, and displays appropriate message.

Administering Event Notification Application

This section describes the procedures to administer an event notification application.

Event notifications are used to generate and send the notifications to subscribers. These notifications are mostly related to subscribers service usage and policy changes that may affect the subscriber.

This section includes following sub-sections:

Configuring Event Notification Server

This section describers the procedures to configure an event notification server.

Event notification server is used by SSC to communicate with other components of PCC solutions such as IPCF that want to use the event notification functionality provided by SSC. Notification server can also be used to handle load balancing among SMTP and SMPP servers used by the event notification module.

Event notification server configuration involves following tasks:

Configuring Event Notification Server Instance

This section describes the procedure to configure an event notification server instance.

To configure an event notification server instance:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press a to access event notification server configuration option.
  5. Press S to configure an event notification server.
  6. Specify server IP address.
  7. Specify server port to communicate with this server. SSC Administration Console displays the IP address and port for all configured event notification servers.

Viewing Event Notification Server Instance

This section describes the procedure to view an event notification server instance.

To view an event notification server instance:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press a to access event notification server configuration option.
  5. Press V to view existing server configuration. SSC Administration Console displays the IP address and port for all configured event notification servers.

Configuring SMTP Server

This section describes the procedures to configure an SMTP server.

Simple Mail Transfer Protocol (SMTP) is a standard used by Internet Protocol (IP) networks to transmit e-mails. SMTP is used by mail servers and Mail Transfer Agents (MTAs) to send or receive mails. Mail client applications use SMTP to send messages to servers. SSC allows you to configure SMTP servers that can be used to send event notification related messages as e-mails.

SMTP server configuration involves following tasks:

Configuring Primary SMTP Server

This section describes the procedure to configure primary SMTP server.

To configure primary SMTP server:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press b to access SMTP server configuration option.
  5. Press P to configure primary SMTP server.
  6. Specify the server IP address.
  7. Specify the port used to communicate with this server.
  8. Specify the e-mail throttle rate. This indicates maximum number of e-mails that can be sent per second. SSC Administration Console configures the server or displays appropriate error message.

Configuring Secondary SMTP Server

This section describes the procedure to configure secondary SMTP server.

To configure secondary SMTP server:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press b to access SMTP server configuration option.
  5. Press S to configure secondary SMTP server.
  6. Specify IP address of the machine that is hosting secondary SMTP server.
  7. Specify the port used to communicate with this server.
  8. Specify e-mail throttle rate. This rate indicates maximum number of e-mails that can be sent per second. SSC Administration Console configures the secondary SMTP server or displays appropriate error message.

Viewing SMTP Server Configuration

This section describes the procedure to view configuration of existing SMTP servers.

To view SMTP server configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press b to access SMTP server configuration option.
  5. Press V to view existing SMTP server configuration. SSC Administration Console displays IP address, port that is to be used for communication with this server, and e-mail throttle rate for all the configured primary as well as secondary SMTP servers.

Configuring SMPP Server

This section describes the procedures to configure an SMPP server.

Short Message Peer to Peer (SMPP) protocol is used for exchanging SMS messages between Short Message Service Centers (SMSCs) and external short messaging entities. SSC allows you to configure SMPP servers that can be used to send event notifications and related messages as an SMS.

Type Of Numbering (TON) and Numbering Plan Indicator (NPI) are mandatory for supporting connection with SMPP server. Different combinations of TON and NPI values are supported while sending SMS to SMSC using SMPP interface. SMPP server configuration can be used to configure both source as well as destination TON and NPI values.

SMPP server configuration involves following tasks:

Configuring Primary SMPP Server

This section describes the procedure to configure primary SMPP server.

To configure primary SMPP server:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press c to access SMPP server configuration option.
  5. Press P to configure primary SMPP server.
  6. Specify client system Id. This indicates unique identification number of client system or subscriber system. This is supplied by SMPP provider.
  7. Specify password to access the machine hosting SMPP server.
  8. Specify system type. This indicates the category of client (or subscriber) system. Maximum 8 characters are allowed to indicate the system type. System type is always SMPP for an SMPP server.
  9. Specify the service type. This indicates the category of service being used by the subscribers receiving this notification. Maximum 8 characters are allowed to indicate the service type. Service type is the event, regarding which the notification is being sent thru SMS.
  10. Specify the IP address or FQDN of the SMPP primary server. This indicates the IP address or Fully Qualified domain Name (FQDN) of the machine that is hosting the SMPP server.
  11. Specify server port. This indicates the port number that is to be used for communicating with the machine that is hosting SMPP server.
  12. Specify source address. This indicates IP address of the SMPP server.
  13. Specify server response time in seconds. This indicates the time by which the machine hosting the event notification server should acknowledge or drop the event request.
  14. Specify enquire link time in seconds. This indicates time by which the link is accessible.
  15. Specify event throttle rate. This rate indicates maximum number of SMSs that can be sent per second. SSC Administration Console configures primary SMPP server or displays appropriate error message.

Configuring Secondary SMPP Server

This section describes the procedure to configure secondary SMPP server.

To configure secondary SMPP server:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press c to access SMPP server configuration option.
  5. Press S to configure secondary SMPP server. SSC Administration Console configures parameters for secondary SMPP server, as per step 6 to step 15 of previous section – Configuring primary SMPP server.

Viewing SMPP Server Configuration

This section describes the procedure to view configuration of SMPP servers.

To view SMPP server configuration:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press c to access SMPP server configuration option.
  5. Press V to view existing SMPP server configuration. SSC Administration Console displays configured values of SMPP server parameters, mentioned in sections configuring primary and secondary SMPP servers.

    IMPORTANT:

    This information is displayed for all configured SMPP servers i.e. for primary as well as secondary servers.

Configuring E-mail Layout

This section describes the procedures to configure an e-mail layout.

E-mail layout configuration involves following tasks:

Configuring E-mail Parameters

This section describes the procedure to configure e-mail parameters.

To configure e-mail parameters:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press d to access e-mail parameters configuration option.
  5. Press P to configure e-mail parameters.
  6. Specify e-mail footer.
  7. Specify e-mail header.
  8. Specify sender's e-mail address. SSC Administration Console configures e-mail parameters or displays appropriate error message.

Viewing E-mail Parameters

This section describes the procedure to view mail parameters.

To view e-mail parameters:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press d to access mail parameters configuration option.
  5. Press V to view existing e-mail parameters. SSC Administration Console displays the header, footer and sender’s e-mail address that will be used for sending the event notification thru e-mail

Configuring Interface Monitor

This section describers the procedures to configure and view interface parameters for event notification interface.

SSC allows you to configure and view the retry count and retry interval for event notification interface.

Interface monitor configuration involves following tasks:

Configuring Retry Parameters for Event Notification (EN) Interface

This section describes the procedure to configure retry parameters for an EN interface.

To configure retry parameters for an EN interface:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press e to access interface monitor configuration option.
  5. Press C to configure the retry parameters for EN interface.
  6. Specify interface retry count.
  7. Specify interface retry interval. SSC Administration Console configures interface monitoring parameters.

Viewing Retry Parameters for Event Notification (EN) Interface

This section describes the procedure to view retry parameters, configured for an EN interface.

To view an event notification server instance:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access Event notification Application Administration (EventAppAdmin) options.
  4. Press e to access interface monitor configuration option.
  5. Press V to view existing retry parameters for the EN interface. SSC Administration Console displays interface retry count and interface retry interval configured for the EN interface.

Monitoring SSC Performance Using Console

This section describes the procedures to use the SSC Administration Console, to monitor the performance of SSC system.

This section includes following sub-sections:

Monitoring System Log

This section describes the procedures to monitor the system logs.

SSC node, logs certain system parameters periodically. System logs record information about the web servers used in the deployment along with session and system information. These logs can be used for troubleshooting issues related to both system hardware and related operating system software used by the SSC node.

Depending upon the deployment configuration, these logs can be:
  • stored locally in files on the SSC host machines.
  • using system syslog, these logs can be stored on some external server.

IMPORTANT:

System logs are different from event logs. Refer SSC Logs Administration, for more information on event logs.

System logs are categorized as:
  • System Log
  • Session Log
  • Web Server Log.
The web server logs are further categorized as:
  • Web server error logs: These contain the errors encountered while accessing the web server. These are stored in error.log file in ../localhome/ssc /3rdparty/apapche/logs directory.
  • Web server access logs: These contain access details for the web server. These are stored in access.log file in ../localhome/ssc/3rdparty/apache/logs directory.
  • AXIS framework log: These contain SSC framework related information. These are stored in libaxis.log file in ../localhome/ssc/3rdparty/axis/modules/logging directory.
System logs monitoring involves following tasks:

Accessing System Log

This section describes the procedure to access system logs.

To access system log:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press a to access system log option.
  5. Press S to view system logs. SSC Administration Console displays the locations where system process logs as well as system start-up and internal log files are created.

    IMPORTANT:

    The file sn-SSC.log contains system process logs and the file startup.log contains system start-up and internal logs.

Accessing Session Log

This section describes the procedure to access session log.

To access session log:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press n to access session log option. SSC administration Console displays location of the session log file.

    IMPORTANT:

    The file session_xxxxx.log contains the session log, where xxxxxx is concatenation of the date on which the logs are generated and a system generated number. For example a file session_2010122117346.log stores the session logs for 21st December 2010.

Accessing Web Server Log

This section describes the procedure to access web server log.

To access web server log:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press w to access web server log option. SSC administration Console displays location of the web server log files.

Monitoring System Statistics

This section describes the procedures to monitor the system statistics.

SSC node stores certain system parameters at periodic time interval. These parameters can be used to monitor the system performance as well as for troubleshooting purpose.

Depending upon your access privilege following system statistics views are available:
  • Summary View: This view generates a summary of important statistical parameters.
  • By Process View: The SSC node spawns different processes such as SysMgr, AppMgr, EnCtrl and ShCtrl for the installed SSC components. This view displays the statistical parameters related to the selected process.
  • Refresh View: This view updates the statistical information on the UI with latest available values for the selected parameters.
  • Clear Stats View: This view clears the displayed values of bulk statistics parameters.
Monitoring system statistics involves following tasks:

Viewing System Statistics by Summary

This section describes the procedure to view system statistics summary.

To access system statistics by summary:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press b to access system statistics option.
  5. Press s to access the summary view. SSC Administration Console displays a summary of system statistics. It displays current values of important statistical parameters related to different SSC processes such as Sh and event notification applications, UDR controller, that are active for this SSC instance.

Viewing System Statistics by Process

This section describes the procedure to view system statistics associated with various SSC processes.

To access system statistics by process:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press b to access system statistics option.
  5. Press P to access system statistics related to specific processes. SSC Administration Console displays active processes associated with this instance of SSC.
  6. Specify the number associated with process, whose statistics you want to view.
  7. enter N if you want to view IPC statistics, V for verbose display or B for basic display.
  8. Specify the instance, whose statistical parameters you want to view. SSC Administration Console displays available data or appropriate error message.

Clearing System Statistics View

This section describes the procedure to clear the displayed statistics.

To clear system statistics view:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press b to access system statistics option.
  5. Press t to clear the displayed statistics. SSC Administration Console displays active process related to this SSC instance.
  6. Specify the process for which you want to clear the bulk statistics. SSC Administration Console clears the statistics related to this process.

Refreshing System Statistics View

This section describes the procedure to refresh the displayed statistics.

To refresh system statistics view:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press b to access system statistics option.
  5. Press R to refresh existing view. SSC Administration Console displays updated values for the bulk statistics.

    IMPORTANT:

    The refresh view option will work only when you have selected summary or by process view options.

Monitoring System Resources

This section describes the procedures to monitor the system resources using thresholds.

Threshold is a concept used to monitor a system, such as SSC, for conditions that could potentially introduce errors or cause outage. In most cases these conditions are temporary, such as high CPU utilization or inconsistency in the processes associated with scheduler or heart beat daemon and are resolved quickly.

However continuous occurring of such conditions in large number and during specific time interval may indicate larger issues.

Thresholds help to identify such conditions and allow administrators to take preventive actions.

Depending upon the system configuration following threshold models are supported:
  • Alert: A resource is monitored and alert condition occurs when value associated with this resource reaches or exceeds the configured high threshold within specified polling interval. An alert is then generated and sent at the end of polling interval.
  • Alarm: For a resource, both high and low thresholds are defined, alarm condition occurs when resource value reaches or exceeds high threshold value, in such case alarm is generated and sent at end of polling interval. This alarm is cleared if during the next polling interval the resource value equals or falls below the low threshold value.

Thresholds can be used for system administration as well as troubleshooting purpose.You can configure threshold percentage for certain system resources such as processes associated with CPU usage, logging or scheduling.

As per the deployment configuration and your access privileges, you can view or configure the thresholds associated with following:
  • System resources.
  • System processes.
  • Applications.
As per your deployment system resources can be further categorized as:
  • CPU
  • SWAP
As per your deployment, active SSC processes associated with this SSC instance can be categorized as:
  • Heart Beat Daemon (HbD)
  • Log Daemon (LogD)
  • System Manager (SysMgr)
  • Scheduler
  • Sh Controller (ShCtrl)
  • Application Manager (AppMgr)
  • Event Notification Controller (EnCtrl)
  • Profile Controller (ProCtrl)
  • UDR Manager(UdrMgr)
As per your deployment the applications associated with this SSC instance can be categorized as:
  • Maximum active Sh sessions.
  • Maximum input queue size for application manager per blade.
  • Maximum input queue size for application manager across the system.

System resource monitoring involves following tasks:

Viewing Thresholds

This section describes the procedure to view thresholds.

To view thresholds:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press C to access resource monitor option.
  5. Press V to view existing thresholds. SSC Administration Console displays thresholds in percentage for processes associated with configured resources.

Configuring Thresholds

This section describes the procedure to configure thresholds.

To configure thresholds:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press C to access resource monitor option.
  5. Press C to configure thresholds.
  6. Specify thresholds in percentage for process associated with configured resources.

    IMPORTANT:

    The SSC installation process, sets the default threshold values for resources while configuring the data base.

Viewing System Status

This section describes the procedure to view system status.

To view system status:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press C to access resource monitor option.
  5. Press S to view system status. SSC administration Console displays the system status. it displays percentage of active processes associated with the host name.

    IMPORTANT:

    System status includes information such as active processes and Sh sessions associated with the host (or blade) name. This includes processes such as Logd. SysMgr, ShCtrl as well as processes associated with CPU and swap. The status also displays items in input queue for the AppMgr process.

Monitoring Threshold Policies

This section describes the procedures to monitor threshold policies.

Threshold policies can be used for monitoring the service usage of the subscribers. You can also use policies for administering some parameters of SSC.

Monitoring threshold policies involves following tasks:

Viewing Threshold Policies

This section describes the procedure to view threshold policies.

To view threshold policies:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press d to access threshold policy option.
  5. Press V to view existing threshold policies. SSC administration Console displays a list of configured threshold policies.

    IMPORTANT:

    Depending upon services that are being offered and your threshold configuration strategy, threshold policies can be categorized as, threshold breach policies or maximum active Sh session breach policies.

Configuring Threshold Policies

This section describes the procedure to configure threshold policies.

To configure threshold policies:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access performance options.
  4. Press C to access resource monitor option.
  5. Press P to configure a threshold policy.
  6. Specify whether you want to reject the new session when the threshold is breached. SSC Administration Console configures the threshold breach policy and displays appropriate message.

Administering Profile

This section describes the procedures to administer the subscriber profile.

IMPORTANT:

The profile administration option is available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then profile administration option can be accessed by pressing 1 otherwise it can be accessed by pressing 6 or associated option number. For more information refer User Administration section.

Each subscriber account is identified by its unique International Mobile Subscriber Identity (IMSI) or Mobile Subscriber ISDN Number (MSISDN). A subscriber profile links plans and subscription tires to an account. Thus a subscriber profile facilitates service customization for a specific subscriber account.

A subscriber profile identifies various usage, data or service plans and add-on, associated with a subscriber, along with privileges and entitlements that can be availed by the profile holder.

Depending upon the services that are being provided, a subscriber profile may have following attributes:
  • Mobile Subscriber ISDN Number (MSISDN).
  • International Mobile Subscriber Identity (IMSI).
  • Enable e-mail flag.
  • Enable SMS flag.
  • Subscription Status.
  • Flag Name.
  • Flag value.
  • Billing start date.

IMPORTANT:

Attributes of the subscriber profile can also be provisioned using SPR APIs such as createSubscriber, updateSubscriber and deleteSubscriber. Refer Cisco SPR Provisioning Guide for more information.

IMPORTANT:

SSC provides a facility to bulk load the subscriber profile data, refer Bulk Load Provisioning feature in Overview chapter and the procedure to bulk load the subscriber profile in Before You Begin section of SSC Administration chapter.

Profile administration includes tasks related to provisioning of subscriber profiles as well as plans. Provisioning tasks can be categorized as:
  • Creating new subscriber profiles or plans.
  • Associating plans with subscriber profile.
  • Modifying existing subscriber profiles.
  • Modifying plans for top-up facility.
  • Viewing individual subscriber profile or plan.
  • View all configured subscriber profiles or plans.

This section includes following sub-sections:

Viewing Subscriber Profile and Usage

This section describes the procedures to view subscriber’s profile and service usage.

Viewing subscriber profile and associated usage of services involves following tasks:

Viewing Existing Subscriber Profile

This section describes the procedure to view existing subscriber profile.

To view existing profile:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 1 to access profile administration option.
  4. Press a to access view profile option.
  5. Specify International Mobile Subscriber Identity (IMSI) or Mobile Subscriber ISDN Number (MSISDN) or NAI associated with the subscriber whose profile you want to view. SSC Administration Console displays the subscriber record.

Viewing Service Usage

This section describes the procedure to view existing usage of a subscriber profile.

To view usage:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 1 to access profile administration option.
  4. Press b to access view usage option.
  5. Specify International Mobile Subscriber Identity (IMSI) or Mobile Subscriber ISDN Number (MSISDN) or NAI associated with the subscriber, whose usage you want to view.
  6. Specify do you want to view usage for a specific data plan.
  7. Provide the plan id, if you have answered as yes in the previous step.
  8. Specify plan name, if you have answered as yes in step 6. SSC Administration Console displays the subscriber usage or appropriate error message.

Administering Subscriber Profile

This section describes the procedures to administer a subscriber profile.

Subscriber profile administration involves following tasks:

IMPORTANT:

Enhanced SSC architecture supports multiple values for subscriber profile attributes. If a given attribute such as description supports multiple values, then while maintaining the subscriber profile, SSC Administration Console keeps on displaying this field till you enter a blank for it.

Adding Subscriber Profile

This section describes the procedure to add a subscriber profile.

To add a subscriber profile:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 1 to access profile administration option.
  4. Press b to access add subscriber option.
  5. SSC Administration Console displays a message for providing subscriber credentials.

    IMPORTANT:

    For steps 6 to 8, press enter key if you do not want to change the existing value.

  6. Specify either IMSI, MSISDN or NAI as an id for this subscriber.
  7. Specify subscriber name and description.
  8. Specify Billing Date in format DD/MM/YYYY.
  9. Specify subscription tire.
  10. Specify whether you want to send SMS notifications to this subscriber.
  11. Specify e-mail address for sending the notifications through mail.
  12. Specify whether you want to give profile attribute to this subscriber. SSC Administration Console communicates this information to the back-end database and displays appropriate message.

Deleting Subscriber Profile

This section describes the procedure to delete a subscriber profile.

To delete a subscriber profile:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 1 to access profile administration option.
  4. Press c to access delete subscriber option.
  5. Specify either IMSI, MSISDN or NAI as an id for this subscriber whose record you want to delete from the database. SSC Administration Console deletes the record and displays appropriate message. Or it displays an error message indicating that such record is not available.

Modifying Subscriber Profile

This section describes the procedure to modify a subscriber profile.

To modify a subscriber profile:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 1 to access profile administration option.
  4. Press d to access modify subscriber option.
  5. Specify either IMSI, MSISDN or NAI as an id for this subscriber, whose record you want to modify in the database.

    IMPORTANT:

    For steps 6 to 8, press enter key if you do not want to change the existing value.

  6. Specify subscriber name and description.
  7. Specify Billing Date in format DD/MM/YYYY.
  8. Specify subscription tire.
  9. Specify whether you want to send SMS notifications to this subscriber.
  10. Specify e-mail address for sending the notifications through mail.
  11. Specify whether you want to give profile attribute to this subscriber. SSC Administration Console communicates this information to the back-end database and displays appropriate message.

Administering Group Accounts

This section describes the procedures to administer group accounts.

IMPORTANT:

The group administration option is available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then group administration option can be accessed by pressing 2 otherwise it can be accessed by pressing 7 or associated option number. For more information refer User Administration section.

A group account is a subscription that is being availed by multiple subscribers simultaneously where one of the subscribers is designated as head of the group and can have special administrative privileges for all other members of this group. Multiple data plans may be associated with a group account. Such an account can be used to:
  • Allow multiple subscribers to share an account.
  • Provide differential treatment to head of the group as compare to other members.
  • Configure thresholds on group account usage.
  • Generate notifications upon reaching such thresholds.

IMPORTANT:

A group account is mostly associated with family plans.

Group administration includes following provisioning tasks:
  • Creating group accounts and associating members with such accounts.
  • Modifying group account by adding or deleting its members.
  • Viewing existing group profile.
  • Associating plan with group profile.

This section includes following sub-sections:

Manage Group

This section describes the procedure to view, add and delete group accounts.

Managing group profile involves following tasks:

Viewing Existing Group Profile

This section describes the procedure to view an existing group profile.

To view existing group profile:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access group administration option.
  4. Press a to access view option. This option allows you to view existing group accounts and plans.
  5. Press V to access view details option.
  6. Specify the group name whose details you want to view. SSC Administration Console displays the group profile details such as its name, MSISDN, subscription tire, billing date, short description of the group, its status and e-mail as well as SMS notification status.

Adding Group Account

This section describes the procedure to add a group account.

To add a group account:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access group administration option.
  4. Press a to access manage group option.
  5. Press o to configure a new subscriber group account.
  6. Specify the group account name.
  7. Specify the description of this group account.
  8. Specify the subscription tire associated with this group.
  9. Specify SMS notification preference. If you select, yes, then notifications will be sent as SMS.
  10. Specify MSISDN.
  11. Specify e-mail notification preference. If you select yes, then notifications will be sent as an e-mail.
  12. If you select yes in the previous step, then specify the e-mail address.
  13. Specify billing date in dd/mm/yyyy format.

Deleting Group Account

This section describes the procedure to delete a group account.

To delete a group account:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access group administration option.
  4. Press a to access manage group option.
  5. Press t to delete an existing group account. SSC Administration Console deletes the group account and displays appropriate message.

Manage Members

This section describes the procedures to add a member to and delete a member from group account.

Managing members of a group account involves following tasks:

Adding Member to Group Account

This section describes the procedure to add a member to a group account.

To add a member to group account:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access group administration option.
  4. Press b to access manage member option.
  5. Press M to add a member to an existing group account.
  6. Specify name of the group to which you want to add this member.
  7. Specify subscriber credentials. You can use either IMSI/MSIDN or NAI of this subscriber as well as its subscriber id, and add this subscriber to the group.
  8. Specify whether you want to add this subscriber as group administrator SSC Administration Console adds the member to the group and displays appropriate message.

Deleting Member from Group Account

This section describes the procedure to delete a member from a group account.

To delete a member from group account:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access group administration option.
  4. Press b to access manage member option.
  5. Press t to delete a member from an existing group account.
  6. Specify name of the group account from which you want to delete this member.
  7. Specify whether you want to delete this subscriber from the associated group account. SSC Administration Console adds the member to the group and displays appropriate message.

Manage Subscriptions

This section describes the procedure to associate a plan with the group profile.

Managing subscriptions for a group account involves following tasks:

Associating Plan with Group Profile

This section describes the procedure to associate a plan with group profile.

To associate a plan with group profile:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 2 to access group administration option.
  4. Press c to access manage subscription option.
  5. Press f to associate a plan with an existing group account.
  6. Specify the group account name.
  7. Specify subscription order.
  8. Specify start date and end date in DD/MM/YYYY format.
  9. Specify whether you want to generate the notifications.
  10. Specify whether you want to associate more plans with this group.
  11. If you select yes in previous step, then provide the information for additional plans. SSC Administration Console associates the plan with the group account and displays appropriate message.

Administering Plans

This section describes the procedures to administer the service and data plans.

IMPORTANT:

The plan administration option is available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then plan administration option can be accessed by pressing 3 otherwise it can be accessed by pressing 8 or associated option number. For more information refer User Administration section.

Depending upon services that are being provided as per the business model, following parameters constitute a plan:
  • Unique name and Id.
  • Payment type such as pre-paid or post-paid.
  • Subscription validity such as start and end time.
  • Frequency of re-charge period such as weekly, monthly, six monthly.
  • Category of the service or subscriber as defined by service provider.
  • Priority of service or subscriber as defined by service provider.
  • Grace period, and number of days allowed, if the period is enabled.
  • QoS parameters.
  • Usage limits for volume or time consumption.
  • Thresholds for volume or time consumption.
A plan defines the services that are being rendered to the subscriber. Depending upon their payment method such as pre-paid or post-paid, different categories of plans can be associated with them. Following are various plan categories:
  • Data Plan: This is the basic category that has an independent existence. A subscriber can be associated with single or multiple data plans.
  • Service Plan: A service plan is always associated with a data plan. A service plan cannot have an independent existence from its parent data plan.
  • Service Pack: This is a service plan that needs to be explicitly subscribed by the subscriber.

Data plan, service plan and service pack define the basic services that can be rendered by the subscriber.

Add – on is always associated with the data or service plans or packs. Add on is used to render customized services by enhancing the attributes of existing plans. Following are the add-on categories:
  • Service Add-on: Used to enable tethering.
  • Allowance Add-on: Used to increment volume or time usage.
  • Validity Add-on: Used to increment subscription validity.
This section includes following sub-sections:

View Plans

This section describes the procedures to view a specific plan or all plans.

Viewing plans involves following tasks:

Viewing a Specific Plan

This section describes the procedure to view a specific usage or data plan.

To view a specific plan:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access plan administration option.
  4. Press a to access view option.
  5. Specify the name of the plan whose details you want to view. SSC Administration Console displays the plan details such as plan id, name, type, associated volume as well as time usage limits along with validity, monitoring level and start as well as end date.

Viewing All Plans

This section describes the procedure to view all existing usage as well as data plans.

To view all plans:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access plan administration option.
  4. Press e to access view all plans option. SSC Administration Console displays a list of all existing usage as well as data plans.

Administer Plans

This section describers the procedures to administer plans.

Administering plans involves following tasks:

Adding New Plan

This section describes the procedure to add a new usage or data plan.

To add a new plan:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access plan administration option.
  4. Press b to add a new plan.
  5. Specify the name and short description for a new plan.
  6. Specify base usage limits, such as volume limit in bytes and time usage limits in seconds.
  7. Specify the validity period for this plan in days.
  8. Specify the start date for this plan in YYYY –MM- DD format and the start time in HH:MM:SS format.
  9. Specify end date and end time in same format as of start date and start time.
  10. Specify the roaming details, use values 1 for home, 2 for roaming and 3 for both.
  11. Enter quota limit type, use values 1 for hard limit and 2 for soft limit.
  12. Specify y if you want to add another threshold for this plan.

    IMPORTANT:

    While configuring a new plan, if you select the threshold category as time or any, then you need to specify absolute and percentage value for such threshold category.

  13. Specify the quota or usage type, use values 1 for volume, 2 for any and 3 for time based usage of the service.
  14. If you have selected volume as a quota or usage type then specify absolute volume.
  15. Specify y if you want to generate a notification, when the threshold mentioned in previous steps is crossed
  16. Specify whether you want to configure additional usage limits (service plans) for this plan. If you select yes, then specify the name for the usage limit (service plan).
  17. Specify the volume usage limits in bytes and time usage limits in seconds.
  18. Specify the validity period.Select value 1 for hard limit and 2 for soft limit.
  19. Specify whether you want to add additional threshold. If you select no, then specify whether you want to configure additional usage limits (service plans). Once you have configured all the data plans and corresponding usage limits (service plans), then SSC Administration Console displays the message that the plan is added successfully to the database.

Deleting Plan

This section describes the procedure to delete an existing plan.

To delete a plan:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access plan administration option.
  4. Press c to access delete plan option.
  5. SSC Administration Console displays a list of existing plans. Select the plan that you want to delete. SSC Administration Console deletes the selected plan.

Modifying Plan

This section describes the procedure to modify an existing plan.

To modify a plan:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 3 to access plan administration option.
  4. Press d to access modify plan option.
  5. Specify name of the plan that you want to modify.
  6. Specify following values as per the category of modifications that you want to perform on the existing plan.Select 1 for changing plan details, 2 for changing existing usage limits, 3 for adding new usage limits to the plan, 4 for deleting existing usage limits from the plan.
  7. If you select option 1 in previous step, then specify the description for the plan.
  8. Specify updated volume and time usage limits.
  9. Specify new validity period.
  10. Specify new start and end date as well as time.
  11. Specify the changed roaming status for the plan, the valid options are 1 for home, 2 for roaming and 3 for both.
  12. Specify changed quota limits, the valid options are 1 – for hard limit, 2 – for soft limit.
  13. Select y, if you want to change any other threshold for this plan.
  14. Specify updated quota type. Valid values are 1 for volume, 2 for any and 3 for time quota.
  15. Specify your choice for modified quota or usage and provide new absolute as well as percentage values.
  16. Specify whether you want to generate a notification when this threshold is crossed.
  17. Specify the template name, if you want to store this plan as a template.
  18. Specify whether you want to change any threshold for this plan.
  19. Specify whether you want to change volume, time or any other category of quota associated with this plan. SSC Administration Console updates the plan details in the database.

Administering Subscriptions

This section briefly describes the tasks associated with subscription maintenance.

IMPORTANT:

The subscription administration option is available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then subscription administration option can be accessed by pressing 4 otherwise it can be accessed by pressing 9 or associated option number. For more information refer User Administration section.

Subscription administration includes following tasks:

View Usage

This task describes how to view usage associated with a subscriber profile.

To view usage
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press a to view the usage associated with this subscriber profile.
  5. Specify either subscriber id or MISI or MSISDN or NAI of the subscriber whose usage you want to view.
  6. Specify whether you want to view the usage associated with a specific data plan. SSC Administration Console displays the usage values.

Associating Data Plan

This task describes how to associate a data plan.

To associate a data plan:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press b to associate data plan with this subscriber profile.
  5. Specify Plan Name that you want to associate with this subscription.
  6. Specify the subscription order, default value is 0.
  7. Specify start and end date in YYYY-MM-DD and H:M:S format. Both date and time are optional fields.
  8. Specify the opted out status for this plan. Available options are 1- Forever, 2- Enabled, 3 – Disabled, 4 – Not set, 5 – Current cycle. Following is the significance of selected opted out status:
    • Enabled: Indicates that subscriber has opted for this subscription.
    • Disabled : Indicates that either the subscriber has not subscribed for this plan or the subscription is no longer valid.
    • Current Cycle: Indicates that the subscriber has opted out of the current re-charge cycle. This status will be changed to enabled after current re-charge cycle.
    • Not Set : Indicates that the opted out status has not be set for this subscription.
    • Forever: This option is reserved for feature use, currently it indicates status as disabled.
  9. Specify whether you want to generate the notification.
  10. Specify whether you want to associate any other plans with this subscriber profile. If you select yes then SSC Administration Console repeats entire procedure and associates selected plans with the subscriber profile or displays appropriate error message.

Associating Service

This task describes how to associate a service.

To associate a service:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press c to associate a service with a subscriber profile.
  5. Specify the subscriber id or IMSI, MSIDN or NAI of the subscriber account with which you want to associate the service.
  6. Specify the name of parent plan that is associated with this profile and needs to be modified to associate a new service.
  7. Specify the name of the service that you want to associate with subscriber profile.
  8. Specify start and end date in YYYY-MM-DD and H:M:S format. Both date and time are optional fields.
  9. Specify the opted out status for this service. Available options are 1- Forever, 2- Enabled, 3 – Disabled, 4 – Not set, 5 – Current cycle.
  10. Specify whether you want to generate the notification.
  11. Specify whether you want to associate any other plans. If you select yes then SSC Administration Console repeats entire procedure and associates selected services with the subscriber profile or displays appropriate error message.

Topping-up Quota

This task describes how to top-up quota.

To top-up quota:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press d to top-up quota associated with this subscriber profile.
  5. Specify the id or IMSI or MSISDN or NAI associated with the subscriber for whom you want to top-up quota.
  6. Specify whether you want to reset the previous usage.
  7. Provide Plan Id or Plan name that you want to use to provide top-up.
  8. Specify the volume based quota in byte that you want to add.
  9. Specify the time based quota in seconds that you want to add. SSC Administration Console updates the quota for the selected subscriber profile or displays appropriate error message.

Modifying Data Plan Subscription

This task describes how-to modify plan subscription.

To modify plan subscription:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press e to modify the data plan subscription for this profile.
  5. Specify the id or IMSI or MSISDN or NAI associated with the subscriber for whom you want modify data plan.
  6. Specify the plan details such its name or id.
  7. Specify the subscription order with which this plan is associated.
  8. Specify end date in DD/MM/YYYY format.
  9. Specify whether you want to generate the notification for this change.
  10. Specify whether the grace period is applicable for this plan or not. Valid options are 1- None 2- Activation 3- Renewal.
  11. Specify whether you want to associate more plans with this profile. If you select yes option then SSC Administration Console re-executes entire procedure for another data plan, otherwise it updates the association for the selected data plan.

Modifying Service Plan Subscription

This task describes how to modify service plan subscription.

To modify service plan subscription.
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press f to modify service plan subscription for profile.
  5. Follow steps described in the previous procedure to modify the service plan that is associated with selected subscriber profile.

Resetting Usage

This task describes how to re-set usage.

To reset usage:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press g to reset the usage associated with this subscriber profile. profile.
  5. Specify the id or IMSI or MSISDN or NAI associated with the subscriber whose usage you want to reset.
  6. Specify the plan details such its name or id. For which you want to reset the usage.

    IMPORTANT:

    For data plan provided plan name or Id, for the service plan provide name or id of the parent plan.

  7. Specify new volume usage in bytes.
  8. Specify updated volume balance.
  9. Specify new time usage in seconds.
  10. Specify updated time balance. SSC Administration Console either resets the usage or displays appropriate error message.

Recharging Plan

This task describes how to re-charge a plan.

To recharge a plan:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press i to recharge the plan associated with this profile.
  5. Specify subscriber id or IMSI or MSISDN or NAI of the subscriber for whom you want to recharge the plan.
  6. Specify the id and name of the plan that you want to recharge.

    IMPORTANT:

    Plan name is mandatory.

  7. Specify the name of the parent plan for the plan that you want to recharge. SSC Administration Console recharges the plan or displays appropriate error message.

Removing Data Plan Subscription

This task describes how to remove a data plan subscription.

To remove a data plan subscription:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press j to remove the data plan subscription associated with this profile.
  5. Specify subscriber id or IMSI or MSISDN or NAI of the subscriber for whom you want to recharge the plan.
  6. Specify the name of data plan that you want to disassociate from the subscriber profile. SSC Administration Console disassociated the plan from subscriber profile or displays appropriate error message.

Removing Service Subscription

This task describes how to remove a service subscription.

To remove a service subscription:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press k to remove service subscription associated with this profile.
  5. Specify subscriber id or IMSI or MSISDN or NAI of the subscriber for whom you want disassociate the service from their profile.
  6. Specify the name of the service that you want to disassociate from the subscriber profile.
  7. Specify name of the parent plan that was used to associate this service with subscriber profile. SSC Administration Console disassociates the service from subscriber profile or displays appropriate error message.

Renewing Data Plan Subscription

This task describes how to renew a data plan subscription.

To renew data plan subscription:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press l to renew the data plan subscription associated with this profile.
  5. Specify subscriber id or IMSI or MSISDN or NAI of the subscriber for whom you want renew the subscription to data plan.
  6. Specify the name of the data plan for which you want to renew the subscription. SSC Administration Console either renews the subscription to the specified data plan or displays appropriate error message.

Renewing Service Plan Subscription

This task describes how to renew a service plan subscription.

To renew service plan subscription:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press K to renew the data plan subscription associated with this profile.
  5. Specify subscriber id or IMSI or MSISDN or NAI of the subscriber for whom you want renew the subscription to the service plan.
  6. Specify the name of the service plan for which you want to renew the subscription. SSC Administration Console either renews the subscription to the specified data plan or displays appropriate error message.

Validity Add-on Data Plan

This task describes how to validate add-on data plan.

To validate add-on data plan:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press n to access validity add-on data plan option.
  5. Specify subscriber id or IMSI or MSISDN or NAI of the subscriber with whom you want to associate the validity add-on data plan.
  6. Specify the name of the data plan for which you want to add-on the validity.
  7. Specify the validity extension on seconds. SSC Administration Console increases the validity period or displays appropriate error message.

Validly Add-on Service

This task describes how to validate add-on service.

To validate add-on service:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 4 to access subscription administration option.
  4. Press o to access validity add-on service plan option.
  5. Specify subscriber id or IMSI or MSISDN or NAI of the subscriber with whom you want to associate the validity add-on data plan.
  6. Specify the name of the service plan for which you want to add-on the validity.
  7. Specify the name of parent plan with which this service plan is associated.
  8. Specify the validity extension on seconds. SSC Administration Console increases the validity period or displays appropriate error message

Administering Data Store

This section describes the procedures to administer the subscriber data store.

IMPORTANT:

The data store administration option is available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then data store administration option can be accessed by pressing 5 otherwise it can be accessed by pressing 9 or associated option number. For more information refer User Administration section.

This section includes following sub-sections:

In a Policy Charging and Control (PCC) solution SSC acts as a data store for Subscriber Profile Registry (SPR). As per your PCC implementation and the services that are being offered, SSC stores following information in a database:
  • Subscriber Tire.
  • Profile Attribute.
  • Notification Template.
  • Auto provisioning Template

Administering Subscriber Tires

This section describes the procedures to administer the data related to subscriber tire.

Subscribers can be categorized into different tires such as gold, silver or bronze based on the kind of services consumed and corresponding charges paid by them. A subscription or subscriber tire can be used to provide appropriate policy as well as charging treatment to the subscriber, when they are accessing the network. Depending on the business model, it is possible to create consumer or corporate subscription tires with which appropriate service plans can be associated.

Administering subscriber tire involves following tasks:

Adding New Subscriber Tire

This section describes the procedure to add a new subscriber tire.

To add a new subscriber tire:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press a to access subscriber tire option.
  5. Press N to add a new tire.
  6. specify tire name.
  7. Specify description for this tire. SSC Administration Console adds the subscriber tire and displays appropriate message.

Viewing All Subscriber Tires

This section describes the procedure to view all existing subscriber tires.

To view all existing subscriber tires:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press a to access subscriber tire option.
  5. Press V to view all existing subscriber tires. SSC Administration Console displays names of all available subscriber tires.

Viewing a Specific Subscriber Tire

This section describes the procedure to view details of a specific subscriber tire.

To view a specific subscriber tire:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press a to access subscriber tire option.
  5. Press w to view a specific subscriber tire.
  6. Specify the name of subscriber tire, whose details you want to view. SSC Administration Console displays tire id, its name and description.

Deleting Specific Subscriber Tire

This section describes the procedure to delete a specific subscriber tire.

To delete a subscriber tire:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press a to access subscriber tire option.
  5. Press l to access delete a subscriber tire option.
  6. Specify the name of subscriber tire, that you want to delete. SSC Administration Console deletes the subscriber tire and displays appropriate message.

Administering Profile Attributes

This section describes the procedures to administer the data related to profile attributes.

Subscriber profile attributes can be configured using SSC data store. Depending on the business model and available subscriber data, various attributes can be configured for the subscriber profile. These attributes can be used by Policy Provisioning Tool (PPT) along with rules, rule bases and APN information from the PCEF to create relevant polices.

Each profile attribute has a unique name and can have multiple expected values. One of the expected value is set as default value. For example a profile attribute titled Verification can have expected values as Done, Not done and In process. The default value can be set to Not done, once verification is completed the expected value can be set to Done. Default value of the profile attribute can be modified, but it is not possible to delete any of the expected values once the profile attribute is configured.

Administering profile attributes involves following tasks:

Adding New Attribute

This section describes the procedure to add a new attribute to the subscriber profile.

To add a new attribute:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press b to access profile attribute option.
  5. Press N to add a new profile attribute.

    IMPORTANT:

    Enhanced SSC architecture supports multiples values for subscriber enrolled attributes. If your deployment supports this feature, then while creating the attribute you need to specify the type of attribute as multiple value or single value and provision it accordingly.

  6. Specify a name for this profile attribute.
  7. Specify the expected value for this attribute.
  8. Specify default value for this attribute. SSC Administration Console adds this attribute to the subscriber profile.

Viewing specific Profile Attribute

This section describes the procedure to view a specific attribute of the subscriber profile.

To view a specific profile attribute:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press b to access profile attribute option.
  5. Press V to access view option.
  6. Specify the name of subscriber profile attribute whose details you want to view. SSC Administration Console displays the attribute details such as its id, name, expected value and default value.

Viewing All Profile Attributes

This section describes the procedure to view a specific attribute of the subscriber profile.

To view all profile attributes:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press b to access profile attribute option.
  5. Press w to access view all attributes option. SSC Administration Console displays a list of all configured subscriber profile attributes.

Deleting Profile Attribute

This section describes the procedure to delete a specific attribute of the subscriber profile.

To delete a profile attribute:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press b to access profile attribute option.
  5. Press t to delete a profile attribute.
  6. specify the name of the profile attribute that you want to delete. SSC Administration Console deletes this profile attributes or displays appropriate error message.

Updating a Profile Attribute

This section describes the procedure to update a specific attribute of the subscriber profile.

To update a profile attribute:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press b to access profile attribute option.
  5. Press U to update a profile attribute.
  6. specify the name of the profile attribute that you want to modify.
  7. Specify modified expected value for this attribute, or press enter to keep the expected value un-changed.
  8. Specify the modified default value for this attribute, or press enter to keep the default value un-changed. SSC Administration Console updates the profile attribute and displays appropriate message.

Administering Notification Templates

This section describes the procedures to administer the data related to notification templates.

Notification templates are used to convey policy changes as well as status or usage related updates to the subscribers. SSC can send notifications as e-mail or SMS messages using the mail servers and SMSCs. SSC console can also be used to create and maintain notification templates.

IMPORTANT:

Refer Event Notification Management feature, from Features and Functionality section of the Overviewchapter.

Administering notification templates involves following tasks:

Adding New Notification Template

This section describes the procedure to add a new notification template.

To add new notification template:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press c to access notification template option.
  5. Press N to add a new template.
  6. specify template name.
  7. Specify event type associated with this notification template. Event type indicates occurrence of some event or status change related to the service usage of the subscriber.For example you can create an event type as say Quota80%Full, which indicates that the subscriber has utilized 80% of his or her quota.
  8. Specify the SMS message that you want to associate with this template or press enter to skip this option.

    IMPORTANT:

    Notification template can have maximum 2000 characters.

  9. Specify the e-mail message that you want to associate with this template or press enter to skip this option. SSC Administration Console adds the notification template to the database.

Viewing Notification Template

This section describes the procedure to view an existing notification template.

To view a notification template:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press c to access notification template option.
  5. Press V to view an existing notification template.
  6. Specify the name of template that you want to view. SSC Administration Console displays the template id, name, type of associated event along with SMS and e-mail message.

Viewing all Notification Templates

This section describes the procedure to view all available notification templates.

To view all notification templates:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press c to access notification template option.
  5. Press w to view all configured notification templates. SSC Administration Console displays the list of all available notification templates.

Deleting Notification Template

This section describes the procedure to delete a notification template.

To delete a notification template:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press c to access notification template option.
  5. Press t to delete an existing notification template.
  6. Specify name of the notification template that you want to delete. SSC Administration Console deletes this notification template and displays appropriate message.

Updating Notification Template

This section describes the procedure to update a notification template.

To update a notification template:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press c to access notification template option.
  5. Press U to update a notification template.
  6. Specify name of the notification template that you want to update.
  7. Specify the event type associated with this notification template. Event type indicates occurrence of some event or status change related to the service usage of the subscriber.For example you can create an event type as say Quota80%Full, which indicates that the subscriber has utilized 80% of his or her quota.
  8. Specify updated notification message that you want to send through SMS or press enter key to keep this field blank.
  9. Specify the updated notification message that you want to send through e-mail or press enter key to keep this field blank. SSC Administration Console updates the notification template and displays appropriate message.

Administering Auto provisioning Templates

This section describes the procedures to administer auto provisioning templates.

Auto provisioning template can be used to create a subscriber profile in SSC on the fly. Such scenario may arise if a subscriber is requesting for higher QoS through Online Charging System (OCS) node when their profile is not available with SSC, as SSC is still being integrated in the system. The auto provisioning template can have mandatory as well as default attributes. Mandatory attributes will have hard coded default values. These values will be over written by the user input. Hence user input is mandatory for such attributes. Optional attributes will have zero as the default value,

IMPORTANT:

Subscriber auto provisioning template can be configured using SSC administration console as well as by policy provisioning method.

Administering auto provisioning templates involves following tasks:

Creating Auto provisioning Template

This section describes the procedure to create an auto provisioning template.

To create an auto provisioning template:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press d to access auto provisioning option.
  5. Press T to access auto provisioning option.

    IMPORTANT:

    Press # to remove existing value and <enter > to keep existing default value

  6. Specify subscriber name.
  7. Specify brief description for this subscriber
  8. Specify subscription tire that is to be associated with this subscriber.
  9. Specify billing start date in DD/MM/YYYY format.
  10. Enter y or n to enable or disable SMS notification.
  11. Enter y or n to enable or disable e-mail notification.
  12. If e-mail notification is enabled then specify e-mail address.
  13. Specify whether you want to set profile attributes for this subscriber.

    IMPORTANT:

    SSC Administration Console displays the name and expected values for the profile attributes. Select appropriate value or press <enter> to ignore this profile attribute.

  14. Specify whether you want to associate a plan with this subscriber.
  15. If you select y in previous step, then specify plan details such as plan name.
  16. SSC Administration Console configures the auto provisioning template or displays appropriate error message.

Viewing Auto provisioning Template

This section describes the procedure to view an existing auto provisioning template.

To view an existing auto provisioning template:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 5 to access data store administration option.
  4. Press d to access auto provisioning option.
  5. Press v to view existing templates. SSC Administration Console displays parameters or flags of auto provisioning template such as Enable e-mail, Enable SMS, Notification preference and Subscription Order along with their default values.

Administering Network

This section briefly describes the administration of network entities associated with the SSC deployment.

IMPORTANT:

The Network Administration option is available only when you log in to SSC Administration Console as a policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then Network Administration option can be accessed by pressing 6 or associated option number. For more information refer User Administration section.

Subscribers can access network services from their home region as well as when they are roaming out of their defined home region. SSC allows service providers to:
  • Define their network as per various geographical or network entities.
  • Create appropriate usage and monitoring policies using this network information.
  • Support white as well as black listing by applying required policies.

This section includes following sub-sections:

Area Administration

This section briefly describes area administration.

An area can be defined using following network entities:
  • Mobile Country Code (MCC).
  • Mobile Network Code (MNC).
  • Serving GRS Support Node (SGSN) using IP address and subnet mask.
  • Serving Gateway (SGW) using IP address and subnet mask.
  • Location Area Code (LAC).
  • Routing Area Code (RAC).
  • Serving Area Code (SAC).
  • Tracking Area Code (TAC).
  • Cell Identity (CI).
  • E-UTRAN Cell Identity (ECI).

The Area Administration section contains following tasks:

Viewing An Area

This task describes how to view an existing area in the network.

To view an area:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press ato access area administration option.
  5. Press V to view the configured area.
  6. Specify the Area Name. SSC Administration Console displays information regarding configured area or appropriate error message. Refer next procedure for the area details displayed by administration console.

Adding New Area

This task describes how to configure a new area in the network.

To add a new area:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press ato access area administration option.
  5. Press N to add new Area.
  6. Specify area name.
  7. Specify an integer value as Mobile Country Code (MCC).
  8. Specify an integer value as Mobile Network Code (MNC).
  9. Specify default SGSN IP in IPv4 or Ipv6 Addr/Mask format, if you want to provision SGSN for the area.
  10. Specify default Serving Gateway (S Gateway) IP in IPv4 or Ipv6 Addr/Mask format, if you want to provision SGSN for the area.
  11. Specify an integer value as default Location Area Code (LAC).
  12. Specify LAC offset or press entire to skip.
  13. Specify an integer value as Default Routing Area Code (RAC).
  14. Specify RAC offset value or press enter to skip.
  15. Specify an integer value as Serving Area Code (SAC).
  16. Specify SAC offset or press enter to skip.
  17. Specify an integer value as Tracking Area Code (TAC).
  18. Specify TAC offset value or press enter to skip.
  19. Specify an integer value as Cell Identity (CI).
  20. Specify CI offset value or presenter to skip.
  21. Specify an integer value as E-UTRAN Cell Identity (ECI).
  22. Specify ECI- Offset or press enter to skip. SSC Administration configures the area as per specifications or displays appropriate error message.

Deleting an Area

This task describes how to delete an existing area from the network.

To delete and existing area:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press ato access area administration option.
  5. Press D to delete a configured area.
  6. Specify name of the area that you want to delete. SSC Administration Console deletes the area or displays appropriate error message.

Viewing All Areas

This task describes how to view all the configured area in the network.

To view all existing areas:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press ato access area administration option.
  5. Press w to view all the configured areas. SSC Administration Console displays the list of configures areas along with their name and id.

Region Administration

This section briefly describes region administration.

A region can be configured using any combination of multiple network entities described in previous section. Policies can be configured for specific regions. A home region can be associated with each subscriber while creating the subscriber profile.

The Region Administration section contains following tasks:

Viewing a Region

This task describes how to view an existing region in the network.

To view a n existing region:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press bto access region administration option.
  5. Press V to view an existing region. SSC Administration Console displays the region details such as total areas in the region and the region id.

Adding a New Region

This task describes how to configure a new region in the network.

To add a new region:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press bto access region administration option.
  5. Press N to configure a new region.
  6. Specify the region name SSC Administration Console configures region or displays appropriate error message.

Deleting an Existing Region

This task describes how to delete an existing region from the network.

To delete an existing region:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press bto access region administration option.
  5. Press D to delete an existing region. SSC Administration Console deletes the region and displays appropriate message.

Editing an Existing Region

This task describes how to edit an existing region in the network.

To edit an existing region:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press E to edit an existing region.
  5. Specify the id of the region that you want to edit.
  6. Specify the edit options as 1 or 2 to add or delete an area to this region SSC Administration Console either dis-associates an area from the region or associates an area with it as per the selected option and displays appropriate message.

Viewing All Regions

This task describes hoe to view all the configured regions in the network.

To view all existing regions:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press wto view all the configured regions. SSC Administration Console displays a list containing names and ids of all the configured regions.

Region List Administration

This section briefly describes region list administration.

The Region List Administration section contains following tasks:

Viewing A Region List

This task describes how to view a region list in the network.

To view a region list:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press V to view an existing region list.

Adding a New Region List

This task describes how to configure a region list in the network.

To add a new region list:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press c to access region list administration option.
  5. Press Nto configure a new region list.
  6. Specify the name for new region list. SSC Administration Console configures the region list and displays appropriate message.

Editing a Region List

This task describes how to edit an existing region list in the network.

To edit a region list
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press c to access region list administration option.
  5. Press E to edit an existing region list.
  6. Specify the identification number of the region list that you want to edit.
  7. Specify the identification number of the region that you want to add to or remove from the list.
  8. Enter 1 for adding or 2 for deleting the region mentioned in the previous step to this region list. SSC Administration Console either completes the operation or displays appropriate error message.

Deleting a Region List

This task describes how to delete an existing region list from the network.

To delete a region list:
  1. Login to the SSC node with policy administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 6 to access network administration option.
  4. Press c to access region list administration option.
  5. Press D to delete an existing region list.

Viewing All Region Lists

This task describes hoe to view all the configured region list in the network.

To view all regions:
  1. Access the SSC Administration Console by executing the script ./sscadm.
  2. Press 6 to access network administration option.
  3. Press w to view all the configured region lists. SSC Administration Console displays a list containing names and ids of all the configured region lists.

Monitoring SSC Security Using Console

This section describes the procedures to monitor the security of SSC.

IMPORTANT:

The number to access security option from SSC Administration Console varies as per your access credentials. If you log-in with policy administrative credentials then security option can be accessed by pressing 9 otherwise it can be access by pressing 7. For more information refer User Administration section.

This section includes following sub-sections:

Changing Password

This section describes how to change the system password.

Changing Password

This section describes the procedure to change system password.

To change password:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 7 to access security option.
  4. Press a to access change password option.
  5. Specify old and new password.
  6. Confirm new password. SSC Administration Console changes the password and displays appropriate message.

Monitoring Security Using System Audit

This section describes audit records and lists procedures to use audit logs to monitor security of SSC node.

Various provisioning operations and events associated with the SSC deployment are recorded or audited. Such records are known as audit records. These records are categorized as system log, SPR log and event log. Audit records can be used for security, monitoring as well as troubleshooting purpose.

An audit record contains:
  • Audit Id A unique identifier for each record. The audit id is generated by the SSC.
  • Event Id It represents a category of event associated with the SSC deployment. For example adding a subscriber is an event associated with SSC it will have an identifier, sending a notification through SMS is another event associated with SSC so it will have a different identifier.
  • Module Id It represents the SSC module that has recorded or audited this information. For example provisioning events will be recorded by profile manager.
  • Client Context It represent the type of client associated with this event. For example, the client can be SSC Console, a SOAP or XML API used for SSC provisioning or a PPT client.
  • Subscriber Id It represents the subscriber associated with this event. For example when a subscriber is created or deleted then corresponding subscriber id will be stored in the audit record.
  • Plan Id It represents a data, service or group plan associated with the event. For example if a plan is created or recharged then corresponding plan id will be stored in audit record.
  • Audit Date It represents the date when this audit record is generated.
  • Request Data It represents the data requested by the SSC operation. It is available in XML format.
  • Response Data It represents the response received by the SSC operation. It is available in XML format.

IMPORTANT:

Audit record stores only successful transactions. Unsuccessful transactions that do not affect SSC deployment are not stored.

Depending upon your access privilege you can monitor and maintain security of the SSC instance by accessing following audit records:
  • System Audit
  • SPR Audit
  • Event Log Audit

IMPORTANT:

The SPR and Event Log audit options are available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials.

System audit records events related to configuration of:
  • Sh server and peer.
  • EN controller and manager.
  • Log demon.
  • Process log
  • Bulk statistics.
  • Bulk statistics FTP.
  • SNMP alarm.
  • RSMon.
  • Ud client and attribute.
SPR Audit records events related to creation and deletion of:
  • Subscription tire.
  • Profile attribute.
  • Subscriber profile.
  • Notification template.
  • Data plan.
  • Group account.
SPR Audit also records event related to updates to:
  • Subscriber profile.
  • Profile attribute.
  • Notification templates.
Event logs records event related to:
  • Sending an SMS to SMPP server.
  • Sending an e-mail to SMTP server.

Refer to sections SSC Logs Administration and Monitoring System Logs for more information.

System as well as SPR or event audit involves following tasks:

Viewing Logs

This section describes the procedure to view system audit logs.

To view logs:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 7 to access security option.
  4. Press b to access system audit option.
  5. Press V to access view logs option.
  6. Specify the start date and start time of the period for which you want to view the logs. In DD- MM-YYY HH:MM format.
  7. Specify the end date and end time in the format mentioned in the previous step.
  8. Select the filter that is to be used to access the SPR or event audit logs, by specifying y or n. You can select module id, event id or subscriber details as the filter. SSC Administration Console displays the logs.

Viewing Log Records

This section describes the procedure to view records of system audit log.

To view log records:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 7 to access security option.
  4. Press b to access system audit option.
  5. Press L to access view log record option.
  6. Specify the record Id of the log record that you want to view. SSC Administration Console displays the log record.

Managing Session

This section describes how to manage system sessions.

Viewing Existing Session

This section describes the procedure to view existing system session.

To view existing session:
  1. Login to the SSC node with administrative privileges.
  2. Access the SSC Administration Console by executing the script ./sscadm.
  3. Press 7 to access security option.
  4. Press c to access manage session option.
  5. Press V to view information regarding existing session. SSC Administration Console displays User Name, Role, Log on Time, time and date of Last Activity, for all the active sessions.