ImageVerifierCode 换一换
格式:PDF , 页数:531 ,大小:1.82MB ,
资源ID:730946      下载积分:10000 积分
快捷下载
登录下载
邮箱/手机:
温馨提示:
如需开发票,请勿充值!快捷下载时,用户名和密码都是您填写的邮箱或者手机号,方便查询和重复下载(系统自动生成)。
如填写123,账号就是123,密码也是123。
特别说明:
请自助下载,系统不会自动发送文件的哦; 如果您已付费,想二次下载,请登录后访问:我的下载记录
支付方式: 支付宝扫码支付 微信扫码支付   
注意:如需开发票,请勿充值!
验证码:   换一换

加入VIP,免费下载
 

温馨提示:由于个人手机设置不同,如果发现不能下载,请复制以下地址【http://www.mydoc123.com/d-730946.html】到电脑端继续下载(重复下载不扣费)。

已注册用户请登录:
账号:
密码:
验证码:   换一换
  忘记密码?
三方登录: 微信登录  

下载须知

1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。
2: 试题试卷类文档,如果标题没有明确说明有答案则都视为没有答案,请知晓。
3: 文件的所有权益归上传用户所有。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 本站仅提供交流平台,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

版权提示 | 免责声明

本文(ETSI ES 202 388-4-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 4 Call control SCF《开放业务接入(OSA) 应用编程接口(.pdf)为本站会员(figureissue185)主动上传,麦多课文库仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。 若此文所含内容侵犯了您的版权或隐私,请立即通知麦多课文库(发送邮件至master@mydoc123.com或直接QQ联系客服),我们立即给予删除!

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

1、 ETSI ES 202 388-4 V1.1.1 (2005-03)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 4: Call control SCF(Parlay 4)ETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 2 Reference DES/TISPAN-06004-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. Full details of the entire series can be found in part 1 10. To evaluate conformance of a particular implementation, it is necessary t

5、o 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 Purposes (TSS Application Programming Interface (API); Part 4: Call Control; Sub-part 1: Call Control Com

6、mon Definitions (Parlay 4)“. 2 ETSI ES 202 915-4-2: “Open Service Access (OSA); Application Programming Interface (API); Part 4: Call Control; Sub-part 2: Generic Call Control SCF (Parlay 4)“. 3 ETSI ES 202 915-4-3: “Open Service Access (OSA); Application Programming Interface (API); Part 4: Call Co

7、ntrol; Sub-part 3: Multi-Party Call Control SCF (Parlay 4)“. 4 ETSI ES 202 915-4-4: “Open Service Access (OSA); Application Programming Interface (API); Part 4: Call Control; Sub-part 4: Multi-Media Call Control SCF (Parlay 4)“. 5 ETSI ES 202 915-4-5: “Open Service Access (OSA); Application Programm

8、ing Interface (API); Part 4: Call Control; Sub-part 5: Conference Call Control SCF (Parlay 4)“. 6 ETSI ES 202 363: “Open Service Access (OSA); Application Programming Interface (API); Implementation Conformance Statement (ICS) proforma specification; (Parlay 4)“. 7 ISO/IEC 9646-1: “Information techn

9、ology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 8 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. 9 ETSI ETS 300 406:

10、 “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 10 ETSI ES 202 388-1: “Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part 1: Overview (Parlay 4)“. E

11、TSI ETSI ES 202 388-4 V1.1.1 (2005-03) 8 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 202 915-4-1 1, ES 202 915-4-2 2, ES 202 915-4-3 3, ES 202 915-4-4 4, ES 202 915-4-5 5, ISO/IEC 9646-1 7, ISO/IEC 9646-2 8 and the f

12、ollowing apply: abstract test case: Refer to ISO/IEC 9646-1 7. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 7. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 7. Implementation Conformance Statement (ICS): Refer to ISO/IEC 9646-1 7. ICS proforma: Refer to ISO/IEC 9646-1 7. Implementation U

13、nder Test (IUT): Refer to ISO/IEC 9646-1 7. Implementation eXtra Information for Testing (IXIT): Refer to ISO/IEC 9646-1 7. IXIT proforma: Refer to ISO/IEC 9646-1 7. Lower Tester (LT): Refer to ISO/IEC 9646-1 7. Test Purpose (TP): Refer to ISO/IEC 9646-1 7. 3.2 Abbreviations For the purposes of the

14、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 Conformance Statement IUT Implementation Under Test IXIT

15、 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 Control (CC): Generic Call Control Service (GCC). MultiPart

16、y Call Control Service (MPCC). MultiMedia Call Control Service (MMCC). Conference Call Control Service (CCC). ETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 9 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, starting at 01,

17、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 representing t

18、he group reference according to TSS = sequential number: (01-99) 5.1.2 Source of TP definition The TPs are based on ES 202 915-4-1 1, ES 202 915-4-2 2, ES 202 915-4-3 3, ES 202 915-4-4 4 and ES 202 915-4-5 5. 5.1.3 Test strategy As the base standards ES 202 915-4-1 1, ES 202 915-4-2 2, ES 202 915-4-

19、3 3, ES 202 915-4-4 4 and ES 202 915-4-5 5 contain no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standards and the ICS specification ES 202 363 6. The TPs are only based on conformance requirements related to the externally observable behaviour o

20、f the IUT and are limited to conceivable situations to which a real implementation is likely to be faced (see ETS 300 406 9). 5.2 TPs for the Call Control SCF All ICS items referred to in this clause are as specified in ES 202 363 6 unless indicated otherwise by another numbered reference. All param

21、eters specified in method calls are valid unless specified. The procedures to trigger the SCF to call methods in the application are dependant on the underlying network architecture and are out of the scope of the present document. Those method calls are preceded by the words “Triggered action“. 5.2

22、.1 Generic Call Control The TPs in this clause are based on ES 202 915-4-2 2. ETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 105.2.1.1 IpCallControlManager 5.2.1.1.1 Mandatory, valid behaviour Test GCC_IPCALLCONTROLMANAGER _01 Summary: IpCallControlManager, all mandatory methods, successful Reference: ES 2

23、02 915-4-2 2, clause 6.1 Condition: createCall method is supported. Test Sequence: 1. Method call setCallback() on IpCallControlManager Parameters: valid, not null, value of appInterface parameter Check: no exception is returned 2. Method call createCall() Parameters: valid appCall Check: valid valu

24、e of TpCallIdentifier is returned : IpCallControlManager: (Logical View:IpAppLogic)2. createCall(appCall)1. setCallback(appInterface)callReferenceETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 11Test GCC_IPCALLCONTROLMANAGER _02 Summary: IpCallControlManager, all mandatory methods, successful Reference: ES

25、 202 915-4-2 2, clause 6.1 Condition: enableCallNotification method is supported. Test Sequence: 1. Method call enableCallNotification() Parameters: appCallControlManager with valid, not null, value, valid eventCriteria Check: valid value of TpAssignmentID is returned 2 Triggered action: cause IUT t

26、o call callEventNotify()method on the testers (Application) IpAppCallControlManager interface Parameters: valid callReference, valid eventInfo, assignmentID returned in 1 3. Method call disableCallNotification() Parameters: assignmentID returned in 1 Check: no exception is returned : IpCallControlMa

27、nager: (Logical View:IpAppLogic)3. disableCallNotification(assignmentID)1. enableCallNotification(appCallControlManager, eventCriteria): IpAppCallControlManager2. callEventNotify(callReference, eventInfo, assignmentID)assignmentIDappCallETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 12Test GCC_IPCALLCONTRO

28、LMANAGER _03 Summary: IpCallControlManager, all mandatory methods, successful Reference: ES 202 915-4-2 2, clause 6.1 Condition: enableCallNotification method is supported. Test Sequence: 1. Method call setCallback() on IpCallControlManager Parameters: valid, non-null, value of appInterface paramete

29、r Check: no exception is returned 2. Method call enableCallNotification() Parameters: appCallControlManager with null, value, valid eventCriteria Check: valid value of TpAssignmentID is returned 3. Triggered action: cause IUT to call callEventNotify()method on the testers (Application) IpAppCallCont

30、rolManager interface. Parameters: valid callReference, valid eventInfo, assignmentID returned in 2. 4. Method call disableCallNotification() Parameters: assignmentID returned in 2. Check: no exception is returned : IpCallControlManager: (Logical View:IpAppLogic)4. disableCallNotification(assignmentI

31、D)1. changeCallNotification(assignmentID, eventCriteria): IpAppCallControlManager2. enableCallNotification(appCallControlManager, eventCriteria)3. callEventNotify(callReference, eventInfo, assignmentID)assignmentIDappCallsetCallback(appInterface)ETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 135.2.1.1.2 Ma

32、ndatory, invalid behaviour Test GCC_IPCALLCONTROLMANAGER _04 Summary: IpCallControlManager, enableCallNotification, P_INVALID_CRITERIA Reference: ES 202 915-4-2 2, clause 6.1 Condition: enableCallNotification method is supported. Test Sequence: 1. Method call enableCallNotification() Parameters: val

33、id appCallControlManager, invalid eventCriteria but with a valid event type Check: P_INVALID_CRITERIA is returned. : IpCallControlManager: (Logical View:IpAppLogic)1. enableCallNotification(appCallControlManager, invalid eventCriteria)P_INVALID_CRITERIATest GCC_IPCALLCONTROLMANAGER _05 Summary: IpCa

34、llControlManager, enableCallNotification, P_INVALID_INTERFACE_TYPE Reference: ES 202 915-4-2 2, clause 6.1 Condition: enableCallNotification method is supported. Test Sequence: 1. Method call enableCallNotification() Parameters: invalid appCallControlManager, valid eventCriteria Check: P_INVALID_INT

35、ERFACE_TYPE is returned : IpCallControlManager: (Logical View:IpAppLogic)1. enableCallNotification(invalid appCallControlManager, eventCriteria)P_INVALID_INTERFACE_TYPEETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 14Test GCC_IPCALLCONTROLMANAGER _06 Summary: IpCallControlManager, disableCallNotification,

36、P_INVALID_ASSIGNMENT_ID Reference: ES 202 915-4-2 2, clause 6.1 Condition: disableCallNotification is supported. Test Sequence: 1. Method call enableCallNotification() Parameters: appCallControlManager with valid, not null, value, valid eventCriteria Check: valid value of TpAssignmentID is returned

37、2. Method call disableCallNotification() Parameters: invalid assignmentID Check: P_INVALID_ASSIGNMENT_ID is returned : IpCallControlManager: (Logical View:IpAppLogic)2. disableCallNotification(invalid assignmentID)P_INVALID_ASSIGNMENT_ID1. enableCallNotification(appCallControlManager, eventCriteria)

38、Test GCC_IPCALLCONTROLMANAGER _07 Summary: IpCallControlManager, createCall, P_INVALID_INTERFACE_TYPE Reference: ES 202 915-4-2 2, clause 6.1 Condition: createCall method is supported. Test Sequence: 1. Method call createCall() Parameters: invalid value of appCall Check: P_INVALID_INTERFACE_TYPE is

39、returned ETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 15: IpCallControlManager: (Logical View:IpAppLogic)1. createCall(invalid appCall)P_INVALID_INTERFACE_TYPE5.2.1.1.3 Optional, valid behaviour Test GCC_IPCALLCONTROLMANAGER _08 Summary: IpCallControlManager, getCriteria, successful Reference: ES 202 915

40、-4-2 2, clause 6.1 Condition: enableCallNotification and getCriteria methods are 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() Paramet

41、ers: 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 where eventCriteria given in 1. is included as a value of this TpCallEventCrit

42、eriaResultSet 4. Method call disableCallNotification() Parameters: assignmentID returned in 1. Check: no exception is returned ETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 16: IpCallControlManager: (Logical View:IpAppLogic)4. disableCallNotification(assignmentID)1. setCallback(appInterface)2. enableCallN

43、otification(appCallControlManager, eventCriteria)assignmentID3. getCriteria( )eventCriteriaTest GCC_IPCALLCONTROLMANAGER _09 Summary: IpCallControlManager, changeCallNotification, successful Reference: ES 202 915-4-2 2 clause 6.1 Condition: enableCallNotification, getCriteria and changeCallNotificat

44、ion 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 eventCriteria Check: valid value of TpAssignmentID is returned 2. Method call get

45、Criteria() 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() Parameters: assignmentID returned in 1., valid eventCriteria different from t

46、his 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 TpCallEventCriteriaResultSet 5. Triggered action: cause IUT to call callEventNot

47、ify() method on the testers (Application) IpAppCallControlManager interface. Parameters: valid callReference, valid eventInfo, assignmentID returned in 1. ETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 176. Method call disableCallNotification() Parameters: assignmentID returned in 1. Check: no exception is

48、 returned : (Logical View:IpAppLogic): IpCallControlManager3. changeCallNotification(assignmentID, eventCriteria)4. getCriteria( )eventCriteria: IpAppCallControlManager5. callEventNotify(callReference, eventInfo, assignmentID)appCall1. enableCallNotification(appCallControlManager, eventCriteria)assi

49、gnmentID6. disableCallNotification(assignmentID)2. getCriteria( )eventCriteriaETSI ETSI ES 202 388-4 V1.1.1 (2005-03) 18Test GCC_IPCALLCONTROLMANAGER _10 Summary: IpCallControlManager, all methods, successful Reference: ES 202 915-4-2 2 clause 6.1 Condition: enableCallNotification, setCallLoadControl, callOverLoadEncountered and callOverLoadCeased methods are supported. Test Sequence: 1. Method call enableCallNotification() Parameters: appCallControlManager with valid, no

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1