SIST ETS 300 098-4:1998

Integrated Services Digital Network (ISDN); Connected Line Identification Restriction (COLR) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user

Conformance Test Specification for the DSS1 protocol for the Connected line identification restriction (COLR) Supplementary service - including PIXIT proforma

Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: omejitev identifikacije (razpoznavanja) priključka v zvezi (COLR) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 4. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) - Proforma specifikacije za uporabnika

General Information

• Status: Published
• Publication Date: 31-May-1998
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• Technical Committee: SPS - Signalling protocols and switching
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jun-1998
• Due Date: 01-Jun-1998
• Completion Date: 01-Jun-1998
• Ref Project: ETSI ETS 300 098-4 ed.1 (1997-05) - Integrated Services Digital Network (ISDN); Connected Line Identification Restriction (COLR) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Connected Line Identification Restriction (COLR) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the user33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 098-4 Edition 13SIST ETS 300 098-4:1998en01-MDQXDU-19983SIST ETS 300 098-4:1998SLOVENSKI
STANDARD



SIST ETS 300 098-4:1998



EUROPEANETS 300 098-4TELECOMMUNICATIONMay 1997STANDARDSource: ETSI TC-SPSReference: DE/SPS-05061-M-4ICS:33.020Key words:ISDN, DSS1, supplementary service, COLR, testing, ATS, PIXIT, userIntegrated Services Digital Network (ISDN);Connected Line Identification Restriction (COLR)supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 4: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proformaspecification for the userETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail].: [phone] - Fax: [phone]Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1997. All rights reserved.SIST ETS 300 098-4:1998



Page 2ETS 300 098-4: May 1997Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 098-4:1998



Page 3ETS 300 098-4: May 1997ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.84Abstract Test Method (ATM).95Untestable test purposes.96ATS conventions.96.1Declarations part.96.1.1Type definitions.96.1.1.1Simple type definitions.96.1.1.2Structured type definitions.106.1.1.2.1TTCN structured type definitions.106.1.1.2.2ASN.1 structured type definitions.106.1.1.3ASP type definitions.106.1.1.3.1TTCN ASP type definitions.106.1.1.3.2ASN.1 ASP type definitions.116.1.1.4PDU type definitions.116.1.1.4.1TTCN PDU type definitions.116.1.1.4.2ASN.1 PDU type definitions.116.1.2Test suite constants.116.1.3Test suite parameters.116.1.4Variables.116.1.4.1Test suite variables.116.1.4.2Test case variables.116.1.5Test suite operation definitions.116.1.6Alias definitions.116.2Constraints part.126.2.1Structured type constraint declaration.126.2.2ASN.1 type constraint declaration.126.2.3ASP type constraint declaration.126.2.3.1ASN.1 ASP type constraint declaration.126.2.3.2TTCN ASP type constraint declaration.126.2.4PDU type constraint declaration.126.2.4.1ASN.1 PDU type constraint declaration.126.2.4.2TTCN PDU type constraint declaration.126.2.5Chaining of constraints.126.2.5.1Static chaining.126.2.5.2Dynamic chaining.126.2.6Derived constraints.136.2.7Parameterized constraints.136.2.8Value assignment.136.2.8.1Specific values.136.2.8.2Matching values.136.3Dynamic part.136.3.1Test cases.136.3.2Test steps.136.3.3Defaults.137ATS to TP map.13SIST ETS 300 098-4:1998



Page 4ETS 300 098-4: May 19978PCTR conformance.149PIXIT conformance.1410ATS conformance.14Annex A (normative):Protocol Conformance Test Report (PCTR) proforma.15A.1Identification summary.15A.1.1Protocol conformance test report.15A.1.2IUT identification.15A.1.3Testing environment.15A.1.4Limits and reservations.16A.1.5Comments.16A.2IUT conformance status.16A.3Static conformance summary.16A.4Dynamic conformance summary.16A.5Static conformance review report.17A.6Test campaign report.17A.7Observations.17Annex B (normative):Partial PIXIT proforma.18B.1Identification summary.18B.2Abstract test suite summary.18B.3Test laboratory.18B.4Client (of the test laboratory).19B.5System Under Test (SUT).19B.6Protocol information.20B.6.1Protocol identification.20B.6.2IUT information.20B.6.2.1Parameters.20B.6.2.2Parameter values.20B.6.2.3Sending of messages by IUT.20Annex C (normative):Abstract Test Suite (ATS).21C.1The TTCN Graphical form (TTCN.GR).21C.1.1ATS for basic access.21C.1.2ATS for primary rate access.21C.2The TTCN Machine Processable form (TTCN.MP).21C.2.1ATS for basic access.21C.2.2ATS for primary rate access.21Annex D (informative):General structure of ATS.22History.23SIST ETS 300 098-4:1998



