back

Information
AccessIntegrator V3.3

UMN:TED

A50010-T3-B100-1-7618
UMN:TED Information
AccessIntegrator V3.3

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

Copyright (C) Siemens AG 1998

Issued by the Information and Communication Networks Group

Hofmannstraße 51
D-81359 München

Technical modifications possible.

Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

AD – 2 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1 Manual concept and target groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 Manual structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.3 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

2 TMN architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Scope of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1.1 Main features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

3 Operating concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 Multi user system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Single user system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.3 Local Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.4 Connection to the Access Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.5 Integration with an external management system . . . . . . . . . . . . . . . . . . . 3-5
3.6 Hardware and software platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

4 Graphical user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 General features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Network views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2.1 Display of status information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.3 Object-oriented approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.4 Help system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

5 Management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5.1 Network management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.1 Automatic network capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.2 Network Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.3 Path, Service and Subscriber management . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1.4 Air connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.1.5 Subscriber line test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5.1.6 Mass provisioning of subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5.2 Element management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.2.1 Security management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.2.2 Fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.2.3 Configuration management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.2.3.1 Configuring network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.2.3.2 Software management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.2.3.3 Inventory data retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.2.4 Performance management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.2.5 Traffic measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.3 Basic functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.3.1 Data backup and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.3.2 Consistency check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.3.3 Time scheduled jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.3.4 Creating log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.3.5 Media interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

A50010-T3-B100-1-7618 AD – 3
UMN:TED Information
AccessIntegrator V3.3

6 Software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

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

AD – 4 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

Illustrations
Fig. 2.1 Position of ACI within the Management Layers . . . . . . . . . . . . . . . . . . . 2-1
Fig. 2.2 AccessIntegrator’s field of application . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Fig. 3.1 ACI as a multi user system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Fig. 3.2 LAN / WAN topology with routers and RAS . . . . . . . . . . . . . . . . . . . . . . 3-2
Fig. 3.3 ACI as a single user system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Fig. 3.4 Example of a SISA-DCN with several hierarchical levels . . . . . . . . . . . 3-4
Fig. 4.1 ACI main window with all views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Fig. 6.1 The ACI software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

A50010-T3-B100-1-7618 AD – 5
UMN:TED Information
AccessIntegrator V3.3

AD – 6 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

1 Introduction
This chapter provides an overview of
• the O.N.M.S AccessIntegrator documentation and the various target groups
(O.N.M.S = Optimized Network Management System)
• the manual concept
• the notational conventions used.

1.1 Manual concept and target groups

The AccessIntegrator documentation describes how to use the networks managed by
AccessIntegrator. It consists of the following manuals:
– Technical Description (TED)
– Operating Manual (OMN)
– System Administration Manual (ADMN)
– Installation Manual (IMN).
Each of these manuals is intended for a particular target group as described below.
TED The System Description is aimed at those with a general interest in AccessIntegrator. It
contains an introduction on how to manage Access Networks using AccessIntegrator,
describes the system architecture, and provides an overview of the functionality of
AccessIntegrator.
OMN The Operating Manual is intended for those involved in the configuration and monitoring
of Access Networks and network elements. It contains step-by-step instructions on how
to perform the various configuration and monitoring tasks.
ADMN The System Administration Manual is intended for those responsible for ensuring the
smooth operation of the AccessIntegrator components. It describes the security mech-
anisms available and explains how to use them (e.g. data backup and restore).
IMN The Installation Manual is aimed at those responsible for installing the AccessIntegrator
software and configuring the underlying system. It contains detailed instructions on how
to install the individual AccessIntegrator components.

1.2 Manual structure

All of the AccessIntegrator manuals listed above have basically the same structure.
They contain:
– a table of contents
– a list of illustrations
– a list of tables
– an overview of the entire manual
– the specific description
– a list of abbreviations.

A50010-T3-B100-1-7618 1–1
UMN:TED Information
AccessIntegrator V3.3

1.3 Notational conventions

The following notational conventions are used in all the manuals:

Notational convention Meaning

Courier Input and output

Example: Enter LOCAL for the server name
Command not found

Italics Variables
Example: name can be up to eight characters long.
Bold Special emphasis
Example: This name must not be deleted.

“Quotes” User interface labels (e.g. windows, menu items, buttons)

Example: Click the “OK” button.
Select the “File” menu.

