ETSI ES 202 196-4-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 4 Call control SCF《开放业务接入(OSA) 应用编程接口(_1.pdf

1、 ETSI ES 202 196-4 V1.2.1 (2005-02)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 4: Call control SCF(Parlay 3)ETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 2 Reference RES/TISPAN-06005-04-OSA Keywords API, OSA, TSS Essential

2、, 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). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been

3、 carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Com

4、mittee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 4 of a multi-part deliverable covering Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part 2: “Commo

5、n data definitions“; Part 3: “Framework“; Part 4: “Call control SCF“; Part 5: “User interactions SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal capabilities SCF“; Part 8: “Data session control SCF“; Part 9: “Generic messaging SCF“; Part 10: “Connectivity manager SCF“; Part 11: “Account management S

6、CF“; Part 12: “Charging SCF“. To evaluate conformance of a particular implementation, it is necessary to have a set of test purposes to evaluate the dynamic behaviour of the Implementation Under Test (IUT). The specification containing those test purposes is called a Test Suite Structure and Test Pu

7、rposes (TSS Application Programming Interface (API); Part 4: Call Control SCF (Parlay 3)“. 2 ETSI ES 202 170: “Open Service Access (OSA); Application Programming Interface (API); Implementation Conformance Statement (ICS) proforma specification (Parlay 3)“. 3 ISO/IEC 9646-1: “Information technology

8、- 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 ETSI ETS 300 406: “Meth

9、ods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 201 915-4 1, ISO/IEC 9646-1 3, ISO/IEC 9646-

10、2 4 and the following apply: abstract test case: Refer to ISO/IEC 9646-1 3. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 3. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 3. ICS proforma: Refer to ISO/IEC 9646-1 3. Implementation Conformance Statement (ICS): Refer to ISO/IEC 9646-1 3. Imp

11、lementation eXtra Information for Testing (IXIT): Refer to ISO/IEC 9646-1 3. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 3. ETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 8 IXIT proforma: Refer to ISO/IEC 9646-1 3. Lower Tester (LT): Refer to ISO/IEC 9646-1 3. Test Purpose (TP): Refer to ISO/I

12、EC 9646-1 3. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: API Application Programming Interface ATM Abstract Test Method ATS Abstract Test Suite CC Call Control CCC Conference Call Control service GCC Generic Call Control service ICS Implementation C

13、onformance Statement IUT Implementation Under Test IXIT Implementation eXtra Information for Testing LT Lower Tester MMCC MultiMedia Call Control service MPCC MultiParty Call Control service OSA Open Service Access TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) - SCF Call Cont

14、rol (CC): Generic Call Control Service (GCC). MultiParty Call Control Service (MPCC). MultiMedia Call Control Service (MMCC). Conference Call Control Service (CCC). 5 Test Purposes (TP) - SCF 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming convention TPs are numbered, sta

15、rting at 01, within each group. Groups are organized according to the TSS. Additional references are added to identify the actual test suite (see table 1). Table 1: TP identifier naming convention scheme Identifier: _ = SCG name: “CC“ for Call Control part of Call Control SCF = group number: field r

16、epresenting the group reference according to TSS = sequential number: (01 to 99) ETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 9 5.1.2 Source of TP definition The TPs are based on ES 201 915-4 1. 5.1.3 Test strategy As the base standard ES 201 915-4 1 contains no explicit requirements for testing, the TPs

17、 were generated as a result of an analysis of the base standard and the ICS specification ES 202 170 2. The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT and are limited to conceivable situations to which a real implementation is likely to b

18、e faced (see ETS 300 406 5). 5.2 TPs for the Call Control SCF All ICS items referred to in this clause are as specified in ES 202 170 2 unless indicated otherwise by another numbered reference. All parameters specified in method calls are valid unless specified. The procedures to trigger the SCF to

19、call methods in the application are dependant on the underlying network architecture and are out of the scope of this test specification. Those method calls are preceded by the words “Triggered action“. ETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 105.2.1 Generic Call Control 5.2.1.1 IpCallControlManager

20、 5.2.1.1.1 Mandatory, valid behaviour Test GCC_IPCALLCONTROLMANAGER _01 Summary: IpCallControlManager, all mandatory methods, successful Reference: ES 201 915-4 1, clause 6.3.1 Condition: createCall method is supported Test Sequence: 1. Method call setCallback() on IpCallControlManager Parameters: v

21、alid, not null, value of appInterface parameter Check: no exception is returned 2. Method call createCall() Parameters: valid appCall Check: valid value of TpCallIdentifier is returned : IpCallControlManager: (Logical View:IpAppLogic)2. createCall(appCall)1. setCallback(appInterface)callReferenceETS

