Configuration Model Description GBG SMSC V1 - 0

Company Confidential
Project
:
Prepaid Solution description
Customer :
ACISION
SOLUTION DESCRIPTION
FOR
PREPAID SOLUTION
Covering GBG SMSC integration
INTERNAL USE ONLY
Copyright Acision BV 2008

Table of Contents
Document version: 1.0
Page 32
Project
:
Customer :
ACISION
Page 32
Introduction.....................................................................................................................................................4
1.1
Document Scope.......................................................................................................................................4
1.2
Audience...................................................................................................................................................4
1.3
Reference Documents...............................................................................................................................4
Solution overview............................................................................................................................................5
Technical specification of the solution...........................................................................................................6

3.1
Solution requirements...............................................................................................................................6
3.2
Solution pre-requisites..............................................................................................................................6
3.3
GBG Interfaces.........................................................................................................................................6
3.4
Implementation models.............................................................................................................................7
3.5
Charging models......................................................................................................................................8
3.5.1
Debit-Credit Model...........................................................................................................................8
3.5.2
Reserve-Commit Model....................................................................................................................8
3.5.3
Enhanced Reserve-Commit Model...................................................................................................8
3.6
4
Transaction flows.....................................................................................................................................9
Solution implementation...............................................................................................................................11
4.1
Real-time billing mode: Prepaid subscribers provisioned on SMSC.....................................................11
4.2
Bulk billing mode: Prepaid subscribers NOT provisioned on SMSC.....................................................11
4.3
Roaming prepaid subscribers.................................................................................................................11
4.4
Using Rule Based Decision Logic..........................................................................................................11
4.4.1
Example of Rule Based Decision Logic.........................................................................................11
4.5
Standard configuration parameters........................................................................................................11
4.5.1
SMSC configuration.......................................................................................................................11
4.5.2
GBG SMSC connection...............................................................................................................11
4.5.3
GBG IN connection.....................................................................................................................11
4.5.4
CDR Billing Configuration.............................................................................................................11
5
Solution Tuning & Sizing..............................................................................................................................11

5.1
Troubleshooting prepaid configurations.................................................................................................11
5.1.1
Log files GBG.................................................................................................................................11
5.1.2
Log files SMSC...............................................................................................................................11
5.1.3
General logging...............................................................................................................................11
5.1.4
Tools................................................................................................................................................11
5.2
Sizing and redundancy............................................................................................................................11
Solution - Frequently Asked Questions.......................................................................................................11
Configuration examples................................................................................................................................11
7.1
Basic example of GBG configuration for SMSC....................................................................................11
7.2
Basic example of GBG configuration for Diameter................................................................................11
Project
:
Customer :
ACISION
Page 32
Version and Configuration Management

Version No.
Configuration History Sheet

Date
Details of Changes included in update
Version No.
Distribution
Date
Name
Author
Project
:
Customer :
ACISION
1
Introduction
Page 32
Project
:
Customer :
ACISION
Page 32
Document Scope
The scope of this document to provide additional details on the integration of a solution
consisting of the following components:
- SMSC V5
- GBG / Diameter
Not in the scope of this document is the integration of GBG with:
-
MMSC
OMG
PSA
Message Plus
Project
:
Customer :
ACISION
Audience
This document is intended to be used by:
- CSI engineers
- Deployment engineers
Page 32
Project
:
Customer :
ACISION
Page 32
Reference Documents
All referenced documents mentioned in the table below can be found on the
distribution server.
Documents referenced
Version Date
Title
5.2
SMSC Operator Manual
5.2
SMSC Command Reference Manual
5.2
SMSC Billing Manual
2.1
GBG Installation Manual
2.1
GBG Configuration Manual
1.6
GBG Generic Diameter Module
Configuration Manual
1.7.0
SMS Prepaid Billing Protocol Interface
Specification Version 1.7.0
2.1
GBG Technical Product Description
Release note prepaid rdbl (5.1 of 5.2??)
Release note SMSC_V05_21_043
Author
Tag
Project
:
Customer :
ACISION
2
Page 32
Solution overview
Problem description:
When a customer orders a prepaid solution from Acision, CSI and deployment engineers often have
problems with integration of the relevant products. Because the deployment engineers most of the
time have knowledge of one product only, integration takes much time and often leads to support and
performance problems once the solution is taken into production.
Solution description summary:
This solution is intended to help CSI and deployment engineers with configuration and tuning of a
prepaid solution consisting of the following products:
-
GBG V2.1
SMSC V5.2
The benefits of using this solution will be:

- faster deployment of the solution
- standardisation of the solution
-
Solution deliverables:
Solution
deliverable name
Brief description of deliverable
Owner of the
deliverable
User of the
deliverable
This document
Description of integration of SMSC, GBG

and IN for prepaid solution
CSI
Solution
integrator,
deployment
engineer
Test documentation and reports
CSI
Solution
integrator,
deployment
engineer
Project
:
Customer :
ACISION
3
Technical specification of the solution
Page 32
Project
:
Customer :
ACISION
Page 32
Solution requirements
GBG is a billing gateway which enables offloading of protocol conversions from other products. As
such it differs from PSA which also offers rating models and stores subscriber information.
The table below provides a comparison of the functionality of the GBG and PSA component
Functionality
GBG
PSA
Protocol conversion from SPBP to Diameter; several other

protocols are supported but not mentioned here. The
Diameter protocol implementation by PSA is not the same as
the one by GBG
Service rating
Transaction database
Subscriber database GBG cannot support routing based
on individual subscriber information, but can do LDAP
lookups
Credit/debit buffering (accumulation mode) is not available
on GBG.
Flexible Routing GBG supports routing on prefix and other
patterns
V
V
V
V
V
Project
:
Customer :
ACISION
Page 32
Solution pre-requisites
This document assumes that the GBG and SMSC software has been installed on the system.
This solution description is based on the following software versions:
-
GBG 2.1
SMSC V5.2
This solution description is based on the following hardware and operating systems:
GBG software runs on NGP supported Linux platforms with Red Hat Linux.
SMSC runs on Itanium or Alpha with OpenVMS.
Other hardware and operating systems are possible for GBG to run on, please contact CSI or product
management (PM) in that case.
Older versions of SMSC might be supported, please check with CSI or PM.
Project
:
Customer :
ACISION
Page 32
GBG Interfaces
GBG supports the following interfaces:
Category
Protocol
Versions
INPUT interfaces
BIP
1.0, 1.1, 2.0
SPBP
1.7.1 and previous Input interfaces

compatible versions
PSP
SAP 0x80 (OMG)

SAP 0x51 (Telepath)
Output prepaid interfaces
RTPP
1.1
Diameter Base Protocol
RFC 3588
IETF Draft 8
This document covers only SPBP and Diameter protocols.

For Diameter several solution packs have been developed which support the following IN platforms.
Only SMSC packages are mentioned here. The generic solution is now used by
solution pack name
SMSC-Diameter
SMSC-SCAP
SMSCTecnomen_DCCA_Diameter
SMSC-Comverse_Diameter
source
generic solution
pack
generic solution
pack
generic solution
pack
generic solution
pack
application
supported Diameter application
SMSC V5
Acision Diameter for SMS

Charging, v 1.0
SMSC V5
Ericsson SCAP, v. CCN 5.1
SMSC V5
Tecnomen DCCA, release

