User Guide For Output of Call Data: 1 General

USER GUIDE FOR OUTPUT OF CALL DATA Page 1 of 28
DIRECTIONS FOR USE 1553-APR 101 14/22 Uen A
Copyright Ericsson GmbH 2010 - All Rights Reserved
USER GUIDE FOR OUTPUT OF CALL DATA
Contents
1 General
1.1 Revision Information
1.2 Introduction
1.3 Concepts
2 FOAM Functionalities
2.1 General
2.2 Output of Call Data Records
2.3 Common Charging Output (CCO)
2.4 IOG Handling
2.5 Adjunct Processor Handling
2.6 Source Filtering
2.7 Automatic Charging Buffer Flushing in Traffic Isolation
3 References
http://cpistore.internal.ericsson.com/alexserv?AC=LINK&ID=11423&FN=1553-APR101... 10/14/2012
1 General
1.1 Revision Information

This version is based on 1553-APR 101 14/14 rev A.
The reason for this revision is the improvement on Blade Cluster System "Automatic Charging
Buffer Flushing in Traffic Isolation".
1.2 Introduction
This document gives a general overview how the formatting and output of Call Data Records is
handled.
The command examples in this document are simplified and might exclude necessary non-charging
related parameters.
The document does not replace any other operation and maintenance documents.
1.3 Concepts
1.3.1 Terminology
ADJUNCT PROCESSOR (AP) is an AXE external processor with a formatter, to which call data
can be transferred instead of IOG.
-
ASN.1 is a specification by ITU-T/ISO for defining application layer protocol syntaxes and
notation for abstract syntax definition. There are two components in ASN.1: a notation and a
set of encoding rules (ASN.1 Basic Encoding Rules).
-
AXE PARAMETER is a parameter with a definition and value that is common to one or more
central software units. The value of some classes of AXE parameters may be changed by
means of a command.
-
AXE PARAMETER SET is a group of AXE Parameters having the same scope. For example, a
set of parameters may be defined for a function, another for a set of parts, and another for
an application system.
-
CALL DATA RECORD (CDR) contains the collection of data that concerns a call, a short
message or a call independent supplementary service subscriber procedure as well as data
about any possible, associated event which occurs during the call. A Call Data Record
consists of a call module and may have one or more event modules.
-
CALL MODULE is a collection of data related to a call/short message service/call independent
supplementary service subscriber procedure.
-
EVENT MODULE is data related to an event which is independent of time duration.

-
EXTERNAL MEDIUM is a storage device external to the AXE, for example, a magnetic tape or
an optical disk.
-
IMMEDIATE CALL ITEMIZATION (ICI) is a charging method which provides detailed outputs
for all or certain types of calls and other chargeable events available immediately after
chargeable traffic activity has ended or after partial output, as defined in the charging
analysis.
-
PARTIAL OUTPUT refers to the periodic output of Call Data Records, used by all specified
charging output types. Reason for a partial output can be:
Long call duration. The partial output occurs at regular

intervals during a call, where the interval is set by
exchange parameters.
System limits. For example partial output is triggered

when a specified number of registered events have occurred.
Real time charging purposes.
TOLL TICKETING (TT) is a charging method which provides detailed outputs for all or
certain types of calls and other chargeable events, as defined in the charging analysis.
1.3.2 Abbreviations
ALI Alarm Interface

AP Adjunct Processor
ANSI American National Standards Institute
ASN.1
Abstract Syntax Notation One
AT Alphanumerical Terminal
BER Basic Encoding Rules
CCO Common Charging Output
CDF Call Data File
CDMA
Code Division Multiple Access
CHFIM
CHarging Filter Module
CHOC
CHarging Output Commands
CHOF
CHarging Output Formatting
CHOOB
CHarging Object Owning Block
CHOP
CHarging Output to Adjunct Processor
CHSFILT
CHarging Source FILTering
CP Central Processor
DCS Data Communication Subsystem
DFO Direct File Output

