Technical Committee

SSCOP Conformance Abstract Test Suite 
version 1.1

AF-TEST-0067.001
May, 1999

© 1999 by The ATM Forum.  The ATM Forum hereby grants the limited right to reproduce this specification/document in whole, but not in part, for the purpose of including this specification/document, at no extra cost and on an “as is” basis, in documentation for products.  This right shall not be, and is not, transferable.  Any material so included shall contain all of the disclaimers and propriety and other notices contained herein or therein.  All other rights reserved.  Except as expressly stated in this notice, no part of this specification/document may be reproduced or transmitted in any form or by any means, or stored in any information storage and retrieval system, without the prior written permission of The ATM Forum.

The information in this publication is believed to be accurate as of its publication date.  Such information is subject to change without notice and The ATM Forum is not responsible for any errors.  The ATM Forum does not assume any responsibility to update or correct any information in this publication.  Notwithstanding anything to the contrary, neither The ATM Forum nor the publisher make any representation or warranty, expressed or implied, concerning the completeness, accuracy, or applicability of any information contained in this publication.  No liability of any kind shall be assumed by The ATM Forum or the publisher as a result of reliance upon any information contained in this publication.

The receipt or any use of this document or its contents does not in any way create by implication or otherwise:

•	Any express or implied license or right to or under any ATM Forum member company's patent, copyright, trademark or trade secret rights which are or may be associated with the ideas, techniques, concepts or expressions contained herein; nor
•	Any warranty or representation that any ATM Forum member companies will announce any product(s) and/or service(s) related thereto, or if such announcements are made, that such  announced product(s) and/or service(s) embody any or all of the ideas, technologies, or concepts contained herein; nor
•	Any form of relationship between any ATM Forum member companies and the recipient or user of this document.

Implementation or use of specific ATM standards or recommendations and ATM Forum specifications will be voluntary, and no company shall agree or be obliged to implement them by virtue of participation in The ATM Forum.

The ATM Forum is a non-profit international organization accelerating industry cooperation on ATM technology.  The ATM Forum does not, expressly or otherwise, endorse or promote any specific products or services.

NOTE:  The user's attention is called to the possibility that implementation of the ATM interoperability specification contained herein may require use of an invention covered by patent rights held by ATM Forum Member companies or others.  By publication of this ATM interoperability specification, no position is taken by The ATM Forum with respect to validity of any patent claims or of any patent rights related thereto or the ability to obtain the license to use such rights.  ATM Forum Member companies agree to grant licenses under the relevant patents they own on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license.  For additional information contact:

The ATM Forum
Worldwide Headquarters
2570 West El Camino Real, Suite 304
Mountain View, CA 94040-1313
Tel:	+1-650-949-6700
Fax:	+1-650-949-6705

Preperation and checking of an abstract test suite of this kind requires the concerted time and effort of many individuals. The Chair wishes to highlight the efforts of the following contributors to this specification:

Leslie Collica

The Chair especially wishes to thank the editor Johan Appelbom for his diligent and extensive work.

Gregan Crawford   (Test Working Group Chair)

Contents
1. 	Introduction	2
1.1	Definition of Terminologies	2
1.1.1	Valid PDU	2
1.1.2	Invalid PDU	2
1.1.3 	Inopportune PDU	2
1.2	Power Up	2
2.	Methodology	2
3.	Conformance ATS Status Report	3
4.	Test Configuration	3
5.	Test Suite Structure	4
6.	Assumptions on the Capabilities of the Testers	4
6.1	Error Generation	4
7.	Timers	4
8.	Abbreviations	5
9.	References	5
Annex A PIXIT	6
Annex B Abstract Test Suite	8

1. 	Introduction

This document provides the conformance abstract test suite for the Service Specific Connection Oriented Protocol (SSCOP) ITU Recommendation Q.2110[2]. This test suite aligns with the principles defined in OSI Conformance Testing Methodology and Framework, ISO 9646 Parts 1-2[3][4].  The test scripts are written in the internationally standardized Tree and Tabular Combined Notation, TTCN, defined in ISO 9646 Part 3[5].  

The Protocol Implementation eXtra Information for Testing (PIXIT) proforma is provided in Annex A.  The PIXIT questionnaire needs to be completed for a particular System equipment (Implementation Under Test) prior to conformance testing. 

1.1	Definition of Terminologies

This test suite uses valid, invalid, and inopportune Protocol Data Units (PDUs) to test the IUT behavior.  These terms are defined as follows:

1.1.1	Valid PDU
 
A valid PDU is an expected PDU which arrives at the correct state or phase and does not belong to any of the categories listed under invalid PDUs.

1.1.2	Invalid PDU
 
An invalid PDU is a PDU which is syntactically incorrect.

1.1.3 	Inopportune PDU
 
