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

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

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

2、 V9.0.0 (2010-01)1(3GPP TS 29.199-1 version 9.0.0 Release 9) Reference RTS/TSGC-0029199-01v900 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 lucratif

3、 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 do

5、cument 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.ets

6、i.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, PLUGTESTSTM

7、, 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 be

8、nefit 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-1 V9.0.0 (2010-01)2(3GPP TS 29.199-1 version 9.0.0 Release 9) Intellectual Property Rights IPRs essential or potentially essential to t

9、he 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 ETS

10、I 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

11、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). The pres

12、ent 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 htt

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

14、ations . 9g34 Use of Web Services technologies . 10g34.1 Web Service message content 10g34.1.1 SOAP 10g34.1.2 XML . 10g34.1.3 HTTP 10g34.2 Web Service interface definitions 10g34.2.1 WSDL . 10g34.3 Security for Parlay X Web Services . 10g34.4 XML data types 10g35 Detailed service description . 11g35

15、.1 Address data items 11g35.2 Charging . 11g35.2.1 Charging data type 11g35.3 Exception definition . 12g35.4 Service exception . 12g35.5 Policy exception . 13g36 Namespaces 14g37 Sequence diagrams . 14g38 XML Schema data type definition . 14g38.1 TimeMetrics enumeration 14g38.2 TimeMetric structure

16、14g38.3 ChargingInformation structure . 14g38.4 ServiceError structure . 15g38.5 SimpleReference structure 15g38.6 CallParticipantStatus enumeration . 15g38.7 CallParticipantTerminationCause enumeration 15g38.8 CallParticipantInformation Structure . 15g38.9 CallSession Structure . 16g38.10 MediaInfo

17、 structure 16g38.11 Media enumeration . 16g38.12 MediaDirection enumeration 17g38.13 RetrievalStatus enumeration . 17g38.14 NameValuePair structure . 17g39 Web Service interface definition 17g310 Fault definitions 17g310.1 ServiceException 17g310.1.1 SVC0001: Service error 17g310.1.2 SVC0002: Invali

18、d input value 18g310.1.3 SVC0003: Invalid input value with list of valid values 18g310.1.4 SVC0004: No valid address(es) 18g3ETSI ETSI TS 129 199-1 V9.0.0 (2010-01)4(3GPP TS 29.199-1 version 9.0.0 Release 9) 10.1.5 SVC0005: Duplicate correlator. 18g310.1.6 SVC0006: Invalid group . 18g310.1.7 SVC0007

19、: Invalid charging information. 18g310.1.8 SVC0008: Overlapping Criteria . 18g310.2 PolicyException . 19g310.2.1 POL0001: Policy error 19g310.2.2 POL0002: Privacy error 19g310.2.3 POL0003: Too many addresses 19g310.2.4 POL0004: Unlimited notifications not supported . 19g310.2.5 POL0005: Too many not

20、ifications requested . 19g310.2.6 POL0006: Groups not allowed . 20g310.2.7 POL0007: Nested groups not allowed 20g310.2.8 POL0008: Charging not supported . 20g310.2.9 POL0009: Invalid frequency requested 20g310.2.10 POL0010: Retention time interval expired . 20g310.2.11 POL0011: Media Type not suppor

21、ted . 20g310.2.12 POL0012: Too many description entries specified . 20g310.2.13 POL0013: Addresses duplication . 21g310.3 Fault number ranges by service 21g311 Service policies 21g312 WSDL usage and style . 21g312.1 Service definition and documents 22g312.1.1 Interface sets . 22g312.1.2 Preparing fo

22、r document definition 22g312.1.3 Documents 23g312.1.3.1 Types definition document 23g312.1.3.2 Shared faults document . 23g312.1.3.3 Service interface document . 23g312.1.3.4 Service bindings document . 23g312.1.4 Document separation rationale . 24g312.1.5 Document version identifier . 24g312.1.6 Do

23、cument naming example 24g312.1.7 Service definitions for notification patterns 24g312.2 Namespaces 25g312.2.1 Namespaces for Parlay X Web Services . 25g312.2.2 Use of namespaces 25g312.2.3 Namespace elements . 25g312.2.4 Namespace Usage . 26g312.2.4.1 Why namespace versions are used 26g312.2.4.2 Whe

24、n namespace versions are changed 26g312.2.4.3 Benefit of managing namespace versions . 26g312.2.5 Common namespaces . 27g312.2.6 Target namespace . 27g312.2.7 WSDL and Schema namespaces . 27g312.2.8 Local namespace use 28g312.2.9 Examples 28g312.3 Authoring style - Document content and names . 28g31

25、2.3.1 General WSDL document information . 28g312.3.2 Names . 28g312.3.3 Case usage for names 29g312.3.4 Naming conventions for special names 29g312.3.5 Document layout . 29g312.4 Data type definitions 30g312.4.1 Types section declaration 30g312.4.1.1 Optional elements . 30g312.4.1.2 Nillable element

26、s. 30g312.4.1.3 User defined simple data types 30g312.4.1.4 Data structures . 30g312.4.1.5 Enumerations 31g312.4.1.6 Unions . 31g3ETSI ETSI TS 129 199-1 V9.0.0 (2010-01)5(3GPP TS 29.199-1 version 9.0.0 Release 9) 12.4.1.7 Web Service references . 31g312.5 Messages and interfaces (PortTypes) . 32g312

27、.5.1 Message Parts . 32g312.5.1.1 Document style Web Services. 32g312.5.2 Interfaces (PortTypes) . 32g312.5.3 Faults (Exceptions) . 32g312.6 Bindings and service definitions 33g312.6.1 Binding . 33g312.6.2 Service definition 33g313 Backward Compatibility Guidelines 34g313.1 Implementation Guidelines

