SIST ETS 300 130-6:1997

Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network

;

Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: razpoznavanje (identifikacija) zlonamernega klica (MCID) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 6. del: Niz abstraktnih preskusov (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) - Proformna specifikacija za omrežje

General Information

• Status: Published
• Publication Date: 31-Oct-1997
• 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-Nov-1997
• Due Date: 01-Nov-1997
• Completion Date: 01-Nov-1997
• Ref Project: ETSI ETS 300 130-6 ed.1 (1996-10) - Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYIntegrated Services Digital Network (ISDN); Malicious Call Identification (MCID) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma specification for the network33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 130-6 E13SIST ETS 300 130-6:1997en01-DYJXVW-19973SIST ETS 300 130-6:1997SLOVENSKI
STANDARD



SIST ETS 300 130-6:1997



EUROPEANETS 300 130-6TELECOMMUNICATIONOctober 1996STANDARDSource: ETSI TC-SPSReference: DE/SPS-05061-N-6ICS:33.080Key words:ISDN, DSS1, supplementary service, MCID, testing, ATS, PIXIT, networkIntegrated Services Digital Network (ISDN);Malicious Call Identification (MCID) supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 6: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT) proformaspecification for the networkETSIEuropean 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 1996. All rights reserved.SIST ETS 300 130-6:1997



Page 2ETS 300 130-6: 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 130-6:1997



Page 3ETS 300 130-6: October 1996ContentsForeword.71Scope.92Normative references.93Definitions and abbreviations.103.1Definitions.103.2Abbreviations.104Abstract Test Method (ATM).114.1Description of ATM used.114.1.1Conventions for test components and PCOs.114.1.2Conventions for variables and parameters.124.2Alternative ATM.135Untestable test purposes.146ATS conventions.146.1Declarations part.146.1.1Type definitions.146.1.1.1Simple type definitions.146.1.1.2Structured type definitions.146.1.1.2.1TTCN structured type definitions.146.1.1.2.2ASN.1 structured type definitions.146.1.1.3ASP type definitions.166.1.1.3.1TTCN ASP type definitions.166.1.1.3.2ASN.1 ASP type definitions.166.1.1.4PDU type definitions.166.1.1.4.1TTCN PDU type definitions.166.1.1.4.2ASN.1 PDU type definitions.166.1.2Test suite constants.176.1.3Test suite parameters.176.1.4Variables.176.1.4.1Test suite variables.176.1.4.2Test case variables.176.1.5Test suite operation definitions.176.2Constraints part.186.2.1Structured type constraint declaration.186.2.2ASN.1 type constraint declaration.186.2.2.1Specification of encoding rules.196.2.3ASP type constraint declaration.206.2.3.1ASN.1 ASP type constraint declaration.206.2.3.2TTCN ASP type constraint declaration.206.2.4PDU type constraint declaration.206.2.4.1ASN.1 PDU type constraint declaration.206.2.4.2TTCN PDU type constraint declaration.206.2.5Chaining of constraints.206.2.5.1Static chaining.206.2.5.2Dynamic chaining.206.2.6Derived constraints.216.2.7Parameterized constraints.216.2.8Value assignment.216.2.8.1Specific values.216.2.8.2Matching values.21SIST ETS 300 130-6:1997



Page 4ETS 300 130-6: October 19966.3Dynamic part.216.3.1Test cases.216.3.2Test steps.216.3.2.1PTC1_IN.216.3.2.2PTC1_OUT.216.3.3Defaults.217ATS to TP map.228PCTR conformance.229PIXIT conformance.2210ATS conformance.22Annex A (normative):Protocol Conformance Test Report (PCTR) proforma.23A.1Identification summary.23A.1.1Protocol conformance test report.23A.1.2IUT identification.23A.1.3Testing environment.23A.1.4Limits and reservations.24A.1.5Comments.24A.2IUT conformance status.24A.3Static conformance summary.24A.4Dynamic conformance summary.24A.5Static conformance review report.25A.6Test campaign report.25A.7Observations.25Annex B (normative):Partial PIXIT proforma.26B.1Identification summary.26B.2Abstract test suite summary.26B.3Test laboratory.26B.4Client (of the test laboratory).27B.5System Under Test (SUT).27B.6Protocol information.28B.6.1Protocol identification.28B.6.2Parameter values.28B.6.3Actions required to stimulate IUT.28B.6.4Configuration of IUT.28B.7Basic call PIXIT items.29B.7.1Parameter values - information element codings.29Annex C (normative):Abstract Test Suite (ATS).30C.1The TTCN Graphical form (TTCN.GR).30C.2The TTCN Machine Processable form (TTCN.MP).30SIST ETS 300 130-6:1997