2.1
SMSC V5
Comverse Diameter
Project
:
Customer :
ACISION
Page 32
Implementation models
SMSC V5 supports two billing modes:
1. Real-time billing mode: SMS prepaid with on-board database of prepaid subscribers (option
19a) also referred to as real time. The subscribers are provisioned on SMSC.
The SMSC will only forward debit requests to the billing system where a prepaid subscriber is
the charged party. All other messages are considered to be sent by post paid subscribers
(see 4.1)
2. Bulk billing mode: SMS prepaid with external database of prepaid subscribers (option 19b)
referred to as bulk mode. The subscribers are NOT provisioned on SMSC.
All debit requests where a mobile party is the charged party are forwarded to the billing
system and based on the response of the billing system the message will be accepted or
rejected by the SMSC (see 4.2).
Bulk mode should be considered when most of the subscribers are prepaid. The drawback of the onboard database solution is that data of prepaid subscribers has to be provisioned on several
platforms, which leads to higher operational costs.
Another common configuration model is where prepaid subscribers are charged in the local network.
The prepaid solution offers the possibility to charge internationally roaming subscribers (see 4.3). It
also makes it possible to charge messages from application to mobile recipient.
When operating in Real Time mode, older versions of the SMSC provided only one way to determine
whether a prepaid transaction would be initiated for the mobile originator. This was accomplished by
checking if the MSISDN of the charged party was provisioned on the onboard prepaid database.
With rule based decision logic it is possible to use different criteria to decide whether or not a prepaid
trigger should be sent to the Prepaid System. For example: the originator IMSI can be used to
determine if a mobile originator is prepaid. This alternative has the advantage that the provisioning of
IMSI ranges is much more convenient than the provisioning of large numbers of discrete MSISDNs.
Rule based decision logic (RBDL) offers a very flexible way to configure all kinds of complicated
charging models. Besides this SMS Prepaid Real Time provisioning improvement, rule based decision
logic also offers more flexibility regarding the SMS Prepaid configuration in general - the operator can
now define his own rules for making Prepaid Charging decisions dependent on the characteristics of
the submitted message (see 4.4).
How to configure the models mentioned above will be described in the next chapter.
Project
:
Customer :
ACISION
Charging models
The SPBP protocol supports the following charging models:
Page 32
Project
:
Customer :
ACISION
1.1.1
Page 32
Debit-Credit Model
The debit-credit model is suited for true pre-service acceptance charging, when all charging
parameters are known during initiation of the service. The account of the subscriber is debited realtime before the service is applied. Since the charging is complete, there is only need for further
communication between the SMSC and the GBG when the service can not be finished successfully
and a refund is required. The latter is done via a credit operation.
Project
:
Customer :
ACISION
1.1.2
Page 32
Reserve-Commit Model
The reserve-commit model differs from the debit-credit model by always requiring a positive
confirmation (the commit) that a service was delivered successfully. When that confirmation is not
received within a certain time, it is concluded that apparently the service was not successful and the
account should be credited. In the SPBP, the debit operation can be interpreted as the reserve from
this model, while the commit is implemented via the info operation.
Project
:
Customer :
ACISION
1.1.3
Page 32
Enhanced Reserve-Commit Model
Optionally, a credit operation can be added to the reserve-commit model (or equivalently, a commit
could be added to the debit-credit model) to prevent the key role of timers in the reserve-commit
model. In the enhanced reserve-commit model the SMSC will provide the GBG with an explicit
confirmation of the outcome of the service delivery, irrespective whether it was successful or not.
A second use of this model is to be able to do post-delivery charging on the GBG using parameters
that a priori can only be obtained after service delivery such as recipient location.
In this document only the debit-credit model will be considered. Please ask first CSI or in second
instance PM for assistance if the customer is using a different charging model.
Project
:
Customer :
ACISION
Transaction flows
The following figures show the transaction flow of the most common configurations.
Transaction flow for SMS with sufficient credit
Transaction flow for SMS with insufficient credit
Page 32
Project
:
Customer :
ACISION
Transaction flow for SMS refund
Page 32
Project
:
Customer :
ACISION
4
Page 32
Solution implementation
For all models the following licenses should be enabled in SYS$SYSTEM:CMG_LICENSE.DAT

SMSC_PREPAID_SMS_ENABLED
SMSC_PP_BULK_ENABLED when the customer wants to use bulk mode.
The corresponding attributes should be enabled:
SMSC_COMMON /PREPAID_SMS_ENABLED
SMSC_COMMON /PP_SMS_BULK_ENABLED when the customer wants to use bulk mode.
Project
:
Customer :
ACISION
Page 32
Real-time billing mode: Prepaid subscribers provisioned on SMSC

When prepaid subscribers are provisioned on the SMSC debit requests for prepaid subscribers only
are forwarded to the billing system; all other messages are considered to be sent by post paid
subscribers.
The table PP_REC in the SSD contains all prepaid users. SSD entities load these data in memory to
determine if the MSISDN belongs to a prepaid user.
The prepaid additions to the services database are installed by running the interactive script
SMSC$ROOT:[SCRIPTS]SDB_CREATE_PREPAID.COM. This script assumes that the SDB itself has
already been created and adds the prepaid table (PP_REC) to it. The operator is requested to supply
the expected total number of expected prepaid users and the table is dimensioned accordingly.
Extension of the prepaid table will be handled by the database software and will not have impact on a
running SSD.
The prepaid user table can be maintained via PRL, SOG or LIW.
Parameter settings for this model:
Parameter
Class
Value
PREPAID_SMS_ENABLED
SMSC
ON
PP_SMS_BULK_ENABLED
SMSC
OFF
PP_MODE
SMSC
REAL_TIME
MAX_PP_USERS
SSD_COMMON
Number of
prepaid users in
database + 10%
PP_OGT_LIST_TYPE
SSD_COMMON
NOT_USED
Explanation
This parameter is used to specify
whether the SMS Prepaid functionality is
enabled by the SMSC
whether SMS Prepaid bulk functionality
is enabled by the SMSC
This parameter is used to specify the
operational mode of the SMSC for
prepaid traffic
maximum number of prepaid users that
the SSD will hold in memory.
MAX_PP_USERS can be set to values in
the range of 0 to 20,000,000.
Not relevant in this model
PP_OGT_LIST_SIZE
SSD_COMMON
Not relevant in this model
If the attribute PP_OGT_LIST_TYPE is set to MATCH_ALL, all originator global titles and point codes
match the WHITE list. In that case the SMSC will always perform the prepaid checks when a prepaid
mobile is the charged party.
If the attribute PP_OGT_LIST_TYPE is set to NOT_USED, the list is not searched and the originating
network is unknown, but the OGT field will be populated in the prepaid request.
In the BULK prepaid operational mode, due to the NOT_USED value the prepaid checks are NOT
performed for the mobile prepaid subscriber.
If the attribute PP_OGT_LIST_TYPE is set to BLACK, and the global title or point code is on the list,
then there will be no prepaid request generated.
If the attribute PP_OGT_LIST_TYPE is set to WHITE and the global title or point code are on the list,
then a prepaid request will be generated.
If the LIST_TYPE is BLACK or WHITE, and the blacklist is empty, then point code will not trigger a
prepaid request, but global title will trigger a prepaid request.
Project
:
Customer :
ACISION
Page 32
NOTE: the PP_OGT_LIST can also contain prefix entries, so there can also be a match on the first
digits of the global title.
Project
:
Customer :
ACISION
Page 32
Bulk billing mode: Prepaid subscribers NOT provisioned on SMSC

In BULK mode all debit requests where a mobile subscriber is the charged party are forwarded to the
billing system and based on the response of the billing system the message will be accepted or
rejected by the SMSC.
Parameter settings for this model:
Parameter
Class
Value
PREPAID_SMS_ENABLED
SMSC
ON
PP_SMS_BULK_ENABLED
SMSC
ON
PP_MODE
SMSC
BULK
PP_OGT_LIST_TYPE
SSD_COMMON
MATCH_ALL
PP_OGT_LIST_SIZE
SSD_COMMON
Explanation
supported by the SMSC
is supported by the SMSC
prepaid traffic: REAL_TIME or BULK.
The SMSC will always perform a prepaid
check when a prepaid mobile is the
charged party, independent of global
title or point code.
Not relevant for MATCH_ALL
Project
:
Customer :
ACISION
Page 32
Roaming prepaid subscribers

