1st section : COVER SHEET

This section is dedicated to document internal management This section must not be distributed externally

TITLE
Title 1: Title 2: Title 3:
(Client-Market/Generic) (Stage/Product Identification) (Type of Document)

VIETNAM / VMS ICC SPECIFICATIONS FOR MMS/SMSMO OFFLINE CHARGING OBJECT

Summary: This document contains the specifications to make off-line charging for MMS and SMSMO calls for ICC service for Vietnam. Audience: This document is to be used by the customer. AUTHORIZED DISTRIBUTION: INTERNAL EXTERNAL

DOCUMENT IDENTIFICATION:
History Ed
01

It

Status
Draft

Comments
Creation of document

Author(s)

Approval(s)

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

1/2

Internal Information
Reference of origin document:

END OF 1st SECTION

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

2/2

INTELLIGENT NETWORK

VIETNAM / VMS ICC

SPECIFICATIONS FOR MMS/SMSMO OFFLINE CHARGING

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

1/2

PREFACE

This document describes the specification of SMS/MMS Off-Line Charging tool for ICC in Vietnam.

HISTORY

Editio n
Ed 01

Date
(yy-mm-dd)

Comments

09-10-16

Creation of document

TRADEMARKS

None.

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

2/2

TABLE OF CONTENTS

1. DESCRIPTION SOLUTION.........................................................................................................................5 1.1 PRINCIPLE OF MMS OFF LINE CHARGING ......................................................................................................5 1.2 ACCOUNT CHARGING LOGIC...........................................................................................................................5 1.3 ASN CONVERSION PROCESS STEPS..........................................................................................................8 2. DESCRIPTION OF THE ASN CONVERSION PROCESS.......................................................................9 2.1 THE ALGORITHM...........................................................................................................................................9 2.2 FILES SPECIFICATIONS..................................................................................................................................10 2.2.1 SPECIFICATION OF THE SMSMO.INI FILE.......................................................................................................10 2.2.2 SPECIFICATION OF THE MDV FILES...............................................................................................................10 2.2.3 OTHER FILES.............................................................................................................................................11 2.2.4 OUTPUT FILES...........................................................................................................................................11 2.3 ERROR & EXCEPTION HANDLING BY OFLCS.............................................................................12 2.3.1 OFLCS INTERNAL ERROR................................................................................................................12 2.3.2 OFLCS FILTERED RECORDS.............................................................................................................12 2.3.3 DPE ERROR AT CE INTERFACE.......................................................................................................13 2.3.4 TIMEOUT AT CE INTERFACE...........................................................................................................13 2.3.5 TE TICKET SENDING NOK................................................................................................................13

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

3/2

REFERENCE DOCUMENTS

None. N Reference Ed Title

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

4/2

1. DESCRIPTION SOLUTION 1.1 PRINCIPLE OF MMS OFF LINE CHARGING

Each hour, the charging proxy creates a file, containing SMS/MMS costs for given MSISDN's on the IN platform, a script is put in the crontab process to get via FTP the files from the charging proxy. Then a process on the IN SMP platform treats these files. On the IN platform, to withdraw the SMSMO/MMS cost of the account credit, 2 steps are necessary: - First, a process, launched each hour, reads some MDV files containing the costs of SMSMO/MMS messages for each MSISDN. The treatment consists in conversion of these flat files to ASN.1 grammar. The credit to be withdrawn in the file should always be positive. - The OFLC Service treats the final withdrawal.

1.2 ACCOUNT CHARGING LOGIC

The ASN conversion process transfers its ready tickets file in the input directory of the OFLCS server that is configured. Only one OFLCS SEP (the SEP one named "%srvname%-1") polls the input directory of the ready ticket files and inserts the file name into the file name queue (implemented in shared memory) in ascending order by time of file creation. To ensure that each file is processed only once, the OFLCS maintains a queue of file names with locking mechanism. The entry of the file name queue contains the following information: File name and file length If the file is taken by a SEP for processing: SEP ID Each OFLCS SEP can select a free ready file from the file name queue. The selection rule is the first free file in the file name queue. REMARK: Chronological processing of records cant be guaranteed when multiple OFLCS SEPs are running. (Chronological processing of records is important for bundle management and for itemized billing). As soon as an OFLCS SEP has taken a ready file in the file name queue, it processes it as following: It writes its SEP ID in the file name queue entry. It renames the ready ticket file (with the suffix .rdy) in current ticket file (with the suffix .cur) It copies the current ticket file in a buffer, and extracts each record from the buffer according the configured pace in the activity time band load profile. It decodes each ticket and it calls CRE for one shot rating and charging and it generates the INDR ticket.
VIETNAM / VMS - ICC Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