Page 5ETS 300 098-4: May 1997ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS is part 4 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Connected LineIdentification Restriction (COLR) supplementary service, as described below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for the user";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification for the user";Part 5:"TSS&TP specification for the network";Part 6:"ATS and partial PIXIT proforma specification for the network".Transposition datesDate of adoption:23 May 1997Date of latest announcement of this ETS (doa):31 August 1997Date of latest publication of new National Standardor endorsement of this ETS (dop/e):28 February 1998Date of withdrawal of any conflicting National Standard (dow):28 February 1998SIST ETS 300 098-4:1998



Page 6ETS 300 098-4: May 1997Blank pageSIST ETS 300 098-4:1998



Page 7ETS 300 098-4: May 19971ScopeThis fourth part of ETS 300 098 specifies the Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proforma for the User side of the T reference pointor coincident S and T reference point (as defined in ITU-T Recommendation I.411 [10]) ofimplementations conforming to the stage three standard for the Connected Line Identification Restriction(COLR) supplementary service for the pan-European Integrated Services Digital Network (ISDN) bymeans of the Digital Subscriber Signalling System No. one (DSS1) protocol, ETS 300 098-1 [2].ETS 300 098-3 [4] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATSand partial PIXIT proforma specification. Other parts specify the TSS&TP and the ATS and partial PIXITproforma for the Network side of the T reference point or coincident S and T reference point ofimplementations conforming to ETS 300 098-1 [2].2Normative referencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-networkinterface layer 3; Specifications for basic call control".[2]ETS 300 098-1 (1992): "Integrated Services Digital Network (ISDN); ConnectedLine Identification Restriction (COLR) supplementary service; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 1: Protocol specification".[3]ETS 300 098-2 (1995): "Integrated Services Digital Network (ISDN); ConnectedLine Identification Restriction (COLR) supplementary service; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 2: Protocol ImplementationConformance Statement (PICS) proforma specification".[4]ETS 300 098-3: "Integrated Services Digital Network (ISDN); Connected LineIdentification Restriction (COLR) supplementary service; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 3: Test Suite Structure andTest Purposes (TSS&TP) specification for the user".[5]ISO/IEC 9646-1: "Information technology - OSI Conformance TestingMethodology and Framework; Part 1: General Concepts".[6]ISO/IEC 9646-2: "Information technology - OSI Conformance TestingMethodology and Framework; Part 2: Abstract Test Suite Specification".[7]ISO/IEC 9646-3: "Information technology - OSI Conformance TestingMethodology and Framework; Part 3: The Tree and Tabular CombinedNotation".[8]ISO/IEC 9646-4: "Information technology - OSI Conformance TestingMethodology and Framework; Part 4: Test realization".[9]ISO/IEC 9646-5: "Information technology - OSI Conformance TestingMethodology and Framework; Part 5: Requirements on test laboratories andclients for the conformance assessment process".[10]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -Reference configurations".SIST ETS 300 098-4:1998



Page 8ETS 300 098-4: May 19973Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply:Abstract Test Suite (ATS): See ISO/IEC 9646-1 [5].Implementation Under Test (IUT): See ISO/IEC 9646-1 [5].Lower Tester (LT): See ISO/IEC 9646-1 [5].Point Of Control And Observation (PCO): See ISO/IEC 9646-1 [5].Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [5].PICS proforma: See ISO/IEC 9646-1 [5].Protocol Implementation Extra Information For Testing (PIXIT): See ISO/IEC 9646-1 [5].PIXIT proforma: See ISO/IEC 9646-1 [5].System Under Test (SUT): See ISO/IEC 9646-1 [5].Upper Tester (UT): See ISO/IEC 9646-1 [5].3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteBERBasic Encoding RulesCOLRConnected Line Identification RestrictionExTSExecutable Test SuiteIUTImplementation Under TestLTLower TesterMOTMeans Of TestingPCOPoint of Control and ObservationPCTRProtocol Conformance Test ReportPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingSUTSystem Under TestTCPTest Co-ordination ProceduresTPTest PurposeTTCNTree and Tabular Combined NotationUTUpper TesterSIST ETS 300 098-4:1998



