Telecommunications Systems 2

(1)

Telecommunications Systems 2

(2)

Sistemas de Telecomunicações II - 4.2

Telecommunications Management Network

ITU-T M.3000–M.3599

(3)

Telecommunications Management Network

Subject areas

– Architecture;

– Interface specification methodology;

– Management services;

– Management functions (protocol independent);

– Management information models and catalogue;

– Management information registration;

– Communication protocols;

– Systems management services and management messages (protocol

specific);

– Conformance requirements;

– International standard profiles;

– Terminology;

(4)

Telecommunications Management Network

Referenced areas

– Telecommunication services;

– Telecommunication network architecture;

– Telecommunication network management for traffic;

– Telecommunication network maintenance;

– Telecommunication network security;

– Telecommunication network components;

– Telecommunication network provisioning;

– Communication protocols;

– OSI systems management services;

– OSI layer management functions;

– ISPs or implementation requirements;

– Managed object naming and addressing.

(5)

Telecommunications Management Network

Mapping of TMN-referenced Recommendations

(6)

Telecommunications Management Network

Relationship of a TMN to a telecommunication network

(7)

Telecommunications Management Network

The objective for the TMN specifications is to provide a framework for

telecommunications management.

By introducing the concept of generic network models for management, it

is possible to perform general management of diverse equipment,

network and services using generic information models and standard

interfaces.

A TMN is intended to support a wide variety of management areas which

cover the planning, installation, operations, administration,

maintenance and provisioning of telecommunications networks and

services.

Management functional areas:

– performance management;

– fault management;

– configuration management;

– accounting management;

(8)

TMN management functions

Performance Management

Performance Quality

Assurance

Performance Monitoring

Performance Management

Control

Performance Analysis

Fault Management

Reliability, Availability and

Survivability (RAS) Quality

Assurance

Alarm surveillance

Fault localization

Fault Correction

Testing

Trouble administration

Configuration Management

Network Planning and Engineering

Installation

Service Planning and Negotiation

Provisioning

Status and control

Accounting Management

Usage Measurement

Tariffing/pricing

Collections and Finance

Enterprise Control

Security Management

Prevention

Detection

Containment and Recovery

Security Administration

(9)

Telecommunications Management Network

Requirements of the TMN

– the ability to exchange management information across the boundary between the telecommunications environment and the TMN environment;

– the ability to exchange management information across the boundary between TMN environments;

– the ability to convert management information from one format to another so that

management information flowing within the TMN environment has a consistent nature; – the ability to transfer management information between locations within the TMN

environment;

– the ability to analyse and react appropriately to management information;

– the ability to manipulate management information into a form which is useful and/or meaningful to the management information user;

– the ability to deliver management information to the management information user and to present it with the appropriate representation;

– the ability to ensure secure access to management information by authorized management information users;

– the ability to achieve technology independence based on requirements and to be extendable to include prominent and available management technologies in its

(10)

Telecommunications Management Network

(11)

(12)

TMN Functional architecture

• Function blocks;

• Management Application

Functions (MAFs);

• TMN Management

Function Sets and TMN

Management Functions;

• Reference points.

(13)

TMN Function blocks

• Operations Systems Function (OSF)

• Network Element Function (NEF)

• Workstation Function (WSF)

• Transformation Function (TF)

Relationships between logical function blocks

expressed as reference points (f, q, x)

(14)

(15)

Management Application Functionality

• Operations Systems Functionality – Management

Application Function (OSF-MAF);

• Network Element Functionality

−

_Management

Application Function (NEF-MAF);

• Transformation Functionality – Management

Application Function (TF-MAF);

• Work Station Functionality

−

_Management

(16)

TMN Management Function Sets and

TMN Management Functions

To perform TMN management services, interactions take

place between MAFs in different TMN function blocks,

with the help of the support functions.

These interactions between cooperating MAFs are referred to

as TMN Management Functions.

TMN Management Functions, that collectively are all of the

potential interactions that a single MAF will support, are

grouped together and referred to as a TMN Management