A common configuration model is when all prepaid subscribers are charged in the network and only
roaming subscribers need to be charged by the billing system. This can be configured with a blacklist
or a white list of global titles. This model can be applied in BULK mode and in REAL_TIME mode.
If the SMSC Prepaid Originator GT list has been configured as a blacklist and the Global Title (GT)
address of the originator of an SM appears on the list, then the blacklisted originators are seen to be
in the home PLMN and the message has already been processed for billing in the network. No
transactions are sent to the Prepaid billing system. In this case the OGT list is populated with all
switches which belong to the network of the customer.
If the SMSC Prepaid Originator GT list has been configured as a white list and the Global Title (GT)
address of the originator of an SM does not appear on the list, then the SMSC assumes that the
message has already been processed for billing in the network, and the message is treated as FREE.
No transactions are sent to the Prepaid billing system. In this case the OGT list is populated with all
switches which do not belong to the network of the customer.
Parameter settings for BULK mode:
Parameter
Class
Value
PREPAID_SMS_ENABLED
SMSC
ON
PP_SMS_BULK_ENABLED
SMSC
ON
PP_MODE
SMSC
BULK
MAX_PP_USERS
SSD_COMMON
PP_OGT_LIST_TYPE
SSD_COMMON
BLACK or
WHITE
Explanation
In BULK mode prepaid subscribers are
not cached in memory
See explanation above
Parameter settings for REAL_TIME mode:

Parameter
Class
Value
PREPAID_SMS_ENABLED
SMSC
ON
PP_SMS_BULK_ENABLED
SMSC
OFF
PP_MODE
SMSC
REAL_TIME
MAX_PP_USERS
SSD_COMMON
Number of prepaid users in

database + 10%
PP_OGT_LIST_TYPE
SSD_COMMON
BLACK or WHITE
PP_OGT_LIST_SIZE
SSD_COMMON
Default 0
Explanation
maximum number of prepaid users that
the SSD will hold in memory.
MAX_PP_USERS can be set to values in
the range of 0 to 20,000,000.
See explanation above
maximum number of prepaid Global
Titles (GTs) that the SSD will hold in
Project
:
Customer :
ACISION
Page 32
memory
Project
:
Customer :
ACISION
Page 32
Using Rule Based Decision Logic.

All models described above can also be implemented using rule based decision logic, in which case
the characteristics of a prepaid user are captured in rules.
Parameter
Class
Value
MSG_RULES_ENABLED
SMSC
ON
MSG_RULES_PP_ENABLED
SSD_COMMON
ON
MAX_MSG_RULES
SSD_COMMON
0 - 512
MAX_MSG_RULE_SETS
SSD_COMMON
0 - 20
RECIPIENT_ADDR_RANGE_R
SMSC
OFF
Explanation
This qualifier is used to specify whether the Rule
Based Decision Logic functionality is supported by
the SMSC. When set to ON, the SMSC expects a
decision rule configuration in the
SSD_MSG_RULES.CNF file. MSG_RULES_ENABLED
can be set to OFF or ON.
This attribute can only be set if all the SSD entities
are stopped. The value ON is allowed when the
SMSC_COMMON attribute
/RECIPIENT_ADDR_RANGE_R is set to OFF.
This qualifier is used to specify whether the Rule
Based Decision Logic functionality supports Prepaid
rulesets. When set to ON, the SMSC expects the
operator to define Prepaid rulesets for making
prepaid charging decisions. When set to OFF, the
SMSC will not accept a Rule Based Decision Logic
configuration containing Prepaid rulesets.
This attribute can only be set when all SSD entities
are stopped.
This qualifier is used to specify the maximum
number of rules that can be stored in memory. If
not all configured rules fit in memory, the rule
based decision functionality is disabled.
MAX_MSG_RULES can be set to values in the range
of 0 to 512
This attribute can only be modified when all SSD
entities are stopped.
This qualifier specifies the maximum number of
decision rule sets that can be stored in memory. If
not all configured rule sets fit in memory, the rule
based decision functionality is disabled.
MAX_MSG_RULE_SETS can be set to values in the
range from 0 to 20.
This attribute can only be modified when all SSD
entities are stopped.
See explanation below
This feature cannot be enabled when the Recipient Address Range Routing (RARR) is enabled
system-wide, i.e. when the SMSC_COMMON /RECIPIENT_ADDR_RANGE_R attribute is set to ON.
However, within the RBDL functionality, the provisioned RARR ranges can still be checked for routing
to an LA or catchall message gateway when the APPLY_RARR action is executed for a matching rule.
Rules need to be configured in the file SMSC$ROOT:[DATA]SSD_MSG_RULES.CNF
Project
:
Customer :
ACISION
1.1.4
Page 32
Example of Rule Based Decision Logic.
This example shows the use of IMSI ranges and Originating Global Title to forward prepaid requests
for roaming prepaid subscribers only. In order to decide on the SMSC whether a charging is
necessary, the following rules are applied:
Rule 1: VLR (OGTI address) If the OGTI (Originating Global Title) is not MSC prefix 0039 (national
roaming can be authorized in the network) then the SMS is submitted by an international roaming
subscriber.
Rule 2: IMSI If 6th digit of the IMSI equals 1, 2, 3 or 4 then this subscriber is a prepaid subscriber.
Rules 1 and 2 can be applied in sequence, which means the non-roaming traffic is filtered out before
the prepaid rule is applied, and only the prepaid traffic is treated by GBG-CCN on-line billing.
SSD_MSG_RULES.CNF content:
Rule_set Roaming_Prepaid
{
Rule rw1
Order 1
Conditions A_GT not in 3,
A_IMSI in 4
Actions PP_SET_A_PP, PP_CHARGE_A
}
Rule Catchall order 30
Action APPLY_RARR
Eval_on_submission Roaming_Prepaid, Catchall
Two rules are created: One for the prepaid roaming and one for RARR. Normal RARR has to be
disabled, however it is used via RDBL like it is normally used.
SDB content:
PRL> sea ag_prefix
TON
NPI
ADDR_PREFIX
1
?
"39*"
?
6
"222881*"
?
6
"222882*"
?
6
"222883*"
?
6
"222884*"
PRL> show addr_group 3
ADDR_GROUP_ID: 3
SUBS_PROFILE_ID: 0
PRL> show addr_group 4
ADDR_GROUP_ID: 4
SUBS_PROFILE_ID: 0
ADDR_GROUP_ID
3
4
4
4
4
The OGTI prefix has been added to the address_prefix table in the SDB.
Project
:
Customer :
ACISION
Page 32
Standard configuration parameters

This section contains all configuration settings that are independent of the implementation model.
Project
:
Customer :
ACISION
1.1.5
Page 32
SMSC configuration
Parameter
Class
Value
PP_SUPPORTED_SPBP_MSGS
SMSC
PP_SUPPORTED_ADD_SER
SMSC
Explanation
This parameter is a bitmask that is used to
specify which messages of the SPBP are
supported by the SMSC. See note below
specify which additional services of the SPBP are
supported by the SMSC. See note below
NOTE: PP_SUPPORTED_SPBP_MSGS and PP_SUPPORTED_ADD_SER are important

