CCRROOSSSSCROSS- CROSS---DOMAIN · PDF fileAlcatel-Lucent 3DN 00801 IAAA DEZZA ... S12 A100 0S12 A100 0S12 A100 0 S12 Local Operations: PC With Browser Data Network XMC server(s) -

Created by Neevia Document Converter trial version

1300 XMC PRODUCT DESCRIPTION RELEASE 8.0

Alcatel-Lucent 3DN 00801 IAAA DEZZA

Date: December 2010

1/44

All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authoriza-

tion

PRODUCT DESCRIPTION

CROSSCROSSCROSSCROSS----DOMAIN MANAGDOMAIN MANAGDOMAIN MANAGDOMAIN MANAGEEEEMENT CENTERMENT CENTERMENT CENTERMENT CENTER

ALCATELALCATELALCATELALCATEL----LUCENT 1300 XMCLUCENT 1300 XMCLUCENT 1300 XMCLUCENT 1300 XMC

PRODUCT RELEASE RPRODUCT RELEASE RPRODUCT RELEASE RPRODUCT RELEASE R8888....0000

Edition 1.0

#3DR20003QMW

WPT

AHF0

2

Created by Neevia Document Converter trial version http://www.neevia.com

http://www.neevia.com



Date: December 2010

2/44


tion

SUMMARY

SUMMARY.....................................................................................................................2

LIST OF FIGURES...........................................................................................................5

LIST OF TABLES.............................................................................................................6

1 INTRODUCTION ....................................................................................................7

1.1 KEY FEATURES ..................................................................................................... 8

2 A1300 XMC FUNCTIONAL DESCRIPTION..............................................................9

2.1 FEATURE LIST ....................................................................................................... 9

2.2 MANAGED NETWORKS ..................................................................................... 10

3 A1300 XMC FEATURE DESCRIPTION .................................................................. 12

3.1 TOPOLOGY MANAGEMENT.............................................................................. 13

3.2 NETWORK SUPERVISION ................................................................................... 15

3.3 FAULT MANAGEMENT ....................................................................................... 16 3.3.1 Alarm handling ........................................................................................ 17 3.3.2 Alarm reporting and logging .................................................................... 18

3.4 SECURITY MANAGEMENT.................................................................................. 19 3.4.1 Main functionalities................................................................................... 19

3.5 LOG MANAGEMENT.......................................................................................... 20 3.5.1 NE Logs ................................................................................................... 20 3.5.2 XMC Logs................................................................................................. 20 3.5.3 Log Browsing............................................................................................ 21

3.6 JOB MANAGEMENT........................................................................................... 21

3.7 MULTI NE SCRIPTING......................................................................................... 21

3.8 NE SOFTWARE MANAGEMENT .......................................................................... 22 3.8.1 NE Software upgrade: .............................................................................. 22 3.8.2 NE backup/IMPORT: ................................................................................ 22

3.9 PERFORMANCE MANAGEMENT......................................................................... 24

3.10 QOS MANAGEMENT ......................................................................................... 24

3.11 NAVIGATION..................................................................................................... 24

3.12 CONFIGURATION MANAGEMENT .................................................................... 24

3.13 EQUIPMENT MANAGEMENT.............................................................................. 25

3.14 EXTERNAL INTERFACES ...................................................................................... 25 3.14.1 3GPP NBI ................................................................................................. 25 3.14.2 SNMP NBI ................................................................................................ 25 3.14.3 XML/SOAP NBI......................................................................................... 25

3.15 ON LINE DOCUMENTATION............................................................................. 26





Date: December 2010

3/44


tion

3.16 XMC PLATFORM FUNCTIONS............................................................................ 26 3.16.1 XMC platform backup/restore................................................................... 26 3.16.2 XMC platform monitoring ......................................................................... 26 3.16.3 XMC Health monitoring ............................................................................ 26 3.16.4 Geographical redundancy ........................................................................ 27 3.16.5 Time management ................................................................................... 27

3.17 NETWORK MANAGEMENT................................................................................. 27 3.17.1 RA/RNC management .............................................................................. 27

4 XMC OVERALL ARCHITECTURE ........................................................................... 28

4.1 HARDWARE ARCHITECTURE............................................................................... 29 4.1.1 XMC server............................................................................................... 30

4.2 SOFTWARE ARCHITECTURE ............................................................................... 30 4.2.1 General concept....................................................................................... 30 4.2.2 detailed software architecture ................................................................... 31

5 TECHNICAL DESCRIPTION.................................................................................. 33

5.1 PROTOCOLS AND INTERFACES......................................................................... 33 5.1.1 interface between XMC and NEs ............................................................... 33 5.1.2 interface between XMC and other OMCS .................................................. 34 5.1.3 Interfaces between XMC and OSS ............................................................. 34

5.2 XMC RESILIENCE................................................................................................ 34 5.2.1 Platform Resilience.................................................................................... 34 5.2.2 MTBF System Availability........................................................................... 35

5.3 DISASTER RECOVERY ......................................................................................... 35 Ø Different scenarios.................................................................................... 35 Ø Data integrity............................................................................................ 35

5.4 CAPACITY .......................................................................................................... 35

5.5 HARDWARE CONFIGURATION .......................................................................... 37 5.5.1 Current configuration ............................................................................... 37 5.5.2 Physical dimensions of each element......................................................... 38 5.5.3 Heat dissipation........................................................................................ 38 5.5.4 Power consumption .................................................................................. 38

5.6 DIAL-IN CAPABILITIES ........................................................................................ 39

5.7 SERVICE RESTORATION TIMES ........................................................................... 40 5.7.1 XMC upgrades ......................................................................................... 40 5.7.2 Integration with Network Management System .......................................... 41

5.8 INSTALLATION & COMMISSIONING REQUIREMENTS........................................ 41 5.8.1 XMC installation ....................................................................................... 41 5.8.2 Network management commissioning ...................................................... 41

6 DOCUMENTATION ............................................................................................. 42

6.1 XMC DOCUMENTATION ................................................................................... 42

6.2 OTHER RELATED DOCUMENTATION:................................................................ 43

7 GLOSSARY........................................................................................................... 44





Date: December 2010

4/44


tion





Date: December 2010

5/44


tion

LIST OF FIGURES

Figure 1: XMC key features ............................................................................................................8

Figure 2: Example of IMS management with XMC with portal on OMC-P.......................................11

Figure 3: XMC Alarm supervision panel ........................................................................................16

