ETSI EN 300 185-6 V1.2.4 (1998-06)
Integrated Services Digital Network (ISDN); Conference call, add-on (CONF) 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
Integrated Services Digital Network (ISDN); Conference call, add-on (CONF) 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
REN/SPS-05145-J1-6
Digitalno omrežje z integriranimi storitvami (ISDN) – Dopolnilna storitev: konferenčni klic, postopno vzpostavljanje (CONF) – Protokol digitalne naročniške signalizacije št. 1 (DSS1) – 6. del: Abstraktni preskušalni niz (ATS) in delna dodatna informacija za preskušanje izvedbe protokola (PIXIT) – Proforma specifikacija za omrežje
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYRIRUPDIntegrated Services Digital Network (ISDN); Conference call, add-on (CONF) 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:EN 300 185-6 Version 1.2.4SIST EN 300 185-6 V1.2.4:2003en01-december-2003SIST EN 300 185-6 V1.2.4:2003SLOVENSKI
STANDARD
EN 300 185-6 V1.2.4 (1998-06)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Conference call, add-on (CONF) supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 6: Abstract Test Suite (ATS) and partial ProtocolImplementation eXtra Information for Testing (PIXIT)proforma specification for the networkSIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)2ReferenceREN/SPS-05145-J1-6 (1ppi0iqo.PDF)KeywordsISDN, DSS1, supplementary service, CONF,testing, ATS, PIXIT, networkETSIPostal 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 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)3ContentsIntellectual Property Rights.5Foreword.51Scope.62Normative references.63Definitions and abbreviations.73.1Definitions.73.2Abbreviations.74Abstract Test Method (ATM).84.1Description of ATM used.84.1.1Conventions for test components and PCOs.84.1.2Conventions for variables and parameters.94.1.3Special conventions for the CONF supplementary service.104.1.4Conventions for the remote user group.104.2Alternative ATM.115Untestable test purposes.126ATS conventions.126.1Declarations part.126.1.1Type definitions.126.1.1.1Simple type definitions.126.1.1.2Structured type definitions.126.1.1.2.1TTCN structured type definitions.126.1.1.2.2ASN.1 structured type definitions.126.1.1.3ASP type definitions.146.1.1.3.1TTCN ASP type definitions.146.1.1.3.2ASN.1 ASP type definitions.146.1.1.4PDU type definitions.146.1.1.4.1TTCN PDU type definitions.146.1.1.4.2ASN.1 PDU type definitions.146.1.2Test suite constants.146.1.3Test suite parameters.146.1.4Variables.156.1.4.1Test suite variables.156.1.4.2Test case variables.156.1.5Test suite operation definitions.156.2Constraints part.156.2.1Structured type constraint declaration.156.2.2ASN.1 type constraint declaration.156.2.2.1Specification of encoding rules.166.2.3ASP type constraint declaration.176.2.3.1ASN.1 ASP type constraint declaration.176.2.3.2TTCN ASP type constraint declaration.176.2.4PDU type constraint declaration.186.2.4.1ASN.1 PDU type constraint declaration.186.2.4.2TTCN PDU type constraint declaration.186.2.5Chaining of constraints.186.2.5.1Static chaining.186.2.5.2Dynamic chaining.186.2.6Derived constraints.186.2.7Parameterized constraints.186.2.8Value assignment.186.2.8.1Specific values.186.2.8.2Matching values.19SIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)46.3Dynamic part.196.3.1Test cases.196.3.2Test steps.196.3.2.1PTC1_IN.196.3.2.2PTC1_OUT.196.3.3Defaults.197ATS to TP map.198PCTR conformance.209PIXIT conformance.2010ATS conformance.20Annex A (normative):Protocol Conformance Test Report (PCTR) proforma.21A.1Identification summary.21A.1.1Protocol conformance test report.21A.1.2IUT identification.21A.1.3Testing environment.21A.1.4Limits and reservations.22A.1.5Comments.22A.2IUT conformance status.22A.3Static conformance summary.22A.4Dynamic conformance summary.22A.5Static conformance review report.23A.6Test campaign report.23A.7Observations.24Annex B (normative):Partial PIXIT proforma.25B.1Identification summary.25B.2Abstract test suite summary.25B.3Test laboratory.25B.4Client (of the test laboratory).26B.5System Under Test (SUT).26B.6Protocol information.27B.6.1Protocol identification.27B.6.2Parameter values.27B.6.3Codings of information elements.27B.6.4Configuration of IUT.27B.7Basic call PIXIT items.28B.7.1Parameter values - information element codings.28Annex C (normative):Abstract Test Suite (ATS).29C.1The TTCN Graphical form (TTCN.GR).29C.2The TTCN Machine Processable form (TTCN.MP).29Annex D (informative):General structure of ATS.30Annex E (informative):Changes with respect to the previous ETS 300 185-6.31History.32SIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 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 6 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Conference call, add-on (CONF)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:"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 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)61ScopeThis sixth part of EN 300 185 specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtraInformation for Testing (PIXIT) proforma for the Network 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 Conference call, add-on (CONF) supplementary service for the pan-European Integrated Services Digital Network(ISDN) by means of the Digital Subscriber Signalling System No. one (DSS1) protocol, EN 300 185-1 [2].EN 300 185-5 [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 User side ofthe T reference point or coincident S and T reference point of implementations conforming to EN 300 185-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 185-1 (V1.2): "Integrated Services Digital Network (ISDN); Conference call, add-on(CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 1: Protocol specification".[3]EN 300 185-2 (V1.2): "Integrated Services Digital Network (ISDN); Conference call, add-on(CONF) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".[4]EN 300 185-5 (V1.2): "Integrated Services Digital Network (ISDN); Conference call, add-on(CONF) 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]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 185-6 V1.2.4:2003
ETSIEN 300 185-6 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:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteBERBasic Encoding RulesCMCo-ordination MessageCONFConference call, add-onCPCo-ordination PointExTSExecutable Test SuiteIUTImplementation Under TestLTLower TesterMOTMeans 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 NotationSIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)8UTUpper Tester4Abstract 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 the user-networkinterface where a T reference point or coincident S and T reference point applies. Thus the IUT is the network DSS1protocol 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 consideredthat 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 ofthe 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 suitewould be constructed. Such a test method specifies behaviour at multiple network interfaces. One very importantlimitation here is that tests are focused on one particular interface. Thus the test system is made up one Main TestComponent (MTC) and one or more Parallel Test Components (PTC), see figure 1.4.1.1Conventions for test components and PCOsMaster partSlave partMTCAPTC2CPA2PTC1CPA1L0 PCOL1 PCOL2 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" testersare only an explicit description of how to deal with the "other" interfaces during the testing process, i.e. "how to makethe IUT send the required message".SIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)9This means, in particular, that the verdict will only be assigned from the protocol aspects observed on the interfaceunder test (i.e. by the "master" tester), as it would be observed by a terminal connected to this interface. A failure in thecorrelation between the protocol at the different interfaces to which the different testers are connected, i.e. in themechanism of the functional service itself, will not cause a FAIL verdict. For instance, if the IUT fails to send a messageon 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 morePTCs. Thus it is responsible for starting the PTCs and afterwards co-ordinates activities by exchanging Co-ordinationMessages (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 areused. All PCOs reside at the service access points between layers 2 and 3.MTCSUTPTC1,2Layer 3¾¾¾¾Layer 2¾¾¾¾Layer 1¾L0¾¾¾¾¾¾¾¾¾IUT¾¾¾¾¾¾¾¾¾
¾¾
¾¾¾¾¾¾¾¾¾¾¾¾¾¾L1,2¾¾¾¾¾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 of the IUTand test case verdicts are assigned depending on the behaviour observed at this PCO. The PTCs PTC1, PTC2 etc. usePCOs L1, L2 etc. These PCOs are used to control and, in a limited way, observe the behaviour of the networkequipment at interfaces other than the one under test. No verdicts are assigned at these PCOs.As stated in a previous paragraph, the non-receipt of network generated messages at L0, which are stimulated by eventsat the L1, L2 etc., 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_NUM1call referenceCREF2B channel (basic)bch_num2(to PTC2)channel nr (primary)CH_NUM2PCO L0IPN0, LIPN0PTC1call referenceP1CREFB channel (basic)P1_bch_numchannel nr (primary)P1_CH_NUMPCO L1IPN1, LIPN1SIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)10PTC2call referenceP2CREFB channel (basic)P2_bch_numchannel nr (primary)P2_CH_NUMPCO L2IPN2, LIPN24.1.3Special conventions for the CONF supplementary serviceTo begin a conference from the Null Call State, a remote user is not required. The CREF1 will be used without thePTC1. To add a party to the conference, a remote user with CREF2 using PTC2 is called.Some remote user test cases use 2 parties. To do that the first party is added by using the CREF2 with PTC1. After theparty has been added to the conference, CREF2 will be released. Then it is possible to add the second party by usingCREF2 with PTC2.4.1.4Conventions for the remote user groupFor this group, the side of the network which is being tested is where the conference remote user is connected. The mostconvenient approach here is to connect PTC1 to the IUT. The MTC is, as for the served user group test cases, connectedat the served user side of the network. This approach allows the reuse of test steps developed for the served user grouptests. This approach, representing a slight modification in the test method, is illustrated in figure 3. This shows that thepart of the network considered to be the IUT is connected to PTC1 rather than MTC1.Master partSlave partMTCAPTC2CPA2PTC1CPA1L0 PCOL1 PCOL2 PCOIUTNETWORKFigure 3: Multi-party test method - modified for remote user testsSIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)11The PTC1 is used to observe the notifications sent by the network. The test step PTC1_remoteUser_CR1 is used tocheck the receipt of the notification and depending on the result sends a CM back to the MTC. The MTC then issues averdict depending on the CM received from the PTC1. This is done in order to maintain the convention that the MTC isonly allowed to issue verdicts. However, one consequence of this is that any behaviour at the served user side which isnon-conforming will result in a Fail verdict being issued even though the focus of the tests is at the remote user side.This constraint is viewed as acceptable given the fact that in any case the network shall provide a conforming serveduser interface as well as one or more conforming remote user interfaces.4.2Alternative ATMAs stated in subclause 4.1, an ATS based on a single-party (remote) ATM is possible. Such an ATS may be generatedfrom the one specified in the present document. 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 givenin 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 EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)125Untestable 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 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.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 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.SIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)13In table 3, 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 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 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.Table 4: 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 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 a TTCN type.SIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)146.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 6. Such ASPs are only used for requesting orreceiving service from the lower layer.Table 6: TTCN ASP type definition DL_REL_INTTCN ASP Type DefinitionASP NAME : DL_REL_IN(DL_RELEASE_INDICATION)PCO Type : SAPComments :Parameter Name
|
Parameter Type
|
CommentsDetailed Comments :Table 7 shows an example of a parameterized ASP. All ASPs containing PDUs contain only that PDU and no otherparameters.Table 7: 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 directly in the testsuite parameter table). The referenced type can have a length or value restriction attached to it in its declaration table.SIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)156.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 is used when it isnecessary to attach restrictions to these type definitions (it is not allowed to include restrictions directly in the test casevariable table). The referenced type can have a length or value restriction attached to it in its declaration table.Where test case variables are used in constraints, they are passed as formal parameters.6.1.5Test suite operation definitionsThe description part of a test suite operation definition uses either natural language or meta C.Table 8: 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 8 is used in the constraints part when assigning an element of type CHIa value. As previously described, the CHI type can be defined in two ways depending on whether the ATS is testingbasic 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\UDWHDFFHVVEDVLFDFRQVWUDLQWRIW\SH&+,YDOLGIRUEDVLFDFFHVVEDVLFBIODJD%RROHDQYDOXH758(LIEDVLFDFFHVVLVDSSOLFDEOH)$/6(RWKHUZLVHThis operation returns the correct constraint according to the Boolean flag basic_flag. That constraint will then beassigned 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 are used for thepurpose 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 receive constraint.SIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)16Table 9: 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 where Component isstructured data of some type.If the constraint is a send constraint (as in table 9) the value for the component element is stated as "{comp}" wherecomp is an argument received as a parameter. The "{" and "}" turns the value into a SET OF value which is correctaccording to that element's type definition.Table 10: 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 Component where Component isstructured data of some type.If the constraint is a receive constraint (as in table 10) the corresponding matching value is assigned by usingSUPERSET. The key-word SUPERSET has an argument that is type compatible with the type definition of that field. Intable 10, the element named components is defined as "SET OF Component" and this implies that the argument toSUPERSET should be of type SET OF Component. This is achieved the same way as for send constraints, enclosing thevalue in curly brackets.The semantic of SUPERSET is stated in ISO/IEC 9646-3 [8], subclause 11.6.4.7. In short it defines the semantic asfollows: "A value that uses SUPERSET matches the incoming value if, and only if, the incoming value contains at leastall of the elements defined within the SUPERSET, and may contain more elements." This is exactly the semanticdefinition used in this ATS.6.2.2.1Specification of encoding rulesAt the time of specifying this ATS the mechanisms related to encoding of ASN.1 types, specified in DAM-2 ofISO/IEC 9646-3 [8], were not yet stable. Nevertheless as there is a variation in the encoding rules as applied to ASN.1types and constraints specified in this ATS, a mechanism is used to differentiate the different encoding rules. Given thenon-finalized status of DAM-2, a solution which is broadly in the spirit of DAM-2 has been created. Comment fieldshave been used as a means of including the encoding rules.SIST EN 300 185-6 V1.2.4:2003
ETSIEN 300 185-6 V1.2.4 (1998-06)17For ASN.1 used in this ATS, two variations of encoding rules are used. One is the commonly known Basic EncodingRules (BER) as specified in CCITT Recommendation X.209 [12]. In the second case the encoding is according toISDN, i.e. the ASN.1 data types are a representation of structures contained within the ISDN specification (basic call,Generic functional protocol or individual supplementary service). For example, if octets of an information element arespecified in ASN.1 as a SEQUENCE then this should be encoded in an Executable Test Suite (ExTS) as any other ISDNinformation element specifie
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...