ETSI EN 301 933-3-2003 Intelligent Network (IN) Intellegent Network Capability Set 3 (CS3) Intelligent Network Application Protocol (INAP) Test Suite Structure and Test Purposes (T_1.pdf

《ETSI EN 301 933-3-2003 Intelligent Network (IN) Intellegent Network Capability Set 3 (CS3) Intelligent Network Application Protocol (INAP) Test Suite Structure and Test Purposes (T_1.pdf》由会员分享，可在线阅读，更多相关《ETSI EN 301 933-3-2003 Intelligent Network (IN) Intellegent Network Capability Set 3 (CS3) Intelligent Network Application Protocol (INAP) Test Suite Structure and Test Purposes (T_1.pdf（92页珍藏版）》请在麦多课文档分享上搜索。

1、ETS I EN 30 1 933-3 VI .I .I (2003-01) European Sfandard (Telecommunicafions series) Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Test Suite Structure and Test Purposes (TSS Part 3: Specialized Resource Function (SRF) 2 ETSI E

2、N 301 933-3 VI .I .I (2003-01) Reference DENISPAN-I 20063-3-3 Keywords IN, CS3, INAP, 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). All published ETSI

3、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 3 of a multi

4、-part deliverable covering the Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Test Suite Structure and Test Purposes (TSS “Call Party Handling (CPH)“; “Specialized Resource Function (SRF)“. National transposition dates Date of adoption of this EN: Date o

5、f 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): 10 January 2003 30 April 2003 3 1 October 2003 3 1 October 2003 ETSI 6 ETSI EN 301 933-3 VI .I .I (2003-01) 1

6、Scope The present document contains the Test Suite Structure and Test Purposes (TSS Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 1 : Common aspects“. ETSI EN 301 93 1-2: “Intelligent Network (IN); Intelligent Network Capabi

7、lity Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 2: SCF-SSF interface“. 21 31 ETSI EN 301 93 1-3: “Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Protocol specification; Part 3 : SC

8、F-SRF interface“. 41 Void. 51 ETSI EN 301 933-1: “Intelligent Network (IN); Intelligent Network Capability Set 3 (CS3); Intelligent Network Application Protocol (INAP); Test Suite Structure and Test Purposes (TSS Part 1: Basic capability set of CS3“. 91 ETSI EN 301 933-2: “Intelligent Network (IN);

9、Intelligent Network capability Set 3 (CS3); Intelligent Network Application protocol (INAP); Test Suite Structure and Test Purposes (TSS Part 2: Call Party Handling (CPH) “ . Void. ISO/IEC 9646- 1 : “Information technology - Open Systems Interconnection - Conformance testing methodology and framewor

10、k - Part 1 : General concepts“. ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. ETSI 7 ETSI EN 301 933-3 VI .I .I (2003-01) 3 Definitions and abbreviations 3.1 De fi nit ions For the

11、purposes of the present document, the following terms and defmitions apply: - - terms defined in EN 301 931-1 i; terms defined in ISO/IEC 9646-1 SI and in ISO/IEC 9646-2 9. In particular, the following terms defied in ISO/IEC 9646-1 SI apply: - Abstract Test Suite (ATS); - Implementation Under Test

12、(IUT); - System Under Test (SUT); - Protocol Implementation Conformance Statement (PICS). 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ATS BI BO BV CA CPH cs cs EDP-R FSM IN INAP IP is iSSP IUT MSC PDU PICS PIXIT SCF SCP SDF SDL SRF SSF SSP SUT TCAP

13、TP TSS Abstract Test Suite Invalid Behaviour tests Inopportune Behaviour tests Valid Behaviour tests Capability tests Call Party Handling Call Segment Capability Set Event Detection Point - Request Finite State Machine Intelligent Network Intelligent Network Application Protocol Intelligent Peripher

14、al initiating SSF initiating SSP Implementation Under Test Message Sequence Chart Protocol Data Unit Protocol Implementation Coiiformance Statement Protocol Implementation extra Information for Testing Service Control Function Service Control Point Service Data Function Specification and Description

15、 Language Specialized Resource Function Service Switching Function Service Switching Point System Under Test Transaction Capabilities Application Part Test Purpose Test Suite Structure ETSI 8 ETSI EN 301 933-3 VI .I .I (2003-01) 4 Test Purpose generalities 4.1 I n trod u ction The Implementation Und

16、er Test (IUT) is always an SSF. The testing of the direct interface between SCF and SRF is not within the scope of the present document. Two basic scenarios are possible: A) B) The SSF acts as a relay for operations exchanged between the SCF and the SRF; The SSF establishes a temporary connection to

17、 an assisting SSF or handed-off SSF or directly to an SRF. In A) the SSF is tested together with the addressed SRF, and, possibly, together with an intermediate Assisting/Handed-off SSF. The SRF can be integrated in the SSF or not. Case A) is applicable to an SSF operating as: 1) Initiating SSF, 2)

