ETSI TR 188 007 V2.1.1 (2008-11)

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network and Service Management; WG8 Specification Guidelines

DTR/TISPAN-08018-NGN

General Information

• Status: Published
• Publication Date: 06-Nov-2008
• Technical Committee: TISPAN 8 - TISPAN Network Management
• Current Stage: 12 - Completion
• Due Date: 28-Oct-2008
• Completion Date: 07-Nov-2008

Standards Content (Sample)

Technical Report
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Network and Service Management;
WG8 Specification Guidelines
2 ETSI TR 188 007 V2.1.1 (2008-11)

Reference
DTR/TISPAN-08018-NGN
Keywords
interface, management, methodology
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TR 188 007 V2.1.1 (2008-11)
Contents
Intellectual Property Rights . 5
Foreword . 5
Introduction . 5
1 Scope . 6
1.1 Motivation and Vision . 6
1.2 Scope . 6
1.3 Non-scope. 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 10
4 Principles of the Guidelines . 11
4.1 Three-Step-Approach . 11
4.2 Reuse of Methodologies . 12
4.3 Units of Standardization . 13
4.4 Modelling . 13
4.5 ETSI documentation of standards . 13
5 NGN Management Specification Methodologies . 14
5.1 Generic Activities and Context Specific Activities . 14
5.2 WG8 Methodology Details. 14
5.2.1 Step 1: Requirements . 15
5.2.1.1 Step 1a: Generic Requirements . 15
5.2.1.2 Step 1b: Context-specific Requirements . 15
5.2.2 Step 2: Technology Independent Modelling . 16
5.2.2.1 Step 2a: Generic, Technology Independent Modelling . 16
5.2.2.1.1 Management Information Model (MIM) . 16
5.2.2.1.2 Meta-Model . 16
5.2.2.2 Step 2b: Context Specific, Technology Independent Modelling . 16
5.2.2.2.1 UML Information Model . 16
5.2.2.2.2 Functional Architecture/Technology-Independent NOSI . 17
5.2.3 Step 3: Technology Dependent Modelling . 17
5.2.3.1 Step 3a: Generic, Technology Dependent Modelling . 17
5.2.3.2 Step 3b: Context Specific, Technology Dependent Modelling . 17
5.3 Tool-based Approach . 18
5.3.1 Tool Chain . 18
5.3.2 Tools . 18
6 Mapping from WG8 Methodology Elements to WG8 Standards Documents . 18
6.1 Titles and Objectives of documents. 18
6.2 Mapping to TISPAN WG8 documents . 19
Annex A: Existing Methodologies . 20
A.1 Management Interface Specification Methodology (ITU-T) . 20
A.2 Integration Reference Points (3GPP) . . 21
A.3 mTOP Specification Guidelines (TMF) . 23
A.4 NGOSS Lifecycle (TMF) . 24
A.4.1 Background . 24
A.4.2 Lifecycle View of Interfaces and Contracts . 24
A.4.3 Relation with NOSIs . 25
ETSI
4 ETSI TR 188 007 V2.1.1 (2008-11)
A.4.4 Documenting the Lifecycle Views . 27
History . 28