parameters that determine how many requests will be sent to the prepaid system. When these
parameters are not configured correctly this will lead to sending unnecessary prepaid transactions to
the prepaid system, which can lead to overloading the prepaid system and loss of prepaid service.
The default setting of these parameters is to enable all possible prepaid requests, which results in
twice the normal load of prepaid requests and the default setting should always be modified.
The possible values of PP_SUPPORTED_SPBP_MSGS are credit requests, delivery messages, and
statistical triggers. Credit requests are used to refund messages, which could not be delivered.
Delivery messages are used if the subscriber is charged after the message has been delivered or can
be relevant in case of concatenated messages. Statistical triggers are used for free messages.
In most cases PP_SUPPORTED_SPBP_MSGS can be set to 1 which will result in a refund if the
messages cannot be delivered. If refunds in this case are not allowed by the operator this parameter
should be set to 0.
There are customers who need different settings for this parameter, for example if the recipient is
charged when he is roaming, or when the reserve-commit model is used. In these cases contact CSI
for assistance with configuration.
PP_SUPPORTED_ADD_SER is used to charge additional services like notifications, forwarding, last
resort addressing, provisioning, reply-path, SMS commands and forwarding to a unified mailbox.
In most cases PP_SUPPORTED_ADD_SER can be set to 0. When an additional service is supported
by the billing system the setting of this parameter should be discussed with the prepaid specialists
CSI and in second instance with PM.
The following parameters affect charging of messages. Charging of messages from mobile to
applications (MO-AT) and from application to mobile (AO-MT) is configured for each application
separately in the large account database. Large accounts are never charged.
Parameter
Class
Value
PP_JAMMED_SETTING
SMSC_COMMON
SMS_FREE
PP_MOMT_CHARGING
SMSC_COMMON
ORIGINATOR
PP_NOTIF_SETTING
SMSC_COMMON
CHARGED
PP_PB_TIMEOUT
SMH_COMMON
Explanation
This parameter is used to specify the behavior
of the SMSC when the Payment System
interface is JAMMED. This behavior can be
either: all prepaid messages are rejected or all
prepaid messages are free
This parameter is used to specify whether the
originator or the recipient is the charged party
in prepaid MO-MT traffic and whether this
Primary Service is free or not
This parameter is used to specify whether
notifications or status reports are charged,
free or ignored.
The PP_PB_TIMEOUT qualifier is used to
specify the timeout value for the Payment
System response to an earlier Primary or
Additional Service debit transaction. A value of
0 means that the SMH will wait indefinitely for
Project
:
Customer :
ACISION
Page 32
PP_PB_TIMEOUT_TICK
SMH_COMMON
USE_CACHE
PBR_COMMON
NO
CACHE_SIZE
PBR_COMMON
100
the response to arrive.

SMSC timeout (pp_pb_timeout) > GBG timeout
(msg_timeout_ms) > BS timeout
(response_timeout_ms)
The PP_PB_TIMEOUT_TICK qualifier is used to
specify how often the SMH checks whether
messages waiting for a Payment System
response have timed out.
This parameter specifies whether or not a
local cache is used when there is no active
session with the Prepaid Billing System. See
note below
Should not be used, see note below
CACHE_TO_FILE
PBR_COMMON
NO
Should not be used, see note below
HEARTBEAT_INTERVAL
PBR_COMMON
500
HEARTBEAT_TIMEOUT
PBR_COMMON
500
MAX_MISSED_HEARTBEA
TS
PBR_COMMON
MAX_CONNECTIONS
PBR_COMMON
10
MAX_REQUEUE_ATTEMPT
S
PBR_COMMON
MAX_TRANS_PER_SEC
PBR_COMMON
1000
THROUGHPUT_INTERVAL
PBR_COMMON
PP_APA_INCLUDED
PBR_COMMON
NO
PP_CM_INCLUDED
PBR_COMMON
NO
PP_EMS_INCLUDED
PBR_COMMON
NO
This qualifier is used to specify the interval

between two heartbeats the PBR transmits.
This qualifier is used to specify the timeout
value for the heartbeat that the PBR expects
to receive from the Payment System.
This qualifier is used to specify the maximum
number of missed heartbeats before the PBR
will terminate the associated SPBP session.
A value of 0 means that the PBR will never
terminate the associated session, but the
SMSC will not know if the PSA is down or
having problems. A value of 0 is NOT
recommended.
The MAX_CONNECTIONS qualifier is used to
specify the maximum number of SPBP
connections. The number of connections from
GBG to SMSC should not exceed this
parameter
The MAX_REQUEUE_ATTEMPTS qualifier is
used to specify the maximum number of
requeue attempts for an undeliverable debit
or credit record.
Each PBR entity will process a maximum of
(MAX_TRANS_PER_SEC *
THROUGHPUT_INTERVAL) transactions per
THROUGHPUT_INTERVAL seconds long
intervals.
The THROUGHPUT_INTERVAL qualifier is used
to specify the interval in which throughput
measurements are taken.
This qualifier is used to specify whether
Application Port Addressing (APA) information
is included in the billing information sent to
the Payment System.
Concatenated Message (CM) information is
included in the billing information sent to the
Payment System
Enhanced Message Service (EMS) information
is included in the billing information sent to
Project
:
Customer :
ACISION
PRES_ADDR_ENABLED
PBR_COMMON
NO
UNTR_ADDR_ENABLED
PBR_COMMON
NO
SPBP_OPT_FIELDS_MASK
PBR_COMMON
PP_ACCEPT_BLOCKED
SMH_COMMON
OFF
PP_REJECT_NO_RNI
SMH_COMMON
NO
PP_FIXED_BILLING
SMH_COMMON
ABN_ENABLED
SMH_COMMON
Page 32
the Payment System
Only to be considered when ADT is used. It is
best to set this attribute to NO. When set to
YES this attribute breaks other default
features.
Only to be considered when ADT is used. It is
best to use the default, because changing this
attribute breaks other default features.
specify which SPBP optional fields are
enabled. See explanation below.
This parameter is used to switch sending a
positive acknowledgement for the MO/SM,
when the prepaid charged party is blocked.
This attribute specifies whether or not a
message requiring prepaid charging will be
rejected in case no Recipient Number
Information data is available. See also release
note smsc_v05_21_043
See billing configuration below
This parameter specifies whether Account
Balance Notification (ABN) messages are
generated by the SMSC.
NOTE: The USE_CACHE parameter should always be set to NO, because it has a negative impact
on the performance of the SMSC. The content of the cache can be different on each of the SMSC
nodes, because a prepaid user can be registered in all caches with different values.
When CACHE_TO_FILE is enabled the negative impact on the performance of the SMSC will be
major, because this will result in the memory cache being written to disk regularly.
SPBP_OPT_FIELDS_MASK: for details see SMS Prepaid Billing Protocol Interface Specification
Version 1.7.0. Please contact CSI or PM for configuration details.
It is possible to send notifications with account balance information to the prepaid subscriber by
enabling ABN. There are several parameters that control the content of the notification sent to the
mobile, for detail see the SMSC reference manual.
Project
:
Customer :
ACISION
1.1.6
Page 32
GBG SMSC connection
In this section we will look at the configuration of one SMSC with one GBG. Adding more GBG or
SMSC nodes to the configuration is reasonably straight forward, but more complicated models with
several systems will be discussed in the section on tuning and sizing.
For customer specific implementations, GBG development team supplies a solution pack, which
includes the example of configuration files customized for the deployment.
If a solution pack is not provided, use some of the product-specific examples delivered with GBG.
GBG base pack includes examples for typical SMSC deployments.
When starting with the example file, copy the example file to target filename (e.g. gbg.ini) before
making any changes.
The connection to the prepaid system is initialised by the GBG. On the SMSC the TCP server needs
to be configured to present the prepaid service to the GBG. This is done in the TCP configuration file.
It is recommended to use a separate TCP server (and consequently a separate TCP configuration file)
for the prepaid service. This way restarting the prepaid TCP server will not affect the connection to the
applications (large accounts) and vice versa.
For most systems one PBR entity per node is configured. The section on tuning and sizing will look at
other options.
Normally there is only one port configured where the prepaid service is offered, but it is possible to
define more ports. The following lines should be added to the TCP configuration files and the number
of ports in the file (TCP_NR_PORTS) should be incremented.
PORT
SERVICE
CHANNELTYPE
<port-number>
P_PBR
SWITCHED
The information about the connection (hostname and port) needs to be configured on GBG in the
gbg.ini file.
Parameter
Value
REMOTE_ADDRESS
SMSC NODE
+ PORT
CONNECTIONS
Description
Defines the address of the SMSC. (see GBG CMAN
section 4.5.3) When several SMSCs are used there
will be an entry for each SMSC node.
The hostname can be a domain name or an IPaddress.
Number of connections established to the each
address, default 1. The number of connections
should not be larger than PBR_COMMON /
MAX_CONNECTIONS on the SMSC
The following parameters determine the (re)connection timeouts. These parameters might change
between GBG versions, so always check the GBG Configuration Manual.
MSG_TIMEOUT_MS
5000
Processing timeout value for requests. GBG must

