ETSI TS 129 198-12-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmin.pdf

1、 ETSI TS 129 198-12 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA)Application Programming Interface (API);Part 12: Charging Service Capability Feature (SCF) (3GPP TS 29.198-

2、12 version 9.0.0 Release 9)floppy3ETSI ETSI TS 129 198-12 V9.0.0 (2010-01)13GPP TS 29.198-12 version 9.0.0 Release 9Reference RTS/TSGC-0029198-12v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348

3、 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in pri

4、nt. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Us

5、ers of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your com

6、ment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards I

7、nstitute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a T

8、rade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 198-12 V9.0.0 (2010-01)23GPP TS 29.198-12 version 9.0.0 Release 9Intellectual Proper

9、ty Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Ess

10、ential, 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, ha

11、s 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 Technical Specification (TS) has been produced by ET

12、SI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM,

13、 UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 198-12 V9.0.0 (2010-01)33GPP TS 29.198-12 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 6g3Introduction 6g31 Scope 8g32 References 8g33 Definitions

14、and abbreviations . 9g33.1 Definitions 9g33.2 Abbreviations . 9g34 Charging SCF . 9g34.1 General requirements on support of methods . 9g35 Sequence Diagrams 9g35.1 Reservation / payment in parts . 9g35.2 Immediate Charge 11g36 Class Diagrams . 13g37 The Service Interface Specifications 14g37.1 Inter

15、face Specification Format . 14g37.1.1 Interface Class 15g37.1.2 Method descriptions 15g37.1.3 Parameter descriptions 15g37.1.4 State Model . 15g37.2 Base Interface . 15g37.2.1 Interface Class IpInterface 15g37.3 Service Interfaces . 15g37.3.1 Overview 15g37.4 Generic Service Interface . 16g37.4.1 In

16、terface Class IpService 16g37.4.1.1 Method setCallback() 16g37.4.1.2 Method setCallbackWithSessionID() 16g38 Charging Interface Classes . 17g38.1 Interface Class IpChargingManager . 17g38.1.1 Method createChargingSession() 18g38.1.2 Method createSplitChargingSession() 18g38.2 Interface Class IpAppCh

17、argingManager 19g38.2.1 Method sessionAborted() 20g38.2.2 Method abortMultipleChargingSessions() 20g38.3 Interface Class IpChargingSession . 20g38.3.1 Method creditAmountReq() 21g38.3.2 Method creditUnitReq() 22g38.3.3 Method debitAmountReq() . 23g38.3.4 Method debitUnitReq() . 23g38.3.5 Method dire

18、ctCreditAmountReq() 24g38.3.6 Method directCreditUnitReq() 25g38.3.7 Method directDebitAmountReq() . 25g38.3.8 Method directDebitUnitReq() . 26g38.3.9 Method extendLifeTimeReq() 27g38.3.10 Method getAmountLeft() 27g38.3.11 Method getLifeTimeLeft() 27g38.3.12 Method getUnitLeft() 28g38.3.13 Method ra

19、teReq() 28g3ETSI ETSI TS 129 198-12 V9.0.0 (2010-01)43GPP TS 29.198-12 version 9.0.0 Release 98.3.14 Method release() . 28g38.3.15 Method reserveAmountReq() . 29g38.3.16 Method reserveUnitReq() . 29g38.4 Interface Class IpAppChargingSession 30g38.4.1 Method creditAmountErr() . 32g38.4.2 Method credi

20、tAmountRes() 32g38.4.3 Method creditUnitErr() . 32g38.4.4 Method creditUnitRes() 33g38.4.5 Method debitAmountErr() 33g38.4.6 Method debitAmountRes() . 34g38.4.7 Method debitUnitErr() 34g38.4.8 Method debitUnitRes() . 34g38.4.9 Method directCreditAmountErr() . 35g38.4.10 Method directCreditAmountRes(

21、) 35g38.4.11 Method directCreditUnitErr() . 36g38.4.12 Method directCreditUnitRes() 36g38.4.13 Method directDebitAmountErr() 36g38.4.14 Method directDebitAmountRes() . 37g38.4.15 Method directDebitUnitErr() 37g38.4.16 Method directDebitUnitRes() . 38g38.4.17 Method extendLifeTimeErr() 38g38.4.18 Met

22、hod extendLifeTimeRes() . 38g38.4.19 Method rateErr() . 38g38.4.20 Method rateRes() 39g38.4.21 Method reserveAmountErr() . 39g38.4.22 Method reserveAmountRes() 39g38.4.23 Method reserveUnitErr() . 40g38.4.24 Method reserveUnitRes() 40g38.4.25 Method sessionEnded() . 41g39 State Transition Diagrams 4

23、1g39.1 State Transition Diagrams for IpChargingSession . 41g39.1.1 Session Created State 43g39.1.2 Amount Reserved State 43g39.1.3 Volume Reserved State . 43g39.1.4 Reservation Ended State . 43g310 Content Based Charging Service Properties. 43g311 Data Definitions . 45g311.1 Charging Data Definition

24、s 45g311.1.1 IpChargingManager 45g311.1.2 IpChargingManagerRef 45g311.1.3 IpAppChargingManager . 45g311.1.4 IpAppChargingManagerRef . 45g311.1.5 IpChargingSession 45g311.1.6 IpChargingSessionRef 45g311.1.7 IpAppChargingSession . 45g311.1.8 IpAppChargingSessionRef . 45g311.1.9 TpApplicationDescriptio

25、n 45g311.1.10 TpAppInformationSet . 46g311.1.11 TpAppInformation 46g311.1.12 TpAppInformationType 46g311.1.13 TpSessionEndedCause 46g311.1.14 TpMerchantAccountID . 46g311.1.15 TpCorrelationID . 46g311.1.16 TpCorrelationType 47g311.1.17 TpChargingPrice . 47g311.1.18 TpAmount . 47g311.1.19 TpChargingP

26、arameterSet 47g311.1.20 TpChargingParameter . 47g311.1.21 TpChargingParameterID . 47g311.1.22 TpChargingParameterValue . 48g3ETSI ETSI TS 129 198-12 V9.0.0 (2010-01)53GPP TS 29.198-12 version 9.0.0 Release 911.1.23 TpChargingParameterValueType . 48g311.1.24 TpVolumeSet 48g311.1.25 TpVolume . 48g311.

27、1.26 TpUnitID 48g311.1.27 TpChargingSessionID . 49g311.1.28 TpPriceVolumeSet 49g311.1.29 TpPriceVolume . 49g311.1.30 TpChargingError . 49g312 Exception Classes . 49g3Annex A (normative): OMG IDL Description of Charging SCF . 51g3Annex B (informative): W3C WSDL Description of Charging SCF . 52g3Annex

28、 C (informative): Java API Description of the Charging SCF 53g3Annex D (informative): Description of Charging for 3GPP2 cdma2000 networks 54g3D.1 General Exceptions. 54g3D.2 Specific Exceptions 54g3D.2.1 Clause 1: Scope 54g3D.2.2 Clause 2: References 54g3D.2.3 Clause 3: Definitions and abbreviations

29、 . 54g3D.2.4 Clause 4: Charging SCF . 54g3D.2.5 Clause 5: Sequence Diagrams 54g3D.2.6 Clause 6: Class Diagrams . 54g3D.2.7 Clause 7: The Service Interface Specifications 55g3D.2.8 Clause 8: Charging Interface Classes . 55g3D.2.9 Clause 9: State Transition Diagrams 55g3D.2.10 Clause 10: Content Based

30、 Charging Service Properties . 55g3D.2.11 Clause 11: Data Definitions 55g3D.2.12 Clause 12: Exception Classes . 55g3D.2.13 Annex A (normative): OMG IDL Description of Charging SCF . 55g3D.2.14 Annex B (informative): W3C WSDL Description of Charging SCF . 55g3D.2.15 Annex C (informative): Java API De

31、scription of the Charging SCF . 55g3Annex E (informative): Change history . 56g3History 57g3ETSI ETSI TS 129 198-12 V9.0.0 (2010-01)63GPP TS 29.198-12 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the p

32、resent document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x

33、.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third d

