SIST-TP TR 101 303 V1.1.2:2004
(Main)Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Requirements definition study; Introduction to service and network management
- Abstract
Note : Part I is WI 1004-(1) part 2 is WI 3014-(2) This work item delivers a service and network management framework for ETSI Tiphon [requirements, information models, management interfaces and information bases]. Based on existing general service & network management frameworks, it defines: Service and Network Management Requirements The roles of network management in TIPHON networks, a common terminology, information models for IP telephony manageable elements and a set of protocols & information bases to communicate network management information.
- Status
- Published
- Publication Date
- 31-Mar-2004
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Apr-2004
- Due Date
- 01-Apr-2004
- Completion Date
- 01-Apr-2004
SIST-TP TR 101 303 V1.1.2:2004 is the Slovenian version of ETSI TR 101 303 V1.1.2, produced for the Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) project. It introduces the service and network management framework for TIPHON Release 3. The report sets out the management requirements, information models, management interfaces, and information bases used to support IP telephony and related TIPHON service capabilities.
What does SIST-TP TR 101 303 V1.1.2:2004 specify?
SIST-TP TR 101 303 V1.1.2:2004 specifies how TIPHON service and network management is framed around the management plane, the TIPHON Application Plane, and the TIPHON Transport Plane. It gives the structure for service and network management requirements, terminology, information models for manageable IP telephony elements, and the protocols and information bases used to carry management information.
The main body is organized into scope, references, definitions and abbreviations, objectives and roadmap, generic requirements, Fault Management, Configuration Management, Accounting Management, Performance Management, Security Management, and information at management interfaces.
| Annex | What it covers |
|---|---|
| Annex A | The purpose of the TMN layers, including EML, NML, SML, and BML |
| Annex B | Bibliography |
What are the key requirements of SIST-TP TR 101 303 V1.1.2:2004?
SIST-TP TR 101 303 V1.1.2:2004 builds TIPHON network management on the TMN model and uses UML-based modelling for its information view. In practice, that means the document is not only describing functions - it is also setting the modelling approach and the interfaces that management systems should use.
Framework and modelling
Clause 5.1 states that the TNM framework is based on ITU-T Recommendation M.3010, with interface methodology from ITU-T Recommendations M.3020 and M.3013. It includes TMN layer structure, FCAPS processes, information flows between layers, functions and domains, UML modelling, management interfaces, and Management Information Bases (MIB) derived from UML models. This matters because implementers need a common structure for how management data is modelled and exchanged.
The framework uses Q interfaces unless that is inappropriate, and it prefers existing business and service processes from the TeleManagement Forum plus protocols and information bases already defined by IETF and ITU-T. This means the work is intended to fit with established operations practice rather than inventing a separate management stack.
TIPHON planes, entities and domains
Clauses 5.2 to 5.6 relate TNM to the TIPHON architecture and functional entities. The document ties management information flows to the A reference points between the management plane and the application and transport planes, and it uses functional entity packages for service, service control, call control, bearer control, and media control. For a reader, this is the map that shows where management data belongs in the TIPHON architecture.
Clause 5.5 explains that service applications combine service capabilities and managed objects, and that the managed objects are derived from service capability attributes needed for FCAPS. That is important in practice because service management data should follow the service capability it supports.
Clause 5.6 introduces management domains and ownership domains. It says release 3 supports service capabilities and higher-order service application, while the element-manager to network-element interface is out of scope. This narrows the implementation focus to the interfaces and information flows the report is actually defining.
Fault and performance management
Clause 6 limits Fault Management to alarm surveillance, fault localization, and testing. It excludes fault correction, reliability and availability quality assurance, and trouble administration. In practice, this means the document helps you detect, isolate, and test faults, but not run the full outage and trouble-ticket lifecycle.
Clause 9 limits Performance Management to metrics, communication failures, multiple call degradation, and SLA monitoring. It includes call set-up and teardown metrics and voice quality metrics from TS 101 329-3, but excludes hard faults and provisioning faults. This keeps performance management focused on service degradation and service quality, not general fault handling.
Later-release topics and management information
Clauses 7, 8, and 10 mark Configuration Management, Accounting Management, and Security Management as topics for later release in the framework. Clause 11 focuses on information exchanged at management interfaces, especially for inter-domain services, provisioning, trouble resolution, status and performance tracking, and inter-administration accounting. It also says the specific exchanged items are agreed bilaterally or multilaterally during service design and development.
What terms does SIST-TP TR 101 303 V1.1.2:2004 define?
- Administrative domain - a network controlled by a single operator, covering both the network and management domains.
- Management domain - one or more management systems, plus managed systems and subdomains, administered by a single operator.
- Tiphon Network Management (TNM) - the TIPHON management framework that organizes service and network management for the TIPHON planes.
- FCAPS - the five management process areas: Fault, Configuration, Accounting, Performance, and Security.
- Quality of Service (QoS) - the service quality measure used in performance-related management and statistics.
- Network Element (NE) - an individual network element that is monitored and controlled through management functions.
Who uses SIST-TP TR 101 303 V1.1.2:2004?
SIST-TP TR 101 303 V1.1.2:2004 is used by TIPHON service providers, network operators, and system designers working on IP telephony management. It is also relevant to teams defining management information models, management interfaces, and MIBs for TIPHON systems.
In practice, it supports architects who map management data to functional entities, operations teams that need fault and performance management concepts, and standards or interoperability teams working on intra-domain and inter-domain service management.
What changed in SIST-TP TR 101 303 V1.1.2:2004 from the previous edition?
SIST-TP TR 101 303 V1.1.2:2004 is the December 2001 publication of ETSI TR 101 303 and replaces V1.1.1 from June 2001.
Which standards are used with SIST-TP TR 101 303 V1.1.2:2004?
- ITU-T Recommendation M.3010 - provides the principles for the telecommunications management network that the TNM framework is based on.
- ITU-T Recommendation M.3020 - provides the TMN interface specification methodology used for TIPHON management systems.
- ITU-T Recommendation M.3013 - contributes considerations for a telecommunications management network.
- ETSI TR 101 307 - supplies TIPHON requirements for service interoperability, Phase 2.
- ETSI TS 101 314 - provides the TIPHON network architecture and reference configurations used for the plane and reference-point relationships.
- ETSI TS 101 329-3 - provides end-to-end quality of service signalling and control, including the metrics used in performance management.
What does the SIST-TP TR 101 303 V1.1.2:2004 document contain?
The document uses a roadmap figure to show how TIPHON Release 3 management work fits into later release work. It also includes figures for the TIPHON planes, TNM reference points, functional entity packages, package decomposition, service application and managed object relationships, and management domains and interfaces.
Clause 5 includes a worked example for the service functional layer, showing how generic managed objects and atomic functional packages are structured. Annex A explains the purpose of the TMN layers, and the body of the report uses those layers to explain how management responsibilities are divided across the architecture.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST-TP TR 101 303 V1.1.2:2004 is a technical report published by the Slovenian Institute for Standardization (SIST). Its full title is "Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Requirements definition study; Introduction to service and network management". This standard covers: Note : Part I is WI 1004-(1) part 2 is WI 3014-(2) This work item delivers a service and network management framework for ETSI Tiphon [requirements, information models, management interfaces and information bases]. Based on existing general service & network management frameworks, it defines: Service and Network Management Requirements The roles of network management in TIPHON networks, a common terminology, information models for IP telephony manageable elements and a set of protocols & information bases to communicate network management information.
Note : Part I is WI 1004-(1) part 2 is WI 3014-(2) This work item delivers a service and network management framework for ETSI Tiphon [requirements, information models, management interfaces and information bases]. Based on existing general service & network management frameworks, it defines: Service and Network Management Requirements The roles of network management in TIPHON networks, a common terminology, information models for IP telephony manageable elements and a set of protocols & information bases to communicate network management information.
SIST-TP TR 101 303 V1.1.2:2004 is classified under the following ICS (International Classification for Standards) categories: 33.020 - Telecommunications in general. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST-TP TR 101 303 V1.1.2:2004 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-april-2004
Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON), 3.
izdaja - Študija definicije zahtev - Uvod v upravljanje storitev in omrežja
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON)
Release 3; Requirements definition study; Introduction to service and network
management
Ta slovenski standard je istoveten z: TR 101 303 Version 1.1.2
ICS:
33.020 Telekomunikacije na splošno Telecommunications in
general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
Technical Report
Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON) Release 3;
Requirements definition study;
Introduction to service and
network management
2 ETSI TR 101 303 V1.1.2 (2001-12)
Reference
RTR/TIPHON-01004.1a
Keywords
internet, IP, management, network, telephony,
VoIP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
editor@etsi.fr
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2001.
All rights reserved.
ETSI
3 ETSI TR 101 303 V1.1.2 (2001-12)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope.5
2 References.5
3 Definitions and abbreviations.5
3.1 Definitions.5
3.2 Abbreviations.6
4 Objectives and roadmap .6
5 Generic requirements.7
5.1 TNM framework.7
5.2 Relationship between TNM and Tiphon architecture.8
5.3 Relationship between TNM and Tiphon functional entities.9
5.4 Worked example for the service functional layer.10
5.5 Relationship between TNM and tiphon service capabilities .10
5.6 Management layers, ownership domains and management interfaces .11
6 Fault Management.13
7 Configuration Management.13
8 Accounting Management.13
9 Performance Management.13
10 Security Management.14
11 Information at Management Interfaces .14
Annex A: The purpose of the TMN layers.15
A.1 Element management layer (EML) .15
A.2 Network management layer (NML).15
A.3 Service management layer (SML).15
A.4 Business management layer (BML).16
Annex B: Bibliography.17
History .18
ETSI
4 ETSI TR 101 303 V1.1.2 (2001-12)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Report (TR) has been produced by ETSI Project Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON).
ETSI
5 ETSI TR 101 303 V1.1.2 (2001-12)
1 Scope
The objective of ETSI Project TIPHON is the specification of interoperability mechanisms and related parameters to
enable multimedia communications (particularly voice) to take place, to a defined quality of service, between switched
circuit networks (SCN) and Internet Protocol (IP) based networks and their associated terminal equipment.
The present document presents an overview of the interactions between the Management Plane and the TIPHON
Application Plane and TIPHON Transport Plane. It introduces the framework for the TIPHON Service and Network
Management for ETSI TIPHON releases, capable of supporting TIPHON service capabilities.
The TIPHON network architecture [5] defines real-time operations associated with service control. The management
plane must be capable of managing these services. The framework is based on the TMN model
(ITU-T Recommendation M.3010 [1]) and upon the TeleManagement Forum's Business Process Model for Telecom
Operations. This model includes the well-known "FCAPS" processes - Fault, Configuration, Accounting, Performance,
and Security, structuring them into a form commonly used by service providers.
2 References
For the purposes of this Technical Report (TR) the following references apply:
[1] ITU-T Recommendation M.3010: "Principles for a Telecommunications management network".
[2] ETSI TR 101 307: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON); Requirements for service interoperability; Phase 2".
[3] ITU-T Recommendation M.3020: "TMN Interface Specification Methodology".
[4] ITU-T Recommendation M.3013: "Considerations for a telecommunications management
network".
[5] ETSI TS 101 314: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON); Network architecture and reference configurations; TIPHON Release 2".
[6] TS 101 329-3: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON) Release 3; End-to-End Quality of Service in TIPHON Systems; Part 3: Signalling and
Control of end-to-end Quality of Service.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
administrative domain: network controlled by a single operator (it encompasses both network and management
domains)
management domain: collection of one or more management systems, and zero or more managed systems and
management sub domains that is administered by a single operator
ETSI
6 ETSI TR 101 303 V1.1.2 (2001-12)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
BML Business Management Layer
CMIP Common Management Information Protocol
CMISE Common Management Information Service Element
EML Element Management Layer
IP Internet Protocol
NE Network Element
NML Network Management Layer
OMG Object Management Group
QoS Quality of Service
SCN Switched Circuit Networks
SML Service Management Layer
TNM Tiphon Network Management
UML Unified Modelling Language
4 Objectives and roadmap
Given the broad scope of the service and network management framework, a roadmap is needed to show the sequence
of deliverables and their content for the TIPHON releases. For TIPHON release 4, this roadmap indicates objectives for
TIPHON Network Management (TNM) Framework.
Tiphon Release 4 (Objectives)
Configuration Management
Security Management
Accounting Management
Verification Scenarios for Simple Call Service Application
Tiphon Release 3
Focus on Intra Domain Management and Inter Domain
Management Interfaces
General Requirements
-
- Service and Network Requirements;
- Generic Framework Requirements
- - Framework: UML modeling language, information models
- - Inter Domain Service Management interface
Fault Management
WGs Approval
Requirements & UML use cases
Performance Management
Publications as
Requirements & UML use cases
part of Tiphon
Focus on TIPHON Application Plane
Releases
and TIPHON Transport Plane
& Intra Management Domain
Release 3 Release 4
July 2000 July 2001
Figure 1: Tiphon network management roadmap
ETSI
Tiphon Releases
7 ETSI TR 101 303 V1.1.2 (2001-12)
Definitions 1004
Roadmap
FCAPS Scope
TNM Framework
Generic Requirements
Overview &
Introduction
WI 1004 REPORT
Generic NM Definitions
Specific aspects of TNM
FaFaFaulululttt CoCoConnnfffiiiggguuurrraaatttiiiooonnn AcAcAccccooounununtttiiingngng PePePerfrfrfooorrrmmmaaancncnceee SeSeSecccuuurrriiitttyyy VVVeeerrriiififificccaaatititiooonnn
MMMaaanananagegegemmmeeennnttt MMMaaanananagegegemmmeeennnttt MMMaaanananagegegemmmeeennnttt MaMaMannnaaagggeeemmmeeentntnt MMMaaanananagegegemmmeeennnttt ScScSceeennnaaarrriiiooosss
WI 1011 SPESPESPECCC WI SPECSPECSPEC WI SPECSPECSPEC WI 1010 SPSPSPECECEC WI SPESPESPECCC WI USUSUSEEE CA CA CASSSEEESSS
In Scope
In Scope
To verify that the
Voice QualityAlarm Surveillance
other documents
Call set-up successCorrelation
in this set meet the
Performance Metrics
Testing
needs of network
SLA Monitoring
operators / service
Out of Scope
providers with a set
Out of ScopeService Availability
of agreed use cases.
Hard Faults
Trouble Ticket Admin
Provisioning Faults
Figure 2: Tiphon network management document structure
5 Generic requirements
5.1 TNM framework
The architecture and functional decomposition of TIPHON Network Management shall be based on
ITU-T Recommendation M.3010 [1]. The interface definition methodology for TIPHON management systems shall be
based upon ITU-T Recommendations M.3020 [3] and M.3013 [4].
The TNM framework shall include:
- the TMN layer structure;
- FCAPS processes (Fault, Configuration, Accounting, Performance, Security);
- the definition of information flows between layers, functions and domains;
- the use of a formal methodology for modelling of the management information based upon the OMG's Unified
Modelling Language (UML).
The TNM framework shall also include:
- the definition of information interfaces between TIPHON systems and management systems;
- the definition of Management Information Bases (MIB) based on the UML models.
It shall include:
- the use of Q interfaces unless considered inappropriate.
It shall not include:
- the use of TMN management communication services and protocols based on CMIP/CMISE unless considered
appropriate.
ETSI
------
...