Figure 4: Alarm Management......................................................... Error! Bookmark not defined.

Figure 5: Topology management..................................................................................................13

Figure 6: Map view ......................................................................................................................14

Figure 7: Supervision management...............................................................................................15

Figure 8: Job management ..........................................................................................................21

Figure 9: XMC Overall Architecture...............................................................................................28

Figure 10: XMC Network Architecture ............................................................................................29

Figure 11: XMC General concept...................................................................................................31

Figure 12: XMC Software Architecture ............................................................................................32

Figure 13: Interface between XMC and NEs ...................................................................................33





Date: December 2010

6/44


tion

LIST OF TABLES

Table 1: ENMS versus XMC Capacity .............................................. Error! Bookmark not defined.

Table 2: Service Restoration Times .................................................................................................40

Table 3: XMC Documentation........................................................................................................43





Date: December 2010

7/44


tion

1 INTRODUCTION

In co-ordination with the renovation of the next generation of networks, and taking advantage of a new “distributed” management architecture, the Alcatel-Lucent-Lucent 1300 XMC Cross-Domain Man-agement Center provides the combination of field proven network management technologies issued from the switching world, with state-of-the-art packet/circuit/fixed/mobile network management appli-cations. Seamless integration of both technologies is offered by the XMC for network supervision and configuration and for 2G, 3G or mixed networks (IMS, NGN). The following domains are covered:

• Fault management,

• Configuration management,

• Performance Management,

• Security Management.





Date: December 2010

8/44


tion

1.1 KEY FEATURES

The XMC is the management system of the both Fixed Networks and Mobile Networks, covering both Circuit and Packet Switched. It encompasses the centralized element management of these NEs and some network management functions:

• Unified platform administration mechanisms;

• Single platform login and common security management mechanisms;

• Common alarm management for all the managed elements;

• Common performance management for all the managed elements;

• Common network hierarchical system view for the managed network;

• Network level configuration management functions, encompassing several elements in order to simplify configuration management tasks and to ensure configuration data coherency between the different elements ;

Figure 1: XMC key features

- Global Fault Mgt

- Staff and access control Mgt

- Open interface to

external OSS’s

Local or Remote Operator

Positions via LAN / WAN

Network & Service

External OSS

A100 0 S12 A100 0 S12

A100 0 S12 A100 0 S12

A100 0 S12 A100 0 S12

Local Operations: PC With Browser

Data Network

XMC

server(s)

- NE software & data Mgt

- Flexible and evolving

software and hardware

architecture

Core Networks

- Provisioning functions

XMC Integrated

Management Center





Date: December 2010

9/44


tion

2 A1300 XMC FUNCTIONAL DESCRIPTION

This section highlights the main function provided by XMC.

2.1 FEATURE LIST

• Management of network elements both on Fixed/Mobile networks, covering circuit and packet domains - Both domains can be managed with the same product and be used either individually or in combination in the same network

• Network topology - With animated tree /map and covering the totality of the network

• Alarm collection and centralised alarm management - X733 alarm format current and historical alarm database - Alarm filtering, automatic and manual acknowledge

• Centralised performance collection - All the observation counters concerning the complete network are centralised on the XMC - Available in XML format to external performance management tool for on-line real time traffic supervision and off-line traffic analysis functions - Files are retrieved periodically - periodicity is configurable

• Network Element counter definition depends on the type of network element - Alcatel-Lucent based NEs: list of counters is customisable by the operator - SNMP based Nes: list of counters is predefined or customizable

• Seamless navigation - Between integrated and non integrated (distributed) application - 3 tier architecture based on Java Web Start technology

• Centralised operators and profile management - Single Sign On - Operators sign-on defines the associated profile

• North Interface for OSS access - Fault, Configuration, Performance 3GPP based model (Interfaces are Corba / XML based) - SNMP interface, restricted to alarms forwarding

• Optional North Interface SOAP/XML

• NE software download and backup/restore - Centralised for the whole network





Date: December 2010

10/44


tion

• Log management - Centralized log browsing

• -Actions and events logging

• -Access to NE based log management

• XMC platform management - Online backup / restore - Full backup - Process supervision - Active / Ready hardware redundancy

• Network Management Level functions for packet domain - RA 2G/3G management between SGSNs and DNS

• Network Management Level functions

• Multi NE function scripting

• QOS package for traffic Analysis and traffic Supervision

2.2 MANAGED NETWORKS

XMC allows to manage all of Alcatel-Lucent Core Network Elements and releases, including:

• Alcatel-Lucent IMS domain nodes :

- 1440 USDS, 1430 uHSS, 8650 SDM

- 5060 WCS, 5020 CSC; 5020 MGC,

- 5450 MRF, 5450 AGCF, 5450 ISCF, 5450 IRC

- 5420 CTS, 5420 PCM, 5430 SRB, 5750 SSC, ACME SD, Vital QIP

- Gateways: 7570 MGW, 7510 TGW; 7500ABN, Reefpoint security gateway,

- 5920 PRBT

- Application servers: 5400 IAS, 5410 Presence, 5410 XDMS, 5430 Pts, 5430 IM, 5430 ECN

- IN applications: 8626 MMPR; 8610 ICC, 8615 IeCCF;

- Portal with legacy managers : OMC-P, CMC-10, CMC-12

• Packet domain U2 (through OMC PS), and U3, namely

7500 SGSN, iGGSN, 7500GGSN, Cisco Routers, DNS, A8965 CDR....





Date: December 2010

11/44


tion

• Circuit domain U1x, U2, U3, … software releases (through OMC CS) as well as NGN networks: 5060 WCS, 1430uHSS, 7570MG, A8965 CDR, routers, …

• Fixed NGN : 5060 MGC10, 7510 MGW, 7515 MGW, …

Note : For an exhaustive list of covered NE, please refer to the release note corresponding to an XMC specific release.

Figure 2: Example of IMS management with XMC with portal on OMC-P





Date: December 2010

12/44


tion

3 A1300 XMC FEATURE DESCRIPTION





Date: December 2010

13/44


tion

3.1 TOPOLOGY MANAGEMENT

Figure 3: Topology management

The “TOPO” management provides a coherent and effective supervision of the managed network.

It is responsible for the management and persistency of the list of all managed elements within the network. It stores all the static information concerning each network element, namely:

• Logical name,

• Friendly name,

• Type

• Release

• IP address

• Supervision state

• Access Control Domain

It allows the operator to create, delete or modify network topology attributes as well as exporting the data in an HTML or CSV compliant format.

