Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); Verification Demonstration and Interoperability (VDI) activities; Version 3

RTR/TIPHON-06003

Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON) - Demonstracija preverjanja in medobratovalnost (VDI) - Različica 3

General Information

Status
Published
Publication Date
20-Jan-2000
Current Stage
12 - Completion
Due Date
23-Jun-2000
Completion Date
21-Jan-2000

Buy Standard

Technical report
TP TR 101 334 V3.1.1:2004
English language
21 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST-TP TR 101 334 V3.1.1:2004
01-april-2004
+DUPRQL]DFLMDWHOHNRPXQLNDFLMLQLQWHUQHWQHJDSURWRNRODSUHNRPUHåLM 7,3+21 
'HPRQVWUDFLMDSUHYHUMDQMDLQPHGREUDWRYDOQRVW 9', 5D]OLþLFD
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON);
Verification Demonstration and Interoperability (VDI) activities; Version 3
Ta slovenski standard je istoveten z: TR 101 334 Version 3.1.1
ICS:
33.020 Telekomunikacije na splošno Telecommunications in
general
SIST-TP TR 101 334 V3.1.1:2004 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TP TR 101 334 V3.1.1:2004

---------------------- Page: 2 ----------------------

SIST-TP TR 101 334 V3.1.1:2004
ETSI TR 101 334 V3.1.1 (2000-01)
Technical Report
Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON);
Verification Demonstration and Interoperability (VDI) activities;
Version 3

---------------------- Page: 3 ----------------------

SIST-TP TR 101 334 V3.1.1:2004
2 ETSI TR 101 334 V3.1.1 (2000-01)
Reference
RTR/TIPHON-06003
Keywords
internet, interoperability, testing, voice, VoIP, IP
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.:+33492944200 Fax:+33493654716
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
Internet
secretariat@etsi.fr
Individual copies of this ETSI deliverable
can be downloaded from
http://www.etsi.org
If you find errors in the present document, send your
comment to: editor@etsi.fr
Important notice
This ETSI deliverable 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.
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

---------------------- Page: 4 ----------------------

SIST-TP TR 101 334 V3.1.1:2004
3 ETSI TR 101 334 V3.1.1 (2000-01)
Contents
Intellectual Property Rights.5
Foreword .5
1 Scope.6
2 References.6
3 Abbreviations .6
4 Interoperability Testing.7
4.1 Purpose/ Objectives.7
4.2 Testing.7
4.3 Privacy.7
4.4 Responsible WG.7
4.5 Test Procedures .7
4.6 Test Scoring.7
4.7 Participation .7
4.7.1 Joint events .7
4.7.2 Who can participate .7
5 Interoperability Events.8
5.1 Face-to-face Interoperability Events.8
5.1.1 Organization .8
5.1.2 Registration.8
5.1.3 Scheduling .8
5.1.4 Frequency .8
5.2 Remote Interoperability Events .9
5.2.1 Organization .9
5.2.2 Registration.9
5.2.3 Communication.9
5.2.4 Time.9
5.2.5 Scheduling .10
6 Implementers Net .10
6.1 Purpose/Objectives.10
6.2 Architecture.10
6.3 Procedures.11
6.4 Requirements.11
6.5 Technical details of the Dial up ISDN router .12
6.6 Administration of the ISDN router .12
7 The Virtual Interoperability Meeting Place (VIMP) .12
7.1 Purpose.12
7.2 Structure .12
7.3 Organization .12
8 Implementers mailing list.13
8.1 Purpose of TIPHON_Implementers .13
8.2 How to join the TIPHON_Implementers List.13
ETSI

---------------------- Page: 5 ----------------------

