SIST ES 202 391-6 V1.3.1:2008

SLOVENSKI STANDARD
SIST ES 202 391-6 V1.3.1:2008
01-september-2008

2GSUWLGRVWRSGRVWRULWYH26$6SOHWQHVWRULWYH3DUOD\;GHO3ODþLOR3DUOD\

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

The present 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 printers of the PDF version kept on a specific network drive

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

If you find errors in the present document, please send your comment to one of the following services:

DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered

3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.

Intellectual Property Rights................................................................................................................................5

Foreword.............................................................................................................................................................5

1 Scope........................................................................................................................................................6

2 References................................................................................................................................................6

2.1 Normative references.........................................................................................................................................6

3 Definitions and abbreviations...................................................................................................................7

3.1 Definitions..........................................................................................................................................................7

3.2 Abbreviations.....................................................................................................................................................7

4 Detailed service description .....................................................................................................................7

5 Namespaces..............................................................................................................................................7

6 Sequence diagrams...................................................................................................................................8

6.1 Charge for content..............................................................................................................................................8

7 XML Schema data type definition ...........................................................................................................9

7.1 Property structure...............................................................................................................................................9

8 Web Service interface definition..............................................................................................................9

8.1 Interface: AmountCharging................................................................................................................................9

8.1.1 Operation: chargeAmount.............................................................................................................................9

8.1.1.1 Input message: chargeAmountRequest...................................................................................................9

8.1.1.2 Output message: chargeAmountResponse..............................................................................................9

8.1.1.3 Referenced faults.....................................................................................................................................9

8.1.2 Operation: refundAmount...........................................................................................................................10

8.1.2.1 Input message: refundAmountRequest.................................................................................................10

8.1.2.2 Output message: refundAmountResponse............................................................................................10

8.1.2.3 Referenced faults...................................................................................................................................10

8.2 Interface: VolumeCharging..............................................................................................................................10

8.2.1 Operation: chargeVolume...........................................................................................................................11

8.2.1.1 Input message: chargeVolumeRequest.................................................................................................11

8.2.1.2 Output message: chargeVolumeResponse............................................................................................11

8.2.1.3 Referenced faults...................................................................................................................................11

8.2.2 Operation: getAmount................................................................................................................................11

8.2.2.1 Input message: getAmountRequest.......................................................................................................12

8.2.2.2 Output message: getAmountResponse..................................................................................................12

8.2.2.3 Referenced faults...................................................................................................................................12

8.2.3 Operation: refundVolume...........................................................................................................................12

8.2.3.1 Input message: refundVolumeRequest..................................................................................................12

8.2.3.2 Output message: refundVolumeResponse.............................................................................................12

8.2.3.3 Referenced faults...................................................................................................................................12

8.3 Interface: ReserveAmountCharging.................................................................................................................13

8.3.1 Operation: reserveAmount..........................................................................................................................13

8.3.1.1 Input message: reserveAmountRequest................................................................................................13

8.3.1.2 Output message: reserveAmountResponse...........................................................................................13

8.3.1.3 Referenced faults...................................................................................................................................13

8.3.2 Operation: reserveAdditionalAmount.........................................................................................................14

8.3.2.1 Input message: reserveAdditionalAmountRequest ...............................................................................14

8.3.2.2 Output message : reserveAdditionalAmountResponse .........................................................................14

8.3.2.3 Referenced faults...................................................................................................................................14

8.3.3 Operation: chargeReservation.....................................................................................................................15

8.3.3.1 Input message: chargeReservationRequest...........................................................................................15

8.3.3.2 Output message: chargeReservationResponse ......................................................................................15

8.3.3.3 Referenced faults...................................................................................................................................15

8.3.4 Operation: releaseReservation....................................................................................................................15

8.3.4.1 Input message: releaseReservationRequest...........................................................................................15

8.3.4.2 Output message: releaseReservationResponse......................................................................................16

8.3.4.3 Referenced faults...................................................................................................................................16

8.4 Interface: ReserveVolumeCharging.................................................................................................................16

8.4.1 Operation: getAmount................................................................................................................................16

8.4.1.1 Input message: getAmountRequest.......................................................................................................16

8.4.1.2 Output message : getAmountResponse.................................................................................................16

8.4.1.3 Referenced faults...................................................................................................................................16

8.4.2 Operation: reserveVolume..........................................................................................................................17

8.4.2.1 Input message: reserveVolumeRequest.................................................................................................17

8.4.2.2 Output message: reserveVolumeResponse...........................................................................................17

8.4.2.3 Referenced faults...................................................................................................................................17

8.4.3 Operation: reserveAdditionalVolume.........................................................................................................17

8.4.3.1 Input message: reserveAdditionalVolumeRequest................................................................................18

8.4.3.2 Output message: reserveAdditionalVolumeResponse ..........................................................................18

8.4.3.3 Referenced faults...................................................................................................................................18

8.4.4 Operation: chargeReservation.....................................................................................................................18