DL Data Link
EOS End-of-Selection
FD Flexible Disk
FMS File Management Subsystem
FOAM
Formatting and Output Application Module
FOS Formatting Output System
FPU File Process Utility
HD Hard Disk
ICB Incoming Calls Barred
ICI Immediate Call Itemization
IOG Input/Output Group
ISDN Integrated Services Digital Network
ISO International Standardisation Organisation
ITU International Telecommunication Union
MC Message Centre
MCS Man-Machine Communication Subsystem
MS Mobile Station
MSC Mobile Switching Centre
MT Magnetic Tape
PBC Periodic Buffer Control
RDT Reliable Data Transfer
RMP Resource Module Platform
SAE Size Alteration Event
SP Support Processor
SPS Support Processor Subsystem
TT Toll Ticketing
UE
User Equipment
WCDMA
Wideband Code Division Multiple Access
2 FOAM Functionalities
2.1 General
/---------------------------------------------\
- RMP -
- -
|---------------------------------------------/
-
/-----------------------+---------------------\
- FOAM -
- /---------------\ /-----------\ -
- - Common - - Source - -
- - Charging - - Filtering - -
- - Output - - - -
- |---------------/ |-----------/ -
|---------------------------------------------/
- -
/------+--------\ /----+-------\
- File handling - - Adjunct -
- IOG - - Processor -
|---------------/ |------------/
FIGURE 1: Charging Related Functionalities
The Formatting and Output Application Module (FOAM) is part of Application Module based AXE.
The FOAM contains two functions Common Charging Output (CCO) and Source Filtering. The CCO
provides the administration with the means to output the charging data (Call Data) to either
Input/Output Group (IOG) or Adjunct Processor (AP). In addition, Source Filtering provides the
administration with the possibility to select the data to be output for call by using the source
filtering information.
CHOC
CHarging Output Commands is the command handling block.
CHOD
CHarging Output Distribution is the output interface block between FOAM and FMS.
CHOF
CHarging Output Formatting is the block that handles charging output in ASN.1 format to
IOG.
CHOP
CHarging Output Adjunct Processor is the block that handles charging output in ASN.1
format to AP.
CHSFILT
CHarging Source FILTering block processes changes in the output parameters for CHFIM
blocks.
CHFIM
CHarging Filter Module is the block that contains Source Filtering information.
CHOOB
CHarging Object Owning Block is the object handling block.
2.2 Output of Call Data Records
2.2.1 Output Functions
TOLL TICKETING (TT)
Data is collected for all calls which according to the charging analysis shall be charged in
this way. The data from a call is output when the call is disconnected or when the limit for
partial output is reached. The limit for partial output can be, for example, call duration or
number of call related events.
The Toll Ticketing functionality outputs data into a detailed output record (Call Data Record).
The Call Data Record can consist of a Call Module and possible Call Related Event Module(s).
In case of IOG interface the TT Call Data Record is sent to the File Management Subsystem
to be stored on hard disk. The File Management Subsystem stores the output in files which
can consist of a number of subfiles.
In case of Adjunct Processor interface the Call Data Record is sent to Adjunct Processor to be
stored and further processed there. Application dependent Formatter in Adjunct Processor
makes different types of output for the function.
IMMEDIATE CALL ITEMIZATION (ICI)
The purpose of the functionality Immediate Call Itemization is to make available detailed call
data immediately after chargeable traffic activity has ended or after partial output. Data is
collected for all chargeable traffic activities for which ICI is applied according to the
charging analysis. Immediate Call Itemization can be performed for both the A- and the B-
subscriber, providing the criteria for the service are fulfilled (see chapter Immediate Call
Itemization for Calling/Called Subscribers).
The ICI functionality outputs data into a detailed output record (Call Data Record). The Call
Data Record can consist of a Call Module and possible Call Related Event Module(s).
In case of IOG interface the ICI Call Data Record can be sent to the File Management
Subsystem to be stored on hard disk or sent to the destination by using Direct File Output
function.
In case of Adjunct Processor interface the Call Data Record is sent to Adjunct Processor to be
stored and further processed there. Application dependent Formatter in Adjunct Processor
makes different types of output for the function. In case of Adjunct Processor interface only
an indication of ICI output is made to make it possible to separate ICI output from TT output
in the post-processing system.
2.2.2 Structure of Call Data Record in ASN.1 Format
2.2.2.1 Structure of Single Call Data Record
The Call Data Record consists of the following parts:
Call Module
Call data related to the call.
Event Module
Call data for call related events.
/-------------------------------------------------\
- Tag = Single Call Data Record -
- -
+-------------------------------------------------+
- Length = Number of octets -
- -
+-------------------------------------------------+
- /-----------------------------------------\ -
- - Tag = Call Module - -
- +-----------------------------------------+ -
- - Length = Number of octets - -
- +-----------------------------------------+ -
- - Tagged Data - -
- - . - -
- - . - -
- - . - -
- |-----------------------------------------/ -
- /-----------------------------------------\ -
- - Tag = Sequence - -
- +-----------------------------------------+ -
- - Length = Indefinite - -
- +-----------------------------------------+ -
- - /-----------------------------------\ - -
- - - Tag = Event Module - - -
- - +-----------------------------------+ - -
- - - Length = Number of octets - - -
- - +-----------------------------------+ - -
- - - Tagged Data - - -
- - - . - - -
- - - . - - -
- - - . - - -
- - |-----------------------------------/ - -
- - . - -
- - . - -
- - . - -
- - /-----------------------------------\ - -
- - - Tag = Event Module - - -
- - +-----------------------------------+ - -
- - - Length = Number of octets - - -
- - +-----------------------------------+ - -
- - - Tagged Data - - -
- - - . - - -
- - - . - - -
- - - . - - -
- - |-----------------------------------/ - -
- +-----------------------------------------+ -
- - End of contents (=Event Modules) - -
- |-----------------------------------------/ -
|-------------------------------------------------/
FIGURE 2: Structure of Single Call Data Record
2.2.2.2 Structure of Composite Call Data Record
It is possible to output a Composite Call Data Record instead of separated Single Call Data Records.
A Composite Call Data Record consists a sequence of Single Call Data Records.
/-------------------------------------------------\
- Tag = Composite Call Data Record -
- -
+-------------------------------------------------+
- Length = Indefinite -
- -
+-------------------------------------------------+
- /-----------------------------------------\ -
- - Tag = Single Call Data Record - -
- +-----------------------------------------+ -
- +-----------------------------------------+ -
- - - -
- - - -
- - - -
- - See figure 2 - -
- - - -
- - - -
- - - -
- - - -
- |-----------------------------------------/ -
- -
- . -
- . -
- . -
- -
- /-----------------------------------------\ -
- - Tag = Single Call Data Record - -
- +-----------------------------------------+ -
- +-----------------------------------------+ -
- - - -
- - - -
- - - -
- - - -
- - See figure 2 - -
- - - -
- - - -
- - - -
- |-----------------------------------------/ -
+-------------------------------------------------+
- End of contents (=Composite Call Data Record) -
|-------------------------------------------------/
FIGURE 3: Structure of Composite Call Data Record
2.3 Common Charging Output (CCO)
2.3.1 Description
The Common Charging Output (CCO) is a part of the Formatting and Output Application Module
(FOAM). CCO provides the administration with the means to output the Call Data (Charging Data)
to either Input/Output Group (IOG) or Adjunct Processor (AP).
The output of Call Data Records can be performed using the output functions Toll Ticketing (TT) or
Immediate Call Itemization (ICI). The output method can be defined in the charging analysis of
the call. The output of call data records can be performed to IOG or Adjunct Processor. Interface
can be selected by command CHOIC.
2.3.2 Functionality of Common Charging Output
The functionality of Common Charging Output can be divided to the different subfunctionalities.
The subfunctionalities are following:
CHarging Output Commands
CHOC is the command receiving/handling block for all commands in FOAM.
CHarging Output Formatting
Output limit check is only performed for ISDN Calls and ISDN Supplementary Service
Procedures. The check determines whether the call reached the limit for output. The output
limit determines the point or state which ISDN Calls and ISDN Supplementary Service
Procedures must at least reach in order for a CDR to be output. Even if the output limit is not
reached, output is performed if conditions for call attempt charging are met.
CHOF fetches call and event data from the RMP. The data is either untagged visible view
data, ASN.1 tagged log data or 'data with unspecified length' (log data). The data is
processed, formatted and stored for output in ASN.1 format.
CHarging Output Distribution
CHOD is used as an interface between FOAM and FMS. The buffers used to transfer charging
data from FOAM to FMS are allocated in CHOD. The data can be output by using low capacity
interface, high capacity interface, or alphanumerical IO-device. The data can be transferred
to an output file, optical disk or IO-device.
CHarging Output Adjunct Processor
CHOP fetches call and event data from the RMP in untagged (visible view data), tagged
(ASN.1) format (log data) or as 'data with unspecified length' (log data). The data is stored
for output to Adjunct Processor in ASN.1 format.
Output limit check is only performed for ISDN Calls and ISDN Supplementary Service
Procedures. The check determines whether the call reached the limit for output. The output
limit determines the point or state which ISDN Calls and ISDN Supplementary Service
Procedures must at least reach in order for a CDR to be output. Even if the output limit is not
reached, output is performed if conditions for call attempt charging are met.
CHOP utilizes the protocol 'Message Protocol to Adjunct Processor' when sending data to
Adjunct Processor.
2.3.3 Commands for Handling of Common Charging Output
- CHOIC, Charging Output Interface, Change