Page 9ETS 300 098-4: May 19974Abstract Test Method (ATM)The remote test method is applied for the COLR user ATS. The Point of Control and Observation (PCO)resides at the service access point between layers 2 and 3. This PCO is named "L" (for Lower). TheL PCO is used to control and observe the behaviour of the Implementation Under Test (IUT) and test caseverdicts are assigned depending on the behaviour observed at this PCO.TesterSUTLTIUTPCOLayer 2Layer 2Layer 1Layer 1Service providerFigure 1: Remote test methodISO/IEC 9646-2 [6] allows the informal expression of Test Co-ordination Procedures (TCP) between theSystem Under Test (SUT) upper layer(s) and the Lower Tester (LT). In the ATS contained in annex C,TCP is achieved by use of a second "informal" PCO, called "O" (for Operator). This PCO is used tospecify control but not observation above the IUT and consequently, events at this PCO are never used togenerate test case verdicts. The use of this O PCO is regarded as a preferred alternative to the use of theimplicit send event, in that it allows the ATS to specify in a clear and meaningful way what actions arerequired to be performed on the IUT.5Untestable test purposesThere are no untestable test purposes associated with this ATS.6ATS conventionsThis clause is structured similarly to the structure of a TTCN ATS. However, the names of the subclausesare arranged in a way more suitable to this ETS.6.1Declarations part6.1.1Type definitions6.1.1.1Simple type definitionsWhere appropriate, simple types have a length, a value list or a range restriction attached.Simple types defined as being of some string type (e.g. BIT STRING, OCTET STRING), have a lengthrestriction or a value list attached.Simple types, defined as being of INTEGER type, have a value list or a range restriction attached.SIST ETS 300 098-4:1998



Page 10ETS 300 098-4: May 19976.1.1.2Structured type definitions6.1.1.2.1TTCN structured type definitionsAll structured type definitions are provided with a full name.All elements in every structured type definition, defined as being of some string type (e.g. BIT STRING,OCTET STRING), have a length restriction attached.If an element in a structured type definition is defined as being of a referenced type, the (possible)restriction is defined in that referenced type.For information elements the identifier, which is unique for each element, has its type defined as a simpletype where the value list is restricted to the single value which is the identifier itself. This has theadvantage that it allows a test system derived from this ATS to easily identify information elementsembedded in messages. An ATS where information element identifiers are represented as unrestrictedtypes can present difficulties for a derived test system in the case where it needs to find one informationelement embedded in a number of others and the constraints for the other elements have the any-or-omitvalue. In such a case the test system cannot easily find the beginning of each information element.6.1.1.2.2ASN.1 structured type definitionsThere are no ASN.1 structured type definitions in the ATS.6.1.1.3ASP type definitions6.1.1.3.1TTCN ASP type definitionsTTCN ASP type definitions only contain one PDU or no PDU at all. The relationship between an ASP typeand a PDU type is one-to-one. That is, there exists one ASP type definition for each PDU type definition (ifthat ASP type contains a PDU).All TTCN ASP type definitions are provided with a full identifier.Some ASPs are not parameterized as shown in the example in table 1. Such ASPs are only used forrequesting or receiving service from the lower layer.Table 1: TTCN ASP type definition DL_REL_INTTCN ASP Type DefinitionASP NAME : DL_REL_IN
(DL_RELEASE_INDICATION)PCO Type : SAPComments :Parameter Name
|
Parameter Type
|
CommentsDetailed Comments :Table 2 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU andno other parameters.Table 2: TTCN ASP type definition DL_DATA_RQTTCN ASP Type DefinitionASP NAME : DL_DATA_RQ
(DL_DATA_Request)PCO Type : SAPComments : CEId: = (SAPI,CES) mapped onto
DLCI: = (SAPI,TEI)
ASP is used to request the transmission of layer 3 PDUsParameter Name
|
Parameter Type
|
Commentsmun (MessageUnit)
|PDU
|Detailed Comments :SIST ETS 300 098-4:1998



Page 11ETS 300 098-4: May 19976.1.1.3.2ASN.1 ASP type definitionsThere are no ASN.1 ASP type definitions in the ATS.6.1.1.4PDU type definitions6.1.1.4.1TTCN PDU type definitionsThe TTCN PDU type reflects the actual data being transferred or received. All PDUs are embedded inASPs.If a specific PDU type definition contains elements defined in terms of a pre-defined type, that element hasa restriction attached to it.6.1.1.4.2ASN.1 PDU type definitionsThere are no ASN.1 PDU type definitions in the ATS.6.1.2Test suite constantsNo test suite constants are used or defined in this ATS.6.1.3Test suite parametersEach test suite parameter is defined in terms of a predefined type or a referenced type. A referenced typeis used when it is necessary to attach restrictions to these type definitions (it is not allowed to includerestrictions directly in the test suite parameter table). The referenced type can have a length or valuerestriction attached to it in its declaration table.6.1.4Variables6.1.4.1Test suite variablesNo test suite variables are used or defined in this ATS.6.1.4.2Test case variablesEach test case variable is defined in terms of a predefined type or a referenced type. A referenced type isused when it is necessary to attach restrictions to these type definitions (it is not allowed to includerestrictions directly in the test case variable table). The referenced type can have a length or valuerestriction attached to it in its declaration table.Where test case variables are used in constraints, they are passed as formal parameters.6.1.5Test suite operation definitionsNo test suite operations are used or defined in this ATS.6.1.6Alias definitionsAlias definitions are used to highlight the exchange of PDUs embedded in ASPs.EXAMPLE:Alias "SETUP" is expanded with "DL_DATA_RQ" to send a SETUP PDUconstraint by ASP constraint Ms(SUnn(Par,Par)).SIST ETS 300 098-4:1998



