Charging Data Administration Siemens

Charging Data Administration

Contents
1 Charging Data Administration: Overview 3
2 Mobile Call Records 7
2.1 Functionality 8
2.2 MML Commands for MCR 22
2.3 MCR File Handling 32
3 Advice of Charge and Charge Unit Collection 45
3.1 AOC Function 46
3.2 Prerequisite 48
3.3 Mobile Zoning 50
3.4 Mobile Zones 58
3.5 Zoning for Fixed Network Calls 66
3.6 MML Commands 68
4 Administration of Mobile Thresholds 70
5 Interadministrative Charging 73
5.1 Functionality 74
5.2 Functional Structure 78
5.3 IACHASTA Schedules (for OUT=MET) 90
5.4 Traffic Distinction (for OUT=MET) 96
5.5 Counter Sets (Counters for OUT=MET, Extensions also for AMA) 100
5.6 Activation and Deactivation of IACHASTA 104
5.7 IACHASTA Saving for AMA Registration 106
5.8 IACHASTA Saving and Accounting for Meters 108
6 Network Facilities for Charging 111

MN2513EU09S1_0001 SSNC
1
© 2001 Siemens AG
 Siemens Charging Data Administration

7 Exercises 117
8 Solution 127

2 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

1 Charging Data Administration: Overview

MN2513EU09S1_0001 SSNC
3
© 2001 Siemens AG
 Siemens Charging Data Administration

Charging data administration can be divided into three main areas:

l Ticket production for mobile subscriber charges: Mobile call records (MCR).
The call data is recorded individually and collected in a disk file for every call and
within a call for the various sections. This data is handled in a post-processing
procedure at the billing center. Here the telephone bills are produced and the
statistics are collected. Specific MCRs can be created for the following call types:
Mobile originating call (MOC)
Mobile terminating call (MTC)
Interrogation/roaming (ROA)
Call forwarding (CF)
Short message service (SMS)
Emergency call trace
Transit call
l Provisioning of the tariff data for the advice of charge feature
The MSC calculates the tariff regulation for the call based on the directory number
of the subscriber called. These tariff regulations (so-called e-parameters) are con-
veyed to the calling mobile station, and from there they must compute the current
accumulation of charges.
l Interadministrative charging
For billing between different operators or for statistical purposes, it is possible to
define the traffic flow in an MSC (e.g. from all MSCs to the PSTN, from all BSCs to
the PSTN, from PSTN to the MSCs, etc.) and to trigger charge meters or produce
tickets for them.

4 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS SIEMENS SIEMENS

vis. MSC forwarding

A-party MSC

roaming
MOC
call forwarding
SIEMENS SIEMENS

mobile vis. MSC

subscriber A-party
call records
MTC
SIEMENS SIEMENS

inc. trunk group

transit
call records

MSN
advice of charge SIEMENS SIEMENS

parameters
vis. MSC
A-party
tariff
MOC description

SIEMENS SIEMENS

SIEM ENS SIEMENS

PLMN other
net 1
SIEMENS SIEMENS

SIEM ENS S IEMENS

interadministrative SIEMENS SIEMENS

SIEMENS SIEMENS
charging and
statistics

other
net 2

Fig. 1 Areas of charging for mobile application

MN2513EU09S1_0001 SSNC
5
© 2001 Siemens AG
 Siemens Charging Data Administration

6 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

2 Mobile Call Records

MN2513EU09S1_0001 SSNC
7
© 2001 Siemens AG
 Siemens Charging Data Administration

2.1 Functionality
Call records develop during any type of call and within this in different sections.
The following tickets are the most important ones that develop during service:
Mobile call records are encoded in ASN1. ASN1 facilitates high flexibility concerning
the customer specific ticket generation as well as its evaluation in the billing center.

Ticket Entity
MOC MSC of the calling party
MTC visited MSC of the called
party
Roaming Gateway MSC
MSC of the calling party
CF forwarding MSC
SCI MSC of the calling party
SMS SMS MOC MSC of the
sending party
SMS MTC MSC of the
receiving party
Emergency MSC of the calling party
Call Trace
Transit transit MSC

The opposite page shows examples of records and their contents. The details of the
record contents are not discussed any further here, as this would go beyond the
scope of this document.
The record application (MOC,ROA,MTC etc.) can be recognized by the so-called call
transaction type. Apart from that the records also contain data such as
IMSI/MSISDN/IMEI of served subscriber (served party), MSRN, served other
number, other party, third party, incoming/outgoing trunk group, basic services,
supplementary services, call duration, start of recording time etc.

8 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

MOC CFn
CFnRecord
MOCRecord
Record Record
•Call transaction type: MOC •Call transaction type: CFn
•Call transaction type: MOC •Call transaction type: CFn
•Served party: calling party •Served party : called party B
•Served party: calling party •Served party : called party B
•Other party: called party •Other party: called party C
•Other party: called party •Other party: called party C
•date/ time/ duration •Third party: calling party A
•date/ time/ duration •Third party: calling party A
•incoming/ outgoing trunk group •date/ time/ duration
•incoming/ outgoing trunk group •date/ time/ duration
•Service •incoming outgoing trunk group
•Service •incoming outgoing trunk group
•Supplementary service •Service
•Supplementary service •Service
•Suppl. service
•Suppl. service
MTC
MTCRecord SCI
Record SCIRecord
Record
•Call transaction type: MTC •Call transaction type:
•Call transaction type: MTC •Call transaction type:
•Served party : called party <SS action> *
•Served party : called party <SS action> *
•Other party: calling party •Served party : calling party
•Other party: calling party •Served party : calling party
•MSRN if GMSC=vis. MSC •date/ time
•MSRN if GMSC=vis. MSC •date/ time
•date/ time/ duration •Service
•date/ time/ duration •Service
•incoming/ outgoing trunk group •Supplementary service
•incoming/ outgoing trunk group •Supplementary service
•Service
•Service
•Supplementary service *) for invocation no separate record
•Supplementary service *) for invocation no separate record
ROA
ROARecord Short
Record ShortMessage
MessageRecord
Record
•Call transaction type: roaming •Call transaction type:
•Call transaction type: roaming •Call transaction type:
•Served party : called party SMS MOC/MTC
•Served party : called party SMS MOC/MTC
•Other party: calling party •Served party : calling party (MOC)
•Other party: calling party •Served party : calling party (MOC)
•MSRN called party (MTC)
•MSRN called party (MTC)
•date/ time/ duration •date/ time
•date/ time/ duration •date/ time
•incoming/ outgoing trunk group •Service: SMS
•incoming/ outgoing trunk group •Service: SMS
Transit
TransitRecord
Record Emergeny
EmergenyCall
CallTrace
Trace
Record
Record
•Call transaction type: transit
•Call transaction type: transit
•Served other number: calling party
•Served other number: calling party •Call transaction type: ECT
•Other party: called party •Call transaction type: ECT
•Other party: called party •Served party : calling party
•date/ time/ duration •Served party : calling party
•date/ time/ duration •Other party: called party
•incoming/ outgoing trunk group •Other party: called party
•incoming/ outgoing trunk group •date/ time
•date/ time
•Service: emerg. call
•Service: emerg. call

Fig. 2 Examples of records and record contents

MN2513EU09S1_0001 SSNC
9
© 2001 Siemens AG
 Siemens Charging Data Administration

2.1.1 Call Records in Various Paths: Mobile to Mobile Call

A mobile to mobile call consists of the sections mobile originating and mobile
terminating call. For the mobile originating call a MOC ticket is created; for the mobile
terminating call an optional roaming ticket (ROA) and an MTC ticket are created.

10 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS SIEMENS SIEMENS

visited interrogation
MOC HLR
MSC A

MSRN
called
party number

MOC ticket
ROA ticket

N
MS

R
MS
RN

SIEMENS SIEMENS

MTC ticket

visited
MSC B/VLR

MOC ticket mobile originating call ticket

ROA ticket roaming ticket
MTC ticket mobile terminating call ticket
Fig. 3 Tickets of a mobile to mobile call

MN2513EU09S1_0001 SSNC
11
© 2001 Siemens AG
 Siemens Charging Data Administration

2.1.2 Call Records in Various Paths: Mobile to Mobile Call with

Call Forwarding Unconditional
This call setup consists of a mobile originating call and, since a call forwarding
unconditional to a mobile subscriber is concerned, a call forwarding call with a
following mobile terminating call. An MOC ticket is created for the mobile originating
call. Since the call forwarding is already detected in the HLR or in the visited MSC, a
call forwarding ticket is created instead of the ROA ticket. Since the forwarded to
number again refers to a mobile subscriber, a ROA ticket and, in the visited MSC of
the subscriber called, a MTC ticket is created. The creation of the ROA tickets for call
forwarding unconditional and also for not reachable with IMSI detach (e.g. SIM card
removed) is to be released project specifically.

12 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS

HLR B1

on
gati
rro
nte
CF
i unconditional
no
w. to
f or

SIEMENS SIEMENS

visited interrogation
MOC MSC A HLR B2

CF ticket
MSRN
called
party number

MOC ticket
ROA ticket

RN
MS

MS
RN

SIEMENS SIEMENS

MTC ticket

visited
MSC B2/VLR

MOC ticket mobile originating call ticket

ROA ticket roaming ticket
MTC ticket mobile terminating call ticket
CF ticket call forwarding ticket
Fig. 4 Tickets of a mobile to mobile call incl. call forwarding

MN2513EU09S1_0001 SSNC
13
© 2001 Siemens AG
 Siemens Charging Data Administration

2.1.3 Call Records in Various Paths: Mobile to Mobile Call with

Call Forwarding Conditional

2.1.3.1 Call Forwarding Conditions in the Visited MSC of the Called Party /
GMSC Detected
The called party has an active 'call forwarding no reply' and does not respond, a 'call
forwarding on busy' and is engaged or a 'call forwarding not reachable' and no traffic
channel is available.
The MTC is switched through to the visited MSC of the called party like a normal
MTC, i.e. by means of the mobile station roaming number. The call forwarding
condition is detected in the visited MSC. The forwarded to number available in the
VLR is evaluated and can lead to another interrogation.
A MOC ticket and a roaming ticket are created in the visited MSC of the calling party.
A call forwarding ticket is created in the visited MSC of the forwarding party and, if
project specifically activated, another roaming ticket.
A normal MTC ticket is created in the MSC of the forwarded to party.

14 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS

HLR called party

provide
routing
info
send roaming
number
SIEMENS SIEMENS
MSRN
MSC calling party
SIEMENS SIEMENS CF
CFcondition
Conditionmet
met
MSC called party

CF ticket
MOC ticket
roaming
roaming ticket
ticket provide
routing
info

SIEMENS SIEMENS SIEMENS SIEMENS

HLR forwarded to MSRN

party MTC ticket

MSC forwarded to
party
send
roaming number

Fig. 5 Tickets for call forwarding condition met in visited MSC B

MN2513EU09S1_0001 SSNC
15
© 2001 Siemens AG
 Siemens Charging Data Administration

2.1.3.2 Call Forwarding Condition in the Visited MSC of the Calling Party /
GMSC Detected
The called party has an active 'call forwarding not reachable', the MSUB is IMSI
detached.
In the case of interrogation the HLR in the visited MSC of the called party asks for an
MSRN. As the mobile subscriber is detached at present, the VLR sends back the
message "absent subscriber". Now the HLR recognizes that the call forwarding con-
dition has been met and sends the "forwarded to number" back to the visited MSC of
the calling party. If applicable, the latter will perform another interrogation and set up
a call to forwarded to party.
A normal MOC ticket is created in the visited MSC of the calling party.
After the forwarded to number has been evaluated a CF ticket is also created there.
If the forwarded to party is a mobile subscriber of the own network again, the MSC
will also create a roaming ticket.
A normal MTC ticket is created in the MSC of the forwarded to party.

16 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS

HLR called party

call forwarding provide
routing
ticket info

MOC ticket

absent send
subscriber roaming
forwarded number
SIEMENS SIEMENS
to number
MSC calling party
SIEMENS SIEMENS

CF MSC called party

CFcondition
conditionmet
met

roaming ticket
SIM Card
project dependent

MSRN
provide MTC ticket
routing
info
SIEMENS SIEMENS SIEMENS SIEMENS

HLR forwarded to MSRN

party

MSC forwarded to
send party
roaming
number

Fig. 6 Call forwarding conditional detected in GMSC/vis. MSC calling party

MN2513EU09S1_0001 SSNC
17
© 2001 Siemens AG
 Siemens Charging Data Administration

2.1.4 Call Records in Various Paths: Short Message Service

Short Message Service originating