SIST-TP TR 101 334 V3.1.1:2004
4 ETSI TR 101 334 V3.1.1 (2000-01)
Annex A (informative): Guidelines for the Organization of Interoperability Events .14
A.1 Responsibilities .14
A.2 Timing.14
A.3 How to register.14
A.4 Guest rooms in hotel .14
A.5 Deadline for registration .14
A.6 Rental of Equipment .14
A.7 Shipping of equipment .14
A.8 Facilities.15
A.9 Network.16
A.10 Information Services .17
A.11 On-site Staff .17
A.12 Conference Calls .17
A.13 Sponsors .17
A.14 Event kit / Information package .17
A.15 Documents to have ready at the beginning of interoperability event.18
A.16 Running the event .18
A.17 After the interoperability event.19
Bibliography.20
History.21
ETSI

---------------------- Page: 6 ----------------------

SIST-TP TR 101 334 V3.1.1:2004
5 ETSI TR 101 334 V3.1.1 (2000-01)
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 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 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

---------------------- Page: 7 ----------------------

SIST-TP TR 101 334 V3.1.1:2004
6 ETSI TR 101 334 V3.1.1 (2000-01)
1 Scope
The present document introduces the activities of the Verification-Demonstration-Interoperability (VDI) working group
of TIPHON which organizes interoperability events and provides remote testing facilities (Implementers Net).
2 References
The following documents contain provisions which, 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, the latest version applies.
• 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] TS 101 335: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON); Test specifications".
[2] ITU-T Recommendation H.323: "Packet based multimedia communications systems".
[3] ITU-T Recommendation H.245: "Control protocol for multimedia communication".
[4] ITU-T Recommendation H.225.0: "Call signalling protocols and media stream packetization for
packet-based multimedia communication systems".
3 Abbreviations
For the purposes of the present document the following abbreviations apply:
BRI Basic Rate Interface
CoIP Conferencing over IP Activity Group of IMTC
IMTC International Multimedia Teleconferencing Consortium
INOW! Interoperability NOW, Activity Group of IMTC
ISDN Integrated Services Digital Network
LAN Local Area Network
NDA Non-Disclosure Agreement
PBX Private Branch eXchange
PRI Primary Rate Interface
PSTN Public Switched Telephone Network
STF Specialist Task Force
VDI Verification-Demonstration-Interoperability
VIMP Virtual Interop Meeting Place
WG Working Group
ETSI

---------------------- Page: 8 ----------------------

SIST-TP TR 101 334 V3.1.1:2004
7 ETSI TR 101 334 V3.1.1 (2000-01)
4 Interoperability Testing
4.1 Purpose/ Objectives
The purpose of interoperability testing is to verify the TIPHON specifications and interoperability of different
implementations. These tests can either take place in a single room, “classic" or “face-to-face" Interoperability Events,
or can be spread over the whole world using remote connectivity, then they are called remote Interop events.
4.2 Testing
Testing will verify all TIPHON scenarios (that is, PC to PC, PC to Phone, Phone to PC, and Phone to Phone). Testing
will attempt to completely demonstrate and debug these services, rather than just concentrate on the specific protocol
elements that are required.
4.3 Privacy
The result of the tests will not be in any case available outside TIPHON membership, nor may it be used in any case
under any situation to promote some products as being "more" TIPHON compliant than others, or for any other purpose
other than the verification and debugging of the TIPHON specifications.
There will be no formal kind of NDA to be filled out, but there is always a kind of gentleman’s agreement not to
disclose any individual results.
Documents that request changes to the TIPHON specifications as a result of the Interoperability events will not directly
reference the vendor that found the fault.
4.4 Responsible WG
Interoperability events will be operated under the responsibility of WG6, with support from the relevant protocol
generating and specifying WGs (i.e. WG3, WG4, and WG5).
4.5 Test Procedures
Test specifications of all TIPHON scenarios can be found in TS 101 335 [1].
4.6 Test Scoring
In tests which are scored, score sheets are distributed based on TS 101 335 [1].
4.7 Participation
4.7.1 Joint events
TIPHON interoperability events are in general organized jointly with IMTC CoIP.
4.7.2 Who can participate
Participation is open to ETSI members, ETSI associate members, IMTC members, and companies in the application
process to become a member of ETSI or IMTC. Participants need to have products or services available for testing with
other companies. Companies simply wanting to observe the testing will not be allowed to attend the event.
ETSI