8.4.4.1 Input message: chargeReservationRequest...........................................................................................18

8.4.4.2 Output message: chargeReservationResponse ......................................................................................18

8.4.4.3 Referenced faults...................................................................................................................................19

8.4.5 Operation: releaseReservation....................................................................................................................19

8.4.5.1 Input message: releaseReservationRequest...........................................................................................19

8.4.5.2 Output message: releaseReservationResponse......................................................................................19

8.4.5.3 Referenced faults...................................................................................................................................19

9 Fault definitions......................................................................................................................................19

9.1 ServiceException..............................................................................................................................................19

9.1.1 SVC0270: Charge failed.............................................................................................................................19

10 Service policies ......................................................................................................................................20

Annex A (normative): WSDL for Payment .......................................................................................21

Annex B (informative): Bibliography...................................................................................................22

History ..............................................................................................................................................................23

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); 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

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, 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

This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet

The present document is part 6 of a multi-part deliverable covering Open Service Access (OSA); Parlay X

The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org), PayCircle

The present document is part 6 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).

The OSA specifications define an architecture that enables application developers to make use of network functionality

The present document specifies the Payment Web Service. The following are defined here:

References are either specific (identified by date of publication and/or edition number or version number) or

• Non-specific reference may be made only to a complete document or a part thereof and only in the following

- if it is accepted that it will be possible to use all future changes of the referenced document for the

Referenced documents which are not found to be publicly available in the expected location might be found at

For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,

the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the

reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the

method of access to the referenced document and the full network address, with the same punctuation and use of upper

NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee

The following referenced documents are indispensable for the application of the present document. For dated

references, only the edition cited applies. For non-specific references, the latest edition of the referenced document

[2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common

For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] apply.

For the purposes of the present document, the abbreviations given in ES 202 391-1 [2] apply.

A vast amount of content, both information and entertainment, will be made available to subscribers. To support a

business model that enables operators to offer integrated billing, a payment API is crucial. Open and inter-operable

"payment APIs" are the key to market growth and investment protection. The Payment Web Service supports payments

The Payment Web Service described in the present document supports payment reservation, pre-paid payments, and

post-paid payments. It supports charging of both volume and currency amounts, a conversion function and a settlement

Note that certain parameters are negotiated off line. For example the currency, volume type, default reservation

An example of an application scenario could be a multimedia service. Assume a subscriber is interested in receiving a

stream of, say, a soccer match. The subscriber selects a match and establishes a trusted relation with the provider.

Again, the provider obtains the MSISDN and other information from the subscriber. The subscriber wants to know what

the service will cost and the provider interacts with the operators rating engine (getAmount) taking into account the

subscriber's subscription, time of day, etc. The value returned is a ChargingInformation amount and is printed on the

page that is displayed at the MS. The subscriber then decides to stream the match to his MS. Subsequently, the provider

will reserve the appropriate amount with the operator (reserveAmount) to ensure that the subscriber can fulfil his

payment obligations. The match starts and the provider periodically charges against the reservation

(chargeReservation). The match ends in a draw and is extended with a "sudden death" phase. The subscriber continues

listening, so the existing reservation is enlarged (reserveAdditionalAmount). Suddenly, one of the teams scores a goal,

so the match abruptly ends, leaving part of the reserved amount unused. The provider now releases the reservation

(releaseReservation), and the remaining amount is available for future use by the subscriber.

Now we can extend this scenario by having the subscriber participate in a game of chance in which the provider refunds

a percentage of the usage costs (refundAmount) based on the ranking of a particular team in this tournament. For

example, the subscriber gambling on the team that wins the tournament receives a full refund, while for gambling on the

The "xsd" namespace is used in the present document to refer to the XML Schema data types defined in XML

Assume a subscriber is interested in downloading a ring tone to his device. The subscriber selects a ring tone and

establishes a trusted relation with the ring tone provider. Essentially, the ring tone provider obtains the address

(MSISDN) and other information from the subscriber. The ring tone may be downloaded to the device using SMS. As

soon as the download succeeds, the provider of the ring tone will charge the subscriber (chargeAmount).

This operation results in directly charging to the account indicated by the end user identifier. The charge is specified as

a ChargingInformation data structure, consisting of information on the amount to be charged and a description to

appear on the bill. The reference code is used to uniquely identify the request; it is the application's responsibility to

referenceCode xsd:string No Textual information to uniquely identify the request, e.g. in

This operation results in directly applying a refund to the account indicated by the end user identifier. The refund is

specified as a currency amount. The billing text field is used for textual information to appear on the bill. The reference

code is used to uniquely identify the request; it is the application's responsibility to provide a unique reference code

referenceCode xsd:string No Textual information to uniquely identify the request, e.g. in

This operation results in directly charging to the account indicated by the end user identifier. The charge is specified as

a volume. The billing text field is used for textual information to appear on the bill. The reference code is used to

uniquely identify the request; it is the application's responsibility to provide a unique reference code within the scope of