ETSI TS 103 239-3 V1.1.1 (2014-12)

Integrated broadband cable telecommunication networks (CABLE); Testing; Conformance test specifications for MAP-E technology; Part 3: Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)

DTS/CABLE-00012-3

General Information

• Status: Published
• Publication Date: 07-Dec-2014
• Technical Committee: CABLE WG4 - Network, Fault, Monitoring and Performance Management and Test & Measu
• Current Stage: 12 - Completion
• Due Date: 07-Dec-2014
• Completion Date: 08-Dec-2014

Standards Content (Sample)

ETSI TS 103 239-3 V1.1.1 (2014-12)






TECHNICAL SPECIFICATION
Integrated broadband cable
telecommunication networks (CABLE);
Testing; Conformance test specifications
for MAP-E technology;
Part 3: Abstract Test Suite (ATS) and
Protocol Implementation eXtra Information for Testing (PIXIT)

�

---------------------- Page: 1 ----------------------
2 ETSI TS 103 239-3 V1.1.1 (2014-12)



Reference
DTS/CABLE-00012-3
Keywords
ATS, CPE, IP, IPv6, transition
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
The present document can be downloaded from:
http://www.etsi.org
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2014.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 239-3 V1.1.1 (2014-12)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Abstract test method . 8
4.1 Abstract protocol tester . 8
4.2 Test configurations . 9
4.2.1 CF01: BR as IUT . 9
4.2.2 CF02: CPE as IUT . 10
4.3 TTCN-3 Test architecture. 10
4.4 Ports and ASPs (Abstract Services Primitives) . 13
4.4.1 TTCN-3 ports. 13
4.4.2 Abstract Service Primitives . 13
5 Implemented Test Purposes . 14
6 ATS conventions . 14
6.1 Naming conventions . 14
6.1.1 General guidelines . 14
6.1.2 MAP-E specific TTCN-3 naming conventions . 15
6.1.3 Usage of Log statements . 16
6.1.4 Test Case (TC) identifier . 16
6.2 On line documentation . 17
Annex A (normative): Partial PIXIT proforma for MAP-ETSI. 18
A.1 Identification summary. 18
A.2 ATS summary . 18
A.3 Test laboratory . 18
A.4 Client identification . 19
A.5 SUT . 19
A.6 Protocol layer information. 19
A.6.1 Protocol identification . 19
A.6.2 IUT information . 20
Annex B (normative): PCTR Proforma for MAP-E . 21
B.1 Identification summary. 21
B.1.1 Protocol conformance test report . 21
B.1.2 IUT identification . 21
B.1.3 Testing environment . 21
B.1.4 Limits and reservation . 22
B.1.5 Comments. 22
B.2 IUT Conformance status . 22
B.3 Static conformance summary . 22
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 239-3 V1.1.1 (2014-12)
B.4 Dynamic conformance summary . 23
B.5 Static conformance review report . 23
B.6 Test campaign report . 24
B.7 Observations . 25
Annex C (normative): TTCN-3 library modules . 26
C.1 Electronic annex, zip file with TTCN-3 code . 26
Annex D (informative): Bibliography . 27
History . 28

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 239-3 V1.1.1 (2014-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://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Integrated broadband cable
telecommunication networks (CABLE).
The present document is part 3 of a multi-part deliverable covering the conformance test specification for MAP-E
technology, as identified below:
Part 1: "Protocol Implementation Conformance Statement (PICS) proforma";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)";
Part 3: "Abstract Test Suite (ATS) and Protocol Implementation eXtra Information for Testing (PIXIT)".
The development of the present document follows the guidance provided in the ETSI EG 202 798 [i.1]. Therefore the
present document is also based on the guidance provided in ETSI EG 202 798 [i.1].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will",
"will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms
for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 239-3 V1.1.1 (2014-12)
1 Scope
The present document contains the Abstract Test Suite (ATS) for MAP-E technology as defined in [1] and addressing
specific cable industry requirements as defined in ETSI TS 101 569-1 [11] in compliance with the relevant requirements
and in accordance with the relevant guidance given in ISO/IEC 9646-7 [5].
The objective of the present document is to provide a basis for conformance tests for MAP-E technology equipment
giving a high probability of inter-operability between different manufacturer's equipment.
These ISO standards for the methodology of conformance testing (ISO/IEC 9646-1 [2] and ISO/IEC 9646-2 [3]) as well
as the ETSI rules for conformance testing (ETSI ETS 300 406 [6]) are used as a basis for the test methodology.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] Draft-ietf-softwire-map-12: "Mapping of Address and Port with Encapsulation (MAP)".
[2] ISO/IEC 9646-1 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 1: General concepts".
[3] ISO/IEC 9646-2 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 2: Abstract Test Suite specification".
[4] ISO/IEC 9646-6 (1994): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 6: Protocol profile test specification".
[5] ISO/IEC 9646-7 (1995): "Information technology -- Open Systems Interconnection --
Conformance testing methodology and framework -- Part 7: Implementation Conformance
Statements".
[6] ETSI ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and profile
conformance testing specifications; Standardization methodology".
[7] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control
Notation version 3; Part 1: TTCN-3 Core Language".
[8] Void.
[9] Void.
[10] ETSI TS 103 239-2: "Integrated broadband cable telecommunication networks (CABLE); Testing;
Conformance test specifications for MAP-E technology; Part 2: Test Suite Structure and Test
Purposes (TSS&TP)".
[11] ETSI TS 101 569-1: "Integrated Broadband Cable Telecommunication Networks (CABLE); Cable
Network Transition to IPv6 Part 1: IPv6 Transition Requirements".
ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 103 239-3 V1.1.1 (2014-12)
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI EG 202 798: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and
interoperability testing".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI TS 101 569-1 [11],
ISO/IEC 9646-1 [2] and ISO/IEC 9646-7 [5] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply.
3GPP Third Generation Partnership Project
ASP Abstract Services Primitives
ATM Abstract Test Method
ATS Abstract Test Suite
BR Border Router
CPE Customer Premises Equipment
DHCP Dynamic Host Configuration Protocol
DNS Domain Name System
FTP File Transfer Protocol
GRT Global Routing Table
HTML HyperText Markup Language
HTTP HyperText Transfer Protocol
IP Internet Protocol
IPv4 IP version 4
IPv6 IP version 6
IUT Implementation Under Test
MAP-E Mapping of Address and Port with Encapsulation (MAP)
MSS Maximum Segment Size
MTC Main Test Component
MTS Methods for Testing and Specification
OSI Open System Interconnection
PA Platform Adaptor
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation Extra Information for Testing
PTC Parallel Test Components
SUT System Under Test
TA Test Adaptor
TC Test Case
TP Test Purpose
TSS Test Suite Structure
TTCN Testing and Test Control Notation
VRF Virtual Routing and Forwarding
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 103 239-3 V1.1.1 (2014-12)
4 Abstract test method
This clause describes the ATM used to test the MAP-E technology.
4.1 Abstract protocol tester
An abstract protocol tester presented in figure 1 is a process providing the test behaviour for testing an IUT. Thus it will
emulate an entity which is capable of proving the IUT functionalities. This type of test architecture provides a situation
of communication which is equivalent to real operation between real devices. The test system will simulate valid and
invalid behaviours, and will analyse the reaction of the IUT. Then the test verdict, e.g. pass or fail, will depend on the
result of this analysis. Thus this type of test architecture enables to focus the test objective on the IUT behaviour only.
In order to access an IUT, the corresponding abstract protocol tester needs to use lower layers to establish a proper
connection to the system under test (SUT) over a physical link (Lower layers link).

