SIST EN 301 452-2 V1.3.1:2005

• Abstract:

  ATS & partial PIXIT for Call completion services.

• Status: Published
• Publication Date: 31-Mar-2005
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Apr-2005
• Due Date: 01-Apr-2005
• Completion Date: 01-Apr-2005
• Mandate: T-326
• Ref Project: ETSI EN 301 452-2 V1.3.1 (2000-12) - Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Call completion supplementary service for the VPN b service entry point; Part 2: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma

SIST EN 301 452-2 V1.3.1:2005 is the SIST adoption of ETSI EN 301 452-2 V1.3.1 for the call completion supplementary service in a Private Integrated Services Network (PISN). It specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for implementations at the VPN "b" service entry point, so it is mainly used when preparing and running conformance tests.

What does SIST EN 301 452-2 V1.3.1:2005 specify?

SIST EN 301 452-2 V1.3.1:2005 specifies the testing material for the Call completion supplementary service (SS-CC) at the VPN "b" service entry point. The standard does not describe the service behavior itself; it provides the test suite and the information needed to adapt that suite to a particular implementation.

The document is Part 2 of a multi-part deliverable. Part 1, EN 301 452-1, provides the Test Suite Structure and Test Purposes (TSS&TP) that relate to this ATS and partial PIXIT proforma.

Annex	What it covers
Annex A	Protocol Conformance Test Report (PCTR) proforma
Annex B	Partial PIXIT proforma
Annex C	Abstract Test Suite (ATS)

The main body is organized into clauses on scope, references, definitions and abbreviations, the abstract test method, untestable test purposes, ATS conventions, ATS-to-TP mapping, and conformance for PCTR, PIXIT and ATS.

What are the key requirements of SIST EN 301 452-2 V1.3.1:2005?

SIST EN 301 452-2 V1.3.1:2005 gives the rules for how the ATS is written, how it is applied, and what a conforming test report or test setup must contain. For a lab or implementer, the practical impact is that the test method, encoding rules and proformas are fixed, so results can be compared consistently.

The test method is multi-party

Clause 4 uses a multi-party test method. The Point of Control and Observation (PCO) named L0 sits at the service access point between layers 2 and 3, and verdicts are assigned from what is observed there. A second PCO, called O, is for operator control above the IUT and is not used for verdicts.

In practice, this means the tester must separate what is only operational control from what is evidence of conformance. Actions routed through O help set up the System Under Test (SUT), but they do not count as test observations.

The ATS is intended to be fully testable

Clause 5 states that there are no untestable test cases associated with the ATS and the abstract test method. That matters because the suite is meant to be executable as written, without built-in test purposes that the method cannot reach.

TTCN and ASN.1 are used together

Clause 6 says the ATS uses the TTCN version defined in TR 101 101 and uses ASN.1 where it helps model data structures, restrictions, or remote operation components. The standard also allows TTCN and ASN.1 to be combined by referring to ASN.1 types from TTCN types.

For a test tool or test realizer, this means the implementation must support both notations and their interaction, not just one of them.

Encoding rules are controlled

Clause 6.2.2 sets the encoding approach for ASN.1 in this ATS. The default is the ISDN-style direct encoding used for ASN.1 constraint tables, while Basic Encoding Rules (BER) are used only where the table header says ASN1_Encoding: BER. The clause also states that ASN.1 types of type "Component" are encoded using BER.

In practice, this tells the test developer how to turn abstract data into concrete test messages. Using the wrong encoding would make a test case look correct in structure but incorrect on the wire.

Test purposes map directly to test cases

Clause 7 states that the identifiers used for the test purposes are reused as test case names. This creates a one-to-one mapping between TPs and test cases.

That makes traceability straightforward for test planning, coverage review and defect reporting.

Conformance is tied to the proformas and the ATS

Clauses 8, 9 and 10 define what conformance means for the report, the PIXIT and the ATS. A test laboratory producing a PCTR must use the proforma in Annex A, and a PIXIT or augmented partial PIXIT must be technically equivalent to Annex B. A conforming ETS must be technically equivalent to the ATS in Annex C, and the MOT used by a laboratory must conform to the ATS requirements.

For users, this means the document is not only a test suite - it also specifies the report and preparation information needed to run it properly.

