The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of
reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including
mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA®
based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of
testing including interoperability, robustness, regression, system and integration testing. The specification of test suites
for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and
protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2])
defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the
present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into
consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the
scope of the present document.

  • Standard
    379 pages
    English language
    sale 15% off
  • Standard
    379 pages
    English language
    sale 15% off
  • Standardization document
    379 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [9]) to TTCN-3 as
defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.

  • Standard
    154 pages
    English language
    sale 15% off
  • Standard
    154 pages
    English language
    sale 15% off
  • Standardization document
    154 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of
all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing
(including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of
APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including
interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer
protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines types for behaviour definitions in TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages and guidelines for this package in combination with other packages is
outside the scope of the present document.

  • Standard
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    44 pages
    English language
    sale 15% off
  • Standard
    44 pages
    English language
    sale 15% off

The present document defines the mapping rules for CORBA IDL (as defined in clause 3 in [4]) to TTCN-3 (as defined
in ETSI ES 201 873-1 [1]) to enable testing of CORBA-based systems. The principles of mapping CORBA IDL to
TTCN-3 can be also used for the mapping of interface specification languages of other object-/component-based
technologies.
The specification of other mappings is outside the scope of the present document.

  • Standard
    31 pages
    English language
    sale 15% off
  • Standard
    31 pages
    English language
    sale 15% off
  • Standardization document
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies the rules to define schemas for JSON data structures in TTCN-3, to enable testing of
JSON-based systems, interfaces and protocols, and the conversion rules between TTCN-3 [1] and JSON [2] to enable
exchanging TTCN-3 data in JSON format between different systems.

  • Standard
    36 pages
    English language
    sale 15% off
  • Standard
    36 pages
    English language
    sale 15% off
  • Standardization document
    36 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered
by the present document.

  • Standard
    60 pages
    English language
    sale 15% off
  • Standard
    60 pages
    English language
    sale 15% off
  • Standardization document
    60 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies the control interfaces for TTCN-3 test system implementations. The TTCN-3 Control
Interfaces provide a standardized adaptation for management, test component handling and encoding/decoding of a test
system to a particular test platform. The present document defines the interfaces as a set of operations independent of a
target language.
The interfaces are defined to be compatible with the TTCN-3 standard (see clause 2). The interface definition uses the
CORBA Interface Definition Language (IDL) to specify the TCI completely. Clauses 8, 9, 10, 11 and 12 present
language mappings for this abstract specification to the target languages Java™, ANSI C, C++, XML and C#.
A summary of the IDL-based interface specification is provided in annex A.
NOTE: Java™ is the trade name of a programming language developed by Oracle Corporation. This information
is given for the convenience of users of the present document and does not constitute an endorsement by
ETSI of the programming language named. Equivalent programming languages may be used if they can
be shown to lead to the same results.

  • Standard
    374 pages
    English language
    sale 15% off
  • Standard
    375 pages
    English language
    sale 15% off
  • Standardization document
    374 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document proposes an evolved version of the Green Abstraction Layer formulation capable of operating within ETSI NFV environments.

  • Standard
    71 pages
    English language
    sale 15% off
  • Standard
    71 pages
    English language
    sale 15% off
  • Standardization document
    71 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standardization document
    71 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the Extended TRI package of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language or in its interfaces TRI and TCI, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. This package defines a more efficient handling of software values by a version of TRI, that does not use binary encoded messages for the communication with the SUT, but uses the values as they are; meaning e.g. that software objects or serialized data can be passed directly between the SUT and the TE. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

  • Standard
    30 pages
    English language
    sale 15% off
  • Standard
    30 pages
    English language
    sale 15% off
  • Standardization document
    30 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer protocols is outside the scope of the present document. TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or usages of TTCN-3. This package defines types for behaviour definitions in TTCN-3. While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language with a number of packages, the concrete usages of and guidelines for this package in combination with other packages is outside the scope of the present document.

  • Standard
    44 pages
    English language
    sale 15% off
  • Standard
    44 pages
    English language
    sale 15% off
  • Standardization document
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [9]) to TTCN-3 as defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.

  • Standard
    154 pages
    English language
    sale 15% off
  • Standard
    154 pages
    English language
    sale 15% off
  • Standardization document
    154 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of
reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including
mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA®
based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of
testing including interoperability, robustness, regression, system and integration testing. The specification of test suites
for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and
protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2])
defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the
present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into
consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the
scope of the present document.

  • Standard
    374 pages
    English language
    sale 15% off
  • Standard
    374 pages
    English language
    sale 15% off
  • Standardization document
    374 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2], X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered by the present document.

  • Standard
    60 pages
    English language
    sale 15% off
  • Standard
    60 pages
    English language
    sale 15% off
  • Standardization document
    60 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standardization document
    60 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document aims at further simplifying end-user access to ICT devices, services, and applications by providing
recommended terms for basic and commonly-used ICT-related objects and activities, limited to those terms that end
users are commonly exposed to. Recommended terms are provided in five languages: English, French, German, Italian,
and Spanish (as spoken in their respective European countries).
The recommended terms apply to mobile ICT devices and mobile applications (whether they are standalone or whether
they provide access to related services) commonly found in mobile ICT devices (most of the recommended terms are
applicable to both mobile and stationary devices, services, and applications). The recommended terms are applicable to
the User Interface (UI) design for a product as well as that of any user documentation accompanying it.
User requirements and available results of standardization work have been considered and integrated in the present document,
providing implementation-oriented guidance. Wherever possible, a Design-for-All approach has been adopted,
taking functional abilities of users, including elderly users and users with cognitive, physical, or sensory limitations into
account.
The present document does not provide design guidance, nor does it intend to restrict the ability of market players to
further improve and develop their terminals and services. Neither does it intend to limit their options to trademark user
interface elements or profile the user experience of brand-specific user interface implementations as a competitive edge.

  • Standard
    102 pages
    English language
    sale 15% off
  • Standard
    102 pages
    English language
    sale 15% off
  • Standardization document
    102 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standardization document
    102 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the metrics and measurement methods for the energy efficiency of functional components
of NFV environment. The NFV functional components include Virtualised Network Functions (VNFs) and NFV
Infrastructure (NFVI) defined in NFV architecture framework as described in ETSI GS NFV 002 [i.1]. Management
and Orchestration (MANO) is not included as system under test, but will be eventually taken as test environment.
The measurement method described in the present document is intended to be used to assess and compare the energy
efficiency of same functional components independently in lab testing and pre-deployment testing. Energy efficiency of
co-located VNFs sharing same platform resources cannot be compared using the defined method in present document.
The scope of the document is not to define measurement method in operational NFV environment.
The present document is intended to define common energy efficiency measurement methods for NFV environments,
not try to cover all different types of VNFs (e.g. firewall, gateway, etc.), but it provides the basis to make extensible
definition.

  • Standard
    19 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    19 pages
    English language
    sale 15% off
  • Standard
    19 pages
    English language
    sale 15% off

The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [9]) to TTCN-3 as
defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.

  • Standard
    153 pages
    English language
    sale 15% off
  • Standard
    153 pages
    English language
    sale 15% off
  • Standardization document
    153 pages
    English language
    sale 10% off
    e-Library read for
    1 day

RES/MTS-201873-1v4A1

  • Standard
    364 pages
    English language
    sale 15% off
  • Standard
    364 pages
    English language
    sale 15% off
  • Standardization document
    364 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies the control interfaces for TTCN-3 test system implementations. The TTCN-3 Control