Figure 1: Generic abstract protocol tester
The "Protocol Data Units" (PDUs) are the messages exchanged between the IUT and the abstract protocol tester which
permits to trigger the IUT and to analyse its reaction. The result of the analysis allows to assign the test verdict.
Further control actions on the IUT may be necessary from inside the SUT, for instance to simulate a primitive from the
upper layer or the management/security entity. Further details on such control actions are provided by means of an
upper tester presented in clause 4.3.
The above "Abstract Test Method" (ATM) is well defined in ISO/IEC 9646-1 [2] and supports a wide range of
approaches for testing including the TTCN-3 abstract test language [7].
The abstract protocol tester used for MAP-E test suite is described in figure 2. The test system will send and receive IP
packets, by using other upper layer protocols such as DHCP, DNS and FTP, in order to analyse MAP-E functionality.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 103 239-3 V1.1.1 (2014-12)
Test System System Under Test
MAP-E
Functionality
DNS/DHCP/
FTP/HTTP/etc*
IP packets
IPv4/IPv6 IPv4/IPv6
Ethernet Ethernet
Lower Layers Link

NOTE: * Those protocols are used to prove certain MAP-E functionalities.

Figure 2: Abstract Protocol Tester - MAP-E
4.2 Test configurations
The test suite for MAP-E uses two test configurations in order to cover the different test scenarios. Distinction between
the two configurations is given by the two main components in MAP-E, which are BR and CPE.
4.2.1 CF01: BR as IUT
In this configuration, the BR is the IUT and the test system simulates an CPE in one side and a IPv4 host in the other
side.
Test system (TTCN-3)
Host -
Simulated
BR - IUT
CPE -
Simulated

