Short Message Service Centre 4.64.0

Real-time Prepaid Interface to PSAReal-time Prepaid Interface 3.2.5

Configuration GuideInstallation & Configuration Guide

Document Version: 0.30.1Document Status: DRAFTDocument Release Date: October 2003

Table of Contents

1 Configuration....................................................................................................10

1.1 Introduction........................................................................................................................ 10

1.2 Licence.............................................................................................................................. 10

1.3 Prepaid Billing Large Account Configuration......................................................................10

1.4 Prepaid Billing O&M Configuration.....................................................................................10

1.5 Miscellaneous Prepaid Billing Configuration......................................................................14

1.6 TCP configuration..............................................................................................................14

1.7 Configuring Bulk Prepaid for SMSC 4.6 per LA.................................................................14

1.8 Modifying existing SMSC parameters for Bulk Prepaid for SMSC 4.6...............................15

© 2001 CMG Wireless Data Solutions B.V. — List of Tables iii

© 2001 by CMG Wireless Data Solutions B.V. All rights reserved. This document may not be copied in whole or in part without the prior written consent of CMG Wireless Data Solutions B.V.

The information in this document is subject to change without notice and should not be construed as a commitment by CMG Wireless Data Solutions B.V.. CMG Wireless Data Solutions B.V. assumes no responsibility for any errors that may appear in this document.

The software described in this document is furnished under license and may be used or copied only in accordance with the terms of such license.

Products mentioned in this document are identified by the trademarks or service marks of their respective companies or organisations.

List of Tables

Table P-1: Typographic conventions....................................................................................................vii

Table 1-1 PBR_COMMON Attributes...................................................................................................11

Table 1-2 SMSC Attributes..................................................................................................................12

Table 1-3 SMH_COMMON Attributes..................................................................................................13

Table 1-4 SSD_COMMON Attributes...................................................................................................13

Table 1-5: Relevant Prepaid Logicals..................................................................................................14

© 2001 CMG Wireless Data Solutions B.V. — List of TablesList of TablesTable of ContentsList of Tables v

Preface

Purpose

The purpose of this document is to describe the installation and configuration aspects of the Real-time Prepaid interface of the Short Message Service Centre.

Since many of the actual requirements and entry criteria for installation are not yet known at the time of this writing, it is suggested that this document is updated in a later stadium to include this information. Also performance issues cannot be addressed yet.

Audience

The target audience of this document are all persons who are involved in or have to know more about the installation and configuration of the Real-time Prepaid interface. This document is for CMG internal use only.

Organisation

This document has currently only one chapter. The first chapter describes the configuration aspects, currently only for the SMSC.

Typographic conventions

In this document, the typographic conventions listed in Table P-1 are used.

Table P-1: Typographic conventions

Typeface or Symbol

Meaning/Used for Example

Courier Refers to a keyboard key, system command, label, button, filename, window, or other computer component or output.

The directory data contains…

Click the Close button to…

<courier> Serves as a placeholder for variable text that the user will replace as appropriate to its context.

Use the file name <entity>.cfg for...

$ Denotes an OpenVMS Digital Command Language prompt.

$ dir

– Denotes line continuation; the character should be ignored as the user types the example, and Enter should only be pressed after the last line.

$ search [.data]*.dat -searchforthis

© 2001 CMG Wireless Data Solutions B.V. — Preface vii

1.1 HConfiguration

This chapter describes how Real-time Prepaid can be configured.

1.2 Introduction

This document focuses on configuration issues for prepaid billing with PSA.

For a description of the functionality you can read the SMSC Operator Manual, chapter 7.10.2 Option 019b – SMS Prepaid with external prepaid database.

1.3 Licence

The following SMSC licenses must be activated to use the “Prepaid SMSC” option:

SMSC_PREPAID_SMS_ENABLED

SMSC_PP_BULK_ENABLED

1.4 Prepaid Billing Large Account Configuration

In this section Large Account (LA) specific configuration issues regarding prepaid billing are presented.

The attribute MO_PP_CHARGING determines per LA what the charging characteristics are for prepaid users in MO-LA traffic. The attribute can be set to:

MOBILE_CHARGED (default) when the prepaid user is the charged party and the message is not free.

MOBILE_FREE when the prepaid user is the charged party and the message is free.

LARGE_ACCOUNT when the LA is the charged party and the message is charged via the postpaid billing.

The attribute MT_PP_CHARGING determines per LA what the charging characteristics are for prepaid users in LA-MT traffic. The attribute can be set to:

MOBILE_CHARGED when the prepaid user is the charged party and the message is not free.

MOBILE_FREE when the prepaid user is the charged party and the message is free.

LARGE_ACCOUNT (default) when the LA is the charged party and the message is charged via the postpaid billing.

Both LA attributes are available via PRL (qualifiers /MO_PP_CHARGING and /MT_PP_CHARGING) and PRX (via the Large Account screen under ‘More Attributes’).

1.5 Prepaid Billing O&M Configuration