An SMS outgoing record is created for all outgoing short messages, if the short
message transfer has been confirmed by the SMS interworking MSC and the option
short message record has been switched on:
(MOD MSERVOPT:FEAT=CSMSMOC (national subscribers) or CISMSMOC
(international subscribers).
If the transfer is not successful, an SMS originating unsuccessful record can be
created depending on the network option:
(MOD MSERVOPT:FEAT=CUSMSMOC ).

Short Message Service terminating

An SMS terminating record is created for all incoming short messages, after the
mobile station has confirmed the reception of the short message and the option short
message record has been switched on:
(MOD MSERVOPT:FEAT=CSMSMTC (national subscribers) or CISMSMTC
(international subscribers).
If the transfer is not successful, an SMS terminating unsuccessful record can be
created depending on the network option:
(MOD MSERVOPT:FEAT=CUSMSMTC ).

18 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

PBX

SMS
center

SIEMENS SIEMENS

Interworking
MSC

Fo
r wa
re

r
su

d
sh SMS MOC successful/
lt

o rt
m unsuccessful ticket
Fo es
r wa sa
rd ge
sh
or SMS-
SUBMIT
SIEMENS SIEMENS
tm
es
sa
ge
MSC HI XARI
PLS CALL
SEPP
SMS MTC successful/ SMS-
unsuccessful ticket DELIVERY
ACKNOW-
LEDGE

Fig. 7 SMS MOC/MTC tickets

MN2513EU09S1_0001 SSNC
19
© 2001 Siemens AG
 Siemens Charging Data Administration

2.1.5 Call Records in Various Paths: Call Transfer

The precondition for a call transfer is that the transferring party has a call on hold and
another one in active state. Therefore we will begin with the creation of the pre-
conditions. In the following example the subsequent transferring party is the called
party for the first call and the calling party for the second call. We will not mention
roaming tickets in the following example.

A --> B
The mobile subscriber B (subsequent transferring party) receives a call from mobile
subscriber A. In the course of this a normal MOC ticket is created in the visited MSC
(A) of the calling party. A normal MTC ticket is created in the visited MSC (B) of the
called party.

A -> hold
Mobile subscriber B puts mobile subscriber A on hold. The supplementary service
"Call Hold" is entered in the mobile terminating call record of subscriber B. The
original call A->B is billed even during the hold.

B -> C
Mobile subscriber B performs a call to mobile subscriber C. In the MSC B a mobile
originating record is created for mobile subscriber B. In the MSC C a mobile terminat-
ing call record is created for the mobile subscriber C. The call B-> C is billed in the
normal way.

A<->C
Mobile subscriber B now performs a call transfer. Mobile subscriber A is only con-
nected to mobile subscriber C now. The call transfer is now either recorded in all
MOC and MTC records of mobile subscriber B (inline recording) or written into an
extra record (SCI invocation record).
The MOC ticket for mobile subscriber A and the MTC ticket for mobile subscriber C is
continued. The MTC ticket of mobile subscriber B, who caused the call transfer, is
completed as intermediate (first) ticket and as call duration contains the time of the
call to the call transfer. When releasing mobile subscriber B again receives an inter-
mediate (last) MTC ticket, which indicates the time of the call transfer. The MOC
ticket of mobile subscriber B is completed as intermediate (first) ticket and as call
duration contains the time from the call setup to C up to the call transfer. When
releasing mobile subscriber B again receives an intermediate (last) MOC ticket,
which indicates the time of the call transfer.

20 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

First
Firstintermediate
intermediate
SIEMENS SIEMENS

MTC
MTCticket
ticket MSC A
SS:
SS:CHCH/ /CT*
CT*
Call
Callduration:
duration:
Call
CallA->B
A->Buntil
untilCT
CT
Last
Lastintermediate
intermediate
MTC
MTCticket
ticket MSUB A
SS: CT*
SS: CT*
Call
Callduration:
duration:
CT
CTuntil
untilrelease
release SingleMOC
Single MOCticket
ticket
Call duration:
Call duration:
SIEMENS SIEMENS
Call
CallA->
A->BBuntil
untilrelease
release
MSC B

SingleMTC
Single MTCticket
ticket
Call duration:
Call duration:
Call
CallB->
B->CCuntil
untilrelease
release
MSUB B
First
Firstintermediate
intermediate
MOC
MOCticket
ticket
SS:
SS:CT*
CT*
*)*)ororSCI Call
Callduration:
SIEMENS SIEMENS

SCIrecord
record Call
duration:
Type: CT invocation
Type: CT invocation Call B->CCuntil
B-> untilCT
CT
MSC C
Last
Lastintermediate
intermediate
MOC
MOCticket
ticket
SS:
SS:CT*
CT*
Call
Callduration:
duration:
CT
CT untilrelease
until release MSUB C

Fig. 8 Records for call transfer (example)

MN2513EU09S1_0001 SSNC
21
© 2001 Siemens AG
 Siemens Charging Data Administration

2.2 MML Commands for MCR

2.2.1 Environment for the Creation of Call Records
Whether records for particular calls are created in an MSC or not depends on certain
general conditions. One of these conditions is the base activation of the MCR record
creation, and then the parametering of the incoming trunk group plays a role.
Certain record types require code point configurations other than the standard
configurations.
If advice of charge is performed in addition to the mobile call record generation or if
charge unit collection is demanded in the ticket, the parametering for the zoning must
also be changed.
The opposite table shows those cases in which special records are generated.

22 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

MCR Record Generation

Recordtype Condition

MOC · basic activation with ACT IAFEAT

· incoming trunk group: CR TGRP: GCOS=AMAREQD

· GCOS not equal ZON

· or for charge unit collection and advice of charge

GCOS=ZON and
CR MZOPT: CHTYPE=MOC, BILLING = AMA,...;
CF · basic activation with ACT IAFEAT

· incoming trunk group: CR TGRP: GCOS=AMAREQD

· GCOS not equal ZON

· or for charge unit collection and advice of charge

GCOS=ZON and
CR MZOPT: CHTYPE=CF, BILLING = AMA,...;
MTC · basic activation with ACT IAFEAT
· incoming trunk group: CR TGRP: GCOS=AMAREQD,....;

ROA · basic activation with ACT IAFEAT

· incoming trunk group: CR TGRP: GCOS=AMAREQD,....;

· special codepoint CR CPT:CODE=, AMA=YES, ORIG1=ORIGRO,....;

TRANSIT · basic activation with ACT IAFEAT

· incoming trunk group: CR TGRP: GCOS=AMATRANS,...;

· CR TGRP: GCOS not equal PSTNTGRP, because this value causes the
generation of a generic_common instead of a generic_mobil record
· GCOS not equal ZON

· or for charge unit collection

GCOS=ZON and
CR ZOPT: BILLING = AMA ,...;
· CRCPT:CODE=, AMA not equal YES

Fig. 9 Conditions for mobile call record creation

MN2513EU09S1_0001 SSNC
23
© 2001 Siemens AG
 Siemens Charging Data Administration

2.2.2 Base Activation

The base activation of the MCR record generation is executed my means of the MML
command ACT IAFEAT. The type to be entered here is MCR. The SIZE parameter
specifies the size of the billing file IA.ICMCR in PAM pages. One PAM page equals
2 kbyte.
If, in addition, the tickets are to be issued immediately, e.g. for emergency call trace
or threshold reporting, the type MCRI must also be activated.

2.2.3 Trunk Group Parametering

As already mentioned, the ticket creation depends on the parameters of the incoming
trunk group. The basic prerequisite for the ticket creation for MOC, call forwarding,
roaming and MTC is to set the parameter GCOS to AMAREQD (AMA required). If
you wish to generate transit tickets though, set the parameter GCOS to AMATRANS.
If the transit tickets are not to be generated in the MCR format (ASN1 GENERIC_M)
but in the AMA format (binary GENERIC_C), set the GCOS parameter to
PSTNTGRP. These parameter values exclude each other.
Existing trunk groups can be modified with ENTR TGDAT.

2.2.4 Announcement Groups

If a call leads to an announcement group you can determine whether a record is to
be written for this call or not during the parametering of the announcement group. In
this case set the GCOS parameter to CHARGABL.
If this parameter is not set, this call is regarded as not answered. In this case,
depending on the project option CALLATT, a record is either written or not.

24 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Basic Activation of MCR Generation

ACT IAFEAT: TYPE=MCR, SIZE=<size of disk file in PAM pages>;

DISP IAFEAT;

Trunk Group Parameters for MCR Generation

CR TGRP: TGNO= ,
GCOS=<AMAREQD|{AMATRANS|PSTNGRP}>,...;

ENTR TGDAT: TGNO= ,

GCOS=<AMAREQD|{AMATRANS|PSTNGRP}>,...;

DISP TGRP: TGNO= ;

Announcement Group Parameters for MCR Generation

CR ANGRP: TGNO= ,GCOS=CHARGABL,...;

DISP ANGRP: TGNO= ;

ENTR ANGCOS: TGNO= ,GCOS=CHARGABL;

Fig. 10 MML commands for MCR generation

MN2513EU09S1_0001 SSNC
25
© 2001 Siemens AG
 Siemens Charging Data Administration

2.2.5 Additional MML Commands for ROA Tickets

When setting up the code point (CR CPT) for the evaluation of the mobile station
roaming number, you can also specify the parameter AMA=YES. In this case a
roaming ticket is created upon evaluation of the MSRN. A prerequisite for this is the
project specific release of the feature and the correct parameter setup for the
incoming trunk group.
A code point should only be set with the parameter AMA = YES if you really wish to
generate a roaming ticket and only if you have received the mobile station roaming
number from the HLR. This situation can be recognized via the ORIG1 = ORIGRO
administered in the project data.

26 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Creation and Display of a Codepoint for ROA Tickets

CR CPT: CODE= <part of MSRN>, AMA=YES,

ORIG1= <ORIGRO>, DEST= <vis. MSC>,...;

DISP CPT: CODE=<part of MSRN>, DEST=<vis. MSC>;

Fig. 11 MML commands for roaming ticket

Mobile Project data

MOBILE PROJECT DESCRIPTION DATA

PROJECT IDENTIFIER (PROJECT) : XYZ

NUMBERING SCHEME

MOBILE COUNTRY CODE (MCC) : 26

MOBILE NETWORK CODE (MNC) : 02

.............................

EMERGENCY NUMBER (EMERGNO) : 110

LENGTH OF MSC EXTERNAL LACOD (MSCLACOD): 16
MSRN FORMAT (MSRNFORM): INAT
HANDOVER NUMBER FORMAT (HONFORM) : INAT

GENERAL DATA

MAXIMUM TIMES OF CALL FORWARDINGS (MAXCF) : 5

NO REPLY CONDITION TIMER DEFAULT VALUE FOR
CALL FORWARDING (RCTIMCFW): 20
CALL BACK (RCTIMCBC): 15
SPECIAL ORIGINATING MARK 1 FOR
CALL FORWARDING (ORIGCFW) : 100
HANDOVER (ORIGHO) : 130
ROAMING (ORIGRO) : 130
LOOP LTG FOR IN (ORIGLOOP): 150
UNSTRUCT. SUPPL. SERVICE DATA (ORIGUSSD): 160
CALL COMPLETION BUSY SUBSCRIB (ORIGCCBS):
IN (ORIG1IN) : 120

...........................

CASE B HANDLING ALWAYS IN GMSC (BALWGMSC): NO

SERVICE CLASS MARK MOC DEFAULT (SCMMODEF): B0101
SYSTEM IDENTIFIER (SYSIND) : GSM
SYSTEM MY TYPE (MYTYP) : NOT
MARKET IDENTIFIER (MARKETID): 0
SWITCH NUMBER (SWITCHNB): 0
SYSTEM DN (SYSTEMDN):
DEFAULT CARRIER ACCESS CODE (DFLTCAC) :
NATIONAL
SUPPL. SERVICE MAP CODE SCI CODE
-----------------+------------+------------

HOTBILL 245
INSCMMOC 241

Fig. 12 Roaming originating mark in the project data

MN2513EU09S1_0001 SSNC
27
© 2001 Siemens AG
 Siemens Charging Data Administration

2.2.6 Additional MML Commands for MCR with

Charge Unit Collection

Mobile calls
If the charges for mobile calls (MOC, CF, ROA etc.) are to be computed in the MSC
immediately in order to log them in the MCR or if advice of charge (see also chapter
on advice of charge) is to be carried out, you need to define the tariff regulations.
l The incoming trunk group must be marked to the effect that zoning is being carried
out. Zoning, as a rule, means the conversion of the received digits (e.g.
B-MSISDN) into a tariff regulation. The trunk group must be set up with the
parameter GCOS=ZON in this case.
l Mobile zone points are set up with the help of the command CR MZOPT. Digit
combinations which entirely or as a rule partially correspond to the received digit
combinations (e.g. B- MSISDN for MOC or the forwarded to number for CF) are
converted and assigned to a zone report (MZONO). For MOCs and CFs various
zone reports can be allocated; the system is informed of this with the parameter
CHTYPE = MOC/CF.
The billing parameter must be set to AMA in this case, as otherwise no ticket will
be generated. For more information on this see the section Advice of Charge.

PSTN or MSC calls

In case zoning for calls via an incoming trunk group from PSTN or other MSC or for
fixed subscribers is necessary in order to be able to carry out charge unit collection in
the transit tickets or in the ticket for PABX, for instance, the zoning for trunk groups
and fixed subscribers must be set up differently from the mobile specific zoning.
l The fact that zoning is being carried out must be indicated for calls via trunk
groups. The trunk group must be set up with the parameter GCOS=ZON in this
case.
l A zone point is set up with the MML command CR ZOPT. Here an allocation
between dialing information received and a zone is made. The zone refers to tariff
information, similar to mobile specific zone points.
The parameter billing must be set to AMA in this case, otherwise no ticket will be
generated. The parameter ZONE refers to a fixed network tariff zone. For more
information on this see the section Advice of Charge.
l The data set up in this manner can be displayed with the corresponding display
commands.

28 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Activation of Zoning in the Incoming Trunk Group

CR TGRP: TGNO=.....,
GCOS=ZON&AMAREQD[&
{AMATRANS|PSTNTGRP}],.....;

ENTR TGDAT: TGNO=.....,

GCOS=ZON&AMAREQD[&
{AMATRANS|PSTNTGRP}],.....;

DISP TGRP: TGNO=.....;

Creation and Display of a Mobile Zone Point (BSSAP TGRP)

CR MZOPT: MZONO=<mobile zone >,

CODE={<called party number>|
<forwarded to number>},
BILLING=AMA;
DISP MZOPT: MZONO=<mobile zone >,
[CODE={<called party number>|
<forwarded to number>}];

Creation and Display of a Fixed Network Zone Point (other TGRP)

CR ZOPT: ZONO=<zone number>,

CODE=<signaled called party number>,
BILLING=AMA;

DISP ZOPT: ZONO=<zone number>,

[CODE=<signaled called party number>];
Charges in Call records

ENTR CDTDAT: EXTNSD=CHARGE,....;

Fig. 13 MML commands for zoning

MN2513EU09S1_0001 SSNC
29
© 2001 Siemens AG
 Siemens Charging Data Administration

2.2.7 Example: Trunk Group Parameter for MCR

The opposite example requires you to perform advice of charge or charge unit
collection in the MSC.
The trunk groups coming from BSS and PABX contain the parameter GCOS =
AMAREQD and ZON. In other words, AMAREQD creates the basic prerequisite for
the ticket generation. Whether a ticket is really generated for the respective call
depends on the parametering of the mobile or fixed zone points (BILLING equal or
unequal AMA).
The trunk groups coming from PSTN and other PLMN entities were set up with the
GCOS = ZON, AMAREQD and AMATRANS. In this case a transit ticket is generated
for the transit connections, if this was set up correspondingly with
CR ZOPT:BILLING = AMA.

30 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

GCOS= GCOS=
SIEMENS

AMAREQD MSC AMAREQD

ZON
AMATRANS
ZON

PSTN BSSAP
AMAREQD
AMATRANS AMAREQD
ZON ZON

PLMN MIC Loop

CHARGABL AMAREQD
ZON

DAS PABX Loop

Fig. 14 Example of trunk group parameters

MN2513EU09S1_0001 SSNC
31
© 2001 Siemens AG
 Siemens Charging Data Administration

2.3 MCR File Handling

