SIST EN 300 745-3:2000
(Main)Integrated Services Digital Network (ISDN); Message Waiting Indication (MWI) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user
Integrated Services Digital Network (ISDN); Message Waiting Indication (MWI) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for the user
Test specification for DE/SPS-05069-1
Digitalno omrežje z integriranimi storitvami (ISDN) - Dopolnilna storitev: indikacija čakajočega sporočila (MWI) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - 3. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) - Specifikacija za uporabnika
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Message Waiting Indication (MWI) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) 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 745-3 Version 1.2.43SIST EN 300 745-3:en01-GHFHPEHU3SIST EN 300 745-3:SLOVENSKI
STANDARD
SIST EN 300 745-3:2000
EN 300 745-3 V1.2.4 (1998-09)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Message Waiting Indication (MWI) supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 3: Test Suite Structure and Test Purposes (TSS&TP)specification for the userSIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)2ReferenceDEN/SPS-05069-3 (6wcr0iqo.PDF)KeywordsISDN, DSS1, supplementary service, MWI,testing, TSS&TP, 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 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)3ContentsIntellectual Property Rights.4Foreword.41Scope.52Normative references.53Definitions.63.1Definitions related to conformance testing.63.2Definitions related to EN 300 745-1.64Abbreviations.75Test Suite Structure (TSS).76Test Purposes (TP).76.1Introduction.76.1.1TP naming convention.86.1.2Source of TP definition.86.1.3TP structure.86.1.4Test strategy.96.2User TPs for MWI.96.2.1S/T.96.2.1.1Controlling user.96.2.1.1.1Activation.96.2.1.1.2Deactivation.106.2.1.2Receiving user.116.2.1.2.1Invocation.116.2.2T reference point (private ISDN).126.2.2.1Controlling user.126.2.2.1.1Activation.126.2.2.1.2Deactivation.136.2.2.2Receiving user.146.2.2.2.1Activation.146.2.2.2.2Deactivation.167Compliance.178Requirements for a comprehensive testing service.17History.18SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)4Intellectual 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.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 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Message Waiting Indication (MWI)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".National transposition datesDate of adoption of this EN:18 September 1998Date of latest announcement of this EN (doa):31 December 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 June 1999Date of withdrawal of any conflicting National Standard (dow):30 June 1999SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)51ScopeThis third part of EN 300 745 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the User side of theT reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [7]) ofimplementations conforming to the stage three standard for the Message Waiting Indication (MWI) supplementaryservice for the pan-European Integrated Services Digital Network (ISDN) by means of the Digital Subscriber SignallingSystem No. one (DSS1) protocol, EN 300 745-1 [1].A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol ImplementationeXtra Information for Testing (PIXIT) proforma based on the present document. Other parts specify the TSS&TP andthe ATS and partial PIXIT proforma for the Network side of the T reference point or coincident S and T reference pointof implementations conforming to EN 300 745-1 [1].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 745-1 (V1.2): "Integrated Services Digital Network (ISDN); Message Waiting Indication(MWI) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 1: Protocol specification".[2]EN 300 745-2 (V1.2): "Integrated Services Digital Network (ISDN); Message Waiting Indication(MWI) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".[3]ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 1: General concepts".[4]ISO/IEC 9646-2 (1994): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 2: Abstract test suite specification".[5]ISO/IEC 9646-3 (1992): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".[6]EN 300 196-1 (V1.2): "Integrated Services Digital Network (ISDN); Generic functional protocolfor the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 1: Protocol specification".[7]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".[8]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]".[9]ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)6[10]CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".[11]ITU-T Recommendation I.210 (1993): "Principles of the telecommunication services supported byan ISDN and the means to describe them".3DefinitionsFor the purposes of the present document, the following definitions apply:3.1Definitions related to conformance testingabstract test case: Refer to ISO/IEC 9646-1 [3].Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].active test: A test case where the Implementation Under Test (IUT) is required to send a particular message, but not inreaction to a received message. This would usually involve the use of PIXIT information to see how this message can begenerated and quite often is specified in an ATS using an implicit send event.Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].implicit send event: Refer to ISO/IEC 9646-3 [5].lower tester: Refer to ISO/IEC 9646-1 [3].passive test: A test case where the IUT is required to respond to a protocol event (e.g. received message) with anotherprotocol event (e.g. send message) which normally does not require any special operator intervention as associated withthe implicit send event.point of control and observation: Refer to ISO/IEC 9646-1 [3].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].PICS proforma: Refer to ISO/IEC 9646-1 [3].Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].PIXIT proforma: Refer to ISO/IEC 9646-1 [3].system under test: Refer to ISO/IEC 9646-1 [3].Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].3.2Definitions related to EN 300 745-1component: See EN 300 196-1 [6], subclause 11.2.2.1.Dummy call reference: See EN 300 403-1 [8], subclause 4.3.Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [9], definition 308.ISDN number: A number conforming to the numbering and structure specified in CCITT Recommendation E.164 [10].invoke component: See EN 300 196-1 [6], subclause 11.2.2.1.return error component: See EN 300 196-1 [6], subclause 11.2.2.1.return result component: See EN 300 196-1 [6], subclause 11.2.2.1.service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201.supplementary service: See ITU-T Recommendation I.210 [11], subclause 2.4.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)7S/T: The DSS1 protocol entity at the User side of the user-network interface where a coincident S and T reference pointapplies.T: The DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is aPrivate ISDN).receiving user: The user that receives the message waiting indication.controlling user: The user that activates and deactivates the message waiting indication.4AbbreviationsFor the purposes of the present document, the following abbreviations apply:ATMAbstract Test MethodATSAbstract Test SuiteISDNIntegrated Services Digital NetworkIUTImplementation Under TestMWIMessage Waiting IndicationPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureU00Null call stateU01Call Initiated call stateU19Release Request call stateU31Bearer Independent Transport call state5Test Suite Structure (TSS)S/TGroup·Controlling User·activationU01·deactivationU02·Receiving User·invocationU03T (private ISDN)·Controlling User·activationU04·deactivationU05·Receiving User·activationU06·deactivationU07Figure 1: Test suite structure6Test Purposes (TP)6.1IntroductionFor each test requirement a TP is defined.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)86.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional referencesare added to identify the actual test suite and whether it applies to the network or the user (see table 1).Table 1: TP identifier naming convention schemeIdentifier:__=supplementary service: "MWI"=type of IUT:UUserNNetwork=group2 digit field representing group reference according to TSS=sequential number(001-999)6.1.2Source of TP definitionThe TPs are based on EN 300 745-1 [1].6.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPsmore readable and checkable. A particular structure has been used and this is illustrated in table 2. This table should beread in conjunction with any TP, i.e. use a TP as an example to fully understand the table.Table 2: Structure of a single TP for MWITP partTextExampleHeader tabsee table 1 tabsubclause 0.0.0 CR.mandatory, optional (see note 1)StimulusEnsure that the IUT in the or U10 etc. see below for message structurereceiving a XXXX messageor to request a .Reactionsends, saves, does, etc.using en bloc sending, .if the action is sending see below for message structure, etc.and remains in the same stateor and enters state Messagestructuremessage containing aSETUP, FACILITY, CONNECT, .a) information element withb) a encoded as or including and back to a or b,Bearer capability, Facility, .NOTE 1:Mandatory TP are always applicable. Optional TPs are applicable according to the configuration optionsof the IUT. If the configuration option is covered by a PICS item, a selection criteria is indicated, else theselection of the corresponding test cases will depend on test suite parameters (PIXIT) in the ATS.NOTE 2:Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from oneTP to the next.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)96.1.4Test strategyAs the base standard EN 300 745-1 [1] contains no explicit requirements for testing, the TPs were generated as a resultof an analysis of the base standard and the PICS specification EN 300 745-2 [2]. The criteria applied include thefollowing:-only the requirements from the point of view of the T or coincident S and T reference point are considered;-whether or not a test case can be built from the TP is not considered.6.2User TPs for MWIAll PICS items referred to in this subclause are as specified in EN 300 745-2 [2] unless indicated otherwise by anothernumbered reference.Unless specified:-The messages indicated are valid and contain at least the mandatory information elements and possibly optionalinformation elements.-The information elements indicated are valid and contain at least the mandatory parameters and possibly optionalparameters.-The FACILITY messages are transmitted using the point-to-point connectionless bearer independent transportmechanism (dummy call reference, DL-DATA-REQUEST) as specified in EN 300 196-1 [6], subclause 8.3.2.2.Where the broadcast connectionless bearer independent transport mechanism applies (dummy call reference,DL-UNIT DATA-REQUEST), the indication of the corresponding subclause of EN 300 196-1 [6] is given (i.e.subclause 8.3.2.4).6.2.1S/TSelection:IUT supports the S and T reference point procedures. PICS: R 3.1.6.2.1.1Controlling userSelection:IUT supports the controlling user procedures. PICS: R 4.1.6.2.1.1.1ActivationMWI_U01_001subclause 9.1.1mandatoryEnsure that the IUT in the MWI Idle state, to activate the MWI supplementary service,transmits a FACILITY message, including a Facility information element with a MWIActivate invoke componentand enters the MWI Activation Requested state.MWI_U01_002subclause 9.1.1mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return result component,transmits no message and enters the MWI Idle state.MWI_U01_003subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "notSubscribed",transmits no message and enters the MWI Idle state.MWI_U01_004subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "invalidReceivingUserNr",transmits no message and enters the MWI Idle state.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)10MWI_U01_005subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"supplementaryServiceInteractionNotAllowed",transmits no message and enters the MWI Idle state.MWI_U01_006subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "resourceUnavailable",transmits no message and enters the MWI Idle state.MWI_U01_007subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "invalidServedUserNr",transmits no message and enters the MWI Idle state.MWI_U01_008subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"receivingUserNotSubscribed",transmits no message and enters the MWI Idle state.MWI_U01_009subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"controllingUserNotRegistered",transmits no message and enters the MWI Idle state.MWI_U01_010subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "indicationNotDelivered",transmits no message and enters the MWI Idle state.MWI_U01_011subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"maxNumOfControllingUsersReached",transmits no message and enters the MWI Idle state.MWI_U01_012subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"maxNumOfActiveInstancesReached",transmits no message and enters the MWI Idle state.MWI_U01_013subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a reject component containing the invoke identifier,transmits no message and remains in the MWI Activation Requested state.6.2.1.1.2DeactivationMWI_U02_001subclause 9.2.1mandatoryEnsure that the IUT in the MWI Idle state, to deactivate the MWI supplementary service,transmits a FACILITY message, including a Facility information element with a MWIDeactivate invokecomponent and enters the MWI Deactivation Requested state.MWI_U02_002subclause 9.2.1mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return result component,transmits no message and enters the MWI Idle state.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)11MWI_U02_003subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value "notSubscribed",transmits no message and enters the MWI Idle state.MWI_U02_004subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"invalidReceivingUserNr",transmits no message and enters the MWI Idle state.MWI_U02_005subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"supplementaryServiceInteractionNotAllowed",transmits no message and enters the MWI Idle state.MWI_U02_006subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value "resourceUnavailable",transmits no message and enters the MWI Idle state.MWI_U02_007subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value "invalidServedUserNr",transmits no message and enters the MWI Idle state.MWI_U02_008subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"receivingUserNotSubscribed",transmits no message and enters the MWI Idle state.MWI_U02_009subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"controllingUserNotRegistered",transmits no message and enters the MWI Idle state.MWI_U02_010subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"indicationNotDelivered",transmits no message and enters the MWI Idle state.MWI_U02_011subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a reject component containing the invoke identifier,transmits no message and remains in the MWI Deactivation Requested state.6.2.1.2Receiving userSelection:IUT supports the receiving user procedures. PICS: R 4.2.6.2.1.2.1InvocationMWI_U03_001subclause 9.5mandatoryEnsure that the IUT in the Null call state U00, on receipt of a FACILITY message, including a Facility informationelement with a MWIIndicate invoke component (invocation in the immediate mode, activation),transmits no message and remains in the Null call state U00.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)12MWI_U03_002subclause 9.5mandatoryEnsure that the IUT in the Call initiated call state U01, on receipt of a FACILITY message, including a Facilityinformation element with a MWIIndicate invoke component (invocation in the deferred mode, activation),transmits no message and remains in the Call initiated call state U01.MWI_U03_003subclause 9.5mandatoryEnsure that the IUT in the Call initiated call state U00, on receipt of a FACILITY message, including a Facilityinformation element with a MWIIndicate invoke component containing a "numberOfMessages" parameter with thevalue 0 (invocation in the immediate mode, deactiv0ation),transmits no message and remains in the Call initiated call state U00.6.2.2T reference point (private ISDN)Selection:IUT supports the T reference point procedures. PICS: R 3.2.6.2.2.1Controlling userSelection:IUT supports the controlling user procedures. PICS: R 4.1.6.2.2.1.1ActivationMWI_U04_001subclause 10.1.1mandatoryEnsure that the IUT in the Null call state U00 and in the MWI Idle state, to activate the MWI supplementary service,transmits a REGISTER message, including a Facility information element with a MWIActivate invokecomponent and enters the Bearer Independent Transport call state U31 and the MWI Activation Requested state.MWI_U04_002subclause 10.1.1mandatoryEnsure that the IUT in the Bearer Independent Transport call state U31 and in the MWI Activation Requested state, onreceipt of a RELEASE message including a Facility information element with a MWIActivate return result component,transmits a RELEASE COMPLETE message and enters the Null call state U00 and the MWI Idle state.MWI_U04_003subclause 10.1.2mandatoryEnsure that the IUT in the Bearer Independent Transport call state U31 and in the MWI Activation Requested state, onreceipt of a RELEASE message, including a Facility information element with a MWIActivate return error componentcontaining the error value "invalidReceivingUserNr",transmits a RELEASE COMPLETE message and enters the Null call state U00 and the MWI Idle state.MWI_U04_004subclause 10.1.2mandatoryEnsure that the IUT in the Bearer Independent Transport call state U31 and in the MWI Activation Requested state, onreceipt of a RELEASE message, including a Facility information element with a MWIActivate return error component
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Message Waiting Indication (MWI) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 3: Test Suite Structure and Test Purposes (TSS&TP) 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 745-3 Version 1.2.4SIST EN 300 745-3:2000en01-april-2000SIST EN 300 745-3:2000SLOVENSKI
STANDARD
SIST EN 300 745-3:2000
EN 300 745-3 V1.2.4 (1998-09)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Message Waiting Indication (MWI) supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 3: Test Suite Structure and Test Purposes (TSS&TP)specification for the userSIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)2ReferenceDEN/SPS-05069-3 (6wcr0iqo.PDF)KeywordsISDN, DSS1, supplementary service, MWI,testing, TSS&TP, 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 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)3ContentsIntellectual Property Rights.4Foreword.41Scope.52Normative references.53Definitions.63.1Definitions related to conformance testing.63.2Definitions related to EN 300 745-1.64Abbreviations.75Test Suite Structure (TSS).76Test Purposes (TP).76.1Introduction.76.1.1TP naming convention.86.1.2Source of TP definition.86.1.3TP structure.86.1.4Test strategy.96.2User TPs for MWI.96.2.1S/T.96.2.1.1Controlling user.96.2.1.1.1Activation.96.2.1.1.2Deactivation.106.2.1.2Receiving user.116.2.1.2.1Invocation.116.2.2T reference point (private ISDN).126.2.2.1Controlling user.126.2.2.1.1Activation.126.2.2.1.2Deactivation.136.2.2.2Receiving user.146.2.2.2.1Activation.146.2.2.2.2Deactivation.167Compliance.178Requirements for a comprehensive testing service.17History.18SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)4Intellectual 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.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 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) Message Waiting Indication (MWI)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".National transposition datesDate of adoption of this EN:18 September 1998Date of latest announcement of this EN (doa):31 December 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 June 1999Date of withdrawal of any conflicting National Standard (dow):30 June 1999SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)51ScopeThis third part of EN 300 745 specifies the Test Suite Structure and Test Purposes (TSS&TP) for the User side of theT reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [7]) ofimplementations conforming to the stage three standard for the Message Waiting Indication (MWI) supplementaryservice for the pan-European Integrated Services Digital Network (ISDN) by means of the Digital Subscriber SignallingSystem No. one (DSS1) protocol, EN 300 745-1 [1].A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol ImplementationeXtra Information for Testing (PIXIT) proforma based on the present document. Other parts specify the TSS&TP andthe ATS and partial PIXIT proforma for the Network side of the T reference point or coincident S and T reference pointof implementations conforming to EN 300 745-1 [1].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 745-1 (V1.2): "Integrated Services Digital Network (ISDN); Message Waiting Indication(MWI) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 1: Protocol specification".[2]EN 300 745-2 (V1.2): "Integrated Services Digital Network (ISDN); Message Waiting Indication(MWI) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification".[3]ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 1: General concepts".[4]ISO/IEC 9646-2 (1994): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 2: Abstract test suite specification".[5]ISO/IEC 9646-3 (1992): "Information technology - Open Systems Interconnection - Conformancetesting methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)".[6]EN 300 196-1 (V1.2): "Integrated Services Digital Network (ISDN); Generic functional protocolfor the support of supplementary services; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 1: Protocol specification".[7]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".[8]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]".[9]ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)6[10]CCITT Recommendation E.164 (1991): "Numbering plan for the ISDN era".[11]ITU-T Recommendation I.210 (1993): "Principles of the telecommunication services supported byan ISDN and the means to describe them".3DefinitionsFor the purposes of the present document, the following definitions apply:3.1Definitions related to conformance testingabstract test case: Refer to ISO/IEC 9646-1 [3].Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3].active test: A test case where the Implementation Under Test (IUT) is required to send a particular message, but not inreaction to a received message. This would usually involve the use of PIXIT information to see how this message can begenerated and quite often is specified in an ATS using an implicit send event.Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [3].implicit send event: Refer to ISO/IEC 9646-3 [5].lower tester: Refer to ISO/IEC 9646-1 [3].passive test: A test case where the IUT is required to respond to a protocol event (e.g. received message) with anotherprotocol event (e.g. send message) which normally does not require any special operator intervention as associated withthe implicit send event.point of control and observation: Refer to ISO/IEC 9646-1 [3].Protocol Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 [3].PICS proforma: Refer to ISO/IEC 9646-1 [3].Protocol Implementation eXtra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 [3].PIXIT proforma: Refer to ISO/IEC 9646-1 [3].system under test: Refer to ISO/IEC 9646-1 [3].Test Purpose (TP): Refer to ISO/IEC 9646-1 [3].3.2Definitions related to EN 300 745-1component: See EN 300 196-1 [6], subclause 11.2.2.1.Dummy call reference: See EN 300 403-1 [8], subclause 4.3.Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [9], definition 308.ISDN number: A number conforming to the numbering and structure specified in CCITT Recommendation E.164 [10].invoke component: See EN 300 196-1 [6], subclause 11.2.2.1.return error component: See EN 300 196-1 [6], subclause 11.2.2.1.return result component: See EN 300 196-1 [6], subclause 11.2.2.1.service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201.supplementary service: See ITU-T Recommendation I.210 [11], subclause 2.4.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)7S/T: The DSS1 protocol entity at the User side of the user-network interface where a coincident S and T reference pointapplies.T: The DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is aPrivate ISDN).receiving user: The user that receives the message waiting indication.controlling user: The user that activates and deactivates the message waiting indication.4AbbreviationsFor the purposes of the present document, the following abbreviations apply:ATMAbstract Test MethodATSAbstract Test SuiteISDNIntegrated Services Digital NetworkIUTImplementation Under TestMWIMessage Waiting IndicationPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureU00Null call stateU01Call Initiated call stateU19Release Request call stateU31Bearer Independent Transport call state5Test Suite Structure (TSS)S/TGroup·Controlling User·activationU01·deactivationU02·Receiving User·invocationU03T (private ISDN)·Controlling User·activationU04·deactivationU05·Receiving User·activationU06·deactivationU07Figure 1: Test suite structure6Test Purposes (TP)6.1IntroductionFor each test requirement a TP is defined.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)86.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional referencesare added to identify the actual test suite and whether it applies to the network or the user (see table 1).Table 1: TP identifier naming convention schemeIdentifier:__=supplementary service: "MWI"=type of IUT:UUserNNetwork=group2 digit field representing group reference according to TSS=sequential number(001-999)6.1.2Source of TP definitionThe TPs are based on EN 300 745-1 [1].6.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPsmore readable and checkable. A particular structure has been used and this is illustrated in table 2. This table should beread in conjunction with any TP, i.e. use a TP as an example to fully understand the table.Table 2: Structure of a single TP for MWITP partTextExampleHeader tabsee table 1 tabsubclause 0.0.0 CR.mandatory, optional (see note 1)StimulusEnsure that the IUT in the or U10 etc. see below for message structurereceiving a XXXX messageor to request a .Reactionsends, saves, does, etc.using en bloc sending, .if the action is sending see below for message structure, etc.and remains in the same stateor and enters state Messagestructuremessage containing aSETUP, FACILITY, CONNECT, .a) information element withb) a encoded as or including and back to a or b,Bearer capability, Facility, .NOTE 1:Mandatory TP are always applicable. Optional TPs are applicable according to the configuration optionsof the IUT. If the configuration option is covered by a PICS item, a selection criteria is indicated, else theselection of the corresponding test cases will depend on test suite parameters (PIXIT) in the ATS.NOTE 2:Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from oneTP to the next.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)96.1.4Test strategyAs the base standard EN 300 745-1 [1] contains no explicit requirements for testing, the TPs were generated as a resultof an analysis of the base standard and the PICS specification EN 300 745-2 [2]. The criteria applied include thefollowing:-only the requirements from the point of view of the T or coincident S and T reference point are considered;-whether or not a test case can be built from the TP is not considered.6.2User TPs for MWIAll PICS items referred to in this subclause are as specified in EN 300 745-2 [2] unless indicated otherwise by anothernumbered reference.Unless specified:-The messages indicated are valid and contain at least the mandatory information elements and possibly optionalinformation elements.-The information elements indicated are valid and contain at least the mandatory parameters and possibly optionalparameters.-The FACILITY messages are transmitted using the point-to-point connectionless bearer independent transportmechanism (dummy call reference, DL-DATA-REQUEST) as specified in EN 300 196-1 [6], subclause 8.3.2.2.Where the broadcast connectionless bearer independent transport mechanism applies (dummy call reference,DL-UNIT DATA-REQUEST), the indication of the corresponding subclause of EN 300 196-1 [6] is given (i.e.subclause 8.3.2.4).6.2.1S/TSelection:IUT supports the S and T reference point procedures. PICS: R 3.1.6.2.1.1Controlling userSelection:IUT supports the controlling user procedures. PICS: R 4.1.6.2.1.1.1ActivationMWI_U01_001subclause 9.1.1mandatoryEnsure that the IUT in the MWI Idle state, to activate the MWI supplementary service,transmits a FACILITY message, including a Facility information element with a MWIActivate invoke componentand enters the MWI Activation Requested state.MWI_U01_002subclause 9.1.1mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return result component,transmits no message and enters the MWI Idle state.MWI_U01_003subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "notSubscribed",transmits no message and enters the MWI Idle state.MWI_U01_004subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "invalidReceivingUserNr",transmits no message and enters the MWI Idle state.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)10MWI_U01_005subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"supplementaryServiceInteractionNotAllowed",transmits no message and enters the MWI Idle state.MWI_U01_006subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "resourceUnavailable",transmits no message and enters the MWI Idle state.MWI_U01_007subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "invalidServedUserNr",transmits no message and enters the MWI Idle state.MWI_U01_008subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"receivingUserNotSubscribed",transmits no message and enters the MWI Idle state.MWI_U01_009subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"controllingUserNotRegistered",transmits no message and enters the MWI Idle state.MWI_U01_010subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value "indicationNotDelivered",transmits no message and enters the MWI Idle state.MWI_U01_011subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"maxNumOfControllingUsersReached",transmits no message and enters the MWI Idle state.MWI_U01_012subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIActivate return error component containing the error value"maxNumOfActiveInstancesReached",transmits no message and enters the MWI Idle state.MWI_U01_013subclause 9.1.2mandatoryEnsure that the IUT in the MWI Activation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a reject component containing the invoke identifier,transmits no message and remains in the MWI Activation Requested state.6.2.1.1.2DeactivationMWI_U02_001subclause 9.2.1mandatoryEnsure that the IUT in the MWI Idle state, to deactivate the MWI supplementary service,transmits a FACILITY message, including a Facility information element with a MWIDeactivate invokecomponent and enters the MWI Deactivation Requested state.MWI_U02_002subclause 9.2.1mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return result component,transmits no message and enters the MWI Idle state.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)11MWI_U02_003subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value "notSubscribed",transmits no message and enters the MWI Idle state.MWI_U02_004subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"invalidReceivingUserNr",transmits no message and enters the MWI Idle state.MWI_U02_005subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"supplementaryServiceInteractionNotAllowed",transmits no message and enters the MWI Idle state.MWI_U02_006subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value "resourceUnavailable",transmits no message and enters the MWI Idle state.MWI_U02_007subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value "invalidServedUserNr",transmits no message and enters the MWI Idle state.MWI_U02_008subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"receivingUserNotSubscribed",transmits no message and enters the MWI Idle state.MWI_U02_009subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"controllingUserNotRegistered",transmits no message and enters the MWI Idle state.MWI_U02_010subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a MWIDeactivate return error component containing the error value"indicationNotDelivered",transmits no message and enters the MWI Idle state.MWI_U02_011subclause 9.2.2mandatoryEnsure that the IUT in the MWI Deactivation Requested state, on receipt of a FACILITY message, including a Facilityinformation element with a reject component containing the invoke identifier,transmits no message and remains in the MWI Deactivation Requested state.6.2.1.2Receiving userSelection:IUT supports the receiving user procedures. PICS: R 4.2.6.2.1.2.1InvocationMWI_U03_001subclause 9.5mandatoryEnsure that the IUT in the Null call state U00, on receipt of a FACILITY message, including a Facility informationelement with a MWIIndicate invoke component (invocation in the immediate mode, activation),transmits no message and remains in the Null call state U00.SIST EN 300 745-3:2000
ETSIEN 300 745-3 V1.2.4 (1998-09)12MWI_U03_002subclause 9.5mandatoryEnsure that the IUT in the Call initiated call state U01, on receipt of a FACILITY message, including a Facilityinformation element with a MWIIndicate invoke component (invocation in the deferred mode, activation),transmits no message and remains in the Call initiated call state U01.MWI_U03_003subclause 9.5mandatoryEnsure that the IUT in the Call initiated call state U00, on receipt of a FACILITY message, including a Facilityinformation element with a MWIIndicate invoke component containing a "numberOfMessages" parameter with thevalue 0 (invocation in the immediate mode, deactiv0ation),transmits no message and remains in the Call initiated call state U00.6.2.2T reference point (private ISDN)Selection:IUT supports the T reference point procedures. PICS: R 3.2.6.2.2.1Controlling userSelection:IUT supports the controlling user procedures. PICS: R 4.1.6.2.2.1.1ActivationMWI_U04_001subclause 10.1.1mandatoryEnsure that the IUT in the Null call state U00 and in the MWI Idle state, to activate the MWI supplementary service,transmits a REGISTER message, including a Facility information element with a MWIActivate invokecomponent and enters the Bearer Independent Transport call state U31 and the MWI Activation Requested state.MWI_U04_002subclause 10.1.1mandatoryEnsure that the IUT in the Bearer Independent Transport call state U31 and in the MWI Activation Requested state, onreceipt of a RELEASE message including a Facility information element with a MWIActivate return result component,transmits a RELEASE COMPLETE message and enters the Null call state U00 and the MWI Idle state.MWI_U04_003subclause 10.1.2mandatoryEnsure that the IUT in the Bearer Independent Transport call state U31 and in the MWI Activation Requested state, onreceipt of a RELEASE message, including a Facility information element with a MWIActivate return error componentcontaining the error value "invalidReceivingUserNr",transmits a RELEASE COMPLETE message and enters the Null call state U00 and the MWI Idle state.MWI_U04_004subclause 10.1.2mandatoryEnsure that the IUT in the Bearer Independent Transport call state U31 and in the MWI Activation Requested state, onreceipt of a RELEASE message, including a Facility information element with a MWIActivate return error c
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.