A1338

A1338

CDR COLLECTOR /CHARGING GATEWAY

PRODUCT DESCRIPTION

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 1/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

TABLE OF CONTENTS
1 A1338 PRESENTATION ..................................................................................................................3
1.1 Functional scope ..............................................................................................................................3
1.2 Benefits............................................................................................................................................5
2 FUNCTIONAL DESCRIPTION......................................................................................................6
2.1 A1338 CDR Collector.....................................................................................................................7
2.1.1 CDR collection from NE..........................................................................................................................................................8
2.1.2 CDR processing and storage.................................................................................................................................................8
2.1.3 CDR Distribution.....................................................................................................................................................................9

2.2 A1338 Charging Gateway for UMTS/GPRS packet networks .....................................................10

2.2.1 CDR collection from NE........................................................................................................................................................11
2.2.2 CDR/File processing and storage.......................................................................................................................................11
2.2.3 CDR Distribution...................................................................................................................................................................12

2.3 A1338 File Collector.....................................................................................................................13

2.3.1 CDR/File collection from NE................................................................................................................................................14
2.3.2 CDR/File processing and storage.......................................................................................................................................14
2.3.3 CDR Distribution...................................................................................................................................................................14

2.4 Administration & Supervision Functions ......................................................................................15

2.4.1 Topology management.........................................................................................................................................................15
2.4.2 Configuration management..................................................................................................................................................16
2.4.3 Alarm management................................................................................................................................................................17
2.4.4 Statistics .................................................................................................................................................................................18
2.4.5 Tools and Services................................................................................................................................................................18

3 SYSTEM MANAGEMENT..............................................................................................................20
3.1 A1338 Hardware architecture .......................................................................................................20
3.2 Defence concepts ..........................................................................................................................21
3.2.1 Service availability ................................................................................................................................................................21
3.2.2 A1338 module restart ............................................................................................................................................................22
3.2.3 Acknowledgement mechanism............................................................................................................................................22

3.3 Performance and dimensioning .....................................................................................................22

3.3.1 Performance............................................................................................................................................................................22
3.3.2 Dimensioning.........................................................................................................................................................................22
3.3.3 Hardware platform.................................................................................................................................................................22

4 ABBREVIATIONS & ACRONYMS ...............................................................................................23

A. APPENDIX- A1338 VARIANTS COMPARISON ........................................................................24
B. APPENDIX - A1338 REFERENCES ............................................................................................26

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 2/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

1 A1338 PRESENTATION

1.1 Functional scope

Voice and data call detail data generated by telecommunications networks are, apart
from being used to generate bills, increasingly being used for a number of different
purposes such as Customer usage analysis, fraud management, network QoS
measurements and the like.
The A1338 is the Alcatel mediation product dedicated to centralized Call Detail Record
collection.
The A1338 collects various types of CDR coming from different elements of the network
and distributes them to different OSS (Billing Centre, Statistics, Customer Care, Fraud
Management System and/or data warehouse).
To cope with network growth and technological evolution, Network Elements (NE) need to
be added, suppressed, replaced and/or renewed without impacting or disabling service
and business activities which generate operator revenues.
The A1338 has been designed to support this. The product presents stable interfaces that
isolate and protect the OSS level from network evolution. The Alcatel A1338 is
synchronized with the evolution of the Alcatel network.
The A1338 has the ability to take into account various types of NE coming from several
NE-vendors.
Depending on the type and structure of the customer telecommunication network, OSS
architecture, the specific needs and business model, the A1338 product is proposed in
several functional variants: the A1338 File Collector, the A1338 CDR Collector and the
A1338 Charging Gateway for UMTS/GPRS packet networks.

IN,SMSC,VMS,
UMS
OTHER
Platforms
E10, S12, NGN, OSS
Other vendors
PSTN
A1338
BILLING
MSC/VLR PLMN SYSTEMS
Backbone

Fraud
Management
BSS System