Interfaces provide a standardized adaptation for management, test component handling and encoding/decoding of a test
system to a particular test platform. The present document defines the interfaces as a set of operations independent of a
target language.
The interfaces are defined to be compatible with the TTCN-3 standard (see clause 2). The interface definition uses the
CORBA Interface Definition Language (IDL) to specify the TCI completely. Clauses 8, 9, 10, 11 and 12 present
language mappings for this abstract specification to the target languages Java™, ANSI C, C++, XML and C#.
A summary of the IDL-based interface specification is provided in annex A.
NOTE: Java™ is the trade name of a programming language developed by Oracle Corporation. This information
is given for the convenience of users of the present document and does not constitute an endorsement by
ETSI of the programming language named. Equivalent programming languages may be used if they can
be shown to lead to the same results.

  • Standard
    368 pages
    English language
    sale 15% off
  • Standard
    374 pages
    English language
    sale 15% off
  • Standardization document
    368 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of
reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including
mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA®
based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of
testing including interoperability, robustness, regression, system and integration testing. The specification of test suites
for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and
protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2])
defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the
present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into
consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the
scope of the present document.

  • Standard
    367 pages
    English language
    sale 15% off
  • Standard
    368 pages
    English language
    sale 15% off
  • Standardization document
    367 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of
all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing
(including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of
APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including
interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer
protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines types for behaviour definitions in TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

  • Standard
    45 pages
    English language
    sale 15% off
  • Standard
    45 pages
    English language
    sale 15% off
  • Standardization document
    45 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies the rules to define schemas for JSON data structures in TTCN-3, to enable testing of
JSON-based systems, interfaces and protocols, and the conversion rules between TTCN-3 [1] and JSON [2] to enable
exchanging TTCN-3 data in JSON format between different systems.

  • Standard
    34 pages
    English language
    sale 15% off
  • Standard
    35 pages
    English language
    sale 15% off
  • Standardization document
    34 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies the control interfaces for TTCN-3 test system implementations. The TTCN-3 Control
Interfaces provide a standardized adaptation for management, test component handling and encoding/decoding of a test
system to a particular test platform. The present document defines the interfaces as a set of operations independent of a
target language.
The interfaces are defined to be compatible with the TTCN-3 standard (see clause 2). The interface definition uses the
CORBA Interface Definition Language (IDL) to specify the TCI completely. Clauses 8, 9, 10, 11 and 12 present
language mappings for this abstract specification to the target languages Java™, ANSI C, C++, XML and C#.
A summary of the IDL-based interface specification is provided in annex A.
NOTE: JavaTM is the trade name of a programming language developed by Oracle Corporation. This information
is given for the convenience of users of the present document and does not constitute an endorsement by
ETSI of the programming language named. Equivalent programming languages may be used if they can
be shown to lead to the same results.

  • Standard
    364 pages
    English language
    sale 15% off
  • Standard
    364 pages
    English language
    sale 15% off
  • Standardization document
    364 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered
by the present document.

  • Standard
    59 pages
    English language
    sale 15% off
  • Standard
    59 pages
    English language
    sale 15% off
  • Standardization document
    59 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [9]) to TTCN-3 as
defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.

  • Standard
    153 pages
    English language
    sale 15% off
  • Standard
    153 pages
    English language
    sale 15% off
  • Standardization document
    153 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies the requirements for a Global KPI for energy management (designated KPIEP) and its
underpinning Objective KPI for energy consumption addressing the following objectives for the cable operator access
networks of broadband deployment:
• energy consumption;
• renewable energy.
The requirements are mapped to the concepts of ETSI EN 305 200-1 [i.5].
Energy management of cable access networks comprises a number of independent layers. The present document
addresses performance of infrastructures that supports the normal function of hosted ICT equipment within the cable
access network (e.g. power distribution, environmental control, security and safety). The present document does not
address other layers such as performance of ICT equipment itself, performance of usage of available processing power,
and layers related to final service delivered (e.g. processing power required per itemized outcome) or overlay layers
(e.g. final energy required per itemized outcome).
The environmental impact and management of different energy sources are outside the scope of the present document.
Within the present document:
• clause 4 describes the energy parameters for cable access networks employing DOCSIS 3.0 and/or
DOCSIS 3.1 together with inclusions/exclusions of different energy sources;
• clause 5 specifies the requirements for measurement, calculation, classification and reporting of KPIEP.

  • Standard
    28 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    28 pages
    English language
    sale 15% off
  • Standard
    28 pages
    English language
    sale 15% off