18、Assisting SSF, or 3) Handed-off SSF. Individual TPs can be applicable to a true subset of the three SSF sub-functions. To handle this, Test Parameters applicable to TP Selection are defiied (see clause 4.6). Case B) is only applicable to an SSF operating as an Initiating SSF. The operation used to c

19、onnect to the SRF is EstablishTemporaryConnection. Configurations for cases A) and B) are defined in clause 5. A TP is defined for one or several conformance requirements to be tested. It is expected, that each TP will result in a test case keeping the same name, specified in the ATS. 4.2 Grouping o

20、f Test purposes According to the two basic scenarios defined in the previous clause, the test purposes are grouped in the following 2 main groups: a) SSF Relaying, and b) Direct SCF-SRF operation. Inside a main group the Test purposes are grouped by elementary procedures. A procedure groups elementa

21、ry INAP operations belonging together conceptually. The procedures are defiied in clause 6.2. 4.3 Source of Test purpose definitions The test purposes are based on the requirement documented in EN 301 931-1 i, EN 301 931-2 2 and EN 301 931-3 3. 4.4 Method used for developing Test purposes See EN 301

22、 933-1 5. ETSI 9 ETSI EN 301 933-3 VI .I .I (2003-01) Work item no.: IN2 Ref Purpose: Requirements refs Selection Cond. Preamble : Test description Pass criteria Postamble: 4.5 Method used for Test purpose description The table describing each TP is as shown in table 1. TP name, e.g. INS-A-BASIC-FC-

23、BV-O1 Temporary work item number; to be deleted when the TPs are stable Reference to INAP CS2 TP (optional) Textual phrasing of the TP to be achieved. Reference to clause(s) of EN 301 931-2 2. For TPs related to the SRF function: also reference to clause(s) of EN 301 931-3 3. In the latter case the