INFORMATION
GPRS/UMTS Internet SYSTEMS
Backbone
Data Warehouses,
SGSN GGSN
IP marketing database
Routers
TELECOM & DATACOM WORLD DRIVEN OSS & IT WORLD DRIVEN

Figure 1 : A1338 Network positioning

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 3/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

According to the TMN standard, the A1338 operates at the Network Management Layer,
collects CDRs from NEs and distributes them to applications of upper level as Business
Management layer (e.g. Billing system) or Service Management Layer (e.g. Fraud
management).

Other
Customer Care Interconnect Systems Other
& Billing Applications

BML

Fraud Mgt
System
SML

A1338
NML

EML
A100
0S12 A 10
S0102

A100
0S12 A100
S12
0

SCP

VMS SMS GPRS/UMTS equipment ATM equipment

SWITCH
(SGSN, GGSN,…)
MSC

Figure 2 : A1338 Position in TMN Architecture

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 4/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

1.2 Benefits

The A1338 product is well suited to be integrated into the Customer’s network and is able
to evolve with the network extension and evolution.
The solution has been designed to be scalable with planned network growth, in a smooth
and simple way.
The A1338 has been developed to give operators a significant edge in achieving the
following objectives:
• Increase revenues, because it provides a single secure collection point of CDR
coming from different types of NE and their distribution to different types of OSS
applications (Billing Center, Statistics, Customer Care, Fraud Management System);
• Anticipating market evolution through its multi-vendor and multi-technology
approach;
• Handling various types of billing (e.g. normal billing, hot billing);
• Reduce operational costs by centralizing CDR collection;
• Increase QoS: the Call Detail Record is the inexhaustible source of information
through the diffusion of CDR data to different value added applications (e. g. fraud
management)

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 5/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2 FUNCTIONAL DESCRIPTION

The A1338 product is proposed in three variants according to the customer and the type
of network. The main features of the three variants are described in the following sections.
The A1338 collects call detail records coming from the equipment level, stores, processes
them (after validation and possible packet CDR aggregation) and distributes them or
simply keeps them for further requests coming from external systems.
The A1338 is a product composed of several functional blocks dedicated to:
• CDR collection
• CDR processing
• CDR distribution
• Administration and supervision (e.g. maps, statistics, alarms)
• System facilities (e.g. backup/restore)

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 6/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.1 A1338 CDR Collector

This variant processes individual CDRs; blocks or files coming from NE are opened to
extract and validate CDRs. Depending on OSS requirements, a format adaptation may
be provided in this variant. The type of networks addressed with this variant is fixed or
circuit part of mobile networks.

OSS
APPLICATION OSS
OSS APPLICATION
APPLICATION

FTP over TCP/IP

or FTAM over X.25 or IP
Outgoing CDRs

CDR Distribution
CDR (Routing,,
database OSS mediations) Administration
&
Supervision

CDR Processing
(Validation, storage)
CDR
consultation

