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

1、 ETSI TS 129 199-7 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 7: Account management (3GPP TS 29.199-07 version 9.0.0 Release 9)floppy3ETSI ETS

2、I TS 129 199-7 V9.0.0 (2010-01)13GPP TS 29.199-07 version 9.0.0 Release 9Reference RTS/TSGC-0029199-07v900 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

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

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

5、 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 comment to one of the following services: http

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

7、 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 Trade Mark of ETSI currently being registere

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

9、ntial 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 notif

10、ied 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 guarantee can

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

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

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

14、 Abbreviations . 7g34 Detailed service description . 7g35 Namespaces 7g36 Sequence diagrams . 8g36.1 Prepaid account recharge using a voucher . 8g36.2 Prepaid account recharge using direct payment . 9g37 XML Schema data type definition . 10g37.1 DatedTransaction structure . 10g37.2 Balance structure

15、 10g37.3 BalanceExpireDetails structure 10g37.4 AccountChangedEvent enumeration 10g38 Web Service interface definition 11g38.1 Interface: AccountManagement . 11g38.1.1 Operation: GetBalance 11g38.1.1.1 Input message: GetBalanceRequest 11g38.1.1.2 Output message: GetBalanceResponse . 11g38.1.1.3 Refe

16、renced faults . 11g38.1.2 Operation: GetCreditExpiryDate 12g38.1.2.1 Input message: GetCreditExpiryDateRequest . 12g38.1.2.2 Output message: GetCreditExpiryDateResponse 12g38.1.2.3 Referenced faults . 12g38.1.3 Operation: BalanceUpdate 13g38.1.3.1 Input message: BalanceUpdateRequest . 13g38.1.3.2 Ou

17、tput message: BalanceUpdateResponse . 13g38.1.3.3 Referenced faults. 13g38.1.4 Operation: VoucherUpdate . 14g38.1.4.1 Input message: VoucherUpdateRequest 14g38.1.4.2 Output message: VoucherUpdateResponse . 14g38.1.4.3 Referenced Faults 14g38.1.5 Operation: GetHistory. 15g38.1.5.1 Input message: GetH

18、istoryRequest . 15g38.1.5.2 Output message: GetHistoryResponse 15g38.1.5.3 Referenced faults . 15g38.1.6 Operation: GetBalanceTypes 16g38.1.6.1 Input message: GetBalanceTypesRequest . 16g38.1.6.2 Output message: GetBalanceTypesResponse 16g38.1.6.3 Referenced faults . 16g38.2 Interface: AccountManage

19、mentNotificationManager 17g38.2.1 Operation: startNotification 17g38.2.1.1 Input message: startNotificationRequest . 17g38.2.1.2 Output message: startNotificationResponse 17g38.2.1.3 Referenced faults . 17g3ETSI ETSI TS 129 199-7 V9.0.0 (2010-01)43GPP TS 29.199-07 version 9.0.0 Release 98.2.2 Operat

20、ion: endNotification . 18g38.2.2.1 Input message: endNotificationRequest 18g38.2.2.2 Output message: endNotificationResponse . 18g38.2.2.3 Referenced faults. 18g38.3 Interface: AccountNotification . 18g38.3.1 Operation: accountCharged 18g38.3.1.1 Input message: accountChargedRequest . 18g38.3.1.2 Ou

21、tput message: accountChargedResponse 18g38.3.1.3 Referenced faults. 18g38.3.2 Operation: accountRecharged . 19g38.3.2.1 Input message: accountRechargedRequest . 19g38.3.2.2 Output message: accountRechargedResponse 19g38.3.2.3 Referenced faults. 19g38.3.3 Operation: accountLow . 19g38.3.3.1 Input mes

22、sage: accountLowRequest . 19g38.3.3.2 Output message: accountLowResponse 19g38.3.3.3 Referenced faults . 19g39 Fault definitions 20g39.1 Fault: ServiceException . 20g39.1.1 End user authentication failed . 20g39.1.2 Unknown Voucher 20g39.2 Fault: PolicyException . 20g39.2.1 Vouchers not accepted 20g

23、310 Service policies 20g3Annex A (normative): WSDL for Account Management . 21g3Annex B (informative): Description of Parlay X Web Services Part 7: Account management for 3GPP2 cdma2000 networks 22g3B.1 General Exceptions. 22g3B.2 Specific Exceptions 22g3B.2.1 Clause 1: Scope 22g3B.2.2 Clause 2: Ref

