33.040.01 - Telecommunication systems in general
ICS 33.040.01 Details
Telecommunication systems in general
Telefonie und Telegraphie im allgemeinen
Systemes de telecommunications en general
Telekomunikacijski sistemi na splošno
General Information
- 1 (current)
- 2
- 3
- 4
- 5
The present document addresses the accessibility of ETSI deliverables for users with physical and/or cognitive disabilities. It contains recommendations that are based on the consultation of different sources: expert judgement for the identification of improvements that are easily implemented and that can immediately improve the accessibility of ETSI deliverables, the consultation of authors of ETSI deliverables with a focus on their requirements related to the creation of content for accessible deliverables, and the consultation of users of ETSI deliverables who have physical and/or cognitive disabilities. The results of the analysis take the form of a comprehensive set of recommendations and guidelines to ensure accessible and usable ETSI deliverables, including recommendations for the needed modifications of the ETSI publication processes and specifications of most suitable tools for publication. For this task, short-term, mid-term and, long-term perspectives have been adopted, ranging from immediate changes to a strategic outlook of a future publication environment of ETSI deliverables.
- Standard45 pagesEnglish languagesale 15% off
- Standard45 pagesEnglish languagesale 15% off
- Guide45 pagesEnglish languagesale 10% offe-Library read for1 day
The present document defines the mapping rules for W3C® XML Schema (as defined in [7] to [8]) to TTCN-3 as defined in ETSI ES 201 873-1 [1] to enable testing of XML-based systems, interfaces and protocols.
- Standard161 pagesEnglish languagesale 15% off
- Standard161 pagesEnglish languagesale 15% off
- Standardization document161 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard396 pagesEnglish languagesale 15% off
- Standard396 pagesEnglish languagesale 15% off
- Standardization document396 pagesEnglish languagesale 10% offe-Library read for1 day
The present document gives guidelines for hosting accessible ETSI meetings on ETSI premises, those of ETSI members, or in public environments (e.g. conference centres). It proposes changes to the meeting registration procedure on the ETSI portal allowing participants to register accessibility requirements. It provides a resource collection that links to the most pertinent existing sign language interpreter databases and additionally includes a collection of recommended tools for speech-to-text tools and services, to help make meetings accessible for deaf and hard-of-hearing participants. It further includes a comparison of accessibility features of available meeting tools, recommendations for tool selection, an evaluation of the accessibility of joint editing and presentation tools and related recommendations for ETSI and for meeting hosts.
- Standard84 pagesEnglish languagesale 15% off
- Standard84 pagesEnglish languagesale 15% off
- Guide84 pagesEnglish languagesale 10% offe-Library read for1 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
- Standard44 pagesEnglish languagesale 15% off
- Standard44 pagesEnglish languagesale 15% off
- Standardization document44 pagesEnglish languagesale 10% offe-Library read for1 day
The present document provides detailed functional, service and accessibility requirements from the Human Factors perspective for the implementation of and compliance with the European Accessibility Act [i.27] which requires the provision of interoperable total conversation services wherever voice and video communication is available. It details how to provide an interoperable total conversation service, with voice, real-time text and sign language-supportive video communication media synchronized, as a context-optimized service, with no need for additional pre-registration. It also details viable fall-back options. Effective wireless coupling to hearing technologies, with the avoidance of interferences with assistive devices, and beyond, is also addressed. The necessary background information and specifications containing technical parameters is provided as informative annexes to the present document. The present document additionally provides guidance on how to implement the interoperable total conversation services for emergency communications so that the needs of all users, including people with disabilities, are met. As such the present document complements other standards developed in the area, such as EN 301 549 [1] and ETSI TS 101 470 [29].
- Standard83 pagesEnglish languagesale 15% off
- Standard83 pagesEnglish languagesale 15% off
- Standardization document83 pagesEnglish languagesale 10% offe-Library read for1 day
The present document is based upon benchmark for server Energy Efficiency (EE) tool for general and heterogeneous servers [i.6].
The present document specifies:
1) test conditions and product configuration for the assessment of EE of heterogeneous servers using reliable, accurate and reproducible measurement methods;
2) an EE metric to support procurement requirements;
3) requirements for equipment to perform the measurements and analysis;
4) requirements for the measurement process;
5) requirements for the management of the EE metric calculation;
6) operation or run rules to configure, execute, and monitor the testing;
7) documentation and reporting requirements.
The metrics and methods apply to heterogeneous servers with various configurations, including type and count of APAs, CPU, memory, storage and any other add-on hardware expected to be present when deployed.
NOTE: Products whose feature set and intended operation are not addressed by active mode testing parameters are excluded from this evaluation method.
- Standard24 pagesEnglish languagesale 15% off
- Standard24 pagesEnglish languagesale 15% off
- Standardization document24 pagesEnglish languagesale 10% offe-Library read for1 day
The present document defines the power consumption metrics, the methodology and the test conditions to measure the
power consumption of broadband fixed telecommunication networks equipment. The present document does not cover
all possible configuration of equipment but only homogenous configurations.
The types of broadband access technologies covered by the present document are the ones widely deployed at the date
of publication. Currently, the present document considers DSLAM DSL, MSAN, PON OLT and Point to Point OLT
equipment. Other access technologies may be included in further versions of the present document.
The present document also considers measurement methodology for VDSL2 equipment with vectoring functionality.
In addition to the full power state, power-saving states as defined in DSL standards [i.1] and [i.2] are also covered.
The present document focuses on Network Equipment. The end-user equipment is handled in other documents, see
ETSI EN 301 575 [i.6] for CPE [i.6] and ETSI EN 303 423 [i.9] for network standby.
- Standard25 pagesEnglish languagesale 15% off
- Standard25 pagesEnglish languagesale 15% off
- Standard25 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard395 pagesEnglish languagesale 15% off
- Standard395 pagesEnglish languagesale 15% off
- Standardization document395 pagesEnglish languagesale 10% offe-Library read for1 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, notably those terms that end users are commonly exposed to. Recommended terms are provided in 27 languages: Bulgarian, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Icelandic , Irish, Italian, Latvian, Lithuanian, Maltese, Norwegian, Polish, Portuguese, Rhaeto Romance, Romanian, Slovak, Slovenian, Spanish, and Swedish (as spoken in their respective European countries).
The recommended terms apply to mobile ICT devices and mobile applications (whether they are standalone or provide access to related services) commonly found in mobile ICT devices. Though developed in a mobile ICT context, most of the recommended terms are applicable to both mobile and fixed-network 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, when available, industry-originated documents as well as results of previous 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 provides recommendations for terms that may be used by those who consider supporting the languages addressed in future products and services. It does not provide design guidance, nor does it intend to restrict the ability of market players to further improve and develop their devices 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.
- Standard506 pagesEnglish languagesale 15% off
- Standard506 pagesEnglish languagesale 15% off
- Standardization document506 pagesEnglish languagesale 10% offe-Library read for1 day
The present document specifies an evolved version of the Green Abstraction Layer capable of operating within ETSI
NFV environments.
- Standard113 pagesEnglish languagesale 15% off
- Standard113 pagesEnglish languagesale 15% off
- Standardization document113 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard36 pagesEnglish languagesale 15% off
- Standard36 pagesEnglish languagesale 15% off
- Standardization document36 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard376 pagesEnglish languagesale 15% off
- Standard375 pagesEnglish languagesale 15% off
- Standardization document375 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies design principles for information technology and network telecommunications cabling (e.g. SAN and LAN) in accordance with EN 50173 5, based upon the criteria and classifications for “availability” and “physical security” within EN 50600 1.
This document addresses the telecommunications cabling infrastructures used in data centres. It describes:
a) for design, the application of generic cabling standards in the EN 50173 series;
b) for installation specification, planning and practices and quality assurance, the application of standards in the EN 50174 series (and related standards).
In addition, this document specifies requirements and recommendations for the following:
1) general information technology cabling to support the IT operation of the data centre;
2) telecommunications cabling to monitor and control, as appropriate, power distribution, environmental control and physical security of the data centre;
3) other building automation cabling;
4) pathways, pathway systems, spaces and enclosures for the telecommunications cabling infrastructures.
Safety and electromagnetic compatibility (EMC) requirements are outside the scope of this document and are covered by other standards and regulations. However, information given in this document can be of assistance in meeting these standards and regulations.
- Standard61 pagesEnglish languagesale 10% offe-Library read for1 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, notably those terms that
end users are commonly exposed to. Recommended terms are provided in 19 languages: Bulgarian, Croatian, Czech,
Danish, Dutch, English, Finnish, French, German, Greek, Hungarian, Italian, Norwegian, Polish, Portuguese,
Romanian, Slovak, Spanish, and Swedish (as spoken in their respective European countries).
The recommended terms apply to mobile ICT devices and mobile applications (whether they are standalone or provide
access to related services) commonly found in mobile ICT devices. Though developed in a mobile ICT context, most of
the recommended terms are applicable to both mobile and fixed-network 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, industry-originated documents, and, when 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 devices 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.
- Standard386 pagesEnglish languagesale 15% off
- Standard375 pagesEnglish languagesale 15% off
- Standardization document375 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard44 pagesEnglish languagesale 15% off
- Standard44 pagesEnglish languagesale 15% off
- Standard44 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard384 pagesEnglish languagesale 15% off
- Standard385 pagesEnglish languagesale 15% off
- Standardization document385 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard62 pagesEnglish languagesale 15% off
- Standard61 pagesEnglish languagesale 15% off
- Standardization document61 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard374 pagesEnglish languagesale 15% off
- Standard375 pagesEnglish languagesale 15% off
- Standardization document375 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard93 pagesEnglish languagesale 15% off
- Standard92 pagesEnglish languagesale 15% off
- Standardization document92 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard30 pagesEnglish languagesale 15% off
- Standard30 pagesEnglish languagesale 15% off
- Standardization document30 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard379 pagesEnglish languagesale 15% off
- Standard379 pagesEnglish languagesale 15% off
- Standardization document379 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard3 pagesEnglish and French languagesale 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.
- Standard31 pagesEnglish languagesale 15% off
- Standard31 pagesEnglish languagesale 15% off
- Standardization document31 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard154 pagesEnglish languagesale 15% off
- Standard154 pagesEnglish languagesale 15% off
- Standardization document154 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard36 pagesEnglish languagesale 15% off
- Standard36 pagesEnglish languagesale 15% off
- Standardization document36 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard44 pagesEnglish languagesale 15% off
- Standard44 pagesEnglish languagesale 15% off
- Standard44 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard60 pagesEnglish languagesale 15% off
- Standard60 pagesEnglish languagesale 15% off
- Standardization document60 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard60 pagesEnglish languagesale 15% off
- Standard60 pagesEnglish languagesale 15% off
- Standardization document60 pagesEnglish languagesale 10% offe-Library read for1 day
- Standardization document60 pagesEnglish languagesale 10% offe-Library read for1 day
The present document proposes an evolved version of the Green Abstraction Layer formulation capable of operating within ETSI NFV environments.
- Standard71 pagesEnglish languagesale 15% off
- Standard71 pagesEnglish languagesale 15% off
- Standardization document71 pagesEnglish languagesale 10% offe-Library read for1 day
- Standardization document71 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard375 pagesEnglish languagesale 15% off
- Standard374 pagesEnglish languagesale 15% off
- Standardization document374 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard30 pagesEnglish languagesale 15% off
- Standard30 pagesEnglish languagesale 15% off
- Standardization document30 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard374 pagesEnglish languagesale 15% off
- Standard374 pagesEnglish languagesale 15% off
- Standardization document374 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard154 pagesEnglish languagesale 15% off
- Standard154 pagesEnglish languagesale 15% off
- Standardization document154 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard44 pagesEnglish languagesale 15% off
- Standard44 pagesEnglish languagesale 15% off
- Standardization document44 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard102 pagesEnglish languagesale 15% off
- Standard102 pagesEnglish languagesale 15% off
- Standardization document102 pagesEnglish languagesale 10% offe-Library read for1 day
- Standardization document102 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard19 pagesEnglish languagesale 15% off
- Standard19 pagesEnglish languagesale 15% off
- Standard19 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard153 pagesEnglish languagesale 15% off
- Standard153 pagesEnglish languagesale 15% off
- Standardization document153 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard5 pagesEnglish and French languagesale 15% off
RES/MTS-201873-1v4A1
- Standard364 pagesEnglish languagesale 15% off
- Standard364 pagesEnglish languagesale 15% off
- Standardization document364 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard374 pagesEnglish languagesale 15% off
- Standard368 pagesEnglish languagesale 15% off
- Standardization document368 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard368 pagesEnglish languagesale 15% off
- Standard367 pagesEnglish languagesale 15% off
- Standardization document367 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard45 pagesEnglish languagesale 15% off
- Standard45 pagesEnglish languagesale 15% off
- Standardization document45 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard35 pagesEnglish languagesale 15% off
- Standard34 pagesEnglish languagesale 15% off
- Standardization document34 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard364 pagesEnglish languagesale 15% off
- Standard364 pagesEnglish languagesale 15% off
- Standardization document364 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard59 pagesEnglish languagesale 15% off
- Standard59 pagesEnglish languagesale 15% off
- Standardization document59 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard153 pagesEnglish languagesale 15% off
- Standard153 pagesEnglish languagesale 15% off
- Standardization document153 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard3 pagesEnglish and French languagesale 15% off
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.
- Standard28 pagesEnglish languagesale 15% off
- Standard28 pagesEnglish languagesale 15% off
- Standard28 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard43 pagesEnglish languagesale 15% off
- Standard44 pagesEnglish languagesale 15% off
- Standardization document44 pagesEnglish languagesale 10% offe-Library read for1 day
- 1 (current)
- 2
- 3
- 4
- 5