5/2

 If ticket processing is not successful, According error type, it sends an alarm and writes the wrong record in the error file dedicated to the error type (with the suffix .xxxerr) . When all the tickets of the file are processed, it renames the current ticket file in ended ticket file (with the suffix .end). And it removes the file entry from the file name queue. It polls again the file name queue for a next ready ticket file.

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

6/2

The figure hereafter presents a global view of the ICC OFFLINE charging chain

ICC

Products

Accounting files
Customers charged accounts

SMS -Center

Convergent Rating Engine

Pfmstat/stata cc
5: accounting files storage TE UNS

3: Rating and charging request /reply

4: Accounting ticket

SMS notification

OFFLINE Call Service

Input files

ticket

2: fetched input ticket

ASN TOOL

CONVERSION

I: Files transfer (FTP)

External Mediation device

1: 2: 3: 4: 5: Files transferred containing MDV format followed by asn conversion by ALU tool. Input tickets file fetched containing data in ASN1 format. CDR Rating and charging Request / Reply Accounting ticket generation and sending toward ICC ticket chain. Accounting ticket storage in accounting ticket file

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

7/2

1.3 ASN CONVERSION PROCESS STEPS

At 1. 2. 3. Each hour, the following process is launched by crontab process: SMSMO.INI File Loading containing all information about the environment. MDV files loading. if MDV files are correct, for each MSISDN present in .MSC/.chpini files conversion algorithm is launched. Ie. YYYYMMDDhhmmXXXX.chpin YYYYMMDDhhmmXXXX.chpin.rdy SMSYYMMDD_xxx.MSC SMSYYMMDD_xxx.MSC.rdy 4. .rdy files are treated by the OFLCS. 5. Alarms and results writing is done by OFLCS. 6. Exit

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

8/2

2. DESCRIPTION OF THE ASN CONVERSION PROCESS

2.1 THE ALGORITHM

The algorithm of the program is represented below. YYMMDD is the date of the SMSMO/MMS file (for example 010115 if the date of the file is 15 January 2001) <NAME> = MMS Is TMP<NAME>.MSC present ? No Yes Process TMP<NAME>.MS C no Number of treated accounts>= MAX_TREATMENT Yes Save the untreated accounts into TMP<NAME>.MSC

N: number of SMSYYMMDD_xxx.MSC or YYYYMMDDHHMMxxxx.chpin files N=0 ? no Sort the SMSYYMMDD_xxx.MSC or no YYYYMMDDHHMMxxxx.chpin files from the oldest to the most recent N=0 ?

yes

yes no Process the SMSYYMMDD_xxx.MSC [N] or YYYYMMDDHHMMxxxx.chpin[N] file yes Save the untreated accounts into TMP<NAME>.MSC Move SMSYYMMDD_xxx.MSC [N] into SMSYYMMDD_xxx.SAV [N] or Move YYYYMMDDHHMMxxxx.chpin [N]

Number of treated accounts >= MAX_TREATMENT no

Move SMSYYMMDD_xxx.MSC [N] into SMSYYMMDD_xxx.SAV [N] or Move YYYYMMDDHHMMxxxx.chpin [N] into YYYYMMDDHHMMxxxx.SAV <NAME> = MMS ? Yes <NAME> = SMS No

End of treatment

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

9/2

2.2 FILES SPECIFICATIONS