24、erences 22g3B.2.3 Clause 3: Definitions and abbreviations . 22g3B.2.4 Clause 4: Detailed service description 22g3B.2.5 Clause 5: Namespaces 22g3B.2.6 Clause 6: Sequence diagrams . 23g3B.2.7 Clause 7: XML Schema data type definition 23g3B.2.8 Clause 8: Web Service interface definition 23g3B.2.9 Claus

25、e 9: Fault definitions 23g3B.2.10 Clause 10: Service policies . 23g3B.2.11 Annex A (normative):WSDL for Account Management . 23g3Annex C (informative): Change history . 24g3History 25g3ETSI ETSI TS 129 199-7 V9.0.0 (2010-01)53GPP TS 29.199-07 version 9.0.0 Release 9Foreword This Technical Specificat

26、ion has been produced by the 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 wor

27、king with the 3GPP community 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

28、TSG with an identifying change 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 increment

29、ed for all changes of substance, 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 7 of a multi-part deliverable covering the 3rdGeneration Partnership

30、 Project; Technical Specification 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: “Accou

31、nt management“ Part 8: “Terminal 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 Servic

32、e (QoS)“ Part 18: “Device Capabilities 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-7 V9.0.0 (2010-01)63GPP TS 29.199-07 version 9.0.0 Release 91 Scope The present do

33、cument is Part 7 of the Stage 3 Parlay X Web Service 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 fun

34、ctional architecture for the 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 Account Management Web Service aspects of the interface. All aspects of the Account Management Web Service are defined here, these being:

35、 Name spaces. Sequence diagrams. Data definitions. 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

36、of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 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 public

37、ation, edition number, version number, etc.) or 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

38、 the latest version of that document in the same 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: “Se

39、rvice aspects; Service principles“. 5 W3C Recommendation (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 Services; Part 1: Common“. 3 Definitions and abbreviations 3.1 De

40、finitions For the purposes of the present document, the terms and definitions given in 3GPP TS 29.199-1 6 apply. ETSI ETSI TS 129 199-7 V9.0.0 (2010-01)73GPP TS 29.199-07 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

41、apply. 4 Detailed service description Pre-paid subscribers, whether they have subscribed to pre-paid telephony, SMS, or data service, have credits with their service providers; the consumption of services will lead to reduction of their credit, or the credit may expire. Therefore, from time to time,

42、 subscribers may have to recharge their accounts. This occurs through an application that interfaces with the subscriber either directly or indirectly. Examples of direct interaction are voice prompts and WAP/web pages, or even SMS. Typically, such multi-modal applications either request a currency

43、amount and, e.g. credit card information, or a voucher number plus credentials. The voucher number and credentials are then validated and causes a pre-determined currency amount to be transferred. The Parlay X Account Management API described in the present document supports account querying, direct

44、 recharging and recharging through vouchers. As a side effect, it may prevent subscribers from having their account balance credits expire. 5 Namespaces The AccountManagement interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/account_management/v4_0 The AccountManagementNotification inte

45、rface uses the namespace: http:/www.csapi.org/wsdl/parlayx/ account_management /notification/v4_0 The AccountManagementNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/ account_management /notification_manager/v4_0 The data types are defined in the namespace: http:/

46、www.csapi.org/schema/parlayx/account_management/v4_0 The xsd namespace is used in the present document to refer to the XML Schema data types defined in XML Schema 5. The use of the name xsd is not semantically significant. ETSI ETSI TS 129 199-7 V9.0.0 (2010-01)83GPP TS 29.199-07 version 9.0.0 Relea

47、se 96 Sequence diagrams This subclause discusses three scenarios; one where a subscriber uses a voucher, one where the subscriber directly recharges after the payment is cleared, and one where the subscriber checks the recent transactions. NOTE: Associated Account Management API messages are shown i

48、n bold format: e.g. (getBalance). 6.1 Prepaid account recharge using a voucher The prepaid subscriber wishes to recharge their account with a voucher and query their account balance. The subscriber uses their mobile phone or other wireline phone to interact with an IVR system. In order to recharge t

49、heir account, the subscriber must enter the voucher number, the MSISDN to be recharged , and PIN(s). The IVR system accesses an external voucher database to validate the voucher number. The subscribers account balance is then increased with the value of the voucher (voucherUpdate). The subscriber queries their account balance (getBalance), before and/or after the recharge. : End User : IVR : Payment Web ServiceLog on to IVREnter voucher informationUpdate voucherAcknowledge receiptRequest balanceGet balanceBalancePlay balan