The present document defines the Behaviour Types package of TTCN-3. TTCN-3 can be used for the specification of
all types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing
(including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of
APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of testing including
interoperability, robustness, regression, system and integration testing. The specification of test suites for physical layer
protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language, but which are optional as part of a package which is suited for dedicated applications and/or
usages of TTCN-3.
This package defines types for behaviour definitions in TTCN-3.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

  • Standard
    44 pages
    English language
    sale 15% off
  • Standard
    43 pages
    English language
    sale 15% off
  • Standardization document
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies a Diameter application for use between a Connectivity session Location and repository
Function (CLF) and an Application Function (AF).

  • Standard
    30 pages
    English language
    sale 15% off
  • Standard
    30 pages
    English language
    sale 15% off
  • Standardization document
    30 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the methodology and the test conditions to measure the power consumption of router and
switch equipment.
The present document is applicable to Core, edge and access routers.
Home gateways are not included in the present document.

  • Standard
    15 pages
    English language
    sale 15% off
  • Standard
    15 pages
    English language
    sale 15% off
  • Standardization document
    15 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines a core set of features that enable multiple subscriber devices to gain access to operator
provided high-speed data service using DOCSIS. This core set of features allows for both IPv4- and IPv6-enabled
devices to gain connectivity to the Internet.
The eRouter is specified as an Embedded Service/Application Functional Entity (eSAFE) device that is implemented in
conjunction with a DOCSIS cable modem device.
The core set of features defined in the present document includes the ability to provision multiple CPE devices, a
description of how to forward data to and from CPE devices, and also the ability to forward IP Multicast traffic to CPE
devices and among CPE devices.

  • Standard
    101 pages
    English language
    sale 15% off
  • Standard
    106 pages
    English language
    sale 15% off
  • Standardization document
    101 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies the control interfaces for TTCN-3 test system implementations. The TTCN-3 Control
Interfaces provide a standardized adaptation for management, test component handling and encoding/decoding of a test
system to a particular test platform. The present document defines the interfaces as a set of operations independent of a
target language.
The interfaces are defined to be compatible with the TTCN-3 standard (see clause 2). The interface definition uses the
CORBA Interface Definition Language (IDL) to specify the TCI completely. Clauses 8, 9, 10, 11 and 12 present
language mappings for this abstract specification to the target languages Java™, ANSI C, C++, XML and C#.
A summary of the IDL-based interface specification is provided in annex A.
NOTE: JavaTM is the trade name of a programming language developed by Oracle Corporation. This information
is given for the convenience of users of the present document and does not constitute an endorsement by
ETSI of the programming language named. Equivalent programming languages may be used if they can
be shown to lead to the same results.

  • Standard
    376 pages
    English language
    sale 15% off
  • Standard
    377 pages
    English language
    sale 15% off
  • Standardization document
    376 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the mapping rules for CORBA IDL (as defined in clause 3 in [4]) to TTCN-3 (as defined
in ETSI ES 201 873-1 [1]) to enable testing of CORBA-based systems. The principles of mapping CORBA IDL to
TTCN-3 can be also used for the mapping of interface specification languages of other object-/component-based
technologies.
The specification of other mappings is outside the scope of the present document.

  • Standard
    31 pages
    English language
    sale 15% off
  • Standard
    31 pages
    English language
    sale 15% off
  • Standardization document
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [9]) to TTCN-3 as
defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.

  • Standard
    153 pages
    English language
    sale 15% off
  • Standard
    153 pages
    English language
    sale 15% off
  • Standardization document
    153 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the operational semantics of TTCN-3. The present document is based on the TTCN-3
core language defined in ETSI ES 201 873-1 [1].

  • Standard
    175 pages
    English language
    sale 15% off
  • Standard
    175 pages
    English language
    sale 15% off
  • Standardization document
    175 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines a normative way of using ASN.1 as defined in Recommendations ITU-T X.680 [2],