Page 12ETS 300 098-4: May 19976.2Constraints part6.2.1Structured type constraint declarationFor every structured type definition there exists one or more structured type constraint.6.2.2ASN.1 type constraint declarationNo ASN.1 type constraint declaration exists in this ATS.6.2.3ASP type constraint declaration6.2.3.1ASN.1 ASP type constraint declarationNo ASN.1 ASP type constraint declaration exists in this ATS.6.2.3.2TTCN ASP type constraint declarationFor TTCN ASP constraint declarations there is a one-to-one relationship between its type and theconstraint. That is, there is only one constraint for each TTCN ASP type declaration. The reason for this isthat the ASPs are used only for carrying PDU values.6.2.4PDU type constraint declaration6.2.4.1ASN.1 PDU type constraint declarationNo ASN.1 PDU type constraint declaration exists in this ATS.6.2.4.2TTCN PDU type constraint declarationPDU constraints are used for assigning values or patterns to the data being sent or received.6.2.5Chaining of constraints6.2.5.1Static chainingStatic chaining, that is a fixed reference to a specific constraint, is used in this ATS. The static chaining isused for static binding of both variables and sub-structures.6.2.5.2Dynamic chainingDynamic chaining is achieved when having a reference to a value which is unknown. The only thingknown (before run-time) is the type of that reference. The reference is passed as a parameter. Strictdynamic chaining is not used in this ATS. What is used is something that is called "semi-dynamicchaining". The definition of semi-dynamic chaining is that the fixed reference is parameterized with anunknown value. That value is received as a parameter.Table 3: TTCN ASP constraint declaration MsTTCN ASP Constraint DeclarationConstraint Name : Ms(PARAM: PDU)ASP Type
: DL_DATA_RQDerivation Path :Comments
:
Parameter Name
|
Parameter Value
|
Commentsmun
|PARAM
|Detailed comments :Table 3 is an example of semi-dynamic chaining. The TTCN ASP constraint is parameterized withmetatype PDU value named PARAM. That value is passed further down in the structure as a value to themessage unit.SIST ETS 300 098-4:1998



Page 13ETS 300 098-4: May 19976.2.6Derived constraintsNo derivation of any constraints is used. All constraints are considered to be base constraints.6.2.7Parameterized constraintsParameterized constraints are used in this ATS.6.2.8Value assignment6.2.8.1Specific valuesFor specific value assignment both explicit values and references to explicit values are used.6.2.8.2Matching valuesAs matching values the following mechanisms are used:Instead of Value:AnyOrOmit"*"AnyValue"?"Omit"-"Inside value:AnyOne"?"AnyOrNone"*"6.3Dynamic part6.3.1Test casesEach test case contains the test purpose text from ETS 300 098-3 [4]. To be able to read and understandthe test case dynamic behaviour it is recommended that the test steps are understood first.6.3.2Test stepsMuch use has been made of test steps to avoid needless repetition of dynamic behaviour. Many test stepsare based on those used for the ISDN basic call ATS.6.3.3DefaultsThe RETURN statement which is defined in DAM1 of ISO 9646-3 [7] is not used. This statement allowsvalid background behaviour to be handled in the default tree with a possibility to return to the original set ofalternatives in the test case.7ATS to TP mapThe identifiers used for the TPs are reused as test case names. Thus there is a straightforward one-to-one mapping.SIST ETS 300 098-4:1998



Page 14ETS 300 098-4: May 19978PCTR conformanceA test laboratory, when requested by a client to produce a PCTR, is required, as specified inISO/IEC 9646-5 [9], to produce a PCTR conformant with the PCTR template given in annex B ofISO/IEC 9646-5 [9].Furthermore, a test laboratory, offering testing for the ATS specification contained in annex C, whenrequested by a client to produce a PCTR, is required to produce a PCTR conformant with the PCTRproforma contained in annex A of this ETS.A PCTR which conforms to this PCTR proforma specification shall preserve the content and ordering ofthe 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 testlaboratory.9PIXIT conformanceA test realizer, producing an executable test suite for the ATS specification contained in annex C, isrequired, as specified in ISO/IEC 9646-4 [8], to produce an augmented partial PIXIT proforma conformantwith this partial PIXIT proforma specification.An augmented partial PIXIT proforma which conforms to this partial PIXIT proforma specification shall, asa minimum, have contents which are technically equivalent to annex B. The augmented partial PIXITproforma may contain additional questions that need to be answered in order to prepare the Means OfTesting (MOT) for a particular IUT.A test laboratory, offering testing for the ATS specification contained in annex C, is required, as specifiedin ISO/IEC 9646-5 [9], to further augment the augmented partial PIXIT proforma to produce a PIXITproforma conformant with this partial PIXIT proforma specification.A PIXIT proforma which conforms to this partial PIXIT proforma specification shall, as a minimum, havecontents which are technically equivalent to annex B. The PIXIT proforma may contain additionalquestions that need to be answered in ord
...

