1、 ETSI ES 202 504-1 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 1: Common(Parlay X 3)floppy3 ETSI ETSI ES 202 504-1 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01034-1-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE
2、 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 present document may be m
3、ade 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 k
4、ept 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/status/status.asp If yo
5、u 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 restriction extend to reprodu
6、ction in all media. European Telecommunications Standards Institute 2008. The Parlay Group 2008. All rights reserved. DECTTM, 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
7、for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 504-1 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights6 Foreword.6 1 Scope 8 2 References 8 2.1 Normative references .8 3 Definitions and abbreviations.9 3.1 Definitions9 3.2 Abbreviations .9 4 Use of We
8、b Services technologies .10 4.1 Web Service message content 10 4.1.1 SOAP 10 4.1.2 XML .10 4.1.3 HTTP 10 4.2 Web Service interface definitions 10 4.2.1 WSDL.10 4.3 Security for Parlay X 3 Web Services 10 4.4 XML data types10 5 Detailed service description .11 5.1 Address data items11 5.2 Charging.11
9、 5.2.1 Charging data type11 5.3 Exception definition .12 5.4 Service exception .12 5.5 Policy exception .12 6 Namespaces13 7 Sequence diagrams.13 8 XML Schema data type definition .13 8.1 TimeMetrics enumeration 13 8.2 TimeMetric structure13 8.3 ChargingInformation structure .13 8.4 ServiceError str
10、ucture.14 8.5 SimpleReference structure14 8.6 CallParticipantStatus enumeration .14 8.7 CallParticipantTerminationCause enumeration14 8.8 CallParticipantInformation structure 15 8.9 CallSession structure 15 8.10 MediaInfo structure 15 8.11 Media enumeration.15 8.12 MediaDirection enumeration15 9 Web
11、 Service interface definition16 10 Fault definitions16 10.1 ServiceException16 10.1.1 SVC0001: Service error16 10.1.2 SVC0002: Invalid input value 16 10.1.3 SVC0003: Invalid input value with list of valid values 16 10.1.4 SVC0004: No valid address(es)16 10.1.5 SVC0005: Duplicate correlator.17 10.1.6
12、 SVC0006: Invalid group.17 10.1.7 SVC0007: Invalid charging information.17 10.1.8 SVC0008: Overlapping Criteria .17 ETSI ETSI ES 202 504-1 V1.1.1 (2008-05) 4 10.2 PolicyException .17 10.2.1 POL0001: Policy error17 10.2.2 POL0002: Privacy error18 10.2.3 POL0003: Too many addresses 18 10.2.4 POL0004:
13、Unlimited notifications not supported.18 10.2.5 POL0005: Too many notifications requested .18 10.2.6 POL0006: Groups not allowed .18 10.2.7 POL0007: Nested groups not allowed 18 10.2.8 POL0008: Charging not supported .18 10.2.9 POL0009: Invalid frequency requested 19 10.2.10 POL0010: Retention time
14、interval expired .19 10.2.11 POL0011: Media type not supported19 10.3 Fault number ranges by service19 11 Service policies 19 12 WSDL usage and style .19 12.1 Service definition and documents 20 12.1.1 Interface sets .20 12.1.2 Preparing for document definition20 12.1.3 Documents 21 12.1.3.1 Types d
15、efinition document21 12.1.3.2 Shared faults document .21 12.1.3.3 Service interface document .21 12.1.3.4 Service bindings document .21 12.1.4 Document separation rationale .22 12.1.5 Document version identifier .22 12.1.6 Document naming example 22 12.1.7 Service definitions for notification patter
16、ns23 12.2 Namespaces23 12.2.1 Namespaces for Parlay X 3 Web Services23 12.2.2 Use of namespaces23 12.2.3 Namespace elements.24 12.2.4 Namespace usage24 12.2.4.1 Why namespace versions are used 24 12.2.4.2 When namespace versions are changed 24 12.2.4.3 Benefit of managing namespace versions .25 12.2
17、.5 Common namespaces .25 12.2.6 Target namespace .25 12.2.7 WSDL and Schema namespaces.25 12.2.8 Local namespace use 26 12.2.9 Examples 26 12.3 Authoring style - Document content and names.26 12.3.1 General WSDL document information.26 12.3.2 Names .26 12.3.3 Case usage for names27 12.3.4 Naming con
18、ventions for special names 27 12.3.5 Document layout.27 12.4 Data type definitions 28 12.4.1 Types section declaration28 12.4.1.1 Optional elements .28 12.4.1.2 Nillable elements.28 12.4.1.3 User defined simple data types28 12.4.1.4 Data structures.29 12.4.1.5 Enumerations 29 12.4.1.6 Unions .29 12.
19、4.1.7 Web Service references.29 12.5 Messages and interfaces (PortTypes) .30 12.5.1 Messages.30 12.5.1.1 Document style Web Services.30 12.5.2 Interfaces (PortTypes).30 12.5.3 Faults (Exceptions) .30 ETSI ETSI ES 202 504-1 V1.1.1 (2008-05) 5 12.6 Bindings and service definitions 31 12.6.1 Binding .3
20、1 12.6.2 Service definition31 Annex A (normative): WSDL for common data definitions 32 History 33 ETSI ETSI ES 202 504-1 V1.1.1 (2008-05) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these
21、 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 u
22、pdates 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 as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on
23、the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part
24、1 of a multi-part deliverable covering 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:
25、 “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 Service (QoS)“; Par
26、t 18: “Device Capabilities and Configuration“; Part 19: “Multimedia Streaming Control“; Part 20: “Multimedia Multicast Session Management“. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. The present document forms part of the Parlay
27、X 3.0 set of specifications. ETSI ETSI ES 202 504-1 V1.1.1 (2008-05) 7 The present document is equivalent to 3GPP TS 29.199-01 V7.2.0 (Release 7). The Mapping specification of the Parlay X 3 Web Services (ES 202 504) to the Parlay/OSA APIs (ES 203 915 11) and, where applicable, to IMS, is also struc
28、tured as above. A mapping of the Parlay X 3 Web Services is however not applicable for all parts (e.g. part 13), but the numbering of parts is kept. Table 1: Overview of the Parlay X 3 Web Services and OSA APIs mappings Parlay X 3 Web Services (ES 202 504 series) OSA APIs (and IMS) mappings (TR 102
29、397 series) ES 202 504-1 Common TR 102 397-1 Common mapping TR 102 397-2-1 Generic Call Control mapping ES 202 504-2 Third party call TR 102 397-2-2 Multi-Party Call Control mapping TR 102 397-3-1 Generic Call Control mapping ES 202 504-3 Call notification TR 102 397-3-2 Multi-Party Call Control map
30、ping TR 102 397-4-1 User Interaction mapping ES 202 504-4 Short messaging TR 102 397-4-2 Multi-Media Messaging mapping TR 102 397-5-1 User Interaction mapping ES 202 504-5 Multimedia messaging TR 102 397-5-2 Multi-Media Messaging mapping ES 202 504-6 Payment TR 102 397-6 Charging mapping ES 202 504-
31、7 Account management TR 102 397-7 Account Management mapping ES 202 504-8 Terminal status TR 102 397-8 Mobility User Status mapping TR 102 397-9-1 Mobility User Location mapping ES 202 504-9 Terminal location TR 102 397-9-2 Mobility User Location CAMEL mapping TR 102 397-10-1 Generic Call Control -
32、for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the prima
33、ry 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,
34、with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the appli
35、cation of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 ETSI TR 121 905: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommuni
36、cations System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905 version 7.2.0 Release 7)“. 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 IETF RFC 3966: “The tel URI for Telephone Numbers“. ETSI E
37、TSI ES 202 504-1 V1.1.1 (2008-05) 9 NOTE: Available at: http:/www.ietf.org/rfc/rfc3966.txt. 4 IETF RFC 3261: “SIP: Session Initiation Protocol“. NOTE: Available at: http:/www.ietf.org/rfc/rfc3261.txt. 5 WS-I Basic Profile Version 1.0: “Final Material“. NOTE: Available at: http:/www.ws-i.org/Profiles
38、/BasicProfile-1.0-2004-04-16.html. 6 W3C Note (15 March 2001): “Web Services Description Language (WSDL) 1.1“. NOTE: Available at: http:/www.w3.org/TR/2001/NOTE-wsdl-20010315. 7 OASIS Standard 200401 (March 2004): “Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)“. NOTE: Available
39、 at: http:/docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf. 8 W3C Recommendation (12 February 2002): “XML-Signature Syntax and Processing“. NOTE: Available at: http:/www.w3.org/TR/2002/REC-xmldsig-core-20020212/. 9 ISO 4217: “Codes for the representation of currencies
40、and funds“. 10 IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“. NOTE: Available at: http:/www.ietf.org/rfc/rfc3986.txt. 11 ETSI ES 203 915 (All parts): “Open Service Access (OSA); Application Programming Interface (API)“. 3 Definitions and abbreviations 3.1 Definitions For the pur
41、poses of the present document, the following terms and definitions apply: application: computer program 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 S
42、ervice Provider: entity which provides Web Services interfaces to capabilities offered Web Service Requester: entity which operates Applications that access Web Services 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 121 905 1 and the following apply: 3GPP
43、Third Generation Partnership Project ETSI European Telecommunications Standards Institute IT Information Technology OASIS Organization for the Advancement of Structured Information Standards OSA Open Service AccessRFC Request For Comment SIP Session Initiation Protocol UDDI Universal Description Dis
44、covery and Integration URI Uniform Resource Identifier W3C World Wide Web Consortium ETSI ETSI ES 202 504-1 V1.1.1 (2008-05) 10WSDL Web Service Definition Language WS-I Web Services-Interoperability Organization XML Extensible Markup Language 4 Use of Web Services technologies 4.1 Web Service messag
45、e 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 5, using the 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
46、Basic Profile 5. 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 5. 4.2 Web Service interface definitions All Parlay X 3 Web Services are defined according to the following. 4.2.1 WSDL All Web Service interfaces SHALL
47、be defined using WSDL 1.1 as defined in the WSDL specification 6 and be conformant to the WSDL use defined in WS-I Basic Profile 5. See clause 12 for detailed information on the WSDL style to be followed by Parlay X 3 Web Services. 4.3 Security for Parlay X 3 Web Services If a message contains an id
48、entifier and/or credentials representing the sender of the message then these SHALL be provided in a manner prescribed by WS-Security 7. Encryption of message content MAY be required by the Web Service Provider. If this is required, then this SHALL be accomplished in one of the following manners: Us
49、e of a Virtual Private Network, to be administered independent of the Web Service implementation. Use of Transport Level Security using HTTP over TLS as specified in the WS-I Basic Profile 5. Integrity of the message content MAY be required by the Web Service Provider. If this is required, then this SHALL be accomplished using XML Digital Signature 8. 4.4 XML data types Where possible standard XML Schema data types are used, as defined in clause 3 (Built-in datatypes) in XML Schema 2. ETSI ETSI ES 202 504-1 V1.1.1 (200