<Courier> Keyboard shortcuts

Example: <CTRL> <ALT>+<ESC>

→ Menu sequences
Example: “File” → “Exit”
Additional information
i
Warnings at critical points in the procedure
!

Tab. 1.1 Notational conventions

1–2 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

2 TMN architecture
Siemens O.N.M.S (Optimized Network Management System) offers management solu-
tions for all types of telecommunications networks. It supports all functional layers, from
the Element Management Layer through to the Business Management Layer in accor-
dance with the standard ITU-T M.3010.
AccessIntegrator (ACI) is a part of this O.N.M.S. concept and serves as a management
system for Access Networks connected by means of an QD2 management interface. It
supplies management functions for the Element Management and the Network
Management Layers.

Support of the management of the

Business Management Layer whole enterprise

Service assurance/provisioning and

Service Management Layer
billing

Planning surveillance and configura-

Network Management Layer
Access tion of network resources
Integrator
Configuration and control of
Element Management Layer individual network elements

Fig. 2.1 Position of ACI within the Management Layers

The following areas are supported in accordance with the standard ITU-T M.3010:
Network management
• Network presentation
• Path and service management
• Air connection management.
Element management
• Fault management
• Configuration management
• Performance management
• Security management.

2.1 Scope of application

You can administer and monitor various network technologies, such as FastLink, FMX2,
DECTlink, CDMAlink and WideLink, using ACI (see Fig. 2.2).
The Access Networks are connected through a Data Communications Network (DCN),
which transfers management information from ACI to the network elements and vice
versa.
The AccessIntegrator software is based on a client/server architecture allowing for
distributed management and continuous adjustment to the needs of constantly growing
networks.

A50010-T3-B100-1-7618 2–1
UMN:TED Information
AccessIntegrator V3.3

ACI Client ACI Client ACI Client

LAN

ACI Server ACI Server

QD2 QD2

Data Communications Network

FastLink/FMX2 DECTlink CDMAlink WideLink

Fig. 2.2 AccessIntegrator’s field of application

2.1.1 Main features

AccessIntegrator offers network providers the following advantages:
• Integration of different network element technologies
• Standard user interface for all connected Access Networks
• Comprehensive functionality in accordance with the ITU-T M.3010 standard for the
Network Management Layer and the Element Management Layer
• Runs on standard PCs
• Inexpensive solution both for large and small networks.

2–2 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

3 Operating concept
AccessIntegrator is designed on the basis of a client/server architecture and can be
used as a:
• Multi user system
• Single user system
• Local Craft Terminal.

3.1 Multi user system

In a multi user system, you can split up the various tasks among several users who can
work simultaneously at different PCs. A multi user system can consist of several server
and client PCs. As many as 20 clients can be connected to each server. The server PCs
provide the connection to the Access Network. Each ACI server has a database which
contains the network data.

Client 1 Client 2 Client n

LAN

Server 1 Server 2

Windows NT domains

QD2 QD2

DCN DCN

Fig. 3.1 ACI as a multi user system

The client and server PCs are connected to one another through a LAN. When
AccessIntegrator is started, each client selects the server to which a connection is to be
established.
Client/server connections can cover large distances using a Wide Area Network (WAN).
In this case, the connection is established using X.25, ISDN, or a modem (19.2 Kbps)
using routers or the Windows NT Remote Access Server (RAS). Fig. 3.2 shows a
sample topology using both options.

A50010-T3-B100-1-7618 3–1
UMN:TED Information
AccessIntegrator V3.3

Router/Bridge
TCP/IP over WAN
64 Kbps

RAS
Windows NT
Remote access
over telephone,
X.25, ISDN lines

Modem

QD2 QD2 Remote

Terminals

DCN DCN

based on: Standard PCs

Windows NT
Versant DB DCN Data Communications Network
DB Database

Fig. 3.2 LAN / WAN topology with routers and RAS

3.2 Single user system

Small networks, such as FastLink domains, can be administered using a single user
system. All tasks are carried out from a single PC, which is equipped both with the server
and the client functionalities. It also contains the central database.

Client & Server

QD2

DCN

Fig. 3.3 ACI as a single user system

3–2 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

3.3 Local Craft Terminal