SLOVENSKI STANDARD
SIST ETS 300 098-4:1998
01-junij-1998
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'RSROQLOQDVWRULWHYRPHMLWHY
LGHQWLILNDFLMHUD]SR]QDYDQMDSULNOMXþNDY]YH]L&2/53URWRNROGLJLWDOQH
QDURþQLãNHVLJQDOL]DFLMHãW'66GHO$EVWUDNWQLSUHVNXãDOQLQL]$76LQ
GHOQDGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHL]YHGEHSURWRNROD3,;,73URIRUPD
VSHFLILNDFLMH]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Connected Line Identification Restriction
(COLR) supplementary service; Digital Subscriber Signalling System No. one (DSS1)
protocol; Part 4: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra
Information for Testing (PIXIT) proforma specification for the user
Ta slovenski standard je istoveten z: ETS 300 098-4 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 098-4:1998 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 098-4:1998

---------------------- Page: 2 ----------------------

SIST ETS 300 098-4:1998
EUROPEAN ETS 300 098-4
TELECOMMUNICATION May 1997
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05061-M-4
ICS: 33.020
Key words: ISDN, DSS1, supplementary service, COLR, testing, ATS, PIXIT, user
Integrated Services Digital Network (ISDN);
Connected Line Identification Restriction (COLR)
supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 4: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma
specification for the user
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail]
Tel.: [phone] - Fax: [phone]
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 1997. All rights reserved.

---------------------- Page: 3 ----------------------

SIST ETS 300 098-4:1998
Page 2
ETS 300 098-4: May 1997
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 098-4:1998
Page 3
ETS 300 098-4: May 1997
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .8
3.1 Definitions .8
3.2 Abbreviations .8
4 Abstract Test Method (ATM).9
5 Untestable test purposes.9
6 ATS conventions .9
6.1 Declarations part.9
6.1.1 Type definitions .9
6.1.1.1 Simple type definitions.9
6.1.1.2 Structured type definitions .10
6.1.1.2.1 TTCN structured type definitions .10
6.1.1.2.2 ASN.1 structured type definitions.10
6.1.1.3 ASP type definitions.10
6.1.1.3.1 TTCN ASP type definitions .10
6.1.1.3.2 ASN.1 ASP type definitions .11
6.1.1.4 PDU type definitions .11
6.1.1.4.1 TTCN PDU type definitions.11
6.1.1.4.2 ASN.1 PDU type definitions .11
6.1.2 Test suite constants .11
6.1.3 Test suite parameters .11
6.1.4 Variables .11
6.1.4.1 Test suite variables.11
6.1.4.2 Test case variables.11
6.1.5 Test suite operation definitions.11
6.1.6 Alias definitions .11
6.2 Constraints part.12
6.2.1 Structured type constraint declaration.12
6.2.2 ASN.1 type constraint declaration .12
6.2.3 ASP type constraint declaration .12
6.2.3.1 ASN.1 ASP type constraint declaration .12
6.2.3.2 TTCN ASP type constraint declaration.12
6.2.4 PDU type constraint declaration.12
6.2.4.1 ASN.1 PDU type constraint declaration.12
6.2.4.2 TTCN PDU type constraint declaration .12
6.2.5 Chaining of constraints.12
6.2.5.1 Static chaining .12
6.2.5.2 Dynamic chaining .12
6.2.6 Derived constraints.13
6.2.7 Parameterized constraints.13
6.2.8 Value assignment.13
6.2.8.1 Specific values.13
6.2.8.2 Matching values.13
6.3 Dynamic part.13
6.3.1 Test cases.13
6.3.2 Test steps.13
6.3.3 Defaults .13
7 ATS to TP map.13

---------------------- Page: 5 ----------------------