2.3.1 General
After the base activation of the individual call data administration (IA) MCR with ACT
IAFEAT the system sets up the file IA.ICMCR on both system disks. The size of the
file corresponds to the SIZE parameter for the feature activation.
After the end of the call or, in the case of long calls, after the GP timer T114 has
expired, the call data collected in the corresponding LTG is sent to the CP. In the
latter case it is necessary to keep to a certain ticket sequence:
First, (e.g. MOC), intermediate (e.g. MOC-intermediate), last ticket.
If in call modifications are performed, e.g. service change, intermediate tickets are
equally sent to the CP and buffered there. In this case the following sequence could
occur:
First, (e.g. MOC), intermediate (e.g. MOC-intermediate), last ticket (e.g. in call
modification).
The data is stored in a buffer within the CP. If the buffer is full the data is stored in the
cyclic file IA.ICMCR. The buffer can also be transferred to the disk file compulsorily,
e.g. to update the data before a file transfer (TRANSBUFFER:TYPE=MCR).
Additionally, the new command MOD IAFEAT allows the introduction of a safety
timer (parameter SAVTIMER, specified in minutes) after which the buffer contents
are automatically transferred to disk.
This periodical buffer transfer is possible for the following charging buffer types: AMA,
CDR, IARA, INA, ITR, LIR, MCR and OME.
Notes:
If an automatic or manual transfer of the buffer occurs while the safety timer is
running this timer is reset.
The default value is 0. This means, periodic saving to disk takes place every 2
minutes if the amount of the buffer data is equal to the block size.
When the value of SAVTIMER is not equal to 0, saving of all the buffer data to disk
takes place periodically according to the entered value.
An incomplete block is filled up with zeros. Due to the periodic saving, it is possible to
have a high amount of filled up zeros.

The file transfer for the MCR data can either be performed via FTAM or via Transfer
File (TRANS FILE:FILE=...;).
In case the records were stored on the CP disk, they can be displayed at the BCT
etc. with the MML command DISP MCR.

32 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

LTG

call data
SIEMENS call data
collection
collection
CP After end of call or intermediate:
1. depending on timer 114
2. in case of in call modification

MOC after MOC after

MOC MOC
buffer in call modif. in call modif.
buffer
TYPE=MCR
TYPE=MCR
T114 icm T114 release
If buffer full or SAVTIM expired or
TRANS BUFFER:TYPE=MCR;

ACT IAFEAT:
FEAT=MCR,
IA.ICMCR SIZE=
IA.ICMCR

TRANS FILE
FTAM
MCR
records DISP MCR:
SIEMENS
NIX DORF
DIGITS=..................,
FORMAT=...............;

Fig. 15 Record collection and storage

Display of MCR Records

DISP MCR : DIGITS= {A|B}-<digits>-<digit length>-{D|I}[,DATE=]

[,TIME=] [,FORMAT={TAB|HEX}];

Selective file transfer from CP buffer

MODIAFEAT: TYPE= ,SAVTIMER=<0,2,4,6,...,60>;

Fig. 16 MML commands

MN2513EU09S1_0001 SSNC
33
© 2001 Siemens AG
 Siemens Charging Data Administration

2.3.2 The Cyclic File IA.ICMCR

IA.ICMCR is a cyclic file. Cyclic file means that although the file has a fixed physical
beginning and a fixed physical end, the logical beginning and the logical end of the
file depend on the momentary writing and copying situation. In other words, the
logical end of the file can physically be before the logical beginning of the file, as the
file access is cyclic. For example, if the write pointer reaches the physical end of the
file, in the next step writing is continued after the header at the physical beginning of
the file.
Parts of the file that have already been written on, but not copied and released yet,
cannot be overwritten in the case of the IA.ICMCR file. In other words, if the write
pointer reaches this area, which must not be overwritten, the logical end of the file
has been reached and the file is filled 100 %. From now onwards records are lost.
Avoid this in any case by copying regularly and in good time.
If the file is copied onto another medium, it is always the area since the last copying
process which is copied, i.e. a delta copy is created. If several identical copies need
to be created, the system does this automatically. This is implemented by the fact
that a total copying process must always be completed with a REL CYCFILE. In other
words, a number of individual copying processes before a REL CYCFILE always lead
to copies of identical contents. After entering the command REL CYCFILE the copy-
ing area is released and can be overwritten with new records.

34 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

phys. begin
Header

write
Actual records
pointer
released during
log. REL CYCFILE
end Released Area
frozen after last
log. e.g. TRANS FILE
begin Copy Area without REL CYCFILE

Same
Actual records contents
phys. end
REL CYCFILE phys. begin
+ Header
new records

write Actual records

pointer

log. released during

end REL CYCFILE
Released Area

begin
Actual records
phys. end

Fig. 17 The cyclic file IA.ICMCR

File transfer

TRANS FILE: FILE= IA.ICMCR ,

VSNR=<volume serial number of e.g.MOD>,
[,PRONAM=<name of remote processor>]
[,USINF=<remote userid>-<remote account no>]
[,MODE=CR] [,COPMOD=POST]
[,RETPER=<retension period in days];

Release of a cyclic file

REL CYCFILE: FILE= IA.ICMCR [,UNCOND=YES|NO] ;

Fig. 18 MML commands for IA.ICMCR

MN2513EU09S1_0001 SSNC
35
© 2001 Siemens AG
 Siemens Charging Data Administration

2.3.3 Selective transfer of Charging Files

It is possible to copy only specific information (like MOC tickets only) from these
billing files:
l IA.ICMCR
l IA.ICITR
l IA.ICMIR
l IA.ICINA

The following example, where only records for MOC and MTC shall be transferred
(administration is different for CP and MP files; see also 2.3.6), illustrates this:
l Check if the number of safety copies for the billing file is two or more. A selective
transfer is only possible if this transfer is not the only one. The last copy process
always transfers the whole file contents for safety reasons.
CP: DISP FILE:FILE=IA.ICMCR,ALL=Y;
MP: DISP SAMAR:Name of SAM File Array=IA.ICMCR, Display action=attr;
l If required, set the number of safety copies to a value of two (or more).
CP: SET FGRPATT:FGRP=IA.ICMCR,SAFCOP=2;
MP: MOD SAMAR: Name of SAM File Array=IA.ICMCR, No. of safety copies=2;
l The selection criteria for the selective transfer are entered. Possibilities other than
the record layout are the supplementary services like Hot billing, or the success
status of a previously performed Hot Billing transfer via X.25 link.
CP+MP: ACT BILLREC:FILE=IA.ICMCR,RECLAY=MOC&MTC;
l Start the process for copying the selected data to magnetic tape. For MP files, the
file transfer is initiated by means of FTP from the Switch Commander.
CP: TRANS FILE:FILE=IA.ICMCR,VSNR=<tape>,...;
l The second copying process transfers the whole file contents to another magnetic
tape. This is necessary to prevent billing data from being lost. The file cannot be
released until after the transfer. This transfer resets the settings entered previously
with ACT BILLREC. They have to be entered again for the next selective transfer.
CP: TRANS FILE:FILE=IA.ICMCR,VSNR=<tape>,...;
l With the next command, the cyclic disk file is released again. That means old data
can now be overwritten. This is not necessary for MP files.
CP: REL CYCFILE:FILE=IA.ICMCR;
l If required, reset the number of safety copies.
CP: SET FGRPATT:FGRP=IA.ICMCR,SAFCOP=1;
MP: MOD SAMAR: Name of SAM File Array=IA.ACMCR, No. of safety copies=1;

36 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Selective File Transfer from CP

ACTBILLREC: FILE= [,RECLAY= ] [,SSV= ] [,SEL= ];

Selective File Transfer from MP

DISPSAMAR: name of SAM file array, display action;

MODSAMAR name of SAM file array, no. of safety copies, ;

ACTBILLREC: FILE= [,RECLAY= ] [,SSV= ] [,SEL= ];

Fig. 19 MML commands and Q3 tasks for selective billing file transfer

MN2513EU09S1_0001 SSNC
37
© 2001 Siemens AG
 Siemens Charging Data Administration

2.3.4 Client Record Formatting on CAP

It is possible to format the MCR records customer specifically. This customer specific
formatting is performed by Siemens according to the customer's wishes. The
corresponding setup commands are therefore not discussed in this document.
Usually the specific records are created during the transfer to the billing center or the
data carriers. If the data is also supposed to be filed on disk customer specifically,
use the feature client record formatting on CAP. Client record formatting on CAP
(CRFONCAP) is a project specific feature and needs to be activated with
MODMSERVOPT:FEAT=CRFONCAP. This service feature enables the records in
the IA.ICMCR file to have a customer specific format even on the disk.
This feature does not restrict the file transfer via FILE TRANSFER, FTAM and HOT
operation.

WARNING
If this feature is switched to active, the MCR records can no longer be dis-
played with DISP MCR.

38 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

LTG

SIEMENS
Call
Calldata
data
collection
collection
CP

MODMSERVOPT:
CRFONCAP
CRFONCAP
FEAT=CRFONCAP... SIEM ENS
NIX DORF

buffer
buffer
TYPE=MCR
TYPE=MCR
Customer specific
layout
HOT
operation
IA.ICMCR
IA.ICMCR

TRANS FILE
FTAM
MCR
records DISP MCR:
SIEMENS
NIXDORF
DIGITS=..................,
FORMAT=...............;

Fig. 20 Client record formatting on CAP

MN2513EU09S1_0001 SSNC
39
© 2001 Siemens AG
 Siemens Charging Data Administration

2.3.5 HOT Operation

HOT operation or HOT billing is a mobile subscriber supplementary service. It is
allocated to the mobile subscriber with ENTR GCSERV: GCSERV=HOTBILL,.. . As
HOT billing is no GSM specified supplementary service, it must be made known
project specifically (see DISP MPRDDAT). The accumulating records for MOC, MTC,
CF and SMS MOC/MTC are immediately transferred to a billing center via X25 link,
where they can be called up project specifically.
The billing center must confirm the transferred records. The transmitted records are
collected in the IA.ICMCR file as are those without HOT billing. Records that could be
transmitted successfully as HOT bill record obtain a flag indicating the successful
transmission.
If CRFONCAP was used parallel to HOT billing the HOT bill records are transmitted
to the billing center in the client format.

40 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

LTG

SIEMENS
Call data
Call data
collection
collection
CP
ENTR GCSERV:
GCSERV=HOTBILL,
HOT MSIN=....;
HOToperation
operation SIEMENS
NIXDORF

service
service
reco
buffer rd
buffer
TYPE=MCR
TYPE=MCR a ck
now
ledg
e PBX

X.25 Billing Center

Flag in record:
hot transfer result

MTC IA.ICMCR
TRANS FILE
MOC IA.ICMCR FTAM
CF
SMS MOC/MTC

Fig. 21 HOT billing

MN2513EU09S1_0001 SSNC
41
© 2001 Siemens AG
 Siemens Charging Data Administration

2.3.6 Charging Files on the MP Disk

If the MSC is configured with a Signaling System Network Controller (SSNC) instead
of a Common Channel Signaling Network Controller (CCNC), the MCR files can be
stored either on CP or MP disk.
An MP file is used if the parameter FILEAR=IA.ICMCR is specified in the command
ACT IAFEAT. This MP file has to exist before executing this command.
File transfer of MP files to a post-processing center is done by means of FTP over
the IP-interface of the MP. For CP files the X.25 interface of the CP is supported. The
feature Hot Operation still works, since these tickets are sent immediately from CP to
a postprocessing center and not from the disk file. therefor it requires the X.25 link on
the CP, although the files may be stored on either CP or MP disk.
If the charging files are stored on the MP disk it is neither possible to display records
with the command DISP MCR nor to transfer them with the command TRANS FILE.
File transfer of MP files done exclusively by means of FTP over the IP-interface of the
MP.
In addition to the MCR file, storage of charging files on MP disk is also applicable to
the file types ITR, INA, IARA and AMA.

42 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Trunks and SS7 Links

LTG

LTG
SS7 Links

SSNC ASN

LIC LTG
High DLU
Speed LTG
Links LIC
(1.5/2Mb/s) SN B
MP:SLT
AMXE
SC MP:SLT

MP:STATS

MBDH
MBDA
MB D
MP:SM
Ethernet MBDC
MP:OAM

IA.ICMCR

X.25 AMPC IOP:MB

CP113C

IA.ICMCR

Fig. 22 Charging files on MP disk

Filefeature

ACTIAFEAT: TYPE= ,FILEAR=<name> [,FILERECSZ= ]

[,RECFORM= ];

Fig. 23 MML command

MN2513EU09S1_0001 SSNC
43
© 2001 Siemens AG
 Siemens Charging Data Administration

44 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

3 Advice of Charge and

Charge Unit Collection

MN2513EU09S1_0001 SSNC
45
© 2001 Siemens AG
 Siemens Charging Data Administration

3.1 AOC Function

If this supplementary service is activated, data is sent from the MSC to the mobile
station with each mobile originating call (MOC) and each mobile terminating call
(MTC), which enables it to independently calculate the charge units accruing in the
course of a call:
l The supplementary service "advice of charge, information level" is used to display
the charge units at the mobile station, i.e. to inform the mobile subscriber of the
charges that have been incurred.
l The supplementary service "advice of charge, charging level" enables the mobile
station to calculate the charge units incurred, e.g. for automatic billing of the user
of the mobile station. With this supplementary service the important technical
attribute in the PLMN is that the mobile station must confirm the transmitted call
charge data, otherwise the connection is cleared down.
In the case of a mobile terminating call the charges depend on the home PLMN of
the mobile subscriber with this service; in the case of a mobile originating call, they
depend on the location of the mobile subscriber and also on the called party's
number. The methods employed for calculating the charge units, administering the
necessary mobile specific zones and tariffs, and concerning discrepancies between
the charge units shown at the mobile station and those actually metered in the MSC
are described in detail on the following pages.

46 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS
1

AOC
information 2
Zoning
Zoningand
andCharging
Charging
Database
Database

CODE
CODE

e-parameter:
e-parameter:
1 2
initial
initialunits
units
units
units pertime
per timeinterval
interval
must seconds
seconds per timeinterval
per time interval
........
........
AOC
charging
1 CONNECT
FACIITY( e-PARAMETER)
2 CONNECT ACKN
FACILITY ACKNOWLEDGE

Fig. 24 Advice of charge

MN2513EU09S1_0001 SSNC
47
© 2001 Siemens AG
 Siemens Charging Data Administration