The Local Craft Terminal (LCT) is a special form of single user system. It consists of a
portable PC used for on-site commissioning and maintenance of network elements.
The LCT can be connected to any SISA cluster controllers or to the network elements
themselves through the F port. Compared with the central single user system, the func-
tionality provided on the LCT is considerably restricted. Its graphical user interface,
however, is absolutely identical to that of the central system, so users can carry out on-
site maintenance work with a user interface that is completely familiar to them. Conse-
quently, the LCT does not require an operating manual of its own.

3.4 Connection to the Access Network

ACI and the network elements communicate through the QD2 interface. The network
elements are linked to the ACI server using a serial QD2 bus.
The serial QD2 bus with a master and up to 30 slaves is the basic structure which can
be cascaded to create hierarchical network structures.
Siemens cluster controllers from the SISA-GK product family are used for cascading.
ACI is connected to the top-level cluster controller. The cluster controllers below it form
the network hierarchy and transport telegrams from and to the network elements of the
next branch. This network structure is called the SISA DCN (Data Communications
Network).
The SISA cluster controllers provide ports allowing AccessIntegrator to be connected to
various other existing transport systems:
• V.11 synchronous / asynchronous (64 Kbps and 9.6 Kbps)
• V.24/28 synchronous (9.6 Kbps)
• G.703 synchronous (64 Kbps).
Each SISA cluster controller has three ports, one master port and two slave ports. Each
port can be configured either as a QD2 or a QD2* port (see Fig. 3.4). The SISA cluster
controller polls the network elements connected to the QD2 bus or the next SISA cluster
controller (QD2* port) through the master port.
Apart from the SISA cluster controllers, SISA alarm collectors (SISA ASAs) with special
alarm contacts can also be used in the SISA DCN. Alarms indicating open cabinet doors
or power supply failures can thus be reported to ACI.
Data communications between ACI and the network elements use the QD2 protocol in
both directions. The protocol meets the ITU-T standard for layers 1 (RS485) and
2 (HDLC).
The physical connection between ACI and the network is implemented by means of a
QD2 board equipped with eight DCN ports. A QD2 hierarchy can be connected to each
port.

A50010-T3-B100-1-7618 3–3
UMN:TED Information
AccessIntegrator V3.3

ACI

1 Local QD2 bus 30

SISA-GK SISA-GK SISA-GK SISA-ASA NE

QD2* QD2*
64 Kbps V.11 synchronous 64 Kbps V.11 asynchronous

SISA-GK SISA-GK
QD2 QD2

SISA-GK SISA-ASA NE SISA-GK SISA-GK SISA-ASA NE

QD2* QD2 QD2

SISA-GK
QD2 QD2 QD2*
Layer 7: AWP01 AWP01
Layer 4-6: not used not used
SISA-GK SISA-GK SISA-ASA NE Layer 3: VMP01 VMP01
Layer 2: HDLC HDLC
Layer 1: RS 485 G.703/V.11 (asyn./syn.)

QD2*

SISA-GK
QD2

NE NE NE NE

Fig. 3.4 Example of a SISA-DCN with several hierarchical levels

3–4 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

3.5 Integration with an external management system

You can link the AccessIntegrator to an external management system through an
Application Programmer’s Interface (API) in the form of an SNMP interface on the ACI
server. The SNMPv1 protocol is used for data communications.
The master agent of the external management system communicates with three
subagents in ACI according to the SNMP management model. The subagents can
access the following functions:

Alarm display - subagent ALARMING

Using the alarm interface, the external management system can:
• Receive all alarms sent by the network elements in the form of SNMP traps
• Use the ACI Fault Management filter options to filter out certain alarms
• Request the global alarm list for active alarms in order to determine the network
status. All alarms in the list are sent to the external management system as a
sequence of traps.

Subscriber line test - subagent SUBSCRIBER LINE TEST

Using this interface, the external management system can:
• Configure the automatic test program which performs the subscriber line test
(possible for FastLink network elements of type AMX which are connected to a
measurement unit)
• Define threshold values for the test
• Query the result of automatic tests
• Perform manual line tests.

Connection monitoring - subagent WATCHDOG

You can monitor the connection between ACI and the management system. ACI sends
traps at regular intervals and thus lets the management system quickly detect connec-
tion breakdowns.
The SNMP interface is not included in the standard ACI software.

3.6 Hardware and software platforms

AccessIntegrator can be installed on standard PCs running Windows NT V4.0 with the
current Service Pack.
Refer to the Installation Manual for details on which type of PC you need for a specific
situation.