SIST ETS 300 098-4:1998
Page 4
ETS 300 098-4: May 1997
8 PCTR conformance. 14
9 PIXIT conformance. 14
10 ATS conformance. 14
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma . 15
A.1 Identification summary. 15
A.1.1 Protocol conformance test report. 15
A.1.2 IUT identification. 15
A.1.3 Testing environment. 15
A.1.4 Limits and reservations . 16
A.1.5 Comments. 16
A.2 IUT conformance status . 16
A.3 Static conformance summary. 16
A.4 Dynamic conformance summary. 16
A.5 Static conformance review report . 17
A.6 Test campaign report. 17
A.7 Observations. 17
Annex B (normative): Partial PIXIT proforma . 18
B.1 Identification summary. 18
B.2 Abstract test suite summary . 18
B.3 Test laboratory. 18
B.4 Client (of the test laboratory) . 19
B.5 System Under Test (SUT) . 19
B.6 Protocol information. 20
B.6.1 Protocol identification . 20
B.6.2 IUT information. 20
B.6.2.1 Parameters . 20
B.6.2.2 Parameter values. 20
B.6.2.3 Sending of messages by IUT. 20
Annex C (normative): Abstract Test Suite (ATS). 21
C.1 The TTCN Graphical form (TTCN.GR) .21
C.1.1 ATS for basic access . 21
C.1.2 ATS for primary rate access. 21
C.2 The TTCN Machine Processable form (TTCN.MP) . 21
C.2.1 ATS for basic access . 21
C.2.2 ATS for primary rate access. 21
Annex D (informative): General structure of ATS. 22
History. 23

---------------------- Page: 6 ----------------------

SIST ETS 300 098-4:1998
Page 5
ETS 300 098-4: May 1997
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols and
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS is part 4 of a multi-part standard covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Connected Line
Identification Restriction (COLR) supplementary service, as described below:
Part 1: "Protocol specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification for the user";
Part 4: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for
Testing (PIXIT) proforma specification for the user";
Part 5: "TSS&TP specification for the network";
Part 6: "ATS and partial PIXIT proforma specification for the network".
Transposition dates
Date of adoption: 23 May 1997
Date of latest announcement of this ETS (doa): 31 August 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 28 February 1998
Date of withdrawal of any conflicting National Standard (dow): 28 February 1998

---------------------- Page: 7 ----------------------

SIST ETS 300 098-4:1998
Page 6
ETS 300 098-4: May 1997
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 098-4:1998
Page 7
ETS 300 098-4: May 1997
1 Scope
This fourth part of ETS 300 098 specifies the Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma for the User side of the T reference point
or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [10]) of
implementations conforming to the stage three standard for the Connected Line Identification Restriction
(COLR) supplementary service for the pan-European Integrated Services Digital Network (ISDN) by
means of the Digital Subscriber Signalling System No. one (DSS1) protocol, ETS 300 098-1 [2].
ETS 300 098-3 [4] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS
and partial PIXIT proforma specification. Other parts specify the TSS&TP and the ATS and partial PIXIT
proforma for the Network side of the T reference point or coincident S and T reference point of
implementations conforming to ETS 300 098-1 [2].
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network
interface layer 3; Specifications for basic call control".
[2] ETS 300 098-1 (1992): "Integrated Services Digital Network (ISDN); Connected
Line Identification Restriction (COLR) supplementary service; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 1: Protocol specification".
[3] ETS 300 098-2 (1995): "Integrated Services Digital Network (ISDN); Connected
Line Identification Restriction (COLR) supplementary service; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 2: Protocol Implementation
Conformance Statement (PICS) proforma specification".
[4] ETS 300 098-3: "Integrated Services Digital Network (ISDN); Connected Line
Identification Restriction (COLR) supplementary service; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and
Test Purposes (TSS&TP) specification for the user".
[5] ISO/IEC 9646-1: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 1: General Concepts".
[6] ISO/IEC 9646-2: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 2: Abstract Test Suite Specification".
[7] ISO/IEC 9646-3: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 3: The Tree and Tabular Combined
Notation".
[8] ISO/IEC 9646-4: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 4: Test realization".
[9] ISO/IEC 9646-5: "Information technology - OSI Conformance Testing
Methodology and Framework; Part 5: Requirements on test laboratories and
clients for the conformance assessment process".
[10] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -
Reference configurations".

---------------------- Page: 9 ----------------------

SIST ETS 300 098-4:1998
Page 8
ETS 300 098-4: May 1997
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [5].
Implementation Under Test (IUT): See ISO/IEC 9646-1 [5].
Lower Tester (LT): See ISO/IEC 9646-1 [5].
Point Of Control And Observation (PCO): See ISO/IEC 9646-1 [5].
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [5].
PICS proforma: See ISO/IEC 9646-1 [5].
Protocol Implementation Extra Information For Testing (PIXIT): See ISO/IEC 9646-1 [5].
PIXIT proforma: See ISO/IEC 9646-1 [5].
System Under Test (SUT): See ISO/IEC 9646-1 [5].
Upper Tester (UT): See ISO/IEC 9646-1 [5].
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BER Basic Encoding Rules
COLR Connected Line Identification Restriction
ExTS Executable Test Suite
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
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
SUT System Under Test
TCP Test Co-ordination Procedures
TP Test Purpose
TTCN Tree and Tabular Combined Notation
UT Upper Tester

