SIST-TP TR 101 835 V1.1.1:2004

• Abstract:

  To define and declare the methods by which the TIPHON project will manage the identification and prioritisation of requirements within the TIPHON project.

• Status: Published
• Publication Date: 31-Mar-2004
• ICS: 33.020 - Telecommunications in general
• 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
• Ref Project: ETSI TR 101 835 V1.1.1 (2000-07) - Telecommunications and Internet Protocol Harmonization over Networks (TIPHON); Project method definition

SIST-TP TR 101 835 V1.1.1:2004 is a Slovenian standard identical to ETSI TR 101 835 V1.1.1 for Telecommunications and Internet Protocol Harmonization over Networks (TIPHON). It specifies the project method TIPHON uses to identify, qualify, schedule and prioritise requirements, and it is intended for TIPHON members, working group chairs, work item rapporteurs and the TIPHON Project Management Committee.

What does SIST-TP TR 101 835 V1.1.1:2004 specify?

SIST-TP TR 101 835 V1.1.1:2004 defines the specification development process used to keep TIPHON releases coherent and delivered in a timely way. It sets out how the project turns broad needs into a managed release, then into architectures, interfaces, mappings and conformance material.

The document is organised around a five-step process in clause 4, followed by release deliverables in clause 5.

Annex	What it covers
Annex A	Requirements Definition Studies, including suggested report headings
Annex B	Technology mapping and compliance, including how to report non-conformance
Annex C	Relationships between process steps and TIPHON Working Groups

What are the key requirements of SIST-TP TR 101 835 V1.1.1:2004?

From requirements to releases

Clause 4.1 says TIPHON work shall start from clearly stated requirements drawn from the TIPHON scope, TIPHON scenarios and specific market requirements. If an issue is not clear enough, a Requirements Definition Study (RDS) is needed before the topic can be taken into a release. In practice, this stops teams from building a release around incomplete or disputed requirements.

Clause 4.2 says a TIPHON release shall be built from qualified requirements, with a statement of the top-level topics to be addressed and a plan that identifies the related work items. That means release planning is not just a list of ideas - it is a controlled work package.

Architecture and implementation

Clause 4.3 requires Step B to develop Service Capability Definitions and associated Statements of Service Independent Requirements. TIPHON focuses on user and network capabilities that can be assembled into service capabilities, rather than specifying end services themselves. For readers, this means the standard is about the building blocks needed for services, not the commercial service offer.

Clause 4.4 requires Step C to create a Reference Architecture that is independent of underlying technology where possible, together with management and network information flows. This gives the project a stable design view before technology choices are fixed.

Clause 4.5 then maps that architecture into protocol and management frameworks. These frameworks identify the key interfaces and the behavior expected across each interface, which is what engineers need before they can write implementation requirements.

Mapping, conformance and compliance

Clause 4.6 and Annex B require the interface definitions to be mapped to the technologies supported by the release. Where a technology meets the interface requirements, a protocol profile is produced. Where it does not, the mapping must clearly state the non-conformance so the technology developer can see the gap and decide on corrective action or extension.

Clause 4.6 also requires Protocol Implementation Conformance Specifications and a security analysis and compliance specification. In practice, that gives the release a final check that the chosen profiles can be implemented correctly and that security and integrity issues have been addressed.

Annex A adds a controlled format for RDS reports, with issue statement, issue scope, discussion, and conclusions/results/recommendations. Annex C links each process step to the TIPHON Working Groups, which helps with task allocation and coordination.

What terms does SIST-TP TR 101 835 V1.1.1:2004 define?

• Step - a discrete phase of major activity within the process.
• Requirements Definition Study (RDS) - a focused piece of work used to explore requirements that are not yet clear enough.
• Service Capability Definition - the description of the core network and management capabilities expected for a release.
• Service Independent Requirements - requirements captured separately from a particular service implementation.
• Reference Architecture - the static, technology-independent design view for a release.
• Protocol Framework - the set of key protocol interfaces needed for a compliant release.
• Protocol profile - the defined way a protocol is to be used to implement an identified interface.

