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

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

2、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 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 Tech

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

5、cessary 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 11: Account Management 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

7、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 spec

8、ifications; 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

9、terms and definitions given in ES 202 915-11 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): Ref

10、er 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-11 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-

11、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: AM Account Management API Application Programming Interface ATM Abstract Test Method ATS Abstract Test Suite ICS

12、 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) Account Management 5 Test Purposes (TP) 5

13、.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 convent

14、ion scheme Identifier: _ = SCG name: “AM“ for Account Management part of Account Management 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-11 1. ETSI ETSI ES 202 3

15、88-11 V1.1.1 (2005-03) 7 5.1.3 Test strategy As the base standard ES 202 915-11 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 requirements related t

16、o 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 Account Management SCF All ICS items referred to in this clause are as specified in ES 202 363 2 unless indicated other

17、wise 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 method calls are

18、preceded by the words “Triggered action“. 5.2.1 Account Management Test AM_01 Summary: IpAccountManager all methods, successful. Reference: ES 202 915-11 1, clause 8.1. Precondition: createNotification and destroyNotification supported. Preamble: Registration of the IUT (Account Manager SCF) and the

19、 tester (application) to the framework. The tester must have obtained a reference to an instance of the IpAccountManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call setCallback() Parameters: appInterface with value of testers (Ap

20、plications) IpAppAccountManager interface Check: no exception is returned 2. Method call createNotification() Parameters: appAccountManager, chargingEventCriteria Check: valid value of TpAssignmentID is returned 3. Triggered action: cause IUT to call reportNotification() method on the testers (Appli

21、cation) IpAppAccountManager interface. Parameters: chargingEventInfo, assignmentId 4. Method call destroyNotification() Parameters: assignmentID given in 2. Check: no exception is returned ETSI ETSI ES 202 388-11 V1.1.1 (2005-03) 8 : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2

22、. c reateNotification(appAccountManager, chargingEventCriteria)assignmentID( )3. reportNotification(chargingEventInfo, assignmentId)4. destroyNotification(assignmentId)Test AM_02 Summary: IpAccountManager all methods, successful. Reference: ES 202 915-11 1, clause 8.1. Precondition: createNotificati