The current view (Figure 3: Topology management) of the network is displayed via a tree. A “geo-graphical map view” is also available, including if needed a background picture (Figure 4: Map view).





Date: December 2010

14/44


tion

Figure 4: Map view





Date: December 2010

15/44


tion

3.2 NETWORK SUPERVISION

Figure 5: Supervision management

The Network Supervision component manages the dynamic states of the managed elements, namely:

• Supervision state - declared or supervised. Nodes connected to the Management LAN should be explicitly declared via their OAM interface ( there is no auto discovery, since on the same management LAN, several manager and nodes could co-exist)

• Communication state – state of the link between the NE and the XMC (polling frequence is Node dependant, from 40 sec to 1 minute)

• Alarm synthesis – highest severity alarm present on the NE

• Unacknowledged alarm synthesis - highest severity unacknowledged alarm present on the NE

The operator may perform some operations on the NEs such as start/stop the supervision, start/stop PM collection, backup, software upgrade, …

From this view and for a selected NE, the operator can navigate to the map, the corresponding alarm panel, the software management view or the equipment management.

The network view is customisable by operator:

• The view can be restricted to a subset of NEs using filtering facilities.

• The operator can choose the plugging(s) to be loaded





Date: December 2010

16/44


tion

3.3 FAULT MANAGEMENT

Figure 6: XMC Fault Management panel





Date: December 2010

17/44


tion

Real-time collection and display of Alarms provide early detection of network faults and improve reac-tion time to anomalies.

Fault management is provided by a generic application: CFMA (Common Fault Management Asset)

CFMA provides all services related to the handling of alarms in a distributed TMN system:

o Current alarm management;

o Alarm reporting and logging.

3.3.1 ALARM HANDLING

The X.733 alarm reports are converted into Managed Objects called current alarms. It contains both the information sent by the EML agents and additional state information reflecting the management of the alarm by the operator:

o Acknowledgement state specifies whether any operator has seen the alarm. A current alarm can be acknowledged:

§ Manually by the operator;

§ Automatically according to a user-defined severity level.

o Cleared state indicates disappearance of a fault; the EML agent notifies alarm clearance.

o Reservation state is the current alarm owned by any operator; operations on a reserved alarm can only be performed by its owner.

Current alarms are removed from the active list to the historical list in the following ways:

• Once cleared and acknowledged

• Manually, on operator request;

• On periodic purging according to user-criteria;

• On reaching storage capacity overflow criteria.

The criteria for the two automatic purging mechanisms can be based on alarm date and time and alarm type.

Current alarm information including alarm creation, change of alarm states and alarm deletion is dis-tributed through a well-defined open interface giving other TMN application easy access.

Alarm synchronisation with EML agents is done:

o Manually on operator request;

o Automatically in case of restarts of re-establishment of supervision link..

Current alarm counters present a synthesis of alarm information to the operator. Alarm counters can be defined according to user-defined criteria such as alarm severity, type, state, probable cause, af-fected network element, or a combination of these.

Alarm severity assignment profile is also an option available, allowing operator to define himself the severity level of an alarm. This feature is available only at the XMC level, and is not applicable in the embedded EML.





Date: December 2010

18/44


tion

3.3.2 ALARM REPORTING AND LOGGING

Alarm reports are received from agents through an open interface conform to the standard ITU-T X.733. The operator may consult the alarm log configuration and display and remove log records.

Each time a current alarm has been removed, an historical alarm is created. A historical alarm con-tains both the information of the current alarm and additional information describing the reason of the removal. Historical alarms can be exported to flat files in a well-defined format for post-processing by external applications for special needs (alarm statistics...).

Lists of current and historical alarms are displayed to the operator according to user-defined criteria. These criteria can be based on alarm severity, alarm type, alarm probable cause, affected network element, alarm time and date, alarm states or a combination of these.

Each alarm in the current and historical alarm lists is displayed with a colour representing its severity. The mapping between alarm severity and colours is configurable. The layout of the current and histori-cal alarm lists can be fully customised. The alarm attributes and the order in which they have to be displayed can also be specified by the user.

Filtering of the displayed alarms is provided: the operator can define and store his own default cus-tomisation of display - and alarm criteria.

Alarms can also be sent by email or SMS.





Date: December 2010

19/44


tion

3.4 SECURITY MANAGEMENT

Centralised administration of access rights and user profiles helps to protect the system against inten-tional and unintentional damage.

The Security Management component, abbreviated as CSA (Common Security Asset), focuses on the security aspects of the TMN system:

o Specify, store and distribute Access Control Information throughout the TMN system;

o Profile the Graphical User Interface of the TMN system according to user access rights;

3.4.1 MAIN FUNCTIONALITIES

Main functionality’s provided are:

o User access control:

§ Authentication based on username/password (per user basis);

§ Illicit access logging with log consultation (different criteria);

§ Inactivity period management;

§ Limited number of unsuccessful login attempt (with user lock).

o User right management:

§ Functional right management through "on duty" and "off duty" period manage-ment;

§ Work schedule: based on day/hour with default or specific user calendar.

o User sessions management

§

3.4.1.1 FUNCTIONAL ACCESS CONTROL

Access Control Information may specify:

o Users having log-in authorisation. They can be arranged in user groups having a dedicated role and access profile.

o Default profiles include: Viewer, Operator, Administrator, SEC Administrator

Access Control Information is stored in a central database and can be consulted through graphical user interface.

SEC supports User Interface profiling by building several resources according to the user access rights, these files are used to profile the user interface when this user logs in to the system. Access rights are thus reflected at user interface level by greying or removing menu items or icons.

3.4.1.2 NETWORK ACCESS DOMAIN

The XMC supports the NE access control. The target of this feature is to allow customer to define "management domain", and allowing an operator to work only on a restricted set of management domain, without visibility on the other domains.

In particular, a management domain could be a "geographical area":





Date: December 2010

20/44


tion

q An operator is allowed to manage a configured set of NEs

q The set of authorized NEs is configured by grouping already created NE together

q A NE can belong to several groups. The XMC administrator can define as many domains as needed, without any constraint; he can give them any name.

3.5 LOG MANAGEMENT

3.5.1 NE LOGS

In a distributed network management environment, the log files corresponding to actions and events on the network elements are kept on the NE itself. A NE specific application and user interface enables the user to browse and work on the NE logs. NE logs cover operator’s accesses, operations, alarms, events and errors. Log files can be backed-up locally.

