siemens d900 1800 charging

Operation

Charging

OMN:SSS-TA

A30808-X3003-X458-2-7619

AD - 2 A30808-X3003-X458-2-7619

OMN:SSS-TA Operation Charging

Copyright (C) Siemens AG 1996

Issued by the Public Communication Network GroupHofmannstraße 51D-81359 München

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

! Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of theparts can also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in prop-erty 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 theapplicable safety standards.

OMN:SSS-TA

A30808-X3003-X458-2-7619 AD – 3

Operation Charging

IssuesNote on the change indication:

The change indications for a title marked as issue 1 refer to the previous version. Thechange indications for a title with an issue greater than 1 refer to the preceding issue.

Change indications:

N = new; G = modified; 0 = deleted;

Title Issue Page(s)

Administration Section (AD) 2 AD - 1. . . . . AD - 8 GIntroduction (IN) 2 IN - 1. . . . . . IN - 92 GTask List (TL) 1 TL - 1. . . . . TL - 10Task Summary Lists (TS) 1 TS - 1. . . . . TS - 2

1 TS-300 - 1. .TS-300 - 11 TS-302 - 1. .TS-302 - 11 TS-305 - 1. .TS-305 - 11 TS-307 - 1. .TS-307 - 11 TS-500 - 1. .TS-500 - 11 TS-501 - 1. .TS-501 - 11 TS-502 - 1. .TS-502 - 11 TS-504 - 1. .TS-504 - 11 TS-505 - 1. .TS-505 - 11 TS-506 - 1. .TS-506 - 11 TS-510 - 1. .TS-510 - 11 TS-511 - 1. .TS-511 - 11 TS-512 - 1. .TS-512 - 11 TS-513 - 1. .TS-513 - 11 TS-530 - 1. .TS-530 - 11 TS-531 - 1. .TS-531 - 11 TS-532 - 1. .TS-532 - 11 TS-600 - 1. .TS-600 - 11 TS-601 - 1. .TS-601 - 11 TS-602 - 1. .TS-602 - 11 TS-603 - 1. .TS-603 - 11 TS-604 - 1. .TS-604 - 11 TS-605 - 1. .TS-605 - 11 TS-606 - 1. .TS-606 - 11 TS-607 - 1. .TS-607 - 11 TS-608 - 1. .TS-608 - 11 TS-721 - 1. .TS-721 - 11 TS-731 - 1. .TS-731 - 11 TS-732 - 1. .TS-732 - 11 TS-733 - 1. .TS-733 - 11 TS-740 - 1. .TS-740 - 11 TS-741 - 1. .TS-741 - 11 TS-831 - 1. .TS-831 - 11 TS-840 - 1. .TS-840 - 1

Task Procedures (TP) 1 TP - 1. . . . . TP - 21 TP-301 - 1. .TP-301 - 41 TP-302 - 1. .TP-302 - 41 TP-501 - 1. .TP-501 - 21 TP-503 - 1. .TP-503 - 21 TP-511 - 1. .TP-511 - 2


AD – 4 A30808-X3003-X458-2-7619

1 TP-513 - 1 . TP-513 - 21 TP-523 - 1 . TP-523 - 21 TP-524 - 1 . TP-524 - 21 TP-530 - 1 . TP-530 - 21 TP-545 - 1 . TP-545 - 21 TP-550 - 1 . TP-550 - 41 TP-600 - 1 . TP-600 - 21 TP-603 - 1 . TP-603 - 21 TP-701 - 1 . TP-701 - 21 TP-702 - 1 . TP-702 - 21 TP-703 - 1 . TP-703 - 41 TP-704 - 1 . TP-704 - 21 TP-705 - 1 . TP-705 - 41 TP-706 - 1 . TP-706 - 21 TP-707 - 1 . TP-707 - 21 TP-720 - 1 . TP-720 - 21 TP-721 - 1 . TP-721 - 21 TP-722 - 1 . TP-722 - 21 TP-761 - 1 . TP-761 - 21 TP-767 - 1 . TP-767 - 21 TP-769 - 1 . TP-769 - 21 TP-770 - 1 . TP-770 - 21 TP-811 - 1 . TP-811 - 21 TP-820 - 1 . TP-820 - 41 TP-822 - 1 . TP-822 - 21 TP-824 - 1 . TP-824 - 21 TP-830 - 1 . TP-830 - 21 TP-900 - 1 . TP-900 - 61 TP-905 - 1 . TP-905 - 41 TP-910 - 1 . TP-910 - 41 TP-915 - 1 . TP-915 - 41 TP-931 - 1 . TP-931 - 21 TP-933 - 1 . TP-933 - 21 TP-934 - 1 . TP-934 - 2

Task Complexes (TC) 1 TC - 1 . . . . .TC - 21 TC-001 - 1 . TC-001 - 21 TC-002 - 1 . TC-002 - 21 TC-009 - 1 . TC-009 - 21 TC-010 - 1 . TC-010 - 21 TC-011 - 1 . TC-011 - 41 TC-303 - 1 . TC-303 - 6

Appendix (AP) 1 AP - 1 . . . . .AP - 2

This document consists of a total of 268 pages.

OMN:SSS-TA

A30808-X3003-X458-2-7619 AD – 5

Operation Charging

Contents

1 Introduction (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-11.1 PLMN Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-11.1.1 Administration of Weekday Categories and Holidays . . . . . . . . . . . . . . . IN-21.1.2 Charging with MCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-31.1.2.1 Types of Calls requiring Generation of MCR . . . . . . . . . . . . . . . . . . . . . IN-31.1.3 Mobile Call Records: Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-131.1.4 Hot Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-171.1.5 Zones and Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-171.1.5.1 Zoning for Originating Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-201.1.5.2 Tariffs for Mobile Terminating Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-231.1.5.3 Surcharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-241.1.5.4 Call Attempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-241.1.5.5 Subscriber Controlled Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-241.1.5.6 Advice of Charge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-241.1.6 Call Charge Registration in the Intelligent Network (IN) . . . . . . . . . . . . IN-261.1.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-261.1.6.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-271.1.6.3 Charge Registration for the IN Services: General. . . . . . . . . . . . . . . . . IN-281.1.6.4 Administration by MML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-281.2 Interadministration Revenue and Statistics (IARA). . . . . . . . . . . . . . . . . IN-311.2.1 IARA Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-331.2.2 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-341.2.3 IARSTAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-391.2.3.1 Registration Counters and Tariff Zones . . . . . . . . . . . . . . . . . . . . . . . . . IN-391.2.3.2 Functional Sequence of IARSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-411.2.3.3 IARSTAT Post-Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-411.2.3.4 Example of an IARSTAT Application . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-441.2.4 IARAMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-501.2.4.1 MML commands for IARAMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-501.2.4.2 Example of an IARAMA Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-511.2.4.3 Saving the Registered Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-531.2.5 Regeneration of the IARA database . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-531.2.6 Procedure after Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-531.3 Trunk Meters and Statistics Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-541.3.1 Trunk Meters for Trunk Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-541.3.2 Statistics Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-551.3.3 Statistics Meter Switchover Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-551.4 Charging of Wired Subscribers of a Combined

Switching Center (CSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-571.4.1 Subscriber Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-581.4.1.1 Tariff Administration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-581.4.1.2 Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-591.4.1.3 Tariff Sequences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-601.4.1.4 Tariff Switchovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-621.4.1.5 Weekday Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-631.4.2 Zone Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-64


AD – 6 A30808-X3003-X458-2-7619

1.4.2.1 Creation of Zone Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-651.4.3 Charge Band Message and Zone Traffic Type . . . . . . . . . . . . . . . . . . . IN-681.4.4 Supplementary Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-691.4.4.1 Registration of charges for the input of supplementary

services (facility input FAI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-691.4.4.2 Registration of charges for the usage of supplementary

services (facility usage FAU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-691.4.4.3 Account suspensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-701.4.5 Counter Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-701.4.5.1 Creation of Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-701.4.5.2 Creation of Backup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-711.4.5.3 Billing File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-711.4.5.4 Counter Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-721.4.6 Subscriber Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-741.4.7 Statistics Meters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-741.4.7.1 Use of Statistics Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-741.4.7.2 Statistics index Structure and Selection of Currently

Active Statistics Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-751.4.7.3 Statistics Meter Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-781.4.8 Trunk Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-781.4.9 Individual Call Data Administration Feature . . . . . . . . . . . . . . . . . . . . . . IN-781.4.9.1 Automatic Message Accounting (AMA) . . . . . . . . . . . . . . . . . . . . . . . . . IN-801.4.9.2 Detailed Billing (DEB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-811.4.9.3 Meter Observation (MOB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-821.4.9.4 Preventive Meter Observation (PMOB) . . . . . . . . . . . . . . . . . . . . . . . . . IN-831.4.10 Call Charge Registration in the Intelligent Network (IN). . . . . . . . . . . . . IN-831.4.10.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-831.4.10.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-851.4.10.3 Charge Registration for the IN Services: General . . . . . . . . . . . . . . . . . IN-861.4.10.4 Administration by MML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-871.4.11 Reverse Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-891.5 Notes on the Iridium Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IN-91

2 Task List (TL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-12.1 Selection of Charging Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-12.2 PLMN Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-12.2.1 Holiday and Weekday Category Administration. . . . . . . . . . . . . . . . . . . . TL-12.2.2 Automatic Message Accounting Administration . . . . . . . . . . . . . . . . . . . . TL-12.2.3 Administration of Zones and Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-22.2.3.1 Administration of Zones and Tariffs for Mobile Originating Calls,

Call Attempts, Call Forwarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-22.2.3.2 Administration of Tariffs for Mobile Terminating Calls (PLMN Tariffs) . . . TL-22.2.4 Charge Registration in the Intelligent Network (IN) . . . . . . . . . . . . . . . . . TL-22.2.5 Administration of Control Meters for Connection Groups. . . . . . . . . . . . . TL-22.2.6 Administration of Statistics Meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-32.3 Interadministration Revenue Accounting (IARA) Administration . . . . . . . TL-32.3.1 IARSTAT Destination and IARSTAT Origin Name Administration. . . . . . TL-32.4 Charging of Wired Subscribers of a Combined

OMN:SSS-TA

A30808-X3003-X458-2-7619 AD – 7

Operation Charging

Switching Center (CSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-52.4.1 Subscriber Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-52.4.2 Zone Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-52.4.3 Charge Band Messages and Zone Traffic Types . . . . . . . . . . . . . . . . . . TL-62.4.4 Subscriber Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-62.4.5 Meter Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-72.4.6 Subscriber Meters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-72.4.7 Statistics Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-72.4.8 Trunk Meters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-82.4.9 Automatic Message Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-82.4.10 Charge Registration in the IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-82.4.11 Reverse Charging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-92.4.12 Subscriber's Private Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TL-9

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

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

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

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


AD – 8 A30808-X3003-X458-2-7619

A30808-X3003-X458-2-7619 IN – 1

Operation Charging OMN:SSS-TA

1 Introduction (IN)The tariff and charging administration register comprises two large tariff establishmentand 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 aPLMN because both charging types can be applied for the operation of a combinedswitching center.

A CSC is a network node which can implement the function of a PLMN and that of aPSTN 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 followsthe numbering scheme of the PSTN.

– Wire-line subscribers: Both wire-line subscribers and PABXs can be connected tothe MSC.

WLL subscribers are mobile subscribers who only differ from "normal" mobilesubscribers 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 mobilesubscribers.

Logging the charges to the individual subscribers is described in two different sectionsTN subscribers.The charging between different administrations is described for both types of chargingin Section IARA.

For the Iridium project please refer to the notes in Section 1.5

1.1 PLMN ChargingCharges for mobile subscribers generally consist of a fixed network access componentand a variable network utilization component. Network utilization charges are registeredon 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 Recommenda-tions of the Global System for Mobile Communication) subscribers are registered exclu-sively 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 thecall, as well as the calling and called party numbers. If mobile tariffs have been estab-lished, the record can also contain this information.

MCR are generated at the MSC that controls the related call.

IN – 2 A30808-X3003-X458-2-7619


Only valid for Iridium: MCRs are generated at the MSC (i.e. GSC) that controls therelated call. This also applies if after sending of the correlation data message a connec-tion is switched entirely within the satellite network. In this case, from the viewpoint ofthe MSC, the connection remains intact but is "muted" while the earth terminal controllerETC monitors the connection via satellite (see OMN:SSS-CCS7).

Depending on the particular project, records can be generated for the following types ofcalls:– 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 weekdaycategories and holidays.

1.1.1 Administration of Weekday Categories and HolidaysHow a call is charged generally depends on the day of the call and the time of day. Thetime of day is determined by the system time (see OMN:SSS-SY). The charging-rele-vant time intervals of a day are set with tariff categories (ENTR MTARCAT). Holidaysare marked by allocating a holiday category (e.g.FULL HOLIDAY) to the correspondingdate. These allocations form a holiday calendar. A distinction can be made betweenfixed and variable holidays. The allocation of weekday categories and fixed and variableholidays 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 mobilecharging feature (Advice of Charge) and as a common calendar group (e.g. for chargingof wire-line subscribers of a CSC, for IARA or for periodic execution of command files orroute switching). A calendar group consists of the allocation of the individual days of theweek to a weekday category, a fixed holiday calendar and a separate calendar for thevariable holidays each year.

Apart from being dependent on the time of day, call charging is also dependent on theweekday 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 cate-gory ”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 aweekday category. This allocation has top priority.

A30808-X3003-X458-2-7619 IN – 3


1.1.2 Charging with MCRWhen using the mobile communication network, MCR are generated at the MSC. Theserecords are used to register the total charges of the served mobile subscriber within theframework of data post processing. The information needed to handle charging for theindividual types of calls is stored in the GPs of all LTGs. If changes occur in the mannerin which charges are registered (e.g. due to a change in tariffs after a given time limithas been reached), the CP punctually transmits the new information to all GPs. For eachcall, the GP collects the current time, the duration of the call and the tariffs used. All othercharging data are registered in the CP. After a handover, the above-mentioned chargingdata are registered in the anchor LTG, i.e. the BSSAP-LTG which established theconnection 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 ofcalls 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 MODTIOUT). These intermediate data records are numbered consecutively so that the firstdata record is called "first intermediate" and the last "last". If the service is changedduring 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 MSCrequires 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 transitcalls

– 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 MCRBelow are some example situations in which MCR are generated. The basic assumptionin each description is that all participating parties are located (visiting or home) indifferent networks. No inter-PLMN interrogations are executed in these examples (seeOMN:SSS-RO); the generation of (optional) interrogation records is not explicitly indi-cated. 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 notaffect the indicated records.

IN – 4 A30808-X3003-X458-2-7619


Mobile Originating Call

If a mobile originating call is successful, i.e. answered (i.e. the calling party is a mobilesubscriber and the called party is a fixed network subscriber or a subscriber of a otherPLMN), charging is performed at the visited MSC (VMSC) of the calling mobilesubscriber. The accumulated charging data contain information on the connection fromthe location of the served mobile subscriber to the called party (see Fig. 1.1 for call toPSTN).

The MCR generated at the visited MSC of the calling party contains the followingspecific information:– call type/transaction type: MOC– served mobile identity: IMSI, MSISDN, IMEI of the calling mobile subscriber– other party: number of the called subscriber

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), anMCR is generated at the visited MSC for the called mobile subscriber. The collectedcharging data contain information on the call's destination component, otherwise desig-nated as the mobile terminating component. This mobile terminating component isdependent on the visited MSC and the HLR of the served mobile subscriber (seeFig. 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 specificinformation:– 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)

Signaling

Called party

VMSC

GMSC

PLMN

Calling party PSTN

Exch

Speech and

signaling

A30808-X3003-X458-2-7619 IN – 5


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 originatingcall. For the called mobile party, an MCR is generated as it is for a mobile terminatingcall (see Fig. 1.3).

The MCR generated at the visited MSC of the served mobile subscribers contain thefollowing 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

Speech and

signaling

Signaling

Calling partyCalled party

PSTN

ExchHLR GMSC

VMSC

PLMN

IN – 6 A30808-X3003-X458-2-7619


Fig. 1.3 Mobile-to-mobile call

Call Forwarding Unconditional

When call forwarding unconditional is activated for a mobile subscriber, the HLRanswers the routing information interrogation via the gateway MSC when the connectionis a mobile terminating call. The HLR therefore transmits to the GMSC the number ofthe party to be forwarded to. This message also contains the information that a callforwarding transaction is being performed.

A mobile terminating call can be forwarded to another mobile subscriber in a PLMN aswell as to a fixed network subscriber in the PSTN. Two related examples are providedbelow (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 infor-mation:

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: –

Visited

PLMN of the

calling party

Speech and

signaling

SignalingCalling party

Visited PLMN of the

B subscriber

VMSC

Home PLMN of the

called party

HLRGMSC

PSTNVMSCGMSC

Called party

Exch Exch Exch

GMSC

A30808-X3003-X458-2-7619 IN – 7


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: –

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 thefollowing 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)

Party for-

warded to

Home and visited

PLMN of the party

to be forwarded to

Home PLMN of the

called party

HLR

GMSC

Calling party

Visited PLMN of the

calling party

VMSC

HLR

GMSC

VMSC

Exch Exch Exch

PSTN

GMSC

Speech and

signaling

Signaling

IN – 8 A30808-X3003-X458-2-7619


Fig. 1.5 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 MSCof the called party and forwarded from there to a third party, provided that the require-ment for the supplementary service has been met. Calls can be forwarded to anothermobile subscriber or to a subscriber in the fixed network.

Example: All three parties are mobile subscribers (see Fig. 1.6). The generated MCRcontain than the following specific information:

Home PLMN of the

called party

HLRGMSC

Exch

Party forwarded toCalling party PSTN

Speech and

signaling

Signaling

A30808-X3003-X458-2-7619 IN – 9


Fig. 1.6 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 depen-

dent)– supplementary service: –

Forwarded-to

party

Visited PLMN of the

party forwarded to

Home PLMN

of the party

forwarded to

Home and

visited PLMN

of the called party

Visited PLMN of the

calling party

GMSC

GMSC GMSC

GMSC

Exch Exch

Exch ExchPSTN

VMSC

Calling party

HLR

VMSC

Called party

HLR

VMSC

Speech and

signaling

Signaling

IN – 10 A30808-X3003-X458-2-7619


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 SCI‘s normallyhandeled in the MSC, this means also those SCI‘s which are negative aknowledgedfrom 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 carryingout a routing-information interrogation to the HLR. For this purpose, the following codepoints 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 thecalled 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 performsthe 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 unsuc-cessful call attempts (MOD MSERVOPT). This type of record can also be generatedwhen the call attempt cannot be charged.The data records correspond (up to the connection type) to those successful connec-tions.Generation of the data record starts for MOC after recognition of a valid B directorynumber. 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 subscriberanswers.

A30808-X3003-X458-2-7619 IN – 11


Short Message Service

As soon as a mobile subscriber receives or transmits a short message, an MCR can begenerated at his visited MSC (depending on the project). It is also possible to determineon a project-specific basis whether these records are to be generated for successfulSMS transactions only or also for those which were unsuccessful.

SMS records are similar to those for speech or data connections, but they contain thefollowing additional information.– service center address– transmission result

If the SMS is being used in parallel with a speech or data connection, two separate datarecords are created.

Transit Calls

MCR can also be generated for transit calls (depending on the projectMOD MSERVOPT), provided that the incoming trunk group has been created withGCOS=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 inthe area of his home MSC and neither interrogation nor call forwarding are performedby the home MSC.An MCR for transit calls is generated at the home MSC only when no other mobile MCRis generated.

When zoning is entered on the incoming trunk also the ZOPT has to be created withBILLING=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 onlywhen the announcement group (CR ANGRP) has been created with GCOS=CHAR-GABL. (Project dependend also for nonchargeable Announcements possible).

In-call announcements, i.e. announcements during calls in progress (e.g. in the case ofCall 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 inprogress 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 tomobile 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 – Bconnection is not closed, but continued as if there were no interruption. Only the nameof the supplementary service in use (Call Hold) is registered. The new connectionbetween mobile subscribers B and C is charged as usual. As a result, two data recordsare 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

IN – 12 A30808-X3003-X458-2-7619


– 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 callwhile he is busy. The called mobile subscriber can then answer, reject or ignore theincoming call.

Generation of MCR:If mobile subscriber B, during a call with mobile susbcriber A, receives notice of CallWaiting from mobile subscriber C, the supplementary service used (CW) is registeredregardless of whether the incoming call is answered, rejected or ignored. The onlyprerequisite for this information to be registered is that mobile subscriber B is in theprocess of a call.

Assuming that mobile subscriber A initiated the call to mobile subscriber B, the followingrecords 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 CallHold 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 speechconference with up to 5 other subscribers.In this case, separate MCR are generated for each individual connection. The contentsare the same as for normal MOCs or MTCs. The supplementary service used is regis-tered 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 MMLcommands 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 busi-ness 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 supple-mentary services.Call charge registration is also separate for each subscriber. This means that recordsare 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).

ExampleA double mobile subscriber with1.IMSI-1: not activeMSISDN-1, teleservice "Telephony"

A30808-X3003-X458-2-7619 IN – 13


2.IMSI-2: activeMSISDN-2, teleservice "Telephony" and supplementary service "Call ForwardingUnconditional" active with FTNO (the number forwarded to) in the PSTN is called onthe MSISDN-1.This MTC triggers a switchover to the active IMSI (IMSI-2), whereby the callforwarding to the specified FTNO becomes effective. Then the MSISDN-1 (numberdialed) appears in the MCR, and the FTNO is registered in the data field "othersubscriber". Consequently, the MSISDN-1 linked to the IMSI-1 and the FTNO linkedto 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. Thepersonal voice mail box is a computer box in the PLMN (voice mail system VMS) andrepresents a kind of call answering device in the PLMN. The mobile subscriber can callup 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 subscribercan 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 ISDNprimary access rate or basic access.

Call charge registration is carried out in the MSC to which the digital subscriber and thePABX are connected. One can select the kind of charging (PLMN or PSTN) for all fixsubscribers 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 zonepoint 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 inaddition a code, which allows the call to be allocated to a PABX-subscriber or to a digitalsubscriber, 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: AdministrationThe 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)

IN – 14 A30808-X3003-X458-2-7619


– 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 duplicatedmagnetic disk file IA.ICMCR as soon as the data buffer is full. At least two data buffersare 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 datacan also be dumped from the CP data buffer to the magnetic disk file manually by MMLcommand (TRANS BUFFER).

The MCR magnetic disk file is a duplicated cyclic file. When the capacity level of the filereaches a predetermined threshold (e.g. 75%), an alarm is indicated at the systempanel. A copy file should now (at the very latest) be initiated and afterwards, the origi-nating 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 lostafter such a selective transfer, the last copy of an MCR is automatically copiedcompletely. This means that selective transfer of billing data is only possible if thenumber of copies required, specified in SET FGRPATT using SAFCOP, is greater thanone. So as to ensure that the parameter SAFECOP is observed during selective filetransfer by FTAM, the MCR can only be reset explicited with the commandREL CYCFILE, even from a remote terminal.

Contents of Mobile Call Records

The charge data collected during the call are formatted in a precisely predeterminedmanner and stored in this form as an MCR. The content of the MCR can be created inthe 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, subscribercontrolled input).In Table 1.1 (example for a MCR - project dependend), the fields foreseen for eachparticular type of record are marked with an ”x”; fields marked with a ”–” do not apply. Ifinformation is not available for a certain field that should actually be filled (e.g. thenumber of the calling party is unknown at the MTC), a ”filler” is provided to preserve theinternal 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).

A30808-X3003-X458-2-7619 IN – 15


MCR content MOC MTC Inter-rogation

CF SCI SMS Emerg.calltrace

Tran-sit

Record type (e.g. single record) ×/+ ×/+ x x x x x x

Call type (e.g. MOC, interrog.) ×/+ ×/+ x x x x x x

Time quality (secure, insecure) ×/+ ×/+ x x x x x x

IMSI (of served subscriber) x x x x x x x –

MSISDN (of served subscriber) ×/+ ×/+ x x – x x –

IMEI (of served subscriber) x x – – – – x –

MSRN (* if VMSC=GMSC) – ×(*) x – – – – –

Transaction identity (differentiatingbetween parallel transactions of an MS)

x x – x x x x –

Other number (calling party for transit) – – – – – – – x

Other party (e.g. no of calling party at MTC) ×/+ ×/+ x x – – x x

SPC or name of registering MSC ×/+ ×/+ – x x x x x

SPC of originating/terminating MSC x x – – x x x –

Cell identity x x – – x x x –

Incoming trunk group x x x x – – x x

Outgoing trunk group x x x x – – – x

Start of recording: date, time ×/+ ×/+ x x x x x x

Call duration ×/+ ×/+ x x – – – x

Teleservice (e.g. telephony) ×/+ ×/+ – x x x x –

Bearer service (e.g. data transmission) x x – x x x – –

Transmission type (full rate/half rate) x x – – – – – –

MS classmark x x – – x x x –

AOC (parameters for tariffs utilized) x x – – – – – –

Charge type (charged, non-chargeable) x – – x – – – –

Charge units x x – x x x – –

Tariff category x – – x x x – –

Charge registering disturbance x – – x x x – –

Reason for call disturbance ×/+ ×/+ – x – – – x

Third party – – – x – – – –

Supplementary service x x – x x – – –

MS access rate (data transmission rate) x x – x x x – –

Address of service center – – – – – x – –

Tab. 1.1 Example of MCR(+ applies to PBX subscribers)

IN – 16 A30808-X3003-X458-2-7619


Mobile Call Records: project-specific processing

In the MCR, the system ensures that certain standard information is available. Justwhich information is used to calculate subscriber charges depends on the individualproject. As a consequence, the MCR s undergo project-specific formatting (client recordformatting). This formatting contains only the data actually needed for data post-processing or data required by the network provider for other reasons. The actual refor-matting is done automatically during the copying process (e.g. from magnetic disk tomagnetic tape) or after storing e. g. for use of FLAM. The files thus copied and formattedare then sent to data post-processing centers, where the charges are registered for theindividual mobile subscribers.

FLAM compression for billing files

A reduction in the time for transmitting billing files to a post-processing center can beachieved by compression with the project-dependent FLAM (Frankenstein LidzbaAccess 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 continuouscompressed (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 orderto 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, parameterACTION).The originating file is released after compression (ACTION=REL) even if several storecopies 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 iscreated with CR FGRP) must be allocated to the "FLAM" file before the start of trans-mission of data collected in the MCR file.Backup files to be transmitted as compressed files must be allocated to the copyingservice MUUTJ. The names of the backup files must contain the original file name (e.g.B.SET FGRPATT:FGRP:BU.IA.ICMCR, PRNAME=MUUTJ).

A30808-X3003-X458-2-7619 IN – 17


1.1.4 Hot OperationThe term hot operation encompasses all cases in which MCR are generated supple-mentarily and/or formatted during an ongoing call or immediately after its terminationand 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 authorizedsubscriber are formatted immediately after call termination and sent to the appropriateprocessing center. The MCR is subsequently marked at the MSC as having beensuccessfully or unsuccessfully transmitted. The MCR is then further processed at theMSC as described above.

This treatment of billing data consequently does not change ”normal” billing conductedvia MCR. It does, however, additionally enable the network provider to rapidly compiledetailed 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 implementedand 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 appropriateprocessing center. This record contains essential information concerning the identity ofthe 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 termi-nated, 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 acti-vating the emergency call key at the mobile station or because the number dialed hasbeen 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 datarecord 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 withACT IAFEAT).

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