---------------------- Page: 10 ----------------------

SIST ETS 300 098-4:1998
Page 9
ETS 300 098-4: May 1997
4 Abstract Test Method (ATM)
The remote test method is applied for the COLR user ATS. The Point of Control and Observation (PCO)
resides at the service access point between layers 2 and 3. This PCO is named "L" (for Lower). The
L 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.
Tester SUT
LT IUT
PCO
Layer 2 Layer 2
Layer 1 Layer 1
Service provider
Figure 1: Remote test method
ISO/IEC 9646-2 [6] allows the informal expression of Test Co-ordination Procedures (TCP) between the
System Under Test (SUT) upper layer(s) and the Lower Tester (LT). In the ATS contained in annex C,
TCP is achieved by use of a second "informal" PCO, called "O" (for Operator). This PCO is used to
specify control but not observation above the IUT and consequently, events at this PCO are never used to
generate test case verdicts. The use of this O PCO is regarded as a preferred alternative to the use of the
implicit send event, in that it allows the ATS to specify in a clear and meaningful way what actions are
required to be performed on the IUT.
5 Untestable test purposes
There are no untestable test purposes associated with this ATS.
6 ATS conventions
This clause is structured similarly to the structure of a TTCN ATS. However, the names of the subclauses
are arranged in a way more suitable to this ETS.
6.1 Declarations part
6.1.1 Type definitions
6.1.1.1 Simple type definitions
Where appropriate, simple types have a length, a value list or a range restriction attached.
Simple types defined as being of some string type (e.g. BIT STRING, OCTET STRING), have a length
restriction or a value list attached.
Simple types, defined as being of INTEGER type, have a value list or a range restriction attached.

---------------------- Page: 11 ----------------------

SIST ETS 300 098-4:1998
Page 10
ETS 300 098-4: May 1997
6.1.1.2 Structured type definitions
6.1.1.2.1 TTCN structured type definitions
All structured type definitions are provided with a full name.
All elements in every structured type definition, defined as being of some string type (e.g. BIT STRING,
OCTET STRING), have a length restriction attached.
If an element in a structured type definition is defined as being of a referenced type, the (possible)
restriction is defined in that referenced type.
For information elements the identifier, which is unique for each element, has its type defined as a simple
type where the value list is restricted to the single value which is the identifier itself. This has the
advantage that it allows a test system derived from this ATS to easily identify information elements
embedded in messages. An ATS where information element identifiers are represented as unrestricted
types can present difficulties for a derived test system in the case where it needs to find one information
element embedded in a number of others and the constraints for the other elements have the any-or-omit
value. In such a case the test system cannot easily find the beginning of each information element.
6.1.1.2.2 ASN.1 structured type definitions
There are no ASN.1 structured type definitions in the ATS.
6.1.1.3 ASP type definitions
6.1.1.3.1 TTCN ASP type definitions
TTCN ASP type definitions only contain one PDU or no PDU at all. The relationship between an ASP type
and a PDU type is one-to-one. That is, there exists one ASP type definition for each PDU type definition (if
that ASP type contains a PDU).
All TTCN ASP type definitions are provided with a full identifier.
Some ASPs are not parameterized as shown in the example in table 1. Such ASPs are only used for
requesting or receiving service from the lower layer.
Table 1: TTCN ASP type definition DL_REL_IN
TTCN ASP Type Definition
ASP NAME : DL_REL_IN
     (DL_RELEASE_INDICATION)
PCO Type : SAP
Comments :
Parameter Name           |   Parameter Type    |    Comments
Detailed Comments :
Table 2 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and
no other parameters.
Table 2: TTCN ASP type definition DL_DATA_RQ
TTCN ASP Type Definition
ASP NAME : DL_DATA_RQ
     (DL_DATA_Request)
PCO Type : SAP
Comments : CEId: = (SAPI,CES) mapped onto
      DLCI: = (SAPI,TEI)
      ASP is used to request the transmission of layer 3 PDUs
Parameter Name           |   Parameter Type    |    Comments
mun (MessageUnit)         |PDU            |
Detailed Comments :

---------------------- Page: 12 ----------------------