In addition, centralized Log browsing is provided by XMC, for all the 5020 WCS / Tomix based/Application servers NE and for the XMC. This feature consists in collecting periodically (each hour per default) the log information on the nodes, parsing this information in order to populate a da-tabase and offer : editing / filtering / sorting / searching / exporting operations on these data. On demand collection is also provided. Log can be exported, according to several criteria, locally on a specific file system of the XMC or on an external log server. Two category of log are supported: security log and standard log. The security log contains information related to operator access and sensitive operations; the default retention for these logs is 180 days whereas the default retention period for the standard logs is 30 days. The filtering criteria are based on date, NE type, Event type, operator name, action result/progress, functional domain, error type or free text. The data collected by the XMC concerns the OAM logs only. The other trace/log files are excluded for several reasons: their content is usually reserved to Alcatel-Lucent experts. Their format is free text and can only be parsed with classical Unix tools (perl, grep,..)

3.5.2 XMC LOGS

The XMC server manages directly a set of log files keeping track of XMC operations such as:

• Access log files 2006/06/14 13:35:38 - access from FRORVD0C20959 (IP: 155.132.235.221), by user Alcatel-LucentAdmin : success

• Security log file

2006/06/14 13:28:38:sablet:SAS(0):Operator name=axadmin:LogNameCommand: SAS has started and is ready to accept incoming connections.





Date: December 2010

21/44


tion

• Administration operations (creation / deletion of NE, creation of users…), relevant internal events ( XMC services, Trap received from NEs) and scheduled actions results.

20060614112910.595Z;stateChange;INFO;Process.logim();Process.logim();MON - Monitored Process state change;EVENT.stateChange;previousState.init<>free_text.change to freezing

Logs files are circular. Log file sizes are configurable.

3.5.3 LOG BROWSING

3.6 JOB MANAGEMENT

XMC provides an internal Job/scheduler management, providing a synthesis of all the NEs Jobs launched from XMC. This addresses the Multi_NE scripting, and the operations of Software Upgrade and NE Backup. A dedicated panel shows the status of all the jobs launched.

Figure 7: Job management

3.7 MULTI NE SCRIPTING





Date: December 2010

22/44


tion

The XMC provides a centralized management for Multi NE scripting. This feature allows to:

o Open Corba/Python session for Tomix based NE for access to OAM services: access con-trol, hardware management, SS7management, performance management, log manage-ment, version change, applicative interfaces.

o Open CLI Session for A5020 WCS nodes: monitoring and provisioning domain or other CLI based nodes

o SSH/Perl scripts for any UNIX basedNEs o Launch immediate and differed script execution on a group of nodes of same type o Store results of script execution in results files o Handle script job state

3.8 NE SOFTWARE MANAGEMENT

This application enables the operator to manage and control the network elements software releases from a central position. It consists of the following operations, which can be manually controlled or can be scheduled and automatically performed:

3.8.1 NE SOFTWARE UPGRADE:

• Import phase: this phase consists in loading on the software repository the software necessary to NEs downloading.

• Download phase: this phase consists in downloading simultaneously the files into managed NEs (limitation to 20 NEs). The downloading progress status is displayed.

• Activation phase: this phase consists in the activation of the new software in the managed NEs.

• Validation: this phase consists in the declaration of the new software as the default one in the managed NEs

Note 1 : The exact SU steps are NE dependant and dynamically discovered by the XMC.

Note 2 : Depending of the NE, the SU operations can be limited to download operation only. In such case the other steps must be performed by the operator through SSH.

3.8.2 NE BACKUP/IMPORT:

• The XMC offers the possibility to control backup/import operations for the NE data (NE system backup is not supported) onto a centralized repository. The backup repository server can be the XMC or an external server.

• The backup can be scheduled or immediate and can be performed toward one NE or a group of NEs.

• The operator is able to consult the state of the backup jobs and the state of the backup reposi-tory. A Progress tool bar is provided. In case of failure, a message is provided to warn the op-erator.





Date: December 2010

23/44


tion

• The NE import is performed from the XMC by transferring the backup file on the NE.

• Note that external backup agent can be installed on XMC, allowing customer to use its own backup infrastructure, and to store NE data backup within this infrastructure.





Date: December 2010

24/44


tion

3.9 PERFORMANCE MANAGEMENT

2 types of performance data are collected on the NE : either Performance counters through snmp get or Performance files through sftp/https.

For the NEs that do build their own files, configuration is performed through the EML hosted at NE level : the operator can configure, activate (reporting period, granularity period) and visualise network element counters for each individual network element.

For the NEs that support polling through snmp get, the XMC allows the operator to define the counters to poll, the Granularity period (GP) and the Reporting Period (RP).

At the end of each reporting period the XMC generates a 3GPP XML files for each NE. These PM files are available on a specific file system.

An external OSS can access to these PM files (PUSH and PULL mode supported) for further analysis. XMC support also an optional QOS package for such analysis.

In addition, an automatic cleanup is performed by the system with a default retention period of 7 days.

3.10 QOS MANAGEMENT

The QoSAC optional package is available for the analysis of the QOS of the network. The input of the QOS package are the PM files built by the XMC. This package allows an operator to select a set of counters to be displayed, to define KPIs for Alarm generation, and to provide QoS Reports.

3.11 NAVIGATION

The XMC product uses the latest web based, java web start technology as well as principles of distrib-uted network management. In order to offer the user complete transparency of where applications ac-tually run, the navigation component allows the user to navigate between XMC resident applications and other web based applications in a transparent, seamless manner.

3.12 CONFIGURATION MANAGEMENT

This application is implemented at two different levels:

t The first one is NE dependent as it resides directly on the NE. A graphical interface specific to the Network Element will enable the provisioning of the network element

t The second, at XMC level, which enables the provisioning at multiple NE level

o Multi NE scripting

o XML SOAP for 5060 MGC-10 provisioning.

These features allow customers to develop dedicated provisioning procedures (tailored service)

In addition, where appropriate, the XMC provides “co-operative” management function to simplify network level configuration; for example “Routing Area” con figuration in a GPRS network.





Date: December 2010

25/44


tion

3.13 EQUIPMENT MANAGEMENT

This application shows the operator the network element from the aspect of the physical layout of the NE (with status information mapped on it). The application is NE dependent as it resides directly on the NE.

3.14 EXTERNAL INTERFACES

3.14.1 3GPP NBI

The external interfaces provided are based on the 3GPP standard R6; they cover the alarm (FM) do-main, the performance management domain (PM) in XML format.