28、 for Server Programmers . 34g313.2 Implementation Guidelines for Client Programmers 34g313.3 Removal of items from the specifications 34g3Annex A (normative): WSDL for common data definitions 36g3Annex B (informative): Description of Parlay X Web Services Part 1: Common Definitions for 3GPP2 cdma200

29、0 networks 37g3B.1 General Exceptions. 37g3B.2 Specific Exceptions 37g3B.2.1 Clause 1: Scope 37g3B.2.2 Clause 2: References 37g3B.2.3 Clause 3: Definitions and abbreviations . 37g3B.2.4 Clause 4: Use of Web Services technologies . 37g3B.2.5 Clause 5: Detailed service description 37g3B.2.6 Clause 6:

30、Namespaces 38g3B.2.7 Clause 7: Sequence diagrams . 38g3B.2.8 Clause 8: XML Schema data type definition 38g3B.2.9 Clause 9: Web Service interface definition 38g3B.2.10 Clause 10: Fault definitions 38g3B.2.11 Clause 11: Service policies . 38g3B.2.12 Clause 12: WSDL usage and style . 38g3B.2.13 Annex A

31、 (normative): WSDL for common data definitions 38g3Annex C (informative): Change history 39g3History 40g3ETSI ETSI TS 129 199-1 V9.0.0 (2010-01)6(3GPP TS 29.199-1 version 9.0.0 Release 9) Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). 3GPP ac

32、knowledges 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 community to improve future versions of the present documen

33、t. 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 change of release date and an increase in version numb

34、er 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 substance, i.e. technical enhancements, corrections, upd

35、ates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 1 of a multi-part TS covering the 3rdGeneration Partnership Project; Technical Specification Group Core Network and Terminals; Open Service Access

36、 (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: “Terminal Status“ Part 9: “Terminal location“ Part 10: “Call han

37、dling“ 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 Capabilities and Configuration“ Part 19: “Multimedia streamin

38、g control“ Part 20: “Multimedia multicast session management“ Part 21: “Content management“ Part 22: “Policy“ ETSI ETSI TS 129 199-1 V9.0.0 (2010-01)7(3GPP TS 29.199-1 version 9.0.0 Release 9) The Mapping specification of the Parlay X Web Services (3GPP TS 29.199) to the Parlay/OSA APIs (3GPP TS 29.

39、198) and, where applicable, to IMS, is also structured as above. A mapping of the Parlay X Web Services is however not applicable for all Parts (e.g. Part 13), but the numbering of Parts is kept. Table: Overview of the Parlay X Web Services Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Sta

40、ge 2“. 4 3GPP TS 22.101: “Service 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 IETF RFC 3966: “The tel URI for Telephone Numbers“. NOTE: Available at http:/www.ietf.org/rfc/rf

41、c3966.txt. 7 IETF RFC 3261: “SIP: Session Initiation Protocol“. NOTE: Available at htpp:/www.ietf.org/rfc/rfc3261.txt. 8 WS-I Basic Profile Version 1.0: “Final Material“. NOTE: Available at http:/www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html. 9 W3C Note (15 March 2001): “Web Services Descri

42、ption Language (WSDL) 1.1“. NOTE: Available at http:/www.w3.org/TR/2001/NOTE-wsdl-20010315. 10 OASIS Standard 200401 (March 2004): “Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)“. ETSI ETSI TS 129 199-1 V9.0.0 (2010-01)9(3GPP TS 29.199-1 version 9.0.0 Release 9) NOTE: Available

43、 at http:/docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf. 11 W3C Recommendation (12 February 2002): “XML-Signature Syntax and Processing“. NOTE: Available at http:/www.w3.org/TR/2002/REC-xmldsig-core-20020212/. 12 ISO 4217: “Codes for the representation of currencies

44、and funds“. 13 IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“. NOTE: Available at http:/www.ietf.org/rfc/rfc3986.txt. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: application: computer program

45、 that accesses a Web Service SOAP: not an acronym, protocol used for XML messaging Web Service: software system designed to support interoperable machine-to-machine interaction over a network Web Service Provider: entity which provides Web Services interfaces to capabilities offered Web Service Requ

46、ester: entity which operates Applications that access Web Services 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: IP Internet Protocol IT Information Technology OASIS Organization for the Advancement of Structured Information Standards OSA Open Service

47、 AccessPSTN Public Switched Telephone Network RFC Request For Comment SIP Session Initiation Protocol SLA Service Level Agreement URI Uniform Resource Identifier W3C World Wide Web Consortium WSDL Web Service Definition Language WS-I Web Services-Interoperability Organization XML Extensible Markup L

48、anguage ETSI ETSI TS 129 199-1 V9.0.0 (2010-01)10(3GPP TS 29.199-1 version 9.0.0 Release 9) 4 Use of Web Services technologies 4.1 Web Service message content 4.1.1 SOAP All Web Service messages SHALL send and accept messages that conform to the SOAP use defined in the WS-I Basic Profile 8, using th

49、e document/literal encoding style. 4.1.2 XML All Web Service messages SHALL send and accept messages that conform to the XML use defined in the WS-I Basic Profile 8. 4.1.3 HTTP All Web Service messages SHALL send and accept messages that conform to the HTTP use defined in the WS-I Basic Profile 8. 4.2 Web Service interface definitions All Parlay X Web Services are defined according to the following. 4.2.1 WSDL All Web Service interfaces SHALL be defined using WSDL 1.1 as defined in the WSDL specification 9 and be conformant to the WSDL us