ETSI ES 202 196-12-2005 Open Service Access (OSA) Application Programming Interface (API) Test Suite Structure and Test Purposes (TSS&TP) Part 12 Charging SCF《开放业务接入(OSA) 应用编程接口(AP.pdf

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

5、n 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 management S

6、CF“; 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 Test Pu

7、rposes (TSS Application Programming Interface (API); Part 12: Charging 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: “Information technology - O

8、pen 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 ETS 300 406: “Methods

9、 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-12 1, ISO/IEC 9646-1 3, ISO/IEC 9646-2

10、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/IEC 9646-1 3. Imple

11、mentation 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-12 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): Refer to ISO/IE

12、C 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 SessionICS Implementation Conformance Statement IUT Implementa

13、tion 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) Charging: - IpChargingManager (CM); - IpChargingSession (CS). 5 Test Purposes (TP) 5.1 Introduction For each test requiremen

14、t 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 convention scheme Identifier: _ = SCG name: “CH

15、“ for CHarging 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-12 1. ETSI ETSI ES 202 196-12 V1.2.1 (2005-02) 7 5.1.3 Test strategy As the base standard ES 201 915-

16、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 170 2. The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT and are limited to conceivab

17、le 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 170 2 unless indicated otherwise by another numbered reference. All parameters specified in method calls are valid

18、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 words “Triggered action“. 5.2.1 Charging 5.2.1.1 IpChargingManager T

19、est CH_CM_01 Summary: IpChargingManager, successful Reference: ES 201 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 tha

20、t service and signing the required service agreement. Test Sequence: 1. Method call createChargingSession() Parameters: appChargingSession, sessionDescription, merchantAccount, user, correlationID Check: valid value of TpChargingSessionID is returned : IpChargingManager : IpAppChargingManager1. crea

21、teChargingSession(appChargingSession, sessionDescription, merchantAccount, user, correlationID)chargingSessionIDETSI ETSI ES 202 196-12 V1.2.1 (2005-02) 8 5.2.1.2 IpChargingSession Test CH_CS_01 Summary: IpChargingSession, amount reservation and debit, successful Reference: ES 201 915-12 1, clause 8

22、.3 Precondition: reserveAmountReq, debitAmountReq supported 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 requi

23、red service agreement. Successful call of the createChargingSession() method on the IpChargingManager interface. Test Sequence: 1. Method call reserveAmountReq() Parameters: sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber Check: no exception is re

24、turned 2. Triggered action: cause IUT to call 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: reservedAmoun

25、t has a value between the requested preferredAmount and minimumAmount 3. Method call debitAmountReq() Parameters: sessionID, applicationDescription, amount, closeReservation, requestNumber Check: no exception is returned 4. Triggered action: cause IUT to call debitAmountRes() method on the testers (

26、applications) 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, req

27、uestNumber Check: no exception is returned ETSI ETSI ES 202 196-12 V1.2.1 (2005-02) 9 : IpAppChargingSession: IpAppChargingManager: IpChargingManager: IpChargingSessionPreamble: createChargingSession(appChargingSession, sessionDescription, merchantAccount, user, correlationID)chargingSessionID1. res

28、erveAmountReq(sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber)2. reserveAmountRes(sessionID, requestNumber, reservedAmount, sessionTimeLeft, requestNumberNextRequest)3. debitAmountReq(sessionID, applicationDescription, amount, closeReservation, re

29、questNumber)4. debitAmountRes(sessionID, requestNumber, debitedAmount, reservedAmountLeft, requestNumberNextRequest)5. release(sessionID, requestNumber)minimumAmount reservedAmount preferredAmountdebitedAmount as requested, reservedAmountLeft correctly calculatedETSI ETSI ES 202 196-12 V1.2.1 (2005-

30、02) 10Test CH_CS_02 Summary: IpChargingSession, amount reservation and credit, successful Reference: ES 201 915-12 1, clause 8.3 Precondition: reserveAmountReq, creditAmountReq supported Preamble: Registration of the IUT (Charging SCF) and the tester (application) to the framework. The tester must h

31、ave 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 on the IpChargingManager interface. Test Sequence: 1. Method call reserveAmountReq() Parameters:

32、 sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber Check: no exception is returned 2. Triggered action: cause IUT to call reserveAmountRes() method on the testers (applications) IpAppChargingSession interface, i.e. accept the reservation of an amoun

33、t of money Parameters: sessionID, requestNumber, reservedAmount, sessionTimeLeft, requestNumberNextRequest Check: reservedAmount has a value between the requested preferredAmount and minimumAmount 3. Method call creditAmountReq() Parameters: sessionID, applicationDescription, amount, closeReservatio

34、n, requestNumber Check: no exception is returned 4. Triggered action: cause IUT to call creditAmountRes() method on the testers (applications) IpAppChargingSession interface, i.e. accept the credit request Parameters: sessionID, requestNumber, creditedAmount, reservedAmountLeft, requestNumberNextReq

35、uest Check: creditedAmount as requested, reservedAmountLeft correctly calculated 5. Method call release() Parameters: sessionID, requestNumber Check: no exception is returned ETSI ETSI ES 202 196-12 V1.2.1 (2005-02) 11: IpAppChargingSession: IpAppChargingManager: IpChargingManager: IpChargingSession

36、Preamble: createChargingSession(appChargingSession, sessionDescription, merchantAccount, user, correlationID)chargingSessionID1. reserveAmountReq(sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber)2. reserveAmountRes(sessionID, requestNumber, reserve

37、dAmount, sessionTimeLeft, requestNumberNextRequest)3. creditAmountReq(sessionID, applicationDescription, amount, closeReservation, requestNumber)4. credi tAmountRes(sessionID, requestNumber, creditedAmount, reservedAmountLeft, requestNumberNextRequest)5. release(sessionID, requestNumber)minimumAmoun

38、t reservedAmount preferredAmountcreditedAmount as requested, reservedAmountLeft correctly calculatedETSI ETSI ES 202 196-12 V1.2.1 (2005-02) 12Test CH_CS_03 Summary: IpChargingSession, amount reservation and variation, successful Reference: ES 201 915-12 1, clause 8.3 Precondition: reserveAmountReq,

39、 debitAmountReq, creditAmountReq, getAmountLeft supported. 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 requir

40、ed service agreement. Successful call of the createChargingSession() method on the IpChargingManager interface. Test Sequence: 1. Method call reserveAmountReq() Parameters: sessionID, applicationDescription, chargingParameters, preferredAmount, minimumAmount, requestNumber Check: no exception is ret

41、urned 2. Triggered action: cause IUT to call 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

42、 has a value between the requested preferredAmount and minimumAmount 3. Method call creditAmountReq() Parameters: sessionID, applicationDescription, amount, closeReservation, requestNumber Check: no exception is returned 4. Triggered action: cause IUT to call creditAmountRes() method on the testers

43、(applications) IpAppChargingSession 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: ses

44、sionID, applicationDescription, amount, closeReservation, 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, deb

45、itedAmount, reservedAmountLeft, 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 C

46、heck: no exception is returned ETSI ETSI ES 202 196-12 V1.2.1 (2005-02) 13: IpAppChargingSession: IpAppChargingManager: IpChargingManager: IpChargingSes sionPreamble: createChargingSession(appChargingSession, sessionDescription, merchantAccount, user, correlationID)chargingSessionID1. reserveAmountR

47、eq(sess ionID, applic ationDescription, chargingParameters, preferredAmount , minimumAmount, requestNumber)2. reserveAmountRes(sessionID, requestNumber, reservedAmount, sessionTimeLeft, requestNumberNextRequest)minimumAmount reservedAmount preferredAmount3. creditAmountReq(sessionID, applicationDesc

48、ription, amount, closeReservation, requestNumber)4. creditAmountRes(sessionID, requestNumber, creditedAmount, reservedAmountLeft, requestNumberNextRequest)creditedAmount as requested, reservedAmountLeft correctly calculated5. debitAmountReq(sessionID, applicationDescription, amount, closeReservation

49、, 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 196-12 V1.2.1 (2005-02) 14Test CH_CS_04 Summary: IpChargingSession, amount reservation and variation of life time, successful Reference: ES 201 915-12 1, clause 8.3 Precondition: reserveAmountReq, extendLifeTimeReq, getLifeTimeLeft supported Pream