The objects / modules (IRP – Integration Reference Point) which are implemented are:

• Common Management

EP IRP (Entry Point)

CS IRP (Communication Surveillance)

Notification IRP

FT IRP (File Transfer) (via ftp, sftp)

• Alarm Management

Alarm IRP

• Performance Management

PM IRP (Performance Management)

The interfaces are only partially covering legacy nodes managed through existing OMCs (OMC CS, OMC PS, CMC…): The FM domain is fully covered, the PM domain is covered in as much as all per-formance files are centralised in a single format (3GPP xml) and in a single point. Provisioning inter-faces for these networks still go through the specific interfaces, which exist, on the corresponding OMC.

3.14.2 SNMP NBI

XMC provides a northbound interface allowing external OSSs to retrieve all the alarms, according to SNMP trap (V1/V2c/V3). This includes also the alarms provided by legacy managers (OMC-CS, PS, OMC-P CMC…). This is a generic mapping, providing also resynchronisation capabilities.

Filtering on the NBI is supported by configuration : the operator can define for each OSS, in-clude/exclude filters based on NE or NE_type

3.14.3 XML/SOAP NBI





Date: December 2010

26/44


tion

In addition, an XML/SOAP interface is supported, in order to provision the MGC30, and to translate XMC/SOAP command from OSS to native Corba MML command..

3.15 ON LINE DOCUMENTATION

Electronic customer documentation is delivered by Alcatel-Lucent as an integral part of its products and is integrated in the Alcatel-Lucent 1300 XMC. Each customer documentation package is composed of document sets that are enriched with display and viewing capabilities to become what is called a "col-lection".

There is one collection of electronic documents for a given product release (version, date of issue). Such collections are accessed through a dedicated documentation user interface, commonly known as the "electronic library". Stored and shipped on CD-ROM, an entire customer documentation package may be consulted via an appropriately configured personal computer, workstation or operator termi-nal.

3.16 XMC PLATFORM FUNCTIONS

3.16.1 XMC PLATFORM BACKUP/RESTORE

The XMC offers a backup / restore facilities of its own system and data partitions in order to recover following a major fault (disk crash, corrupted file system, etc)

t Data back up – the system is running but data has been lost or is corrupted

t System backup – the system will not boot or initialise correctly

Note that external backup agent can be installed on XMC, allowing customer to use its own backup infrastructure.

3.16.2 XMC PLATFORM MONITORING

The XMC product implements a number of monitoring services to ensure service continuity of the XMC platform; these are:

t Process supervision and (auto) restart

t Disk space monitoring with possible threshold definition and alarm generation

t Memory occupancy

t CPU load

t Hardware monitoring (disks, PSU, I/O cards)

t XMC software inventory

3.16.3 XMC HEALTH MONITORING

XMC provides counters in regard to its own health.





Date: December 2010

27/44


tion

Supported mibs are : MIB2/UCD-SNMP/CPQHOST mibs.

XMC periodically collects these mibs and builds an XML PM file according to the GP (Granularity pe-riod) and RP (Reporting period).

3.16.4 GEOGRAPHICAL REDUNDANCY

The XMC can work in a redundant configuration where the hardware is duplicated on two separate sites. The machines work in an active / ready mode with mutual supervision via a heart bit mechanism. The data is automatically replicated between the two machines. The switch over is performed under the administrator’s control. Thanks to the embedded EML, it is still possible for an operator to work on the node while the Management system is not fully operational. The total time of service perturbation is less than 5 minutes.

3.16.5 TIME MANAGEMENT

The XMC can be synchronised on an external timeserver using the NTP protocol. It can also act as a server for the network elements if required.

3.17 NETWORK MANAGEMENT

3.17.1 RA/RNC MANAGEMENT

This feature allows the monitoring of the data consistency between Serving GPRS Support Node (SGSN) and Domain Name System (DNS) configuration.

• The XMC is in charge of monitoring the SGSN(s) in order to get their RA/RNC configuration. The monitoring is triggered either by the SGSN or automatically: resynchronisation.

• The XMC automatically updates the primary DNS(s) configuration regarding the list of RA/RNC objects known by the SGSN(s).

• The XMC offers an Audit feature, which allows to check the DNS configuration consistency ac-cording to the data gathered on all DNS(s) and SGSN(s).

• The XMC allows the resynchronisation of the DNS(s) according to the results of a previous Au-dit.

• The OMC offers a synthetic view (Tree/Table) of the objects managed by the SGSN/DNS.





Date: December 2010

28/44


tion

4 XMC OVERALL ARCHITECTURE

The XMC concept is based on a “portal” approach interfacing the existing OMCs and the NE embed-ded element managers.

Figure 8: XMC Overall Architecture

In such an approach, integration between existing OMC and new element managers is done in a loose manner.

This “loose” integration enables:

• Existing OMCs investment saving

• To preserve existing product look & feel

• To de-couple XMC road maps for different network technologies

• To guarantee the stability of the existing installed network and network management

• To quickly integrate new type of equipment while offering integrated network supervision and unique interface to OSS.

This portal approach can be extended to other existing Alcatel-Lucent 1300 OMC equipment offering standard external interface.

The main benefits of the Alcatel-Lucent network Management solution are:

OMC CS, PS, CMC, ISMC, OMC-P

AAAA LLLL MMMM AAAA PPPP

X.25 IP

Network Level

Management

Element Level

Management IP NE

Management Tomix ATCA Management

• Management of both Circuit, Packet, UMA, @IMS domain

• Log management • Software Download and backup Restore • OMC Plateform auto surveillance

• Geographical reduncandy

EML MSC HLR ...

MSC MSC

HLR HLR

... ...

XMC

Spatial WEM client

Spatial

Santera MGW

Alcatel MGW

WEM

• Single Platform Login • Common Security Management • Common Performance Management • Common Alarm Management • Common Network Map • Seamless navigation • Northbound Interface





Date: December 2010

29/44


tion

• Interoperability XMC provides standard 3GPP/CORBA/SNMP north interfaces for OSS access

• Independency between element manager level and network management level This distributed architecture - Removes the constraints for synchronisation between NE evolutions and XMCs - Simplifies the upgrade procedure: no impact on XMC system in case of NE upgrade - Offers one unique EML software accessible both from remote or local point - Reduces delay (no need to have specific developments in XMC, less network validation)

Open architecture for other Alcatel-Lucent XMC The portal architecture is open and can be extended to other Alcatel-Lucent Network Manager to pro-vide unified network view and reduction of operator workplaces.