The PIXIT captures implementation-specific test settings

Annex B asks for parameter values, timer values, information parameter values, configuration options and basic call information element coding. The items cover matters such as Business Group data, waiting times, Called Party Number details, diversion behavior, signaling-connection retention, congestion simulation, and related basic call coding.

In practice, the IUT provider or test owner must fill in these values so the laboratory can adapt the suite to the actual implementation under test.

What terms does SIST EN 301 452-2 V1.3.1:2005 define?

• Abstract Test Suite (ATS) - The structured set of abstract test cases in Annex C that is used to assess conformance.
• Protocol Implementation eXtra Information for Testing (PIXIT) - The implementation-specific information needed to prepare and parameterize testing.
• Protocol Conformance Test Report (PCTR) - The report template used to record the test setup, status, results and observations.
• Implementation Under Test (IUT) - The protocol implementation being checked against the specified conformance requirements.
• System Under Test (SUT) - The complete system in which the IUT is exercised during testing.
• Point of Control and Observation (PCO) - The interface where the tester controls and/or observes protocol behavior.
• Tree and Tabular Combined Notation (TTCN) - The notation used to write the ATS in this standard.

Who uses SIST EN 301 452-2 V1.3.1:2005?

SIST EN 301 452-2 V1.3.1:2005 is used by conformance test laboratories, test realizer teams, and manufacturers or integrators implementing SS-CC for PISN and VPN "b" service entry point inter-exchange signaling. They use it to build a Means Of Testing (MOT), execute an ETS, complete PIXIT and PCTR proformas, and document the outcome of conformance assessment.

It is also relevant to engineers and quality managers who need to prepare an implementation for testing or review a test report for a call completion supplementary service. The document is classified under telephone networks, so it sits in telecom interoperability and conformance work rather than in product design alone.

Which standards are used with SIST EN 301 452-2 V1.3.1:2005?

• ETSI ETS 300 366 - The base protocol specification for the call completion supplementary services that the ATS tests against.
• ETSI EN 301 452-1 (V1.1.4) - The companion part that defines the Test Suite Structure and Test Purposes related to this ATS and partial PIXIT.
• ISO/IEC 9646 (all parts) - The conformance testing framework used for ATS, PCTR, PIXIT and test realization.
• ETSI TR 101 101 (V1.1.1) - The TTCN interim version used for the ATS conventions in this document.
• ISO/IEC 8825-1 - The ASN.1 encoding rules referenced for BER, CER and DER.

What does the SIST EN 301 452-2 V1.3.1:2005 document contain?

The document contains the abstract test method description, the ATS conventions for TTCN and ASN.1, and the rules for ATS-to-TP mapping and conformance. Annex A provides a full PCTR proforma with identification, environment, conformance summary and a detailed test campaign report format.

Annex B is a partial PIXIT proforma with tables for parameter values, timer values, information parameter values, configuration options and coding items. Annex C contains the ATS in both TTCN.GR and TTCN.MP form, and the report tables list test groups for originating, terminating and interworking cases.

