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

《ETSI ES 202 196-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》由会员分享，可在线阅读，更多相关《ETSI ES 202 196-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（52页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI ES 202 196-8 V1.2.1 (2005-02)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 8: Data session control SCF(Parlay 3)ETSI ETSI ES 202 196-8 V1.2.1 (2005-02) 2 Reference RES/TISPAN-06005-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 covering Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part 2

5、: “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 mana

6、gement 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 and

7、 Test Purposes (TSS Application Programming Interface (API); Part 8: Data Session 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: “Informa

8、tion 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 ETSI ET

9、S 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-8 1, ISO/IEC 9646-1

10、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 ISO/I

11、EC 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-8 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 Purpose (TP)

12、: 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 Session DSC Data Session Control ICS Implementation Conformance

13、 Statement IUT Implementation 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) Data Session Control SCF: IpDataSessionControlManager (CM). IpDataSession (DS). 5 Test Purposes (TP

14、) 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 conv

15、ention 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 196-8 V1.2.1 (2005-02) 7 5.1.2 Source of TP definition The TPs are based on ES 201 915-8 1

16、. 5.1.3 Test strategy As the base standard ES 201 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 170 2. The TPs are only based on conformance requirements related to the externally observa

17、ble 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 this clause are as specified in ES 202 1702 unless indicated otherwise by another numbere

18、d 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 this test specification. Those method calls are preceded by the word

19、s “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 201 915-8 1, clause 8.4 Preamble: Registration of the IUT (Data Session Control SCF) and the tester (applica

20、tion) 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() Parameters: appDataSessionControlManager (non-NU

21、LL), eventCriteria Check: valid value of TpAssignmentID is returned 2. Triggered Action: cause IUT to call reportNotification() method on the testers (applications) IpAppDataSessionControlManager interface. Parameters: dataSessionReference, eventInfo, assignmentID 3. Method call destroyNotification(

22、) Parameters: assignmentID Check: no exception is returned ETSI ETSI ES 202 196-8 V1.2.1 (2005-02) 8 : IpAppDataSessionControlManager: IpDataSessionControlManager1. createNotification(appDataSessionControlManager, eventCriteria)assignmentID2. reportNotification(dataSessionReference, eventInfo, assig

23、nmentID)appDataSession3. destroyNotification(assignmentID)Test DSC_CM_02 Summary: IpDataSessionControlManager, all methods, successful Reference: ES 201 915-8 1, clause 8.4 Precondition: changeNotification() and getNotifications() implemented Preamble: Registration of the IUT (Data Session Control S

24、CF) 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() Parameters: appDataSe