22、I ETSI ES 202 196-4 V1.2.1 (2005-02) 11Test GCC_IPCALLCONTROLMANAGER _02 Summary: IpCallControlManager, all mandatory methods, successful Reference: ES 201 915-4 1, clause 6.3.1 Condition: enableCallNotification method is supported Test Sequence: 1. Method call enableCallNotification() Parameters: a

23、ppCallControlManager with valid, not null, value, valid eventCriteria Check: valid value of TpAssignmentID is returned 2. Triggered action: cause IUT to call callEventNotify()method on the testers (Application) IpAppCallControlManager interface Parameters: valid callReference, valid eventInfo, assig

24、nmentID returned in 1. 3. Method call disableCallNotification() Parameters: assignmentID returned in 1 Check: no exception is returned : IpCallControlManager: (Logical View:IpAppLogic)3. disableCallNotification(assignmentID)1. enableCallNotification(appCallControlManager, eventCriteria): IpAppCallCo

25、ntrolManager2. callEventNotify(callReference, eventInfo, assignmentID)assignmentIDappCallETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 12Test GCC_IPCALLCONTROLMANAGER _03 Summary: IpCallControlManager, all mandatory methods, successful Reference: ES 201 915-4 1, clause 6.3.1 Condition: enableCallNotificat

26、ion method is supported Test Sequence: 1. Method call setCallback() on IpCallControlManager Parameters: valid, non-null, value of appInterface parameter Check: no exception is returned 2. Method call enableCallNotification() Parameters: appCallControlManager with null, value, valid eventCriteria Che

27、ck: valid value of TpAssignmentID is returned 3. Triggered action: cause IUT to call callEventNotify()method on the testers (Application) IpAppCallControlManager interface Parameters: valid callReference, valid eventInfo, assignmentID returned in 2. 4. Method call disableCallNotification() Parameter

28、s: assignmentID returned in 2. Check: no exception is returned : IpCallControlManager: (Logical View:IpAppLogic)4. disableCallNotification(assignmentID)setCallback( ): IpAppCallControlManager2. enableCallNotification(appCallControlManager, eventCriteria)3. callEventNotify(callReference, eventInfo, a

29、ssignmentID)assignmentIDappCallETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 135.2.1.1.2 Mandatory, invalid behaviour Test GCC_IPCALLCONTROLMANAGER _04 Summary: IpCallControlManager, enableCallNotification, P_INVALID_CRITERIA Reference: ES 201 915-4 1, clause 6.3.1 Condition: enableCallNotification method

30、 is supported Test Sequence: 1. Method call enableCallNotification() Parameters: valid appCallControlManager, invalid eventCriteria but with a valid event type Check: P_INVALID_CRITERIA is returned : IpCallControlManager: (Logical View:IpAppLogic)1. enableCallNotification(appCallControlManager, inva

31、lid eventCriteria)P_INVALID_CRITERIATest GCC_IPCALLCONTROLMANAGER _05 Summary: IpCallControlManager, enableCallNotification, P_INVALID_INTERFACE_TYPE Reference: ES 201 915-4 1, clause 6.3.1 Condition: enableCallNotification method is supported Test Sequence: 1. Method call enableCallNotification() P

32、arameters: invalid appCallControlManager, valid eventCriteria Check: P_INVALID_INTERFACE_TYPE is returned : IpCallControlManager: (Logical View:IpAppLogic)1. enableCallNotification(invalid appCallControlManager, eventCriteria)P_INVALID_INTERFACE_TYPEETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 14Test GCC

33、_IPCALLCONTROLMANAGER _06 Summary: IpCallControlManager, disableCallNotification, P_INVALID_ASSIGNMENT_ID Reference: ES 201 915-4 1, clause 6.3.1 Condition: disableCallNotification is supported Test Sequence: 1. Method call enableCallNotification() Parameters: appCallControlManager with valid, not n

34、ull, value, valid eventCriteria Check: valid value of TpAssignmentID is returned 2. Method call disableCallNotification() Parameters: invalid assignmentID Check: P_INVALID_ASSIGNMENT_ID is returned : IpCallControlManager: (Logical View:IpAppLogic)2. disableCallNotification(invalid assignmentID)P_INV

35、ALID_ASSIGNMENT_ID1. enableCallNotification(appCallControlManager, eventCriteria)Test GCC_IPCALLCONTROLMANAGER _07 Summary: IpCallControlManager, createCall, P_INVALID_INTERFACE_TYPE Reference: ES 201 915-4 1, clause 6.3.1 Condition: createCall method is supported Test Sequence: 1. Method call creat