Who uses SIST-TP TR 101 835 V1.1.1:2004?

TIPHON members use this document to plan work and keep releases aligned with the project scope. Working group chairs and work item rapporteurs use it to organise studies, define deliverables and move requirements through the process.

The TIPHON Project Management Committee uses it to coordinate release planning and review progress. Technology, protocol and management specialists use it when mapping requirements to technologies, checking conformance and preparing security analysis.

What changed in SIST-TP TR 101 835 V1.1.1:2004 from the previous edition?

SIST-TP TR 101 835 V1.1.1:2004 is the Slovenian identical adoption of ETSI TR 101 835 V1.1.1 (2000-07).

Which standards are used with SIST-TP TR 101 835 V1.1.1:2004?

• ITU-T Recommendation I.130 (1988) - provides the ISDN method for characterising telecommunication services and network capabilities.
• ETSI TS 122 105 (V3.7.0) - provides UMTS services and service capabilities terminology and structure that TIPHON uses as a point of reference.

What does the SIST-TP TR 101 835 V1.1.1:2004 document contain?

The document contains an introduction to the TIPHON process, a five-step release method, and a list of deliverables for each step. It also includes guidance on how to run Requirements Definition Studies, how to map technologies and report compliance, and how the TIPHON Working Groups fit into the process.

Its figures show the release flow, capability definition, reference architecture, implementation framework, technology mapping and the final conformance and security checks. For users, those figures are the quickest way to see how TIPHON moves from requirements to specifications and then to implementation profiles.

