1、EN 300 1 85-3 VI .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 (DSSI) protocol; Part 3: Test Suite Structure and Test Purposes (TSS Essential,
2、 orpotentially Essential, IPRs noted to ETSI in respect of ETSI standards“, which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/www.etsi.fr/ipr or http:/www.etsi.org/ipr). Pursuant to the ETSI IPR Policy, no investigation, including
3、 IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in SR O00 314 (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 se
4、ries) has been produced by ETSI Technical Committee Signalling Protocols and Switching (SPS). The present document is part 3 of a multi-part standard covering the Digital Subscriber Signalling System No. one (DSS 1) protocol specification for the Integrated Services Digital Network (ISDN) Conference
5、 call, add-on (CONF) supplementary service, 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 Implem
6、entation extra Information 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: The present v
7、ersion updates the references to the basic call specifications. I National transposition dates Date of 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 Natio
8、nal Standard (dow): 19 June 1998 30 September 1998 31 March 1999 31 March 1999 - STDnETSI EN 300 185-3-ENGL 1998 3400855 O332204 7qb m 5 EN 300 185-3 V1.2.4 (1 99846) This third part of EN 300 185 specifies the Test Suite Strucbre and Test Purposes (TSS or b) all versions up to and including the ide
9、ntified version (identifed by “up to and including“ before the version identity); or c) all versions subsequent to and including the identified version (identified by “onwards“ following the version identity); or d) publications without mention of a specific version, in which case the latest version
10、 applies A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. Li1 EN 300 185-1 (V1.2): “Integrated Services Digital Network (ISDN); Conference call, add-on (CONF) supplementary service; Digital Subscriber Signalling System No. one
11、 (DSSI) protocol; Part 1: Protocol specification“. EN 300 185-2 (V 1.2): “Integrated Services Digital Network (ISDN); Conference call, add-on (CONF) supplementary service; Digital Subscriber Signalling System No. one (DSSl) protocol; Part 2: Protocol Implementation Conformance Statement (PICS) profo
12、rma specification“. ISO/EC 9646-1: “Information Technology - OS1 Conformance Testing Methodology and Framework; Part 1: General Concepts“. ISOAEC 9646-2: “Information Technology - OS1 Conformance Testing Methodology and Framework; Part 2: Abstract Test Suite specification“. lSO/IEC 9646-3: “Informat
13、ion Technology - OS1 Conformance Testing Methodology and Framework; Part 3: The Tree and Tabular Combined Notation“. 121 131 41 151 161 EN 300 196-1: “Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling Syst
14、em No. one (DSS 1) protocol; Part 1 : Protocol specification“. 71 181 91 1101 ITU-T Recommendation 1.41 1 (1993): “ISDN user-network interfaces - Reference configurations“. EN 300 403-1: “Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS 1) protocol; Signa
15、lling network layer for circuit-mode basic call control; Part 1 : Protocol specification ITU-T Recommendation Q.931 (1993), modified“. ITU-T Recommendation 1.112: “Vocabulary and terms for ISDNs“. CCIT Recommendation E. 164 “Numbering plan for the ISDN era“. ETSI 6 EN 300 185-3 V1.2.4 (1998-06) 1111
16、 ITU -T Recommendation 1.2 10: “Principles of the telecommunication services supported by an ISDN and the means to describe them“. 3 Definit ions For the purposes of the present document, the following definitions apply: 3.1 Definitions related to conformance testing abstract test case: Refer to ISO
17、/iEC 9646-1 131. Abstract Test Suite (ATS): Refer to ISOhEC 9646-1 131. Implementation Under Test (IUT): Refer to ISO/iEC 9646-1 131. implicit send event: Refer to ISO/IEC 9646-3 1.51. lower tester: Refer to ISOIIEC 9646-1 131. point of control and observation: Refer to ISO/IEC 9646-1 131. Protocol
18、Implementation Conformance Statement (PICS): Refer to ISO/IEC 9646-1 131. PICS proforma: Refer to ISO/iEC 9646- 1 131. Protocol Implementation extra Information for Testing (PIXIT): Refer to ISO/IEC 9646-1 3. PIXIT proforma: Refer to ISOhEC 9646-1 131. system under test: Refer to ISO/IEC 9646-1 131.
19、 Test Purpose (TP): Refer to ISO/lEC 9646-1 131. 3.2 Definitions related to EN 300 185-1 Call Held auxiliary state: See EN 300 1%-1 161, subclause 7.1.2. call reference: See EN 300 403-1 181, subclause 4.3. component: SeeEN 300 1%-1 SI, subclause 11.2.2.1. Idle auxiliary state: See EN 300 196-1 161,
20、 subclause 7.1.2. Integrated Services Digital Network (ISDN): See ITU-T Recommendation 1.112 191, definition 308. ISDN number: A number conforming to the numbering and structure specified in CCIT Recommendation E.164 lo. invoke component: See EN 300 1%-1 161, subclause 11.2.2.1. remote user: A user
21、which is involved in an instance of the CONF supplementary service but who has no control over it. return error component: See EN 300 1%-1 161, subclause 11.2.2.1. return result component: See EN 300 1%-1 161, subclause 11.2.2.1. served user: The user who invokes the CONF supplementary service. serv
22、ice; telecommunication service: See ITU-T Recommendation 1.1 12 SI, definition 201. supplementary service: See ITU-T Recommendation 1.210 il, subclause 2.4. ETSI 7 EN 300 1 85-3 V1.2.4 (i 998-06) user: The DSS 1 protocol entity at the User side of the user-network interface where a T reference point
23、 or coincident S and T reference point applies. user (SIT): The DSSl protocol entity at the User side of the user-network interface where a coincident S and T reference point applies. user (T): The DSSl protocol entity at the User side of the user-network interface where a T reference point applies
24、(User is the Private ISDN). 4 Abbreviations For the purposes of the present document, the following abbreviations apply: ATM ATS CCRef CONF DSSl ISDN IUT SCRef TP TSS u00 u01 U03 u10 u12 u19 Abstract Test Method Abstract Test Suite Call Reference for call related to the conference Conference call, a
25、dd-on Digital Subscriber Signalling System No. one Integrated Services Digitai Network Implementation Under Test Cali Reference for a private Cali not related to the conference Test Purpose Test Suite Stnicaire Ide call state Call Initiated call state Outgoing Call Proceeding call state Active call
26、state Disconnect Indication Cali state Release Request call state 5 Test Suite Structure (TSS) CONF - User I Served user (Sil or T) I I Private ISDN (T) (10) of remote user by remote user (07) (08 1 NOTE: Numbers in brackets represent group numbers and are used in TP identifiers. Figure 1: Test suit
27、e structure 6 Test Purposes (TP) 6.1 i n t rod uct i on For each test requirement a TP is defined. ETSI 8 EN 300 1 85-3 V1.2.4 (1 99846) Text tab tab tab CR. Ensure that lhe IUT in the see below for message structure or if the action is sending see below for message structure encoded as orincluding
28、, and back to a orb, Table 1: TP identifier naming convention scheme Bearer capability, Facility, . Identifier: - css = supplementary service: e.g. “CONF“ ciut = type of IUT: U User = group cnnn = sequential number (O01 -999) N Network 2 digit field representing group reference according to TSS 6.1.
29、2 Source of TP definition The TPs are based on EN 300 185-1 111, clauses 9, 10 and 14. 6.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 i
30、s 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. TP pari Header Stimulus Reaction Message structure NOTE: 1 orand enters call state ISETUP, FACILITY, CONNECT, . 9 EN 300 1 85-3 V1.2.4 (1 998-06) 6.1.4 Test stra
31、tegy As the base standard EN 300 185-1 i 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 185-2 121. The criteria applied included the following: - - only the requirements from the point of view of
32、 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.2 User TPs for CONF Ali PICS items referred to in this subclause are as specified in EN 300 185-2 (21 unless indicated otherwise by another numbered reference. 6.2.1
33、Served user (S/T or T) Selection: IUT supports served user requirements. PICS: R 4.1. 6.2.1.1 Begin 6.2.1.1.1 Begin from U00 CONF-U01-001 subclause 9.2.1.1. valid optional Ensure that the IUT in the call state UOO, to request a conference, sends, using implicitly en-bloc sending, a SETUP message con
34、taining a Facility information element with a BeginCONF invoke component and a compatible (for CONF purposes) Bearer capability information element, no Called party number and no Called party subaddress information element included and enters call state UO1. Selection: The BeginCONF component does n
35、ot contain the ConfSize parameter. CONF-U01002 subclause 9.2.1.1. valid optional Ensure that the IUT in the call state UOO, to request a conference, sends, using implicitly en-bloc sending, a SETUP message containing a Facility information element with a BeginCONF invoke component, including a ConfS
36、ize parameter indicating the maximum number of remote users and a compatible (for CONF purposes) Bearer capability information element, no Called party number and no Called party subaddress information element included and enters call state UO1. Selection: The BeginCONF component contains the ConfSi
37、ze parameter. CONF-UOl-O03 subclause 9.2.1.1 valid mandatory Ensure that the IUT in the call state U03 receiving a CONNECT message with a correctly encoded BeginCONF rehim result component, saves the Conferenceld parameter, does not respond to the network and enters call state U10. CONF-UOl-004 subc
38、lause 9.2.1.1 invalid mandatory Ensure that the IUT in the call state U03 receiving a CONNECT message with an incorrectly encoded BeginCONF return result component including an invalid invokelD, sends a FACILITY or a DISCONNECT message containing a Facility information element with a reject componen
39、t encoded as return result problem. CONF-U01005 subclause 9.2.1.2 valid mandatory Ensure that the IUT in the call state U01 receiving a RELEASE message with a correctly encoded BeginCONF return error component, sends a RELEASE COMPLETE message and enters call state UOO. CONF-UOl-O06 subclause 9.2.1.
40、2 valid mandatory Ensure that the IUT in the call state U03 receiving a DISCONNECT message with a correctly encoded BeginCONF return error component, enters state U12. ETSI 10 EN 300 185-3 V1.2.4 (1 99806) CONF-U01007 subclause 9.2.1.2 invalid mandatory Ensure that the IUT in the call state U01 rece
41、iving a RELEASE message with an incorrectly encoded BeginCONF return error component including an invalid invokelD, sends a FACILTY message containing a Facility information element with a reject component encoded as return error problem followed by a RELEASE COMPLETE message and enters call state U
42、OO, or sends a RELEASE COMPLETE message containing a Facility information element with a reject component encoded as return error problem and enters call state UOO. CONFUOlOO8 subclause 9.2.1.2 invalid mandatory Ensure that the IUT in the call state U03 receiving a DISCONNECT message with an incorre
43、ctly encoded BeginCONF return error component including an invalid invokeID, sends a FACILTY message containing a Facility information element with a reject component encoded as return error problem and enters call state U12, or sends a RELEASE message containing a Facility information element with
44、a reject component encoded as return error problem and enters call state U 19. 6.2.1.1.2 Begin from U10 Selection: IUT supports beginning the conference from the Active call state U10. PICS: MC 1.2. CONF-U02-001 subclause 9.2.2.1 valid optional Ensure that the IUT in the call state U10, to request a
45、 conference, sends a FACILITY message indicating the call reference of the existing call containing a Facility information element with a BeginCONF invoke component and remains in the same call state. Selection: The BeginCONF component does not contain the ConfSize parameter. CONF-U02002 subclause 9
46、.2.2.1 valid optional Ensure that the IUT in the call state U10 (Call Held), to request a conference, sends a FACLITY message indicating the call reference of the existing call containing a Facility information element with a BeginCONF invoke component and remains in the same call state. Selection:
47、The BeginCONF component does not contain the ConfSize parameter. Selection: CONF invocation from the Call Held auxiliary state is supported. PICS: MC 3.1. CONF-U02-003 subclause 9.2.2.1 valid optional Ensure that the IUT in the call state U10, to request a conference, sends a FACILITY message indica
48、ting the call reference of the existing call containing a Facility information element with a BeginCONF invoke component with a ConfSize parameter indicating the maximum number of remote users and remains in the same call state. Selection: The BeginCONF component does contain the ConfSize parameter.
49、 CONF-U02-004 subclause 9.2.2.1 valid optional Ensure that the IUT in the call state U10 (Call Held), to request a conference, sends a FACILITY message indicating the call reference of the existing call containimg a Facility information element with a BeginCONF invoke component with a ConfSize parameter indicating the maximum number of remote users and remains in the same call state. Selection: The BeginCONF component does contain the ConfSize parameter. Selection: CONF invocation from the Call Held auxiliary state is supported. PICS: MC 3.1. CONF-U02-005