4.1 HARDWARE ARCHITECTURE

The XMC is built on the hardware platform HP DL 380 G6 Intel Xeon Processor. XMC server(s) are

connected to a fast Ethernet LAN to the operator workplaces and printers. They provide client/server-

distributed architecture, the applications running on different servers.

Operator workplaces (OWP) are PC’s with windows XP. They can be local or remote from the Network

Operation Center site.

Figure 9: XMC Network Architecture

NTP server (if any)

External storage

100 Base-T LAN

External OSS (if any) Additional NM eqts

OWPs System console

ENMS

NE net 1,

...

Printer

Ethernet

Web Console

Bkp LAN

1GbE

NE sub net 2





Date: December 2010

30/44


tion

4.1.1 XMC SERVER

XMC server is equipped in standard with:

• DAT and DVD drives,

• Optional external storage cabinet containing up to 10 * 73/140 G bytes disks. The disks are provi-

sioned by pairs (mirroring) according to the storage capacity needed.

Only one hardware configurations is possible

• DL 380 G6 Linux Server

• 2 quadriCore boards

• 48 GB memory

• From 4 * 140GB disks + external storage

4.2 SOFTWARE ARCHITECTURE

4.2.1 GENERAL CONCEPT

Each software module is split into an “Information Manager” and a “User Service Manager” (GUI)

Each Information IM/USM handles a management area

• Either a general purpose area (e.g. network topology, network supervision, alarm management...), independently of the Network Element technology,

• Or a network specific area (e.g. APN management, ...)

Each NE communication Manager

• Handles the communication with the related Network Element with the appropriate management protocol,

• Provides the same interface to the general purpose IMs

• Provides specific interface to the network specific IMs

Each NE provides its Element Manager

• Accessed via web browser

• Uploaded and run via JNLP (Java Network Launching protocol)





Date: December 2010

31/44


tion

Figure 10: XMC General concept

4.2.2 DETAILED SOFTWARE ARCHITECTURE

XMC is based on the Alcatel-Lucent standard platform CNM, the common platform for the new gen-

eration management systems developed within Alcatel-Lucent. The added value of this common plat-

form is that it enables integrated management across different network technologies, thus providing

the following advantages:

• Same ergonomics for all new generation OS

• Easier integration between Alcatel-Lucent’s Operation Systems (OS)

• Simplified configuration and maintenance of the OS itself, enabling homogeneous operator

administration, access security, OS backup and restore, etc…

• Easy operator access to all management functions

It also implements “state of the art” approach such as:

• Java Web Start technology for the user interfaces

• Full Java / Corba portable software

• Clear internal interfaces enabling fast and easy introduction of new network elements

Navigation Bus

CORBA Bus

CORBA Bus

Generic or network specific Information Managers(IM)

Network Element specific Communication Managers(IM)

Generic or network specific User Interfaces (USM)

NeNetworkElement

Managers





Date: December 2010

32/44


tion

• Distributed management: a “distributed architecture” is used where network element manage-

ment software and associated graphical user interface reside on the network element them-

selves.

Figure 11: XMC Software Architecture

Perf mgt IM

Navigation Bus

Supervision IM

Software IM

Topology IM

Supervision USM

Software USM

Topology USM

Naming Service

3GPP Itf IM

3GPP North Interface

CORBA /XML

SNMP/FTP

Ne

Nw Perf Analysis

Notification Service

Tomix CM

SNMP CM

CORBA Bus

FTP/CORBA

IP node Tomix (*)

ASIM

GGSN

GGSN CM

CORBA Bus

AS USM

Network mgt IM

Other

OSS I/F

OMC PS,CS CMC,ISMC…

WSS CM

MSC Atrium

Network mgt USM

Network Element

Managers

SNMP North Itf (Alarms)

SNMP Itf IM





Date: December 2010

33/44


tion

5 TECHNICAL DESCRIPTION

5.1 PROTOCOLS AND INTERFACES

5.1.1 INTERFACE BETWEEN XMC AND NES

All connections to XMC are done using the IP network (X25 is only used through the OMC CS, 1300

CMC, ISMC). The Network Elements use standard protocols such as Corba, http/https, ftp/sftp or

SNMP V2c/V3.

XMC server

Tomix NE

iiop

http/https

snmp

ftp/sftp

Operator

Workplaces

iiop/ ftp/sftp

SNMP NE, iGGSN

OMC-CS,

OMC PS,

CMC,

http/https

ftp/sftp

telnet/ssh iiop

http/https

X11

Legacy

NEs

X25

External OSS

iiop

snmp

http/https

telnet/ssh ftp/sftp

DMSC

snmp

ftp/sftp

cli

snmp

http/https

ftp/sftp

telnet/ssh

OMC-P

xml/sftp

rmi

LGP/LCP

Figure 12: Interface between XMC and NEs





Date: December 2010

34/44


tion

5.1.1.1 INTERFACES CAPACITY AND BANDWIDTH

The XMC provides Ethernet 10_10-1000Base-T interface to the managed Core Network NEs.

5.1.2 INTERFACE BETWEEN XMC AND OTHER OMCS

All connections between XMC and other OMCs are done using the IP network – The Corba interface is

used for interconnection with OMC CS, OMC PS and 1300 CMC. SNMP and FTP interfaces are used

for interconnection with OMC-P – Other interfaces may be used as required

5.1.3 INTERFACES BETWEEN XMC AND OSS

The XMC provides open “North” interfaces to external systems, based on 3GPP standards. They cover

fault (3GPP corba/SNMP) , topology (CSV) , configuration (SOAP/XML) and performance management

(3GPP/XML).

5.1.3.1 INTERFACES CAPACITY AND BANDWIDTH

External interfaces are provided through the Ethernet 10-100-1000 Base-T LAN, thanks to an OmniS-

witch 24 ports.

q 2 OSS maximum can be connected to each interface at a time.

q A 1Gb port is reserved for connection to a customer backup LAN.

5.2 XMC RESILIENCE

5.2.1 PLATFORM RESILIENCE

XMC Server redundancy is ensured at different levels:

• The use of mirrored internal disk guarantees the system availability,

• The use of mirrored high availability disk arrays ensures the database integrity,

• An uninterruptible power supply (UPS), takes care of bridging, even in the event of prolonged volt-

age breakdowns.





Date: December 2010

35/44


tion

5.2.2 MTBF SYSTEM AVAILABILITY