25、ssionControlManager (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. Method call changeNotification() Parameter

26、s: assignmentID, eventCriteria (different to 1.) Check: no exception is returned 4. Method call getNotifications() Parameters: none Check: value of TpDataSessionEventCriteriaResultSet containing event criteria as specified in 3. is returned 5. Method call destroyNotification() Parameters: assignment

27、ID 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 196-8 V1.2.1 (2005-02) 9 : IpAppDataSessionControlManager: IpDataSessionControlManager1. createNotificatio

28、ns(appDataSessionControlManager, eventCriteria1)assignmentID2. getNotifications( )eventCriteria13. changeNotification(assignmentID, eventCriteria2)4. getNotifications( )eventCriteria25. destroyNotification(assignmentID)6. destroyNotification(assignmentID)P_INVALID_ASSIGMENT_IDThis method is used to

29、check that the assignmentID has been correctly released after the destroyNotification() method callETSI ETSI ES 202 196-8 V1.2.1 (2005-02) 10Test DSC_CM_03 Summary: IpDataSessionControlManager, createNotification(), P_INVALID_CRITERIA exception Reference: ES 201 915-8 1, clauses 7.4.1 and 8.3 Preamb

30、le: 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. Met

31、hod call createNotification() Parameters: appDataSessionControlManager (non-NULL), invalid eventCriteria Check: P_INVALID_CRITERIA is returned : IpAppDataSessionControlManager: IpDataSessionControlManager1. createNotifications(appDataSessionControlManager, invalid eventCriteria)P_INVALID_CRITERIA ex

32、ceptionETSI ETSI ES 202 196-8 V1.2.1 (2005-02) 11Test DSC_CM_04 Summary: IpDataSessionControlManager, destroyNotification(), P_INVALID_ASSIGMENT_ID exception Reference: ES 201 915-8 1, clauses 7.4.1 and 8.3 Preamble: Registration of the IUT (Data Session Control SCF) and the tester (application) to

33、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() Parameters: appDataSessionControlManager (non-NULL), even

34、tCriteria Check: valid value of TpAssignmentID is returned 2. Method call destroyNotification() Parameters: invalid assignmentID Check: P_INVALID_ASSIGMENT_ID is returned : IpAppDataSessionControlManager: IpDataSessionControlManager2. destroyNotification(invalid assignmentID)P_INVALID_ASSIGNMENT exc

35、eption1. createNotifications(appDataSessionControlManager, eventCriteria)assignmentIDETSI ETSI ES 202 196-8 V1.2.1 (2005-02) 12Test DSC_CM_05 Summary: IpDataSessionControlManager, changeNotification(), P_INVALID_ASSIGMENT_ID exception Reference: ES 201 915-8 1, clauses 7.4.1 and 8.3 Precondition: ch

36、angeNotification() 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 required ser

37、vice 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 assignmentID, eventCriteria Check: P_INVALID_ASSIGMENT_ID is

38、returned : IpAppDataSessionControlManager: IpDataSessionControlManager2. changeNotification(invalid assignmentID)P_INVALID_ASSIGNMENT exception1. createNotifications(appDataSessionControlManager, eventCriteria)assignmentIDETSI ETSI ES 202 196-8 V1.2.1 (2005-02) 13Test DSC_CM_06 Summary: IpDataSessio

39、nControlManager, changeNotification(), P_INVALID_CRITERIA exception Reference: ES 201 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 obtaine

40、d 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 value of TpAssignmen

41、tID is returned 2. Method call changeNotification() Parameters: assignmentID, invalid eventCriteria Check: P_INVALID_CRITERIA is returned : IpDataSessionControlManager: IpAppDataSessionControlManager1. createNotifications(appDataSessionControlManager, eventCriteria)assignmentID2. changeNotification(

42、invalid eventCriteria)P_INVALID_CRITERIA exceptionETSI ETSI ES 202 196-8 V1.2.1 (2005-02) 14Test DSC_CM_07 Summary: all methods, successful, two createNotification() method calls Reference: ES 201 915-8 1, clause 8.4 Precondition: getNotifications() implemented Preamble: Registration of the IUT (Dat

43、a 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() Pa

44、rameters: 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. Method call createNotif

45、ication() 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) IpAppDataSessionControlManager interf

46、ace Parameters: dataSessionReferencer, 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 (applications) IpAppDa

47、taSessionControlManager interface. Parameters: dataSessionReference, eventInfo, assignmentID Check: The interface given in 1. receives the event. ETSI ETSI ES 202 196-8 V1.2.1 (2005-02) 151 : IpAppDataSessionControlManager: IpDataSessionControlManager1. createNotification(appDataSessionControlManage

48、r1, eventCriteria)assignmentID12. getNot ifications ( )eventCriteria2 : IpAppDataSessionControlManager3. createNotification(appDataSessionControlManager2, eventCriteria)assignmentID14. reportNotification(dataSessionReference, eventInfo, assignmentID1)6. reportNotification(dataSessionReference, event

49、Info, assignmentID1)5.Triggered ac tion: Kill the appDataSessionControlManager item created in 3.5.2.1.2 IpDataSession Test DSC_DS_01 Summary: IpDataSession, release after connectReq(), successful with interrupt after reportNotification() Reference: ES 201 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