3.2 Prerequisite
3.2.1 Trunk Group
l To be able to perform advice of charge for mobile subscribers who have been
allocated this general call service, or to be able to perform charge unit collection
(CUC) for MCR ticket, the incoming BSS trunk group needs to be set to the value
ZON in the parameter GCOS for zoning to actually be executed.
l A zoning origin ORIG2 can be assigned to the incoming BSS trunk group or the
cell. This is evaluated in the zoning similarly to the ORIG1 in the digit translator
and can be employed for origin dependent zoning. ORIG2 comprises a value
range of 1 to 153 for mobile calls. In REGEN files the ORIG2 values 255 and 254
can also occur. These are the internal default values that are entered for MOC or
CF in the zoning translator if no ORIG2 is used there. The ORIG2 of the BSSAP
trunk group has priority over the ORIG2 value of the cell unless the project specific
service feature "cell dependent charging" (MODSERVOPT:FEAT=CELLDCH) has
been released (sales feature) and activated.

3.2.2 Week Day Categories and Holidays

l The week day categories need to be specified in the MSCs for the respective
project. Here the categories of the individual days of the week are specified.
E.g. Monday to Friday working day, Saturday half weekend day and Sunday full
weekend day.
A second mobile specific calendar can, if project specifically released
(MODMSERVOPT: FEAT=MULHLDAY), be administered at the same time as the
general holiday calendar:
Common MOD WDCAT:FEAT= COMMON,...
Mobile specific MOD WDCAT:FEAT=MCHARGE,...
l Apart from the weekday calendar the holiday calendar also needs to be set up
per MSC. In this case a distinction is made between fixed holidays and movable
holidays. Fixed holidays are on the same date every year and therefore do not
require the respective year to be stated, movable holidays are on a different date
every year and therefore the respective year must be stated. A holiday category
such as: HH holiday half, HO holiday full or HN holiday national is assigned to the
respective entered date.

48 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS

Trunk Group
GCOS=ZON
ORIG2=1..153

ORIG2=1..153

Trunk Group Parameters for Zoning

CR TGRP: TGNO=..., GCOS=ZON&....[,ORIG2=1...153],...;

Cell Parameters for Zoning

CR INTCELL: LACOD=.., CI=..., BSCSPC=..., LMN=...

[,ORIG2= 1...153],..;

Fig. 25 Trunk group and cell parameters

MO TU WE TH FR SA SU

working day half full

weekend

December January February March

MO 7 14 21 28 4 11 18 25 1 8 15 22 1 8 15 22 29 *
TU 1 8 15 22 29 5 12 19 26 2 9 16 23 2 9 16 23 30
WE 2 9 16 23 30 6 13 20 27 3 10 17 24 3 10 17 24 31
TH 3 10 17 24 31 7 14 21 28 4 11 18 25 4 11 18 25
FR 4 11 18 25* 1* 8 15 22 29 5 12 19 26 5 12 19 26
SA 5 12 19 26* 2 9 16 23 30 6 13 20 27 6 13 20 27
SU 6 13 20 27 3 10 17 24 31 7 14 21 28 7 14 21 28
*) Christmas *) New Year *) Easter Monday
fixed holiday fixed holiday movable holiday

Weekday Categories

MOD WDCAT: FEAT={COMMON|MCHARGE},

WD= MO...SU,
WDCAT= {WO|EH|EF} ;

Holiday Calender for Holidays

CR HOLICAL: FEAT={COMMON|MCHARGE},
YEAR={<yy>|X},
DATECAT= <month>-<day>-{HH|HO|HN} ;

Fig. 26 Weekday categories and holiday calendar

MN2513EU09S1_0001 SSNC
49
© 2001 Siemens AG
 Siemens Charging Data Administration

3.3 Mobile Zoning

3.3.1 MML Command Structure MOC/CF
The MML commands for setting up the advice of charge parameters or for charge
unit collection consist of the following parts:
l Determination of an allocation of the selected code to the code valid for this zone
by means of the mobile zone point. It is possible to create zone points for MOC
and call forwarding. In other words, it is possible to specify different tariff in-
structions for both the application cases.
l The zone of the mobile zone point refers to a zone description. Here a tariff
category for fullrate, halfrate and call attempts is assigned to the zone.
l The tariff categories are specified by means of the switchover times and according
to the tariffs valid after the switchover.
l The tariffs valid and used in the tariff categories are specified with the so-called
e-parameters.
l In addition to the tariff instructions it is also possible to administer a so-called
scaling factor. The scaling factor is a multiplier of the total charging units for a
communication.

50 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

CODE mobile
mobilezonezonepoint
point
code
code
mobile
mobilezone
zone 5
call
calltype
typeMOC/CF
MOC/CF
CR MZOPT:
full rate CODE=....,
half rate CHTYPE= CF/MOC,
mobile
mobilezone zone MZONO=....;
zone
zone
e-parameter

full
fullrate
ratetariff
tariffcategory
category 4
half rate tariff category
half rate tariff category CR MZONE:
call
callattempt
attempttariff
tariffcategory
category ZONO=....,
FULL=.....,
11 12 1 HALF=....,
10 2 tarif
tarifcategory
category ATTEMPT=...;
9 3 tariff
8 4 tariff switchtime
switch time 2
7 6 5 tariff
tariff
ENTR MTARCAT:
MTARCAT=...,
SWTAR=
<time>-<tariff>-<wdcat>;
mobile
mobiletariff
tariff
e-parameter
e-parameter 1
ENTR MTAR:
MTAR=...,
En=...,...;
3
PLMN
PLMNtariff
tariff ENTR PLMNTAR:
e-parameter:scaling
e-parameter:scalingfactor
factor E3SCF=<scaling factor>,...;

Fig. 27 Structure of MML commands for mobile zoning MOC/CF

MN2513EU09S1_0001 SSNC
51
© 2001 Siemens AG
 Siemens Charging Data Administration

3.3.2 MML Command Structure MTC

If a mobile subscriber is roaming in a foreign network, e.g., the mobile subscriber
must then, unlike if he/she is in the own network, pay for the call from the home
PLMN to the foreign PLMN. This share of the incurred charges can be displayed to
the mobile subscriber by means of AOC. In this case it is necessary though, to
specify the charge units for MTC in the visited PLMN in all nets that have roaming
contracts. Nevertheless, the problem for the mobile subscriber is that, although the
used charge units are displayed, he/she usually does not know how much a charge
unit costs.
l It is possible to specify the corresponding e-parameters for any home PLMN by
means of the PLMN tariff.

52 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS

MTC
MTC

SIEMENS SIEMENS

home PLMN
e-parameter

foreign
PLMN

PLMN
PLMNTariff
Tariff
e-parameter
e-parameter
scaling
scalingfactor
factor ENTR PLMNTAR:
Ex....=
Ey....=....,..
NETW=MCC-MNC.;

Fig. 28 Tariff for MTCs

MN2513EU09S1_0001 SSNC
53
© 2001 Siemens AG
 Siemens Charging Data Administration

3.3.3 Mobile Tariffs

The mobile tariffs are specified with the MML command ENTR MTAR. Up to 522
different tariffs are possible. This MML command specifies the e-parameters E1, E2,
E4 up to E7 according to GSM 02.024. For mnemonic reasons the PARAMETER
names obtain a supplement to the respective e<number>.
The parameter values all have a range of 0...8191, but a different granularity. E.g.
units per time interval granularity 0.1: value range from 0 to 819,1. The e-parameters
to be specified have the following meaning:

e-parameter name meaning granularity

E1UPTI units per time interval (u/i) 0.1

E2SPTI seconds per time interval (t/i) 0.1
E4INU initial units (u) 0.1
E5UPDI units per data interval u/di 0.1
E6SPDI segments per data interval (seg/di) 1
E7SPITI seconds per initial time interval (t/i) 0.1

Apart from the displayed MML commands there are also commands for canceling
and modifying (CAN MTAR,MOD MTAR).

54 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Charge
units

E1
units per
time interval

E1
units per * scaling factor
time interval
E4
initial
units
E7 E2 E2
time
seconds per seconds per seconds per
initial time interval time interval
time interval

Begin of the call End of the call

Fig. 29 e-parameters

Entering a mobile tariff

ENTR MTAR : MTAR=1...522 ,E1UPTI= ,E2SPTI= ,E4INU= [,E5UPDI=]

[,E6SPDI=] ,E7SPITI= ;

Displaying a mobile tariff

DISP MTAR : TAR= ;

Fig. 30 MML command for mobile tariff administration

MN2513EU09S1_0001 SSNC
55
© 2001 Siemens AG
 Siemens Charging Data Administration

3.3.4 Mobile Tariff Categories

The mobile tariff category is identified by a number from 1 to 254 (MTARCAT) and
can be allocated to a zone with this identification number.
The mobile tariff category contains the validity instruction referring to the weekday
category (HH, HO, HN, WO, EF, EH) and time of the day for certain tariffs (defined by
ENTR MTAR). It is not the scopes that are specified for a tariff here, but the switch-
over or switch-on times. You can specify up to 32 tariffs and switchover times per
tariff category. A weekday category can contain up to 30 switchover times.
The example opposite defines the following tariff category:
Tariff 5 is to be valid on working days between 8 am and 6 pm.
Tariff 4 is to be valid on working days from 6 pm to 8 am of the following day.
Tariff 4 is also to be valid on weekends and on holidays.
In this case only the switchovers on working days need to be defined. In other words,
on the one hand the switchover to tariff 5 on working days at 8 am to switch over
from tariff 4. On the other hand the switchover to tariff 4 at 6 pm needs to be defined.
A switchover on weekends and holidays is not necessary, as a switchover to tariff 4
has already taken place on the previous working day.

56 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Entering the mobile tariff category

ENTR MTARCAT: MTARCAT= 1...254,

SWTAR= <hh>-<mm>-<tariff>-<weekday cat>
[& <hh>-<mm>-<tariff>-<weekday cat> ]
[....];

Modification of the mobile tariff category

MOD MTARCAT: MTARCAT= 1...254, NSWTAR=..., CSWTAR=...;

Cancellation of the mobile tariff category

CAN MTARCAT: MTARCAT= 1...254;

Display of the mobile tariff category

DISP MTARCAT: MTARCAT= 1...254;

Fig. 31 MML commands for tariff category administration

Mo
Tu
We Tariff 5
Th
Fr
Sa
Su Tariff 4
00.00 08.00 18.00 24.00

HO Tariff 4

ENTR MTARCAT: MTARCAT=2,

SWTAR = 8-00-5-WO & 18-00-4-WO;

Fig. 32 Example of mobile tariff category administration

MN2513EU09S1_0001 SSNC
57
© 2001 Siemens AG
 Siemens Charging Data Administration

3.4 Mobile Zones

A mobile zone represents a geographic distance from the call origin and is defined by
the tariff categories that correspond to the respective distance.
A mobile zone is identified by a zone number between 0 and 511. This zone number
serves to address the zone and, e.g., to allocate it to a mobile zone point. The zone
numbers 0 (no charge), 127 (charging in higher exchange), 254 (call forwarding), 255
(MOC) are not used or administered, may occur in REGEN runs, though.
In a zone the tariff categories are defined, that are to be used for the half rate
application, full rate application and call attempts. Call attempts should only be
administered if call attempt MCR generation (MSERVOPT:FEAT=CALLATT) is also
switched on.

58 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Creation of the mobile zone

CR MZONE: ZONO= 0...511, FULL= <tariff category>

[,HALF=<tariff category>]
[,ATTEMPT=<tariff category>];

Modification of the mobile zone

MOD MZONE: ZONO= 0...511, <FULL= <tariff category>,

HALF=<tariff category>,
ATTEMPT=<tariff category> >;

Cancellation of the mobile zone

CAN MZONE: ZONO= 0...511;

Display of the mobile zone

DISP MZONE: ZONO= 0...511;

Fig. 33 MML commands for mobile zone administration

MN2513EU09S1_0001 SSNC
59
© 2001 Siemens AG
 Siemens Charging Data Administration

3.4.1 Mobile Zone Point

A mobile zone point is the allocation of tariff instructions to a dialed and signaled
code (called party number, forwarded to number).
The tariff instruction can either be a previously defined zone (CR MZONE), an inter-
cept or another tariff instruction (no zoning, zoning in a higher ranking entity (next
MSC, intelligent net) etc.).

Parameter description:
l CODE
CODE consists of two information units a-b
a) indicates the dialed or signaled CODE with up to 15 digits hexadecimal.
b) indicates the mode of the code:
UNK unknown: the CODE is entered in the database as it was input
INAT international: the entered CODE is supplied with the international prefix (see
DISP MPRDDAT) in the database E.g. CODE=49172 => 0049172
NAT national: the entered code is stored in the database with the national prefix
COMB combined: the entered CODE is set up twice. In the national format and in
the international format. This mode only makes sense for the own country code.
The CODE is entered beginning with the own country code and followed by the
NDC. From this the system generates a zone point with preceding international
prefix and with omitted country code, but leading national prefix.
E.g.: CODE=49172 => 0049172 and 0172
If the entered CODE does not begin with the own country code, the code is
generated twice, with national and with international prefix. In other words, it is
questionable in how far this entry really makes sense. E.g.: CODE=172 => 00172
and 0172
l MZONO
The parameter MZONO consists of three information units a-b-c
a) specifies the zone defined in CR MZONE
b) specifies the ORIG2 value that is allocated to the incoming trunk group or the
internal cell.
c) specifies the position of the ORIG2 evaluation, i.e. after which digit location the
ORIG2 is evaluated. If this information unit is omitted the ORIG2 is evaluated
after the evaluation of all the digits.

60 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Creation of the mobile zone point

CR MZOPT: CODE=.., CHTYPE= ...,

{MINCEPT=...,MZONO=...., MZOCHA=....,}
[,TKZOINF=] [,MEPROC=] [,BILLING=] ;

Modification of the mobile zone point

MOD MZOPT: CODE= [,CHTYPE=]

{<,NMZONO= ,CMZONO=>
MZOCHA=....,MINCEPT=...,}
[,TKZOINF=] [,MEPROC=]
[,BILLING=] [,CBILLING=] ;

Cancelation of the mobile zone point

CAN MZOPT: CODE= [,INCEPT=];

Display of the mobile zone point

DISP MZOPT: {MINCEPT= [,CODE=] [,TKZOINF=]

MZOCHA= [,CODE=] [,BILLING=] [,TKZOINF]
MZONO= [,CODE=] [,BILLING=] [,TKZOINF=] };

Fig. 34 MML commands for mobile zone points

Parameter CODE = a-b

a: dialed or signaled number up to 15 digits hexadecimal
b: type of CODE
UNK unknown CODE is stored like entered
e.g. CODE=0049172 ==> Database: 0049172
INAT CODE is stored with prefixed international prefix from
international MPRDDAT
e.g. CODE=49172 ==> Database: 0049172
NAT national CODE is stored with prefixed national prefix from MPRDDAT
e.g. CODE=172 ==> Database: 0172
COMB CODE is stored in two versions once with international prefix
and own country code and once with national prefix
e.g. CODE=49172 ==> Database: 0049172 and 0172

