doc/UG/DSS1 ETSI Protocol Modules for TTCN-3 Toolset with TITAN, User Guide.adoc - titan/titan.ProtocolModules.DSS1_ETSI - Git at Google

 ---
 Author: Gábor Bettesch
 Version: 198 17-CNL 113 435, Rev. C
 Date: 2012-10-12

 ---
 = DSS1 ETSI Protocol Modules for TTCN-3 Toolset with TITAN, User Guide
 :author: Gábor Bettesch
 :revnumber: 198 17-CNL 113 435, Rev. C
 :revdate: 2012-10-12
 :toc:
 == About This Document

 === How to Read This Document

 This is the User Guide for the DSS1 protocol module. The DSS1 Layer 3 protocol module is developed for the TTCN-3 Toolset with TITAN. This document should be read together with Function Specification <<_3, [3]>>.

 === Presumed Knowledge

 To use this protocol module the knowledge of the TTCN-3 language <<_1, [1]>> is essential.

 DSS1 is specified in the Function Specification <<_4, [4]>> and the Recommendation <<_5, [5]>>. Functional protocol is described in <<_6, [6]>> and in <<_7, [7]>>.

 == System Requirements

 Protocol modules are a set of TTCN-3 source code files that can be used as part of TTCN-3 test suites only. Hence, protocol modules alone do not put specific requirements on the system used. However, in order to compile and execute a TTCN-3 test suite using the set of protocol modules the following system requirements must be satisfied:

 * TITAN TTCN-3 Test Executor R7A (1.7.pl0) or higher installed. For installation guide see <<_2, [2]>>.

 NOTE: This version of the protocol module is not compatible with TITAN releases earlier than R7A.

 = Protocol Modules

 == Overview

 Protocol modules implement the messages structure of the related protocol in a formalized way, using the standard specification language TTCN-3. This allows defining of test data (templates) in the TTCN-3 language <<_1, [1]>> and correctly encoding/decoding messages when executing test suites using the Titan TTCN-3 test environment.

 Protocol modules are using Titan’s RAW encoding attributes <<_2, [2]>> and hence are usable with the Titan test toolset only.

 The implementation of the functional protocol is based on files contained in annex "E" of <<_6, [6]>> and in <<_7, [7]>>

 The table below contains the implemented layer 3 messages and the corresponding TTCN-3 type records.

 [width="100%",cols="35%,15%,50%",options="header",]
 |===============================================================================
 |Message name |Reference |Corresponding type record in __DSS1_Types.ttcn__
 |`ALERTING` |<<_4, [4]>> 3.1.1 |PDU_DSS1_Alerting
 |`CALL PROCEEDING` |<<_4, [4]>> 3.1.2 |PDU_DSS1_CallProceeding
 |`CONGESTION CONTROL` |<<_5, [5]>> 3.1.3 |PDU_DSS1_CongestionControl
 |`CONNECT` |<<_4, [4]>> 3.1.4 |PDU_DSS1_Connect
 |`CONNECT ACKNOWLEDGE` |<<_4, [4]>> 3.1.5 |PDU_DSS1_ConnectAcknowledge
 |`DISCONNECT` |<<_4, [4]>> 3.1.6 |PDU_DSS1_Disconnect
 |`FACILITY` |<<_4, [4]>> 3.1.7 |PDU_DSS1_Facility
 |`HOLD` |<<_4, [4]>> 3.1.8 |PDU_DSS1_Hold
 |`HOLD ACKNOWLEDGE` |<<_4, [4]>> 3.1.9 |PDU_DSS1_HoldAcknowledge
 |`HOLD REJECT` |<<_4, [4]>> 3.1.10 |PDU_DSS1_HoldReject
 |`INFORMATION` |<<_4, [4]>> 3.1.11 |PDU_DSS1_Information
 |`NATIONAL REGISTER` |<<_4, [4]>> 3.1.12 |PDU_DSS1_NationalRegister
 |`NATIONAL REGISTER ACKNOWLEDGE`|<<_4, [4]>> 3.1.13 |PDU_DSS1_NationalRegisterAcknowledge
 |`NOTIFY` |<<_4, [4]>> 3.1.14 |PDU_DSS1_Notify
 |`PROGRESS` |<<_4, [4]>> 3.1.15 |PDU_DSS1_Progress
 |`REGISTER` |<<_4, [4]>> 3.1.16 |PDU_DSS1_Register
 |`RELEASE` |<<_4, [4]>> 3.1.17 |PDU_DSS1_Release
 |`RELEASE COMPLETE` |<<_4, [4]>> 3.1.18 |PDU_DSS1_ReleaseComplete
 |`RESTART` |<<_4, [4]>> 3.1.19 |PDU_DSS1_Restart
 |`RESTART ACKNOWLEDGE` |<<_4, [4]>> 3.1.20 |PDU_DSS1_RestartAcknowledge
 |`RESUME` |<<_4, [4]>> 3.1.21 |PDU_DSS1_Resume
 |`RESUME ACKNOWLEDGE`|<<_4, [4]>> 3.1.22 |PDU_DSS1_ResumeAcknowledge
 |`RESUME REJECT`|<<_4, [4]>> 3.1.23 |PDU_DSS1_ResumeReject
 |`RETRIEVE` |<<_4, [4]>> 3.1.24 |PDU_DSS1_Retrieve
 |`RETRIEVE ACKNOWLEDGE` |<<_4, [4]>> 3.1.25 |PDU_DSS1_RetrieveAcknowledge
 |`RETRIEVE REJECT` |<<_4, [4]>> 3.1.26 |PDU_DSS1_RetrieveReject
 |`SEGMENT` |<<_4, [4]>> 3.1.27 |PDU_DSS1_Segment
 |`SETUP` |<<_4, [4]>> 3.1.28 |PDU_DSS1_Setup
 |`SETUP ACKNOWLEDGE` |<<_4, [4]>> 3.1.29 |PDU_DSS1_SetupAcknowledge
 |`STATUS` |<<_4, [4]>> 3.1.30 |PDU_DSS1_Status
 |`STATUS ENQUIRY` |<<_4, [4]>> 3.1.31 |PDU_DSS1_StatusEnquiry
 |`SUSPEND` |<<_4, [4]>> 3.1.32 |PDU_DSS1_Suspend
 |`SUSPEND ACKNOWLEDGE` |<<_4, [4]>> 3.1.33 |PDU_DSS1_SuspendAcknowledge
 |`SUSPEND REJECT` |<<_4, [4]>> 3.1.34 |PDU_DSS1_SuspendReject
 |`USER INFORMATION` |<<_4, [4]>> 3.1.35 |PDU_DSS1_UserInformation
 |===============================================================================

 == Installation

 The set of protocol modules can be used in developing TTCN-3 test suites using any text editor. However to make the work more efficient a TTCN-3-enabled text editor is recommended (e.g. `nedit`, `xemacs`). Since the DSS1 ETSI protocol is used as a part of a TTCN-3 test suite, this requires TTCN-3 Test Executor be installed before the module can be compiled and executed together with other parts of the test suite. For more details on the installation of TTCN-3 Test Executor see the relevant section of <<_2, [2]>>.

 The files with extension _.asn_, the files __Facility_EncDec.cc__ and __Remote_Operations_Information_Objects.asn__ (CNL 113 369) are not needed unless use of the functional protocol is required. It is required if DSS1 parameters `DSS1_ExtendedFacility` or `DSS1_Facility` are in use and the coding of 'component' element as octetstring is not detailed enough for the test.

 == Configuration

 None.

 = Terminology

 No specific terminology is used.

 = Abbreviations

 DSS1:: Digital Subscriber Signaling System No. 1

 ETSI:: European Telecommunications Standards Institute

 GUI:: Graphical User Interface

 ISDN:: Integrated Services Digital Network

 SEA:: Simulated Environment Architecture

 TTCN-3:: Testing and Test Control Notation version 3

 = References

 [[_1]]
 [1] ETSI ES 201 873-1 v.4.4.1 (2012) +
 The Testing and Test Control Notation version 3. Part 1: Core Language

 [[_2]]
 [2] User Documentation for the TITAN TTCN-3 Test Executor

 [[_3]]
 [3] DSS1 ETSI Protocol Modules for TTCN-3 Toolset with TITAN, Function Specification

 [[_4]]
 [4] DSS1 LAYER 3 PROTOCOL SPECIFICATION, INFORMATION ELEMENTS FOR BOTH BASIC CALL AND SUPPLEMENTARY SERVICE CONTROL, ISDNE

 [[_5]]
 [5] ITU-T Q.931 (03/93) +
 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 (DSS 1) – ISDN USER-NETWORK INTERFACE LAYER 3 SPECIFICATION FOR BASIC CALL CONTROL

 [[_6]]
 [6] ETSI EN 300 196-1 V1.3.2 (2001-06) +
 ISDN: Generic functional protocol for the support of supplementary services

 [[_7]]
 [7] DSS1 LAYER 7 PROTOCOL SPECIFICATION, FACILITY CONTROL OF SUPPLEMENTARY SERVICES (DSS1 L7 PROTOCOL), ISDN-E
	---
	Author: Gábor Bettesch
	Version: 198 17-CNL 113 435, Rev. C
	Date: 2012-10-12

	---
	= DSS1 ETSI Protocol Modules for TTCN-3 Toolset with TITAN, User Guide
	:author: Gábor Bettesch
	:revnumber: 198 17-CNL 113 435, Rev. C
	:revdate: 2012-10-12
	:toc:
	== About This Document

	=== How to Read This Document

	This is the User Guide for the DSS1 protocol module. The DSS1 Layer 3 protocol module is developed for the TTCN-3 Toolset with TITAN. This document should be read together with Function Specification <<_3, [3]>>.

	=== Presumed Knowledge

	To use this protocol module the knowledge of the TTCN-3 language <<_1, [1]>> is essential.

	DSS1 is specified in the Function Specification <<_4, [4]>> and the Recommendation <<_5, [5]>>. Functional protocol is described in <<_6, [6]>> and in <<_7, [7]>>.

	== System Requirements

	Protocol modules are a set of TTCN-3 source code files that can be used as part of TTCN-3 test suites only. Hence, protocol modules alone do not put specific requirements on the system used. However, in order to compile and execute a TTCN-3 test suite using the set of protocol modules the following system requirements must be satisfied:

	* TITAN TTCN-3 Test Executor R7A (1.7.pl0) or higher installed. For installation guide see <<_2, [2]>>.

	NOTE: This version of the protocol module is not compatible with TITAN releases earlier than R7A.

	= Protocol Modules

	== Overview

	Protocol modules implement the messages structure of the related protocol in a formalized way, using the standard specification language TTCN-3. This allows defining of test data (templates) in the TTCN-3 language <<_1, [1]>> and correctly encoding/decoding messages when executing test suites using the Titan TTCN-3 test environment.

	Protocol modules are using Titan’s RAW encoding attributes <<_2, [2]>> and hence are usable with the Titan test toolset only.

	The implementation of the functional protocol is based on files contained in annex "E" of <<_6, [6]>> and in <<_7, [7]>>

	The table below contains the implemented layer 3 messages and the corresponding TTCN-3 type records.

	[width="100%",cols="35%,15%,50%",options="header",]
	\|===============================================================================
	\|Message name \|Reference \|Corresponding type record in __DSS1_Types.ttcn__
	\|`ALERTING` \|<<_4, [4]>> 3.1.1 \|PDU_DSS1_Alerting
	\|`CALL PROCEEDING` \|<<_4, [4]>> 3.1.2 \|PDU_DSS1_CallProceeding
	\|`CONGESTION CONTROL` \|<<_5, [5]>> 3.1.3 \|PDU_DSS1_CongestionControl
	\|`CONNECT` \|<<_4, [4]>> 3.1.4 \|PDU_DSS1_Connect
	\|`CONNECT ACKNOWLEDGE` \|<<_4, [4]>> 3.1.5 \|PDU_DSS1_ConnectAcknowledge
	\|`DISCONNECT` \|<<_4, [4]>> 3.1.6 \|PDU_DSS1_Disconnect
	\|`FACILITY` \|<<_4, [4]>> 3.1.7 \|PDU_DSS1_Facility
	\|`HOLD` \|<<_4, [4]>> 3.1.8 \|PDU_DSS1_Hold
	\|`HOLD ACKNOWLEDGE` \|<<_4, [4]>> 3.1.9 \|PDU_DSS1_HoldAcknowledge
	\|`HOLD REJECT` \|<<_4, [4]>> 3.1.10 \|PDU_DSS1_HoldReject
	\|`INFORMATION` \|<<_4, [4]>> 3.1.11 \|PDU_DSS1_Information
	\|`NATIONAL REGISTER` \|<<_4, [4]>> 3.1.12 \|PDU_DSS1_NationalRegister
	\|`NATIONAL REGISTER ACKNOWLEDGE`\|<<_4, [4]>> 3.1.13 \|PDU_DSS1_NationalRegisterAcknowledge
	\|`NOTIFY` \|<<_4, [4]>> 3.1.14 \|PDU_DSS1_Notify
	\|`PROGRESS` \|<<_4, [4]>> 3.1.15 \|PDU_DSS1_Progress
	\|`REGISTER` \|<<_4, [4]>> 3.1.16 \|PDU_DSS1_Register
	\|`RELEASE` \|<<_4, [4]>> 3.1.17 \|PDU_DSS1_Release
	\|`RELEASE COMPLETE` \|<<_4, [4]>> 3.1.18 \|PDU_DSS1_ReleaseComplete
	\|`RESTART` \|<<_4, [4]>> 3.1.19 \|PDU_DSS1_Restart
	\|`RESTART ACKNOWLEDGE` \|<<_4, [4]>> 3.1.20 \|PDU_DSS1_RestartAcknowledge
	\|`RESUME` \|<<_4, [4]>> 3.1.21 \|PDU_DSS1_Resume
	\|`RESUME ACKNOWLEDGE`\|<<_4, [4]>> 3.1.22 \|PDU_DSS1_ResumeAcknowledge
	\|`RESUME REJECT`\|<<_4, [4]>> 3.1.23 \|PDU_DSS1_ResumeReject
	\|`RETRIEVE` \|<<_4, [4]>> 3.1.24 \|PDU_DSS1_Retrieve
	\|`RETRIEVE ACKNOWLEDGE` \|<<_4, [4]>> 3.1.25 \|PDU_DSS1_RetrieveAcknowledge
	\|`RETRIEVE REJECT` \|<<_4, [4]>> 3.1.26 \|PDU_DSS1_RetrieveReject
	\|`SEGMENT` \|<<_4, [4]>> 3.1.27 \|PDU_DSS1_Segment
	\|`SETUP` \|<<_4, [4]>> 3.1.28 \|PDU_DSS1_Setup
	\|`SETUP ACKNOWLEDGE` \|<<_4, [4]>> 3.1.29 \|PDU_DSS1_SetupAcknowledge
	\|`STATUS` \|<<_4, [4]>> 3.1.30 \|PDU_DSS1_Status
	\|`STATUS ENQUIRY` \|<<_4, [4]>> 3.1.31 \|PDU_DSS1_StatusEnquiry
	\|`SUSPEND` \|<<_4, [4]>> 3.1.32 \|PDU_DSS1_Suspend
	\|`SUSPEND ACKNOWLEDGE` \|<<_4, [4]>> 3.1.33 \|PDU_DSS1_SuspendAcknowledge
	\|`SUSPEND REJECT` \|<<_4, [4]>> 3.1.34 \|PDU_DSS1_SuspendReject
	\|`USER INFORMATION` \|<<_4, [4]>> 3.1.35 \|PDU_DSS1_UserInformation
	\|===============================================================================

	== Installation

	The set of protocol modules can be used in developing TTCN-3 test suites using any text editor. However to make the work more efficient a TTCN-3-enabled text editor is recommended (e.g. `nedit`, `xemacs`). Since the DSS1 ETSI protocol is used as a part of a TTCN-3 test suite, this requires TTCN-3 Test Executor be installed before the module can be compiled and executed together with other parts of the test suite. For more details on the installation of TTCN-3 Test Executor see the relevant section of <<_2, [2]>>.

	The files with extension _.asn_, the files __Facility_EncDec.cc__ and __Remote_Operations_Information_Objects.asn__ (CNL 113 369) are not needed unless use of the functional protocol is required. It is required if DSS1 parameters `DSS1_ExtendedFacility` or `DSS1_Facility` are in use and the coding of 'component' element as octetstring is not detailed enough for the test.

	== Configuration

	None.

	= Terminology

	No specific terminology is used.

	= Abbreviations

	DSS1:: Digital Subscriber Signaling System No. 1

	ETSI:: European Telecommunications Standards Institute

	GUI:: Graphical User Interface

	ISDN:: Integrated Services Digital Network

	SEA:: Simulated Environment Architecture

	TTCN-3:: Testing and Test Control Notation version 3

	= References

	[[_1]]
	[1] ETSI ES 201 873-1 v.4.4.1 (2012) +
	The Testing and Test Control Notation version 3. Part 1: Core Language

	[[_2]]
	[2] User Documentation for the TITAN TTCN-3 Test Executor

	[[_3]]
	[3] DSS1 ETSI Protocol Modules for TTCN-3 Toolset with TITAN, Function Specification

	[[_4]]
	[4] DSS1 LAYER 3 PROTOCOL SPECIFICATION, INFORMATION ELEMENTS FOR BOTH BASIC CALL AND SUPPLEMENTARY SERVICE CONTROL, ISDNE

	[[_5]]
	[5] ITU-T Q.931 (03/93) +
	DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 (DSS 1) – ISDN USER-NETWORK INTERFACE LAYER 3 SPECIFICATION FOR BASIC CALL CONTROL

	[[_6]]
	[6] ETSI EN 300 196-1 V1.3.2 (2001-06) +
	ISDN: Generic functional protocol for the support of supplementary services

	[[_7]]
	[7] DSS1 LAYER 7 PROTOCOL SPECIFICATION, FACILITY CONTROL OF SUPPLEMENTARY SERVICES (DSS1 L7 PROTOCOL), ISDN-E