1、 ETSI ES 202 388-12 V1.1.1 (2005-03)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Test Suite Structure and Test Purposes (TSSPart 12: Charging SCF(Parlay 4)ETSI ETSI ES 202 388-12 V1.1.1 (2005-03) 2 Reference DES/TISPAN-06004-12-OSA Keywords API, OSA, TSS Essential,
2、 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, has been
3、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 Technical Comm
4、ittee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 12 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 necessary to
5、 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 12: Charging SCF (Parlay 4)“. 2 ETSI ES 202 36
6、3: “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: General concepts“
7、. 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 specifications; Standard
8、ization 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 terms and definition
9、s given in ES 202 915-12 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 to ISO/IEC 9646-1
10、 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-12 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. IXIT proforma:
11、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 CH CHarging CM Charging Manager CS Charging S
12、essionICS 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) Charging - IpChargingManager (CM
13、) - IpChargingSession (CS) 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 added to identify the actual test suite (se
14、e table 1). Table 1: TP identifier naming convention scheme Identifier: _ = SCG name: “CH“ for CHarging SCF = group number: two character field representing the group reference according to TSS = sequential number: (01 to 99) ETSI ETSI ES 202 388-12 V1.1.1 (2005-03) 7 5.1.2 Source of TP definition T
15、he TPs are based on ES 202 915-12 1. 5.1.3 Test strategy As the base standard ES 202 915-12 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 requiremen
16、ts 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 Charging SCF All ICS items referred to in this clause are as specified in ES 202 363 2 unless indicated oth
17、erwise 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 ar
18、e preceded by the words “Triggered action“. 5.2.1 Charging 5.2.1.1 IpChargingManager Test CH_CM_01 Summary: IpChargingManager, successful. Reference: ES 202 915-12 1, clause 8.1. Preamble: Registration of the IUT (Charging SCF) and the tester (application) to the framework. The tester must have obta
19、ined a reference to an instance of the IpChargingManager interface through selecting that service and signing the required service agreement. Test Sequence: 1. Method call createChargingSession() Parameters: appChargingSession, sessionDescription, merchantAccount, user, correlationID Check: valid va
20、lue of TpChargingSessionID is returned : IpChargingManager : IpAppChargingManager1. createChargingSession(appChargingSession, sessionDescription, merchantAccount, user, correlationID)chargingSessionETSI ETSI ES 202 388-12 V1.1.1 (2005-03) 8 Test CH_CM_02 Summary: IpChargingManager, successful. Refer
21、ence: ES 202 915-12 1, clause 8.1. Preamble: Registration of the IUT (Charging SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpChargingManager interface through selecting that service and signing the required service agreement. Te
22、st Sequence: 1. Method call createSplitChargingSession() Parameters: appChargingSession, sessionDescription, merchantAccount, users, correlationID Check: valid value of TpChargingSessionID is returned : IpChargingManager: IpAppChargingManager1. createSplitChargingSession(appChargingSession, sessionD
23、escription, merchantAccount, users, correlationID)chargingSession5.2.1.2 IpChargingSession Test CH_CS_01 Summary: IpChargingSession, amount reservation and debit, successful. Reference: ES 202 915-12 1, clause 8.3. Precondition: reserveAmountReq, debitAmountReq supported. Preamble: Registration of t
24、he IUT (Charging SCF) and the tester (application) to the framework. The tester must have obtained a reference to an instance of the IpChargingManager interface through selecting that service and signing the required service agreement. Successful call of the createChargingSession() method or the cre
25、ateSplitChargingSession() method on the IpChargingManager interface. Test Sequence: 1. Method call reserveAmountReq() Parameters: sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber Check: no exception is returned 2. Triggered action: cause IUT to cal
26、l reserveAmountRes() method on the testers (applications) IpAppChargingSession interface, i.e. accept the reservation of an amount of money Parameters: sessionID, requestNumber, reservedAmount, sessionTimeLeft, requestNumberNextRequest Check: reservedAmount has a value between the requested preferre
27、dAmount and minimumAmount 3. Method call debitAmountReq() Parameters: sessionID, applicationDescription, amount, closeReservation, requestNumber Check: no exception is returned ETSI ETSI ES 202 388-12 V1.1.1 (2005-03) 9 4. Triggered action: cause IUT to call debitAmountRes() method on the testers (a
28、pplications) IpAppChargingSession interface, i.e. accept the debit request Parameters: sessionID, requestNumber, debitedAmount, reservedAmountLeft, requestNumberNextRequest Check: debitedAmount as requested, reservedAmountLeft correctly calculated 5. Method call release() Parameters: sessionID, requ
29、estNumber Check: no exception is returned : IpAppChargingSession: IpChargingSession1. reserveAmountReq(sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber)2. reserveAmountRes(sessionID, requestNumber, reservedAmount, sessionTimeLeft, requestNumberNext
30、Request)3. debitAmountReq(sessionID, applicationDescription, amount, closeReservation, requestNumber)4. debi tAmountRes(sessi onID, requestNumber, debitedAmount, reservedAmountLeft, requestNumberNextRequest)5. release(sessionID, requestNumber)minimumAmount reservedAmount preferredAmountdebitedAmount
31、 as requested, reservedAmountLeft correctly calculatedTest CH_CS_02 Summary: IpChargingSession, amount reservation and credit, successful. Reference: ES 202 915-12 1, clause 8.3. Precondition: reserveAmountReq, creditAmountReq supported. Preamble: Registration of the IUT (Charging SCF) and the teste
32、r (application) to the framework. The tester must have obtained a reference to an instance of the IpChargingManager interface through selecting that service and signing the required service agreement. Successful call of the createChargingSession() method or the createSplitChargingSession() method on
33、 the IpChargingManager interface. Test Sequence: 1. Method call reserveAmountReq() Parameters: sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber Check: no exception is returned 2. Triggered action: cause IUT to call reserveAmountRes() method on the
34、testers (applications) IpAppChargingSession interface, i.e. accept the reservation of an amount of money Parameters: sessionID, requestNumber, reservedAmount, sessionTimeLeft, requestNumberNextRequest Check: reservedAmount has a value between the requested preferredAmount and minimumAmount 3. Method
35、 call creditAmountReq() Parameters: sessionID, applicationDescription, amount, closeReservation, requestNumber Check: no exception is returned ETSI ETSI ES 202 388-12 V1.1.1 (2005-03) 104. Triggered action: cause IUT to call creditAmountRes() method on the testers (applications) IpAppChargingSession
36、 interface, i.e. accept the credit request Parameters: sessionID, requestNumber, creditedAmount, reservedAmountLeft, requestNumberNextRequest Check: creditedAmount as requested, reservedAmountLeft correctly calculated 5. Method call release() Parameters: sessionID, requestNumber Check: no exception
37、is returned : IpAppChargingSession: IpChargingSession1. reserveAmountReq(sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber)2. reserveAmountRes(sessionID, requestNumber, reservedAmount, sessionTimeLeft, requestNumberNextRequest)3. creditAmountReq(ses
38、sionID, applicationDescription, amount, closeReservation, requestNumber)4. creditAmountRes(sessionID, requestNumber, creditedAmount, reservedAmountLeft, requestNumberNextRequest)5. release(sessionID, requestNumber)mi nimumAmount reservedAmount preferredAmountcreditedAmount as requested, reservedAmou
39、ntLeft correctly calculatedTest CH_CS_03 Summary: IpChargingSession, amount reservation and variation, successful. Reference: ES 202 915-12 1, clause 8.3. Precondition: reserveAmountReq, debitAmountReq, creditAmountReq, getAmountLeft supported. Preamble: Registration of the IUT (Charging SCF) and th
40、e tester (application) to the framework. The tester must have obtained a reference to an instance of the IpChargingManager interface through selecting that service and signing the required service agreement. Successful call of the createChargingSession() method or the createSplitChargingSession() me
41、thod on the IpChargingManager interface. Test Sequence: 1. Method call reserveAmountReq() Parameters: sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber Check: no exception is returned 2. Triggered action: cause IUT to call reserveAmountRes() method
42、on the testers (applications) IpAppChargingSession interface, i.e. accept the reservation of an amount of money Parameters: sessionID, requestNumber, reservedAmount, sessionTimeLeft, requestNumberNextRequest Check: reservedAmount has a value between the requested preferredAmount and minimumAmount ET
43、SI ETSI ES 202 388-12 V1.1.1 (2005-03) 113. Method call creditAmountReq() Parameters: sessionID, applicationDescription, amount, closeReservation false, requestNumber Check: no exception is returned 4. Triggered action: cause IUT to call creditAmountRes() method on the testers (applications) IpAppCh
44、argingSession interface, i.e. accept the credit request Parameters: sessionID, requestNumber, creditedAmount, reservedAmountLeft, requestNumberNextRequest Check: creditedAmount as requested, reservedAmountLeft correctly calculated 5. Method call debitAmountReq() Parameters: sessionID, applicationDes
45、cription, amount, closeReservation false, requestNumber Check: no exception is returned 6. Triggered action: cause IUT to call debitAmountRes() method on the testers (applications) IpAppChargingSession interface, i.e. accept the debit request Parameters: sessionID, requestNumber, debitedAmount, rese
46、rvedAmountLeft, requestNumberNextRequest Check: debitedAmount as requested, reservedAmountLeft correctly calculated 7. Method call getAmountLeft() Parameters: sessionID Check: correct value of TpChargingPrice is returned 8. Method call release() Parameters: sessionID, requestNumber Check: no excepti
47、on is returned : IpAppChargingSession: IpChargingSession1. reserveAmountReq(sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber)2. reserveAmountRes(sessionID, requestNumber, reservedAmount, sessionTimeLeft, requestNumberNextRequest)minimumAmount reser
48、vedAmount preferredAmount3. creditAmountReq(sessionID, applicationDescription, amount, closeReservation, requestNumber)4. creditAmountRes(sessionID, requestNumber, creditedAmount, reservedAmountLeft, requestNumberNextRequest)creditedAmount as requested, reservedAmountLeft correctly calculated5. debi
49、tAmountReq(sessionID, applicationDescription, amount, closeReservation, requestNumber)6. debitAmountRes(sessionID, requestNumber, debitedAmount, reservedAmountLeft, requestNumberNextRequest)debitedAmount as requested, reservedAmountLeft correctly calculated7. getAmountLeft(sessionID)correct amount8. release(sessionID, requestNumber)ETSI ETSI ES 202 388-12 V1.1.1 (2005-03) 12Test CH_CS_04 Summary: IpChargingSession, amount reservation and variation of life time, successful. Reference: ES 202 915-12 1, clause 8.3. Prec