- CHOIP, Charging Output Interface, Print
- CHOLC, Charging Output Limit, Change
- CHOLP, Charging Output Limit, Print
- CHOUC, Charging Output User Function Parameters,
Change
- CHOUP, Charging Output User Function Parameters,
Print
- CHOTC, Charging Output File Attributes, Change
- CHOFI, Charging Output File Open, Initiate
- CHOFE, Charging Output File Open, End
- CHOBI, Charging Output File Block, Initiate
- CHOBE, Charging Output File Block, End
- CHOFP, Charging Output File Status, Print
- CHOTP, Charging Output File Attributes, Print
- CHODP, Charging Output Chargeable Duration Data,
Print
- CHOPI, Charging Output Adjunct Processor
Interface, Initiate
- CHOPE, Charging Output Adjunct Processor
Interface, End
- CHOEC, Charging Output Adjunct Processor
Interface Parameters, Change
- CHOPP, Charging Output Adjunct Processor
Interface, Print
See Adaptation Directions:
- Traffic Data: Common Charging Output

- Traffic Data: Common Charging Output to Adjunct
Processor
See Operational Instructions:
- Common Charging Output Configuration

Data, Change
- Common Charging Output File Output for
IOG11, Initiate
IOG3, Initiate
- Common Charging Output Congestion
- Common Charging Output Error
- Common Charging Output Charging Data Output
Interface from IOG to Adjunct Processor,
Change
- Common Charging Output Charging Data Output
Interface from Adjunct Processor to IOG,
Change
- Common Charging Output Adjunct Processor
Interface Buffer Size, Change
Interface Configuration Data, Change
Interface Congestion
Interface Fault
2.3.4 Call Data Output to IOG
The output of call data record can be performed using the output functions Toll Ticketing (TT)
and/or Immediate Call Itemization (ICI). Each of those functions handles output separately. Call
Data Record can be formatted and transferred to the output medium in IOG.
The data is output in ASN.1 format.
/------------------------------------------------------------\
- RMP -
- -
|------------------------------------------------------------/
-
/--------------------------------------+---------------------\
- FOAM - -
- /--------------------------------+-----------\ -
- - CCO - - -
- - /-----V------\ - -
- - - - - -
- - - CHOF - - -
- - - - - -
- - |------------/ - -
- - - - -
- - -Transfer of- -
- - -data - -
- - - - -
- - /-----V------\ - -
- - - - - -
- - - CHOD - - -
- - - - - -
- - |------------/ - -
- |--------------------------------+-----------/ -
|--------------------------------------+---------------------/
/--------------------------------------+---------------------\
- IOG - Transfer of charging-
- - data to the -
- /-----V------\ destination -
<-+--------------------------------+ FMS - -
- Output |------------/ -
- to billing -
- system Storage of assorted -
- charging data -
|------------------------------------------------------------/

