ETSI TS 129 199-6-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Parlay X web services P_1.pdf

《ETSI TS 129 199-6-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Parlay X web services P_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 129 199-6-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Parlay X web services P_1.pdf（34页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 129 199-6 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA);Parlay X web services;Part 6: Payment (3GPP TS 29.199-06 version 9.0.0 Release 9)floppy3ETSI ETSI TS 129 19

2、9-6 V9.0.0 (2010-01)13GPP TS 29.199-06 version 9.0.0 Release 9Reference RTS/TSGC-0029199-06v900 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 623 562 00017 - NAF 742 C Association but non lucrati

3、f 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 print. In any case of existing or perceived difference in

4、 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. Users of the present document should be aware that the d

5、ocument 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 comment to one of the following services: http:/portal.et

6、si.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 Institute 2010. All rights reserved. DECTTM, PLUGTESTST

7、M, 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 Trade Mark of ETSI currently being registered for the b

8、enefit 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 199-6 V9.0.0 (2010-01)23GPP TS 29.199-06 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentially essential to th

9、e 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

10、 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 guarantee can be given a

11、s 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 ETSI 3rd Generation Partnership Project (3GPP). The prese

12、nt 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, UMTS, 3GPP and ETSI identities can be found under http

13、:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 199-6 V9.0.0 (2010-01)33GPP TS 29.199-06 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 6g3Introduction 6g31 Scope 7g32 References 7g33 Definitions and abbreviations Services 7g33.1 Definitions 7g33.2 Abb

14、reviations . 8g34 Detailed service description . 8g35 Namespaces 9g36 Sequence diagrams . 10g36.1 Charge for content 10g37 XML Schema data type definition . 11g37.1 Void 11g37.2 SplitType structure . 11g38 Web Service interface definition 12g38.1 Interface: AmountCharging 12g38.1.1 Operation: Charge

15、Amount 12g38.1.1.1 Input message: ChargeAmountRequest 12g38.1.1.2 Output message: ChargeAmountResponse . 12g38.1.1.3 Referenced faults . 12g38.1.2 Operation: RefundAmount . 13g38.1.2.1 Input message: RefundAmountRequest 13g38.1.2.2 Output message: RefundAmountResponse . 13g38.1.2.3 Referenced faults

16、 . 13g38.1.3 Operation: ChargeSplitAmount 14g38.1.3.1 Input message: ChargeSplitAmountRequest . 14g38.1.3.2 Output message: ChargeSplitAmountResponse 14g38.1.3.3 Referenced faults. 14g38.2 Interface: VolumeCharging 15g38.2.1 Operation: ChargeVolume 15g38.2.1.1 Input message: ChargeVolumeRequest . 15

17、g38.2.1.2 Output message: ChargeVolumeResponse . 15g38.2.1.3 Referenced faults . 15g38.2.2 Operation: GetAmount . 16g38.2.2.1 Input message: GetAmountRequest 16g38.2.2.2 Output message: GetAmountResponse . 16g38.2.2.3 Referenced faults . 16g38.2.3 Operation: RefundVolume 17g38.2.3.1 Input message: R

18、efundVolumeRequest 17g38.2.3.2 Output message: RefundVolumeResponse . 17g38.2.3.3 Referenced faults . 17g38.2.4 Operation: ChargeSplitVolume 18g38.2.4.1 Input message: ChargeSplitVolumeRequest . 18g38.2.4.2 Output message: ChargeSplitVolumeResponse 18g38.2.4.3 Referenced faults . 18g38.3 Interface:

19、ReserveAmountCharging . 19g38.3.1 Operation: ReserveAmount 19g38.3.1.1 Input message: ReserveAmountRequest . 19g3ETSI ETSI TS 129 199-6 V9.0.0 (2010-01)43GPP TS 29.199-06 version 9.0.0 Release 98.3.1.2 Output message: ReserveAmountResponse 19g38.3.1.3 Referenced faults . 19g38.3.2 Operation: Reserve

20、AdditionalAmount . 20g38.3.2.1 Input message: ReserveAdditionalAmountRequest 20g38.3.2.2 Output message : ReserveAdditionalAmountResponse 20g38.3.2.3 Referenced faults . 20g38.3.3 Operation: ChargeReservation 21g38.3.3.1 Input message: ChargeReservationRequest 21g38.3.3.2 Output message: ChargeReser

21、vationResponse . 21g38.3.3.3 Referenced faults. 21g38.3.4 Operation: ReleaseReservation . 22g38.3.4.1 Input message: ReleaseReservationRequest . 22g38.3.4.2 Output message: ReleaseReservationResponse 22g38.3.4.3 Referenced faults. 22g38.4 Interface: ReserveVolumeCharging . 23g38.4.1 Operation: GetAm

22、ount . 23g38.4.1.1 Input message: GetAmountRequest 23g38.4.1.2 Output message : GetAmountResponse 23g38.4.1.3 Referenced faults . 23g38.4.2 Operation: ReserveVolume . 24g38.4.2.1 Input message: ReserveVolumeRequest . 24g38.4.2.2 Output message: ReserveVolumeResponse 24g38.4.2.3 Referenced faults . 2

23、4g38.4.3 Operation: ReserveAdditionalVolume 25g38.4.3.1 Input message: ReserveAdditionalVolumeRequest 25g38.4.3.2 Output message: ReserveAdditionalVolumeResponse . 25g38.4.3.3 Referenced faults. 25g38.4.4 Operation: ChargeReservation 26g38.4.4.1 Input message: ChargeReservationRequest 26g38.4.4.2 Ou