In this section the O&M configuration issues regarding the prepaid billing are presented. Table1-2, Table 1-3, Table 1-4 and detail the relevant attributes from SMSC classes PBR_COMMON, SMSC, SMH_COMMON and SSD respectively.

© 2001 CMG Wireless Data Solutions B.V. — Abbreviations 9

Table 1-2 PBR_COMMON Attributes

Attribute Description Value

MAX_TRANS_PER_SEC The maximum number of transactions that each PBR process will handle per second. The overshoot of transactions is postponed.

1000

SPBP_OPT_FIELDS_MASK This attribute is used to specify which of the optional protocol fields are included by the SMSC in the transaction records.

0xFFFFFFF

USE_CACHE This attribute is used by the SMSC to determine whether to remember the latest blocking status of prepaid users or not. If it is set to "YES", a cache will be created and used when the connection to the PSA is down. If "NO", then no cache will be created.

NO

YES might cause performance problems.

CACHE_SIZE This attribute defines the size of the local prepaid user cache. Irrelevant when no caching used

100

smaller values are not allowed

CACHE_TO_FILE This attribute determines whether or not the prepaid user is mapped onto a file or not.

NO

PP_CM_INCLUDED The attribute is used to specify whether Concatenated Message information is included in the billing information sent to the Prepaid Billing System.

Not supported by PSA 3.2.5

NO

PP_EMS_INCLUDED The attribute is used to specify whether Enhanced Message Service Information is included in the billing information sent to the Prepaid Billing System.

Not supported by PSA 3.2.5

NO

PP_APA_INCLUDED The attribute is used to specify whether Application Port Addressing Information is included in the billing information sent to the Prepaid Billing System.

Not supported by PSA 3.2.5

NO

Table 1-3 SMSC Attributes

Attribute Description Value

PREPAID_SMS_ENABLED Indicates whether the prepaid functionality is enabled or not.

ON

PP_SMS_BULK_ENABLED Indicates whether SMS Prepaid bulk functionality is enabled or not.

ON

PP_SUPPORTED_SPBP_ MSGS This attribute is used to specify which transaction types are generated by the SMSC.

The bits of this field correspond to the following optional fields (bit 0 is the least significant bit):

Bit 0: Support Credit for charged Primary Services

Other bits are not supported by PSA 3.2.5

1

PP_SUPPORTED_ADD_ SER This attribute is used to specify which Additional Service transaction records are supported by the SMSC.

Not supported by PSA 3.2.5

0

PP_MOMT_CHARGING This attribute 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.

Depends on customer

Flag; ORIGINATOR_FREE, ORIGINATOR_CHARGED, RECIPIENT_FREE & RECIPIENT_CHARGED; BOTH_CHARGED default = ORIGINATOR_CHARGED.

_FREE is not supported by PSA 3.2.5

PP_MOFIX_CHARGING This attribute is used to specify whether the originator or the recipient is the charged party in prepaid MO-FIX (non-LA) traffic and whether this type of traffic is free or not.

Depends on customer

Flag; ORIGINATOR_FREE, ORIGINATOR_CHARGED & RECIPIENT; default = ORIGINATOR_CHARGED.

_FREE is not supported by PSA 3.2.5

PP_FIXMT_CHARGING This attribute is used to specify whether the originator or the recipient is the charged party in prepaid FIX (non-LA)-MT traffic and whether this type of traffic is free or not.

Depends on customer

Flag; ORIGINATOR, RECIPIENT_CHARGED & RECIPIENT_FREE; default = ORIGINATOR.

_FREE is not supported by PSA 3.2.5

PP_NOTIF_SETTING This attribute is used to specify whether requested Notifications or Status Reports by prepaid users are

Flag; FREE, CHARGED & IGNORED; default =

© 2001 CMG Wireless Data Solutions B.V. — Abbreviations 11

Attribute Description Valuefree, charged or whether these requests are ignored altogether.

Not supported by PSA 3.2.5

CHARGED.

PP_JAMMED_SETTING This attribute is used to specify the behaviour of the SMSC when the PSA interface is jammed. This behaviour can be either: all prepaid messages are rejected; all prepaid messages are free but the last known blocking status is used to accept or reject them; all prepaid messages are free regardless of the last known blocking status. If the attribute /PP_FIXED_BILLING has been set to PRE_AND_POSTPAID, the generated submission and/or delivery CDR will contain information about the JAMMED event.

SMS_FREE

Other settings will result in SMS_FREE behaviour

PP_MODE This attribute is used to specify the operational mode of the SMSC for prepaid traffic.

Only BULK is supported by PSA 3.2.5

BULK

See PML> help set class SMSC /pp_mode hot to change this setting

Table 1-4 SMH_COMMON Attributes

Attribute Description Value

PP_PB_TIMEOUT This attribute is used to specify the timeout value (in seconds) for the PSA response to an earlier transaction. A value of 0 means that the SMSC will wait indefinitely for the response to arrive.

5

PP_PB_TIMEOUT _TICK

PP_FIXED_BILLING This attribute is used to specify the SMSC logging behaviour with respect to prepaid messages: messages charged to pre- and postpaid users are logged, messages charged to prepaid users only are logged or messages charged to postpaid users only are logged.

