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

Update to references to cite latest basic call standards et al. Incorporation of minor technical modifications where necessary.

Digitalno omrežje z integriranimi storitvami (ISDN) – Dopolnilna storitev: konferenca treh (3PTY) – 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 specifikacija za uporabnika

General Information

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Standard

Standard
SIST EN 300 188-4 V1.2.4:2003
English language
26 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

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:EN 300 188-4 Version 1.2.4SIST EN 300 188-4 V1.2.4:2003en01-december-2003SIST EN 300 188-4 V1.2.4:2003SLOVENSKI

STANDARD
SIST EN 300 188-4 V1.2.4:2003

EN 300 188-4 V1.2.4 (1998-06)European Standard (Telecommunications series)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 ProtocolImplementation eXtra Information for Testing (PIXIT)proforma specification for the userSIST EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)2ReferenceREN/SPS-05145-J2-4 (1qp00iqo.PDF)KeywordsISDN, DSS1, supplementary service, 3PTY,testing, ATS, PIXIT, userETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00

Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo 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 1998.All rights reserved.SIST EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)3ContentsIntellectual Property Rights................................................................................................................................5Foreword............................................................................................................................................................51Scope........................................................................................................................................................62Normative references...............................................................................................................................63Definitions and abbreviations..................................................................................................................73.1Definitions.........................................................................................................................................................73.2Abbreviations.....................................................................................................................................................74Abstract Test Method (ATM)..................................................................................................................85Untestable test purposes...........................................................................................................................86ATS conventions......................................................................................................................................86.1Declarations part................................................................................................................................................86.1.1Type definitions...........................................................................................................................................86.1.1.1Simple type definitions...........................................................................................................................86.1.1.2Structured type definitions......................................................................................................................96.1.1.2.1TTCN structured type definitions.....................................................................................................96.1.1.2.2ASN.1 structured type definitions.....................................................................................................96.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..................................................................................................................126.2Constraints part................................................................................................................................................126.2.1Structured type constraint declaration........................................................................................................126.2.2ASN.1 type constraint declaration..............................................................................................................126.2.2.1Specification of encoding rules.............................................................................................................136.2.3ASP type constraint declaration.................................................................................................................146.2.3.1ASN.1 ASP type constraint declaration................................................................................................146.2.3.2TTCN ASP type constraint declaration................................................................................................146.2.4PDU type constraint declaration.................................................................................................................146.2.4.1ASN.1 PDU type constraint declaration...............................................................................................146.2.4.2TTCN PDU type constraint declaration................................................................................................146.2.5Chaining of constraints...............................................................................................................................146.2.5.1Static chaining......................................................................................................................................146.2.5.2Dynamic chaining.................................................................................................................................146.2.6Derived constraints.....................................................................................................................................156.2.7Parameterized constraints...........................................................................................................................156.2.8Value assignment.......................................................................................................................................156.2.8.1Specific values......................................................................................................................................156.2.8.2Matching values....................................................................................................................................156.3Dynamic part....................................................................................................................................................156.3.1Test cases...................................................................................................................................................156.3.2Test steps....................................................................................................................................................156.3.3Defaults......................................................................................................................................................16SIST EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)47ATS to TP map......................................................................................................................................168PCTR conformance................................................................................................................................169PIXIT conformance................................................................................................................................1610ATS conformance..................................................................................................................................16Annex A (normative):Protocol Conformance Test Report (PCTR) proforma.............................17A.1Identification summary..........................................................................................................................17A.1.1Protocol conformance test report.....................................................................................................................17A.1.2IUT identification............................................................................................................................................17A.1.3Testing environment........................................................................................................................................17A.1.4Limits and reservations....................................................................................................................................18A.1.5Comments........................................................................................................................................................18A.2IUT conformance status.........................................................................................................................18A.3Static conformance summary.................................................................................................................18A.4Dynamic conformance summary............................................................................................................18A.5Static conformance review report..........................................................................................................19A.6Test campaign report..............................................................................................................................19A.7Observations...........................................................................................................................................19Annex B (normative):Partial PIXIT proforma................................................................................20B.1Identification summary..........................................................................................................................20B.2Abstract test suite summary...................................................................................................................20B.3Test laboratory.......................................................................................................................................20B.4Client (of the test laboratory).................................................................................................................21B.5System Under Test (SUT)......................................................................................................................21B.6Protocol information..............................................................................................................................22B.6.1Protocol identification......................................................................................................................................22B.6.2Parameter values..............................................................................................................................................22B.6.3Sending of messages by IUT............................................................................................................................22Annex C (normative):Abstract Test Suite (ATS).............................................................................23C.1The TTCN Graphical form (TTCN.GR)................................................................................................23C.2The TTCN Machine Processable form (TTCN.MP).............................................................................23Annex D (informative):General structure of ATS.............................................................................24Annex E (informative):Changes with respect to the previous ETS 300 188-4................................25History..............................................................................................................................................................26SIST EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document 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) supplementaryservice, 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:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network";Part 6:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the network".The present version updates the references to the basic call specifications.National transposition datesDate of adoption of this EN:19 June 1998Date of latest announcement of this EN (doa):30 September 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 March 1999Date of withdrawal of any conflicting National Standard (dow):31 March 1999SIST EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)61ScopeThis fourth part of EN 300 188 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtraInformation for Testing (PIXIT) proforma for the User side of the T reference point or coincident S and T referencepoint (as defined in ITU-T Recommendation I.411 [11]) of implementations conforming to the stage three standard forthe Three Party (3PTY) supplementary service for the pan-European Integrated Services Digital Network (ISDN) bymeans of the Digital Subscriber Signalling System No. one (DSS1) protocol, EN 300 188-1 [2].EN 300 188-3 [4] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS and partial PIXITproforma specification. Other parts specify the TSS&TP and the ATS and partial PIXIT proforma for the Network sideof the T reference point or coincident S and T reference point of implementations conforming to EN 300 188-1 [2].2Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case the latest version applies.A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1:Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".[2]EN 300 188-1 (V1.2): "Integrated Services Digital Network (ISDN); Three Party (3PTY)supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 1:Protocol specification".[3]EN 300 188-2 (V1.2): "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]EN 300 188-3 (V1.2): "Integrated Services Digital Network (ISDN); Three Party (3PTY)supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: TestSuite Structure and Test Purposes (TSS&TP) specification for the user".[5]EN 300 196-1: "Integrated Services Digital Network (ISDN); Generic functional protocol for thesupport 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 andFramework; Part 1: General Concepts".[7]ISO/IEC 9646-2: "Information Technology - OSI Conformance Testing Methodology andFramework; Part 2: Abstract Test Suite Specification".[8]ISO/IEC 9646-3: "Information Technology - OSI Conformance Testing Methodology andFramework; Part 3: The Tree and Tabular Combined Notation".[9]ISO/IEC 9646-4: "Information Technology - OSI Conformance Testing Methodology andFramework; Part 4: Test realization".SIST EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)7[10]ISO/IEC 9646-5: "Information Technology - OSI Conformance Testing Methodology andFramework; Part 5: Requirements on test laboratories and clients for the conformance assessmentprocess".[11]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".[12]CCITT Recommendation X.209 (1988): "Specification of Basic Encoding Rules for AbstractSyntax Notation One (ASN.1)".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, 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 the present document, 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 EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)84Abstract Test Method (ATM)The remote test method is applied for the 3PTY user ATS. The Point of Control and Observation (PCO) resides at theservice access point between layers 2 and 3. This PCO is named "L" (for Lower). The L PCO is used to control andobserve the behaviour of the Implementation Under Test (IUT) and test case verdicts are assigned depending on thebehaviour 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 the System UnderTest (SUT) upper layer(s) and the Lower Tester (LT). In the ATS contained in annex C, TCP is achieved by use of asecond "informal" PCO, called "O" (for Operator). This PCO is used to specify control but not observation above theIUT and consequently, events at this PCO are never used to generate test case verdicts. The use of this O PCO isregarded as a preferred alternative to the use of the implicit send event, in that it allows the ATS to specify in a clear andmeaningful way what actions are required 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 subclauses are arrangedin a way more suitable to the present document.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 length restriction or avalue list attached.Simple types, defined as being of INTEGER type, have a value list or a range restriction attached.SIST EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)96.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 definedin that referenced type.For information elements the identifier, which is unique for each element, has its type defined as a simple type where thevalue list is restricted to the single value which is the identifier itself. This has the advantage that it allows a test systemderived from this ATS to easily identify information elements embedded in messages. An ATS where informationelement identifiers are represented as unrestricted types can present difficulties for a derived test system in the casewhere it needs to find one information element embedded in a number of others and the constraints for the otherelements have the any-or-omit value. In such a case the test system cannot easily find the beginning of each informationelement.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" TTCNcannot. 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 isnecessary to use ASN.1 to reproduce the type definitions for remote operation components as specified in the basestandards.The fact that ASN.1 provides a better restriction mechanism for type definitions is used for the purpose of achievingtype-compatibility.In table 1, the ASN.1 type BIT7OR15 is defined as being of type BIT STRING with a size constraint attached to it. Thesize is determined by the value of CR_LENGTH, a test suite parameter. It can have the value of either 7 or 15. The typeBIT7OR15 is used in the structured type CR, field cr_r allowing this type to represent a Basic Access or a Primary RateAccess call reference. By using this type definition the field cr_r is always type compatible with values of typeBIT STRING (SIZE(7)) and BIT STRING (SIZE(15)). Another approach to solve this problem would be to define thetype BIT7OR15 as BIT STRING (SIZE(7 | 15)). This type has a small disadvantage compared with the previous one. Itis impossible, 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 depending on whether itrepresents basic or primary rate access. In TTCN, this needs to be defined as two different types. In ASN.1 this can bedone 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 EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)10Table 2: ASN.1 type definition CHIASN.1 Type DefinitionType Name : CHIComments

: Info Element Channel Identification
EN 300 403-1 subclause 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 a TTCN 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 type and a PDUtype is one-to-one. That is, there exists one ASP type definition for each PDU type definition (if that ASP type containsa 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 orreceiving 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 EN 300 188-4 V1.2.4:2003

ETSIEN 300 188-4 V1.2.4 (1998-06)11Table 5 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and no otherparameters.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 in ASPs.If a specific PDU type definition contains elements defined in terms of a pre-defined type, that element has a restrictionattached 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 type is used when itis necessary to attach restrictions to these type definitions (it is not allowed to include restrictions d

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.