SIST EN 300 286-5 V1.4.1:2005
(Main)Integrated Services Digital Network (ISDN); User-to-User Signalling (UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network
Integrated Services Digital Network (ISDN); User-to-User Signalling (UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network
This version contains some technical comments provided by Italtel.
Digitalno omrežje z integriranimi storitvami (ISDN) – Dopolnilna storitev: meduporabniška signalizacija (UUS) – Protokol digitalne naročniške signalizacije št. 1 (DSS1) – 5. del: Zgradba preskušalnega niza in namen preskušanja (TSS&TP) – 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.VWRULWHYIntegrated Services Digital Network (ISDN); User-to-User Signalling (UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol; Part 5: Test Suite Structure and Test Purposes (TSS&TP) 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 286-5 Version 1.4.1SIST EN 300 286-5 V1.4.1:2005en01-januar-2005SIST EN 300 286-5 V1.4.1:2005SLOVENSKI
STANDARD
SIST EN 300 286-5 V1.4.1:2005
ETSI EN 300 286-5 V1.4.1 (2003-01)European Standard (Telecommunications series) Integrated Services Digital Network (ISDN);User-to-User Signalling (UUS) supplementary service;Digital Subscriber Signalling System No. one (DSS1) protocol;Part 5: Test Suite Structure and Test Purposes (TSS&TP)specification for the network
SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 2
Reference REN/SPAN-130308-1 Keywords DSS1, ISDN, network, supplementary service, TSS&TP, UUS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88
Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editor@etsi.org 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 2003. All rights reserved.
DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 3
Contents Intellectual Property Rights.4 Foreword.4 1 Scope.5 2 References.5 3 Definitions and abbreviations.6 3.1 Definitions related to conformance testing.6 3.2 Definitions related to EN 300 286-1.6 3.3 Abbreviations.7 4 Test Suite Structure (TSS).8 5 Test Purposes (TP).9 5.1 Introduction.9 5.1.1 TP naming convention.9 5.1.2 Source of TP definition.9 5.1.3 TP structure.9 5.1.4 Test strategy.10 5.1.5 Test of point-to-multipoint configurations.10 5.2 Network TPs for UUS.10 5.2.1 Served user.11 5.2.1.1 Service 1.11 5.2.1.1.1 Activation.11 5.2.1.1.2 Invocation.12 5.2.1.2 Service 2.14 5.2.1.2.1 Activation.14 5.2.1.2.2 Invocation.15 5.2.1.3 Service 3.16 5.2.1.3.1 Activation.16 5.2.1.3.2 Invocation.18 5.2.1.3.3 Flow control.19 5.2.2 Remote user.20 5.2.2.1 Service 1.20 5.2.2.1.1 Activation.20 5.2.2.1.2 Invocation.31 5.2.2.2 Service 2.37 5.2.2.2.1 Activation.37 5.2.2.2.2 Invocation.40 5.2.2.3 Service 3.42 5.2.2.3.1 Activation.42 5.2.2.3.2 Invocation.48 5.2.2.3.3 Flow control.49 6 Compliance.51 7 Requirements for a comprehensive testing service.51 Annex A (informative): Change record.52 A.1 Changes between EN 300 286-5 V1.2.4 and 1.3.6.52 A.2 Changes between ETS 300 286-5 Edition 1 and EN 300 286-5 V1.2.4.52 A.3 Changes between EN 300 286-5 V1.3.6 and
EN 300 286-5 V1.4.1.52 History.53
SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 4
Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://webapp.etsi.org/IPR/home.asp). All published ETSI deliverables shall include information which directs the reader to the above source of information. Foreword This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services and Protocols for Advanced Networks (SPAN). The present document is part 5 of a multi-part standard covering the Integrated Services Digital Network (ISDN); User-to-User Signalling (UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol, 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 dates Date of adoption of this EN: 27 December 2002 Date of latest announcement of this EN (doa): 31 March 2003 Date of latest publication of new National Standard or endorsement of this EN (dop/e):
30 September 2003 Date of withdrawal of any conflicting National Standard (dow): 30 September 2003
SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 5
1 Scope The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the Network side of the T reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [7]) of implementations conforming to the stage three standard for the User-to-User Signalling (UUS) 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 286-1 [1]. A further part of the present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the present document. 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 EN 300 286-1 [1]. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. [1] ETSI EN 300 286-1: "Integrated Services Digital Network (ISDN); User-to-User Signalling (UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 1: Protocol specification". [2] ETSI EN 300 286-2: "Integrated Services Digital Network (ISDN); User-to-User Signalling (UUS) supplementary service; Digital Subscriber Signalling System No. one (DSS1) protocol;
Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification". [3] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [4] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification". [5] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)". [6] ETSI EN 300 196-1: "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". [7] ITU-T Recommendation I.411: "ISDN user-network interfaces - Reference configurations". [8] ETSI EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. 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: "Vocabulary of terms for ISDNs". [10] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". [11] ITU-T Recommendation I.210: "Principles of the telecommunication services supported by an ISDN and the means to describe them". SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 6
[12] ETSI EN 300 403-3: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;
Part 3: Protocol Implementation Conformance Statement (PICS) proforma specification". 3 Definitions and abbreviations For the purposes of the present document, the following terms and definitions apply. 3.1 Definitions related to conformance testing Abstract Test Case (ATC): Refer to ISO/IEC 9646-1 [3]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3]. active test: test case where the IUT is required to send a particular message, but not in reaction to a received message. This would usually involve the use of PIXIT information to see how this message can be generated 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 (LT): Refer to ISO/IEC 9646-1 [3]. passive test: test case where the IUT is required to respond to a protocol event (e.g. received message) with another protocol event (e.g. send message) which normally does not require any special operator intervention as associated with the implicit send event Point of Control and Observation (PCO): 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 (SUT): Refer to ISO/IEC 9646-1 [3]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [3]. 3.2 Definitions related to EN 300 286-1 call reference: See EN 300 403-1 [8], clause 4.3. called user: user at the destination side of the call calling user: user at the origination side of the call component: See EN 300 196-1 [6], clause 11.2.2.1. Integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [9], definition 308. ISDN number: number conforming to the numbering and structure specified in ITU-T Recommendation E.164 [10] invoke component: See EN 300 196-1 [6], clause 11.2.2.1. network: DSS1 protocol entity at the Network side of the user-network interface where a T reference point or coincident S and T reference point applies SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 7
network (S/T): DSS1 protocol entity at the Network side of the user-network interface where a coincident S and T reference point applies network (T): DSS1 protocol entity at the Network side of the user-network interface where a T reference point applies (Network connected to Private ISDN) return error component: See EN 300 196-1 [6], clause 11.2.2.1. return result component: See EN 300 196-1 [6], clause 11.2.2.1. served user: user who invokes the UUS supplementary service. The served user is the calling user except for service 3 where the called user, as a network option can invoke the service 3 in the Active call state. service; telecommunication service: See ITU-T Recommendation I.112 [9], definition 201. supplementary service: See ITU-T Recommendation I.210 [11], clause 2.4. 3.3 Abbreviations For the purposes of the present document, the following abbreviations apply: ATM Abstract Test Method ATS Abstract Test Suite CES Connection Endpoint Suffix CR Call Reference ISDN Integrated Services Digital Network IUT Implementation Under Test N00 Null call state N01 Call Initiated call state N02 Overlap Sending call state N03 Outgoing Call Proceeding call state N04 Call Delivered call state N06 Call Present call state N07 Call Received call state N08 Connect Request call state N09 Incoming Call Proceeding call state N10 Active call state N11 Disconnect Request call state N12 Disconnect Indication call state N19 Release Request call state N25 Overlap Receiving call state PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementation eXtra Information for Testing TP Test Purpose TSS Test Suite Structure UUS User-to-User Signalling SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 8
4 Test Suite Structure (TSS) Served user Group · Service 1 · activation · implicit (01) · explicit (02) · invocation · during call establishment (03) · during call clearing · initiated by the calling user (04) · initiated by the called user (05) · Service 2 · activation (06) · invocation (07) · Service 3 · activation · during call establishment (08) · during active call state (09) · invocation (10) · flow control (11)
Remote user Group - Service 1 - activation - implicit (12) - explicit (13) - invocation - during call establishment (14) - during call clearing - initiated by the calling user (15) - initiated by the called user (16) - Service 2 - activation (17) - invocation (18) SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 9
- Service 3 - activation - during call establishment (19) - during active call state (20) - invocation (21) - flow control (22)
NOTE: Numbers in brackets represent group numbers and are used in TP identifiers.
Figure 1: Test suite structure 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming convention TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references are 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 scheme
Identifier: __
= supplementary service: e.g. "UUS"
= type of IUT: U User N Network
= group 2 digit field representing group reference according to TSS
= sequential number (001-999)
5.1.2 Source of TP definition The TPs are based on EN 300 286-1 [1]. 5.1.3 TP structure Each TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPs more readable and checkable. A particular structure has been used and this is illustrated in table 2. This table should be read in conjunction with any TP, i.e. use a TP as an example to fully understand the table. SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 10 Table 2: Structure of a single TP for UUS TP part Text Example Header tab see table 1
tab Clause X.X.X
tab valid, invalid, inopportune
CR. mandatory, optional, conditional Stimulus Ensure that the IUT in the
N10 etc.
see below for message structure receiving a XXXX message
or to request a . Reaction
sends, saves, does, etc.
using en bloc sending, .
if the action is sending
see below for message structure , etc. and remains in the same state or and enters state
Message structure message containing a SETUP, FACILITY, CONNECT, .
a) information element with b) a encoded as or including and back to a or b, Bearer capability, Facility, . NOTE: Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from one TP to the next.
5.1.4 Test strategy As the base standard EN 300 286-1 [1] contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the PICS specification EN 300 286-2 [2]. The criteria applied include the following: - 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. 5.1.5 Test of point-to-multipoint configurations In the case of a point-to-multipoint configuration several terminals may be attached to one basic access interface. Each terminal will use a different Connection Endpoint Suffix (CES). To reflect this in the TPs, the CES for which a message is received or sent (e.g. ".on receipt of an ALERTING message for CES1.") is named explicitly where this clarification is needed. 5.2 Network TPs for UUS All PICS items referred to in this clause are as specified in EN 300 286-2 [2] unless indicated otherwise by another numbered reference. SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 11 5.2.1 Served user 5.2.1.1 Service 1 Selection: Does the IUT support service 1? PICS: MC 2.1. 5.2.1.1.1 Activation 5.2.1.1.1.1 Implicitly requested UUS_N01_001 clause 9.1.1.1.1 valid mandatory Ensure that the IUT, in the call state N00, receiving a valid SETUP message with a User-user information element without user information and the network can accept the request,
accepts the message (resulting in the inclusion of the same User-user information element in the SETUP message sent to the remote user) and enters the call state N01. UUS_N01_002 clause 9.1.1.1.2 invalid mandatory Ensure that the IUT, in the call state N00, receiving a valid SETUP message with a User-user information element without user information and the network cannot accept the request,
discards the User-user information element (resulting in the sending of a SETUP message without User-user information element to the remote user) and enters the call state N01. UUS_N01_003 clause 9.1.1.1.2 invalid mandatory Ensure that the IUT, in the call state N00, receiving a valid SETUP message with a User-user information element of less than 3 octets in length,
discards the User-user information element (resulting in the sending of a SETUP message without User-user information element to the remote user) and enters the call state N01. 5.2.1.1.1.2 Explicitly requested Selection: Does the IUT support the explicit request of service 1? PICS: MC 2.1.2. UUS_N02_001 clause 9.1.1.2.1 valid mandatory Ensure that the IUT, in the call state N00 receiving a valid SETUP message with a Facility information element including a UserUserService invoke component indicating service 1 preferred,
accepts the message (resulting in the inclusion of the same Facility information element in the SETUP message sent to the remote user) and enters the call state N01. UUS_N02_002 clause 9.1.1.2.1 valid mandatory Ensure that the IUT, in the call state N00 receiving a valid SETUP message with a Facility information element including a UserUserService invoke component indicating service 1 required,
accepts the message (resulting in the inclusion of the same Facility information element in the SETUP message sent to the remote user) and enters the call state N01. UUS_N02_003 clause 9.1.1.2.2 inopportune mandatory Ensure that the IUT, in the call state N00 receiving a SETUP message with a Facility information element including a UserUserService invoke component indicating service 1 and an incompatible bearer capability,
sends a RELEASE COMPLETE message without UserUserService return error component and enters the call state N00. UUS_N02_004 clause 9.1.1.2.2 inopportune mandatory Ensure that the IUT, in the call state N00 receiving a valid SETUP message with a Facility information element including a UserUserService invoke component indicating service 1 preferred and the resources are not available,
continues with normal call handling and includes a UserUserService return error component with the value "rejectedByNetwork" in a valid SETUP ACKNOWLEDGE, CALL PROCEEDING, PROGRESS, ALERTING or CONNECT message. SIST EN 300 286-5 V1.4.1:2005
ETSI ETSI EN 300 286-5 V1.4.1 (2003-01) 12 UUS_N02_005 clause 9.1.1.2.2 inopportune mandatory Ensure that the IUT, in the call state N00 receiving a valid SETUP message with a Facility information element including a UserUserService invoke component indicating service 1 preferred and the service 1 is not subscribed to,
continues with normal call handling and includes a UserUserService return error component with the value "rejectedByNetwork" in a valid SETUP ACKNOWLEDGE, CALL PROCEEDING, PROGRESS, ALERTING or CONNECT message. UUS_N02_006 clause 9.1.1.2.2 inopportune mandatory Ensure that the IUT, in the call state N00 receiving a valid SETUP message with a Facility information element including a UserUserService invoke component indicating service 1 required and the resources are not available,
sends a DISCONNECT or RELEASE COMPLETE message, with cause value #47 "resources unavailable", including a UserUserService return error component with the value "rejectedByNetwork" and enters the call state N12 or N00. 5.2.1.1.2 Invocation 5.2.1.1.2.1 During call establishment UUS_N03_001 clause 9.1.2.1.1 valid mandatory Ensure that the IUT, in the call state N00, receiving a valid SETUP message including a User-user information element with user information,
accepts the message (resulting in the sending of a SETUP message to the remote user with the same User-user information element) sends a SETUP ACKNOWLEDGE or a CALL PROCEEDING message and enters the call state N02 or N03. NOTE: This TP corresponds to the invocation of service 1 simultaneously with the activation by the same User-user information element. UUS_N03_002 clause 9.1.2.1.1 valid mandatory Ensure that the IUT, in the call state N00, receiving a valid SETUP message including a UserUserService invoke component indicating service 1 and a User-user information element with user information,
accepts the message (resulting in the sending of a SETUP message to the remote user with the same UserUserService invoke component and User-user information element) sends a SETUP ACKNOWLEDGE or a CALL PROCEEDING message and enters the call state N02 or N03. UUS_N03_003 clause 9.1.2.1.2 invalid mandatory Ensure that the IUT, in the call state N00, receiving a valid SETUP message including a User-user information element with user information with an overall length exceeding 131 octets,
discards the User-user information element (resulting in the sending of a SETUP message without User-user information element to the remote user) sends a SETUP ACKNOWLEDGE or a CALL PROCEEDING message and optionally sends a STATUS message with cause value #43 "access information discarded". 5.2.1.1.2.2 During call clearing 5.2.1.1.2.2.1 Clearing initiated by the calling user UUS_N04_002 clause 9.1.2.2.1.a valid mandatory Ensure that the IUT, in the call state N03 and in the service 1 active state, receiving a DISCONNECT message with a User-user informat
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.