Page 5ETS 300 130-6: October 1996Annex D (informative):General structure of ATS.31History.32SIST ETS 300 130-6:1997



Page 6ETS 300 130-6: October 1996Blank pageSIST ETS 300 130-6:1997



Page 7ETS 300 130-6: 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 6 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Malicious CallIdentification (MCID) 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 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 130-6:1997



Page 8ETS 300 130-6: October 1996Blank pageSIST ETS 300 130-6:1997



Page 9ETS 300 130-6: October 19961ScopeThis sixth part of ETS 300 130 specifies the Abstract Test Suite (ATS) and partial Protocol ImplementationeXtra Information for Testing (PIXIT) proforma for the Network side of the T reference point or coincidentS and T reference point (as defined in ITU-T Recommendation I.411 [11]) of implementations conformingto the stage three standard for the Malicious Call Identification (MCID) supplementary service for thepan-European Integrated Services Digital Network (ISDN) by means of the Digital Subscriber SignallingSystem No. one (DSS1) protocol, ETS 300 130-1 [2].ETS 300 130-5 [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 User side of the T reference point or coincident S and T reference point ofimplementations conforming to ETS 300 130-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 130-1 (1993): "Integrated Services Digital Network (ISDN); MaliciousCall Identification (MCID) supplementary service; Digital Subscriber SignallingSystem No. one (DSS1) protocol; Part 1: Protocol specification".[3]ETS 300 130-2 (1995): "Integrated Services Digital Network (ISDN); MaliciousCall Identification (MCID) supplementary service; Digital Subscriber SignallingSystem No. one (DSS1) protocol; Part 2: Protocol Implementation ConformanceStatement (PICS) proforma specification".[4]ETS 300 130-5: "Integrated Services Digital Network (ISDN); Malicious CallIdentification (MCID) supplementary service; Digital Subscriber SignallingSystem No. one (DSS1) protocol; Part 5: Test Suite Structure and TestPurposes (TSS&TP) specification for the network".[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 130-6:1997



Page 10ETS 300 130-6: 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:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteBERBasic Encoding RulesCMCo-ordination MessageCPCo-ordination PointExTSExecutable Test SuiteIUTImplementation Under TestLTLower TesterMCIDMalicious Call IdentificationMOTMeans Of TestingMTCMain Test ComponentPCOPoint of Control and ObservationPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingPTCParallel Test ComponentSUTSystem Under TestTCPTest Co-ordination ProceduresTPTest PurposeTTCNTree and Tabular Combined NotationUTUpper TesterSIST ETS 300 130-6:1997



Page 11ETS 300 130-6: October 19964Abstract Test Method (ATM)4.1Description of ATM usedThe requirement for testing the network IUT is to focus on the behaviour of the network IUT at theuser-network interface where a T reference point or coincident S and T reference point applies. Thus theIUT is the network DSS1 protocol entity at a particular user-network interface and is not the wholenetwork.It is possible to specify an ATS based on a Single party (remote) test method for such an IUT. However, itis considered that an ATS based on such an approach is of limited use as the only way to specify IUTgenerated PDUs is to use the "implicit send" statement. Many users of such an ATS would replace the"implicit send" statements with descriptions of the behaviour at other interfaces.An ATS based on a multi-party test method is considered to be more useful in that it is closer to how areal test suite would be constructed. Such a test method specifies behaviour at multiple networkinterfaces. One very important limitation here is that tests are focused on one particular interface. Thusthe test system is made up one Main Test Component (MTC) and one or more Parallel Test Components(PTC), see figure 1.4.1.1Conventions for test components and PCOsMaster partSlave partMTCAPTC1CPA1L0 PCOL1 PCOIUTNETWORKFigure 1: Multi-party test methodIn a master/slave arrangement, the MTC is considered to be the master while the PTCs are the slaves.The "slave" testers are only an explicit description of how to deal with the "other" interfaces during thetesting process, i.e. "how to make the IUT send the required message".SIST ETS 300 130-6:1997



Page 12ETS 300 130-6: October 1996This means, in particular, that the verdict will only be assigned from the protocol aspects observed on theinterface under test (i.e. by the "master" tester), as it would be observed by a terminal connected to thisinterface. A failure in the correlation between the protocol at the different interfaces to which the differenttesters are connected, i.e. in the mechanism of the functional service itself, will not cause a FAIL verdict.For instance, if the IUT fails to send a message on the tested interface after another interface hasreceived the proper stimulus, the verdict will be INCONCLUSIVE.The MTC MTCA has two functions in this configuration. Firstly, it has the MTC function of controlling theone or more PTCs. Thus it is responsible for starting the PTCs and afterwards co-ordinates activities byexchanging Co-ordination Messages (CM) with the PTCs. Secondly it is responsible for the behaviour ofthe Lower Tester (LT) at PCO L0.A combination of the remote and multi-party test methods is applied. As can be seen from figure 1,several PCOs are used. All PCOs reside at the service access points between layers 2 and 3.MTCSUTPTC1Layer 3¾¾¾¾Layer 2¾¾¾¾Layer 1¾L0¾¾¾¾¾¾¾¾¾IUT¾¾¾¾¾¾¾¾¾
¾¾
¾¾¾¾¾¾¾¾¾¾¾¾¾¾L1¾¾¾¾¾Layer 3¾¾¾¾Layer 2¾¾¾¾Layer 1Service providerFigure 2: Combination of the remote and multi-party test methodsThe MTC PCO is named "L0" ("L" for Lower). The L0 PCO is used to control and observe the behaviour ofthe IUT and test case verdicts are assigned depending on the behaviour observed at this PCO. The PTCPTC1 uses PCO L1. This PCO is used to control and, in a limited way, observe the behaviour of thenetwork equipment at interfaces other than the one under test. No verdicts are assigned at this PCO.As stated in a previous paragraph, the non-receipt of network generated messages at L0, which arestimulated by events at the L1, will result in INCONCLUSIVE rather than FAIL verdicts being assigned.4.1.2Conventions for variables and parametersMTCAcall referenceCREF1B channel (basic)bch_num1(to PTC1)channel nr (primary)CH_NUM1PCO L0IPN0, LIPN0PTC1call referenceP1CREFB channel (basic)P1_bch_numchannel nr (primary)P1_CH_NUMPCO L1IPN1, LIPN1SIST ETS 300 130-6:1997



Page 13ETS 300 130-6: October 19964.2Alternative ATMAs stated in subclause 4.1, an ATS based on a single-party (remote) ATM is possible. Such an ATS maybe generated from the one specified in this ETS. The following general steps should be taken:1)remove all PTC behaviour;2)remove all CREATE statements;3)replace CMs which are used to provoke PDUs at the MTC, with implicit send statements.An example, showing the difference between the multi-party ATM and single-party ATM for a single testcase, is given in tables 1 and 2.Table 1: Test case dynamic behaviour table using multi-party ATMTEST CASE DYNAMIC BEHAVIOURTest Case NameHOLD_N04_001GroupRemoteUser_ST_OR_T/Holding/PurposeEnsure that the IUT, while in the Active call state N10, to notifythe non-served user that the call is heldsends a NOTIFY message with a notification indicator coded as"remote hold" to user B and remains in the Active call state.DefaultDF69901(1)ConfigurationCONFIG1Comments9.2.1validoptional Nr| Label| BEHAVIOUR DESCRIPTION| CREF| V| COMMENTS1||CREATE ( PTC1: PTC1_IN_servedUser)|||2|| +PR31002|||preamble N103||
CPA1!CP_M START TWAIT|S_HL||4||
L0?NOTIFYr|A_NO20(CREF1,hold_NID)|(P)|5||
+CS59901(10,1)|||check N106||
?TIMEOUT TWAIT||(I)|7||
+PO49901(1)|||postamble N0DETAILED COMMENTS:Table 2: Test case dynamic behaviour table using single-party ATMTEST CASE DYNAMIC BEHAVIOURTest Case NameHOLD_N04_001GroupRemoteUser_ST_OR_T/Holding/PurposeEnsure that the IUT, while in the Active call state N10, to notifythe non-served user that the call is heldsends a NOTIFY message with a notification indicator coded as"remote hold" to user B and remains in the Active call state.DefaultDF69901(1)ConfigurationComments9.2.1validoptional Nr| Label| BEHAVIOUR DESCRIPTION| CREF| V| COMMENTS1||+PR31002|||preamble N102|| |NO20(CREF1,hold_NID)||3||
L0?NOTIFYr|A_NO20(CREF1,hold_NID)|(P)|4||
+CS59901(10,1)|||check N105||
?TIMEOUT TWAIT||(I)|6||
+PO49901(1)|||postamble N0DETAILED COMMENTS:SIST ETS 300 130-6:1997