A50010-T3-B100-1-7618 3–5
UMN:TED Information
AccessIntegrator V3.3

3–6 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

4 Graphical user interface

4.1 General features

The AccessIntegrator graphical user interface is based on Windows NT. Since this oper-
ating system is widely used, most users will be familiar with its concepts. AccessInte-
grator was developed in accordance with the Microsoft User Interface Styleguide for
Windows NT, and offers the same look and feel.
Access Networks are administered and monitored in a graphical presentation which
constantly provides the user with the latest status information. Any executable functions
are available in the main menu below the title bar in the main window of ACI. Functions
required frequently are also contained in the tool bar and in the context-sensitive menus.
Any user entries, such as requests for system output, are made in dialog boxes. System
messages, such as warnings or error messages, always appear in message boxes that
you have to acknowledge.

4.2 Network views

ACI offers various views of the Access Network. The views simultaneously present
different hierarchical levels. The following views will give you a comprehensive overview
of the Access Network:

Port View
This view displays the eight ports of the QD2 board, and is used to select a particular
SISA-DNC or Access Network.

DCN Tree
This view displays the network in a hierarchical structure in accordance with the SISA
addressing scheme, where the leaves of the tree represent the QD2 network elements.
All network elements within one Access domain are detected automatically by the ACI
during server startup and displayed in the DCN Tree. A separate DCN Tree is generated
for each port used on the QD2 board (DCNPORT#1... #8). The system presents both
the SISA elements and the QD2 network elements. The icons for the different network
element types are predefined in ACI.

Network Map
This view displays the actual network topology without the SISA elements. The Network
Map is generated by the user with the aid of the Network Editor. It is based on the DCN
Trees which are generated automatically and contain all existing network elements.
Network elements can be copied from the DCN Tree to the Network Map and placed
wherever required using drag and drop. In contrast to the DCN Tree, the Network Map
can also contain connections between individual network elements.
Depending on the size of a network and on its geographical position, network elements
can be grouped to form subnetworks. Any number of subnetworks can be generated for
a map and nested. This allows large networks to be presented in an hierarchical struc-
ture.

A50010-T3-B100-1-7618 4–1
UMN:TED Information
AccessIntegrator V3.3

Equipment View
This view displays the hardware components of a network element, i.e. the current
module configuration. Each module is labeled with the module name and the slot
number. ACI automatically detects any changes made to the configuration, for instance
when a new module is inserted or a module is removed, and the presentation in the
Equipment View is updated accordingly.

Functional View
This view shows the logical structure of the network elements. Instead of hardware units
(shelf, modules), it displays functional units such as ports, multiplexers, or cross connec-
tions. All functions are represented by the same symbol and labeled appropriately.
Compared to the Equipment View, the Functional View provides a more uniform over-
view. While the Equipment View is continually changing as the module configuration is
changed, the Functional View remains the same.

4.2.1 Display of status information

If network elements or their components undergo a state transition, this is signaled in all
views. The DCN Tree and Network Map propagate the status information to all hierar-
chical levels, thus allowing for efficient network monitoring.
ACI distinguishes between the following states:
• Alarm severity
Alarms received by the network elements are signaled in the views by color-coding
the icons displayed. Different colors are used depending on the alarm severity. Also
the alarm status Acknowledged is displayed by color-coding.
• Operating mode
The user can influence the operating mode. The user can, for instance, disable a
network element or its components for maintenance purposes. Network elements in
the operating mode In Maintenance are marked with a wrench icon. Network
elements in this state do not send alarms to ACI.
• Operational state
This state indicates whether or not a network element can be accessed by ACI. As
soon as ACI detects an interruption of the connection to a network element, it marks
the appropriate icon with a red cross in the display.
• Synchronization state
If an individual network element has been selected in the view, the synchronization
state of the element appears in the status bar of the ACI main window. This provides
information on the synchronization between the object in the database (MIB) and the
physical network element.

4–2 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

Fig. 4.1 ACI main window with all views

4.3 Object-oriented approach

Besides indicating results, the graphical presentation of the network status also allows
for an object-oriented approach to tasks in hand. You select the object for which you
wish to carry out an operation and the system displays the operations allowed for that
object.
This method has the following advantages:
– the user does not need to know from the outset which operations may be carried out
for a specific object
– access to the objects and the connected operations is controlled through user
profiles (user roles). Only the operations that a user is allowed to carry out are actu-
ally displayed.
– the user can access context-sensitive help through the help system. ACI only
provides help texts on the current operation step.
ACI supports multiple object selection for several functions, which makes command
execution much more efficient.

A50010-T3-B100-1-7618 4–3
UMN:TED Information
AccessIntegrator V3.3

4.4 Help system

ACI’s on-line help system supports the user with comprehensive information on the
tasks in hand. Help texts on specific tasks contain step-by-step instructions and subject-
specific information. There is also context-sensitive help, which users can call up from
a dialog box using the “Help” button.

4–4 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

5 Management functions
In accordance with the ITU-T M.3010 standard, AccessIntegrator offers functions for the
Network Management Layer and the Element Management Layer. Furthermore, it
supplies a series of basic functions which are described briefly below.

5.1 Network management

Network management covers the presentation of the entire network including the
Network Editor by means of which the Network Map can be generated. Path, service
and subscriber management also belong to the network management functions, as
does air connection management.

5.1.1 Automatic network capture

Since the bus structure of the SISA DCN defines the hardware addresses, ACI can auto-
matically determine the network configuration when the system is started. QD2 tele-
grams are sent to the various network elements and the responses are evaluated. An
object is created in the database for each network element that is recognized and any
data required, such as the modules installed, network element data, and status informa-
tion are stored.
While the system starts up and the network data is collated, a dialog box containing a
series of counters displays the system’s progress. Network elements that the system
could not identify are logged. As soon as the system is up and running, the graphical
presentation of the network in the form of the DCN Tree is also complete. This view
displays the network elements in accordance with the SISA addressing scheme, which
doesn’t match the real network topology.

5.1.2 Network Editor

With the aid of the Network Editor a user can prepare a Network Map in which in oppo-
site to the DCN Tree the actual network topology is displayed.
He can:
• Generate a subnet structure (map hierarchy)
• Copy the QD2 network elements from the DCN Tree to the map using drag and drop
• Insert connections
• Add background images
• Add “labels” to the icons
• Optionally structure the map layout.

5.1.3 Path, Service and Subscriber management

The Access Network provides the subscribers with access to a variety of services. Path
Management and Service Management allows the user to create services, and the
paths switched through the Access Network to be monitored. For each created service
resp. path the current status is displayed. This status is evaluated from the status of the
resources which build up the path. If a problem occurs, the user can quickly locate the
services and subscribers affected by the problem and take the appropriate measures.

A50010-T3-B100-1-7618 5–1
UMN:TED Information
AccessIntegrator V3.3

This version of AccessIntegrator supports the following services:

PSTN wired, mobile (Public Switched Telephone Network)

ISDN wired, mobile (Integrated Services Digital Network)
64 kB, 2*64 kB
LL wired,mobile (Leased Line)
64 kB, n*64 kB, 2 MB, 34 MB
CTM mobile (Cordless Terminal Mobility)
CONF wired (Conferences)
The system supplies optimum support to the user while installing a service. Path and
Service Management automatically selects a path on the basis of the connections
included in the Network Map as soon as the starting point and the end point have been
defined. Any network resources required, such as termination points, cross connections,
or V5 ports, are automatically reserved. When defining the starting and end points the
user is only offered network elements that are valid for the service in question and that
are still free.
Establishing a service and closing it down again are both carried out in two phases.
When a service is being established it is first planned, i.e. it is merely included in the ACI
database. In the second phase, it is activated and the configuration data is loaded into
the network elements. A service can be activated at any given time. The advantage of
this concept is that the user can establish services without any disruption to the opera-
tion of the network.
When a service is deleted the process is rolled up the other way. First, the resources in
the network are deactivated and the configuration data is deleted from the network
elements, if desired. In the second phase any reservations made are canceled again,
and the service is deleted from the ACI database.
With Subscriber Management it is possible to create subscriber data and link it with
the established services or paths. In case of an error, the ACI user can quickly access
important subscriber information. The subscriber link to the installed services is not
absolutely necessary. It is also possible to use subscriber management to create a
customer data base that can also be used as desired.

Automatically establishing services

The “Learn Service” function permits existing physical paths in the network to be recog-
nized and automatically installed in path and service management, i.e. to be transferred
into the ACI database. The desired termination points of the path as well as the type of
service must be provided. This procedure can also be prompted from service manage-
ment as well as via the tool MASSPROVI within the context of a mass provisioning of
subscribers.

5.1.4 Air connection management

DECTlink and CDMAlink subscribers are registered in the RDU (Radio Distribution
Unit). The subscribers have to register themselves by entering an authorization code at
a time specified by the ACI operator.
When a subscriber has registered successfully, the RDU issues an internal event report.
Connection attempts with the wrong authorization code are reported to AccessIntegrator
with an alarm.

5–2 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

The RDU subscriber data is also stored on the ACI server and can be restored from
there, if needed.
Air Connection Management also provides the user with status information. The Authen-
tication Status can be displayed as well as all detached subcribers.

5.1.5 Subscriber line test

In FastLink systems, the quality of the connected multiplexer subscriber lines can be
tested using special measurement units (MEU). The test program can be adjusted to
given requirements, and can test both incoming and outgoing connections.
Individual subscriber lines can be measured manually. The results of the test (measure-
ment data) are displayed in a dialog box. If several lines are to be tested, the test has to
be started automatically. The test program writes a log file containing the faulty lines or
lines that could not be measured. The user can view the test results at any time. The
automatic test program can be run at intervals as often as required.

5.1.6 Mass provisioning of subscribers

Connecting subscribers on a massive scale is more efficient with the MASSPROVI tool.
The requirements include a connection to an EWSD local exchange via a V5 interface
(V5.1 or V5.2).
The telephone number of the AN subscriber is first entered in the EWSD local exchange
(LE). Thereafter, the subscriber or telephone number is assigned in the ACI database.
With MASSPROVI, this subscriber line enabling is automated for the ACI. According to
EWSD commands (MML) as well as AN design data (SISA network) a configuration file
that can be written into in the ACI database is generated. Plausibilty checks guarantee
data consistency between the LE and the AN.
Furthermore, detailed documentation of the access network including subscriber and V5
information, which supports administration or fault clearance is generated.
The most important advantage of MASSPROVI lies in a decreased commissioning pe-
riod and thereby a more rapid return of customer revenues, as subscribers can be more
quickly switched on as opposed to manual commissioning.
The tool can be put into operation for DECTlink and FastLink subscribers, however all
configuration scenarios are not yet supported.

A50010-T3-B100-1-7618 5–3
UMN:TED Information
AccessIntegrator V3.3

5.2 Element management

The Element Management layer covers security management, fault management,
configuration management and performance management

5.2.1 Security management

AccessIntegrator’s Security Management offers the system administrator a flexible
concept for defining and managing user profiles (user roles).
Access to ACI functions is managed with authorization classes. The ACI authorization
classes are linked with global Windows NT user groups. If an ACI authorization class is
assigned to a global NT user group, all NT user IDs in the global group have access to
specific ACI functions.
This concept means that a Windows NT server responsible for managing user accounts
is configured as the primary domain controller within the domain.
Each ACI user is granted authorizations by means of
• Windows NT authorization (user name + password)
• Membership of a global group
• Assignment of an ACI authorization class.
AccessIntegrator distinguishes between six authorization classes that already contain
default entries and that need to be assigned to global Windows NT groups when the
system is installed. The system administrator can alter the function scope of the autho-
rization classes. Functions can thus be permitted or prohibited, and user profiles can be
adapted individually.

5.2.2 Fault management

Fault Management controls the alarm states of all network elements, alarm presentation
in the graphical network image, and logs any alarms it receives in a global alarm list.
Four categories of alarm severity have been defined in accordance with the ITU-T X.733
standard: critical, major, minor, warning. Each category has a color code
assigned to it.
Any alarms received are included in the global alarm list. The affected objects, e.g.
modules, functional units, or network elements, appear in the graphical user interface in
the color that corresponds to the degree of severity of the alarm issued for them. If
several alarms are issued for a single object, it is assigned the color of the alarm with
the highest degree of severity.
In hierarchical network maps the alarms are propagated to all hierarchy levels. If a crit-
ical alarm is issued for a module in the bottom-most level of a network, the subnet icon
in the top hierarchy level will also appear red.
The global alarm list is updated continuously. Alarms that have been canceled (status =
off) are deleted from the list. The list always reflects the current status of the network.
Alarms can be logged in order to facilitate the location of faults and for statistical
purposes. Both alarms that are on and those that are off are logged. This allows you
to determine even after some time, how long a certain alarm was active in the network.
Any active alarm can be acknowledged by the user. This, too, is presented graphically.
Via the media interface it is possible to signal alarms also acoustically.

5–4 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

5.2.3 Configuration management

Configuration Management comprises the following main tasks:
• Configuring network elements
• Software management
• Inventory data retrieval.

5.2.3.1 Configuring network elements

The configuration data is split up into
a) general parameters:
– date and time
– user data
– alarm configuration data
– resetting modules
b) specific parameters, e.g.:
– switching cross connections
– interface parameters for V5.1 / V5.2
– locking / unlocking subscriber ports
c) test parameters:
– test loops
– connections
This data is entered or output in special dialog boxes. The network elements are config-
ured upon commissioning. With the exception of tests and maintenance tasks, no further
intervention is required as a rule while the system is up and running. If a faulty network
element or module needs to be replaced, the configuration data can be recovered from
the backup.