SLOVENSKI STANDARD
01-april-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,61±6LJQDOL]DFLMVNLSURWRNROPHG
FHQWUDODPL±'RSROQLOQDVWRULWHYGRNRQþDQMHNOLFD]DYVWRSQRWRþNR931E
VWRULWYH±GHO$EVWUDNWQLSUHVNXãDOQLQL]$76LQGRGDWQDLQIRUPDFLMD]D
SUHVNXãDQMHGHOQHL]YHGEHSURWRNROD3,;,7±3URIRUPDVSHFLILNDFLMD
Private Integrated Services Network (PISN); Inter-exchange signalling protocol; Call
completion supplementary service for the VPN b service entry point; Part 2: Abstract
Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing
(PIXIT) proforma
Ta slovenski standard je istoveten z: EN 301 452-2 Version 1.3.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Private Integrated Services Network (PISN);
Inter-exchange signalling protocol;
Call completion supplementary service
for the VPN "b" service entry point;
Part 2: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT)
proforma
2 ETSI EN 301 452-2 V1.3.1 (2000-12)
Reference
DEN/SPAN-05188-3
Keywords
PSS1, PISN, VPN, supplementary service,
CCBS, CCNR, testing, ATS, PIXIT
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: [phone] Fax: [phone]
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2000.
All rights reserved.
ETSI
3 ETSI EN 301 452-2 V1.3.1 (2000-12)
Contents
Intellectual Property Rights .5
Foreword.5
1 Scope.6
2 References.6
3 Definitions and abbreviations.6
3.1 Definitions . 6
3.2 Abbreviations. 6
4 Abstract Test Method (ATM).7
4.1 Description of ATM used . 7
5 Untestable test purposes.8
6 ATS conventions .8
6.1 Version of TTCN used . 8
6.2 Use of ASN.1. 8
6.2.1 Situations where ASN.1 is used. 8
6.2.2 Specification of encoding rules. 8
7 ATS to TP map.9
8 PCTR conformance .9
9 PIXIT conformance .10
10 ATS conformance.10
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma .11
A.1 Identification summary .11
A.1.1 Protocol conformance test report. 11
A.1.2 IUT identification. 11
A.1.3 Testing environment. 12
A.1.4 Limits and reservations. 12
A.1.5 Comments. 12
A.2 IUT conformance status.12
A.3 Static conformance summary .12
A.4 Dynamic conformance summary.13
A.5 Static conformance review report.13
A.6 Test campaign report .13
A.7 Observations.16
Annex B (normative): Partial PIXIT proforma.17
B.1 Identification summary .17
B.2 Abstract test suite summary .17
B.3 Test laboratory.17
B.4 Client (of the test laboratory) .18
B.5 System Under Test (SUT).18
B.6 Protocol information.19
B.6.1 Protocol identification . 19
ETSI
4 ETSI EN 301 452-2 V1.3.1 (2000-12)
B.6.2 IUT information . 19
B.6.2.1 Parameter values. 19
B.6.2.2 Timer values. 19
B.6.2.3 Information parameter values . 20
B.6.2.4 Configuration Options. 20
B.7 Basic call PIXIT items .21
B.7.1 Parameter values - information element coding. 21
Annex C (normative): Abstract Test Suite (ATS).22
C.1 The TTCN Graphical form (TTCN.GR).22
C.2 The TTCN Machine Processable form (TTCN.MP) .22
Bibliography.23
History .24
ETSI
5 ETSI EN 301 452-2 V1.3.1 (2000-12)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and
Protocols for Advanced Networks (SPAN).
The present document is part 2 for a multi-part deliverable covering the Inter-exchange signalling protocol; Call
completion supplementary service for the VPN "b" service entry point, as described below:
Part 1: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Part 2: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification".
National transposition dates
Date of adoption of this EN: 8 December 2000
Date of latest announcement of this EN (doa): 31 March 2001
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 September 2001
Date of withdrawal of any conflicting National Standard (dow): 30 September 2001
ETSI
6 ETSI EN 301 452-2 V1.3.1 (2000-12)
1 Scope
This second part of EN 301 452 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra
Information for Testing (PIXIT) proforma for the VPN "b" entry point of implementations conforming to the standard
for the Call completion supplementary service (SS-CC) as described in ETS 300 366 [1].
EN 301 452-1 [2] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS and partial PIXIT
proforma specification.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, subsequent revisions do apply.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ETSI ETS 300 366 (1995): "Private Integrated Services Network (PISN); Inter-exchange
signalling protocol; Call completion supplementary services [ISO/IEC 13870 (1995) modified]".
[2] ETSI EN 301 452-1 (V1.1.4) "Private Integrated Services Network (PISN); Inter-exchange
signalling protocol: Call completion supplementary service for the VPN "b" service entry point;
Test Suite and Test Purposes (TSS&TP)".
[3] ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework".
[4] ETSI TR 101 101 (V1.1.1): "Methods for Testing and Specification (MTS); TTCN interim version
including ASN.1 1994 support [ISO/IEC 9646-3] (Second Edition Mock-up for JTC1/SC21
Review)".
[5] ISO/IEC 8825-1: "Information technology - ASN.1 encoding rules: Specification of Basic
Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules
(DER)" (See also ITU-T Recommendation X.690)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ISO/IEC 9646 [3] shall apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
APDU Application Protocol Data Unit
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
ETSI
7 ETSI EN 301 452-2 V1.3.1 (2000-12)
BER Basic Encoding Rules
CCBS Call Completion to Busy Subscriber
CCNR Call Completion on No Reply
CM Co-ordination Message
ETS Executable Test Suite
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
MTC Main Test Component
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PTC Parallel Test Component
SUT System Under Test
TP Test Purpose
TTCN Tree and Tabular Combined Notation
VPN Virtual Private Network
4 Abstract Test Method (ATM)
4.1 Description of ATM used
The multi-party test method is applied for testing the IUT. The general configuration used is shown in figure 1.
A Point of Control and Observation (PCO) resides at the service access point between layers 2 and 3 in the test system.
The PCO used by the MTC is named "L0" (for Lower). This PCO is used to control and observe the behaviour of the
Implementation Under Test (IUT) and test case verdicts are assigned depending on the behaviour observed at this PCO.
A second "informal" PCO, called "O" (for Operator) is used to specify control but not observation above the IUT;
events at this PCO are never used to generate test case verdicts. Messages sent by the tester at this PCO explicitly
indicate to the operator actions which are to be performed on the SUT. This is regarded as a preferred alternative to the
use of the implicit send event.
CPA1
PTC1 MTC
PCO O PCO L0
IUT
Figure 1: Multi-party test method
The relationship between the IUT and the tester is as follows:
• when the IUT is either in the Originating configuration or in the Terminating configuration, the IUT is connected
to the MTC. The verdict depends on the behaviour observed at the PCO between the IUT and the MTC. The
PCO O is used to specify control above the IUT, using the PTC process.
ETSI
8 ETSI EN 301 452-2 V1.3.1 (2000-12)
5 Untestable test purposes
There are no untestable test cases associated with this ATS and ATM.
6 ATS conventions
6.1 Version of TTCN used
The version of TTCN used is that defined in TR 101 101 [4].
6.2 Use of ASN.1
6.2.1 Situations where ASN.1 is used
ASN.1 has been used for three major reasons. First, types defined in ASN.1 can model problems that "pure" TTCN
cannot. For instance, data structures modelling ordered or unordered sequences of data are preferably defined in ASN.1.
Second, ASN.1 provides a better restriction mechanism for type definitions by using sub-type definitions. Third, it is
necessary to use ASN.1 to reproduce the type definitions for remote operation components as specified in the base
standards in ASN.1.
The possibility to use TTCN and ASN.1 in combination is used, i.e. referring to an ASN.1 type from a TTCN type.
6.2.2 Specification of encoding rules
There is a variation in the encoding rules applied to ASN.1 types and constraints specified in this ATS and therefore a
mechanism is needed to differentiate the encoding rules. However the mechanism specified in
ISO/IEC 9646-3/AM2 [3] and in TR 101 101 [4] does not facilitate definition of the encoding rules as needed for this
ATS. A solution is therefore used which is broadly in the spirit of ISOIEC 9646-3/AM2 [3] in which comment fields
have been used as a means of encoding rules.
For ASN.1 used in this ATS, two variations of encoding rules are used. One is the commonly known Basic Encoding
Rules (BER) as specified in ISO/IEC 8825-1 [5]. In the second case the encoding is according to ISDN, i.e. the ASN.1
data types are a representation of structures contained within the ISDN specification (basic call, Generic functional
protocol or individual supplementary service). For example, if octets of an information element are specified in ASN.1
as a SEQUENCE then this should be encoded in an Executable Test Suite (ETS) as any other ISDN information
element specified using tabular TTCN. This ISDN encoding variation is the default encoding rule for this ATS. This
means that all ASN.1 constraint tables are encoded using ISDN (non-BER) encoding unless stated otherwise. BER
encoding should never be applied to an ASN.1 constraint where BER encoding has not been specified. This encoding
rule is sometimes named "Direct Encoding".
For BER encoding, an indication is given in the comments field of the table header. For this ATS such indications
appear in the ASN.1 type constraint declaration tables only. In the table header comment field, the notation
"ASN1_Encoding: BER" is used.
In this particular ATS all ASN.1 type constraints which are of type "Component" are to be encoded using BER.
Table 1 shows an example of a ASN.1 type Constrained Declaration used in this ATS.
ETSI
9 ETSI EN 301 452-2 V1.3.1 (2000-12)
Table 1: ASN.1 type constraint declaration showing use of encoding variation
ASN.1 Type Constraint Declaration
Constraint Name : CCBSRequestInv_S1 (INV_ID: InvokeIDType)
ASN.1 Type : Component
Derivation Path :
Comments : Sent Component: CCBSRequest Invoke component, maintain signalling connection
is required (i.e. retain_sig_connection TRUE)
ASN1_Encoding: BER
Description
cCBSRequest_Comp
cCBSRequest_InvokeComp
{ invokeID INV_ID, -- the invoke identifier
operation_value localValue 40, -- value for operation
argument {numberA PX_Number_A1,
numberB PX_Number_B,
service PX_PSS1_IE, -- BCAP/HLC/LLC embedded
subaddrA OMIT,
subaddrB OMIT,
can_retain_service OMIT,
retain_sig_connection TRUE,
extension OMIT
}
}
Detailed comments :
7 ATS to TP map
The identifiers used for the TPs are reused as test case names. Thus there is a straightforward one-to-one mapping.
8 PCTR conformance
A test laboratory, when requested by a client to produce a PCTR, is required, as specified in ISO/IEC 9646-5 [3], to
produce a PCTR conformant with the PCTR template given in annex B of ISO/IEC 9646-5 [3].
Furthermore, a test laboratory, offering testing for the ATS specification contained in annex C, when requested by a
client to produce a PCTR, is required to produce a PCTR conformant with the PCTR proforma contained in annex A.
A PCTR which conforms to this PCTR proforma specification shall preserve the content and ordering of the clauses
contained in annex A. Clause A.6 of the PCTR may contain additional columns. If included, these shall be placed to the
right of the existing columns. Text in italics may be retained by the test laboratory.
ETSI
10 ETSI EN 301 452-2 V1.3.1 (2000-12)
9 PIXIT conformance
A test realizer, producing an executable test suite for the ATS specification contained in annex C, is required, as
specified in ISO/IEC 9646-4 [3], to produce an augmented partial PIXIT proforma conformant with this partial PIXIT
proforma specification.
An augmented partial PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a
minimum, have contents which are technically equivalent to annex B. The augmented partial PIXIT proforma may
contain additional questions that need to be answered in order to prepare the Means Of Testing (MOT) for a particular
IUT.
A test laboratory, offering testing for the ATS specification contained in annex C, is required, as specified in
ISO/IEC 9646-5 [3], to further augment the augmented partial PIXIT proforma to produce a PIXIT proforma
conformant with this partial PIXIT proforma specification.
A PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, have contents
which are technically equivalent to annex B. The PIXIT proforma may contain additional questions that need to be
answered in order to prepare the test laboratory for a particular IUT.
10 ATS conformance
The test realizer, producing MOT and ETS for this ATS specification, shall comply with the requirements of
ISO/IEC 9646-4 [3]. In particular, these concern the realization of an ETS based on each ATS. The test realizer shall
provide a statement of conformance of the MOT to this ATS specification.
An ETS which conforms to this ATS specification shall contain test groups and test cases which are technically
equivalent to those contained in the ATS in annex C. All sequences of test events comprising an abstract test case shall
be capable of being realized in the executable test case. Any further checking which the test system might be capable of
performing is outside the scope of this ATS specification and shall not contribute to the verdict assignment for each test
case.
Test laboratories running conformance test services using this ATS shall comply with ISO/IEC 9646-5 [3].
A test laboratory which claims to conform to this ATS specification shall use an MOT which conforms to this ATS.
ETSI
11 ETSI EN 301 452-2 V1.3.1 (2000-12)
Annex A (normative):
Protocol Conformance Test Report (PCTR) proforma
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that
users of the present document may freely reproduce the PCTR proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PCTR.
A.1 Identification summary
A.1.1 Protocol conformance test report
PCTR number:
PCTR date:
Corresponding SCTR number:
Corresponding SCTR date:
Test laboratory identification:
Test laboratory manager:
Signature:
A.1.2 IUT identification
Name:
Version:
Protocol specification: ETS 300 366
PICS:
Previous PCTRs (if any):
ETSI
12 ETSI EN 301 452-2 V1.3.1 (2000-12)
A.1.3 Testing environment
PIXIT reference number:
ATS specification: EN 301 452-2
Abstract test method: Multi-party test method (see ISO/IEC
...