SIST ETS 300 098-4:1998
Page 11
ETS 300 098-4: May 1997
6.1.1.3.2 ASN.1 ASP type definitions
There are no ASN.1 ASP type definitions in the ATS.
6.1.1.4 PDU type definitions
6.1.1.4.1 TTCN PDU type definitions
The TTCN PDU type reflects the actual data being transferred or received. All PDUs are embedded in
ASPs.
If a specific PDU type definition contains elements defined in terms of a pre-defined type, that element has
a restriction attached to it.
6.1.1.4.2 ASN.1 PDU type definitions
There are no ASN.1 PDU type definitions in the ATS.
6.1.2 Test suite constants
No test suite constants are used or defined in this ATS.
6.1.3 Test suite parameters
Each test suite parameter is defined in terms of a predefined type or a referenced type. A referenced type
is used when it is necessary to attach restrictions to these type definitions (it is not allowed to include
restrictions directly in the test suite parameter table). The referenced type can have a length or value
restriction attached to it in its declaration table.
6.1.4 Variables
6.1.4.1 Test suite variables
No test suite variables are used or defined in this ATS.
6.1.4.2 Test case variables
Each test case variable is defined in terms of a predefined type or a referenced type. A referenced type is
used when it is necessary to attach restrictions to these type definitions (it is not allowed to include
restrictions directly in the test case variable table). The referenced type can have a length or value
restriction attached to it in its declaration table.
Where test case variables are used in constraints, they are passed as formal parameters.
6.1.5 Test suite operation definitions
No test suite operations are used or defined in this ATS.
6.1.6 Alias definitions
Alias definitions are used to highlight the exchange of PDUs embedded in ASPs.
EXAMPLE: Alias "SETUP" is expanded with "DL_DATA_RQ" to send a SETUP PDU
constraint by ASP constraint Ms(SUnn(Par,Par)).

---------------------- Page: 13 ----------------------

SIST ETS 300 098-4:1998
Page 12
ETS 300 098-4: May 1997
6.2 Constraints part
6.2.1 Structured type constraint declaration
For every structured type definition there exists one or more structured type constraint.
6.2.2 ASN.1 type constraint declaration
No ASN.1 type constraint declaration exists in this ATS.
6.2.3 ASP type constraint declaration
6.2.3.1 ASN.1 ASP type constraint declaration
No ASN.1 ASP type constraint declaration exists in this ATS.
6.2.3.2 TTCN ASP type constraint declaration
For TTCN ASP constraint declarations there is a one-to-one relationship between its type and the
constraint. That is, there is only one constraint for each TTCN ASP type declaration. The reason for this is
that the ASPs are used only for carrying PDU values.
6.2.4 PDU type constraint declaration
6.2.4.1 ASN.1 PDU type constraint declaration
No ASN.1 PDU type constraint declaration exists in this ATS.
6.2.4.2 TTCN PDU type constraint declaration
PDU constraints are used for assigning values or patterns to the data being sent or received.
6.2.5 Chaining of constraints
6.2.5.1 Static chaining
Static chaining, that is a fixed reference to a specific constraint, is used in this ATS. The static chaining is
used for static binding of both variables and sub-structures.
6.2.5.2 Dynamic chaining
Dynamic chaining is achieved when having a reference to a value which is unknown. The only thing
known (before run-time) is the type of that reference. The reference is passed as a parameter. Strict
dynamic chaining is not used in this ATS. What is used is something that is called "semi-dynamic
chaining". The definition of semi-dynamic chaining is that the fixed reference is parameterized with an
unknown value. That value is received as a parameter.
Table 3: TTCN ASP constraint declaration Ms
TTCN ASP Constraint Declaration
Constraint Name : Ms(PARAM: PDU)
ASP Type    : DL_DATA_RQ
Derivation Path :
Comments    :
     Parameter Name     |    Parameter Value    |       Comments
mun                |PARAM             |
Detailed comments :
Table 3 is an example of semi-dynamic chaining. The TTCN ASP constraint is parameterized with
metatype PDU value named PARAM. That value is passed further down in the structure as a value to the
message unit.

---------------------- Page: 14 ----------------------

SIST ETS 300 098-4:1998
Page 13
ETS 300 098-4: May 1997
6.2.6 Derived constraints
No derivation of any constraints is used. All constraints are considered to be base constraints.
6.2.7 Parameterized constraints
Parameterized constraints are used in this ATS.
6.2.8 Value assignment
6.2.8.1 Specific values
For specific value assignment both explicit values and references to explicit values are used.
6.2.8.2 Matching values
As matching values the following mechanisms are used:
Instead of Value:
AnyOrOmit "*"
AnyValue "?"
Omit "-"
Inside value:
AnyOne "?"
AnyOrNone "*"
6.3 Dynamic part
6.3.1 Test cases
Each test case contains the test purpose text from ETS 300 098-3 [4]. To be able to read and understand
the test case dynamic behaviour it is recommended that the test steps are understood first.
6.3.2 Test steps
Much use has been made of test steps to avoid needless repetition of dynamic behaviour. Many test steps
are based on those used for the ISDN basic call ATS.
6.3.3 Defaults
The RETURN statement which is defined in DAM1 of ISO 9646-3 [7] is not used. This statement allows
valid background behaviour to be handled in the default tree with a possibility to return to
...