ETSI ETS 300 188-4 ed.1 (1996-10)
Integrated Services Digital Network (ISDN); Three-Party (3PTY) 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
Integrated Services Digital Network (ISDN); Three-Party (3PTY) 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
DE/SPS-05061-J2-4
Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: konferenca treh (3PTY) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 4. del: Niz abstraktnih preskusov (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) - Proformna specifikacija za uporabnika
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYIntegrated Services Digital Network (ISDN); Three-Party (3PTY) 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 188-4 Edition 13SIST ETS 300 188-4:1997en01-RNWREHU-19973SIST ETS 300 188-4:1997SLOVENSKI
STANDARD
SIST ETS 300 188-4:1997
EUROPEANETS 300 188-4TELECOMMUNICATIONOctober 1996STANDARDSource: ETSI TC-SPSReference: DE/SPS-05061-J2-4ICS:33.080Key words:ISDN, DSS1, supplementary service, 3PTY, testing, ATS, PIXIT, userIntegrated Services Digital Network (ISDN);Three-Party (3PTY) 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: secretariat@etsi.frTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright 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 1996. All rights reserved.SIST ETS 300 188-4:1997
Page 2ETS 300 188-4: October 1996Whilst 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 188-4:1997
Page 3ETS 300 188-4: October 1996ContentsForeword.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.116.1.1.3.1TTCN ASP type definitions.116.1.1.3.2ASN.1 ASP type definitions.126.1.1.4PDU type definitions.126.1.1.4.1TTCN PDU type definitions.126.1.1.4.2ASN.1 PDU type definitions.126.1.2Test suite constants.126.1.3Test suite parameters.126.1.4Variables.126.1.4.1Test suite variables.126.1.4.2Test case variables.126.1.5Test suite operation definitions.136.2Constraints part.136.2.1Structured type constraint declaration.136.2.2ASN.1 type constraint declaration.136.2.2.1Specification of encoding rules.146.2.3ASP type constraint declaration.156.2.3.1ASN.1 ASP type constraint declaration.156.2.3.2TTCN ASP type constraint declaration.156.2.4PDU type constraint declaration.156.2.4.1ASN.1 PDU type constraint declaration.156.2.4.2TTCN PDU type constraint declaration.156.2.5Chaining of constraints.156.2.5.1Static chaining.156.2.5.2Dynamic chaining.156.2.6Derived constraints.166.2.7Parameterized constraints.166.2.8Value assignment.166.2.8.1Specific values.166.2.8.2Matching values.166.3Dynamic part.166.3.1Test cases.166.3.2Test steps.166.3.3Defaults.167ATS to TP map.17SIST ETS 300 188-4:1997
Page 4ETS 300 188-4: October 19968PCTR conformance.179PIXIT conformance.1710ATS conformance.17Annex A (normative):Protocol Conformance Test Report (PCTR) proforma.18A.1Identification summary.18A.1.1Protocol conformance test report.18A.1.2IUT identification.18A.1.3Testing environment.18A.1.4Limits and reservations.19A.1.5Comments.19A.2IUT conformance status.19A.3Static conformance summary.19A.4Dynamic conformance summary.19A.5Static conformance review report.20A.6Test campaign report.20A.7Observations.21Annex B (normative):Partial PIXIT proforma.22B.1Identification summary.22B.2Abstract test suite summary.22B.3Test laboratory.22B.4Client (of the test laboratory).23B.5System Under Test (SUT).23B.6Protocol information.24B.6.1Protocol identification.24B.6.2Parameter values.24B.6.3Sending of messages by IUT.24Annex C (normative):Abstract Test Suite (ATS).25C.1The TTCN Graphical form (TTCN.GR).25C.2The TTCN Machine Processable form (TTCN.MP).25Annex D (informative):General structure of ATS.26History.27SIST ETS 300 188-4:1997
Page 5ETS 300 188-4: October 1996ForewordThis 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) Three-Party (3PTY)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 of this ETS:4 October 1996Date of latest announcement of this ETS (doa):31 January 1997Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 July 1997Date of withdrawal of any conflicting National Standard (dow):31 July 1997SIST ETS 300 188-4:1997
Page 6ETS 300 188-4: October 1996Blank pageSIST ETS 300 188-4:1997
Page 7ETS 300 188-4: October 19961ScopeThis fourth part of ETS 300 188 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 [11]) ofimplementations conforming to the stage three standard for the Three-Party (3PTY) supplementaryservice for the pan-European Integrated Services Digital Network (ISDN) by means of the DigitalSubscriber Signalling System No. one (DSS1) protocol, ETS 300 188-1 [2].ETS 300 188-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 188-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 188-1 (1993): "Integrated Services Digital Network (ISDN); Three-Party(3PTY) supplementary service; Digital Subscriber Signalling System No. one(DSS1) protocol; Part 1: Protocol specification".[3]ETS 300 188-2 (1995): "Integrated Services Digital Network (ISDN); Three-Party(3PTY) supplementary service; Digital Subscriber Signalling System No. one(DSS1) protocol; Part 2: Protocol Implementation Conformance Statement(PICS) proforma specification".[4]ETS 300 188-3: "Integrated Services Digital Network (ISDN); Three-Party(3PTY) 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]ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN); Genericfunctional protocol for the support of supplementary services; Digital SubscriberSignalling System No. one (DSS1) protocol; Part 1: Protocol specification".[6]ISO/IEC 9646-1: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 1: General Concepts".[7]ISO/IEC 9646-2: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 2: Abstract Test Suite Specification".[8]ISO/IEC 9646-3: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 3: The Tree and Tabular CombinedNotation".[9]ISO/IEC 9646-4: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 4: Test realization".[10]ISO/IEC 9646-5: "Information Technology - OSI Conformance TestingMethodology and Framework; Part 5: Requirements on test laboratories andclients for the conformance assessment process".[11]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -Reference configurations".SIST ETS 300 188-4:1997
Page 8ETS 300 188-4: October 1996[12]CCITT Recommendation X.209 (1988): "Specification of Basic Encoding Rulesfor Abstract Syntax Notation One (ASN.1)".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply:Abstract Test Suite (ATS): See ISO/IEC 9646-1 [6].Implementation Under Test (IUT): See ISO/IEC 9646-1 [6].Lower Tester (LT): See ISO/IEC 9646-1 [6].Point of Control and Observation (PCO): See ISO/IEC 9646-1 [6].Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [6].PICS proforma: See ISO/IEC 9646-1 [6].Protocol Implementation eXtra Information for Testing (PIXIT): See ISO/IEC 9646-1 [6].PIXIT proforma: See ISO/IEC 9646-1 [6].System Under Test (SUT): See ISO/IEC 9646-1 [6].Upper Tester (UT): See ISO/IEC 9646-1 [6].3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:3PTYThree-PartyASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteBERBasic Encoding RulesExTSExecutable Test SuiteIUTImplementation Under TestLTLower TesterMOTMeans Of TestingPCOPoint of Control and ObservationPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingSUTSystem Under TestTCPTest Co-ordination ProceduresTPTest PurposeTTCNTree and Tabular Combined NotationUTUpper TesterSIST ETS 300 188-4:1997
Page 9ETS 300 188-4: October 19964Abstract Test Method (ATM)The remote test method is applied for the 3PTY 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 [7] 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 188-4:1997
Page 10ETS 300 188-4: October 19966.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 definitionsASN.1 has been used for three major reasons. First, types defined in ASN.1 can model problems that"pure" TTCN cannot. For instance, data structures modelling ordered or unordered sequences of data arepreferably defined in ASN.1. Second, ASN.1 provides a better restriction mechanism for type definitionsby using sub-type definitions. Third, it is necessary to use ASN.1 to reproduce the type definitions forremote operation components as specified in the base standards.The fact that ASN.1 provides a better restriction mechanism for type definitions is used for the purpose ofachieving type-compatibility.In table 1, the ASN.1 type BIT7OR15 is defined as being of type BIT STRING with a size constraintattached to it. The size is determined by the value of CR_LENGTH, a test suite parameter. It can have thevalue of either 7 or 15. The type BIT7OR15 is used in the structured type CR, field cr_r allowing this typeto represent a Basic Access or a Primary Rate Access call reference. By using this type definition the fieldcr_r is always type compatible with values of type BIT STRING (SIZE(7)) and BIT STRING (SIZE(15)).Another approach to solve this problem would be to define the type BIT7OR15 asBIT STRING (SIZE(7 | 15)). This type has a small disadvantage compared with the previous one. It isimpossible, in run-time, to determine the actual length of any instance of this type.Table 1: ASN.1 type definition BIT7OR15ASN.1 Type DefinitionType Name : BIT7OR15Comments
:Type DefinitionBIT STRING(SIZE(CR_LENGTH))Table 2 shows a typical use of ASN.1. The CHI element will have two different type definitions dependingon whether it represents basic or primary rate access. In TTCN, this needs to be defined as two differenttypes. In ASN.1 this can be done in one, the type being a choice of either BASIC_CHI or PRIMARY_CHI.These two types are then (locally) defined in the same table.SIST ETS 300 188-4:1997
Page 11ETS 300 188-4: October 1996Table 2: ASN.1 type definition CHIASN.1 Type DefinitionType Name : CHIComments
: Info Element Channel Identification
ETS 300 102-1 clause 4.5.13Type DefinitionCHOICE { basic
BASIC_CHI, primary
PRIMARY_CHI}-- Local type definitions --BASIC_CHI ::= SEQUENCE { chi_i
CHI_I,
-- Identifier chi_l
BIT STRING(SIZE(8)),
-- Length chi_e3_cs
BIT STRING(SIZE(8))
-- Channel selection}PRIMARY_CHI ::= SEQUENCE { chi_i
CHI_I,
-- Identifier chi_l
BIT STRING(SIZE(8)),
-- Length chi_e3_p1
BIT STRING(SIZE(4)),
-- First nibble of Channel selection chi_e3_pe
BIT STRING(SIZE(1)),
-- Preferred/Exclusive Bit chi_e3_p3
BIT STRING(SIZE(3)),
-- Last three bits of Channel selection chi_e4
BIT STRING(SIZE(8)),
-- Channel type chi_e5_chl
BIT STRING(SIZE(1)), chi_e5_ch2
BIT STRING(SIZE(7))
-- Channel number}Table 3 shows an example of how ASN.1 can be used to model unordered sequences.Table 3: ASN.1 type definition FIESASN.1 Type DefinitionType Name : FIESComments
:Type DefinitionSET OF FIEThe possibility to use TTCN and ASN.1 in combination is used, i.e. referring to an ASN.1 type from aTTCN type.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 4. Such ASPs are only used forrequesting or receiving service from the lower layer.Table 4: 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 :SIST ETS 300 188-4:1997
Page 12ETS 300 188-4: October 1996Table 5 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU andno other parameters.Table 5: TTCN ASP type definition DL_DATA_RQ_ALERTTTCN ASP Type DefinitionASP NAME : DL_DATA_RQ_ALERT(DL_DATA_REQUEST)PCO Type : SAPComments :Parameter Name
|
Parameter Type
|
Commentsmun (MessageUnit)
|ALERT_PDU
|Detailed Comments :6.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.SIST ETS 300 188-4:1997
Page 13ETS 300 188-4: October 19966.1.5Test suite operation definitionsThe description part of a test suite operation definition uses either natural language or meta C.Table 6: Test suite operation definition ASSIGN_CHITest Suite Operation DefinitionOperation Name : ASSIGN_CHI(basic, primary : CHI; basic_flag : BOOLEAN)Result Type
: CHIComments
: This operation is used to assign a correct Channel identification information
element to PDUs dependent on the type of access that is tested.Description{if(basic_flag)
return basic;else
return primary}Detailed comments :The test suite operation definition shown in table 6 is used in the constraints part when assigning anelement of type CHI a value. As previously described, the CHI type can be defined in two ways dependingon whether the ATS is testing basic or primary rate access. To avoid duplicate types and thereby duplicatetest cases the CHI type is defined in ASN.1. This operation is used to assign a value to an element of CHItype. It takes three parameters:This operation returns the correct constraint according to the Boolean flag basic_flag. That constraint willthen be assigned to the specific element of type CHI.6.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 declarationConstraints of this type are used to assign the corresponding type a specific value. These constraints areused for the purpose of modelling unordered data or specific types that cannot be expressed in TTCN.A value assigned to an element of type SET OF differs depending on whether it is a send or receiveconstraint.Table 7: ASN.1 type constraint declaration fIEs (send constraint)ASN.1 Type Constraint DeclarationConstraint Name : fIEs(comp : Component)ASN.1 Type
: FIEDerivation Path :Comments
: Send FIE which will contain one component "comp".Description{
informationElementIdentifier
'00011100'B,
length
CALC_FIE_LENGTH(comp),
extBit
'1'B,
spareBits
'00'B,
protocolProfile
'10001'B,
components
{comp}}Detailed comments :NOTE:The last element in the constraint, components, is of type SET OF Component whereComponent is structured data of some type.SIST ETS 300 188-4:1997
Page 14ETS 300 188-4: October 1996If the constraint is a send constraint (as in table 7) the value for the component element is stated as"{comp}" where comp is an argument received as a parameter. The "{" and "}" turns the value into a SETOF value which is correct according to that element's type definition.Table 8: ASN.1 type constraint declaration fIEr (receive constraint)ASN.1 Type Constraint DeclarationConstraint Name : fIEr(comp : Component)ASN.1 Type
: FIEDerivation Path :Comments
: A received FIE which can contain several components, but which contains at
least "comp".Description{
informationElementIdentifier
'00011100'B,
length
'????????'B,
extBit
'1'B,
spareBits
'00'B,
protocolProfile
'10001'B,
components
SUPERSET({comp})}Detailed comments :NOTE:The last element in the constraint, named components, is of type SET OF Componentwhere Component is structured data of some type.If the constraint is a receive constraint (as in table 8) the corresponding matching value is assigned byusing SUPERSET. The key-word SUPERSET has an argument that is type compatible with the typedefinition of that field. In table 8, the element named components is defined as "SET OF Component" andthis implie
...
SLOVENSKI STANDARD
SIST ETS 300 188-4:1997
01-december-1997
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 'RSROQLOQDVWRULWHY
NRQIHUHQFDWUHK 37< 3URWRNROGLJLWDOQHQDURþQLãNHVLJQDOL]DFLMHãW '66
GHO 1L]DEVWUDNWQLKSUHVNXVRY $76 LQGHOQDGRGDWQDLQIRUPDFLMD]D
SUHVNXãDQMHL]YHGEHSURWRNROD 3,;,7 3URIRUPQDVSHFLILNDFLMD]DXSRUDEQLND
Integrated Services Digital Network (ISDN); Three-Party (3PTY) 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 188-4 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 188-4:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 188-4:1997
---------------------- Page: 2 ----------------------
SIST ETS 300 188-4:1997
EUROPEAN ETS 300 188-4
TELECOMMUNICATION October 1996
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05061-J2-4
ICS: 33.080
Key words: ISDN, DSS1, supplementary service, 3PTY, testing, ATS, PIXIT, user
Integrated Services Digital Network (ISDN);
Three-Party (3PTY) 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: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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 1996. All rights reserved.
---------------------- Page: 3 ----------------------
SIST ETS 300 188-4:1997
Page 2
ETS 300 188-4: October 1996
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 188-4:1997
Page 3
ETS 300 188-4: October 1996
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.11
6.1.1.3.1 TTCN ASP type definitions .11
6.1.1.3.2 ASN.1 ASP type definitions .12
6.1.1.4 PDU type definitions .12
6.1.1.4.1 TTCN PDU type definitions.12
6.1.1.4.2 ASN.1 PDU type definitions .12
6.1.2 Test suite constants .12
6.1.3 Test suite parameters .12
6.1.4 Variables .12
6.1.4.1 Test suite variables.12
6.1.4.2 Test case variables.12
6.1.5 Test suite operation definitions.13
6.2 Constraints part.13
6.2.1 Structured type constraint declaration.13
6.2.2 ASN.1 type constraint declaration .13
6.2.2.1 Specification of encoding rules.14
6.2.3 ASP type constraint declaration .15
6.2.3.1 ASN.1 ASP type constraint declaration .15
6.2.3.2 TTCN ASP type constraint declaration.15
6.2.4 PDU type constraint declaration.15
6.2.4.1 ASN.1 PDU type constraint declaration.15
6.2.4.2 TTCN PDU type constraint declaration .15
6.2.5 Chaining of constraints.15
6.2.5.1 Static chaining .15
6.2.5.2 Dynamic chaining .15
6.2.6 Derived constraints.16
6.2.7 Parameterized constraints.16
6.2.8 Value assignment.16
6.2.8.1 Specific values.16
6.2.8.2 Matching values.16
6.3 Dynamic part.16
6.3.1 Test cases.16
6.3.2 Test steps.16
6.3.3 Defaults .16
7 ATS to TP map.17
---------------------- Page: 5 ----------------------
SIST ETS 300 188-4:1997
Page 4
ETS 300 188-4: October 1996
8 PCTR conformance. 17
9 PIXIT conformance. 17
10 ATS conformance. 17
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma . 18
A.1 Identification summary. 18
A.1.1 Protocol conformance test report. 18
A.1.2 IUT identification. 18
A.1.3 Testing environment. 18
A.1.4 Limits and reservations . 19
A.1.5 Comments. 19
A.2 IUT conformance status . 19
A.3 Static conformance summary. 19
A.4 Dynamic conformance summary. 19
A.5 Static conformance review report . 20
A.6 Test campaign report. 20
A.7 Observations. 21
Annex B (normative): Partial PIXIT proforma . 22
B.1 Identification summary. 22
B.2 Abstract test suite summary . 22
B.3 Test laboratory. 22
B.4 Client (of the test laboratory) . 23
B.5 System Under Test (SUT) . 23
B.6 Protocol information. 24
B.6.1 Protocol identification . 24
B.6.2 Parameter values . 24
B.6.3 Sending of messages by IUT . 24
Annex C (normative): Abstract Test Suite (ATS). 25
C.1 The TTCN Graphical form (TTCN.GR) . 25
C.2 The TTCN Machine Processable form (TTCN.MP) . 25
Annex D (informative): General structure of ATS. 26
History. 27
---------------------- Page: 6 ----------------------
SIST ETS 300 188-4:1997
Page 5
ETS 300 188-4: October 1996
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) Three-Party (3PTY)
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 of this ETS: 4 October 1996
Date of latest announcement of this ETS (doa): 31 January 1997
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 July 1997
Date of withdrawal of any conflicting National Standard (dow): 31 July 1997
---------------------- Page: 7 ----------------------
SIST ETS 300 188-4:1997
Page 6
ETS 300 188-4: October 1996
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 188-4:1997
Page 7
ETS 300 188-4: October 1996
1 Scope
This fourth part of ETS 300 188 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 [11]) of
implementations conforming to the stage three standard for the Three-Party (3PTY) 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 188-1 [2].
ETS 300 188-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 188-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 188-1 (1993): "Integrated Services Digital Network (ISDN); Three-Party
(3PTY) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 1: Protocol specification".
[3] ETS 300 188-2 (1995): "Integrated Services Digital Network (ISDN); Three-Party
(3PTY) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol; Part 2: Protocol Implementation Conformance Statement
(PICS) proforma specification".
[4] ETS 300 188-3: "Integrated Services Digital Network (ISDN); Three-Party
(3PTY) 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] ETS 300 196-1 (1993): "Integrated Services Digital Network (ISDN); Generic
functional protocol for the support of supplementary services; Digital Subscriber
Signalling System No. one (DSS1) protocol; Part 1: Protocol specification".
[6] ISO/IEC 9646-1: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 1: General Concepts".
[7] ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 2: Abstract Test Suite Specification".
[8] ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 3: The Tree and Tabular Combined
Notation".
[9] ISO/IEC 9646-4: "Information Technology - OSI Conformance Testing
Methodology and Framework; Part 4: Test realization".
[10] 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".
[11] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces -
Reference configurations".
---------------------- Page: 9 ----------------------
SIST ETS 300 188-4:1997
Page 8
ETS 300 188-4: October 1996
[12] CCITT Recommendation X.209 (1988): "Specification of Basic Encoding Rules
for Abstract Syntax Notation One (ASN.1)".
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 [6].
Implementation Under Test (IUT): See ISO/IEC 9646-1 [6].
Lower Tester (LT): See ISO/IEC 9646-1 [6].
Point of Control and Observation (PCO): See ISO/IEC 9646-1 [6].
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [6].
PICS proforma: See ISO/IEC 9646-1 [6].
Protocol Implementation eXtra Information for Testing (PIXIT): See ISO/IEC 9646-1 [6].
PIXIT proforma: See ISO/IEC 9646-1 [6].
System Under Test (SUT): See ISO/IEC 9646-1 [6].
Upper Tester (UT): See ISO/IEC 9646-1 [6].
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
3PTY Three-Party
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BER Basic Encoding Rules
ExTS Executable Test Suite
IUT Implementation Under Test
LT Lower Tester
MOT Means Of Testing
PCO Point of Control and Observation
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 188-4:1997
Page 9
ETS 300 188-4: October 1996
4 Abstract Test Method (ATM)
The remote test method is applied for the 3PTY 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 [7] 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 188-4:1997
Page 10
ETS 300 188-4: October 1996
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
ASN.1 has been used for three major reasons. First, types defined in ASN.1 can model problems that
"pure" TTCN cannot. For instance, data structures modelling ordered or unordered sequences of data are
preferably defined in ASN.1. Second, ASN.1 provides a better restriction mechanism for type definitions
by using sub-type definitions. Third, it is necessary to use ASN.1 to reproduce the type definitions for
remote operation components as specified in the base standards.
The fact that ASN.1 provides a better restriction mechanism for type definitions is used for the purpose of
achieving type-compatibility.
In table 1, the ASN.1 type BIT7OR15 is defined as being of type BIT STRING with a size constraint
attached to it. The size is determined by the value of CR_LENGTH, a test suite parameter. It can have the
value of either 7 or 15. The type BIT7OR15 is used in the structured type CR, field cr_r allowing this type
to represent a Basic Access or a Primary Rate Access call reference. By using this type definition the field
cr_r is always type compatible with values of type BIT STRING (SIZE(7)) and BIT STRING (SIZE(15)).
Another approach to solve this problem would be to define the type BIT7OR15 as
BIT STRING (SIZE(7 | 15)). This type has a small disadvantage compared with the previous one. It is
impossible, in run-time, to determine the actual length of any instance of this type.
Table 1: ASN.1 type definition BIT7OR15
ASN.1 Type Definition
Type Name : BIT7OR15
Comments :
Type Definition
BIT STRING(SIZE(CR_LENGTH))
Table 2 shows a typical use of ASN.1. The CHI element will have two different type definitions depending
on whether it represents basic or primary rate access. In TTCN, this needs to be defined as two different
types. In ASN.1 this can be done in one, the type being a choice of either BASIC_CHI or PRIMARY_CHI.
These two types are then (locally) defined in the same table.
---------------------- Page: 12 ----------------------
SIST ETS 300 188-4:1997
Page 11
ETS 300 188-4: October 1996
Table 2: ASN.1 type definition CHI
ASN.1 Type Definition
Type Name : CHI
Comments : Info Element Channel Identification
ETS 300 102-1 clause 4.5.13
Type Definition
CHOICE {
basic BASIC_CHI,
primary PRIMARY_CHI
}
-- Local type definitions --
BASIC_CHI ::= SEQUENCE {
chi_i CHI_I, -- Identifier
chi_l BIT STRING(SIZE(8)), -- Length
chi_e3_cs BIT STRING(SIZE(8)) -- Channel selection
}
PRIMARY_CHI ::= SEQUENCE {
chi_i CHI_I, -- Identifier
chi_l BIT STRING(SIZE(8)), -- Length
chi_e3_p1 BIT STRING(SIZE(4)), -- First nibble of Channel selection
chi_e3_pe BIT STRING(SIZE(1)), -- Preferred/Exclusive Bit
chi_e3_p3 BIT STRING(SIZE(3)), -- Last three bits of Channel selection
chi_e4 BIT STRING(SIZE(8)), -- Channel type
chi_e5_chl BIT STRING(SIZE(1)),
chi_e5_ch2 BIT STRING(SIZE(7)) -- Channel number
}
Table 3 shows an example of how ASN.1 can be used to model unordered sequences.
Table 3: ASN.1 type definition FIES
ASN.1 Type Definition
Type Name : FIES
Comments :
Type Definition
SET OF FIE
The possibility to use TTCN and ASN.1 in combination is used, i.e. referring to an ASN.1 type from a
TTCN type.
6.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 4. Such ASPs are only used for
requesting or receiving service from the lower layer.
Table 4: 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 :
---------------------- Page: 13 ----------------------
SIST ETS 300 188-4:1997
Page 12
ETS 300 188-4: October 1996
Table 5 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and
no other parameters.
Table 5: TTCN ASP type definition DL_DATA_RQ_ALERT
TTCN ASP Type Definition
ASP NAME : DL_DATA_RQ_ALERT(DL_DATA_REQUEST)
PCO Type : SAP
Comments :
Parameter Name | Parameter Type | Comments
mun (MessageUnit) |ALERT_PDU |
Detailed Comments :
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.
---------------------- Page: 14 ----------------------
SIST ETS 300 188-4:1997
Page 13
ETS 300 188-4: October 1996
6.1.5 Test suite operation definitions
The description part of a test suite operation definition uses either natural language or meta C.
Table 6: Test suite operation definition ASSIGN_CHI
Test Suite Operation Definition
Operation Name : ASSIGN_CHI(basic, primary : CHI; basic_flag : BOOLEAN)
Result Type : CHI
Comments : This operation is used to assign a correct Channel identification information
element to PDUs dependent on the type of access that is tested.
Description
{
if(basic_flag)
return basic;
else
return primary
}
Detailed comments :
The test suite operation definition shown in table 6 is used in the constraints part when assigning an
element of type CHI a value. As previously described, the CHI type can be defined in two ways depending
on whether the ATS is testing basic or primary rate access. To avoid duplicate types and thereby duplicate
test cases the CHI type is defined in ASN.1. This operation is used to assign a value to an element of CHI
type. It takes three parameters:
SULPDU\DFRQVWUDLQWRIW\SH&+,YDOLGIRUSULPDU\UDWHDFFHVV
EDVLFDFRQVWUDLQWRIW\SH&+,YDOLGIRUEDVLFDFFHVV
EDVLFBIODJD%RROHDQYDOXH758(LIEDVLFDFFHVVLVDSSOLFDEOH)$/6(RWKHUZLVH
This operation returns the correct constraint according to the Boolean flag basic_flag. That constraint will
then be assigned to the specific element of type CHI.
6.2 Constraints part
6.2.1 Structured type constraint decl
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.