A1300 XMC total, ( MTBF about 150 000 Hours for HP DL 380 G6, about 124 000 for the internal

switch 6800-24 ) corresponds to a figure significantly less than one major failure per 5 years. Precise

information is available from Alcatel-Lucent under a confidentiality procedure with server provider.

The XMC provides: 99.996 high availability in geographical redundancy, and 99.98 in case of simplex

server.

5.3 DISASTER RECOVERY

Please refer to chapter “Redundancy plan” for the description of the types of redundancy proposed for

XMC.

Ø Different scenarios

§ Connectivity loss (addressed by link redundancy implemented at DCN level),

§ Problem at server level (mirrored disks and redundant power supply)

§ Site disaster (site redundancy)

Ø Data integrity

In case of loss of connection to the NE’s, resynchronization mechanisms allow to realign data between

XMC and NE’s – there is no loss of data for alarms (all NEs) and observations (all NEs except SNMP

NEs which do not store files locally). This is done by date comparison between the data available on

the XMC and the data still available on the nodes.

At server level, data integrity is ensured by mirrored disk.

Data integrity in case of site disaster is ensured thanks to periodical automatic replication of XMC data

from the active XMC to the ready XMC.

5.4 CAPACITY

Through the different server sizes the XMC scales to:

§ The number of operator connections

§ The size of the managed network

§ The management applications of the XMC





Date: December 2010

36/44


tion

Thanks to the distributed management architecture of the XMC, the GUI of the XMC can be distributed

onto the operators’ workplaces.

The XMC server can be scaled easily from 4 and 8 CPUs and corresponding memory sizes inside a

unique hardware box. Additional disks can also be added leading to a fully evolutive configuration.

Because of the distributed architecture on the Element Management Layer, only single server configu-

rations are now proposed.

These figures are given as an indication – precise dimensioning is required for each network and op-

tions. These figures correspond to a typical mix of circuit and packet network elements with an XMC

with no options and no external interfaces apart from the Alarm Management 3GPP module.

Note that when nodes are managed directly by the XMC, they count as 1 but when they are managed

through an existing OMC (OMC PS, OMC CS, CMC, ISMC, OMC-P…) they count as 0,8 and the

number of operators accessing the legacy network does not impact the XMC dimensioning.





Date: December 2010

37/44


tion

5.5 HARDWARE CONFIGURATION

The XMC standard configuration is based on a HP server Proliant running Linux Redhat with a

minimum 12 Gb of RAM and embedded in a rack with the following devices:

§ One DAT for system and data backup (AC-powered only)

§ One Switch Router (OS6850)

§ One trackball and keyboard monitor

A standalone server can also be proposed to be integrated in a customer cabinet.

2 power variants are available:

- 750W 220V AC

- 1200W -48V DC , NEBS compliant

No standard racked solution is available for the DC version. No DAT is available neither : In this

case, full backup is performed on dedicated Hotplug disks, using mirroring mechanism.

5.5.1 CURRENT CONFIGURATION

The server currently deployed is a DL380 G6 racked in a 38U cabinet. This server is equipped with :

- 2 quad-core Xeon DP E5540

- 24 Go RAM

- 2 pairs of mirrored 146 Gb SAS hotplug disk drives

- One DVD ROM

- 2*4*G eth ports, one DVD ROM

- ILO advanced pack for remote maintenance services

Details information related to the HP servers are available on http://www.hp.com

Environment certificates ( RoHS ) are available on hp site :

http://h40047.www4.hp.com/certificates/sublevel.html?id=141

NEBS compliance test report is available at the following URL :

https://sps.eu.alcatel-lu-cent.com/sites/Corporate%20other.sys_oem_tcm/Shared%20Documents/Vendors/H/Hewlett%20Packard/Specifications/DL380G6/DL380G6_NEBS_Compliance_Test_Report.pdf





Date: December 2010

38/44


tion

5.5.2 PHYSICAL DIMENSIONS OF EACH ELEMENT

The XMC is composed of several devices stored in a 19” cabinet, 38U.The cabinet dimensions are the

following:

Node Cabinet Height (mm) Cabinet Width (mm) CabinetDepth(mm) Weight of equipped cabinet

(kg)

XMC 1800 (38U useful)

600 1000 250 max

5.5.3 HEAT DISSIPATION

The table below lists the known heat dissipation figures for the OMC components:

Heat Dissipation / hour

OS6800-24 Ethernet switch (24 ports) 41.228 Btu/hour

HP DL 380 server 1195,5 BTU

5.5.4 POWER CONSUMPTION

Power consumption of all OMC component are listed in the table below :

Power Consumption max

HP DL 380 G6 Proliant 100–240VAC, 50/60Hz 370 W

DDS4 LVD DAT 90–264 VAC, 50–60 Hz 140 W

Internal Disk 100–240 VAC, 50–60 Hz 20 W

HP LaserJet Printer 220–240 VAC, 50–60 Hz 330 W

OS6800-24 Ethernet switch

(24 ports)

220–240 VAC, 50–60 Hz 110 watts





Date: December 2010

39/44


tion

Environmental conditions and requirements The table below describes the environmental conditions of the Core Network OMC’s:

Proliant DL380 G6 server

RoHS

Compliant with RoHS legislation (see NOTE) (e.g. EU, China, etc.)

The use of the noted material in a solution and subsequent resale of

that solution will result in the solution no longer meeting the re-quirements of RoHS legislation.

NOTE: Directive 2002/95/EC restricts the use of lead, mercury, cad-mium, hexavalent chromium, PBBs

and PBDEs in electronic products. Countries/regions outside the EU, eg. China, are introducing similar

legislation. References to 'RoHS legislation' means requirements of

Directive 2002/95/EC or to similar substance restriction legislation enacted by any country/region outside the EU.

Electromagnetic Interference Complies with FCC Rules and Regulations, part 15, as a Class A digital

device. Manufacturer’s Declaration to EN55022 Level A, VCCI Regis-tered, Class I, Korea RLL

Operating Temperature 10º – 35ºC (50º – 95ºF)

Non-Operating Temperature -30º – 60ºC (-22º – 140ºF) Maximum Rate of Temperature Change 10ºC/hour (18°F/Hr)

Operating Relative Humidity 10 to 90%, non-condensing, 28°C (82.4°F)

Non-Operating Relative Humidity 5 to 95%, 38.7°C (101.7°F)

Operating Altitude To 3.0km (10,000 ft) above sea level

Non-Operating Altitude To 9.1km (30,000 ft) above sea level

OS6800-24 switch

