SDP Plugin Description

SDP5

Overview

2/1550-FAM 901 107/5 Uen L

Copyright

© Copyright Ericsson AB 2012. All rights reserved.

Disclaimer

No part of this document may be reproduced in any form without the written
permission of the copyright owner.

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

Trademark List

Ericsson is the trademark of Telefonaktiebolaget LM Ericsson. All

other trademarks mentioned in this document are the
property of their respective owners.

2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Contents

Contents

1 Introduction 1
1.1 Purpose and Scope 1
1.2 Prerequisites for the User 1

2 Plug-ins 3
2.1 Configuration 3
2.2 FSC-DataSynchronizer 4
2.3 FSC-Event 4
2.4 FSC-EventLog 4
2.5 FSC-FTPManager 5
2.6 FSC-Scheduler 6
2.7 FSC-ServerEvent 8
2.8 FSC-SMSInterface (optional) 8
2.9 FSC-SS7ManagerHD 9
2.10 FSC-SystemMonitor 10
2.11 FSC-TraceEventLog 10
2.12 FSC-TXFAlarm (Optional) 11
2.13 FSC-UssdHD 11
2.14 PSC-BlockHandler 12
2.15 PSC-CDRProcessor 13
2.16 PSC-CIPDiameter (Optional) 14
2.17 PSC-ConfigHandler 14
2.18 PSC-DCIPDiameter (Optional) 17
2.19 PSC-DdsXmlRpcIf (Optional) 18
2.20 PSC-ExternalNotification 18
2.21 PSC-LDAP 19
2.22 PSC-PPASInterface 20
2.23 PSC-Preactivation (Optional) 20
2.24 PSC-SDPInapHD 20
2.25 PSC-SogInterface 21
2.26 PSC-SubscriberHandler 23
2.27 PSC-TrafficHandler 25
2.28 PSC-UssdCallback 26

2/1550-FAM 901 107/5 Uen L | 2013-05-08

SDP Plugin Description

3 System Diagram 29

Glossary 31

Reference List 33

2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Introduction

1 Introduction

This section covers purpose and scope.

1.1 Purpose and Scope

The purpose of this document is to describe the plug-ins and tools in the
Service Data Point (SDP).

1.2 Prerequisites for the User

The person reading this document should have knowledge about FDS.

2/1550-FAM 901 107/5 Uen L | 2013-05-08 1

 SDP Plugin Description

2 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

2 Plug-ins

This section describes all plug-ins in the SDP. For information how the plug-ins
are related to each other and external interfaces see section Section 3 on
page 29.

Software modules are handled as plug-ins in the SDP system and is loaded into
a plug-in container to be executed managed by FDS (Framework for Flexible
Distributed System). A plug-in could consist of one or many components. A
component is a logical software part for performing a specific function.

For more information about FDS see Component descriptions for FDS.

• Component Description FDS Component Controller Reference [25]

• Component Description FDS Glue Reference [22]

• Component Description FDS Servers Reference [24]

• Component Description FDS Tools Reference [23]

• Component Description Servers FDSClusterController Reference [28]

• Component Description Servers FDSConfigSync Reference [26]

• Component Description Servers, FDS ExternalRequestHandler Reference

[27]

• Component Description Servers FDSFunctionCtrl Reference [29]

All plug-ins can register events in the Event plug-in and subscribes to alarms
in the SS7 stack. For more information about Events in the SDP see SDP
Event Description Reference [19]

2.1 Configuration
The configuration of a plug-in is managed by create requests. The configuration
is stored in /var/opt/fds/config/plugin/<plugin>/Config.cfg, this file is read only
and can not be changed manually. For more information about configuration
see Reference [6]

Each plug-in has a standard MO which can be used for configuring the plug-in.
See also SDP Plugin ConfigurationReference [9]

The MO's are mainly used from the SDP-GUI.

For detailed information about the MO see the configuration file

/var/opt/fds/config/cluster/MoHandler/MoHandler.cfg, this file is read only and
shall not be changed manually. For more information see Reference [20]

2/1550-FAM 901 107/5 Uen L | 2013-05-08 3

 SDP Plugin Description

2.2 FSC-DataSynchronizer
The DataSynchronizer plug-in is used to automatically synchronize
configuration between SDP nodes.

2.2.1 Functionality
The DataSynchronizer plug-in manages most part of the configuration
synchronization, for more information see Reference [18]. The recommended
setup is to let one cluster, the primary cluster, synchronize its data to all other
clusters, the secondary clusters, and thereby ensuring that all clusters have the
same configuration. A secondary cluster will be an exact copy of the primary
cluster with respect to the data that is synchronized between the clusters. Any
changes made to a secondary cluster will be detected and overwritten by the
primary cluster.

The DataSynchronizer GUI is used to view and change the configuration that is
to be synchronized to other SDP nodes.

Currently, the DataSynchronizer can be used to synchronize ERE tree

structures between nodes.

2.3 FSC-Event
The Event plug-in handles the basic event generation and is the receiver of all
generated events in the node.

2.3.1 Functionality
The Event plug-in is the receiver of all generated events in the node. plug-ins
that generate events must therefore register an event sender with this plug-in.

Event also allows plug-ins (event subscribers) that are interested in events to
register. When the events are generated they are propagated to the interested
plug-ins. Three possibilities are provided for subscriptions: ordinary, inverted
and everything.

This plug-in provides a CORBA interface for event registration.

The plug-in also provides tracing functionality with events.

2.4 FSC-EventLog
The EventLog plug-in is used for maintaining a log of events that occur in the
system and query for lines and deletion of lines in the log file. The plug-in
subscribers to normal non-trace events from the Event plug-in.

4 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

2.4.1 Functionality
The purpose of the EventLog plug-in is to keep track of (subscribed) events
that occur in the system and store them in a log file. The plug-in also allows
some queries on this log file.

