1、 ETSI TR 102 397-6 V1.1.1 (2005-08)Technical Report Open Service Access (OSA);Mapping of Parlay X Web Services to Parlay/OSA APIs;Part 6: Payment MappingETSI ETSI TR 102 397-6 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-06-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia A
2、ntipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 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 pr
3、esent document may be made available in more than one electronic version or in print. 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 printe
4、rs of the PDF version kept on a specific network drive within ETSI Secretariat. Users 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/
5、status/status.asp If you find errors in the present document, please send your comment 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 restri
6、ction extend to reproduction in all media. European Telecommunications Standards Institute 2005. The Parlay Group 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being r
7、egistered by ETSI 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. ETSI ETSI TR 102 397-6 V1.1.1 (2005-08) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 3 Definitions and a
8、bbreviations.6 3.1 Definitions6 3.2 Abbreviations .6 4 Mapping description.6 5 Sequence diagrams.7 5.1 Direct charging.7 5.2 Reservation-based charging8 5.3 Conversion of volume to currency amount 9 6 Detailed mapping information9 6.1 Operations 9 6.1.1 chargeAmount.9 6.1.1.1 Mapping to IpChargingMa
9、nager.createChargingSession10 6.1.1.2 Mapping to IpChargingSession.directDebitAmountReq.10 6.1.1.3 Mapping from IpAppChargingSession.directDebitAmountRes.10 6.1.1.4 Mapping from IpAppChargingSession.directDebitAmountErr.10 6.1.1.5 Mapping from IpAppChargingSession.sessionEnded10 6.1.1.6 Mapping from
10、 IpAppChargingManager.sessionAborted.11 6.1.2 refundAmount.11 6.1.2.1 Mapping to IpChargingManager.createChargingSession11 6.1.2.2 Mapping to IpChargingSession.directCreditAmountReq12 6.1.2.3 Mapping from IpAppChargingSession.directCreditAmountRes 12 6.1.2.4 Mapping from IpAppChargingSession.directC
11、reditAmountErr 12 6.1.2.5 Mapping from IpAppChargingSession.sessionEnded12 6.1.2.6 Mapping from IpAppChargingManager.sessionAborted.12 6.1.3 chargeVolume.12 6.1.3.1 Mapping to IpChargingManager.createChargingSession13 6.1.3.2 Mapping to IpChargingSession.directDebitUnitReq .13 6.1.3.3 Mapping from I
12、pAppChargingSession.directDebitUnitRes13 6.1.3.4 Mapping from IpAppChargingSession.directDebitUnitErr13 6.1.3.5 Mapping from IpAppChargingSession.sessionEnded13 6.1.3.6 Mapping from IpAppChargingManager.sessionAborted.14 6.1.4 refundVolume .14 6.1.4.1 Mapping to IpChargingManager.createChargingSessi
13、on14 6.1.4.2 Mapping to IpChargingSession.directCreditUnitReq.15 6.1.4.3 Mapping from IpAppChargingSession.directCreditUnitRes.15 6.1.4.4 Mapping from IpAppChargingSession.directCreditUnitErr.15 6.1.4.5 Mapping from IpAppChargingSession.sessionEnded15 6.1.4.6 Mapping from IpAppChargingManager.sessio
14、nAborted.15 6.1.5 getAmount 15 6.1.5.1 Mapping to IpChargingManager.createChargingSession16 6.1.5.2 Mapping to IpChargingSession.rateReq16 6.1.5.3 Mapping from IpAppChargingSession.rateRes16 6.1.5.4 Mapping from IpAppChargingSession.rateErr16 6.1.5.5 Mapping from IpAppChargingSession.sessionEnded16
15、6.1.5.6 Mapping from IpAppChargingManager.sessionAborted.17 6.1.6 reserveAmount17 6.1.6.1 Mapping to IpChargingManager.createChargingSession17 6.1.6.2 Mapping to IpChargingSession.reserveAmountReq18 6.1.6.3 Mapping from IpAppChargingSession.reserveAmountRes18 ETSI ETSI TR 102 397-6 V1.1.1 (2005-08)
16、4 6.1.6.4 Mapping from IpAppChargingSession.reserveAmountErr18 6.1.6.5 Mapping from IpAppChargingSession.sessionEnded18 6.1.6.6 Mapping from IpAppChargingManager.sessionAborted.18 6.1.7 reserveAdditionalAmount.18 6.1.7.1 Mapping to IpChargingSession.reserveAmountReq19 6.1.7.2 Mapping from IpAppCharg
17、ingSession.reserveAmountRes19 6.1.7.3 Mapping from IpAppChargingSession.reserveAmountErr19 6.1.7.4 Mapping from IpAppChargingSession.sessionEnded19 6.1.7.5 Mapping from IpAppChargingManager.sessionAborted.19 6.1.8 chargeReservation (Amount)19 6.1.8.1 Mapping to IpChargingSession.debitAmountReq.20 6.
18、1.8.2 Mapping from IpAppChargingSession.debitAmountRes.20 6.1.8.3 Mapping from IpAppChargingSession.debitAmountErr.20 6.1.8.4 Mapping from IpAppChargingSession.sessionEnded20 6.1.8.5 Mapping from IpAppChargingManager.sessionAborted.20 6.1.9 releaseReservation 20 6.1.9.1 Mapping to IpChargingSession.
19、release20 6.1.10 reserveVolume21 6.1.10.1 Mapping to IpChargingManager.createChargingSession21 6.1.10.2 Mapping to IpChargingSession.reserveUnitReq.21 6.1.10.3 Mapping from IpAppChargingSession.reserveUnitRes.22 6.1.10.4 Mapping from IpAppChargingSession.reserveUnitErr.22 6.1.10.5 Mapping from IpApp
20、ChargingSession.sessionEnded22 6.1.10.6 Mapping from IpAppChargingManager.sessionAborted.22 6.1.11 reserveAdditionalVolume.22 6.1.11.1 Mapping to IpChargingSession.reserveUnitReq.22 6.1.11.2 Mapping from IpAppChargingSession.reserveUnitRes.23 6.1.11.3 Mapping from IpAppChargingSession.reserveUnitErr
21、.23 6.1.11.4 Mapping from IpAppChargingSession.sessionEnded23 6.1.11.5 Mapping from IpAppChargingManager.sessionAborted.23 6.1.12 chargeReservation (Volume) 23 6.1.12.1 Mapping to IpChargingSession.debitUnitReq23 6.1.12.2 Mapping from IpAppChargingSession.debitUnitRes23 6.1.12.3 Mapping from IpAppCh
22、argingSession.debitUnitErr24 6.1.12.4 Mapping from IpAppChargingSession.sessionEnded24 6.1.12.5 Mapping from IpAppChargingManager.sessionAborted.24 6.2 Exceptions 24 7 Additional notes .24 History 25 ETSI ETSI TR 102 397-6 V1.1.1 (2005-08) 5 Intellectual Property Rights IPRs essential or potentially
23、 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); Essential, or potentially Essential, IPRs
24、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 carried out by ETSI. No guarante
25、e 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 Report (TR) has been produced by ETSI Technical Committee Telecommunications and
26、Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 6 of a multi-part deliverable covering Open Service Access (OSA); Mapping of Parlay X Web Services to Parlay/OSA APIs, as identified below: Part 1: “Common Mapping“; Part 2: “Third Party Call Map
27、ping“; Part 3: “Call Notification Mapping“; Part 4: “Short Messaging Mapping“; Part 5: “Multimedia Messaging Mapping“; Part 6: “Payment Mapping“; Part 7: “Account Management Mapping“; Part 8: “Terminal Status Mapping“; Part 9: “Terminal Location Mapping“; Part 10: “Call Handling Mapping“; Part 11: “
28、Audio Call Mapping“; Part 12: “Multimedia Conference Mapping“; Part 14: “Presence Mapping“. NOTE: Part 13 has not been provided as there is currently no defined mapping between ES 202 391-13 4 and the Parlay/OSA APIs. If a mapping is developed, it will become part 13 of this series. The present docu
29、ment has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR 102 397-6 V1.1.1 (2005-08) 6 1 Scope The present document specifies the mapping of the Parlay X Payment Web Service to the Charging Service Capability Feature (SCF). The Parlay X Web Servic
30、es provide powerful yet simple, highly abstracted, imaginative, telecommunications functions that application developers and the IT community can both quickly comprehend and use to generate new, innovative applications. The Open Service Access (OSA) specifications define an architecture that enables
31、 application developers to make use of network functionality through an open standardized interface, i.e. the Parlay/OSA APIs. 2 References For the purposes of this Technical Report (TR), the following references apply: 1 ETSI TR 121 905: “Universal Mobile Telecommunications System (UMTS); Vocabular
32、y for 3GPP Specifications (3GPP TR 21.905)“. 2 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 3 ETSI TR 102 397-1: “ Open Service Access (OSA); Mapping of Parlay X Web Services to Parlay/OSA APIs; Part 1: Common
33、 Mapping“. 4 ETSI ES 202 391-13: “Open Service Access (OSA); Parlay X Web Services; Part 13: Address List Management“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 102 397-1 3 apply. 3.2 Abbreviations For the purposes
34、 of the present document, the abbreviations given in TR 102 397-1 3 apply. 4 Mapping description The Payment capability can be implemented with Parlay/OSA Charging. It is applicable to ETSI OSA 1.x/2.x/3.x, Parlay/OSA 3.x/4.x/5.x and 3GPP Releases 4 to 6. ETSI ETSI TR 102 397-6 V1.1.1 (2005-08) 7 5
35、Sequence diagrams 5.1 Direct charging This use case shows an application debiting a specific amount from a customer account. The use cases are similar for all direct debits and credits however a different Payment Web Service operation is used for each. In the diagram below VolumeCharging could repla
36、ce AmountCharging and refundAmount/Volume operations could replace chargeAmount/Volume operations. Application “forward event“ “new“ createChargingSession() directDebitAmountReq() directDebitAmountRes() release() chargeAmountResponsePayment: AmountCharging Interface IpApp Charging Session IpCharging
37、 Manager IpCharging Session chargeAmountRequest Figure 1 ETSI ETSI TR 102 397-6 V1.1.1 (2005-08) 8 5.2 Reservation-based charging This use case shows an application reserving a specific amount of credit in a customer account. The credit is increased and then deducted (charged against) at a later poi
38、nt. The use case is similar for a volume credit reservation and subsequent deduction although a different Payment Web Service interface (ReserveVolumeCharging) would be used instead. reserveAmountRequestreserveAmountResponse“forward event“ reserveAmountRes()reserveAmountRes()debitAmountRes()“forward
39、 event“ reserveAmountReq() reserveAdditionalAmountRequest createChargingSession()“forward event“chargeReservationRequestchargeReservationResponse release() “new“ reserveAmountReq() reserveAdditionalAmountResponse debitAmountReq() releaseReservationRequestreleaseReservationResponseApplicationIpApp Ch
40、arging Session IpCharging Manager IpCharging Session Payment: ReserveAmount Charging Interface Figure 2 ETSI ETSI TR 102 397-6 V1.1.1 (2005-08) 9 5.3 Conversion of volume to currency amount This use case shows an application requesting the conversion of a specified volume to a currency amount. This
41、use case also applies when the getAmount operation is invoked on the ReserveVolumeCharging interface. Application Payment: VolumeCharging Interface IpApp Charging Session IpCharging Session getAmountRequest“forward event“IpCharging Manager “new“createChargingSession()rateReq() rateRes()release() get
42、AmountResponse Figure 3 6 Detailed mapping information 6.1 Operations 6.1.1 chargeAmount The sequence diagram in clause 5.1 illustrates the flow for the chargeAmount operation. It is mapped to the following Parlay/OSA methods: IpChargingManager.createChargingSession; IpChargingSession.directDebitAmo
43、untReq; IpAppChargingSession.directDebitAmountRes; IpAppChargingSession.directDebitAmountErr; IpAppChargingSession.sessionEnded; IpAppChargingManager.sessionAborted. ETSI ETSI TR 102 397-6 V1.1.1 (2005-08) 10 6.1.1.1 Mapping to IpChargingManager.createChargingSession The IpChargingManager.createChar
44、gingSession method is invoked with the following parameters. Name Type Comment appCharging Session IpAppCharging SessionRef Reference to callback (internal). sessionDescription TpString Not mapped Descriptive text for informational purposes. merchantAccount TpMerchant AccountID Not mapped Identifies
45、 the account of the party providing the application to be used. user TpAddress Specifies the address associated with the account to be charged. It is constructed based on the URI provided in the endUserIdentifier part of chargeAmountRequest message, mapped as described in TR 102 397-1 3. correlation
46、ID TpCorrelationID Not mapped Used to correlate the charging with network activity. The result from IpChargingManager.createChargingSession is of type TpChargingSessionID and is used internally to correlate the callbacks. Parlay exceptions thrown by IpChargingManager.createChargingSession are mapped
47、 to Parlay X exceptions as defined in clause 6.2. 6.1.1.2 Mapping to IpChargingSession.directDebitAmountReq The IpChargingSession.directDebitAmountReq method is invoked with the following parameters. Name Type Comment sessionID TpSessionID Not mapped. The value returned in the result from IpCharging
48、Manager.createChargingSession. application Description TpApplication Description The Text element of this parameter matches the value of the billingText part. Optionally this may be concatenated with the text string value of the referenceCode part. charging Parameters TpCharging ParameterSet Not map
49、ped. amount TpChargingPrice The Amount element of this parameter matches the value of the amount part. The Currency element of this parameter matches the value defined in the Currency service policy. requestNumber TpInt32 Not mapped. The value returned in the result from IpChargingManager.createChargingSession. Parlay exceptions thrown by IpChargingSession.directDebitAmountReq are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.3 Mapping from IpAppChargingSession.directDebitAmountRes The invocation of the IpAppChargingSessi