ETSI
5 ETSI TR 188 007 V2.1.1 (2008-11)
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 Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
Introduction
The present document describes the specification methodology in ETSI TISPAN WG8. The present document includes
guidelines for the specification of NGN OSS Service Interfaces (NOSI) throughout all the steps necessary for their
standardization. The present document accompanies the specification process in WG8 by documenting the way of work.
Clause 1 outlines the background and motivation for the present document, and describes vision and scope for the
specification guidelines.
Clauses 2 and 3 give references, definitions, and clarify abbreviations in the context of the present document.
Clause 4 develops the basic principles of the specification guidelines which are the foundation for the work in WG8.
Clause 5 elaborates the WG8 specification methodology by investigating each step in detail. Furthermore, a tool-based
approach is introduced to ease and accelerate the standardization process by automation.
Clause 6 deals with naming conventions for the ETSI TISPAN WG8 documents, and the mapping of the methodology
steps to existing and planned documents.
Annex A includes a description of existing methodologies and their importance for the work in WG8.
ETSI
6 ETSI TR 188 007 V2.1.1 (2008-11)
1 Scope
1.1 Motivation and Vision
In ETSI TISPAN WG8's current NGN Management related work, standards forming principles are being used
implicitly. Therefore, Specification Guidelines are necessary to transform these implicitly existing principles to
explicitly described principles. These WG8 Specification Guidelines should reflect and, if necessary, modify or unify
explicit principles. Consequently, the basic driver and motivation for the evolution of such WG8 Specification
Guidelines are the currently running WG8 standardization activities in the area of NGN OSS. From this point of view,
the work on the Specification Guidelines has an accompanying character to WG8's regular standards forming process.
The vision standing behind this work is that ETSI TISPAN WG8 has a clear understanding of how to develop NOSIs
from an idea to standard documents, following a set of guidelines which head, ease, and accelerate the whole standards
developing process, and using a consistent terminology.
1.2 Scope
The present document puts on record the WG8 internal way how to develop ideas to standard documents.
The basis of the present document is a status-quo analysis of WG8's way to develop ideas to standards. Therefore,
implicitly existing steps of the actual WG8 standardization activities have been identified and their purpose has been
clarified. These implicit steps have then been reflected, consolidated, and transformed to explicit methodology
elements.
The present document captures the above mentioned reflected, consolidated, explicit steps and bundles them to a
consistent WG8 methodology. The present document sets the WG8 methodology in relation to a list of well-selected
existing methodologies or wide-spread standards forming technologies, and considers the use of these methodologies in
WG8. Furthermore, the present document provides guidelines how to map explicit methodology elements to standards
documents.
The present document tracks how the WG8 specifications are currently produced, i.e. it describes the ongoing and it
will direct the future work of ETSI TISPAN WG8. However, not all aspects of the WG8 methodology are already fully
defined and ready to be documented. Those aspects are identified in the present document as "for further study".
The scope of the present document explained before is depicted in figure 1.

Identification&Clarification Documentation of the
concerning their purpose results in TR 188 007
Consistent
Implicitly existing
Investigation, Analysis Explicit WG8
steps of WG8 WG8 internal
and Evaluation methodology
Specification
standardization
of current methods steps
work Guidelines
Reflection, Consolidation Consideration of proved
and Transformation existing methodologies