5.2.3.2 Software management

Software management comprises APS management (APS = Application Programs
Software) and backup and recovery of network element data.

APS management
In addition to the configuration data, each network element requires specific software in
order to run. This software is loaded onto the network elements or modules when the
Access Network is installed and commissioned. The term APS covers all software
specific to the network elements that is needed for a certain version of an Access
Network.
The APS version of a network consists of a stock list and the associated individual pro-
grams (P-APS = partial APS). Each network element type has its own program. The
entire APS software is stored in a special directory on the ACI server.

A50010-T3-B100-1-7618 5–5
UMN:TED Information
AccessIntegrator V3.3

AccessIntegrator supports the user in the following tasks:

• Managing the APS versions on the ACI server (insert, delete)
• Checking the software versions loaded in the Access Network
• Downloading software for the network elements, modules, subnetworks, or the
entire network. This takes place by means of QD2 telegrams or file transfer, accord-
ingly to the type of network element.

Network element backup and recovery

For reasons of data security, the configuration data pertaining to the network elements
is also stored on the ACI server. When a network element is replaced or if a fault occurs,
the configuration data can be restored on the network elements from ACI.
A backup function allows the network element data to be backed up to the hard disk of
the ACI server. The Restore function is used to load the data on to the network elements
again, if necessary. This takes place by means of QD2 telegrams or file transfer.