An inopportune PDU is a syntactically valid PDU arriving at a time (IUT's state) when it should be considered irrelevant by the IUT.

1.2	Power Up

Power Up is a function that allows the system to accept a BGN PDU in state Idle irrespectively of the sequence number in the BGN PDU. 
This functionality was approved by ITU SG/11 at their plenary January 31,1997. It is described in ITU document 
COM 11-R 67-E
It is also described by ATMForum contribution 97-0216. ATMForum has accepted this functionality.

2.	Methodology

This conformance test suite has been developed as described in ISO/IEC International Standard 9646-1 and 2 [3][4].  A testing matrix has been developed after study of the SSCOP Specification and a selection of the appropriate test groups.  The remote single layer embedded (RSE) test method has been selected, as shown below, and test cases have been generated.  The notation used in this abstract test suite is the Tree and Tabular Combined Notation (TTCN) as described in ISO/IEC IS 9646-3[5].  This version of the SSCOP conformance test suite uses sequential TTCN, but conversion into concurrent TTCN will bring some improvement in the test case description and implementation.
3.	Conformance ATS Status Report

The TTCN of this abstract test suite has passed the syntax checking process for version
Af-test-0067.001.mp dated 990219 of the .mp file according to the TTCN specification in 
ISO 9646 part 3 version ISO/IEC 9646-3:1997 second edition.

Status of Test Suite	Date	Comments	
Test suite executed against
an implementation	990219	Executed against a simulated environment	
Revision	990219	Af-test-0067.001	

4.	Test Configuration

The test configuration used for testing SSCOP is given in Figure 1.  The system under test (SUT) includes the SSCOP of the IUT, the Service Specific Convergence Function (SSCF), and a higher layer, such as Q.2931.  For the remote, single layer testing for the SSCOP, the tester has only one Point of Control and Observation (PCO).

System Under Test

Tester

SSCOP-PDUs

Higher
Layers

SSCF

CP-AAL5

ATM

PHY

SSCOP

 LT_PCO

IUT
SSCOP

Figure 1.  Example Configuration for SSCOP testing using RSE test method

5.	Test Suite Structure

For the SSCOP test suite, there are two major groups, Protocol Capabilities (PC) and System Parameters (SP) group.  In the PC group, there is a subgroup for each of the SSCOP states (state_x, where x = 1 - 10), each having a subgroup for valid, invalid, and inopportune tests, as defined in the Definitions of Terminologies section above.  The System Parameters group includes tests for SSCOP system parameters (e.g., timers and counters).
 
The test structure for the SSCOP ATS is:

	 - SSCOP/
	   - Protocol Capabilities (PC)
		- state_1
			- valid
			- invalid
			- inopportune
		- state_2	
			- valid
			- invalid
			- inopportune
	   	:
	   	:
		- state_10	
			- valid
			- invalid
			- inopportune
   	- System Parameters (SP)
		- Timer
		- Parm 

6.	Assumptions on the Capabilities of the Testers

6.1	Error Generation

The tester is asked to generate errors in some test cases, to allow for testing of error conditions.  
7.	Timers

Several timers have been defined for testing.  These timers are:

(1)	T_Wait is used to limit the test time waiting for "no response" from the IUT.  
(2)	T_Opr is used to allow sufficient time for a test operator to initiate some test action.  This timer is used in conjunction with an "Implicit send" for test coordination. 

These timers are not used to verify the exact timing of an implementation, but to limit the time which the test should wait for a PDU or to limit the total duration of the test.
8.	Abbreviations

	ATM	Asynchronous Transfer Mode
	ATS	Abstract Test Suite
	ISO/IEC	International Organization for Standardization/International Electrotechnical Commission
	IUT	Implementation Under Test
	PCO	Point of Control and Observation
	PDU	Protocol Data Unit
	PHY	Physical Layer
	PICS	Protocol Implementation Conformance Statement
	PIXIT	Protocol Implementation Extra Information for Testing
	RSE	Remote Single Layer Embedded test method
	SSCF	Service Specific Convergence Function
	SSCOP	Service Specific Connection Oriented Protocol
	SUT	System Under Test
	TTCN	Tree and Tabular Combined Notation
	UNI	User-Network Interface

9.	References

[1]	ATM Forum User-Network Interface (UNI) Specification 3.1.

[2] 	ITU Recommendation Q.2110, B-ISDN - ATM Adaptation Layer - Service Specific Connection Oriented Protocol (SSCOP).

[3]	ISO/IEC 9646-1 "Information Technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General Concepts", 1991.

[4]	ISO/IEC 9646-2 "Information Technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract test suite specification", 1991.

[5]	ISO/IEC 9646-3 "Information Technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The tree and tabular combined notation", 1991.  

Annex A PIXIT

	Protocol Implementation eXtra Information for Testing (PIXIT) Proforma 
	For SSCOP 

IUT

Name:

Version:

Machine Configuration:

Operating System Identification:

IUT Identification:

PICS Reference for IUT:

Limitations of the IUT :

Timers

Item #	Question	Value	Answer	
T1	Enter the value for the timer that is used when no response is expected from the IUT(T_Wait).	ms		
T2	Enter the value for the timer that is long enough to allow  test operator intervention (T_Opr).	s		

General

Item #	Question	Answer(Yes/No)	
G1	Can the IUT, at state 1, be forced to send BGN PDU when requested by test operator?		
G2	Can the IUT, at state 4, be forced to send BGN PDU when requested by test operator?		
G3	Can the IUT, at state 2, be forced to send END PDU when requested by test operator?		
G4	Can the IUT, at state 5, be forced to send END PDU when requested by test operator?		
G5	Can the IUT, at state 10, be forced to send END PDU when requested by test operator?		
G6	Can the IUT, at state 10, be forced to send RS PDU when requested by test operator?		
G7	Can the IUT, at state 10, be forced to send POLL PDU when requested by test operator?		
G8	Can the IUT, at state 10, be forced to send SD PDU when requested by test operator?		

Power Up

Item #	Question	Test Suite parameter name	Answer
(Yes/No)	
PU1	Is Power up implemented?	Power_up_robust		

Annex B Abstract Test Suite

	Abstract Test Suite