Parameter MZONO = a-b-c

a: zone number created with CR MZONE
b: ORIG2 from CR TGRP or CR INTCELL
c: position of ORIG2 in the evaluation sequence

Fig. 35 Selected parameters

MN2513EU09S1_0001 SSNC
61
© 2001 Siemens AG
 Siemens Charging Data Administration

l CHTYPE
The charging type indicates whether this mobile zone point is to be valid for mobile
originating calls (value MOC) or call forwarding calls (value CF).
l MINCEPT
The mobile intercept gives you the option to route the call onto an intercept
UNOBDEn. The parameter consists of three information units a-b-c.
a) intercept
b) specifies the ORIG2 value that is allocated to the incoming trunk group or the
internal cell.
c) specifies the position of the ORIG2 evaluation, i.e. after which digit location the
ORIG2 is evaluated. If this information unit is omitted the ORIG2 is evaluated
after the evaluation of all the digits.
l MZOCHA
The parameter MZOCHA gives you the option to determine the zoning behavior
instead of a zone. The parameter consists of three information units a-b-c.
a) zoning characteristic. Here you can determine whether it is no longer
necessary to zone because zoning has already been performed in a preceding
entity, e.g. another MSC (CONZON), whether to zone in a higher ranking
entity, e.g. intelligent network SCP and whether to expect zoning information
from there (ZONINHI) or whether the call is free of charge (NOPULSE).
b) specifies the ORIG2 value that has been allocated to the incoming trunk or
internal cell
c) specifies the position of the ORIG2 evaluation, i.e. after which digit location the
ORIG2 is evaluated. If this information unit is omitted the ORIG2 is evaluated
after the evaluation of all the digits.
l TKZOINF
Similar to MZOCHA = ZONINHI this indicates whether to expect zoning infor-
mation form higher ranking entities. Contrary to ZONINHI this is optional and not
obligatory.
l BILLING
If you wish to generate MCR tickets for this call, set this parameter to AMA. If no
tickets are to be created, do not enter the parameter.

62 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Parameter CHTYPE

MOC Mobile zone point for MOC

CF Mobile zone point for CF

Parameter MINCEPT= a-b-c

a: Intercept for intercept handling: UNOBDEn

b: ORIG2 from CR TGRP or CR INTCELL

c: Position of ORIG2 in the evaluation sequence

Parameter MZOCHA= a-b-c

a: zoning characteristic

ZONINHI zoning in a higher ranking entity

NOPULSE charge free number

CONZON zoning in a lower ranking entity

b: ORIG2 from CR TGRP or CR INTCELL

c: Position of ORIG2 in the evaluation sequence

Parameter TKZOINF

YES zoning information is allowed from a higher ranking entity

NO zoning information is not allowed from a higher ranking entity

Parameter BILLING

AMA An MCR ticket is written for this call

Fig. 36 Parameters for mobile zone points

MN2513EU09S1_0001 SSNC
63
© 2001 Siemens AG
 Siemens Charging Data Administration

3.4.2 PLMN Tariff

On the one hand the PLMN tariff specifies the tariff for mobile terminating calls for the
respective roaming partner networks. On the other hand you can specify the scaling
factor here, by which the total units per call are to be multiplied. As parameters the e-
parameters e 1 to e 7 are offered here. The parameters e 1, e 2 and e 4 up to e 7
have already been described under ENTR MTAR. The parameter E3SCF represents
the scaling factor. It is subject to a granularity of 0.01, i.e. the total units are multiplied
by E3SCF value / 100.
The scaling factor must in any case be determined for MOCs for the own network.

64 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Entering of the PLMN tariff

ENTR PLMNTAR : NETW= <mob. country code>-<mob. network

code>
[,E1UPTI=] [,E2SPTI=] [,E3SCF=] [,E4INU=]
[,E5UPDI=] [,E6SPDI=] [,E7SPITI=] ;

Modification of the PLMN tariff

MOD PLMNTAR : NETW= <mob. country code>-<mob. network

code>
<,E1UPTI= ,E2SPTI= ,E3SCF= ,E4INU= ,E5UPDI=
,E6SPDI= ,E7SPITI= >;

Cancellation of the PLMN tariff

CAN PLMNTAR : NETW= <mob. country code>-<mob. network

code>;

Display of the PLMN tariff

DISP PLMNTAR : NETW= <mob. country code>-<mob. network

code>;

Fig. 37 MML commands for PLMN tariff administration

MN2513EU09S1_0001 SSNC
65
© 2001 Siemens AG
 Siemens Charging Data Administration

3.5 Zoning for Fixed Network Calls

For incoming calls via non-BSSAP trunks groups, PABX or other wired subscribers
the zoning needs to be set up for fixed network calls.

3.5.1 MML Command Structure

l The code received from a PABX, a fixed subscriber or via a trunk group is
evaluated and converted into a zone number. The zone number represents a geo-
graphic zone from the point of view of the respective MSC, which bears a
particular tariff instruction.
l The zone number is used to refer to a tariff switchover point. Here a tariff is
assigned depending on the week day category and the time of the day. If no
switchovers have been programmed (yet), a zone with a basic tariff is referred to.
l The tariff is determined by the so-called pulse communication. Here, similar to the
GSM e-parameters, it is determined how many unique charge units and/or how
many periodic charge units (units per time interval) are to be counted for this call.

66 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS
4
fixed CR ZOPT:
MSC CODE fixedzone
zonepoint
point CODE=....,
code
code
PSTN ZONO=....;
zone
zone
switch

or

tariff
tariffswitch
switch
11 12 1 zone
10 2 zone
9 3 switch
switchtime
time- -tariff
tariff
8 4
7 6 5

3 zone
zone
ENTR TARSW: zone
zone
TIME= basic
basictariff
tariff 2
WDCAT= ENTR TAR:
ZONE= ...., ZONE= ...,
NAME.. ; NAME=... ;
tariff
tariff 1
units
unitsper
pertime
time ENTR TAR:
NAME=... ,
PLSCOM= ....;

ticket

Fig. 38 Command structure of fixed network zoning

MN2513EU09S1_0001 SSNC
67
© 2001 Siemens AG
 Siemens Charging Data Administration

3.6 MML Commands

l A tariff is specified by means of the MML command ENTR TAR. The parameter
PLSCOM specifies the units to be counted. The first information unit indicates the
number of units. The second information unit specifies the duration of a time
interval and the third the validity duration of the unit/interval instruction. This
validity duration only makes sense if several PLSCOM values are linked with &
(PLSCOM SEQUENZ), as after the validity duration has expired, the next
PLSCOM value linked with & is branched to. If this one's validity duration also
expires, the next one is branched to etc. until the last PLSCOM value has been run
through.
The parameter SEQEND = indicates what is to happen after the PLSCOM
sequence cycle:
SEQEND=CYCLIC means that the cycle is restarted with the first value of the
sequence.
SEQEND= LIMIT means the call is released.
SEQUEND=NONCYC means the last sequence value is valid until the end of the
call.
l With ENTR TAR: ZONO = a zone is set up and a basic tariff allocated to it. This
basic tariff is valid until the first switchover time.
l ENTR TARSW is used to specify switchover times. From the point in time pro-
grammed with the parameters TIME and WDCAT onwards the tariff specified
under NAME is valid for this zone. The optional parameter Date indicates the first
time coming into effect of the switchover.
l CR ZOPT is used to perform an allocation between received CODE and the set up
zone, a zone characteristic or an INTERCEPT. The parameter ORIG2 specifies
the origin of the trunk group or the wired subscriber. If pulse metering is executed
in the project (DISP EXDDAT) the corresponding counter in the pulse metering for
number of calls or units can be determined with the parameters SUCACNTR and
SUCHCNTR. Billing indicates whether call metering (METERING) or ticket
recording (AMA) is to be performed for this call. If the parameter is set to AMA,
transit MCR records are written for trunk groups (GCOS=AMATRANS). If the
parameter is set to AMA, AMA tickets (binary in file IA.ICAMA) or MCR tickets can
be written for wired subscribers project specifically.

68 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Entering the tariff

ENTR TAR : NAME= <tariff name >,

PLSCOM= <units>[-<intervall>[-<duration>]&....]
[,SEQEND={NONCYC|CYCLIC|LIMIT}]

Creation of a zone with a basic tariff

ENTR TAR : ZONE=<zone number>,NAME= <tariff name> ;

Entering a switchover time

ENTR TARSW : ZONO= ,NAME= ,TIME= [,DATE=] [,WDCAT=] ;

Creation of a zone point

CR ZOPT : CODE= ,
{ZONO=<zone number>.| ZOCHA= | INCEPT= }
[,ORIG2=] [,BILLING=] [,SUCHCNTR=]
[,SUCACNTR=] [,MEPROC=] [,TKZOINF=];

Fig. 39 MML commands for fixed network zoning

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN2513EU09S1_0001 SSNC
69
© 2001 Siemens AG
 Siemens Charging Data Administration

4 Administration of Mobile Thresholds

Apart from the charging for billing or advice of charge the system provides charging
supervision, which can be used to issue warnings depending on the passed number
of charge units per call or to release the call.
l Charge unit warning for national calls
If a defined number of charge units for national calls has been exceeded, a
warning is issued on the corresponding output device (MOD MOBTHR:
MOBTHR=NATVAL-<1/10 units>;).
l Charge unit warning for international calls
If a defined number of charge units for international calls has been exceeded, a
warning is issued on the corresponding output device (MOD MOBTHR:
MOBTHR=INTVAL-<1/10 units>;).
l Release for national/international calls
If a defined number of charge units for national or international calls has been
exceeded, a warning is issued on the corresponding output device and the call is
released (MOD MOBTHR: MOBTHR=UNRELT-<1/10 units>;).
l Call duration supervision
In releases up to including SR5.0 the absolute call duration supervision was
patched project specifically. This absolute call duration limitation can be
administered per MML command (MOD MOBTHR: MOBTHR=DURSUP-<time in
minutes>;). If a fixed call duration for national or international calls is exceeded, a
warning is issued on the corresponding output device and, depending on the
feature ETREP, the call is released. By means of the feature ETHRTS11, the call
duration limitation may be limited to the service Telephony only.

70 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

national

SIEMENS SIEMENS

NATVAL

Inter-
national

INTVAL

UNRELT
11 12 1
10 2
9 3
8 4
7 6 5

DURSUP

SIEMENS
NIXDORF

Entering mobile thresholds

MOD MOBTHR : MOBTHR=<type>-<value>;

Displaying mobile thresholds

DISP MOBTHR : MOBTHR=<type>;

Fig. 40 Charging mobile thresholds

MN2513EU09S1_0001 SSNC
71
© 2001 Siemens AG
 Siemens Charging Data Administration

72 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

5 Interadministrative Charging

MN2513EU09S1_0001 SSNC
73
© 2001 Siemens AG
 Siemens Charging Data Administration

5.1 Functionality
"Interadministrative charging and statistics" (IACHASTA) is a procedure for charging
data billing between various operators or networks or for ascertaining statistics. To do
so you can install test points at the incoming or outgoing traffic flow, where charge
meters are counted or AMA (automatic message accounting) tickets are written. The
meter data or AMA tickets are collected on the system disk and transmitted to a
billing center for post-processing.
In the example on the opposite page it is possible to imagine that the traffic flow in
the gateway MSC to and from the PSTN should be monitored and that corresponding
meters should be counted or the AMA data ascertained. Registration points could be
installed for the following types of traffic flow:
l From MSC1 to the PSTN
l From MSC2 to the PSTN
l From the PABX to the PSTN
l From the PSTN to the MSC1
l From the PSTN to the MSC2
l From the PSTN to the digital announcement system
l From the PSTN to the PABX

74 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS

MSC 1

PLMN PSTN

N
SIEMENS SIEMENS
MS
SIEMENS SIEMENS

PABX Gateway Exchange

MSC

SIEMENS SIEMENS

MSC 2
Interadministrative
Charging and Statistics:
•Counters
•Tickets

DAS

Fig. 41 Principle of IACHASTA

MN2513EU09S1_0001 SSNC
75
© 2001 Siemens AG
 Siemens Charging Data Administration

Imagine the heart of the IACHASTA registration as a matrix, which on the one hand
covers all definable (administrable) incoming traffic streams and on the other hand
covers all definable (administrable) outgoing traffic streams. The point of intersection
of the incoming or outgoing traffic streams then results in traffic flow through the MSC
and generates the IACHASTA test point or registration point. Counting with meters or
AMA data recording is carried out at such a registration point.

76 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

SIEMENS SIEMENS

MSC 2

PABX

SIEMENS SIEMENS DAS SIEMENS SIEMENS

MSC 1 PSTN
exchange

incoming

outgoing
Registration point
e.g. from PSTN to MSC1
•AMA
•Counter

Fig. 42 IACHASTA registration points

MN2513EU09S1_0001 SSNC
77
© 2001 Siemens AG
 Siemens Charging Data Administration

5.2 Functional Structure

So-called registration points (IACRGPT) for recording the corresponding traffic are
defined for data creation. Such a registration point usually consists of a combination
of incoming and outgoing registration objects (IACOBJ). However, it can contain only
one outgoing and thus all incoming or only one incoming and thus all outgoing
registration objects. A registration object is a group of one or more switching
elements. A switching element can be a trunk group, a directory number or a
recorded announcement machine etc.

78 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Switching Element
e.g.
Announcement
Switching Element
Trunkgroup
e.g.
PABX etc.
Announcementgroup
Switching element
Trunkgroup IACOBJ
e.g.
PABX etc.
announcement group
Group of switching
trunk group
elements
PABX etc. Set of switching
elements forms
(max 8191)

e.g.
incoming

IACRGPT IACRGPT
IACHASTA registration IACHASTA registration
point point
Combination of IACOBJ Combination of IACOBJ
for which the traffic for which the traffic
registration has to registration has to
be executed with AMA be executed with AMA
or meters or meters
(max 32767) (max 32767)
e.g.
outgoing
IACRGPT IACRGPT
IACHASTA registration IACHASTA registration
point point
Combination of IACOBJ Combination of IACOBJ
for which the traffic for which the traffic
registration has to registration has to
be executed with AMA be executed with AMA
or meters or meters
(max 32767) (max 32767)

Fig. 43 Structure of IACHASTA

MN2513EU09S1_0001 SSNC
79
© 2001 Siemens AG
 Siemens Charging Data Administration

5.2.1 IACHASTA Switching Elements

Definition of switching elements