SLOVENSKI STANDARD
01-april-2004
Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON) -
Definicija projektne metode
Telecommunications and Internet Protocol Harmonization over Networks (TIPHON);
Project method definition
Ta slovenski standard je istoveten z: TR 101 835 Version 1.1.1
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);
Project method definition
2 ETSI TR 101 835 V1.1.1 (2000-07)
Reference
DTR/TIPHON-01007
Keywords
IP, methodology, planning, procedure, VoIP
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://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
[e-mail]
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 2000.
All rights reserved.
ETSI
3 ETSI TR 101 835 V1.1.1 (2000-07)
Contents
Intellectual Property Rights.4
Foreword.4
Introduction .4
1 Scope .5
2 References .5
3 Definitions and abbreviations.5
3.1 Definitions.5
3.2 Abbreviations .5
4 Overview of the TIPHON process .6
4.1 TIPHON Release Schedule .6
4.2 Step A - Release Definition.7
4.3 Step B – Capabilities and Requirements .8
4.4 Step C – Reference Architecture .9
4.5 Step D – Implementation Framework .10
4.6 Step E - Technology Mapping and Verification.11
5 Deliverables for TIPHON Releases .13
5.1 Deliverables for Step A .13
5.2 Deliverables for Step B .13
5.3 Deliverables for Step C .13
5.4 Deliverables for Step D .13
5.5 Deliverables for Step E.13
Annex A: Requirements Definition Studies.14
A.1 Introduction .14
A.2 Headings for RDS reports .14
Annex B: Technology Mapping and Compliance .15
B.1 Mapping and Compliance .15
Annex C: Relationships between process steps and TIPHON WGs.16
C.1 Roles of TIPHON Working Groups in the Process.16
History .18
ETSI
4 ETSI TR 101 835 V1.1.1 (2000-07)
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://www.etsi.org/ipr).
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).
Introduction
The ETSI Project TIPHON considers a broad range of complex networking technologies and the inter-working of those
technologies to provide capabilities that may be used to provide public services. Given the complexity of these issues
and the pace of technological development, the project requires a clear internal management process by which it can
identify, quantify, schedule and deliver its work in a timely and organized manner. The present document draws upon
and modifies related procedures developed for the production of ISDN [1] and UMTS [2] specifications and declares a
process to be used within the TIPHON project.
ETSI
5 ETSI TR 101 835 V1.1.1 (2000-07)
1 Scope
The present document defines the specification development process to be used to ensure the TIPHON project develops
coherent specifications in a timely manner.
The present document is applicable to members of the TIPHON project, working group chairs, work item rapporteurs
and the TIPHON Project Management Committee. It should be referenced when planning work to be undertaken by the
project.
2 References
The following documents contain provisions that, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, subsequent revisions do apply.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ITU-T Recommendation I.130 (1988): "Method for the characterization of telecommunication
services supported by an ISDN and network capabilities of an ISDN".
[2] ETSI TS 122 105 (V3.7.0): "Universal Mobile Telecommunications System (UMTS); Services
and Service Capabilities (3G TS 22.105 version 3.7.0 Release 1999)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Step: discrete phase of major activity within the process.
RDS: focussed piece of work that is undertaken to explore requirements that are not sufficiently clear.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ISDN Integrated Services Digital Network
RDS Requirements Definition Study
TIPHON Telecommunications and Internet Protocol Harmonization Over Networks
TR ETSI Technical Report
TS ETSI Technical Specification
ETSI
6 ETSI TR 101 835 V1.1.1 (2000-07)
4 Overview of the TIPHON process
The TIPHON project considers a wide range of complex technology issues arising from the inter-working of differing
and independently evolving network technologies. The TIPHON process therefore comprises two distinct stages. The
first stage is concerned with establishing a fixed set of requirements to be worked on and in doing so defines the scope
of a TIPHON Release. Whilst the second stage is concerned with developing a coherent set of specifications from a
fixed set of requirements for a specific TIPHON Release, as shown in Figure 1.
TIPHON
scenarios
TIPHON
Requirements
Scope of
Release
Definition
TIPHON
Scheduling
Studies
Market
Requirements
Step A Step B Step C Step D Step E
Step A Step B Step C Step D Step E
Step A Step B Step C Step D Step E
Step A Step B Step C Step D Step E
Release n
Figure 1: Overview of the TIPHON process
4.1 TIPHON Release Schedule
The TIPHON project shall work towards its goals from clearly stated and expressed requirements derived from three
sources; the TIPHON project scope, the TIPHON scenarios and specific market requirements. Where an aspect relevant
to the TIPHON project cannot be clearly stated or is insufficiently understood from these three sources, a TIPHON
Requirements Definition Study (RDS) will be required before these aspects can be considered for incorporation within a
Release. A Requirements Definition Study considers various aspects of a given topic as is appropriate and produces a
qualified set of requirements relating to the topic as a result. The project will therefore be constrained to working on a
clearly understood, scoped and qualified set of requirements within each Release whilst having the ability through
Requirements Definition Studies to adapt to a continually changing environment.
ETSI
7 ETSI TR 101 835 V1.1.1 (2000-07)
4.2 Step A - Release Definition
As shown in Figure 2, a TIPHON Release shall be constructed from a set of qualified requirements that can be
progressed through to a coherent and focussed set of specifications of the necessary quality within an acceptable period
of time. The Release definition shall comprise a statement of the top-level topics to be addressed within a specific
release and the declaration of a plan with the identification of the associated work items.
TIPHON Scope, Scenarios,
Market Requirements and Requirements Definition Studies
TIPHON
TIPHON
Release Definition
Release n Plan
for Release n
Other Steps
Step B
Step B
Figure 2: Step A - Release Definition in TIPHON
ETSI
8 ETSI TR 101 835 V1.1.1 (2000-07)
4.3 Step B – Capabilities and Requirements
Based upon the information contained and referenced by a TIPHON Release Definition, Step B will develop
appropriate Service Capability Definitions and associated Statements of Service Independent Requirements. These
aspects of the process draw upon but are not constrained by the stage 1 elements of the ISDN three stage process. A
complete application of that process has not been adopted by the TIPHON project for two reason – firstly it would
simply lead to a recreation of an ISDN on an IP cor
...