process the request and send a response within the
set time. If the request is not completely processed
in the set time, GBG replies with response code
corresponding to the internal response code
CONGESTION.
Project
:
Customer :
ACISION
ESTABLISH_RETRIES
RECONNECT_INTERVAL_MS
5000
KEEPALIVE_INTERVAL_MS
5000
CONNECTION_IDLE_LIMIT_MS
12000
Page 32
Specifies the maximum number of timeouts

possible for SPBP "Request To Establish" prior to a
connection being closed.
Tells the SPBP module for how long it should wait (in
milliseconds) before attempting to initiate a new
connection.
Specifies the period of SPBP keep alive generator, in
milliseconds. The keep alive is generated by GBG
SPBP module when no data are sent to the remote
party (e.g. SMSC) during this period.
If there is no incoming traffic on the connection for
the given period (in milliseconds), the GBG closes
the connection.
Response Code Mapping

The response code represents the result of the charging operation on the billing system and is
propagated from the billing system back to the SMSC. GBG normalizes response codes of the
different billing systems to a limited set of internal response codes. The internal response codes maps
into appropriate response code designated for the SMSC.
Normally the response code mapping delivered with the solution pack does not need to be changed.
Please contact prepaid experts in CSI when the behavior of the IN billing system is not compatible
with the standard solution.
Example:
[SPBP]
default_route="Hub"
msg_timeout_ms=5000
coi="COI_1"
prim_billing_opcode=9001
add_billing_opcode=9002
prepaid_status=1
version=0x010701
service=2
connect_timeout_ms=2000
establish_timeout_ms=3000
establish_retries=5
reconnect_interval_ms=3000
cleanup_timeout_ms=4000
wfclose_timeout_ms=1500
ready_timeout_ms=2000
keepalive_interval_ms=3000
connection_idle_limit_ms=12000
remote_address="127.0.0.1:12201"
remote_address="spbp.example.com:12201"
connections=1
response_code=SUCCESS:0x0000
response_code=SUB_NOT_FOUND:0x0200
response_code=SUB_INSOLVENT:0x0202
response_code=0xF000
Project
:
Customer :
ACISION
1.1.7
Page 32
GBG IN connection
In this section we will look at the configuration of one GBG with one IN. Adding more nodes to the
configuration is reasonably straight forward, but more complicated models with several systems will
be discussed in the section on tuning and sizing. In real life there are more complicated scenarios with
several IN platforms, sometimes from different vendors, where it is necessary to route the request
based on subscriber specific information (IMSI or MSISDN ranges). GBG offers the possibility to
create scripts in a Pascal like language to define these routing scenarios.
The correct values for target host/port and possibly also for target realm may not be known to GBG
development. Therefore check these values in the gbg.ini and change them if necessary.
Parameter
Value
REMOTE_ADDRESS
HOSTNAME+PO
RT
REMOTE_REALM
DOMAIN NAME
SCAP_COMPATIBILITY
OFF
RESPONSE_TIMEOUT_MS
5000
Description
Host and port of the peer system with Diameter
interface. Used as destination for requests originated
by GBG. The peer system must use the same host
name as source address.
Realm name of the Diameter billing system.
Enables compatibility modes for communication with
billing systems adhering to various Diameter flavors.
Possible values are:
Standard - Compatible with Diameter standards.
Ericsson_SCAP - Compatible with [Draft8].
maximum allowed response time of billing system. If
the response is not received within the time, internal
response code of
the internal message is set to CONGESTION
See also Generic Diameter Module Configuration Manual
Project
:
Customer :
ACISION
1.1.8
Page 32
CDR Billing Configuration
SMSC and GBG both support the generation of billing records, CDRs. Here we will only look at the
CDR configuration on SMSC and concentrate on solutions to separate hot billing CDRs.
Hot billing CDRs are billing records that could not be processed in real time but are processed as
soon as possible after they are generated (the records are still hot). This processing is especially used
for prepaid text messages that could not be charged on submission time because the IN billing
system was not available: the billing system was in jammed state. On the SMSC it is possible to split
the CDRs in streams and to write the jammed prepaid CDRs into a separate directory.
Relevant SMSC parameters:
Parameter
Class
SMSC_LOGGING_MASK
SMSC
Value
PP_FIXED_BILLING
SMH_COMMON
PRE_AND_POSTPAID
NR_EXTRA_CDR_STREAMS
SMSC_COMMON
1 or more
Explanation
This parameter is a bitmask which is
used to specify which information is
logged by the SMSC
logging behavior of the SMH towards the
LOGSRV: pre- and postpaid messages,
only prepaid messages or only postpaid
messages.
The number of CDR streams is n+1,
where nr_extra_cdr_streams = n
When this attribute is 0, all CDRs will be
written into 1 file.
For more details how to configure billing see the SMSC Billing Manual.
Project
:
Customer :
ACISION
5
Solution Tuning & Sizing
Page 32
Project
:
Customer :
ACISION
Page 32
Troubleshooting prepaid configurations

During implementation of a prepaid solution of SMSC with GBG the following tools can be used for
troubleshooting.
Project
:
Customer :
ACISION
1.1.9
Page 32
Log files GBG
The following environment variables are available to trace and debug GBG.
Parameter
Value
GBG_LOG_FLAGS
FS
GBG_LOG_LEVEL
Explanation
Can be set to SV during deployment
and trouble shooting, requires restart
of GBG
Can be set to 5 during deployment
and trouble shooting, requires
GBG_LOG_FLAGS to be set to V and
restart of GBG
It is important to configure logrotate for rotation of log files to prevent disks getting full.
Project
:
Customer :
ACISION
1.1.10
Page 32
Log files SMSC
The default SMSC log file in SMSC$ROOT:[LOG] gives information about the status of the prepaid
processes.
To troubleshoot it is often necessary to trace the PBR entity. The following command gives a PBR
trace with all relevant information:
PML> trace class PBR /enttrci=all /enttrco=all /trcl=6 /test=39
Searching the produced trace file with the following OpenVMS command will give all information
about PBS transactions:
$ search <trace-file> PBS, TRANS /match=and /window=(0,3) /output=<output-file>
Project
:
Customer :
ACISION
1.1.11
Page 32
General logging
Besides the log and trace files it is good to trace the TCP traffic on GBG or SMSC with tcpdump.
Wireshark (aka Ethereal) supports the Diameter protocol, which makes trouble shooting easy. To get
a full translation of all fields it is necessary to put the relevant xml files and data dictionary in the
Diameter subdirectory of Wireshark.
Project
:
Customer :
ACISION
1.1.12
Page 32
Tools
Besides Wireshark the following tools are available to help with testing the prepaid solution.
Rory: Send and receive Prepaid Billing Protocol (PBP) messages. It can be used on the SMSC to
simulate the GBG and on the GBG to simulate the SMSC. This tool is not fit for performance tests.
Seagull: a free, Open Source (GPL) multi-protocol traffic generator test tool can be used to test
scenarios with Diameter protocol. A Seagull scenario - written in XML - describes the messages that
are sent and received. It also indicates the behaviour to adopt in case a message is unexpected or a
check on a parameter fails. It is not possible to test complex scenarios with a single Seagull setup.
Project
:
Customer :
ACISION
Page 32
Sizing and redundancy