Temperature Operating

Storage

0 to 40 C

–20 to 70 C

Humidity

Operating

Storage

Operating relative humidity: 10 to 90% non-condensing

Storage relative humidity: 10 to 95% non-condensing

Safety Compliance Canada CSA 60950, Germany TUV, GS Mark for Germany, Australia

c-Tick for Australia, China CCC, CB Certification (per IEC 60950)

5.6 DIAL-IN CAPABILITIES

Modem access to the XMC is not supported.





Date: December 2010

40/44


tion

5.7 SERVICE RESTORATION TIMES

Operation Time

Switchover (synchronisation done

)

5 min

Manual resynchronisation +

switchover

15 min

Full start of XMC (including op-

erating System)

20 min

Full Backup of XMC 55 min

Full restore of XMC 55 min

Full new installation of XMC

(Including Operating System)

1.5 hours

Minor upgrade 30 minutes

Table 1: Service Restoration Times

5.7.1 XMC UPGRADES

XMC release upgrades can be divided into two groups:

• Major release upgrades, generally synchronized with Core Network release upgrades;

• Minor release upgrades, which are XMC maintenance deliveries.

Major release upgrades bring major functional evolutions and may require complete XMC reinstalla-

tion (only in case of changes in 3PP software or Operating system).

Minor release upgrades always consist in patching the running XMC software. There is only a partial

interruption of the supervision service, if some processes needs to be frozen while performing the

patch.

At Core Network release upgrade, the XMC needs not necessarily be upgraded as the network release

now carries its specific element level management software.

Depending on the type of upgrade (needing XMC reinstallation or not) and on the hardware configu-

ration of the XMC, different upgrade procedures can be proposed. The time taken for a migration is,

at worse, the time taken for a complete re-installation.





Date: December 2010

41/44


tion

5.7.2 INTEGRATION WITH NETWORK MANAGEMENT SYSTEM

Integration with an external network management system is possible through the external interfaces

offered by the XMC. Please refer to the chapter “External Interfaces” for the description of these inter-

faces.

5.8 INSTALLATION & COMMISSIONING REQUIREMENTS

5.8.1 XMC INSTALLATION

Basic requirements for the room where the XMC is installed are :

§ Have air conditioning,

§ Have a raised floor,

§ Have double secured 220 V power supply,

§ Offer access to the external networks (accessing to the managed network elements).

Detailed installation and commissioning requirements listed in the installation documentation.

5.8.2 NETWORK MANAGEMENT COMMISSIONING

Thanks to the Embedded EML technology, the installation of the nodes and the installation of the XMC can be de-coupled: the GUI required to install/configure a node can be reached from the XMC itself, or directly from the node console. In other words, a node can be installed with or without XMC pres-ence.

In addition to the declaration/configuration, when the Qosac option is available, the commissioning of the network takes benefit from the Qosac predefined reports.





Date: December 2010

42/44


tion

6 DOCUMENTATION

6.1 XMC DOCUMENTATION

XMC document collection, is composed of:

Name Reference Comment

Administrator Guide 3BL96356HAAAPCZZA This document describes the administrative tasks from the

Alcatel-Lucent 1300 XMC Operation and Maintenance

Platform Management 3BL96354HAAAPCZZA This document describes the Platform Management appli-

cation : process monitoring, XMC/Ne default configura-

tion and management of the redundancy.

Network Management 3BL65018GCCAPCZZA This document describes the configuration tasks from the

Alcatel-Lucent 1300 XMC Operation and Maintenance

Center-Core Network

NE software and data Man-

agement

3BL77030IAAAPCZZA This document describes the software management tasks

from the Alcatel-Lucent 1300 XMC Operation and Main-

tenance Center-Core Network

Fault Management 3BL97132IAAAPCZZA Description of the general principles for Fault Manage-

ment.

Performance Management 3BL65019GCBAPCZZA This document describes how to manage performance

from an Alcatel-Lucent 1300 XMC. It also lists SNMP

counters. This document applies beginning with Release

5.3

NE Log management 3BL77945HAAAPCZZA This document describes the management of the OAM

logs

NE scripting Management 3BL74380HAAAPCZZA This document describes the NE scripting capabilities

SNMP Alarm Forwarding 3BL59971GCCAPCZZA Description of the SNMP north interface.

SOAP NorthBound Interface 3BL68892GCBAPBZZA Description of the SOAP north bound interface.

3GPP Alarm User Guide 3BL59947GAAAPCZZA Description of the 3GPP north bound interface.





Date: December 2010

43/44


tion

Alarm dictionaries 3BLxxx These documents lists all alarms for each managed

network element, and corrective actions or proce-

dures to be Applied

Counter lists 3BLxxx These documents lists all counters for each man-

aged network element

Table 2: XMC Documentation

Documentation is delivered on CD, and can be installed on the XMC server itself, or on any XP PCs. Documents are available in HTML or PDF format.

6.2 OTHER RELATED DOCUMENTATION:

• XMC Alarm management feature Description 3DN00811AAAA • XMC Geographical redundancy Feature Description 3DN00810AAAAFSZZA

• XMC Performance Management Feature Description 3DN 00812 AAA FS ZZA

• XMC Security Strategy Feature Description 3BL 59923 GBAA DTZZA

• XMC 3GPP Northbound interface SOC 3DN00832AAAAFOZZA

• XMC Security strategy 3BL59923GACADTZZA

• A1342 QOSAC Product description 3DN 00770 AAA





Date: December 2010

44/44


tion

7 GLOSSARY

API Application Programming Interface

APN Access Point Name

CS Circuit-Switched

DHCP Dynamic Host Configuration Protocol

DNS Domain Name System

ETSI European Telecommunication Standardization Institute

iGGSN Intelligent Gateway GPRS Support Node

GPRS General Packet Radio Service

GSM Global System for Mobile communication

HLR Home Location Register

IP Internet Protocol

LAN Local Area Network

NMC Network Management Centre

NS Network Service

OAM Operation, Administration and Maintenance

XMC Operation & Maintenance Center – Core Network

O&M Operation and Maintenance

PDP Packet Data Protocol

PDN Packet Data Network

PLMN Public Land Mobile Network

QoS Quality of Service

RA Routeing Area

SGSN Serving GPRS Support Node

SID Shared Information/Data

SNMP Simple Network Management Protocol

SSH Secured SHel

TCP Transfer Control Protocol

TMF TeleManagement Forum

TMN Telecommunication Management Network

VLR Visited Location Register