2.2.1 Specification of the SMSMO.ini file
The first line of the SMSMO.ini file allows to treat the SMS/MMS files which are previous to the date of the day: The format of the first line is BACKDAY=n where n is the number of days For example BACKDAY=1 means that the program will process the SMS/MMS files of the day before then the SMS/MMS files of the day. BACKDAY=0 means that the program will only process the SMS/MMS files of the day. Note: the first line (BACKDAY=n) is optional. If it is not present, the program will only process the SMS/MMS files of the day. The SMSMO.ini file allows to specify the parameters of the out of call logic as well as the maixmum number of accounts that can be treated during each hour. The format of each line is the following: H is the hour (from 0 to 23) MAX if the maximum number of accounts that can be treated during the hour H (i.e. # of accounts converted to asn1). OOC1 is depreciated and kept for legacy reasons. OOC2 is depreciated and kept for legacy reasons.
H/MAX/OOC1/OOC2

Here is an example of SMSMO.ini file

BACKDAY=2 0/5000/100/200 1/5000/0/200 2/4000/0/200 .

Be careful, there mustnt be a space character between the different parameters. In the contrary case, the program prints an error (SMSMO.ini is not correct!) and exits.

23/3000/100/300

2.2.2 Specification of the MDV Files

The MDV files come from a Mediation Device by FTP commands for SMS-MO files. They will come from the charging proxy by FTP commands for MMS files. They should be copyed in the dir: <OFLC_SOURCE_FILE_DIR> configured in the OFLC service. The name format of these files for MMS treatment should be: <OFLC_SOURCE_FILE_DIR>/CHPIN/YYYYMMDDhhmmXXXX.chpin The name format of these files for SMS treatment should be: < OFLCS_SOURCE_FILE_DIR >/MSC/SMSYYMMDD_xxx.MSC Where: - YY - Year of day SMSMO Treatment - 2 digits. - YYYY - Year of day MMS Treatment - 4 digits. - MM - Month of day SMSMO/MMS Treatment - 2 digits. - DD - Day of day SMSMO/MMS Treatment - 2 digits. - HH - Hour of day MMS Treatment - 2 digits.
VIETNAM / VMS - ICC Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

10/2

MM - Minute of day MMS Treatment - 2 digits. xxx : the file number: this file number increases for each new file for each day.

The format of each line in these files is:

msisdn:cost (where msisdn is the msisdn number of the subscriber and cost is the cost of the SMS/MMS)

Be careful, there musnt be a space character between msisdn and : or between : and cost. In the contrary case, the program prints a warning and continues the processing.

The cost should always be positive. (It means that the accounts should be withdrawn)

2.2.3 Other Files

The process automatically creates a temporary file if the treatment of a MDV files is too long. All of SMSMO/MMS not treated are copied in this file.
The File format is the same as MDV Files: <OFLC_SOURCE_FILE_DIR>/MSC/TMPSMS.MSC for SMS treatment <OFLC_SOURCE_FILE_DIR>/CHPIN/TMPMMS.MSC for MMS treatment The format of each line is the same as for SMSYYMMDD_xxx.MSC / YYYMMDDHHMMxxxx.chpin:
msisdn:cost

2.2.4 Output Files

The output files are the following: <OFLC_RESULT_DIR>/YYYYMMDDHHMMxxxx.SAV As soon as the YYYYMMDDHHMM.chpin is treated by the SMP, it is saved into YYYYMMDDHHMM.SAV <OFLC_RESULT_DIR>/SMSYYMMDD_xxx.SAV As soon as the SMSYYMMDD_xxx.MSC is treated by the SMP, it is saved into SMSYYMMDD_xxx.SAV <OFLC_ERROR_DIR>/ YYYMMDDHHMMxxxx.chpin.xxxerr.RES This file indicates all the accounts which have been treated (with the date, the hour, the msisdn, the credit, the cost of the MMS) and the errors or problems that may occur. <OFLC_ERROR_DIR>/ SMSYYMMDD_xxx.MSC.xxxerr.RES This file indicates all the accounts which have been treated (with the date, the hour, the msisdn, the credit, the cost of the SMS) and the errors or problems have occured. <OFLC_ERROR_DIR>/ YYYMMDDHHMMxxxx.chpin.resok.RES (SMSYYMMDD_xxx.MSC.resok.RES) This file indicates all the accounts which have been treated (with the date, the hour, the msisdn, the credit, the cost of the SMS) and no errors or problems have occurred. <OFLC_ERROR_DIR>/asntool.RES This file outputs the legacy messages of the pps offline tool occurred while conversion and treatment of the MDV files.

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

11/2

For each successful charging, there is one line in .RES file showing how much money has been deducted from bonus credit and main credit. The format of this line is as follow:

20090909112023:904408686:5000:2000:3000:1 => Ok 20090909123028:122333457:4500:0:0:0 => NOK

a) Time - YYYYMMDDhhmmss b) MSISDN c) Amount requested to be charged d) Charged_Main e) Charged_Bonus f) Result Code