34、igit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 12 of a multi-part TS covering the 3rdGeneration Partnership Project: Technical Specification Group Core Network; Open Service Access (OSA); Application Programming Inter

35、face (API), as identified below. The API specification (3GPP TS 29.198) is structured in the following Parts: Part 1: “Overview“; Part 2: “Common Data Definitions“; Part 3: “Framework“; Part 4: “Call Control“; Sub-part 1: “Call Control Common Definitions“; Sub-part 2: “Generic Call Control SCF“; Sub

36、-part 3: “Multi-Party Call Control SCF“; Sub-part 4: “Multi-Media Call Control SCF“; Sub-part 5: “Conference Call Control SCF“; Part 5: “User Interaction SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities SCF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SCF“; (not part

37、of 3GPP Release 8) Part 10: “Connectivity Manager SCF“; (new in 3GPP Release 8) Part 11: “Account Management SCF“; Part 12: “Charging SCF“. Part 13: “Policy Management SCF“; Part 14: “Presence and Availability Management SCF“; Part 15: “Multi Media Messaging SCF“; Part 16: “Service Broker SCF“. The

38、Mapping specification of the OSA APIs and network protocols (3GPP TR 29.998) is also structured as above. A mapping to network protocols is however not applicable for all Parts, but the numbering of Parts is kept. Also in case a Part is not supported in a Release, the numbering of the parts is maint

39、ained. ETSI ETSI TS 129 198-12 V9.0.0 (2010-01)73GPP TS 29.198-12 version 9.0.0 Release 9Table: Overview of the OSA APIs Application Programming Interface; Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for the Open Services Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (

40、OSA); Stage 2“. 4 World Wide Web Consortium Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation (www.w3.org). 5 Wireless Application Protocol (WAP), Version 1.2, UAProf Specification (www.wapforum.org). 6 ISO 4217: “Codes for the representation of currenci

41、es and funds“. ETSI ETSI TS 129 198-12 V9.0.0 (2010-01)93GPP TS 29.198-12 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 29.198-1 1 apply. 3.2 Abbreviations For the purposes of the present documen

42、t, the abbreviations given in TS 29.198-1 1 apply. 4 Charging SCF The following clauses describe each aspect of the Charging Service Capability Feature (SCF). The order is as follows: The Sequence diagrams give the reader a practical idea of how each of the SCF is implemented. The Class relationship

43、s clause shows how each of the interfaces applicable to the SCF, relate to one another The Interface specification clause describes in detail each of the interfaces shown within the Class diagram part. The State Transition Diagrams (STD) show the the transition between states in the SCF. The states

44、and transitions are well-defined; either methods specified in the Interface specification or events occurring in the underlying networks cause state transitions. The Data definitions clause shows a detailed expansion of each of the data types associated with the methods within the classes. Note that

45、 some data types are used in other methods and classes and are therefore defined within the Common Data types part of this specification. 4.1 General requirements on support of methods An implementation of this API which supports or implements a method described in the present document, shall suppor

46、t or implement the functionality described for that method, for at least one valid set of values for the parameters of that method. Where a method is not supported by an implementation of a Service interface, the exception P_METHOD_NOT_SUPPORTED shall be returned to any call of that method. Where a

47、method is not supported by an implementation of an Application interface, a call to that method shall be possible, and no exception shall be returned. 5 Sequence Diagrams 5.1 Reservation / payment in parts The sequence diagram illustrates how to request a reservation and how to charge a user from th

48、e reserved amount, for instance to charge a user for a streamed video which lasts 10 minutes and costs a total of $2.00. The operations and interfaces that do not provide rating are employed throughout this sequence diagram. We assume the application has already discovered the Charging SCF. As a res

49、ult, the application received an object reference pointing to an object that implements the IpChargingManager interface. The operations which handle units are used exactly the same, except that the amount of application usage is indicated instead of a price. ETSI ETSI TS 129 198-12 V9.0.0 (2010-01)103GPP TS 29.198-12 version 9.0.0 Release 9Application : IpChargingSession : IpChargingManager : IpAppChargingSession1: new()2: createChargingSes sion( )3: new()4: reserveAmountReq( )5: reserveAmountRes( )6: forward event()7: debitAmountReq( )8: de