Operation

Charging
OMN:SSS-TA
A30808-X3003-X458-2-7619

OMN:SSS-TA

Operation Charging

Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the
parts can also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.
Therefore only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950. All equipment connected has to comply with the
applicable safety standards.

Copyright (C) Siemens AG 1996

Issued by the Public Communication Network Group
Hofmannstrae 51
D-81359 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

AD - 2

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Issues
Note on the change indication:
The change indications for a title marked as issue 1 refer to the previous version. The
change indications for a title with an issue greater than 1 refer to the preceding issue.
Change indications:
N = new;

G = modified;

Title
Administration Section (AD)
Introduction (IN)
Task List (TL)
Task Summary Lists (TS)

Task Procedures (TP)

A30808-X3003-X458-2-7619

0 = deleted;
Issue
2
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

Page(s)
AD - 1. . . . . AD
IN - 1. . . . . . IN
TL - 1. . . . . TL
TS - 1. . . . . TS
TS-300 - 1. .TS-300
TS-302 - 1. .TS-302
TS-305 - 1. .TS-305
TS-307 - 1. .TS-307
TS-500 - 1. .TS-500
TS-501 - 1. .TS-501
TS-502 - 1. .TS-502
TS-504 - 1. .TS-504
TS-505 - 1. .TS-505
TS-506 - 1. .TS-506
TS-510 - 1. .TS-510
TS-511 - 1. .TS-511
TS-512 - 1. .TS-512
TS-513 - 1. .TS-513
TS-530 - 1. .TS-530
TS-531 - 1. .TS-531
TS-532 - 1. .TS-532
TS-600 - 1. .TS-600
TS-601 - 1. .TS-601
TS-602 - 1. .TS-602
TS-603 - 1. .TS-603
TS-604 - 1. .TS-604
TS-605 - 1. .TS-605
TS-606 - 1. .TS-606
TS-607 - 1. .TS-607
TS-608 - 1. .TS-608
TS-721 - 1. .TS-721
TS-731 - 1. .TS-731
TS-732 - 1. .TS-732
TS-733 - 1. .TS-733
TS-740 - 1. .TS-740
TS-741 - 1. .TS-741
TS-831 - 1. .TS-831
TS-840 - 1. .TS-840
TP - 1. . . . . TP
TP-301 - 1. .TP-301
TP-302 - 1. .TP-302
TP-501 - 1. .TP-501
TP-503 - 1. .TP-503
TP-511 - 1. .TP-511

- 8
- 92
- 10
- 2
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 1
- 2
- 4
- 4
- 2
- 2
- 2

G
G

AD 3

OMN:SSS-TA

Operation Charging

Task Complexes (TC)

Appendix (AP)

1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

TP-513 - 1
TP-523 - 1
TP-524 - 1
TP-530 - 1
TP-545 - 1
TP-550 - 1
TP-600 - 1
TP-603 - 1
TP-701 - 1
TP-702 - 1
TP-703 - 1
TP-704 - 1
TP-705 - 1
TP-706 - 1
TP-707 - 1
TP-720 - 1
TP-721 - 1
TP-722 - 1
TP-761 - 1
TP-767 - 1
TP-769 - 1
TP-770 - 1
TP-811 - 1
TP-820 - 1
TP-822 - 1
TP-824 - 1
TP-830 - 1
TP-900 - 1
TP-905 - 1
TP-910 - 1
TP-915 - 1
TP-931 - 1
TP-933 - 1
TP-934 - 1
TC - 1
TC-001 - 1
TC-002 - 1
TC-009 - 1
TC-010 - 1
TC-011 - 1
TC-303 - 1
AP - 1

. TP-513
. TP-523
. TP-524
. TP-530
. TP-545
. TP-550
. TP-600
. TP-603
. TP-701
. TP-702
. TP-703
. TP-704
. TP-705
. TP-706
. TP-707
. TP-720
. TP-721
. TP-722
. TP-761
. TP-767
. TP-769
. TP-770
. TP-811
. TP-820
. TP-822
. TP-824
. TP-830
. TP-900
. TP-905
. TP-910
. TP-915
. TP-931
. TP-933
. TP-934
. . . . .TC
. TC-001
. TC-002
. TC-009
. TC-010
. TC-011
. TC-303
. . . . .AP

2
2
2
2
2
4
2
2
2
2
4
2
4
2
2
2
2
2
2
2
2
2
2
4
2
2
2
6
4
4
4
2
2
2
2
2
2
2
2
4
6
2

This document consists of a total of 268 pages.

AD 4

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Contents
1
1.1
1.1.1
1.1.2
1.1.2.1
1.1.3
1.1.4
1.1.5
1.1.5.1
1.1.5.2
1.1.5.3
1.1.5.4
1.1.5.5
1.1.5.6
1.1.6
1.1.6.1
1.1.6.2
1.1.6.3
1.1.6.4
1.2
1.2.1
1.2.2
1.2.3
1.2.3.1
1.2.3.2
1.2.3.3
1.2.3.4
1.2.4
1.2.4.1
1.2.4.2
1.2.4.3
1.2.5
1.2.6
1.3
1.3.1
1.3.2
1.3.3
1.4
1.4.1
1.4.1.1
1.4.1.2
1.4.1.3
1.4.1.4
1.4.1.5
1.4.2

A30808-X3003-X458-2-7619