Figure 1: Scope of WG8 Specification Guidelines
ETSI
7 ETSI TR 188 007 V2.1.1 (2008-11)
1.3 Non-scope
The following items are out of the scope of the present document:
• Guidance for other ETSI WGs or standardization bodies than TISPAN WG8.
• Definition of a new standardization process in the sense of refining or formalizing the guidelines.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
Not applicable.
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] ETSI TS 188 001: "Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); NGN management; Operations Support Systems Architecture".
[i.2] ETSI TS 188 002-1: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Subscription Management; Part 1: Requirements".
[i.3] ETSI TS 188 002-2: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network and Service Management; Subscription Management;
Part 2: Information Model".
ETSI
8 ETSI TR 188 007 V2.1.1 (2008-11)
[i.4] ETSI TS 188 002-3: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network and Service Management; Subscription Management;
Part 3: Functional Architecture".
[i.5] ITU-T recommendation M.3020: "Management interface specification methodology".
[i.6] ETSI TS 132 150: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Integration Reference
Point (IRP) Concept and definitions (3GPP TS 32.150)".
[i.7] TMF: "mTOP Specification methodology".
NOTE: Available at http://www.tmforum.org/.
[i.8] OASIS Standard: "Reference Model for Service Oriented Architecture 1.0".
[i.9] TMF Specification 053B: "Technology Neutral Architecture, Contract Description: Business and
System Views, V4.4".
[i.10] OMG Specification: "Unified Modelling Language, V2.1.1".
[i.11] TMF Specification GB921: "Enhanced Telecom Operations Map, Release 7".
[i.12] 3GPP TS 32.155: "3rd Generation Partnership Project; Technical Specification Group Services
and System Aspects; Telecommunication management; Requirements template".
[i.13] TMF Specifications GB922 & GB926: "SID Solution Suite, Release 7.0".
[i.14] ETSI TS 132 101: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Principles and high level
requirements (3GPP TS 32.101)".
[i.15] ETSI TS 132 151: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Integration Reference
Point (IRP) Information Service (IS) template (3GPP TS 32.151)".
[i.16] ETSI TS 132 152: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Integration Reference
Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire
(3GPP TS 32.152)".
[i.17] 3GPP TS 32.153: "3rd Generation Partnership Project; Technical Specification Group Services
and system Aspects; Telecommunication management; Integration Reference Point (IRP)
technology specific templates, rules and guidelines".
[i.18] ETSI TS 132 154: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; Backward and Forward
Compatibility (BFC); Concept and definitions (3GPP TS 32.154)".
[i.19] TMF Specification GB927: "TMF Lifecycle Methodology, V1.1".
[i.20] ETSI TR 188 004: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Management; OSS vision".
[i.21] ETSI TR 102 647: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network Management; Operation Support System Standards
Overview and Gap Analysis".
[i.22] ETSI TS 188 003: "Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); OSS requirements; OSS definition of requirements and
priorities for further network management specifications for NGN".
[i.23] ETSI TS 188 005-1: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Management; Network Resource Model (NRM);
Part 1: Requirements".
ETSI
9 ETSI TR 188 007 V2.1.1 (2008-11)
[i.24] ETSI TS 188 005-2: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network and Service Management; Network Resource Model;
Part 2: Information Service".
[i.25] ETSI TS 188 005-3: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network and Service Management; Network Resource Model;
Part 3: eXtensible Markup Language (XML) Schema definition".
[i.26] ETSI TS 132 732: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Telecommunication management; IP Multimedia
Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP):
Information Service (IS) (3GPP TS 32.732)".
[i.27] ITU-T recommendation M.3060/Y.2401: "Principles for the Management of the Next Generation
Networks".
[i.28] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture".
[i.29] 3GPP TR 32.809: "3rd Generation Partnership Project; Technical Specification Group Services
and System Aspects; Telecommunication management; Feasibility Study of XML-based
(SOAP/HTTP) IRP Solution Sets".
[i.30] 3GPP TR 32.818: "3rd Generation Partnership Project; Technical Specification Group Services
and System Aspects; Telecommunication management; Study on 3GPP SA5/MTOSI XML
harmonization".
[i.31] ETSI TS 188 008: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IPTV Management; Context and Requirements".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
contract: fundamental unit of interoperability in an NGOSS system
NOTE: It is much more than a software interface specification. Rather, the contract is a specification of how a
managed entity interacts with its environment. As such, it includes other aspects of the solution in
addition to software [i.9].
guidelines: provide instructions and advice for performing a task or activity, and suggest possible approaches to reach a
pre-defined goal
information model: conceptual/analysis/domain/semantic model that represents real-world objects. It includes things
of interest (entities), relationships between these entities (associations), and details/characteristics of these entities
(attributes)
NOTE: It provides a way of structuring information, standard definitions, and a consistent common terminology.
There are several terms for an information model in different standardization organizations
(e.g. information service, information agreement). In order to use a unique term, within the present
document the term information model is used.
methodology: documented approach for performing activities in a coherent, consistent, accountable, and repeatable
manner
NGN OSS Service Interface (NOSI): well defined grouping of related NGN OSS Operations and constant data which
are necessary to deliver coherent business or system functionality [i.1]
ETSI
10 ETSI TR 188 007 V2.1.1 (2008-11)
Service Oriented Architecture (SOA): paradigm for organizing and utilizing distributed capabilities that may be
under the control of different ownership domains [i.8]. It is an evolution of distributed computing and modular object-
oriented programming
NOTE: SOA builds applications out of software services. Services are relatively large, intrinsically unassociated
units of functionality, which have no calls to each other embedded in them. They typically implement
functionalities as services. Instead of services embedding calls to each other in their source code,
protocols are defined which describe how one or more services can talk to each other. This architecture
then relies on a business process to link and sequence services, in a process known as orchestration, to
meet a new or existing business system requirement.
SOA service interface concept: means for interacting with a service. It includes the specific protocols, commands, and
information exchange by which actions are initiated that result in the real world effects as specified through the service
functionality portion of the service description
NOTE: The specifics of the interface should be syntactically represented in a standard referenceable format
prescribing what information needs to be provided to the service in order to access its capabilities and
interpret responses. It is not specified how the consumer accesses the interface definition nor how the
service itself is accessed. However, it is assumed that for a service to be usable, its interface is represented
in a format that allows interpretation of the interface information by its consumers [i.8].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASN.1 Abstract Syntax Notation No.1
BA Business Agreement
CMIP Common Management Information Protocol
CORBA Common Object Request Broker Architecture
DDP Document Delivery Package
eTOM enhanced Telecom Operations Map
GDMO Generic Definition of Managed Objects
IA Information Agreement
IDL Interface Definition Language
IIS Interface Implementation Specification
IOC Information Object Class
IRP Integration Reference Point
IS Information Service
JMS Java Message Service
MIM Management Information Model
MISM Management Interface Specification Methodology
mTOP multi Technology OSS Program
MTOSI Multi-Technology Operations System Interfaces
NGN Next Generation Network
NGOSS New Generation Operations Systems and Software
NOSI NGN OSS Service Interface
NRM Network Resource Model
OSS Operations Support System
SID Shared Information and Data model
SNMP Simple Network Management Protocol
SOA Service Oriented Architecture
SOAP Simple Object Access Protocol
SuM Subscription Management
TIP TeleManagement Forum Interface Program
TMF TeleManagement Forum
UML Unified Modelling Language
WS Web Services
WSDL Web Service Definition Language
XML eXtensible Markup Language
ETSI
11 ETSI TR 188 007 V2.1.1 (2008-11)
4 Principles of the Guidelines
This clause clarifies and describes important principles of the WG8 Specification Guidelines in terms of basic
methodology approach, re-use of existing specification methodologies, actual objects of standardization, modelling
technologies used for the specification work as well as documentation of the standards developed in WG8.
4.1 Three-Step-Approach
During the development of standards in ETSI TISPAN WG8 basically a three-step-approach (see figure 2) is used. This
approach comprises the following steps:
• Step1 (Requirements): This step includes the conceptual definitions, use cases and traceable requirements
related to a certain aspect of NGN OSS standardization. In WG8 this is mainly related to NOSIs (see
clause 4.3). Traceability of the requirements should be ensured in all subsequent phases. An update of the
requirements may be needed, e.g. after discovery of new aspects during phase 2.
EXAMPLE 1: Use cases and requirements for Subscription Management [i.2].
• Step 2 (Technology-independent modelling): This step comprises the definition of information-bearing
entities, their properties, and relationships between them, in a technology-independent way. In the context of
SOA, this includes the identification and separation of operations (verbs) and attributes (nouns), according to
particular NGN OSS Services. This work is based on the requirements in step 1 and allows finally the
technology-independent definition of NOSIs (see clause 4.3).
EXAMPLE 2: Information model [i.3] and functional architecture for Subscription Management [i.4].
• Step 3 (Technology-dependent modelling): This step provides the mapping of the technology-independent
NOSI definitions of step 2 to NOSI definitions in a specific interface technology.
EXAMPLE 3: Interface specification for Subscription Management in IDL, XML and WSDL.
As far as possible the activities in all three steps should be supported by tools which make a certain degree of
automation possible (see clause 5.3). The three-step-approach is described in more detail in clause 5 of the present
document.
This approach in ETSI TISPAN WG8 follows a SOA-based methodology (see figure A.2), as opposed to object-
oriented methodology, with a composition of interfaces according to related NGN OSS services (see clause 5.3). The
management entities as NGN OSS services are connected by well-defined interface agreements or contracts, which are
the NOSIs (see clause 4.3). This proceeding is also in line with considerations in TMF NGOSS [i.9], TMF mTOP/TIP,
and in ITU-T recommendation M.3060 [i.27].
ETSI
12 ETSI TR 188 007 V2.1.1 (2008-11)