X.681 [3], X.682 [4] and X.683 [5] with TTCN-3. The harmonization of other languages with TTCN-3 is not covered
by the present document.

  • Standard
    59 pages
    English language
    sale 15% off
  • Standard
    59 pages
    English language
    sale 15% off
  • Standardization document
    59 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of
reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including
mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA®
based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of
testing including interoperability, robustness, regression, system and integration testing. The specification of test suites
for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and
protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2])
defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the
present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into
consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the
scope of the present document.

  • Standard
    359 pages
    English language
    sale 15% off
  • Standard
    359 pages
    English language
    sale 15% off
  • Standardization document
    359 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document provides the specification of the runtime interface for TTCN-3 test system implementations. The
TTCN-3 Runtime Interface provides a standardized adaptation for timing and communication of a test system to a
particular processing platform and the system under test, respectively. The present document defines the interface as a
set of operations independent of target language.
The interface is defined to be compatible with the TTCN-3 standard (see ETSI ES 201 873-1 [2]). The present
document uses the CORBA Interface Definition Language (IDL) to specify the TRI completely. Clauses 6, 7 and 8
present language mappings for this abstract specification to the target languages JavaTM, ANSI C, and C++. A summary
of the IDL based interface specification is provided in annex A.
NOTE: JavaTM is the trade name of a programming language developed by Oracle Corporation. This information
is given for the convenience of users of the present document and does not constitute an endorsement by
ETSI of the programming language named. Equivalent programming languages may be used if they can
be shown to lead to the same results.

  • Standard
    93 pages
    English language
    sale 15% off
  • Standard
    93 pages
    English language
    sale 15% off
  • Standardization document
    93 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This new part of the standard defines the language mapping between JSON schema and TTCN-3 and additional encoding instructions for JSON data format representation option.

  • Standard
    35 pages
    English language
    sale 15% off
  • Standard
    35 pages
    English language
    sale 15% off
  • Standardization document
    35 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document, "Approaches for Testing Adaptive Networks" defines a framework of testing principles and