Introduction (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-1

PLMN Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-1
Administration of Weekday Categories and Holidays . . . . . . . . . . . . . . . IN-2
Charging with MCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-3
Types of Calls requiring Generation of MCR . . . . . . . . . . . . . . . . . . . . . IN-3
Mobile Call Records: Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-13
Hot Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-17
Zones and Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-17
Zoning for Originating Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-20
Tariffs for Mobile Terminating Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-23
Surcharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-24
Call Attempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-24
Subscriber Controlled Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-24
Advice of Charge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-24
Call Charge Registration in the Intelligent Network (IN) . . . . . . . . . . . . IN-26
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-26
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-27
Charge Registration for the IN Services: General. . . . . . . . . . . . . . . . . IN-28
Administration by MML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-28
Interadministration Revenue and Statistics (IARA). . . . . . . . . . . . . . . . . IN-31
IARA Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-33
Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-34
IARSTAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-39
Registration Counters and Tariff Zones . . . . . . . . . . . . . . . . . . . . . . . . . IN-39
Functional Sequence of IARSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-41
IARSTAT Post-Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-41
Example of an IARSTAT Application . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-44
IARAMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-50
MML commands for IARAMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-50
Example of an IARAMA Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-51
Saving the Registered Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-53
Regeneration of the IARA database . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-53
Procedure after Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-53
Trunk Meters and Statistics Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-54
Trunk Meters for Trunk Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-54
Statistics Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-55
Statistics Meter Switchover Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-55
Charging of Wired Subscribers of a Combined
Switching Center (CSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-57
Subscriber Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-58
Tariff Administration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-58
Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-59
Tariff Sequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-60
Tariff Switchovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-62
Weekday Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-63
Zone Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-64

AD 5

OMN:SSS-TA

Operation Charging

1.4.2.1
1.4.3
1.4.4
1.4.4.1
1.4.4.2
1.4.4.3
1.4.5
1.4.5.1
1.4.5.2
1.4.5.3
1.4.5.4
1.4.6
1.4.7
1.4.7.1
1.4.7.2
1.4.7.3
1.4.8
1.4.9
1.4.9.1
1.4.9.2
1.4.9.3
1.4.9.4
1.4.10
1.4.10.1
1.4.10.2
1.4.10.3
1.4.10.4
1.4.11
1.5
2
2.1
2.2
2.2.1
2.2.2
2.2.3
2.2.3.1
2.2.3.2
2.2.4
2.2.5
2.2.6
2.3
2.3.1
2.4

AD 6

Creation of Zone Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Charge Band Message and Zone Traffic Type . . . . . . . . . . . . . . . . . . .
Supplementary Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Registration of charges for the input of supplementary
services (facility input FAI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Registration of charges for the usage of supplementary
services (facility usage FAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Account suspensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Counter Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creation of Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creation of Backup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Billing File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Counter Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subscriber Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistics Meters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use of Statistics Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistics index Structure and Selection of Currently
Active Statistics Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistics Meter Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trunk Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Individual Call Data Administration Feature . . . . . . . . . . . . . . . . . . . . . .
Automatic Message Accounting (AMA) . . . . . . . . . . . . . . . . . . . . . . . . .
Detailed Billing (DEB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Meter Observation (MOB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preventive Meter Observation (PMOB) . . . . . . . . . . . . . . . . . . . . . . . . .
Call Charge Registration in the Intelligent Network (IN). . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Charge Registration for the IN Services: General . . . . . . . . . . . . . . . . .
Administration by MML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reverse Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Notes on the Iridium Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IN-65
IN-68
IN-69
IN-69
IN-69
IN-70
IN-70
IN-70
IN-71
IN-71
IN-72
IN-74
IN-74
IN-74
IN-75
IN-78
IN-78
IN-78
IN-80
IN-81
IN-82
IN-83
IN-83
IN-83
IN-85
IN-86
IN-87
IN-89
IN-91

Task List (TL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selection of Charging Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PLMN Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Holiday and Weekday Category Administration. . . . . . . . . . . . . . . . . . . .
Automatic Message Accounting Administration . . . . . . . . . . . . . . . . . . . .
Administration of Zones and Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration of Zones and Tariffs for Mobile Originating Calls,
Call Attempts, Call Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration of Tariffs for Mobile Terminating Calls (PLMN Tariffs) . . .
Charge Registration in the Intelligent Network (IN) . . . . . . . . . . . . . . . . .
Administration of Control Meters for Connection Groups. . . . . . . . . . . . .
Administration of Statistics Meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interadministration Revenue Accounting (IARA) Administration . . . . . . .
IARSTAT Destination and IARSTAT Origin Name Administration. . . . . .
Charging of Wired Subscribers of a Combined

TL-1
TL-1
TL-1
TL-1
TL-1
TL-2
TL-2
TL-2
TL-2
TL-2
TL-3
TL-3
TL-3

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.4.6
2.4.7
2.4.8
2.4.9
2.4.10
2.4.11
2.4.12

Switching Center (CSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Subscriber Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zone Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Charge Band Messages and Zone Traffic Types . . . . . . . . . . . . . . . . . .
Subscriber Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Meter Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subscriber Meters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Statistics Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trunk Meters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic Message Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Charge Registration in the IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reverse Charging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subscriber's Private Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Task Summary Lists (TS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-1

Task Procedures (TP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-1

Task Complexes (TC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TC-1

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AP-1

A30808-X3003-X458-2-7619

TL-5
TL-5
TL-5
TL-6
TL-6
TL-7
TL-7
TL-7
TL-8
TL-8
TL-8
TL-9
TL-9

AD 7

OMN:SSS-TA

AD 8

Operation Charging

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

1 Introduction (IN)
The tariff and charging administration register comprises two large tariff establishment
and charging data subareas:
charges that are billed to the individual subscriber and
charges that are shared by the administrations of the individual networks
But the charging that is usual in the PSTN must be discriminated from that used in a
PLMN because both charging types can be applied for the operation of a combined
switching center.
A CSC is a network node which can implement the function of a PLMN and that of a
PSTN network node.
Generally speaking, distinctions are made between three types of subscribers:
Mobile subscribers: A mobile subscriber can move freely within the GSM system
and is in contact with the network via a radio link.
Wireless local-loop subscribers (WLL subscribers): Mobile subscribers with
restricted location authorization within the PLMN and a call number which follows
the numbering scheme of the PSTN.
Wire-line subscribers: Both wire-line subscribers and PABXs can be connected to
the MSC.
WLL subscribers are mobile subscribers who only differ from "normal" mobile
subscribers due to a small number of typical features (e. g. numbering scheme).
Accordingly, the only distinctions made in the following are between wire-line and mobile
subscribers.
Logging the charges to the individual subscribers is described in two different sections
TN subscribers.
The charging between different administrations is described for both types of charging
in Section IARA.
For the Iridium project please refer to the notes in Section 1.5

1.1

PLMN Charging
Charges for mobile subscribers generally consist of a fixed network access component
and a variable network utilization component. Network utilization charges are registered
on a per call basis and depend on:
date and time
call duration
type of service
call origin and destination
utilization of supplementary services (additional charging may be optional)
Call charges for GSM-PLMN (public land mobile network based on the Recommendations of the Global System for Mobile Communication) subscribers are registered exclusively by automatic message accounting.
Automatic message accounting generates a Mobile Call Record (MCR) for each call.
This record contains all important call information, e.g. the date, time and duration of the
call, as well as the calling and called party numbers. If mobile tariffs have been established, the record can also contain this information.
MCR are generated at the MSC that controls the related call.

A30808-X3003-X458-2-7619

IN 1

OMN:SSS-TA

Operation Charging

Only valid for Iridium: MCRs are generated at the MSC (i.e. GSC) that controls the
related call. This also applies if after sending of the correlation data message a connection is switched entirely within the satellite network. In this case, from the viewpoint of
the MSC, the connection remains intact but is "muted" while the earth terminal controller
ETC monitors the connection via satellite (see OMN:SSS-CCS7).
Depending on the particular project, records can be generated for the following types of
calls:
mobile originating calls (MOC)
mobile terminating calls (MTC)
emergency calls
IN call
interrogation (at the MSC which interrogates the HLR for the subscriber location
data, called "Roaming Records")
subscriber controlled input (SCI; at the visited MSC of the served mobile subscriber)
call forwarding (at the MSC which forwards an incoming call)
call attempt (unsuccessful) of an MOC, MTC or call forwarding
reception and transmission of a short message
transit calls
additional records that can be immediately evaluated in a suitable processing center
(hot operation)
If one use AOC, how a charge is established depends essentially on the time of the call.
Consequently, a section will first be presented here on the administration of weekday
categories and holidays.

1.1.1

Administration of Weekday Categories and Holidays

How a call is charged generally depends on the day of the call and the time of day. The
time of day is determined by the system time (see OMN:SSS-SY). The charging-relevant time intervals of a day are set with tariff categories (ENTR MTARCAT). Holidays
are marked by allocating a holiday category (e.g.FULL HOLIDAY) to the corresponding
date. These allocations form a holiday calendar. A distinction can be made between
fixed and variable holidays. The allocation of weekday categories and fixed and variable
holidays to the days of the week form a calendar group. Depending on the project,
calendar groups can be created for specific features at present, for the mobile
charging feature (Advice of Charge) and as a common calendar group (e.g. for charging
of wire-line subscribers of a CSC, for IARA or for periodic execution of command files or
route switching). A calendar group consists of the allocation of the individual days of the
week to a weekday category, a fixed holiday calendar and a separate calendar for the
variable holidays each year.
Apart from being dependent on the time of day, call charging is also dependent on the
weekday category.
Calendar are administered in three phases:
each day of the week (Monday, Tuesday, ... , Sunday) is first allocated to a weekday
category (e.g. the days Monday through Friday are allocated to the weekday category working day and Saturday and Sunday to the weekday category weekend).
holidays with a fixed date (e.g. New Year's Day) are allocated to a weekday category.
This allocation has priority over the general day allocation.
holidays with variable dates or holidays which occur only once are allocated to a
weekday category. This allocation has top priority.

IN 2

A30808-X3003-X458-2-7619

Operation Charging

1.1.2

OMN:SSS-TA

Charging with MCR

When using the mobile communication network, MCR are generated at the MSC. These
records are used to register the total charges of the served mobile subscriber within the
framework of data post processing. The information needed to handle charging for the
individual types of calls is stored in the GPs of all LTGs. If changes occur in the manner
in which charges are registered (e.g. due to a change in tariffs after a given time limit
has been reached), the CP punctually transmits the new information to all GPs. For each
call, the GP collects the current time, the duration of the call and the tariffs used. All other
charging data are registered in the CP. After a handover, the above-mentioned charging
data are registered in the anchor LTG, i.e. the BSSAP-LTG which established the
connection to the base station system prior to the first handover. At the end of the call,
all relevant information is collected in a CP buffer in the form of an MCR. In the case of
calls of long duration, intermediate data records may be generated for safety reasons.
A new data record is generated after the sequence of timer 114 (can be set with MOD
TIOUT). These intermediate data records are numbered consecutively so that the first
data record is called "first intermediate" and the last "last". If the service is changed
during a call (in-call modification) or in case of call transfer, a new record is created.
It is possible to display all or individual data records (DISP MCR).
Selection criteria are as follows:
IMSI or MSISDN of the A or B subscriber
Date and time of the recording
Sequence number of the data record
The displayed include the following:
A and B subscriber directory number
Date and time of the call
Connection type/service used
Incoming and outgoing trunk
Note:
if client record formatting on CAP is active, no DISP MCR is possible!
The generation of MCR for mobile subscribers (Mobile Call Records) at an MSC
requires fulfillment of the following conditions:
The MCR feature must be activated (ACT IAFEAT)
All incoming or bothway trunk groups for calls for which the MCR are to be generated
must be created with GCOS=AMAREQD, or with AMATRANS in the case of transit
calls
If zoning has been created for an incoming or bothway trunk group (GCOS=ZON),
the generation of an MCR must be explicitly indicated for the particular zone point
(CR MZOPT.: ..., BILLING=AMA)
Project dependend additionally items may be checked

1.1.2.1

Types of Calls requiring Generation of MCR

Below are some example situations in which MCR are generated. The basic assumption
in each description is that all participating parties are located (visiting or home) in
different networks. No inter-PLMN interrogations are executed in these examples (see
OMN:SSS-RO); the generation of (optional) interrogation records is not explicitly indicated. Calls between mobile stations (mobile-to-mobile) are performed via the PSTN.
The scope of the examples has been limited for reasons of clarity only this does not
affect the indicated records.

A30808-X3003-X458-2-7619

IN 3

OMN:SSS-TA

Operation Charging

Mobile Originating Call

If a mobile originating call is successful, i.e. answered (i.e. the calling party is a mobile
subscriber and the called party is a fixed network subscriber or a subscriber of a other
PLMN), charging is performed at the visited MSC (VMSC) of the calling mobile
subscriber. The accumulated charging data contain information on the connection from
the location of the served mobile subscriber to the called party (see Fig. 1.1 for call to
PSTN).
The MCR generated at the visited MSC of the calling party contains the following
specific information:
call type/transaction type: MOC
served mobile identity: IMSI, MSISDN, IMEI of the calling mobile subscriber
other party: number of the called subscriber

Speech and
signaling

PLMN
PSTN

Calling party

GMSC

Exch

Signaling

Called party

VMSC

Fig. 1.1

Mobile originating call (MOC)

Mobile Terminating Call
For mobile terminating calls (in this example, the calling party is located in the PSTN,
and the called party is a mobile subscriber located in the area of his home PLMN), an
MCR is generated at the visited MSC for the called mobile subscriber. The collected
charging data contain information on the call's destination component, otherwise designated as the mobile terminating component. This mobile terminating component is
dependent on the visited MSC and the HLR of the served mobile subscriber (see
Fig. 1.2).
It is possible to switch on or off the generation of MTC-tickets for the "own" subcribers
(MOD MSERVOPT).
The MCR generated at the visited MSC of the called party contains the following specific
information:
call type/transaction type: MTC
served mobile identity: IMSI, MSISDN, IMEI of the called mobile subscriber
other party: number of the calling subscriber (if known)

IN 4

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

PLMN
HLR

PSTN
GMSC

Exch

Calling party

Called party

VMSC

Speech and
signaling
Signaling

Fig. 1.2

Mobile terminating call (MTC)

Mobile-to-Mobile Call
For the calling mobile party, an MCR is generated just as it is for a mobile originating
call. For the called mobile party, an MCR is generated as it is for a mobile terminating
call (see Fig. 1.3).
The MCR generated at the visited MSC of the served mobile subscribers contain the
following specific information:
At the visited MSC of the calling party:
call type/transaction type: MOC
served mobile identity: IMSI, MSISDN, IMEI of the calling party
other party: MSISDN of the called party
At the visited MSC of the called party:
call type/transaction type: MTC
served mobile identity: IMSI, MSISDN, IMEI of the called party
other party: MSISDN of the calling party

A30808-X3003-X458-2-7619

IN 5

OMN:SSS-TA

Operation Charging

Visited
PLMN of the
calling party

Calling party

Speech and
signaling

Home PLMN of the

called party

Signaling

HLR
GMSC
VMSC

GMSC

Exch

Exch

PSTN

Exch

VMSC

GMSC

Visited PLMN of the

B subscriber

Fig. 1.3

Called party

Mobile-to-mobile call
Call Forwarding Unconditional
When call forwarding unconditional is activated for a mobile subscriber, the HLR
answers the routing information interrogation via the gateway MSC when the connection
is a mobile terminating call. The HLR therefore transmits to the GMSC the number of
the party to be forwarded to. This message also contains the information that a call
forwarding transaction is being performed.
A mobile terminating call can be forwarded to another mobile subscriber in a PLMN as
well as to a fixed network subscriber in the PSTN. Two related examples are provided
below (see also Fig. 1.4 and Fig. 1.5).
PLMN -> PLMN -> PLMN
The MCR that are generated at the involved MSCs contain the following specific information:
At the visited MSC of the calling party:
call type/transaction type: MOC
served mobile identity: IMSI, MSISDN, IMEI of the calling party
other party:dialed number (MSISDN of the called party)
supplementary service:

IN 6

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

At the gateway MSC in the PLMN of the called party:

call type/transaction type: CF
served mobile identity: MSISDN of the called party
other party: MSISDN of the party to be forwarded to
supplementary service: call forwarding unconditional
third party: MSISDN of the calling party (if signalling is possible)
At the visited MSC of the forwarded-to party:
call type/transaction type: MTC
served mobile identity: IMSI of the party to be forwarded to
other party: MSISDN of the called party
supplementary service:

Speech and
signaling
Home PLMN of the
called party

Signaling

HLR
Visited PLMN of the
calling party

Home and visited

PLMN of the party
to be forwarded to

GMSC

Calling party

HLR

VMSC

GMSC
GMSC
VMSC

Exch

Exch

Party forwarded to

Exch

PSTN
Fig. 1.4

Call forwarding unconditional (PLMN -> PLMN ->PLMN)

PSTN -> PLMN -> PSTN
The MCR generated at the gateway MSC in the PLMN of the called party contains the
following specific information (see Fig. 1.5):
call type/transaction type: CF
served mobile identity: called party's MSISDN
other party: number of the party to be forwarded to
supplementary service: call forwarding unconditional
third party: MSISDN of the calling party (if signalling is possible)

A30808-X3003-X458-2-7619

IN 7

OMN:SSS-TA

Operation Charging

Speech and
signaling

Home PLMN of the

called party

Signaling
HLR
GMSC

Exch

Calling party

Fig. 1.5

PSTN

Party forwarded to

Call forwarding unconditional (PSTN->PLMN->PSTN)

Call Forwarding Conditional (No Reply, Busy, Mobile Subscriber Not Reachable)
Just as a normal mobile terminating call, this type of call is first routed to the visited MSC
of the called party and forwarded from there to a third party, provided that the requirement for the supplementary service has been met. Calls can be forwarded to another
mobile subscriber or to a subscriber in the fixed network.
Example: All three parties are mobile subscribers (see Fig. 1.6). The generated MCR
contain than the following specific information:

IN 8

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Speech and
signaling
Home and
visited PLMN
of the called party

Home PLMN
of the party
forwarded to

Called party

Visited PLMN of the

calling party

Signaling

Visited PLMN of the

party forwarded to
HLR
VMSC

Calling party

Forwarded-to
party

HLR

GMSC

VMSC

GMSC

VMSC

GMSC

GMSC

Exch

PSTN

Exch

Fig. 1.6

Exch

Exch

Call forwarding conditional (PLMN -> PLMN -> PLMN)

At the visited MSC of the calling party:
call type/transaction type: MOC
served mobile identity: calling party's IMSI
other party:dialed number (MSISDN of the called party)
supplementary service:
At the visited MSC of the called party:
call type/transaction type: CF
served mobile identity: called party's IMSI
other party: MSISDN of the party forwarded to
supplementary service: code of the supplementary service providing the call
forwarding
At the visited MSC of the party forwarded to:
call type/transaction type: MTC
served mobile identity: IMSI of the party forwarded to
other party:MSISDN of the called party or number of A-subscriber (project dependent)
supplementary service:

A30808-X3003-X458-2-7619

IN 9

OMN:SSS-TA

Operation Charging

Subscriber Controlled Input

A new MCR is generated upon successful completion of a subscriber controlled input,
the current record is closed beforehand. Successfull means here: all SCIs normally
handeled in the MSC, this means also those SCIs which are negative aknowledged
from the HLR.The record contains the following specific information:
call type/transaction type: type of subscriber controlled input (i.e. registration,
erasure, activation, deactivation, supplementary service interrogation)
served mobile identity: IMSI of the mobile subscriber
supplementary service: code of the affected supplementary service
Roaming (Interrogation)
A supplementary MCR can be generated (depending on the project) at the MSC carrying
out a routing-information interrogation to the HLR. For this purpose, the following code
points must be created with AMA=YES (see OMN:SSS-RO):
code points for all digit combinations which are created for the translation of
numbers transmitted as mobile station roaming numbers (MSRN) by foreign MSCs.
(The home MSC only performs the interrogation and is not the visited MSC of the
called subscriber- GMSC is not the VMSC.)
Essential code point features:
CR CPT:...DEST=<destination>, AMA=YES, ...;
code points for home mobile station roaming numbers. (The home MSC performs
the interrogation and is simultaneously the visited MSC of the called subscriber GMSC=VMSC).
Essential code point features:
CR CPT:...TRATYP=MOBTERM or MOBBOTH, AMA=YES,...;
The MCR for interrogation is generated precisely when:
the basic conditions for the generation of an MCR have been fulfilled (see 1.1.2)
the feature is available and activated in the MSC (MOD MSERVOPT)
one of the code points described above has been reached
the interrogation has actually been performed at the home MSC
the call setup is successful
The MCR for interrogation contains the following specific information:
call type/transaction type: roaming
served mobile identity: IMSI, MSISDN of the called party (or the party which is
forwarded to if the call has been forwarded to a mobile party)
MSRN
Unsuccessful Call Attempt
The individual project determines whether or not an MCR will be generated for unsuccessful call attempts (MOD MSERVOPT). This type of record can also be generated
when the call attempt cannot be charged.
The data records correspond (up to the connection type) to those successful connections.
Generation of the data record starts for MOC after recognition of a valid B directory
number. Data record generation for MTC begins with the seizure of a trunk to the BSS.
Data record generation for call attempts is interrupted as soon as the B subscriber
answers.

IN 10

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Short Message Service

As soon as a mobile subscriber receives or transmits a short message, an MCR can be
generated at his visited MSC (depending on the project). It is also possible to determine
on a project-specific basis whether these records are to be generated for successful
SMS transactions only or also for those which were unsuccessful.
SMS records are similar to those for speech or data connections, but they contain the
following additional information.
service center address
transmission result
If the SMS is being used in parallel with a speech or data connection, two separate data
records are created.
Transit Calls
MCR can also be generated for transit calls (depending on the project
MOD MSERVOPT), provided that the incoming trunk group has been created with
GCOS=AMATRANS.
Data record generation for call attempts is not possible here.
Transit calls are calls for which neither the calling nor the called subscriber is located in
the area of his home MSC and neither interrogation nor call forwarding are performed
by the home MSC.
An MCR for transit calls is generated at the home MSC only when no other mobile MCR
is generated.
When zoning is entered on the incoming trunk also the ZOPT has to be created with
BILLING=AMA. The trunk has to be created as an mobile trunkgroup (GCOS).
Announcements
An MCR is usually generated for a mobile originating call to an announcement only
when the announcement group (CR ANGRP) has been created with GCOS=CHARGABL. (Project dependend also for nonchargeable Announcements possible).
In-call announcements, i.e. announcements during calls in progress (e.g. in the case of
Call Hold or Call Waiting) must be created without a charge (i.e. no entry under GCOS).
Call Hold
The supplementary service Call Hold enables a mobile subscriber to interrupt a call in
progress and to use this channel for another outgoing call or to accept a waiting call.
Afterwards, the call on hold can be continued.
A separate data record is generated for each call.
The following applies to the case where mobile subscriber B puts a call in progress to
mobile subscriber A on hold and sets up a call to subscriber C.
Even after the call to mobile subscriber A is put on hold, the data record for the A B
connection is not closed, but continued as if there were no interruption. Only the name
of the supplementary service in use (Call Hold) is registered. The new connection
between mobile subscribers B and C is charged as usual. As a result, two data records
are created simultaneously for mobile subscriber B.
Types of records:
in the VMSC of mobile subscriber A, a normal MOC record
in the VMSC of mobile subscriber B, an MTC and an MOC record

A30808-X3003-X458-2-7619

IN 11

OMN:SSS-TA

Operation Charging

in the VMSC of mobile subscriber C, an MTC record.

Call Waiting
The Call Waiting feature allows a mobile subscriber to be informed of an incoming call
while he is busy. The called mobile subscriber can then answer, reject or ignore the
incoming call.
Generation of MCR:
If mobile subscriber B, during a call with mobile susbcriber A, receives notice of Call
Waiting from mobile subscriber C, the supplementary service used (CW) is registered
regardless of whether the incoming call is answered, rejected or ignored. The only
prerequisite for this information to be registered is that mobile subscriber B is in the
process of a call.
Assuming that mobile subscriber A initiated the call to mobile subscriber B, the following
records are generated in the VMSC:
of mobile subscriber A,
an MOC record
of mobile subscriber B:
an MTC record registering the supplementary service used, Call Waiting (and Call
Hold if the call in progress was put on hold to answer the incoming call) for the A
B connection, and
an MTC record for the B C connection if the incoming call was accepted
of mobile subscriber C:
an MOC record if the call from mobile subscriber B was accepted.
Multiparty
The supplementary service Multiparty allows a mobile subscriber to set up a speech
conference with up to 5 other subscribers.
In this case, separate MCR are generated for each individual connection. The contents
are the same as for normal MOCs or MTCs. The supplementary service used is registered only in the data record of the mobile subscriber controlling the Multiparty service.
Double Mobile Subscribers
Two mobile subscribers created in the HLR can be linked to each other by MML
commands in such a way that the currently "active" SIM (and thereby the "active" IMSI)
can be reached by dialing one of the associated MSISDNs (see OMN:SSS-SU).
This feature can be used by, for instance, subscribers wishing to use one SIM for business calls and another SIM for private calls.
Otherwise, the two mobile subscribers are completely independent. They have e.g.
different MSISDNs and IMSIs and can have different telecommunications and supplementary services.
Call charge registration is also separate for each subscriber. This means that records
are generated for each IMSI as for normal mobile subscribers.
As this feature is controlled by the HLR alone the VLR only has information on the
"active" mobile subscriber different MSISDNs may be registered in the MCR
(depending on the project).
Example
A double mobile subscriber with
1.IMSI-1: not active
MSISDN-1, teleservice "Telephony"

IN 12

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

2.IMSI-2: active
MSISDN-2, teleservice "Telephony" and supplementary service "Call Forwarding
Unconditional" active with FTNO (the number forwarded to) in the PSTN is called on
the MSISDN-1.
This MTC triggers a switchover to the active IMSI (IMSI-2), whereby the call
forwarding to the specified FTNO becomes effective. Then the MSISDN-1 (number
dialed) appears in the MCR, and the FTNO is registered in the data field "other
subscriber". Consequently, the MSISDN-1 linked to the IMSI-1 and the FTNO linked
to the IMSI-2 are entered in the record.

Call Back
Call back allows a mobile subscriber who is temporarily inaccessible in the PLMN (busy,
no paging reply or no reply) to redirect incoming calls to a personal voice mail box. The
personal voice mail box is a computer box in the PLMN (voice mail system VMS) and
represents a kind of call answering device in the PLMN. The mobile subscriber can call
up the recorded messages from the external computer box by means of an access code.
The subscriber is informed of a message by the Short Message. The mobile subscriber
can request the spoken messages from the external computer box with an access code.
The following data records can be generated:
SCI data record for activating, deactivating and service requests
Forwarding the incoming calls to the voice mail box
SMS data record for the subscriber information via stored messages
MOC data record for the mail box request
Direct Connection of Wired Digital Subscribers and PABXs
PABXs and wired digital subscribers can be connected to an MSC by means of an ISDN
primary access rate or basic access.
Call charge registration is carried out in the MSC to which the digital subscriber and the
PABX are connected. One can select the kind of charging (PLMN or PSTN) for all fix
subscribers in the installation mode by means of the command MOD MSERVREL.
The digit combinations for which MCR are to be generated are to be set via the zone
point with BILLING=AMA.
All incoming and outgoing calls are registered, as are subscriber-controlled inputs (SCI)
for call forwarding (only Call Forwarding Unconditional) made by PABX subscribers.
The MCR corresponds in structure to the one for mobile subscribers. It also includes in
addition a code, which allows the call to be allocated to a PABX-subscriber or to a digital
subscriber, and the ISDN basic service used.
Call charge registration is only possible if the following features are available in the MSC
(depending on the project, MOD MSERVOPT).
Charging of incoming/outgoing PABX calls
Charging of subscriber-controlled inputs made by PABX subscribers
Charging of incoming/outgoing calls from/to digital subscribers

1.1.3

Mobile Call Records: Administration

The billing data collected in the CP are processed into MCR.
upon call termination
upon intermediate saving for calls of long duration (e.g. after every 30 minutes)

A30808-X3003-X458-2-7619

IN 13

OMN:SSS-TA

Operation Charging

when the service is changed during an ongoing call (in-call modification)

The records are first transferred to a CP data buffer and then dumped to the duplicated
magnetic disk file IA.ICMCR as soon as the data buffer is full. At least two data buffers
are provided for the storage of currently generated MCR during this copying process,
which alternately record the billing data and copy them onto the magnetic disk. The data
can also be dumped from the CP data buffer to the magnetic disk file manually by MML
command (TRANS BUFFER).
The MCR magnetic disk file is a duplicated cyclic file. When the capacity level of the file
reaches a predetermined threshold (e.g. 75%), an alarm is indicated at the system
panel. A copy file should now (at the very latest) be initiated and afterwards, the originating cycle file should be released for rewriting.
It is also possible to copy only selected MCR (e.g. for certain call types)
(ACT BILLREC).
So as to prevent the record from being deleted and the rest of the data from being lost
after such a selective transfer, the last copy of an MCR is automatically copied
completely. This means that selective transfer of billing data is only possible if the
number of copies required, specified in SET FGRPATT using SAFCOP, is greater than
one. So as to ensure that the parameter SAFECOP is observed during selective file
transfer by FTAM, the MCR can only be reset explicited with the command
REL CYCFILE, even from a remote terminal.
Contents of Mobile Call Records
The charge data collected during the call are formatted in a precisely predetermined
manner and stored in this form as an MCR. The content of the MCR can be created in
the customer specific manner with the command ENTR BILLREC (in istallation mode).
Additionally the content of these MCR varies according to the type of call made (e.g.
mobile originating call, mobile terminating call, interrogation, call forwarding, subscriber
controlled input).
In Table 1.1 (example for a MCR - project dependend), the fields foreseen for each
particular type of record are marked with an x; fields marked with a do not apply. If
information is not available for a certain field that should actually be filled (e.g. the
number of the calling party is unknown at the MTC), a filler is provided to preserve the
internal structure of the record. Some of the fields marked with an x are optional, i.e.
they can be completely omitted (e.g. advice of charge information).

IN 14

A30808-X3003-X458-2-7619

Operation Charging

MCR content

OMN:SSS-TA

MOC

MTC

Interrogation

CF

SCI

SMS

Emerg.
calltrace

Transit

Record type (e.g. single record)

/+

/+

Call type (e.g. MOC, interrog.)

/+

/+

Time quality (secure, insecure)

/+

/+

/+

/+

IMEI (of served subscriber)

MSRN (* if VMSC=GMSC)

(*)

Transaction identity (differentiating

between parallel transactions of an MS)

Other number (calling party for transit)

Other party (e.g. no of calling party at MTC)

/+

/+

SPC or name of registering MSC

/+

/+

SPC of originating/terminating MSC

Cell identity

Incoming trunk group

Outgoing trunk group

Start of recording: date, time

/+

/+

Call duration

/+

/+

Teleservice (e.g. telephony)

/+

/+

Bearer service (e.g. data transmission)

Transmission type (full rate/half rate)

MS classmark

AOC (parameters for tariffs utilized)

Charge type (charged, non-chargeable)

Charge units

Tariff category

Charge registering disturbance

/+

/+

Third party

Supplementary service

MS access rate (data transmission rate)

Address of service center

IMSI (of served subscriber)

MSISDN (of served subscriber)

Reason for call disturbance

Tab. 1.1

Example of MCR(+ applies to PBX subscribers)

A30808-X3003-X458-2-7619

IN 15

OMN:SSS-TA

Operation Charging

Mobile Call Records: project-specific processing

In the MCR, the system ensures that certain standard information is available. Just
which information is used to calculate subscriber charges depends on the individual
project. As a consequence, the MCR s undergo project-specific formatting (client record
formatting). This formatting contains only the data actually needed for data postprocessing or data required by the network provider for other reasons. The actual reformatting is done automatically during the copying process (e.g. from magnetic disk to
magnetic tape) or after storing e. g. for use of FLAM. The files thus copied and formatted
are then sent to data post-processing centers, where the charges are registered for the
individual mobile subscribers.
FLAM compression for billing files
A reduction in the time for transmitting billing files to a post-processing center can be
achieved by compression with the project-dependent FLAM (Frankenstein Lidzba
Access Method).
The compression can only be used for the following files:
IA.ICMCR (PLMN charge registration)
IA.ICINA (IN calls)
IA.ICAMA (fixed network charge registration in the CSC)
The following conditions must be fulfilled:
the feature must implemented and activated (project-dependent,
MOD MSERVOPT: FEAT=FLAMCOMP)
the feature must be allocated (ENTR FILEFEAT) to the file and activated
(ACT FILEFEAT).
If compression is activated for a file, the data of the originating file are continuous
compressed (e.g. the file IA.ICMCR) and written to a "FLAM" file. The name of the
"FLAM" file consists of the name of the originating file with the extension ".FLAM" (e.g.
IA.ICMCR.FLAM). No other files may be generated with the extension ".FLAM" in order
to avoid breakdowns in the network nodes.
It can be determined whether the originating file is to be released after compression
(normal case) or must be kept (e.g. for test purposes) (ENTR FILEFEAT, parameter
ACTION).
The originating file is released after compression (ACTION=REL) even if several store
copies are made under SET FGRPATT .
The compressed files can be transmitted to tape (TRANS FILE) as well as with FTAM.
There are two possibilities:
transmission of all data compressed before start of transmission
transmission of all generated data up to the start of transmission
A copying service procedure for compressing all generated data before transmission
(e.g. SET FGRPATT:FGRP=xxx.FLAM,PRNAM=MUUT4, condition: file group is
created with CR FGRP) must be allocated to the "FLAM" file before the start of transmission of data collected in the MCR file.
Backup files to be transmitted as compressed files must be allocated to the copying
service MUUTJ. The names of the backup files must contain the original file name (e.g.
B.SET FGRPATT:FGRP:BU.IA.ICMCR, PRNAME=MUUTJ).

IN 16

A30808-X3003-X458-2-7619

Operation Charging

1.1.4

OMN:SSS-TA

Hot Operation
The term hot operation encompasses all cases in which MCR are generated supplementarily and/or formatted during an ongoing call or immediately after its termination
and sent to a processing center designated for that purpose.
There are two applications:
hot billing
emergency call trace
The hot billing feature is allocated to a mobile subscriber as a supplementary service
(see OMN:SSS-SU).
Hot billing
To utilize the hot billing feature, the following prerequisites must be fulfilled:
for the served mobile subscriber, the hot billing service must be registered in the
VLR database
the feature must be implemented and activated in the MSC/VLR (depending on the
project)
MCR for MOC, CF and MTC (not for transit calls and roaming) for the authorized
subscriber are formatted immediately after call termination and sent to the appropriate
processing center. The MCR is subsequently marked at the MSC as having been
successfully or unsuccessfully transmitted. The MCR is then further processed at the
MSC as described above.
This treatment of billing data consequently does not change normal billing conducted
via MCR. It does, however, additionally enable the network provider to rapidly compile
detailed billing independently of the usual data post processing rhythm.
Emergency call trace
The prerequisite for utilizing the emergency call trace feature is that it is implemented
and activated in the MSC/VLR (depending on the project MOD MSERVOPT).
Whenever the system identifies a call as an emergency call, an MCR is immediately
i.e. during the ongoing call generated, formatted and transmitted to the appropriate
processing center. This record contains essential information concerning the identity of
the mobile subscriber (MSISDN; IMSI; IMEI)(if known), start time and date and location
(i.e. cell identity CI, LACOD), Emergency Centre number. After the call has been terminated, this emergency record and the MOC record (which is generated in all cases)
are further processed at the MSC as described above.
The system identifies an emergency call either because the call has been set up by activating the emergency call key at the mobile station or because the number dialed has
been created as an emergency call number (see OMN:SSS-RO).
In case the connection to the emergency call center (X25) is not available, the ECT data
record is saved at the end of the call like a normal MCR data record.
This data record is identified as non-successful and output locally as emergency printout
(precondition being that the "immediate printout" feature has been activated with
ACT IAFEAT).

1.1.5

Zones and Tariffs

Each standard MCR contains all the information needed to correctly determine the
charges for a given call (e.g. subscriber identity, MSC identity, call time and call duration,

A30808-X3003-X458-2-7619

IN 17

OMN:SSS-TA

Operation Charging

services utilized, etc.). The charges are then calculated in data post processing or
directly in the MSC.
To allow charges to be calculated immediately at the MSC or in the mobile station (AoC),
tariffs, i.e. combinations of parameters, can be defined for determining the number of
charge units in relation to the duration of the call. These calculated charge units are
stored in the MCR. The parameters used for registration can also be stored in the MCR.
When the parameters are transmitted to the mobile station, the mobile station can calculate the charge units autonomously and display an advice of charge to the mobile
subscriber.
For administration of call charge registration, a distinction must be made among the
mobile-specific calls, such as mobile originating calls (including call forwarding) or
mobile terminating calls and calls from wired digital subscribers and ISDN PABXs,
connected via the EDSS1 protocol to the MSC.
While charge registration of MTCs depends only on the home PLMN of the served
mobile subscriber, the tariff for MOCs includes other parameters such as call origin,
dialed digit combination and the time of day and week.

E1UPTI

Charge
units

E1UPTI
E2SPTI

E1UPTI
E2SPTI

E1UPTI
E2SPTI
E4INU

E7SPITI
Time

1.
Start of call

Fig. 1.7

2.

3.

3.

3.

4.
Call
termination

Charge units based on a mobile tariff

Charging for the above-mentioned traffic types is based on a mobile-specific tariff.
Depending on the project, a maximum of 522 tariffs may be created. A tariff is determined by means of the following parameters:
E1UPTI
number of charge units per time interval
E7SPITI
duration of initial time interval in seconds
E2SPTI
duration of all subsequent time intervals in seconds (i.e. clock for
additional charging)
E4INU
basic charge per call (number of charge units)
E3SCF
scaling factor (factor for multipying the number of charge units, calculated from the other parameters)

IN 18

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

The number of charge units for a given call is determined as follows (see Fig. 1.7):
1. At the start of the call, the number of call units defined in E4INU (basic charge) is
stored in a counter. At the same time, a timer is started, whose value is defined in
E7SPITI. (If E7SPITI=0, E2SPTI is used instead.)
2. When this timer expires, the number of charge units defined in E1UPTI is added to
the current counter. At the same time, a timer is started, the value of which is defined
in E2SPTI.
3. When this timer expires, the number of charge units defined in E1UPTI is added to
the current counter. At the same time, the timer is restarted. The procedure
described here in step 3 is then repeated until the call has been terminated.
4. The accumulated count at the end of the call is multiplied by E3SCF. Thus, the total
number of charge units is calculated for that particular call. (This multiplication is not
shown in Fig. 1.7.)
Consequently, for the call shown in Fig. 1.7, the following number of units N is obtained:
N=(E4INUI+4xE1UPTI)xE3SCF.
Example:
A tariff is defined by the following parameter values:
E1UPTI
1 unit/interval
E7SPITI
20 seconds/interval
E2SPTI
15 seconds /interval
E4INU
2 units
E3SCF
2
When entering the appropriate MML command, it is important to bear in mind that the
parameter values actually to be entered are generally multiples of the units used here
(e.g. 1 second per time interval corresponds to an input of E7SPITI=10).
Consequently, the following number of charge units is obtained in relation to the duration
of the call:
Call
duration
(sec.)

Charge units based on

E4INU

E7SPITI

E2SPTI

Char
ge
units
(total)

10

20

30

60

10

90

14

120

18

Tab. 1.2

Charge units dependent on call duration

In the case of unsuccessful call attempts, the charge is calculated from the product of
the basic charge determined with E4INU by the scaling factor E3SCF.
In case of charging troubles for mobile subscribers, the LTGs might not be loaded with
correct charging information. The reloading of the LTG can be obtained by entering the
command MOD PLMNTAR without parameter specification.

A30808-X3003-X458-2-7619

IN 19

OMN:SSS-TA

1.1.5.1

Operation Charging

Zoning for Originating Calls

Zoning for Wired and PABX Subscribers
The generation of MCR (if PLMN charging is used - project dependend) for certain digit
combinations is controlled via the zone point for wired subscribers (CR ZOPT).
In the case of digit combinations for which records are to be generated, BILLING=AMA
must be created.
Zoning for Mobile Originating Calls and Call Forwarding
For outgoing calls (mobile originating calls, MOC) and the forwarded part of a diverted
call (i.e. the part between the original called mobile subscriber and the forwarded-to
subscriber), tariffs and zones are administered in the same manner. The same tariffs
and/or zones may also be utilized. A zone is allocated to a certain call type (MOC, CF)
when the zone point (CR MZOPT) is created with parameter CHTYPE.
For these applications, several tariffs can be defined which are valid when the relevant
prerequisites have been fulfilled. A tariff of this kind consists of parameters E1UPTI,
E2SPTI, E4INU and E7SPITI. addition, the system allocates parameter E3SCF to this
tariff. This parameter is taken from the tariff created for mobile terminating calls (MTC)
for the home PLMN of the served mobile subscriber. The following criteria determine
which of the created tariffs is used for a given call:
the digit combination dialed
the origin of the MOC (optional)
the type of resource used (full or half transmission rate, call attempt)
weekday category and time of day
call type (MOC, call forwarding)
In order to have a tariff available for all possible cases, the following objects must be
administered:
mobile tariff: Every parameter combination from which the number of charge units is
calculated in relation to call duration must be created as a tariff.
tariff category: A tariff category defines which tariff will be switched over to at which
time (i.e. time of day and weekday category). Up to 32 tariffs and switchover times
may be allocated to one tariff category. A weekday category may have up to 30
different switchover times.
mobile zone: A mobile zone allocates a tariff category to call types featuring different
network utilization. Tariff categories can be allocated for the following call types
within a given zone:
calls with a full transmission rate
calls with a half transmission rate
unsuccessful call attempts
a mobile-specific zone point defines which mobile zone will be allocated a combination of:
selected digits
call origin (ORIG2) cell-dependent or trunk-group-dependent (only for MOC)
call type: MOC or call forwarding
If no ORIG2 is entered, the default value 255 is used. In additional to trunk groups, individual radio cells can also be allocated an origin code (ORIG2), which is used for charge
calculation by means of zone points (project dependend, MOD MSERVOPT:
FEAT=CELLDCH). If an ORIG2 value is defined for a cell and the feature is active, the
ORIG2 value entered for the trunk group between BSC and MSC is overwritten by the
ORIG2 of the cell during zoning in the MSC.

IN 20

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

So as to ensure accurate charge calculation, there must be zone points for all digit
combinations that can be dialed and are required for interrogation. It is not necessary to
define a separate zone point for each code point (or vice versa). However, it must be
ensured that each of these digit combinations is covered by a zone point.
The parameters are entered in the form of digits (without traffic discrimination digits) and
code type

CODE

TYPE OF CODE

Zone point

49179

INAT

0049179

179

NAT

0179

0012345

UNK

0012345

49179

COMB

a) CC is the own country code:

0049179
0179
b) CC is not the own country code
0049179
049179

Tab. 1.3

Example of mobile-specific zone points

The system then uses this information to put together the digit combination to be dialed.
Tab. 1.3 shows an example of the zone points created from this information
(CR MZOPT) (in the example with CC=49, NDC=179, the national traffic discrimination
digit 0 and the international traffic discrimination digit 00).
As the subscribers of the own PLMN can be reached by dialing a directory number with
or without the country code (CC), zone points must be created for both possibilities.
These two zone points are automatically generated by entering the code type "COMB",
provided that the CC is the subscriber's own country code. Only the international traffic
discrimination digits are added Tab. 1.3 for all other digit combinations.
Calls to the packet network (dedicated PAD access) are zoned by using the dialed digits
(short code). Zone points for these short codes must be created with the code type
"UNK". MOC charge registration for such a "4x bearer service" (data transmission to the
packet network) includes only the circuit-switched part that leads to the PAD, and not
the use of the PSDN itself.
Zones 0 and 127 have a special position and cannot be administered. Zone 0 is
reserved for no charge calls, and zone 127 is reserved for calls that are to be zoned in
the next node.
For each tariff category, the system automatically selects the tariff producing the lowest
number of charge units at a call duration of 2 minutes. These so-called lowest tariffs
are stored in an internal table. This table is always updated when another tariff becomes
the lowest tariff for a given category due to a change in the created tariffs and/or tariff
categories. The lowest tariffs are transmitted by the CP to all GPs that might be incapable of correctly performing the tariff switchovers as foreseen in the tariff categories
(e.g. in case of a GP or CP recovery, configuration of an LTG, system time insecure).

A30808-X3003-X458-2-7619

IN 21

OMN:SSS-TA

Operation Charging

This prevents individual calls from being overcharged. As soon as the exceptional status
has been terminated, the lowest tariffs are automatically replaced by the tariffs that are
valid at that particular time.
It is generally recommended that a switchover time be foreseen at midnight (00:00
hours) for each weekday category. Since switchover times are always entered for a tariff
category, the tariff that was valid for the previous day will continue to be valid up until
the first switchover time of the next day. If there is no switchover at midnight, charges
registered at the beginning of the new day could either be too high or too low. Example:
On a normal weekend, the evening tariff on a Sunday is to be valid until the first
switchover on Monday. As soon as a variable holiday is allocated to the FULL
WEEKEND weekday category, the weekend tariff will initially be valid for the next
working day in this case as well, although this may not be desired.
Creating zoning for mobile originating calls examples:
Two different zone points are to be created for directory numbers of the own PLMN
(CC=49, NDC=179) belonging to two different mobile zones. As a weekday category,
the designation "working day" shall apply to the days Monday through Friday; Saturday
and Sunday shall be assigned the HALF WEEKEND or FULL WEEKEND categories. A
total of five different tariffs are required.
The following MML commands are entered:
ENTR MTAR: MTAR=1, E1UPTI=...
(The definition of the parameter set follows.)
Result: Mobile tariff 1 is created.
The same procedure applies for tariffs 2 through 5.
ENTR PLMNTAR: NETW=26203, E3SCF=100;
Result: For all mobile subscribers whose IMSI begins with MCC=262 and MNC=03,
the charge units calculated using the tariffs defined here are multiplied by a factor of
1. With this command, a multiplier must be created for the charge units for each
PLMN whose mobile subscribers may utilize sevices. (If charges are also to be
registered for mobile terminating calls, the command ENTR PLMNTAR must be
entered with additional parameters that define the accompanying tariffs.)
ENTR MTARCAT: MTARCAT=10,
SWTAR=00001WO & 00001EH &
00001EF & 08003WO &
08003EH & 08003EF;
Result: In this tariff category, there is a switchover to tariff 1 on all days at midnight
(00:00 hours) and to tariff 3 at 8 a.m. (08:00 hours).
ENTR MTARCAT: MTARCAT=20,
SWTAR=00002WO & 00002EH &
00001EF & 08004WO &
09005EH & 09005EF;
Result: In this tariff category, there is a switchover to tariff 2 at midnight (00:00 hours)
from Monday through Saturday, and to tariff 1 on Sundays at midnight. From
Monday through Friday there is a switchover to tariff 4 at 8 a.m. and to tariff 5 at 9
a.m. on Saturdays and Sundays.
CR MZONE: ZONO=1, FULL=10;
Result: In zone 1, tariff category 10 is used to calculate full transmission rate
charges.
CR MZONE: ZONO=2, FULL=10, ATTEMPT=20;
Result: In zone 2, tariff category 10 is used to calculate full transmission rate

IN 22

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

charges, and tariff category 20 is taken to register unsuccessful call attempt

charges.
CR MZOPT: CODE=49179COMB, MZONO=1, CHTYPE=MOC;
Result: For every mobile originating call to a number beginning with the digit
sequence 0049179 or 0179, charges are calculated (for full rate transmission)
according to the conditions defined in tariff category 10. Unsuccessful call attempts
are not charged.
CR MZOPT: CODE=123UNK, MZONO=2, CHTYPE=MOC;
Result: For every successful mobile originating call to a number beginning with the
digit sequence 123, charges are registered according to the conditions defined in
tariff category 10. Unsuccessful call attempts to numbers beginning with the digit
sequence 123 are also chargeable the charges are calculated according to the
conditions defined in tariff category 20, i.e. the number of charge units indicated in
parameter E4INU of the valid tariff are billed for an unsuccessful call attempt.

Note:
Additionally there is the possibility to create zoning information as used digits, zoning in
a other node, ORIG2 ... by means of the feature Subscriber Dependent Digit Processing
and Feature Control (SDDPFC) as shown in the OMN:SSS-RO.

1.1.5.2

Tariffs for Mobile Terminating Calls

Charge treatment for mobile terminating calls (MTC) depends solely on the home PLMN
of the served mobile subscriber. A specific tariff must be created for every PLMN whose
mobile subscribers may utilize services. A tariff for mobile terminating calls must also be
created for the home PLMN.
A tariff for an MOC is defined in a similar manner, complemented by the additional
entering of a parameter E3SCF. The number of charge units, which is calculated from
the other parameters in relation to call duration, is, for MOCs as well, multiplied by the
factor E3SCFentered here for the PLMN of the calling mobile subscriber. Consequently,
for every PLMN (also for the home PLMN), a tariff must be created for mobile terminating calls even when incoming calls are non chargeable.
A tariff is allocated to a PLMN by specifying the mobile country code (MCC) and the
mobile network code (MNC). Since the MCC and MNC are a part of the international
mobile subscriber identity (IMSI), the tariff valid for every mobile subscriber can be
selected at the MSC.
A change in the PLMN tariffs immediately affects all newly set up calls. Calls that are
already in progress are still charged according to the old tariffs. This also applies to
mobile originating calls inasmuch as parameter E3SCF is affected by the change.
Creating zoning for mobile terminating calls examples:
Tariffs for mobile terminating calls are to be created for mobile subscribers of the home
PLMN (with MCC=262 and MNC=03) and of a foreign PLMN (MCC=206 and MNC=04).
The following MML commands are entered:
ENTR PLMNTAR: NETW=26203, E3SCF=100, E4INU=10;
Result: For mobile subscribers of the home network, 1 charge unit is registered for
each mobile terminating call. With MOCs and MTCs, the total number of charge
units is multiplied by a factor of 1 upon call termination.
ENTR PLMNTAR: NETW=20604, E1UPTI=10, E2SPTI=150, E3SCF=200,
E4INU=20, E7SPITI=200;

A30808-X3003-X458-2-7619

IN 23

OMN:SSS-TA

Operation Charging

Result: For mobile subscribers whose IMSI begins with MCC=206 and MNC=04, all
mobile terminating calls are charged according to the tariff defined here. The charge
units for mobile originating calls and call forwarding for these mobile subscribers are
calculated according to the tariffs created therefor and subsequently multiplied by
the factor 2 defined here in E3SCF.

1.1.5.3

Surcharge
A surcharge is a fixed number of charge units billed for a call in addition to the registration of charges based on call duration and the valid tariff. This surcharge is entered when
creating the appropriate zone point. The number of additionally registered charge units
is recorded in the MCR of the mobile originating call and can thus be billed to the served
mobile subscriber. In this manner, for example, access to services by way of certain
zone points can be additionally charged. The network provider could, for example,
forward this charge to the service provider while the tariff-defined charges are billed for
the utilization of the PLMN.

1.1.5.4

Call Attempt
Depending on the project, charges may be registered for unsuccessful call attempts
(MOC and CF attempts). Zoning can be created as it is for mobile originating calls,
whereby in defining the zone, the parameter ATTEMPT is allocated a tariff category.
Hence, for every call setup, as long as the related feature has been activated at the
MSC, the tariff valid at that time for call attempts is initially used to register the charge
units. As soon as the call setup has been successfully completed (i.e. the called party
answers), this tariff is replaced by the tariff for successful calls. If the attempt is not
successful (e.g. the party does not answer or cannot be reached), the served subscriber
will be billed for the minimum number of charge units contained in parameter E4INU of
the call attempt tariff.

1.1.5.5

Subscriber Controlled Input

Subscriber controlled inputs are zoned as mobile originating calls.
Zoning is based on the transmitted (GSM-specific SS) code for the requested supplementary service.
The required mobile-specific zone points are to be created using:
CR MZOPT: CODE=SS code UNK, MZONO, BILLING=AMA, CHTYPE=MOC;

1.1.5.6

Advice of Charge
The advice of charge feature (AoC) makes it possible to provide the mobile station with
information that allows it to autonomously calculate and display or otherwise evaluate
charge units accumulated during a call (MOC, MTC).
A distinction is made here between Advice of Charge Information Level (AOCINFO) and
Advice of Charge Charging Level (AOCCHRG).
AOCCHRG enables immediate charging for applications in which the mobile subscriber
administered by the network operator does not use the mobile station himself but allows
it to be used by others, e.g. as in the case of rented telephones. Therefore a MZOPT for
the dialed number must be created. If no MZOPT for the dialed number is created, the
MSC interrupt the call immediately.
AOCINFO is used only to "inform" the mobile subscriber of the current charging level for

IN 24

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

the call in question (display of charges). If for this level no MZOPT is created, there is
no display of the charge but the call will be established.
A mobile subscriber can be assigned either the AOCINFO feature or the AOCCHRG
feature.
The following prerequisites must be fulfilled for the advice of charge to be displayed to
the subscriber:
For the AOCCHRG feature, Phase 2 of the GSM Recommendations is a prerequisite in the case of the network elements involved and the MS.
The AOCINFO and/or AOCCHRG features must be activated in the HLR. Only then
will the HLR transmit this supplementary service information along with the
subscriber data to the VLR.
(DISP MSERVOPT: SSERV=AOCINFO or AOCCHRG)
The AOCINFO and/or AOCCHRG features must be activated at the MSC/VLR.
(DISP MSERVOPT: SSERV=AOCINFO or AOCCHRG)
The subscriber must be created in the HLR with the corresponding AoC feature.
(ENTR GCSERV)
The mobile-specific tariffs must be created.
If the AoC feature is activated in an MSC/VLR (depending on the project), it checks,
upon call setup (MOC, MTC), whether the supplementary service AoC (Information or
Charging Level) is registered in the VLR for the served mobile subscriber. If so, the MSC
transmits the parameter set (tariff) currently valid for the call type to the mobile station,
thereby enabling the charges to be calculated and displayed by the mobile station (AoC
Information Level).
If the supplementary service AoC Charging Level is registered in the VLR for the mobile
subscriber concerned, a timer is started in the MSC after the tariff is sent to the mobile
station and the MS is expected to reply.
The reply confirms that the mobile station has the AOC Charging Level feature. Once
this confirmation has been received, the timer is cancelled. If no such confirmation is
received, the call is released when the timer expires. This time can be set using MOD
TIOUT (Timer 116), (see OMN:SSS-SY).
Since mobile subscribers with the AoC Charging Level supplementary service have to
use this service in all cases, any location updates and call requests in networks that do
not support AoC Charging Level are rejected.
In the case of any difficulty in determining the current tariff, the call is released.
If the system switches over to a new tariff during a call in progress, the new parameters
are immediately transmitted to the mobile station. Here the mobile stations with the AoC
Charging Level are informed before those with the AoC Information Level feature.
Call charge information for use of the Call Hold or Multiparty supplementary services are
transmitted to the mobile stations as soon as another subscriber answers the call. These
calls are charged as a separate call.
Charges for call forwarding, subscriber controlled input and unsuccessful call attempts
are not displayed.
Since the AoC is calculated independently of the generation of MCR and their evaluation
in related data post-processing procedures, the netwok provider is responsible for
seeing to it that the methods of calculation are adapted accordingly.
Deviations between the AoC and actual charges
change of service during an ongoing call (in-call modification): In this case, the
system creates a new MCR and uses the tariff valid for the new service to calculate

A30808-X3003-X458-2-7619

IN 25

OMN:SSS-TA

Operation Charging

1.1.6
1.1.6.1

the charges at the MSC. The new parameter set is, however, not transmitted to the
mobile station, which may consequently result in deviations between the actual
charges and those displayed at the mobile station.
minor deviations can arise between the calculated AoC charge units and the exact
evaluation of the MCR. This is due to the fact that minimal time delays can occur
between the switchover time from one tariff to another at the MSC and the instant at
which the tariff is available at the mobile station.
surcharge: Charge units additionally billed as a surcharge are not transmitted to the
mobile station and are consequently not displayed there.

Call Charge Registration in the Intelligent Network (IN)

General
The term Intelligent Network stands for the concept of a network architecture valid for all
telecommunications networks. The basic idea is the introduction of a control level which
contains centrally the service logic or service data, therefore more effectively controlling
the processing of existing and new services.
The following components are provided for the processing of IN services:
Service Switching Point (SSP)
Service Control Point (SCP)
Service Management Point (SMP)
Intelligent Peripheral Nodes (IP)
This manual is only concerned with the SSP function. An SSP is typically integrated in
an MSC or an CSC.
Such a network node within the PLMN is called a M-SSP (see OMN:SSS-CCS7).
The introduction of services such as
freephone
televoting
universal number, etc.,
in the intelligent network (IN) places completely new demands on the charge registration
facilities. These are met by a revolutionary concept for the charge registration of IN calls.
The basic concept is that both parties, i.e.
the calling party
the service subscriber (often the called party)
can be assigned a proportion of the call charge which is incurred.
The question Who pays what? is answered according to the particular IN service used.
There are two basic methods of charge registration for IN calls, depending on where the
charges are registered:
call charge registration by the Service Control Point (SCP) or the Service Management System (SMS);
call charge registration by the Service Switching Point (SSP).
Charge registration by the SCP/SMS is based on the creation of data records for each
IN call. The data required are collected in the SCP (on the basis of the call data supplied
by the SSP, which are transferred to the SCP/SMS at regular intervals). The customerspecific records are created from this in the SMS.
Charge registration by the SCP/SMS is only used for billing the service subscriber.

IN 26

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Charge registration by the SSP is based on the existing call charge functions in the telephone network. The SCP can affect the charge registration, e.g. by transmitting/predefining the zone number to be used.
Charge registration by the SSP can be used for billing both the service user and the
service subscriber.

1.1.6.2

Terminology
Service provider
The service provider is the telephone company that offers IN services to the service
subscriber, for instance, freephone.
Service subscriber
The service subscriber is, for example, a mail order company which accepts the charges
for orders placed by telephone.
Calling line
The calling line in an IN call is the calling party. The calling line can be either the service
user or the service subscriber.
Service user
The service user is, for example, a customer who places orders with a mail order
company free of charge.
Charge registration for the calling line
Normally the calling line's charges are registered in the PLMN by means of PLMN
methods. The IN (SSP/SCP/SMS) has the options of sending
free of charge, or
the zone
The call charge method is determined in the PLMN; any billing data are written to the
PLMN file IA.ICMCR.
Charge registration for the service subscriber
The call charges are assigned to a line service number which is determined by the SCP.
This line service number belongs to an IN service subscriber.
The call charge method is determined in the PLMN; any billing data are written to the
PLMN billing file IA.ICINA.
Trigger profile
The trigger profile is created in the SSP and specifies how the particular IN service is to
be processed.
IN-specific charge
This term refers to the determining of a zone, depending on the IN service used, but
independently of the actual destination of the call.

A30808-X3003-X458-2-7619

IN 27

OMN:SSS-TA

Operation Charging

Flexible charge registration

The SSP can change zone or create a new data record when a call is set up to a new
destination (the primary destination is busy). This includes calls to the intelligent
periphery (IP).
Divided charge registration
This term denotes simultaneous billing of two parties engaged in an IN call, usually the
calling line and the service subscriber. In some instances the charges have to be split
between two different service subscribers.
Ascending branch
This is one part of an IN call: from the calling party to the SSP.
Descending branch
This is the second part of an IN call: from the SSP to the called party.

1.1.6.3

Charge Registration for the IN Services: General

The question of who has to pay for what must be dealt with separately for each IN
subscriber. The amount of the charges to be paid by the calling line and/or the service
subscriber is dependent on the particular service. In addition, due account must be
taken of the network-specific aspects (location of zoning, signal repertoire of signaling
system, etc.).
There are three options for registering charges for IN services:
1. charge registration only by the PSTN
2. charge registration only by IN components
3. charge registration divided between PLMN and IN.
Example
The charges for the universal number (UN) service can be registered as follows. The
charge total is divided between the calling line and the service subscriber (called
party). The user is charged for the ascending branch (from the calling party to the
SSP). One of the conventional methods is employed for this (e.g. pulse metering).
The service subscriber offering the UN pays for the descending branch (from the SSP
to the called party). An IN-specific billing ticket is created for this subscriber.
The SSP detects from the dialed digits that the call is an IN call (via the code point). It
then branches to the relevant trigger profile in the CP. As a result of the subsequent
communication with the SCP, the SSP obtains the actual directory number of the called
party and the corresponding zone.
From MZOCHA=ZONINHI in the command CR MZOPT, the SSP knows that it must use
the zone sent by the SCP.
In the IN, data records are only created for the successful calls. Consequently, the
service subscriber only receives his data record if the call to the called party was set up
successfully.

1.1.6.4

Administration by MML
Each IN call must be zoned before a SCP dialog can start. All trunk groups between
MSC and base station have to be created with GCOS=ZON.

IN 28

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

There are two possibillities for zoning: zoning using the dialed digits or zoning using
additional the SCM digits.
If INTRIG created with GENPROP=PROP6 than zoning is done by means of the dialed
digits, if not zoning is done by means of the SCM digits as prefix.
Therefore one has to create the zone points for these different possibillities if used.
It is not possible to create MZOPTs with MZOCHA=NOPULSE. For charge free zones
one can create: CR MZONE = ZONO= 1...511, Full=0 and allocate the MZOPTs to this
zone.
Charge registration for the calling line in the PLMN
The zone points are created in the MSC of a PLMN. The charges are only assigned to
the calling subscriber.
Zoning in the home exchange:
CR MZOPT: CODE=0180, MZONO =268, BILLING=AMA;
Zoning in a higher-level exchange in the telephone network; charge registration in
the home exchange:
CR MZOPT:CODE =0190, MZOCHA=ZONINHI, BILLING=AMA;
Charge registration for the service subscriber in the IN
Activation of registration of the IN-specific billing data records:
ACT IAFEAT: TYPE=INA;
Allow zoning information to be accepted from the SCP:
CR MZOPT: CODE= ... , ... , TKZOINF=YES;
The SSP use the zones as send from SCP with one exeption: if chargeband number 1
is send zone 127 is used.
Charge registration divided between PLMN and IN
Four steps are required for an IN call:
1.
2.
3.
4.

The CCS7 connection from the SSP to the SCP must be established
The triggers in the CP must be entered and activated (CR INTRIG, ACT INTRIG)
The IN-specific announcements must be prepared (CR INC)
The relevant trigger in the CP is activated by the identification of an IN call.

The code points contain a reference to the trigger profile in the CP (by means of parameter TRATYP). This activates communication with the SCP. The zone points are created
by way of ZOCHA=ZONINHI (in the SSP). The SCP sends the actual called party
number and the zone to be used.
CR MZOPT: CODE=0190, MZOCHA=ZONINHI, BILLING=AMA;
Creation of the trigger profile for the freephone service:
CR INTRIG:PRID =FPHS1, SKEY=31, ... ;
Creation of the code point:
CR CPT:CODE =0130, TRATYP=IN6FPHS1;
Activation of the trigger profile:
ACT INTRIG: PRID=FPHS1;
Zone 355 is to be used for zoning:
CR INTRIG: PRID=<trigger-ID>, SKEY=<service>, ... CHGINF,=ZONE355;

A30808-X3003-X458-2-7619

IN 29

OMN:SSS-TA

Operation Charging

The value for <trigger-ID> must be identical in commands CR INTRIG and CR CPT.
If the call charge data are recorded in the SSP, tariffs must be entered for all zones used
(before the zone points are created) ENTR TAR:; ENTR TARSW
Note:
Additionally there is the possibility to create zoning information as used digits, zoning in
a other node, ORIG2 ... by means of the feature Subscriber Dependent Digit Processing
and Feature Control (SDDPFC) as shown in the OMN:SSS-RO.
Charge registration of IN calls in MSC without IN-function
The following zonepoints are to create for zoning in a overlay configuration:
charge free calls
CR ZOPT : CODE=...., ZOCHA=CONZON;
Zoning in a higher networknode or in a SCP
CR ZOPT : CODE=...., ZOCHA=ZONINHI;
zoning in the own MSC with the option to overwrite the zone-information by SCP
CR ZOPT :CODE=...., ZONO=<zono>, TKZOINF=YES;

IN 30

A30808-X3003-X458-2-7619

Operation Charging

1.2

OMN:SSS-TA

Interadministration Revenue and Statistics (IARA)

A large proportion of telephone communication is conducted at national and international long-distance level. Depending on a PLMN or PSTN telecommunication structure,
subscribers may leave a PLMN service area at the national or international level when
they call a subscriber in the service area of another PLMN or PSTN. In order for revenue
from such calls to be distributed among the PLMNs and PSTNs, the traffic between the
service areas is registered. The revenue accounting is based on the volume of traffic. It
records call data from selectable traffic relations between originating trunk groups and
destinations or routes.
In the D900 system, a flexible procedure geared to administrative requirements is available for revenue accounting between the different networks. The IARA (Interadministration Revenue Accounting) method can be employed for revenue accounting between
the different administrations of a single country as well as those of different countries or
e.g. between two MSC. Thus, IARA can be used, for example, in gateway mobile
services switching centers (GMSC) or PSTNs gateway exchanges. Apart from revenue
accounting, IARA can also be used to collect statistical data.
In a "Combined Switching Center" (CSC), both IARSTAT an IARAMA can be used for
all types of subscribers. A CSC is a network node which can implement the function of
a PLMN and that of a PSTN network node.
Generally speaking, distinctions are made between three types of subscribers:
Mobile subscribers: A mobile subscriber can move freely within the GSM system
and is in contact with the network via a radio link.
Wireless local-loop subscribers (WLL subscribers): Mobile subscribers with
restricted location authorization within the PLMN and a call number which follows
the numbering scheme of the PSTN.
A wire-line subscriber is a subscribers who has the same quality like a PSTN
subscriber.
Generally speaking, wireless local-loop subscribers and wire-line subscribers are only
administered in a "Combined Switching Center" (CSC). From the viewpoint of CSC,
WLL subscribers are mobile subscribers who only differ from "normal" mobile
subscribers due to a small number of typical features (e. g. numbering scheme).
Accordingly, the only distinctions made in the following are between wire-line and mobile
subscribers.
The following operations characterize the IARA procedure:
registration of call data per call for defined traffic relationships
storage of the call data separately for each traffic relationship
output of registered call data for post processing (revenue accounting and statistical
analysis)
IARA can easily be adapted to suit the needs and requirements of the telecommunication networks. Various registration criteria can be defined in the IARA database jointly
for all IARA registrations, and registration jobs based on these criteria enable IARA to
be employed in line with the network-operator requirements.
The IARA procedure comprises software components in the group processors (GP) and
the coordination processor (CP). In IARA procedures the group processors register the
desired call data and transfer these data to the CP. The CP stores the registered call
data and makes it available for post-processing.
An example of an IARSTAT registration can be found in Fig. 1.8

A30808-X3003-X458-2-7619

IN 31

OMN:SSS-TA

Operation Charging

GP

CP
Call
processing

Digit translation, path selection

Evaluation of:
Originating trunk group
Terminating trunk group
Destination route

IARSTAT matrix point involved?

yes

LTG
Gathering
call processingIARSTAT
measurement
data

Buffering of IARSTAT call data per traffic

relationship in hour value counters in the
memory unit

In the 45th minute of each hour summation

of the IARSTAT call data of the matrix point
in registration counters on disk,
file = IC.COUNTERFILE

Provision of IARSTAT call data totals in

postprocessing files on disk
file = IC.Aryymmnn

Output of the postprocessing files to an

OMT or tape or transfer to an operation and
maintenance center

Postprocessing of the call data totals for

revenue accounting and statistical analysis
on a commercial computer

Fig. 1.8

IN 32

Sequence of IARSTAT Registration

A30808-X3003-X458-2-7619

Operation Charging

1.2.1

OMN:SSS-TA

IARA Registration
IARA is based on the registration of call data for defined traffic relationships. If required,
administration can determine the traffic relationships for which call data are to be registered. To do this, the various originating and destination objects are assigned IARA
names which are subsequently linked with each other.
Note: it is not possible to use IARA for IN calls, interception and calls between wire-line
subscribers (LAC to LAC)
There are two ways in which call data can be registered, i.e. registration by means of
IARSTAT (Inter Administration Accounting with Statistics) or by means of IARAMA (Inter
Administration Accounting with AMA).
IARSTAT
Summation of the call data separately for each traffic relationship using registration
counters.
The following call data are aggregated or registered for each tariff (day, evening, night):
Call time in seconds
Number of seizures
Number of successful calls
Seizure time on A side in seconds
Seizure time on B side in seconds
IARA origin and destination names
Call type
IARAMA
Collection of the call data within the measuring types separately for each call and generation of an AMA data record.
The following call data (which refer to the particular call) are registered:
Call time in seconds
Incoming/outgoing trunk group
The first digits of the calling (A) subscribers number
Called (B) subscribers number
Transmission rate
Date and time at the end of the call
Information about the number of successful calls and the transmission rates used can
only be determined by post-processing the AMA data records.
Using Call Data Registration
For wire-line subscribers (analog, digital, (dedicated network) PABX or PSTN
subscribers) of a CSC, both methods of registering call data are available without any
restrictions (one can select the kind of charging (PLMN or PSTN) for all fix subscribers
in the installation mode by means of the command MOD MSERVREL.; for transit calls
which are to be treated like PSTN calls the following is to be created:
ENTR TGDAT: GCOS=PSTNTGRP).
Only IARSTAT can be used for all those calls in which mobile subscribers are
involved. At the same time, it is to be ensured that the IARA configuration of a CSC is
created with the priority in favor of mobile subscribers. All the IARA features which only
apply for the wire-line subscribers are only to be used if they do not affect the registration
of the IARA data of the mobile subscribers.

A30808-X3003-X458-2-7619

IN 33

OMN:SSS-TA

Operation Charging

1.2.2

Terms
IARA Origin and Destination Names
The traffic relationships for which call data are to be registered are characterized by a
defined volume of originating traffic which leads to a specific volume of outgoing traffic.
In order to describe a traffic relationship (in the form of a matrix point), the corresponding
sources of the originating traffic and the selected destinations are combined into groups
in each case by assigning an IARA origin or destination name.
Origin and destination names are entered with ENTR IARNAME.
Definition of an IARA origin name:
One (or more) incoming trunk groups (TGNO)
Local area codes (LAC,DIR=ORIG)(for wire-line subscribers only)
Definition of an IARA destination name:
One (or more) route(s), through
the combination of destination and trunk group (DEST, TGNO)
the combination of destination and route(DEST, RTNO)
Local area codes (LAC, DIR=DEST) (for wire-line subscribers only)
The destination/origin combination LAC-LAC is not registered with IARA.
As a rule, IARA names can be freely selected. The number of names which can be
created, however, is restricted and depends on the measurement type. Refer to
Tab. 1.4.
Measurement Type

IARA Origin Name

Measurement type 1

40

800

Outgoing traffic

Measurement type 2

250

30

Incoming traffic

Measurement type 3

225

225

Transit traffic

Measurement type 4

50

100

Random combination (for statistics)

Tab. 1.4

IARA
Destination
Name

Assignment Required for

Conversion into ASN.1

Maximum Number of IARA Names

For the four different measurement types it is possible to assign a separate IARA name
for each traffic relationship.
Traffic Relationships (Matrix Points)
A traffic relationship is defined by an IARA origin name and an IARA destination name.
In this regard, origins and destinations are assigned IARA names which are linked with
each other. This link is known as a matrix point.
It is created with CR IARMPT.
Data which have been registered for a traffic relationship can be output in both variants
IARSTAT or IARAMA.

IN 34

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Origin name

IARSTAT

IARAMA

Destination name

Fig. 1.9

Traffic Relationships as Matrix Points

Measurement Types
Measurement types are used for processing the registration of the different traffic types
(e.g. incoming traffic, outgoing traffic) separately from each (starting and stopping
counters or data records). The measurement types are assigned upon entering the
IARA names (ENTR IARNAME). IARA provides four different measurement types,
which explains the 4 units in the parameter NAME.
As a rule, the assignment of the measurement type and traffic type can be freely
selected. However, if the IARA files are to be converted into ASN.1 format (Abstract
Syntax Notation 1), e.g. in order to be transferred to a post-processing center by means
of FTAM, the assignment of measurement and traffic types given in Tab. 1.4 is to be
used.
With IARSTAT a separate post-processing file (IR.Aryymmnn) for each measurement
type is created.
If the measurement types are not assigned to separate traffic types, the entire traffic will
be registered with one measurement type and can then only be billed collectively.

Example: Creating traffic relationships

A30808-X3003-X458-2-7619

IN 35

OMN:SSS-TA

Operation Charging

Origin name:INC2

Origin name 2
Destination name:
Dest 2

Measurement
type 4
Destination
Origin name:INC1
Measurement
type 3

Destination name:
Dest 1

Measurement
type 2

Matrix point 1

Measurement
type 1

Origin trunk groups

Fig. 1.10

IN 36

Definition of Matrix Points, Destination and Origin Names

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

The following entries are required for the configuration shown in Fig. 1.10 :
1. Assignment of IARA origin names:
ENTR IARNAME: TGNO=A
NAME=0-0-0-INC2;
ENTR IARNAME: TGNO=B,
NAME=INC1-0-0-INC2;
ENTR IARNAME: TGNO=C,
NAME=INC1-0-0-INC2;
2. Assignment of IARA destination names:
ENTR IARNAME: DEST=X, RTNO=1
NAME=DEST1-0-0-DEST2;
ENTR IARNAME: DEST=Y, RTNO=1
NAME=DEST1-0-0-DEST2;
ENTR IARNAME: DEST=Z, RTNO=1,
NAME=DEST1-0-0-0;
3. Creating the traffic relationships (matrix points) for IARSTAT:
CR IARMPT: MTYPE=IARSTAT1,
DNAME=DEST1, ONAME=INC1, CNTR1=AUTO;
CR IARMPT: MTYPE=IARSTAT4,
DNAME=DEST2, ONAME=INC2, CNTR1=AUTO;
4. Creating the traffic relationships (matrix points) for IARAMA
CR IARMPT: MTYPE=IARSTAT1,
DNAME=DEST1, ONAME=INC1, TICKET=YES;
CR IARMPT: MTYPE=IARSTAT4,
DNAME=DEST2, ONAME=INC2, TICKET=YES;
In this way, matrix point 1 allows measurement data to be collected for the traffic which
arrives from trunk groups B and C and which is routed to destinations X, Y and Z, while
matrix point 2 allows measurement data to be collected for the traffic which arrives from
A, B and C and which is routed to X and Y.
Call Types
As a rule, IARA allows traffic relationships to be registered separately (using different
counters) according to the different call types such as automatic calls or operatorassisted calls.
A CSC only registers the automatic calls (AUTO) of the 6 call types (ENTR IARCON,
parameter CONTYP) which can be evaluated in principle.
Transmission Rate (only valid for wire-line subscribers in a CSC)
The following 4 transmission rates (ENTR IARCON, parameter TMR) are evaluated:
3.1 kHz audio (A3KHZ1)
Speech (SPEECH)
64 kbit/s (KBIT64)
64 kbit/s fallback (KBIT64FB).
For this purpose, IARA uses the signals of the signaling system (in the case of ISUP and
TUP+) which is set up on the incoming trunks. All the other signaling systems (e.g. MFC)
use the standard value of 3.1 kHz audio.

A30808-X3003-X458-2-7619

IN 37

OMN:SSS-TA

Operation Charging

This enables the call data for a traffic relationship to be registered separately according
to the transmission rate required for the call.
Call Groups (only valid for wire-line subscribers in a CSC)
An additional matrix (see Fig. 1.11) is formed by combining call types (in the GSM
system and in a CSC only the "automatically switched calls" call type exists) and transmission rates. IARA checks each call to determine whether or not an intersection exists
in this matrix. For such a combination consisting of a call type and a transmission rate it
is possible to register the traffic separately (e.g. all the automatic calls with 3.1 kHz
audio).
Combinations which consist of a call type and a transmission rate can be assigned to a
call group. It is possible to create a maximum of 6 such call groups.
1

...

6
Call types

Call group

Transmission rates

Fig. 1.11

Matrix for Call Groups

Combinations of call types and transmission rates which have not been assigned to a
call group are not registered.
The system provides a specific default assignment to call groups, whereby the name of
each group is identical with the only call type contained in this particular group. No
distinctions are made between transmission rates. As soon as a new call group is
defined for an APS, i.e. as soon as MML command CR IARGRP is entered for the first
time, all the default call groups are deleted at the same time. Therefore, at this point in
time, only this one particular call group which has been newly created is known within
the system. Any further call groups which are required have to be set up using the MML
command. This also applies for those groups which are identical with the default groups.
Starting and Stopping the Registration Procedure
Once origin and destination names have been entered and linked to matrix points, IARA
registration can be started:
REC IARSTAT: MTYPE=IARSTAT1 [,BEG= ... , TER= ... ];
Registration for a specific measurement type is started with precisely such a registration
task. This can be realized separately for each of the 4 measurement types. By specifying
a time interval, it is possible to control the duration of the registration procedure.

IN 38

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Time-controlled registration and continuous registration tasks can be interrupted with

CAN JOB. It is necessary, however, to wait for the next full hour to elapse if new matrix
points have been created in the meantime.
At the end of each full hour, the data are automatically saved on disk, thus protecting
them from being lost.

1.2.3
1.2.3.1

IARSTAT
Registration Counters and Tariff Zones
Each matrix point may be allocated up to 7 registration counters for the different call
groups (see Fig. 1.12). For D900/D1800 and within a CSC only one counter is used. A
registration counter consists of 3 counters that are used for the time-controlled registration of IARSTAT call data.
For each matrix point one of up to 99 tariff zones can be allocated. A tariff zone defines
the time schedule by which the three counters mentioned above are activated, where
the day tariff corresponds to the day counter
the evening tariff corresponds to the evening counter
the night tariff corresponds to the night counter
The switchover between the three tariffs is definable by MML command but can take
place only on each full hour. If no tariff zone has been allocated to the matrix point, the
day counter is used 24 hours a day.
The number of available registration counters in the system is project-specific.
Tariff switchovers can be created as a function of the weekday category (workday,
weekend, public holiday, etc.) and the hour of the day.

A30808-X3003-X458-2-7619

IN 39

OMN:SSS-TA

Operation Charging

Origin name

Destination name

Matrix point

Registration counter 7
Registration counter 6
Registration counter 5
Registration counter 4
Registration counter 3

Nght
Nght

Nght

Nght
Ve time

Number of calls
Ve time

Number of calls
Ve time
Holding time on

the A side
Number of calls
Ve time
Beleging
Holding
time
A time on
Number of calls
Registration counter 1
the
B side
Nght Ver time
Belegng time
Holding
time
on
A side
number of
Number of calls
the B side
Day
Evening
Night Ve time
Belegng
seizures
Holding
on
time
A time number
of
Number
of
calls
the B side
Call time
Call time
Call time
Holding time on
seizures
Holding
time
on
the A side
number of
Number of calls Number of calls Number of calls
the B side
Beleg time on
seizures
Holding
time
on
the AA side
Number of
the B side
Holding time on Holding time on Holding time on
seizures
Holding
time
on
the A side
the A side
the A side
Znumber of
the B side
seizures
Holding time on Holding time on Holding time on
Zahber of
the B side
the B side
the B side
urures
Number of
Number of
Number of
seizures
seizures
seizures

Registration counter 2

Fig. 1.12

IN 40

Nght

Detailed Structure for a Matrix Point

A30808-X3003-X458-2-7619

Operation Charging

1.2.3.2

OMN:SSS-TA

Functional Sequence of IARSTAT

When a call is set up, the CP determines the trunk group, destination and route and
checks whether a matrix point is involved for the call (Fig. 1.8). Provided the matrix point
is marked as active, the call is traced in the LTG in order to determine the following
IARSTAT call data:
conversation time in seconds
number of successful calls
A side holding time in seconds
B side holding time in seconds
number of trunk seizures
The GP transmits the call data to the CP upon call termination (or as an intermediate
message after every 30 minutes for calls of long duration - the time can be changed with
timer 114 in MOD TIOUT). The CP stores the data in a transient hour value counter. The
distribution according to matrix points, call groups and tariff areas already occurs (day,
evening, night) at this point. An hour value counter consists of three parts (one for each
tariff area). The call data are added to the part corresponding to the valid tariff area. If a
call extends beyond a tariff switchover, the call times and holding times are added to the
counter part for the preceding hour and the current hour in the correct proportions; the
number of calls and seizures is added to the counter part that is valid after the
switchover.
At each full hour, the CP transfers the call data totals registered by the hour value
counter during the preceding hour to the relevant registration counters. These are
located on the disk in file IC.COUNTERFILE.
The registration counter itself is also a summation counter. The call data which are
transferred every hour are added to the stored data. The registration counter contains
tariff zones for day, evening and night registration, after which the hour value counter is
reset.
Generally speaking, the registration counters are designed such that they do not overflow in the course of a month. By way of example, the registration counter for the seizure
and call time is designed such that it can register the times for the uninterrupted use of
800 trunks up to and beyond 31 days without overflowing. The registration counter for
the number of calls and trunk seizures is designed in such a way that, for example, uninterrupted usage of 500 trunks with an average seizure duration of 90 seconds over a
period of 31 days does not result in a counter overflow. If, however, there is reason to
expect that certain registration counters might overflow, it is possible to display their
current status using an MML command. What is more, an MML command can also be
used to create an intermediate file on hard disk before the counters overflow. This intermediate file is then available for further post-processing once the file has been copied
onto tape.
The number of available IARSTAT counters is governed by the particular project.

1.2.3.3

IARSTAT Post-Processing
In addition to registration counter file "IC.COUNTERFILE" which is common to all
IARSTAT registration tasks, the CP also generates a separate post-processing file
(IR.Aryymmnn) (see Fig. 1.13) for each measurement type when a registration task is
entered.

A30808-X3003-X458-2-7619

IN 41

OMN:SSS-TA

Operation Charging

The IARSTAT data are transferred from the IC.COUNTERFILE file into individual postprocessing files at the following times:
Upon completion of a time-controlled registration task
After initiating an intermediate backup using MML command
COPY IARACCT; the registration task continues to run
Once a month at a fixed backup time for continuous registration tasks. The backup
time can be defined using MML command ENTR IARSAVDA. If no specific time is
defined, the data are automatically saved on the 1st day of each month at 0:00 hours
After stopping the registration task using MML command CAN JOB
While the hourly backup of the data is in progress, commands COPY IARACCT and
CAN JOB must not be entered, since the data which are to be saved are not static during
the backup procedure.
The post-processing file is located on both disks. The file name is structured as follows:
IR.A r yy mm nn, where:
r =
yy =
mm=
nn =

IARSTAT measurement type

Year
Month
Consecutive number within a measurement type.

The date specified in the name of the post-processing file always refers to the start of
the registration task. In order to distinguish between IARSTAT post-processing files of
the same registration type which have the same date in the file name, a consecutive
number is used which is incremented each time.
If a post-processing intermediate file has been generated due to an expected overflow,
the generation date of this intermediate file is assigned automatically to the next file.
Once the IARA data have been transferred from the registration counter to the postprocessing file, the IARA counters in the IC.COUNTERFILE are reset.
The post-processing files for the individual measurement tasks can be output onto tape
at any time for further post-processing or transferred to a post-processing center. Since
only closed IARSTAT files can be transferred, DISP IARFILE can be used to interrogate
the status of the entries. When files are copied onto tape, at least two copies are to be
made for safety reasons. The copied file is then to be deleted from the hard disk, but
only after first checking that the IARA data have been successfully processed.
When the post-processing files are transferred into the customer-specific postprocessing file (TRANS FILE:.., COPMOD=POST;), a transformation into a customerspecific format is performed by the copying service process defined in SET
FGRPATT:....,PRNAME=...; for the IR.Aryymmnn files (see also OMN:SSS-SY).
Two copying service processes are available.
The IRCPP process transforms the PAM file (IR. ...) into a sequential (SAM) file (ASCII
format, e.g. for copies onto tape).
The files are converted into ASN.1 format (Abstract Syntax Notation 1), e.g. for transfer
by means of FTAM, using the IRENC process.
While conversion is taking place, the following assignment is made:

IN 42

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

IARSTAT Measurement Type

measurement type

IARSTAT 1

Outgoing traffic

IARSTAT 2

Incoming traffic

IARSTAT 3

Transit traffic

IARSTAT 4

Statistics

Tab. 1.5

Measurement Type Assignments

In other words, if IARSTAT files are to be converted into ASN.1 format (in order to be
transmitted by means of FTAM or copied onto tape), the measurement types are to be
created in line with the above-mentioned assignment.
Generally speaking, the data are post-processed by means of a commercial dataprocessing system. For manual evaluation, it is also possible to output the data from the
IC.COUNTERFILE file with DISP IARSTAT on an operation and maintenance terminal
(OMT). The required registration counters are specified via the registration type and, if
necessary, also via the IARA origin names and the IARA destination/path names. It is
also possible to output the contents of the post-processing files by specifying the file
name on the terminal.

Hourly transfer

Hourly
switchover

Transmission
- Using COPY IARACCT
- At the end of registration
- At the specified backup time

Transmission via
TRANS FILE
with processes IRENC or
IRCPP

IR.A4yymmnn "service process"

IR.A3yymmnn
Post-processing file pro

IARSTAT
Hour value
counter
(duplicated)

IC.COUNTERFILE
IARSTAT counter
for all measurement
types

Measurement type
IR.A2yymmnn
Post-processing file pro
Measurement type
IR.A1yymmnn

Post-processing file
per measurement type
PAM

Post-processing file pro

Measurement type

Customer-specific
post-processing file
per measurement
type
SAM

Call data

Fig. 1.13

IARSTAT Files

A30808-X3003-X458-2-7619

IN 43

OMN:SSS-TA

1.2.3.4

Operation Charging

Example of an IARSTAT Application

The IARSTAT accounting volume to the destinations NAT, INAT and INTCON in the
gateway MSC of the PLMN is to be evaluated using IARSTAT counters. The originating
traffic is caused by the incoming trunk groups IHAM, IMUC and IFRA (see Fig. 1.11).
Task 1
The administration has to know the IARA accounting volume to each destination separately. This is determined regardless of which of the three incoming trunk groups the
originating traffic came in on.
Task 2
The IARSTAT accounting volume to the destinations NAT and INAT is to be registered
time-dependent according to the time schedule defined by the tariff zone number 1.
Tariff zone 1 concludes a day tariff starting at 8.00 h and the tariff switchover at 18.00 h
to the night tariff. The switchover takes place only on workdays.
The IARSTAT accounting volume to the destination INTCON is to be registered without
any tariff switchover.
Task 3
Continuous IARA registration is to be started as soon as possible.
Task 4
The corresponding IARSTAT file is to be copied onto tape for post-processing.
Solution
The execution of these tasks is found on the following pages. The required MML
commands are contained in the figures.

IN 44

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

PLMN

PSTN
RTNO = 1

GMSC

RTNO = 2

DEST = NAT

Gateway
exchange(s)

to NAT

RTNO = 1
RTNO = 2

DEST = INAT

to INAT

RTNO = 1
RTNO = 2

DEST = INTCON

to INTCON

IHAM
IMUC
IFRA

Fig. 1.14

Example: Network Configuration on which the Task is Based

A30808-X3003-X458-2-7619

IN 45

OMN:SSS-TA

Operation Charging

RTNO = 1

GMSC
RTNO = 2

DEST = NAT

RTNO = 1
RTNO = 2

DEST = INAT

RTNO = 1
RTNO = 2

DEST = INTCON

ORIG

Combination of originating trunk groups

ENTR IARNAME: TGNO= IHAM, NAME= ORIG000;
ENTR IARNAME: TGNO= IMUC, NAME= ORIG000;
ENTR IARNAME: TGNO= IFRA, NAME= ORIG000;

IHAM
IMUC
IFRA

RTNO = 1

GMSC
AR1

RTNO = 2

DEST = NAT

RTNO = 1
AR2

RTNO = 2

DEST = INAT

RTNO = 1
AR3

IHAM
IMUC
IFRA

Fig. 1.15

IN 46

RTNO = 2

DEST = INTCON

Combination of destinations/routes
ENTR IARNAME: DEST=NAT,
ENTR IARNAME: DEST=NAT,
ENTR IARNAME: DEST=INAT,
ENTR IARNAME: DEST=INAT,
ENTR IARNAME: DEST=INTCON,
ENTR IARNAME: DEST=INTCON,

RTNO=1,
RTNO=2,
RTNO=1,
RTNO=2,
RTNO=1,
RTNO=2,

NAME=AR1000;
NAME=AR1000;
NAME=AR2000;
NAME=AR2000;
NAME=AR3000;
NAME=AR3000;

Solution for Task 1 (Part 1)

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Reg. Counter
D

GMSC
ORIG

RTNO = 1

AR1
RTNO = 2

DEST = NAT

RTNO = 1
Reg. Counter

AR2
RTNO = 2

DEST = INAT

N
RTNO = 1
AR3
RTNO = 2

DEST = INTCON

Reg. Counter
D

IHAM
IMUC
IFRA

Creation of 3 matrix points

CR IARMPT: MTYPE=IARSTAT1, DNAME=AR1, ONAME=ORIG, CNTR1=ALL;
CR IARMPT: MTYPE=IARSTAT1, DNAME=AR2, ONAME=ORIG, CNTR1=ALL;
CR IARMPT: MTYPE=IARSTAT1, DNAME=AR3, ONAME=ORIG, CNTR1=ALL;
Fig. 1.16

Solution for Task 1 (Part 2)

A30808-X3003-X458-2-7619

IN 47

OMN:SSS-TA

Operation Charging

Reg. Counter
D

GMSC
ORIG

RTNO = 1

AR1

Switchover

RTNO = 2

DEST = NAT

RTNO = 1
Reg. Counter

AR2
RTNO = 2

DEST = INAT

N
RTNO = 1
AR3

Switchover

RTNO = 2

DEST = INTCON

Reg. Counter
D

IHAM
IMUC
IFRA

Creation of a tariff zone and allocation to a matrix point

CR IARTMPD: TZONE=1, TIME=0600, TARIFF=DAY,
WDCAT=WO;
CR IARTMPD: TZONE=1, TIME=1800, TARIFF=NIGHT, WDCAT=WO;
ENTR IARZONE: MTYPE=IARSTAT1, TZONE=1,
ENTR IARZONE: MTYPE=IARSTAT1, TZONE=1,

Fig. 1.17

IN 48

DNAME=AR1, ONAME=ORIG;
DNAME=AR2, ONAME=ORIG;

Solution for Task 2

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Hour value counter

Update: at the end of call or

e.g. 30 min. intermediate

Reg. Counter

GMSC
ORIG

Solution for:
Task 3: REC IARSTAT:
MTYPE=IARSTAT1;
Task 4: COPY IARACCT:
MTYPE=IARSTAT1;
Proc. TP550 in
OMN:SSSTA

RTNO = 1

AR1
RTNO = 2

DEST = NAT

RTNO = 1
Reg. Counter

AR2
RTNO = 2

DEST = INAT

N
RTNO = 1
AR3
RTNO = 2

DEST = INTCON

Reg. Counter
D

N
IHAM
IMUC

Data transfer at xx.00 h

from the preceding hour
value counter part

IFRA

MDD0
MDD1

Entries into the post

processing file:
Automatically at the end
of registration
Once per month at a fixed
time (continuous
registration)
Manually between
xx.05 h and xx.20 h
(MML: COPY IARACCT)

IC.COUNTERFILE
OMT
Possible at
any time

IARSTAT data
display by MML

Not possible during

hourly saving
Fig. 1.18

IR.Aryymmnn
OMC
Data transfer
initiated by MML

Solution for Tasks 3 and 4

A30808-X3003-X458-2-7619

IN 49

OMN:SSS-TA

Operation Charging

1.2.4

IARAMA
IARAMA can only be used for wire-line subscriber in a CSC with PSTN charging.

1.2.4.1

MML commands for IARAMA

The sequence of examples selected corresponds to the required input sequence.
Activate system feature:
ACT IAFEAT: TYPE= IARA;
The standard size of the IARA file is 30 MB.
Record format and number of copies:
SET FGRPATT: FGRP= IA.ICIAR, PRNAME= AGFRx, COPATT= 2048-x,
SAFCOP= 3;
Collect additional IARAMA data:
ENTR CDTDAT: RECIRDAT = RECIRDAT;
The following data are thus collected:
type of recording
call group
origin and destination names
Enter origin and destination names:
ENTR IARNAME: NAME= origin name, TGNO= ... (or LAC or LACOR);
ENTR IARNAME: NAME= destination name, DEST= ... , RTNO= ... (or DEST, TGNO
or LAC);
Enter matrix points with TICKET:
CR IARMPT: MTYPE = IARSTAT2, ONAME = ... , DNAME = ... , TICKET = YES;
Activate recording:
REC IARSTAT: MTYPE = IARSTAT2 [,BEG = ... , TER = ... ];
Recording commences on the next full hour.
Write buffer contents to disk file:
TRANS BUFFER: TYPE = IARA;
Display records:
It is not possible to display IARAMA records with DISP AMA.
Copy AMA file to tape (transparently):
TRANS FILE: FILE = IA.IAR/IA.ICIAR, VSNR = ... ;
Copying to a host or with a change of format see TP-545.

IN 50

A30808-X3003-X458-2-7619

Operation Charging

1.2.4.2

OMN:SSS-TA

Example of an IARAMA Application

By way of example, a CSC (Combined Switching Center) with
A trunk to England
A trunk to France
A trunk to the PSTN
A number of wire-line subscribers of the CSC with the local area code (LAC) 091
Here, traffic relationships 1 to 3 are considered.
Task
The traffic volume of the wire-line subscribers of the CSC (see Fig. 1.19) is to be registered with tickets. Registration is to be performed separately for national and international traffic, while the outgoing traffic is to be assigned to measurement type 1 and the
incoming traffic to measurement type 2.

Combined Switching
Center

England

LAC=091
TGNO=inceng

DEST= englnd,RTNO=1
2
3
PSTN

France
TGNO=incfra

TGNO=inpstn

DEST=france,TGNO=1

Fig. 1.19

DEST=pstn,TGNO=1

Example of a Gateway Exchange

Installation of the database in line with the example
1. Creating the IARA origin names
ENTR IARNAME: TGNO=inceng, NAME=#-inat-#-#;
(Traffic from England)
ENTR IARNAME: TGNO=incfra, NAME=#-inat-#-#;
(Traffic from France)
ENTR IARNAME: TGNO=inpstn, NAME=#-nat-#-#;
(Traffic from the PSTN)
ENTR IARNAME: LAC=091, DIR=ORIG; NAME=csctln-#-#-#;
(Traffic from the wire-line subscribers)
An IARA name consists of 4 parts. Each part addresses one of the 4 possible
parallel registration types. England and France receive the same name since they
constitute one unit for accounting purposes. The traffic which goes out from
England, France and the PSTN generates the incoming traffic and is thus assigned

A30808-X3003-X458-2-7619

IN 51

OMN:SSS-TA

Operation Charging

to measurement type 2, while the traffic from the wire-line subscribers of the CSC is
registered with measurement type 1.
2. Creating the IARA Destination Names
ENTR IARNAME: DEST=englnd, RTNO=1, NAME=inat-#-#-#;
(Traffic to England)
ENTR IARNAME: DEST=france, RTNO=1, NAME=inat-#-#-#;
(Traffic to France)
ENTR IARNAME: DEST=pstn, RTNO=1, NAME=nat-#-#-#;
(Traffic to the PSTN)
ENTR IARNAME: LAC=091, DIR=DEST, NAME=#-csctln-#-#;
(Traffic to the wire-line subscribers)
Here, too, England and France receive the same name since they constitute one
unit for accounting purposes. The same names have been used for origins and
destinations. Although this is possible, it is not necessary.
The destinations for the outgoing traffic (England, France and PSTN) are registered
with measurement type 1, while the destination for the incoming traffic is registered
with measurement type 2.
3. Creating the Matrix Points
CR IARMPT: MTYPE=IARSTAT, ONAME=csctln, DNAME=nat, TICKET=YES;
This command installs the relationship for traffic arriving from a wire-line subscriber
of the CSC and traffic going to a subscriber of the PSTN. The traffic is registered with
registration type 1 and stored in data records. The other matrix points are created in
the same way, whereby the outgoing traffic is registered with measurement type 2
(IARSTAT 2).
CR IARMPT: MTYPE=IARSTAT, ONAME=csctln, DNAME=inat, TICKET=YES;
CR IARMPT: MTYPE=IARSTAT, ONAME=nat, DNAME=csctln, TICKET=YES;
CR IARMPT: MTYPE=IARSTAT, ONAME=inat, DNAME=csctln, TICKET=YES;

Ticket

IARA dest. names

Destin.

csctln

LAC 091

nat

pstn

Ticket

Ticket

inat

englnd

Ticket

france
IARA origin names

Origins

Fig. 1.20

IN 52

csctln
LAC 091

inat

nat
inpstn

inceng

incfra

Creating the Matrix Points for Registration Type 2

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Registration is tariff-independent. The date and time are stored in the ticket. Conversion
into the valid tariff has to be performed by the post-processing center.

1.2.4.3

Saving the Registered Data

Transmission
- Via TRANS BUFFER:TYPE=IARA
- Automatically for full buffer storage

Transmission by means of
-TRANS FILE
with process AGFR6
-REL CYCFILE:FILE=IA.ICIAR

"service process"

IARAMA
Ticket data
buffer

IA.ICIAR
Cyclic IARAMA
file for all
measurement types

Customer-specific
post-processing file
SAM

Call data

Fig. 1.21

1.2.5

IARAMA Files

Regeneration of the IARA database

The complete IARA database can be regenerated. The following command must be
used in order to create the command file for regeneration of the current database.
EXEC REGEN: FUNC = IR;
This creates the command file RG.IR.xxxxx. An empty database (e.g. following an APS
changeover) can then be filled by means of the following command.
EXEC CMDFILE: FILE = RG.IR.xxxxx ;
The database is then regenerated in the state which it was in before the command
EXEC REGEN was executed.
If further recordings were started after the command EXEC REGEN was executed, they
cannot be regenerated. In this case, after EXEC CMDFILE has been performed, a
check must be made with DISP IARJOB to establish which recordings are still in
progress. Any recordings that have disappeared can be restarted by means of:
REC IARSTAT: MTYPE = ... ;
They are then started automatically on the next full hour. To avoid possible loss, the
command EXEC REGEN.

1.2.6

Procedure after Recovery

If fallback to an earlier APS has taken place (recovery with ISTART2G), any inconsistencies between the old and new database must be resolved by incorporating the
logging file. After this, the command

A30808-X3003-X458-2-7619

IN 53

OMN:SSS-TA

Operation Charging

SAVE MET: TYPE = IARA, FUNC = FALLBACK;

must be entered to unblock the counters and re-assign the traffic relations (matrix
points) to the meters. For those traffic relations to which no meters could be assigned
the operator receives a screen message showing the last meter reading.

1.3

Trunk Meters and Statistics Meters

In addition to being registered in AMA files or MCR and IARSTAT procedures, charge
data can also be recorded in a charge saving file for
trunk groups created with GCOS=TRMET
calls via certain zone points, routes or trunk groups (outgoing calls) to which a statistics meter has been allocated
The prerequisite for a registration is that the relevant function has been activated at the
MSC.

1.3.1

Trunk Meters for Trunk Groups

For trunk groups created with GCOS =TRMET, the call charge pulses transmitted via
this trunk group by the remote node are collected in a file. The information contained in
this file can be used, for example, for checking when the zoning for a call is not
performed at the home MSC, i.e. ZOCHA= ZONINHI was entered for the relevant zone
point.
Charge Saving
The backup files are generated in accordance with the types of counters set and the
meter counts are saved in the memory and on the disk. This accompanies the following
functions:
the first recovery following commissioning, or
the next input of the command SAVE MET, or
after the next time-controlled saving time. These times can be set by the operator
with the command ENTR METSAV, or they can be set automatically by the system
at 00:30 hours
The charge data that have been added on by call processing can be immediately or periodically saved on the disk. After memory failures or ODAGEN runs, the data in the operating range are reprocessed using the backup file. If the operating range is extended
with ODAGEN, the charge data are automatically saved so that practically no charge
data are lost.
An automatic save is performed prior to the change to a new APS. If, prior to saving,
errors in the charge records are detected in the memory, they are restored using the
backup file. Such errors can be detected during:
time-controlled charge checks or
routine checks
If the charges on the backup file have also been destroyed or if no backup file is available, the data can be restored from a repair file (a copy of an old backup file). Consequently, it is advisable to save the backup files on tape at regular intervals.
For every type of charge counter there is a duplicated backup file on disk that is
protected against writing and erasure. At specified saving times, the charge data are
written to the backup file.

IN 54

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Charge Data
Charge data are saved at specified times in a backup file. After memory failures, the
data can be restored from the backup file or, if this file has also been destroyed, the data
can be restored from a repair file (a copy of an old backup file). Consequently, it is advisable to save the backup files on tape at regular intervals.
The charge counters are initialized during an APS change. In order to save the charges,
a regeneration file must be created in the old APS (MML command EDIT MET). This
allows the charge data to be regenerated in the new APS (MML command REG MET)

1.3.2

Statistics Meters
Statistics meters are summation counters. They register the number of calls, accumulated meter pulses and the duration of the following call types:
calls zoned via a specified zone point
calls routed via a specified route
calls entering the exchange via a specified trunk group
For this purpose, a statistics index is allocated to each of these objects (zone point,
route, incoming or bothway trunk group). As a result of this allocation,
the number of calls, the charges and the call duration are registered in statistics meter
sets for connections running via this type of object.
Although statistics meters can be specified for the three above-mentioned call types,
only one type should be utilized for statistics counting. If a statistics index is found in
several places during a call setup, only the last one found will be assessed. (The objects
are evaluated here in the following order: incoming trunk group, route, zone point.)
This mutilates the statistics counting.

1.3.3

Statistics Meter Switchover Time

A registration is performed after every call conducted via a zone point and for which a
statistics meter has been created. Call and charge data are thus registered on statistics
meters.
The time group table is a semipermanent table with the fixed size of 256 elements.
One of the six time groups is valid at any time, i.e. the traffic is added to this time group.
Switchovers between the six time groups, dependent on the time and weekday category, can be defined by MML command.
Each statistics meter set consists of a counter for the number of calls, a counter for the
charges, a counter for the call duration and a checksum byte. The meter contents can
be displayed on the monitor by entering the command DISP STATMET (see Fig. 1.22)

A30808-X3003-X458-2-7619

IN 55

OMN:SSS-TA

Operation Charging

Statistics meter n
Counter for the number of calls
Counter for the charge units
Counter for the call duration
Checksum byte

Fig. 1.22

IN 56

Structure of a statistics meter set

A30808-X3003-X458-2-7619

Operation Charging

1.4

OMN:SSS-TA

Charging of Wired Subscribers of a Combined

Switching Center (CSC)
Wired and PABX subscribers can be charged in a CSC both: PLMN charging or PSTN
charging
Call charge registration is carried out in the MSC to which the digital subscriber and the
PABX are connected. One can select the kind of charging (PLMN or PSTN) for all fix
subscribers in the installation mode by means of the command MOD MSERVREL.
Also for transit call one can select the charging mode. For PSTN charging one has to
enter in ENTR TGDAT: GCOS=PSTNTGRP.
Fig. 1.23 contains a general overview of the different types of charge registration.
The registration of interadministrativ traffic is described in a separate chapter.

A30808-X3003-X458-2-7619

IN 57

OMN:SSS-TA

Operation Charging

Charge registration

Subscriber's call charge

(calling party)

Subscriber's call charge

(service subscriber)

IN

TFS

Individual data
recording

Registration of traffic between

administrations

IARA

Registration of statistics

Trunk
metering

Summation
metering

(METTFS)

Individual data
recording
(IARAMA)

Call charges

Facility usage charges

Summation
metering
(IARMET)

Summation
metering

Summation
metering

(METTR)

(METSTAT)

Charges for facility input by the

subscriber

Charges for facility input by the

operator

Individual data
recording

Individual data
recording

Summation
metering

with charges

(AMA/DEB)

(METSUB)

(AMA)

Fig. 1.23

without charges

(FIR)

Charge registration for wired subscribers

1.4.1
1.4.1.1

Subscriber Tariffs
Tariff Administration Tasks
This section deals with the tariffs for subscriber charge registration. No reference is
made to interadministrative revenue accounting (IARA), which is covered by a separate
tariff administration.

IN 58

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Tariff administration tasks are the creation and administration of:

a maximum of 509 tariff zones
a maximum of 512 unsequenced tariffs
a maximum of 256 tariff sequences containing 2 basic tariffs
a maximum of 170 tariff sequences containing 3 basic tariffs
a maximum of 128 tariff sequences containing 4 basic tariffs
a maximum of 1024 tariff switchovers (inclusive mobile tariff switchovers)
There is a total of 512 tariff zones, but three of these (numbers 0, 127 and 255) are
predefined with default values and cannot be modified.
The minimum unit-interval of meter pulses is 200 ms; the maximum unit-interval is 30
minutes. All values must be multiples of 4 ms.

1.4.1.2

Tariffs
A tariff usually has two components:
a network access component
a network usage component
The network access component represents the general costs of providing a subscriber
with access to the network; these are separate from usage of the individual services.
Two different network access charges can be registered:
connection fee (non-recurring)
subscription charge (e.g. monthly)
These charges are not recorded by the tariff administration function, which only covers
the recording of network usage charges.
Network usage charges may in turn be split into the following parts:
a)

for access:

call attempt charge,

call setup charge,
b) for communication.
The call attempt charge is registered for unsuccessful call attempts where call setup was
nevertheless completed successfully, i.e. the address complete message (ACM) was
received.
This is the case if:
the calling party goes on-hook after dialing,
the called party is busy, or
the timer that supervises the ring time duration times out.
If a connection is interrupted by a fault in the exchange, no call attempt charges are
incurred.
The call setup charge is registered for successful calls, i.e. when the called party
answers.
Thus, either the call attempt charge or the call setup charge can be registered for a call,
but not both. These charges can only be applied once per call. They are registered by
means of single pulse metering (SPM) or multiple pulse metering (MPM), irrespective of
the duration of the call.
The communication charge is dependent on the duration of the call. The valid tariff may
change as the result of a tariff switchover.

A30808-X3003-X458-2-7619

IN 59

OMN:SSS-TA

Operation Charging

There are four basic tariffs from which a tariff can be formed:
Single pulse metering (SPM)
One single pulse is registered, irrespective of time, distance, duration, etc.
Multiple pulse metering (MPM)
One multiple pulse is registered. The number of pulses in a multiple pulse may
depend on time, day, distance, etc., but not on the duration of the call.
Periodic pulse metering (PPM)
Single pulses are registered at regular intervals until the call is completed. The
interval between two pulses can be dependent on time, day, distance, etc.
Periodic multiple pulse metering (PMM)
A multiple pulse is registered at regular intervals. The interval between two multiple
pulses and the number of pulses in a multiple pulse can be dependent on time, day,
distance, etc.
Tariff administration allows free selection of basic tariffs, i.e. any of the four basic tariffs,
single pulse metering, multiple pulse metering, periodic pulse metering or periodic
multiple pulse metering, can be created for each tariff in a zone. There are no restrictions
on switching between one tariff and another.
Exceptions:
Zone 0 is reserved for non chargeable calls. This zone cannot be assigned any
tariffs.
Zone 127 means no zoning in the own network node, i.e. zoning takes place in the
higher-level or lower-level network node or zoning has already taken place. For
example, meter pulses may be received over the trunk which have to be forwarded
to the originating exchange and summated there. This zone also cannot be assigned
any tariffs.
Zone 255 is the default value and means no assignment to a zone.
Examples of tariff input:
Entering an SPM tariff (1 pulse per call):
ENTR TAR: NAME= day1, PLSCOM= 1;
Entering an MPM tariff (e.g. 10 pulses per call):
ENTR TAR: NAME= day2, PLSCOM= 10;
Entering a PPM tariff (e.g. 1 pulse every 20 seconds):
ENTR TAR: NAME= day3, PLSCOM= 1-20000;
Entering a PMM tariff (e.g. 10 pulses every 60 seconds):
ENTR TAR: NAME= day4,PLSCOM = 10-60000;
Assigning the tariff day4 to a zone (the tariff day4 must already exist and the zone
must not contain any tariffs):
ENTR TAR: ZONO= 2,NAME = day4;
Notes on the input of tariffs:
Time intervals (for periodic pulse metering) and non-chargeable intervals must always
be input as a multiple of 4 ms:
One pulse every 0.65 seconds >PLSCOM= 1-652 instead of PLSCOM= 1-650.

1.4.1.3

Tariff Sequences
The use of tariff sequences enables different charges to be registered for different
stages of a call (attempt, setup, communication) and for time blocks of different lengths.
If a tariff sequence is entered, the maximum number of tariffs which can be entered is

IN 60

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

reduced by the corresponding number of basic tariffs contained in the sequence. Tariffs
for access charges have no effect on the maximum number of tariffs that can be entered.
A tariff sequence results from the concatenation of a maximum of 6 basic tariffs, i.e. a
maximum of 4 basic call components, the call attempt tariff and the call setup tariff.
Switchover takes place between these different tariffs depending on the various
sections and the duration of the call. Tariff sequences are entered with the command
ENTR TAR
A tariff sequence splits a call into different parts in terms of charges. The access tariff
PLSATT is used to record charges for (unsuccessful) call attempts. For successful calls,
the call setup tariff PLSSUP and the communication tariff PLSCOM can be used. In the
communication part, up to 4 basic tariffs can be linked to form a "communication
sequence".
For each individual tariff in a communication sequence, a tariff duration can be set by
way of an MML input (TARIFF DURATION in parameter PLSCOM). This period limits
the validity of the particular basic tariff. If a tariff duration is specified for PPM or PMM,
it must be a multiple of the unit-interval.
Structure of a tariff sequence:
Access component:
The access tariff can be applied once per call irrespective of its duration (message
rate). The only permissible basic tariffs in this case are SPM and PPM.
The following access tariffs are permitted within a tariff sequence:

call attempt tariff, applied after ACM, input by means of PLSATT and/or
call setup tariff, applied when the called party answers, input by means of
PLSSUP.
The call attempt tariff can only be input in conjunction with the call setup tariff and/or
the communication tariff.
Communication component:
The communication tariff is applied when the called party answers and is input by
means of PLSCOM. It can be dependent on the call duration (measured rate). The
sequence of communication tariffs can comprise up to 4 basic tariffs. The concatenation of SPM, MPM, PPM and PMM is permissible in any combination and in any
sequence.
End of sequence:
As soon as the defined tariff duration of a communication tariff has elapsed, either
the next basic tariff or the agreed procedure for the end of the tariff sequence comes
into effect:
Continue with the last communication tariff (non-cyclic sequence: standard procedure, but only permissible in the case of a PPM or PMM with no tariff duration
specified); input with NONCYCin parameter SEQEND, or
Release the connection (limited sequence); this is defined by entering LIMITas
the value for SEQEND, or
Repeat the sequence from the beginning (cyclic sequence); defined by entering
CYCLIC as the value for SEQEND, or
Continue with a tariff switchover; defined by entering only one PPM or PMM and
no parameter SEQEND(this can be modified on a project-specific basis)

If assigned to a tariff zone, a tariff sequence functions like a simple tariff.

A30808-X3003-X458-2-7619

IN 61

OMN:SSS-TA

Operation Charging

Examples of tariff sequence input:

Entering a single basic tariff (1 pulse) followed (after 10 seconds) by periodic pulse
metering (1 pulse every 20 seconds):
ENTR TAR: NAME= night1, PLSCOM= 1-0-10000&1-20000;
Entering a single basic tariff (1 pulse) followed (after 30 seconds) by multiple pulse
metering (2 pulses every 60 seconds):
ENTR TAR: NAME= night2, PLSCOM= 1-0-30000&2-60000;
Entering a single basic tariff followed by periodic pulse metering, with a maximum
call duration of 30 minutes and application of a call setup tariff of 10 charge units (on
answer):
ENTR TAR: NAME= day5,PLSSUP = 10, PLSCOM= 1-0-10000&1-20000-1800000,
SEQUENT=LIMIT
Entering a single basic tariff (1 pulse) followed (after 30 seconds) by multiple pulse
metering (2 pulses every 60 seconds), repetition of this sequence after 30 minutes,
and including a call attempt tariff of 4 charge units:
ENTR TAR: NAME= day6, PLSATT = 4,PLSCOM = 1-0-30000&2-60000-1800000,
SEQUENT=CYCLIC;

1.4.1.4

Tariff Switchovers
Tariff switchovers can be defined to take place at a specific time, the tariff switchover
time, or after a specific call duration, on the basis of a tariff sequence.
One of the tariffs in a zone is always in effect at any given time, depending on the time
of day and the category of the weekday (workday, weekend or public holiday).
Accordingly, times must be defined in the system for switchover to the appropriate tariff
(e.g. all national zones switched to Day7 tariff every workday at 8 a.m. and to Night3
tariff every evening at 6 p.m.).
A tariff switchover can only be created for a tariff sequence if the latter contains not more
than one PPM tariff or MPM tariff. If this condition is met, then switchover from one basic
tariff to another basic tariff or to a tariff sequence in the course of a call is permissible,
as is switchover from one tariff sequence to another or to a basic tariff. This restriction
can also be removed, depending on the project.
In the case of basic tariff switchovers involving PPM/PMM tariffs within a tariff sequence,
there is always a waiting period until the current periodic time interval and the basic tariff
duration have elapsed. The basic tariff duration is thus extended by the length of the
periodic time interval if the latter has not yet elapsed.
A tariff switchover can only have an effect on the call setup charge if the called party has
not yet answered, otherwise call setup is billed on the basis of the old tariff.
Switchovers of communication tariffs have the following effects:
a) In the case of switchover of an SPM/MPM tariff to an SPM/MPM tariff, the new tariff
does not become effective during a call in progress.
b) In the case of switchover of a PPM/PMM tariff to an SPM/MPM or PPM/PMM tariff,
there is a waiting period for the periodic time interval to elapse before the new tariff
takes effect.
Tariff switchovers for a zone are entered by means of ENTR TARSW. The precondition
for this is that the tariffs to which switchover is to take place have already been defined
with ENTR TAR. A tariff switchover can be entered up to 30 days before it is due to go
into effect.

IN 62

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Switchover from one tariff to a new tariff takes place on the basis of 15-minute intervals
(parameter TIME). The date on which the command should first be executed can be
varied by means of DATE. The tariff which is active at a particular time can depend on
the weekday category (WDCAT).If this parameter is not specified, switchover takes
place every day.
If statistics metering is being carried out in the exchange, switchovers should also be
created for the statistics meters, depending on tariff switchovers, if identical tariff
switchovers have been created for zones in zone points with the same statistical index
or if a statistical index is assigned to a single zone point only. In all other cases, there is
no need to synchronize tariff switchovers and statistics counter switchovers.
Examples of tariff switchover input:
Entering a tariff switchover for 8 a.m. on workdays (to daytime tariff):
ENTR TARSW: ZONO= 4, NAME= day7, TIME= 8-00, WDCAT= WO;
Entering a tariff switchover for 6 p.m. on workdays (to night-time tariff):
ENTR TARSW: ZONO= 4, NAME= night3, TIME= 18-00, WDCAT= WO;
These tariff switchovers take place periodically according to the weekday category.
The command MODTAR is used for single (non-periodic) switchover to another
tariff, e.g. replacement of tariff day8 by tariff day9 in all zones:
MOD TAR: NAME= day8, NNAME= day9, TIME= 10-45, DATE= 99-10-15;

1.4.1.5

Weekday Categories
Tariff switchovers can be performed dependent of the category of the current day. This
permits a highly flexible tariff structure, for example it is possible to switch over to a lower
tariff on Sundays than on public holidays. A further possibility is to apply the weekday
tariffs to international calls on national holidays.
The following day categories are available:
workday (WO)
first day of the weekend (half day, EH)
second day of the weekend (full day, EF)
national holiday (HN)
international holiday (half day, HH)
international holiday (full day, HO)
Public holidays are either movable or fixed.
Fixed holidays fall on the same date every year and thus on a different day of the week
each time. They can be either half holidays (e.g. December 24 in Germany) or full holidays (e.g. January 1). The full holidays can in turn be alternatively national holidays (e.g.
May 1) or international holidays (e.g. December 25).
Movable holidays vary in date from year to year but always fall on the same day of the
week. Here, too, there are both national holidays (such as Easter Monday) and international holidays.
These are entered in the holiday table by means of the command CR HOLICALand
displayed with command DISP HOLICAL.
The weekdays are independent of the year; they are administered with MOD WDCAT
This command is also used to enter the weekend. For example: Saturday can be specified as the first day of the weekend and Sunday as the second day of the weekend.
The priorities for weekdays are as follows:

A30808-X3003-X458-2-7619

IN 63

OMN:SSS-TA

Operation Charging

HO; HH>EF, EH>HN>WO.

This means that if an international holiday falls on a Sunday, the tariff switchovers for
the holiday are performed. On the other hand, if a national holiday falls on a Sunday, the
tariff switchovers for the Sunday take place. This must be taken into account when
entering the weekday categories.

1.4.2

Zone Points
Call charges are generally calculated on the basis of the distance between the calling
and called parties. In other words, a local call can be less expensive than a longdistance call because it uses fewer network resources.
This is implemented by dividing the network into different zones (see Fig. 1.24).
100 km

50 km

25 km

ZONO 4
ZONO 1

ZONO 2

ZONO 3
PSTN 1

Fig. 1.24

PSTN 2

Telephone network with four zones

Thus, there are separate zones for:

local calls
long-distance calls
international calls
intercontinental calls.
Each is governed by a uniform call-charge policy, comprising the currently valid tariffs
and the times set for tariff switchovers (from daytime to night-time tariff, etc.).
The tariffs for these zones must be entered before the zone points are created.
In call processing, the zone is identified by the digit-zone translator by interpreting the
dialed digits.
The translator must perform the following functions on the basis of predefined digit
combinations, line codes (e.g. category and origin) and if applicable the language
digit:
Zone point identification:

IN 64

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

own exchange
remote exchange
no exchange (i.e. zone point not created)
Zone point = own exchange:
establishment of zone (1-126, 128-254, 256-511)
Zone point = remote exchange:
Establish whether
zoning has already taken place
zoning has still to take place.
Establish charge billing method:
AMA
pulse metering
statistics metering.
If the charge billing method is pulse metering, the subscriber meter which is to be
used for metering must be specified. There are meters for the charge units and
meters for the number of calls.
If the charge billing method is statistics metering, the statistics index which is to be
used for metering must be specified.
Establish meter processing (analysis of incoming meter pulses):
suppress answer pulse
suppress 1st meter pulse.

1.4.2.1

Creation of Zone Points

Zone points are created with the command CR ZOPT. This must be done in all
exchanges lying in the path from the origin to the zoning point, because it is not possible
to set up calls without a zone point. In all exchanges that precede the zoning point, it is
defined that zoning is to take place in a higher-ranking exchange. In the exchanges that
lie beyond the zoning point, the incoming trunk group is informed that zoning is no longer
needed.
There is a large number of parameters which allow zoning treatment to be adapted to a
given network environment.
Explanation of parameters
The parameters are listed here in the same order in which they can be found in the CML.
Numbers in brackets, e.g. (3), refer to the zoning point (see Fig. 1.25).

A30808-X3003-X458-2-7619

IN 65

OMN:SSS-TA

Operation Charging

Zoning point:
(1)
(2)
(3)
(4)

local exchange
transit exchange
service switching point
international gateway exchange

SCP

SSP

AVSt

(3)

(4)

B in own
exchange
OVSt

FVSt

OVSt

(1)

(2)

(1)
B in other
exchange

Fig. 1.25

Zoning points

CODE
Digit combination to be assigned to a zone.
(1) CR ZOPT: CODE= 089, ZONO= 10, BILLING=METERING; SUCHCNTR=CNTR2
Calls to the digit combination 089 are charged using the tariff defined for zone 10.
LAC
In exchanges serving two or more local networks, separate zone points (and thus separate tariffs) can be defined for each local network.LAC is specified in the case of a
multiple directory number volume to uniquely identify the called party.
Given:
Subscriber A (local network 089, DN= 1234) in zone 10, subscriber B (own exchange,
local network 088, DN= 1234) in zone 12.
ENTR DNATT: DNVOL=MULTIPLE;
ENTR AREACODE: LAC= 089;
ENTR AREACODE: LAC= 088;
CR DN: LAC= 089, DN= 123400&&123499;
CR DN: LAC= 088, DN= 123400&&123499;
(1) CR ZOPT: CODE= 1234, ZONO= 10, BILLING=METERING; SUCHCNTR=CNTR2
(1) CR ZOPT: CODE= 1234, ZONO= 12, BILLING=METERING; SUCHCNTR=CNTR2
Charges for a call from A to B are registered on the basis of the tariff applicable to zone
12. The tariff for zone 10 applies for calls from B to A.

IN 66

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

ORIG2
ORIG2 allows the zoning exchange to apply different zoning to subscribers with the
same LAC(for instance in a large city).
MFCAT
This parameter is used for origin-dependent zoning. MFCATdefines the type of
subscriber station, allowing, for example, coinbox lines to be zoned differently to ordinary subscribers.
ZDIG
This parameter is used for origin-dependent zoning. The valid zone is determined on the
basis of the language spoken in the country of origin.
To enable the international gateway exchange to evaluate the language digit, the
gateway exchange in the country of origin must transfer parameter ZDIGThis is done via
the route.
FPH
The freephone indicator FPH is used to obtain a zoning result in the international
gateway exchange for TFS traffic (from a TFS exchange or an SSP in the IN) that differs
from that for other traffic. The FPH indicator is appended to the dialed digits via ISUP by
the exchange that detected the TFS call. This means that it is no longer necessary to
create special trunk groups for TFS.
ZONO
ZONO specifies which zone is valid for the calls. Different zones can be defined by
means of tariffs and tariff switchovers.
It is not possible to administer zones 0, 127 and 255.
Zone 0 means that calls are free of charge (entered with parameter ZOCHA).
Zone 127 means that calls are zoned in a lower- or higher-ranking exchange.
Zone 255 is the default zone (no assignment to a zone).
Depending on the particular project, zone points with fixed tariffs can be defined, for
example:
zone 101 for single pulse metering (SPM)
zones 102 to 110 for multiple pulse metering (MPM) with 2-10 pulses per call.
ZOCHA
The zone characteristics parameter is used to define the zoning point. To enable meter
pulses or charge band numbers to be signaled in the network, all trunk groups involved
must be created with METOTR. Charge band numbers are assigned to zones with
command MOD ZOINF. Evaluation of the charge band messages is allowed with
parameter TKZOINF=YES.
BILLING
The BILLING parameter defines the method of billing to be used for calls via this zone
point (AMA and/or METERING).
SUCHCNTR
When charges are registered by means of meter pulses (METERING), it must be
defined which of the subscriber charge counters CNTR1 to CNTR5 is to be used to

A30808-X3003-X458-2-7619

IN 67

OMN:SSS-TA

Operation Charging

register the pulses.

TKZOINF
TKZOINF defines whether charge band messages received from the higher-ranking
exchange are to be evaluated for zoning or not.

1.4.3

Charge Band Message and Zone Traffic Type

With the introduction of the charge band message, the generation of a unit-interval, in
accordance with current tariff regulations, is shifted as far as possible toward the calling
party.
In previous versions with zoning in higher-level exchanges, the meter pulses generated
in such exchanges were transferred to the calling party over the network. The network
can now be relieved of this meter pulse transmission via the trunks (see Fig. 1.26).

PSTN

PSTN
ZOCHA=ZONINHI
Local 0049
exch.
digital

ZOCHA=ZONINHI
CCS7
ZRM 56

ZRM 56=ZONO 15 = Tariff 4

0049=ZONO15=ZRM

GateTrans. 0049 CCS7

exch.
ZRM 56 way
exch.
digital
digital

0049
Gateway
exch.
digital

Tariff 4
Local
exch.
EMD

Fig. 1.26

0049

Pulse

Administration of charge band numbers

Only the charge band message has to be signaled on the long distance level; transfer
by meter pulses is not required until the transition from a digital exchange to an
exchange with pulse signaling.
It is possible to change the assignment of charge band message to zones by means of
MML.
In addition, the system is capable of processing charge band messages which are
received during calls in progress. The tariff is created according to the new zone. Only
the communication part of the new tariff is taken into account. There is a waiting period
for time-out of the currently active interval or of the timer for non chargeable time. If
several charge band messages are received during this period, the last message is
executed.
If no further messages are received apart from the first charge band message, the tariff
switchovers which apply in the current zone are implemented.
If a meter observation is in progress for a subscriber, a new intermediate record is

IN 68

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

created when a new charge band message is received (every 10 seconds maximum).
For properly tariffed charge registration, the zone points must be created with
ZOCHA=ZONINHI in the non-zoning exchanges.
All routes involved must be created with metering over trunk.
The assignment of a zone to a specific charge band message must be identical in all
exchanges concerned.
The corresponding zone point must be allowed to accept charge band messages.
If an expected charge band message does not arrive, the call is released. The same
treatment applies if the system operator has omitted to allocate a zone to a charge band
message.
It is also possible, using MOD ZOINF, to assign a zone to a particular zone traffic type.

1.4.4
1.4.4.1

Supplementary Services
Registration of charges for the input of supplementary
services (facility input FAI)
Supplementary services such as call diversion, abbreviated dialing etc. are created by
the operating company, in some cases at the request of the subscriber. They can also
be created by means of subscriber control input (SCI). It is possible for charges to be
registered for the input of supplementary services (facility input charges).
The registration of facility input charges is created with the command CR FAICHA.
The following methods can be used to register charges for facility input by the subscriber
(FAIS):
AMA
pulse metering (SPM or MPM)
AMA and FIR.
If FAIS charges are to be registered by means of meter pulses, parameter METPULS
must also be specified, otherwise inputs are free of charge (the default value is 0 meter
pulses).

1.4.4.2

Registration of charges for the usage of supplementary

services (facility usage FAU)
Facility usage (FAU) charges are normally only applied in connection with an established call. In principle, however, they are registered independently of the call they
accompany. If AMA or FIR is used to register charges both for the call itself and for FAU,
then only one ticket is produced.
Exceptions to this rule are:
three-way calling
large conference
completion of calls to busy subscribers (CCBS)
repeated use of the same supplementary service.
FAUs are always regarded as calling-party actions. Therefore, of the subscriber-related
charge treatments, only MOBorig is included, but not MOBterm. In other words, if the
called party makes use of the facility, no MOBterm ticket is produced.

A30808-X3003-X458-2-7619

IN 69

OMN:SSS-TA

Operation Charging

Meter pulses for FAU are only included in the AMA/FIRcall ticket or FAU ticket if parameter EXTNSD=CHARGESis specified in command ENTR CDTDAT.
The following methods of charge registration can be entered for FAU by MML
CR FAUCHA):
AMA
pulse metering (SPM or MPM)
AMA and pulse metering (SPM or MPM).
If charges are to be registered by means of meter pulses (BILLING=METERING),
parameter METPULS must also be specified, otherwise facility usage is free of charge
(the default value is 0 meter pulses).
Restrictions:
Charges may be registered for no more than 8 FAUs during one call. At the 9th FAU,
the call is released
in pulse metering, a maximum of 25 pulses is possible per FAU
pulse metering with PPM is not possible
there is no statistics metering
call counters SUCACNTR must not be used as counters for FAU )
all FAUs must use the same charge registration method or be free of charge, in other
words if AMA has been created for one FAU, all other FAUs must also be created
with AMA. It is, however, possible to use different numbers of pulses in the case of
METERING.

1.4.4.3

Account suspensions
The administration can activate and deactivate account suspensions for a subscriber
(e.g. blocking the terminal for international calls). It is possible to create facility input
recording FIRrecords as subsequent proof of such action.
These records have a similar structure to AMA records, but are not used for charge
registration.
They include:
directory number
suspension entered
date of command input
type of input (activated/deactivated).
and, additionally to the data contained in an AMA record: the line type.
The records are stored in a cyclic file with occupancy level alarm signaling.
Capture of the data in an FIR record is created by means of CR FAICHA. The prerequisite for this is that the system feature has been activated (ACT IAFEAT).

1.4.5
1.4.5.1

Counter Administration
Creation of Counters
Counters can be created in the transient memory area of the CP to record meter pulses
for the accumulation of charges and to record call duration, number of calls etc.
There are five different types of counter, each serving a different purpose:
subscriber counters
statistical counters

IN 70

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

trunk meters
counters for toll free service (TFS)
IARA counters

A uniform counter administration concept has been introduced. It covers uniform procedures for the editing, saving and regeneration of subscriber, statistical, trunk and TFS
counters. The existing security mechanisms for IARAcounters have been adapted to
this new concept, but otherwise the treatment of IARA counters is still somewhat
different to that of the other counters.
To allow the contents of the counters to be read out and processed, the format, counter
threshold and directory number type must be defined for each type of counter with
command ENTR METADM.
For subscriber counters, the format defines the selection of counters and the record
length used. For statistical counters, it defines the composition of the set of counters.
For trunk meters it defines the accuracy of the trunk group identification and for TFS
counters it defines the accuracy of the code identification.
The directory number type defines the subscriber (in terms of line type) for whom charge
records are to be written to the billing file.

1.4.5.2

Creation of Backup Files

Depending on the type of counters activated, backup files are created on the following
occasions:
during the first system recovery after an APS change
at the next save time that was entered with command ENTR METSAV or, if no such
time has been input, at the usual system save time of 00:30 hours
when the operator enters command SAVE MET
when a billing file and an APS change file have been created with command
EDIT MET
after the counters have been regenerated with REG MET
Up to 8 automatic save times per day can be created with ENTR METSAV. At the save
time, the validity of the counter contents is checked by calculating the checksum bytes.
If the contents are valid, a backup file is saved both to main memory and to disk. If the
contents are not valid, they are regenerated from the last backup file and then saved to
disk. If errors are found both in the counters themselves and in the backup file, an alarm
is signaled at the system panel. Section 1.4.5.4 explains how to deal with this situation.
Up to 9 intermediate saves can be created to take place between 2 save times. In an
intermediate save, the checksum byte is calculated over the counter contents, evaluated, and if an error is found the counter contents are restored.
Backup files are stored under the name CA.xx.UCHA, where
xx = SU for subscriber counters
ST for statistical counters
TR for trunk meters
TF for TFS counters.

1.4.5.3

Billing File
For billing, a billing file must be generated for each counter type (once a month for
example), using

A30808-X3003-X458-2-7619

IN 71

OMN:SSS-TA

Operation Charging

EDIT MET: TYPE=...,FUNC=ACCOUNT;

Billing files are stored under the name CA.xx.CHA, where
xx = SU for subscriber counters
ST for statistical counters
TR for trunk meters
TF for TFS counters
nn = serial number.
The billing file is created in the format required for postprocessing.
The billing file can be transferred to tape and sent to the computer center for postprocessing or transferred to the postprocessing center via a data link (FTAM).

1.4.5.4

Counter Restoration
Restoration after generation fallback
Generation fallback is the loading of an older APS generation of the same APS version.
It involves reloading of the semipermanent memory area from a backup copy of the
previous APS generation. Unlike ODAGEN runs or APS changes, generation fallback
includes the setting of a so-called fallback flag, which blocks the counters.
The system checks the fallback status of the counters every 10 minutes. If the flag has
been set for one or more counters, this information is output at the OMT screen every
10 minutes, because meter saving is not possible during this time. Entering command
SAVE MET forces display of the blocked counter types. Because the counter contents
are regenerated from a backup file after fallback, any meter pulses received for the
subscriber, trunk, statistics and TFS counters in the interim period are not counted, and
in the case of IARA counters the threshold may be exceeded.
Before unblocking the counters, the logging file must be read in.
Then the fallback procedure can be started with
SAVE MET: TYPE=....,FUNC=FALLBACK;
The flag is reset and the counter readings are regenerated from the backup files.
Counter restoration after APS change
Before an ODAGEN run or APS change, the meter readings must be saved to an APS
change file. This is done with
EDIT MET: TYPE=....,FUNC=APSCHANG;
APS change files are stored under the name CA.xx.APS.nn, where
xx = SU for subscriber counters
ST for statistical counters
TR for trunk meters
TF for TFS counters
nn = serial number.
This file is copied to tape (TRANS FILE).
After the APS change, the meter readings in main memory and on disk are initialized

IN 72

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

and the APS change files are transferred from tape to disk (TRANS FILE). They are also
renamed, because CA. files are write-protected. Then the counter contents are read
from the APS change file with
REG MET: TYPE=...,FILE= <new filename>;
and added to the counts that have accumulated since system start and the regeneration
run. In the case of subscriber counters, this is only possible if the LAC has not changed
as a results of the APS change. Furthermore, the thresholds defined for the counters in
the APS change file and in the new APS must be identical.
Checking and restoring counters by the operator
Operating personnel can use the command SAVE MET to force the creation of a new
backup file and to check the validity of the current counter table.
Depending on the extent of the error that has been found, steps should be taken in the
following order:
1. Meter check
SAVE MET: FUNC=CHECK;
This input executes functions that correspond to those of the intermediate save
defined under ENTR METSAV
2. Simple meter restoration
SAVE MET: FUNC=SAVE;
First, new backup files are created for all activated counter types. Their validity is
checked block by block by calculating checksum bytes. If checksum errors are
found, the corresponding counts are taken from the old, error-free backup file. If
more than 10 such errors occur in the same block, the entire block is taken from the
old backup file. Errors that occur only in the counters, and thus in the new backup
file but not in the old file, are described as simple errors.
The repaired counts are displayed at the OMT. When this save has been completed,
the old backup file is automatically deleted and the new file is stored as the current
backup file.
3. Meter restoration after double errors
SAVE MET: FUNC=SAVE;REFILE= CA.xx.UCHA;
Double errors are checksum errors that are found both in the counter memory and
in the backup file. In this case the counts are restored with the aid of a repair file.
The repair file is an older copy of the backup file. For this reason, an old backup file
should always be held available on tape. It must be a file from the current APS,
however.
4. Meter restoration after double errors without repair file
SAVE MET:FUNC=SAVE;REFILE = CA.xx.UCHA, ZEROIN=YES ;
This command is equivalent to that in point 3. above. The only difference is that, in
cases where checksum errors have been found in memory, in the backup file and in
the repair file, or if these files are not available or are out of date, then the counts in
question are reset to zero.
Here too, the reinitialized counts are output at the OMT.
This command is equivalent to that in point 3. above. The only difference is that, in
cases where checksum errors have been found in memory, in the backup file and in
the repair file, or if these files are not available or are out of date, then the counts in
question are reset to zero.
Here too, the reinitialized counts are output at the OMT.

A30808-X3003-X458-2-7619

IN 73

OMN:SSS-TA

Operation Charging

1.4.6

Subscriber Meters
Each subscriber is assigned 5 counters for use as charge meters when created. How
many of these are actually used can be set by means of CR ZOPT. When the counters
are activated it is important to ensure that they are consistent with the counters activated
in parameter FORMAT of command ENTR METADM. If only one is used for a
subscriber, all charges are accumulated on this one. If a subscriber is assigned several
counters, the number of calls, the call charges, the facility input charges and the facility
usage charges can be registered on separate counters.
Call charge meter
The counter to be used for registering the call charges is specified in command
CR ZOPT (parameter SUCHCNTR). Any of the counters 1 - 5 can be used for the call
charges.
Meter for number of calls made
The counter to be used for registering the number of calls is specified in command
CR ZOPT (parameter SUCHCNTR). Here, only counters 1 or 3 can be used.
Charge meter for subscriber facilities
The counter to be used for storing the facility charges can be specified by means of the
input command ENTR CDTDAT. Different counters can be entered for subscriber
controlled inputs and subscriber facility usage.
Counters which store the number of calls (parameter SUCHCNTR) in command
CR ZOPT) may not be used as charge meters, since this would result in the mutilation
of data.

1.4.7
1.4.7.1

Statistics Meters
Use of Statistics Meters
Statistics metering can be created in order, for example, to support the network management system with information on traffic distribution, for statistical purposes, or for
interadministration revenue accounting. In order to perform statistics metering, the call
charge registration must be created with pulse metering.
Statistics metering can be initiated for the following call types:
calls zoned via a specified zone point;
calls directed to a destination via a specified route;
calls entering the exchange via a specified trunk group.
The operating personnel can assign statistics indices to each of these objects (zone
points, routes, incoming or bothway trunk groups). The assignment of this index means
that for calls which pass via one of these objects the number of calls, the number of
meter pulses, and (in certain cases) the call duration are registered in sets of statistics
meters. If statistics indices for two or more objects are encountered during call setup,
metering is only performed for one object. This in turn distorts the statistics metering.
The priorities for object selection are as follows:
route
zone point
incoming trunk group.

IN 74

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Although statistics indices can be specified for all three objects, only one object (e.g.
only routes) should be used in one project.

1.4.7.2

Statistics index Structure and Selection of Currently

Active Statistics Meter
For statistics metering, up to 256 statistics indices can be assigned for objects of the
same type (see Fig. 1.27).

Statistics indices

Statistics meter groups

Statistics index 0

Registration point 0

Statisticsmeter
group 0

Statistics index 1
Statistics index 2

Registration point X

Registration point 255

Statistics index X

Registration point 0

Statisticsmeter
group 1

Registration point X

Registration point 255

Statistics index 253

Statistics index 254
Statistics index 255

Registration point 0

Registration point X

Statisticsmeter
group 14

Registration point 255

Registration point 0

Registration point X

Statisticsmeter
group 15

Registration point 255

Fig. 1.27

Assignment of statistics indices to statistics meter groups

A statistics index refers to a registration point with the same numbering scheme. Registration points are combined to form statistics meter groups. Depending on the directory

A30808-X3003-X458-2-7619

IN 75

OMN:SSS-TA

Operation Charging

numbers, up to 16 statistics meter groups, each with 256 registration points, can be
created. If a number of groups have been formed, a statistics index refers to the corresponding registration points in all statistics meter groups which have been created.
Statistics meter groups are directly related to directory number blocks, i.e. the directory
number (calling party number in the own exchange) determines the statistics meter
group in which the relevant registration point is addressed.
In the case of calls which reach the exchange via a specified trunk group, the meter
pulses for the given statistics index are metered in statistics meter group 0, since the
calling party number does not belong to the directory number volume of the own
exchange and therefore cannot be assigned to a group.
Up to 6 time groups (depending on the time, the weekday category and the date), each
with 3 subscriber types (ordinary subscriber, coinbox line, service handset) can be
created for a registration point. This means that 18 sets of statistics meters are available;
these are configured as summation meters (see Fig. 1.28).

Registration point X

Subscriber

Coinbox line

Service handset

Statistics meter set 1

Statistics meter set 2

Statistics meter set 3

Time group 0

Statistics meter set 4

Statistics meter set 5

Statistics meter set 6

Time group 1

Statistics meter set 7

Statistics meter set 8

Statistics meter set 9

Time group 2

Statistics meter set 10

Statistics meter set 11

Statistics meter set 12

Time group 3

Statistics meter set 13

Statistics meter set 14

Statistics meter set 15

Time group 4

Statistics meter set 16

Statistics meter set 17

Statistics meter set 18

Time group 5

Fig. 1.28

Structure of a registration point X

One of the 6 time groups is always valid at any given time, i.e. the traffic is added to this
group.
A set of statistics meters consists of three meters:
number of calls,
number of charge units,

IN 76

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

call duration,

and the checksum byte.

The meter for call duration must be activated separately .
The meter readings can be displayed on the screen by means of the command
DISP STATMET. The number of statistics meter groups can be increased to a maximum
of 16 by way of an ODAGEN run (using MOD DBSIZE). Statistics meter group 0 is
permanently configured. A statistics meter group consists of 256 registration points. This
results in a maximum of 4096 registration points for statistics metering for zone points
and routes; only 256 registration points are available for incoming trunk groups,
however, since in this case the metering can only be performed in statistics meter group
0.
In the event of a call, the statistics index is read out of the SETUP data. It points to the
corresponding registration points in the statistics meter groups.

1.4.7.3

Statistics Meter Switchover

When statistics meter switchover takes place, there is a changeover from one time
group to another, depending on the time, the weekday category and/or the tariff switchovers.
Statistics meter switchover is always advisable when, for example, the same tariff
switchovers apply to zones which are linked via one or more zone points with the same
statistics index. This allows charges to be included in statistics as a function of the tariff,
i.e. dependent on time of day and weekday category. If a statistics index is assigned to
different zone points with different tariff switchovers in order to perform a specific task,
it is, of course, not necessary to synchronize statistics and tariff switchovers.
Statistics meter switchover is always applicable to all statistics meter groups.
Measurement of the total traffic for this statistics index in the new time group of all relevant statistics meter groups commences at the time of switchover.
The time of switchover must be entered at least 10 minutes beforehand. This switchover
time must be set to a 15-minute interval.
A total of 2047 switchover requests can be entered for a statistics project.

1.4.8

Trunk Meters
With the aid of trunk meters, the traffic between different operating companies can be
monitored and the charges registered. Each trunk group is assigned, on either side,
meters which summate the number of calls made via this trunk group and also the meter
pulses. If a trunk group is bothway, it can only be used in one direction for trunk group
metering, i.e. either in the incoming or the outgoing direction, otherwise the meter readings will be distorted. For incoming trunk groups, metering is created with
GCOS=TRMET on the basis of the trunk group data. For outgoing trunk groups, the
trunk group data must also be created with GCOS=TRMETand metering must be
enabled by way of the routing data by means of LNDS=TRMET.
The contents of the meters can then be compared by both operating companies. In the
following, the term A side of a trunk group refers to the A side of the second exchange,
while the term B side of a trunk group refers to the B side of the first exchange. The
direction of a call is from the B side (of the first exchange) to the A side (of the second

A30808-X3003-X458-2-7619

IN 77

OMN:SSS-TA

Operation Charging

exchange).
A trunk meter consists of a set of 5 counters:
1.
2.
3.
4.
5.

number of successful incoming and outgoing calls

meter pulses received from the B side before the called party answers
number of meter pulses received from the B side in the course of the call
meter pulses received from the B side after the calling party has gone on-hook
meter pulses received from the B side in the idle state

Meter pulses which are received in the talk state are summated by both sides in the
respective GP and forwarded to the CP at the end of the call (meter 3). Meter pulses
which are received outside the call state, i.e. erroneously, are immediately forwarded
from the GP to the CP (meters 2, 4 and 5).

1.4.9

Individual Call Data Administration Feature

The individual call data administration feature is created in order to collect the charge
data for each call in the form of a data record. These records can then be postprocessed
in a data processing system and used for detailed billing. With certain types of data it is
possible to print out the data records on the on-line printer as soon as they have been
compiled.
In some countries the record layout deviates from the standard layout (e.g. because
additional data are requested). Data may also be required in different codes for the postprocessing computers (binary, hexadecimal, etc.). There are copying processes
(AGFRx) for such adaptations; these can be activated when the record files are copied
from disk to tape or from disk to host processor.
Fig. 1.29 shows an overview of the different types of individual call data administration
Individual call data administration feature

AMA

AMAI
Fig. 1.29

DEB

MOB

PMOB

MOBI

FIR

IARA

INA

Immediate printout

Different types of individual call data administration

The following types of data can be captured by activation of the individual features
(ACT IAFEAT, parameter TYPE):
AMA
AMA data are used for charge accounting. Recording is dependent on:
destination (assignment by means of CR ZOPT) or
incoming trunk group (assignment by means of CR TGRP) or
subscriber facility (assignment by means of CR FAICHA and CR FAUCHA).

IN 78

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

DEB
DEB data are also used for charge accounting. Registration is dependent on the
calling party.
MOB
MOB data are used for observation of the activities (originating and terminating
traffic, FAIS/FAU) of individual subscribers. Registration is dependent on the calling
party (assignment by means ofACT MOBS) and is for a set period (e.g. one month).
PMOB
PMOB data are used for locating expensive calls in connection with pulse metering.
A data record is created if the call charges exceed a (programmable) limit.
FIR
FIR data are used for recording the creation and cancellation of account suspensions by the operating company. Registration is dependent on the type of suspension (assignment by means of CR FAICHA, ).
INA
INA data are used to calculate charges for service subscribers engaged in IN calls.
Registration is dependent on the service subscriber (assignment in SCP/SMS).

The following are available for immediate output:

AMAI (also for DEB)
AMAI data are used for the immediate output of AMA data records. A printout is
made when an AMA or DEB data record is created and a subscriber is in the immediate output mode; .
MOBI
MOBI data are used for the immediate printout of MOBdata records. Printout is
dependent on the subscriber (assignment by means of ACT MOBS).

1.4.9.1

Automatic Message Accounting (AMA)

AMA-data
AMA data are recorded for:
chargeable outgoing calls, depending on the destination ; the ticket includes usage
of service facilities if usage billing with AMA has been created and charges become
due (usually if the call is answered);
incoming calls via trunk groups with the property AMA (trunk group attribute)
unsuccessful calls ).
successful subscriber controlled inputs
usage of service attributes on the B side if usage billing with AMA has been created
and charges become due (usually if the call is answered);
usage of service facilities on the A side if no call ticket is generated, provided that
usage billing with AMA has been created and charges become due (usually if the
call is answered);
inputs by the administration .
If several types of recording are detected for a call (e.g. AMA and DEB or AMA for the
call and for usage of a service facility by the calling party), only one record is generated.
Exceptions:
three-party conference
large conference
call completion to busy subscriber (CCBS)
repeated use of a supplementary service.

A30808-X3003-X458-2-7619

IN 79

OMN:SSS-TA

Operation Charging

The following data are recorded:

calling party number
digits dialed (called party number)
date and time of call
call duration, etc.
The records are generated at the end of the call. In the case of long duration calls, intermediate records are created (e.g. every 30 minutes). The timer for this function can be
administered.
AMA data are collected in a duplicated cyclic disk file. These data are made available
for the compilation of a total bill. An individual bill is created by means of a display job
(DISP AMA).
For postprocessing, the data can be copied to tape or transferred over a data link:.
A three-stage threshold value alarm function is created for the cyclic disk file by means
of SET FGRPATT. If the threshold value (e.g. 75%) is exceeded, an alarm is output.
Saving the file well before it is full ensures that data will not be overwritten and lost (e.g.
at night). An additional threshold value (e.g. 65%) can be entered in order to reduce the
likelihood of operator assistance being required at night. By assigning an alarm to this
lower threshold value it may be possible to make the backup copy during normal working
hours.
AMA features
Additional AMA functions are controlled by the command ENTR CDTDAT.
These functions are:
collection of additional data (e.g. charge units and zone)
collection of alternative data (e.g. start rather than end of call)
generation of AMA data records in special cases (e.g. for all unsuccessful calls).

1.4.9.2

Detailed Billing (DEB)

DEB data
DEB data are recorded for:
chargeable outgoing calls, depending on the subscriber ; the ticket contains a record
of the usage of service facilities if usage billing with AMA and/or METERING has
been created and charges become due (usually if the call is answered);
usage of service facilities on the B side if usage billing with AMA and/or METERING
has been created and charges become due (usually if the call is answered);
successful subscriber controlled inputs
usage of service attributes on the A side if no call ticket is generated, provided that
usage billing with AMA and/or METERING has been created and charges become
due (usually when the call is answered).
Data recording is also affected by the subscriber authorization:
DEB general (all the above-mentioned cases apply).
DEB for traffic classes: only calls with a defined traffic class (e.g. all international
calls) are registered.
DEB for the next call: this requires input of a special code before the actual dialing
information is entered.
The rules for DEB are basically the same as those for AMA. DEB is assigned for each
subscriber, however. The records are stored in the AMA file. They are marked (a set bit

IN 80

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

or flag), so that they can be separated from the AMA records at the postprocessing
stage.
If both AMA and DEB are required for a call (DEB subscriber calls via a zone point with
AMA ), only the AMA record is produced. This record contains the EXTSND and
ALTNSD in accordance with AMA but the DEB flag is set.
If a DEB record is required for several purposes (e.g. for the call and for the usage of a
service facility), only one record is created.
Exceptions:
three-party conference
large conference
call completion to busy subscriber (CCBS)
repeated use of a supplementary service.
DEB features
Additional DEB functions are controlled by the command ENTR CDTDAT.
These functions are:
collection of additional data (e.g. charge units and zone)
collection of alternative data (e.g. start rather than end of call)
generation of DEB data records in special cases (e.g. for FAI and FAU or for FAIS).

1.4.9.3

Meter Observation (MOB)

MOB data
The administration of meter observation (MOB) is one of the tasks covered by
OMN:SSS-SU:MSC (Subscriber Administration), which contains more detailed information on MOB. It is only referred to here in order to complete the description of communications data recording.
Subscribers can apply for MOB for a limited period of time. They do not necessarily have
to be supplied with meter pulses, since a MOB data record is also created for nonchargeable calls.
MOB data can be generated in the following situations:
outgoing and incoming calls
subscriber controlled inputs
facility usage for supplementary services
TFS calls in the TFS exchange.
The data are recorded for:
outgoing calls and subscriber controlled inputs, if at least one digit has been dialed.
The ticket contains a record of facility usage for supplementary services if usage
billing with AMA and/or METERING has been created and charges become due
(usually if the call is answered).
successful incoming calls if the subscriber also has the TERM authorization
facility usage for supplementary services on the B-side (own data record, separate
from TERM data record), if usage billing with AMA and/or METERING has been
created and charges become due (usually if the call is answered)
successful and unsuccessful calls in the TFS exchange.
When MOB is activated or deactivated for a subscriber, a FAIO data record is created
in order to record the period of observation.

A30808-X3003-X458-2-7619

IN 81

OMN:SSS-TA

Operation Charging

If a MOB data record is required for several purposes (e.g. for the call and for the usage
of a service attribute), only one data record is created.
Exceptions:
three-party conference and
large conference
call completion to busy subscriber (CCBS)
repeated facility usage.

call completion to busy subscriber (CCBS).

The MOB data collected can be output immediately at the terminal or on the printer or
in response to an MML request.
MOB data are collected in a double cyclic file. For postprocessing, the data can be
copied to tape or transferred over a data link (TRANS FILE).

1.4.9.4

Preventive Meter Observation (PMOB)

PMOB data
The administration of preventive meter observation PMOB like MOB itself is one of
the tasks covered by OMN:SSS-SU:MSC, which contains more detailed information on
PMOB . It is only referred to here in order to complete the description of communications
data recording.
Unlike the procedure for MOB , with PMOB a data record is only created if charges
exceed a set limit.
PMOB is part of the exchange data. The threshold value set in an exchange applies to
all subscribers.
With PMOB , the subscriber meters must be pulsed. It is therefore necessary to create
the appropriate tariffs and zone points with METERING in an exchange involved in the
call.
If another data record (AMA, DEB or MOB ) has been generated for a call in which the
PMOB threshold value is exceeded, no separate PMOB data record is created.
The data can be stored to disk or tape.
The PMOB data which have been collected can be output at the terminal or on the
printer by means of an MML command.

1.4.10
1.4.10.1

Call Charge Registration in the Intelligent Network (IN)

General
With the introduction of services in the intelligent network (IN), such as
freephone
televoting
universal number, etc.,
completely new demands are placed on the charge registration facilities. These requirements are fulfilled with a revolutionary concept for the charge registration of IN calls.
The basic concept is that both parties, i.e.
the calling party
the service subscriber (often the called party)

IN 82

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

can be assigned a proportion of the call charge which is incurred.

The question Who pays what? is answered according to the particular IN service used.
SSP on local level

SSP on transit level

SMS

SMS

X.25

SSP local

X.25

SCP

SCP

CCS7
Telephone
network

SSP

Fig. 1.30

CCS7

Telephone
network

OVSt

SSP

IN architecture (simplified)

The interface between the telephone network (PSTN) and the intelligent network (IN) is
the Service Switching Point (SSP), which can be implemented
on the local level, or
on the transit level (see Fig. 1.30).
There are two basic methods of charge registration for IN calls, depending on where the
charges are registered:
call charge registration by the Service Control Point (SCP) or the Service Management System (SMS);
call charge registration by the Service Switching Point (SSP).
Charge registration by the SCP/SMS is based on the creation of data records for each
IN call. The data required are collected in the SCP (on the basis of the call data supplied
by the SSP, which are transferred to the SCP/SMS at regular intervals). The customerspecific records are created from this in the SMS.
Charge registration by the SCP/SMS is only used for billing the service subscriber.
Charge registration by the SSP is based on the existing call charge functions in the telephone network. The SCP can affect the charge registration, e.g. by transmitting/predefining the zone number to be used.
Charge registration by the SSP can be used for billing both the service user and the
service subscriber.
OMN:SSS-TA contains the tasks involved in the administration of charge registration by
the SSP.

A30808-X3003-X458-2-7619

IN 83

OMN:SSS-TA

1.4.10.2

Operation Charging

Terminology
Service provider
The service provider is the telephone company that offers IN services to the service
subscriber, for instance, freephone.
Service subscriber
The service subscriber is, for example, a mail order company which accepts the charges
for orders placed by telephone.
Calling line
The calling line in an IN call is the calling party. The calling line can be either the service
user or the service subscriber.
Service user
The service user is, for example, a customer who places orders with a mail order
company free of charge.
Charge registration for the calling line
Normally the calling line's charges are registered in the PSTN by means of PSTN
methods. The IN (SSP/SCP/SMS) has the options of sending
free of charge, or
the zone, or
charge pulses.
The call charge method (AMA and/or METERING) is determined in the PSTN; any AMA
data are written to the PSTN AMA file.
PSTN charge registration (except for non-chargeable calls) should only be performed if
the user on the line is the service user and at the same time the owner of the calling line.
Charge registration for the service subscriber
The call charges are assigned to a line service number which is determined by the SCP.
This line service number belongs to an IN service subscriber.
The call charge method (AMA and/or METERING) is determined in the PSTN; any
AMAdata are written to the PSTN AMA file.
Trigger profile
The trigger profile is created in the SSP and specifies how the particular IN service is to
be processed.
IN-specific charge
This term refers to the determining of a zone, depending on the IN service used, but
independently of the actual destination of the call.
Charge registration default value
If the SSP expects from the SCP a zone which does not arrive, the call is processed
according to the default settings. The charge registration default value can be
suppressed as a project-specific option (flag).

IN 84

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Flexible charge registration

The SSP can change zone or create a new data record when a call is set up to a new
destination (the primary destination is busy). This includes calls to the intelligent
periphery (IP).
Divided charge registration
This term denotes simultaneous billing of two parties engaged in an IN call, usually the
calling line and the service subscriber. In some instances the charges have to be split
between two different service subscribers.
Ascending branch
This is one part of an IN call: from the calling party to the SSP.
Descending branch
This is the second part of an IN call: from the SSP to the called party.

1.4.10.3

Charge Registration for the IN Services: General

The question of who has to pay for what must be dealt with separately for each IN
subscriber. The amount of the charges to be paid by the calling line and/or the service
subscriber is dependent on the particular service. In addition, due account must be
taken of the network-specific aspects (location of zoning, signal repertoire of signaling
system, etc.).
In EWSD there are three options for registering charges for IN services:
1. charge registration only by the PSTN
2. charge registration only by IN components
3. charge registration divided between PSTN and IN.
Example
The charges for the universal number (UN) service can be registered as follows. The
charge total is divided between the calling line and the service subscriber (called
party). The user is charged for the ascending branch (from the calling party to the
SSP). One of the conventional methods is employed for this (e.g. pulse metering).
The service subscriber offering the UN pays for the descending branch (from the SSP
to the called party). An IN-specific AMA ticket is created for this subscriber.
The SSP detects from the dialed digits that the call is an IN call (via the code point). It
then branches to the relevant trigger profile in the CP. As a result of the subsequent
communication with the SCP, the SSP obtains the actual directory number of the called
party and the corresponding zone.
From ZOCHA=ZONINHI in the command CR ZOPT, the SSP knows that it must use the
zone sent by the SCP.
If the anticipated zone is not received, the charges for the IN call can be registered on
the basis of default values. These default values can be set in the IN trigger profile in the
CP by way of CR INTRIG. The following entries are possible:
the calling line remains free of charge
the default zone entered is used
the call is cleared down.
In the IN, data records are only created for the successful calls. Consequently, the
service subscriber only receives his data record if the call to the called party was set up

A30808-X3003-X458-2-7619

IN 85

OMN:SSS-TA

Operation Charging

successfully.
Special case
Through the use of IN components, the zoning of international calls by the PSTN is no
longer necessary. With this application, the calls are routed on the basis of dialed digits
and only the zone is supplied by the SCP. The code points are created without a trigger,
since the SCP does not have to supply a new B number. The zone points are created
with ZOCHA=ZONEXT<trigger-ID>.
For <trigger-ID> the same value must be entered as forCR INTRIG, parameter PRID.

1.4.10.4

Administration by MML
Charge registration for the calling line in the PSTN
The zone points are created in the exchanges in the telephone network. The charges
are only assigned to the calling subscriber.
Zoning in the home exchange:
CR ZOPT: CODE=0180, ZONO=268, BILLING=METERING, SUCHCNTR=CNTR1;
Zoning in a higher-level exchange in the telephone network; charge registration in
the home exchange:
CR ZOPT: CODE=0190, ZOCHA=ZONINHI, BILLING=METERING, SUCHCNTR=CNTR1;
Charge registration for the service subscriber in the IN
Activation of registration of the IN-specific AMA data records:
ACT IAFEAT: TYPE=INA;
Registration of the zone number in the IN data record by assigning a zone the charge
band message sent by the SCP:
MOD ZOINF: ZONO=345, CHBNO=145;
Allow zoning information to be accepted from the SCP:
CR ZOPT: CODE= ... , ... , TKZOINF=YES;
Registration of start date/time instead of end date/time (also applicable to MOB and
IARAMA):
ENTR CDTDAT: ALTNSD=RANSWTIM;
Registration of zone and charge units:
ENTR CDTDAT:EXTNSD=CHARGES;
Charge registration divided between PSTN and IN
Four steps are required for an IN call:
1.
2.
3.
4.

The CCS7 connection from the SSP to the SCP must be established
The triggers in the CP must be entered and activated (CR INTRIG and ACT INTRIG
The IN-specific announcements must be prepared (CR INC)
The relevant trigger in the CP is activated by the identification of an IN call. There
are two possible cases:
Identification via the code points (CR CPT)
Identification via the zone points (CR ZOPT).

IN 86

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Case 1: Identification via the code points

This is the standard situation. The code points contain a reference to the trigger profile
in the CP (by means of parameter TRATYP). This activates communication with the
SCP. The zone points are created by way of ZOCHA=ZONINHI (in the SSP). The SCP
sends the actual called party number and the zone to be used (see Fig. 1.31).
SCP

Trigger via code point: ZOCHA=ZONINHI

Trigger via zone point: ZOCHA=ZONEXTI

ZOCHA
ZONINHI
Local
exch.

SSP

zoned

Local
exch.

Fig. 1.31

Identification of IN call via code point or zone point

The service user's charges are to be registered with pulse metering:

CR ZOPT: CODE=190, ZOCHA=ZONINHI, BILLING=METERING,
SUCHCNTR=CNTR1;
The service user's charges are to be registered with AMA tickets:
CR ZOPT: CODE=190, ZOCHA=ZONINHI, BILLING=AMA;
Creation of the trigger profile for the freephone service:
CR INTRIG: PRID=FPHS1, SKEY=31, ... ;
Creation of the code point:
CR CPT: CODE=0130, TRATYP=IN6FPHS1;
Activation of the trigger profile:
ACT INTRIG: PRID=FPHS1;
If the zone to be sent by the SCP is not received, a default registration can be set in the
trigger profile (project-specific).
Zone 355 is to be used for zoning:
CR INTRIG: PRID=<trigger-ID>, SKEY=<service>, ... ,CHGINF=ZONE355;
The value for <trigger-ID> must be identical in commands CR INTRIG and CR CPT.
If the call charge data are recorded in the SSP, tariffs must be entered for all zones used
(before the zone points are created):
ENTR TAR: NAME=IN1, PLSCOM=110000;
ENTR TARSW: ZONO=468, NAME=IN1, TIME=1400, DATE=991215;
If the call charge data are not recorded in the SSP, the relevant zone must be passed
through to the exchange in question. The charge band message is used for this:
MOD ZOINF: ZONO=345, CHBNO=145;

A30808-X3003-X458-2-7619

IN 87

OMN:SSS-TA

Operation Charging

Case 2: Identification via the zone points

This is a special case for the use of the intelligent network. The code points are created
without the IN trigger; routing is based on the dialed digits. The SCP is only activated in
order to determine the valid zone. To this end, the reference to the trigger profile is
created in the zone point (ZOCHA=ZONEXT). The call is then zoned according to the
zone supplied by the SCP (see Fig. 1.31).
Creating the trigger profile:
CR INTRIG: PRID=INTCALL, SKEY=37, ... ;
Creating the zone point for charge registration in a lower-level exchange:
CR ZOPT: CODE=00, ZOCHA=ZONEXTINTCALL;
The value for ZOCHA in the command CR ZOPT must be identical with the value for
PRID in the command CR INTRIG.
Activating the trigger profile:
ACT INTRIG: PRID=INTCALL;
This special case is used for the zoning of international calls. It is exclusively an IN
service, since there is no service user. Because of this, no IN-specific AMAdata records
need to be created. The calling subscriber pays for the complete connection from A to B.

1.4.11

Reverse Charging
The reverse charging service (RCS) allows the calling party to set up a call to a called
party who accepts the charges for the call. The called party is obliged to accept the call.
The call is set up without the assistance of an operator.
It is possible to restrict the use of the reverse charging service to certain line types, for
instance coinbox lines. This reduces overuse of the service by individuals experimenting
with it.

IN 88

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Configuration
LTGC (RCS)

DIU0
OUT
RCS loop

SN
A

DIU1
INC
AN3

DIU2
AC

AN1
AN2

announcement control
DIU3
PB

AN5
AN4
physical connection
software connection
logical connection

Fig. 1.32 RCS configuration

Key to abbreviations:
OUT ... outgoing DIU
INC ... incoming DIU (incl. AN3)
AC ... announcement control (AN1 and AN2)
PB ... input control (AN5)
AN1 ... announcement for calling party
AN2 ... announcement for called party
AN3 ... announcement that all lines are busy (for calling and called parties)
AN4 ... announcement that the call has been refused (for calling party)
AN5 ... announcement that the call has been accepted by digit input (for called party)
Announcement AN5 is only needed if digit input is required to accept the call.
Access
The service is accessed by dialing the access code as a prefix to the actual called party
number, e.g.:
8XX ZX... NX...

A30808-X3003-X458-2-7619

IN 89

OMN:SSS-TA

Operation Charging

where
8XX is the service access code
ZX ... is the LACof the called party
NX ... is the called party's directory number.
Procedure
The calling party dials 8XX ZX... NX... and is asked to wait for the tone and then
speak his/her name (AN1).
The called party is asked to listen to the name (AN2).
If the RCS exchange is unable to find a free announcement, both parties receive the
announcement that they should wait for a line.
If the called party accepts the call, either by waiting for a defined time or by dialing
a digit (project-specific, AN5), the connection is switched through.
If the called party refuses the call (by going on-hook), the calling party receives the
announcement that the call request has been rejected (AN4).
Charge registration
Charges for RCS calls are registered by means of AMA. Charge registration starts when
the called party accepts the call. The called party is marked in the AMA ticket as the
paying party.
It is also possible for tickets to be generated for calls that are not accepted and for
unsuccessful call attempts.
The RCS exchange only registers charges for the connection from A to B. Facility usage
charges for supplementary services such as abbreviated dialing must be registered at
the originating exchange.

1.5

Notes on the Iridium Project

The OMN:SSS is basically designed for use in the SSS network nodes of a GSM-PLMN.
The satellite-supported mobile communications system Iridium uses Siemens SSS
technology as the gateway switching center (GSC) to the terrestrial networks. In GSM
terminology, the entire Iridium network is classed as a single "PLMN". This network does
not make any distinction between a CSC (combined switching center) and a mobile
(PLMN)-typical network node (MSC, VLR, etc.). Wired subscribers and PBXs are
connected instead to the MSC. The base station system (BSC and BTS) is replaced by
a combination of ETC (earth terminal controller) and satellites. For technical reasons,
not all of the GSM features described can be implemented. As for all projects, only the
features specifically agreed upon in the contract are actually supplied.

IN 90

A30808-X3003-X458-2-7619

Operation Charging

OMN:SSS-TA

Task List (TL)

i

2.1
Create

Display commands are only specified in the procedures when they are absolutely necessary. Generally,
display commands are not necessary for confirming the execution of a command. It can already be seen
from the command acknowledgement output by the system whether the command entered was correctly
executed (see Operator Guidelines OGL). If it should be necessary for administrative reasons to receive
an acknowledgement of the executed tasks in addition to the run listing, the contents of the database
can be displayed, for example, before and after or only after each task using the appropriate commands
(see CML).
Each task contains only the parameters or identifiers characteristic for that particular task.

Selection of Charging Type

PSTN charging of transit calls
GCOS=PSTNTGRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR TGDAT

2.2

PLMN Charging

2.2.1

Holiday and Weekday Category Administration

Display
Display
Display
Create
Create
Modify
Cancel
Cancel
Modify

2.2.2
Display
Display
Activate
Activate
Activate
Activate
Activate
Create
Activate
Activate

fixed holiday table (YEAR=X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

variable holiday table (YEAR=xxxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
weekday category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
fixed holidays in a new holiday table (YEAR=X) . . . . . . . . . . . . . . . . . .
variable holidays in a new holiday table (YEAR=xxxx). . . . . . . . . . . . . .
weekday category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
fixed holiday table (YEAR=X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
variable holiday table (YEAR=xxxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
of existing fixed or variable holiday tables
(add or remove holidays) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DISP HOLICAL
DISP HOLICAL
DISP WDCAT
CR HOLICAL
CR HOLICAL
MOD WDCAT
CAN HOLICAL
CAN HOLICAL
MOD HOLICAL

Automatic Message Accounting Administration

current filling level of MCR file
(ALL=Y, FILE=IA.ICMCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCR file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
collection of billing data for interrogation
(FEAT=CHINTREC, STAT=ACT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
collection of billing data for transit calls
(FEAT=CHTRANS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
collection of billing data for unsuccessful call attempts
(FEAT=CALLATT, STAT=ACT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
cell dependent charging
(FEAT=CELLDCH, STAT=ACT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
feature FLAM compression for billing files
(FEAT=FLAMCOMP, STAT=ACT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FLAM compression of billing files

DISP FILE
DISP MCR
MOD MSERVOPT
MOD MSERVOPT
MOD MSERVOPT
MOD MSERVOPT
MOD MSERVOPT

TS-305
collection of billing data for non-chargeable call attempts
(FEAT=CHFCATT, STAT=ACT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-300
feature immediate printout of billing files
(TYPE=MCRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACT IAFEAT

A30808-X3003-X458-1-7619

TL 1

OMN:SSS-TA

Deactivate
Cancel
Copy
Copy
Copy

Operation Charging

FLAM compression of billing file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

allocation of FLAM compression to a file. . . . . . . . . . . . . . . . . . . . . . . .
MCR file to a remote processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCR file from magnetic disk to tape . . . . . . . . . . . . . . . . . . . . . . . . . . .
a specific MCR file from magnetic disk to tape . . . . . . . . . . . . . . . . . . .

2.2.3

Administration of Zones and Tariffs

2.2.3.1

Administration of Zones and Tariffs for Mobile Originating Calls,

Call Attempts, Call Forwarding

Display
Display
Display
Display
Display
Create

mobile-specific tariffs (parameter sets) . . . . . . . . . . . . . . . . . . . . . . . . .

mobile-specific tariff categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
switchover times for tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
mobile-specific zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
mobile-specific zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zoning for mobile originating calls,
call attempts, call forwarding (zoning in the own MSC). . . . . . . . . . . . .
mobile-specific tariffs (parameter sets) . . . . . . . . . . . . . . . . . . . . . . . . .
mobile-specific tariff categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
switchover times for mobile-specific tariffs . . . . . . . . . . . . . . . . . . . . . .
mobile-specific zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
tariff categories to call/transmission type. . . . . . . . . . . . . . . . . . . . . . . .
mobile-specific zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
mobile-specific tariffs (parameter sets) . . . . . . . . . . . . . . . . . . . . . . . . .
switchover times within a tariff category . . . . . . . . . . . . . . . . . . . . . . . .
allocation of mobile-specific tariffs to a tariff category . . . . . . . . . . . . . .
mobile-specific zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
allocation of tariff categories to call/transmission type . . . . . . . . . . . . .
mobile-specific zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zoning for mobile originating calls, call attempts, call forwarding . . . . .
mobile-specific tariffs (parameter sets) . . . . . . . . . . . . . . . . . . . . . . . . .
mobile-specific tariff categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
allocation of tariff categories to call types . . . . . . . . . . . . . . . . . . . . . . .
mobile-specific zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
mobile-specific zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Enter
Create
Enter
Create
Assign
Create
Modify
Modify
Modify
Modify
Modify
Modify
Cancel
Cancel
Cancel
Cancel
Cancel
Cancel
2.2.3.2

PLMN tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PLMN tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PLMN tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PLMN tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

systemfeature Billing for IN

(TYPE=INA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
code point for IN service triggering
(ZOCHA=ZONINHI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
standard charge registration for IN services . . . . . . . . . . . . . . . . . . . . .
acceptance of zone from charge band message
(TKZOINF=YES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Create
Create
Create

DISP PLMNTAR
ENTR PLMNTAR
MOD PLMNTAR
CAN PLMNTAR

ACT IAFEAT
CR MZOPT
CR INTRIG
CR MZOPT

Administration of Control Meters for Connection Groups

Meter saving
Display

TL 2

TS-600
ENTR MTAR
TS-601
TS-601
TS-602
TS-602
TS-603
MOD MTAR
MOD MTARCAT
MOD MTARCAT
TS-604
TS-604
MOD MZOPT
TS-605
TS-606
TS-607
TS-608
TS-608
CAN MZOPT

Charge Registration in the Intelligent Network (IN)

Activate

2.2.5

DISP MTAR
DISP MTARCAT
DISP MTARCAT
DISP MZONE
DISP MZOPT

Administration of Tariffs for Mobile Terminating Calls (PLMN Tariffs)

Display
Enter
Modify
Cancel

2.2.4

DACT FILEFEAT
TS-307
TS-302
TP-301
TP-302

meter save time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP METSAV

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Enter
Modify
Save

meter save time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR METSAV

meter save time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-721
charges to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAVE MET

Call charge data

Display
Display
Enter
Copy
Copy

meter administration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

call charge data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
meter administration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
statistics meter files to magnetic tape. . . . . . . . . . . . . . . . . . . . . . . . . . .
trunk group control meter files to magnetic tape . . . . . . . . . . . . . . . . . .

2.2.6

Administration of Statistics Meter

Statistics meter
Display
Display
Activate
Cancel

DISP METADM
DISP MET
ENTR METADM
TS-732
TS-733

statistics meter group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

statistics meter call duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
statistics meter call duration
(using: ALTNSD=DURATCUM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
statistics meter call duration
(using: ALTNSD=DURATCUM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Statistics meter switching times

Display
statistics meter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
assignment of statistics meters to objects . . . . . . . . . . . . . . . . . . . . . . .
Display
trunk group control meter readings. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
switching time for statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter
switching time for statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify
switching time for statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancel
switching time for statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DISP STMETGRP
DISP CDTDAT
ENTR CDTDAT
CAN CDTDAT
DISP STATMET
DISP STATMET
DISP TRMET
DISP STATSW
ENTR STATSW
TP-824
CAN STATSW

2.3

Interadministration Revenue Accounting (IARA) Administration

2.3.1

IARSTAT Destination and IARSTAT Origin Name Administration

IARAMA
Activate
Copy

systemfeature IARAMA
TYPE=IARA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACT IAFEAT
IARAMA file from disk to tape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-550

IARSTAT Destination and IARSTAT Origin Name Administration

Display
the assignment of incoming or bothway trunk groups
to the IARSTAT origin name(s) (TGNO). . . . . . . . . . . . . . . . . . . . . . . . .
Display
the assignment of destinations/routes
to the IARSTAT origin name(s) (DEST, RTNO) . . . . . . . . . . . . . . . . . .
Display
IARSTAT destination names or IARSTAT origin names assigned
to a measurement type (MTYPE, DNAME or ONAME) . . . . . . . . . . . . .
Display
the status of IARSTAT destination names or IARSTAT origin names
(MTYPE, DNAME or ONAME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
the number of used and free IARSTAT destination names and
IARSTAT origin names of a measurement type (only MTYPE) . . . . . . .
Assign
a destination/route or a destination/trunk group
to a new or to an already existing IARSTAT destination name . . . . . . .
Assign
an incoming or bothway trunk group to a new or to an
already existing IARSTAT origin name. . . . . . . . . . . . . . . . . . . . . . . . . .
Modify
the assignment of an IARSTAT destination name to
a destination/route or destination/trunk group . . . . . . . . . . . . . . . . . . . .
Modify
the assignment of an IARSTAT origin name to an outgoing or

A30808-X3003-X458-1-7619

DISP IARNAME
DISP IARNAME
DISP IARDAT
DISP IARDAT
DISP IARDAT
TS-500
TS-501
TS-502

TL 3

OMN:SSS-TA

Modify
Cancel
Cancel
Cancel
Cancel

Operation Charging

bothway trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IARA destination or origin name
(IARA matrix points are modified/canceled automatically) . . . . . . . . . .
assignment of a destination/route for IARSTAT destination names
or outgoing/bothway trunk group for IARSTAT origin names . . . . . . . .
relating to a route:
all assignments for the IARA destination names . . . . . . . . . . . . . . . . . .
relating to an outgoing or bothway trunk group:
all assignments for IARSTAT destination names . . . . . . . . . . . . . . . . .
relating to an incoming or bothway trunk group:
all assignments for the IARSTAT origin names. . . . . . . . . . . . . . . . . . .

IARSTAT Matrix Point Administration

Display
number of created and free IARAS matrix points of one
measurement type (only parameter MTYPE) . . . . . . . . . . . . . . . . . . . .
Display
total number of used and free IARSTAT counters for all
measurement types (MTYPE = any mtype). . . . . . . . . . . . . . . . . . . . . .
Display
assignment of the connection types to the IARAcounters of the
IARSTAT matrix point (parameter DNAME and/or ONAME). . . . . . . . .
Display
assignment of an IARSTAT tariff zone to one or more
IARA matrix points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create
IARA matrix point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assign
IARA matrix point to one or more IARSTAT tariff zones . . . . . . . . . . . .
Modify
IARA matrix point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify
IARSTAT tarif zone for one or more IARA matrix points . . . . . . . . . . . .
Deactivate
generation of AMA data records while maintaining
registration in counters (CNTRS=NO, TICKET=YES). . . . . . . . . . . . . .
Deactivate
registration in counters while maintaining generation of
AMA data records (CNTRS=YES, TICKET=NO) . . . . . . . . . . . . . . . . .
Cancel
IARSTAT matrix point
including assignment to IARSTAT tariff zone . . . . . . . . . . . . . . . . . . . .
Cancel
assignment of IARSTAT tariff zone to one or more
IARSTAT matrix points (evening and night counters are no
longer used). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TS-502
MOD IARDAT
TP-503
TS-504
TS-506
TP-503

DISP IARMPT
DISP IARMPT
DISP IARMPT
DISP IARZONE
TS-510
TS-511
TS-512
TS-513
CAN IARMPT
CAN IARMPT
CAN IARMPT

CAN IARZONE

IARSTAT Registration Job Administration

Display
IARSTAT jobs and the relevant file names . . . . . . . . . . . . . . . . . . . . . . DISP IARJOB
Create
IARSTAT registration job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-523
Cancel
IARSTAT registration job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-524
Administration of IARSTAT connection groups
Display
all names of connection groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
assignment of connection types and/or
transmission rates to connection group names . . . . . . . . . . . . . . . . . . .
Create
IARSTAT connection groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify
assignment of connection types and/or
transmission rates to connection group names . . . . . . . . . . . . . . . . . . .
Cancel
IARSTAT connection groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TS-531
TS-532

IARSTAT Tariff Switching Times Administration

Display
IARSTAT tariff switching times for IARSTAT tariff zones . . . . . . . . . . .
Create
IARSTAT tariff switching times for an IARSTAT tariff zone. . . . . . . . . .
Modify
IARSTAT tariff switching times for an IARSTAT tariff zone. . . . . . . . . .
Cancel
IARSTAT tariff switching times for an IARSTAT tariff zone. . . . . . . . . .

DISP IARTMPD
CR IARTMPD
MOD IARTMPD
CAN IARTMPD

DISP IARGRP
DISP IARCON
TS-530

IARSTAT Save Times Administration

Display
IARSTAT save time for continuous registration job. . . . . . . . . . . . . . . . DISP IARSAVDA
Enter
IARSTAT save time for continuous registration job. . . . . . . . . . . . . . . . TP-530

TL 4

A30808-X3003-X458-1-7619

Operation Charging

Modify
Cancel

OMN:SSS-TA

IARSTAT save time for continuous registration job . . . . . . . . . . . . . . . . TP-530

IARSTAT save time for continuous registration job . . . . . . . . . . . . . . . . CAN IARSAVDA

IARSTAT Data Administration

Display
IARSTAT measurement results not yet stored in a post-processing
file (MTYPE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
IARSTAT measurement results stored in a post-processing
file (FILE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
status of the IARSTAT file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Save
IARSTAT counters to a post-processing file intermediately . . . . . . . . . .

DISP IARSTAT
DISP IARSTAT
DISP IARFILE
COPY IARACCT

IARSTAT Post Processing File Administration

Display
IARSTAT post-processing files stored on magnetic disk (FILE=IR.) . . . DISP FILE
Display
IARSTAT post-processing files still in use by an IARSTAT
registration job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARJOB
Copy
IARSTAT post-processing file to magnetic tape. . . . . . . . . . . . . . . . . . . TP-550

2.4

Charging of Wired Subscribers of a Combined

Switching Center (CSC)

2.4.1

Subscriber Tariffs

Tariffs
Display
Enter
Enter
Enter
Modify
Cancel
Cancel
Cancel

tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
tariffs for access charges with single pulse metering (SPM) or
multiple pulse metering (MPM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
tariffs for communication charges with periodic pulse metering (PPM)
or periodic multiple pulse metering (PMM) . . . . . . . . . . . . . . . . . . . . . . .
tariff sequences in pulse format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
tariff (once, not periodically) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
tariff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
tariff names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
tariff zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Tariff switchover times

Display
tariff switchover times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter
tariff switchover time for a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify
tariff switchover times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancel
tariff switchover times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.2
Display
Create
Create
Create
Split
Split
Split
Split
Split

DISP TAR
TP-701
TP-702
TP-703
TP-704
TP-705
TP-706
TP-707
DISP TARSW
TP-720
TP-721
TP-722

Zone Points
zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point for a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point with zone characteristic
using: CODE, ZOCHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point for an announcement
using: CODE, INCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point after digit
using: DIGIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point after originating mark
using: ORIG2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point after category
using: MFCAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point after language digit
using: ZDIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point after freephone indicator

A30808-X3003-X458-1-7619

DISP ZOPT
TP-761
CR ZOPT
CR ZOPT
SPLIT ZOPT
SPLIT ZOPT
SPLIT ZOPT
SPLIT ZOPT

TL 5

OMN:SSS-TA

Modify
Merge
Create
Modify
Cancel

2.4.3

Operation Charging

using: FPH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone points for directory number ranges belonging to the
local network of a foreign-exchange subscriber . . . . . . . . . . . . . . . . . .
zone points for directory number ranges belonging to the
local network of a foreign-exchange subscriber . . . . . . . . . . . . . . . . . .
zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SPLIT ZOPT
MOD ZOPT
TP-767
TP-769
TP-770
CAN ZOPT

Charge Band Messages and Zone Traffic Types

Charge Band Messages

Display
assignment of charge band message to zones
using: CHBNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter
assignment of charge band message to zones
using: ZONO, CHBNO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify
assignment of charge band message to zones
using: ZONO, CHBNO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancel
assignment of charge band message to zones
using: ZONO, CHBNO = 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Allow
acceptance of charge band message from zones
using: TKZOINF = YES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DISP ZOINF
MOD ZOINF
MOD ZOINF
MOD ZOINF
MOD ZOPT

Zone traffic types

Display
assignment of zone traffic type to zones
using: ZONO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOINF
Modify
assignment of zone traffic type to zones
using: ZONO, ZOTRAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOINF

2.4.4

Subscriber Facilities

Registration of facility input charges

Display
charge registration for facility input . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create
charge registration by AMA for facility input by subscriber
using: BILLING = AMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create
charge registration by meter pulses for facility input by subscriber
using: BILLING = METERING, METPULS . . . . . . . . . . . . . . . . . . . . . .
Create
charge registration by AMA for facility input by operator
using: FAIOPER = AMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify
charge registration for facility input . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancel
charge registration for facility input . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter
counters for facility input charges
using: FAICNTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Registration of facility usage charges
Display
charge registration for facility usage . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create
charge registration by AMA for facility usage
using: BILLING = AMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create
charge registration by meter pulses for facility usage
using: BILLING = METERING, METPULS . . . . . . . . . . . . . . . . . . . . . .
Modify
charge registration for facility usage . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancel
charge registration for facility usage . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter
counters for facility usage charges
using: FAUCNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DISP FAICHA
CR FAICHA
CR FAICHA
CR FAICHA
MOD FAICHA
CAN FAICHA
ENTR CDTDAT
DISP FAUCHA
CR FAUCHA
CR FAUCHA
MOD FAUCHA
CAN FAUCHA
ENTR CDTDAT

Account suspension orders

Activate
systemfeature for account suspension order
using: TYPE = FIR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACT IAFEAT

TL 6

A30808-X3003-X458-1-7619

Operation Charging

Display
Create

recording of account suspension order . . . . . . . . . . . . . . . . . . . . . . . . .

recording of account suspension order (activate)
using: FAIOPER = FIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
recording of account suspension order (activate/deactivate) . . . . . . . . .
recording of account suspension order (deactivate). . . . . . . . . . . . . . . .
of account suspension order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
cyclic disk file
using: FILE = IA.ICFIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Modify
Cancel
Display
Copy

2.4.5

Regenerate
Charge data
Activate
Display
Enter
Deactivate

2.4.6

meter saving times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

meter saving time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
meter saving time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
charge meters to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
charge meters to APS change file (prior to APS change)
using: FUNC = APSCHANG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
charge meters (after an APS change) . . . . . . . . . . . . . . . . . . . . . . . . . .
meter type
using: MET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
meter administration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
meter administration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
charge meter blocking (after regeneration)
using: FUNC = FALLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
subscriber charge files to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
subscriber charge files to host processor . . . . . . . . . . . . . . . . . . . . . . . .

CR FAICHA
MOD FAICHA
CAN FAICHA
TS-840
TRANS FILE

DISP METSAV
ENTR METSAV
TS-721
SAVE MET
EDIT MET
REG MET

ENTR EXDDAT
DISP METADM
ENTR METADM
SAVE MET
TS-731
TP-811

Subscriber Meters

Administration of meters for call charges and number of calls

Display
subscriber meters
using: TYPE = METSUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter
meters for call charges
using: SUCHCNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify
meters for call charges
using: SUCHCNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancel
meters for call charges
using: SUCHCNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter
meters for number of calls
using: SUCACNTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify
meters for number of calls
using: SUCACNTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancel
meters for number of calls
using: SUCACNTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.7

DISP FAICHA

Meter Administration

Meter saving
Display
Enter
Modify
Save
Save

Copy
Copy

OMN:SSS-TA

DISP MET
MOD ZOPT
MOD ZOPT
MOD ZOPT
MOD ZOPT
MOD ZOPT
MOD ZOPT

Statistics Meters

Administration of statistics meters

Overview
of commands required for statistics meter administration . . . . . . . . . . .
Enter
statistics meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
statistics meter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
assignment of statistics meters to objects
using: DESC = YES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
recording of call duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A30808-X3003-X458-1-7619

TP-820
TS-740
DISP STATMET
DISP STATMET
DISP CDTDAT

TL 7

OMN:SSS-TA

Assign
Display
Display
Activate
Cancel
Copy
Cancel

Operation Charging

statistics meter groups to directory numbers. . . . . . . . . . . . . . . . . . . . .

statistics meter groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
assignment of statistics meter groups to directory numbers . . . . . . . . .
recording of call duration
using: EXTNSD = CALLDUR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
recording of call duration
using: EXTNSD = CALLDUR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
statistics meter file to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MOD DN
DISP STMETGRP
DISP STMETLNK
ENTR CDTDAT
CAN CDTDAT
TS-732
TS-741

Administration of statistics meter switchover times

Enter
statistics meter switchover time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-822
Modify
statistics meter switchover time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-824
Cancel
statistics meter switchover time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN STATSW

2.4.8
Activate
Activate
Copy
Display

2.4.9

Trunk Meters
trunk metering (incoming)
using: GCOS = TRMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
trunk metering (bothway, outgoing) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
trunk meter files to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
trunk meter readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ENTR TGDAT
TP-830
TS-733
DISP TRMET

Automatic Message Accounting

AMA data and DEB data

Overview
of commands required for AMA administration . . . . . . . . . . . . . . . . . . .
Overview
of commands required for DEB administration . . . . . . . . . . . . . . . . . . .
Display
current occupancy level of AMA file
using: FILE = IA.ICAMA, ALL = YES. . . . . . . . . . . . . . . . . . . . . . . . . . .
Copy
AMA file from disk to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copy
AMA file from disk to host processor . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display
recordings of additional/alternative call data . . . . . . . . . . . . . . . . . . . .
Activate
recordings of additional/alternative call data
using: EXTNSD/ALTNSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter
recordings of call data for AMA and DEB
using: MARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deactivate
recordings of additional/alternative call data
using: EXTNSD/ALTNSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cancel
recordings of call data for AMA and DEB
using: MARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TP-900
TP-905
DISP FILE
TS-731
TP-934
DISP CDTDAT
ENTR CDTDAT
ENTR CDTDAT
CAN CDTDAT
CAN CDTDAT

MOB data and PMOB data

Overview
of commands required for MOB administration . . . . . . . . . . . . . . . . . . . TP-910
Overview
of commands required for PMOB administration. . . . . . . . . . . . . . . . . . TP-915

2.4.10 Charge Registration in the IN

Activate
Enter
Cancel
Create
Create
Create
Record

TL 8

system feature
using: TYPE = INA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
call data processing for AMA records . . . . . . . . . . . . . . . . . . . . . . . . . .
call data processing for AMA records . . . . . . . . . . . . . . . . . . . . . . . . . .
code point for IN service triggering
using: ZOCHA = ZONINHI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point for IN service triggering
using: ZOCHA = ZONEXT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
standard charge registration for IN services . . . . . . . . . . . . . . . . . . . . .
charge band message in IN record . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACT IAFEAT
ENTR CDTDAT
CAN CDTDAT
CR ZOPT
CR ZOPT
CR INTRIG
MOD ZOINF

A30808-X3003-X458-1-7619

Operation Charging

Allow

OMN:SSS-TA

acceptance of zone from charge band message

using: TKZOINF = YES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR ZOPT

2.4.11 Reverse Charging Service

Create
Create
Enter
Enter
Enter
Create

reverse charging service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

charge registration with AMA
using: GCOS = AMAREQD & NOZON. . . . . . . . . . . . . . . . . . . . . . . . . .
charge registration for refused calls
using: GCOS = PROP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AMA ticket (called number) without RCS access code
using: GCOS = PROP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
charge registration for unsuccessful call attempts
using: MARKS = UCALLAMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zone point
using: ZOCHA = NOPULSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TC-303
CR TGRP
ENTR TGDAT
ENTR TGDAT
ENTR CDTDAT
CR ZOPT

2.4.12 Subscriber's Private Meter

Private meter for analog subscriber
Activate
private meter
using: LAC, DN, LNATT = SMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD SUB
Deactivate
private meter
using: LAC, DN, CLNATT = SMET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD SUB
Private meter for ISDN subscriber
Activate
private meter (in 3rd path, SERV)
during call, for all calls
using: LAC, DN, CHRG = CHACONTP,
COS = AOCSTI or AOCFCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD SUB
Deactivate
private meter (in 3rd path, SERV)
using: LAC, DN, CCHRG = CHACONTP,
CCOS = AOCSTI or AOCFCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD SUB

A30808-X3003-X458-1-7619

TL 9

OMN:SSS-TA

TL 10

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Task Summary Lists (TS)

A30808-X3003-X458-1-7619

TS 1

OMN:SSS-TA

TS 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

TS-300

OMN:SSS-TA

Activate collection of billing data for non-chargeable call attempts

Check whether the collection of billing data for unsuccessful call attempts
has been activated.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP MSERVOPT
(FEAT=CALLATT)

Activate the collection of billing data for unsuccessful

call attempts (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MSERVOPT
(FEAT=CALLATT, STAT=ACT)

Activate the collection of billing data for non-chargeable

call attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MSERVOPT
(FEAT=CHFCATT, STAT=ACT)

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-300 1

OMN:SSS-TA

TS-302

Operation Charging

Transfer the IA.ICMCR file to remote processor for data post-processing

Copy the current buffer contents to file IA.ICMCR. . . . . . . . . . . . . . . . . . . . . . . . . . . TRANS BUFFER

using: TYPE=MCR

Assign a service process to file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SET FGRPATT

Transfer file IA.ICMCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRANS FILE

using: FILE=IA.ICMCR or FILE=<new name>/IA.ICMCR,
PRONAM=<name of remote processor>

Check whether the number of copies made equals the

number of copies required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILE
using: FILE=IA.ICMCR, ALL=Y
Step 5 may not be carried out until the number of copies required
has been reached.

Save MCR file to tape (if required). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-301

Cancel cyclic file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REL CYCFILE

using: FILE=IA.ICMCR

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-302 1

A30808-X3003-X458-1-7619

Operation Charging

TS-305

OMN:SSS-TA

Creation of FLAM compression of IA.ICMCR file

The sequence is also valid for the cyclic files IA.ICINA and IA.ICAMA. Insert the valid file name for each case.
1

Creation of file IA.ICMCR

wih FILE=IA.ICMCR, FEAT=FLAMCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR FILEFEAT

Activation of FLAM compression

FILE=IA.ICMCR, FEAT=FLAMCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACT FILEFEAT

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-305 1

OMN:SSS-TA

TS-307

Operation Charging

Cancel allocation FLAM compressio to IA.ICMCR file

The sequence is also valid for the cyclic files IA.ICINA and IA.ICAMA. Insert the valid file name foe each case.
1

Check wether for file IA.ICMCR FLAM compression is still activ

(FILE=IA.ICMCR, FEAT=FLAMCOMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILEFEAT

Deactivation of FLAM compression for IA.ICMCR file

(FILE=IA.ICMCR, FEAT=FLAMCOMP) (if required) . . . . . . . . . . . . . . . . . . . . . . . . . DACT FILEFEAT

Cancel of FLAM compression for IA.ICMCR

(FILE=IA.ICMCR, FEAT=FLAMCOMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN FILEFEAT

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-307 1

A30808-X3003-X458-1-7619

Operation Charging

TS-500

OMN:SSS-TA

Assign IARA destination name

1a

Check whether the destination has been created with the corresponding route
or trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP ROUTE
using: DEST

1b

Check whether the AREACODE has been created (only for wired subscriber) . . . . . DISP AREACODE

2a

Create route (if required). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMN:SSS-RO

2b

Create trunk group (if required). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMN:SSS-RO

2c

Create the AREACODE (only for wired subscriber) (if required) . . . . . . . . . . . . . . . . OMN:SU:MSC

3a

Assign destination and route to an IARSTAT name . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR IARNAME

using: DEST, RTNO, NAME

3b

Assign destination and trunk group to an IARSTAT name . . . . . . . . . . . . . . . . . . . . . ENTR IARNAME

using: DEST, TGNO, NAME

3c

Assign destination and subscriber to an IARA name

(only for wired subscriber). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR IARNAME
using: LAC, DIR=DEST, NAME

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-500 1

OMN:SSS-TA

TS-501

Operation Charging

Assign IARA origin name

1a

Check whether the outgoing or bothway trunk group

has been created . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP TGRP

1b

Check whether the AREACODE has been created (only for wired subscriber). . . . . DISP AREACODE

2a

Create an incoming or bothway trunk group (if required). . . . . . . . . . . . . . . . . . . . . . OMN:SSSRO

2b

Create the AREACODE (only for wired subscriber) (if required) . . . . . . . . . . . . . . . . OMN:SU:MSC

3a

Assign a trunk group to an IARSTAT name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR IARNAME

using: TGNO, NAME

3b

Assign destination and subscriber to an IARA name

(only for wired subscriber) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARNAME
using: LAC, DIR=ORIG, NAME

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-501 1

A30808-X3003-X458-1-7619

Operation Charging

TS-502

OMN:SSS-TA

Modify the assignment of an IARSTAT destination name to a destination or

route or of an IARSTAT origin name to a trunk group

Check whether IARSTAT matrix points have been created for

this IARSTAT name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARZONE
for destination names: using DNAME
for origin names: using ONAME

Cancel IARSTAT matrix points (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN IARMPT

Modify assignment of an IARSTAT name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-501

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-502 1

OMN:SSS-TA

TS-504

Operation Charging

Relating to a route:
Cancel all assignments for the IARSTAT destination names

Relating to one IARSTAT measurement type, a route can be assigned

only for one IARSTAT destination name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP DEST

Cancel all assignments for the IARSTAT destination names . . . . . . . . . . . . . . . . . . TP-503

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-504 1

A30808-X3003-X458-1-7619

Operation Charging

TS-505

OMN:SSS-TA

Relating to a destination:
Cancel all assignments for the IARSTAT destination names

Display all routes for the destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP ROUTE

using: DEST

Cancel IARSTAT name assignment for all routes to that destination . . . . . . . . . . . . . TP-503

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-505 1

OMN:SSS-TA

TS-506

Operation Charging

Relating to an outgoing/bothway trunk group:

Cancel all assignments for the IARSTAT destination names

Display all routes allocated to the trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP ROUTE

using: TGNO

Cancel IARSTAT name assignment using that trunk group . . . . . . . . . . . . . . . . . . . TP-503

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-506 1

A30808-X3003-X458-1-7619

Operation Charging

TS-510

OMN:SSS-TA

Create IARSTAT matrix point

Check whether the IARSTAT destination name is active . . . . . . . . . . . . . . . . . . . . . . DISP IARDAT

using: DNAME

Create an IARSTAT destination name (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . TS-500

Check whether the IARSTAT origin name is active . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARDAT

using: ONAME

Create an IARSTAT origin name (if required). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-501

Check whether the matrix point is inactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARMPT

using: DNAME, ONAME
Note: A matrix point canceled during an activated registration job will
remain in the inactive status as long as the data are not stored in a postprocessing file. It cannot be created again during this time.

Save IARSTAT postprocessing file (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . COPY IARACCT

Create IARSTAT matrix point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR IARMPT

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-510 1

OMN:SSS-TA

TS-511

Operation Charging

Assign IARSTAT matrix points to an IARSTAT tariff zone

Check whether a matrix point is created and active . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARMPT

Create an IARSTAT matrix point (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-510

Assign an IARSTAT matrix point to an IARSTAT tariff zone . . . . . . . . . . . . . . . . . . . TP-511

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-511 1

A30808-X3003-X458-1-7619

Operation Charging

TS-512

OMN:SSS-TA

Modify IARSTAT matrix point

Cancel IARSTAT matrix point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN IARMPT

Check whether an IARSTAT registration job still exists . . . . . . . . . . . . . . . . . . . . . . . DISP IARJOB

An IARSTAT matrix point canceled during an activated registration job will
remain in the inactive status as long as the current IARSTAT registration
call data are not stored in a postprocessing file.

Copy the current call data into a postprocessing file (if required) . . . . . . . . . . . . . . . . COPY IARACCT
The current call data can be copied once into a post processing file
after safeguarding, which occurs every hour on the hour.

Create the new IARSTAT matrix point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS510

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-512 1

OMN:SSS-TA

TS-513

Operation Charging

Modify IARSTAT tariff zone for IARSTAT matrix points

Check whether the IARSTAT matrix point has already been created . . . . . . . . . . . . DISP IARMPT

Create an IARSTAT matrix point (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-510

Modify the IARSTAT tariff zone for IARSTAT matrix points. . . . . . . . . . . . . . . . . . . . TP-513

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-513 1

A30808-X3003-X458-1-7619

Operation Charging

TS-530

OMN:SSS-TA

Create IARSTAT connection group

Note: As soon as the MML command CR IARGRP is entered for an APS, all predefined connection groups are
overwritten.
1

Create name of the connection group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR IARGRP

Enter assignment of connection types and/or transmission rates

to connection-group name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR IARCON

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-530 1

OMN:SSS-TA

TS-531

Operation Charging

Modify IARSTAT connection group

Cancel old assignment of connection types and/or transmission

rates to connection-group name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN IARCON

Enter new assignment of connection types and/or transmission

rates to connection-group name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR IARCON

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-531 1

A30808-X3003-X458-1-7619

Operation Charging

TS-532

OMN:SSS-TA

Cancel IARSTAT connection group

Cancel old assignment of connection types and/or transmission

rates to connection-group name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN IARCON

Check whether another active matrix point is using the connection group
using: CNTRS=ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARMPT
This command must be entered for each of the 4 types of measurement.

Cancel active matrix points (if required). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN IARMPT

Cancel name of connection group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN IARGRP

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-532 1

OMN:SSS-TA

TS-600

Operation Charging

Create zoning for mobile originating calls, call forwarding,

call attempt (zoning in home MSC)

Create tariff categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-601

Assign tariff categories to one or more connection types . . . . . . . . . . . . . . . . . . . . . CR MZONE

Create zone points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-603

The individual steps must be carried out until all objects required have been created or assigned.

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-600 1

A30808-X3003-X458-1-7619

Operation Charging

TS-601

OMN:SSS-TA

Create tariff category

Check whether holiday calendar has been created . . . . . . . . . . . . . . . . . . . . . . . . . . DISP HOLICAL

Create holiday calendar (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR HOLICAL

Check whether all tariffs required have been created. . . . . . . . . . . . . . . . . . . . . . . . . DISP MTAR

Enter missing tariffs (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR MTAR

Create tariff category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR MTARCAT

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-601 1

OMN:SSS-TA

TS-602

Operation Charging

Create mobile-specific zone

Check whether all tariff categories required have been created . . . . . . . . . . . . . . . . DISP MTARCAT

Create missing tariff categories (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-601

Create zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR MZONE

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-602 1

A30808-X3003-X458-1-7619

Operation Charging

TS-603

OMN:SSS-TA

Create mobile-specific zone points

Check whether zone points are already created for a part of the
digit combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP MZOPT
DISP ZOPT
The code (digit combination and code type) for which a new zone point is to be
created may not begin with one or more digits for which a zone point already exists.
Example: A zone point for CODE=0049 cannot be created if
- a zone point (MZOPT) already exists for CODE=4-INAT or
- a zone point (MZOPT) already exists for CODE=49-INAT or
- a zone point (MZOPT) already exists for CODE=491-INAT or
- a zone point (ZOPT) already exists for CODE=004 or (*)
- a zone point (ZOPT) already exists for CODE=0049 (*).
( (*) This assumes the international prefix is 00).
Any such zone points that already existing must be canceled or stored in modified
internal digit chains, i. e. it might be necessary in particular to enter existing ZOPTs
differently, but having the same meanings in terms of content.
Example:
1.
Assume a ZOPT exists with CODE=004 and ORIG2=20 and the international
prefix is 00. In this situation it is impossible to create an MZOPT with CODE=45-INAT
(and e.g. CHTYPE=MOC). Instead, the MZOPT must be created by:
CR MZOPT : CODE=45-INAT,MZONO=1-255-3, CHTYPE=MOC;
This means that the ORIG2 value(255 in this case, corresponds to the internal
ORIG2 representation for standard MOC-ZOPTs) is located at the third position of
the digit chain.
2.
A ZOPT exist with CODE=0045 and ORIG2=20.
In this case, an MZOPT cannot be created with
CR MZOPT : CODE=45-INAT, CHTYPE=MOC,...
The existing ZOPT must be canceled and re-created by means of
CR ZOPT: CODE=0045, ORIG2=20-3,...;
This ZOPT has the same switching significance as the obove ZOPT. The only difference lies in the different digit chain used for internal storage of the information using
digits and origin code ORIG2. It is now possible to enter the MZOPT with the
command described above.
In principle, it is necessary to ensuring canceling and re-creating the zone points that
no gaps occur in the zoning of both the mobile zone points (MZOPTs) and the fixed
network zone points (ZOPTs). It may be necessary to create several new zone points
so as to be ablate continue zoning all the connections covered by the old zone points.

Cancel zone points (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MZOPT

CAN ZOPT

3a

Create zone points for zoning in own MSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-600

3b

Create zone points for zoning in the next MSC, for calls already
zoned or for non-chargeable calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR MZOPT
using: MZOCHA

3c

Create zone points for zoning calls to intercept codes . . . . . . . . . . . . . . . . . . . . . . . . CR MZOPT

using: MINCEPT

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-603 1

OMN:SSS-TA

TS-604

Operation Charging

Modify mobile-specific zone

Check whether the new tariff categories have already been created . . . . . . . . . . . . DISP MTARCAT

Create new tariff categories (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-601

Modify allocation of tariff categories to call/transmission type . . . . . . . . . . . . . . . . . . MOD MZONE

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-604 1

A30808-X3003-X458-1-7619

Operation Charging

TS-605

OMN:SSS-TA

Cancel zoning for mobile originating calls,

call forwarding, call attempttle

Cancel zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN ZOPT

Cancel assignment of tariff categories to connection types . . . . . . . . . . . . . . . . . . . . CAN MZONE

Cancel tariff categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MTARCAT

Cancel tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MTAR

The individual steps are to be carried out until all available objects have been canceled.

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-605 1

OMN:SSS-TA

TS-606

Operation Charging

Cancel mobile-communication tariff

Check whether the tariff is still being used in a tariff category . . . . . . . . . . . . . . . . . . DISP MTARCAT

2a

Cancel tariff category (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-607

2b

Cancel or replace tariff in a tariff category (if required) . . . . . . . . . . . . . . . . . . . . . . . TP-603

Cancel tariff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MTAR

Steps 2a and/or 2b must be carried out until the tariff is no longer used in any tariff category.

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-606 1

A30808-X3003-X458-1-7619

Operation Charging

TS-607

OMN:SSS-TA

Cancel mobile-specific tariff category

Check whether the tariff category is still being used for a zone . . . . . . . . . . . . . . . . . DISP MZONE

2a

Cancel mobile-specific zone (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-608

2b

Replace tariff category to be canceled for a zone (if required) . . . . . . . . . . . . . . . . . . TS-604

Cancel tariff category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MTARCAT

Steps 2a and/or 2b must be carried out until the tariff category is no longer used in any zone.

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-607 1

OMN:SSS-TA

TS-608

Operation Charging

Cancel mobile-specific zone

Check whether the zone is still being used for a zone point . . . . . . . . . . . . . . . . . . . DISP MZOPT

2a

Cancel zone point (if required). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MZOPT

using: INCEPT=UNOBDE0

2b

Assign new zone to this zone point (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MZOPT

Cancel mobile-specific zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MZONE

Steps 2a and/or 2b must be carried out until the zone is no longer used in any zone point.

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-608 1

A30808-X3003-X458-1-7619

Operation Charging

TS-721

OMN:SSS-TA

Modify meter save time

Display the save times and number of checks for charges. . . . . . . . . . . . . . . . . . . . . DISP METSAV

Modify meter save time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR METSAV

using: TIME, CHEKNO

Caution: If you wish to modify only some of the save times or only the number of checks, those values that are to
remain unchanged must be input as well. Omitting an existing time means that it will be canceled.

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-721 1

OMN:SSS-TA

TS-731

Operation Charging

Copy subscriber charge file to magnetic tape

Edit charges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDIT MET

using: FILE = CA.SU.CHA.nn and TYPE = METSUB

Copy file to magnetic tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMN:SSS-SY

Rewind magnetic tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REWIND MT

using: MTD
This concludes copying of the file. Steps 4 and 5 are needed to delete the file on the
disk.
Caution: The disk file must be deleted immediately after successful transfer,
otherwise storage problems may arise on the hard disk!

Display file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILE

using: FILE = CA.SU.CHA.nn and ALL = YES
Obtain expiration date from output mask
(EXPDAT = YY-MM-DD)

Delete file on disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEL FILE

using: FILE = CA.SU.CHA.nn and EXPDAT = YY-MM-DD

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-731 1

A30808-X3003-X458-1-7619

Operation Charging

TS-732

OMN:SSS-TA

Copy statistics meter file to magnetic tape

Edit meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDIT MET

using: FILE = CA.ST.CHA.nn and TYPE = METSTAT

Copy file to magnetic tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMN:SSS-SY

Rewind magnetic tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REWIND MT

using: MTD
This concludes copying of the file. Steps 4 and 5 are needed to delete the file on the
disk.
Caution: The disk file must be deleted immediately after successful transfer,
otherwise storage problems may arise on the hard disk!

Display file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILE

using: FILE = CA.ST.CHA.nn and ALL = YES
Obtain expiration date from output mask
(EXPDAT = YY-MM-DD)

Delete file on disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEL FILE

using: FILE = CA.ST.CHA.nn and EXPDAT = YY-MM-DD

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-732 1

OMN:SSS-TA

TS-733

Operation Charging

Copy trunk meter file to magnetic tape

Edit meters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDIT MET

using: FILE = CA.TR.CHA.nn and TYPE = METTR

Copy file to magnetic tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMN:SSS-SY

Rewind magnetic tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REWIND MT

using: MTD
This concludes copying of the file. Steps 4 and 5 are needed to delete the file on the
disk.
Caution: The disk file must be deleted immediately after successful transfer,
otherwise storage problems may arise on the hard disk!

Display file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILE

using: FILE = CA.TR.CHA.nn and ALL = YES
Obtain expiration date from output mask
(EXPDAT = YY-MM-DD)

Delete file on disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEL FILE

using: FILE = CA.TR.CHA.nn and EXPDAT = YY-MM-DD

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-733 1

A30808-X3003-X458-1-7619

Operation Charging

TS-740

OMN:SSS-TA

Create statistics meter

If statistics metering is to be performed on a directory-number-related basis, i.e. separately according to directory

number blocks, supplementary statistics meter groups (additional to statistics meter group 0) must be generated
by means of an ODAGEN run.
1

Activate the system feature for statistics meter (if required) . . . . . . . . . . . . . . . . . . . ENTR EXDDAT
using: MET = METSTAT
All existing metering methods must additionally be specified!

Define format of the subsequent meter file (if required) . . . . . . . . . . . . . . . . . . . . . . . ENTR METADM
using: FORMAT, TYPE = METSTAT

Activate meter for call duration (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR CDTDAT

using: EXTNSD = CALLDUR

Assign directory number volume to a statistics meter group . . . . . . . . . . . . . . . . . . . MOD DN

using: DN, STMGRP = 0 ... 15

5a

Create statistics index for zone point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPT

using: STAT = 1 ... 255

5b

Create statistics index for trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD TGRP

using: STAT = 1 ... 255

5c

Create statistics index for route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ROUTE

using: STAT = 1 ... 255

Create statistics meter switchover (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-822

(Statistics meters should be switched over synchronously with tariffs).

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-740 1

OMN:SSS-TA

TS-741

Operation Charging

Cancel statistics meter

Display meter readings and objects of statistics metering . . . . . . . . . . . . . . . . . . . . . DISP STATMET

using: DESC = YES

2a

Cancel statistics index for zone point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPT

using: STAT = 0

2b

Cancel statistics index for trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD TGRP

using: STAT = 0

2c

Cancel statistics index for route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ROUTE

using: STAT = 0

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-741 1

A30808-X3003-X458-1-7619

Operation Charging

TS-831

OMN:SSS-TA

Copy AMA file from disk to tape

Prepare magnetic tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMN:SSS-SY

Copy AMA disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-933

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

A30808-X3003-X458-1-7619

TS-831 1

OMN:SSS-TA

TS-840

Operation Charging

Display account suspension orders

Transfer buffer contents to disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRANS BUFFER

using: TYPE = FIR

Display account suspension orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FIRREC

Remark:
Tasks with the comment "if required" are omitted if they have already been carried out in another step.

TS-840 1

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Task Procedures (TP)

A30808-X3003-X458-1-7619

TP 1

OMN:SSS-TA

TP 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Copy billing file from magnetic disk to magnetic tape

Handling of the tape differs in the following cases:
a new magnetic tape: the tape must be labelled first (continuation: see next step)
a labelled magnetic tape without data on it: by copying a new file onto the tape, the data will always be stored
as a sequential file starting behind the label
a labelled magnetic tape with data on it: by copying a new file onto the tape, the data will always be stored
behind the existing data (i.e. the existing data will not be overwritten). If the file is to be copied onto the beginning of the tape, the tape must be labeled (INIT MT) or the existing files on the magnetic tape must be deleted
(DEL FILE).
If the storage capacity of one tape is not sufficient during data transfer, a continuation tape will be automatically
requested by the transfer process. The continuation tape must have been labelled in the same way.
The sequence described in a example for a MCR file is also valid for the cyclic file IA.ICITR.

TP-301

TRANS BUFFER:
TYPE=MCR

DISP FILE:
FILE=IA.ICMCR,
ALL=Y

Keep ready at least as many

tapes as displayed in the
parameter required copies.

Continuation tapes may be

required.

2A

A30808-X3003-X458-1-7619

TP-301 1

OMN:SSS-TA

Operation Charging

2A

Insert magnetic tape with write

ring

DISP MT:
MTD

If the label is changed, all files

still on the tape will be deleted.

Is the tape labelled?

N

Is the label to remain the

same?

INIT MT:
MTD, CODE, VSN

3A

TP-301 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

DISP FILE:
VSN

Do files still exist on the

tape?

Are files to be deleted?

N

DEL FILE:
FILE, VSN

TRANS FILE:
FILE=
new name/IA.ICMCR,
VSNR=vsn tape

If during data transfer a continuation

tape is requested by the output
message MOUNT TAPE, the old
tape must be removed, a new empty
and labelled tape with inserted write
ring must be inserted, and the
command MOUNT TAPE must be
entered to continue the file transfer.

4A

A30808-X3003-X458-1-7619

TP-301 3

OMN:SSS-TA

Operation Charging

4A

REWIND MT:
MTD

Remove tape.

DISP FILE:
FILE=IA.ICMCR,
ALL=Y

Is the number of copies

made, the same as the
number required?
Y

REL CYCFILE
FILE=IA.ICMCR

TP-301 4

2A

Until REL CYCFILE has been

executed, the cyclic MCR file has the
following characteristics:
that part of the file which has been
copied to magnetic tape cannot be
overwritten
up to this point it is possible to create
a further identical copy on magnetic
tape
REL CYCFILE releases the copied
part of the MCR file for overwriting.
After execution of this command it is
no longer possible to make a copy of
this part of the MCR file.

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Copy a specific MCR file from magnetic disk to magnetic tape (local copy)
It is assumed that a new, labelled magnetic tape is used in each case.
If an unlabelled tape or a labelled tape containing data is to be used, see OMN:SSS-SY.

TP-302

TRANS BUFFER:
ICBUFR=ICMCR

DISP FILE:
FILE=IA.ICMCR,
ALL=Y

Is the number of required

copies > 1?

SET FGRPATT:
FGRP=IA.ICMCR,
SAFCOP=2 (or greater)

2A

A30808-X3003-X458-1-7619

TP-302 1

OMN:SSS-TA

Operation Charging

2A

ACT BILLREC:
FILE=IA.ICMCR,
RECLAY=desired traffic
type
If a follow-up tape is requested
during file transfer with the output
message MOUNT TAPE, remove
the old tape, insert a blank, labelled
tape with a write protection ring and
enter the command MOUNT TAPE
to continue file transfer.

TRANS FILE:
FILE=IA.ICMCR,
VSNR=vsn tape

Delete the file?

N

3B

Y
2B
TRANS FILE:
FILE=IA.ICMCR,
VSNR=vsn tape

The selection criterion

(RECLAY in ACT BILLREC) is
automatically reset, i.e. the
entire file is copied.

DISP FILE:
FILE=IA.ICMCR,
ALL=Y

3A

TP-302 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

Does the number of

copies made equal the
number of copies
required?

2B

REL CYCFILE:
FILE=IA.ICMCR

3B

Was the number of copies

required changed
(SAFCOP)?

Before REL CYCFILE is executed, the

cyclic MCR file has the following features:
the part of the magnetic tape copied to
tape cannot be overwritten
until this point it is possible to create
another identical copy on tape
REL CYCFILE releases the copied part of
the MCR file for overwriting. Once the
command is executed, no more copies of
this part of the MCR file can be made.

SET FGRPATT:
FGRP=IA.ICMCR,
SAFCOP=starting value

A30808-X3003-X458-1-7619

TP-302 3

OMN:SSS-TA

TP-302 4

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Modify assignment of IARSTAT destination name to destination/route or of IARSTAT

origin name to trunk group or LAC
The assignments to the names must be modified step by step for the various measurement types in this procedure.
For names that are not desired, the number symbol # must be entered.

TP-501

Is the assignment to an
IARSTAT destination
name to be modified?

DISP IARNAME:
DEST, RTNO
or LAC, DIR=DEST

MOD IARNAME:
DEST, RTNO or TGNO,
oor LAC, DIR=DEST
NAME=new/old

A30808-X3003-X458-1-7619

DISP IARNAME:
TGNO
or LAC, DIR=DEST

MOD IARNAME:
TGNO,
or LAC, DIR=DEST
NAME=new/old

TP-501 1

OMN:SSS-TA

TP-501 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Cancel IARSTAT name assignment

As long as the IARSTAT name is assigned to more than one destination/route or trunk group, all assignments
except the last one can be canceled immediately, regardless of whether a matrix point has been created for that
name or a registration job is in progress.
Before the last assignment can be canceled, (i.e. that IARSTAT name does not exist any more), all associated
matrix points must be canceled one after another.
The assignments to the names must be canceled step by step for the various measurement types in this procedure. For names that are not desired a number symbol # must be entered.

TP-503

1A
Is the assignment to an
IARSTAT destination
name to be canceled?

DISP IARNAME:
DEST, RTNO
or LAC, DIR=DEST

DISP IARNAME:
TGNO
or LAC, DIR=DES

CAN IARNAME:
DEST, RTNO or TGNO,
NAME
or LAC, DIR=DES

CAN IARNAME:
TGNO, NAME
or LAC, DIR=DES

Executed?
N

2A

A30808-X3003-X458-1-7619

TP-503 1

OMN:SSS-TA

Operation Charging

2A

Is a fault report output:

IARSTAT NAME
CANNOT BE
CANCELLED: FIRST
CANCEL MATRIX
POINT(S)?

Cancel all matrix points that

are linked with this IARSTAT
name.

see CML: Section EM

1A

TP-503 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Assign IARSTAT matrix points to an IARSTAT tariff zone

TP-511

DISP IARTMPD:
TZONE

As long as a tariff zone without

tariff switchover time is
assigned, only the day counter
is used.

ENTR IARZONE:
MTYPE, TZONE, DNAME,
ONAME

A30808-X3003-X458-1-7619

TP-511 1

OMN:SSS-TA

TP-511 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Modify IARSTAT tariff zone for one or more IARSTAT matrix points

TP-513

DISP IARTMPD:
TZONE=new value

As long as a tariff zone without

tariff switchover time is
assigned, only the day counter
is used, i.e. the result is the
same as when the IARSTAT
tariff zone assignment is
canceled.

MOD IARZONE:
MTYPE, DNAME, ONAME,
TZONE=new/old value

A30808-X3003-X458-1-7619

TP-513 1

OMN:SSS-TA

TP-513 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Start IARSTAT registration job

Warning: The registration period for two jobs of the same measurement type must not overlap. It should be noted
that the registration jobs are not canceled in the system until one hour after the end of registration

TP-523

DISP IARJOB;

Not more than 2 registration

jobs may exist for one
measurement type.
Already 2 jobs for that
measurement type?

N
Start a continuous registration job?

Y
REC IARSTAT:
MTYPE, BEG

A30808-X3003-X458-1-7619

REC IARSTAT:
MTYPE, BEG, TER

TP-523 1

OMN:SSS-TA

TP-523 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Cancel IARSTAT registration job

TP-524

DISP IARJOB;

CAN JOB:
JN, JOBCOD

A30808-X3003-X458-1-7619

TP-524 1

OMN:SSS-TA

TP-524 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Enter or modify date and hour of IARSTAT saving for continuous registration jobs

TP-530

DISP IARSAVDA;

Hour= 1 and day

number= 1?

Enter default value: first

day of month at 1 a. m.?

N
Enter day number?

CAN IARSAVDA;
N

Y
ENTR IARSAVDA:
HOUR, DAYNUM

A30808-X3003-X458-1-7619

ENTR IARSAVDA:
HOUR, DAYTYP

TP-530 1

OMN:SSS-TA

TP-530 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Copy AMA disk file to host processor

This procedure also applies to cyclic disk files IA.ICMOB and IA.ICIAR.
Specify the appropriate file in the command.
A file transfer that is in progress can be stopped with STOP FILETRF or canceled with CAN FILETRF. An interrupted transfer can be continued by entering a command at the host processor. However, only the copy service
processes for AMA (AGFR1 to AGFR6) are supported.

TP-545

TRANS BUFFER:
TYPE =IARA

Is the format to be
converted?

Y
DISP FILE:
FILE = IA.ICIAR,
ALL = YES

Are the file attributes

correct for the required
format change?

2A

A30808-X3003-X458-1-7619

2B

2C

TP-545 1

OMN:SSS-TA

Operation Charging

2A

2B

2C

SET FGRPATT:
FGRP = IA.ICAMA,
COPATT, PRNAME

The password must be specified if the file has password

protection. This command only
needs to be input once per
session.
ENTR FILEPSW

TRANS FILE:
FILE =new name/IA.ICIAR,
PRONAM, USINF = a[-b]

ENTR FILEPSW

TRANS FILE:
FILE = new name/IA.ICIAR,
PRONAM, USINF = a[-b],
COPMOD = POST

This command edits the file for

postprocessing during copying.
The precondition is that the
copy service process exists
(see OMN:SSS-SY).

USINF must be entered in the

form a[-b], where:
a = USER IDENTIFICATION,
b = USER ACCOUNT
NUMBER

REL CYCFILE:
FILE = IA.ICAMA,
UNCOND = YES

TP-545 2

Copying to the remote

processor is regarded as a
single safe copy. The data in
the file can be deleted or overwritten by means of parameter
UNCOND following transfer
(once) to the host, even if no
other safe copies have been
made.

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Copy IARSTAT file from magnetic disk to magnetic tape

Handling of the tape differs in the following cases:
a new magnetic tape: the tape must be labelled first (continuation: see next step)
a labelled magnetic tape without data on it: by copying a new file onto the tape, the data will always be stored
as a sequential file starting behind the label
a labelled magnetic tape with data on it: by copying a new file onto the tape the data will always be stored
behind the existing data (i.e. the existing data will not be overwritten).
If you want to copy the file onto the beginning of the tape, the tape must be labelled
(INIT MT) or the existing files on the magnetic tape must be deleted (DEL FILE).

TP-550

DISP FILE:
FILE=IR.

DISP FILE:
FILE=IR.Aryymmnn,
ALL=Y

Keep ready as many tapes as

displayed in the parameter
SAVCOP.

2A

A30808-X3003-X458-1-7619

TP-550 1

OMN:SSS-TA

Operation Charging

2A

Insert magnetic tape with write

ring

DISP MT:
MTD

Is the tape labelled?

N
If the label is changed, all files
still on the tape will be deleted.
Y

Is the label to remain the

same?

Y
INIT MT:
MTD, CODE, VSN

3A

TP-550 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

DISP FILE:
VSN

Are there still files on the

tape?

Are files to be deleted?

N

DEL FILE:
FILE, VSN

TRANS FILE:
FILE=new name/
IR.Aryymmnn, VSNR=vsn
tape, COPMOD=POST

4A

A30808-X3003-X458-1-7619

TP-550 3

OMN:SSS-TA

Operation Charging

4A

REWIND MT:
MTD

Remove tape.

DISP FILE:
FILE=IR.Aryymmnn
ALL=Y

Is the number of copies

made, the same as the
number of backup
copies?

One more copy?

Y

2A

TP-550 4

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Create zone points for mobile originating call and call forwarding

TP-600

Is the zone point to be celldependent (A), trunk-groupdependent (B) or independent of origin (C)?

B
DISP INTCELL:
LACOD, CI

DISP TGRP:
TGNO=<tgno of the
incoming trunk group>

Is the cell created with

ORIG2?

Is the circuit group

created with ORIG 2?

Y
MOD INTCELL:
LACOD, CI, NORIG2

CR MZOPT:
CODE, MZONO=zone
[,BILLING=AMA]
[, CHTYPE]

Y
MOD TGRP:
TGNO, NORIG2

CR MZOPT:
MZONO=zone-orig2
CODE [, CHTYPE]
[,BILLING=AMA]

A30808-X3003-X458-1-7619

TP-600 1

OMN:SSS-TA

TP-600 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Modify assignment of mobile-specific tariffs to tariff category

TP-603

Is a tariff to be added or
an old tariff to be replaced
by a new one?

Y
DISP MTAR:
MTAR

MOD MTARCAT:
MTARCAT, CSWTAR

Is the new tariff already

created?

2A

N
ENTR MTAR:
MTAR, E1UPTI, E2SPTI,
E4INU, E7SPITI

Is another new tariff to be

used?

2A

A30808-X3003-X458-1-7619

TP-603 1

OMN:SSS-TA

Operation Charging

2A

MOD MTARCAT:
MTARCAT, NSWTAR,
[,CSWTAR]

TP-603 2

CSWTAR must be specified if

an old value is to be canceled.

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Enter access tariff - with single pulse metering (SPM) or multiple pulse metering (MPM)
Tariffs are entered without any assignment to a zone (i.e. without ZONO). Then a zone must be assigned a tariff
once by means of ENTR TAR: ZONO, NAME. For the remaining tariffs in this zone, tariff switchovers are entered
by means of ENTR TARSW: ZONO, NAME, ... .
A tariff must be input with ZONO if this zone has not yet been assigned a tariff.
The call attempt tariff PLSATT must be entered in connection with PLSSUP or PLSCOM . The call setup tariff
PLSSUP can be specified in connection with the communication tariff PLSCOM. For creation of the communication tariff, please refer to procedures TP-702, TP-703. The access tariff PLSATT can only be created in the originating exchange.

TP-701

DISP TAR:
ZONO = X

DISP TAR:
NAME = X

1A
Does the tariff already
exist?

2A

A30808-X3003-X458-1-7619

2B

TP-701 1

OMN:SSS-TA

Operation Charging

2A
With PLSATT , the charge is
applied before the called party
answers. With PLSSUP the
charge is applied after the
called party answers.

ENTR TAR:
NAME, PLSATT and/or
PLSSUP

2B
Is the tariff to be entered the
first tariff (A) or a secondary
tariff (B) for this zone?

Single pulse metering (SPM) or

multiple pulse metering (MPM)
with parameters
PLSATT/PLSSUP:
No. of pulses: 1-255

A
ENTR TAR:
ZONO, NAME

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

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

Enter more access

tariffs?

NAME of the new tariff

(switchover)
DATE is necessary if the zone
has already been created in the
zone translator
(DISP ZOPT: ZONO)
NAME of old tariff (reset)

1A

TP-701 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Enter communication tariff - with periodic pulse metering (PPM) or periodic multiple
pulse metering (PMM)
Tariffs are entered without any assignment to a zone (i.e. without ZONO) Then a zone can be assigned a tariff
once by means of ENTR TAR: ZONO, NAME. For the remaining tariffs in this zone, tariff switchovers are entered
by means of ENTR TARSW: ZONO, NAME, ...
Communication tariffs can also be entered in connection with access tariffs. In this case parameter PLSATT or
PLSSUP must also be used (see procedure for the creation of access tariffs).
A tariff must be input with ZONO if this zone has not yet been assigned a tariff.

TP-702

DISP TAR:
ZONO = X

DISP TAR:
NAME = X

1A
Does the tariff already
exist?

N
ENTR TAR:
NAME, PLSCOM = n-t

No.of pulses f. PPM: n=1

No.of pulses f. PMM: n=2-255
PERIODIC PULSE TIME
INTERVAL(t)=200ms-30min,
in multiples of 4 ms.

2A

A30808-X3003-X458-1-7619

TP-702 1

OMN:SSS-TA

Operation Charging

2A

Is the tariff to be entered the

first tariff (A) or a secondary
tariff (B) for this zone?

A
ENTR TAR:
ZONO, NAME

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

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

Enter more PPM or PMM

tariffs?

NAME of the new tariff

(switchover)
DATE is necessary if the zone
has already been created in the
zone translator
(DISP ZOPT: ZONO)
NAME of old tariff
(reset)

1A

TP-702 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Enter tariff sequences in pulse format

A tariff sequence consists of an access component (due before the called party answers in the case of an unsuccessful call or after the called party answers in the case of a successful call) and a communication component.
For the access component, only SPM and MPM are admissible. For the communication component, all basic
tariffs (SPM, MPM, PPM and PMM) are permitted and can be linked together in any way. The communication
component can contain up to four basic tariffs. The period of validity of a basic tariff must always be a multiple of
the specified time interval. A tariff sequence can be cyclic, non-cyclic or regulated by a time limit.
The input of a tariff sequence with ZONO is necessary if this zone has not yet been assigned a tariff. If there is
already a tariff in this zone, the sequence is entered without ZONO and then switched over to the sequence by
means of ENTR TARSW: ZONO , NAME, ....

TP-703

DISP TAR:
ZONO = X

DISP TAR:
NAME = X

1A
Does the sequence
already exist?

2A

A30808-X3003-X458-1-7619

3A

TP-703 1

OMN:SSS-TA

Operation Charging

2A

Repeat sequence (A)?

Release call (B)?
Last tariff until end (C) ?

B
ENTR TAR:
NAME [, PLSATT]
[, PLSSUP], PLSCOM,
SEQEND = CYCLIC

ENTR TAR:
NAME [, PLSATT]
[, PLSSUP], PLSCOM,
SEQEND = LIMIT

ENTR TAR:
NAME [, PLSATT]
[, PLSSUP], PLSCOM,
SEQEND = NONCYC

3A

*) At the end of the sequence, the last basic tariff remains in use. It must be periodic (PPM or PMM). The
default value is NONCYC .

TP-703 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

Is the tariff to be entered the

first tariff (A) or a secondary
tariff (B) for this zone?

A
ENTR TAR:
ZONO, NAME

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

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

Enter more tariff

sequences?

NAME of new tariff

(switchover)
DATE is necessary if the zone
has already been created in the
zone translator
(DISP ZOPT: ZONO)
NAME of old tariff
(reset)

1A

A30808-X3003-X458-1-7619

TP-703 3

OMN:SSS-TA

TP-703 4

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Modify tariff
This procedure is used for the single (non-periodic) modification of a tariff. If the change is to be periodic (e.g. every
workday at 8 a.m.), the command ENTR TARSW. The maximum number of tariff switchovers (in all zones) is
limited to 1024. This includes scheduled jobs for the modification, creation or cancellation of tariffs. If the maximum
number has been reached, all further jobs are rejected.

TP-704

DISP TAR:
NAME = X

Display the old and the new

tariff.

DISP TAR:
ZONO = X

Verify that the old tariff exists in

the specified zone.

DISP TARSW:
ZONO = X

A tariff (new tariff/tariff to be

modified) for which a datecontrolled job already exists
cannot be modified. Note the
maximum no. of switchovers!

Does the new tariff

already exist?

2A

A30808-X3003-X458-1-7619

2B

TP-704 1

OMN:SSS-TA

Operation Charging

2A

2B

ENTR TAR:
NAME [,PLSATT]
[, PLSSUP] [, PLSCOM]
[, SEQEND]

ZONO must not be entered.

The new tariff may include a
maximum of one PPM (PMM)
component (depending on the
project). Switchover from pulse
to currency format is not
possible.

MOD TAR:
[ZONO,] NAME, NNAME,
TIME, DATE

If ZONO is not specified, the

modification applies to all
zones which use this tariff (with
NAME ).

Is the job to be canceled

before it is executed?

Used to correct an input error.

The tariff switchover can be
entered up to 30 days in
advance .

N
MOD TAR:
[ZONO,] NAME, NNAME,
TIME, DATE

TP-704 2

To return to the status before

the preceding MOD TAR
(NAME and NNAME
transposed, otherwise no
difference).

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Cancel tariff
A tariff can only be canceled (CAN TAR: NAME) if it is not currently assigned to a zone and is not required for
switchover or modification.
In order to cancel a tariff in a particular zone, the switchover to the tariff in this zone must be canceled
(CAN TARSW) or the zone must be canceled (CAN TAR: ZONO).

TP-705

DISP TARSW:
DATE = X

Are there any datecontrolled jobs for the

tariff to be canceled?

2B

Y
Can they be canceled?
Y

2A

N
The tariff cannot be canceled.
Wait until the date-controlled
jobs have been processed.

A30808-X3003-X458-1-7619

TP-705 1

OMN:SSS-TA

Operation Charging

2A

Cancel by restoring old

status:
MOD TAR (A),
ENTR TARSW(B),
CAN TARSW (C)

B
MOD TAR:
NAME, NNAME, TIME,
DATE

CAN TARSW:
ZONO, TIME
[, DATE] [, WDCAT]

ENTR TARSW:
ZONO, TIME
[, DATE] [, WDCAT]

2B

DISP TAR:
ZONO = X

2C
Is the tariff to be canceled
one of the current tariffs in
any zone?

4A

N
DISP TARSW:
ZONO = X

3A

TP-705 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

Are there switchover jobs

for the tariff?

The tariff is removed from the

database.

CAN TAR:
NAME

This only removes the tariff

name from the zone. The zone
is retained with the other tariffs.
The name also remains in the
database and can be used in
other zones.

Can the jobs be

canceled?

N
CAN TAR:
NAME, ZONO

2C

A30808-X3003-X458-1-7619

TP-705 3

OMN:SSS-TA

Operation Charging

4A

DISP ZOPT:
ZONO = X

Is the zone configured?

N

Y
Do you wish to create a
temporary name for the
tariff that is to be
canceled?

N
TP-706

TP-707

3A

TP-705 4

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Cancel tariff name

It may be necessary to cancel tariff names if the name is to be used for a different tariff. The tariff (value) itself
continues to exist under a temporary name.

TP-706

DISP TAR:
NAME

ENTR TAR:
NAME = <tempname>

Enter the same tariff under a

temporary name.

MOD TAR:
ZONO, NAME, NNAME,
TIME, DATE

If ZONO is not specified, the

tariff is modified in all zones.
DATE = today,
TIME = next quarter hour,
NNAME = <tempname>

Wait until the modification has

been executed.

Is the tariff to be canceled

from one zone only (A) or
from the database (B) ?

2A

A30808-X3003-X458-1-7619

2B

TP-706 1

OMN:SSS-TA

Operation Charging

2A

CAN TAR:
NAME, ZONO

TP-706 2

2B

CAN TAR:
NAME

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Cancel tariff zone

Before a tariff zone is canceled, it must be ensured that it is not assigned. When a tariff zone is canceled, it is
removed from the database. All switchovers for this zone are canceled at the same time. The tariff names used
are still in the database, however (for further use). They can be canceled as per TP-705.

TP-707

DISP ZOPT:
ZONO

Is the zone assigned?

Y

N
DISP ZOINF:
ZONO

Is there zone
information?

The zone points must first be

removed.

2A

Y
MOD ZOINF:
ZONO,
CHBNO = 255

The zone information must be

canceled.

2A

A30808-X3003-X458-1-7619

TP-707 1

OMN:SSS-TA

Operation Charging

2A

CAN TAR:
ZONO

TP-707 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Enter tariff switchover

The precondition for a tariff switchover is that the new tariff already exists.
Within a zone, it is possible to perform switchovers between different basic tariffs (for example, from single pulse
metering to periodic pulse metering and vice versa) or tariff sequences.

TP-720
Parameter DATE is specified if
the tariff switchover is not to
come into effect until after a
certain date or if the zone is
assigned to a zone point.

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

DISP ZOPT:
ZONO

Is there a statistics index?

N

Y
DISP STATSW:
STAT

Is there a switchover
time?

Tariffs and statistics meters

should be synchronized

2A

A30808-X3003-X458-1-7619

TP-720 1

OMN:SSS-TA

Operation Charging

2A

ENTR STATSW:
STAT, TIME, GRP,
WDCAT

TP-720 2

If a DATE is specified with

command ENTR TARSW ,
wait until that date to enter this
command.

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Modify tariff switchover time

The precondition for a tariff switchover is that the new tariff already exists.
Within a zone, it is possible to perform switchovers between different basic tariffs (for example, from single pulse
metering to periodic pulse metering and vice versa) or tariff sequences.

TP-721

DISP TARSW
Immediate cancellation
(without DATE) is only possible
if the new tariff is not yet active
and the zone is not assigned to
a zone point. If a zone point
exists for this zone, the date of
the next switchover must be
entered.

CAN TARSW:
ZONO, TIME [,DATE]
[, WDCAT]

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

Do not enter this command until

CAN TARSW has been
executed (check the parameter
DATE ).
Parameter DATE is specified if
the tariff switchover is not to
come into effect until after a
certain date or if the zone is
assigned to a zone point.

DISP ZOPT:
ZONO

Is there a statistics index?

N

2A

A30808-X3003-X458-1-7619

TP-721 1

OMN:SSS-TA

Operation Charging

2A

TP-824

TP-721 2

Synchronize the switchover

time for the statistics meters
.

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Cancel tariff switchover

TP-722

DISP TARSW

Immediate cancellation
(without DATE) is only possible
if the new tariff is not yet active
and the zone is not assigned to
a zone point. If a zone point
exists for this zone, the date of
the next switchover must be
entered.

CAN TARSW:
ZONO, TIME [, DATE]
[, WDCAT]

DISP ZOPT:
ZONO

Is there a statistics index?

N

Y
CAN STATSW:
STAT, TIME, WDCAT

A30808-X3003-X458-1-7619

If DATE was specified above,

do not enter this command until
this date.

TP-722 1

OMN:SSS-TA

TP-722 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Create zone points for a zone

Zone points with the same digit combination can be assigned to different zones by specifying one or more (special)
codes.
Possible codes: LAC, LACOR
Possible special codes: ORIG2, MFCAT, ZDIG, CXORIG

TP-761

DISP TAR:
ZONO

The zone is charge-free if

BILLING is not specified. not
specified. Further
option:ZOCHA = NOPULSE.

Is the zone to be chargefree?

Generate meter pulses (A) or

produce AMA tickets (B)?

CR ZOPT:
CODE, ZONO
B

A
CR ZOPT:
CODE, ZONO,
BILLING = AMA

2A

A30808-X3003-X458-1-7619

2B

2A

TP-761 1

OMN:SSS-TA

Operation Charging

2A

Do you also wish the

number of calls to be
registered?

N
CR ZOPT:
CODE, ZONO,
BILLING = METERING,
SUCHCNTR

CR ZOPT:
CODE, ZONO,
BILLING = METERING,
SUCHCNTR, SUCACNTR

For SUCACNTR : only CNTR1

or CNTR3 . Do not use any
counter that registers call
charges, facility input charges
or facility usage charges.

2B

Do you wish to enter data

for meter processing?

Y
MOD ZOPT:
CODE, ZONO, MEPROC

TP-761 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Merge zone points

The following inputs are possible for the zoning result:
ZONO or ZOCHA or INCEPT or MBI.

TP-767

Is the zoning result to be a

zone?

Y
DISP TAR:
ZONO

Does the zone number

exist?

Y
MERGE ZOPT:
CODE,
zoning result*)

The zone number must be

created first.

*) Only one zoning result is permitted.

A30808-X3003-X458-1-7619

TP-767 1

OMN:SSS-TA

TP-767 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Create zone point for a directory number range belonging to the local area of a foreign
exchange subscriber

TP-769

DISP TAR:
ZONO

Does the zone exist, i.e.

have tariffs been created
for the zone?

The zone must first be

created with ENTR TAR .

Y
CR ZOPT:
CODE, ZONO,
BILLING, ORIG2

Do you wish to enter data

for meter processing?

Y
MOD ZOPT:
MEPROC, CODE, ZONO,
ORIG2

A30808-X3003-X458-1-7619

ORIG2 = originating mark of

the foreign local area

TP-769 1

OMN:SSS-TA

TP-769 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Modify zone points for directory number ranges belonging to the local area of a foreign
exchange subscriber

TP-770

Do you wish to modify

meter processing?

N
The zoning result can also be
modified.
Possible inputs for the zoning
result: ZONO or ZOCHA or
INCEPT or MBI

MOD ZOPT:
CODE, ORIG2,
zoning result
(parameter to be modified]

MOD ZOPT:
CODE, ZONO, MEPROC
ORIG2

A30808-X3003-X458-1-7619

TP-770 1

OMN:SSS-TA

TP-770 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Copy subscriber charge file to host processor

A file transfer that is in progress can be stopped with STOP FILETRF or canceled with CAN FILETRF .

TP-811

Is this the first time that

the charge data have
been edited?

Y
ENTR METADM:
TYPE = METSUB,
BOOKOF, FORMAT,
DNTYPE = COUNT

EDIT MET:
TYPE = METSUB,
FILE = CA.SU.CHA.nn

ENTR FILEPSW

TRANS FILE:
FILE = CA.SU.CHA.nn,
PRONAM,
USINF = a[-b]

The password must be

specified if the file has
password protection. This
command only needs to be
input once per session.

USINF must be entered in the

form a[-b], where:
a=USER IDENTIFICATION,
b=USER ACCOUNT NUMBER

2A

A30808-X3003-X458-1-7619

TP-811 1

OMN:SSS-TA

Operation Charging

2A

DISP FILE:
FILE = CA.SU.CHA.nn,
ALL = YES

Take the expiration date from

the output mask
(EXPDAT = YY-MM-DD)

DEL FILE:
FILE = CA.SU.CHA.nn,
EXPDAT = YY-MM-DD

TP-811 2

Caution: The disk file must be

deleted immediately after
successful transfer, otherwise
storage problems may arise on
the hard disk.

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Overview of commands for statistics meter administration

This procedure contains the individual commands for the administration of statistics meters. For further information
please refer to the introductory section of this document, the individual procedures and/or the Command Manual
CML.

TP-820

Activate system feature:

ENTR EXDDAT

Define the data format of

the meter file:
ENTR METADM

FORMAT = 1: without call

duration,
FORMAT = 2: with call duration

Display blocked meter

types:
SAVE MET

In addition, the system

interrogates the status of the
charge meters every 10
minutes. If the status is fallback
(APS change, ISTART2G), an
output appears on the OMT.

Are the charge meters

active?

N
Incorporate logging file
2B

2A

A30808-X3003-X458-1-7619

TP-820 1

OMN:SSS-TA

Operation Charging

2A

Restart charge registration

SAVE MET

With TYPE = METSTAT and

FUNC = FALLBACK.

2B
Is the call duration meter
to be started?

Y
Start call duration meter:
ENTR CDTDAT

2C

Statistics metering for a zone

point(A), trunk group(B) or
route(C)?

B
Create zone point with
statistics index:
CR ZOPT

Create trunk group with

statistics index:
CR TGRP

Create route with statistics

index:
CR ROUTE

3A

TP-820 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

Are further statistics

indices to be assigned for
an object of the same
type?

2C

Y
Assignment of directory
number volume to statistics
meter group:
MOD DN

Input of statistics meter

switchovers:
ENTR STATSW

Display statistics meter

readings:
DISP STATMET

Collect statistics meter data

Display statistics meter data

Display the statistics meter

groups and the statistics
indices:
DISP STMETGRP

Assignment of directory
number volume to statistics
meter group:
DISP STMETLNK

4A

A30808-X3003-X458-1-7619

TP-820 3

OMN:SSS-TA

Operation Charging

4A

Display statistics meter

switchover times:
DISP STATSW

Statistics meter switchovers

should be synchronized with
tariff switchovers!

Display statistics meter data

Delete statistics meter data

Cancel indices:
MOD ZOPT / MOD TGRP /
MOD ROUTE

Cancel statistics meter

group:
MOD DN

With STAT = 0

With STMGRP = 0

Cancel statistics meter

switchover time:
CAN STATSW

TP-820 4

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Enter switchover for statistics meters

Statistics meter switchover times should be synchronized with tariff switchovers. To do this, the zone via which the
call charges are registered must be known. In the case of zone points with a statistics index it is displayed by
means of the MML command DISP STATMET . For routes, the relevant codes are determined by entering
DISP CPT and specifying the destination. The zone is established by entering DISP ZOPT and specifying the
code. A tariff switchover has no relevance for incoming trunk groups.

TP-822

DISP STATMET:
DESC = YES

Display the statistics index, the

valid zones and the statistics
meter groups created.

DISP STATSW:
STAT, TIME, WDCAT

Are the switchovers for

tariffs and statistics
meters to be
synchronized?

Y
DISP TARSW:
ZONO

2A

A30808-X3003-X458-1-7619

TP-822 1

OMN:SSS-TA

Operation Charging

2A

ENTR STATSW:
STAT, TIME, WDCAT, GRP

TP-822 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Modify switchover time for statistics meters

Statistics meter switchover times should be synchronized with tariff switchovers. To do this, the zone via which the
call charges are registered must be known. In the case of zone points with a statistics index it is displayed by
means of the MML command DISP STATMET. For routes, the relevant codes are determined by entering
DISP CPT and specifying the destination. The zone is established by entering DISP ZOPT and specifying the
code. A tariff switchover has no relevance for incoming trunk groups.

TP-824

DISP STATSW

CAN STATSW:
STAT, TIME, WDCAT

DISP STATMET:
DESC = YES

Identify the zones to which a

statistics index has been
assigned.

DISP TARSW:
ZONO

2A

A30808-X3003-X458-1-7619

TP-824 1

OMN:SSS-TA

Operation Charging

2A

Are tariff switchovers also

to be modified?

N
ENTR STATSW:
STAT, TIME, WDCAT, GRP

TP-824 2

TP-721

Modify the tariff switchover

times.

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Activate trunk meter for bothway and outgoing trunks groups

If a trunk group is bothway, it can only be used either as an incoming or as an outgoing trunk group for metering
purposes, otherwise the meter readings become distorted.

TP-830

DISP TRMET:
TGNO = X

Has the trunk group been

created?

N
CR TGRP:
TGNO, GCOS = TRMET

Is the trunk group outgoing

(A) or bothway (B)?

ENTR TGDAT:
TGNO,
GCOS = TRMET

Is the trunk group to be used

for metering outgoing (A) or
incoming (B)?
B

2A

A30808-X3003-X458-1-7619

2B

TP-830 1

OMN:SSS-TA

Operation Charging

2A

DISP ROUTE:
TGNO, DEST = X

MOD ROUTE:
TGNO, DEST,
LNDES = TRMET

2B

TP-830 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Overview of commands for AMA administration

This procedure contains the individual commands for the administration of automatic message accounting ( AMA).
Auxiliary conditions (interrogation of steps already executed) have not been included. For further information
please refer to the introductory section of this document, the individual procedures and/or the Command Manual
CML.

TP-900

Activate system feature:

ACT IAFEAT

Record format and number

of copies:
SET FGRPATT

Also to set the occupancy level

alarm.

Collect additional/alternative AMA data:

ENTR CDTDAT

Are the data records registered centrally (CAMA, A) or

locally (LAMA, B)?

A
Allow calling number
indication (incoming)
CR TGRP

2A

A30808-X3003-X458-1-7619

If the trunk group already

exists: with ENTR TGDAT .

2B

TP-900 1

OMN:SSS-TA

Operation Charging

2A

2B

Request calling number

indication (outgoing):
CR ROUTE

Is MFCR2 used as the

signaling system?

Y
Signaling must not be END
TOEND.
If the trunk group already
exists: with CAN TGDAT.

Set LINK-BY-LINK
signaling::
CR TGRP

Calling line type =

PBXLN?

Y
Set LSN or PDN in the
record :
CR PBXLN

Call diversion to announcement or operator with AMA:

CR INC

For registration of the B1 >

B2 leg with AMA.

3A

TP-900 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

AMA for calls (A) or for

FAI/FAU (B)?

4A

AMA destination-dependent
(A) or for incoming trunk
groups (B)?

A
Request AMA data for
incoming trunk group:
CR TGRP

Set zone point to AMA :

CR ZOPT

Set incoming trunk group to

zoning (only necessary for
CAMA):
CR TGRP

If the trunk group already

exists: with ENTR TGDAT.

AMA for unsuccessful call

attempts?

Y
AMA for all unsuccessful call
attempts (A) or only for
unsuccessful chargeable
call attempts (B)?
A
AMAAMA for all
unsuccessful call attempts:
ENTR CDTDAT

AMA for all unsuccessful

call attempts:
ENTR CDTDAT

Enter call attempt tariff for

this zone:
ENTR TAR

4B

A30808-X3003-X458-1-7619

TP-900 3

OMN:SSS-TA

Operation Charging

4A

AMA for FAU (A) or

for FAI (B)?

A
AMA for FAU:
CR FAUCHA

No charge registration for

CENTREX-FAU possible.

AMA for FAIn:

CR FAICHA

For subscriber controlled

inputs and operator inputs.

AMA for CENTREX-FAI:

ENTR CDTDAT

Also possible for implicit

deactivations.

4B

Activate AMA immediate

output:
ACT IAFEAT

Set subscriber to AMAimmediate output:

MOD SUB

With MOD PBX for PBX and

MOD PBXLN for PBXLN.

5A

TP-900 4

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

5A

Immediate output for FAIS:

ENTR CDTDAT

Output of the current

AMA data?

Collect AMA data

Output AMA data

N

Y
Write buffer contents to disk
file:
TRANS BUFFER

Output on magnetic tape (A)

or at OMT (B)?

Automatic if the buffer is full.

A
Copy AMA file to tape or
host:
TRANS FILE

A30808-X3003-X458-1-7619

Display AMA data records:

DISP AMA

TP-900 5

OMN:SSS-TA

TP-900 6

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Overview of commands for administration of detailed billing DEB

This procedure contains the individual commands for the administration of detailed billing DEB . Auxiliary conditions (interrogation of steps already executed) have not been included. For further information please refer to the
introductory section of this document, the individual procedures and/or the Command Manual CML.

TP-905

Activate system feature:

ACT IAFEAT

Record format and no. of

copies:
SET FGRPATT

Also to set the occupancy level

alarm.

Collect
additional/alternative DEB
data:
ENTR CDTDAT

DEB for selected calls (A) or

for all calls (B)?

A
Assign DEB to the
subscribers:
CR SUB

2A

A30808-X3003-X458-1-7619

With CR PBX for PBX and

CR PBXLN for PBXLN.

2B

TP-905 1

OMN:SSS-TA

Operation Charging

2A

DEB for next call (A) or

dependent on traffic category
(B)?

A
Define code for subscriber
controlled input:
ENTR SCFEA

Assign DEB to subscriber:

CR SUB

Assign DEB to subscriber:

CR SUB

Assign traffic type to

destination:
CR DEST

Also possible with

ENTR DNATT.

Link DEB and traffic type:

ENTR TRABLOCK

2B
DEB linetype = PBXLN?
N

Y
Set LSN or PDN in the
record:
CR PBXLN

3A

TP-905 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

DEB required for FAU (A) or

for FAIS (B)? Otherwise go
to C.

A
DEB for all supplementary
services:
ENTR CDTDAT

DEB for all supplementary

services:
ENTR CDTDAT

Register FAU charges (with

AMA and/or METERING:
CR FAUCHA

CR FAICHA is not required

here.

Call diversion to announcement or operator with DEB:

CR INC

MARKS= CXSFAICH will not

be evaluatet (DEB is produced
regardless of this parameter).
MARKS = AMAFAIID will not
be evaluatet (DEB is not
possible for implicit
deactivations).

For registration of the

B1 > B2 leg with DEB.

Activate DEB immediate

output:
ACT IAFEAT

Set subscriber to DEBimmediate output:

MOD SUB

With MOD PBX for PBX and

MOD PBXLN for PBXLN.

4A

A30808-X3003-X458-1-7619

TP-905 3

OMN:SSS-TA

Operation Charging

4A

Immediate output for FAIS:

ENTR CDTDAT

Output of the current

DEB data?

Collect DEB data

Output DEB data

N

Y
Write buffer contents to disk
file:
TRANS BUFFER

Output to tape or host (A) or

at OMT (B)?

Automatic if the buffer is full.

A
DEB file to tape or host:
TRANS FILE

TP-905 4

Display DEB records:

DISP AMA

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Overview of commands for administration of meter observation MOB

This procedure contains the individual commands for the administration of meter observation ( MOB ). Auxiliary
conditions (interrogation of steps already executed) have not been included. For further information please refer
to the introductory section of this document, the individual procedures and/or the Command Manual CML.

TP-910

Activate system feature:

ACT IAFEAT

MOB for ordinary

subscribers (A) or TFS
subscribers (B)?

A
Assign MOB to the ordinary
subscribers:
ACT MOBS

Assign MOB to the TFS

subscribers:
ACT SMOBS

Collect alternative MOB

data:
ENTR CDTDAT

For PBX subscribers, the LSN

is always registered in the
MOB record.

2A

A30808-X3003-X458-1-7619

TP-910 1

OMN:SSS-TA

Operation Charging

2A

Call diversion to announcement or operator with

MOB:
CR INC

MOB for calls (A) or FAU

(B)?

For registration of the

B1 > B2 leg with MOB.

MOB for FAIS is permittet by

software.
MOB for FAIS can be
deactivatet by a patch.

A
No further steps required in
this case.

Register FAU charges (with

AMA / METERING:
CR FAUCHA

Activate MOB immediate

output:
ACT IAFEAT

Immediate output not possible

for TFS-subscribers.

Set subscriber to MOB

immediate output:
ACT MOBS

Collect MOB data

Output of the current

MOB data?

Output MOB data

N

3A

TP-910 2

3B

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

3B

Write buffer contents to disk

file:
TRANS BUFFER

Output to tape or host (A) or

at OMT (B)?

Automatic if the buffer is full.

A
Copy MOB file to tape or to
host:
TRANS FILE

A30808-X3003-X458-1-7619

Display MOB data records:

DISP MOBSDAT

TP-910 3

OMN:SSS-TA

TP-910 4

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Overview of commands for administration of preventive meter observation PMOB

This procedure contains the individual commands for the administration of preventive meter observation (PMOB).
Auxiliary conditions (interrogation of steps already executed) have not been included. For further information
please refer to the introductory section of this document, the individual procedures and/or the Command Manual
CML .

TP-915

Activate system feature:

ACT IAFEAT

Enter tariff:
ENTR TAR

Assign tariff to zone:

ENTR TARSW

In any exchange in the

connection path.

Register call charges with

METERING :
CR ZOPT

2A

A30808-X3003-X458-1-7619

TP-915 1

OMN:SSS-TA

Operation Charging

2A

Set threshold value:

ENTR CDTDAT

Modification of the
threshold value required?

N
Deactivate PMOB :
CAN CDTDAT

Activate PMOB with a new

threshold value:
ENTR CDTDAT
Collect PMOB data

Output PMOB data

Output on magnetic tape (A)

or at OMT (B)?

3A

TP-915 2

3B

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

3A

Output of the current

PMOB data?

3B

Y
Write buffer contents to disk
file:
TRANS BUFFER

Copy PMOB file to tape:

TRANS FILE

A30808-X3003-X458-1-7619

Automatic if the buffer is full.

TRANS BUFFER is not

required in this case.

Display PMOB records:

DISP PMOBSDAT

TP-915 3

OMN:SSS-TA

TP-915 4

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Display AMA data for subscriber

The AMA records for a subscriber can be displayed either completely or for specific time intervals.
Before a display is created, the records still buffered in the memory must be saved to disk. Records awaiting
immediate output cannot be forcibly written to disk.

TP-931

TRANS BUFFER:
TYPE = AMA

Are all subscriber data to

be displayed?

Y
DISP AMA:
DN

A30808-X3003-X458-1-7619

DISP AMA:
DN
[, BEGDATE, BEGTIME,
ENDDATE, ENDTIME]

The time interval for which the

AMA data are output is defined
by 4 parameters, at least one of
which must be specified.
Default values are used for the
other parameters (see CML ).

TP-931 1

OMN:SSS-TA

TP-931 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Copy AMA disk file to tape

This procedure also applies to cyclic disk files IA.ICMOB and IA.ICIAR. Specify the appropriate file in the
command.

TP-933

TRANS BUFFER:
TYPE = AMA

Is the format to be
converted?

N
DISP FILE:
FILE = IA.ICAMA,
ALL = YES

Are the file attributes

correct for the required
format change?

N
SET FGRPATT:
FGRP = IA.ICAMA,
COPATT, PRNAME

2A

A30808-X3003-X458-1-7619

2B

TP-933 1

OMN:SSS-TA

Operation Charging

2A

ENTR FILEPSW

TRANS FILE:
FILE = IA.AMA/IA.ICAMA,
VSNR

MOUNT TAPE:
DEV

2B

The password must be

specified if the file has
password protection. This
command only needs to be
input once per session.

ENTR FILEPSW

TRANS FILE:
FILE = IA.AMA/IA.ICAMA,
VSNR,
COPMOD = POST

This command edits the file for

postprocessing during copying.
The precondition is that the
copy service process exists
(see register OMN:SSS-SY).

Only if there is a continuation

tape.

REWIND MT:
MTD

REL CYCFILE:
FILE = IA.ICAMA

TP-933 2

This command must not be

executed until postprocessing
has taken place.

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Copy AMA disk file to host processor

This procedure also applies to cyclic disk files IA.ICMOB and IA.ICIAR.
Specify the appropriate file in the command.
A file transfer that is in progress can be stopped with STOP FILETRF or canceled with CAN FILETRF. An interrupted transfer can be continued by entering a command at the host processor. However, only the copy service
processes for AMA (AGFR1 to AGFR6) are supported.

TP-934

TRANS BUFFER:
TYPE = AMA

Is the format to be
converted?

Y
DISP FILE:
FILE = IA.ICAMA,
ALL = YES

Are the file attributes

correct for the required
format change?

2A

A30808-X3003-X458-1-7619

2B

2C

TP-934 1

OMN:SSS-TA

Operation Charging

2A

2B

2C

SET FGRPATT:
FGRP = IA.ICAMA,
COPATT, PRNAME

The password must be

specified if the file has
password protection. This
command only needs to be
input once per session.
ENTR FILEPSW

TRANS FILE:
FILE = IA.AMA/IA.ICAMA,
PRONAM, USINF = a[-b]

ENTR FILEPSW

TRANS FILE:
FILE = IA.AMA/IA.ICAMA,
PRONAM, USINF = a[-b],
COPMOD = POST

This command edits the file for

postprocessing during copying.
The precondition is that the
copy service process exists
(see register OMN:SSS-SY).

USINF must be entered in the

form a[-b], where:
a = USER IDENTIFICATION,
b = USER ACCOUNT
NUMBER

REL CYCFILE:
FILE = IA.ICAMA,
UNCOND = YES

TP-934 2

Copying to the remote

processor is regarded as a
single safe copy. The data in
the file can be deleted or
overwritten by means of
parameter UNCOND following
transfer (once) to the host,
even if no other safe copies
have been made.

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Task Complexes (TC)

A30808-X3003-X458-1-7619

TC 1

OMN:SSS-TA

TC 2

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

TC-001

OMN:SSS-TA

Creation of the Calendar Group for Mobile Charging

For the Mobile Charging feature a calendar group is to be created, consisting of the assignment of week
days to a weekday category, a fixed holiday calendar, and a calendar for movable holidays for each individual year.

MML Command Overview

1. Create the weekday categories
MOD WDCAT: FEAT, WD, WDCAT;
This command assigns (project-specific) weekday categories to the individual weekdays.
The weekday categories valid for the project can be displayed with DISP MPRDDAT.
2. Create the fixed holiday table
CR HOLICAL: FEAT,YEAR=X, DATECAT=<month-day-weekday category>
This command assigns the weekday category and the date of the holidays that occur every year.
If a holiday calendar has already been created, additional values can be entered, or assignments
modified, with the command
MOD HOLICAL: FEAT, YEAR=X,
DATECAT= >NDATECAT, CDATECAT>;
3. Create the movable holiday calendar
CR HOLICAL: FEAT, YEAR =xxxx,
DATECAT= <NDATECAT, CDATECAT>;
If a specific year is entered under YEAR, the holidays created are only valid for that year.
f a holiday calendar has already been created, additional values can be entered, or assignments
modified, with
MOD HOLICAL: FEAT, YEAR= xxxx,
<NDATECAT, CDATECAT>;
It is important to note that the movable holiday table can only be modified fortimes in the future (i.e.
not for the following month or for the following year):

Example
For charge registration in a PLMN a calendar group is to be created with the following values:
the days Monday to Friday are to be assigned the weekday category WORKDAY,
Saturday and Sunday are to be assigned the category Full Weekend
fixed holidays (weekday category HO):
January 1st
May 1st
December 25th
Movable holidays (weekday category HO):
for 1998
April 3rd
April 4rd
September 11th
for 1999
April 8th
April 9th
November 30th

A30808-X3003-X458-1-7619

TC-001 1

OMN:SSS-TA

2.1

Operation Charging

Database in the MSC:

1. Create weekday categories
MOD WDCAT: FEAT=MCHARGE, WD=SA, WDCAT=EF;
MOD WDCAT: FEAT=MCHARGE, WD=SU, WDCAT=EF;
Since all weekdays are automatically assigned the weekday category WORKDAY, the categories of
the days from Monday to Friday do not have to be changed.
2. Create the fixed holiday table
CR HOLICAL: FEAT=MCHARGE,YEAR = X,
DATECAT=01-01-HO & 05-01-HO & 12-25-HO;
3. Create the movable holiday calendar
CR HOLICAL: FEAT=MCHARGE,YEAR = 1998,
DATECAT=04-03-HO & 05-01-HO & 09-11-HO;
CR HOLICAL: FEAT=MCHARGE,YEAR = 1999,
DATECAT=04-08-HO & 04-09-HO & 11-30-HO;

TC-001 2

A30808-X3003-X458-1-7619

Operation Charging

TC-002

OMN:SSS-TA

Mobile-specific Tariffs and Zones for Mobile Subscribers of the Home PLMN
For mobile originating calls made by mobile subscribers of a PLMN, in an MSC the duration of call charge
intervals and the associated charge units are to be created for calls according to the type of resources
used (full-rate or half-rate transmission) and/or for call attempts, as well as the switchover points
between the individual tariffs.
In addition to this, the tariffs for mobile terminating calls made by mobile subscribers of the home network
are to be created.

MML Command Overview

1. Create a mobile-specific tariff
ENTR MTAR: MTAR, E1UPTI, E2SPTI, E4INU, E7SPITI;
This command fixes the duration of the calll charge intervals and the number of call charge units per
time interval.
2. Create mobile radio-specific tariff categories
ENTR MTARCAT: MTARCAT, SWTAR=<hour-minute-tariff-weekday category>,....;
This command specifies which tariffs are to be used at which times for charge registration.
3. Create mobile-specific zones
CR MZONE: ZONO, FULL [,HALF] [,ATTEMPT];
This command assigns tariff categories to the type of resource used (full-rate or half-rate transmission) and/or to call attempts.
4. Create the mobile radio-specific tariff for MTC and the scaling factors
ENTR PLMNTAR: NETW, E1UPTI, E2SPTI, E4INU, E7SPITI, E3SCF;
This command specifies the scaling factor (E3SCF), i.e. a PLMN-specific multiplier for the call
charge units calculated from E1, E2, E4 and E7 (see 1.: ENTR MTARCAT) for MOC, as well as the
parameters valid for mobile terminating calls.

Example
The following items are to be created for charge registration in a PLMN with MCC=262 and MNC=03:
3 tariffs with the following parameters:
Tariff 1:
Duration of 1st time interval:
Charge for 1st time interval (basic charge) in charge units:
Duration of subsequent time intervals:
Number of call charge units per subsequent time interval:
Scaling factor:

25 s
2
15 s
1
1

Tariff 2:
Duration of 1st time interval:
Charge for 1st time interval (basic charge) in charge units:
Duration of subsequent time intervals:
Number of call charge units per subsequent time interval:
Scaling factor:

15 s
1
15 s
1
1

Tariff 3:
Duration of 1st time interval:
Charge for 1st time interval (basic charge) in charge units:

30 s
3

A30808-X3003-X458-1-7619

TC-002 1

OMN:SSS-TA

Operation Charging

Duration of subsequent time intervals:

Number of call charge units per subsequent time interval:
Scaling factor:

10 s
1
1

The following tariff categories:

Tariff category 1
On workdays tariff 1 is to apply from 8 am to 6 pm and tariff 2 from 6 pm to 8 am.
At weekends and on holidays tariff 2 is to apply throughout the day.
Tariff category 2:
IIn this tariff category, tariff 2 is to apply throughout the day for every day of the week.
The following zones:
In zone 1 tariff category 1 is to be used for full rate transmission.
In zone 2 tariff category 1 applies for full rate transmission and tariff category 2 for call attempts.
A scaling factor of 1 valid for MOC and MTC of the mobile subscribers of the home PLMN.
MTCs are to be non-chargeable for home mobile subscribers.
2.1

Database in the MSC:

1. Create the mobile-specific tariffs:
Tariff 1:
ENTR MTAR: MTAR=1, E7SPITI=250, E4INU=20, E2SPTI=150, E1UPTI=10;
Tariff 2:
ENTR MTAR: MTAR=2, E7SPITI=150, E4INU=10, E2SPTI=150, E1UPTI=10;
Tariff 3:
ENTR MTAR: MTAR=3, E7SPITI=300, E4INU=30, E2SPTI=100, E1UPTI=10;
2. Create the mobile-specific tariff categories:
ENTR MTARCAT: MTARCAT=1,SWTAR=08-00-1-WO & 18-00-2-WO & 00-00-3-EF & 00-00-3-HO
& 00-00-2-WO;
ENTR MTARCAT: MTARCAT=2,SWTAR=00-00-2-WO;
Prerequisite: Saturday and Sunday were assigned the weekday category Full Weekend (EF) in the
calendar group for mobile charging (DISP WDCAT, MOD WDCAT using FEAT=MCHARGE).
3. Create the mobile-specific zones:
CR MZONE: ZONO=1, FULL=1;
CR MZONE: ZONO=2, FULL=1, ATTEMPT=2;
4. Create mobile-specific tariff for MTC and scaling factor:
ENTR PLMNTAR: NETW=262-03, E3SCF=100;

TC-002 2

A30808-X3003-X458-1-7619

Operation Charging

TC-009

OMN:SSS-TA

Trunk-related Charge Registration of Mobile Originating Calls to the PSTN

For charge registration of an MOC to the PSTN from an MSC area, origin-dependent zone points have
to be created.
MCR data records are to be generated for the calls and for call attempts.

MML Command Overview

1. Generation of MCR data records
Activation of the MCR feature (unless this was already done during installation this can be checked
with DISP IAFEAT):
DACT FNS: FNS=IA;
ACT IAFEAT: TYPE=MCR;
ACT FNS: FNS=IA;
Activation of MCR data record generation for call attempts (unless this was already done during
installation this can be checked with DISP MSERVOPT: FEAT=CALLATT):
MOD MSERVOPT: FEAT=CALLATT, STAT=ACT;
Activation of MCR data record generation and zoning for trunk groups between MSC and BSC:
CR TGRP: TGNO, OPMODE, ORIG1, GCOS=AMAREQD&ZON;
If the trunk groups have already been created, the modification is made with
ENTR TGDAT: TGNO, GCOS=AMAREQD&ZON;
(This command is also valid for base station trunk groups!)
2. Create the origin dependence of the calls for charge registration (ORIG2)
Trunk group dependence:
CR TGRP: TGNO, OPMODE, ORIG2;
If the trunk groups have already been created, the modification is made with
MOD TGRP: TGNO, NORIG2;
3. Create the mobile-specific zone points
CR MZOPT: CODE=<digitscode type>, MZONO=<zoneORIG2ORIG2- position>, CHTYPE,
BILLING;
The zone points define how the charges for an outgoing call are to be registered depending on the
dialed digits, the origin of the call, and the type of call (MOC or CF).
A prerequisite is that the corresponding mobile-specific tariffs, tariff categories and zones have been
created.
The parameter BILLING specifies the type of charge registration. For generation of MCR data
records, BILLING=AMA must be set.

Example
For charge registration of mobile originating calls from PLMN A (see Fig. 5.1) zone points are to be
created for the dialed digits 0043 and 089. Zoning is to be origin-dependent.
Furthermore, the calls are to be registered by means of MCR, whereby for calls from the BSC2 area a
data record is to be generated for chargeable call attempts also (cf. zones 1 and 2 in TC-002.

2.1

Database in the MSC:

1. Activation of MCR data record generation and zoning, and creation of the origin code for the trunk
group between MSC and BSC:
CR TGRP: TGNO=BSC1, OPMODE=BW, ORIG1=50, GCOS=AMAREQD&ZON, ORIG2=10;
CR TGRP: TGNO=BSC2, OPMODE=BW, ORIG1=60, GCOS=AMAREQD&ZON, ORIG2=20;

A30808-X3003-X458-1-7619

TC-009 1

OMN:SSS-TA

Operation Charging

2. Creation of the mobile-specific zone points:

CR MZOPT: CODE=43-INAT, MZONO=1-10, CHTYPE=MOC, BILLING=AMA;
CR MZOPT: CODE=89-NAT,MZONO=1-10, CHTYPE=MOC, BILLING=AMA;
CR MZOPT: CODE=43-INAT,MZONO=2-20, CHTYPE=MOC, BILLING=AMA;
CR MZOPT: CODE=89-NAT,MZONO=2-20, CHTYPE=MOC, BILLING=AMA;

BSC 2
SPC = 260, NAT 0

BTS

TGNO = BSC 2
ORIG1 = 60

BTS

ORIG2 = 20
MSC/VLR

ORIG1 = 50
ORIG2 = 10

PLMN A
CC
NDC
MCC
MNC

= 49
= 179
= 262
= 03

Fig. 5.1

TC-009 2

BTS

SPC = 250, NAT 0

SPC = 200, NAT 0

VLRISD/SCCGPA-digits:
491799900000

BSC 1

TGNO = BSC 1

BTS

BTS

MOC to the fixed network

A30808-X3003-X458-1-7619

Operation Charging

TC-010

OMN:SSS-TA

Cell-related Charge Registration of Mobile Originating Calls to the PSTN

For charge registration of an MOC to the PSTN from an MSC area, cell-related zone points are to be
created.
MCR data records are to be generated for the calls and for chargeable call attempts.

MML Command Overview

1. Generation of MCR data records
Activation of the MCR feature (unless this was already done during installation this can be checked
with DISP IAFEAT):
DACT FNS: FNS=IA;
ACT IAFEAT: TYPE=MCR;
ACT FNS: FNS=IA
Activation of MCR data record generation for call attempts (unless this was already done during
installation this can be checked with DISP MSERVOPT: FEAT=CALLATT):
MOD MSERVOPT: FEAT=CALLATT, STAT=ACT;
2. Create the origin dependence of the calls for charge registration (ORIG2)
Cell dependence:
CR INTCELL: LACOD, CI, ORIG2, BSCSPC, NETIND, LMN;
A prerequisite is that the feature cell-dependent charge registration is available (project-linked).
If the cells have already been created, the modification is made with
MOD INTCELL: LACOD, CI, NORIG2;
3. Create the mobile-specific zone points
CR MZOPT: CODE=<digitscode type>, MZONO=<zoneORIG2ORIG2- position>, CHTYPE,
BILLING;
The zone points define how the charges for an outgoing call are to be registered depending on the
dialed digits, the origin of the call, and the type of call (MOC or CF).
A prerequisite is that the corresponding mobile-specific tariffs, tariff categories and zones have been
created.
The parameter BILLING specifies the type of charge registration. For generation of MCR data
records, BILLING=AMA must be set.

Example
For charge registration of mobile originating calls from PLMN A (see Fig. 5.2) zone points are to be
created for the dialed digits 0043 and 089. Zoning is to be cell-dependent.
Furthermore, the calls are to be registered by means of MCR, whereby for cell CI=2555, unlike the other
cells of the BSC area, a data record is to be generated for call attempts also (cf. zones 1 and 2 in TC702).

2.1

Database in the MSC:

1. Creation of the origin code (ORIG2) of the cell:
CR INTCELL: LACOD=2500, CI=2555, ORIG2=20, BSCSPC=250, NETIND=NAT0, LMN=123F;
CR INTCELL: LACOD=2500, CI=2556, ORIG2=21, BSCSPC=250, NETIND=NAT0, LMN=123F;
CR INTCELL: LACOD=2500, CI=2557, ORIG2=22, BSCSPC=250, NETIND=NAT0, LMN=123F;
2. Creation of the mobile-specific zone points:
CR MZOPT: CODE=43-INAT, MZONO=1-21, CHTYPE=MOC, BILLING=AMA;
CR MZOPT: CODE=43-INAT, MZONO=1-22, CHTYPE=MOC, BILLING=AMA;
CR MZOPT: CODE=43-INAT, MZONO=2-20, CHTYPE=MOC, BILLING=AMA;
CR MZOPT: CODE=89-NAT, MZONO=1-21, CHTYPE=MOC, BILLING=AMA;
CR MZOPT: CODE=89-NAT, MZONO=1-22, CHTYPE=MOC, BILLING=AMA;
CR MZOPT: CODE=89-NAT, MZONO=2-20, CHTYPE=MOC, BILLING=AMA;

A30808-X3003-X458-1-7619

TC-010 1

OMN:SSS-TA

Operation Charging

LACOD = 2500
CI = 2556

ORIG2 = 21

BTS

MSC/VLR
TGNO = BSC

BSC

SPC = 200, NAT 0

VLRISD/SCCGPA digits:
491799900000

SPC = 250, NAT 0

BTS

CI = 2557

CI = 2555

PLMN A

ORIG2 = 22

ORIG2 = 20

BTS
CC
NDC
MCC
MNC

= 49
= 179
= 262
= 03

Fig. 5.2

TC-010 2

MOC to the fixed network

A30808-X3003-X458-1-7619

Operation Charging

TC-011

OMN:SSS-TA

Charge Registration of Mobile Internal Calls

For charge registration of a mobile-to-mobile call where the interrogation is performed by the MSC which
also serves the calling mobile subscriber (see Fig. 5.3), origin-dependent zone points have to be
created.
MCR data records are to be generated for the calls.

MML Command Overview

When creating the database for charge registration of mobile-to-mobile calls it must be taken into
account that these calls are routed via a loop LTG (Fig. 5.4 and OMN:SSS-RO).
1. Generation of MCR data records
Activation of the MCR feature (unless this was already done during installation this can be checked
with DISP IAFEAT):
DACT FNS: FNS=IA;
ACT IAFEAT: TYPE=MCR;
ACT FNS: FNS=IA;
Activation of MCR data record generation and zoning for the trunks groups between MSC and BSC
and the loop LTG:
CR TGRP: TGNO, OPMODE, ORIG1, GCOS=AMAREQD&ZON;
If the trunk groups have already been created, the modification is made with
ENTR TGDAT: TGNO, GCOS;
(This command is also valid for base station trunk groups!)
2. Creation of the origin dependency of the calls for charge registration (ORIG2)
CR TGRP: TGNO, OPMODE, ORIG2;
If the trunk groups have already been created, the modification is made with
MOD TGRP: TGNO, NORIG2;
3. Creation of the mobile radio-specific zone points
CR MZOPT: CODE=<digitscode type>, MZONO=<zoneORIG2ORIG2- position>, CHTYPE,
CHIT;
The zone points define how the charges for an outgoing call are to be registered according to the
dialed digits, the origin of the call, and the type of call (MOC or CF).
A prerequisite is that the corresponding mobile radio-specific tariffs, tariff categories and zones have
been created.
The PARAMETER BILLING specifies the type of charge registration. For generation of MCR data
records, BILLING=AMA must be set.

A30808-X3003-X458-1-7619

TC-011 1

OMN:SSS-TA

Operation Charging

A subscriiber

A
BTS

MSC/VLR
TGNO = BSC

BSC

SPC = 200, NAT 0

VLRISD/SCCGPA-digits:
491799900000

ORIG2 = 10

SPC = 250, NAT 0

ORIG1 = 50

BTS

B subscriber

CI = 2555

PLMN A

ORIG2 = 20

BTS
CC
NDC
MCC
MNC

= 49
= 179
= 262
= 03

Fig. 5.3

TC-011 2

Mobile internal call

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

MSC
SN

LOOP -LTG

TGNO=MICLPO

DIU1

DIU3
TGNO=MICLPI

TGRP1

ORIG1 = 60

BSSAP-LTG LTG
TGNO=BSC

BSC

DIU
ORIG2 = 10

SPC = 250, NAT 0

ORIG1 = 50

PCM system

Fig. 5.4
2

Use of the loop LTG in an MIC

Example
For charge registration of mobile internal calls (Fig. 5.3 and Fig. 5.4), zone points are to be created for
the dialed digits 0049179 and 0179. The zoning is to be origin-dependent..
Furthermore, the calls are to be registered by means of MCR.

2.1

Database in the MSC A:

1. Activation of MCR data record generation and zoning, and creation of the origin code for the trunk
group between MSC and BSC and the loop LTG:
CR TGRP: TGNO=BSC, OPMODE=BW, ORIG1=50, GCOS=AMAREQD&ZON, ORIG2=10;
CR TGRP: TGNO=MICLPO, OPMODE=OG, GCOS=LOOPSIGx&...;
CR TGRP: TGNO=MICLPI, OPMODE=IC, ORIG1=60, GCOS=LOOPSIGx&AMAREQD & ZON,
ORIG2=10;
2. Creation of the mobile-specific zone points:
CR MZOPT: CODE=49179-COMB, MZONO=1-10, CHTYPE=MOC, BILLING=AMA;

A30808-X3003-X458-1-7619

TC-011 3

OMN:SSS-TA

TC-011 4

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

TC-303

OMN:SSS-TA

Reverse Charging Service

The reverse charging service (RCS) enables the calling party to set up a call for which the called party
is charged. The called party must agree to accept the charges.The commands for creating RCS are
entered in the same order as for normal calls.

CODE
code point 8

zone point 9

DEST 6
ROUTE 7

TGNO 3

trunk 4

Fig. 5.5

3... 9 Creation sequence

Normal call processing

The following commands are required for administration of RCS calls:

1

Create LTUs
CR LTU: LTG = ... , LTU = 0 ... 3, TYPE = D30, APPLIC = CASCAS;

Activate DIUs
CONF DIU: LTG = ... , DIU = 0 ... 3, OST = ACT;

Create RCS trunk group

CR TGRP: TGNO = outgoing trunk group to DIU0, OPMODE = OG, GCOS = NOTDIAL & IDITIM0;
CR TGRP: TGNO = incoming trunk group to DIU0, OPMODE = IC, GCOS = PULSDIAL & AMAREQD
& NOZON[& PROP1][& PROP2][& PROP3], PREFIX = aaa;
whereby: PROP1 = AMA tickets for rejected connections,
PROP2 = acceptance by dialing a digit,
PROP3 = called number in AMA ticket does not contain the RCS access code,
aaa = 3 digits for code point of busy announcement (AN3).
This completes the RCS loop between DIU0 and DIU1. This loop contains the CODE for AN3. The
CODE is required for subsequent routing to AN3.
In the case of the loop between the DIUs for announcement control, the CODE is assigned for announcements AN1, AN2 and AN5.
CR TGRP: TGNO = trunk group for announcement control to DIU2 (AN1 und AN2),
OPMODE = BW, PREFIX = bbbccc;

A30808-X3003-X458-1-7619

TC-303 1

OMN:SSS-TA

Operation Charging

whereby: bbbccc = 3 digits for the code point of the A announcement and 3 digits for the code point of
the B announcement
CR TGRP: TGNO = trunk group for input control to DIU3 (AN5),
OPMODE = BW, PREFIX = ddd;
whereby: ddd = 3 digits for the code point of the acceptance announcement
This completes the loop between DIU2 and DIU3. A CODE was not assigned for AN4 as this must be
accessed later by means of an intercept code.
4

Create RCS lines

CR TRUNK: TGNO = outgoing trunk group to DIU0, EQN = a-b-c-d, LCOS = DIGSIG5 & NOTDIAL;
CR TRUNK: TGNO = outgoing trunk group to DIU1, EQN = a-b-c-d, LCOS = DIGSIG5 & NOTDIAL;
CR TRUNK: TGNO = outgoing trunk group to DIU2, EQN = a-b-c-d, LCOS = DIGSIG7;
CR TRUNK: TGNO = outgoing trunk group to DIU3, EQN = a-b-c-d, LCOS = DIGSIG7;

Activate the two ports (twice per port)

CONF PORT: LTG = ... , CHPOS = ... , OST = MBL;
CONF PORT: LTG = ... , CHPOS = ... , OST = ACT;

Create destination for RCS

CR DEST: DEST = RCS, TLIM = RELCLEA;

Create route for RCS

CR ROUTE: DEST = RCS, TGNO = outgoing trunk group, ROUTE = 1, EOS = SIGN, LNDES =
ANIRQD, SSDI = 1, DICON = ...+0;

Create code point for RCS

CR CPT: CODE = 8XX, DEST = RCS;

Create zone point for RCS

CR ZOPT: CODE = 8XX, ZOCHA = NOPULSE;
This completes the creation of routes for RCS. Announcement control is created in much the same way
as for normal call processing, except that the destination in this case is an announcement.

TC-303 2

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

CODE

code point 15

zone point 16

DEST 13

ROUTE 14
announcement
group 10

announcement
line 11

Fig. 5.6
10

10...16 Creation sequence

Call processing for announcements

Create announcement groups

CR ANGRP: TGNO = ANGRPx;
This command must be entered for announcements AN1 to AN5 (x=1...5.

11

Create announcement lines

CR ANLN: TGNO = ANGRPx, EQN = a-b-c-d, SEIZMX = 16;
whereby: x = 3,4 for announcements AN3 and AN4. These are to be heard by several subscribers.

12

Activate ports (twice per port)

CONF PORT: LTG = ... , CHPOS = ... , OST = MBL;
CONF PORT: LTG = ... , CHPOS = ... , OST = ACT;

13

Create destination for announcement AN3

CR DEST: DEST = AN3;

14

Create route for announcement AN3

CR ROUTE: DEST = AN3, TGNO = ANGRP3, ROUTE = 1, EOS = SIGN, LNDES = ANIRQD,
SSDI = 1, DICON = ...+0;

15

Create code point

CR CPT: CODE = aaa, DEST =AN3;
The three digits already entered for PREFIX CODE .

16

Create zone point

CR ZOPT: CODE = aaa, ZOCHA = NOPULSE;
The last four steps must be repeated for all announcements.

A30808-X3003-X458-1-7619

TC-303 3

OMN:SSS-TA

Operation Charging

Announcement AN4 (for rejected connections) is controlled by means of an intercept code.

NEWDEST
INCEPT 17
new CODE

CODE

code point 15

zone point 16

DEST 13

ROUTE 14
announcement
group 10

announcement
line 11
Fig. 5.7
17

10... 17 Creation sequence

Call processing for intercept codes

Create intercept code

CR INC: INCEPT = CALLREJ, INRES = NEWDEST, DEST = AN4;
if the intecept code is to be controlled with NEWDEST .
This completes the creation of announcements for RCS. The next step is to set the timer for RCS:

18

Period of time for acceptance (e.g. 5 sec):

MOD TIOUT: TIMER = 80, TIMVAL = 0-0-5-0;

19

Period of time for AN1 and AN2::

MOD TIOUT: TIMER = 80, TIMVAL = a-b-c-d;
TIMVAL must be set to the higher value of the announcements AN1 and AN2.

20

Period of time for AN5:

MOD TIOUT: TIMER = 80, TIMVAL = a-b-c-d;
TIMVAL must be set to the value of AN5.
Timers 80 and 81 need only be set if digital announcement systems are connected.

TC-303 4

A30808-X3003-X458-1-7619

Operation Charging

21

OMN:SSS-TA

AMA tickets for unsuccessful connections:

ENTR CDTDAT: MARKS = UCALLAMA;
In addition, the traffic to the announcements can be measured (in erlang) with REC ANGRP If the
measured values are too high, more trunks to the announcements can be created.

A30808-X3003-X458-1-7619

TC-303 5

OMN:SSS-TA

TC-303 6

Operation Charging

A30808-X3003-X458-1-7619

Operation Charging

OMN:SSS-TA

Abbreviations

AMA

automatic message accounting

AoC

advice of charge

AOCCHRG

advice of charge charging level

AOCINFO

advice of charge information level

APS

application program system

ASN.1

abstract syntax notation no 1

BSC

base station controller

BSSAP

base station system application part

BTS

base transceiver station

CAP

call processor

CC

country code

CF

call forwarding

CML

command manual

CP

coordination processor

CSC

combined switch center

CW

call waiting

ECT

emergency call trace

EDSS1

european digital signalling system no 1

ETC

earth terminal controller

FLAM

Frankenstein-Lidzba-Access-Method

FTAM

file transfer access and management

FTNO

forwarded to number

GMSC

gateway mobile services switching center

GP

group processor

GSC

gateway switching center

GSC

gateway switching center fr Iridium

GSM

global system for mobile communication

GSM

global system for mobile communications

HLR

home location register

IARA

interadministration revenue accounting

IARAMA

interadministration accounting with AMA

IARAMA

interadministration accounting with

statistics

IMEI

international mobile equipment identity

IMSI

international mobile subscriber identity

IN

intelligent network

ISDN

integrated services digital network

ISUP

ISDN user part

LAC

local area code

LTG

line trunk group

A30808-X3003-X458-1-7619

AP 1

OMN:SSS-TA

Operation Charging

MCC

mobile country code

MCR

mobile call record

MFC

multi frequency code

MML

man machine language

MNC

mobile network code

MOC

mobile originating call

MS

mobile station

MSC

mobile services switching center

MSISDN

international mobile station ISDN number

MSRN

mobile station roaming number

MTC

mobile terminating call

NDC

national destination code

OMT

operation and maintenance center

PABX

private automatic branch exchange

PAD

packet assembly/disassembly facility

PAM

primary access method

PLMN

public land mobile network

PSDN

packet switched data network

PSTN

public switched telephone network

SAM

sequential access method

SCI

subscriber controlled input

SIM

subscriber identity module

SMS

short message services

SS

Supplementary Service

TUP

telephone user part

VLR

visitor location register

VMSC

visited mobile services switching center

WLL

wireless local loop

AP 2

A30808-X3003-X458-1-7619