CHOD CHarging Output Distribution
CHOF CHarging Output Formatting
FOAM Formatting and Output Application Module
IOG Input/Output Group
FIGURE 5: Common Charging Output to IOG
2.3.5 Call Data Output to Adjunct Processor
The output of Call Data Record can be performed using the output functions Toll Ticketing (TT)
and/or Immediate Call Itemization (ICI). A Call Data Record is generated and transferred to
Adjunct Processor. Indication of the output function (TT/ICI) can be added into call data record.
The formatter in the Adjunct Processor can make different types of output record(s) for the
indicated output function(s).
/------------------------------------------------------------\
- RMP -
- -
|------------------------------------------------------------/
-
/-----------------+------------------------------------------\
- FOAM - -
- /-----------+--------------------------------\ -
- - CCO - - -
- - /-----V------\ - -
- - - - - -
- - - CHOP - - -
- - - - - -
- - |------------/ - -
- - - - -
- - - Transfer of - -
- - - data - -
- - - - -
- |-----------+--------------------------------/ -
|-----------------+------------------------------------------/
- Message Protocol to
- Adjunct Processor
/-----------------+------------------------------------------\
- AP - -
- - -
- /-----V------\ -
- - - -
<-+-----------+ Formatter - -
- - - -
- Output |------------/ -
- to billing -
- system -
|------------------------------------------------------------/
CHOP CHarging Output Adjunct Processor
FOAM Formatting and Output Application Module
FIGURE 6: Common Charging Output to AP
2.3.6 Examples
2.3.6.1 Examples of Commands Common for Both IOG and Adjunct Processor
Interface Command CHOLC is used to allow the regulation of output of Common Charging Output
data depending on the call termination status. It is also used to allow the regulation of call attempt
charging.
CHOLC:LIMIT=EOS;
CHOLC:ELIMIT=5&7;
Data for calls that reach through connection are to be output.
Call data is output for all calls that reach the current value of parameter LIMIT. For ISDN-E (ISDN,
Ericsson Implementation) calls not reaching the call termination status indicated by parameter
LIMIT, if flexible counter 5 or 7 are not equal to zero, all call data, including non-zero flexible
counters, is output.
Command CHOIC is used to change charging data output interface. The change of the interface is
possible only when the wanted interface is supported by the AXE parameter POSSIBLEOUTDEST
[REF 4].
CHOIC:INTERF=IOG;
Charging data output interface is changed from Adjunct Processor to IOG.
2.3.6.2 Examples of Commands for IOG Interface
Command CHOUC is used to initiate priority of each output function. An output function with high
priority can use as many idle CDF individuals as available. Output functions with low priority are
only allowed to use the percentage specified in NUMIND, after which congestion is indicated for
that output function.
Command CHOUC also determines the maximum duration that output data can reside in a buffer,
for the specified output function.
CHOUC:FN=TT,PRIORITY=HIGH,CONV=ASN1,PBC=5;
CHOUC:FN=ICI,PRIORITY=LOW,NUMIND=30,CONV=ASN1;
Output function TT is used with high priority. The conversion type is ASN.1 tagged data and
Periodic Buffer Control required is 5 minutes i.e. data is output after 5 minutes.
Output function ICI is also used with low priority. The conversion type is ASN.1 tagged data and
the maximum number of CDF individuals available for ICI is 30 percent of the total number of
individuals.
NOTE: Parameter PBC (Periodic Buffer Control) is only available for TT function.
Command CHOTC specifies the IO device on which the output for the specified output function will
be presented. The IO device cannot be changed during normal operation. The high capacity
interface allows a higher capacity of throughput. The number of buffers that are to be used by an
output function can also be specified, but can only differ from the present value by at most 10.
CHOTC:FN=TT,IO=IOG11,CAP=HIGH;
CHOTC:FN=ICI,IO=IOG11,CAP=HIGH;
CHOTC:FN=TT,BNUM=10;
CHOTC:FN=ICI,BNUM=5;
File type TT is used and file output for that is IOG11 with high capacity interface. File type ICI is
also used with file output IOG11 and with high capacity interface. The number of buffers to be used
for output function TT is set to 10 and the number of buffers to be used for output function ICI is
set to 5.
Command CHOFI opens files corresponding to the specified output function, or re-open it if the file
was previously closed.
CHOFI:FN=TT,FILEID=01;
The file TTFILE01 is to be opened.
2.3.6.3 Examples of Commands for Adjunct Processor Interface
Command CHOPI opens Adjunct Processor interface. Interface must be opened before it can be
used as active interface for charging data output.
NOTE: The buffer size needs to be set to the same size as the one defined in Adjunct Processor.
CHOPI:BSIZE=4;
Buffer size is specified to 4 kilobytes.
Command CHOEC defines output period for buffers used in Adjunct Processor interface.
CHOEC:OUTP=00330;
Output period is specified to 3 minutes and 30 seconds.
Command CHOPE closes Adjunct Processor interface. Interface must be closed before buffer size
can be changed. AP Interface is to be closed when IOG has been changed to be active interface for
call data output.
CHOPE;
2.4 IOG Handling