---------------------- Page: 9 ----------------------

SIST-TP TR 101 334 V3.1.1:2004
8 ETSI TR 101 334 V3.1.1 (2000-01)
5 Interoperability Events
Interoperability events can take place as face-to-face events, or as remote events.
5.1 Face-to-face Interoperability Events
The classical way to test interoperability is to meet in a room and connect multiple systems together.
5.1.1 Organization
Interoperability events are in general organized together with the CoIP (Conferencing over IP) Activity Group of IMTC
(International Multimedia Teleconferencing Consortium).
Annex 1, "Guidelines for the organization of interoperability events", summarizes the experience gained from multiple
interoperability events and may prove useful for future organizers of Interoperability events.
5.1.2 Registration
Prior to any Interop the participants have to register. To optimize this process and to easily provide detailed information
to the other participants ETSI has installed the VIMP. More details are described in clause 7 of the present document.
5.1.3 Scheduling
Scheduling is one of the most difficult aspects of Interop Events. As a consensus we can state that the participants prefer
65% of the time as ad hoc, self scheduled tests and 35% of the time as scheduled by the organizers.
Scheduled tests in face-to-face interoperability events are intended to test the interoperability of a large number of
participants in a minimum of time. Thus the timeslots are pretty short and there is no time for the companies to debug.
Extensive analyses and debugging can take place in the ad-hoc test time after the scheduled tests.
5.1.4 Frequency
Here is some feedback collected at two post Interoperability Events in Boston and Sophia Antipolis.
How many Interop Event should there be per year?
4-99 Boston 6-99 Sophia Antipolis
1 per year 0% 2 %
2 per year 18 % 18 %
3 per year 30 % 45 %
4 per year 49 % 30 %
6 per year 3 % 5 %
Average 3,4 3,2
ETSI

---------------------- Page: 10 ----------------------

SIST-TP TR 101 334 V3.1.1:2004
9 ETSI TR 101 334 V3.1.1 (2000-01)
5.2 Remote Interoperability Events
Remote Interoperability Events provide companies the opportunity to test interoperability in their own labs without
buying other companies equipment. They can interconnect to other parties via the public Internet or the ETSI ISDN
router.
5.2.1 Organization
The organization of a remote interoperability event is different from a face to face event. There is no need to arrange a
room and prepare accommodation, but in order to organize an effective event the information for the participants have to
be much more detailed and precise, as communication is much more complicated and solving simple problems may be
very time-consuming.
5.2.2 Registration
Prior to any Interop the participants have to register. To optimize this process and to provide detailed information to the
other participants in any effective way, ETSI has installed the VIMP. More details are described in clause 7 of the
present document.
The information provided about other participants equipment is very important for remote interoperability events, as it is
much more complicated to collect details at a later stage.
These details include:
- Time of day the contact person is present in the company and able to do testing;
- Ability to test using the pubic internet;
- Ability to test using the TIPHON Interop Router;
- IP-Address of device ( if known and important for test);
- Alias the Endpoint is going to register with;
- Gateway Prefix, the Gateway is going to register with, or Endpoint Alias;
- Number an Endpoint has to dial to reach a telephone connected to the Gateway.
5.2.3 Communication
The communication is simple if you are sitting together in one room. If you test remotely, you must have a telephone
conference or a simple chat tool to communicate the progress of the test. A chat tool also allowS the co-ordinator to be
informed about the progress of a test.
5.2.4 Time
As TIPHON is a world-wide project we have different time zones for the participating companies. It is not complicated
to calculate the actual time in another parts of the world but causes sometimes confusion. To simplify this, TIPHON
should use a common time-base to schedule tests. UTC or the InternetTime can be
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.