Figure 3: CF01, BR equipment is the IUT
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 103 239-3 V1.1.1 (2014-12)
4.2.2 CF02: CPE as IUT
In this configuration, the CPE is the IUT and the test system simulates a BR equipment in one side and an IPv4 host in
the other side.
Test system (TTCN-3)
Host -
Simulated
CPE -
IUT
BR/Host -
Simulated

Figure 4: CF02, CPE equipment is the IUT
4.3 TTCN-3 Test architecture
In general, a conformance test system architecture based on TTCN-3 is as figure 5 shows.
MAP-E Test System SUT
Codec Test control Upper tester application
MAP-E Abstract Test Suite Upper tester
MAP-E IUT
transport
Test adaptor
Upper tester MAP-E lower MAP-E lower
Layers
transport Layers
Lower layer transport link
Upper tester transport link

Figure 5: Global test architecture
The "System Under Test" (SUT) contains:
• The "Implementation Under Test" (IUT), i.e. the object of the test.
• The "Upper tester application" enables to trigger or capture some actions (i.e. higher layer service primitives)
on the IUT.
• The "MAP-E lower layers" enable to establish a proper connection to the system under test (SUT) over a
physical link (Lower layer transport link).
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 103 239-3 V1.1.1 (2014-12)
• The "Upper tester transport" is a functionality, which enables the test system to communicate with the upper
tester application. Then the upper tester can be controlled by a TTCN-3 test component as part of the test
process.
The "MAP-E test system" contains:
• The "TTCN-3 test components" are processes providing the test behaviour. The test behaviour may be
provided as one single process or may require several independent processes.
• The "Codec" is a functional part of the test system to encode and decode messages between the TTCN-3
internal data representation and the format required by the related base standard.
• The "Test Control" enables the management of the TTCN-3 test execution (parameter input, logs, test
selection, etc.).
• The "Test adaptor" (TA) realizes the interface between the TTCN-3 ports using TTCN-3 messages, and the
physical interfaces provided by the IUT.
Based on the above test architecture, figure 5 shows a detailed test architecture used for the MAP-E. The MAP-E ATS
requires using several Parallel Test Components (PTC) dealing with specific communication protocols and a Main Test
Component (MTC) dealing with PTCs' synchronization. The different test components communicate with the MAP-E
SUT over several ports (described in clause 4.4) which are used to exchange protocol messages between the test
components and the MAP-E IUT.
The Upper tester entity enables triggering some functionalities by simulating actions or primitives from above
applications.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 103 239-3 V1.1.1 (2014-12)
MAP-E TTCN-3 ATS
DHCPv6 Http Ftp
component component component
Sync
Sync
port
MAP-E port
component
(sync)
Upper tester / CPE Monitoring Hosts DNS
external functions component component component
components
control
UT
port
Test Adaptor (TA)*
CODECS
FTP HTTP
IPv4 IPv6 DHCP DNS
IPv4
IPv6 Ftp Dns
IPv4 Dhcpv6 Http
port
port port port
port port port

External Upper Tester MAP-E lower layers stack
functions Transport

Platform Adaptor (PA) System Adaptor (SA)
IPv4
UT IPv6
port
port port

NOTE: * Test Adaptor (TA) is out of scope.

Figure 6: MAP-E TTCN-3 test architecture
The following protocol test components are available. Each of these components can be mapped to either a "Main Test
Component" (MTC), when only one component shall be executed, or to a "Parallel Test Component" (PTC), if several
components shall be used.
• CPE: This component simulates a MAP-E CPE entity and its functionality.
• HOST: These components simulate one or more hosts (one component per host).
• MONITORING: This component is used to monitor traffic from the IUT.
• DNS: This component simulates a DNS Client.
• DHCP: This component simulates a DHCPv6 Client.
• FTP: This component simulates a FTP client.
• HTTP: This component simulates a HTTP client.
The Sync component is mapped to the MTC and is used to trigger and synchronize the PTCs in order to orchestrate the
test environment executed by the PTCs. In addition, it starts and terminates the test cases.
The upper tester external functions control represents the functions which the protocol test components may use to
control the upper tester which is located in the SUT. These functions may use either external functions or dedicated
messages and a dedicated port to realise synchronization. These functions can be executed in the protocol test
components.
ETSI