IN – 18 A30808-X3003-X458-2-7619


services utilized, etc.). The charges are then calculated in data post processing ordirectly 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 ofcharge units in relation to the duration of the call. These calculated charge units arestored 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 calcu-late the charge units autonomously and display an advice of charge to the mobilesubscriber.

For administration of call charge registration, a distinction must be made among themobile-specific calls, such as mobile originating calls (including call forwarding) ormobile 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 servedmobile subscriber, the tariff for MOCs includes other parameters such as call origin,dialed digit combination and the time of day and week.

Fig. 1.7 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 deter-mined by means of the following parameters:E1UPTI number of charge units per time intervalE7SPITI duration of initial time interval in secondsE2SPTI 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, calcu-

lated from the other parameters)

Time

E2SPTI

E2SPTI

E2SPTI

Chargeunits

E1UPTI

E1UPTI

E1UPTI

E1UPTI

E4INU

1.Start of call

2. 3. 3. 3. 4.Calltermination

E7SPITI

A30808-X3003-X458-2-7619 IN – 19


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) isstored in a counter. At the same time, a timer is started, whose value is defined inE7SPITI. (If E7SPITI=0, E2SPTI is used instead.)

2. When this timer expires, the number of charge units defined in E1UPTI is added tothe current counter. At the same time, a timer is started, the value of which is definedin E2SPTI.

3. When this timer expires, the number of charge units defined in E1UPTI is added tothe current counter. At the same time, the timer is restarted. The proceduredescribed 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 totalnumber of charge units is calculated for that particular call. (This multiplication is notshown 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:

When entering the appropriate MML command, it is important to bear in mind that theparameter 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 durationof the call:

In the case of unsuccessful call attempts, the charge is calculated from the product ofthe basic charge determined with E4INU by the scaling factor E3SCF.

In case of charging troubles for mobile subscribers, the LTGs might not be loaded withcorrect charging information. The reloading of the LTG can be obtained by entering thecommand MOD PLMNTAR without parameter specification.

E1UPTI 1 unit/intervalE7SPITI 20 seconds/intervalE2SPTI 15 seconds /intervalE4INU 2 unitsE3SCF 2

Calldura-tion

(sec.)

Charge units based on Charge

units(total)

E4INU E7SPITI E2SPTI

10 2 0 0 4

20 2 1 0 6

30 2 1 0 6

60 2 1 2 10

90 2 1 4 14

120 2 1 6 18

Tab. 1.2 Charge units dependent on call duration

IN – 20 A30808-X3003-X458-2-7619


1.1.5.1 Zoning for Originating Calls

Zoning for Wired and PABX Subscribers

The generation of MCR (if PLMN charging is used - project dependend) for certain digitcombinations 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=AMAmust be created.

Zoning for Mobile Originating Calls and Call Forwarding

For outgoing calls (mobile originating calls, MOC) and the ”forwarded part” of a divertedcall (i.e. the part between the original called mobile subscriber and the forwarded-tosubscriber), tariffs and zones are administered in the same manner. The same tariffsand/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 relevantprerequisites have been fulfilled. A tariff of this kind consists of parameters E1UPTI,E2SPTI, E4INU and E7SPITI. addition, the system allocates parameter E3SCF to thistariff. 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 determinewhich 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 beadministered:• 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 timesmay be allocated to one tariff category. A weekday category may have up to 30different switchover times.

• mobile zone: A mobile zone allocates a tariff category to call types featuring differentnetwork utilization. Tariff categories can be allocated for the following call typeswithin 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 combina-tion 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, indi-vidual radio cells can also be allocated an origin code (ORIG2), which is used for chargecalculation 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, theORIG2 value entered for the trunk group between BSC and MSC is overwritten by theORIG2 of the cell during zoning in the MSC.

A30808-X3003-X458-2-7619 IN – 21


So as to ensure accurate charge calculation, there must be zone points for all digitcombinations that can be dialed and are required for interrogation. It is not necessary todefine a separate zone point for each code point (or vice versa). However, it must beensured 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) andcode type

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 discriminationdigit 0 and the international traffic discrimination digit 00).

As the subscribers of the own PLMN can be reached by dialing a directory number withor 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 trafficdiscrimination 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 thepacket network) includes only the circuit-switched part that leads to the PAD, and notthe use of the PSDN itself.

Zones 0 and 127 have a special position and cannot be administered. Zone 0 isreserved for no charge calls, and zone 127 is reserved for calls that are to be zoned inthe next node.

For each tariff category, the system automatically selects the tariff producing the lowestnumber of charge units at a call duration of 2 minutes. These so-called ”lowest” tariffsare stored in an internal table. This table is always updated when another tariff becomesthe ”lowest” tariff for a given category due to a change in the created tariffs and/or tariffcategories. The ”lowest” tariffs are transmitted by the CP to all GPs that might be inca-pable 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).

CODE TYPE OF CODE Zone point

49179 INAT 0049179

179 NAT 0179

0012345 UNK 0012345

49179 COMB a) CC is the own country code:

00491790179

b) CC is not the own country code

0049179049179

Tab. 1.3 Example of mobile-specific zone points

IN – 22 A30808-X3003-X458-2-7619


This prevents individual calls from being overcharged. As soon as the exceptional statushas been terminated, the ”lowest” tariffs are automatically replaced by the tariffs that arevalid at that particular time.

It is generally recommended that a switchover time be foreseen at midnight (00:00hours) for each weekday category. Since switchover times are always entered for a tariffcategory, the tariff that was valid for the previous day will continue to be valid up untilthe first switchover time of the next day. If there is no switchover at midnight, chargesregistered 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 firstswitchover on Monday. As soon as a variable holiday is allocated to the ”FULLWEEKEND” weekday category, the weekend tariff will initially be valid for the nextworking 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; Saturdayand Sunday shall be assigned the HALF WEEKEND or FULL WEEKEND categories. Atotal 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=262–03, 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 of1. With this command, a multiplier must be created for the charge units for eachPLMN whose mobile subscribers may utilize sevices. (If charges are also to beregistered for mobile terminating calls, the command ENTR PLMNTAR must beentered with additional parameters that define the accompanying tariffs.)

– ENTR MTARCAT: MTARCAT=10,SWTAR=00–00–1–WO & 00–00–1–EH &

00–00–1–EF & 08–00–3–WO &08–00–3–EH & 08–00–3–EF;

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=00–00–2–WO & 00–00–2–EH &

00–00–1–EF & 08–00–4–WO &09–00–5–EH & 09–00–5–EF;

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. FromMonday through Friday there is a switchover to tariff 4 at 8 a.m. and to tariff 5 at 9a.m. on Saturdays and Sundays.

– CR MZONE: ZONO=1, FULL=10;Result: In zone 1, tariff category 10 is used to calculate full transmission ratecharges.

– CR MZONE: ZONO=2, FULL=10, ATTEMPT=20;Result: In zone 2, tariff category 10 is used to calculate full transmission rate

A30808-X3003-X458-2-7619 IN – 23


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

– CR MZOPT: CODE=49179–COMB, MZONO=1, CHTYPE=MOC;Result: For every mobile originating call to a number beginning with the digitsequence 0049179 or 0179, charges are calculated (for full rate transmission)according to the conditions defined in tariff category 10. Unsuccessful call attemptsare not charged.

– CR MZOPT: CODE=123–UNK, MZONO=2, CHTYPE=MOC;Result: For every successful mobile originating call to a number beginning with thedigit sequence 123, charges are registered according to the conditions defined intariff category 10. Unsuccessful call attempts to numbers beginning with the digitsequence 123 are also chargeable –the charges are calculated according to theconditions defined in tariff category 20, i.e. the number of charge units indicated inparameter 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 ina other node, ORIG2 ... by means of the feature Subscriber Dependent Digit Processingand Feature Control (SDDPFC) as shown in the OMN:SSS-RO.

1.1.5.2 Tariffs for Mobile Terminating CallsCharge treatment for mobile terminating calls (MTC) depends solely on the home PLMNof the served mobile subscriber. A specific tariff must be created for every PLMN whosemobile subscribers may utilize services. A tariff for mobile terminating calls must also becreated for the home PLMN.

A tariff for an MOC is defined in a similar manner, complemented by the additionalentering of a parameter E3SCF. The number of charge units, which is calculated fromthe other parameters in relation to call duration, is, for MOCs as well, multiplied by thefactor 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 termi-nating calls even when incoming calls are non chargeable.

A tariff is allocated to a PLMN by specifying the mobile country code (MCC) and themobile network code (MNC). Since the MCC and MNC are a part of the internationalmobile subscriber identity (IMSI), the tariff valid for every mobile subscriber can beselected at the MSC.

A change in the PLMN tariffs immediately affects all newly set up calls. Calls that arealready in progress are still charged according to the old tariffs. This also applies tomobile 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 homePLMN (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=262–03, E3SCF=100, E4INU=10;

Result: For mobile subscribers of the home network, 1 charge unit is registered foreach mobile terminating call. With MOCs and MTCs, the total number of chargeunits is multiplied by a factor of 1 upon call termination.

– ENTR PLMNTAR: NETW=206–04, E1UPTI=10, E2SPTI=150, E3SCF=200,E4INU=20, E7SPITI=200;

IN – 24 A30808-X3003-X458-2-7619


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

1.1.5.3 SurchargeA surcharge is a fixed number of charge units billed for a call in addition to the registra-tion of charges based on call duration and the valid tariff. This surcharge is entered whencreating the appropriate zone point. The number of additionally registered charge unitsis recorded in the MCR of the mobile originating call and can thus be billed to the servedmobile subscriber. In this manner, for example, access to services by way of certainzone 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 forthe utilization of the PLMN.

1.1.5.4 Call AttemptDepending 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 theMSC, the tariff valid at that time for call attempts is initially used to register the chargeunits. As soon as the call setup has been successfully completed (i.e. the called partyanswers), this tariff is replaced by the tariff for successful calls. If the attempt is notsuccessful (e.g. the party does not answer or cannot be reached), the served subscriberwill be billed for the minimum number of charge units contained in parameter E4INU ofthe call attempt tariff.

1.1.5.5 Subscriber Controlled InputSubscriber controlled inputs are zoned as mobile originating calls.Zoning is based on the transmitted (GSM-specific SS) code for the requested supple-mentary 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 ChargeThe advice of charge feature (AoC) makes it possible to provide the mobile station withinformation that allows it to autonomously calculate and display or otherwise evaluatecharge units accumulated during a call (MOC, MTC).

A distinction is made here between Advice of Charge Information Level (AOCINFO) andAdvice of Charge Charging Level (AOCCHRG).AOCCHRG enables immediate charging for applications in which the mobile subscriberadministered by the network operator does not use the mobile station himself but allowsit to be used by others, e.g. as in the case of rented telephones. Therefore a MZOPT forthe dialed number must be created. If no MZOPT for the dialed number is created, theMSC interrupt the call immediately.AOCINFO is used only to "inform" the mobile subscriber of the current charging level for

A30808-X3003-X458-2-7619 IN – 25


the call in question (display of charges). If for this level no MZOPT is created, there isno display of the charge but the call will be established.A mobile subscriber can be assigned either the AOCINFO feature or the AOCCHRGfeature.

The following prerequisites must be fulfilled for the advice of charge to be displayed tothe subscriber:– For the AOCCHRG feature, Phase 2 of the GSM Recommendations is a prerequi-

site 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 thesubscriber 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 orCharging Level) is registered in the VLR for the served mobile subscriber. If so, the MSCtransmits 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 (AoCInformation Level).If the supplementary service AoC Charging Level is registered in the VLR for the mobilesubscriber concerned, a timer is started in the MSC after the tariff is sent to the mobilestation and the MS is expected to reply.The reply confirms that the mobile station has the AOC Charging Level feature. Oncethis confirmation has been received, the timer is cancelled. If no such confirmation isreceived, the call is released when the timer expires. This time can be set using MODTIOUT (Timer 116), (see OMN:SSS-SY).

Since mobile subscribers with the AoC Charging Level supplementary service have touse this service in all cases, any location updates and call requests in networks that donot 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 parametersare immediately transmitted to the mobile station. Here the mobile stations with the AoCCharging Level are informed before those with the AoC Information Level feature.

Call charge information for use of the Call Hold or Multiparty supplementary services aretransmitted to the mobile stations as soon as another subscriber answers the call. Thesecalls are charged as a separate call.Charges for call forwarding, subscriber controlled input and unsuccessful call attemptsare not displayed.

Since the AoC is calculated independently of the generation of MCR and their evaluationin related data post-processing procedures, the netwok provider is responsible forseeing 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

IN – 26 A30808-X3003-X458-2-7619


the charges at the MSC. The new parameter set is, however, not transmitted to themobile station, which may consequently result in deviations between the actualcharges and those displayed at the mobile station.

– minor deviations can arise between the calculated AoC charge units and the exactevaluation of the MCR. This is due to the fact that minimal time delays can occurbetween the switchover time from one tariff to another at the MSC and the instant atwhich the tariff is available at the mobile station.

– surcharge: Charge units additionally billed as a surcharge are not transmitted to themobile station and are consequently not displayed there.

1.1.6 Call Charge Registration in the Intelligent Network (IN)

1.1.6.1 GeneralThe term Intelligent Network stands for the concept of a network architecture valid for alltelecommunications networks. The basic idea is the introduction of a control level whichcontains centrally the service logic or service data, therefore more effectively controllingthe 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 inan 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 registrationfacilities. 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 thecharges are registered:• call charge registration by the Service Control Point (SCP) or the Service Manage-

ment 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 eachIN call. The data required are collected in the SCP (on the basis of the call data suppliedby the SSP, which are transferred to the SCP/SMS at regular intervals). The customer-specific records are created from this in the SMS.

Charge registration by the SCP/SMS is only used for billing the service subscriber.

A30808-X3003-X458-2-7619 IN – 27


Charge registration by the SSP is based on the existing call charge functions in the tele-phone network. The SCP can affect the charge registration, e.g. by transmitting/prede-fining the zone number to be used.

Charge registration by the SSP can be used for billing both the service user and theservice subscriber.

1.1.6.2 Terminology

Service provider

The service provider is the telephone company that offers IN services to the servicesubscriber, for instance, freephone.

Service subscriber

The service subscriber is, for example, a mail order company which accepts the chargesfor orders placed by telephone.

Calling line

The calling line in an IN call is the calling party. The calling line can be either the serviceuser or the service subscriber.

Service user

The service user is, for example, a customer who places orders with a mail ordercompany free of charge.

Charge registration for the calling line

Normally the calling line's charges are registered in the PLMN by means of PLMNmethods. 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 thePLMN 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 thePLMN billing file IA.ICINA.

Trigger profile

The trigger profile is created in the SSP and specifies how the particular IN service is tobe processed.

IN-specific charge

This term refers to the determining of a zone, depending on the IN service used, butindependently of the actual destination of the call.

IN – 28 A30808-X3003-X458-2-7619


Flexible charge registration

The SSP can change zone or create a new data record when a call is set up to a newdestination (the primary destination is busy). This includes calls to the intelligentperiphery (IP).

Divided charge registration

This term denotes simultaneous billing of two parties engaged in an IN call, usually thecalling line and the service subscriber. In some instances the charges have to be splitbetween 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: GeneralThe question of who has to pay for what must be dealt with separately for each INsubscriber. The amount of the charges to be paid by the calling line and/or the servicesubscriber is dependent on the particular service. In addition, due account must betaken of the network-specific aspects (location of zoning, signal repertoire of signalingsystem, etc.).

There are three options for registering charges for IN services:

1. charge registration only by the PSTN2. charge registration only by IN components3. charge registration divided between PLMN and IN.

ExampleThe charges for the universal number (UN) service can be registered as follows. Thecharge total is divided between the calling line and the service subscriber (calledparty). The user is charged for the ascending branch (from the calling party to theSSP). 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 SSPto 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). Itthen branches to the relevant trigger profile in the CP. As a result of the subsequentcommunication with the SCP, the SSP obtains the actual directory number of the calledparty and the corresponding zone.

From MZOCHA=ZONINHI in the command CR MZOPT, the SSP knows that it must usethe zone sent by the SCP.

In the IN, data records are only created for the successful calls. Consequently, theservice subscriber only receives his data record if the call to the called party was set upsuccessfully.

1.1.6.4 Administration by MMLEach IN call must be zoned before a SCP dialog can start. All trunk groups betweenMSC and base station have to be created with GCOS=ZON.

A30808-X3003-X458-2-7619 IN – 29


There are two possibillities for zoning: zoning using the dialed digits or zoning usingadditional the SCM digits.If INTRIG created with GENPROP=PROP6 than zoning is done by means of the dialeddigits, 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 zonesone can create: CR MZONE = ZONO= 1...511, Full=0 and allocate the MZOPTs to thiszone.

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 tothe 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 1is send zone 127 is used.

Charge registration divided between PLMN and IN

Four steps are required for an IN call:

1. The CCS7 connection from the SSP to the SCP must be established2. The triggers in the CP must be entered and activated (CR INTRIG, ACT INTRIG)3. The IN-specific announcements must be prepared (CR INC)4. 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 param-eter TRATYP). This activates communication with the SCP. The zone points are createdby way of ZOCHA=ZONINHI (in the SSP). The SCP sends the actual called partynumber 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=IN–6–”FPHS1”;

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,=ZONE–355;

IN – 30 A30808-X3003-X458-2-7619


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 ina other node, ORIG2 ... by means of the feature Subscriber Dependent Digit Processingand 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;

A30808-X3003-X458-2-7619 IN – 31


1.2 Interadministration Revenue and Statistics (IARA)A large proportion of telephone communication is conducted at national and interna-tional long-distance level. Depending on a PLMN or PSTN telecommunication structure,subscribers may leave a PLMN service area at the national or international level whenthey call a subscriber in the service area of another PLMN or PSTN. In order for revenuefrom such calls to be distributed among the PLMNs and PSTNs, the traffic between theservice areas is registered. The revenue accounting is based on the volume of traffic. Itrecords call data from selectable traffic relations between originating trunk groups anddestinations or routes.