When configuring the SMSC and GBG it is possible to create extra processes to support redundancy
and failover.
On each SMSC node normally runs one PBR process, which is capable of handling the prepaid
requests. When a PBR process on one node fails the SMSC will send all requests to the PBR process
on the other node. There are no data available about the relation between performance and more
PBR processes.
There should be a separate TCP process to handle the connection to the prepaid system. There are
no data available about the relation between performance and more TCP processes.
Project
:
Customer :
ACISION
6
Page 32
Solution - Frequently Asked Questions
Q. On the SMSC I am using prepaid bulk mode but I dont see any prepaid traffic.
A. Check the setting of the attribute SSD_COMMON /PP_OGT_LIST_TYPE. The default value of this
attribute is NOT_USED and in the BULK prepaid operational mode, due to the NOT_USED value the
prepaid checks are not performed for the mobile originator.
Q. GBG does not start when I use several modules with the Diameter protocol
A. Check the parameter number_of_threads. This parameter should be equal to or higher than the
number of Diameter modules.
Project
:
Customer :
ACISION
7
Configuration examples
Page 32
Project
:
Customer :
ACISION
Page 32
Basic example of GBG configuration for SMSC.

# To use the file, copy it to gbg.ini.
# When editing, refer to GBG CMAN.
#
#
#
#
The example shows generation of SDR files in CSV format and charging via RTPP
interface. If you need another prepaid interface, replace RTPP prepaid module
with another prepaid module. Make sure to replace reference to RTPP module in
[Routing/RulePrepaid].
#
#
#
#
#
#
#
#
#
#
#
#
#
Parameters that need to be checked/set:

Section [SPBP]
remote_address
msg_timeout_ms
Section [CSV]
attribute
sdr_file_path, namefmt
Section [RTPP] (if RTPP interface is used)
remote_address
response_timeout_ms
[Common]
multiple_instances=0
instance=1
name="GBG"
[SNMP]
trap_oid=".1.3.6.1.4.1.3830.1.1.7"
remote_address="45100"
[Modules]
Hub
="gbg_module_hub"
Stats ="gbg_module_stats"
Routing="gbg_module_routing"
SPBP
="gbg_module_spbp"
CSV
="gbg_module_csv"
RTPP
="gbg_module_rtpp"
[Hub]
default_route=Routing
[Stats]
snmp_oid=".1.3.6.1.4.1.3830.1.1.7.1.1"
[Routing]
stats_name=Stats
[Routing/RulePrepaid]
condition=#PREPAID_STATUS:#PREPAID
route=RTPP
route=CSV
[SPBP]
;connections=1
Project
:
Customer :
ACISION
Page 32
coi="COI"
prepaid_status=1
msg_timeout_ms=5000
response_code=SUB_LACKS_SERVICE:0x0204
response_code=SUB_BARRED:0x0202
response_code=SYNTAX_ERROR:0x0002
response_code=INTERNAL_ERROR:0x0002
response_code=CONGESTION:0x0003
response_code=ACCOUNT_EXPIRED:0x0203
response_code=CREDIT_EXPIRED:0x0205
response_code=LOW_BALANCE:0x0300
response_code=BS_ERROR:0x0102
response_code=DB_ERROR:0x0100
response_code=MISC_ERROR:0xF000
[SPBP/Translation]
transaction
=TRANSACTION
pricing
=PRICING
chargeInfo_msgRef
=TRANS_ID
chargeInfo_timeStamp
=TIMESTAMP
chargeInfo_chargedAddr_PID
=PID
chargeInfo_chargedAddr_TON
=TON
chargeInfo_chargedAddr_NPI
=NPI
chargeInfo_chargedAddr_address
=ADDRESS
chargeInfo_chargedAddr_networkType
=NETW_TYPE
chargeInfo_chargedAddr_localReg_prepaid
=PREPAID
chargeInfo_chargedAddr_localReg_subscriber
=SUBSCRIBER
chargeInfo_chargedAddr_localReg_largeAccount
=LARGE_ACCOUNT
chargeInfo_chargedParty
=CHARGED_PARTY
chargeInfo_billingField
=BILL_F
chargeInfo_chargedGlobalTitle_PID
=GT_PID
chargeInfo_chargedGlobalTitle_TON
=GT_TON
chargeInfo_chargedGlobalTitle_NPI
=GT_NPI
chargeInfo_chargedGlobalTitle_address
=GT_ADDRESS
chargeInfo_chargedGlobalTitle_networkType
=GT_NETW_TYPE
chargeInfo_chargedGlobalTitle_localReg_prepaid
=GT_PREPAID
chargeInfo_chargedGlobalTitle_localReg_subscriber =GT_SUBSCRIBER
chargeInfo_chargedGlobalTitle_localReg_largeAccount=GT_LARGE_ACCOUNT
chargeInfo_singleShot
=SINGLE_SHOT
chargeInfo_storeReference
=STORE_REF
chargeInfo_concatInfo_currentSegment
=CONCAT_SEGMENT
chargeInfo_concatInfo_maxSegment
=CONCAT_MAX_SEGMENT
chargeInfo_concatInfo_cmReference
=CONCAT_REF
chargeInfo_smscAddress
=SMSC_ADDRESS
chargeInfo_vamcInfo_formattedText
=VAMC_FORMATTED_TEXT
chargeInfo_vamcInfo_sizeOfCompData
=VAMC_SIZE_OF_COMPRESSED_DATA
chargeInfo_vamcInfo_shortPortAddress
=VAMC_SHORT_PORT_ADDRESS
chargeInfo_vamcInfo_longPortAddress
=VAMC_LONG_PORT_ADDRESS
chargeInfo_vamcInfo_udhData
=VAMC_UDH_DATA
chargeInfo_chargedPointCode
=POINT_CODE
chargeInfo_chargedImsi
=IMSI
chargeInfo_chargedAddrGroup
=ADDR_GROUP
chargeInfo_billingFieldSMPP
=BILL_F_SMPP
chargeInfo_origMsgID
=ORIG_MSG_ID
chargeInfo_payloadInfo_encoding
=PAYLOAD_ENCODING
chargeInfo_payloadInfo_payloadSize
=PAYLOAD_SIZE
Project
:
Customer :
ACISION
chargeInfo_payloadInfo_numChars
otherAddr_PID
otherAddr_TON
otherAddr_NPI
otherAddr_address
otherAddr_networkType
otherAddr_localReg_prepaid
otherAddr_localReg_subscriber
otherAddr_localReg_largeAccount
otherLAShortNumber
messageOrigAddr_PID
messageOrigAddr_TON
messageOrigAddr_NPI
messageOrigAddr_address
messageOrigAddr_networkType
messageOrigAddr_localReg_prepaid
messageOrigAddr_localReg_subscriber
messageOrigAddr_localReg_largeAccount
origRecipient_address_PID
origRecipient_address_TON
origRecipient_address_NPI
origRecipient_address_address
origRecipient_address_networkType
origRecipient_address_localReg_prepaid
origRecipient_address_localReg_subscriber
origRecipient_address_localReg_largeAccount
origRecipient_digits
teleserviceId_internal
teleserviceId_external
otherGlobalTitle_PID
otherGlobalTitle_TON
otherGlobalTitle_NPI
otherGlobalTitle_address
otherGlobalTitle_networkType
otherGlobalTitle_localReg_prepaid
otherGlobalTitle_localReg_subscriber
otherGlobalTitle_localReg_largeAccount
otherPointCode
otherImsi
otherAddrGroup
servicePrice_valuta
servicePrice_amount
servicePrice_significance
accountBalance_valuta
accountBalance_amount
accountBalance_significance
additionalService
primDuringJam
primServiceTime
[CSV]
;attribute=
sdr_file_path="/home/gbg/var/"
namefmt="node_%T_identity_%U.csv"
delimiter="""
separator=","
sequence=on
;header="CSV file, Created: %T"
;header="-----"
;trailer="Total SDRs: %R"
Page 32
=PAYLOAD_CHARS
=OA_PID
=OA_TON
=OA_NPI
=OA_ADDRESS
=OA_NETW_TYPE
=OA_PREPAID
=OA_SUBSC
=OA_LARGE_ACCOUNT
=OTHER_LA_SHORT_NUMBER
=MOA_PID
=MOA_TON
=MOA_NPI
=MOA_ADDRESS
=MOA_NETW_TYPE
=MOA_PREPAID
=MOA_SUBSC
=MOA_LARGE_ACCOUNT
=OR_PID
=OR_TON
=OR_NPI
=OR_ADDRESS
=OR_NETW_TYPE
=OR_PREPAID
=OR_SUBSC
=OR_LA
=OR_DIGITS
=TELE_ID_INT
=TELE_ID_EXT
=OGT_PID
=OGT_TON
=OGT_NPI
=OGT_ADDRESS
=OGT_NETW_TYPE
=OGT_PREPAID
=OGT_SUBSC
=OGT_LA
=OTHER_POINT_CODE
=OTHER_IMSI
=OTHER_ADDR_GROUP
=PRICE_VALUTA
=PRICE_AMOUNT
=PRICE_SIGNIFICANCE
=ACCOUNT_BALANCE_VALUTA
=ACCOUNT_BALANCE_AMOUNT
=ACCOUNT_BALANCE_SIGNIFICANCE
=ADDITIONAL_SERVICE
=PRIM_JAM
=PRIM_SERVICE_TIME
Project
:
Customer :
ACISION
Page 32
;sdr_file_period=0
;sdr_file_size=0
;sdr_per_file=0
[RTPP]
remote_address="rtpp1.example.com:55555"
remote_address="rtpp2.example.com:55555"
connections=3
response_timeout_ms=3000
forward_mode=off
;window_size=
;response_code=0x1000:SUCCESS
;response_code=0x2000:SYNTAX_ERROR
;response_code=0x2001:SYNTAX_ERROR
;response_code=0x2002:INTERNAL_ERROR
;response_code=0x6000:SUB_INSOLVENT
;response_code=0x6001:SUB_NOT_FOUND
;response_code=0x6002:SUB_BARRED
;response_code=INTERNAL_ERROR
[RTPP/Translation]
#BILLING_OPERATION
TIMESTAMP
=0x2004
=0x2005, convert_timestamp
ADDITIONAL_SERVICE
=0x9000,
PRICING
=0x9001,
ADDRESS
=0x9002,
NPI
=0x9003,
PID
=0x9004,
TON
=0x9005,
GT_ADDRESS
=0x9006,
GT_NPI
=0x9007,
GT_PID
=0x9008,
GT_TON
=0x9009,
CHARGED_PARTY
=0x900A,
CONCAT_SEGMENT
=0x900B,
CONCAT_MAX_SEGMENT
=0x900C,
CONCAT_REF
=0x900D,
PRIM_JAM
=0x900E
ORIG_MSG_ID
=0x900F,
OA_ADDRESS
=0x9010,
OA_NPI
=0x9011,
OA_PID
=0x9012,
OA_TON
=0x9013,
OTHER_LA_SHORT_NUMBER
=0x9014
SINGLE_SHOT
=0x9015
SMSC_ADDRESS
=0x9016
PRIM_SERVICE_TIME
=0x9017,
STORE_REF
=0x9018,
VAMC_FORMATTED_TEXT
=0x9019
VAMC_LONG_PORT_ADDRESS
=0x901A,
VAMC_SHORT_PORT_ADDRESS
=0x901B,
VAMC_SIZE_OF_COMPRESSED_DATA=0x901C,
VAMC_UDH_DATA
=0x901D
MOA_ADDRESS
=0x901E,
MOA_NPI
=0x901F,
MOA_PID
=0x9020,
MOA_TON
=0x9021,
OR_ADDRESS
=0x9022,
OR_NPI
=0x9023,
OR_PID
=0x9024,
OR_TON
=0x9025,
OR_DIGITS
=0x9026
convert, UINT32
if, {{:1}:{set, {BOOL:0}}:{set, {BOOL:1}}}
convert, UTF_STRING
convert, UINT32
convert, UINT32
convert, UINT32
convert, UTF_STRING
convert, UINT32
convert, UINT32
convert, UINT32
convert, UINT32
convert, UINT32
convert, UINT32
convert, UINT32
convert,
convert,
convert,
convert,
convert,
OCTET_STRING
UTF_STRING
UINT32
UINT32
UINT32
convert_timestamp
convert, UINT32
convert, UINT32
convert, UINT32
convert, UINT32
convert,
convert,
convert,
convert,
convert,
convert,
convert,
convert,
UTF_STRING
UINT32
UINT32
UINT32
UTF_STRING
UINT32
UINT32
UINT32
Project
:
Customer :
ACISION
#
#
#
#
#
Generated from:
smsc.gbg.ini.example.xml=2:xml:gbg#1 config.xml=6:xml:gbg#3
config.xml=3:xml:gbg#4 config.xml=4:xml:gbg#2 config.xml=3:xml:gbg#6
config.xml=17:xml:gbg#8
Page 32
Project
:
Customer :
ACISION
Basic example of GBG configuration for Diameter.
[Common]
multiple_instances=0
instance=1
name="GBG"
[SNMP]
trap_oid=".1.3.6.1.4.1.3830.1.1.7"
remote_address="45100"
[Modules]
Hub
="gbg_module_hub"
Stats
="gbg_module_stats"
Routing ="gbg_module_routing"
SPBP
="gbg_module_spbp"
CSV
="gbg_module_csv"
Diameter="gbg_module_diameter"
[Hub]
default_route=Routing
[Stats]
snmp_oid=".1.3.6.1.4.1.3830.1.1.7.1.1"
[Routing]
stats_name=Stats
[Routing/RulePrepaid]
condition=#PREPAID_STATUS:#PREPAID
route=Diameter
route=CSV
[SPBP]
;connections=1
coi="COI"
prepaid_status=1
msg_timeout_ms=5000
response_code=SUB_LACKS_SERVICE:0x0204
response_code=SUB_BARRED:0x0202
response_code=SYNTAX_ERROR:0x0002
response_code=INTERNAL_ERROR:0x0002
response_code=CONGESTION:0x0003
response_code=ACCOUNT_EXPIRED:0x0203
response_code=CREDIT_EXPIRED:0x0205
response_code=LOW_BALANCE:0x0300
response_code=BS_ERROR:0x0102
response_code=DB_ERROR:0x0100
response_code=MISC_ERROR:0xF000
Page 32
Project
:
Customer :
ACISION
[SPBP/Translation]
transaction
=TRANSACTION
pricing
=PRICING
chargeInfo_msgRef
=TRANS_ID
chargeInfo_timeStamp
=TIMESTAMP
chargeInfo_chargedAddr_PID
=PID
chargeInfo_chargedAddr_TON
=TON
chargeInfo_chargedAddr_NPI
=NPI
chargeInfo_chargedAddr_address
=ADDRESS
chargeInfo_chargedAddr_networkType
=NETW_TYPE
chargeInfo_chargedAddr_localReg_prepaid
=chargeInfo_chargedAddr_localReg_subscriber
=chargeInfo_chargedAddr_localReg_largeAccount
=chargeInfo_chargedParty
=CHARGED_PARTY
chargeInfo_billingField
=BILL_F
chargeInfo_chargedGlobalTitle_PID
=GT_PID
chargeInfo_chargedGlobalTitle_TON
=GT_TON
chargeInfo_chargedGlobalTitle_NPI
=GT_NPI
chargeInfo_chargedGlobalTitle_address
=GT_ADDRESS
chargeInfo_chargedGlobalTitle_networkType
=chargeInfo_chargedGlobalTitle_localReg_prepaid
=chargeInfo_chargedGlobalTitle_localReg_subscriber =chargeInfo_chargedGlobalTitle_localReg_largeAccount=chargeInfo_singleShot
=chargeInfo_storeReference
=chargeInfo_concatInfo_currentSegment
=CONCAT_SEGMENT
chargeInfo_concatInfo_maxSegment
=CONCAT_MAX_SEGMENT
chargeInfo_concatInfo_cmReference
=CONCAT_REF
chargeInfo_smscAddress
=SMSC_ADDRESS
chargeInfo_vamcInfo_formattedText
=chargeInfo_vamcInfo_sizeOfCompData
=chargeInfo_vamcInfo_shortPortAddress
=chargeInfo_vamcInfo_longPortAddress
=chargeInfo_vamcInfo_udhData
=chargeInfo_chargedPointCode
=POINT_CODE
chargeInfo_chargedImsi
=IMSI
chargeInfo_chargedAddrGroup
=ADDR_GROUP
chargeInfo_billingFieldSMPP
=BILL_F_SMPP
chargeInfo_origMsgID
=chargeInfo_payloadInfo_encoding
=chargeInfo_payloadInfo_payloadSize
=chargeInfo_payloadInfo_numChars
=otherAddr_PID
=OA_PID
otherAddr_TON
=OA_TON
otherAddr_NPI
=OA_NPI
otherAddr_address
=OA_ADDRESS
otherAddr_networkType
=OA_NETW_TYPE
otherAddr_localReg_prepaid
=otherAddr_localReg_subscriber
=otherAddr_localReg_largeAccount
=otherLAShortNumber
=OTHER_LA_SHORT_NUMBER
messageOrigAddr_PID
=MOA_PID
messageOrigAddr_TON
=MOA_TON
messageOrigAddr_NPI
=MOA_NPI
messageOrigAddr_address
=MOA_ADDRESS
messageOrigAddr_networkType
=messageOrigAddr_localReg_prepaid
=messageOrigAddr_localReg_subscriber
=messageOrigAddr_localReg_largeAccount
=origRecipient_address_PID
=OR_PID
origRecipient_address_TON
=OR_TON
origRecipient_address_NPI
=OR_NPI
origRecipient_address_address
=OR_ADDRESS
Page 32
Project
:
Customer :
ACISION
origRecipient_address_networkType
origRecipient_address_localReg_prepaid
origRecipient_address_localReg_subscriber
origRecipient_address_localReg_largeAccount
origRecipient_digits
teleserviceId_internal
teleserviceId_external
otherGlobalTitle_PID
otherGlobalTitle_TON
otherGlobalTitle_NPI
otherGlobalTitle_address
otherGlobalTitle_networkType
otherGlobalTitle_localReg_prepaid
otherGlobalTitle_localReg_subscriber
otherGlobalTitle_localReg_largeAccount
otherPointCode
otherImsi
otherAddrGroup
servicePrice_valuta
servicePrice_amount
servicePrice_significance
accountBalance_valuta
accountBalance_amount
accountBalance_significance
additionalService
primDuringJam
primServiceTime
Page 32
[CSV]
;attribute=
=====OR_DIGITS
=TELE_ID_INT
=TELE_ID_EXT
=OGT_PID
=OGT_TON
=OGT_NPI
=OGT_ADDRESS
=====OTHER_POINT_CODE
=OTHER_IMSI
=OTHER_ADDR_GROUP
=PRICE_VALUTA
=PRICE_AMOUNT
=PRICE_SIGNIFICANCE
====ADDITIONAL_SERVICE
==PRIM_SERVICE_TIME
sdr_file_path="/home/gbg/var/"
namefmt="node_%T_identity_%U.csv"
delimiter="""
separator=","
sequence=on
;header="CSV file, Created: %T"
;header="-----"
;trailer="Total SDRs: %R"
;sdr_file_period=0
;sdr_file_size=0
;sdr_per_file=0
[OpenDiameter]
product="SMSC_V5_DP"
vendor_id=3830
supported_vendor_id=3830
auth_application_id=4
dictionary="/opt/gbg-2/etc/diameter_dictionary.xml"
identity="gbg.acision.com"
local_realm="acision.com"
response_timeout_ms=3000
[Diameter]
remote_address="diameter.example.com:3868"
remote_realm="example.com"
compatibility=Standard
Project
:
Customer :
ACISION
application_id=4
command_code=272
;username="acision@example.com"
response_code=2001:SUCCESS
response_code=3000-3003:SYNTAX_ERROR
response_code=3004:CONGESTION
response_code=4001:MISC_ERROR
response_code=4002-4009:BS_ERROR
response_code=4010:SUB_LACKS_SERVICE
response_code=4012:SUB_INSOLVENT
response_code=4013-4999:MISC_ERROR
response_code=5003:MISC_ERROR
response_code=5030:SUB_NOT_FOUND
response_code=5031-5999:MISC_ERROR
response_code=9:CONGESTION
response_code=11:SYNTAX_ERROR
response_code=1:INTERNAL_ERROR
[Diameter/Translation/Code]
script_file="../etc/smsc_diameter.diameter.request.pas"
[Diameter/ResponseTranslation/Code]
script_file="../etc/smsc_diameter.diameter.response.pas"
#
#
#
#
#
Generated from:
smsc_diameter.gbg.ini.example.xml=6:xml:gbg#1 config.xml=6:xml:gbg#3
config.xml=15:xml:gbg#11
Page 32