24、tput message: ChargeReservationResponse . 26g38.4.4.3 Referenced faults. 26g38.4.5 Operation: ReleaseReservation . 27g38.4.5.1 Input message: ReleaseReservationRequest . 27g38.4.5.2 Output message: ReleaseReservationResponse 27g38.4.5.3 Referenced faults. 27g39 Fault definitions 28g39.1 ServiceExcep

25、tion 28g39.1.1 SVC0270: Charge failed . 28g39.1.2 SVC0271: Invalid sum of percentage allocations . 28g39.2 PolicyException . 28g39.2.1 POL0250: Too many endUserIdentifiers 28g39.2.2 POL0251: Split charging not supported 28g310 Service policies 28g3Annex A (normative): WSDL for Payment . 29g3Annex B

26、(informative): Description of Parlay X Web Services Part 6: Payment for 3GPP2 cdma2000 networks . 30g3B.1 General Exceptions. 30g3B.2 Specific Exceptions 30g3B.2.1 Clause 1: Scope 30g3B.2.2 Clause 2: References 30g3B.2.3 Clause 3: Definitions and abbreviations . 30g3B.2.4 Clause 4: Detailed service

27、description 30g3B.2.5 Clause 5: Namespaces 30g3B.2.6 Clause 6: Sequence diagrams . 31g3B.2.7 Clause 7: XML Schema data type definition 31g3B.2.8 Clause 8: Web Service interface definition 31g3B.2.9 Clause 9: Fault definitions 31g3ETSI ETSI TS 129 199-6 V9.0.0 (2010-01)53GPP TS 29.199-06 version 9.0.

28、0 Release 9B.2.10 Clause 10: Service policies . 31g3B.2.11 Annex A (normative):WSDL for Payment . 31g3Annex C (informative): Change history . 32g3History 33g3ETSI ETSI TS 129 199-6 V9.0.0 (2010-01)63GPP TS 29.199-06 version 9.0.0 Release 9Foreword This Technical Specification has been produced by th

29、e 3rdGeneration Partnership Project (3GPP). 3GPP acknowledges the contribution of the Parlay X Web Services specifications from The Parlay Group. The Parlay Group is pleased to see 3GPP acknowledge and publish the present document, and the Parlay Group looks forward to working with the 3GPP communit

30、y to improve future versions of the present document. The contents of the present 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 cha

31、nge of release date and an increase in version number as follows: Version x.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 subst

32、ance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 6 of a multi-part deliverable covering the 3rdGeneration Partnership Project; Technical Specifi

33、cation Group Core Network and Terminals; Open Service Access (OSA); Parlay X Web Services, as identified below: Part 1: “Common“ Part 2: “Third party call“ Part 3: “Call Notification“ Part 4: “Short Messaging“ Part 5: “Multimedia Messaging“ Part 6: “Payment“ Part 7: “Account management“ Part 8: “Ter

34、minal Status“ Part 9: “Terminal location“ Part 10: “Call handling“ Part 11: “Audio call“ Part 12: “Multimedia conference“ Part 13: “Address list management“ Part 14: “Presence“ Part 15: “Message Broadcast“ Part 16: “Geocoding“ Part 17: “Application driven Quality of Service (QoS)“ Part 18: “Device C

35、apabilities and Configuration“ Part 19: “Multimedia streaming control“ Part 20: “Multimedia multicast session management“ Part 21: “Content management“ Part 22: “Policy“ ETSI ETSI TS 129 199-6 V9.0.0 (2010-01)73GPP TS 29.199-06 version 9.0.0 Release 91 Scope The present document is Part 6 of the Sta

36、ge 3 Parlay X Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for t

37、he OSA are contained in 3GPP TS 23.198 3. The requirements for OSA are contained in 3GPP TS 22.127 2. The present document specifies the Payment Web Service aspects of the interface. All aspects of the Payment Web Service are defined here, these being: Name spaces. Sequence diagrams. Data definition

38、s. Interface specification plus detailed method descriptions. Fault definitions. Service policies. WSDL Description of the interfaces. The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3

39、 work beyond Rel-9 was moved to OMA in June 2008. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or

40、non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same

41、 Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.127: “Service Requirement for the Open Services Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TS 22.101: “Service aspects; Service principles“. 5 W3C Recomm

42、endation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 6 3GPP TS 29.199-1: “Open Service Access (OSA); Parlay X Web; Part 1: Common“. 3 Definitions and abbreviations Services 3.1 Definitions For the purposes of the present docume

43、nt, the terms and definitions given in 3GPP TS 29.199-1 6 apply. ETSI ETSI TS 129 199-6 V9.0.0 (2010-01)83GPP TS 29.199-06 version 9.0.0 Release 93.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 6 apply. 4 Detailed service description A vast amo

44、unt 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 Paym

45、ent Web Service supports payments for any content in an open, Web-like environment. 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

46、 settlement function in case of a financially resolved dispute. Note that certain parameters are negotiated as part of a service level agreement. For example the taxation procedures and parameters. An example of an application scenario could be a multimedia service. Assume a subscriber is interested

47、 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 wi

48、th the operators rating engine (getAmount) taking into account the subscribers 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 provi

49、der 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