In the D900 system, a flexible procedure geared to administrative requirements is avail-able for revenue accounting between the different networks. The IARA (Interadministra-tion Revenue Accounting) method can be employed for revenue accounting betweenthe different administrations of a single country as well as those of different countries ore.g. between two MSC. Thus, IARA can be used, for example, in gateway mobileservices switching centers (GMSC) or PSTNs gateway exchanges. Apart from revenueaccounting, IARA can also be used to collect statistical data.

In a "Combined Switching Center" (CSC), both IARSTAT an IARAMA can be used forall types of subscribers. A CSC is a network node which can implement the function ofa 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 followsthe numbering scheme of the PSTN.

– A wire-line subscriber is a subscribers who has the same quality like a PSTNsubscriber.

Generally speaking, wireless local-loop subscribers and wire-line subscribers are onlyadministered in a "Combined Switching Center" (CSC). From the viewpoint of CSC,WLL subscribers are mobile subscribers who only differ from "normal" mobilesubscribers 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 mobilesubscribers.

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 telecommunica-tion networks. Various registration criteria can be defined in the IARA database jointlyfor all IARA registrations, and registration jobs based on these criteria enable IARA tobe employed in line with the network-operator requirements.

The IARA procedure comprises software components in the group processors (GP) andthe coordination processor (CP). In IARA procedures the group processors register thedesired call data and transfer these data to the CP. The CP stores the registered calldata and makes it available for post-processing.An example of an IARSTAT registration can be found in Fig. 1.8

IN – 32 A30808-X3003-X458-2-7619


Fig. 1.8 Sequence of IARSTAT Registration

yes

Digit translation, path selection

Evaluation of:Originating trunk group

Terminating trunk groupDestination route

IARSTAT matrix point involved?

Buffering of IARSTAT call data per trafficrelationship in hour value counters in thememory unit

Post–processing of the call data totals forrevenue accounting and statistical analysison a commercial computer

LTG Gatheringcall processing IARSTAT

measurementdata

GP CP

Callprocessing

In the 45th minute of each hour summationof the IARSTAT call data of the matrix pointin registration counters on disk,file = IC.COUNTERFILE

Provision of IARSTAT call data totals inpost–processing files on diskfile = IC.Aryymmnn

Output of the post–processing files to anOMT or tape or transfer to an operation andmaintenance center

A30808-X3003-X458-2-7619 IN – 33


1.2.1 IARA RegistrationIARA 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 regis-tered. To do this, the various originating and destination objects are assigned IARAnames which are subsequently linked with each other.

Note: it is not possible to use IARA for IN calls, interception and calls between wire-linesubscribers (LAC to LAC)

There are two ways in which call data can be registered, i.e. registration by means ofIARSTAT (Inter Administration Accounting with Statistics) or by means of IARAMA (InterAdministration Accounting with AMA).

IARSTAT

Summation of the call data separately for each traffic relationship using registrationcounters.

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 gener-ation 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) subscriber’s number– Called (B) subscriber’s number– Transmission rate– Date and time at the end of the call

Information about the number of successful calls and the transmission rates used canonly be determined by post-processing the AMA data records.

Using Call Data Registration

For wire-line subscribers (analog, digital, (dedicated network) PABX or PSTNsubscribers) of a CSC, both methods of registering call data are available without anyrestrictions (one can select the kind of charging (PLMN or PSTN) for all fix subscribersin the installation mode by means of the command MOD MSERVREL.; for transit callswhich 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 areinvolved . At the same time, it is to be ensured that the IARA configuration of a CSC iscreated with the priority in favor of mobile subscribers. All the IARA features which onlyapply for the wire-line subscribers are only to be used if they do not affect the registrationof the IARA data of the mobile subscribers.

IN – 34 A30808-X3003-X458-2-7619


1.2.2 Terms

IARA Origin and Destination Names

The traffic relationships for which call data are to be registered are characterized by adefined 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 correspondingsources of the originating traffic and the selected destinations are combined into groupsin 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 becreated, however, is restricted and depends on the measurement type. Refer toTab. 1.4.

For the four different measurement types it is possible to assign a separate IARA namefor 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 witheach 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 variantsIARSTAT or IARAMA.

Measurement Type IARA Origin Name IARADestination

Name

Assignment Required forConversion into ASN.1

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 Maximum Number of IARA Names

A30808-X3003-X458-2-7619 IN – 35


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 stoppingcounters or data records). The measurement types are assigned upon entering theIARA 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 freelyselected. However, if the IARA files are to be converted into ASN.1 format (AbstractSyntax Notation 1), e.g. in order to be transferred to a post-processing center by meansof FTAM, the assignment of measurement and traffic types given in Tab. 1.4 is to beused.

With IARSTAT a separate post-processing file (IR.Aryymmnn ) for each measurementtype is created.

If the measurement types are not assigned to separate traffic types, the entire traffic willbe registered with one measurement type and can then only be billed collectively.

Example: Creating traffic relationships

Origin name

Destination name

IARAMA

IARSTAT

IN – 36 A30808-X3003-X458-2-7619


Fig. 1.10 Definition of Matrix Points, Destination and Origin Names

Matrix point 1

Measurementtype 4

Measurementtype 3

Measure-menttype 2

Origin name 2

Destinat-ion name: Dest 1

Measurementtype 1

Origin name:INC2

Destination name:Dest 2

Origin trunk groups

A B C

Destination

X

Y

Z

Origin name:INC1

A30808-X3003-X458-2-7619 IN – 37


The following entries are required for the configuration shown in Fig. 1.10 :

1. Assignment of IARA origin names :

2. Assignment of IARA destination names :

3. Creating the traffic relationships (matrix points) for IARSTAT :

4. Creating the traffic relationships (matrix points) for IARAMA

In this way, matrix point 1 allows measurement data to be collected for the traffic whicharrives from trunk groups B and C and which is routed to destinations X, Y and Z, whilematrix point 2 allows measurement data to be collected for the traffic which arrives fromA, 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 differentcounters) according to the different call types such as automatic calls or operator-assisted 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 andTUP+) 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.

ENTR IARNAME: TGNO=ANAME=0-0-0-INC2;

ENTR IARNAME: TGNO=B,NAME=INC1-0-0-INC2;

ENTR IARNAME: TGNO=C,NAME=INC1-0-0-INC2;

ENTR IARNAME: DEST=X, RTNO=1NAME=DEST1-0-0-DEST2;

ENTR IARNAME: DEST=Y, RTNO=1NAME=DEST1-0-0-DEST2;

ENTR IARNAME: DEST=Z, RTNO=1,NAME=DEST1-0-0-0;

CR IARMPT: MTYPE=IARSTAT1,DNAME=DEST1, ONAME=INC1, CNTR1=AUTO;

CR IARMPT: MTYPE=IARSTAT4,DNAME=DEST2, ONAME=INC2, CNTR1=AUTO;

CR IARMPT: MTYPE=IARSTAT1,DNAME=DEST1, ONAME=INC1, TICKET=YES;

CR IARMPT: MTYPE=IARSTAT4,DNAME=DEST2, ONAME=INC2, TICKET=YES;

IN – 38 A30808-X3003-X458-2-7619


This enables the call data for a traffic relationship to be registered separately accordingto 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 GSMsystem and in a CSC only the "automatically switched calls" call type exists) and trans-mission rates. IARA checks each call to determine whether or not an intersection existsin this matrix. For such a combination consisting of a call type and a transmission rate itis possible to register the traffic separately (e.g. all the automatic calls with 3.1 kHzaudio).

Combinations which consist of a call type and a transmission rate can be assigned to acall group. It is possible to create a maximum of 6 such call groups.

Fig. 1.11 Matrix for Call Groups

Combinations of call types and transmission rates which have not been assigned to acall group are not registered.

The system provides a specific default assignment to call groups, whereby the name ofeach group is identical with the only call type contained in this particular group. Nodistinctions are made between transmission rates. As soon as a new call group isdefined for an APS, i.e. as soon as MML command CR IARGRP is entered for the firsttime, all the default call groups are deleted at the same time. Therefore, at this point intime, only this one particular call group which has been newly created is known withinthe system. Any further call groups which are required have to be set up using the MMLcommand. 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, IARAregistration can be started:

REC IARSTAT: MTYPE=IARSTAT1 [,BEG= ... , TER= ... ];

Registration for a specific measurement type is started with precisely such a registrationtask. This can be realized separately for each of the 4 measurement types. By specifyinga time interval, it is possible to control the duration of the registration procedure.

Call types

Transmission rates

4

3

1

2

6...1

Call group

A30808-X3003-X458-2-7619 IN – 39


Time-controlled registration and continuous registration tasks can be interrupted withCAN JOB. It is necessary, however, to wait for the next full hour to elapse if new matrixpoints have been created in the meantime.

At the end of each full hour, the data are automatically saved on disk, thus protectingthem from being lost.

1.2.3 IARSTAT

1.2.3.1 Registration Counters and Tariff ZonesEach matrix point may be allocated up to 7 registration counters for the different callgroups (see Fig. 1.12). For D900/D1800 and within a CSC only one counter is used. Aregistration counter consists of 3 counters that are used for the time-controlled registra-tion of IARSTAT call data.

For each matrix point one of up to 99 tariff zones can be allocated. A tariff zone definesthe 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 takeplace only on each full hour. If no tariff zone has been allocated to the matrix point, theday 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.

IN – 40 A30808-X3003-X458-2-7619


Fig. 1.12 Detailed Structure for a Matrix Point

number ofseizures

Holding time onthe A side

Holding time onthe B side

Ve time

Number of calls

Nght

Registration counter 7

number ofseizures

Belegingtime A


Ve time

Number of calls

Nght


number ofseizures

Belegng timeA side


Ve time

Number of calls

Nght


Number ofseizures

Belegngtime A


Ve time

Number of calls

Nght


Znumber ofseizures



Ver time

Number of calls

Nght


Zahber ofurures

Beleg time onthe AA side


Ve time

Number of calls

Nght


Matrix point

Origin name

Destination name

Number ofseizures



Call time

Number of calls

Number ofseizures



Call time

Number of calls

Number ofseizures



Call time

Number of calls

Day Evening Night


A30808-X3003-X458-2-7619 IN – 41


1.2.3.2 Functional Sequence of IARSTATWhen a call is set up, the CP determines the trunk group, destination and route andchecks whether a matrix point is involved for the call (Fig. 1.8). Provided the matrix pointis marked as active, the call is traced in the LTG in order to determine the followingIARSTAT 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 intermediatemessage after every 30 minutes for calls of long duration - the time can be changed withtimer 114 in MOD TIOUT). The CP stores the data in a transient hour value counter. Thedistribution 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 eachtariff area). The call data are added to the part corresponding to the valid tariff area. If acall extends beyond a tariff switchover, the call times and holding times are added to thecounter part for the preceding hour and the current hour in the correct proportions; thenumber of calls and seizures is added to the counter part that is valid after theswitchover.

At each full hour, the CP transfers the call data totals registered by the hour valuecounter during the preceding hour to the relevant registration counters. These arelocated on the disk in file IC.COUNTERFILE.

The registration counter itself is also a summation counter. The call data which aretransferred every hour are added to the stored data. The registration counter containstariff zones for day, evening and night registration, after which the hour value counter isreset.

Generally speaking, the registration counters are designed such that they do not over-flow in the course of a month. By way of example, the registration counter for the seizureand call time is designed such that it can register the times for the uninterrupted use of800 trunks up to and beyond 31 days without overflowing. The registration counter forthe number of calls and trunk seizures is designed in such a way that, for example, unin-terrupted usage of 500 trunks with an average seizure duration of 90 seconds over aperiod of 31 days does not result in a counter overflow. If, however, there is reason toexpect that certain registration counters might overflow, it is possible to display theircurrent status using an MML command. What is more, an MML command can also beused to create an intermediate file on hard disk before the counters overflow. This inter-mediate file is then available for further post-processing once the file has been copiedonto tape.

The number of available IARSTAT counters is governed by the particular project.

1.2.3.3 IARSTAT Post-ProcessingIn addition to registration counter file "IC.COUNTERFILE" which is common to allIARSTAT 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 isentered.

IN – 42 A30808-X3003-X458-2-7619


The IARSTAT data are transferred from the IC.COUNTERFILE file into individual post-processing 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 isdefined, 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 andCAN JOB must not be entered, since the data which are to be saved are not static duringthe 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 = IARSTAT measurement typeyy = Yearmm= Monthnn = Consecutive number within a measurement type.

The date specified in the name of the post-processing file always refers to the start ofthe registration task. In order to distinguish between IARSTAT post-processing files ofthe same registration type which have the same date in the file name, a consecutivenumber 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 post-processing file, the IARA counters in the IC.COUNTERFILE are reset.

The post-processing files for the individual measurement tasks can be output onto tapeat any time for further post-processing or transferred to a post-processing center. Sinceonly closed IARSTAT files can be transferred, DISP IARFILE can be used to interrogatethe status of the entries. When files are copied onto tape, at least two copies are to bemade for safety reasons. The copied file is then to be deleted from the hard disk, butonly after first checking that the IARA data have been successfully processed.

When the post-processing files are transferred into the customer-specific post-processing file (TRANS FILE:.., COPMOD=POST;), a transformation into a customer-specific format is performed by the copying service process defined in SETFGRPATT:....,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 (ASCIIformat, e.g. for copies onto tape).The files are converted into ASN.1 format (Abstract Syntax Notation 1), e.g. for transferby means of FTAM, using the IRENC process.

While conversion is taking place, the following assignment is made:

A30808-X3003-X458-2-7619 IN – 43


In other words, if IARSTAT files are to be converted into ASN.1 format (in order to betransmitted by means of FTAM or copied onto tape), the measurement types are to becreated in line with the above-mentioned assignment.

Generally speaking, the data are post-processed by means of a commercial data-processing system. For manual evaluation, it is also possible to output the data from theIC.COUNTERFILE file with DISP IARSTAT on an operation and maintenance terminal(OMT). The required registration counters are specified via the registration type and, ifnecessary, also via the IARA origin names and the IARA destination/path names. It isalso possible to output the contents of the post-processing files by specifying the filename on the terminal.

Fig. 1.13 IARSTAT Files

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

IR.A4yymmnn

Post-processing file proMeasurement type

IR.A3yymmnn

Post-processing file proMeasurement type

IR.A2yymmnnPost-processing file pro

Measurement typeIARSTATHour value

counter(duplicated)

IC.COUNTERFILE

IARSTAT counterfor all measurement

types

IR.A1yymmnn

Post-processing fileper measurement type

PAM

Customer-specificpost-processing fileper measurement

type

SAM

Hourlyswitchover

Call data

"service process"

Transmission viaTRANS FILEwith processes IRENC orIRCPP

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

Hourly transfer

IN – 44 A30808-X3003-X458-2-7619


1.2.3.4 Example of an IARSTAT ApplicationThe IARSTAT accounting volume to the destinations NAT, INAT and INTCON in thegateway MSC of the PLMN is to be evaluated using IARSTAT counters. The originatingtraffic 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 sepa-rately. This is determined regardless of which of the three incoming trunk groups theoriginating traffic came in on.

Task 2

The IARSTAT accounting volume to the destinations NAT and INAT is to be registeredtime-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 hto the night tariff. The switchover takes place only on workdays.The IARSTAT accounting volume to the destination INTCON is to be registered withoutany 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 MMLcommands are contained in the figures.

A30808-X3003-X458-2-7619 IN – 45


Fig. 1.14 Example: Network Configuration on which the Task is Based

PSTN

Gateway

exchange(s)

to NAT

to INAT

to INTCON

GMSC

PLMN

IFRA

IHAM

IMUC

DEST = INTCON

RTNO = 1

RTNO = 2

DEST = NAT

RTNO = 1

RTNO = 2

DEST = INAT

RTNO = 1

RTNO = 2

IN – 46 A30808-X3003-X458-2-7619


Fig. 1.15 Solution for Task 1 (Part 1)

GMSC

DEST = INTCON

RTNO = 1

RTNO = 2

DEST = NAT

RTNO = 1

RTNO = 2

DEST = INAT

RTNO = 1

RTNO = 2

ORIG

IFRA

IHAM

IMUC

Combination of originating trunk groupsENTR IARNAME: TGNO= IHAM, NAME= ORIG–0–0–0;ENTR IARNAME: TGNO= IMUC, NAME= ORIG–0–0–0;ENTR IARNAME: TGNO= IFRA, NAME= ORIG–0–0–0;

GMSC

Combination of destinations/routesENTR IARNAME: DEST=NAT, RTNO=1, NAME=AR1–0–0–0;ENTR IARNAME: DEST=NAT, RTNO=2, NAME=AR1–0–0–0;ENTR IARNAME: DEST=INAT, RTNO=1, NAME=AR2–0–0–0;ENTR IARNAME: DEST=INAT, RTNO=2, NAME=AR2–0–0–0;ENTR IARNAME: DEST=INTCON, RTNO=1, NAME=AR3–0–0–0;ENTR IARNAME: DEST=INTCON, RTNO=2, NAME=AR3–0–0–0;

AR2

AR3

AR1

DEST = INTCON

RTNO = 1

RTNO = 2

DEST = NAT

RTNO = 1

RTNO = 2

DEST = INAT

RTNO = 1

RTNO = 2

IFRA

IHAM

IMUC

A30808-X3003-X458-2-7619 IN – 47


Fig. 1.16 Solution for Task 1 (Part 2)

GMSC

Creation of 3 matrix pointsCR 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;

AR1

AR2

AR3DEST = INTCON

RTNO = 1

RTNO = 2

DEST = NAT

RTNO = 1

RTNO = 2

DEST = INAT

RTNO = 1

RTNO = 2

IFRA

IHAM

IMUC

ORIG

D E N

Reg. Counter

D E N

Reg. Counter

D E N

Reg. Counter

IN – 48 A30808-X3003-X458-2-7619


Fig. 1.17 Solution for Task 2

GMSC

Switchover

Creation of a tariff zone and allocation to a matrix pointCR IARTMPD: TZONE=1, TIME=06–00, TARIFF=DAY, WDCAT=WO;CR IARTMPD: TZONE=1, TIME=18–00, TARIFF=NIGHT, WDCAT=WO;

ENTR IARZONE: MTYPE=IARSTAT1, TZONE=1, DNAME=AR1, ONAME=ORIG;ENTR IARZONE: MTYPE=IARSTAT1, TZONE=1, DNAME=AR2, ONAME=ORIG;

AR1

AR2

AR3DEST = INTCON

RTNO = 1

RTNO = 2

DEST = NAT

RTNO = 1

RTNO = 2

DEST = INAT

RTNO = 1

RTNO = 2

IFRA

IHAM

IMUC

ORIG

Switchover

D NE

Reg. Counter

D NE

Reg. Counter

D E N

Reg. Counter

A30808-X3003-X458-2-7619 IN – 49


Fig. 1.18 Solution for Tasks 3 and 4

Possible atany time

IHAM

IMUC

IFRAData transfer at xx.00 hfrom the preceding hourvalue counter part

IARSTAT datadisplay by MML

Hour value counter

GMSC

AR1

AR2

AR3DEST = INTCON

RTNO = 1

RTNO = 2

DEST = NAT

RTNO = 1

RTNO = 2

DEST = INAT

RTNO = 1

RTNO = 2

ORIGD NE

Reg. Counter

D NE

Reg. Counter

D E N

Reg. Counter

OMT

IC.COUNTERFILE

IR.Aryymmnn

MDD0MDD1

Data transferinitiated by MML

Entries into the postprocessing file:– Automatically at the end

of registration– Once per month at a fixed

time (continuousregistration)

– Manually betweenxx.05 h and xx.20 h(MML: COPY IARACCT)

Solution for:Task 3: REC IARSTAT:

MTYPE=IARSTAT1;Task 4: COPY IARACCT:

MTYPE=IARSTAT1;Proc. TP–550 inOMN:SSS–TA

Update: at the end of call ore.g. 30 min. intermediate

OMCNot possible duringhourly saving

IN – 50 A30808-X3003-X458-2-7619


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

1.2.4.1 MML commands for IARAMAThe 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, TGNOor 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.

A30808-X3003-X458-2-7619 IN – 51


1.2.4.2 Example of an IARAMA ApplicationBy 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 regis-tered with tickets. Registration is to be performed separately for national and interna-tional traffic, while the outgoing traffic is to be assigned to measurement type 1 and theincoming traffic to measurement type 2.

Fig. 1.19 Example of a Gateway Exchange

Installation of the database in line with the example

1. Creating the IARA origin namesENTR 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 possibleparallel registration types. England and France receive the same name since theyconstitute one unit for accounting purposes. The traffic which goes out fromEngland, France and the PSTN generates the incoming traffic and is thus assigned

LAC=091

DEST= englnd,RTNO=1

DEST=france,TGNO=1

TGNO=inpstn

DEST=pstn,TGNO=1

TGNO=inceng

TGNO=incfra

England

FrancePSTN

1

32

Combined SwitchingCenter

IN – 52 A30808-X3003-X458-2-7619


to measurement type 2, while the traffic from the wire-line subscribers of the CSC isregistered with measurement type 1.

2. Creating the IARA Destination NamesENTR 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 oneunit for accounting purposes. The same names have been used for origins anddestinations. Although this is possible, it is not necessary.The destinations for the outgoing traffic (England, France and PSTN) are registeredwith measurement type 1, while the destination for the incoming traffic is registeredwith measurement type 2.

3. Creating the Matrix PointsCR IARMPT: MTYPE=IARSTAT, ONAME=csctln, DNAME=nat, TICKET=YES;This command installs the relationship for traffic arriving from a wire-line subscriberof the CSC and traffic going to a subscriber of the PSTN. The traffic is registered withregistration type 1 and stored in data records. The other matrix points are created inthe 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;

Fig. 1.20 Creating the Matrix Points for Registration Type 2

LAC 091

pstn

Origins

Destin.IARA dest. names

csctln

nat

csctlnIARA origin names

LAC 091

englndinat

Ticket

inceng

inat

Ticket

Ticket

inpstn

nat

Ticket

incfra

france

A30808-X3003-X458-2-7619 IN – 53


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

1.2.4.3 Saving the Registered Data

Fig. 1.21 IARAMA Files

1.2.5 Regeneration of the IARA databaseThe complete IARA database can be regenerated. The following command must beused 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 APSchangeover) 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 commandEXEC REGEN was executed.

If further recordings were started after the command EXEC REGEN was executed, theycannot be regenerated. In this case, after EXEC CMDFILE has been performed, acheck must be made with DISP IARJOB to establish which recordings are still inprogress. 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, thecommand EXEC REGEN.

1.2.6 Procedure after RecoveryIf fallback to an earlier APS has taken place (recovery with ISTART2G), any inconsis-tencies between the old and new database must be resolved by incorporating thelogging file. After this, the command

IA.ICIAR

Cyclic IARAMAfile for all

measurement types

IARAMATicket data

buffer

Call data

"service process"

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

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

Customer-specificpost-processing file

SAM

IN – 54 A30808-X3003-X458-2-7619


SAVE MET: TYPE = IARA, FUNC = FALLBACK;

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

1.3 Trunk Meters and Statistics MetersIn addition to being registered in AMA files or MCR and IARSTAT procedures, chargedata 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 statis-

tics meter has been allocated

The prerequisite for a registration is that the relevant function has been activated at theMSC.

1.3.1 Trunk Meters for Trunk GroupsFor trunk groups created with GCOS =TRMET, the call charge pulses transmitted viathis trunk group by the remote node are collected in a file. The information contained inthis file can be used, for example, for checking when the zoning for a call is notperformed at the home MSC, i.e. ZOCHA= ZONINHI was entered for the relevant zonepoint.

Charge Saving

The backup files are generated in accordance with the types of counters set and themeter counts are saved in the memory and on the disk. This accompanies the followingfunctions:– 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 systemat 00:30 hours

The charge data that have been added on by call processing can be immediately or peri-odically saved on the disk. After memory failures or ODAGEN runs, the data in the oper-ating range are reprocessed using the backup file. If the operating range is extendedwith ODAGEN, the charge data are automatically saved so that practically no chargedata 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 thebackup 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 avail-able, the data can be restored from a repair file (a copy of an old backup file). Conse-quently, 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 isprotected against writing and erasure. At specified saving times, the charge data arewritten to the backup file.

A30808-X3003-X458-2-7619 IN – 55


Charge Data

Charge data are saved at specified times in a backup file. After memory failures, thedata can be restored from the backup file or, if this file has also been destroyed, the datacan be restored from a repair file (a copy of an old backup file). Consequently, it is advis-able 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). Thisallows the charge data to be regenerated in the new APS (MML command REG MET)

1.3.2 Statistics MetersStatistics meters are summation counters. They register the number of calls, accumu-lated 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 metersets 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 inseveral places during a call setup, only the last one found will be assessed. (The objectsare evaluated here in the following order: ”incoming trunk group,” ”route,” ”zone point.”)This mutilates the statistics counting.

1.3.3 Statistics Meter Switchover TimeA registration is performed after every call conducted via a zone point and for which astatistics meter has been created. Call and charge data are thus registered on statisticsmeters.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 cate-gory, can be defined by MML command.

Each statistics meter set consists of a counter for the number of calls, a counter for thecharges, a counter for the call duration and a checksum byte. The meter contents canbe displayed on the monitor by entering the command DISP STATMET (see Fig. 1.22)

IN – 56 A30808-X3003-X458-2-7619


Fig. 1.22 Structure of a statistics meter set

Statistics meter ”n”

Counter for the number of calls

Counter for the charge units

Counter for the call duration

Checksum byte

A30808-X3003-X458-2-7619 IN – 57


1.4 Charging of Wired Subscribers of a CombinedSwitching Center (CSC)Wired and PABX subscribers can be charged in a CSC both: PLMN charging or PSTNcharging

Call charge registration is carried out in the MSC to which the digital subscriber and thePABX are connected. One can select the kind of charging (PLMN or PSTN) for all fixsubscribers 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 toenter 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.

IN – 58 A30808-X3003-X458-2-7619


Fig. 1.23 Charge registration for wired subscribers

1.4.1 Subscriber Tariffs

1.4.1.1 Tariff Administration TasksThis section deals with the tariffs for subscriber charge registration. No reference ismade to interadministrative revenue accounting (IARA), which is covered by a separatetariff administration.

Individual datarecording


Individual datarecording(IARAMA)

Summationmetering(IARMET)

Call charges


Subscriber's call charge(calling party)

Registration of statistics

TFSIN

Subscriber's call charge(service subscriber)

Registration of traffic betweenadministrations

Trunkmetering

Charges for facility input by thesubscriber

Facility usage charges Charges for facility input by theoperator

Summationmetering

Summationmetering

Summationmetering

with charges without chargesSummationmetering

Charge registration

(METTFS)

IARA

(METTR) (METSTAT)

(METSUB) (AMA) (FIR) (AMA/DEB)

A30808-X3003-X458-2-7619 IN – 59


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) arepredefined with default values and cannot be modified.

The minimum unit-interval of meter pulses is 200 ms; the maximum unit-interval is 30minutes. All values must be multiples of 4 ms.

1.4.1.2 TariffsA tariff usually has two components:– a network access component– a network usage component

The network access component represents the general costs of providing a subscriberwith 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 coversthe 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 wasnevertheless completed successfully, i.e. the address complete message (ACM) wasreceived.

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 areincurred.

The call setup charge is registered for successful calls, i.e. when the called partyanswers.

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 bymeans of single pulse metering (SPM) or multiple pulse metering (MPM), irrespective ofthe duration of the call.

The communication charge is dependent on the duration of the call. The valid tariff maychange as the result of a tariff switchover.

IN – 60 A30808-X3003-X458-2-7619


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 maydepend 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. Theinterval 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 multiplepulses 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 periodicmultiple pulse metering, can be created for each tariff in a zone. There are no restrictionson 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. Forexample, meter pulses may be received over the trunk which have to be forwardedto the originating exchange and summated there. This zone also cannot be assignedany 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 alwaysbe 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 SequencesThe use of tariff sequences enables different charges to be registered for differentstages 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

A30808-X3003-X458-2-7619 IN – 61


reduced by the corresponding number of basic tariffs contained in the sequence. Tariffsfor 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. amaximum of 4 basic call components, the call attempt tariff and the call setup tariff.Switchover takes place between these different tariffs depending on the varioussections and the duration of the call. Tariff sequences are entered with the commandENTR TAR

A tariff sequence splits a call into different parts in terms of charges. The access tariffPLSATT 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 thecommunication part, up to 4 basic tariffs can be linked to form a "communicationsequence".

For each individual tariff in a communication sequence, a tariff duration can be set byway of an MML input (TARIFF DURATION in parameter PLSCOM). This period limitsthe 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 (messagerate). 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/orthe 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). Thesequence of communication tariffs can comprise up to 4 basic tariffs. The concate-nation of SPM, MPM, PPM and PMM is permissible in any combination and in anysequence.

• End of sequence:As soon as the defined tariff duration of a communication tariff has elapsed, eitherthe next basic tariff or the agreed procedure for the end of the tariff sequence comesinto effect:

– Continue with the last communication tariff (non-cyclic sequence: standard proce-dure, but only permissible in the case of a PPM or PMM with no tariff durationspecified); input with NONCYCin parameter SEQEND, or

– Release the connection (limited sequence); this is defined by entering LIMITasthe value for SEQEND, or

– Repeat the sequence from the beginning (cyclic sequence); defined by enteringCYCLIC as the value for SEQEND, or

– Continue with a tariff switchover; defined by entering only one PPM or PMM andno 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.

IN – 62 A30808-X3003-X458-2-7619


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 pulsemetering (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 maximumcall duration of 30 minutes and application of a call setup tariff of 10 charge units (onanswer):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 pulsemetering (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 SwitchoversTariff switchovers can be defined to take place at a specific time, the tariff switchovertime, 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 timeof 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 Night3tariff every evening at 6 p.m.).

A tariff switchover can only be created for a tariff sequence if the latter contains not morethan one PPM tariff or MPM tariff. If this condition is met, then switchover from one basictariff 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 restrictioncan 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 tariffduration have elapsed. The basic tariff duration is thus extended by the length of theperiodic 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 hasnot 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 tariffdoes 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 tarifftakes effect.

Tariff switchovers for a zone are entered by means of ENTR TARSW. The preconditionfor this is that the tariffs to which switchover is to take place have already been definedwith ENTR TAR. A tariff switchover can be entered up to 30 days before it is due to gointo effect.

A30808-X3003-X458-2-7619 IN – 63


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 bevaried by means of DATE. The tariff which is active at a particular time can depend onthe weekday category (WDCAT).If this parameter is not specified, switchover takesplace every day.

If statistics metering is being carried out in the exchange, switchovers should also becreated for the statistics meters, depending on tariff switchovers, if identical tariffswitchovers have been created for zones in zone points with the same statistical indexor if a statistical index is assigned to a single zone point only. In all other cases, there isno 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 anothertariff, 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 CategoriesTariff switchovers can be performed dependent of the category of the current day. Thispermits a highly flexible tariff structure, for example it is possible to switch over to a lowertariff on Sundays than on public holidays. A further possibility is to apply the weekdaytariffs 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 weekeach time. They can be either half holidays (e.g. December 24 in Germany) or full holi-days (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 theweek. Here, too, there are both national holidays (such as Easter Monday) and interna-tional holidays.

These are entered in the holiday table by means of the command CR HOLICALanddisplayed with command DISP HOLICAL.

The weekdays are independent of the year; they are administered with MOD WDCATThis command is also used to enter the weekend. For example: Saturday can be spec-ified as the first day of the weekend and Sunday as the second day of the weekend.

The priorities for weekdays are as follows:

IN – 64 A30808-X3003-X458-2-7619


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

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

1.4.2 Zone PointsCall charges are generally calculated on the basis of the distance between the callingand called parties. In other words, a local call can be less expensive than a long-distance call because it uses fewer network resources.

This is implemented by dividing the network into different zones (see Fig. 1.24).

Fig. 1.24 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 tariffsand 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 thedialed digits.

The translator must perform the following functions on the basis of predefined digitcombinations, line codes (e.g. category and origin) and – if applicable – the languagedigit:• Zone point identification:

ZONO 3ZONO 2ZONO 1

25 km

50 km

100 km

PSTN 2PSTN 1

ZONO 4

A30808-X3003-X458-2-7619 IN – 65


– 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 beused for metering must be specified. There are meters for the charge units andmeters for the number of calls.

• If the charge billing method is statistics metering, the statistics index which is to beused 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 PointsZone points are created with the command CR ZOPT. This must be done in allexchanges lying in the path from the origin to the zoning point, because it is not possibleto set up calls without a zone point. In all exchanges that precede the zoning point, it isdefined that zoning is to take place in a higher-ranking exchange. In the exchanges thatlie beyond the zoning point, the incoming trunk group is informed that zoning is no longerneeded.

There is a large number of parameters which allow zoning treatment to be adapted to agiven 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).

IN – 66 A30808-X3003-X458-2-7619


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 sepa-rate tariffs) can be defined for each local network.LAC is specified in the case of amultiple 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;



Charges for a call from A to B are registered on the basis of the tariff applicable to zone12. The tariff for zone 10 applies for calls from B to A.

SCP

SSP

(3)

AVSt

(4)

FVSt

(2)

OVSt

(1)

OVSt

(1)

B in otherexchange

B in ownexchange

A

Zoning point:

(1) local exchange(2) transit exchange(3) service switching point(4) international gateway exchange

A30808-X3003-X458-2-7619 IN – 67


ORIG2

ORIG2 allows the zoning exchange to apply different zoning to subscribers with thesame LAC(for instance in a large city).

MFCAT

This parameter is used for origin-dependent zoning. MFCATdefines the type ofsubscriber station, allowing, for example, coinbox lines to be zoned differently to ordi-nary subscribers.

ZDIG

This parameter is used for origin-dependent zoning. The valid zone is determined on thebasis of the language spoken in the country of origin.

To enable the international gateway exchange to evaluate the language digit, thegateway exchange in the country of origin must transfer parameter ZDIGThis is done viathe route.

FPH

The freephone indicator FPH is used to obtain a zoning result in the internationalgateway exchange for TFS traffic (from a TFS exchange or an SSP in the IN) that differsfrom that for other traffic. The FPH indicator is appended to the dialed digits via ISUP bythe exchange that detected the TFS call. This means that it is no longer necessary tocreate special trunk groups for TFS.

ZONO

ZONO specifies which zone is valid for the calls. Different zones can be defined bymeans 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, forexample:– 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 meterpulses or charge band numbers to be signaled in the network, all trunk groups involvedmust be created with METOTR. Charge band numbers are assigned to zones withcommand MOD ZOINF. Evaluation of the charge band messages is allowed withparameter TKZOINF=YES.

BILLING

The BILLING parameter defines the method of billing to be used for calls via this zonepoint (AMA and/or METERING).

SUCHCNTR

When charges are registered by means of meter pulses (METERING), it must bedefined which of the subscriber charge counters CNTR1 to CNTR5 is to be used to

IN – 68 A30808-X3003-X458-2-7619


register the pulses.

TKZOINF

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

1.4.3 Charge Band Message and Zone Traffic TypeWith the introduction of the charge band message, the generation of a unit-interval, inaccordance with current tariff regulations, is shifted as far as possible toward the callingparty.

In previous versions with zoning in higher-level exchanges, the meter pulses generatedin such exchanges were transferred to the calling party over the network. The networkcan now be ”relieved” of this meter pulse transmission via the trunks (see Fig. 1.26).

Fig. 1.26 Administration of charge band numbers

Only the charge band message has to be signaled on the long distance level; transferby meter pulses is not required until the transition from a digital exchange to anexchange with pulse signaling.

It is possible to change the assignment of charge band message to zones by means ofMML.

In addition, the system is capable of processing charge band messages which arereceived during calls in progress. The tariff is created according to the new zone. Onlythe communication part of the new tariff is taken into account. There is a waiting periodfor time-out of the currently active interval or of the timer for ”non chargeable time”. Ifseveral charge band messages are received during this period, the last message isexecuted.

If no further messages are received apart from the first charge band message, the tariffswitchovers which apply in the current zone are implemented.

If a meter observation is in progress for a subscriber, a new intermediate record is

ZOCHA=ZONINHI ZOCHA=ZONINHI0049=ZONO15=ZRM

ZRM 56

PSTN

ZRM 56

CCS7CCS7 00490049

0049 Pulse

ZRM 56=ZONO 15 = Tariff 4

Gate-wayexch.digital

Trans.exch.digital

Tariff 4

Localexch.EMD

0049Gate-wayexch.digital

PSTN

Localexch.digital

A30808-X3003-X458-2-7619 IN – 69


created when a new charge band message is received (every 10 seconds maximum).

For properly tariffed charge registration, the zone points must be created withZOCHA=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 allexchanges 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 sametreatment applies if the system operator has omitted to allocate a zone to a charge bandmessage.

It is also possible, using MOD ZOINF, to assign a zone to a particular zone traffic type.

1.4.4 Supplementary Services

1.4.4.1 Registration of charges for the input of supplementaryservices (facility input FAI)Supplementary services such as call diversion, abbreviated dialing etc. are created bythe operating company, in some cases at the request of the subscriber. They can alsobe created by means of subscriber control input (SCI). It is possible for charges to beregistered 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 METPULSmust also be specified, otherwise inputs are free of charge (the default value is 0 meterpulses).

1.4.4.2 Registration of charges for the usage of supplementaryservices (facility usage FAU)Facility usage (FAU) charges are normally only applied in connection with an estab-lished call. In principle, however, they are registered independently of the call theyaccompany. 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-relatedcharge treatments, only MOBorig is included, but not MOBterm. In other words, if thecalled party makes use of the facility, no MOBterm ticket is produced.

IN – 70 A30808-X3003-X458-2-7619


Meter pulses for FAU are only included in the AMA/FIRcall ticket or FAU ticket if param-eter EXTNSD=CHARGESis specified in command ENTR CDTDAT.

The following methods of charge registration can be entered for FAU by MMLCR 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 createdwith AMA. It is, however, possible to use different numbers of pulses in the case ofMETERING.

1.4.4.3 Account suspensionsThe administration can activate and deactivate account suspensions for a subscriber(e.g. blocking the terminal for international calls). It is possible to create facility inputrecording FIRrecords as subsequent proof of such action.

These records have a similar structure to AMA records, but are not used for chargeregistration.

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 prerequi-site for this is that the system feature has been activated (ACT IAFEAT).

1.4.5 Counter Administration

1.4.5.1 Creation of CountersCounters can be created in the transient memory area of the CP to record meter pulsesfor 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

A30808-X3003-X458-2-7619 IN – 71


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

A uniform counter administration concept has been introduced. It covers uniform proce-dures for the editing, saving and regeneration of subscriber, statistical, trunk and TFScounters. The existing security mechanisms for IARAcounters have been adapted tothis new concept, but otherwise the treatment of IARA counters is still somewhatdifferent to that of the other counters.

To allow the contents of the counters to be read out and processed, the format, counterthreshold and directory number type must be defined for each type of counter withcommand ENTR METADM.

For subscriber counters, the format defines the selection of counters and the recordlength 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 TFScounters it defines the accuracy of the code identification.

The directory number type defines the subscriber (in terms of line type) for whom chargerecords are to be written to the billing file.

1.4.5.2 Creation of Backup FilesDepending on the type of counters activated, backup files are created on the followingoccasions:– 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 savetime, 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 thecontents are not valid, they are regenerated from the last backup file and then saved todisk. If errors are found both in the counters themselves and in the backup file, an alarmis 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 anintermediate save, the checksum byte is calculated over the counter contents, evalu-ated, 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 countersST for statistical countersTR for trunk metersTF for TFS counters.

1.4.5.3 Billing FileFor billing, a billing file must be generated for each counter type (once a month forexample), using

IN – 72 A30808-X3003-X458-2-7619


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

Billing files are stored under the name CA.xx.CHA, where

xx = SU for subscriber countersST for statistical countersTR for trunk metersTF 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 postpro-cessing 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 theprevious APS generation. Unlike ODAGEN runs or APS changes, generation fallbackincludes 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 hasbeen set for one or more counters, this information is output at the OMT screen every10 minutes, because meter saving is not possible during this time. Entering commandSAVE MET forces display of the blocked counter types. Because the counter contentsare regenerated from a backup file after fallback, any meter pulses received for thesubscriber, trunk, statistics and TFS counters in the interim period are not counted, andin 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 APSchange 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 countersST for statistical countersTR for trunk metersTF 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

A30808-X3003-X458-2-7619 IN – 73


and the APS change files are transferred from tape to disk (TRANS FILE). They are alsorenamed, because CA. files are write-protected. Then the counter contents are readfrom the APS change file with

REG MET: TYPE=...,FILE= <new filename>;

and added to the counts that have accumulated since system start and the regenerationrun. In the case of subscriber counters, this is only possible if the LAC has not changedas a results of the APS change. Furthermore, the thresholds defined for the counters inthe 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 newbackup 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 thefollowing order:

1. Meter checkSAVE MET: FUNC=CHECK;This input executes functions that correspond to those of the intermediate savedefined under ENTR METSAV

2. Simple meter restorationSAVE MET: FUNC=SAVE;First, new backup files are created for all activated counter types. Their validity ischecked block by block by calculating checksum bytes. If checksum errors arefound, the corresponding counts are taken from the old, error-free backup file. Ifmore than 10 such errors occur in the same block, the entire block is taken from theold backup file. Errors that occur only in the counters, and thus in the new backupfile 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 currentbackup file.

3. Meter restoration after double errorsSAVE MET: FUNC=SAVE;REFILE= CA.xx.UCHA;Double errors are checksum errors that are found both in the counter memory andin 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 fileshould always be held available on tape. It must be a file from the current APS,however.

4. Meter restoration after double errors without repair fileSAVE MET:FUNC=SAVE;REFILE = CA.xx.UCHA, ZEROIN=YES ;This command is equivalent to that in point 3. above. The only difference is that, incases where checksum errors have been found in memory, in the backup file and inthe repair file, or if these files are not available or are out of date, then the counts inquestion 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, incases where checksum errors have been found in memory, in the backup file and inthe repair file, or if these files are not available or are out of date, then the counts inquestion are reset to zero.Here too, the reinitialized counts are output at the OMT.

IN – 74 A30808-X3003-X458-2-7619


1.4.6 Subscriber MetersEach subscriber is assigned 5 counters for use as charge meters when created. Howmany of these are actually used can be set by means of CR ZOPT. When the countersare activated it is important to ensure that they are consistent with the counters activatedin parameter FORMAT of command ENTR METADM. If only one is used for asubscriber, all charges are accumulated on this one. If a subscriber is assigned severalcounters, the number of calls, the call charges, the facility input charges and the facilityusage charges can be registered on separate counters.

Call charge meter

The counter to be used for registering the call charges is specified in commandCR ZOPT (parameter SUCHCNTR). Any of the counters 1 - 5 can be used for the callcharges.

Meter for number of calls made

The counter to be used for registering the number of calls is specified in commandCR 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 theinput command ENTR CDTDAT. Different counters can be entered for subscribercontrolled inputs and subscriber facility usage.

Counters which store the number of calls (parameter SUCHCNTR) in commandCR ZOPT) may not be used as charge meters, since this would result in the mutilationof data.

1.4.7 Statistics Meters

1.4.7.1 Use of Statistics MetersStatistics metering can be created in order, for example, to support the network manage-ment system with information on traffic distribution, for statistical purposes, or forinteradministration revenue accounting. In order to perform statistics metering, the callcharge 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 (zonepoints, routes, incoming or bothway trunk groups). The assignment of this index meansthat for calls which pass via one of these objects the number of calls, the number ofmeter pulses, and (in certain cases) the call duration are registered in sets of statisticsmeters. 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.

A30808-X3003-X458-2-7619 IN – 75


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 CurrentlyActive Statistics MeterFor statistics metering, up to 256 statistics indices can be assigned for objects of thesame type (see Fig. 1.27).

Fig. 1.27 Assignment of statistics indices to statistics meter groups

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

•••

Statistics meter groups

Statistics index 0

Statistics index 1

Statistics index 2

Statistics index X

Statistics index 253



•••

Statistics-metergroup 14


Registration point X

Registration point 0













Statistics indices

IN – 76 A30808-X3003-X458-2-7619


numbers, up to 16 statistics meter groups, each with 256 registration points, can becreated. If a number of groups have been formed, a statistics index refers to the corre-sponding registration points in all statistics meter groups which have been created.

Statistics meter groups are directly related to directory number blocks, i.e. the directorynumber (calling party number in the own exchange) determines the statistics metergroup in which the relevant registration point is addressed.

In the case of calls which reach the exchange via a specified trunk group, the meterpulses for the given statistics index are metered in statistics meter group 0, since thecalling party number does not belong to the directory number volume of the ownexchange and therefore cannot be assigned to a group.

Up to 6 time groups (depending on the time, the weekday category and the date), eachwith 3 subscriber types (ordinary subscriber, coinbox line, service handset) can becreated for a registration point. This means that 18 sets of statistics meters are available;these are configured as summation meters (see Fig. 1.28).

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 thisgroup.

A set of statistics meters consists of three meters:– number of calls,– number of charge units,

Statistics meter set 3Statistics meter set 2Statistics meter set 1

Subscriber Coinbox line Service handset

Registration point ”X”

Time group 0

Statistics meter set 6Statistics meter set 5Statistics meter set 4 Time group 1





A30808-X3003-X458-2-7619 IN – 77


– 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 commandDISP STATMET. The number of statistics meter groups can be increased to a maximumof 16 by way of an ODAGEN run (using MOD DBSIZE). Statistics meter group 0 ispermanently configured. A statistics meter group consists of 256 registration points. Thisresults in a maximum of 4096 registration points for statistics metering for zone pointsand 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 group0.

In the event of a call, the statistics index is read out of the SETUP data. It points to thecorresponding registration points in the statistics meter groups.

1.4.7.3 Statistics Meter SwitchoverWhen statistics meter switchover takes place, there is a changeover from one timegroup to another, depending on the time, the weekday category and/or the tariff switcho-vers.

Statistics meter switchover is always advisable when, for example, the same tariffswitchovers apply to zones which are linked via one or more zone points with the samestatistics 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 todifferent 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 rele-vant statistics meter groups commences at the time of switchover.

The time of switchover must be entered at least 10 minutes beforehand. This switchovertime 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 MetersWith the aid of trunk meters, the traffic between different operating companies can bemonitored 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 meterpulses. If a trunk group is bothway, it can only be used in one direction for trunk groupmetering, i.e. either in the incoming or the outgoing direction, otherwise the meter read-ings will be distorted. For incoming trunk groups, metering is created withGCOS=TRMET on the basis of the trunk group data. For outgoing trunk groups, thetrunk group data must also be created with GCOS=TRMETand metering must beenabled 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 thefollowing, 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. Thedirection of a call is from the B side (of the first exchange) to the A side (of the second

IN – 78 A30808-X3003-X458-2-7619


exchange).

A trunk meter consists of a set of 5 counters:

1. number of successful incoming and outgoing calls2. meter pulses received from the B side before the called party answers3. number of meter pulses received from the B side in the course of the call4. meter pulses received from the B side after the calling party has gone on-hook5. 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 therespective GP and forwarded to the CP at the end of the call (meter 3). Meter pulseswhich are received outside the call state, i.e. erroneously, are immediately forwardedfrom the GP to the CP (meters 2, 4 and 5).

1.4.9 Individual Call Data Administration FeatureThe individual call data administration feature is created in order to collect the chargedata for each call in the form of a data record. These records can then be postprocessedin a data processing system and used for detailed billing. With certain types of data it ispossible to print out the data records on the on-line printer as soon as they have beencompiled.

In some countries the record layout deviates from the standard layout (e.g. becauseadditional data are requested). Data may also be required in different codes for the post-processing computers (binary, hexadecimal, etc.). There are copying processes(AGFRx) for such adaptations; these can be activated when the record files are copiedfrom disk to tape or from disk to host processor.

Fig. 1.29 shows an overview of the different types of individual call data administration

Fig. 1.29 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).

Immediate printout

MOB PMOB FIR IARA INA

AMAI MOBI

AMA DEB

Individual call data administration feature

A30808-X3003-X458-2-7619 IN – 79


• DEBDEB data are also used for charge accounting. Registration is dependent on thecalling party.

• MOBMOB data are used for observation of the activities (originating and terminatingtraffic, FAIS/FAU) of individual subscribers. Registration is dependent on the callingparty (assignment by means ofACT MOBS) and is for a set period (e.g. one month).

• PMOBPMOB 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.

• FIRFIR data are used for recording the creation and cancellation of account suspen-sions by the operating company. Registration is dependent on the type of suspen-sion (assignment by means of CR FAICHA, ).

• INAINA 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 ismade when an AMA or DEB data record is created and a subscriber is in the ”imme-diate output” mode; .

• MOBIMOBI data are used for the immediate printout of MOBdata records. Printout isdependent 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 becomedue (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 thecall is answered);

– inputs by the administration .

If several types of recording are detected for a call (e.g. AMA and DEB or AMA for thecall 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.

IN – 80 A30808-X3003-X458-2-7619


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, inter-mediate records are created (e.g. every 30 minutes). The timer for this function can beadministered.

AMA data are collected in a duplicated cyclic disk file. These data are made availablefor 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 meansof 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 thelikelihood of operator assistance being required at night. By assigning an alarm to thislower threshold value it may be possible to make the backup copy during normal workinghours.

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 hasbeen 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 METERINGhas 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 becomedue (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 eachsubscriber, however. The records are stored in the AMA file. They are marked (a set bit

A30808-X3003-X458-2-7619 IN – 81


or flag), so that they can be separated from the AMA records at the postprocessingstage.

If both AMA and DEB are required for a call (DEB subscriber calls via a zone point withAMA ), only the AMA record is produced. This record contains the EXTSND andALTNSD 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 aservice 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 byOMN:SSS-SU:MSC (Subscriber Administration), which contains more detailed informa-tion on MOB. It is only referred to here in order to complete the description of communi-cations data recording.

Subscribers can apply for MOB for a limited period of time. They do not necessarily haveto be supplied with meter pulses, since a MOB data record is also created for non-chargeable 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 usagebilling 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 beencreated 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 createdin order to record the period of observation.

IN – 82 A30808-X3003-X458-2-7619


If a MOB data record is required for several purposes (e.g. for the call and for the usageof 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 orin response to an MML request.

MOB data are collected in a double cyclic file. For postprocessing, the data can becopied 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 ofthe tasks covered by OMN:SSS-SU:MSC, which contains more detailed information onPMOB . It is only referred to here in order to complete the description of communicationsdata recording.

Unlike the procedure for MOB , with PMOB a data record is only created if chargesexceed a set limit.

PMOB is part of the exchange data. The threshold value set in an exchange applies toall subscribers.

With PMOB , the subscriber meters must be pulsed. It is therefore necessary to createthe appropriate tariffs and zone points with METERING in an exchange involved in thecall.

If another data record (AMA, DEB or MOB ) has been generated for a call in which thePMOB 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 theprinter by means of an MML command.

1.4.10 Call Charge Registration in the Intelligent Network (IN)

1.4.10.1 GeneralWith 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 require-ments 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)

A30808-X3003-X458-2-7619 IN – 83


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.

Fig. 1.30 IN architecture (simplified)

The interface between the telephone network (PSTN) and the intelligent network (IN) isthe 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 thecharges are registered:• call charge registration by the Service Control Point (SCP) or the Service Manage-

ment 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 eachIN call. The data required are collected in the SCP (on the basis of the call data suppliedby the SSP, which are transferred to the SCP/SMS at regular intervals). The customer-specific 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 tele-phone network. The SCP can affect the charge registration, e.g. by transmitting/prede-fining the zone number to be used.

Charge registration by the SSP can be used for billing both the service user and theservice subscriber.

OMN:SSS-TA contains the tasks involved in the administration of charge registration bythe SSP.

CCS7

X.25

SMS

SSP

SCP

Tele-phone

network

A B

CCS7

X.25

SMS

SCP

A

SSPOVSt

B

SSP local

SSP on local level SSP on transit level

Telephonenetwork

IN – 84 A30808-X3003-X458-2-7619


1.4.10.2 Terminology

Service provider

The service provider is the telephone company that offers IN services to the servicesubscriber, for instance, freephone.

Service subscriber

The service subscriber is, for example, a mail order company which accepts the chargesfor orders placed by telephone.

Calling line

The calling line in an IN call is the calling party. The calling line can be either the serviceuser or the service subscriber.

Service user

The service user is, for example, a customer who places orders with a mail ordercompany free of charge.

Charge registration for the calling line

Normally the calling line's charges are registered in the PSTN by means of PSTNmethods. 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 AMAdata are written to the PSTN AMA file.

PSTN charge registration (except for non-chargeable calls) should only be performed ifthe 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; anyAMAdata 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 tobe processed.

IN-specific charge

This term refers to the determining of a zone, depending on the IN service used, butindependently 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 processedaccording to the default settings. The charge registration default value can besuppressed as a project-specific option (flag).

A30808-X3003-X458-2-7619 IN – 85


Flexible charge registration

The SSP can change zone or create a new data record when a call is set up to a newdestination (the primary destination is busy). This includes calls to the intelligentperiphery (IP).

Divided charge registration

This term denotes simultaneous billing of two parties engaged in an IN call, usually thecalling line and the service subscriber. In some instances the charges have to be splitbetween 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: GeneralThe question of who has to pay for what must be dealt with separately for each INsubscriber. The amount of the charges to be paid by the calling line and/or the servicesubscriber is dependent on the particular service. In addition, due account must betaken of the network-specific aspects (location of zoning, signal repertoire of signalingsystem, etc.).

In EWSD there are three options for registering charges for IN services:

1. charge registration only by the PSTN2. charge registration only by IN components3. charge registration divided between PSTN and IN.

ExampleThe charges for the universal number (UN) service can be registered as follows. Thecharge total is divided between the calling line and the service subscriber (calledparty). The user is charged for the ascending branch (from the calling party to theSSP). 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 SSPto 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). Itthen branches to the relevant trigger profile in the CP. As a result of the subsequentcommunication with the SCP, the SSP obtains the actual directory number of the calledparty and the corresponding zone.

From ZOCHA=ZONINHI in the command CR ZOPT, the SSP knows that it must use thezone sent by the SCP.

If the anticipated zone is not received, the charges for the IN call can be registered onthe basis of default values. These default values can be set in the IN trigger profile in theCP 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, theservice subscriber only receives his data record if the call to the called party was set up

IN – 86 A30808-X3003-X458-2-7619


successfully.

Special case

Through the use of IN components, the zoning of international calls by the PSTN is nolonger necessary. With this application, the calls are routed on the basis of dialed digitsand 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 createdwith 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 chargesare only assigned to the calling subscriber.• Zoning in the home exchange:

CR ZOPT: CODE=0180, ZONO=268, BILLING=METERING, SUCH-CNTR=CNTR1;

• Zoning in a higher-level exchange in the telephone network; charge registration inthe home exchange:CR ZOPT: CODE=0190, ZOCHA=ZONINHI, BILLING=METERING, SUCH-CNTR=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 chargeband 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 andIARAMA):

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. The CCS7 connection from the SSP to the SCP must be established2. The triggers in the CP must be entered and activated (CR INTRIG and ACT INTRIG3. The IN-specific announcements must be prepared (CR INC)4. 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).

A30808-X3003-X458-2-7619 IN – 87


Case 1: Identification via the code points

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

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=IN–6–”FPHS1”;

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 thetrigger profile (project-specific).

Zone 355 is to be used for zoning:

CR INTRIG: PRID=<trigger-ID>, SKEY=<service>, ... ,CHGINF=ZONE–355;

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=1–10000;

ENTR TARSW: ZONO=468, NAME=IN1, TIME=14–00, DATE=99–12–15;

If the call charge data are not recorded in the SSP, the relevant zone must be passedthrough to the exchange in question. The charge band message is used for this:

MOD ZOINF: ZONO=345, CHBNO=145;

SCP

A

SSPLocal

exch.

B

Local

exch.

zonedZONINHI

ZOCHA

Trigger via code point: ZOCHA=ZONINHI

Trigger via zone point: ZOCHA=ZONEXTI

IN – 88 A30808-X3003-X458-2-7619


Case 2: Identification via the zone points

This is a special case for the use of the intelligent network. The code points are createdwithout the IN trigger; routing is based on the dialed digits. The SCP is only activated inorder to determine the valid zone. To this end, the reference to the trigger profile iscreated in the zone point (ZOCHA=ZONEXT). The call is then zoned according to thezone 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=ZONEXT–”INTCALL”;

The value for ZOCHA in the command CR ZOPT must be identical with the value forPRID 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 INservice, since there is no service user. Because of this, no IN-specific AMAdata recordsneed to be created. The calling subscriber pays for the complete connection from A to B.

1.4.11 Reverse ChargingThe reverse charging service (RCS) allows the calling party to set up a call to a calledparty 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, forinstance coinbox lines. This reduces overuse of the service by individuals experimentingwith it.

A30808-X3003-X458-2-7619 IN – 89


Configuration

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 partynumber, e.g.:

8XX ZX... NX...

A

AN3

B

SN

LTGC (RCS)

RCS loop

announce-ment control

software connectionlogical connection

physical connection

DIU2AC

AN1

AN2

AN5

AN4

DIU1INC

DIU3PB

DIU0OUT

IN – 90 A30808-X3003-X458-2-7619


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 whenthe called party accepts the call. The called party is marked in the AMA ticket as thepaying party.

It is also possible for tickets to be generated for calls that are not accepted and forunsuccessful call attempts.

The RCS exchange only registers charges for the connection from A to B. Facility usagecharges for supplementary services such as abbreviated dialing must be registered atthe originating exchange.

1.5 Notes on the Iridium ProjectThe 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 SSStechnology as the gateway switching center (GSC) to the terrestrial networks. In GSMterminology, the entire Iridium network is classed as a single "PLMN". This network doesnot make any distinction between a CSC (combined switching center) and a mobile(PLMN)-typical network node (MSC, VLR, etc.). Wired subscribers and PBXs areconnected instead to the MSC. The base station system (BSC and BTS) is replaced bya 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 thefeatures specifically agreed upon in the contract are actually supplied.

A30808-X3003-X458-1-7619 TL – 1


2 Task List (TL)

2.1 Selection of Charging TypeCreate PSTN charging of transit calls

GCOS=PSTNTGRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR TGDAT

2.2 PLMN Charging