24、Part numbers are explicitly indicated (part 2 and/or part 3). Reference to a formal selection expression, if the TP is related to an optional INAP feature. If the field is empty, the TP is unconditional (mandatory requirement(s). Reference to a preamble or “None“. Sequence of transmitted and receive

25、d events and timeouts (see clause “TTCN-like notation“). Textual description is also used, as appropriate. Indication of reception (or assured non-reception) of decisive message(s) related to the TP. Reference to a postamble or “None“. 4.5.1 Void 4.5.2 Test categories Valid Behaviour tests (BV) Pred

26、efined state transitions are considered as valid. The test purposes in the valid behaviour test sub group cover as far as reasonable the verification of the normal and exceptional procedures of the various Finite State Machines (FSMs), i.e. a valid behaviour test is a test where the message sequence

27、 and the message contents is considered as valid. Invalid Behaviour tests (BI) This test sub group is intended to ver that the IT is able to react properly having received an invalid Protocol Data Unit (PDU). An invalid PDU is defined as a syntactically incorrect message. Inopportune Behaviour tests

28、 (BO) This test group is intended to veriSl that the IUT is able to react properly in the case an inopportune protocol event occurring. Such an event is syntactically correct but occurs when it is not expected, e.g. a correctly coded operation is received in a wrong state (the IUT may respond by sen

29、ding error UnexpectedComponentSequence). ETSI 10 ETSI EN 301 933-3 VI .I .I (2003-01) 4.5.3 Test purpose naming convention The identifier of the TP is built according to the scheme in table 2. Table 2: TP identifier naming convention scheme IN3 = = = = = indicates IN Capability Set 3 interface: A SS

30、F-SCF interface B SSF-SRF interface C SCF-SCF interface common set BASIC Basic set for CS3 CPH SRF Call Party Handling from Capability Set 3 SRF-related functions from Capability Set 3 procedure name like SF ServiceFiltering test category: BV Valid Behaviour tests BI Invalid Behaviour tests BO Inopp

31、ortune Behaviour tests sequential number: (01-99) Example of test purpose and test case name: IN3-A-BASIC-SF-BV-02 4.5.4 Preambles and their naming conventions Preambles are used to bring the IUT from the initial state to the state where the test takes place. In the CS3 scheme, the set of the preamb

32、les forms a tree, which means that in order to reach the state created by preamble P3, it is necessary to execute preamble P 1 followed by preambles P2 then P3. The naming convention used reflects the description of the connection view set by executing the preamble, in terms of nature of the legs pe

33、r Call Segment (CS), starting from the stable legs then the ones on hold then the ones in transfer, with the indication of the number of legs, while the fiist letter indicates how this configuration was initiated. The general form is: a-stablelegsparty or onHold (legs) or transfer(1egs) for Callsegm

34、ent 11-idem for CallSegment2-idem for Callsegment 31 where: a is letter: O T I for Originating (outgoing call for a user); for Terminating (incoming call for a user); for Initiate Call Attempt (initiated from the network). ETSI 11 ETSI EN 301 933-3 VI .I .I (2003-01) The state names and their abbrev

35、iations used are: Null 1-Party 1P Originating-Set-up os Terminating-Set-up Originating- 1 -Party-Setup Stable- 1 -Party Stable-2-Party Forward TS 01PS S1P S2P FW StableMulti-Passive-Party (no. of passive legs n) SnPP StableMulti-Party (no. of passive legs n) SnP The term “null“ stands for “none“ as

36、in preamble O_NLL_S2P_OH3. There can be two set of CSs with the same nature of legs present at the same time, as in the preamble name O-S2P-SlP-SlP. 4.6 Test purpose parametrization and selection As shown in the “Introduction“ clause, the Implementation under Test (IUT) is always an SSF, either conn

37、ected to an Assisting SSF, a Handed-off SSF or to an SRF. Not all sub-functions defined for an SSF need to be implemented at the same time (see e.g. figure 37 in clause 8 of EN 301 93 1-2 2), and possibly not all operations are implemented (e.g. the use of scripts). In order to define an appropriate

38、 set of TPs for all functions and operations, but to enable deselection of TPs not applicable to particular IUTs, the following Test Parameters are defined in table 3. NOTE: It is assumed, that these Test Parameters are mapped to corresponding PIXIT/Test Suite Parameters. ETSI 12 ETSI EN 301 933-3 V

39、I .I .I (2003-01) SSF-RELAYS-SRF-OPERATIONS SSF-RELAYS-SRF-ASSISTI“ SSF-IS-INITIATING Table 3: Test Parameters applicable to TP selection “CON FI GU RAT1 ON A“ and “CON F I G U RAT1 ON B“ This parameter shall be set to TRUE, if the IUT relays the user interaction operations (PlayAnnouncement etc.) b

40、etween SCF and SRF. Otherwise it shall be set to FALSE. This parameter shall be set to TRUE, if the IUT relays the user interaction operations (PlayAnnouncement etc.) between SCF and SRF via an Assisting SSF. Otherwise it shall be set to FALSE. This parameter shall be set to TRUE, if the IN SSM BOOL

41、EAN BOOLEAN BOOLEAN SSF-I S-ASSI STI NG BOOLEAN SS F-IS-HAN DED-OFF BOOLEAN SSF-IMPLEMENTS-SCRIPTS BOOLEAN SSF-IMPLEMENTS-SCRIPT-EVENTS BOOLEAN SSF-IMPLEMENTS-PA BOOLEAN SSF-IMPLEMENTS-PA-INTERRUPT BOOLEAN SSF-IMPLEMENTS-PCU BOOLEAN Iprocedure. Otherwise. it shall be set to FALSE. IThis parameter sh

42、all be set to TRUE, if the IUT SSFpIMPLEMENTSpPCUpINTERRUPT IBOOLEAN FSM is implemented in the IUT and is used for testing. Otherwise it shall be set to FALSE. See figure 37 in clause 8 of EN 301 931-2 2. (see note 1) This parameter shall be set to TRUE, if the Assisting SSM FSM is implemented in th

43、e IUT and is used for testing. Otherwise it shall be set to FALSE. See figure 37 in clause 8 of EN 301 931-2 2. (see note 1) This parameter shall be set to TRUE, if the Handed-off SSM FSM is implemented in the IUT and is used for testing. Otherwise it shall be set to FALSE. See figure 37 in clause 8

44、 of EN 301 931-2 2. (see note 1) This parameter shall be set to TRUE, if the IUT implements the script operations ScriptRun, ScriptClose and Scriptlnformation. Otherwise it shall be set to FALSE. This parameter shall be set to TRUE, if the IUT implements a script invoking the ScriptEvent operation.

45、Otherwise it shall be set to FALSE. This parameter shall be set to TRUE, if the IUT implements the PlayAnnouncement procedure. Otherwise it shall be set to FALSE. This parameter shall be set to TRUE, if the IUT implements the PlayAnnouncement procedure in an interruptable way, .e. it can be cancelle

46、d with the Cancel operation. Otherwise it shall be set to FALSE. This parameter shall be set to TRUE, if the IUT implements the PrompAndCollectUserlnformation SSF-IMPLEMENTS-PRM SSF-IMPLEMENTS-PRM-INTERRUPT ICancel operation. Otherwise it shall be set to FALSE. IThis parameter shall be set to TRUE,

47、if the IUT SSF-IMPLEMENTS-UTSI IBOOLEAN implements the PrompAndCollectUserlnformation procedure in an interruptable way, .e. it can be cancelled with the Cancel operation. Otherwise it shall be set to FALSE. This parameter shall be set to TRUE, if the IUT implements the PrompAndReceiveMessage proced

48、ure. Otherwise it shall be set to FALSE. This parameter shall be set to TRUE, if the IUT implements the PrompAndReceiveMessage procedure in an interruptable way, .e. it can be cancelled with the BOOLEAN BOOLEAN I implements the RequestReportUTSI, SendSTUI and ReportUTSI procedure. Otherwise it shall

49、 be set to ISS F-TI MER- US ED IBOOLEAN IThe SSF timer is used. ETSI 13 ETSI EN 301 933-3 VI .I .I (2003-01) Test Parameter name I Type Explanation I selected automatically when no Resource IP Address is specified. ;SF-ADRESSED-SRF iTC-EXPLICIT-CORRELATION BOOLEAN The SSF can select an SRF by a valid Resource IP Add ress. (see note 2). This Darameter shall be set to TRUE. if the SSF BOOLEAN iTC-TO-ASSI ST iTC-TO-SRF :O-EXPLICIT-CORRELATION BOOLEAN BOOLEAN BOOLEAN expects the correlationlD and sCFIDparameters to be explicitly contained in the Establish