The plug-in supports additional operations for the plug-in MO which is named
EventLogFile.txt.0. There are two operations that can be used for handling the
log file:

• getLog

Used to retrieve ordinary system events

• Delete

Used to delete a specified fraction or all entries of the actual log file.

Location and name of log file is set in the create request of plug-in. Default
location and name are: /var/opt/fds/logs/EventLogFile.txt.0.

The log file can be accessed through the GUI in the Event Log window

2.5 FSC-FTPManager
The FTPManager plug-in transfer files from the server to other destinations in
the network.

2.5.1 Functionality
The responsibility of the FTPManager plug-in is to manage all the FTP file
transfer operations originated from one server.

The plug-in works in “push” mode, it runs on the server that needs to transfer
the files connecting to the server that will receive the files (it implements the
“put” function of the FTP). When a file transfer fails the first time a event is
generated and a waiting period is used before the file is transferred again, when
the file is finally successfully transferred; another event is generated.

The plug-in's MO interface supports the following operations for handling

connections:

• Start

Starts file transfer on connection(s) for a server.

• Stop

Stops file transfer on connection(s) for a server.

• AddConnection

2/1550-FAM 901 107/5 Uen L | 2013-05-08 5

 SDP Plugin Description

Adds a connection to a plug-in on a specific server.

• Set

Updates data in a connection for a plug-in on a server.

• DeleteConnection

Removes connection(s) for a plug-in on a server.

• GetConnection

Retrieves data for all connections on a server.

The above operations only affects one plug-in on a specific server.

2.6 FSC-Scheduler
Handles the execution of batch jobs at specific intervals and times. The
jobs annotated below with “(SH)” have their evaluation performed in the
SubscriberHandler plug-in after target MSISDNs have been selected in this
plug-in from the database. Requests, one for each MSISDN, are sent to the
SubscriberHandler by use of a CORBA interface.

2.6.1 Functionality
Scheduled jobs currently exists for the following tasks:

• Life cycle change (Database scanning)

Updates supervision, service fee, credit clearance and account disconnect

status and updates the blocks status for the subscriber. When starting up
this job performs pending scheduled service class changes. (SH)

• Service fee deduction (Database scanning)

Performs standard service fee deduction evaluation on all accounts. (SH)

• Flexible service fee deduction (Database scanning)

Performs flexible service fee deduction evaluation on all accounts. (SH)

• Value voucher expiry (Database scanning)

Checks for expiry on temporary service classes on accounts and changes

back to standard service class when the temporary service class has
expired. (SH)

• Negative balance barring (Database scanning)

6 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

Checks for accounts that have gone past the negative balance barring
grace period and performs barring on accounts that has done so.

• Dedicated account clearance (Database scanning)

Checks for expired dedicated accounts. If a dedicated account is expired it

can either be cleared with expiry date set to no expiry and cleared balance,
or be removed entirely. (SH)

• Periodic adjustment (Database scanning)

Performs periodic adjustment evaluation on all accounts.

• Periodic account management (Database scanning)

Triggers periodic account management evaluation on all accounts. (SH)

• File processor (Database scanning, File batch)

Looks for batch files to process in a specified directory and processes the
batch files. The evaluation of the operations in the batch is performed in
SubscriberHandler. Requests are sent to the SubscriberHandler by use
of a CORBA interface. For details on the protocol see Protocol Message
Specification Subscription Data Batch File Reference [7]. Some of the
operations which can be performed in the file batch requires database
scanning because many subscribers are affected by them.

• CDR file remover

This Job removes backup CDR files which has been sent using the
FTPManager.

This plug-in is only installed and run on the active server.

The plug-in supports the following MO operations for the Scheduler MO for
handling scheduling of jobs:

• JobList

Returns all defined scheduled jobs and their configuration.

• JobInformation

Returns statistics from the latest runs of a specific job. The statics include
time for starting and stopping the job and some data which is job specific.

• Start

Starts a specific scheduled job.

• Stop

Stops a specific job.

2/1550-FAM 901 107/5 Uen L | 2013-05-08 7

 SDP Plugin Description

• Set

Updates the job configuration in the plug-in for the job. The parameters
possible to set are start times, interval between consecutive runs of the
job, and if the job is active or passive. Job specific configuration cannot
be changed.

2.7 FSC-ServerEvent
The purpose of ServerEvent plug-in is to translate Framework for Flexible
Distributed System (FDS) events generated by EventLogger to FSC events.

2.7.1 Functionality
When the ServerEvent is started it parses files named ‘EventDefinition.cfg’
which contains the registered events for a specific FDS server. The files can
be found under /var/opt/fds/logs/events/<Directory>. Different parts of FDS
have different files.

ServerEvent plug-in is monitoring 'EventLog.0' for changes and if a change has

been made, the new event is parsed and sent to Event plug-in.

2.8 FSC-SMSInterface (optional)

Handles all functions for the SMS interface which is used for notifications.

2.8.1 Functionality

The SMS interface receives CORBA messages with notification data from other
plug-ins, queues them internally and then send the messages out to an SMSC.
Each SMSC has one dedicated CORBA address.

For each configured SMSC one bi-directional socket is opened. This socket is
used to send SMS. Control information for the protocol stack is also transmitted
using this socket. A standard socket is used for the communication. The SDP
initiates the communication for the connection and attempts to login on the
SMSC. If connection or login fails then the connection thread will be taken
down and a new connection attempt will be made later. This interface is used
to send SMS to the SMSC.

The data coding methods supported for the SMS are:

• IA5 (CCITT T.50)/ASCII (ANSI X3.4)

Data coding 1

• UCS2 (ISO/IEC 10646)

8 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

Data coding 8

The strategy used for selecting data coding is as follows:

• Data coding 8 not supported

Then data coding 1 will be used.

• All characters in the SM is supported using data coding 1.

Then data coding 1 will be used.

• If data coding 8 is supported and the SM contains characters which is not

supported in data coding 1.

Then data coding 8 will be used.

If an SM is too long then characters will be truncated from the end.

The supported protocols to the SMSC are:

• SMPP Protocol Specification v5.0, 19-Febraury-2003, SMS Forum, 2003

• SMPP Protocol Specification v3.4, version 12-Oct-1999, Issue 1.2, SMPP

Developers Forum, 1999

Not everything in the protocols are supported. The SDP only supports the
single SM operation, and does not support the operation for sending a long SM
in multiple SMs.

2.8.2 Limitations

The following configuration limitations exist:

• One SMSC can only have one IP

• There can only be one SMSC at the same IP

• Not possible to add new SMSCs to the configuration in run-time.

2.9 FSC-SS7ManagerHD
The SS7ManagerHD subscribes on alarms from the SS7 protocol stack and
deliver them as events.

2.9.1 Functionality
When the plug-in receives alarms from the SS7 stack, an event is generated
and sent to the EventServer. The SystemMonitor and EventLog plug-ins can
subscribe to the events which has been registered in the Event plug-in.

2/1550-FAM 901 107/5 Uen L | 2013-05-08 9

 SDP Plugin Description

2.10 FSC-SystemMonitor
The SystemMonitor plug-in is used to define and monitor alarms, referred to as
system functions, based on event notification from the Event plug-in.

2.10.1 Functionality
The SystemMonitor can be used separately with the SMA GUI or together with
an Operation Support System (OSS). The SMA GUI is used to view defined
system functions and also for monitoring the status of the system. If the alarms
should be sent to an OSS a converter is needed, e.g. TXFAlarm, see Section
2.12 on page 11.

2.11 FSC-TraceEventLog
The TraceEventLog plug-in is used for maintaining a log of traffic related trace
events and to query for lines and deletion of lines in the log file.

2.11.1 Functionality
Tracing with events works like for normal events but in addition a target has
to be included in the subscription request. The target is the MSISDN which is
used to trigger the sending of the event.

Trace is most commonly used to follow (trace) a call through a live system for
debug purposes.

Location and name of log file is set in the create request of plug-in. Default
location and name are: /var/opt/fds/logs/TraceEventLogFile.txt.

The log file can be accessed through the GUI in the Trace window.

The plug-in supports additional operations for the plug-in MO which is named
TraceEventLog. There following additional operations can be used for the MO:

• getTraceLog

Used to retrieve trace events from the trace event log.

• Delete

Used to delete a specified fraction or all entries of the actual log file

• AddTarget

Used to subscribe to trace events in the plug-in. Subscription is done for a

target (MSISDN) towards one or more plug-ins.

• RemoveTarget

10 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

Used to unsubscribe to trace events in the plug-in. Unsubscription is done

for one or all targets towards one or more plug-ins.

• GUIGetConfig

Used to retrieve a list of all plug-ins with their current subscriptions.

2.12 FSC-TXFAlarm (Optional)

The TXFAlarm plug-in converts different internal alarms to the TXF standard
and stores the alarms in a log file.

2.12.1 Functionality
The TXFAlarm plug-in registers a subscription of which system functions it
wishes to receive from the SystemMonitor. Upon receiving a change in a
system function from the SystemMonitor the TXFAlarm plug-in converts the
alarm into the TXF alarm format. TXF is a text interpretation to the standardized
alarm format specified by the ITU-T X.733 recommendation, see CCITT Rec.
X.733 (1992 E), Reference [1]. The alarm log is transferred to remote disk
using the FTP protocol. The log file can then be accessed and read by an OSS
which is used to monitor the status of a system.

The TXFAlarm plug-in also generates heartbeats in a configurable interval. The

heartbeat string is sent to the OSS and interpreted as a sign that the FDS
based system is up and running.

2.13 FSC-UssdHD
Handles all functions for USSD communication with the EMAP and MAP
protocols.

2.13.1 Functionality
The UssdHD plug-in supports communication using USSD dialogues for EMAP,
supporting both USSD phase 1 and 2. The plug-in also supports using USSD
dialogues with the MAP protocol. Only the operations needed for support of
USSD notifications and USSD callback are supported. USSD notifications are
not supported in EMAP USSD phase 1.

USSD notifications

The UssdHD plug-in receives notifications over a CORBA interface. It is

checked if the message can be represented with characters present in ref GSM
03.38 to UnicodeReference [8]. If this is not possible then the message will be
coded using UCS2 coding ( ISO/IEC 10646). If the message is too long to be
represented in the selected coding then it will be truncated from the end.

2/1550-FAM 901 107/5 Uen L | 2013-05-08 11

 SDP Plugin Description

Routing to the correct HLR is done by use of GT and routing in the SS7
network. If the HLR address is present in the incoming CORBA message then
the HLR address will be used as Global Title. If it is absent then the MSISDN
will be used as Global Title.

USSD callback

USSD clients for use with USSD callback are configured using run-time
configuration, see SDP Plugin Configuration Reference [9]. This interface
specifies which service codes are implemented and the CORBA address which
the request should be routed to.

Incoming USSD callback requests from the SS7 interfaces are transformed to
CORBA messages and sent to the USSDCallback plug-in.

2.14 PSC-BlockHandler
Administers when services connected to a subscriber need to be blocked or
unblocked in the HLR.

2.14.1 Functionality
BlockHandler uses a CORBA interface to SogInterface to determine if
SogInterface is ready to receive a batch of block requests. While the
SogInterface is not ready then the BlockHandler does not query the database.

When SogInterface is ready to receive the BlockHandler queries the database