5.2.3.3 Inventory data retrieval

“Inventory data” is any data, such as device names, device types, geographical location,
software version, and the information on the labels of modules.
The ACI user can output this data directly on the screen for individual network elements
or modules. If data relating to several network elements or the entire network is to be
retrieved, this data can be saved automatically to a file. For this purpose, the user must
define a file name and enter additional information. The automatic retrieval process polls
the network elements sequentially in order to avoid a network overload.
The retrieved data is stored in ASCII format and can be edited using external tools. For
instance, it can be used as the basis for hardware/firmware modifications.

5.2.4 Performance management

AccessIntegrator collects data on the performance of the network in accordance with the
standards ITU-T G.821 and. G.826.
The measurement points in the network elements can be activated and deactivated indi-
vidually. The counter levels are stored every 15 minutes (15 min record) or every
24 hours (24 hr record). The storage capacity in the network elements can be set to a
maximum 100 data records for 15 minute counters and to 30 data records for the
24 hour counter.
The performance data can be displayed in a table on your screen, or stored in a log file.

5.2.5 Traffic measurement

For DECTlink and CDMAlink networks, AccessIntegrator offers the option of collating
traffic measurement data and presenting it graphically. The results of traffic measure-
ments form the basis for planning network extensions and help detect capacity bottle-
necks.

