ETSI ES 202 196-10-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 10 Connectivity manager SCF《开放业务接入(OS_1.pdf

《ETSI ES 202 196-10-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 10 Connectivity manager SCF《开放业务接入(OS_1.pdf》由会员分享，可在线阅读，更多相关《ETSI ES 202 196-10-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 10 Connectivity manager SCF《开放业务接入(OS_1.pdf（58页珍藏版）》请在麦多课文档分享上搜索。

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

2、S Essential, 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 searche

3、s, has been 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 Te

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

5、rt 2: “Common 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

6、management SCF“; 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

7、 and Test Purposes (TSS Application Programming Interface (API); Part 10: Connectivity Manager 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: “In

8、formation technology - 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 ET

9、SI ETS 300 406: “Methods 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-10 1, ISO/IEC 9

10、646-1 3, ISO/IEC 9646-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

11、 ISO/IEC 9646-1 3. Implementation 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-10 V1.2.1 (2005-02) 6 IXIT proforma: Refer to ISO/IEC 9646-1 3. Lower Tester (LT): Refer to ISO/IEC 9646-1 3. Test Purpo

12、se (TP): Refer to ISO/IEC 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 CM Connectivity ManagerICS Implementation Conformance Statement IUT Implementation

13、 Under Test IXIT Implementation eXtra Information for Testing LT Lower Tester OSA Open Service Access TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) Connectivity Manager. 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming conventio

14、n TPs are numbered, starting 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: “CM“ for Connectivity Manager part of Connectiv

15、ity Manager SCF = group number: two character field representing the group reference according to TSS = sequential number: (01 to 99) 5.1.2 Source of TP definition The TPs are based on ES 201 915-10 1. 5.1.3 Test strategy As the base standard ES 201 915-10 1 contains no explicit requirements for tes

16、ting, the TPs 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 i

17、s likely to be faced (see ETS 300 406 5). ETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 7 5.2 TPs for the Connectivity Manager 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 a

18、re 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 this test specification. Those method calls are preceded by the words “Triggered action“. 5.2.1 Connectivity Manager Test C

19、M_01 Summary: getQoSMenu, successful Reference: ES 201 915-10 1, clause 8.1 Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned AppLogic : IpConnectivityManagergetQoSMenu( )menuRefETSI ETSI ES 202 196-10 V1.2.1 (2005-0

20、2) 8 Test CM_02 Summary: getTemplateList, successful Reference: ES 201 915-10 1, clauses 8.1 and 8.4 Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Ch

21、eck: valid value of TpStringList is returned : AppLogic : IpConnectivityManager: IpQoSMenugetQoSMenu( )menuRefgetTemplateList( )templateListETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 9 Test CM_03 Summary: getTemplate, successful Reference: ES 201 915-10 1, clauses 8.1 and 8.4 Test Sequence: 1. Method

22、call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of TpStringList is returned 3. Method call getTemplate() on IpQoSMenu Parameters: Valid value of templateType

23、, which is an item of the TpStringList, returned in 2. Check: valid value of IpInterfaceRef is returned : AppLogic : IpConnectivityManager: IpQoSMenugetQoSMenu( )menuRefgetTemplateList( )templateListgetTemplate(templateType)templateRefETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 10Test CM_04 Summary: ge

24、tTemplateType, successful Reference: ES 201 915-10 1, clauses 8.1, 8.4 and 8.5 Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of Tp

25、StringList is returned 3. Method call getTemplate() on IpQoSMenu Parameters: Valid value of templateType, which is an item of the TpStringList, returned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call getTemplateType() on IpQoSTemplate Parameters: None Check: valid value of TpS

26、tring is returned : AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefgetTemplateTy pe( )templateTypeETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 11Test CM_05 Summary: getDescription, successful Reference:

27、 ES 201 915-10 1, clauses 8.1, 8.4 and 8.5 Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of TpStringList is returned 3. Method cal

28、l getTemplate() on IpQoSMenu Parameters: Valid value of templateType, which is an item of the TpStringList, returned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call getDescription() on IpQoSTemplate Parameters: None Check: valid value of TpString is returned : AppLogic : IpConn

29、ectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefgetDescription( )descriptionETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 12Test CM_06 Summary: setSlaID, successful Reference: ES 201 915-10 1, clauses 8.1, 8.4 and 8.5 Tes

30、t Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of TpStringList is returned 3. Method call getTemplate() on IpQoSMenu Parameters: Valid

31、 value of templateType, which is an item of the TpStringList, returned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call setSlaID() on IpQoSTemplate Parameters: Valid SlaID Check: no exception is returned : AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu(

32、)menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefsetSlaID(slaID)ETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 13Test CM_07 Summary: setSlaID, P_ILLEGAL_SLA_ID Reference: ES 201 915-10 1, clauses 8.1, 8.4 and 8.5 Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManage

33、r Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of TpStringList is returned 3. Method call getTemplate() on IpQoSMenu Parameters: Valid value of templateType, which is an item of the TpStringList, r

34、eturned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call setSlaID() on IpQoSTemplate Parameters: Invalid SlaID Check: P_ILLEGAL_SLA_ID exception is returned : AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plate

35、Ty pe)templateListtemplateRefsetSlaI D(inv alid slaID)P_ILLEGAL_SLA_IDETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 14Test CM_08 Summary: getPipeQoSInfo, setPipeQoSInfo, successful Reference: ES 201 915-10 1, clauses 8.1, 8.4 and 8.5 Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Par

36、ameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of TpStringList is returned 3. Method call getTemplate() on IpQoSMenu Parameters: Valid value of templateType, which is an item of the TpStringList, return

37、ed in 2. Check: valid value of IpInterfaceRef is returned 4. Method call getPipeQoSInfo() on IpQoSTemplate Parameters: None Check: valid TpPipeQoSInfo is returned 5. Method call setPipeQoSInfo() on IpQoSTemplate Parameters: valid pipeQoSInfo with different values of the structure returned in 4. Chec

38、k: no exception is returned 6. Method call getPipeQoSInfo() on IpQoSTemplate Parameters: None Check: TpPipeQoSInfo given in 5. is returned ETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 15: AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem p

39、lateTy pe)templateListtemplateRefgetPipeQoSInf o( )pipeQoSInf osetPipeQoSInf o(pipeQoSInf o)getPipeQoSInf o( )pipeQoSInf oETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 16Test CM_09 Summary: setPipeQoSInfo, P_ILLEGAL_TAG Reference: ES 201 915-10 1, clauses 8.1, 8.4 and 8.5 Test Sequence: 1. Method call ge

40、tQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of TpStringList is returned 3. Method call getTemplate() on IpQoSMenu Parameters: Valid value of templateType, which

41、 is an item of the TpStringList, returned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call setPipeQoSInfo() on IpQoSTemplate Parameters: pipeQoSInfo with a value tagged with “providerSpecified“ or “unspecified“. Check: P_ILLEGAL_TAG exception is returned : AppLogic : IpConnectiv

42、 ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefsetPipeQoSInf o(pipeQoSInf o prov iderSpecif ied or unspecif ied)P_ILLEGAL_TAGETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 17Test CM_10 Summary: setPipeQoSInfo, P_ILLEGAL_VALUE

43、Reference: ES 201 915-10 1, clauses 8.1, 8.4 and 8.5 Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of TpStringList is returned 3.

44、Method call getTemplate() on IpQoSMenu Parameters: Valid value of templateType, which is an item of the TpStringList, returned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call setPipeQoSInfo() on IpQoSTemplate Parameters: pipeQoSInfo with an invalid value in a property. Check: P

45、_ILLEGAL_VALUE exception is returned : AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefsetPipeQoSInf o(pipeQoSInf o with inv alid property v alue)P_ILLEGAL_VALUEETSI ETSI ES 202 196-10 V1.2.1 (2005-0

46、2) 18Test CM_11 Summary: setPipeQoSInfo, P_ILLEGAL_COMBINATION Reference: ES 201 915-10 1, clauses 8.1, 8.4 and 8.5 Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Para

47、meters: None Check: valid value of TpStringList is returned 3. Method call getTemplate() on IpQoSMenu Parameters: Valid value of templateType, which is an item of the TpStringList, returned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call setPipeQoSInfo() on IpQoSTemplate Parame

48、ters: pipeQoSInfo with an invalid combination of values. Check: P_ILLEGAL_COMBINATION exception is returned : AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefsetPipeQoSInf o(pipeQoSInf o with illegal

49、 combination of v alues)P_ILLEGAL_COMBINATIONETSI ETSI ES 202 196-10 V1.2.1 (2005-02) 19Test CM_12 Summary: getValidityInfo, setValidityInfo, successful Reference: ES 201 915-10 1, clauses 8.1, 8.4 and 8.5 Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of TpStringList is returned 3. Method call getTemplate() on IpQoSMenu Parameters: Valid value of templ