guidelines that may be used to test networks that exhibit some form of autonomic adaptive behaviour, which allows
them to dynamically change their configuration, structure or operational parameters. The (re)-configuration is
performed in response to stimuli such as changes in workload, operator policies that govern their operation, context (the
network is context-aware and may have a degree of self-awareness); and challenges in the environment (i.e. conditions
under which the network is operating, e.g. manifestations of faults, errors, failures in various parts of the network and
its hardware and software components).
The functionality of individual components and basic interoperability can be ensured at design time. However, the
complex interactions between various components or functions deployed in a live Adaptive Network (AN) may not be
fully assessed or foreseen. Consequently, the document addresses methodologies to test ANs towards meeting their
functional targets or policies, and ensuring a minimum trust level for autonomic operation of such networks.
NOTE: In the literature, both the terms "autonomous" and "autonomic" are being used in this context, whereas
"autonomous" appears to indicate a higher level of automation. As adaptive networks are, at the time of
writing, surely a technology still at its beginnings, "autonomic" may be a less ambitious and therefore
more appropriate term for the time being. On the other hand, the NGMN 5G White Paper (V1.0) uses the
term combination "autonomic/self-management functions" which points, clearly towards a level beyond
"autonomic". As mobile networks are complex systems, it is most likely that the degree of automation
will increase in the course of technical evolution, but not in an isotropic way; there will be areas with
higher and others with lower levels of automation, and sophistication of respective functions. For these
reasons, the present document will use the term "autonomic".

  • Standard
    31 pages
    English language
    sale 15% off
  • Standard
    31 pages
    English language
    sale 15% off
  • Guide
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the Extended TRI package of TTCN-3. TTCN-3 can be used for the specification of all
types of reactive system tests over a variety of communication ports. Typical areas of application are protocol testing
(including mobile and Internet protocols), service testing (including supplementary services), module testing, testing of
CORBA based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other
kinds of testing including interoperability, robustness, regression, system and integration testing. The specification of
test suites for physical layer protocols is outside the scope of the present document.
TTCN-3 packages are intended to define additional TTCN-3 concepts, which are not mandatory as concepts in the
TTCN-3 core language or in its interfaces TRI and TCI, but which are optional as part of a package which is suited for
dedicated applications and/or usages of TTCN-3.
This package defines a more efficient handling of software values by a version of TRI, that does not use binary encoded
messages for the communication with the SUT, but uses the values as they are; meaning e.g. that software objects or
serialized data can be passed directly between the SUT and the TE.
While the design of TTCN-3 package has taken into account the consistency of a combined usage of the core language
with a number of packages, the concrete usages of and guidelines for this package in combination with other packages
is outside the scope of the present document.

  • Standard
    31 pages
    English language
    sale 15% off
  • Standard
    31 pages
    English language
    sale 15% off
  • Standardization document
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document gives general guidance on the specification and execution of interoperability tests for communication systems specifically in the context of product certification. It provides a framework within which interoperability test specifications for a wide range of product types can be developed. The guidelines are expressed as recommendations rather than strict rules and leave enough freedom to allow test specifiers to adopt and adapt processes to suit each particular project while still ensuring that test specifications accurately reflect the requirements of the base standards and can be executed consistently across a range of configurations.

  • Standard
    41 pages
    English language
    sale 15% off
  • Guide
    41 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the mapping rules for W3C Schema (as defined in [7] to [9]) to TTCN-3 as defined in
ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.

  • Standard
    144 pages
    English language
    sale 15% off
  • Standard
    142 pages
    English language
    sale 15% off
  • Standardization document
    144 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document specifies the control interfaces for TTCN-3 test system implementations. The TTCN-3 Control Interfaces provide a standardized adaptation for management, test component handling and encoding/decoding of a test system to a particular test platform. The present document defines the interfaces as a set of operations independent of a target language.
The interfaces are defined to be compatible with the TTCN-3 standard (see clause 2). The interface definition uses the CORBA Interface Definition Language (IDL) to specify the TCI completely. Clauses 8, 9, 10, 11 and 12 present language mappings for this abstract specification to the target languages Java™, ANSI C, C++, XML and C#. A summary of the IDL-based interface specification is provided in annex A.

  • Standard
    372 pages
    English language
    sale 15% off
  • Standard
    369 pages
    English language
    sale 15% off
  • Standardization document
    372 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the operational semantics of TTCN-3. The present document is based on the TTCN-3
core language defined in ETSI ES 201 873-1 [1].

  • Standard
    174 pages
    English language
    sale 15% off
  • Standard
    173 pages
    English language
    sale 15% off
  • Standardization document
    174 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines the Core Language of TTCN-3. TTCN-3 can be used for the specification of all types of
reactive system tests over a variety of communication ports. Typical areas of application are protocol testing (including
mobile and Internet protocols), service testing (including supplementary services), module testing, testing of CORBA®
based platforms, APIs, etc. TTCN-3 is not restricted to conformance testing and can be used for many other kinds of
testing including interoperability, robustness, regression, system and integration testing. The specification of test suites
for physical layer protocols is outside the scope of the present document.
TTCN-3 is intended to be used for the specification of test suites which are independent of test methods, layers and
protocols. In addition to the textual format defined in the present document, while GFT (ETSI ES 201 873-3 [i.2])
defines a graphical presentation format for TTCN-3. The specification of these formats is outside the scope of the
present document.
While the design of TTCN-3 has taken the eventual implementation of TTCN-3 translators and compilers into
consideration the means of realization of Executable Test Suites (ETS) from Abstract Test Suites (ATS) is outside the
scope of the present document.

  • Standard
    346 pages
    English language
    sale 15% off
  • Standard
    345 pages
    English language
    sale 15% off
  • Standardization document
    346 pages
    English language
    sale 10% off
    e-Library read for
    1 day