A1338
CDR
CDR Collection
((NE mediations)
Collector

Incoming CDRs

Q3IC over X.25

Alcatel NEs
A1000 E10, MSC

Figure 3: A1338 CDR Collector – Example in Alcatel E10 NE environment

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 7/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.1.1 CDR collection from NE

The CDR Collection part of A1338 hosts all the requested mediation functions enabling
collection of various data (CDR) coming from different Network Elements (NE). Depending
on the protocols and interfaces used, the CDR are collected in blocks or in files.
A near real time collection can be performed, in absence of hot billing specific flow it is
simulated by a frequent polling.
This CDR Collection part is also in charge of NE link monitoring with configurable alarms
possible upon detection of communication failures.
The main supported interfaces are:
• Q3IC (basic Alcatel E10/GSM interface using FTAM+CMISE or CMISE only),
• FTAM over X.25,
• FTP over TCP/IP.

2.1.2 CDR processing and storage

The steps of processing and storage are the following for the A1338 CDR Collector:
• CDR validation,
• CDR storage in database.

2.1.2.1 CDR Validation

The CDR Processing part supports validation according to input CDR format
specifications. There may be one or more validation rules for each record element and
for each record type. New rules may be added according to individual needs by a
development on project basis.
For each rule, specific actions are applied in case of violation. For example if the
mandatory field in GSM “MSC type” is absent or with a wrong format the CDR is rejected,
while a record with a duration greater to a given value a warning message is written to a
log file.
Each element value in each record may be validated. The element value is checked
against a list of legal elements values. The element value must be in a defined valid
range, discrete set or must contain a valid bit pattern.

2.1.2.2 CDR Storage

CDR data are stored in a high speed access proprietary database. For this, they are
converted to the A1338 unified CDR format defined to take into account different types of
CDR.
The storage duration of CDR in database can be configured. The default storage duration
is 5 days.

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 8/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.1.3 CDR Distribution

2.1.3.1 Routing part

The CDR are forwarded to the concerned OSS mediations using filters.
Filters contain criteria based on CDR-type, list of NEs, and output format.
The routing part performs the CDR extraction from the database and the CDR duplication
if the same CDR matches several filters.
For example in an Alcatel mobile network, CDR from SSPs may be forwarded to an
Interconnect mediation system, and CDR from RCPs are sent to a billing system.
On a project basis other filters based on value of basic fields can be implemented.

2.1.3.2 OSS mediation

2.1.3.2.1 File building

For the A1338 CDR Collector, CDR forwarded by the routing part are converted to an
output format.
For the A1338 CDR Collector the standard output format is the same as the input one.
For A1338 CDR Collector, customization can be performed to adapt the CDR format to
OSS requirements but it is done on project basis. The format adaptation concerns syntax,
list of fields, encoding (for example ASN1 or ASCII).

2.1.3.2.2 OSS interfaces

The main supported interfaces are:

• FTP (the OSS application is the initiator) over TCP/IP,
• FTAM (the A1338 is the initiator) over X.25 or over IP (RFC1006).
On a project basis other interfaces can be implemented.

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 9/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.2 A1338 Charging Gateway for UMTS/GPRS packet networks

This variant works at CDR level. CDR packets from GSN are opened to extract and
validate the CDR. In addition, an aggregation can be performed to reduce the number of
CDRs received by the OSS. Depending on OSS requirements, a format adaptation may
be provided in this variant. The types of networks addressed with this variant are mobile
data networks (GPRS, UMTS packet switch part).

OSS
APPLICATION OSS
OSS APPLICATION
APPLICATION

FTP over TCP/IP or

RCP over TCP/IP
Outgoing CDRs

CDR Distribution
CDR (Routing,,
database OSS mediations) Administration
&
Supervision

CDR Processing
(Validation,
aggregation,
CDR storage)
consultation

A1338
Charging Gateway
CDR Collection
for UMTS/GPRS
((NE mediations)
packet networks

Incoming CDRs

Ga over TCP/IP

Alcatel NEs
SGSN, GGSN

Figure 4: A1338 Charging Gateway - Example in Alcatel NE environment

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 10/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.2.1 CDR collection from NE

The CDR Collection part of A1338 hosts all the requested mediation functions enabling
collection of various billing data (CDR) coming from different Network Elements (NE). This
CDR Collection part is also in charge of the NE link monitoring.
The supported interface is:
Ga interface over TCP/IP conforming to GSM12.15 for GPRS and TS 32.015 for UMTS.

2.2.2 CDR/File processing and storage

The steps of the processing and storage are the following for the A1338 Charging
Gateway:
• CDR validation,
• CDR aggregation if desired,
• CDR storage in database.

2.2.2.1 CDR Validation

The CDR Processing part supports validation according to input CDR format
specifications. There may be one or more validation rules for each record element and
for each record type. New rules may be added according to individual needs by a
development on project basis.
For each rule, specific actions are applied in case of violation. For example if the
mandatory field “GGSN address” is absent or with a wrong format, the CDR is rejected,
while a record with a duration not equal to the difference between the end time and
beginning time of the call a warning message is written to a log file.
Each element value in each record may be validated. The element value is checked
against a list of legal elements values. The element value must be in a defined valid
range, discrete set or must contain a valid bit pattern.

2.2.2.2 Packet CDR aggregation

Aggregation is performed in the A1338 Charging Gateway (CG) variant for CDRs from
packet based equipment of GPRS/UMTS.
The reason for performing aggregation of Call Detail Records (CDRs) is to reduce the
number of CDRs received by a billing system (data volume reduction) and to lower traffic
load towards OSS.
The Aggregation function merges CDR data for S-CDRs (resp. G-CDRs) having the same
identification. M-CDRs are not aggregated.
Depending on the position in the network, the aggregation element which aggregates can
do so according to different criteria. A configuration file contains the aggregation criteria
(time or volume limits for example).

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 11/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.2.2.3 Storage

The CDR are stored in a high speed access proprietary database. For this, they are
converted to the A1338 unified CDR format defined to take into account different types of
CDR.
The storage duration of CDR in database can be configured. The default storage duration
is 5 days.

2.2.3 CDR Distribution

2.2.3.1 Routing part

The routing part performs the CDR extraction from the database and the CDR duplication
if the same CDR matches several filters.
The CDR are forwarded to the concerned OSS mediations according to filter criteria.
The filter criteria are based on CDR-type, list of NEs and output format.
For example: only S-CDR and M-CDR may be sent to the mediation with an OSS
application and G-CDR to an other application.
On a project basis other filter based on value of basic fields can be implemented.

2.2.3.2 OSS mediation

2.2.3.2.1 File building

For the A1338 Charging Gateway, CDR forwarded by the routing part are converted in
output format.
The A1338 Charging Gateway provides files in ASN1 or ASCII format.
For the Charging Gateway variant, customization can be performed to adapt the CDR
format to OSS requirements but it is done on project basis. The format adaptation
concerns syntax, list of fields, encoding (for example ASN1 or ASCII).

2.2.3.2.2 OSS interfaces

The main supported interfaces are:

• FTP (the OSS application is the initiator) over TCP/IP,
• GTP’ over TCP/IP,
• Unix rcp over IP.
On a project basis other interfaces can be implemented.

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 12/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.3 A1338 File Collector

This variant is the more simple and manipulates only CDR blocks or files and has no
knowledge of the CDR format and content. CDR validation or format adaptation is not
provided in this variant. The type of networks addressed with this variant is fixed or circuit
part of mobile networks.

OSS
APPLICATION OSS
OSS APPLICATION
APPLICATION

FTP over TCP/IP

or FTAM over X.25 or IP
Outgoing CDRs

CDR Distribution
CDR file (Routing,,
Repository OSS mediations) Administration
&
Supervision

File Processing

(storage)

A1338
File
CDR Collection
((NE mediations)
Collector

Incoming CDRs

Q3IC over X.25

Alcatel NEs
A1000 E10, MSC

Figure 5: A1338 File Collector - Example in Alcatel E10 NE environment

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 13/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.3.1 CDR/File collection from NE

The CDR Collection part of A1338 hosts all the requested mediation functions enabling
collection of various billing data (CDR) coming from different Network Elements (NE).
Depending on the protocols and interfaces used, the CDR are collected in blocks or in
files. This CDR Collection part is also in charge of the NE link monitoring with for example
configurable alarms possible upon detection of communication failures.
The main supported interfaces are:
• Q3IC (basic Alcatel E10/GSM interface using FTAM+CMISE or CMISE only) over X.25,
• FTAM over X.25 or IP (RCF 1006),
• FTP over TCP/IP.

2.3.2 CDR/File processing and storage

The steps of the processing and storage are the following for the A1338 File Collector:
detection of duplicated CDR files and file storage in the repository,

2.3.2.1 Storage

The storage duration of CDR files can be configured. The default storage duration is 5
days.

2.3.3 CDR Distribution

2.3.3.1 Routing part

The routing part performs the CDR file extraction from the repository and the file
duplication if the same file matches several filters.
The files are forwarded to the concerned OSS mediations according to filter criteria.
The filter criteria are based on a list of NEs.
For example, CDR from Transit exchanges may be forwarded to a mediation with an
interconnect application and CDR from local exchanges are sent to the billing system.

2.3.3.2 OSS mediation

2.3.3.2.1 File building

For the A1338 File Collector the output format is the same as the input one.

2.3.3.2.2 OSS interfaces

The main supported interfaces are:

• FTP (the OSS application is the initiator) over TCP/IP,
• FTAM (the A1338 is the initiator) over X.25 or over IP (RFC1006).
 Alcatel 2002 Reference Edition Page
3AT 06724 AAAA DEZZA V01 01 14/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.4 Administration & Supervision Functions

The A1338 provides an access to the administration and supervision functions via a
Graphical Interface. This interface is based on X11/MOTIF standards.
A user assistance is provided through the on-line view of the user guide. This guide is
available through the MMI interface of the administration function.

2.4.1 Topology management

The A1338 presents to the user a desktop with maps and submaps, defined by the
operator, of declared elements (mainly NE) which are colored according to current alarm
status and user color definition.

Figure 6: desktop window example

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 15/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.4.2 Configuration management

The user can create/modify/lock/unlock/delete mediation objects, using the

Configuration Manager (GUI).
• NE Mediation configuration concerns for example :
− General NE parameters (user label, location name, host name …),
− Supervision parameters (thresholds and severity of alarms, administrative
state…),
− Data-type corresponding to each CDR flow collected with specific parameters
(example: type of collection, periodicity e.g. polling period, etc) and if necessary
CDR format (example: R24, R5,etc).
− Protocol : username and password.
• OSS Mediation configuration concerns for example :
− General OSS parameter (OSS name,…),
− File closure parameters (file size)
− Supervision parameters (thresholds and severity of alarms, administrative state,
…),
− Protocol : username and password.

Figure 7: configuration window example

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 16/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

Depending on variant the system administrator has to configure network layers (X25 and
Transport layers) with tools offered by the basic software (by HP-UX for example) and the
upper layers (for example CMISE, FTAM) in the appropriate configuration files.

2.4.3 Alarm management

In addition to the alarms automatically generated by A1338 CDR Collector in case of

detection of an abnormal condition, the alarm management administration enables the
customization of the conditions for generating some alarm types.
The user can display alarms. The user can also define filters to determine the alarms to
display.
A SNMP interface can provide to an external SNMP manager an alarm synthesis status
giving by the highest active alarm severity.

Figure 8: Example of NE with active alarm on desktop and corresponding alarm display

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 17/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.4.4 Statistics

The A1338 provides a tool for displaying statistics and counters gathered from all
modules. These counters are updated by each A1338 function: NE Mediation,
aggregation if used, kernel & routing, and OSS mediation.
A Web based interface for the display of counters is available. This enables counters to be
displayed in both table and graphic formats from a remote PC using standard
HTML/Java interfaces.
The collection period is the same for all counters and is a configurable parameter.

Figure 9: Statistic layout example

2.4.5 Tools and Services

2.4.5.1 CDR Consultation

CDR Consultation is used for examining CDRs in the kernel’s database. CDR Consultation
is mainly intended for troubleshooting, and is therefore useful when users want to examine
the contents of a small number of CDRs. Users specify queries based on most fields in a
unified CDR format.
Note: This feature is available with the A1338 CDR Collector and Charging Gateway
variants.
 Alcatel 2002 Reference Edition Page
3AT 06724 AAAA DEZZA V01 01 18/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

2.4.5.2 Logs management

A daily journal destined for A1338 users is maintained. This will log OSS file closure, file
sending, system start-up and shutdown etc…
In addition, the system may be configured to log attempts to log in/out to the server by
using UNIX mechanisms.

Figure 10 : Example of daily log for an OSS mediation

2.4.5.3 Backup/Restore

Backup and restore operations are performed using standard platform/Unix tools.
The OSS mediation generates CDR files with human-readable names so that they can be
easily identified by the operator during backup and restore operations. The operator can
create a dump to a media type (DAT in general) of the current CDR files waiting to be sent
to a given OSS. CDR files are in OSS format.

2.4.5.4 Licence control

The licence control is based on a average daily number of collected CDR that is
computed on the last 30 days. When the limit corresponding to the licence is exceeded
the customer must upgrade his licence within a period of 60 days. When this 60 days
period is finished the CDR are still collected but no longer forwarded. Three alarms with
increasing severity are displayed to warn the customer to upgrade his licence. The licence
is linked to a dedicated hardware platform.

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 19/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

3 SYSTEM MANAGEMENT

3.1 A1338 Hardware architecture

The A1338 gives high flexibility in terms of implementation. Two possible configurations
exist for ensuring the resilience of A1338 functions in terms of:
§ Data integrity,
§ Service integrity.
The configuration for data integrity requires a simplex machine with mirrored disks.
The configuration for service integrity requires a symmetrical architecture with two servers
to perform processing. In this case the A1338 runs in active-standby mode.

Customer
Billing
PC

PC CDRs
LAN
Hub

Hub

LAN
Router
Router

CDRs
CDRs

A1338 A1338
Active server Standby server

CDR : Call Detail Record CDRs

X25 Switch X25 Switch

DCN
X.25 Network CDRs
CDRs

…
A1000 Fixed or Mobile

Figure 11 : Architecture example with redundant configuration

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 20/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

Customer
Billing

PC CDRs

Hub

LAN

A1338
Charging Gateway

CDR : Call Detail Record

Router

CDRs

IP
Backbone CDRs
CDRs

…
GPRS/UMTS packet switches
(GGSN, SGSN)

Figure 12 : Architecture with non redundant configuration

3.2 Defence concepts

3.2.1 Service availability

The high availability of the service is provided by the use of redundant systems working in
active / stand-by mode and managed by a specific software of the hardware platform. A
disk space is shared between the systems where configuration data, CDR files, CDR data
base and logs are stored.
Hardware failures (memory, processor, disk controller, physical telecom links, ….), are
managed by the specific software of the hardware platform. The A1338 application is
also managed by this software and a switch over can be activated if the stand-by system
is available.
Application startup, switch over or stopping are logged.
The system that initiates a switch over is temporarily discarded from the cluster and must
manually be attached after trouble analysis (in order to avoid flip-flop) with a man
machine command.

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 21/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

3.2.2 A1338 module restart

If one function is going down, it is automatically restarted by the system. If the number of
successive restart (configurable) is reached, an alarm is generated and depending on the
high availability of the system, a machine switch can be performed.

3.2.3 Acknowledgement mechanism

One of the major requirements of the A1338 is to process CDRs without losing any of
them.
At each level of the system (i.e. NE mediation, CDR storage in database…) CDRs are first
stored locally in a safe storage media (mirrored disks) before being acknowledged to the
previous level.
This mechanism is also true for CDR acknowledgement between NEs and A1338 and
between A1338 and OSS Applications when a secured protocol is used in push mode.

3.3 Performance and dimensioning

3.3.1 Performance

Due to its scaleable architecture providing very high-performance collection, the A1338 is
able to support the real time CDR collection, enabling the deployment of real time
services.
The A1338, according to the hardware configuration, can collect and validate up to
several thousand CDRs per second coming from several hundred of NEs by file or by
message (event).
For example with a duplex configuration based on the HP N4000 server, the A1338 CDR
Collector variant can collect up to 6000 CDR per second (about 216 Millions of CDR per
day with 10 busy hours).

3.3.2 Dimensioning

The scaleable architecture allows to dimension the A1338 according to the storage
duration needs (impact of disk configuration) from few days to several months.
Usual parameters of the A1338 dimensioning are
§ Maximum Number of OSS clients supported : 3
§ Maximum Number of user positions : 2

3.3.3 Hardware platform

Hewlett Packard platform are used in general and are strongly recommended. But on a
project basis other platforms (SUN for example) can be supported.

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 22/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

4 ABBREVIATIONS & ACRONYMS

BML Business Management Layer

CDR Call Detail Record
CMISE Common Management Information Service Element
EML Equipment Management Layer
FTAM File Transfer Access Method
FTP File Transfer Protocol
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GUI Graphical User Interface
HP Hewlett Packard
IN Intelligent Network
IT Information Technology
NE Network element
NGN Next Generation Network
NML Network Management Layer
QoS Quality of Service
OSS Operation and Support System
SCP Service Control Point
SGSN Serving GPRS Support Node
SML Service Management Layer
SMS Short Message Service
TMN Telecommunications Management Network
UMTS Universal Mobile Telecommunications Systems
VMS Voice Messaging System

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 23/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

A. APPENDIX- A1338 VARIANTS COMPARISON

FUNCTION CDR File Collector Charging

Collector Gateway
for UMTS/GPRS
packet networks
Ability to fit to a large Network YES YES YES
(e.g. more than 12 NEs for a
Mobile Network and more
than 20 for a Fixed Network)
Possibility to collect CDRs with YES YES NO
different formats and
protocols than those of native
Alcatel’s NEs (e.g. FTP, FTAM
server or client, Remote Copy,
etc.)
Collection of CDRs by files YES YES NO
Simultaneous transfer from YES YES YES
various NEs
Storage of files, blocks or YES YES YES
packets collected in their
native format for backup
Validation of the files, blocks YES NO YES
or packets structure collected
(level 1 validation)
Validation of each field of the YES NO YES
CDR (level 2 validation)
Lab configuration of N2 YES NO YES
validation rules (rules value
and process in case of error)
Warning about duplicate files, YES YES YES
CMISE blocks, Ga packets
Packet CDR Aggregation NO NO YES
Display of CDRs through an YES NO YES
GUI command with criteria
Statistics management at file YES YES NO
level
Statistics management at CDR YES NO YES
level

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 24/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

FUNCTION CDR File Collector Charging

Collector Gateway
for UMTS/GPRS
packet networks
Size parameter setting of files YES NO YES
in output
Historical processing of CDRs NO YES NO
files collected from end to end
Filtering of CDRs in output YES NO YES
Support of several OSS YES YES YES
applications
Simultaneous transfers to YES YES YES
various OSS applications
Same information sent to YES YES YES
several OSS applications
Change of format YES NO YES
Storage of files or blocks for YES YES YES
legal purpose
Support of different protocols YES YES YES
for output to OSS (FTP, FTAM
servers or client, Remote
Copy, etc.)
Connection on LAN/ IP YES YES YES
Network to access the OSS
applications
Parameters configuration by YES YES YES
GUI
Network topological lay out YES YES YES
management
Applicative alarms YES YES YES
management
Storage capacity YES YES YES
management
Proprietary Hardware NO NO NO
platform
Different user management YES YES YES

 Alcatel 2002 Reference Edition Page

3AT 06724 AAAA DEZZA V01 01 25/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization
 A1338

B. APPENDIX - A1338 REFERENCES

END OF DOCUMENT
 Alcatel 2002 Reference Edition Page
3AT 06724 AAAA DEZZA V01 01 26/26
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization