1、 ETSI ES 202 196-11 V1.2.1 (2005-02)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 11: Account management SCF(Parlay 3)ETSI ETSI ES 202 196-11 V1.2.1 (2005-02) 2 Reference RES/TISPAN-06005-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 covering Open Service Access (OSA); Application Programming Interface (API); Test Suite Structure and Test Purposes (TSS Part
5、 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 ma
6、nagement 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 a
7、nd Test Purposes (TSS Application Programming Interface (API); Part 11: Account Management 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: “Inform
8、ation 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 E
9、TS 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-11 1, ISO/IEC 9646-
10、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 ISO
11、/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-11 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 (
12、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 Implementation Conformance Statement IUT Implementation Unde
13、r 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) Account Management. 5 Test Purposes (TP) 5.1 Introduction For each test requirement a TP is defined. 5.1.1 TP naming convention TPs a
14、re 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: “AM“ for Account Management part of Account Management
15、 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-11 1. 5.1.3 Test strategy As the base standard ES 201 915-11 1 contains no explicit requirements for testing, the T
16、Ps 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 is likely to
17、 be faced (see ETS 300 406 5). ETSI ETSI ES 202 196-11 V1.2.1 (2005-02) 7 5.2 TPs for the Account Management 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 are valid unle
18、ss 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 Account Management Test AM_01 Summary: I
19、pAccountManager all methods, successful Reference: ES 201 915-11 1, clause 8.1 Precondition: createNotification and destroyNotification 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 ins
20、tance 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 cr
21、eateNotification() Parameters: chargingEventCriteria Check: valid value of TpAssignmentID is returned 3. Triggered action: cause IUT to call reportNotification() method on the testers (Application) IpAppAccountManager interface. Parameters: chargingEventInfo, assignmentId 4. Method call destroyNotif
22、ication() Parameters: assignmentID given in 2. Check: no exception is returned ETSI ETSI ES 202 196-11 V1.2.1 (2005-02) 8 : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. createNotification(chargingEventCriteria)assignmentID( )3. reportNotification(chargingEventInfo, assignmentI
23、d)4. destroyNotification(assignmentId)Test AM_02 Summary: IpAccountManager all methods, successful Reference: ES 201 915-11 1, clause 8.1 Precondition: createNotification, destroyNotification, getNotification and changeNotification supported Preamble: Registration of the IUT (Account Manager SCF) an
24、d 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 tester
25、s (Applications) IpAppAccountManager interface Check: no exception is returned 2. Method call createNotification() Parameters: chargingEventCriteria Check: valid value of TpAssignmentID is returned 3. Method call getNotification() Parameters: None Check: valid value of TpChargingEventCriteriaResultS
26、et is returned, which corresponds to notification created in 1. 4. Method call changeNotification() Parameters: assignmentID give in 1., eventCriteria Check: no exception is returned 5. Method call getNotification() Parameters: None Check: valid value of TpChargingEventCriteriaResultSet is returned,
27、 which corresponds to the change made in 3 6. Method call destroyNotification() Parameters: assignmentID give in 1. Check: no exception is returned ETSI ETSI ES 202 196-11 V1.2.1 (2005-02) 9 : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. createNotification(chargingEventCriteri
28、a)assignmentID( )3. getNotification( )chargingEventCriteriaResultSet.4. changeNotification(assignmentID, eventCriteria)5. getNotification( )chargingEventCriteriaResultSet.6. destroyNotification(assignmentId)ETSI ETSI ES 202 196-11 V1.2.1 (2005-02) 10Test AM_03 Summary: IpAccountManager createNotific
29、ation, P_INVALID_CRITERIA Reference: ES 201 915-11 1, clause 8.1 Precondition: createNotification 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 interfac
30、e 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 createNotification() Parameters: invalid
31、 chargingEventCriteria Check: P_INVALID_CRITERIA is returned : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. createNotification(invalid chargingEventCriteria)P_INVALID_CRITERIA( )ETSI ETSI ES 202 196-11 V1.2.1 (2005-02) 11Test AM_04 Summary: IpAccountManager changeNotification,
32、 P_INVALID_CRITERIA Reference: ES 201 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 IpAccoun
33、tManager 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 createNotification() Pa
34、rameters: chargingEventCriteria Check: valid value of TpAssignmentID 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 exc
35、eption is returned : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. createNotification(chargingEventCriteria)assignmentID( )3. changeNotification(assignmentID, invalid eventCriteria)4. destroyNotification(assignmentId)P_INVALID_CRITERIA( )ETSI ETSI ES 202 196-11 V1.2.1 (2005-02)
36、 12Test AM_05 Summary: IpAccountManager changeNotification, P_INVALID_ASSIGNMENT_ID Reference: ES 201 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 test
37、er 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:
38、 no exception is returned 2. Method call createNotification() Parameters: 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 destroyNotifi
39、cation() Parameters: assignmentID give in 2. Check: no exception is returned : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. createNotification(chargingEventCriteria)assignmentID( )3. c hangeNotification(invalid assignmentID, eventCriteria)4. destroyNotification(assignmentId)P_
40、INVALID_ASSIGNMENT_IDETSI ETSI ES 202 196-11 V1.2.1 (2005-02) 13Test AM_06 Summary: IpAccountManager destroyNotification, P_INVALID_ASSIGNMENT_ID Reference: ES 201 915-11 1, clause 8.1 Precondition: createNotification and destroyNotification supported Preamble: Registration of the IUT (Account Manag
41、er 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
42、 of testers (Applications) IpAppAccountManager interface Check: no exception is returned 2. Method call createNotification() Parameters: chargingEventCriteria Check: valid value of TpAssignmentID is returned 3. Method call destroyNotification() Parameters: invalid assignmentID Check: P_INVALID_ASSIG
43、NMENT_ID is returned 4. Method call destroyNotification() Parameters: assignmentID give in 2. Check: no exception is returned : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. createNotification(chargingEventCriteria)assignmentID( )3. destroyNotification(invalid assignmentID)4. d
44、estroyNotification(assignmentId)P_INVALID_ASSIGNMENT_IDETSI ETSI ES 202 196-11 V1.2.1 (2005-02) 14Test AM_07 Summary: IpAccountManager all methods, successful Reference: ES 201 915-11 1, clause 8.1 Precondition: retrieveTransactionHistoryReq supported Preamble: Registration of the IUT (Account Manag
45、er 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
46、 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 retrieveTransactionHistoryRes() metho
47、d on the testers (Application) IpAppAccountManager interface. Parameters: retrievalID, transactionHistory : IpAppAccountManager: IpAccountManager1. setCallback(appInterface)2. retrieveTransactionHistoryReq(user, transactionInterval)assignmentID( )3. retrieveTransactionHistoryRes(retrievalID, transac
48、tionHistory)ETSI ETSI ES 202 196-11 V1.2.1 (2005-02) 15Test AM_08 Summary: IpAccountManager retrieveTransactionHistoryReq, P_UNKNOWN_SUBSCRIBER Reference: ES 201 915-11 1, clause 8.1 Precondition: retrieveTransactionHistoryReq supported Preamble: Registration of the IUT (Account Manager SCF) and the
49、 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_SUBSCRIBER is returned, or Check:
