Job Description: Senior Consultant

TMF Consensus

TMF Consensus

• •Web/Java user interface
• •CORBA to link business application
• •SNMP manage the network

TMF Direction

•Interoperable OSS: as the de-facto standard.

–Multi-Service Providers, Vendors, Technologies, .…

–Common Business process and Components

•Source of new technologies for OSS developments.

–COTS, CORBA, XML, SOAP, JINI, …

•International Promotion for OSS products.

–Catalyst Showcase，Product　Expo…

TMF Products

•TMN/C++API

• –TMN AP Development Environment
• –GDMO/C++ Information Model API
• –CMIS/C++ Protocoｌ; API
• –ASN.1/C++ ASN.1 API

•A CORBA-CMIP-SNMP Inter-working

• –CMIP/GDMO to CORBA IDL
• –CORBA IDL to CMIP/GDMO
• –SNMP MIB to CORBA IDL

OSS Architecture Case Studies

XML over CORBA

OSS/J Focus areas

Multi Domain Management

Interoperable OSS : TMF Direction

•Interoperable OSS: as the de-facto standard.

–Multi-Service Providers, Vendors, Technologies, .…

–Common Business process and Components

•Source of new technologies for OSS developments.

–COTS, CORBA, XML, SOAP, JINI, …

•International Promotion for OSS products.

–Catalyst Showcase，Product　Expo…

TMF Consensus

•Web/Java user interface

•CORBA to link business application

•SNMP manage the network

TMF Products

•TMN/C++API

–TMN AP Development Environment

–GDMO/C++ Information Model API

–CMIS/C++ Protocoｌ; API

–ASN.1/C++ ASN.1 API

•A CORBA-CMIP-SNMP Inter-working

–CMIP/GDMO to CORBA IDL

–CORBA IDL to CMIP/GDMO

–SNMP MIB to CORBA IDL

Members’ Target of TMF Activities

•Products Promotion

Proof of Interoperability

　 Products Exhibition

by

•Obtaining New Technologies and Know-how

Business Process

Software Architecture, COTS, PnP　

•Establishing Partnership/Networks

Service Providers

ISVs, System Integrators, OSS vendors

Relationships between Telecommunication Network and TMN

Telecommunications Management Network (TMN)

•Telecommunications Management Network (TMN)
•TMN project started fall 1985
•Initial recommendation CCITT M.30 (published in 1988) included work of several Study Groups
•Renamed to recommendation M.3010 in 1992 which defines basic principles for TMN
•The objective for the TMN specifications is to provide a framework for telecommunications network and service management

•Why TMN?

•

To survive in a highly innovative and competitive telecommunications market, use of a robust architecture for network and service management is a must.

The TMN Framework:
•ensures interoperability
•ensures scalability
•is mature (large amount of telecom standards in GDMO)
•provides security
•

•TMN Principles

•TMN Recommendations from ITU-T
•Objectives
•Relationship of a TMN to a Telecom Network
•TMN Functional Architecture
•TMN Information Architecture
•CMIP/CMIS
•TMN Physical Architecture
•Logical Layered Architecture
•

•TMN Recommendations from ITU-T

M.3010	Principles for a telecommunications management network
M.3100	Generic network information model
M.3200	TMN management services
M.3300	TMN management capabilities at the F interface
M.3400	TMN management functions

•The M.3010 recommendation defines “general architectural requirements for a TMN to support the management requirements of administration to plan, provision, install, maintain, operate and administer telecommunication networks and services”
•
•The basic concept behind a TMN is to provide a organized architecture to achieve the interconnection between various types of OS’s and/or telecommunications equipment for the exchange of management information using an agreed architecture with standardized interfaces including protocols and messages
•

•TMN Functional Architecture

•The TMN functional architecture explains the distribution of functionality within a TMN

•Distinction must be made between:

–Role that a function performs (controlling, mediator role, management user oriented, information transport)

–Actual function that is performed (configuration management, fault management, etc.)

•Recommendation M.3010 concentrates on roles whereas M.3400 deals with functions

•

The TMN functional architecture is defined by:

•TMN function blocks, being the roles in which functions operate (coordinate, mediate, etc.)

•

•TMN function points, being the service boundary between two communication management function blocks

•Function blocks defined within M.3010:

•

–OSF Operation Systems Function

–MF Mediation Function

–WSF Work Station Function

–NEF Network Element Function

–QAF Q Adaptor Function

•Reference points defined within M.3010 (g and m are located outside the TMN):

–q class between OSF, QAF, MF and NEF

–f class for attachment of a WSF

–x class between OSFs of two TMNs or between TMN OSF and OSF-like

function in other network

–g class between WSF and users

–m class between QAF and non-TMN managed entities