Page 14ETS 300 130-6: October 19965Untestable test purposesThere are no untestable test cases associated with this ATS and ATM.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.6.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.SIST ETS 300 130-6:1997



Page 15ETS 300 130-6: October 1996In table 3, 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 3: ASN.1 type definition BIT7OR15ASN.1 Type DefinitionType Name : BIT7OR15Comments
:Type DefinitionBIT STRING(SIZE(CR_LENGTH))Table 4 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.Table 4: 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 5 shows an example of how ASN.1 can be used to model unordered sequences.Table 5: 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.SIST ETS 300 130-6:1997



Page 16ETS 300 130-6: October 1996
...

SLOVENSKI STANDARD
SIST ETS 300 130-6:1997
01-november-1997
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1'RSROQLOQDVWRULWHY
UD]SR]QDYDQMHLGHQWLILNDFLMD]ORQDPHUQHJDNOLFD0&,'3URWRNROGLJLWDOQH
QDURþQLãNHVLJQDOL]DFLMHãW'66GHO1L]DEVWUDNWQLKSUHVNXVRY$76LQ
GHOQDGRGDWQDLQIRUPDFLMD]DSUHVNXãDQMHL]YHGEHSURWRNROD3,;,73URIRUPQD
VSHFLILNDFLMD]DRPUHåMH
Integrated Services Digital Network (ISDN); Malicious Call Identification (MCID)
supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 6: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information
for Testing (PIXIT) proforma specification for the network
Ta slovenski standard je istoveten z: ETS 300 130-6 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 130-6:1997 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 130-6:1997

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

SIST ETS 300 130-6:1997
EUROPEAN ETS 300 130-6
TELECOMMUNICATION October 1996
STANDARD
Source: ETSI TC-SPS Reference: DE/SPS-05061-N-6
ICS: 33.080
Key words: ISDN, DSS1, supplementary service, MCID, testing, ATS, PIXIT, network
Integrated Services Digital Network (ISDN);
Malicious Call Identification (MCID) supplementary service;
Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 6: Abstract Test Suite (ATS) and partial Protocol
Implementation eXtra Information for Testing (PIXIT) proforma
specification for the network
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 1996. All rights reserved.

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

SIST ETS 300 130-6:1997
Page 2
ETS 300 130-6: 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 130-6:1997
Page 3
ETS 300 130-6: October 1996
Contents
Foreword .7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .10
4 Abstract Test Method (ATM).11
4.1 Description of ATM used .11
4.1.1 Conventions for test components and PCOs.11
4.1.2 Conventions for variables and parameters .12
4.2 Alternative ATM .13
5 Untestable test purposes.14
6 ATS conventions .14
6.1 Declarations part.14
6.1.1 Type definitions .14
6.1.1.1 Simple type definitions.14
6.1.1.2 Structured type definitions .14
6.1.1.2.1 TTCN structured type definitions .14
6.1.1.2.2 ASN.1 structured type definitions.14
6.1.1.3 ASP type definitions.16
6.1.1.3.1 TTCN ASP type definitions .16
6.1.1.3.2 ASN.1 ASP type definitions .16
6.1.1.4 PDU type definitions .16
6.1.1.4.1 TTCN PDU type definitions.16
6.1.1.4.2 ASN.1 PDU type definitions .16
6.1.2 Test suite constants .17
6.1.3 Test suite parameters .17
6.1.4 Variables .17
6.1.4.1 Test suite variables.17
6.1.4.2 Test case variables.17
6.1.5 Test suite operation definitions.17
6.2 Constraints part.18
6.2.1 Structured type constraint declaration.18
6.2.2 ASN.1 type constraint declaration .18
6.2.2.1 Specification of encoding rules.19
6.2.3 ASP type constraint declaration .20
6.2.3.1 ASN.1 ASP type constraint declaration .20
6.2.3.2 TTCN ASP type constraint declaration.20
6.2.4 PDU type constraint declaration.20
6.2.4.1 ASN.1 PDU type constraint declaration.20
6.2.4.2 TTCN PDU type constraint declaration .20
6.2.5 Chaining of constraints.20
6.2.5.1 Static chaining .20
6.2.5.2 Dynamic chaining .20
6.2.6 Derived constraints.21
6.2.7 Parameterized constraints.21
6.2.8 Value assignment.21
6.2.8.1 Specific values.21
6.2.8.2 Matching values.21

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

SIST ETS 300 130-6:1997
Page 4
ETS 300 130-6: October 1996
6.3 Dynamic part . 21
6.3.1 Test cases . 21
6.3.2 Test steps . 21
6.3.2.1 PTC1_IN . 21
6.3.2.2 PTC1_OUT . 21
6.3.3 Defaults. 21
7 ATS to TP map . 22
8 PCTR conformance. 22
9 PIXIT conformance. 22
10 ATS conformance. 22
Annex A (normative): Protocol Conformance Test Report (PCTR) proforma . 23
A.1 Identification summary. 23
A.1.1 Protocol conformance test report. 23
A.1.2 IUT identification. 23
A.1.3 Testing environment. 23
A.1.4 Limits and reservations . 24
A.1.5 Comments. 24
A.2 IUT conformance status . 24
A.3 Static conformance summary. 24
A.4 Dynamic conformance summary. 24
A.5 Static conformance review report . 25
A.6 Test campaign report. 25
A.7 Observations. 25
Annex B (normative): Partial PIXIT proforma . 26
B.1 Identification summary. 26
B.2 Abstract test suite summary . 26
B.3 Test laboratory. 26
B.4 Client (of the test laboratory) . 27
B.5 System Under Test (SUT) . 27
B.6 Protocol information. 28
B.6.1 Protocol identification . 28
B.6.2 Parameter values . 28
B.6.3 Actions required to stimulate IUT. 28
B.6.4 Configuration of IUT . 28
B.7 Basic call PIXIT items. 29
B.7.1 Parameter values - information element codings. 29
Annex C (normative): Abstract Test Suite (ATS). 30
C.1 The TTCN Graphical form (TTCN.GR) . 30
C.2 The TTCN Machine Processable form (TTCN.MP) . 30

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

SIST ETS 300 130-6:1997
Page 5
ETS 300 130-6: October 1996
Annex D (informative): General structure of ATS.31
History.32

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

SIST ETS 300 130-6:1997
Page 6
ETS 300 130-6: October 1996
Blank page

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