Guidelines
From an idea to a standard document:
Informal definition of proceedings
Step 1: Step 2: Step 3:
Definition Technology Independent Technology Dependent
of Requirements Modelling Modelling
Other TISPAN WGs External Sources
WG1: Services3GPP SA5
WG2: Architecture ITU-T SG4
WG3: ProtocolsTMF NGOSS & mTOP/TIP
WG4: Numbering/AddressingATIS TMOC
WG5: Home Networking Other groups

Figure 2: Three-Step-Approach
The Specification Guidelines provide an informal description of the proceedings in all three steps of this approach as
outlined in clause 1 of the present document.
The standardization work is influenced by several other ETSI TISPAN Working Groups (WG), e.g. WG 1, 2, 3, 4, 5
and groups in other standardization bodies, e.g. 3GPP SA5, ITU-T SG4, and TMF NGOSS/mTOP/TIP. This influence
can be of different nature, e.g.:
• The work can be the basis for WG8 specification activities, e.g. the NGN functional architecture of TISPAN
WG2 [i.28] is the foundation for the Network Resource Model (NRM) specifications.
• There can be some similar activities in other bodies that require co-operation and harmonization, e.g. the
subscription management work in 3GPP SA5 and TMF mTOP/TIP.
4.2 Reuse of Methodologies
In the area of OSS interface specification there are already methodologies in place in various standardization bodies.
These are mainly the following:
• Management Interface Specification Methodology (MISM) by ITU-T SG4 in recommendation M.3020 [i.5].
• Integration Reference Point (IRP) concept by 3GPP SA5 in recommendation TS 132 150 [i.6].
• Interface Specification Guidelines by TMF mTOP [i.7].
They all use a kind of three-step-approach with different terminologies, but with similar content.
In the course of efficiency and to prevent unnecessary work as much as possible existing methodologies, or parts of
them, should be re-used or adapted by ETSI TISPAN WG8.
Annex A investigates the existing methodologies listed above, and evaluates their use for the three steps (see figure 2)
of WG8's specification methodology.
ETSI
13 ETSI TR 188 007 V2.1.1 (2008-11)
4.3 Units of Standardization
Within TISPAN WG8 it has been agreed (on TISPAN level) that the actual units of WG8 standardization are
SOA-based NGN OSS Service Interfaces (NOSIs), in contrast to object-oriented interfaces.
According to the definition in [i.1] a NOSI (graphically depicted as a lollipop) is a well defined grouping of related
NGN OSS Operations and constant data which are necessary to deliver coherent business or system functionality.
The NOSI is:
• The fundamental unit of standardization.
• An aggregation of functionality required for managing some coherent aspect of the NGN network or services.
This functionality is provided through a set of related behaviour/functionality and is made publicly available
for use by consumers of this service interface.
• Comprised of a set of mandatory NGN OSS Operations.
• Equivalent to the SOA service interface concept [i.8] and NGOSS Contract [i.9] (see clause A.4).
As output of ETSI TISPAN WG8 there will be technology-independent NOSI specifications as a result of phase 2
(see figure 2 and clause 5.2.2.2.2), and (ideally automatically generated) technology-dependent NOSI specifications as a
result of phase 3 (see figure 2 and clause 5.2.3.2).
4.4 Modelling
Modelling is the preferred formal designing technique for ETSI TISPAN WG8. It will be mainly used for the
technology-independent modelling in phase 2 (see figure 2).
The preferred language that is used for this modelling is UML [i.10]. It can be used for the design of information
models with information object classes (IOC), for associated meta-models as well as for the protocol-agnostic
description of NOSIs in phase 2 of the standard development process.
ETSI TISPAN WG8 is planning to use UML V2.x.
UML provides the basis for an automated tool-based approach (see clause 5.3), e.g. for generating technology-
dependent phase 3 specifications from technology-independent phase 2 specifications with the help of commercial
UML suites.
Furthermore, UML can be used for the description of use cases in phase 1 (see clause 5.2.1.2).
4.5 ETSI documentation of standards
All ETSI TISPAN WG8 technical documents that follow the three-step-approach (see clause 4.1) should be ETSI
Technical Specifications (TS), at least the specifications for the context-specific aspects (see clause 5.1). The informal
documents within the generic activities should be Technical Reports (TR).
Related to a specific NGN OSS functional area, e.g. subscription management or network resource management, within
each step of the WG8 standard development process one or more TS documents will be produced as output:
• Phase 1: Use cases and Requirements (one document).
• Phase 2: Information Model, Functional Architecture (two documents).
• Phase 3: Technology-dependent definition (one document per technology).
In principle, phase 1, phase 2, and phase 3 documents depend on each other which implies sequential work on the
documents. Nevertheless, all documents can be progressed in parallel if there is a sufficient degree of co-operation,
exchange of information and harmonization.
Further details about the mapping from WG8 Methodology steps to WG8 Standards Documents, e.g. naming and
terminology conventions, will be elaborated in clause 6 of the present document.
ETSI
14 ETSI TR 188 007 V2.1.1 (2008-11)
5 NGN Management Specification Methodologies
This clause describes NGN Management Specification Methodologies with focus on ETSI TISPAN WG8 Methodology
following a best practise approach. The foundation for these methodologies is the three-step-approach which is briefly
outlined in clause 4.1 of the present document (see figure 2). Clause 5.1 details the three-step-approach in terms of a
differentiation between generic and context-specific activities. Within clause 5.2 the three-step-approach is elaborated
in more detail for each step, concerning the work in ETSI TISPAN WG8. In clause 5.3 the tool-based approach is
described which supports the work in all steps, and the transition from one step to the next one.
5.1 Generic Activities and Context Specific Activities
The basic three-step-approach described in clause 4.1 of the present document (see figure 2) can be divided into two
horizontal streams (see figure 3):
• Kind a: Generic activities.
• Kind b: Context-specific activities.
Generic activities concern activities that are of common importance for all different kinds of context-specific activities.
Generic activities can be for example generic requirements, common architecture principles, or overarching information
models and meta-models.
Context-specific activities concern activities in the context of an interface specification for a specific NGN OSS
functional area, for example subscription management, network resource management, charging, fault management,
service quality management, or IPTV. These functional areas can be usually taken from the eTOM processes [i.11].
This differentiation is the basis for a further elaboration of the WG8 specification guidelines in clause 5.2.