2.2.1 Holiday and Weekday Category AdministrationDisplay fixed holiday table (YEAR=X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP HOLICALDisplay variable holiday table (YEAR=xxxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP HOLICALDisplay weekday category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP WDCATCreate fixed holidays in a new holiday table (YEAR=X) . . . . . . . . . . . . . . . . . . CR HOLICALCreate variable holidays in a new holiday table (YEAR=xxxx). . . . . . . . . . . . . . CR HOLICALModify weekday category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD WDCATCancel fixed holiday table (YEAR=X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN HOLICALCancel variable holiday table (YEAR=xxxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN HOLICALModify of existing fixed or variable holiday tables

(add or remove holidays) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD HOLICAL

2.2.2 Automatic Message Accounting AdministrationDisplay current filling level of MCR file

(ALL=Y, FILE=IA.ICMCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILEDisplay MCR file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP MCRActivate collection of billing data for interrogation

(FEAT=CHINTREC, STAT=ACT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MSERVOPTActivate collection of billing data for transit calls

(FEAT=CHTRANS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MSERVOPTActivate collection of billing data for unsuccessful call attempts

(FEAT=CALLATT, STAT=ACT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MSERVOPTActivate cell dependent charging

(FEAT=CELLDCH, STAT=ACT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MSERVOPTActivate feature FLAM compression for billing files

(FEAT=FLAMCOMP, STAT=ACT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MSERVOPTCreate FLAM compression of billing files

TS-305Activate collection of billing data for non-chargeable call attempts

(FEAT=CHFCATT, STAT=ACT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-300Activate feature “immediate printout” of billing files

(TYPE=MCRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACT IAFEAT

i 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 seenfrom the command acknowledgement output by the system whether the command entered was correctlyexecuted (see Operator Guidelines OGL). If it should be necessary for administrative reasons to receivean acknowledgement of the executed tasks in addition to the run listing, the contents of the databasecan 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.

TL – 2 A30808-X3003-X458-1-7619


Deactivate FLAM compression of billing file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DACT FILEFEATCancel allocation of FLAM compression to a file. . . . . . . . . . . . . . . . . . . . . . . . TS-307Copy MCR file to a remote processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-302Copy MCR file from magnetic disk to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-301Copy a specific MCR file from magnetic disk to tape . . . . . . . . . . . . . . . . . . . TP-302

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 mobile-specific tariffs (parameter sets) . . . . . . . . . . . . . . . . . . . . . . . . . DISP MTARDisplay mobile-specific tariff categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP MTARCATDisplay switchover times for tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP MTARCATDisplay mobile-specific zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP MZONEDisplay mobile-specific zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP MZOPTCreate zoning for mobile originating calls,

call attempts, call forwarding (zoning in the own MSC). . . . . . . . . . . . . TS-600Enter mobile-specific tariffs (parameter sets) . . . . . . . . . . . . . . . . . . . . . . . . . ENTR MTARCreate mobile-specific tariff categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-601Enter switchover times for mobile-specific tariffs . . . . . . . . . . . . . . . . . . . . . . TS-601Create mobile-specific zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-602Assign tariff categories to call/transmission type. . . . . . . . . . . . . . . . . . . . . . . . TS-602Create mobile-specific zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-603Modify mobile-specific tariffs (parameter sets) . . . . . . . . . . . . . . . . . . . . . . . . . MOD MTARModify switchover times within a tariff category . . . . . . . . . . . . . . . . . . . . . . . . MOD MTARCATModify allocation of mobile-specific tariffs to a tariff category . . . . . . . . . . . . . . MOD MTARCATModify mobile-specific zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-604Modify allocation of tariff categories to call/transmission type . . . . . . . . . . . . . TS-604Modify mobile-specific zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MZOPTCancel zoning for mobile originating calls, call attempts, call forwarding . . . . . TS-605Cancel mobile-specific tariffs (parameter sets) . . . . . . . . . . . . . . . . . . . . . . . . . TS-606Cancel mobile-specific tariff categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-607Cancel allocation of tariff categories to call types . . . . . . . . . . . . . . . . . . . . . . . TS-608Cancel mobile-specific zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-608Cancel mobile-specific zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MZOPT

2.2.3.2 Administration of Tariffs for Mobile Terminating Calls (PLMN Tariffs)

Display PLMN tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP PLMNTAREnter PLMN tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR PLMNTARModify PLMN tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD PLMNTARCancel PLMN tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN PLMNTAR

2.2.4 Charge Registration in the Intelligent Network (IN)Activate systemfeature “Billing for IN”

(TYPE=INA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACT IAFEATCreate code point for IN service triggering

(ZOCHA=ZONINHI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR MZOPTCreate standard charge registration for IN services . . . . . . . . . . . . . . . . . . . . . CR INTRIGCreate acceptance of zone from charge band message

(TKZOINF=YES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR MZOPT

2.2.5 Administration of Control Meters for Connection GroupsMeter savingDisplay meter save time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP METSAV

A30808-X3003-X458-1-7619 TL – 3


Enter meter save time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR METSAVModify meter save time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-721Save charges to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAVE MET

Call charge dataDisplay meter administration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP METADMDisplay call charge data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP METEnter meter administration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR METADMCopy statistics meter files to magnetic tape. . . . . . . . . . . . . . . . . . . . . . . . . . . TS-732Copy trunk group control meter files to magnetic tape . . . . . . . . . . . . . . . . . . TS-733

2.2.6 Administration of Statistics MeterStatistics meterDisplay statistics meter group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP STMETGRPDisplay statistics meter call duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP CDTDATActivate statistics meter call duration

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

(using: ALTNSD=DURATCUM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN CDTDAT

Statistics meter switching timesDisplay statistics meter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP STATMETDisplay assignment of statistics meters to objects . . . . . . . . . . . . . . . . . . . . . . . DISP STATMETDisplay trunk group control meter readings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP TRMETDisplay switching time for statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP STATSWEnter switching time for statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR STATSWModify switching time for statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-824Cancel switching time for statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN STATSW

2.3 Interadministration Revenue Accounting (IARA) Administration

2.3.1 IARSTAT Destination and IARSTAT Origin Name AdministrationIARAMAActivate systemfeature IARAMA

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

IARSTAT Destination and IARSTAT Origin Name AdministrationDisplay the assignment of incoming or bothway trunk groups

to the IARSTAT origin name(s) (TGNO). . . . . . . . . . . . . . . . . . . . . . . . . DISP IARNAMEDisplay the assignment of destinations/routes

to the IARSTAT origin name(s) (DEST, RTNO) . . . . . . . . . . . . . . . . . . DISP IARNAMEDisplay IARSTAT destination names or IARSTAT origin names assigned

to a measurement type (MTYPE, DNAME or ONAME) . . . . . . . . . . . . . DISP IARDATDisplay the status of IARSTAT destination names or IARSTAT origin names

(MTYPE, DNAME or ONAME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARDATDisplay the number of used and free IARSTAT destination names and

IARSTAT origin names of a measurement type (only MTYPE) . . . . . . . DISP IARDATAssign a destination/route or a destination/trunk group

to a new or to an already existing IARSTAT destination name . . . . . . . TS-500Assign an incoming or bothway trunk group to a new or to an

already existing IARSTAT origin name. . . . . . . . . . . . . . . . . . . . . . . . . . TS-501Modify the assignment of an IARSTAT destination name to

a destination/route or destination/trunk group . . . . . . . . . . . . . . . . . . . . TS-502Modify the assignment of an IARSTAT origin name to an outgoing or

TL – 4 A30808-X3003-X458-1-7619


bothway trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-502Modify IARA destination or origin name

(IARA matrix points are modified/canceled automatically) . . . . . . . . . . MOD IARDATCancel assignment of a destination/route for IARSTAT destination names

or outgoing/bothway trunk group for IARSTAT origin names . . . . . . . . TP-503Cancel relating to a route:

all assignments for the IARA destination names . . . . . . . . . . . . . . . . . . TS-504Cancel relating to an outgoing or bothway trunk group:

all assignments for IARSTAT destination names . . . . . . . . . . . . . . . . . TS-506Cancel relating to an incoming or bothway trunk group:

all assignments for the IARSTAT origin names. . . . . . . . . . . . . . . . . . . TP-503

IARSTAT Matrix Point AdministrationDisplay number of created and free IARAS matrix points of one

measurement type (only parameter MTYPE) . . . . . . . . . . . . . . . . . . . . DISP IARMPTDisplay total number of used and free IARSTAT counters for all

measurement types (MTYPE = any mtype). . . . . . . . . . . . . . . . . . . . . . DISP IARMPTDisplay assignment of the connection types to the IARA–counters of the

IARSTAT matrix point (parameter DNAME and/or ONAME). . . . . . . . . DISP IARMPTDisplay assignment of an IARSTAT tariff zone to one or more

IARA matrix points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARZONECreate IARA matrix point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-510Assign IARA matrix point to one or more IARSTAT tariff zones . . . . . . . . . . . . TS-511Modify IARA matrix point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-512Modify IARSTAT tarif zone for one or more IARA matrix points . . . . . . . . . . . . TS-513Deactivate generation of AMA data records while maintaining

registration in counters (CNTRS=NO, TICKET=YES). . . . . . . . . . . . . . CAN IARMPTDeactivate registration in counters while maintaining generation of

AMA data records (CNTRS=YES, TICKET=NO) . . . . . . . . . . . . . . . . . CAN IARMPTCancel IARSTAT matrix point

including assignment to IARSTAT tariff zone . . . . . . . . . . . . . . . . . . . . CAN IARMPTCancel assignment of IARSTAT tariff zone to one or more

IARSTAT matrix points (evening and night counters are nolonger used). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN IARZONE

IARSTAT Registration Job AdministrationDisplay IARSTAT jobs and the relevant file names . . . . . . . . . . . . . . . . . . . . . . DISP IARJOBCreate IARSTAT registration job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-523Cancel IARSTAT registration job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-524

Administration of IARSTAT connection groupsDisplay all names of connection groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARGRPDisplay assignment of connection types and/or

transmission rates to connection group names . . . . . . . . . . . . . . . . . . . DISP IARCONCreate IARSTAT connection groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-530Modify assignment of connection types and/or

transmission rates to connection group names . . . . . . . . . . . . . . . . . . . TS-531Cancel IARSTAT connection groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-532

IARSTAT Tariff Switching Times AdministrationDisplay IARSTAT tariff switching times for IARSTAT tariff zones . . . . . . . . . . . DISP IARTMPDCreate IARSTAT tariff switching times for an IARSTAT tariff zone. . . . . . . . . . CR IARTMPDModify IARSTAT tariff switching times for an IARSTAT tariff zone. . . . . . . . . . MOD IARTMPDCancel IARSTAT tariff switching times for an IARSTAT tariff zone. . . . . . . . . . CAN IARTMPD

IARSTAT Save Times AdministrationDisplay IARSTAT save time for continuous registration job. . . . . . . . . . . . . . . . DISP IARSAVDAEnter IARSTAT save time for continuous registration job. . . . . . . . . . . . . . . . TP-530

A30808-X3003-X458-1-7619 TL – 5


Modify IARSTAT save time for continuous registration job . . . . . . . . . . . . . . . . TP-530Cancel IARSTAT save time for continuous registration job . . . . . . . . . . . . . . . . CAN IARSAVDA

IARSTAT Data AdministrationDisplay IARSTAT measurement results not yet stored in a post-processing

file (MTYPE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARSTATDisplay IARSTAT measurement results stored in a post-processing

file (FILE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARSTATDisplay status of the IARSTAT file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARFILESave IARSTAT counters to a post-processing file intermediately . . . . . . . . . . COPY IARACCT

IARSTAT Post Processing File AdministrationDisplay IARSTAT post-processing files stored on magnetic disk (FILE=IR.) . . . DISP FILEDisplay IARSTAT post-processing files still in use by an IARSTAT

registration job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARJOBCopy IARSTAT post-processing file to magnetic tape. . . . . . . . . . . . . . . . . . . TP-550

2.4 Charging of Wired Subscribers of a CombinedSwitching Center (CSC)

2.4.1 Subscriber TariffsTariffsDisplay tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP TAREnter tariffs for access charges with single pulse metering (SPM) or

multiple pulse metering (MPM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-701Enter tariffs for communication charges with periodic pulse metering (PPM)

or periodic multiple pulse metering (PMM) . . . . . . . . . . . . . . . . . . . . . . . TP-702Enter tariff sequences in pulse format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-703Modify tariff (once, not periodically) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-704Cancel tariff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-705Cancel tariff names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-706Cancel tariff zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-707

Tariff switchover timesDisplay tariff switchover times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP TARSWEnter tariff switchover time for a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-720Modify tariff switchover times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-721Cancel tariff switchover times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-722

2.4.2 Zone PointsDisplay zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP ZOPTCreate zone point for a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-761Create zone point with zone characteristic

using: CODE, ZOCHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR ZOPTCreate zone point for an announcement

using: CODE, INCEPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR ZOPTSplit zone point after digit

using: DIGIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPLIT ZOPTSplit zone point after originating mark

using: ORIG2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPLIT ZOPTSplit zone point after category

using: MFCAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPLIT ZOPTSplit zone point after language digit

using: ZDIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPLIT ZOPTSplit zone point after freephone indicator

TL – 6 A30808-X3003-X458-1-7619


using: FPH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SPLIT ZOPTModify zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPTMerge zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-767Create zone points for directory number ranges belonging to the

local network of a foreign-exchange subscriber . . . . . . . . . . . . . . . . . . TP-769Modify zone points for directory number ranges belonging to the

local network of a foreign-exchange subscriber . . . . . . . . . . . . . . . . . . TP-770Cancel zone points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN ZOPT

2.4.3 Charge Band Messages and Zone Traffic TypesCharge Band MessagesDisplay assignment of charge band message to zones

using: CHBNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP ZOINFEnter assignment of charge band message to zones

using: ZONO, CHBNO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOINFModify assignment of charge band message to zones

using: ZONO, CHBNO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOINFCancel assignment of charge band message to zones

using: ZONO, CHBNO = 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOINFAllow acceptance of charge band message from zones

using: TKZOINF = YES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPT

Zone traffic typesDisplay assignment of zone traffic type to zones

using: ZONO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOINFModify assignment of zone traffic type to zones

using: ZONO, ZOTRAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOINF

2.4.4 Subscriber FacilitiesRegistration of facility input chargesDisplay charge registration for facility input . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FAICHACreate charge registration by AMA for facility input by subscriber

using: BILLING = AMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR FAICHACreate charge registration by meter pulses for facility input by subscriber

using: BILLING = METERING, METPULS . . . . . . . . . . . . . . . . . . . . . . CR FAICHACreate charge registration by AMA for facility input by operator

using: FAIOPER = AMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR FAICHAModify charge registration for facility input . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD FAICHACancel charge registration for facility input . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN FAICHAEnter counters for facility input charges

using: FAICNTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR CDTDAT

Registration of facility usage chargesDisplay charge registration for facility usage . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FAUCHACreate charge registration by AMA for facility usage

using: BILLING = AMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR FAUCHACreate charge registration by meter pulses for facility usage

using: BILLING = METERING, METPULS . . . . . . . . . . . . . . . . . . . . . . CR FAUCHAModify charge registration for facility usage . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD FAUCHACancel charge registration for facility usage . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN FAUCHAEnter counters for facility usage charges

using: FAUCNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR CDTDAT

Account suspension ordersActivate systemfeature for account suspension order

using: TYPE = FIR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACT IAFEAT

A30808-X3003-X458-1-7619 TL – 7


Display recording of account suspension order . . . . . . . . . . . . . . . . . . . . . . . . . DISP FAICHACreate recording of account suspension order (activate)

using: FAIOPER = FIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR FAICHAModify recording of account suspension order (activate/deactivate) . . . . . . . . . MOD FAICHACancel recording of account suspension order (deactivate). . . . . . . . . . . . . . . . CAN FAICHADisplay of account suspension order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-840Copy cyclic disk file

using: FILE = IA.ICFIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRANS FILE

2.4.5 Meter AdministrationMeter savingDisplay meter saving times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP METSAVEnter meter saving time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR METSAVModify meter saving time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-721Save charge meters to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAVE METSave charge meters to APS change file (prior to APS change)

using: FUNC = APSCHANG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDIT METRegenerate charge meters (after an APS change) . . . . . . . . . . . . . . . . . . . . . . . . . . REG MET

Charge dataActivate meter type

using: MET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR EXDDATDisplay meter administration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP METADMEnter meter administration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR METADMDeactivate charge meter blocking (after regeneration)

using: FUNC = FALLBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAVE METCopy subscriber charge files to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-731Copy subscriber charge files to host processor . . . . . . . . . . . . . . . . . . . . . . . . TP-811

2.4.6 Subscriber MetersAdministration of meters for call charges and number of callsDisplay subscriber meters

using: TYPE = METSUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP METEnter meters for call charges

using: SUCHCNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPTModify meters for call charges

using: SUCHCNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPTCancel meters for call charges

using: SUCHCNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPTEnter meters for number of calls

using: SUCACNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPTModify meters for number of calls

using: SUCACNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPTCancel meters for number of calls

using: SUCACNTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPT

2.4.7 Statistics MetersAdministration of statistics metersOverview of commands required for statistics meter administration . . . . . . . . . . . TP-820Enter statistics meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-740Display statistics meter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP STATMETDisplay assignment of statistics meters to objects

using: DESC = YES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP STATMETDisplay recording of call duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP CDTDAT

TL – 8 A30808-X3003-X458-1-7619


Assign statistics meter groups to directory numbers. . . . . . . . . . . . . . . . . . . . . MOD DNDisplay statistics meter groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP STMETGRPDisplay assignment of statistics meter groups to directory numbers . . . . . . . . . DISP STMETLNKActivate recording of call duration

using: EXTNSD = CALLDUR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR CDTDATCancel recording of call duration

using: EXTNSD = CALLDUR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN CDTDATCopy statistics meter file to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-732Cancel statistics meter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-741

Administration of statistics meter switchover timesEnter statistics meter switchover time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-822Modify statistics meter switchover time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-824Cancel statistics meter switchover time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN STATSW

2.4.8 Trunk MetersActivate trunk metering (incoming)

using: GCOS = TRMET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR TGDATActivate trunk metering (bothway, outgoing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-830Copy trunk meter files to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-733Display trunk meter readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP TRMET

2.4.9 Automatic Message AccountingAMA data and DEB dataOverview of commands required for AMA administration . . . . . . . . . . . . . . . . . . . TP-900Overview of commands required for DEB administration . . . . . . . . . . . . . . . . . . . TP-905Display current occupancy level of AMA file

using: FILE = IA.ICAMA, ALL = YES. . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILECopy AMA file from disk to tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS-731Copy AMA file from disk to host processor . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-934Display recordings of additional/alternative call data . . . . . . . . . . . . . . . . . . . . DISP CDTDATActivate recordings of additional/alternative call data

using: EXTNSD/ALTNSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR CDTDATEnter recordings of call data for AMA and DEB

using: MARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR CDTDATDeactivate recordings of additional/alternative call data

using: EXTNSD/ALTNSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN CDTDATCancel recordings of call data for AMA and DEB

using: MARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN CDTDAT

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

2.4.10 Charge Registration in the INActivate system feature

using: TYPE = INA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACT IAFEATEnter call data processing for AMA records . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR CDTDATCancel call data processing for AMA records . . . . . . . . . . . . . . . . . . . . . . . . . . CAN CDTDATCreate code point for IN service triggering

using: ZOCHA = ZONINHI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR ZOPTCreate zone point for IN service triggering

using: ZOCHA = ZONEXT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR ZOPTCreate standard charge registration for IN services . . . . . . . . . . . . . . . . . . . . . CR INTRIGRecord charge band message in IN record . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOINF

A30808-X3003-X458-1-7619 TL – 9


Allow acceptance of zone from charge band messageusing: TKZOINF = YES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR ZOPT

2.4.11 Reverse Charging ServiceCreate reverse charging service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TC-303Create charge registration with AMA

using: GCOS = AMAREQD & NOZON. . . . . . . . . . . . . . . . . . . . . . . . . . CR TGRPEnter charge registration for refused calls

using: GCOS = PROP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR TGDATEnter AMA ticket (called number) without RCS access code

using: GCOS = PROP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR TGDATEnter charge registration for unsuccessful call attempts

using: MARKS = UCALLAMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR CDTDATCreate zone point

using: ZOCHA = NOPULSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR ZOPT

2.4.12 Subscriber's Private MeterPrivate meter for analog subscriberActivate private meter

using: LAC, DN, LNATT = SMET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD SUBDeactivate private meter

using: LAC, DN, CLNATT = SMET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD SUB

Private meter for ISDN subscriberActivate private meter (in 3rd path, SERV)

during call, for all callsusing: 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

TL – 10 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TS – 1


3 Task Summary Lists (TS)

TS – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TS-300 – 1


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

TS-300 Activate collection of billing data for non-chargeable call attempts

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

2 Activate the collection of billing data for unsuccessfulcall attempts (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MSERVOPT(FEAT=CALLATT, STAT=ACT)

3 Activate the collection of billing data for non-chargeablecall attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD MSERVOPT(FEAT=CHFCATT, STAT=ACT)

TS-302 – 1 A30808-X3003-X458-1-7619



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

1 Copy the current buffer contents to file IA.ICMCR. . . . . . . . . . . . . . . . . . . . . . . . . . . TRANS BUFFERusing: TYPE=MCR

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

3 Transfer file IA.ICMCR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRANS FILEusing: FILE=IA.ICMCR or FILE=<new name>/IA.ICMCR,PRONAM=<name of remote processor>

4 Check whether the number of copies made equals thenumber of copies required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILEusing: FILE=IA.ICMCR, ALL=YStep 5 may not be carried out until the number of copies requiredhas been reached.

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

6 Cancel cyclic file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REL CYCFILEusing: FILE=IA.ICMCR

A30808-X3003-X458-1-7619 TS-305 – 1



TS-305 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.ICMCRwih FILE=IA.ICMCR, FEAT=FLAMCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR FILEFEAT

2 Activation of FLAM compressionFILE=IA.ICMCR, FEAT=FLAMCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACT FILEFEAT

TS-307 – 1 A30808-X3003-X458-1-7619



TS-307 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

2 Deactivation of FLAM compression for IA.ICMCR file(FILE=IA.ICMCR, FEAT=FLAMCOMP) (if required) . . . . . . . . . . . . . . . . . . . . . . . . . DACT FILEFEAT

3 Cancel of FLAM compression for IA.ICMCR(FILE=IA.ICMCR, FEAT=FLAMCOMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN FILEFEAT

A30808-X3003-X458-1-7619 TS-500 – 1



TS-500 Assign IARA destination name

1a Check whether the destination has been created with the corresponding routeor trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP ROUTEusing: 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 IARNAMEusing: DEST, RTNO, NAME

3b Assign destination and trunk group to an IARSTAT name . . . . . . . . . . . . . . . . . . . . . ENTR IARNAMEusing: DEST, TGNO, NAME

3c Assign destination and subscriber to an IARA name(only for wired subscriber). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR IARNAMEusing: LAC, DIR=DEST, NAME

TS-501 – 1 A30808-X3003-X458-1-7619



TS-501 Assign IARA origin name

1a Check whether the outgoing or bothway trunk grouphas 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:SSS–RO

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

3a Assign a trunk group to an IARSTAT name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR IARNAMEusing: TGNO, NAME

3b Assign destination and subscriber to an IARA name(only for wired subscriber) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARNAMEusing: LAC, DIR=ORIG, NAME

A30808-X3003-X458-1-7619 TS-502 – 1



TS-502 Modify the assignment of an IARSTAT destination name to a destination orroute or of an IARSTAT origin name to a trunk group

1 Check whether IARSTAT matrix points have been created forthis IARSTAT name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARZONEfor destination names: using DNAMEfor origin names: using ONAME

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

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

TS-504 – 1 A30808-X3003-X458-1-7619



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

1 Relating to one IARSTAT measurement type, a route can be assignedonly for one IARSTAT destination name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP DEST

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

A30808-X3003-X458-1-7619 TS-505 – 1



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

1 Display all routes for the destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP ROUTEusing: DEST

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

TS-506 – 1 A30808-X3003-X458-1-7619



TS-506 Relating to an outgoing/bothway trunk group:Cancel all assignments for the IARSTAT destination names

1 Display all routes allocated to the trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP ROUTEusing: TGNO

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

A30808-X3003-X458-1-7619 TS-510 – 1



TS-510 Create IARSTAT matrix point

1 Check whether the IARSTAT destination name is active . . . . . . . . . . . . . . . . . . . . . . DISP IARDATusing: DNAME

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

3 Check whether the IARSTAT origin name is active . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARDATusing: ONAME

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

5 Check whether the matrix point is ”inactive” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP IARMPTusing: DNAME, ONAMENote: A matrix point canceled during an activated registration job willremain in the inactive status as long as the data are not stored in a post-processing file. It cannot be created again during this time.

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

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

TS-511 – 1 A30808-X3003-X458-1-7619



TS-511 Assign IARSTAT matrix points to an IARSTAT tariff zone

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

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

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

A30808-X3003-X458-1-7619 TS-512 – 1



TS-512 Modify IARSTAT matrix point

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

2 Check whether an IARSTAT registration job still exists . . . . . . . . . . . . . . . . . . . . . . . DISP IARJOBAn IARSTAT matrix point canceled during an activated registration job willremain in the inactive status as long as the current IARSTAT registrationcall data are not stored in a postprocessing file.

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

4 Create the new IARSTAT matrix point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TS–510

TS-513 – 1 A30808-X3003-X458-1-7619



TS-513 Modify IARSTAT tariff zone for IARSTAT matrix points

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

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

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

A30808-X3003-X458-1-7619 TS-530 – 1



TS-530 Create IARSTAT connection group

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

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

2 Enter assignment of connection types and/or transmission ratesto connection-group name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR IARCON

TS-531 – 1 A30808-X3003-X458-1-7619



TS-531 Modify IARSTAT connection group

1 Cancel old assignment of connection types and/or transmissionrates to connection-group name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN IARCON

2 Enter new assignment of connection types and/or transmissionrates to connection-group name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR IARCON

A30808-X3003-X458-1-7619 TS-532 – 1



TS-532 Cancel IARSTAT connection group

1 Cancel old assignment of connection types and/or transmissionrates to connection-group name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN IARCON

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

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

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

TS-600 – 1 A30808-X3003-X458-1-7619



TS-600 Create zoning for mobile originating calls, call forwarding,call attempt (zoning in home MSC)

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

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

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

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

A30808-X3003-X458-1-7619 TS-601 – 1



TS-601 Create tariff category

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

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

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

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

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

TS-602 – 1 A30808-X3003-X458-1-7619



TS-602 Create mobile-specific zone

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

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

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

A30808-X3003-X458-1-7619 TS-603 – 1



TS-603 Create mobile-specific zone points

1 Check whether zone points are already created for a part of thedigit combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP MZOPT

DISP ZOPTThe code (digit combination and code type) for which a new zone point is to becreated 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 modifiedinternal digit chains, i. e. it might be necessary in particular to enter existing ZOPTsdifferently, but having the same meanings in terms of content.Example:1. Assume a ZOPT exists with CODE=004 and ORIG2=20 and the internationalprefix 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 internalORIG2 representation for standard MOC-ZOPTs) is located at the third position ofthe digit chain.2. A ZOPT exist with CODE=0045 and ORIG2=20.In this case, an MZOPT cannot be created withCR MZOPT : CODE=45-INAT, CHTYPE=MOC,...The existing ZOPT must be canceled and re-created by means ofCR ZOPT: CODE=0045, ORIG2=20-3,...;This ZOPT has the same switching significance as the obove ZOPT. The only differ-ence lies in the different digit chain used for internal storage of the information usingdigits and origin code ORIG2. It is now possible to enter the MZOPT with thecommand described above.In principle, it is necessary to ensuring canceling and re-creating the zone points thatno “gaps” occur in the zoning of both the mobile zone points (MZOPTs) and the fixednetwork zone points (ZOPTs). It may be necessary to create several new zone pointsso as to be ablate continue zoning all the connections covered by the old zone points.

2 Cancel zone points (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MZOPTCAN ZOPT

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

3b Create zone points for zoning in the next MSC, for calls alreadyzoned or for non-chargeable calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CR MZOPTusing: MZOCHA

3c Create zone points for zoning calls to intercept codes . . . . . . . . . . . . . . . . . . . . . . . . CR MZOPTusing: MINCEPT

TS-604 – 1 A30808-X3003-X458-1-7619



TS-604 Modify mobile-specific zone

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

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

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

A30808-X3003-X458-1-7619 TS-605 – 1



TS-605 Cancel zoning for mobile originating calls,call forwarding, call attempttle

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

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

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

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

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

TS-606 – 1 A30808-X3003-X458-1-7619



TS-606 Cancel mobile-communication tariff

1 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

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

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

A30808-X3003-X458-1-7619 TS-607 – 1



TS-607 Cancel mobile-specific tariff category

1 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

3 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.

TS-608 – 1 A30808-X3003-X458-1-7619



TS-608 Cancel mobile-specific zone

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

2a Cancel zone point (if required). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CAN MZOPTusing: INCEPT=UNOBDE0

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

3 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.

A30808-X3003-X458-1-7619 TS-721 – 1



TS-721 Modify meter save time

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

2 Modify meter save time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR METSAVusing: TIME, CHEKNO

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

TS-731 – 1 A30808-X3003-X458-1-7619



TS-731 Copy subscriber charge file to magnetic tape

1 Edit charges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDIT METusing: FILE = CA.SU.CHA.nn and TYPE = METSUB

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

3 Rewind magnetic tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . REWIND MTusing: MTDThis concludes copying of the file. Steps 4 and 5 are needed to delete the file on thedisk.Caution: The disk file must be deleted immediately after successful transfer,otherwise storage problems may arise on the hard disk!

4 Display file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILEusing: FILE = CA.SU.CHA.nn and ALL = YESObtain expiration date from output mask(EXPDAT = YY-MM-DD)

5 Delete file on disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEL FILEusing: FILE = CA.SU.CHA.nn and EXPDAT = YY-MM-DD

A30808-X3003-X458-1-7619 TS-732 – 1



TS-732 Copy statistics meter file to magnetic tape

1 Edit meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDIT METusing: FILE = CA.ST.CHA.nn and TYPE = METSTAT



4 Display file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILEusing: FILE = CA.ST.CHA.nn and ALL = YESObtain expiration date from output mask(EXPDAT = YY-MM-DD)

5 Delete file on disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEL FILEusing: FILE = CA.ST.CHA.nn and EXPDAT = YY-MM-DD

TS-733 – 1 A30808-X3003-X458-1-7619



TS-733 Copy trunk meter file to magnetic tape

1 Edit meters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDIT METusing: FILE = CA.TR.CHA.nn and TYPE = METTR



4 Display file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISP FILEusing: FILE = CA.TR.CHA.nn and ALL = YESObtain expiration date from output mask(EXPDAT = YY-MM-DD)

5 Delete file on disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEL FILEusing: FILE = CA.TR.CHA.nn and EXPDAT = YY-MM-DD

A30808-X3003-X458-1-7619 TS-740 – 1



TS-740 Create statistics meter

If statistics metering is to be performed on a directory-number-related basis, i.e. separately according to directorynumber blocks, supplementary statistics meter groups (additional to statistics meter group 0) must be generatedby means of an ODAGEN run.

1 Activate the system feature for statistics meter (if required) . . . . . . . . . . . . . . . . . . . ENTR EXDDATusing: MET = METSTATAll existing metering methods must additionally be specified!

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

3 Activate meter for call duration (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ENTR CDTDATusing: EXTNSD = CALLDUR

4 Assign directory number volume to a statistics meter group . . . . . . . . . . . . . . . . . . . MOD DNusing: DN, STMGRP = 0 ... 15

5a Create statistics index for zone point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPTusing: STAT = 1 ... 255

5b Create statistics index for trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD TGRPusing: STAT = 1 ... 255

5c Create statistics index for route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ROUTEusing: STAT = 1 ... 255

6 Create statistics meter switchover (if required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TP-822(Statistics meters should be switched over synchronously with tariffs).

TS-741 – 1 A30808-X3003-X458-1-7619



TS-741 Cancel statistics meter

1 Display meter readings and objects of statistics metering . . . . . . . . . . . . . . . . . . . . . DISP STATMETusing: DESC = YES

2a Cancel statistics index for zone point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ZOPTusing: STAT = 0

2b Cancel statistics index for trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD TGRPusing: STAT = 0

2c Cancel statistics index for route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD ROUTEusing: STAT = 0

A30808-X3003-X458-1-7619 TS-831 – 1



TS-831 Copy AMA file from disk to tape

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

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

TS-840 – 1 A30808-X3003-X458-1-7619



TS-840 Display account suspension orders

1 Transfer buffer contents to disk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRANS BUFFERusing: TYPE = FIR

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

A30808-X3003-X458-1-7619 TP – 1


4 Task Procedures (TP)

TP – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-301 – 1


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 begin-ning 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 automaticallyrequested 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 manytapes as displayed in theparameter ”required copies”.

2A

Continuation tapes may berequired.

TP-301 – 2 A30808-X3003-X458-1-7619


2A

Insert magnetic tape with writering

DISP MT:MTD

Is the tape labelled?

N

Y

Is the label to remain thesame? N

Y

3A

INIT MT:MTD, CODE, VSN

If the label is changed, all filesstill on the tape will be deleted.

A30808-X3003-X458-1-7619 TP-301 – 3


3A

DISP FILE:VSN

Do files still exist on thetape? N

Y

Are files to be deleted?

N

Y

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

DEL FILE:FILE, VSN

4A

If during data transfer a continuationtape is requested by the outputmessage MOUNT TAPE, the oldtape must be removed, a new emptyand labelled tape with inserted writering must be inserted, and thecommand MOUNT TAPE must beentered to continue the file transfer.

TP-301 – 4 A30808-X3003-X458-1-7619


4A

REWIND MT:MTD

Remove tape.


Is the number of copiesmade, the same as thenumber required?

N

Y

REL CYCFILEFILE=IA.ICMCR

2AUntil REL CYCFILE has beenexecuted, the cyclic MCR file has thefollowing characteristics:– that part of the file which has beencopied to magnetic tape cannot beoverwritten– up to this point it is possible to createa further identical copy on magnetictapeREL CYCFILE releases the copiedpart of the MCR file for overwriting.After execution of this command it isno longer possible to make a copy ofthis part of the MCR file.

A30808-X3003-X458-1-7619 TP-302 – 1


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


Is the number of requiredcopies > 1? N

Y

2A

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

TP-302 – 2 A30808-X3003-X458-1-7619


2A

ACT BILLREC:FILE=IA.ICMCR,RECLAY=desired traffictype

Delete the file?

N

Y

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

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


3A

If a follow-up tape is requestedduring file transfer with the outputmessage MOUNT TAPE, removethe old tape, insert a blank, labelledtape with a write protection ring andenter the command MOUNT TAPEto continue file transfer.

The selection criterion(RECLAY in ACT BILLREC) isautomatically reset, i.e. theentire file is copied.

3B

2B

A30808-X3003-X458-1-7619 TP-302 – 3


Does the number ofcopies made equal thenumber of copiesrequired?

N

Y

2B

Was the number of copiesrequired changed(SAFCOP)?

N

Y

3B

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

3A

REL CYCFILE:FILE=IA.ICMCR

Before REL CYCFILE is executed, thecyclic MCR file has the following features:–the part of the magnetic tape copied totape cannot be overwritten–until this point it is possible to createanother identical copy on tapeREL CYCFILE releases the copied part ofthe MCR file for overwriting. Once thecommand is executed, no more copies ofthis part of the MCR file can be made.

TP-302 – 4 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-501 – 1


Modify assignment of IARSTAT destination name to destination/route or of IARSTATorigin 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 anIARSTAT destinationname to be modified?

N

Y

DISP IARNAME:DEST, RTNOor LAC, DIR=DEST

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

DISP IARNAME:TGNOor LAC, DIR=DEST

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

TP-501 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-503 – 1


Cancel IARSTAT name assignment

As long as the IARSTAT name is assigned to more than one destination/route or trunk group, all assignmentsexcept the last one can be canceled immediately, regardless of whether a matrix point has been created for thatname 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 associatedmatrix 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 proce-dure. For names that are not desired a number symbol # must be entered.

TP-503

CAN IARNAME:TGNO, NAMEor LAC, DIR=DES

Is the assignment to anIARSTAT destinationname to be canceled?

N

Y

Executed?

N

Y

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

DISP IARNAME:DEST, RTNOor LAC, DIR=DEST

DISP IARNAME:TGNOor LAC, DIR=DES

2A

1A

TP-503 – 2 A30808-X3003-X458-1-7619


2A

Is a fault report output:IARSTAT NAMECANNOT BECANCELLED: FIRSTCANCEL MATRIXPOINT(S)?

N

Y

Cancel all matrix points thatare linked with this IARSTATname.

1A

see CML: Section EM

A30808-X3003-X458-1-7619 TP-511 – 1


Assign IARSTAT matrix points to an IARSTAT tariff zone

TP-511

DISP IARTMPD:TZONE

ENTR IARZONE:MTYPE, TZONE, DNAME,ONAME

As long as a tariff zone withouttariff switchover time isassigned, only the day counteris used.

TP-511 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-513 – 1


Modify IARSTAT tariff zone for one or more IARSTAT matrix points

TP-513

DISP IARTMPD:TZONE=new value

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

As long as a tariff zone withouttariff switchover time isassigned, only the day counteris used, i.e. the result is thesame as when the IARSTATtariff zone assignment iscanceled.

TP-513 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-523 – 1


Start IARSTAT registration job

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

TP-523

DISP IARJOB;

Already 2 jobs for thatmeasurement type? Y

N

Start a continuous regis-tration job? N

Y

REC IARSTAT:MTYPE, BEG

REC IARSTAT:MTYPE, BEG, TER

Not more than 2 registrationjobs may exist for onemeasurement type.

TP-523 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-524 – 1


Cancel IARSTAT registration job

TP-524

DISP IARJOB;

CAN JOB:JN, JOBCOD

TP-524 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-530 – 1


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

TP-530

DISP IARSAVDA;

Hour= 1 and daynumber= 1? N

Y

Enter day number?

N

Y

ENTR IARSAVDA:HOUR, DAYNUM

ENTR IARSAVDA:HOUR, DAYTYP

Enter default value: firstday of month at 1 a. m.? Y

N

CAN IARSAVDA;

TP-530 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-545 – 1


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 inter-rupted transfer can be continued by entering a command at the host processor. However, only the copy serviceprocesses for AMA (AGFR1 to AGFR6) are supported.

TP-545

Are the file attributescorrect for the requiredformat change?

N

Y

2B2A

Is the format to beconverted? N

Y

2C

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

TRANS BUFFER:TYPE =IARA

TP-545 – 2 A30808-X3003-X458-1-7619


2A 2B

The password must be speci-fied if the file has passwordprotection. This command onlyneeds to be input once persession.

This command edits the file forpostprocessing during copying.The precondition is that thecopy service process exists(see OMN:SSS-SY).

2C

Copying to the remoteprocessor is regarded as asingle safe copy. The data inthe file can be deleted or over-written by means of parameterUNCOND following transfer(once) to the host, even if noother safe copies have beenmade.

USINF must be entered in theform a[-b], where:a = USER IDENTIFICATION,b = USER ACCOUNTNUMBER

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

ENTR FILEPSWENTR FILEPSW

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

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

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

A30808-X3003-X458-1-7619 TP-550 – 1


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 asdisplayed in the parameterSAVCOP.

2A

TP-550 – 2 A30808-X3003-X458-1-7619


2A

Insert magnetic tape with writering

DISP MT:MTD

Is the tape labelled?

N

Y

Is the label to remain thesame? N

Y

3A

INIT MT:MTD, CODE, VSN

If the label is changed, all filesstill on the tape will be deleted.

A30808-X3003-X458-1-7619 TP-550 – 3


3A

DISP FILE:VSN

4A

DEL FILE:FILE, VSN

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

Are there still files on thetape? N

Y

Are files to be deleted?

N

Y

TP-550 – 4 A30808-X3003-X458-1-7619


4A

REWIND MT:MTD

DISP FILE:FILE=IR.AryymmnnALL=Y

Is the number of copiesmade, the same as thenumber of backupcopies?

N

Y

One more copy?

Y

N

Remove tape.

2A

A30808-X3003-X458-1-7619 TP-600 – 1


Create zone points for mobile originating call and call forwarding

TP-600

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

MOD INTCELL:LACOD, CI, NORIG2

MOD TGRP:TGNO, NORIG2

DISP INTCELL:LACOD, CI

DISP TGRP:TGNO=<tgno of theincoming trunk group>

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

Is the circuit groupcreated with ORIG 2? N

Y

Is the cell created withORIG2? N

Y

Is the zone point to be cell-dependent (A), trunk-group-dependent (B) or indepen-dent of origin (C)?

B

A C

TP-600 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-603 – 1


Modify assignment of mobile-specific tariffs to tariff category

TP-603

Is another new tariff to beused? Y

N

Is the new tariff alreadycreated? Y

N

Is a tariff to be added oran old tariff to be replacedby a new one?

N

Y

DISP MTAR:MTAR

MOD MTARCAT:MTARCAT, CSWTAR

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

2A

2A

TP-603 – 2 A30808-X3003-X458-1-7619


2A

MOD MTARCAT:MTARCAT, NSWTAR,[,CSWTAR]

CSWTAR must be specified ifan old value is to be canceled.

A30808-X3003-X458-1-7619 TP-701 – 1


TP-701

DISP TAR:ZONO = X

2A

DISP TAR:NAME = X

1A

Does the tariff alreadyexist? Y

N

2B

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 tariffonce by means of ENTR TAR: ZONO, NAME. For the remaining tariffs in this zone, tariff switchovers are enteredby 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 tariffPLSSUP can be specified in connection with the communication tariff PLSCOM. For creation of the communica-tion tariff, please refer to procedures TP-702, TP-703. The access tariff PLSATT can only be created in the origi-nating exchange.

TP-701 – 2 A30808-X3003-X458-1-7619


2A

ENTR TAR:NAME, PLSATT and/orPLSSUP

Is the tariff to be entered thefirst tariff (A) or a secondarytariff (B) for this zone?

A

B

ENTR TAR:ZONO, NAME

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

Enter more accesstariffs? Y

N

1A

2B

With PLSATT , the charge isapplied before the called partyanswers. With PLSSUP thecharge is applied after thecalled party answers.

DATE is necessary if the zonehas already been created in thezone translator(DISP ZOPT: ZONO)

NAME of the new tariff(switchover)

NAME of old tariff (reset)


Single pulse metering (SPM) ormultiple pulse metering (MPM)with parametersPLSATT/PLSSUP:No. of pulses: 1-255

A30808-X3003-X458-1-7619 TP-702 – 1


Enter communication tariff - with periodic pulse metering (PPM) or periodic multiplepulse metering (PMM)

Tariffs are entered without any assignment to a zone (i.e. without ZONO) Then a zone can be assigned a tariffonce by means of ENTR TAR: ZONO, NAME. For the remaining tariffs in this zone, tariff switchovers are enteredby means of ENTR TARSW: ZONO, NAME, ...

Communication tariffs can also be entered in connection with access tariffs. In this case parameter PLSATT orPLSSUP 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

Does the tariff alreadyexist? Y

N

ENTR TAR:NAME, PLSCOM = n-t

2A

1A

DISP TAR:NAME = X

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

TP-702 – 2 A30808-X3003-X458-1-7619


2A


A

B

ENTR TAR:ZONO, NAME


Enter more PPM or PMMtariffs? Y

N

1A


NAME of the new tariff(switchover)

NAME of old tariff(reset)


A30808-X3003-X458-1-7619 TP-703 – 1


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 unsuc-cessful 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 basictariffs (SPM, MPM, PPM and PMM) are permitted and can be linked together in any way. The communicationcomponent can contain up to four basic tariffs. The period of validity of a basic tariff must always be a multiple ofthe 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 isalready a tariff in this zone, the sequence is entered without ZONO and then switched over to the sequence bymeans of ENTR TARSW: ZONO , NAME, ....

1A

TP-703

DISP TAR:ZONO = X

Does the sequencealready exist? Y

N

2A

DISP TAR:NAME = X

3A

TP-703 – 2 A30808-X3003-X458-1-7619


2A

Repeat sequence (A)?Release call (B)?Last tariff until end (C) ?

B

A C

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). Thedefault value is NONCYC .

A30808-X3003-X458-1-7619 TP-703 – 3



A

B

ENTR TAR:ZONO, NAME

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

Enter more tariffsequences? Y

N

1A

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


NAME of new tariff(switchover)

NAME of old tariff(reset)

3A

TP-703 – 4 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-704 – 1


Modify tariff

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

TP-704

DISP TAR:NAME = X

DISP TAR:ZONO = X

Does the new tariffalready exist? N

Y

2B2A

Display the old and the newtariff.

Verify that the old tariff exists inthe specified zone.

A tariff (new tariff/tariff to bemodified) for which a date-controlled job already existscannot be modified. Note themaximum no. of switchovers!

DISP TARSW:ZONO = X

TP-704 – 2 A30808-X3003-X458-1-7619


2A 2B

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

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

Is the job to be canceledbefore it is executed? Y

N

Used to correct an input error.The tariff switchover can beentered up to 30 days inadvance .

If ZONO is not specified, themodification applies to allzones which use this tariff (withNAME ).

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

ZONO must not be entered.The new tariff may include amaximum of one PPM (PMM)component (depending on theproject). Switchover from pulseto currency format is notpossible.

To return to the status beforethe preceding MOD TAR(NAME and NNAMEtransposed, otherwise nodifference).

A30808-X3003-X458-1-7619 TP-705 – 1


Cancel tariff

A tariff can only be canceled (CAN TAR: NAME) if it is not currently assigned to a zone and is not required forswitchover 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).

DISP TARSW:DATE = X

The tariff cannot be canceled.Wait until the date-controlledjobs have been processed.

TP-705

Are there any date-controlled jobs for thetariff to be canceled?

N

Y

Can they be canceled?

Y

N

2B

2A

TP-705 – 2 A30808-X3003-X458-1-7619


2A

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

MOD TAR:NAME, NNAME, TIME,DATE

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

2B

DISP TAR:ZONO = X

Is the tariff to be canceledone of the current tariffs inany zone?

Y

N

DISP TARSW:ZONO = X

2C

3A

4A

Cancel by restoring oldstatus:MOD TAR (A),ENTR TARSW(B),CAN TARSW (C)

B

A C

A30808-X3003-X458-1-7619 TP-705 – 3


3A

The tariff is removed from thedatabase.

Are there switchover jobsfor the tariff? Y

N

CAN TAR:NAME

Can the jobs becanceled? Y

N

CAN TAR:NAME, ZONO

This only removes the tariffname from the zone. The zoneis retained with the other tariffs.The name also remains in thedatabase and can be used inother zones.

2C

TP-705 – 4 A30808-X3003-X458-1-7619


4A

DISP ZOPT:ZONO = X

Is the zone configured?

N

Y

Do you wish to create atemporary name for thetariff that is to becanceled?

Y

N

TP-706 TP-707

3A

A30808-X3003-X458-1-7619 TP-706 – 1


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) itselfcontinues to exist under a temporary name.

ENTR TAR:NAME = <tempname>

Enter the same tariff under atemporary name.

DISP TAR:NAME

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

TP-706

If ZONO is not specified, thetariff is modified in all zones.DATE = ”today”,TIME = “ next quarter hour”,NNAME = <tempname>

Wait until the modification hasbeen executed.

Is the tariff to be canceledfrom one zone only (A) orfrom the database (B) ?

A

B

2B2A

TP-706 – 2 A30808-X3003-X458-1-7619


2A 2B

CAN TAR:NAME, ZONO

CAN TAR:NAME

A30808-X3003-X458-1-7619 TP-707 – 1


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 isremoved from the database. All switchovers for this zone are canceled at the same time. The tariff names usedare still in the database, however (for further use). They can be canceled as per TP-705.

DISP ZOPT:ZONO

The zone points must first beremoved.

TP-707

Is the zone assigned?

Y

N

DISP ZOINF:ZONO

Is there zoneinformation? N

Y

MOD ZOINF:ZONO,CHBNO = 255

2A

The zone information must becanceled.

2A

TP-707 – 2 A30808-X3003-X458-1-7619


2A

CAN TAR:ZONO

A30808-X3003-X458-1-7619 TP-720 – 1


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 pulsemetering” to ”periodic pulse metering” and vice versa) or tariff sequences.

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

TP-720

DISP ZOPT:ZONO

Parameter DATE is specified ifthe tariff switchover is not tocome into effect until after acertain date or if the zone isassigned to a zone point.

Is there a statistics index?

N

Y

DISP STATSW:STAT

Is there a switchovertime? Y

N

2A

Tariffs and statistics metersshould be synchronized

TP-720 – 2 A30808-X3003-X458-1-7619


2A

ENTR STATSW:STAT, TIME, GRP,WDCAT

If a DATE is specified withcommand ENTR TARSW ,wait until that date to enter thiscommand.

A30808-X3003-X458-1-7619 TP-721 – 1


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 pulsemetering” to ”periodic pulse metering” and vice versa) or tariff sequences.

DISP TARSW

TP-721

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


Immediate cancellation(without DATE) is only possibleif the new tariff is not yet activeand the zone is not assigned toa zone point. If a zone pointexists for this zone, the date ofthe next switchover must beentered.

DISP ZOPT:ZONO


N

Y

2A

Do not enter this command untilCAN TARSW has beenexecuted (check the parameterDATE ).Parameter DATE is specified ifthe tariff switchover is not tocome into effect until after acertain date or if the zone isassigned to a zone point.

TP-721 – 2 A30808-X3003-X458-1-7619


2A

Synchronize the switchovertime for the statistics meters.

TP-824

A30808-X3003-X458-1-7619 TP-722 – 1


Cancel tariff switchover

DISP TARSW

If DATE was specified above,do not enter this command untilthis date.

TP-722

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

CAN STATSW:STAT, TIME, WDCAT

DISP ZOPT:ZONO


N

Y

Immediate cancellation(without DATE) is only possibleif the new tariff is not yet activeand the zone is not assigned toa zone point. If a zone pointexists for this zone, the date ofthe next switchover must beentered.

TP-722 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-761 – 1


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, LACORPossible special codes: ORIG2, MFCAT, ZDIG, CXORIG

DISP TAR:ZONO

The zone is charge-free ifBILLING is not specified. notspecified. Furtheroption:ZOCHA = NOPULSE.

TP-761

Is the zone to be charge-free? Y

N

Generate meter pulses (A) orproduce AMA tickets (B)?

A

B

CR ZOPT:CODE, ZONO,BILLING = AMA

CR ZOPT:CODE, ZONO

2A 2B 2A

TP-761 – 2 A30808-X3003-X458-1-7619


2A

Do you also wish thenumber of calls to beregistered?

Y

N

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

MOD ZOPT:CODE, ZONO, MEPROC

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

Do you wish to enter datafor meter processing? N

Y

For SUCACNTR : only CNTR1or CNTR3 . Do not use anycounter that registers callcharges, facility input chargesor facility usage charges.

2B

A30808-X3003-X458-1-7619 TP-767 – 1


Merge zone points

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

DISP TAR:ZONO

TP-767

Is the zoning result to be azone? N

Y

Does the zone numberexist? N

Y

MERGE ZOPT:CODE,zoning result*)

The zone number must becreated first.

*) Only one zoning result is permitted.

TP-767 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-769 – 1


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

ORIG2 = originating mark ofthe foreign local area

TP-769

DISP TAR:ZONO

Does the zone exist, i.e.have tariffs been createdfor the zone?

N

Y

CR ZOPT:CODE, ZONO,BILLING, ORIG2

The zone must first becreated with ENTR TAR .

Do you wish to enter datafor meter processing? N

Y

MOD ZOPT:MEPROC, CODE, ZONO,ORIG2

TP-769 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-770 – 1


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

TP-770

Do you wish to modifymeter processing? Y

N

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

MOD ZOPT:CODE, ZONO, MEPROCORIG2

The zoning result can also bemodified.Possible inputs for the zoningresult: ZONO or ZOCHA orINCEPT or MBI

TP-770 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-811 – 1


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 .

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

TP-811

Is this the first time thatthe charge data havebeen edited?

N

Y

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

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

ENTR FILEPSW

The password must bespecified if the file haspassword protection. Thiscommand only needs to beinput once per session.

2A

USINF must be entered in theform a[-b], where:a=USER IDENTIFICATION,b=USER ACCOUNT NUMBER

TP-811 – 2 A30808-X3003-X458-1-7619


2A

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

Take the expiration date fromthe output mask(EXPDAT = YY-MM-DD)

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

Caution : The disk file must bedeleted immediately aftersuccessful transfer, otherwisestorage problems may arise onthe hard disk.

A30808-X3003-X458-1-7619 TP-820 – 1


Overview of commands for statistics meter administration

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

Activate system feature:ENTR EXDDAT

Display blocked metertypes:SAVE MET

Define the data format ofthe meter file:ENTR METADM

TP-820

Are the charge metersactive? Y

N

Incorporate logging file

In addition, the systeminterrogates the status of thecharge meters every 10minutes. If the status is fallback(APS change, ISTART2G), anoutput appears on the OMT.

2B

2A

FORMAT = 1: without callduration,FORMAT = 2: with call duration

TP-820 – 2 A30808-X3003-X458-1-7619


2A

2B

Restart charge registrationSAVE MET

Is the call duration meterto be started? N

Y

Start call duration meter:ENTR CDTDAT

Statistics metering for a zonepoint(A), trunk group(B) orroute(C)?

B

A C

Create zone point withstatistics index:CR ZOPT

With TYPE = METSTAT andFUNC = FALLBACK.

2C

Create trunk group withstatistics index:CR TGRP

Create route with statisticsindex:CR ROUTE

3A

A30808-X3003-X458-1-7619 TP-820 – 3


3A

Are further statisticsindices to be assigned foran object of the sametype?

N

Y

Assignment of directorynumber volume to statisticsmeter group:MOD DN

Display statistics meterreadings:DISP STATMET

Assignment of directorynumber volume to statisticsmeter group:DISP STMETLNK

Display the statistics metergroups and the statisticsindices:DISP STMETGRP

Input of statistics meterswitchovers:ENTR STATSW

4A

2C

Collect statistics meter data

Display statistics meter data

TP-820 – 4 A30808-X3003-X458-1-7619


Display statistics meterswitchover times:DISP STATSW

Cancel statistics meterswitchover time:CAN STATSW

Cancel statistics metergroup:MOD DN

Cancel indices:MOD ZOPT / MOD TGRP /MOD ROUTE

With STAT = 0

Statistics meter switchoversshould be synchronized withtariff switchovers!

Delete statistics meter data

Display statistics meter data

With STMGRP = 0

4A

A30808-X3003-X458-1-7619 TP-822 – 1


Enter switchover for statistics meters

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

DISP STATMET:DESC = YES

Display the statistics index, thevalid zones and the statisticsmeter groups created.

TP-822

DISP STATSW:STAT, TIME, WDCAT

Are the switchovers fortariffs and statisticsmeters to besynchronized?

N

Y

DISP TARSW:ZONO

2A

TP-822 – 2 A30808-X3003-X458-1-7619


ENTR STATSW:STAT, TIME, WDCAT, GRP

2A

A30808-X3003-X458-1-7619 TP-824 – 1


Modify switchover time for statistics meters

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

DISP STATSW

Identify the zones to which astatistics index has beenassigned.

TP-824

DISP STATMET:DESC = YES

CAN STATSW:STAT, TIME, WDCAT

DISP TARSW:ZONO

2A

TP-824 – 2 A30808-X3003-X458-1-7619


ENTR STATSW:STAT, TIME, WDCAT, GRP

2A

Are tariff switchovers alsoto be modified? Y

N

TP-721 Modify the tariff switchovertimes.

A30808-X3003-X458-1-7619 TP-830 – 1


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 meteringpurposes, otherwise the meter readings become distorted.

DISP TRMET:TGNO = X

ENTR TGDAT:TGNO,GCOS = TRMET

CR TGRP:TGNO, GCOS = TRMET

Has the trunk group beencreated? Y

N

TP-830

Is the trunk group outgoing(A) or bothway (B)?

A

B

Is the trunk group to be usedfor metering outgoing (A) orincoming (B)?

B

A

2A 2B

TP-830 – 2 A30808-X3003-X458-1-7619


2A

2B

DISP ROUTE:TGNO, DEST = X

MOD ROUTE:TGNO, DEST,LNDES = TRMET

A30808-X3003-X458-1-7619 TP-900 – 1


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 informationplease refer to the introductory section of this document, the individual procedures and/or the Command ManualCML.

TP-900

2A

Record format and numberof copies:SET FGRPATT

Collect additional/alter-native AMA data:ENTR CDTDAT

Also to set the occupancy levelalarm.

Allow calling numberindication (incoming)CR TGRP

Are the data records registe-red centrally (CAMA, A) orlocally (LAMA, B)?

A

B

If the trunk group alreadyexists: with ENTR TGDAT .

2B

Activate system feature:ACT IAFEAT

TP-900 – 2 A30808-X3003-X458-1-7619


2A 2B

Request calling numberindication (outgoing):CR ROUTE

Is MFCR2 used as thesignaling system? N

Y

Set LINK-BY-LINKsignaling::CR TGRP

Calling line type =PBXLN? N

Y

Set LSN or PDN in therecord :CR PBXLN

Call diversion to announce-ment or operator with AMA:CR INC

3A

Signaling must not be END–TO–END.If the trunk group alreadyexists: with CAN TGDAT.

For registration of the B1 ––>B2 leg with AMA.

A30808-X3003-X458-1-7619 TP-900 – 3


3A

AMA for calls (A) or forFAI/FAU (B)?

A

B

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

A

B

Set zone point to AMA :CR ZOPT

Request AMA data forincoming trunk group:CR TGRP

AMA for all unsuccessful callattempts (A) or only forunsuccessful chargeablecall attempts (B)?

A

B

Set incoming trunk group tozoning (only necessary forCAMA):CR TGRP

AMAAMA for allunsuccessful call attempts:ENTR CDTDAT

Enter call attempt tariff forthis zone:ENTR TAR

4B

4A

If the trunk group alreadyexists: with ENTR TGDAT.

AMA for unsuccessful callattempts? N

Y

AMA for all unsuccessfulcall attempts:ENTR CDTDAT

TP-900 – 4 A30808-X3003-X458-1-7619


4A

AMA for FAU (A) orfor FAI (B)?

A

B

AMA for FAU:CR FAUCHA

AMA for CENTREX-FAI:ENTR CDTDAT

AMA for FAIn:CR FAICHA

No charge registration forCENTREX-FAU possible.

For subscriber controlledinputs and operator inputs.

Also possible for implicitdeactivations.

4B

Activate AMA immediateoutput:ACT IAFEAT

Set subscriber to AMA-immediate output:MOD SUB

5A

With MOD PBX for PBX andMOD PBXLN for PBXLN.

A30808-X3003-X458-1-7619 TP-900 – 5


5A

Immediate output for FAIS:ENTR CDTDAT

Output of the currentAMA data? N

Y

Write buffer contents to diskfile:TRANS BUFFER

Output on magnetic tape (A)or at OMT (B)?

A

B

Copy AMA file to tape orhost:TRANS FILE

Display AMA data records:DISP AMA

Automatic if the buffer is full.

Collect AMA data

Output AMA data

TP-900 – 6 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-905 – 1


Overview of commands for administration of detailed billing DEB

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

TP-905

2A


Record format and no. ofcopies:SET FGRPATT

Collectadditional/alternative DEBdata:ENTR CDTDAT

Also to set the occupancy levelalarm.

DEB for selected calls (A) orfor all calls (B)?

A

B

2B

With CR PBX for PBX andCR PBXLN for PBXLN.

Assign DEB to thesubscribers:CR SUB

TP-905 – 2 A30808-X3003-X458-1-7619


2A

DEB linetype = PBXLN?

N

Y

Set LSN or PDN in therecord:CR PBXLN

3A

DEB for next call (A) ordependent on traffic category(B)?

A

B

Define code for subscribercontrolled input:ENTR SCFEA

Assign DEB to subscriber:CR SUB

Assign DEB to subscriber:CR SUB

Assign traffic type todestination:CR DEST

Link DEB and traffic type:ENTR TRABLOCK

Also possible withENTR DNATT.

2B

A30808-X3003-X458-1-7619 TP-905 – 3


3A

4A

DEB for all supplementaryservices:ENTR CDTDAT

DEB for all supplementaryservices:ENTR CDTDAT

CR FAICHA is not requiredhere.

Register FAU charges (withAMA and/or METERING:CR FAUCHA

Call diversion to announce-ment or operator with DEB:CR INC

For registration of theB1 ––> B2 leg with DEB.

Activate DEB immediateoutput:ACT IAFEAT

With MOD PBX for PBX andMOD PBXLN for PBXLN.

Set subscriber to DEB-immediate output:MOD SUB

MARKS= CXSFAICH will notbe evaluatet (DEB is producedregardless of this parameter).MARKS = AMAFAIID will notbe evaluatet (DEB is notpossible for implicitdeactivations).

DEB required for FAU (A) orfor FAIS (B)? Otherwise goto C.

A

C B

TP-905 – 4 A30808-X3003-X458-1-7619


4A

Immediate output for FAIS:ENTR CDTDAT

Output of the currentDEB data? N

Y


DEB file to tape or host:TRANS FILE

Display DEB records:DISP AMA


Output DEB data

Collect DEB data

Output to tape or host (A) orat OMT (B)?

A

B

A30808-X3003-X458-1-7619 TP-910 – 1


Overview of commands for administration of meter observation MOB

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

TP-910

2A


Collect alternative MOBdata:ENTR CDTDAT

MOB for ordinarysubscribers (A) or TFSsubscribers (B)?

A

B

Assign MOB to the TFSsubscribers:ACT SMOBS

Assign MOB to the ordinarysubscribers:ACT MOBS

For PBX subscribers, the LSNis always registered in theMOB record.

TP-910 – 2 A30808-X3003-X458-1-7619


2A

Call diversion to announce-ment or operator withMOB:CR INC

For registration of theB1 ––> B2 leg with MOB.

MOB for calls (A) or FAU(B)?

A

B

Register FAU charges (withAMA / METERING:CR FAUCHA

No further steps required inthis case.

MOB for FAIS is permittet bysoftware.MOB for FAIS can bedeactivatet by a patch.

Activate MOB immediateoutput:ACT IAFEAT

Set subscriber to MOBimmediate output:ACT MOBS

Immediate output not possiblefor TFS-subscribers.

Output of the currentMOB data? N

Y

3B3A

Output MOB data

Collect MOB data

A30808-X3003-X458-1-7619 TP-910 – 3




Output to tape or host (A) orat OMT (B)?

A

B

Copy MOB file to tape or tohost:TRANS FILE

Display MOB data records:DISP MOBSDAT

3A 3B

TP-910 – 4 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-915 – 1


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 informationplease refer to the introductory section of this document, the individual procedures and/or the Command ManualCML .

TP-915

2A


In any exchange in theconnection path.

Enter tariff:ENTR TAR

Assign tariff to zone:ENTR TARSW

Register call charges withMETERING :CR ZOPT

TP-915 – 2 A30808-X3003-X458-1-7619


2A

Set threshold value:ENTR CDTDAT

3B

Modification of thethreshold value required? Y

N

Activate PMOB with a newthreshold value:ENTR CDTDAT

Deactivate PMOB :CAN CDTDAT

Output on magnetic tape (A)or at OMT (B)?

A

B

3A

Output PMOB data

Collect PMOB data

A30808-X3003-X458-1-7619 TP-915 – 3


3A


3B

Copy PMOB file to tape:TRANS FILE

Display PMOB records:DISP PMOBSDAT

Output of the currentPMOB data? N

Y

TRANS BUFFER is notrequired in this case.


TP-915 – 4 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-931 – 1


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 awaitingimmediate output cannot be forcibly written to disk.

TP-931

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

TRANS BUFFER:TYPE = AMA

Are all subscriber data tobe displayed? N

Y

DISP AMA:DN

The time interval for which theAMA data are output is definedby 4 parameters, at least one ofwhich must be specified.Default values are used for theother parameters (see CML ).

TP-931 – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TP-933 – 1


Copy AMA disk file to tape

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

TP-933

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


Y

N


2B2A

Is the format to beconverted? Y

N


TP-933 – 2 A30808-X3003-X458-1-7619


2A 2B

ENTR FILEPSW

REWIND MT:MTD

MOUNT TAPE:DEV

REL CYCFILE:FILE = IA.ICAMA

ENTR FILEPSW

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


This command edits the file forpostprocessing during copying.The precondition is that thecopy service process exists(see register OMN:SSS-SY).

Only if there is a continuationtape.

This command must not beexecuted until postprocessinghas taken place.

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

A30808-X3003-X458-1-7619 TP-934 – 1


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 inter-rupted transfer can be continued by entering a command at the host processor. However, only the copy serviceprocesses for AMA (AGFR1 to AGFR6) are supported.

TP-934


N

Y

2B2A

Is the format to beconverted? N

Y

2C

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


TP-934 – 2 A30808-X3003-X458-1-7619


2A 2B


This command edits the file forpostprocessing during copying.The precondition is that thecopy service process exists(see register OMN:SSS-SY).

2C

Copying to the remoteprocessor is regarded as asingle safe copy. The data inthe file can be deleted oroverwritten by means ofparameter UNCOND followingtransfer (once) to the host,even if no other safe copieshave been made.

USINF must be entered in theform a[-b], where:a = USER IDENTIFICATION,b = USER ACCOUNTNUMBER


ENTR FILEPSWENTR FILEPSW

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

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

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

A30808-X3003-X458-1-7619 TC – 1


5 Task Complexes (TC)

TC – 2 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TC-001 – 1


TC-001 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 weekdays to a weekday category, a fixed holiday calendar, and a calendar for movable holidays for each indi-vidual year.

1 MML Command Overview

1. Create the weekday categoriesMOD 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 tableCR 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 assignmentsmodified, with the commandMOD HOLICAL: FEAT, YEAR=X,DATECAT= >NDATECAT, CDATECAT>;

3. Create the movable holiday calendarCR 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 assignmentsmodified, withMOD 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):

2 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 1stMay 1stDecember 25th

Movable holidays (weekday category HO):for 1998 April 3rd

April 4rdSeptember 11th

for 1999 April 8thApril 9thNovember 30th

TC-001 – 2 A30808-X3003-X458-1-7619


2.1 Database in the MSC:

1. Create weekday categoriesMOD 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 ofthe days from Monday to Friday do not have to be changed.

2. Create the fixed holiday tableCR HOLICAL: FEAT=MCHARGE,YEAR = X,DATECAT=01-01-HO & 05-01-HO & 12-25-HO;

3. Create the movable holiday calendarCR 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;

A30808-X3003-X458-1-7619 TC-002 – 1


TC-002 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 chargeintervals and the associated charge units are to be created for calls according to the type of resourcesused (full-rate or half-rate transmission) and/or for call attempts, as well as the switchover pointsbetween the individual tariffs.In addition to this, the tariffs for mobile terminating calls made by mobile subscribers of the home networkare to be created.


1. Create a mobile-specific tariffENTR MTAR: MTAR, E1UPTI, E2SPTI, E4INU, E7SPITI;This command fixes the duration of the calll charge intervals and the number of call charge units pertime interval.

2. Create mobile radio-specific tariff categoriesENTR 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 zonesCR MZONE: ZONO, FULL [,HALF] [,ATTEMPT];This command assigns tariff categories to the type of resource used (full-rate or half-rate transmis-sion) and/or to call attempts.

4. Create the mobile radio-specific tariff for MTC and the scaling factorsENTR PLMNTAR: NETW, E1UPTI, E2SPTI, E4INU, E7SPITI, E3SCF;This command specifies the scaling factor (E3SCF), i.e. a PLMN-specific multiplier for the callcharge units calculated from E1, E2, E4 and E7 (see 1.: ENTR MTARCAT) for MOC, as well as theparameters valid for mobile terminating calls.

2 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: 25 sCharge for 1st time interval (basic charge) in charge units: 2Duration of subsequent time intervals: 15 sNumber of call charge units per subsequent time interval: 1Scaling factor: 1

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

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

TC-002 – 2 A30808-X3003-X458-1-7619


The following tariff categories:

Tariff category 1On 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.


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 thecalendar 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;

Duration of subsequent time intervals: 10 sNumber of call charge units per subsequent time interval: 1Scaling factor: 1

A30808-X3003-X458-1-7619 TC-009 – 1


TC-009 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 haveto be created.MCR data records are to be generated for the calls and for call attempts.


1. Generation of MCR data recordsActivation of the MCR feature (unless this was already done during installation – this can be checkedwith 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 duringinstallation – 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 withENTR 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 withMOD TGRP: TGNO, NORIG2;

3. Create the mobile-specific zone pointsCR MZOPT: CODE=<digits–code type>, MZONO=<zone–ORIG2–ORIG2- position>, CHTYPE,BILLING;The zone points define how the charges for an outgoing call are to be registered depending on thedialed 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 beencreated.The parameter BILLING specifies the type of charge registration. For generation of MCR datarecords, BILLING=AMA must be set.

2 Example

For charge registration of mobile originating calls from PLMN A (see Fig. 5.1) zone points are to becreated 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 adata record is to be generated for chargeable call attempts also (cf. zones 1 and 2 in TC-002.


1. Activation of MCR data record generation and zoning, and creation of the origin code for the trunkgroup 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;

TC-009 – 2 A30808-X3003-X458-1-7619


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;

Fig. 5.1 MOC to the fixed network

ORIG2 = 20

PLMN A

CC = 49NDC = 179MCC = 262MNC = 03

BSC 1

SPC = 250, NAT 0

BTS

BTS

BTS

A

VLRISD/SCCGPA-digits: 491799900000

SPC = 200, NAT 0

MSC/VLR TGNO = BSC 1

TGNO = BSC 2

ORIG1 = 50

ORIG2 = 10

BTS

BSC 2

SPC = 260, NAT 0

BTSORIG1 = 60

A30808-X3003-X458-1-7619 TC-010 – 1


TC-010 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 becreated.MCR data records are to be generated for the calls and for chargeable call attempts.


1. Generation of MCR data recordsActivation of the MCR feature (unless this was already done during installation – this can be checkedwith DISP IAFEAT):DACT FNS: FNS=IA;ACT IAFEAT: TYPE=MCR;ACT FNS: FNS=IAActivation of MCR data record generation for call attempts (unless this was already done duringinstallation – 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 withMOD INTCELL: LACOD, CI, NORIG2;

3. Create the mobile-specific zone pointsCR MZOPT: CODE=<digits–code type>, MZONO=<zone–ORIG2–ORIG2- position>, CHTYPE,BILLING;The zone points define how the charges for an outgoing call are to be registered depending on thedialed 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 beencreated.The parameter BILLING specifies the type of charge registration. For generation of MCR datarecords, BILLING=AMA must be set.

2 Example

For charge registration of mobile originating calls from PLMN A (see Fig. 5.2) zone points are to becreated 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 othercells of the BSC area, a data record is to be generated for call attempts also (cf. zones 1 and 2 in TC-702).


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;

TC-010 – 2 A30808-X3003-X458-1-7619


Fig. 5.2 MOC to the fixed network

CI = 2557

ORIG2 = 20

A

VLRISD/SCCGPA digits: 491799900000

SPC = 200, NAT 0

MSC/VLR

BSC

SPC = 250, NAT 0

CI = 2555

BTS

BTS

BTS

TGNO = BSC

PLMN A

CC = 49NDC = 179MCC = 262MNC = 03

CI = 2556

ORIG2 = 21

ORIG2 = 22

LACOD = 2500

A30808-X3003-X458-1-7619 TC-011 – 1


TC-011 Charge Registration of Mobile Internal Calls

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


When creating the database for charge registration of mobile-to-mobile calls it must be taken intoaccount that these calls are routed via a loop LTG (Fig. 5.4 and OMN:SSS-RO).

1. Generation of MCR data recordsActivation of the MCR feature (unless this was already done during installation – this can be checkedwith 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 BSCand the loop LTG:CR TGRP: TGNO, OPMODE, ORIG1, GCOS=AMAREQD&ZON;If the trunk groups have already been created, the modification is made withENTR 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 withMOD TGRP: TGNO, NORIG2;

3. Creation of the mobile radio-specific zone pointsCR MZOPT: CODE=<digits–code type>, MZONO=<zone–ORIG2–ORIG2- position>, CHTYPE,CHIT;The zone points define how the charges for an outgoing call are to be registered according to thedialed 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 havebeen created.The PARAMETER BILLING specifies the type of charge registration. For generation of MCR datarecords, BILLING=AMA must be set.

TC-011 – 2 A30808-X3003-X458-1-7619


Fig. 5.3 Mobile internal call

B subscriber

A subscriiber

ORIG2 = 20

A

VLRISD/SCCGPA-digits: 491799900000

SPC = 200, NAT 0

MSC/VLR

BSC

SPC = 250, NAT 0

CI = 2555

BTS

BTS

BTS

TGNO = BSC

ORIG2 = 10

PLMN A

CC = 49NDC = 179MCC = 262MNC = 03

ORIG1 = 50

A30808-X3003-X458-1-7619 TC-011 – 3


Fig. 5.4 Use of the loop LTG in an MIC

2 Example

For charge registration of mobile internal calls (Fig. 5.3 and Fig. 5.4), zone points are to be created forthe 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 trunkgroup 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;

SN

DIU

TGRP1

DIU3

DIU1

PCM system

LOOP -LTG

BSSAP-LTG -

LTG

BSC

SPC = 250, NAT 0

MSC

TGNO=BSC

TGNO=MICLPO

ORIG2 = 10

ORIG1 = 50

ORIG1 = 60

TGNO=MICLPI

TC-011 – 4 A30808-X3003-X458-1-7619


A30808-X3003-X458-1-7619 TC-303 – 1


TC-303 Reverse Charging Service

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

Fig. 5.5 “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;

2 Activate DIUs

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

3 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. TheCODE is required for subsequent routing to AN3.

In the case of the loop between the DIUs for announcement control, the CODE is assigned for announce-ments AN1, AN2 and AN5.

CR TGRP: TGNO = trunk group for announcement control to DIU2 (AN1 und AN2),OPMODE = BW, PREFIX = bbbccc;

TGNO 3

DEST 6

ROUTE 7

code point 8 zone point 9

CODE

trunk 4 3... 9 Creation sequence

TC-303 – 2 A30808-X3003-X458-1-7619


whereby: bbbccc = 3 digits for the code point of the A announcement and 3 digits for the code point ofthe 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 beaccessed 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;

5 Activate the two ports (twice per port)

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

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

6 Create destination for RCS

CR DEST: DEST = RCS, TLIM = RELCLEA;

7 Create route for RCS

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

8 Create code point for RCS

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

9 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 wayas for ”normal” call processing, except that the destination in this case is an announcement.

A30808-X3003-X458-1-7619 TC-303 – 3


Fig. 5.6 Call processing for announcements

10 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.

announcementgroup 10

announcementline 11

CODE


ROUTE 14

DEST 13

10...16 Creation sequence

TC-303 – 4 A30808-X3003-X458-1-7619


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

Fig. 5.7 Call processing for intercept codes

17 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.

NEWDEST

new CODE

INCEPT 17

CODE


ROUTE 14

10... 17 Creation sequence

DEST 13

announcementgroup 10

announcementline 11

A30808-X3003-X458-1-7619 TC-303 – 5


21 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 themeasured values are too high, more trunks to the announcements can be created.

TC-303 – 6 A30808-X3003-X458-1-7619


OMN:SSS-TA

A30808-X3003-X458-1-7619 AP – 1

Operation Charging

6 AbbreviationsAMA 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 für 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 withstatistics

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


AP – 2 A30808-X3003-X458-1-7619

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

siemens d900 1800 charging

Documents

task procedures tp

task summary lists ts

sssta operation charging

preceding issue

issue greater

operation chargingissuesnote

thechange indications

task complexes tc