•

•In order to allow effective definition of managed resources, TMN makes use of OSI Systems Management principles and is based on an object-oriented paradigm.

•

•Management systems exchange information modeled in terms of managed objects (MO)

•

•Because the environment being managed is distributed, network management is a distributed application which requires exchange of information.

•For a specific management association, the management processes will take one of two possible roles:

–Manager, which issues operation directives and receives notifications

–Agent, responds to directives and emits notifications (deals with the MO’s)

•

•The element management layer (EML) manages each network element on an individual basis and supports an abstraction of the functions provided by the NE layer.

•Each element manager has the following principle roles:

–control and coordination of a subset of network elements

–provide a gateway function to permit the network management layer to interact with network elements

–maintaining statistical, log and other data about elements

•OSFs in the element layer always interface with OSFs in the network management layer through the q3 reference point

•

•The network management layer (NML) has the responsibility for the management of all the NE’s, as presented by the EML, both individually and as a set.

•The NML has the following principle roles:

–control and coordination of the network view of network elements within its scope or domain

–the provision, cessation or modification of network capabilities for the support of service to customers

–interact with the service management layer on performance, usage, availability, etc.

•OSFs in the NML always interface with OSFs in the service management layer through the q3 reference point

•

•Service management layer (SML) is concerned with, and responsible for, the contractual aspects of services that are being provided to customers or available to potential new customers.

•Principle roles for the SML:

–customers facing and interfacing with other administrations

–interaction with service providers

–interaction with the SML

–maintaining statistical data (e.g., QoS)

–interaction with the business management layer

–interaction between services

•

•The business management layer (BML) includes all the functions necessary for the implementation of policies and strategies within the organization which owns and operates the services (and possibly the network)

•The BML:

–interacts with the service management layer

–Is influenced by high levels of control such as legislation or macro-economic factors (e.g., tariffing policies, quality maintenance strategies)

•

•FCAPS !

• •Fault management

• •Configuration management

• •Accounting management

• •Performance management

• •Security management

•TMN Strengths

•TMN is a very suitable framework for telecommunications management purpose since:

–It identifies different abstraction levels

–It forces a structure approach when faces with the problem of network and service management

–It is a widely adopted standard, which ensures that everyone speaks the same language

•TMN is particularly strong at the bottom layers of the TMN pyramid, using the power of OSI systems management and the associated object approach

•

•High interoperability by standardizing

–protocol

–information model

–services

–MIBs

•scalability by well-developed reliable “event channel” (notifications with EFD discriminators)

•complex types (structures)

•scoping and filtering (OSI modeling)

•TMN offers security, which is essential at EML and X interface

•

•TMN weaknesses

•Implementation of TMN isn’t so easy

•TMN Q3 interface is based on a full OSI stack (solutions for stacks with reduced functionality are developed, e.g., CMIP on TCP/IP)

•GDMO and ASN.1 are very complex (solution is the use of tools that hide GDMO and ASN.1). ASN.1 is designed for completeness, not simplicity.

•TMN functional architecture does not map very well to service management. It originates from the bottom layers of the pyramid

•

•

OSS, eTOM and OSS/J

OSS Abbreviations

Abbreviations