for subscribers where the block status needs to be updated in the HLR. Found
Subscribers are evaluated for changed block status and if updates are needed
then a message is sent to the SogInterface. This message is sent using glue
and contains a batch of subscribers. The number of subscribers in a batch
(work sequence) is configurable in the create request.

If block evaluation indicates that no update is needed, then the indication for
block status change needed is cleared for the subscriber, and the wanted block
status is also updated.

SogInterface updates the HLR and sends back a reply containing the
updated block status. When receiving the reply the BlockHandler updates
the database with the actual block status for the subscriber. If the updated
subscriber is 'account disconnected' then a CORBA messages is sent to the
SubscriberHandler to initiate deletion of the subscriber.

For a subscriber with a number plan change active, then the BlockHandler will
initiate update of blocking status for both the old and the new MSISDN. The
update is considered successful if at least one of the MSISDN was successfully
updated. This is done because there is no way of knowing which MSISDN is
currently configured in the HLR.

12 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

The blocking thread is only run in the active plug-in. If the plug-in becomes
passive the blocking thread is stopped.

The following special operations are supported by the BlockHandler MO

• EvaluateDBStatus

Runs the blocking thread even if the SogInterface is not ready to receive
requests,

• EvaluateLogic

Supports evaluation of wanted block status for a specified MSISDN.

2.15 PSC-CDRProcessor
Extracts information from received CDRs and triggers the charging operation
by sending a message to the traffic handler plug-in.

2.15.1 Functionality
The CDRProcessor plug-in parses the CDR files in the input directory,
transforms them to TrafficInterface CORBA messages and sends them to the
TrafficHandler. The Input file format is specified in Detail Record Parameter
List Input SDP - CDR Reference [16]