---------------------- Page: 12 ----------------------
13 ETSI TS 103 239-3 V1.1.1 (2014-12)
4.4 Ports and ASPs (Abstract Services Primitives)
4.4.1 TTCN-3 ports
The MAP-E Test Suite implements the following ports:
• Ipv6Port, to send and receive IPv6 packets.
• Ipv4Port, to send and receive IPv4 packets.
• DnsPort, to send and receive DNS messages.
• Dhcpv6Port, to send and receive DHCPv6 messages.
• FtpPort, to trigger the following FTP actions: login, logout, and data sending (both IPv4 and IPv6). It can
monitor incoming traffic.
• HttpPort, to trigger the following HTTP actions: data sending (both IPv4 and IPv6). It can monitor incoming
traffic.
• UtPort, included in order to be able to stimulate the IUT and receive extra information from IUT upper layers
(it is not used in the current implementation and is provided for future expansion).
4.4.2 Abstract Service Primitives
Abstract service primitives are commands or actions that need to be performed on the IUT in order to trigger certain
behaviour or to obtain information about the IUT state.
The list of ASP used in the MAP-E ATS is shown in table 1.
Table 1: MAP-E Abstract Service Primitives
TTCN-3 text Action/Command Description
Are routing tables configured GRT Action To check that routing tables are
upstream ingress & VRF upstream properly configured
egress?
Is Gateway Prefix withdrawn? Action To check that the gateway prefix is
withdrawn
Remove the route Command To remove the route from IUT routing
tables
Remove the cache Command To remove the IUT cache

ETSI

---------------------- Page: 13 ----------------------
14 ETSI TS 103 239-3 V1.1.1 (2014-12)
5 Implemented Test Purposes
Table 2 shows the test purposes from ETSI TS 103 239-2 [10] which have been implemented and included in the
present document.
Table 2: Implemented Test Purposes
TP Identifier TC Identifier Group Subgroup PICS Untestable Implemented
TP/MAP-E/BR/BF/BV/01 TC_MAPE_BR_BF_BV_01 Basic Function PICS_ROLE_IS_BR  Yes
TP/MAP-E/BR/AS/BV/01 TC_MAPE_BR_AS_BV_01 PICS_ROLE_IS_BR  Yes
TP/MAP-E/BR/AS/BV/02 TC_MAPE_BR_AS_BV_02 PICS_ROLE_IS_BR  Yes
Address Structure
TP/MAP-E/BR/AS/BV/03 TC_MAPE_BR_AS_BV_03 PICS_ROLE_IS_BR,
PICS_PORT_RANGE  Yes
BR
TP/MAP-E/BR/SC/BV/01 TC_MAPE_BR_SC_BV_01 Session Control PICS_ROLE_IS_BR  Yes
TP/MAP-E/BR/AA/BV/01 TC_MAPE_BR_AA_BV_01 Anycast
Addressing PICS_ROLE_IS_BR  Yes
TP/MAP-E/BR/MSSC/BV/01 TC_MAPE_BR_MSSC_BV_01 MSS Clamping PICS_ROLE_IS_BR  Yes
TP/MAP-E/BR/FRAG/BV/01 TC_MAPE_BR_FRAG_BV_01 Fragmentation PICS_ROLE_IS_BR  Yes
TP/MAP- TC_MAPE_BR_GWA_BV_01
E/CPE/GWA/BV/01 PICS_ROLE_IS_CPE  Yes
Gateway
TP/MAP- TC_MAPE_BR_GWA_BV_02 Addressing
E/CPE/GWA/BV/02 PICS_ROLE_IS_CPE  Yes
TP/MAP-E/CPE/BF/BV/01 TC_MAPE_BR_BF_BV_01 Basic Function PICS_ROLE_IS_CPE  Yes
TP/MAP-E/CPE/AS/BV/01 TC_MAPE_BR_AS_BV_01 Address Structure PICS_ROLE_IS_CPE  Yes
CPE
TP/MAP- TC_MAPE_BR_FRAG_BV_01
Fragmentation
E/CPE/FRAG/BV/01 PICS_ROLE_IS_CPE  Yes
TP/MAP- TC_MAPE_BR_MSSC_BV_01
MSS Clamping
E/CPE/MSSC/BV/01 PICS_ROLE_IS_CPE  Yes
TP/MAP-E/CPE/SC/BV/01 TC_MAPE_BR_SC_BV_01 PICS_ROLE_IS_CPE,
Session Control
PICS_PORT_RANGE  Yes

6 ATS conventions
The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions
made for the development of the ATS. These conventions shall be considered during any later maintenance or further
development of the ATS.
6.1 Naming conventions
This test suite follows the naming convention guidelines provided in ETSI ETS 300 406 [6] and ETSI EG 202 798 [i.1].
6.1.1 General guidelines
The naming convention is based on the following underlying principles:
• Identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of
TTCN-3 element it represents.
• Suffixes should not be used except in those specific cases identified in table 3.
• Prefixes and suffixes should be separated from the body of the identifier with an underscore ("_").
EXAMPLE 1: c_sixteen, t_wait.
• Only module names, data type names and module parameters should begin with an upper-case letter. All other
names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter.
• The start of second and subsequent words in an identifier should
...