23、on, destroyNotification, getNotification and changeNotification supported. Preamble: Registration of the IUT (Account Manager SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpAccountManager interface through selecting that service

24、and signing the required service agreement. Test Sequence: 1. Method call setCallback() Parameters: appInterface with value of testers (Applications) IpAppAccountManager interface Check: no exception is returned 2. Method call createNotification() Parameters: appAccountManager, chargingEventCriteria

25、 Check: valid value of TpAssignmentID is returned 3. Method call getNotification() Parameters: None Check: valid value of TpChargingEventCriteriaResultSet is returned, which corresponds to notification created in 1. 4. Method call changeNotification() Parameters: assignmentID give in 1., eventCriter

26、ia Check: no exception is returned 5. Method call getNotification() Parameters: None Check: valid value of TpChargingEventCriteriaResultSet is returned, which corresponds to the change made in 3. ETSI ETSI ES 202 388-11 V1.1.1 (2005-03) 9 6. Method call destroyNotification() Parameters: assignmentID

27、 give in 1. Check: no exception is returned : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. createNotification(appAccountManager, chargingEventCriteria)assignmentID( )3. getNotification( )chargingEventCriteriaResultSet( )4. changeNotification(assignmentID, eventCriteria)5. getN

28、otification( )chargingEventCriteriaResultSet( )6. destroyNotification(assignmentId)ETSI ETSI ES 202 388-11 V1.1.1 (2005-03) 10Test AM_03 Summary: IpAccountManager createNotification, P_INVALID_CRITERIA. Reference: ES 202 915-11 1, clause 8.1. Precondition: createNotification supported. Preamble: Reg

29、istration of the IUT (Account Manager SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpAccountManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call setCallback()

30、Parameters: appInterface with value of testers (Applications) IpAppAccountManager interface Check: no exception is returned 2. Method call createNotification() Parameters: appAccountManager, invalid chargingEventCriteria Check: P_INVALID_CRITERIA is returned : IpAppAccountManager: IpAccountManager1.

31、 setCallback(appInterface)2. createNotification(appAccountManager, chargingEventCriteria)P_INVALID_CRITERIA( )ETSI ETSI ES 202 388-11 V1.1.1 (2005-03) 11Test AM_04 Summary: IpAccountManager changeNotification, P_INVALID_CRITERIA. Reference: ES 202 915-11 1, clause 8.1. Precondition: createNotificati

32、on and changeNotification supported. Preamble: Registration of the IUT (Account Manager SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpAccountManager interface through selecting that service and signing the required service agree

33、ment. Test Sequence: 1. Method call setCallback() Parameters: appInterface with value of testers (Applications) IpAppAccountManager interface Check: no exception is returned 2. Method call createNotification() Parameters: appAccountManager, chargingEventCriteria Check: valid value of TpAssignmentID

34、is returned 3. Method call changeNotification() Parameters: assignmentID give in 1., invalid eventCriteria Check: P_INVALID_CRITERIA is returned 4. Method call destroyNotification() Parameters: assignmentID give in 2. Check: no exception is returned : IpAppAccountManager: IpAccountManager1. setCallb

35、ack(appInterface)2. createNotification(appAccountManager, chargingEventCriteria)assignmentID( )3. changeNotification(assignmentID, eventCriteria)4. destroyNotification(assignmentId)P_INVALID_CRITERIA( )ETSI ETSI ES 202 388-11 V1.1.1 (2005-03) 12Test AM_05 Summary: IpAccountManager changeNotification

36、, P_INVALID_ASSIGNMENT_ID. Reference: ES 202 915-11 1, clause 8.1. Precondition: createNotification and changeNotification supported. Preamble: Registration of the IUT (Account Manager SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the

37、 IpAccountManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call setCallback() Parameters: appInterface with value of testers (Applications) IpAppAccountManager interface Check: no exception is returned 2. Method call createNotifica

38、tion() Parameters: appAccountManager, chargingEventCriteria Check: valid value of TpAssignmentID is returned 3. Method call changeNotification() Parameters: invalid assignmentID, eventCriteria Check: P_INVALID_ASSIGNMENT_ID is returned 4. Method call destroyNotification() Parameters: assignmentID gi

39、ve in 2. Check: no exception is returned : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. createNotification(appAccountManager, chargingEventCriteria)assignmentID( )3. changeNotification(assignmentID, eventCriteria)4. destroyNotification(assignmentId)P_INVALID_ASSIGNMENT_IDETSI

40、ETSI ES 202 388-11 V1.1.1 (2005-03) 13Test AM_06 Summary: IpAccountManager destroyNotification, P_INVALID_ASSIGNMENT_ID. Reference: ES 202 915-11 1, clause 8.1. Precondition: createNotification and destroyNotification supported. Preamble: Registration of the IUT (Account Manager SCF) and the tester

41、(application) to the framework. The tester must have obtained a reference to an instance of the IpAccountManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call setCallback() Parameters: appInterface with value of testers (Applicatio

42、ns) IpAppAccountManager interface Check: no exception is returned 2. Method call createNotification() Parameters: appAccountManager, chargingEventCriteria Check: valid value of TpAssignmentID is returned 3. Method call destroyNotification() Parameters: invalid assignmentID Check: P_INVALID_ASSIGNMEN

43、T_ID is returned 4. Method call destroyNotification() Parameters: assignmentID give in 2. Check: no exception is returned : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. createNotification(appAccountManager, chargingEventCriteria)assignmentID( )3. destroyNotification(invalid as

44、signmentID)4. destroyNotification(assignmentId)P_INVALID_ASSIGNMENT_IDETSI ETSI ES 202 388-11 V1.1.1 (2005-03) 14Test AM_07 Summary: IpAccountManager all methods, successful. Reference: ES 202 915-11 1, clause 8.1. Precondition: retrieveTransactionHistoryReq supported. Preamble: Registration of the

45、IUT (Account Manager SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpAccountManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call setCallback() Parameters: appIn

46、terface with value of testers (Applications) IpAppAccountManager interface Check: no exception is returned. 2. Method call retrieveTransactionHistoryReq() Parameters: user, transactionInterval Check: valid value of TpAssignmentID is returned 3. Triggered action: cause IUT to call retrieveTransaction

47、HistoryRes() method on the testers (Application) IpAppAccountManager interface. Parameters: retrievalID, transactionHistory : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. retrieveTransactionHistoryReq(user, transactionInterval)assignmentID( )3. retrieveTransactionHistoryRes(re

48、trievalID, transactionHistory)ETSI ETSI ES 202 388-11 V1.1.1 (2005-03) 15Test AM_08 Summary: IpAccountManager retrieveTransactionHistoryReq, P_UNKNOWN_SUBSCRIBER. Reference: ES 202 915-11 1, clause 8.1. Precondition: retrieveTransactionHistoryReq supported. Preamble: Registration of the IUT (Account

49、 Manager SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpAccountManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call setCallback() Parameters: appInterface with value of testers (Applications) IpAppAccountManager interface Check: no exception is returned 2. Method call retrieveTransactionHistoryReq() Parameters: invalid user, transactionInterval Check: P_UNKNOWN_SUBSCRIBE