1、ETSI EN 300 196-5 1.2.1 (2001-11) European Sfandard (Telecommunicafions series) Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. one (DSSI) protocol; Part 5: Test Suite Structure and Test Purpo
2、ses (TSS Essential, orpotentially Essential, IPRs notlJied to ETSI in respect ofETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by E
3、TSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR O00 3 14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This European Standard (Telecommunications series) has been produced by ETSI Te
4、chnical Committee Services and Protocols for Advanced Networks (SPAN). The present document is part 5 of a multi-part deliverable covering the Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. o
5、ne (DSS1) protocol; as described below: Part 1 : “Protocol specification“; Part 2: Part 3: Part 4: “Protocol Implementation Conformance Statement (PICS) proforma specification“; “Test Suite Structure and Test Purposes (TSS “Abstract Test Suite (ATS) and partial Protocol Implementation extra Informat
6、ion for Testing (PIXIT) proforma specification for the user“; “Test Suite Structure and Test Purposes (TSS “Abstract Test Suite (ATS) and partial Protocol Implementation extra Information for Testing (PIXIT) proforma specification for the network“. Part 5: Part 6: National transposition dates Date o
7、f adoption of this EN: Date of latest announcement of this EN (doa): Date of latest publication of new National Standard or endorsement of this EN (dop/e): Date of withdrawal of any conflicting National Standard (dow): 9 November 200 1 28 February 2002 3 1 August 2002 3 1 August 2002 ETSI 6 ETSI EN
8、300 196-5 VI .2.1 (2001-1 1) 1 Scope The present document specifies the Test Suite Structure and Test Purposes (TSS Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS 1) protocol; Part 1 : Protocol specification“. ETSI EN 300 196-
9、2: “Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS 1) protocol; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification“. ISO/IEC 9646- 1 : “Information t
10、echnology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1 : General concepts“. ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract test suite specification“. ITU-T Recommenda
11、tion 1.41 1 (1 993): “ISDN user-network interfaces - Reference configurations“. 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
12、 ITU-T Recommendation Q.93 1 (1993), modified“. 21 31 41 51 61 NOTE: There are no clause numbering in EN 300 403-1; the clause numbers used in the present document actually refer to the clause numbers of ITU-T Recommendation Q.93 1. 71 SI ITU-T Recommendation I. 112 (1993): “Vocabulary and terms for
13、 ISDNs“. ITU-T Recommendation 1.2 10 (1993): “Principles of telecommunication services supported by an ISDN and the means to describe them“. 91 ITU-T Recommendation X.209 (1988): “Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN. i)“. ETSI 7 ETSI EN 300 196-5 VI .2.1 (2001
14、-1 1) lo1 ITU-T Recommendation X.690: “Information technology - ASN. 1 encoding rules - Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)“. ETSI EN 301 313-3: “Integrated Services Digital Network (ISDN) and Broadband Integrated Service
15、s Digital Network (B-ISDN); Generic Addressing and Transport (GAT); Part 3: Test Suite Structure and Test Purposes (TSS telecommunication service: See ITU-T Recommendation I. 112 7, definition 201. supplementary service: See ITU-T Recommendation 1.210 SI, clause 2.4. 4 Abbreviations For the purposes
16、 of the present document, the following abbreviations apply: ATM ATS CR DSSl GFP ISDN IUT NO0 NO3 NO4 NO7 NO 8 NO9 N10 N12 N19 N25 NCICS PICS PIXIT TP TSS u1 Abstract Test Method Abstract Test Suite Call Reference Digital Subscriber Signalling System No. one Generic Functional Protocol Integrated Se
17、rvices Digital Network Implementation Under Test Null call state Outgoing Call Proceeding call state Call Delivered call state Call Received call state Connect Request call state Incoming Call Proceeding call state Active call state Disconnect Indication call state Release Request call state Overlap
18、 Receiving call state Networked Call Independent Signalling Connection Protocol Implementation Conformance Statement Protocol Implementation extra Information for Testing Test Purpose Test Suite Structure Unnumbered Information ETSI 9 ETSI EN 300 196-5 VI .2.1 (2001-1 1) 5 General Test Suite Structu
19、re (TSS) Generic Functional Protocol - Network I I I I I I I I Clause 9 Clause 10 Clause 11 Annex D Annex E Clause 8 Clauses 1-6 Clause 7 Figure 1: Test suite structure More detailed TSS for each group (branch) are contained in separate clauses. 6 TSS whether or not a test case can be built from the
20、 TP is not considered. 6.1.5 Test of call states Many TPs include a reference to the IUTs final call state after the realization of the TP. In these cases the TP includes the requirement to ensure that the IUT has entered this particular final call state. Ensuring that the IUT is in a particular cal
21、l state shall be realized by following the procedures described in clause 5.8.10 of EN 300 403-1 6. According to these procedures, the IUT on receipt of a STATUS ENQUIRY message, shall respond with a STATUS message indicating, in the third octet of the Call state information element, the current cal
22、l state of the IUT. This exchange of messages is not mentioned explicitly in each TP but is considered to be implicit in the reference to the final call state. This way of phrasing the TPs has been used to avoid over-complicating the text and structure of the TPs and to improve the readability. NOTE
23、: Timer T322 is associated with this STATUS ENQUIRYBTATUS procedure. ETSI 11 ETSI EN 300 196-5 VI .2.1 (2001-1 1) 6.2 Network TSS - - check supplementary service transport mechanism(s) supported and apply relevant TPs from clause 6.2.3.2.3; apply TP from clause 6.2.3.2.4. ETSI 25 Transport ETSI EN 3
24、00 196-5 VI .2.1 (2001-1 1) 6.2.3.2.2 Application of operations (clause 8.2) Table 3: Cross reference between transport mechanisms, call states, messages, call references and data links mechanism Bearer related pt-to-pt Bearer related broadcast pt-to-multipt Bearer independent Connection oriented po
25、int-to-point for local signalling clause 8.3.2.1 Bearer independent Connectionless point-to-point for local signalling clause call state message call reference N 00, 01, 02, 03,04, 06,07, call control message CR of an existing 08, 09, IO, 11, 12, 19, 25 FACILITY call N 00, 01, 02, 03, 04, 06, 07, ca
26、ll control message CR of an existing 08, 09, IO, 11, 12, 19, 25 FACILITY call N 00, 19, 31 REGISTER CR created FACILITY (call state 31 only) RELEASE RELEASE COMP STATUS (note) STATUS ENQ* N any state FACILITY dummy CR (I-frame) Bearer independent Connection oriented broadcast for local 18.3.2.2 Not
27、specified FACILITY (U I-frame) signalling dummy CR IBearer independent IN any state Connectionless broadcast for local I signalling Bearer independent INO, NI, N3, N6, N8, N9, Connection oriented pt-to-pt for general NI O, NI 9 signalling Bearer independent I Connection oriented Not used broad cast
28、for genera I (I-frame) data link dia point-to-point data link dia point-to-point data link dia broadcast data ink dia point-to-point D-link signalling NOTE: STATUS, STATUS ENQUIRY not used for transportation of components. 6.2.3.2.2.1 Invocation (clause 8.2.2.1) Selection: IUT supports use of the in
29、vocation procedure. PICS: SCn 2.1 GFP-N8-01-001 clause 8.2.2.1 Ensure that the IUT, in call state and in the state, to initiate an operation, sends a message with containing a Facility information element with a invoke component (via ) and enters the state. GFP-N8-01-002 clause 8.2.2.1 Ensure that t
30、he IUT, in call state and in the state receiving a message with containing a Facility information element with a invoke component (via ), enters I remains in call state and enters the state. ETSI 26 ETSI EN 300 196-5 VI .2.1 (2001-1 1) 6.2.3.2.2.2 Return result (clause 8.2.2.2) Selection: IUT suppor
31、ts use of the return result procedure. PICS: SCn 2.2 GFP-N8-02-001 clause 8.2.2.2 Ensure that the IUT, in call state and in the state, to transfer the result of a successfully performed operation, sends a message with containing a Facility information element with a return result component (via ), e
32、nters I remains in call state and enters the state. GFPN8-02-002 clause 8.2.2.2 Ensure that the IUT, in call state and in the state receiving a message with containing a Facility information element with a return result component (via ), enters I remains in call state and enters the state. 6.2.3.2.2
33、.3 Return error (clause 8.2.2.3) Selection: IUT supports use of the return error procedure. PICS: SCn 2.3 GFP-N8-03-001 clause 8.2.2.3 Ensure that the IUT, in call state and in the state, to transfer error information in the case of an unsuccessfully performed operation, sends a message with contain
34、ing a Facility information element with a return error component (via ), enters I remains in call state and enters the state. GFPN8-03-002 clause 8.2.2.3 Ensure that the IUT, in call state and in the state receiving a message with containing a Facility information element with a return error compone
35、nt (via ), enters I remains in call state and enters the state. 6.2.3.2.2.4 Reject (clause 8.2.2.4) Selection: IUT supports use of the reject procedure. PICS: SCn 2.4 GFP-N8-04-001 clause 8.2.2.4 Ensure that the IUT, in call state and in the state receiving a message with containing a Facility infor
36、mation element with a reject component not including an invoke identifier (via ), enters I remains in call state and enters the state. NOTE 1: The receipt of a reject component is dealt with according to the procedures defiied in the individual supplementary service ETSs. GFPN8-04-002 clause 8.2.2.4
37、 Ensure that the IUT, in call state and in the state receiving a message with containing a Facility information element with a reject component including a valid invoke identifier (via ), enters I remains in call state and enters the state. GFPN8-04-003 clause 8.2.2.4 Ensure that the IUT, in call st
38、ate and in the state detecting an error classified as general-problemKproblem code in a received message with containing a Facility information element with a component (via ), sends a message with containing a Facility information element with a reject component indicating general-problemKproblem c
39、ode and including an invoke identifier or including NULL (via ), enters I remains in call state and enters the state. NOTE 2: For a list of problem codes see EN 300 196-1 i, table 2 or table D.1. ETSI 27 ETSI EN 300 196-5 VI .2.1 (2001-1 1) GFPN8-04-004 clause 8.2.2.4 Ensure that the IUT, in call st
40、ate and in the state detecting an error classified as / in a received message with containing a Facility information element with a component (via ), sends a message with containing a Facility information element with a reject component indicating / and including a valid invoke identifier (via ), en
41、ters I remains in call state and enters the state. NOTE 3 : = invoke-problem, return-result-problem or return-error-problem. For a list of problem codes see EN 300 196-1 i, table 2 or table D.1. 6.2.3.2.3 Transport of components (clause 8.3) NOTE: Most TPs of clause 6.2.3.2.2 also test the procedure
42、s of clause 8.3 of EN 300 196-1 i. Only additional procedures related to clause 8.3 of EN 300 196-1 i, not already covered, are included below. 6.2.3.2.3.1 Bearer related transport (clause 8.3.1) Selection: IUT supports the bearer related supplementary services procedure. PICS: MCn 2.1 GFP-N8-05-001
43、 clause 8.3.1.1.2 Ensure that the IUT, in call state and in the state unable to process a invoke component, sends a message with containing a Facility information element with a component (via ), enters I remains in call state and enters the state or ignores the invocation. NOTE: = DISCONNECT, RELEA
44、SE, RELEASE COMPLETE, FACILITY = return error, reject 6.2.3.2.3.2 Bearer independent transport (clause 8.3.2) Selection: IUT supports the bearer independent supplementary services procedure. PICS: MCn 2.2. 6.2.3.2.3.2.1 Connection-oriented (clause 8.3.2.1) Selection: IUT supports the point-to-point
45、(bearer independent) connection-oriented transport mechanism. PICS: MCn 2.5. GFP-N8-06-001 clause 8.3.2.1.1.1 Ensure that the IUT, in call state NO0 in order to establish a connection towards the responder, sends a REGISTER message and enters the Bearer independent Transport call state N3 1, GFPN8-0
46、6-002 clause 8.3.2.1.1.2 Ensure that the IUT, in call state and in the state receiving a REGISTER message with a call reference in use, ignores the message and sends a STATUS message with a Cause information element containing the cause value #101, a Call state information element containing the cal
47、l state and using the call reference value of the received REGISTER message and remains in the same states. GFPN8-06-003 clause 8.3.2.1.1.2 Ensure that the IUT, in call state NO0 and in the state receiving a REGISTER message containing a Facility information element with an invalid protocol profile,
48、 sends a RELEASE COMPLETE message containing cause #lo0 and using the call reference value of the received REGISTER message. GFPN8-06-004 6 clause 8.3.2.1.1.1 & clause 5.8.3.2 d Ensure that the IUT, in call state and in the state receiving a REGISTER message with a call reference not recognized as r
49、elating to a call and with the call reference flag set to “l“, ignores the message. ETSI 28 ETSI EN 300 196-5 VI .2.1 (2001-1 1) GFPN8-06-005 clause 8.3.2.1.2.1 Ensure that the IUT, in call state N3 1 and in the state to transfer data, sends a FACILITY message and remains the same call state and enters the state. GFPN8-06-006 clause 8.3.2.1.2.2 Ensure that the IUT, in call state N3 1 and in the state receiving a message other than FACILITY, RELEASE, RELEASE COMPLETE, STATUS or STATUS ENQUIRY using the call reference assigned by a