The handling of IOG3 is not described in this User Guide.
IOG20 handling is similar to IOG11 handling; commands can be used with parameter 'IOG11' also
in case of IOG20.
2.4.1 Description
/-------\
/+------\-
- -+-----------------------------
- CP ++----------+------------------
- +/ --
|-------/ --
--
/---------++-----\
- /--++--\ - ICB
- SPS +------+------ --- --- --->
- - SP - -
- |------/ -
|---------+------/
/---------------\ - /-------------\
- /----\ - - - /----\ -
- - AT +-+-----+-------+--+ HD - -
- |----/ - - - |----/ -
- - - - -
- /----\ - - - /----\ -
- - AT +-+-----+-------+--+ FD - -
- |----/ - - - |----/ -
- - - - -
- /----\ - - - /----\ -
- - ALI+-+-----+-------+--+ MT - -
- |----/ - - - |----/ -
- MCS - - - FMS -
|---------------/ - |-------------/
-
/-------------\ -
- DCS DL - -
- <------+-/
|-------------/
ALI Alarm Interface

AT Alphanumerical Terminal
DCS Data Communication Subsystem
DL Data Link
FD Flexible Disk
HD Hard Disk
ICB Incoming Calls Barred
MCS Man-Machine Communication Subsystem
MT Magnetic Tape
SP Support Processor
SPS Support Processor Subsystem
FIGURE 7: The Subsystems of SP-based IO System
File Management Subsystem (FMS) is used for handling the external mass storage requirements of
AXE. FMS handles the different types of files, functions for sending files over data links or
transferring them to an external medium.
Data Communication Subsystem (DCS) is used to transfer data between network entities outside of
the IOG via data links. Using DCS it is also possible to make "real-time" charging for ICI service
with Direct File Output functionality.
NOTE: Availability of DCS depends on APZ version.
FMS and DCS are the most important subsystems inside the IO system in order to store or transfer
the charging data.
The Toll Ticketing data generated in the exchange is stored in files (TT files) on the IOG hard disk
(HD) before it is sent to the billing center for post-processing. The files can be sent to the billing
center over a data link or by using an external medium.
Immediate Call Itemization files (ICI files) can be handled like the TT files. It might however be
more appropriate to use faster methods when transferring the data to its destination. The method
to transfer the data immediately to a remote destination without intermediate storage on the HD is
called Direct File Output.
2.4.2 File Process Utility (FPU)
File processing is carried out by the FPU (File Processing Utility) function. This function administers
the distribution of files to external receiver via a data link. File Process Utility function (FPU) also
ensures the safe transfer of the closed subfiles via data link before any overwriting is done.
Data by FPU can be transferred in four different ways:
- Manual transfer over a data link

- Ericsson MTP over X.25 interface
- Automatic transfer over a data link
- Polled transfer over a data link
- FTAM over X.25 interface
- Manual transfer to an external medium
NOTE: For data links, DCS is required.
2.4.3 Direct File Output (DFO)
A function called Direct File Output allows the sending of files directly over a data link without
intermediate storage on hard disk media. Each record is sent on the link as soon as it is produced.
This opportunity allows transfer of ICI data immediately to a remote destination without
intermediate storage on the HD.
However during the link failure, produced data (to be output) may be either stored in a backup file
or transmitted towards another data link, if such a backup has been defined.
2.4.4 Infinite Sequential Files
The function Infinite Sequential Files provides a file user with a virtual file of infinite size by
dividing the file into a predefined number of subfiles. On writing into a subfile the subfile becomes
active. The previous subfile is closed and the next is waiting to take over. After filling the last
subfile at continuous outputs, the data will be written in the first subfile again and the procedure
can continue in this manner infinitely. Such files are useful for large or continuous outputs such as
Toll Ticketing. A subfile is not overwritten until remove condition (e.g data from the subfile is
dumped to an external medium and subfile has been closed 48 hours) are fulfilled.
Here is a figure about an Infinite Sequential file:
/-------------------------------------------------------\
- TT FILE 00 -
- -
-subfile subfile subfile ... subfile -
- 1. 2. 3. ... Nth -
-/-----\ /-----\ /-----\ /-----\ /------\-
--Fill - -Fill - -Fill - - - -Fill --
--1st - -2nd - -3rd - - - ... -Nth --
-- - - - - - - - - --
-- - - - - - - - ... - --
-- - - - - - - - - --
-- ->- ->- ->- -> ... >- --
-- - - - - - - - - --
-- - - - - - - - - --
-- - - - - - - - - --
-- - - - - - - - - --
-- - - - - - - - - --
-- - - - - - - - - --
-- - - - - - - - - --
-|-----/ |-----/ |-----/ |-----/ |---V--/-
- - After last subfile is -
- |||||||||||||||||||||||||| filled, storing continues-
- from the beginning of the-
- first subfile -
|-------------------------------------------------------/
2.4.5 Commands for Handling of IOG
Commands for file handling:
Entry command INMCT required
- INFET, IO Subsystem Functions File Administration,

External, Transfer
- INFIC, IO Subsystem Functions File Administration,
Change
- INFII, IO Subsystem Functions File Administration,
Initiate
- INFIP, IO Subsystem Functions File Administration,
Print
- INFIR, IO Subsystem Functions File Administration,
Remove
- INFIT, IO Subsystem Functions File Administration,
Transfer
- INVOI, IO Subsystem Functions, Volume Administration,
Initiate
Commands for the definition of Infinite Sequential File:
No entry command required
- IOIFE, IO Infinite Sequential File Function,

End
- IOIFI, IO Infinite Sequential File Function,
Insert
- IOIFP, IO Infinite Sequential File Function,
Print
- IOIFR, IO Infinite Sequential File Function,
Remove
Commands for File Process Utility (FPU) functions:
No entry command required
- INFCC, File Process Utility Function IO Node