36、eCall() Parameters: invalid value of appCall Check: P_INVALID_INTERFACE_TYPE is returned : IpCallControlManager: (Logical View:IpAppLogic)1. createCall(invalid appCall)P_INVALID_INTERFACE_TYPEETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 155.2.1.1.3 Optional, valid behaviour Test GCC_IPCALLCONTROLMANAGER

37、_08 Summary: IpCallControlManager, getCriteria, successful Reference: ES 201 915-4 1, clause 6.3.1 Condition: enableCallNotification and getCriteria methods are supported Test Sequence: 1. Method call setCallback() on IpCallControlManager Parameters: valid, non-null, value of appInterface parameter

38、Check: no exception is returned 2. Method call enableCallNotification() Parameters: appCallControlManager with null value, valid eventCriteria Check: valid value of TpAssignmentID is returned 3. Method call getCriteria() Parameters: None Check: valid value of TpCallEventCriteriaResultSet is returned

39、 where eventCriteria given in 1. is included as a value of this TpCallEventCriteriaResultSet 4. Method call disableCallNotification() Parameters: assignmentID returned in 1. Check: no exception is returned : IpCallControlManager: (Logical View:IpAppLogic)4. disableCallNotification(assignmentID)1. se

40、tCallback(appInterface)2. enableCallNotification(appCallControlManager, eventCriteria)assignmentID3. getCriteria( )eventCriteriaETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 16Test GCC_IPCALLCONTROLMANAGER _09 Summary: IpCallControlManager, changeCallNotification, successful Reference: ES 201 915-4 1, cla

41、use 6.3.1 Condition: enableCallNotification, getCriteria and changeCallNotification methods are supported Preamble: Application has a reference interface used for callbacks Test Sequence: 1. Method call enableCallNotification() Parameters: appCallControlManager with valid, not null, value, valid eve

42、ntCriteria Check: valid value of TpAssignmentID is returned 2. Method call getCriteria() Parameters: None Check: valid value of TpCallEventCriteriaResultSet is returned where eventCriteria given in 1. is included as a value of this TpCallEventCriteriaResultSet 3. Method call changeCallNotification()

43、 Parameters: assignmentID returned in 1., valid eventCriteria different from this given in 1. Check: no exception is returned 4. Method call getCriteria() Parameters: None Check: valid value of TpCallEventCriteriaResultSet is returned where eventCriteria given in 3. is included as a value of this Tp

44、CallEventCriteriaResultSet 5. Triggered action: cause IUT to call callEventNotify() method on the testers (Application) IpAppCallControlManager interface Parameters: valid callReference, valid eventInfo, assignmentID returned in 1. 6. Method call disableCallNotification() Parameters: assignmentID re

45、turned in 1. Check: no exception is returned ETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 17: (Logical View:IpAppLogic): IpCallControlManager3. changeCallNotification(assignmentID, eventCriteria)4. getCriteria( )eventCriteria: IpAppCallControlManager5. callEventNotify(callReference, eventInfo, assignment

46、ID)appCall1. enableCallNotification(appCallControlManager, eventCriteria)assignmentID6. disableCallNotification(assignmentID)2. getCriteria( )eventCriteriaETSI ETSI ES 202 196-4 V1.2.1 (2005-02) 18Test GCC_IPCALLCONTROLMANAGER _10 Summary: IpCallControlManager, all methods, successful Reference: ES

47、201 915-4 1, clause 6.3.1 Condition: enableCallNotification, setCallLoadControl, callOverLoadEncountered and callOverLoadCeased methods are supported Test Sequence: 1. Method call enableCallNotification() Parameters: appCallControlManager with valid, not null, value, valid eventCriteria Check: valid

48、 value of TpAssignmentID is returned 2. Method call setCallLoadControl() Parameters: valid duration, valid mechanism, valid treatment, valid addressRange Check: valid value of TpAssignmentID is returned 3. Triggered action: cause IUT to call callEventNotify() numerous times during the following sequ

49、ence, and attempt to provoke an overload condition and then remove it 4. Triggered action: cause IUT to call callOverLoadEncountered() method on the testers (Application) IpAppCallControlManager interface Parameters: valid assignmentID 5. Triggered action: cause IUT to call callOverLoadCeased() method on the testers (Application) IpAppCallControlManager interface Parameters: valid assignmentID : IpCallControlManager: (Logical View:IpAppLogic): IpAppCallControlManager1. enableCallNotification(appCallControl