5–6 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

5.3 Basic functions

5.3.1 Data backup and recovery

ACI supports the system administrator in the following backup and recovery routines:
• Backup and recovery of the ACI database
• Database migration during software upgrades
• Backup and recovery of network element data (configuration)
• Backup and recovery of the subscriber data (DECTlink, CDMAlink).

5.3.2 Consistency check

If the connection to the network is interrupted, e.g. due to line breakdowns, the consis-
tency of the data in the ACI database can no longer be guaranteed. ACI automatically
performs a consistency check immediately the connection to the network is established
again. All network elements affected are analyzed and their current status is transferred
to the database. If any differences are encountered, the network presentation is updated
accordingly.
The user can also activate a manual consistency check at any time, if the displayed
network status does not seem to reflect its actual status. The check can be carried out
for individual network elements or subnetworks, or for the entire network.

5.3.3 Time scheduled jobs

A universal scheduler allows the user to issue time scheduled jobs. The jobs can be
viewed, changed or deleted in the relevant dialog box.

5.3.4 Creating log files

The Log Administration Tool allows the user to create log files for the following:
• alarms and events in the Access Network
• ACI-internal events
• Performance data
• Test data from subscriber line tests.
Any log files that are created, are stored on the hard disk of the ACI server. The size of
the log files depends on the number of objects selected. A log file may contain, for
instance the alarms from a single network element or from the entire network.
The user can limit the size of a file. If the size is not limited, the system will carry on
logging data until the capacity of the hard disk has been used up completely. If the user
defines a file size, what action the program takes when the file is full can also be spec-
ified. Logging is either terminated or the program overwrites the contents of the file,
starting with the first record (wrap around).