File Condition, Change
- INFDC, File Process Utility Function IO Node
File Destination, Change
- INFDI, File Process Utility Function IO Node
File Destination, Insert
- INFDP, File Process Utility Function IO Node
File Destination, Print
- INFDR, File Process Utility Function IO Node
File Destination, Remove
- INFMT, File Process Utility Function IO Node
File Multiple, Transfer
- INFOE, File Process Utility Function IO Node
File Override, End
- INFOI, File Process Utility Function IO Node
File Manual Override, Initiate
- INFPC, File Process Utility Function IO Node
File Time Period, Change
- INFRI, File Process Utility Function IO Node
File Retransfer, Initiate
- INFSI, File Process Utility Function IO Node
File Subfile, Initiate
- INFSP, File Process Utility Function IO Node
File Status, Print
- INFTE, File Process Utility Function IO Node
File Transfer, End
- INFTI, File Process Utility Function IO Node
File Transfer, Initiate
- INFUE, File Process Utility Function IO Node
File Utility, End
- INFUP, File Process Utility Function IO Node
File Utility, Print
Commands for Direct File Output:
Entry command IMLCT required
- ILDFI, IO Data Channel Subsystem Functions,

DFO Device Initiate
- ILDFP, IO Data Channel Subsystem Functions,
DFO Device Print
- ILDFR, IO Data Channel Subsystem Functions,
DFO Device Remove
See Operational Instructions:

IOG11, Initiate
IOG3, Initiate
- SPG, Start
- SPG in Single Node, Start
- SPG, File on Hard Disk, Define
- SPG, Device File, Define
- SPG File, Delete
- File Process Utility, Override Condition, Initiate
- File Process Utility, Override Condition, End
- File Process Utility, Time Slot, Define
- File Process Utility, Destination Data, Change
- File Process Utility, File and Destination, Define
- File Process Utility, Manual File Transfer, Start
- File Process Utility, Manual File Transfer, Stop
- File Process Utility, File and Destination, Delete
- FILE Process Utility, File, Retransfer
- Infinite Sequential File, Active Subfile, Change
- Infinite Sequential File, Definition, Change
- DFO IO Device Fault
- DFO Backup, Define
2.4.6 Examples for Charging Data Files
Procedure is according to Operational Instruction for

IOG11, Initiate
2.4.6.1 Creation of a Volume on Hard Disk
Files are contained in volumes. Volumes are related to storage units, i.e. hard disks, flexible disks
and tapes. A flexible disk and a magnetic tape contain only one volume. The volume is created
when the disk is formatted or the tape is scratched. When a hard disk is formatted it creates a
potential volume covering the whole hard disk. This volume cannot be used for storing of files, so
after formatting a hard disk, volumes have to be created with command INVOI.
2.4.6.2 Creation of a File on HD without Infinite Sequential Files
A new file is created with the command INFII. A file must be given a unique name. Some names
are system defined, otherwise the name can be chosen according to recommendations or
randomly.
INMCT:SPG=0;
INFII:FILE=TTFILE00,VOL=CALLVOLUME,RLENGTH=2048,EXP=100,
SIZE=200,TYPE=SEQ,FCLASS=SPL;
END;
File management function is initiated by command INMCT. The file TTFILE00 is created and is
connected to the volume CALLVOLUME. The file type is a sequential file i.e. each new record is
written in sequence after the previous one. Reading of the records from a sequential file is done in
the same order as they were written. File class is simple file i.e. the file shall not have any subfiles.
The record length is 2048 octets and the reserved file size is 200 records. The value of expansion
factor is 100 i.e. if the file size is reached then the file will be expanded in steps of 100 records.
2.4.6.3 Creation of a File on HD with Infinite Sequential Files
The infinite file consists of subfiles. The size of a subfile can be variable and it is controlled by
attributes maximum size of subfile (MAXSIZE) and maximum life time of subfile (MAXTIME).
When both attributes MAXTIME and MAXSIZE are given, a subfile is closed when a limit set by one
of the attributes is fulfilled.
The initial size of a subfile (SIZE) can be expanded by number of records defined by an attribute
expansion factor (EXP), if MAXTIME is given.
Example 1. Use of MAXTIME and EXP
INMCT:SPG=0;
SIZE=200,TYPE=SEQ,FCLASS=CMP;
END;
IOIFI:FILE=TTFILE00,NSUB=9999,MAXTIME=120;
The creation of the main file (TTFILE00) is described in example above. The file TTFILE00 is
inserted in the infinite sequential file table by command IOIFI. The number of subfiles is 9999.
The maximum life time for a subfile is 120 minutes. If the initial size 200 is reached within 120
minutes the size of the subfile is expanded by 100 records.
When subfile 0001 has been used 120 minutes, the subfile is automatically closed and reported to
File Process Utility (FPU). The storing of data continues in subfile 0002. When storage starts in a
subfile, the next subfile is automatically created to be used when the first subfile is closed.
The creation of new subfiles continues until the maximum number, set by command, is reached.
Data will then be written into the first subfile again if that file has been removed/deleted according
to the remove conditions. If files are not removed in time, an alarm is issued when the number of
subfiles is closed to the maximum.
Example 2. Use of MAXSIZE
INMCT:SPG=0;
SIZE=200,TYPE=SEQ,FCLASS=CMP;
END;
IOIFI:FILE=TTFILE00,NSUB=9999,MAXSIZE=400,MAXTIME=60;
The creation of the main file (TTFILE00) as in example above. The file TTFILE00 is inserted in the
infinite sequential file table by command IOIFI. The number of subfiles is 9999.
The maximum size of subfile is 400 records. A subfile is closed when either all the 400 records are
filled or the lifetime limit 60 minutes for the subfile is reached.
NOTE 1:
When MAXSIZE is given and the MAXTIME is not given, the initial size of subfile is overwritten by
MAXSIZE and the subfile expansion is never done. That is, the attribute EXP is useless.
NOTE 2:
The memory in IOG HD is reserved according to MAXSIZE, if it is given. That is, lot of memory will
be waisted when there is too big MAXSIZE value in relation with MAXTIME.
E.g. If MAXSIZE is 200 and MAXTIME is 30, then within 2 hours (120 minutes) area of 800 records
is reserved on IOG HD.
Recommendation of the attributes SIZE, EXP, MAXSIZE and MAXTIME:

Do not set the attributes so that you get lot of subfiles per unit of time. The generation of many
subfiles can decrease the capacity of the file system, in terms of access time and amount of stored
data on the medium.
Do not generate more than one subfile each half an hour.
2.4.6.4 Creation of a Device File (Flexible Disk)
When a device file is to be created the same command should be used but with another parameter
combination. Here the file device must be given instead of the volume.
INMCT:SPG=0;
INFII:FILE=DL0A1,NODE=A,IO=DL-1,RLENGTH=512,EXP=64,SIZE=16,
TYPE=SEQ,FCLASS=DEV;
END;
2.4.6.5 Using the File Process Utility (FPU)
A manual transfer to a specified destination is ordered by the command INFTI. Simple files and
individual subfiles of a composite file can be transferred.
INFTI:FILE=TTFILE00,DEST=CHARGING;
The file TTFILE00 has been specified as above. The manual transfer of the file is required to the
destination CHARGING.
The automatic transfer is carried out on subfiles only. When a subfile is full with data (or after a
predefined time in certain files) it is closed and reported to the FPU list. The writing of data will
then automatically continue in the next subfile, FPU transfers all reported subfiles to the specified
destination as soon as possible.
INFDI:FILE=TTFILE00,DEST=CHARGING,EQUIP=MT;
INFCC:FILE=TTFILE00,REMOVE=2400,DUMPCOND=DUMP;
The file TTFILE00 has been defined as before. The automatic transfer is activated with command
INFDI, destination is CHARGING and equipment that receives the file data is Optical Disk.
Automatic Removal Conditions is also required and it can be specified by command INFCC. The
data of file TTFILE00 remains in Hard Disk 24 hours before it is made undefined and erased from
the HD if one of the two output conditions is fulfilled (TRANSCOND or DUMPCOND). Dump condition
indicates the number of Optical Disk the subfiles must be dumped on before they are removed
from the Hard Disk. (DUMP= One disk, DUPL= Two disks).
2.5 Adjunct Processor Handling

The Adjunct Processor is implemented on an open platform for example UNIX or NT-based system,
that interworks with the CP through the 'Message Protocol to AP'.
CP- AP
-
/-----\ - /-----------\
- - /------------------\ - - Protocols to
- CCO +---+ Message Protocol +---\ /----+ Formatter +--> e.g. billing
- - - to AP - - - - - system
- - |------------------/ /-+--+--\ - -
|-----/ - -Message- |-----------/
- -store -
- - -
- |-------/
-
FIGURE 8: Adjunct Processor interface with Formatter
This User Guide does not describe how Adjunct Processor is maintained. There is however,
operational documentation for maintaining the Adjunct Processor, e.g. System Administration
Guide and Installation Instructions for Adjunct Processor. Similarly own user documents exist for
Formatter application (FOS) and Reliable Data Transfer (RDT) in case of an APG40 based output
system.
For detail, refer to User Guide for Charging Data Output through APG.
2.6 Source Filtering
2.6.1 Description
The purpose of this function is to give the operators the possibility to select the data to be output
for the call and to set the ASN.1 tag values. For each traffic case (for example: MS originating,
Transit) a set of parameters exists which can be output on the CDR. Using the Source Filtering
function it is possible to define which of these parameters are to be output on the CDR for different
traffic cases. This is illustrated in figure 9.
/----------\ /---------\ /----------------\ /-----\

-Chargeable--->-Source - ASN.1 tags -Generate ASN.1 - - -
-Traffic --->-Filtering-================>-Call Data Record-==>-ASN.1-
-Activity --->- - -(all collected - -CDR -
-(e.g. Call--->-/-------\- - parameters) - - -
- From MS) --->--CHFIM00-- /---------\ - - - -
- --->-+-------+--->-Collected-==>- - - -
- --->--CHFIM01-- -Data for - - - - -
- --->-|-------/--->-Call Data- |----------------/ |-----/
- --->- : - -Records -
- --->-/-------\--->- -
- --->--CHFIMxx-- - -
- --->-|-------/--->- -
|----------/ A |---------/ A |---------/
- -
All the Parameters
parameters that are
that can be needed
collected
FIGURE 9: Source Filtering
2.6.2 Functionality of Source Filtering
The Source Filtering information is stored in CHarging FIlter Module (CHFIM) blocks. This is
implemented with a multi block concept. That means that the user reads the data from block
CHFIMxx. Each CHFIMxx block contains the Source Filtering information for one traffic case. The
Source Filtering information defines the parameters that shall be output on the CDR and the
corresponding ASN.1 tags. The xx in the block name of CHFIMxx corresponds to a traffic case. The
possible CHFIMxx blocks for each mobile application can be derived from the view service values
stated in [REF 5] and [REF 6].
2.6.3 Initial Setting of Source Filtering Information
The data in the Call Data Records can be selected by setting application parameters in CHFIMxx
blocks at initial start and at large restart with reload. The Printout Description for Common
Charging Output ASN.1 Result lists all parameters for each Call Data Record that can be collected.
The customer has to specify which ones need to be output. Source Filtering (CHFIMxx blocks) is
used to select whether a parameter is output and to specify the ASN.1 tag for that parameter.
2.6.4 Change of Source Filtering Information
After initial setting, Source Filtering Information can be changed by commands in order to disable
the output of parameters on the CDR. This can be done during traffic without the need for system
restart to activate the changes. This is described in a separate user guide [REF 2].
2.7 Automatic Charging Buffer Flushing in Traffic Isolation

