ETSI ES 202 388-8-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 8 Data Session Control SCF《开放业务接入(OSA)_1.pdf

1、 ETSI ES 202 388-8 V1.1.1 (2005-03)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 8: Data Session Control SCF(Parlay 4)ETSI ETSI ES 202 388-8 V1.1.1 (2005-03) 2 Reference DES/TISPAN-06004-08-OSA Keywords API, OSA, TSS E

2、ssential, 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,

3、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 Techn

4、ical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 8 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 nece

5、ssary 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 8: Data Session Control SCF (Parlay 4)

6、“. 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 - Part 1

7、: 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 speci

8、fications; 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, the t

9、erms and definitions given in ES 202 915-8 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): Refer

10、 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-8 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 9646-1 3

11、. 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 Control ManagerDS Data Se

12、ssion DSC Data Session Control ICS 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) Data Se

13、ssion Control SCF IpDataSessionControlManager (CM) IpDataSession (DS) 5 Test Purposes (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

14、added to identify the actual test suite (see table 1). Table 1: TP identifier naming convention scheme Identifier: _ = SCF name: “DSC“ for Data Session Control SCF = group number: two character field representing the group reference according to TSS = sequential number: (01 to 99) ETSI ETSI ES 202 3

15、88-8 V1.1.1 (2005-03) 7 5.1.2 Source of TP definition The TPs are based on ES 202 915-8 1. 5.1.3 Test strategy As the base standard ES 202 915-8 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 36

16、3 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 be faced (see ETS 300 406 5). 5.2 TPs for the Data Session Control SCF All ICS items referred to in

17、this clause are as specified in ES 202 363 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 call methods in the application are dependant on the underlying network architecture and ar

18、e out of the scope of this test specification. Those method calls are preceded by the words “Triggered action“. 5.2.1 Data Session Control, SCF side 5.2.1.1 IpDataSessionControlManager Test DSC_CM_01 Summary: IpDataSessionControlManager, mandatory methods, successful. Reference: ES 202 915-8 1, clau

19、se 8.4. Preamble: Registration of the IUT (Data Session Control SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpDataSessionControlManager interface through selecting that service and signing the required service agreement. Test Se

20、quence: 1. Method call createNotifications() Parameters: appDataSessionControlManager (non-NULL), eventCriteria Check: valid value of TpAssignmentID is returned 2. Triggered Action: cause IUT to call reportNotification() method on the testers (applications) IpAppDataSessionControlManager interface.

21、Parameters: dataSessionReference, eventInfo, assignmentID 3. Method call destroyNotification() Parameters: assignmentID Check: no exception is returned ETSI ETSI ES 202 388-8 V1.1.1 (2005-03) 8 : IpAppDataSessionControlManager: IpDataSessionControlManager1. createNotifications(appDataSessionControlM

22、anager, eventCriteria)assignmentID2. reportNotification(dataSessionReference, eventInfo, assignmentID)appDataSession3. destroyNotification(assignmentID)Test DSC_CM_02 Summary: IpDataSessionControlManager, all methods, successful. Reference: ES 202 915-8 1, clause 8.4. Precondition: changeNotificatio

23、n() and getNotifications() implemented. Preamble: Registration of the IUT (Data Session Control SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpDataSessionControlManager interface through selecting that service and signing the req

24、uired service agreement. Test Sequence: 1. Method call createNotifications() Parameters: appDataSessionControlManager (non-NULL), eventCriteria Check: valid value of TpAssignmentID is returned 2. Method call getNotifications() Parameters: none Check: value of TpDataSessionEventCriteriaResultSet cont

25、aining event criteria as specified in 1. is returned 3. Method call changeNotification() Parameters: assignmentID, eventCriteria (different to 1.) Check: no exception is returned 4. Method call getNotifications() Parameters: none Check: value of TpDataSessionEventCriteriaResultSet containing event c

26、riteria as specified in 3. is returned 5. Method call destroyNotification() Parameters: assignmentID Check: no exception is returned 6. Method call destroyNotification() Parameters: assignmentID as received in1. and destroyed in 5. Check: P_INVALID_ASSIGNMENT_ID is returned ETSI ETSI ES 202 388-8 V1

27、.1.1 (2005-03) 9 : IpAppDataSessionControlManager: IpDataSessionControlManager1. createNotification(appDataSessionControlManager, eventCriteria1)assignmentID2. getNotifications( )eventCriteria13. changeNotification(assignmentID, eventCriteria2)4. getNotifications( )eventCriteria25. destroyNotificati

28、on(assignmentID)6. destroyNotification(assignmentID)P_INVALID_ASSIGMENT_IDThis method is used to check that the assignmentID has been correctly released after the destroyNotification() method callTest DSC_CM_03 Summary: IpDataSessionControlManager, createNotification(), P_INVALID_CRITERIA exception.

29、 Reference: ES 202 915-8 1, clauses 7.4.1 and 8.3. Preamble: Registration of the IUT (Data Session Control SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpDataSessionControlManager interface through selecting that service and sign

30、ing the required service agreement. Test Sequence: 1. Method call createNotification() Parameters: appDataSessionControlManager (non-NULL), invalid eventCriteria Check: P_INVALID_CRITERIA is returned ETSI ETSI ES 202 388-8 V1.1.1 (2005-03) 10: IpAppDataSessionControlManager: IpDataSessionControlMana

31、ger1. createNotification(appDataSessionControlManager, invalid eventCriteria)P_INVALID_CRITERIA exceptionTest DSC_CM_04 Summary: IpDataSessionControlManager, destroyNotification(), P_INVALID_ASSIGMENT_ID exception. Reference: ES 202 915-8 1, clauses 7.4.1 and 8.3. Preamble: Registration of the IUT (

32、Data Session Control SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpDataSessionControlManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call createNotification()

33、 Parameters: appDataSessionControlManager (non-NULL), eventCriteria Check: valid value of TpAssignmentID is returned 2. Method call destroyNotification() Parameters: invalid assignmentID Check: P_INVALID_ASSIGMENT_ID is returned : IpAppDataSessionControlManager: IpDataSessionControlManager2. destroy

34、Notification(invalid assignmentID)P_INVALID_ASSIGNMENT exception1. createNotification(appDataSessionControlManager, eventCriteria)assignmentIDETSI ETSI ES 202 388-8 V1.1.1 (2005-03) 11Test DSC_CM_05 Summary: IpDataSessionControlManager, changeNotification(), P_INVALID_ASSIGMENT_ID exception. Referen

35、ce: ES 202 915-8 1, clauses 7.4.1 and 8.3. Precondition: changeNotification() implemented. Preamble: Registration of the IUT (Data Session Control SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpDataSessionControlManager interface

36、 through selecting that service and signing the required service agreement. Test Sequence: 1. Method call createNotification() Parameters: appDataSessionControlManager (non-NULL), eventCriteria Check: valid value of TpAssignmentID is returned 2. Method call changeNotification() Parameters: invalid a

37、ssignmentID, eventCriteria Check: P_INVALID_ASSIGMENT_ID is returned : IpAppDataSessionControlManager: IpDataSessionControlManager2. changeNotification(invalid assignmentID)P_INVALID_ASSIGNMENT exception1. createNotification(appDataSessionControlManager, eventCriteria)assignmentIDTest DSC_CM_06 Summ

38、ary: IpDataSessionControlManager, changeNotification(), P_INVALID_CRITERIA exception. Reference: ES 202 915-8 1, clauses 7.4.1 and 8.3. Precondition: changeNotification() implemented. Preamble: Registration of the IUT (Data Session Control SCF) and the tester (application) to the framework. The test

39、er must have obtained a reference to an instance of the IpDataSessionControlManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call createNotification() Parameters: appDataSessionControlManager (non-NULL), eventCriteria Check: valid

40、value of TpAssignmentID is returned 2. Method call changeNotification() Parameters: assignmentID, invalid eventCriteria Check: P_INVALID_CRITERIA is returned ETSI ETSI ES 202 388-8 V1.1.1 (2005-03) 12: IpDataSessionControlManager: IpAppDataSessionControlManager1. createNotification(appDataSessionCon

41、trolManager, eventCriteria)assignmentID2. changeNotification(invalid eventCriteria)P_INVALID_CRITERIA exceptionTest DSC_CM_07 Summary: All methods, successful, two createNotification() method calls. Reference: ES 202 915-8 1, clause 8.4. Precondition: getNotifications() implemented. Preamble: Regist

42、ration of the IUT (Data Session Control SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpDataSessionControlManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call c

43、reateNotifications() Parameters: appDataSessionControlManager (non-NULL), eventCriteria Check: valid value of TpAssignmentID is returned 2. Method call getNotifications() Parameters: none Check: value of TpDataSessionEventCriteriaResultSet containing event criteria as specified in 1. is returned 3.

44、Method call createNotifications() Parameters: appDataSessionControlManager (non-NULL) different from 1., eventCriteria same as in 1. Check: same value of TpAssignmentID as in 1. is returned 4. Triggered Action: cause IUT to call reportNotification() method on the testers (applications) IpAppDataSess

45、ionControlManager interface Parameters: dataSessionReference, eventInfo, assignmentID Check: The interface given in 3. receives the event 5. Triggered action: Kill the appDataSessionControlManager item referenced in 3. 6. Triggered Action: cause IUT to call reportNotification() method on the testers

46、 (applications) IpAppDataSessionControlManager interface. Parameters: dataSessionReference, eventInfo, assignmentID Check: The interface given in 1. receives the event. ETSI ETSI ES 202 388-8 V1.1.1 (2005-03) 13: IpDataSessionControlManager1 : IpAppDataSessionControlManager1. createNotifications(app

47、DataSessionControlManager1, eventCriteria)assignmentID12. getNotifications ( )eventCriteria2 : IpAppDataSessionControlManager3. createNotifications(appDataSessionControlManager2, eventCriteria)assignmentID14. reportNotification(dataSessionReference, eventInfo, assignmentID1)6. reportNot ificat ion(d

48、at aSessionReference, eventInfo, ass ignmentID1)5.Triggered action: Kill the appDataSessionControlManager item created in 3.Test DSC_CM_08 Summary: All methods, successful, two createNotifications() method calls. Reference: ES 202 915-8 1, clause 8.4 Precondition: enableNotifications() implemented P

49、reamble: Registration of the IUT (Data Session Control SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpDataSessionControlManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call enableNotifications() Parameters: None Check: valid value of TpDataSessionEventCriteriaResultSet is returned 2. Triggered Action: cause IUT to call reportNotification() method on the testers (applications) Ip