SIST ETS 300 130-6:1997
Page 7
ETS 300 130-6: 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 6 of a multi-part standard covering the Digital Subscriber Signalling System No. one
(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Malicious Call
Identification (MCID) 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: 9 ----------------------

SIST ETS 300 130-6:1997
Page 8
ETS 300 130-6: October 1996
Blank page

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

SIST ETS 300 130-6:1997
Page 9
ETS 300 130-6: October 1996
1 Scope
This sixth part of ETS 300 130 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation
eXtra Information for Testing (PIXIT) proforma for the Network 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 Malicious Call Identification (MCID) 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 130-1 [2].
ETS 300 130-5 [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 User side of the T reference point or coincident S and T reference point of
implementations conforming to ETS 300 130-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 130-1 (1993): "Integrated Services Digital Network (ISDN); Malicious
Call Identification (MCID) supplementary service; Digital Subscriber Signalling
System No. one (DSS1) protocol; Part 1: Protocol specification".
[3] ETS 300 130-2 (1995): "Integrated Services Digital Network (ISDN); Malicious
Call Identification (MCID) supplementary service; Digital Subscriber Signalling
System No. one (DSS1) protocol; Part 2: Protocol Implementation Conformance
Statement (PICS) proforma specification".
[4] ETS 300 130-5: "Integrated Services Digital Network (ISDN); Malicious Call
Identification (MCID) supplementary service; Digital Subscriber Signalling
System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test
Purposes (TSS&TP) specification for the network".
[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: 11 ----------------------

SIST ETS 300 130-6:1997
Page 10
ETS 300 130-6: 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:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
BER Basic Encoding Rules
CM Co-ordination Message
CP Co-ordination Point
ExTS Executable Test Suite
IUT Implementation Under Test
LT Lower Tester
MCID Malicious Call Identification
MOT Means Of Testing
MTC Main Test Component
PCO Point of Control and Observation
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
PTC Parallel Test Component
SUT System Under Test
TCP Test Co-ordination Procedures
TP Test Purpose
TTCN Tree and Tabular Combined Notation
UT Upper Tester

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

SIST ETS 300 130-6:1997
Page 11
ETS 300 130-6: October 1996
4 Abstract Test Method (ATM)
4.1 Description of ATM used
The requirement for testing the network IUT is to focus on the behaviour of the network IUT at the
user-network interface where a T reference point or coincident S and T reference point applies. Thus the
IUT is the network DSS1 protocol entity at a particular user-network interface and is not the whole
network.
It is possible to specify an ATS based on a Single party (remote) test method for such an IUT. However, it
is considered that an ATS based on such an approach is of limited use as the only way to specify IUT
generated PDUs is to use the "implicit send" statement. Many users of such an ATS would replace the
"implicit send" statements with descriptions of the behaviour at other interfaces.
An ATS based on a multi-party test method is considered to be more useful in that it is closer to how a
real test suite would be constructed. Such a test method specifies behaviour at multiple network
interfaces. One very important limitation here is that tests are focused on one particular interface. Thus
the test system is made up one Main Test Component (MTC) and one or more Parallel Test Components
(PTC), see figure 1.
4.1.1 Conventions for test components and PCOs
Master part Slave part
MTCA
PTC1
CPA1
L0 PCO L1 PCO
IUT
NETWORK
Figure 1: Multi-party test method
In a master/slave arrangement, the MTC is considered to be the master while the PTCs are the slaves.
The "slave" testers are only an explicit description of how to deal with the "other" interfaces during the
testing process, i.e. "how to make the IUT send the required message".

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

SIST ETS 300 130-6:1997
Page 12
ETS 300 130-6: October 1996
This means, in particular, that the verdict will only be assigned from the protocol aspects observed on the
interface under test (i.e. by the "master" tester), as it would be observed by a terminal connected to this
interface. A failure in the correlation between the protocol at the different interfaces to which the different
testers are connected, i.e. in the mechanism of the functional service itself, will not cause a FAIL verdict.
For instance, if the IUT fails to send a message on the tested interface after another interface has
received the proper stimulus, the verdict will be INCONCLUSIVE.
The MTC MTCA has two functions in this configuration. Firstly, it has the MTC function of controlling the
one or more PTCs. Thus it is responsible for starting the PTCs and afterwards co-ordinates activities by
exchanging Co-ordination Messages (CM) with the PTCs. Secondly it is responsible for the behaviour of
the Lower Tester (LT) at PCO L0.
A combination of the remote and multi-party test methods is applied. As can be seen from figure 1,
several PCOs are used. All PCOs reside at the service access points between layers 2 and 3.
MTC SUT PTC1
Layer 3 IUT Layer 3
 L0      L1 
Layer 2 Layer 2
 
        
Layer 1 Layer 1
Service provider
Figure 2: Combination of the remote and multi-party test methods
The MTC PCO is named "L0" ("L" for Lower). The L0 PCO is used to control and observe the behaviour of
the IUT and test case verdicts are assigned depending on the behaviour observed at this PCO. The PTC
PTC1 uses PCO L1. This PCO is used to control and, in a limited way, observe the behaviour of the
network equipment at interfaces other than the one under test. No verdicts are assigned at this PCO.
As stated in a previous paragraph, the non-receipt of network generated messages at L0, which are
stimulated by events at the L1, will result in INCONCLUSIVE rather than FAIL verdicts being assigned.
4.1.2 Conventions for variables and parameters
MTCA
call reference CREF1
B channel (basic) bch_num1 (to PTC1)
channel nr (primary) CH_NUM1
PCO L0 IPN0, LIPN0
PTC1
call reference P1CREF
B channel (basic) P1_bch_num
channel nr (primary) P1_CH_NUM
PCO L1 IPN1, LIPN1

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

SIST ETS 300 130-6:1997
Page 13
ETS 300 130-6: October 1996
4.2 Alternative ATM
As stated in subclause 4.1, an ATS based on a single-party (remote) ATM is possible. Such an ATS may
be generated from the one specified in this ETS. The following general steps should be taken:
1) remove all PTC behaviour;
2) remove all CREATE statements;
3) replace CMs which are used to provoke PDUs at the MTC, with implicit send statements.
An example, showing the difference between the multi-party ATM and single-party ATM for a single test
case, is given in tables 1 and 2.
Table 1: Test case dynamic behaviour table using multi-party ATM
TEST CASE DYNAMIC BEHAVIOUR
Test Case Name HOLD_N04_001
Group RemoteUser_ST_OR_T/Holding/
Purpose Ensure that the IUT, while in the Active call state N10, to notify
the non-served user that the call is held
sends a NOTIFY message with a notification indicator coded as
"remote hold" to user B and remains in the Active call state.
Default DF69901(1)
Configuration CONFIG1
Comments 9.2.1 valid optional
Nr | Label| BEHAVIOUR DESCRIPTION | CREF | V | COMMENTS
1 | |CREATE ( PTC1: PTC1_IN_servedUser) | | |
2 | | +PR31002 | | |preamble N10
3 | | CPA1!CP_M START TWAIT |S_HL | |
4 | |  L0?NOTIFYr |A_NO20(CREF1,hold_NID) |(P)|
5 | |  +CS59901(10,1) | | |check N10
6 | |  ?TIMEOUT TWAIT | |(I)|
7 | |  +PO49901(1) | | |postamble N0
DETAILED COMMENTS:
Table 2: Test case dynamic behaviour table using single-party ATM
TEST CASE DYNAMIC BEHAVIOUR
Test Case Name HOLD_N04_001
Group RemoteUser_ST_OR_T/Holding/
Purpose Ensure that the IUT, while in the Active call state N10, to notify
the non-served user that the call is held
sends a NOTIFY message with a notification indicator coded as
"remote hold" to user B and remains in the Active call state.
Default DF69901(1)
Configuration
Comments 9.2.1 valid optional
Nr | Label| BEHAVIOUR DESCRIPTION | CREF | V | COMMENTS
1 | |+PR31002 | | |preamble N10
2 | | |NO20(CREF1,hold_NID) | |
3 | | L0?NOTIFYr |A_NO20(CREF1,hold_NID) |(P)|
4 | |  +CS59901(10,1) | | |check N10
5 | | ?TIMEOUT TWAIT | |(I)|
6 | |  +PO49901(1) | | |postamble N0
DETAILED COMMENTS:

---------------------- Page: 15 ----------------------

SIST ETS 300 130-6:1997
Page 14
ETS 300 130-6: October 1996
5 Untestable test purposes
There are no untestable test cases associated with this ATS and ATM.
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.
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.

---------------------- Page: 16 ----------------------

SIST ETS 300 130-6:1997
Page 15
ETS 300 130-6: October 1996
In table 3, 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 Pr
...