Function Set.

(17)

TMN Functional architecture

Layering of TMN

management functions

A specialization of OSF function blocks based upon different layers of

abstraction is:

• Business; • Service; • Network; • Element.

(18)

Definitions

TMN management goals: High-level objectives of a user in performing

management activities.

TMN management roles: TMN management roles define the activities

that are expected of the staff or system that perform

telecommunications management. TMN management roles are defined

independent of other components, i.e. telecommunications resources

and TMN management functions.

Telecommunications resources: Telecommunications resources are

physical or logical entities requiring management, using TMN

management services.

TMN management scenario: A TMN management scenario is an example

of management interactions from a management service.

(19)

TMN information architecture

Interaction model

• A TMN interaction model provides the rules and patterns that govern the

flow of information between TMN function blocks at a reference point.

• Possible interaction models include manager/agent, client/server,

invoker/responder, peer-to-peer, publisher/subscriber, and

consumer/producer and are associated with a specific management

paradigm.

• For the exchange of management information, management processes will

take on one of two possible roles:

– Managed Role: a process that manages the TMN information elements

associated with managed resources. The process acting in this role responds to

directives issued by the process acting in the managing role. It will also reflect

to the process acting in the managing role a view of these information elements

and provide information reflecting resource behaviour (e.g. information

source);

(20)

Management interactions

CMIP - Common Management Information Protocol CMIS - Common Management Information Services

(21)

Information model for management

Example of

Leased Circuit and

reconfigurable

Services:

- LCS using request

and explicit deletion

(22)

(23)

TMN physical architecture

• TMN physical blocks

– Operations System (OS)

– Transformation

– Network Element (NE)

– Workstation (WS)

• Data Communication Network (DCN)

• TMN logical layered architecture within the TMN physical

architecture

• Interoperable interface concept

• TMN standard interfaces

– Q interface

– F interface

– X interface

(24)

TMN physical architecture

Physical blocks

QMD Q-mediation device QA Q-adapter

(25)

(26)

Relationship between the TMN functional and

information architecture to physical architectures

(27)

Shared management knowledge

In order to interwork, communicating management

systems must share a common view or

understanding of at least the following

information:

– supported protocol capabilities;

– supported management functions;

– supported managed object classes;

– available managed object instances;

– authorized capabilities;

(28)

(29)

Common Object Request Broker Architecture

The initial TMN interface

specifications for

intra-and inter-administration

TMN interfaces were

developed using the

Guidelines for the

Definition of Managed

Objects (GDMO) notation

from OSI Systems

Management with

Common Management

Information Protocol

(CMIP) as the protocol.

The inter-TMN administration interface

(X) included both CMIP and CORBA

General/Internet Inter-ORB Protocol

(GIOP/IIOP) as possible choices at

the application layer.

(30)

Technology integration

(31)

Common Management Information Protocol

Basic Reference Model definitions:

application-service-element; application-process;

real open system; systems-management.

Management Framework definitions:

managed object;

management information; management information base;

systems management application-entity.

Remote Operations definitions:

association-initiator; association-responder; linked-operations; Remote Operations;

Remote Operation Service Element; invoker;

performer;

CMIS definitions:

attribute;

Common Management Information Service Element;

Common Management Information Services; CMISE-service-provider; CMISE-service-user; invoking CMISE-service-user; performing CMISE-service-user.

ACSE definitions:

application context; application-association; association.

Presentation definitions:

abstract syntax;

(32)

(33)

Intelligent Network

IN is an architectural concept for the operation and provision

of new services which is characterized by:

– centralized service logic;

– extensive use of information processing techniques; – efficient use of network resources;

– modularization and reusability of network functions;

– integrated services creation and implementation by means of modularized reusable network functions;

– flexible allocation of network functions to physical entities; – portability of network functions among physical entities;

– standardized communication between network functions via service independent interfaces;

– some user-specific service attributes that can be controlled by the users themselves;

– some subscriber-specific service attributes that can be controlled by the subscribers themselves;