Guidelines
Contexts
From an idea to a standard document:
E.g. SuM, NRM, Charging,
Informal definition of proceedings
Fault Management, Service
Quality Management, IPTV
Kind a: Generic Activities
Kind b: Context Specific Activities

Figure 3: Generic and context specific activities
5.2 WG8 Methodology Details
This clause investigates the details of the specification methodology in ETSI TISPAN WG8. Figure 4 shows the
integration of the three-step-approach (figure 2) with the introduction of common and context-specific activities
(figure 3) that is applied to the work in ETSI TISPAN WG8. According to this structure the following clauses elaborate
the single methodology steps in detail.
ETSI
15 ETSI TR 188 007 V2.1.1 (2008-11)
Guidelines
Contexts
From an idea to a standard document:
E.g. SuM, NRM, Charging,
Informal definition of proceedings
Fault Management, Service
Quality Management, IPTV
Step 1a Step 2a Step 3a
Definition of Generic Requirements Technology Independent Modelling Technology Dependent Modelling
NGN OSS Analysis and requirements Meta-Models  Formal Management Information
Model (MIM) NGN OSS Scope and vision
- NGN OSS Architecture principles Meta Models
Step 1b Step 2b Step 3b
Context specific requirements Context specific model Context specific and technology
- dependent models
Context specific information Context specific use cases
model / Integration with the MIM -
and requirementsContext and technology
Context-specific Functional Context specific scope dependent NOSI
Architecture / Technology E.g. XML/WSDL, CORBA/IDL,
independent NOSI
SNMP, CMIP
Figure 4: WG8 Methodology Details
5.2.1 Step 1: Requirements
5.2.1.1 Step 1a: Generic Requirements
Generic requirements in the context of ETSI TISPAN WG8 concern common requirements on NGN OSS in a broader
sense, to sharpen and restrict the problem area as a whole. The work includes:
• An analysis of the problem area, in case of WG8 the NGN OSS, concerning existing standards and gaps.
• Scope and vision of the whole work in the NGN OSS area.
• Common requirements on NGN OSS to be met by all context-specific activities.
• Architecture principles that should apply to all context-specific activities in the area of NGN OSS.
• Requirements on a common Management Information Model (see clause 5.2.2.1.1).
5.2.1.2 Step 1b: Context-specific Requirements
The first step within the stream of context-specific activities is the development of requirements. This is to guide and
ease the following steps.
An important issue is the traceability of requirements across all phases of the specification process to ensure the
consideration of each requirement, e.g. by use of a suitable enumeration scheme for references. The aim is to have a
bi-directional (forward and backward) referencing scheme.
It is recommended to define Use Cases to either derive or emphasize the requirements for the particular context, i.e.
specific service interfaces for NGN OSS. The use cases should be defined with the help of UML use case diagrams.
For the definition of context-specific requirements in WG8, the requirements template (including the use case template)
for the requirements phase in ITU-T recommendation M.3020, annex A [i.5] will be used. It is part of the Management
Interface Specification Methodology (MISM) of ITU-T SG4 (see clause A.1). This template has also been completely
taken over by 3GPP TS 32.155 [i.12] and will be used by 3GPP SA5 within its Integration Reference Point (IRP)
methodology (see clause A.2).
The joint M.3020/3GPP template will be used by WG8 for all future context-specific requirement specifications.
An update of the requirements and use cases should be possible if new aspects rise in subsequent phases of the
specification process.
ETSI
16 ETSI TR 188 007 V2.1.1 (2008-11)
5.2.2 Step 2: Technology Independent Modelling
5.2.2.1 Step 2a: Generic, Technology Independent Modelling
A generic technology-independent modelling in the context of ETSI TISPAN WG8 concerns the specification of a
Management Information Model (MIM) from which the context-specific information models can be derived as well as
the definition of a common meta-model as a kind of methodology for handling information models, to ease the
integration of information models from different standardization bodies.
5.2.2.1.1 Management Information Model (MIM)
A TISPAN Management Information Model (MIM) would focus on designing and specifying an information
abstraction and representation of the TISPAN management entities - their properties, operations, and relationships,
independent of any specific repository, application, protocol, or platform. This is similar in scope to the TMF SID
Business View and System View [i.13]. This information model also provides a linkage between services defined
within ETSI TISPAN WG1 and TISPAN management entities.
Candidates to be considered for the MIM are TMF SID [i.13] and 3GPP NRM [i.26]. SID seems to be a reasonable
basis for the decomposition of the MIM into different domains, whereas for the resource domain the integration
between NRM and SID seems to be appropriate. Thus, a combination of SID and NRM with some enhancements could
represent the MIM from which specific information models, e.g. for SuM, can be derived.
To specify the MIM, consolidated requirements (see clause 5.2.1.1) and an information model in UML have to be
elaborated. Both activities are for further study.
5.2.2.1.2 Meta-Model
A meta-model is a model that describes abstract syntax and semantics of a domain. An information model is an instance
of a meta-model. A meta-model defines the concepts for modelling an information model.
The UML language of TISPAN, 3GPP and SID domains could be represented by a meta-model and provides a way of
integration between these models. A meta-model could ease the further development of SuM, NRM and MIM
information models, and achieve a harmonization of the different terminologies.
From such a common meta-model aspects of different information models for specific contexts can be derived where
necessary.
Until now no final decision has been made about the development of a common meta-model in ETSI TISPAN WG8
(for further study). A candidate to be considered is the TMF NGOSS meta-model.
5.2.2.2 Step 2b: Context Specific, Technology Independent Modelling
The second step within the stream of context-specific activities is the protocol-independent modelling of a particular
context, i.e. NOSIs, based on the requirements of step 1b (see clause 5.2.1.2). For each context-specific aspect, an
information model in UML and a functional architecture with a technology-independent
...