2.3 ERROR & EXCEPTION HANDLING BY OFLCS

This section describes the errors and exceptions that might occur while processing of records, and the approaches taken by the OFLCS to prevent or handle such conditions. The tickets in error are stored in error ticket file for further processing. Tickets in error are split in several error files in function of the error type. Tools have to be provided to filter and analyze error and to correct ticket error in order to replay the ticket. OFLCS generates alarm in case of error and exception. But OFLCS must reduce, as far it is possible the flow of alarm: One alarm per error ticket file can be generated instead of one per error ticket.

2.3.1 OFLCS INTERNAL ERROR

In case the OFLCS fails due to internal error (file access,), it dumps the present record in the configured error directory, in a file that is named exactly as the current record file with an extension ".procerr". The dump also contains the description of the error. It is up to the operator to correct if necessary the ICC problem.

2.3.2 OFLCS FILTERED RECORDS

In some cases, records can be filtered by OFLCS instead of the external mediation device. In such a case, it dumps the present record in the configured error directory, in a file that is named exactly as the current record file with an extension ".filterr". The dump also contains the filtering criteria parameter with its value. ERROR IN DECODING RECORD - ASN.1 ENCODING NOK In case the OFLCS fails to decode an ASN.1 encoded record, it dumps the present record in the configured error directory, in a file that is named exactly as the current record file with an extension ".fileerr". The dump also contains the description of the error.

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

12/2

2.3.3 DPE ERROR AT CE INTERFACE

In case of a DPE error at the CE interface, the OFLCS dumps the present record in the configured error directory, in a file that is named exactly as the current record file with an extension ".dpeerr". The dump also contains the description of the error. It is up to the operator to correct if necessary the ICC problem.

2.3.4 TIMEOUT AT CE INTERFACE

In case of a timeout at CE interface, the OFLCS service does not retry processing of the same record to avoid double charging. OFLCS dumps the original ticket in the configured error directory, in a file that is named exactly as the current record file with an extension ".dpeerr". The dump also contains the description of the error (timeout). It is up to the operator to check that the charging has not been done using the ticket identifier and may be the start date and time of the ticket. If the charging ticket does not exist, the ticket has to be processed again. CE REPLY NOK, RATING ERROR OR MISSING NFORMATION IN RECORD In case the CE replies NOK to any of the OFLCS request, or gives a rating error, or some mandatory information is missing in the record, the OFLCS dumps the present record in the configured error directory, in a file that is named exactly as the current record file with an extension ".ratingerr". The dump also contains the description of the error. The error description must be as detailed as possible, so that the operator can correct the error, and then the ticket could be replay for charging. OFLCS is able to handle the exhaustive list of all the CRE return codes (result code and sub result code). OFLCS analyses and maps the CRE return codes into OFLCS error type and error description.

2.3.5 TE TICKET SENDING NOK

In case of a error at the TE interface, the account is charged but the accounting ticket can not be sent successfully toward TE, OFLCS dumps the present record in the configured error directory, in a file that is named exactly as the current record file with an extension ".teerr". The dump also contains the description of the error. In this case, the account is charged therefore the accounting ticket is not sent. It is up to the operator to correct if necessary the ICC problem.

VIETNAM / VMS - ICC

Specifications for MMS/SMSMO offline charging Ed 01 Draft All rights reserved. Passing on or copying of this document, use and communication of its contents not permitted without written authorization

Network Applications Division

13/2