Configuration Model Description GBG SMSC V1 - 0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuration Model Description GBG SMSC V1 - 0

Uploaded by

Copyright:

Available Formats

Company Confidential

INTERNAL USE ONLY

Copyright Acision BV 2008

Technical specification of the solution...........................................................................................................6

Real-time billing mode: Prepaid subscribers provisioned on SMSC.....................................................11

Bulk billing mode: Prepaid subscribers NOT provisioned on SMSC.....................................................11

Roaming prepaid subscribers.................................................................................................................11

Solution Tuning & Sizing..............................................................................................................................11

Sizing and redundancy............................................................................................................................11

Solution - Frequently Asked Questions.......................................................................................................11

Basic example of GBG configuration for SMSC....................................................................................11

Basic example of GBG configuration for Diameter................................................................................11

Document version: 1.0

Version and Configuration Management

Configuration History Sheet

Document version: 1.0

Document version: 1.0

Document version: 1.0

Document version: 1.0

Document version: 1.0

The benefits of using this solution will be:

Brief description of deliverable

Description of integration of SMSC, GBG

Test documentation and reports

Document version: 1.0

Technical specification of the solution

Document version: 1.0

Protocol conversion from SPBP to Diameter; several other

Document version: 1.0

Document version: 1.0

1.0, 1.1, 2.0

1.7.1 and previous Input interfaces

SAP 0x80 (OMG)

Output prepaid interfaces

Diameter Base Protocol

This document covers only SPBP and Diameter protocols.

Document version: 1.0

supported Diameter application

Acision Diameter for SMS

Ericsson SCAP, v. CCN 5.1

Tecnomen DCCA, release

Document version: 1.0

Document version: 1.0

Document version: 1.0

Document version: 1.0

Enhanced Reserve-Commit Model

Document version: 1.0

Transaction flow for SMS with insufficient credit

Document version: 1.0

Document version: 1.0

For all models the following licenses should be enabled in SYS$SYSTEM:CMG_LICENSE.DAT

Document version: 1.0

Real-time billing mode: Prepaid subscribers provisioned on SMSC

Not relevant in this model

Document version: 1.0

Document version: 1.0

Bulk billing mode: Prepaid subscribers NOT provisioned on SMSC

Document version: 1.0

Roaming prepaid subscribers

Parameter settings for REAL_TIME mode:

Number of prepaid users in

Document version: 1.0

Document version: 1.0