(34)

(35)

(36)

Telecommunications Management Network

Management Services:

• Customer Administration;

• Network Provisioning Management;

• Work Force Management;

• Tariff, Charging and Accounting Administration;

• Quality of Service and Network Performance Administration;

• Traffic Measurement and Analysis Administration;

• Traffic Management;

• Routing and Digit Analysis Administration;

• Maintenance Management;

• Security Administration;

• Logistics Management.

(37)

Management Services and

(38)

(39)

(40)

Decomposition of VPN service

(41)

(42)

TMN management services

for IMT 2000 security management

• Telecommunication resources

– Fraud Information Gathering System (FIGS)

– Visited Network

– Home Network Fraud Detection System (HN-FDS)

• Fraud Information Gathering functions

– Fraud Alert function

– Activate Information Gathering function

– Report FIGS function

– Deactivate Information Gathering function

– Modify FIGS Report function

– Advise Suspend FIGS Monitoring function

– Advise Resume FIGS Monitoring function

(43)

Management Information Base

Overview

A Management Information Base is a specification containing definitions

of managed information in a formalism that allows remote monitoring

and control of systems over a network.

The simplest, incorrect way is to visualize a MIB as a database on a

managed system. It is more correct to view a MIB as definitions of the

information that can be accessed and the events that can be reported

by standard protocols.

Standard operations are requested or performed on a system via a

management agent by management clients. It is left to this

management agent to access the requested information and return it to

the requesting client.

(44)

Management Information Base

Definition of Managed Objects

The majority of the development of the Media MIB can be

broken down into the following four tasks:

– Characterization of the managed entity in terms of

components, attributes, actions, state and statistics.

– Organization of information into collections of Object IDs

(OID)s.

– MIB organization – MIB structure and hierarchy tree related

to MIB Object Names.

(45)

Management Information Base

Operations on Managed Objects

• The definition of managed objects may proceed

independent of the protocols used to operate on the MIB.

• Operations may be generalized into three categories:

– information retrieval,

– information modification, and

(46)

Definitions

Management Information Base (MIB): The specification of information in a manner that

allows standard access through a network management protocol.

Multipoint Control Unit: The MCU is an endpoint that provides the capability for three or

more terminals and Gateways to participate in a multipoint conference.

Multipoint Controller: The MC is an entity on the local area network that provides for the

control of three or more terminals participating in a multipoint conference. It may also connect two terminals in a point-to-point conference that may later develop into a multipoint conference.

Object Identifier (OID): The permanent assignment of a value to represent a managed

object through a process termed registration.

Structure of Management Information (SMI): The rules used to define objects which can be

accessed via a network management protocol.

Simple Network Management Protocol (SNMP): The network management protocols used

in the Internet for TCP/IP systems. There is a body of work termed SNMPV2 and SNMPV3 that are expanded successors to SNMP.

The Common Management Information Protocol (CMIP) specifies protocol elements that may be used to provide the operation and notification services described in ITU-T Rec. X.710, which defines the Common Management Information Services (CMIS).

Terminal: A terminal is any endpoint and may be a user's terminal or some other

(47)

Multimedia management information base

• MIB Applicability by Device Type

– H.323 Systems

– H.320 Systems

• Management Model Overview

– Gateway Model

– Multiple Instances

• Management Hierarchy

– H.323

• CallSignalling

• RAS (Registration, Admission and Status)

• Terminal • Gatekeeper • Multipoint Controller • Multipoint Processor – H.320 • Entity • Terminal

• Multipoint Control Unit

– H.245

– Gateway

– Real Time Protocol (RTP)

– MIB-II

– Interfaces Group

(48)

Multimedia management information base

Formal language description modules

• ANNEX A - Textual Conventions

• ANNEX B - H.323 (Packet-Based Multimedia Communications Systems)

– B.1 H.225 CallSignalling – B.2 RAS – B.3 H.323 Terminal – B.4 H.323 Gatekeeper – B.5 Multipoint Controller – B.6 Multipoint Processor