The received responses are used to build two output CDR files (See :

• Successfully charged CDR results

File containing successful charging operations, this file is used regardless

of how much could be charged of the subscriber. Successful response
code is used if the charge was deducted in full, partially or not at all. These
CDRs are coded using Detail Record Parameter List Data Record Output
SDP v4.7 Reference [15]

• Rejected CDR result

File containing CDRs that have not been charged, because the MSISDN
was not found in the SDP. This file contains copies of the rejected
input CDRs according to Detail Record Parameter List Input SDP -
CDRReference [16].

The CDR files are connected so each input CDR file gives one or two output
CDR files as a result.

CDR data in an CDR input file is processed synchronously with the

TrafficHandler, that is the next CDR in a file is not handled until the reply to the
previous one has been received and processed.

2/1550-FAM 901 107/5 Uen L | 2013-05-08 13

 SDP Plugin Description

Load regulation for CDR processing is described in SDP System Administrator's

GuideReference [6]

2.16 PSC-CIPDiameter (Optional)

Handles incoming diameter requests and triggers the charging operation by
sending a message to the TrafficHandler plug-in.

2.16.1 Functionality

This plug-in has functions for supporting the Diameter protocol stack and
standard diameter commands. For more information see Charging Interrogation
Protocol to SDP (IP)Reference [21]

The plug-in handles incoming CIR commands and transforms them to

TrafficInterface CORBA messages and sends them to the TrafficHandler. The
received responses are transformed to CIA commands and sent out over the
Diameter protocol.

If the request takes too long to process in the TrafficHandler and times out then
CIPDiameter sends back a CIA when the time out is detected. A reply from the
TrafficInterface which comes in after the time out has occurred will be discarded.

CIPDiameter has support for duplication detection over Diameter. This feature
implies storing data for sent replies and use them later if a duplicate command
is received over diameter.

Load regulation for CIPDiameter is described in SDP System Administrator's

GuideReference [6]

2.17 PSC-ConfigHandler
Handles all non traffic or subscriber related configuration tasks. A main task is
configuration of all MO's related to ERE tree structures and SDP configuration
data

It provides data notifications for some configuration changes like changes to

service classes, DA definitions, UA definitions, Offer definitions, UC definitions,
UT definitions and PAM class. See PMS SDP Data NotificationReference
[14] for details.

2.17.1 Functionality

The ConfigHandler receives requests on the StandardServerInterface and

processes them. The incoming requests on the StandardServerInterface
include creating, deleting, updating and retrieving ERE tree structures.

14 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

The ConfigHandler implements the following MOs for handling configuration

data in the SDP:

• All ERE trees MOs

Used for configuration of all the SDP ERE tree structures.

• AccountDataManager

Used for configuration related to account data.

• AccountFinderClient

Used for configuration of the account finder client.

• Announcement

Used for configuring announcement codes for CS1+ calls.

• BCDConfig

Used in Business Configuration Distribution (BCD) for configuring

connection towards BCD server. See SDP User Guide Business
Configuration Consolidation and Distribution Reference [32]

• BCDEntityAdmin

Used in Business Configuration Distribution for configuration of the entity

distribution and reference counting. See SDP User Guide Business
Configuration Consolidation and Distribution Reference [32]

• Customization

Used for configuration of customization parameters.

• CdrFileTracker

Used for configuration of parameters for the CDR File Tracker function.

• CdrGeneratorsConfig

Used for configuration of CDR generation parameters for

SubscriberHandler, TrafficHandler and certain Scheduled jobs.

• DatabaseStatusCheck

No operations registered.

• DataNotification

Used for generating a complete data notification. See SDP

System Administrator's GuideReference [6] and PMS SDP Data
NotificationReference [14] for details.

2/1550-FAM 901 107/5 Uen L | 2013-05-08 15

 SDP Plugin Description

• DdsConfigHandler

Handles configuration for DDS.

• DedicatedAccountDefinition

Used for configuration of Dedicated Account Definition groups

Restrictions apply on changing data unit type for a DA definition.

• Diameter

Communication protocol used to/from SDP and between SDP clusters.

• DRLConfig

Handles configuration for data roaming limits.

• ExtendedStatistic

Used for configuration related to statistics.

• NumberLists

Used for configuration related to general number lists.

• OfferDefinitionDbManager

Used for configuration related to offers.

• OptionalFeatures

Used by SMA GUI. Same function as the Function MO in FDS, but

considers both license state and function control state for a licensed
function.

• PeriodicAdjustmentDefinition

Used for configuration related to periodic adjustment definition data.

• PAM.class

Used for configuration of PAM class.

• PamSnapshot

Used for configuration of PAM snapshot.

• Schedule

Used for configuration of schedules

• ServiceClass

16 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

Used for service class configuration. See SDP User Guide Service Class
Administration Reference [13] for details.

• ServiceData

Used for configuration of Service Options

• ServiceFeeDefinition

Used for Flexible Service Fee Deduction configuration.

• UCDefinitionManager

Used for configuration related to usage counter definitions.

• UsageAccumulatorDefinition

Used for configuration related to usage accumulator definition data.

• UsageCounterDataManager

Used for configuration related to usage counter data.

• UsageThresholdDataManager

Used for configuration related to usage thresholds data.

• UTDefinitionManager

Used for configuration related to usage thresholds definitions.

2.18 PSC-DCIPDiameter (Optional)

Handles DCIP requests over diameter to enable communication between SDP
clusters.

2.18.1 Functionality

This plug-in has functions for supporting the Diameter protocol stack and
standard diameter commands. For more information see Distributed Charging
Interrogation Protocol, DCIP Reference [30].

The plug-in handles incoming DCIPInterface CORBA messages from the

TrafficHandler plug-in and transforms them to a DCIP diameter request
before sent out over the Diameter protocol. On the receiving SDP-cluster,
the request will be received by the DCIPDiameter plug-in and transformed to
a DCIPInterface CORBA message before it is sent to the TrafficHandler. The
response is handled exactly in the same way..

2/1550-FAM 901 107/5 Uen L | 2013-05-08 17

 SDP Plugin Description

DCIPDiameter has support for duplication detection over Diameter. This

feature implies storing data for sent replies and use them later if a duplicate
command is received over diameter.

A request towards the AccountFinder is done from the plug-in to find out
the realm of the receiving SDP-cluster, if this data is missing. See SDP
System Administrator's GuideReference [6] for instruction how to setup the
AccountFinderClient configuration. For more information see document SDP
Implementation Instruction - DCIPReference [31].

2.19 PSC-DdsXmlRpcIf (Optional)

Enables external nodes to set up Dynamic Discounts, based on location and
time.

2.19.1 Functionality
This plug-in provides an XML RPC interface where data related to Dynamic
Discounts can be received. The protocol supported for configuring discounts is
Discount Administration Protocol Reference [10].

Received data over the protocol is used to configure temporary and default
discounts in the SDP. The plug-in uses internal MO requests to configure the
SDP with data received over the XML RPC interface.

2.20 PSC-ExternalNotification
Handles the threshold notification and the life cycle notification protocols.

2.20.1 Functionality
Balance notifications

The plug-in receives balance notifications from other plug-ins. The notifications
can arrive either in glue messages or in CORBA messages. The incoming
messages are converted to CSV lines according to the protocol, see Protocol
Message Specification Threshold Notification Protocol Reference [5]

The active plug-in replicates balance notifications to the passive

ExternalNotification plug-in. This replication is currently performed using glue
messages. A special notification containing a stop marker indicates to the
passive side that a file has been processed and that it can be discarded.

The plug-in supports generating files for several destinations with threshold
notifications. The files are moved to their final destinations by use of the
FTPManager. The contents of these files are all identical.

18 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

Time between file generation can be set down to 5 seconds.

Lifecycle notifications

The plug-in receives life cycle notifications from other plug-ins. The notifications
can arrive either in glue messages or in CORBA messages. The incoming
messages are converted and stored in a file directory. The SogInterface polls
this directory for new files and sends the notifications to the correct destination.
Each destination has a specific directory for storing files.

The plug-in replicates life cycle notifications between the plug-ins. This
replication is currently performed using glue messages. A special notification
containing a stop marker indicates to the passive side that a file has been
processed and that it can be discarded.

Most lifecycle notifications are sent to all subscribers on an account because

the changed data is on account level. When such a notification is received one
entry for each subscriber is created in the generated file.

If the destination is temporary blocked (new life cycle notifications are stored but
they are not sent out), then ExternalNotification will generate one file per hour.

Time between file generation can be set down to 1 second.

Working files

The ExternalNotification uses file extensions internally to determine its purpose.

The following file extensions are used

• active

Working file in a plug-in with active state

• passive

Working file in a plug-in with passive state

• No extension

File is ready.

2.21 PSC-LDAP
Handles the server part for communication over the LDAP protocol.

2.21.1 Functionality
The LDAP server is used for answering LDAP client requests from other
SDPs. The LDAP server implements part of the back-end interface defined
by the LDAP server within the OpenLDAP software, seeOpenLDAP software

2/1550-FAM 901 107/5 Uen L | 2013-05-08 19

 SDP Plugin Description

Reference [2]. The OpenLDAP software is used as the LDAP protocol server
and the LDAP server is loaded as a back-end to the LDAP protocol server.

The plug-in implements community charging functions using the LDAP protocol,
by retrieving community entities for the non-charged subscriber.

2.22 PSC-PPASInterface
Handles the RPC interface and forwards request to the SubscriberHandler
plug-in.

2.22.1 Functionality

RPC interface

The interface towards the PPASInterface is based on the RPC protocol.

Messages are linked lists of character strings. Each character string is a
name-value-pair. Name-value-pairs are used both in incoming requests and
outgoing responses. Currently this plug-in accepts messages using Protocol
Message Specification SDP Account Management Protocol (RPC) Protocol
Reference [3]. The PPASInterface performs validity checks on the parameters
in incoming messages and validates that parameters received are according
to the protocol specification.

SubscriberHandlerInterface

From an incoming message over RPC protocol the PPASInterface builds up

a CORBA message (using the SubscriberHandlerInterface) and sends the
message to the SubscriberHandler. From the reply from the SubscriberHandler,
a reply is composed and sent out as an outgoing reply over the RPC protocol.

2.23 PSC-Preactivation (Optional)

Performs traffical preactivation of accounts on request from the TrafficHandler
plug-in. Counts the number of active subscribers in the SDP.

2.23.1 Functionality

It needs to be present during the upgrade and until the traffic to it has been
redirected by setting the appropriate function control parameters.

2.24 PSC-SDPInapHD
Handles INAP CS1+ and triggers the charging operation by sending a message
to the traffic handler plug-in.

20 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

2.24.1 Functionality
The InapHD plug-in supports communication using the SS7 standard for the
INAP CS1+ protocol. The Retrieve and Update operations are supported.
Parameters related to the SS7 stack are configured using standard MO
operation in the plug-in, see SDP Plugin Configuration Reference [9] for details.
The supported SS7 protocol operations are described in Protocol Message
Specification Charging Interrogation Protocol to SDPReference [11]

Load regulation for SDPInapHD is described in SDP System Administrator's

GuideReference [6]

Retrieve operation

The InapHD plug-in receives incoming SS7 dialogues with the retrieve
operation. The incoming data is unpacked and put into a CORBA message and
sent to the TrafficHandler. When the reply is received it is packed into a retrieve
result structure and sent out over the SS7 interface.

Dialogues are time supervised and the dialogue is taken down when it times
out. If a reply is received when the dialogue has timed out, then the reply will
be discarded.

Update operation

Messages are received over CORBA from USSDCallback. The CORBA

message is packed into an update operation and sent out over the SS7
interface. When the Update result operation is received, then it is forwarded in
a CORBA message to USSDCallback.

2.25 PSC-SogInterface
Handles the MML/CAI interface for the HLR/EMA Blocking function. Handles
the MML interface for Life cycle notification function.

2.25.1 Functionality

Blocking Function

The SogInterface supports blocking in several different HLR/EMA, see Interface

Description Service Control Reference [12]. Each node which is to receive
commands is configured as a connection. Differentiation between which
connection shall be used is either MSISDN number series or service class.
Differentiation method cannot be mixed between different connections. It is
also possible to configure a default connection which receives all blocking
commands which does not match the number series / service class of any
other connection. Configuration of connections is done in the create request
and is not changeable in runtime. A mixed environment with HLR and EMA
is supported.

2/1550-FAM 901 107/5 Uen L | 2013-05-08 21

 SDP Plugin Description

The plug-in implements a CORBA interface which indicates if the SDP is ready
to receive new work sequences for blocking subscribers. The ready to receive
interface will return false and stop all blocking commands when any of the
connections to HLR/EMA are not working.

Work sequences with batches of subscribers to block / unblock are received

from BlockHandler using a glue interface. Block messages are stored in an
internal queue, one for each HLR/EMA destination. The SogInterface attempts
to apply blocking to the parameters indicated in the messages and indicates
back in the reply to BlockHandler which blocking statuses have been changed.

Blocking commands can be processed in several threads. How many threads

which shall be used can be set per connection. Since many receiving nodes
can not handle many simultaneous connection requests from the SDP, there is
a function in place which limits how fast new connections can be made. The
limit is one new connection every two second for all nodes except APG40 and
one new connection every 10 seconds for APG40.

Lifecycle notification function

The SogInterface supports sending lifecycle notifications to several different

external systems through an MML interface, see Protocol Message
Specification - External Life Cycle NotificationReference [4]. Each external
system which is to receive commands is configured as a destination.
Destination are connected to one or more service classes and it is possible to
have a default destination. Configuration of destinations is done through an
MO called LifeCycleNotification which is implemented in the SogInterface. The
MO supports adding, deleting and updating destinations in run-time. It is also
possible to only buffer data (creating files but without sending commands ) and
to start/stop (affects both buffering in files and command sending) destinations
by updating the configuration data in the destination. The connection data also
includes a second IP which can be used for failover if the primary IP becomes
unavailable.

Commands to send are received in files. The files are created by the
ExternalNotification plug-in. The SogInterface completes the commands with a
transaction id and sends them to the external system.

The SogInterface keeps track of which command was the latest processed
by using bookmark files which is updated every time a successful answer or
permanent failure to a command is received. The SogInterface also keeps track
of a transaction id file in the same way. If the command goes down and then
up again, these files are used to resume command sending where it left off.
The files and bookmark files are removed by the SogInterface when they are
processed. The SogInterface also keeps track of the latest used transaction
id by storing it in a file and updating it every time a successful answer or
permanent failure is received. Both bookmark file and transaction id files are
kept on a per destination basis.

Commands are processed synchronously which means that there is always

only one thread processing commands for any destination.

22 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

HLR / EMA / External System interface

Balance notifications and lifecycle notifications are handled in the same way
when sent over the socket.

When sending a command, there can either be problem with the communication
in which case SogInterface keeps track of failed connection attempts. This is
used to perform failover for a life cycle notification destination.

If an answer is received on the socket then the action taken by the SogInterface
can be one of the following

• Successful, the response indicated successful execution

• Try again, the command was not successful but should be tried again.
Error codes that indicates a temporary error on the server side should use
this option.

• Permanent failure, the command was not successful and error code
indicates that it never will be. To this category belongs messages that
indicate that the MSISDN does not exist.

• Not logged in, when using CAI interface user sessions can time out and
result in this type of responses. The SogInterface will restart the connection
and log in again when these error codes are received.

For blocking function there are default answer responses and they are also
configurable in the create request. Each connection can have its own answer
responses.

For life cycle notification function there are only default answer responses.

2.26 PSC-SubscriberHandler
Administers the database ordered from Scheduler, SMA GUI or PPASinterface.

2.26.1 Functionality
The SubscriberHandler receives requests on the SubscriberHandlerInterface
and processes them. The incoming requests on the SubscriberHandlerInterface
include creating, deleting, updating and retrieving data for subscribers.

Updates of subscribers are reported in CDRs using Detail Record Parameter

List Data Record Output SDP v4.7 Reference [15]

The CDR File Tracker also executes, if active license exists, within the
SubscriberHandler container. The CdrFileTracker adds a control block to each
send CDR file. The same block is also written to a file log stored in the SDP. A
copy of each sent CDR file is archived in the SDP. The CDR receiver builds
its own file log from the control block in each received CDR file which can

2/1550-FAM 901 107/5 Uen L | 2013-05-08 23

 SDP Plugin Description

be compared to the file log generated in SDP. If the SDP and client file logs
differ this may indicate that a CDR file is missing and can then be retrieved
from the SDP archive.

The SubscriberHandler implements the following MOs for handling configuration

data in the SDP:

• ReservationAwareHandling

Used for setting if reservation aware handling should be used for

administrative actions on subscribers.

• CurrencyControlFunctionHandling

Used for configuration related to currency.

• DataRecordFunctionAdmin

Used for configuration related to version information in data records.

• CdrFileTrackerListener

Used for listening for updated configuration of the CDR File Tracker
function.

• CdrGeneratorsConfig

Implemented in PSC-ConfigHandler.

• UserNotificationHandling

Used for user notification configuration.

• ExternalNotificationHandling

Used for configuration of external notifications.

• MaxDebtManager

Used for configuration related to max dept.

• DRLConfigListener

Used for listening for new configuration of data roaming limits.

• DatabaseStatusCheck

No operations registered.

24 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

2.27 PSC-TrafficHandler
Executes all service and rating functions ordered from the charging interfaces;
SDPInapHD, CIPDiameter, DCIPDiameter and CDRProcessor.

2.27.1 Functionality
The TrafficHandler receives requests on the TrafficInterface and processes
them. The incoming requests on the TrafficInterface includes rating of services
from different charging interfaces. The request may then be sent to the
DCIPInterface if the processing shows that it is necessary e.g. the provider is
located on a different SDP.

Updates of subscribers are reported in CDRs using Detail Record Parameter

List Data Record Output SDP v4.7 Reference [15] or using Detail Record
Parameter List Credit Control Record Reference [17]. When the latter protocol
is used the TrafficHandler generates the binary data for the CDR which is sent
out over the Diameter protocol. The CDR file is generated by CCN.

The TrafficHandler implements the following MOs for handling configuration

data in the SDP:

• Categorization

Used for configuration of categorization parameters.

• CustomizationDataListener

Used for listening for new configuration of customization parameters.

• DatabaseStatusCheck

No operations registered.

• DRLConfigListener

Used for listening for new configuration of data roaming limits.

• LDAPClient

Used for configuration of LDAPClient parameters.

• ReplicationCheck

Used by other plugins to verify that replication works on this plugin

• ReservationHandling

Used to set configuration related to reservations.

• ServiceConfig

2/1550-FAM 901 107/5 Uen L | 2013-05-08 25

 SDP Plugin Description

Used for configuration of services.

• UserNotificationHandling

Used for user notification configuration

• Statistic

Used for configuration of statistics.

• CdrGeneratorsConfig

Implemented in PSC-ConfigHandler.

• ExternalNotificationHandling

Used for configuration of external notifications.

• CurrencyControlFunctionHandling

Used for configuration related to currency.

• DuplicationDetection

Used for configuration related to duplication detection.

• NumberNormalization

Used for configuration related to normalization of different phone number

formats.

• MaxDebtManager

Used for configuration related to max dept..

• ExtendedStatisticListener

Used for listening for new configuration of extended statistics.

• DataRecordFunctionAdmin

Used for configuration related to version information in data records.

2.28 PSC-UssdCallback
Handles the USSD call back functions.

2.28.1 Functionality
This plug-in is used to allow originating international call by use of USSD
callback. The plug-in receives a CORBA message from UssdHD transforms it

26 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Plug-ins

and send it to InapHD using another CORBA message. InapHD will then send
data over the INAP CS1+ protocol to initiate a roaming callback call over CS1+.

When transforming the message the UssdCallback plug-in can optionally

perform number normalization adjustments and account finder lookup on the
calling subscriber. This analysis is performed when USSD Mappings between
SDP ID and IP addresses has been configured in the SDP.

2/1550-FAM 901 107/5 Uen L | 2013-05-08 27

 SDP Plugin Description

28 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 System Diagram

3 System Diagram

This section describes how all plug-ins are related to each other and external
interfaces. See all functional SDP plug-ins in Figure 1 and all alarm and event
plug-ins in Figure 2.

RPC

PSC-PPAS
Interface Data
Batch File Notification (4)

CDR Output (1)

Statistics Counters (2) FSC-FTP PSC-Subscriber PSC-Admin PSC-Config
Threshold Notification (3) Manager Handler (1) Account Handler
Data Notification (4)
GUI

MML/CAI FSC-Scheduler
PSC-SOG PSC-Block
(1)
Interface Handler
Threshold
Notification (3) PSC-External LDAP/DNS DB PSC-LDAP
Notification Statistic Counters (2) LDAP

SMS FSC-SMS PSC-Traffic XMLRPC

PSC-DdsXml
Interface Handler (1) RpcIf

EMAP/MAP
FSC-UssdHD PSC-CDR CDR Input
Processor (1)

PSC-Ussd PSC-SDP PSC-DCIP PSC-CIP FSC-Data

DNS Synchronizer
Callback InapHD Diameter Diameter

SelectionTree
CIP/IP
INAP CS1+ DNS Distribution

Figure 1 Functional plug-ins

2/1550-FAM 901 107/5 Uen L | 2013-05-08 29

 SDP Plugin Description

Events from Events from Events from

FDS platfrom all plugins SS7 stack

FSC-Server FSC-SS7
Event ManagerHD

FSC-Event

FSC-Trace FSC-Event FSC-System

EventLog Log Monitor

FSC-TXFAlarm

Trace log file Event log file

TXF Alarm
to OSS
Figure 2 Alarm and Event plug-ins

30 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Glossary

Glossary

AF FTP
Account Finder File Transfer Protocol

API GSM
Application Programming Interface Global System for Mobile Communications

CAI GUI
Customer Application Interface Graphical User Interface

CDR HLR
Charging Data Record Home Location Register

CIA HTTP/HTTPS
Charging Interrogation Answer HyperText Transfer Protocol/Secure

CIP INAP
Charging Interrogation Protocol Intelligent Network Application Part

CIR IP
Charging Interrogation Request Internet Protocol

CORBA LDAP
Common Object Request Broker Architecture Lightweight Directory Access Protocol

CS MO
Capability Set Managed Object

CSV MSISDN
Comma Separated Values Mobile Subscriber ISDN Number

DB MVNO
Database Mobile Virtual Network Operator

DDS OSS
Dynamic Discount Solution Operation Support System

EMA PAM
Ericsson Multi Activation Periodic Account Management

ERE PSC
Ericsson Rating Engine Product Specific Component

FSC RMA
Function Specific Component Rating Manager Application

FDS RPC
Framework for Flexible Distributed System Remote Procedure Call

2/1550-FAM 901 107/5 Uen L | 2013-05-08 31

 SDP Plugin Description

SDP
Service Data Point

SM
Short Message

SMA
SDP Management Application

SMS
Short Message Service

SMSC
Short Message Service Center

SS7
Signalling System Number 7

SQL
Structured Query Language

TCP
Transmission Control Protocol

TXF
TMOS Text File adaptation

USSD
Unstructured Supplementary Service Data

XML
Extensible Markup Language

32 2/1550-FAM 901 107/5 Uen L | 2013-05-08

 Reference List

Reference List

Ericsson Documents

External References

[1] CCITT Rec. X.733 (1992 E), http://www.itu.int

[2] OpenLDAP software, http://www.openldap.org

[3] Protocol Message Specification SDP Account Management Protocol

(RPC) Protocol, 3/155 19-FAY 302 03/2-1040

[4] Protocol Message Specification - External Life Cycle Notification, 1/155

19-FAY 302 14/2

[5] Protocol Message Specification Threshold Notification Protocol, 155

19-FAY 302 13/2

[6] SDP System Administrator's Guide, 1/1543-FAM 901 107/5

[7] Protocol Message Specification Subscription Data Batch File, 3/155

19-FAY 302 12/2

[8] GSM 03.38 to Unicode, http://unicode.org/Public/MAPPINGS/ETSI/GS

M0338.TXT

[9] SDP Plugin Configuration, 1/1550-FAM 901 107/5

[10] Discount Administration Protocol , 1/155 19-FAY 302 048/1

[11] Protocol Message Specification Charging Interrogation Protocol to SDP,

1/155 19-FAY 302 01/2

[12] Interface Description Service Control, 155 19-FAY 302 14/1

[13] SDP User Guide Service Class Administration, 3/1553-FAM 901 107/5

[14] PMS SDP Data Notification, 3/155 19-FAY 302 035/1

[15] Detail Record Parameter List Data Record Output SDP v4.7, 6/190
59-FAY 302 22/2

[16] Detail Record Parameter List Input SDP - CDR, 190 59-FAY 302 16/2

[17] Detail Record Parameter List Credit Control Record, 7/190 59-FAY 302
04/1

[18] SDP User Guide System Administration Tool , 5/1553-FAM 901 107/5

2/1550-FAM 901 107/5 Uen L | 2013-05-08 33

 SDP Plugin Description

[19] SDP Event Description, 2/1551-FAM 901 107/5

[20] SDP Application Configuration, 4/1531-FAM 901 107/5 Uen

[21] Charging Interrogation Protocol to SDP (IP), 155 19-FAY 302 003/1

[22] Component Description FDS Glue, 1/102 62-CNA 403 0559/2 Uen A

[23] Component Description FDS Tools, 1/102 62-CNA 403 0783/1 Uen C

[24] Component Description FDS Servers, 1/102 62-CNA 403 0784/1 Uen C

[25] Component Description FDS Component Controller, 5/102 62-CNA 403

0784/1 Uen A

[26] Component Description Servers FDSConfigSync, 3/102 62-CNA 403

0784/1 Uen C

[27] Component Description Servers, FDS ExternalRequestHandler, 7/102

62-CNA 403 0784/1 Uen C

[28] Component Description Servers FDSClusterController, 8/102 62-CNA

403 0784/1 Uen C

[29] Component Description Servers FDSFunctionCtrl, 9/102 62-CNA 403

0784/1 Uen C

[30] Distributed Charging Interrogation Protocol, DCIP, 155 19-FAY 302 056/1
Uen

[31] SDP Implementation Instruction - DCIP, 15/154 31-FAM 901 1075/5 Uen

[32] SDP User Guide Business Configuration Consolidation and Distribution,

21/1553-FAM 901 107/5 Uen

34 2/1550-FAM 901 107/5 Uen L | 2013-05-08