l IACHASTA can be defined for the following switching elements:
Private branch exchanges (PBXs)
Digital line units (DLUs)
Directory number blocks (DNs)
Trunk groups (TGRPs)
Announcement groups (ANGRPs)
Statistical indices in zone points (CR (M)ZOPT:STAT=)

TIP
The statistical index can't be used in ROUTEs any longer, as it was possible in older
releases.

80 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

own network other SIEMENS SIEMENS

SIEMENS SIEMENS
network

TGRP
TGRP

Network node
with
IACHASTA
SIEMENS SIEMENS
SIEMENS
PBX
DN
Network node
with
IACHASTA
wired
subscriber
PABX DLU

ZONING ANGRP
CRZOPT:
STAT=
DAS
CRMZOPT:
STAT=

Fig. 44 Switching elements

MN2513EU09S1_0001 SSNC
81
© 2001 Siemens AG
 Siemens Charging Data Administration

5.2.2 IACHASTA Objects

Definition of IACHASTA objects

An IACHASTA object is formed from one or more switching elements which belong
together. An IACHASTA object defines a traffic flow to which a registration point is
assigned to create the corresponding billing data (AMA or meter) for this incoming or
outgoing traffic flow. The IACHASTA object is identified with a name. Up to 8192
IACHASTA objects can be defined.

82 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

IACHASTA Object:
Switching Elements

TGNO= BWMSC1
TGRP
TGNO= ANNO1 OWN
ANGRP
TGNO= BWMSC2
TGRP

TGNO= BW49F NATFOR

TGRP

TGNO= BW45F
TGRP INTFOR
TGNO= BW43F
TGRP

DN= 335
PABX
PABX
DN= 327
PABX

Fig. 45 Example of definition of IACHASTA objects

MN2513EU09S1_0001 SSNC
83
© 2001 Siemens AG
 Siemens Charging Data Administration

MML commands
An IACHASTA object is defined with the MML command CR IACOBJ, canceled with
CAN IACOBJ and displayed with DISP IACOBJ. Note that when performing the setup
only one switching element can be entered per MML command. If you wish to have
several switching elements in the object, repeatedly enter the MML command with
the same object name. It is permitted to join various switching element types
(ANGRP, TGRP etc.) within one object.

84 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Creation of an IACHASTA object

CR IACOBJ: OBJ=<object name>,

{ANGRP=<announcement group number>,
DLU=<dlu number>,
DN=<directory number>, [LAC= <loc. area code>]
[,PBX=YES],
STAT=<statistic counter number>,
TGNO=<trunk group number>};

Display an IACHASTA object

DISP IACOBJ {OBJ=<object name> or X,

ANGRP=<announcement group number>,
DLU=<dlu number>,
DN=<directory number>, LAC= <loc. area code>
[,PBX=YES],
STAT=<statistic counter number>,
TGNO=<trunk group number>};

Cancel an IACHASTA object

CAN IACOBJ OBJ=<object name> ,

{ANGRP=<announcement group number>,
DLU=<dlu number>,
DN=<directory number>, LAC= <loc. area code>
[,PBX=YES],
STAT=<statistic counter number>,
TGNO=<trunk group number>};

Fig. 46 MML commands to create an IACHASTA OBJECT

MN2513EU09S1_0001 SSNC
85
© 2001 Siemens AG
 Siemens Charging Data Administration

5.2.3 IACHASTA Registration Points

Definition of IACHASTA registration points

An IACHASTA registration point consists of the following components:
l The registration type indicates whether registration takes place via meter or AMA.
If registration is done using a meter, further steps such as definition of the
counters, the transmission medium, the counter switching system, etc. are
required to define the registration. If the traffic is always registered using AMA,
creation of registration points can be avoided and the AMA registration for the
whole traffic can be started.
l Combination of IACHASTA objects
A registration point consists of one, several or no incoming IACHASTA objects and
of one, several or no outgoing objects.
If no object for incoming or outgoing traffic is assigned (although at least one
object is required), this means that registering is done for the entire incoming or
outgoing traffic.
A registration point which contains only incoming or outgoing objects is referred to
as a "single-sided registration point".
A registration point which contains both incoming and outgoing objects is referred
to as a "double-sided registration point".
If an object is used in both incoming and outgoing direction, the registration point
can be identified by the object/object combination alone. Therefore it is not
necessary to assign an identification name to the registration point. The advantage
is that no names are wasted. This is important because 32,767 registration points
can be created and only 8,191 can have a name.
A registration point without a registration point name is referred to as an
"anonymous registration point".
If several objects are used both in incoming and outgoing direction, the registration
point must be identified with a registration point name.
A registration point which contains a registration point name is referred to as a
"named registration point".

86 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Type of registration

AMA Meters

Combination of objects

Type Description

Single-sided registration point The registration point contains

either just incoming or just outgoing
objects.

Double-sided registration point The registration point contains both

incoming and outgoing objects.

Anonymous registration point The registration point contains

exactly one incoming and one
outgoing object. The registration
point does not get any name.

Named registration point The registration point contains

more than one incoming or one
outgoing object. The registration
point needs a name.

Registration schedule for METERING

A registration point contains a reference to a time schedule.

Will be discussed under IACHASTA schedules

Fig. 47 Registration points

MN2513EU09S1_0001 SSNC
87
© 2001 Siemens AG
 Siemens Charging Data Administration

MML commands
An IACHASTA registration point is defined with CR IACRGPT. If an anonymous
registration point is defined, an object definition is sufficient for the definition. If a
registration point is to consist of several destination or origin points, the objects must
not be linked with "&". In this case the command for the first object combination is
provided with a registration point name. The other objects are entered by repeatedly
entering CR IACRGPT while inputting the same registration point name.

88 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Creation of an IACHASTA registration point

CR IACRGPT: <OBJORIG=< originating object name >,

OBJDEST=< destination object name >>,
OUT={MET|AMA},
[SCHED=<schedule number>]
[,RGPT=<registration point name>];

Display of an IACHASTA registration point

DISP IACRGPT {<OBJORIG=< originating object name >,

OBJDEST=< destination object name >>,
,RGPT=<registration point name>};

Fig. 48 MML commands for registration point administration

MN2513EU09S1_0001 SSNC
89
© 2001 Siemens AG
 Siemens Charging Data Administration

5.3 IACHASTA Schedules (for OUT=MET)

Definition
If an IACHASTA registration point is used for metering it is possible to assign a so-
called schedule. A schedule offers the possibility to count in various counter groups
(so-called "time groups") depending on the time of day and weekday category. A
maximum of 16 IACHASTA schedules each with up to 6 time groups is possible in
the system. The number of time groups must be stipulated before they are assigned
to a schedule. The validities can be entered in 15 min. increments. Time group 1 is
defined as a standard to be valid from 0:00 to 24:00 o'clock for every weekday
category and cannot be changed. Time group 1 therefore covers all periods which
are not covered by the individual time groups 2..6. When defining time groups, note
that a validity period and not a switchover time must be defined.

90 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

IACHASTA Object

schedule n

TIMEGROUP n
valid
IACHASTA Object WO - HO
RGPT
09.00 - 18.00 08.00-18.00

TIMEGROUP COUNTERS
2
valid
TIMEGROUP 1 - HN
00.00
WO HH HO 0.800-18.00
valid

6
WO HH HO HNCOUNTERS
EH EF

x.
ma
n max.1 6
00.00 - 24.00
WO = WORKDAY
HH = HALFHOLIDAY INTERN. COUNTERS
HO = HOLIDAY INTERN.
HN = HOLIDAY NATIONAL
EH = WEEKEND HALF
EF = WEEKEND FULL

Fig. 49 Time groups of a registration point

MN2513EU09S1_0001 SSNC
91
© 2001 Siemens AG
 Siemens Charging Data Administration

Example
The example on the opposite page shows a time schedule definition. From 7.00 am
to 9.00 am and from 6 pm to 12 pm on working days counting is done in time group 2
and from 9.00 am to 6 pm in time group 3. In the non-defined time counting is done in
time group 1. From 8.00 am to 6 pm on international holidays counting is done in time
group 2. During the non-defined time counting is done in time group 1.

92 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

TG 3 TG 2 TG 3

07.00 09.00 18.00

TG 1
WO

00.00 24.00

TG 2

08.00 18.00
TG 1
HO

00.00 24.00

TG 1
other days

counting in :
TG 1 : default every day 00.00 - 24.00
TG 2 : international holiday 08.00 - 18.00
working day 09.00 - 18.00
TG 3 : working day 07.00 - 09.00 & 18.00 - 24.00

Fig. 50 Example of counting in different time groups for one schedule

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN2513EU09S1_0001 SSNC
93
© 2001 Siemens AG
 Siemens Charging Data Administration

MML commands
You need to generally determine how many time groups are used for the system.
This is done with the MML command ENTR IACSET. The number of time groups can
be specified to be a number between 1 and 6. This specification needs to be
performed before setting up the first registration point with OUT = MET.
The schedule itself is specified with MOD IACSCHED. Here you determine how to
count at which time of the day for a particular weekday category. Note that contrary
to the switchover definitions for fixed networks or mobile calls, you need to define an
interval and not a switchover time. Switching over to another defined time group or, if
none is defined, to time group 1 is done automatically at the end of the interval.

94 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Entering the maximum number of time groups

ENTR IACSET: TIMGRPMX=<max. number of time groups>,...;

Definition of the schedule

MOD IACSCHED: SCHED=<schedule number>,

TIMGRP=<time group number>,
TIME=<time range1>[&< time range 2>
[&<time range 3>]], WDCAT=<weekday category>;

Fig. 51 Definition of a schedule

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN2513EU09S1_0001 SSNC
95
© 2001 Siemens AG
 Siemens Charging Data Administration

5.4 Traffic Distinction (for OUT=MET)

Traffic distinction definition
The traffic flow defined by a registration point can be subdivided again according to
the traffic type after time-dependent assignment to different time groups. The traffic of
a registration point can either be assigned according to the "transmission medium
required" (TMR) or according to the subscriber category (for wired subscribers):
l Distinction according to TMR
Up to 4 so-called traffic groups can be defined for assignment according to TMR.
Each of these traffic groups is assigned to a transmission medium and obtains the
corresponding counter sets.
The authorized transmission media are:
3.1 kHz audio (e.g. fax)
Speech (e.g. telephony)
64 kbit/s (e.g. data digital)
64 kbit/s with fallback (e.g. 7.1 kHz speech with fallback)

96 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

IACHASTA object

IACHASTA object
RGPT

Time
group 6
Traffic group 1 with counters
for e.g. 64 kbit/s
TrafficTraffic
groupgroup
1 with2counters
with counters
for e.g. 64 kbit/s Fallback
for e.g. 64 kbit/s
Traffic group 3 with counters
Traffic group 2 with counters
Time for e.g. Speech
for e.g. 64 kbit/s Fallback
group 1 Traffic group 4 with counters
Traffic group 3 with counters
for e.g. 3.1kHz Audio
for e.g. Speech
Traffic group 4 with counters
for e.g. 3.1kHz Audio

Fig. 52 Distinction according to TMR

MN2513EU09S1_0001 SSNC
97
© 2001 Siemens AG
 Siemens Charging Data Administration

MML commands
The number of traffic groups to be used in the system must be specified with ENTR
IACSET before the defining the first registration point.
MOD IACTRADI is used to define a traffic distinction. The application of the max. of 4
traffic groups is defined with the parameter TRADRP1..4. In other words, it is
possible to allocate one or several TMR or line categories to a traffic group.

98 SSNC MN2513EU09S1_0001
© 2001 Siemens AG
Charging Data Administration Siemens

Entering of the maximum number of traffic groups

ENTR IACSET: TRAGRPMX=<max. number of traffic groups>,...;

Definition of the traffic groups

MOD IACTRADI: RGPTTYPE={SINGLE|DOUBLE}, DISTINCT=TMR,

TRAGRP1=....[,..[.,... [TRAGRP4=....]]] ;

Fig. 53 MML commands for traffic distinction

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN2513EU09S1_0001 SSNC
99
© 2001 Siemens AG
 Siemens Charging Data Administration

5.5 Counter Sets (Counters for OUT=MET, Extensions

also for AMA)
Definition of counter sets
A counter set consists of a number of individual counters. Some of these counters
are standard and some can be switched on and off using an MML command for all
registrations of the network node.

100 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

Counters for IACHASTA

Counter Standard or administrable

Call duration standard

Number of seizures (call standard

attempts)

Seizure time before B-side standard

answer

Number of successful calls standard

or including number of
unsuccessful calls ENTR CDTDAT:
MARKS=UCALLIAC,..

Call charges on A-side ENTR CDTDAT:

EXTNSD=CHARGES,..

Call charges from B-side over ENTR CDTDAT:

trunk EXTNSD=BMETPULS,..

Fig. 54 Counters for IACHASTA

MN2513EU09S1_0001 SSNC
101
© 2001 Siemens AG
 Siemens Charging Data Administration

MML commands
The counter or AMA records can be modified with the help of the MML command
ENTR CDTDAT (enter call data treatment data).
The parameter EXTNSD (extra non standard) specifies whether the charge units are
to be recorded in the ticket or whether a special counter is to be installed for this. This
parameter can also be used to switch on the trunk monitoring count.
MARKS=UCALLIAC is used to also count the unanswered calls instead of only the
answered calls.

102 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

Modification of IACHASTA Counters/Records

ENTR CDTDAT: <EXTNSD=<CHARGE|BMETPULS>,

MARKS=UCALLIAC,
REC={IACAMA|IACMET}>,...;

Fig. 55 MML commands for counter/record administration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN2513EU09S1_0001 SSNC
103
© 2001 Siemens AG
 Siemens Charging Data Administration

5.6 Activation and Deactivation of IACHASTA

IACHASTA with meters and with AMA must be activated after input of the appropriate
registration command. The activation cannot be carried out for the individual
registration points, but must be carried out for particular registration types. An active
registration can be deactivated again.
l Activation of meter registration points:
All single-sided registration points
All double-sided registration points
All MET registration points (mixed)
l Activation of AMA registration points:
All AMA registration points
Registration of all traffic flows without ever defining a registration point
l Deactivation of meter registration points:
All single-sided registration points
All double-sided registration points
All MET registration points (mixed)
l Deactivation of AMA registration points:
All AMA registration points
Registration of all traffic flows without ever defining a registration point.

104 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

Activation / deactivation of meter registration points

Single-sided registration points
Double-sided registration points
All meter registration points

Activation / deactivation of AMA registration

All AMA registration points
All traffic flows without registration points

Fig. 56 Activation of different IACHASTA registrations

Activation/deactivation of IACHASTA

ACT IACRG: OUT={AMA|MET},