In MSC-S BC system, when a blade traffic isolation is initiated by command, the traffic isolation
procedure should be delayed in order to wait until all charging data in FOAM are transferred into
charging AP.
However, if the AP connection is lost during this charging data transferring period, FOAM delays
the traffic isolation procedure. After the operator restore the CP-AP connection and release the
alarm "COMMON CHARGING OUTPUT ADJUNCT PROCESSOR INTERFACE FAULT", FOAM continues
charging data transferring and complete traffic isolation progress.
As to traffic isolation in MSC-S BC system, please refer to User Guide for MSC Server Blade
Cluster Configuration and Handling.
Note: for those traffic isolation initiated by Recovery (e.g. large restart or cloning), FOAM does not
delay the isolation progress due to CDR survives the recovery.
3 References
1 1/1553-1/APT 210 26/x Uen
User Guide for Charging, GSM and UMTS
2 1/1553-APR 101 14/x Uen
User Guide for masking source filtering data using DBS
3 3/155 18-APR 101 14/x Uen
Parameter Set AMCFOAMC Changeable Exchange Adaptation
4 4/155 18-APR 101 14/x Uen
Parameter Set AMCFOAMS Changeable Exchange Adaptation
5 3/155 18-APX 101 01/x Uen
View Service Values in Mobile Charging
(WCDMA/GSM)
6 3/155 18-AXE 106 32/x Uen
View Service Values in Mobile Charging
(CDMA)
7 24/1553- CSA 121 01/x Uen
User Guide for Charging Data Output through APG
8 36/1553- CSA 121 01/x Uen
User Guide for MSC Server Blade Cluster Configuration and Handling

User Guide For Output of Call Data: 1 General

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

User Guide For Output of Call Data: 1 General

Uploaded by

Copyright:

Available Formats

USER GUIDE FOR OUTPUT OF CALL DATA Page 1 of 28

DIRECTIONS FOR USE 1553-APR 101 14/22 Uen A

Copyright Ericsson GmbH 2010 - All Rights Reserved

USER GUIDE FOR OUTPUT OF CALL DATA

1.1 Revision Information

EVENT MODULE is data related to an event which is independent of time duration.

Long call duration. The partial output occurs at regular

System limits. For example partial output is triggered

Real time charging purposes.

ALI Alarm Interface

DFO Direct File Output

FIGURE 1: Charging Related Functionalities

2.2 Output of Call Data Records

2.2.1 Output Functions

TOLL TICKETING (TT)

IMMEDIATE CALL ITEMIZATION (ICI)

2.2.2 Structure of Call Data Record in ASN.1 Format

2.2.2.1 Structure of Single Call Data Record

The Call Data Record consists of the following parts:

Call data related to the call.

Call data for call related events.

FIGURE 2: Structure of Single Call Data Record

2.2.2.2 Structure of Composite Call Data Record

FIGURE 3: Structure of Composite Call Data Record

2.3 Common Charging Output (CCO)

2.3.2 Functionality of Common Charging Output

CHarging Output Commands

CHOC is the command receiving/handling block for all commands in FOAM.

CHarging Output Formatting

CHarging Output Distribution

CHarging Output Adjunct Processor

2.3.3 Commands for Handling of Common Charging Output

- CHOIC, Charging Output Interface, Change

See Adaptation Directions:

- Traffic Data: Common Charging Output

See Operational Instructions:

- Common Charging Output Configuration

2.3.4 Call Data Output to IOG

The data is output in ASN.1 format.

CCO Common Charging Output

FIGURE 5: Common Charging Output to IOG

2.3.5 Call Data Output to Adjunct Processor

FIGURE 6: Common Charging Output to AP

Data for calls that reach through connection are to be output.

Charging data output interface is changed from Adjunct Processor to IOG.

2.3.6.2 Examples of Commands for IOG Interface

The file TTFILE01 is to be opened.

2.3.6.3 Examples of Commands for Adjunct Processor Interface

Buffer size is specified to 4 kilobytes.

Output period is specified to 3 minutes and 30 seconds.

2.4 IOG Handling

ALI Alarm Interface

FIGURE 7: The Subsystems of SP-based IO System

transferring them to an external medium.

NOTE: Availability of DCS depends on APZ version.

2.4.2 File Process Utility (FPU)

Data by FPU can be transferred in four different ways:

- Manual transfer over a data link

NOTE: For data links, DCS is required.

2.4.3 Direct File Output (DFO)

2.4.4 Infinite Sequential Files

Here is a figure about an Infinite Sequential file:

2.4.5 Commands for Handling of IOG