ETSI ES 202 388-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

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

5、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 Purposes (TSS Application Programming Interface (API); Part 10: Connectivity Manager SCF (Parl

6、ay 4)“. 2 ETSI ES 202 363: “Open Service Access (OSA); Application Programming Interface (API); Implementation Conformance Statement (ICS) proforma specification; (Parlay 4)“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - P

7、art 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: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing

8、specifications; Standardization methodology“. 6 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)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document,

9、the terms and definitions given in ES 202 915-10 1, ISO/IEC 9646-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. Implementation Under Test (IUT):

10、 Refer to ISO/IEC 9646-1 3. Lower Tester (LT): Refer to ISO/IEC 9646-1 3. Implementation Conformance Statement (ICS): Refer to ISO/IEC 9646-1 3. ETSI ETSI ES 202 388-10 V1.1.1 (2005-03) 6 ICS proforma: Refer to ISO/IEC 9646-1 3. Implementation eXtra Information for Testing (IXIT): Refer to ISO/IEC 9

11、646-1 3. IXIT proforma: Refer to ISO/IEC 9646-1 3. Test Purpose (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 Manag

12、erICS Implementation Conformance Statement IUT Implementation Under Test IXIT Implementation eXtra Information for Testing LT Lower Tester OSA Open Service Access SCF Service Capability Feature TP Test Purpose TSS Test Suite Structure 4 Test Suite Structure (TSS) Connectivity Manager 5 Test Purposes

13、 (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming convention 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

14、convention scheme Identifier: _ = SCG name: “CM“ for Connectivity Manager part of Connectivity 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 202 915-10 1. ETSI ET

15、SI ES 202 388-10 V1.1.1 (2005-03) 7 5.1.3 Test strategy As the base standard ES 202 915-10 1 contains no explicit requirements for testing, the TPs were generated as a result of an analysis of the base standard and the ICS specification ES 202 363 2. The TPs are only based on conformance requirement

16、s related to the externally observable behaviour of the IUT and are limited to conceivable situations to which a real implementation is likely to be faced (see ETS 300 406 5). 5.2 TPs for the Connectivity Manager SCF All ICS items referred to in this clause are as specified in ES 202 363 2 unless in

17、dicated otherwise by another numbered reference. All parameters 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 meth

18、od calls are preceded by the words “Triggered action“. 5.2.1 Connectivity Manager Test CM_01 Summary: getQoSMenu, successful. Reference: ES 202 915-10 1, clause 8.1. Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of IpInterfaceRef is returned

19、AppLogic : IpConnectivityManagergetQoSMenu( )menuRefETSI ETSI ES 202 388-10 V1.1.1 (2005-03) 8 Test CM_02 Summary: getTemplateList, successful. Reference: ES 202 915-10 1, clauses 8.1 and 8.4. Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager Parameters: None Check: valid value of

20、IpInterfaceRef is returned 2. Method call getTemplateList() on IpQoSMenu Parameters: None Check: valid value of TpStringList is returned : AppLogic : IpConnectivityManager: IpQoSMenugetQoSMenu( )menuRefgetTemplateList( )templateListTest CM_03 Summary: getTemplate, successful. Reference: ES 202 915-1

21、0 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 Check: valid value of TpStringList is returned 3. Method call getTemplate() o

22、n IpQoSMenu Parameters: Valid value of templateType, which is an item of the TpStringList, returned in 2. Check: valid value of IpInterfaceRef is returned ETSI ETSI ES 202 388-10 V1.1.1 (2005-03) 9 : AppLogic : IpConnectivityManager: IpQoSMenugetQoSMenu( )menuRefgetTemplateList( )templateListgetTemp

23、late(templateType)templateRefTest CM_04 Summary: getTemplateType, successful. Reference: ES 202 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() o

24、n 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, returned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call getTemplateType() on IpQ

25、oSTemplate Parameters: None Check: valid value of TpString is returned ETSI ETSI ES 202 388-10 V1.1.1 (2005-03) 10: AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefgetTemplateTy pe( )templateTypeTest

26、 CM_05 Summary: getDescription, successful. Reference: ES 202 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

27、: 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 getDescription() on IpQoSTemplate Parameters: None Check:

28、valid value of TpString is returned ETSI ETSI ES 202 388-10 V1.1.1 (2005-03) 11: AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefgetDescription( )descriptionTest CM_06 Summary: setSlaID, successful.

29、Reference: ES 202 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.

30、 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 setSlaID() on IpQoSTemplate Parameters: Valid SlaID Check: no exception is returned ETSI ETSI ES 202 3

31、88-10 V1.1.1 (2005-03) 12: AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefsetSlaID(slaID)Test CM_07 Summary: setSlaID, P_ILLEGAL_SLA_ID. Reference: ES 202 915-10 1, clauses 8.1, 8.4 and 8.5. Test Se

32、quence: 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 val

33、ue 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: Invalid SlaID Check: P_ILLEGAL_SLA_ID exception is returned ETSI ETSI ES 202 388-10 V1.1.1 (2005-03) 13: AppLogic : IpConne

34、ctiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefsetSlaI D(inv alid slaID)P_ILLEGAL_SLA_IDTest CM_08 Summary: getPipeQoSInfo, setPipeQoSInfo, successful. Reference: ES 202 915-10 1, clauses 8.1, 8.4 and 8.5. Test Seque

35、nce: 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

36、of templateType, which is an item of the TpStringList, returned 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 pipeQoSIn

37、fo with different values of the structure returned in 4. Check: no exception is returned 6. Method call getPipeQoSInfo() on IpQoSTemplate Parameters: None Check: TpPipeQoSInfo given in 5. is returned ETSI ETSI ES 202 388-10 V1.1.1 (2005-03) 14: AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTe

38、mplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefgetPipeQoSInf o( )pipeQoSInf osetPipeQoSInf o(pipeQoSInf o)getPipeQoSInf o( )pipeQoSInf oTest CM_09 Summary: setPipeQoSInfo, P_ILLEGAL_TAG. Reference: ES 202 915-10 1, clauses 8.1, 8.4 and 8.5. Test Sequenc

39、e: 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

40、 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 a value tagged with “providerSpecified“ or “unspecified“. Check: P_ILLEGAL_TAG exception is returned ETSI

41、 ETSI ES 202 388-10 V1.1.1 (2005-03) 15: AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefsetPipeQoSInf o(pipeQoSInf o prov iderSpecif ied or unspecif ied)P_ILLEGAL_TAGTest CM_10 Summary: setPipeQoSIn

42、fo, P_ILLEGAL_VALUE. Reference: ES 202 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 TpStri

43、ngList 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 Parameters: pipeQoSInfo with an invalid value i

44、n a property. Check: P_ILLEGAL_VALUE exception is returned ETSI ETSI ES 202 388-10 V1.1.1 (2005-03) 16: AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy pe)templateListtemplateRefsetPipeQoSInf o(pipeQoSInf o with inv alid prop

45、erty v alue)P_ILLEGAL_VALUETest CM_11 Summary: setPipeQoSInfo, P_ILLEGAL_COMBINATION. Reference: ES 202 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 getTemplate

46、List() 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, returned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call setPipeQoSInfo()

47、 on IpQoSTemplate Parameters: pipeQoSInfo with an invalid combination of values. Check: P_ILLEGAL_COMBINATION exception is returned ETSI ETSI ES 202 388-10 V1.1.1 (2005-03) 17: AppLogic : IpConnectiv ity Manager: IpQoSMenu : IpQoSTemplategetQoSMenu( )menuRefgetTemplateList( )getTemplate(tem plateTy

48、pe)templateListtemplateRefsetPipeQoSInf o(pipeQoSInf o with illegal combination of v alues)P_ILLEGAL_COMBINATIONTest CM_12 Summary: getValidityInfo, setValidityInfo, successful. Reference: ES 202 915-10 1, clauses 8.1, 8.4 and 8.5. Test Sequence: 1. Method call getQoSMenu() on IpConnectivityManager

49、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, returned in 2. Check: valid value of IpInterfaceRef is returned 4. Method call getValidityInfo() on IpQoSTemplate Parameters: None Check: valid TpValidityInfo is returned 5. Method call setValidityInfo() on IpQoSTemplate Pa