RGTTYPE={SINGLE|DOUBLE|MIXED},
[BEG=<begin time>[,[ TER=<end time>,]
[ALLTRAF=YES,]
[FILEEXT=<filename extension>];

DACT IACRG: OUT={AMA|MET},

RGTTYPE={SINGLE|DOUBLE|MIXED},

Fig. 57 MML command for activation/deactivation of different IACHASTA registrations

MN2513EU09S1_0001 SSNC
105
© 2001 Siemens AG
 Siemens Charging Data Administration

5.7 IACHASTA Saving for AMA Registration

Description of saving
l Like other "call data recording features", IACHASTA requires a basic activation if
you wish to record with AMA.
IARA-type feature activation
Definition of the file size (default 30 Mbyte/15000 PAM pages)
Definition of the number of files (1 or 2 files)
l Before the AMA file is transferred to another medium (FTAM, file transfer to
tape, etc.) the data must be put into final condition. This is done in the normal way
by transmitting the transfer buffer.
Updating the AMA disk file
l The transfer takes place in the usual way, i.e. with TRANSFER FILE or the
corresponding FTAM commands.
l The disk file must be re-enabled after the transfer.

106 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

LTG

SIEMENS
Call
Calldata
data
collection
collection
CP After end of call or intermediate:
1. Depending on timer 114

buffer
buffer
TYPE=IARA
TYPE=IARA

If buffer full or
TRANS BUFFER:TYPE=IARA; ACT IAFEAT:
FEAT=IARA,
SIZE=
NUMFILE= {1|2}
IA.ICMCR
IA.ICIAR1
IA.ICIAR2

FTAM 2 file in parallel via 2 x.25 links

TRANS FILE

Fig. 58 IACHASTA saving for AMA registration

Basic activation/deactivation of IACHASTA

ACT IAFEAT: TYPE=IARA,

SIZE= <disk size in pam pages>,
NUMFILES={1|2};

Fig. 59 MML command for IACHASTA AMA basic activation

MN2513EU09S1_0001 SSNC
107
© 2001 Siemens AG
 Siemens Charging Data Administration

5.8 IACHASTA Saving and Accounting for Meters

Description of saving

Backup
Backup of the counters from the common memory onto the disk file CA.IC.UCHA
takes place hourly. The counters on the disk are added up and set back in a common
memory.
No recovery post-processing activities are necessary after an ISTART 2 G, because
the old CA.IC.UCHA was saved as
CA.IC.UCHA. <3-place day ><2-place hour><1-place sequence number>. A new
CA.IC.UCHA is created for the new APS.
l Billing
At the end of a registration order (ACTIACRG:TER=) or at the end of the month a
billing file is created from the backup file and the counters of the backup file are set
back. If a billing file is to be created manually before the end of the month, before
expiration of the registration order or after a fallback, this can be done with the
MML command EDIT MET. The billing file is created with the following file name:
CA.IR.rnnns.fffff

r= S: Single-sided registration
D: Double-sided registration
M: Mixed registration
nnns If fewer than 11 account files are created per day, nnn corresponds
to the day of the year and s to a sequential number between 0 and
9
fffff Extension corresponding to FILEEXT=

108 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

LTG

SIEMENS counters
counters
CP After end of call or intermediate:
Depending on timer 114

counter
countersets
sets

Transferred every full hour

and reset in CMY

Transferred every
month and reset
IA.ICMCR in UCHA
CA.IC.UCHA

CA.IR.R......

IACHASTA
+
registration DISP MET: TRANS FILE
SIEMENS
NIXDORF TYPE=IACMET, FTAM
.....;

Fig. 60 IACHASTA counter files

MN2513EU09S1_0001 SSNC
109
© 2001 Siemens AG
 Siemens Charging Data Administration

File Name Convention and MML Commands

Update file name convention

File name: CA.IC.UCHA[.dddhhs]

ddd day of the year in case of a fall back

hh hour of the day in case of a fall back
s sequential number in case of a fall back

Account file name convention

File name: CA.IR.rnnns.fffff

r= S: Single-sided registration
D: Double-sided registration
M: Mixed registration

nnns Less than 11 account files per day:

nnn: day of the year
s: current file number 0...9

More than 10 account files per day:

nnns: current number for file 11 to n beginning with 4000

fffff Extension corresponding to ACT IACRG: FILEEXT=

Fig. 61 File names

Generation of an account file and meter display

EDIT MET: TYPE=IACMET

[{RGPTTYPE= {DOUBLE|MIXED|SINGLE},
SOURCE=<source file>}];

DISP MET: TYPE=IACMET,

<RGPT=<registration point name>,
OBJORIG=, OBDEST=,
SOURCE=<source file>>;

Fig. 62 MML commands for meter administration

110 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

6 Network Facilities for Charging

MN2513EU09S1_0001 SSNC
111
© 2001 Siemens AG
 Siemens Charging Data Administration

The following command can be used to enable/disable certain network facilities for
charging:
MOD MSERVOPT: FEAT= xxxx, STATUS= ACT/BLK/RST;

Selection of important network facilities:

l CELL DEPENDENT CHARGING
This network facility indicates the status of the feature 'cell dependent charging'.
When activated for zoning purposes, the cell ORIG2 is used instead of the BSS-
trunk ORIG2.
l CHARG MTC OWN SUBSCRIBERS
This flag determines whether charging records have to be generated for MTCs to
own subscribers (i.e. subscribers of the home PLMN).
l CHARGE FREE CALL ATTEMPTS
This network facility determines whether charge free call attempts should be
handled. If released non chargeable records can be generated (see also: charging
of call attempts).
Remark: call attempt record generation will not be performed if both network
facilities for call attempt are inactive.
l CHARGING FOR TRANSIT
This network facility determines whether charging for transit records is applicable.
l CHARGING OF CALL ATTEMPTS
This network facility determines whether charged call attempts should be handled.
If released chargeable records can be generated (see also: charge free call
attempts).
l COLLEC. FOR INTERNAT. SMS MO
This flag determines whether charging records have to be generated for mobile
originated SMS transactions with traffic type = International.
International traffic exists, if at least the SMS originating subscriber or the involved
SMS center does not belong to the home PLMN.
l COLLEC. FOR INTERNAT. SMS MT
This flag determines whether charging records have to be generated for mobile
terminating SMS transactions with traffic type = International.
International traffic exists, if at least the SMS receiving subscriber or the involved
SMS center does not belong to the home PLMN.

112 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

FEAT= Meaning
CELLDCH CELL DEPENDENT CHARGING
CMTCOSUB CHARG MTC OWN
SUBSCRIBERS
CHFCATT CHARGE FREE CALL ATTEMPTS
CHTRANS CHARGING FOR TRANSIT
CALLATT CHARGING OF CALL ATTEMPTS
CISMSMO COLLEC. FOR INTERNAT. SMS
MO
CISMSMT COLLEC. FOR INTERNAT. SMS
MT
CSMSMO COLLEC. FOR NATIONAL SMS
MO
CSMSMT COLLEC. FOR NATIONAL SMS
MT

Fig. 63 DISP MSERV features for charging

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN2513EU09S1_0001 SSNC
113
© 2001 Siemens AG
 Siemens Charging Data Administration

l COLLEC. FOR NATIONAL SMS MO

This flag determines whether charging records have to be generated for mobile
originated SMS transactions with traffic type = National.
National traffic exists, if both the SMS originating subscriber and the involved SMS
center belong to the home PLMN.
l COLLEC. FOR NATIONAL SMS MT
This flag determines whether charging records have to be generated for mobile
terminating SMS transactions with traffic type = National.
National traffic exists, if both the SMS receiving subscriber and the involved SMS
center belong to the home PLMN.
l DISPLAY MOBILE CALL RECORD
This feature is only applicable if (IN) CLIENT FORMATTING ON CAP is inactive.
It allows the usage of the MML command DISP MCR to display the contents of
mobile call records stored on disk.
l FIXED SUBSCRIBER RECORDS ASN1
If released, all records for fixed subscribers are coded in ASN1. Otherwise fixed
subscribers get EWSD-AMA records (binary).
l FORMAT CLIENT RECORDS ON CAP
If active, the process 'Client Formatting' is directly called by the charging service.
Otherwise the formatting process takes place at the time of file transfer.
The command DISPMCR is not executable if FORMAT CLIENT RECORDS ON
CAP is activated.
l HOT BILLING IN GATEWAY MSC
In the case of Call Forwarding an indication whether hot billing is subscribed or
not, has to be sent with the message 'send routing info result' from HLR to the
GMSC.
This only needs to be done if the feature is activated.
l ADD ROA REC AT HLR DETECTED CF
An additional ROA record is created in the case of HLR detected Call Forwarding.
Normally no ticket is created in such a case.
l INTERROGATION RECORDS
Determines whether generation of roaming records is necessary.
l MULTIPLE HOLIDAY CALENDAR
Allows the administration of holiday calendars for mobile charging (MCHARGE)
purposes, in addition to the common (COMMON) holiday calendars.
l THRESHOLD REPORTING
This network facility indicates the status of the feature Threshold Reporting.

114 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

FEAT= Meaning
CSMSMO COLLECT. FOR NAT.SMS MO
CSMSMT COLLECT. FOR NAT.SMS MT
DISPMCR DISPLAY MOBILE CALL
RECORD
CSCASN1 FIXED SUBSCRIBER RECORDS
ASN1
CRFONCAP FORMAT CLIENT RECORDS ON
CAP
HOTBGMSC HOT BILLING IN GATEWAY MSC
CHCFROA ADD ROA REC AT HLR
DETECTED CF
CHINTREC INTERROGATION RECORDS
MULHLDAY MULTIPLE HOLIDAY CALENDAR
THRREP THRESHOLD REPORTING

Fig. 64 DISP MSERV features for charging

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MN2513EU09S1_0001 SSNC
115
© 2001 Siemens AG
 Siemens Charging Data Administration

116 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

7 Exercises

MN2513EU09S1_0001 SSNC
117
© 2001 Siemens AG
 Siemens Charging Data Administration

118 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

Exercise 1
Title: Mobile call records and advice of charge
Objectives: The subscriber will be able to set up a charging data base
Prerequisite: None

Task

Define a complete charging database for AOC or charge unit collection for the CODE
............................<team> according to the following parameters:
Tariff 1 0,5 units on call setup, 30 seconds initial time interval
2 units for every 30 seconds
Tariff 2 2 units on call setup, 30 seconds initial time interval
3 units for every 20 seconds
MTAR 1<team> / 2<team>
MTAR CAT <team>
ZONO <team>
zone point for MOC and Fullrate
PLMWTAR MCC= , NDC=

MN2513EU09S1_0001 SSNC
119
© 2001 Siemens AG
 Siemens Charging Data Administration

Assign the AOC INFO SS to the corresponding MSUBS

WO Mo
Tu
We Tariff 2
Th
Fr
half Sa
full Su
Tariff 1
00.00 08.00 18.00 24.00

full HO Tariff 1
Fixed holidays: January 1, December 25, 26

120 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

Questions: Answers:
Which MML
commands do
you need?

MN2513EU09S1_0001 SSNC
121
© 2001 Siemens AG
 Siemens Charging Data Administration

122 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

Exercise 2
Title: IACHASTA
Objectives: The subscriber will be able to set up an IACHASTA charging
data base
Prerequisite: The corresponding traffic distinction groups for TMR already
exist.
Task

Set up IACHASTA objects and registration points with metering according to the
following data.
l An object for trunk groups from other MSCs with the name MSC<team
nummer>:TGNO = UMS1<team nummer> and UMS2<team nummer>
l An object for the trunk group to Telekom with the name TELE<team nummer>:
TGNO=UTE<team nummer>
l Display the objects
l A schedule with schedule number <team nummer>, that counts in time group 2 on
working days from 8 am to 6 pm. In the remaining time is counted in the standard
time group.
l A registration point to Telekom and a registration point from Telekom.
l Please do not start the registration, as only one double or one single job can run
parallel.

MN2513EU09S1_0001 SSNC
123
© 2001 Siemens AG
 Siemens Charging Data Administration

Questions: Answers:
Which MML
commands do
you need?

124 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

Exercise 3
Title: Charging Data
Objectives: The participant will be able to locate errors in the charging data
base.
Prerequisite: None
Task
The mobile call from the MSUB ................................................. to the
MSUB .......................................................... is not answered. Check the MSC
database with your new knowledge and try to find the error.
Do not correct the error!
Test

How would you correct the error?

MN2513EU09S1_0001 SSNC
125
© 2001 Siemens AG
 Siemens Charging Data Administration

126 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

8 Solution

MN2513EU09S1_0001 SSNC
127
© 2001 Siemens AG
 Siemens Charging Data Administration

128 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

Solution 1
Title: Mobile call records and advice of charge
Objectives: The subscriber will be able to display the charging or tariff data
set up
Prerequisite: None

Task

Define a complete charging database for AOC or charge unit collection for the CODE
............................<team> according to the following parameters:
Tariff 1 0,5 units on call setup, 30 seconds initial time interval
2 units for every 30 seconds
Tariff 2 2 units on call setup, 30 seconds initial time interval
3 units for every 20 seconds
MTAR 1<team> / 2<team>
MTAR CAT <team>
ZONO <team>
zone point for MOC and Fullrate
PLMWTAR MCC= , NDC=

MN2513EU09S1_0001 SSNC
129
© 2001 Siemens AG
 Siemens Charging Data Administration

Assign the AOC INFO SS to the corresponding MSUBS

WO Mo
Tu
We Tariff 2
Th
Fr
half Sa
full Su
Tariff 1
00.00 08.00 18.00 24.00

full HO Tariff 1
Fixed holidays: January 1, December 25, 26

130 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

1128

ENTRTGDAT:TGNO=TGPKI2,GCOS=ZON;

1128

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:02:22

1128 CA SIEMENS0 2867/00007

ENTRTGDAT:TGNO=TGPKI2,GCOS=ZON; EXEC'D

END JOB 1128

1140

DISPTGRP:TGNO=TGPKI2;

1140

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:03:05

1140 CA SIEMENS0 2871/20023

TGNO = TGPKI2 OPMODE = BW

GCOS = JSUBORD &ZON &NONSEQ &CCS7MUP &BS
&AMAREQD &ANIREVAL &USVERS0
ORIG1 = 20 ORIG2 =

END JOB 1140

MN2513EU09S1_0001 SSNC
131
© 2001 Siemens AG
 Siemens Charging Data Administration

1159

DISPTGRP:TGNO=MICINC;

1159

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:05:59

1159 CA SIEMENS0 2871/20023

TGNO = MICINC OPMODE = IC

GCOS = JSUBORD &NOZON &AMAREQD &LOOPSIG1 &LOOPTRAF
ORIG1 = 99 ORIG2 =

END JOB 1159

1160

ENTRTGDAT:TGNO=MICINC,GCOS=ZON;

1160

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:06:21

1160 CA SIEMENS0 2867/00007

ENTRTGDAT:TGNO=MICINC,GCOS=ZON; EXEC'D

END JOB 1160

132 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

1189

DISPMSERVOPT:FEAT=MULHLDAY;

1189

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:09:56

1189 CA SIEMENS0 2992/06692

DISPMSERVOPT:FEAT=MULHLDAY; EXEC'D

SERVICE/ CONNECTION RADIO CHANNEL ALTERNATIVE

FEATURE STATUS ELEMENT REQUIREMENT SCI OCI SERVICE
----------+--------+------------+--------------+-----+-----+-----------
MULHLDAY ACT

END JOB 1189

1190

CRHOLICAL:FEAT=MCHARGE,YEAR=1999,DATECAT=12-25-HO;

1190

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:10:40

1190 CA SIEMENS0 2988/00007

CRHOLICAL:FEAT=MCHARGE,YEAR=1999,DATECAT=12-25-HO; EXEC'D

END JOB 1190

MN2513EU09S1_0001 SSNC
133
© 2001 Siemens AG
 Siemens Charging Data Administration

1203

MODWDCAT:FEAT=MCHARGE,WD=MO,WDCAT=WO;

1203

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:11:53

1203 CA SIEMENS0 2988/00007

MODWDCAT:FEAT=MCHARGE,WD=MO,WDCAT=WO; EXEC'D

END JOB 1203

1204

MODWDCAT:FEAT=MCHARGE,WD=TU,WDCAT=WO;

1204

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:12:00

1204 CA SIEMENS0 2988/00007

MODWDCAT:FEAT=MCHARGE,WD=TU,WDCAT=WO; EXEC'D

END JOB 1204

134 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

1205

MODWDCAT:FEAT=MCHARGE,WD=WE,WDCAT=WO;

1205

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:12:03

1205 CA SIEMENS0 2988/00007

MODWDCAT:FEAT=MCHARGE,WD=WE,WDCAT=WO; EXEC'D

END JOB 1205

1206

MODWDCAT:FEAT=MCHARGE,WD=TH,WDCAT=WO;

1206

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:12:07

1206 CA SIEMENS0 2988/00007

MODWDCAT:FEAT=MCHARGE,WD=TH,WDCAT=WO; EXEC'D

END JOB 1206

MN2513EU09S1_0001 SSNC
135
© 2001 Siemens AG
 Siemens Charging Data Administration

1207

MODWDCAT:FEAT=MCHARGE,WD=FR,WDCAT=WO;

1207

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:12:12

1207 CA SIEMENS0 2988/00007

MODWDCAT:FEAT=MCHARGE,WD=FR,WDCAT=WO; EXEC'D

END JOB 1207

1208

MODWDCAT:FEAT=MCHARGE,WD=SU,WDCAT=HH;

1208

COMMAND SUBMITTED

1208 MASKNO:10001
COMMAND ERROR MESSAGE FOR MODWDCAT : 1 ERROR(S)
MASKNO:10990
THE FOLLOWING DATA ARE INVALID:

CNTXT PAR.NAME PARAMETER VALUE

-----+--------+---------------------------------------------------------
WDCAT =<HH>

END JOB 1208

136 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

1209

MODWDCAT:FEAT=MCHARGE,WD=SA,WDCAT=EH;

1209

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:13:15

1209 CA SIEMENS0 2988/00007

MODWDCAT:FEAT=MCHARGE,WD=SA,WDCAT=EH; EXEC'D

END JOB 1209

1210

MODWDCAT:FEAT=MCHARGE,WD=SA,WDCAT=EF;

1210

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:13:26

1210 CA SIEMENS0 2988/00007

MODWDCAT:FEAT=MCHARGE,WD=SA,WDCAT=EF; EXEC'D

END JOB 1210

MN2513EU09S1_0001 SSNC
137
© 2001 Siemens AG
 Siemens Charging Data Administration

1213

MODWDCAT:FEAT=MCHARGE,WD=SU,WDCAT=EF;

1213

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:13:32

1213 CA SIEMENS0 2988/00007

MODWDCAT:FEAT=MCHARGE,WD=SU,WDCAT=EF; EXEC'D

END JOB 1213

1223

DISPWDCAT:FEAT=MCHARGE;

1223

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:13:49

1223 CA SIEMENS0 2992/20029

TABLE OF WEEKDAY-CATEGORIES FOR MCHARGE APPLICATION

MO TU WE TH FR SA SU
---+---+---+---+---+---+---
WO WO WO WO WO EH EF

END TEXT 1223

138 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

MSC3/D2MMPK1V16031298/000 99-02-16 14:13:52

1223 CA SIEMENS0 2992/00007

DISPWDCAT:FEAT=MCHARGE; EXEC'D

END JOB 1223

1247

ENTRMTAR:MTAR=1,E1UPTI=20,E2SPTI=300,E4INU=5,E7SPITI=300;

1247

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:17:58

1247 CA SIEMENS0 2922/00007

ENTRMTAR:MTAR=1,E1UPTI=20,E2SPTI=300,E4INU=5,E7SPITI=300; EXEC'D

END JOB 1247

MN2513EU09S1_0001 SSNC
139
© 2001 Siemens AG
 Siemens Charging Data Administration

1254

ENTRMTAR:MTAR=2,E1UPTI=30,E2SPTI=200,E4INU=20,E7SPITI=200;

1254

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:19:21

1254 CA SIEMENS0 2922/00007

ENTRMTAR:MTAR=2,E1UPTI=30,E2SPTI=200,E4INU=20,E7SPITI=200; EXEC'D

END JOB 1254

1284

MODHOLICAL:FEAT=MCHARGE,YEAR=1999,NDATECAT=12-26-HO;

1284

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:23:21

1284 CA SIEMENS0 2988/00007

MODHOLICAL:FEAT=MCHARGE,YEAR=1999,NDATECAT=12-26-HO; EXEC'D

END JOB 1284

140 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

1285

DISPHOLICAL:FEAT=MCHARGE,YEAR=1999;

1285

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:23:31

1285 CA SIEMENS0 2992/20030

HOLIDAY CALENDAR FOR MCHARGE APPLICATION

Year : 1999

(DATE-FORMAT : MM-DD)

DATE WDCAT
------+------
12-25 HO
12-26 HO

END TEXT 1285

MSC3/D2MMPK1V16031298/000 99-02-16 14:23:34

1285 CA SIEMENS0 2992/00007

DISPHOLICAL:FEAT=MCHARGE,YEAR=1999; EXEC'D

END JOB 1285

MN2513EU09S1_0001 SSNC
141
© 2001 Siemens AG
 Siemens Charging Data Administration

1299

ENTRPLMNTAR:NETW=262-30,E3SCF=100;

1299

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:25:52

1299 CA SIEMENS0 2922/00007

ENTRPLMNTAR:NETW=262-30,E3SCF=100; EXEC'D

END JOB 1299

1311

ENTRMTARCAT:MTARCAT=1,SWTAR=18-00-1-WO&8-00-2-WO;

1311

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:27:55

1311 CA SIEMENS0 2922/00007

ENTRMTARCAT:MTARCAT=1,SWTAR=18-00-1-WO&8-00-2-WO; EXEC'D

END JOB 1311

142 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

1320

CRMZONE:ZONO=1,FULL=1;

1320

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:28:34

1320 CA SIEMENS0 2922/00007

CRMZONE:ZONO=1,FULL=1; EXEC'D

END JOB 1320

1344

CRMZOPT:CODE=4917230-INAT,CHTYPE=MOC,MZONO=1;

1344

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:31:01

1344 CA SIEMENS0 2926/00007

CRMZOPT:CODE=4917230-INAT,CHTYPE=MOC,MZONO=1; EXEC'D

END JOB 1344

MN2513EU09S1_0001 SSNC
143
© 2001 Siemens AG
 Siemens Charging Data Administration

1350

DISPMZOPT:MZONO=1;

1350

COMMAND SUBMITTED

MSC3/D2MMPK1V16031298/000 99-02-16 14:32:15

1350 CA SIEMENS0 2926/20020

MOBILE ZONEPOINTS

MZONO/
MZOCHA/
CODE MINCEPT STAT CHTYPE SURCH TKZ BIL MEPROC
--------------------+----------------+----+------+-----+---+---+--------
4917230 -INAT 1 MOC NO
END TEXT 1350

144 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

Solution 2
Title: Interadministrative charging and statistics
Objectives: The subscriber will be able to display the IACHASTA data
set up
Prerequisite: None

Task
Set up IACHASTA objects and registration points with metering according to the
following data.
l An object for trunk groups from other MSCs with the name MSC<team
nummer>:TGNO = UMS1<team nummer> and UMS2<team nummer>
l An object for the trunk group to Telekom with the name TELE<team nummer>:
TGNO=UTE<team nummer>
l Display the objects
l A schedule with schedule number <team nummer>, that counts in time group 2 on
working days from 8 am to 6 pm. In the remaining time is counted in the standard
time group.
l A registration point to Telekom and a registration point from Telekom.
l Please do not start the registration, as only one double or one single job can run
parallel.

<CR IACOBJ:OBJ=MSC9,TGNO=UMSC29;

MSC5/D2MMPK1V16180024/003 98-02-20 13:14:44

2053 OMT-00/SIEMENS0 2944/00007

CRIACOBJ:OBJ=MSC9,TGNO=UMSC29; EXEC'D

END JOB 2053

2065
<CR IACOBJ:OBJ=MSC9,TGNO=UMSC19;

MSC5/D2MMPK1V16180024/003 98-02-20 13:15:03

2065 OMT-00/SIEMENS0 2944/00007

CRIACOBJ:OBJ=MSC9,TGNO=UMSC19; EXEC'D

END JOB 2065

MN2513EU09S1_0001 SSNC
145
© 2001 Siemens AG
 Siemens Charging Data Administration

2107
<DISP IACOBJ:OBJ=MSC9,LAC=;

MSC5/D2MMPK1V16180024/003 98-02-20 13:18:02

2107 OMT-00/SIEMENS0 2948/08599

DISPIACOBJ:OBJ=MSC9; EXEC'D

COMPOSITION OF IACHASTA OBJECT

ELEMENT ELEMENT
TYPE IDENTIFICATION
--------+-------------------
TGRP UMSC19
TGRP UMSC29

END JOB 2107

2110
<CR IACOBJ:OBJ=TELE9,TGNO=UTE9;

MSC5/D2MMPK1V16180024/003 98-02-20 13:32:53

2110 OMT-00/SIEMENS0 2944/00007

CRIACOBJ:OBJ=TELE9,TGNO=UTE9; EXEC'D

END JOB 2310

2120
<MOD IACSCHED:SCHED=9,TIMGRP=2,TIME=8-00&&18-00,WDCAT=WO;

MSC5/D2MMPK1V16180024/003 98-02-20 13:19:23

2120 OMT-00/SIEMENS0 2944/00007

MODIACSCHED:SCHED=9,TIMGRP=2,TIME=8-00&&18-00,WDCAT=WO; EXEC'D

END JOB 2120

2132
<DISP IACSCHED:SCHED=9;

MSC5/D2MMPK1V16180024/003 98-02-20 13:19:33

2132 OMT-00/SIEMENS0 2948/08562

DISPIACSCHED:SCHED=9; EXEC'D

IACHASTA SCHEDULE

TIME TIME GROUP FOR WEEKDAY CATEGORY

HO HH EF EH HN WO
--------+----+----+----+----+----+------
00:00 1 1 1 1 1 1
08:00 2
18:00 1

END JOB 2132

146 SSNC MN2513EU09S1_0001

© 2001 Siemens AG
Charging Data Administration Siemens

2264
<DISP IACTRADI;

MSC5/D2MMPK1V16180024/003 98-02-20 13:30:07

2264 OMT-00/SIEMENS0 2948/08561

DISPIACTRADI; EXEC'D

IACHASTA TRAFFIC GROUPS

RGPT DISTINCTION TRAFFIC TMR / LINE CATEGORY

TYPE CRITERION GROUP
-------+------------+--------+--------------------------------------
SINGLE TMR 1 A3KHZ1
SINGLE TMR 2 KBIT64 KBIT64FB
SINGLE TMR 3 SPEECH
DOUBLE TMR 1 A3KHZ1
DOUBLE TMR 2 SPEECH
DOUBLE TMR 3 KBIT64 KBIT64FB

END JOB 2264

2311
<CR IACRGPT:OUT=MET,OBJORIG=MSC9,OBJDEST=TELE9,SCHED=9;

MSC5/D2MMPK1V16180024/003 98-02-20 13:33:13

2311 OMT-00/SIEMENS0 2944/00007

CRIACRGPT:OUT=MET,OBJORIG=MSC9,OBJDEST=TELE9,SCHED=9; EXEC'D

END JOB 2311

2320
<DISP IACRGPT:OBJORIG=MSC9,OBJDEST=TELE9;

MSC5/D2MMPK1V16180024/003 98-02-20 13:33:35

2320 OMT-00/SIEMENS0 2948/08533

DISPIACRGPT:OBJORIG=MSC9,OBJDEST=TELE9; EXEC'D

IACHASTA REGISTRATION POINT DATA

ORIGIN DESTINATION OUTPUT REGISTRATION SCHEDULE STATUS

OBJECT OBJECT TYPE POINT
-------+------------+---------+-------------+---------+------
MSC9 TELE9 MET 9 ACT

END JOB 2320

MN2513EU09S1_0001 SSNC
147
© 2001 Siemens AG
 Siemens Charging Data Administration

2324
<DISP IACRGPT:RGPT=X;

MSC5/D2MMPK1V16180024/003 98-02-20 13:33:46

2324 OMT-00/SIEMENS0 2948/08592

DISPIACRGPT:RGPT=X; EXEC'D

LIST OF ALL EXISTING NAMED IACHASTA REGISTRATION POINTS

------------------------------------------------------------------------
NO (MORE) DATA FOR DISPLAY AVAILABLE

END JOB 2324

2330
<CR IACRGPT:OUT=MET,OBJORIG=TELE9,OBJDEST=MSC9,SCHED=9;

MSC5/D2MMPK1V16180024/003 98-02-20 13:33:13

2330 OMT-00/SIEMENS0 2944/00007

CR IACRGPT:OUT=MET,OBJORIG=TELE9,OBJDEST=MSC9,SCHED=9; EXEC'D

END JOB 2330

148 SSNC MN2513EU09S1_0001

© 2001 Siemens AG