A50010-T3-B100-1-7618 5–7
UMN:TED Information
AccessIntegrator V3.3

5.3.5 Media interface

Via the media interface, the ACI user can configure a signal tone to indicate all alarms
in fault management as well as an internal system event message Disconnected NE.
The signaling is enabled either through a sound card (if available) or a beep tone. The
alarm or event signaling can be filtered according to severity or NE type.
The interface is configurable and is accessible from any client PC. The configuration
data is entered in the Windows NT registry, thereby enabling access for each individual
ACI user.

5–8 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

6 Software architecture
The AccessIntegrator software is object-oriented in design, and therefore allows object-
oriented access to all functions from the graphical user interface. The object-oriented
database system Versant was chosen for data storage.
The AccessIntegrator consists of several processes. Fig. 6.1 shows how these proc-
esses are distributed within the client/server architecture.

CLIENT Workstation Application

WSAP

Operating System Windows NT

SERVER

Workstation Application
WSAP (optional)

API Application
(optional)

Mediation Application ACI Toolset

MED

Database System (Versant)

Operating System Windows NT

DCN Server (QD2)

Fig. 6.1 The ACI software architecture

A50010-T3-B100-1-7618 6–1
UMN:TED Information
AccessIntegrator V3.3

The individual processes perform the following tasks:

• Workstation Application (WSAP)
This client process provides the graphical user interface. It is based on the Microsoft
Foundation Classes (MFC), from which the AccessIntegrator classes were derived.
• Mediation Application (MED)
This is the server process, responsible for internal communication and administra-
tion of the database. It controls all communication between the WSAP and the
Access Network.
• API Application
The Application Programmer’s Interface allows connection to other TMN applica-
tions. The API process is a special client of the MED process, and is served in the
same way as a WSAP process.
• Database (Versant)
The object-oriented database stores network data (network model), the Network
Map data, subscriber data and data on path, service and subscriber management.
• DCN server
The DCN server forms the connection to the Access Network (QD2 interface), and
is responsible for data communications in both directions.

The ACI Toolset offers various tools, such as the tool for evaluating traffic data (PDPT).

6–2 A50010-T3-B100-1-7618
Information UMN:TED
AccessIntegrator V3.3

7 Abbreviations
ACI AccessIntegrator
AMX Access Multiplexer
API Application Programmer’s Interface
APS Application Programs System
ASA Alarm Collector
AWP01 Application protocol 01
CDMA Code Division Multiple Access
CONF Conferences
CTM Cordless Terminal Mobility
DCN Data Communications Network
DECT Digital Enhanced Cordless Telecommuni-
cations
FMX Flexible Mutiplexer
FMX2
HDLC High Level Data Link Control
ISDN Integrated Services Data Network
ITU-T International Telecommunications Union -
Telecommunications Standardization
Sector
LAN Local Area Network
LCT Local Craft Terminal
LL Leased Line
MED Mediation Process
O.N.M.S Optimized Network Management System
PSTN Public Switched Telephone Network
QD2 QD2 Interface
RAS Remote Access Server
RDU Radio Distribution Unit
SISA Supervision and Information System for
Local and Remote Areas
SISA-GK Physical SISA DCN Node
SNMP Simple Network Management Protocol
TMN Telecommunications Management Network
VMP01 Switching protocol 01
WAN Wide Area Network
WSAP Workstation Application Process

A50010-T3-B100-1-7618 AP – 1
UMN:TED Information
AccessIntegrator V3.3

AP – 2 A50010-T3-B100-1-7618