3GPP		The Third Generation Partnership Project
3GPP2		The Third Generation Partnership Project 2
ACSE		Application Control Service Element
AAA		Authentication, Authorization, Accounting
ABC		Accounting Billing Charging
ABE		Aggregate Business Entities
AE		Application Entity
API		Application Programmers Interface
ATIS		Alliance for Telecommunications Industry Solutions
ATM		Asynchronous Transfer Mode
B2B		Business-to-Business
BPEL		Business Process Execution Language
BPEL4WS		Business Process Execution Language for Web Services
BPML		Business Process Modelling Language
BSS		Business Support System
CAPEX		Capital Expenditure
CBE (OSS/J)		Core Business Entities
CBE (SID)		Common Business Entities
CCITT		Comité Consultatif International Téléphonique et Télégraphique
CCM		CORBA Component Model
CDR		Call Detailed Record
CIM		Common Information Model
CLI		Command Line Interface
CMIP		Common Management Information Protocol
CMIS		Common Management Information Service
CMISE		Common Management Information Service Elements
CMOP		CMIP Over TCP/IP
COPS		Common Open Policy Service
CORBA		Common Object Request Broker Architecture
COTS		Commercial Off the Shelf Software
CRM		Customer Relationship Management
CWM		Common Warehouse Metamodel
DCML		Data Center Markup Language
DEN-ng		Directory Enabled Directories – new generation
DNSSec		DNS Security Extensions
DIT		Directory Information Tree
DMTF		Distributed Management Task Force
DNSSEC		DNS Security Extensions
DSL		Digital Subscriber Line
DSLAM		Digital Subscriber Line Access Multiplexer
DTD		Document Type Definition
EAI		Enterprise Application Integration
EAN		European Article Numbering
ebXML		Electronic Business XML
ECMA		European Computer Manufacturers Association
EDIFICE		The European B2B forum for the Electronics Industry
EJB		Enterprise Java Beans
EPS		Eurescom Permanent Staff
eTOM		Enhanced Telecom Operations Map
ESIF		Emergency Services Interconnection Forum
ETSI		European Telecommunications Standards Institute
FAQ		Frequently asked questions
FCAPS		Fault, Configuration, Accounting, Performance, Security
GGF		Global GRID Forum
HTTP		HyperText Transport Protocol
HTTPS		Secure Internet Protocol
ICT		Information and Communications Technology
IDL		Interface Definition Language
IEEE		Institute of Electrical and Electronics Engineers
IETF		Internet Engineering Task Force
IMAP		Internet Messaging Access Protocol
IP		Internet Protocol
IPCC		International Packet Communications Consortium
IPDR		Internet Protocol Detail Record
ISO		International Organization for Standardization
IPSec		IP Security protocol
ISO		International Organization for Standardization
ISV		Independent Software Vendors
IT		Information Technologies
ITIL		IT Infrastructure Library
ITU		International Telecommunication Union
ITU-R		ITU - Radio Sector
ITU-T		ITU - Telecom Sector
J2EE		JavaTM 2 Platform, Enterprise Edition
JAXP		Java API for XML Processing
JCP		Java Community Process
JDBC		Java Database Connectivity
JMS		Java Messaging Service
JMX		Java Management Extension
LAN		Local Area Network
LDAP		Light weight Directory Access Protocol
MAC		Medium Access Control
MDA		Model Driven Architecture
MIB		Management Information Base
MOF		Meta Object Facility
MSF		Multiservice Switching Forum
MTNM		Multi Technology Network Management
NGN		Next Generation’s Networks
NGOSS		New Generation Operations Software and Systems
NMD		Network Management Domain
NPF		Network Processing Forum
OA&M		Operations Administration and Maintenance
OAM&P		Operations, Administration, Maintenance & Provisioning
OAGIS		Open Applications Group
OASIS		Organization for the Advancement of Structured Information Standards
OBF		Ordering and Billing Forum (ATIS)
OCAF		Open Communication Architecture Forum
ODP		Open Distributed Processing
OIF		Optical Internetworking Forum
OLO		Other Licenced Operator
OMA		Object Management Architecture
OMG		Object Management Group
OPEX		Operating Expenditure
OS		Operating System
OSI		Open Systems Interconnection
OSA, OSA/Parlay		Open Service Access
OSS		Operation Support Systems
OSS/J		OSS through Java
PBNM		Policy-Based Network Management
PEP		Policy Enforcement Point
PIB		Policy Information Base
PIM		Platform Independent Model
PSM		Platform Specific Model
PBNM		Policy-Based Network Management
PSM		Platform Specific Model
QoS		Quality of Service
RDN		Relative Distinguished Name
RFC		Request For Comments
RFP		Request For Proposal
ROPM		Remote Operation Protocol Machine
ROSE		Remote Operations Service Element
SAF		Service Availability Forum
SCF		Service Capability Features
SDH		Synchronous Digital Hierarchy
SDO		Standards Defining Organisation
SFTP		Secure File Transfer
SI		System Integrator
SID		Shared Information and Data
SIP		Session Initialisation Protocol
SNIA		Storage Networking Industry Association
SLA		Service Level Agreement
SMD		Service Management Domain
SNMP		Simple Network Management Protocol
SOA		Service Oriented Architecture
SOAP		Simple Object Access Protocol
SP		Service Provider
SQL		Structured Query Language
SSH		Secure SHell
SSL		Secure Socket Layer
TCP/IP		Transmission Control Protocol/Internet Protocol
TLS		Transport Layer Security Protocol
TMF		TeleManagement Forum
tML		Telecommunications Markup Language
TMN		Telecommunications Management Network
TNA		Technology Neutral Architecture
UCC		Uniform Code Council
UDDI		Universal Discovery, Description and Integration
UDP		User Datagram Protocol
UMD		Utility Management Domain
UML		Unified Modelling Language
USM		User-based Security Model
USP		Unique Selling Point
VACM		Views-based Access Control Model
VPN		Virtual Private Network
WAN		Wide Area Network
WEBM		Web-Based Enterprise Management
WLAN		Wireless LAN
WSDL		Web Service Definition Language
XMI		XML Metadata Interchange
XML		Extensible Markup Language