User Guide For Charging of ISDN-E Calls

USER GUIDE FOR CHARGING OF ISDN-E CALLS AND SUPPLEMENTARY SER...
Page 1 of 56
DIRECTIONS FOR USE 7/1553-APX 101 01/4 Uen C
Telefonaktiebolaget LM Ericsson 2003
USER GUIDE FOR CHARGING OF ISDN-E CALLS AND

SUPPLEMENTARY SERVICES IN MOBILE EXCHANGES
Contents
1 General
1.1 Introduction
1.2 Revision Information
1.3 Network
1.4 Concepts
1.5 Introduction to ISDN-E Charging
2 ISDN-E Charging Functionalities

2.1 General
2.2 Subscriber Properties Influencing Charging of ISDN-E Calls and Supplementary Services
2.3 Basic Call Charging
2.4 Call Attempt Charging
2.5 Counting of Transfered Information Elements
2.6 Service Charging
2.7 Advice of Charge
2.8 ISDN-E IN Calls
2.9 Initiation of Call Data Output
3 Congestion Handling
3.1 Size Alterations
3.2 Congestion Handling
4 Miscellaneous
4.2 ISDN-E Charging Exchange Parameters
5 References
http://localhost:9032/alexserv?AC=LINK&ID=9526&FN=7_1553-APX10101_4Uen.C.ht... 5/29/2015
USER GUIDE FOR CHARGING OF ISDN-E CALLS AND SUPPLEMENTARY SER... Page 2 of 56
1 General
1.1 Introduction
This document gives a general overview of how charging of calls originating from an ISDN-E
access integrated in a mobile exchange can be handled. The document also describes how ISDN-
E supplementary services can be charged in mobile exchanges.
This document does not cover output of call data records. This is described in reference [1.
This document does not replace Function Specifications or any other operation and maintenance
documents.
The command examples in this document are simplified and might exclude necessary non
charging related parameters.
1.2 Revision Information

This document is based on 7/1553-APX 101 01/3 Rev. A. The reason for this revision is addition
of SAE 1097 and 1098 which are originated from wireline, and it has been lifted for Wireless
systems. Besides, the Internal AXE cause code value range described was corrected from 4096
to 255.
1.3 Network
An ISDN-E Access can be integrated in the same physical exchange as MSC/VLR, GMSC, SSF,
SMS-GMSC, SMS-IWMSC and HLR functionality.
1.4 Concepts
1.4.1 Terminology
Access Related Individual Number (AIN)

Subscriber number connected to an access.
-
Active Phase
The phase of the call starting when answer message (AMN or CON) has been received and
ending at call disconnection.
-
Advice of Charge (AoC)
Advice of Charge enables the subscriber to receive charging information through his
terminal at set up, during and at end of a specific call.
-
Call Data Record
A Call Data Record contains the collection of charging data that concerns a call or a non
call related supplementary service.
-
Charging Determination Point (CDP)
The Charging Determination Point is the exchange in the network that decides how a call
should be charged.
-
Charging Point
The Charging Point is the exchange in the network that performs the charging of a call,
based on information received from the CDP.
-
Default Calling Number (DCN)
Number to be used as calling party number in case a user provided number is not accepted
or available.
-
Direct Dialling In (DDI)
The Direct Dialling In supplementary service enables a calling user to make a call via the
public network directly to a user within a private exchange without the assistance of an
operator.
-
End-To-End Information
User provided information elements which are part of call control messages and
transparently transported through the network.
-
Event Module
An Event Module contains data related to an event during a call, such as invocation of a
call related supplementary service.
-
Flexible Counter
Counter(s) that have no predefined meaning. The counter(s) are used to register the
number of information elements transfered for the charged subscriber. These counters are
used during the call only.
-
Group Number (GN)
Subscriber number which identifies a Group Number Route.
-
Group Number Related Individual Number (GIN)
Individual number which has a relation to a group number.
-
ISDN-E
A common identifier for a specific Ericsson implementation of ISDN functions based on
Ericsson and ETSI standards, used to distinguish this implementation from other Ericsson
ISDN implementations.
-
Information Case Code
AXE internal representation having only local network-user significance. Translated to
access protocol causes and/or text messages. The total number of information case codes
is 4096. The Information Case Code values in the range from 1 to 255 coincide with
internal cause values. All other Information Case Code values (>255) are locally generated
in AXE function blocks, where situations occur that need a text information and/or an
access protocol cause value to be sent to the user equipment. The information case code is
only valid for ISDN-E access.
-
Internal Cause Code
An internal cause value has end-to-end significance within a node and/or it could be
generated in any part of the system (interwork and be transported), from incoming to
outgoing side or vice-versa. The value range is from 1 to 255.
-
Tariff Class (TC)
A Tariff Class is used to indicate the charge rate of a call/service. The actual charge rate is
dependent on the day and the time of day when the call/service is active.
-
Tariff Message
A Tariff Message is used for transferring charging information between exchanges. A Tariff
Message is used if the charging determination point and the charging point are in different
exchanges.
-
Toll Ticketing (TT)
Toll Ticketing is a charging method which provides detailed outputs for all or certain types
of calls or supplementary services.
-
User To User Service Type 1
User To User Service Type 1 refers to the transfer of User-To-User Information (UUI)
elements in call control messages during the setup/clearing phases of the call.
1.4.2 Abbreviations
ACM
Address Complete Message
AIN
Access Related Individual Number
AoC
Advice of Charge
AOC-D
AoC during the call
AOC-E
AoC at the end of the call
AOC-S
AoC at call set-up time
ATP
Access Transparent Transport
BSCC
Basic Service Charging Code
CAC
Call Attempt Charging
CC
Charging Case
CDF
Call Data File
CDP
Charging Determination Point
CDR
Call Data Record
CI
Call Indicator
CHT
Called Subscriber Charging Type
CO
Origin for Charging
CON
Connect Message
CPC
Calling Party Category
DCN
Default Calling Number
DDI
Direct Dialling In
DSS1
Digital Subscriber Signaling system No.1
EOS
End of Selection
ETSI
European Telecommunication Standard Institute
GN
Group Number
GIN
Group Number Related Individual Number
HLR
Home Location Register
ICC
Information Cause Code
IN
Intelligent Network
ISDN
Integrated Services Digital Network
ISUP
ISDN User Part
MSC
Mobile Switching Center
OBA
Origin for B-number Analysis
OOA
Origin for Output Analysis
PABX
Private Automatic Branch Exchange
PLMN
Public Land Mobile Network
PRA
Primary Rate Access
PSTN
Public Switched Telephone Network
RSSP
Result of Supplementary Service Procedure
SMS-GMSC
Short Message Service Gateway MSC
SMS-IWMSC
Short Message Service Inter-working MSC
SSF
Service Switching Function
SSI
Supplementary Service Indicator
SSP
Supplementary Service Procedure
TC
Tariff Class
TCL
Type of Calling Subscriber
TGR
Tariff Group
TT
Toll Ticketing
TUP
Telephone User Part
UUI
User to User Information
VLR
Visitor Location Register
1.5 Introduction to ISDN-E Charging

ISDN-E Charging can be performed for:
-
Calls originating from an ISDN-E access
-
Calls diverted by an ISDN-E subscriber
-
Usage of non call related supplementary services
-
Usage of call related supplementary services
ISDN-E charging is performed by collecting required data into call data records. Using the data in
these records, a billing system outside the AXE can process the required data in order to produce
a bill for a subscriber.
1.5.1 Call Data Records
The following types of call data records can be output for ISDN-E charging:
a
A call data record used to charge calls originating from an ISDN-E access.
b
A call data record used to charge calls diverted by an ISDN-E subscriber.
c
A call data record used to charge for the usage of non call related ISDN-E supplementary
services.
1.5.2 Event Module
The following event module can be output as part of a call data record for ISDN-E charging:
a
A call data module to charge for supplementary service invocation or activation related to a
call.
1.5.3 Call Types
A call originating from an ISDN-E subscriber connected to a mobile exchange can be routed
towards the following destinations:
-
ISDN/PSTN/PLMN outside the own exchange
-
ISDN in the own exchange
-
GMSC in the own exchange
-
SSF in the own exchange
ISDN-E call data records can also be linked to other call data records output in the own exchange
by using a unique Network Call Reference.
In case of calls through SSF composite call data records may be output.
2 ISDN-E Charging Functionalities
2.1 General
The following chapters describe the mechanisms in the AXE to perform charging of ISDN-E calls
and supplementary services. The chapters are divided into the following parts:
-
Subscriber properties influencing charging
-
Basic call charging
-
Call attempt charging
-
Counting of transferred information elements
-
Service charging
-
Advice of charge
-
IN charging
-
Initiation of call data output
Each part contains where relevant a general description of the functionality, a list of important
Operational Documents and examples how exchange data can be specified. The exchange data
examples found in this document are for definition of new data. No examples to change or
remove data are shown. Similarly there are no examples for the usage of print commands.
2.2 Subscriber Properties Influencing Charging of ISDN-E Calls and

Supplementary Services
2.2.1 Description
Subscriber properties influencing charging can be assigned to ISDN-E subscriptions. The

properties listed below can be assigned to the subscriber number types AIN, GN and GIN. The
only exception is CHVALNM which can only be assigned to AIN and GIN subscriptions.
-
Called Subscriber Charging Type (CHT)
-
Charging of validated number (CHVALNM)
-
Origin for Charging (CO)
-
Calling Party Category (CPC)
-
Origin for B-number analysis (OBA)
-
Tariff Group (TGR)
The properties CHT, CHVALNM, CO, CPC, OBA and TGR are used to influence charging of both
normal and forwarded calls. The properties CHVALNM, CO, CPC and TGR are used to influence
charging of supplementary services.
2.2.1.1 Called Subscriber Charging Type (CHT)
The CHT category assigned to the called subscriber of a call can be used to influence the
charging of the calling subscriber. The CHT can be used as such as input to the ISDN-E basic call
charging analysis in case of local ISDN-E->ISDN-E calls. In case of incoming calls from another
exchange terminating on an ISDN-E subscriber in the own exchange, the CHT is used to set the
charge indicator sent backwards on the ISUP/TUP.
2.2.1.2 Charging of validated number (CHVALNM)
The CHVALNM property is used to specify if an AIN/GIN should be considered the chargeable
subscription, or if the DCN is to be charged for a call/service. An AIN/GIN can only be the
charged subscription if the AIN/GIN was received from the user and successfully validated.
The properties of the charged subscription are used as input to the ISDN-E basic call and service
charging analysis. The charged subscription is also output as the calling party number in call
data records.
2.2.1.3 Origin for Charging (CO)
The CO property can be used to divide subscriptions into classes/categories for which special
charging should be done. The CO property is used as a branching parameter in the ISDN-E basic
call and service charging analysis. The CO value 32 will always lead to a call/service which is free
of charge, i.e. no call data records are possible.
2.2.1.4 Calling Party Category (CPC)
The CPC property specifies the information sent in the forward direction indicating the category
of the calling party. The CPC can influence charging as a branching parameter in the ISDN-E
basic call and service charging analysis. The Type of Calling Subscriber (TCL) available in call
data records is also based on the CPC. An exchange parameter based table in block IUCACH is
used to map the CPC to Type of Calling Subscriber.
2.2.1.5 Origin for B-number analysis (OBA)
The OBA property specifies the analysis tree, where the B-number analysis is to be started. The
OBA can affect charging through the B-number analysis.
2.2.1.6 Tariff Group (TGR)
The TGR property can be used to divide subscriptions into classes/categories for which special
charging should be done. The TGR property is used as a branching parameter in the ISDN-E
basic call and service charging analysis. The prices per charge unit generated for AoC purposes
are specified by TGR.
2.2.2 Commands for Subscriber Property Handling
Default values specified with exchange parameters are used when a subscription is created.
These default values can later be changed with command IUSCC.
Command Description
- IUSCC, ISDN-E End User, End User Service, Change

- IUSCP, ISDN-E End User, End User Service, Print
- IXPCI, ISDN-E Exchange Data, Service Provision
Characteristics, Initiate
- IXEPC: ISDN-E Exchange Data, EMG Property, Change
Adaption Direction
- Subscriber Data: ISDN-E End User Services
Operational Instruction
- ISDN-E, Service Data for Subscriber, Change
Application Information
- Subscriber Categories, ISDN-E
2.2.3 Example
The subscriber number 1234567 is given the value 10 to the

property CO.
IUSCC:SNB=1234567,PROP=CO-10;
2.3 Basic Call Charging

Basic Call Charging is performed in the AXE by collecting call related data into call data records.
The basic call charging analysis dedicated to ISDN-E calls decides whether a TT call data record
should be produced for a call. It also provides some charging related data to be output in call
data records.
Basic call charging analysis also determines the tariff class to be used for a call. A tariff class is
needed in order to be able to generate charge units for AoC purposes.
The input parameters for the ISDN-E basic call charging analysis are obtained from the basic
service analysis, the B-number analysis and calling/called party subscription data.
2.3.1 Basic Service Analysis
2.3.1.1 Description
The basic service analysis is used to determine if the requested bearer and/or tele service is
supported by the exchange and allowed for the calling/called party. The analysis is based on the
elements Bearer Capability and High Layer Compatibility received in the DSS1 Setup message
from the user. In case of diverted calls, where Bearer Capability and High Layer Compatibility
elements are not always available, the Basic Service Analysis may also be based on the
Transmission Medium Requirement.
USER GUIDE FOR CHARGING OF ISDN-E CALLS AND SUPPLEMENTARY SE... Page 10 of 56
The result of the basic service analysis that affects charging is the Basic Service Charging Code
(BSCC). This result reflects the requested bearer/tele service.
2.3.1.2 Commands for Basic Service Analysis Administration
Command Description
- IXBAE, ISDN-E Exchange Data, Basic Service Analysis,

End
- IXBAI, ISDN-E Exchange Data, Basic Service Analysis,
Initiate
- IXBAP, ISDN-E Exchange Data, Basic Service Analysis,
Print
- IXBCC, ISDN-E Exchange Data, Basic Service
Characteristics, Change
- IXBCE, ISDN-E Exchange Data, Basic Service
Characteristics, End
- IXBCI, ISDN-E Exchange Data, Basic Service
Characteristics, Initiate
- IXBCP, ISDN-E Exchange Data, Basic Service
Characteristics, Print
Adaption Direction
- Traffic Data: Basic Service Analysis ISDN-E
Operation Instruction
- ISDN-E, Basic Service, Analysis Data, Change

- ISDN-E, Basic Service, Analysis Data, Define
- ISDN-E, Basic Service, Analysis Data, Delete
2.3.1.3 Example 1 (Telephony Calls)
Basic Service Characteristics are defined for a telephony

call. The BSCC value describing the requested basic service
is 3, ISUP is not required, the transmission medium
requirement is speech, transmission breaks are allowed,
tone sending is allowed and a date and time stamp is not
required. For a subscriber to be allowed to use this basic
service, the basic service type TPHY must be assigned to
the subscription with command IUSCC.
IXBCI:BSCH=1,BSTY=TPHY,BSCC=3,ISPI=1,TMR=0,TBP=NO,TONE=YES,
DTSTAMP=NO;
Basic Service Analysis data for analyzing the received

Bearer Capability and High Layer Compatibility is defined.
In case the required tele service capability is telephony,
transfer capability is speech and transfer mode is circuit
mode, the basic service characteristics for telephony calls
will be used.
IXBAI:TSERV=1,TCAP=0,TMODE=0,BSCH=1;
2.3.1.4 Example 2 (Data Transmission)
Basic Service Characteristics are defined for a tele-Tex

call. The BSCC value describing the requested basic service
is 4, ISUP is preferred, the transmission medium requirement

is 64 kbit/s unrestricted, transmission breaks are not
allowed, tone sending is not allowed and a date and time
stamp is not required. For a subscriber to be allowed to use
this basic service, the basic service type TELETEX must be
assigned to the subscription with command IUSCC.
IXBCI:BSCH=2,BSTY=TELETEX,BSCC=4,ISPI=0,TMR=0,TBP=YES,
TONE=NO,DTSTAMP=NO;
Basic Service Analysis data for analyzing the received

Bearer Capability and High Layer Compatibility is defined.
In case the required tele service capability is tele-Tex,
transfer capability is unrestricted digital information
and transfer mode is circuit mode, the basic service
characteristics for tele-Tex calls will be used.
IXBAI:TSERV=49,TCAP=8,TMODE=0,BSCH=2;
2.3.2 B-Number Analysis
2.3.2.1 Description
The B-number analysis is used to analyze the called number digits. The B-number analysis result
that affects charging is the Charging Case. The Charging Case reflects the destination of the call.
The B-number analysis consists of a preanalysis and the actual B-number analysis. In the
preanalysis the B-number origin, B-number type and Numbering plan are analyzed. The result is
a new B-number origin for the actual B-number analysis. The actual B-number analysis analyzes
the B-number origin and called party number and results in information how the call should be
routed, charged, etc.
In case several Charging Cases are specified for the analyzed B-number, the last one found is
used as input to the ISDN-E basic call charging analysis.
2.3.2.2 Commands for Administering B-Number Analysis Data
Command Description
- ANBAI, Analysis of B-Number, Activation, Initiate

- ANBAR, Analysis of B-Number, Activation, Reset
- ANBCI, Analysis of B-Number, Copying, Initiate
- ANBLI, Analysis of B-Number, Logged, Initiate
- ANBSE, Analysis of B-Number, Specification, End
- ANBSI, Analysis of B-Number, Specification, Initiate
- ANBSP, Analysis of B-Number, Specification, Print
- ANBZI, Analysis of B-Number, Zeroing, Initiate
- PNBAI, Pre-Analysis of Number Information for B-Number,
Activation, Initiate
- PNBAR, Pre-Analysis of Number Information for B-Number,
Activation, Reset
- PNBCI, Pre-Analysis of Number Information for B-Number,
Copying, Initiate
- PNBLI, Pre-Analysis of Number Information for B-Number,
Logging, Initiate
- PNBSE, Pre-Analysis of Number Information for B-Number,
Specification, End
- PNBSI, Pre-Analysis of Number Information for B-Number,
Specification, Initiate
- PNBSP, Pre-Analysis of Number Information for B-Number,
Specification, Print
- PNBZI, Pre-Analysis of Number Information for B-Number,
Zeroing, Initiate
Adaption Direction
- Traffic Data: B-Number Analysis
Operational Instructions
- B-Number Analysis Data, Change
2.3.2.3 Example
The following example shows a simple example of B-number analysis data. The CC which the B-
number analysis data refers to must be specified and active in the ISDN-E Basic Call Charging
Analysis data.
For numbers with B-number origin 0, numbering plan 1

(ISDN/PSTN E.163/E.164), B-number type 1 (International
number), the analysis is continued with B-number analysis
origin 10.
PNBSI:BO=0,NAPI=1,BNT=1,OBA=10;
For numbers with B-number origin 10 within the number

series 1234, Charging Case 2 and Routing Case 3 are used.
ANBSI:B=10-1234,CC=2,RC=3,L=5-15;
The B-number analysis data is specified in a non operating area which must be activated before
it will be used during traffic.
2.3.3 ISDN-E Basic Call Charging Analysis
2.3.3.1 Description
The ISDN-E Basic Call Charging Analysis is performed when the call has reached the called party.
In case of calls to another exchange using ISUP/TUP signaling this means that ISDN-E basic call
charging analysis is done when ACM/CON is received. In case of local calls within the own
exchange, the ISDN-E basic call charging analysis is done when alerting starts.
The ISDN-E Basic Call Charging Analysis consists of two parts, i.e the branching condition
analysis and the charging program analysis.
Note: The charging program must be set locally in IUSAM for ISDN-E calls. Thus the application
parameter CHARGING_ANALYSIS_LOCATION must be set to "local charging analysis" in IUCCON.
The branching condition analysis analyzes the following input values:
-
Charging Case
-
-
Call Indicator
-
Charging Origin
-
Tariff Group
-
-
Called subscriber Charging Category
The call indicator indicates what type of call is being setup, i.e. a normal call or a diverted call.
The other input parameters have been described in previous chapters.
The branching condition data is structured in branching condition trees. There is a branching
condition tree for every charging case.
The result of the Branching Condition Analysis is a reference to a charging program. The
charging program reference is used as input to the charging program analysis.
The charging program analysis analyzes the charging program pointed out by the branching
condition analysis. The results of the charging program analysis are:
-
The location of the charging determination point and the charging point.
-
The charged party (A-party or no-party)
-
Whether a Toll Ticketing call data record should be produced (TT=FEP-64).
-
Tariff Class.
-
Outgoing Trunk Information
If the charging determination point is not in the own exchange, a tariff message must have been
received at the time when the charging analysis is performed. If this is not the case, the call will
be disconnected or free of charge, depending on the exchange parameter CHFAULTACTION in
block IUCCON. If a charging message is received, a new ISDN-E basic call charging analysis is
initiated. The used CC is in this case obtained from the tariff message.
The ISDN-E Basic Call Charging Analysis data is specified in a not operating area. The not
operating area must be activated in order to be used during traffic.
2.3.3.2 Commands for Specifying ISDN-E Basic Call Charging Analysis Data
Command Description
- ICAPE, ISDN-E Charging, Call Charging Program

Specification Procedure, End
- ICAPI, ISDN-E Charging, Call Charging Program
Specification Procedure, Initiate
- ICASE, ISDN-E Charging, Call Charging Program
Specification, End
- ICASI, ISDN-E Charging, Call Charging Program
- ICASP, ISDN-E Charging, Call Charging Program
- ICAZI, ISDN-E Charging, Call Charging Program
Zeroing, Initiate
- ICBAI, ISDN-E Charging, Call Branching Condition
Activation, Initiate
- ICBAR, ISDN-E Charging, Call Branching Condition
Activation, Reset
- ICBPE, ISDN-E Charging, Call Branching Condition,
Procedure End
- ICBPI, ISDN-E Charging, Call Branching Condition,
Procedure Initiate
- ICBSE, ISDN-E Charging, Call Branching Condition
Specification, End
- ICBSI, ISDN-E Charging, Call Branching Condition
- ICBSP, ISDN-E Charging, Call Branching Condition
- ICBZI, ISDN-E Charging, Call Branching Condition
Zeroing, Initiate
Adaption Direction
- Traffic Data: Call Charging Analysis Program ISDN-E,

Mobile
- Traffic Data: Call Charging Analysis Branching Condition
ISDN-E
- ISDN-E, Call Charging Program, Change

- ISDN-E, Call Charging Program, Define
- ISDN-E, Call Charging Program, Delete
- ISDN-E, Charging Case, Change
- ISDN-E, Charging Case, Define
- ISDN-E, Charging Case, Delete
2.3.3.3 Example
The not operating area is cleared
ICAZI:CHP=1&&5;
New charging programs are specified in the not operating

area. Before the following commands can be successfully
executed, the TCs must be defined and activated. See
ADI TRAFFIC DATA: TARIFF CLASSES for more information
about specification of Tariff Classes.
ICASI:CHP=1,CD=3,NP,TT=FEP-64;
ICASI:CHP=2,CD=3,AP,TT=FEP-64,TC=1;
ICASI:CHP=5,CD=1;
The new charging programs are activated
ICAAI:CHP=1&&5;
Charging Case data is cleared in the not operating area.
ICBZI:CC=1&3&5;
A charging case tree without branching conditions is

specified
ICBSI:CC=1,CHP=2;
A charging case tree including branching conditions is

specified. The first branch specifies that in case of
CI=1 (normal originating call), CO between 1 and 5 and
CHT=0 (charged call), Charging Program number 3 is used.
The second branch specifies that in case of
CI=1 (normal originating call), CO between 1 and 5 and
CHT=1 (call free of charge), Charging Program number 1
is used. The third branch specifies that in case of
CI=4 (forwarded call) and CHT=0 (charged call), Charging
Program number 4 is used. The fourth branch specifies
that in case of CI=4 (forwarded call) and CHT=1 (call free
of charge), Charging Program number 1 is used.
ICBPI:CC=3;
ICBSI:BC=CI-1&CO-1&&-5&CHT-0,CHP=3;
ICBSI:BC=CHT-1,CHP=1;
ICBSI:BC=CI-4&CHT-0,CHP=4;
ICBSI:BC=CHT-1,CHP=1;
ICBPE;
A charging case tree is specified for calls where a

tariff message is expected. Information received in
the tariff message is used as charging case when a new
ISDN-E basic call charging analysis is started due to
the reception of a tariff message. The tariff message
must contain a charging case that is defined in the
ISDN-E basic call charging analysis data of the
receiving exchange.
ICBSI:CC=5,CHP=5;
The new Charging Case trees are activated
ICBAI:CC=1&3&5;
The branching condition trees specified above have the following structure:
CC CI CO CHT
/--0 /---0 /---0 /----0---- CHP=3

+--1-- CHP=2 +---1------------1---\ +----1---- CHP=1
+--2 +---2 +---2---+ +----2
+--3-------------3 +---3-------------3
+--4 +---4---\ +---4---+ +----4
+--5-- CHP=5 +---5 | +---5---/ .
| +---6 | | . .
+---7 | +---25
. | +---26
. | | .
| | .
| +---50
| | .
| +---66
| +---67
| .
|
| /----0---- CHP=4
| +----1---- CHP=1
\----------------------2
+----3
FIGURE 1: Branching Condition Tree
2.4 Call Attempt Charging

The function provides the operator with a mechanism to register and charge Call Attempts. Call
Attempt Analysis can be performed when a call is disconnected before reaching active phase. If
the Call Attempt is chargeable Call Attempt Charging can be performed and Call Attempt data
can be output in the CDR.
Depending on a parameter setting it is also possible to charge Call Attempts for calls reaching
active phase.
Call Attempt Analysis is based on analysis and mapping tables. These tables are defined by
application parameters and commands. If the Call Attempt is chargeable, a selected flexible
counter can be stepped.
2.4.1 Call Attempt Analysis
2.4.1.1 Description
Upon call disconnection the Call Attempt data is analysed to determine if the Call Attempt is
chargeable. Before Call Attempt Analysis is initiated, it is checked whether the capabilities
regarding the called subscriber and signaling type indicate that Call Attempt Analysis should be
performed.
Type of Called Subscriber

Type of called subscriber can be:
- ISDN
- PSTN
- Unknown
For each type of called subscriber it can be specified whether Call Attempt Analysis should be
performed or not.
Type of Signaling
Type of signaling can be:
- ISUP all the way
- Not ISUP all the way
- Local
- Unknown
For each type of signaling it can be specified whether Call Attempt Analysis should be performed
or not.
If the above mentioned checks indicate that Call Attempt Analysis can be initiated, the analysis
will be performed with the following inputs:
- Call Attempt State
- Cause and Location for call disconnection
- Type of release
Call Attempt State

The progress of the call setup is derived from the signaling of the route of the call setup and the
Call Attempt State is set accordingly. The Call Attempt States are:
Initial Start of call setup, ie. the call request

is not sent yet.
Call Sent The call request has been sent, but no

acknowledgment has been received yet.
Call Rejected The call is rejected and is not offered to
the called subscriber, e.g. due to congestion

in the public network.
Call Offered The call is offered to the called subscriber

but no response is received yet, ie. an ACM
is received without backward information.
No Response A call has been offered but the call is

rejected or no response has been received and
a time out has occurred. In case of a PABX
supporting DDI the state is reached when a
call was sent but no ACM is received.
Alerting The call has been accepted by the called

subscriber and alerting has started.
Unknown Call The progress of the call setup can't be

determined since the information received is
insufficient.
Active The call has reached active phase.
For each state it can be specified whether Call Attempt Charging should be performed, whether
the result should depend on the type of release or if the result should depend on Cause and
Location.
The Call Attempt State output in the CDR is an external operator defined state which is mapped
from the internal state using exchange parameters.
Cause and Location

The Cause value indicates the reason for the call disconnection, e.g. 'No Circuit/Channel
Available' or 'No Route to Destination'. The cause value used in the Call Attempt Analysis is an
external (operator defined) value which is mapped from an internal cause code (Cause Code
Mapping Table):
/---------\
1 | |
+---------+
2 | |
+---------+
-------->| |----------->
Internal | | External
AXE Cause| | User Defined
Code | | Cause Code
| |
+---------+
255 | |
\---------/
FIGURE 2: Cause Code mapping table
The Cause Code mapping table is specified with commands. For call attempt charging only a
subset of the mapping between information case code (i.e. 1..255 -> internal cause codes) and
external cause is applicable. The values to be used in the mapping table are described in AI
'Information Cause Code Analysis'.
The Location value indicates in which parts of the network the release occurred, e.g. 'Public
Network Serving the Local User' or 'Public Network Serving the Remote User'. Location values
are described in AI 'Route Analysis'.
Two tables are provided to perform analysis of the call attempt criteria depending on the
external cause and the location for the call clearing.
The first table (External Cause/Location Release Analysis Table) determines if a Release Analysis
shall be performed or a second table shall be consulted. The second table (External
Cause/Location Call Attempt Criteria) specifies if charging is to be performed for the given
combination of cause and location values.
Type of Release
Type of release can be:
- A-party
- B-party
- Network (other)
For each type of release it can be specified (in Release Analysis Table) whether Call Attempt
Charging should be performed or whether the result should depend on cause and location.
2.4.1.2 Commands for Specifying Information Case Code Data
Command Description
- IXICC, ISDN-E Exchange Data, Analysis of Information

Case Code, Change
- IXICE, ISDN-E Exchange Data, Analysis of Information
Case Code, End
- IXICI, ISDN-E Exchange Data, Analysis of Information
Case Code, Initiate
- IXICP, ISDN-E Exchange Data, Analysis of Information
Case Code, Print
Adaption Direction
- Traffic Data: Information Case Code Analysis

Specifications ISDN-E
- Information Case Code Analysis Specifications

ISDN-E Administration
- Information Cause Code Analysis,

Changeable Exchange Adaption
- Route Analysis
2.4.1.3 Example
The signaling capabilities must be 'ISUP all the way' and the type of the called subscriber must
be 'ISDN' before Call Attempt Analysis is initiated. If we have a local call, the signaling
capabilities are also on the same level as ISUP:
SIGNALLINGTYPEISUP = 1 (Perform Call Attempt Analysis)
SIGNALLINGTYPELOCAL = 1 ( " )
CALLEDSUBSCRIBERISDN = 1 ( " )
For all calls ending up in state 'Call Offered' (Internal AXE Call State 3), the External
Cause/Location Release Analysis Table should be checked. If the Call Attempt state is
'Alerting' (Internal AXE Call State 5) the Call Attempt is always chargeable:
RESULTSTATEANALYSIS3 = 3 (Call Offered -> External Cause/

Location Release
Analysis
required)
RESULTSTATEANALYSIS5 = 1 (Alerting -> Call Attempt

chargeable)
If the call is disconnected with Information Cause Code 6 (Call Rejected), it should be checked
from where the disconnection was initiated (Release Analysis Table). If the call is disconnected
with Information Cause Code 61 (No answer from User), Call Attempt Charging should always be
performed.
ICC value 6 should be mapped to external cause 21 and ICC value 61 to external cause 19.
Value 0 will be used as Origin for Analysis:
IXICI:ORIG=0,ICC=6,CAUSE=21;
IXICI:ORIG=0,ICC=61,CAUSE=19;
For cause code 21, the following locations will indicate that Release Analysis Table should be
checked:
0 =
User
1 =
Local network (Private network serving the local user)
2 =
Local network (Public network serving the local user)
3 =
Transit network
4 =
Remote local network (Public network serving the
remote user)
5 = Remote private network (Private network serving the
remote user)
All other location values will indicate that no Call Attempt Charging should be performed. This
must, however, be indicated in the External Cause/Location Call Attempt Criteria Table.
This gives us the following bit string for cause code 21:
Location: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit: 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1
CAUSELOCATIONRAR021 = H'003F
For locations 6 - 15 it is indicated in the 2nd matrix that no Call Attempt Charging should be
performed. Locations 0 - 5 are also set to 0, meaning that if the release is caused by the
network no Call Attempt Charging will be performed. In case the release is caused by the A or B
party, the analysis ends up in the Release Analysis Table.
CAUSELOCATIONCAC021 = H'0000 (No Call Attempt Charging)
For cause code 19 Call Attempt Charging will always be performed:
CAUSELOCATIONRAR019 = H'0000 (For all locations,check

the External Cause/
Location Call Attempt
Criteria Table)
CAUSELOCATIONCAC019 = H'FFFF (For all locations, perform

Call Attempt Charging).
If the call is disconnected by the A or B subscriber, the Call Attempt is chargeable. If the call is
disconnected by the network, the result will depend on Cause and Location:
APARTYRELEASE = 1 (Call Attempt chargeable)
BPARTYRELEASE = 1 ( " )
OTHERRELEASE = 0 (Check External Cause/Location

Call Attempt Criteria Table)
If the Call Attempt is chargeable, it will be indicated on flexible counter 1:
CALLATTEMPTINDICATION = 8 (If Call Attempt chargeable,

step flexible counter 1)
State Analysis table
/---------\
0 | |--> (NO CAC)
+---------+ Release Analysis table
1 | |--> (NO CAC)
+---------+ /---------\
2 | |--> (NO CAC) A | |--> (CAC)
+---------+ /-> +---------+
--------> 3 | |-------------\ | B | |--> (CAC)
Internal +---------+ | | +---------+
AXE Call 4 | |--> (NO CAC) | | O | |---\
State +---------+ | | \---------/ |
5 | |--> (CAC) | | |
+---------+ | | |
6 | |--> (NO CAC) | | |
\---------/ | | |
| | |
/-----------------------------------/ \-----------------\ |
| | |
| External Cause/Location Release Analysis Table | |
| | |
| 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 | |
\-> /-----------------------------------------------\ | |
0 | | | | | | | | | | | | | | | | | | |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--| | |
| | | |
/---------------------------------------------------\| | |
| +-+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--++ | |
| 19 | 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| | |
| +-----------------------------------------------+ | |
| 20 | | | | | | | | | | | /------------------/ |
| +-------------------------------+--+--+--+--+--++ |
| 21 | 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 1| 1| 1| 1| 1| 1| |
| +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--| |
+------+--+--+--+--+--+--+--+--+--/ | |
| | | |
| +-----------------------------------------------+ |
|255 | | | | | | | | | | | | | | | | | |
| \--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--/ |
| |
| |
v v
v v
| |
| External Cause/Location Call Attempt |
| Criteria Table |
| |
| 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 |
| /-----------------------------------------------\ |
| 0 | | | | | | | | | | | | | | | | | |
| +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--| |
\--> | | <--/
| |
+-----------------------------------------------+
19 | 1| 1| 1| 1| 1| 1| 1| 1| 1| 1| 1| 1| 1| 1| 1| 1| (CAC)
+-----------------------------------------------+
20 | | | | | | | | | | | | | | | | |
+-----------------------------------------------+
21 | 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| (NO CAC)
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--|
| |
| |
+-----------------------------------------------+
255 | | | | | | | | | | | | | | | | |
\--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--/
(CAC) : Call Attempt is chargeable

(NO CAC) : Call Attempt is not chargeable
FIGURE 3: Call Attempt Analysis data.
2.5 Counting of Transfered Information Elements

Information elements exchanged between two subscribers with ISDN capabilities are transfered
in call control messages. These call control messages can consist of various information elements
which can be counted for charging purposes.
The information transfered in the User to User (UUI) element in call control messages is carried
transparently to the remote user. These elements are used in relation with the supplementary
service User-To-User Service Type 1.
Information sent in other elements is often referred to as End-To-End elements.
It is also possible to use the Call Attempt function to decide if transfered information elements
should be counted, e.g. for calls disconnected before reaching active phase. The elements can be
counted if the Call Attempt is chargeable and the call and subscriber capabilities indicate:
- the type of the called subscriber is ISDN
- ISUP signaling is supported all the way
If the capabilities of the called subscriber are unknown at call disconnection, counting of
elements is still performed if the Call Attempt is chargeable.
2.5.1 Counting of Information Elements on flexible counters
2.5.1.1 Description
The transfered information elements are counted on selected flexible counters during the call.
The selection is done with exchange parameters. This mapping between information elements
and flexible counters is called Layer 1 mapping.
At call termination/partial output the flexible counters are output in a detailed call data record if
required.
2.5.1.2 Information Elements that can be Counted/Charged
The following Information elements can be independently counted and charged in the forward
and backward direction:
ATP data, forward direction

-
ATP data, backward direction
-
ATP octets, forward direction
-
ATP octets, backward direction
-
Low Layer Compatibility, forward direction
-
Low Layer Compatibility, backward direction
-
Progress indicator, forward direction.
-
Progress indicator, backward direction.
-
User provided cause, forward direction.
-
User provided cause, backward direction.
-
Network provided cause, forward direction.
-
Network provided cause, backward direction.
The following elements are uni directional i.e they can only be sent in one direction. They can
also be independently counted like any other information elements.
-
Calling Party Number.
-
Second Calling Party Number
-
Calling Party Sub address.
-
Called Party Sub address.
-
High Layer Compatibility.
-
Connected Party Sub address.
-
Bearer capability.
The following UUI elements consists of messages transfered transparently between the
subscribers terminal. These messages consist of information elements that can be counted.
-
User to User service type 1, forward direction.
-
User to User service type 1, backward direction.
There is also a parameter that indicates if a flexible counter should be stepped in case a call
attempt is chargeable.
2.5.1.3 Individual or collective counting of information elements
It is possible to select how the information elements are to be counted. Two possible options
exist (set with exchange parameters):
-
Transfered information elements can be counted collectively.
The selected flexible counter is incremented by one when one or more information
elements are transferred. The flexible counter chosen for this purpose is selected with an
exchange parameter (ALLACCESSDATA).
-
Transfered information elements can be counted individually.
The selected flexible counter is incremented by one for the transfer of each information
element that is to be counted.
Note:
When counting information sent in UUI elements, the selected flexible counter is stepped once
for each message unit provided that it is not an Empty Message. The minimum size of an not
Empty Message is defined by exchange parameter CHARGING_LENGTH in IUUUS.
2.5.2 Example
The figure below is an example of a Layer 1 mapping. Under each information element the
setting of the corresponding exchange parameter is indicated.
The mapping below means that User-to-User 1 elements (both directions) will be counted on
flexible counter 2, Calling Party Sub address will be counted on flexible counter 6 and Called
Party Sub address will be counted on flexible counter 7.
Information Elements Flexible Counters
Flexible counter 1
U2U forw. service 1 --------------------------\

(UUS1SERVICEFW = 9) | |
| Flexible counter 2
U2U back. service 1 --/
(UUS1SERVICEBW = 9) Flexible counter 3
ATP data, forw. direction Flexible counter 4

(ATPDATAELEMENTFW = 0)
Flexible counter 5
ATP data, backw. direction
(ATPDATAELEMENTBW = 0) /----------------\
| |
Calling party number | Flexible counter 6
(CALLINGPTYNUM = 0) |
| /--------------\
2 nd. Calling party number | | |
(SECONDCALLINGPTYNUM = 0) | | Flexible counter 7
| |
Calling party subaddress ----/ | Flexible counter 8
(CALLINGPTYSUBADDRESS = 13) |
|
Called party subaddress ------/
(CALLEDPTYSUBADDRESS = 14)
High layer compatibility

(HLCOMPATIBILITY = 0)
Low layer compatibility, forw.

(LLCOMPATIBILITYFW = 0)
Low layer compatibility, back.

(LLCOMPATIBILITYBW = 0)
Connected party subaddress

(CONNECTEDPTYSUBADDRESS = 0)
Bearer capability
(BEARERCAPABILITY = 0)
Progress indicator, forw.

(PROGRESSINDICATORFW = 0)
Progress indicator, backw.

(PROGRESSINDICATORBW = 0)
User provided cause, forw.

(USERPROVIDEDCAUSEFW = 0)
User provided cause, backw.

(USERPROVIDEDCAUSEBW = 0)
Network prov. cause, forw.

(NETPROVIDEDCAUSEFW = 0)
Network prov. cause, backw.

(NETPROVIDEDCAUSEBW = 0)
FIGURE 4: Layer 1 mapping.
2.6 Service Charging

The usage of Supplementary Services can be recorded in call data records or event modules
based on the result of the ISDN-E service charging analysis.
2.6.1 ISDN-E Service Charging Analysis
2.6.1.1 Description
The ISDN-E Service Charging Analysis is used to decide whether ISDN-E supplementary services
should be recorded in the form of TT outputs.
The Service Charging Analysis uses some input parameters which are specific for supplementary
service charging:
-
Supplementary Service Indicator (SSI)
SSI indicates which supplementary service has been used, e.g. Closed User Group.
-
Supplementary Service Procedure (SSP)
SSP indicates the action that has been performed for the supplementary service, e.g.
activation.
-
Result of Supplementary Service Procedure (RSSP)
RSSP indicates the result of the action performed for the service, e.g. double ordered
procedure.
The possible values for these parameters are described in Application Information 'Traffic Activity
Code, ISDN-E Subscribers'.
The ISDN-E Service Charging Analysis consists of two parts, i.e the branching condition analysis
and the charging program analysis. The branching condition analysis analyses the following input
values:
-
Supplementary Service Indicator
-
Supplementary Service Procedure
-
Result of Supplementary Service Procedure
-
Charging Origin
-
Tariff Group
-
-
The result of the Branching Condition Analysis is a reference to a charging program. The
charging program reference is used as input to the charging program analysis.
The charging program analysis analyzes the charging program pointed out by the branching
condition analysis. The results of the charging program analysis are:
-
Whether Toll Ticketing applies to the service (TT=FEP-64).
-
Tariff Class.
-
Charged Party
The ISDN-E Service Charging Analysis data is specified in a not operating area. The not
operating area must be activated in order to be used during traffic.
2.6.1.2 Commands for Specifying ISDN-E Service Charging Analysis Data
Command Description
- ICSAI, ISDN-E Charging, Service Charging Program,

Activation Initiate
- ICSAR, ISDN-E Charging, Service Charging Program,
Activation Reset
- ICSSE, ISDN-E Charging, Service Charging Program,
Specification End
- ICSSI, ISDN-E Charging, Service Charging Program,
Specification Initiate
- ICSSP, ISDN-E Charging, Service Charging Program,
Specification Print
- ICSZI, ISDN-E Charging, Service Charging Program,
Zeroing Initiate
- ICCAI, ISDN-E Charging, Service Branching Condition,
Activation Initiate
- ICCAR, ISDN-E Charging, Service Branching Condition,
Activation Reset
- ICCPE, ISDN-E Charging, Service Branching Condition,
Procedure End
- ICCPI, ISDN-E Charging, Service Branching Condition,
Procedure Initiate
- ICCSI, ISDN-E Charging, Service Branching Condition,
Specification Initiate
- ICCSP, ISDN-E Charging, Service Branching Condition,
Specification Print
- ICCZI, ISDN-E Charging, Service Branching Condition,
Zeroing Initiate
Adaption Direction
- Traffic Data: Service Charging Analysis Branching

Condition ISDN-E
- Traffic Data: Service Charging Analysis Program ISDN-E,
Mobile
- ISDN-E, Branching Condition Data, Change

- ISDN-E, Branching Condition Data, Define
- ISDN-E, Branching Condition Data, Delete
- ISDN-E, Service Charging Program, Change

- ISDN-E, Service Charging Analysis Program, Define
- ISDN-E, Service Charging Program, Disconnect
- Traffic Activity Code, ISDN-E Subscribers

2.6.1.3 Example
The not operating area is cleared
ICSZI:CHPS=1&&4;
New charging programs are specified in the not operating

area
ICSSI:CHPS=1,NP,TT=FEP-64;
ICSSI:CHPS=2,AP,TT=FEP-64,TC=1;
The new charging programs are activated
ICSAI:CHPS=1&&4;
The not operating area for branching condition data is

cleared.
ICCZI;
A branching tree is specified. The branching tree has a

similar structure to the branching tree shown in Figure 1
(SSI-121 = Closed User Group, SSI-4 = Call Forwarding No
Reply).
ICCPI;
ICCSI:BC=SSI-121&CO-1&&-5,CHPS=3;
ICCSI:BC=CO-7,CHPS=1;
ICCSI:BC=SSI-4&CO-1,CHPS=4;
ICCSI:BC=CO-3,CHPS=2;
ICCPE;
The new branching tree is activated
ICCAI;
2.7 Advice of Charge
2.7.1 Description
The supplementary service Advice of Charge (AoC) enables the served user to receive charging
rate information at call set-up and to receive recorded charging information during the active
phase and at end of the call.
AoC for ISDN-E Mobile System Calls is divided into three services:
-
AoC at call set-up time (AOC-S)
-
AoC during the call (AOC-D)
-
AoC at the end of the call (AOC-E)
2.7.2 Advice of Charge at Call Set-Up Time
The AOC-S supplementary service is a call-related service which makes it possible to send
charging information to the served user's premises at call set-up. It can be activated only during
call setup, either on all calls (in which case activation is automatic) or on a per call basis (in
which case the served user activates the service when originating the call). The service is
automatically invoked at the same time as it is activated.
When the AOC-S service is invoked the information about the charging rates that will apply to
the call will be assembled by the network and sent to the served user during the call set-up
period. The information is provided at the latest when the calling user is informed that the called
user has accepted the call. The charging information relates to the charges incurred on the
network to which the served user is attached.
If the charging rate changes during the call (for example due to a tariff switch or change in user
tariff) then AOC-S is automatically invoked again and the served user will be informed of the new
charging rates.
2.7.3 Advice of Charge During the Call
The AOC-D service is a call related supplementary service which allows the served user to
receive call related charging information both during the active phase of an ISDN call and when
the call is terminated. This means that AOC-D also automatically includes AOC-E.
The service can be either activated automatically at the start of the call, requested during call
setup or requested during the call.
Charging information will then be sent to the served user's terminal equipment at periodic
intervals until and also at the end of the call. The supplied information will be the cumulative
charge incurred from the start of the call until the moment when the charging information is sent
to the served user.
2.7.4 Advice of Charge at the End of the Call
The AOC-E service is a call related supplementary service which allows the served user to
receive call related charging information at the end of an ISDN call.
The service can be either activated automatically at the start of the call, requested during call
setup, or requested during the call.
Charging information will then be sent to the served users terminal equipment at termination of
the call. This information relates to the charges incurred by the served user on the network for
the call.
2.7.5 Commands for Handling AoC
Command Description
- CHTSI, Charging Administration of Tariff Specification,

Initiate
- CHRAI, Charging Administration of Tariff Activation,
Initiate
- CHCPI, Charging Administration of Tariff Class Procedure,
Initiate
- CHCSI, Charging Administration of Tariff Class
- CHCPE, Charging Administration of Tariff Class Procedure,
End
- CHCAI, Charging Administration of Tariff Class Activation,
Initiate
- CHSZI, Charging Administration of Switching Class Zeroing,
Initiate
- CHSPI, Charging Administration of Switching Class
Procedure, Initiate
- CHSSI, Charging Administration of Switching Class
- CHSPE, Charging Administration of Switching Class
Procedure, End
- CACAS, Calendar Function, Day Category,
Set
- IUSCC, ISDN-E End User, End User Service,
Change
- IUSOC, ISDN-E End User, Service Options,
Change
- ICPSC, ISDN-E, Charging Price Specification,
Change
- ICPSE, ISDN-E, Charging Price Specification,
End
- ICPSP, ISDN-E, Charging Price Specification,
Print
Adaption Direction
- Subscriber Data: Charging Price Specification ISDN-E

- Traffic Data: Switching Classes
- Traffic Data: Tariff Data
- Traffic Data: Tariff Classes
- ISDN-E, Charging, Price Specification, Initiate

- ISDN-E, Charging, Price Specification, Change
- ISDN-E, Charging, Price Specification, End
- ISDN-E User Advice of Charge, During the Call

- ISDN-E User, Advice of Charge, at the End of the Call
- ISDN-E User, Advice of Charge at Call Set-Up Time
2.7.6 Examples
2.7.6.1 Prerequisites
In order to enable a subscriber to use the supplementary service Advice of Charge the charging
analysis data must be specified so that it is possible to determine a valid tariff class and tariff for
the call. For more information see chapter 'ISDN-E Basic Call Charging Analysis' above.
First the tariffs are specified like tariff 1 below:
CHTSI:T=1,NSP=15,TDS=10,NPP=5;
CHRAI:T=ALL;
Tariff 1 generates 15 charge units at the beginning of charging and subsequently 5 charge units
every 10 seconds. The tariff is activated immediately. For more options see ADI TRAFFIC DATA:
TARIFF DATA.
After this the day categories are specified as below:
CACAS:DAY=MON,DCAT=0;
CACAS:DAY=TUE,DCAT=0;
CACAS:DAY=WED,DCAT=0;
CACAS:DAY=THU,DCAT=0;
CACAS:DAY=FRI,DCAT=0;
CACAS:DAY=SAT,DCAT=3;
CACAS:DAY=SUN,DCAT=6;
Midweek days are given day category 0, Saturdays day category 1 and Sundays day category 3.
Switching classes also have to be defined:
CHSZI:SWC=1;
CHSPI:SWC=1
CHSSI:DCAT=0, TIME=0700&1200&2000&2200;
CHSSI:DCAT=3, TIME=1200&2200&0000;
CHSSI:DCAT=6;
CHSPE;
Switching class 1 above is given four switching times for day category 1 and three switching
times for day category 3. For day category 6 tariff 1 is applicable all day since no switching time
is given. For more options about specifying of switching classes see ADI TRAFFIC DATA:
SWITCHING CLASSES.
The tariff classes are specified like tariff class below:
CHCPI:TC=1, SWC=1;
CHCSI:DCAT=0, T=5&2&3&4;
CHCSI:DCAT=3, T=1&3&6;
CHCSI:DCAT=6 T=1;
CHCPE;
CHCAI:TC=1;
The tariff class 1 above is given 3 day categories and 6 tariffs including tariff 1 specified aerlier.
The tariff class is connected to switching class 1 also specified earlier. For more detailed
information see ADI TRAFFIC DATA: TARIFF CLASSES.
This finally gives the following situation:
/-------------------------------------\
| DCAT | Switching times and tariffs |

/----------------------------------------------------+
| Time | | 0700 1200 2000 2200 |
+--------------- 0 ------------------------------+
| Valid tariff | | 5 | 2 | 3 | 4 | 5 |
+----------------------------+-----+-----+-----+-----+
| Time | 0000 1200 2200 2400
+--------------- 3 ------------------------------+
| Valid tariff | | 1 | 3 | 6 |
+----------------------------------+-----------+-----+
| Time | 0000 2400
+--------------- 6 ------------------------------+
| Valid tariff | | 1 |
\--------------+-------+-----------------------------/
After this, the calling subscriber is provided a tariff group:
IUSCC:SNB=1234567, PROP=TGR-63;
In this example the subscriber with number 1234567 is connected to tariff group 63.
2.7.6.2 Definition of AoC data for a Subscriber
The charging analysis described above finally results in a applicable tariff which in the end
generates charge units for the AoC functionality. Now a price for each charge unit and for
stepping of flexible counters is to be defined:
ICPSC:TGR=63, PRICEBC=20, PRICE1=10, PRICE8=15;
In this example the prices for tariff group 63 is defined. The price for one charge unit is 20. The
price for stepping of flexible counter 1 is 10 and for counter 8 it is 15.
Changing the prices for a tariff group does not affect ongoing calls.
NOTE: Output of User-To-User 1 supplementary service information and End-To-End information

on flexible counters and inclusion of the flexible counters into charging information for AoC is
defined by exchange parameters. The flexible counters are included into charging information by
default by IUAOCD parameter INCLUDE_FLEXIBLE_COUNTER1..8. However, the User-To-User 1
information is not put on the flexible counters by default so if required the IUCITM parameter
UUS1SERVICEFW is to be set.
2.7.6.3 Provisioning of Supplementary Service AoC for a Subscriber
The AoC information or price for a tariff group is now defined. A subscriber is also connected to
the new tariff group (above). However, no AoC information will still be generated since the
subscriber is not provided with any AoC service yet:
IUSCC:SNB=1234567, SS=AOCD-1;
The subscriber is now provided with the supplementary service AOC-D for all calls. AOC-S and
AOC-E is handled in a similar way.
2.7.6.4 Defining of activation and presentation mode for AoC
In order to get a proper outcome an activation and presentation mode has to be set for the
subscriber:
IUSOC:SNB=1234567, SSTY=AOCD, OPT=ACTMODE-1&PREKEYP-4;
The AOC-D service is now activated automatically on all calls and the information is sent using
Keypad protocol. Furthermore, the information is presented in currency units and sent in Display
information elements. For more options see AI ISDN-E User Advice of Charge, During the Call.
For more options regarding defining of activation and presentation mode for AOC-E or AOC-S see
AI ISDN-E User, Advice of Charge, at the End of the Call or AI ISDN-E User, Advice of Charge at
Call Set-up.
2.7.6.5 Definition of AoC Data for a Call Related Supplementary Service
See note in chapter 'Definition of AoC data for a Subscriber' above.
2.7.7 Output of the AoC Data
2.7.7.1 AoC for Calls
The AOC-D and AOC-E information sent to the subscriber at call release can be output in the call
data record used to charge the originating ISDN call component or call forwarding ISDN call
component. The information is output only for informative purposes and not for charging
invocation of the Supplementary Service AoC.
For charging purposes the AoC data can be output as an Event Module "ISDN SS Invocation
Event Module" in the call data record used to charge the originating ISDN call component or call
forwarding ISDN call component. There will be one module of AoC data for each time the AoC
supplementary service is activated by the subscriber or automatically by configuration.
2.8 ISDN-E IN Calls

In case of ISDN-E originating call and triggering of IN by dialling an IN number it is possible to
output IN charging data in a composite call data record together with the ISDN Originating Call
component.
If an ISDN-E subscriber has Call Forwarding to an IN number, IN charging data can be output in
a composite call data record together with the ISDN Call Forwarding Call component.
Administration and charging of ISDN-E IN is similar to administration and charging of mobile IN.
See the 'User Guide for Charging of Mobile IN and CAMEL Calls' reference [2, for more
information related to this topic.
2.9 Initiation of Call Data Output

Data related to ISDN-E calls and supplementary services can be collected within the exchange
and output by the function Toll Ticketing.
Initiation of output of collected call data is initiated when a chargeable traffic activity is ended
(for instance, call is disconnected) or when a limit for partial output is reached.
For long duration calls, output of data for the call can be split into several registrations. The time
interval between these partial outputs can be chosen by means of exchange parameters.
The time interval between partial outputs is measured from the time when the previous output
was made:
-
the minimum time interval between partial outputs is 2 hours.
-
the maximum time interval between partial outputs is 10 hours.
-
the accuracy for first partial output is 0-10 minutes.
Partial output can also be triggered by thresholds specified for each flexible counters. The
thresholds are specified with exchange parameters.
It is also possible to trigger partial output when a predefined limit of call related supplementary
services is reached.
Partial output can not be triggered before the active phase.
When a call is disconnected, or at partial output, the charging data is sent to FOAM for output.
For output of the call data record, please refer to the 'User Guide for Output of Call Data'
reference [1.
3 Congestion Handling

Charging data is collected during the call in logs in the block CHVIEW.
For each call module, one call individual (SAE 1097) in block IUCCON is reserved. This call
individual coordinates the charging data collection for the duration of the call. At the same time
when the call individual is seized, a view individual (SAE 446) is reserved in block CHVIEW. This
individual coordinates the storing of charging data in the logs. The view consists of logs. A log is
divided into two components, log header individual (SAE 601) and log part individual (SAE 600).
The charging data is stored in the log parts. The log header is needed to coordinate the data
structure for the log parts.
When one log part is full a new log part is reserved.
At partial output the data structure in CHVIEW is copied to a new data structure, and the copied
data structure is sent to output.
When performing charging for supplementary services, an individual (SAE 500) in block IUCSIC
is reserved. This individual coordinates and collects data related to the usage of a supplementary
service. View and log data is handled in the same way as when performing charging for a call.
IUCCON CHVIEW FOAM
SAE 1097 SAE 446 SAE 601
/-----\ /-----\ /------\ /------\ /------\ /-----\

|Call | |View | |Log | |Log | |Log | |CDF |
|ind. +----+ind. +----+Header+-+Header+-+Header| |ind. |
| | | | |ind. | |ind. | |ind. | | |
\-----/ \-----/ \------/ \------/ \------/ \-----/
| | | |
SAE 600 | |
| | | |
/--+---\ /--+---\ /--+---\
| |Log | |Log | |Log |
|Part | |Part | |Part |
| |ind. | |ind. | |ind. |
\------/ \------/ \------/

| . . .
. . .
| . . .
/--+---\ /--+---\ /--+---\
| |Log | |Log | |Log |
|Part | |Part | |Part |
| |ind. | |ind. | |ind. |
\------/ \------/ \------/
IUCSIC |
SAE 500 SAE 446 SAE 601

|
/-----\ /--+--\ /------\
|Supp.| |View | |Log |
|Serv.+----+ind. +----+Header|
|ind. | | | |ind. |
\-----/ \-----/ \------/
|
SAE 600
|
/--+---\
|Log |
|Part |
|ind. |
\------/
FIGURE 6: Size alteration
3.2 Congestion Handling

When the connection to the output device is down the call data is first buffered in FOAM. In case
of congestion in FOAM see 'User Guide for Output of Call Data' reference [1.
When there is full congestion in FOAM call data can be buffered in CHVIEW data structure
depending on exchange parameters in FOAM. See 'User Guide for Output of Call Data' reference
[1 for more information.
When there is full congestion in FOAM the charging coordinator can take certain actions at the
setup phase of the call, taking into account that there might still be congestion in the output
when the call data for this call is to be output. This is called early congestion check. The
exchange parameter ACTPREDCONGTTFEP decides whether to continue the call without charging,
disconnect the call or continue as normal.
When there is full congestion in the CHVIEW data structure it is not possible to store charging
data for the call. Then the exchange parameter CHCONGACTION in the block IUCCON decides
whether to disconnect the call or proceed without charging. In case of full congestion in the call
individuals the alarm 'SOFTWARE FILE CONGESTION' is generated.
In case of full congestion in CHVIEW when performing charging for a supplementary service, it is
up to the supplementary service to decide whether the procedure should be performed or not.
4 Miscellaneous
4.1.1 Global Size Alteration Events
4.1.1.1 SAE 040
Number of Tariff Classes
Value Range: 0-511
An individual is seized when a TC is specified in the operating or not operating area.
4.1.1.2 SAE 041
Number of Tariffs
Value Range: 0-2048
An individual is seized when a tariff is specified in the operating or not operating area.
4.1.1.3 SAE 446
Number of views.
Value Range: 0-1048474
An individual is seized when a call or a supplementary service takes place. The individual will be
released when the call/service is finished. Several logs can be connected to a charging view, for
the collection of data. A log consists of a log header, and one or more log parts.
4.1.1.4 SAE 454
Number of subscription records
4.1.1.5 SAE 1097
Number of individuals for Supplementary Service Control originating. One traffic individual is
seized for each originating call disconnected.
4.1.1.6 SAE 1098
Number of individuals for ncreases or decreases the number of Supplementary Service Control
terminating individuals. One traffic individual is seized for each terminating call. It is released
when the call is disconnected.
4.1.2 Local Size Alteration Events
4.1.2.1 IUAOCD
-
SAE 500
Size Alteration Event SAE=500, Number of AOC-D traffic process individuals. See Note
below.
Value range: 0 - 4G (Note) The number of possible records in this file is dependent on the
pointer size of the APZ used. The stated number is valid for a 32-bit APZ. If a 16-bit APZ is
used, the maximum size is 65534.
4.1.2.2 IUAOCE
-
SAE 500
Size Alteration Event SAE=500, Number of AOC-E traffic process individuals. See Note
below.
4.1.2.3 IUAOCS
-
SAE 500
Size Alteration Event SAE=500, Number of AOC-S process individuals. See Note below.
4.1.2.4 IUCSIC
-
SAE 500
Size Alteration Event SAE=500, number of individuals for charging of supplementary
services.
Value range: 0 - 1048575
4.1.2.5 IUCBCA
-
SAE 520
Size Alteration Event SAE=520, number of records for Charging Case.
Value Range: 0-4096
An individual is seized when a branching condition based an a Charging Case that has not
been used before is defined.
-
SAE 521
Size Alteration Event SAE=521, number of records for Basic Service Charging Code.
Value Range: 0-8192
An individual is seized when a branching condition based on BSCC is defined.
-
SAE 522
Size Alteration Event SAE=522, number of records for Tariff Group.
An individual is seized when a branching condition based on TGR is defined.
-
SAE 523
Size Alteration Event SAE=523, number of records for Charging Origin.
An individual is seized when a branching condition based on CO is defined.
-
SAE 524
Size Alteration Event SAE=524, number of records for Called Subscriber's Charging
Category.
An individual is seized when a branching condition based on CHT is defined.
-
SAE 528
Size Alteration Event SAE=528, number of records for Calling Party Category.
An individual is seized when a branching condition based on CPC is defined.
-
SAE 533
Size Alteration Event SAE=533, number of records for Call Indicator.
An individual is seized when a branching condition based on CI is defined.
4.1.2.6 IUCCPA
-
SAE 529
Size Alteration Event SAE=529, number of records for charging programs.
Value Range: 1-4097
An individual is seized when a charging program is defined.
4.1.2.7 IUCSCA
SAE 522
Size Alteration Event SAE=522, number of records for Tariff Group.
An individual is seized when a branching condition based on TGR is defined.
-
SAE 523
Size Alteration Event SAE=523, number of records for Charging Origin.
An individual is seized when a branching condition based on CO is defined.
-
SAE 525
Size Alteration Event SAE=525, number of records for Supplementary Service Indicator.
Value Range: 0-2
An individual is seized when a branching condition based on SSI is defined.
-
SAE 526
Size Alteration Event SAE=526, number of records for Supplementary Service Procedure.
Value Range: 0-512
An individual is seized when a branching condition based on SSP is defined.
-
SAE 527
Size Alteration Event SAE=527, number of records for Result of Supplementary Service
Procedure.
An individual is seized when a branching condition based on RSSP is defined.
-
SAE 528
Size Alteration Event SAE=528, number of records for Calling Party Category.
An individual is seized when a branching condition based on CPC is defined.
4.1.2.8 IUCSPA
-
SAE 530
Size Alteration Event SAE=530, number of records for service charging programs.
Value Range: 0-4097
An individual is seized when a service charging program is defined.
4.1.2.9 CHVIEW
-
SAE 600
Size Alteration Event SAE=600, number of log parts.
A log part is seized when a log header is seized and when a log part is completely filled
with data. The log part is released when the view is released. For an ISDN-E call, 4 log
parts are usually seized. For a supplementary service, 1 log part is usually seized.
-
SAE 601
Size Alteration Event SAE=601, number of log headers.
A log header is seized when a view is seized and when a user indicates that it wants to
write data into a log. The log header is released when the view is released. Three log
headers are normally seized during an ISDN-E call and one log header is seized for a
supplementary service.
4.2 ISDN-E Charging Exchange Parameters
4.2.1 IUAOCD
-
CURRENCY_INFO_ON_TT_RECORD
The parameter specifies if the AOCD information sent to the subscriber at end of the call is
to be registered on TT record.
Value Range: 0-1

Guiding value: 0
0 = Not to be registered on TT record
1 = To be registered on TT record
-
OUTPUT_TIME_INTERVAL_FUNCTIONAL
The parameter specifies the sending rate of AOCD charging information to the subscriber.
Value Range: 0-60

Guiding value: 30
0 = Send immediately upon reception of charging units
1 - 60 = Minimum time between sending
-
INCLUDE_FLEXIBLE_COUNTERx
The parameters INCLUDE_FLEXIBLE_COUNTERx (x=1-8) specifies how the corresponding
flexible counter is to be included into AOCD information sent to the subscriber.
Value Range: 0-2

Guiding value: 2
0 = Flexible counter not included
1 = Flexible counter included in total only
2 = Flexible counter included in sub-totals and total
-
TYPE_OF_CHARGING_UNIT_INDICATOR
The parameter specifies if the sub-unit 'Type of Charging Unit' is to be included into AOCD
information sent to the subscriber.
Value Range: 0-1

Guiding value: 1
0 = Sub-unit not to be included
1 = Sub-unit to be included
4.2.2 IUAOCE
-
CURRENCY_INFO_ON_TT_RECORD
The parameter specifies if the AOCE information sent to the subscriber at end of the call is
to be registered on TT record.
Value Range: 0-1

Guiding value: 0
0 = Not to be registered on TT record
1 = To be registered on TT record
-
INCLUDE_FLEXIBLE_COUNTERx
The parameters INCLUDE_FLEXIBLE_COUNTERx (x=1-8) specifies if the corresponding
flexible counter is to be included into AOCE information sent to the subscriber.
Value Range: 0-1

Guiding value: 1
0 = Flexible counter not included
1 = Flexible counter included in total
-
TYPE_OF_CHARGING_UNIT_INDICATOR
The parameter specifies if the sub-unit 'Type of Charging Unit' is to be included into AOCE
information sent to the subscriber.
Value Range: 0-1

Guiding value: 1
0 = Sub-unit not to be included
1 = Sub-unit to be included
4.2.3 IUAOCS
-
SEND_CALL_ATTEMPT
The parameter specifies if the charged item 'call attempt' is to be included into AOCS
information.
Value Range: 0-1

Guiding value: 1
0 = Do not send charged item call attempt
1 = Send charged item call attempt
4.2.4 IUCACH
-
COMPRESSEDCPCxxx
The parameters COMPRESSEDCPCxxx (xxx=0-255) specifies the Type of Called Subscriber
value to which a CPC value will be mapped. xxx specifies the CPC value in question.
Value Range: 0-15
4.2.5 IUCCON
-
AOCCHUNITBCALL
The parameter indicates the external charging unit type for charging units for a basic call.
Value Range: 1-10AOCCHUNITOPSS

Guiding value: This parameter shall be set according to the external charging unit type.
-
AOCCHUNITOPSS
The parameter indicates the external charging unit type for charging units for operating of
supplementary services.
Value Range: 1-10

-
AOCCHUNITFLEXCOUNTx
The parameter AOCCHUNITFLEXCOUNTx (x=1-8) indicates the external charging unit type
for charging units for the corresponding flexible counter.
Value Range: 1-10

-
AOCINCSERV
The parameter indicates whether AOC-S information should include the charging
information for operation of supplementary services.
Value Range: 0-1

Guiding value: 1
0 = SS charging information will not be included
1 = SS charging information will be included
-
DURATIONLIMIT
The parameter specifies the time in hours between partial outputs of call data records.
Value Range: 2-16

Guiding value: 2
-
CHARGING_ANALYSIS_LOCATION
The parameter indicates if centralized charging analysis will be performed or not.
Value Range: 0-1

Guiding value: 1
0 = Local charging analysis will be performed
1 = Centralized charging analysis will be performed
Note: The charging program must be set locally in IUSAM for ISDN-E calls
(CHARGING_ANALYSIS_LOCATION = 0).
-
CHFAULTACTION
The parameter specifies the action to be taken when charging analysis, storing of a FEP or
writing of data fails.
Value Range: 0-1

Guiding value: 0
0 = Continue the call free of charge
1 = Disconnect the call
-
CHCONGACTION
The parameter specifies the action to be taken when charging view can not be seized.
Value Range: 0-2

Guiding value: 0
0 = Continue the call free of charge
2 = EOS analysis decides how to proceed
-
ACTPREDCONGTTFEP
The parameter specifies the action in case of predefined congestion in the TT function.
Value Range: 0-4

Guiding value: 3
1,2 = Continue the call without any outputs
3 = Continue the call without outputs with predefined congestion
4 = Continue the call with TT output
-
FLEXCNT1LIMIT
The parameter specifies the threshold limit for partial output for flexible counter 1.

Guiding value: 0
0 = No threshold limit specified
1 - 65535 = Specified threshold limit
-
FLEXCNT2LIMIT

Guiding value: 0
-
FLEXCNT3LIMIT

Guiding value: 0

-
FLEXCNT4LIMIT

Guiding value: 0
-
FLEXCNT5LIMIT

Guiding value: 0
-
FLEXCNT6LIMIT

Guiding value: 0
-
FLEXCNT7LIMIT

Guiding value: 0
-
FLEXCNT8LIMIT

Guiding value: 0
4.2.6 IUCITM
4.2.6.1 Advice of Charge
-
AOCSINCUUS
Indicates whether charging information about transfered UUS information elements should
be included by AOC-S.
Value Range: 0-1

Guiding value: 1
0 = Charging information will not be included
1 = Charging information will be included
4.2.6.2 Call Attempt Charging, Type of Called Subscriber
Value Range: 0-1

0 = No call attempt analysis
1 = Call attempt analysis
-
CALLEDSUBSCRIBERISDN
The parameter indicates if the Call Attempt analysis shall be performed if the called
subscriber type is ISDN.
Guiding value: 1
-
CALLEDSUBSCRIBERPSTN
subscriber type is PSTN.
Guiding value: 0
-
CALLEDSUBSCRIBERUNKNOWN
subscriber type is unknown.
Guiding value: 0
4.2.6.3 Call Attempt Charging, Type of Signaling
Value Range: 0-1

-
SIGNALLINGTYPEISUP
The parameter indicates if the Call Attempt analysis shall be performed if the type of
signaling is ISUP all the way.
Guiding value: 1
-
SIGNALLINGTYPELOCAL
signaling is local.
Guiding value: 0
-
SIGNALLINGTYPENOTISUP
signaling is not ISUP all the way.
Guiding value: 0
-
SIGNALLINGTYPEUNKNOWN
signaling is unknown.
Guiding value: 0
4.2.6.4 Call Attempt Charging, State Mapping Table
The parameters indicate which internal AXE Call Attempt state is to be mapped onto a user
defined Call Attempt state. This table is only used for output purposes and is intended for
operators who are only interested in a subset of call attempt states.
Value Range: 0-7
0 = Initial
Start of call setup, ie. the call request is not sent
yet.
1 = Call Sent
The call request has been sent, but no acknowledgment
has been received yet.
2 = Call Rejected
The call is rejected and is not offered to the called
subscriber, e.g. due to congestion in the public
network.
3 = Call Offered
The call is offered to the called subscriber but no
response is received yet, ie. an ACM is received without
backward information.
4 = No Response
A call has been offered but the call is rejected or no
response has been received and a time out has occurred.
In case of a PABX supporting DDI the state is reached
when a call was sent but no ACM is received.
5 = Alerting
The call has been accepted by the called subscriber and
alerting has started.
6 = Unknown Call
The progress of the call setup can't be determined since
the information received from the signaling system is
insufficient.
7 = Active
The call has reached active phase.
-
MAPPINGSTATE0
Guiding value: 0
-
MAPPINGSTATE1
Guiding value: 1
-
MAPPINGSTATE2
Guiding value: 2
-
MAPPINGSTATE3
Guiding value: 3
-
MAPPINGSTATE4
Guiding value: 4
-
MAPPINGSTATE5
Guiding value: 5
-
MAPPINGSTATE6
Guiding value: 6
-
MAPPINGSTATE7
Guiding value: 7
4.2.6.5 Call Attempt Charging, State Analysis Table
The parameters indicate the Call Attempt Charging State Analysis result for call termination in
each of the internal call states.
Value Range: 0-3
0 = No charging in this state

1 = Always charge in this state
2 = Charging in this state is dependent on the type of
release (that is the release analysis is to be
performed).
3 = Charging in this state is dependent on the reason for
call clearing (that is the cause/location analysis is
to be performed).
-
RESULTSTATEANALYSIS0
The parameter specifies the action to be taken for state 'Initial'.
Guiding value: 0
-
The parameter specifies the action to be taken for state 'Call Sent'.
Guiding value: 0
-
The parameter specifies the action to be taken for state 'Call Rejected'.
Guiding value: 2
-
The parameter specifies the action to be taken for state 'Call Offered'.
Guiding value: 3
-
The parameter specifies the action to be taken for state 'No Response'.
Guiding value: 3
-
The parameter specifies the action to be taken for state 'Alerting'.
Guiding value: 1
-
The parameter specifies the action to be taken for state 'Unknown Call'.
Guiding value: 1
4.2.6.6 Call Attempt Charging, Release Analysis Table
Release analysis is performed when, for certain call states, the Call Attempt Criteria is dependent
on the type of release. For each type of call release, a result is set which specifies whether the
Call Attempt Criteria has been fulfilled.
Value Range: 0-1
0 = Cause/Location Call Attempt Criteria table specifies

whether Call Attempt Criteria is fulfilled.
1 = Call Attempt Criteria fulfilled.
-
APARTYRELEASE
The parameter indicates the analysis result for A-party release.
Guiding value: 1
-
BPARTYRELEASE
The parameter indicates the analysis result for B-party release.
Guiding value: 1
-
OTHERPARTYRELEASE
The parameter indicates the analysis result for other (network) release.
Guiding value: 0
4.2.6.7 Call Attempt Charging, Cause and Location tables
Two matrices are used in which for each combination of cause and location a result is set. In the
first matrix the result indicates if a release analysis is required or not. When a release analysis is
not required, the result in the second matrix specifies whether the call attempt criteria has been
fulfilled.
Cause/Location Release Analysis Required Table (1st matrix)

-----------------------------------------------------------
Value range: H'0 - H'FFFF
CAUSELOCATIONRAR000
CAUSELOCATIONRAR001
CAUSELOCATIONRAR002
.
.
CAUSELOCATIONRAR255
Cause/Location Call Attempt criteria table (2nd matrix)

-------------------------------------------------------
Value range: H'0 - H'FFFF
CAUSELOCATIONCAC000
CAUSELOCATIONCAC001
CAUSELOCATIONCAC002
.
.
CAUSELOCATIONCAC255
Description of parameters (1st matrix)

--------------------------------------
Value of the (bit) location.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 I
Value of the 1 I
cause. 3 --------------x
4
.
.
.
255
Format : CAUSELOCATIONRARXXX, where XXX = cause.
For each 'CAUSELOCATIONRARXXX' hexadecimal value, there is a

corresponding 16 bit binary value (where each bit represents
one of the 16 possible locations) and each bit can be set in
the following way :
0 = 2nd matrix specifies whether call attempt criteria fulfilled.

1 = Release Analysis required.
Description of parameters (2nd matrix)

-------------------------------------------------------
Value of the (bit) location.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 I
Value of the 1 I
cause. 3 --------------X
4
.
.
.
255
Format : CAUSELOCATIONCACXXX, where XXX = cause.
For each 'CAUSELOCATIONCACXXX' hexadecimal value, there is a

corresponding 16 bit binary value (where each bit represents
one of the 16 possible locations) and each bit can be set in
the following way :
0 = Call Attempt criteria not fulfilled.

1 = Call Attempt criteria fulfilled.
4.2.6.8 Other Call Attempt Charging parameters
-
CACFORWARDEDCALL
The parameter indicates if the Call Attempt analysis shall be performed for forwarded calls.
Value Range: 0-1


Guiding value: 0
-
CALLATTEMPTFUNCTION
The parameter indicates if the Call Attempt Charging function is active.
Value Range: 0-1

0 = Not active
1 = Active for originating ISDN calls
Guiding value: 1
-
DEFAULTCACCAUSECODE
The parameter indicates the default cause code value to be used for Call Attempt Charging
in case the information case code is not active or the mapping table can not be read during
restart due to congestion.
Value Range: 0-255

Guiding value: 31
-
PREVENTTRANSFROMISDN
The parameter indicates if the type of signalling and type of called access should be
considered to be ISUP and ISDN if this was the case at any point during call set-up but
changed later. If the parameter is active counting of information elements will stop if a
transition from ISUP/ISDN to NOT_ISUP/POTS occurs.
Value Range: 0-1

0 = Not active
1 = Active
Guiding value: 0
-
SIMPLECACFUNCTION
The parameter indicates if the simple version of the Call Attempt Charging is used for
originating calls. Successful calls are analyzed.
Value Range: 0-1

0 = Not active
1 = Active for originating ISDN calls
Guiding value: 1
-
SIMPLECACDIVERTED
The parameter indicates if the simple version of the Call Attempt Charging is used for
diverted calls. Successful calls are analyzed.
Value Range: 0-1

0 = Not active
1 = Active for diverted ISDN calls.
Guiding value: 1
4.2.6.9 Counting of transfered information elements (Layer 1 mapping)
The parameters indicates on which flexible counter each transfered information element should
be counted. The values have the following meaning:
Value range: 0, 1, 8- 15
0 Not to be counted.
1 Count collectively (see parameter ALLACCESSDATA).
8 Store information element on flexible counter 1.
-
UUS1SERVICEFW
Specifies a flexible counter for User-to-User Information (UUI) elements sent forward by
Service 1.
Guiding value: 8
-
UUS1SERVICEBW
Specifies a flexible counter for User-to-User Information (UUI) elements sent backward by
Service 1.
Guiding value: 8
-
ATPDATAELEMENTFW
Specifies a flexible counter for ATP data elements in the forward direction.
Guiding value: 11
-
ATPDATAELEMENTBW
Specifies a flexible counter for ATP data elements in the backward direction.
Guiding value: 11
-
ATPOCTETSFW
Specifies a flexible counter for ATP data octets sent in the forward direction.
Guiding value: 11
-
ATPOCTETSBW
Specifies a flexible counter for ATP data octets sent in the backward direction.
Guiding value: 11
-
CALLINGPTYNUM
Specifies a flexible counter for End-to-End access information element 'Calling Party
Number'.
Guiding value: 11
-
SECONDCALLINGPTYNUM
Specifies a flexible counter for End-to-End access information element 'Second Calling
Party Number'.
Guiding value: 11
-
CALLINGPTYSUBADDRESS
Specifies a flexible counter for End-to-End access information element 'Calling Party
Subaddress'.
Guiding value: 11
-
CALLEDPTYSUBADDRESS
Specifies a flexible counter for End-to-End access information element 'Called Party
Subaddress'.
Guiding value: 11
-
HLCOMPATIBILITY
Specifies a flexible counter for End-to-End access information element 'High Layer
Compatibility'.
Guiding value: 11
-
LLCOMPATIBILITYFW
Specifies a flexible counter for End-to-End access information element 'Low Layer
Compatibility' (SETUP) in the forward direction.
Guiding value: 11
-
LLCOMPATIBILITYBW
Specifies a flexible counter for End-to-End access information element 'Low Layer
Compatibility' (SETUP) in the backward direction.
Guiding value: 11
-
CONNECTEDPTYSUBADDRESS
Specifies a flexible counter for End-to-End access information element 'Connected Party
Subaddress'.
Guiding value: 11
-
BEARERCAPABILITY
Specifies a flexible counter for End-to-End access information element 'Bearer Capability'.
Guiding value: 11
-
PROGRESSINDICATORFW
Specifies a flexible counter for End-to-End access information element 'Progress Indicator'
in the forward direction.
Guiding value: 11
-
PROGRESSINDICATORBW
Specifies a flexible counter for End-to-End access information element 'Progress Indicator'
in the backward direction.
Guiding value: 11
-
USERPROVIDEDCAUSEFW
Specifies a flexible counter for End-to-End access information element 'User Provided
Cause Internal' in the forward direction.
Guiding value: 11
-
USERPROVIDEDCAUSEBW
Specifies a flexible counter for End-to-End access information element 'User Provided
Cause Internal' in the backward direction.
Guiding value: 11
-
NETWORKPROVIDEDCAUSEFW
Specifies a flexible counter for End-to-End access information element 'Network Provided
Cause' in the forward direction.
Guiding value: 11
-
NETWORKPROVIDEDCAUSEBW
Specifies a flexible counter for End-to-End access information element 'Network Provided
Cause' in the backward direction.

Guiding value: 11
-
CALLATTEMPTINDICATION
Specifies a flexible counter to step in case the call attempt is chargeable.
Guiding value: 10
-
ALLACCESSDATA
The parameter indicates if collective counting is active and on which flexible counter the
elements should be counted.
Guiding value: 0
4.2.6.10 Other parameters related to counting of transfered information elements
-
CHARGINGREDIRECT
The parameter specifies if counting of information elements is allowed for a redirected or
deflected leg of the call.
Value range: 0-1
0 = Redirected leg is not to be counted.
1 = Redirected leg is to be counted.
Guiding value: 0
4.2.7 IUCSIC
-
ACTPREDCONGTTFEP
The parameter specifies the action in case of predefined congestion for toll ticketing FEP.
Value Range: 0-15

0 = Charging not possible
1 = Charging not possible
2 = Continue with charging but without output
3 = Continue with charging but without output for FEPs with predefined congestion
15 = Continue with charging and with output for FEPs with predefined congestion
Guiding value: 3
4.2.8 IUCHDB
-
DEFAULT_CO
The parameter specifies the default value given to the CO property when a subscription is
created.
Value Range: 0-127

Guiding value: 0
-
DEFAULT_TGR
The parameter specifies the default value given to the TGR property when a subscription is
created.
Value Range: 0-63

Guiding value: 0
4.2.9 IUDB
-
CHT_ARN_VALUE
The parameter specifies the default value given to the CHT property when an Access
Related subscription is created.
Value Range: 0-15

Guiding value: 0
-
CHT_GRN_VALUE
The parameter specifies the default value given to the CHT property when a Group Number
Value Range: 0-15

Guiding value: 0
-
CHVALNM_ARN_VALUE
The parameter specifies the default value given to the CHVALNM property when an Access
Value Range: 0-1

0 = Always charge DCN
1 = Charge validated number
Guiding value: 1
-
CHVALNM_GRN_VALUE
The parameter specifies the default value given to the CHVALNM property when a Group
Number Related subscription is created.
Value Range: 0-1

0 = Always charge DCN
1 = Charge validated number
Guiding value: 1
-
CPC_ARN_VALUE
The parameter specifies the default value given to the CPC property when an Access
Value Range: 0-255

Guiding value: 10
-
CPC_GRN_VALUE
The parameter specifies the default value given to the CPC property when a Group Number
Value Range: 0-255

Guiding value: 10
-
OBA_ARN_VALUE
The parameter specifies the default value given to the OBA property when an Access
Value Range: 0-255

Guiding value: 0
-
OBA_GRN_VALUE
The parameter specifies the default value given to the OBA property when a Group Number
Value Range: 0-255

Guiding value: 0
4.2.10 IUUUS
-
CHARGING_LENGTH
The parameter specifies the minimum chargeable length of a UUI element.
Value Range: 0-255

Guiding value: 1
5 References
1
1553-APR 101 14/7 Uen
User guide for output of call data
2
8/1553-APX 101 01/3 Uen
User Guide for Charging of Mobile IN and CAMEL Calls in GMSC/MSC/SSF/gsmSSF Node,
GSM
3
10/155 18-APR 101 20/3 Uen
Traffic Activity Code, ISDN-E Subscribers
4
9/155 18-APR 101 20/3 Uen
Subscriber Categories, ISDN-E

User Guide For Charging of ISDN-E Calls

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

User Guide For Charging of ISDN-E Calls

Загружено:

Авторское право:

Доступные форматы

USER GUIDE FOR CHARGING OF ISDN-E CALLS AND SUPPLEMENTARY SER...

DIRECTIONS FOR USE 7/1553-APX 101 01/4 Uen C

Telefonaktiebolaget LM Ericsson 2003

USER GUIDE FOR CHARGING OF ISDN-E CALLS AND

2 ISDN-E Charging Functionalities

1.2 Revision Information

Access Related Individual Number (AIN)

1.5 Introduction to ISDN-E Charging

1.5.1 Call Data Records

1.5.2 Event Module

1.5.3 Call Types

2 ISDN-E Charging Functionalities

2.2 Subscriber Properties Influencing Charging of ISDN-E Calls and

Subscriber properties influencing charging can be assigned to ISDN-E subscriptions. The

2.2.1.1 Called Subscriber Charging Type (CHT)

2.2.1.2 Charging of validated number (CHVALNM)

2.2.1.3 Origin for Charging (CO)

2.2.1.4 Calling Party Category (CPC)

2.2.1.5 Origin for B-number analysis (OBA)

2.2.1.6 Tariff Group (TGR)

2.2.2 Commands for Subscriber Property Handling

- IUSCC, ISDN-E End User, End User Service, Change

- Subscriber Data: ISDN-E End User Services

- ISDN-E, Service Data for Subscriber, Change

- Subscriber Categories, ISDN-E

The subscriber number 1234567 is given the value 10 to the

2.3 Basic Call Charging

2.3.1 Basic Service Analysis

2.3.1.2 Commands for Basic Service Analysis Administration

- IXBAE, ISDN-E Exchange Data, Basic Service Analysis,

- Traffic Data: Basic Service Analysis ISDN-E

- ISDN-E, Basic Service, Analysis Data, Change

2.3.1.3 Example 1 (Telephony Calls)

Basic Service Characteristics are defined for a telephony

Basic Service Analysis data for analyzing the received

2.3.1.4 Example 2 (Data Transmission)

Basic Service Characteristics are defined for a tele-Tex

is 4, ISUP is preferred, the transmission medium requirement

Basic Service Analysis data for analyzing the received

2.3.2 B-Number Analysis

2.3.2.2 Commands for Administering B-Number Analysis Data

- ANBAI, Analysis of B-Number, Activation, Initiate

- Traffic Data: B-Number Analysis

- B-Number Analysis Data, Change

For numbers with B-number origin 0, numbering plan 1

For numbers with B-number origin 10 within the number

2.3.3 ISDN-E Basic Call Charging Analysis

The branching condition analysis analyzes the following input values:

- ICAPE, ISDN-E Charging, Call Charging Program

- Traffic Data: Call Charging Analysis Program ISDN-E,

- ISDN-E, Call Charging Program, Change

The not operating area is cleared

New charging programs are specified in the not operating

The new charging programs are activated

Charging Case data is cleared in the not operating area.

A charging case tree without branching conditions is

A charging case tree including branching conditions is

A charging case tree is specified for calls where a

The new Charging Case trees are activated

/--0 /---0 /---0 /----0---- CHP=3

FIGURE 1: Branching Condition Tree

2.4 Call Attempt Charging

2.4.1 Call Attempt Analysis