Depends on customer.

Flag; PRE_AND_POSTPAID, POSTPAID_ONLY & PREPAID_ONLY; default = POSTPAID_ONLY.

Table 1-5 SSD_COMMON Attributes

Attribute Description Value

PP_OGT_LIST_TYPE This attribute is used to specify the type of originator global title list. This setting defines whether the prepaid check is performed when the originator global title is found on the list or when

Flag: “BLACK”, “WHITE”, “NOT_USED”, “MATCH_ALL”

Attribute Description Value

it is not found on the list.

Depends on customer

Should not be “NOT_USED”, because then primary service is not charged

PP_MAX_USERS The /MAX_PP_USERS qualifier is used to specify the maximum number of prepaid users that the SSD will hold in memory. This attribute is a parameter.

Should be zero in PSA 3.2.5

1.6 Miscellaneous Prepaid Billing Configuration

In this section the remaining configuration issues regarding the prepaid billing are presented.

For the configuration of the SMSC prepaid solution the following logicals are relevant (Table 1-6). They should be defined in the file SMSC$ROOT:[SCRIPTS]SMSC_COMMON.COM. Running this script on each backend node and restarting the entities can modify the values.

Table 1-6: Relevant Prepaid Logicals

Logical Description Value

PBR_CACHE_DIR This parameter determines the location of the prepaid user cache.

If USE_CACHE = NO this attribute is irrelevant

String; a valid VMS directory name; default = SMSC$ROOT:[DATA]

© 2001 CMG Wireless Data Solutions B.V. — Abbreviations 13

For more detailed information about these attributes is referred to the SMSC online help and the [SOG] of the related SMSC release.

1.7 TCP configuration

One or more ports should be associated with the PBR in the TCP configuration file(s) SMSC$ROOT:[DATA]TCP_<entity name>.CNF The keyword P_PBR should be used for the service field.

For example:

PORT 5001SERVICE P_PBRCHANNEL_TYPE SWITCHED

1.8 Configuring Bulk Prepaid for SMSC 4.6 per LA

The following paragraph describes the Bulk Prepaid functionality as far as it is configured per LA.

For MO-LA and LA-MT traffic the SMSC offers the opportunity to configure the charging behaviour per LA.

For MO-LA traffic the default is that prepaid originator is the charged party and the traffic is non-FREE. Other non-default possibilities are that the prepaid originator is the charged party and the traffic is FREE or that the (receiving) LA is the charged party. If non-default MO-LA characteristics are needed, this can be configured via PRL:

PRL> UPDATE LA <short_number> /MO_PP_CHARGING = (MOBILE_CHARGED|MOBILE_FREE|LARGE_ACCOUNT)

This attribute can also be set via PRX via the Large Account screen, under 'More Attributes'.

For LA-MT traffic the default is that large account itself is the charged party. Other non-default possibilities are that the prepaid recipient is the charged party and the traffic is non-FREE or FREE. If non-default LA-MT characteristics are needed, this can be configured via PRL:

PRL> UPDATE LA <short_number> /MT_PP_CHARGING = (MOBILE_CHARGED|MOBILE_FREE|LARGE_ACCOUNT)

This attribute can also be set via PRX via the Large Account screen, under 'More Attributes'.

1.9 Modifying existing SMSC parameters for Bulk Prepaid for SMSC 4.6

If you use PBR caching, the PBR has to be started with enough quota (memory) to keep the cache in memory. The required amount of memory for the cache is 2000000 x 12 bytes = 24 Mbytes. Hence, the following PML has to be executed for each node before starting up the PBR for the first time:

© 2001 CMG Wireless Data Solutions B.V. — Abbreviations 15

PML> add class ad entity <node> /QUOTA= (PBR, WSQUOTA=650000, WSDEFAULT=650000,WSEXTENT=650000,PGFLQUOTA=650000)

In order to support the higher latency of the prepaid messages, more contexts are needed for the GIW and the SIWPLMN:

PML> SET CLASS PLMN /MAX_ACTIONS=<new value>

Here new value is 20% higher than the current setting on the system. The above command can only be executed while all SIWPLMN and DIWPLMN entities are stopped.

The current value is obtained by the following command:

PML> SHOW CLASS PLMN /MAX_ACTIONS

Abbreviations

GIW Gateway InterWorking

MD Managing Director

OGT Originator Global Title

PBB Prepaid Billing Blocker

PBR Prepaid Billing Router

PML Presentation Manager Line

PRH Provision Handler

PRL Provisioning Line interface Program

PRX Provisioning X-server

SMH Short Message Handler

SMSC Short Message Service Centre

SSD Subscriber Service Director

© 2001 CMG Wireless Data Solutions B.V. — Abbreviations 17

References

[SOG] System Operator Guide

[RN] Release Note for Real-time Prepaid

Version History

Version

Status Date Details of Changes

Author(s)

0.1 DRAFT October 2003 Draft version for STC J. Van Beers

Approval

Version Date Approved by Signature