1、 ETSI TR 102 397-1 V1.1.1 (2005-08)Technical Report Open Service Access (OSA);Mapping of Parlay X Web Services to Parlay/OSA APIs;Part 1: Common MappingETSI ETSI TR 102 397-1 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-01-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia An
2、tipolis 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 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 pre
3、sent 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 printer
4、s of the PDF version kept 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/s
5、tatus/status.asp If you 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 restric
6、tion extend to reproduction in all media. European Telecommunications Standards Institute 2005. The Parlay Group 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being re
7、gistered by ETSI 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. ETSI ETSI TR 102 397-1 V1.1.1 (2005-08) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 3 Definitions and ab
8、breviations.6 3.1 Definitions6 3.2 Abbreviations .6 4 Mapping description.6 5 Sequence diagrams.6 6 Detailed Mapping Information.7 6.1 Data Types7 6.1.1 Mapping of URI address to TpAddressPlan.7 6.1.2 Mapping of TpAddressPlan to URI address.7 6.1.3 Mapping of TimeMetric to TpDuration.7 6.1.4 Mapping
9、 of TpDuration to TimeMetric.8 6.1.5 Mapping of TimeMetric0 unbounded to TpDate(AndTime),TpTime8 6.1.6 Mapping of TpDate(AndTime),TpTime to TimeMetric0 unbounded8 6.1.7 Mapping of ChargingInformation to TpAoCInfo8 6.2 Exceptions 9 6.2.1 Mapping of TpCommonExceptions to ServiceException.9 6.2.2 Mappi
10、ng of Common Parlay/OSA Exceptions to ServiceException9 7 Additional Notes 9 History 10 ETSI ETSI TR 102 397-1 V1.1.1 (2005-08) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential
11、 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
12、 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 the ETSI W
13、eb server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 1 of a
14、multi-part deliverable covering Open Service Access (OSA); Mapping of Parlay X Web Services to Parlay/OSA APIs, as identified below: Part 1: “Common Mapping“; Part 2: “Third Party Call Mapping“; Part 3: “Call Notification Mapping“; Part 4: “Short Messaging Mapping“; Part 5: “Multimedia Messaging Map
15、ping“; Part 6: “Payment Mapping“; Part 7: “Account Management Mapping“; Part 8: “Terminal Status Mapping“; Part 9: “Terminal Location Mapping“; Part 10: “Call Handling Mapping“; Part 11: “Audio Call Mapping“; Part 12: “Multimedia Conference Mapping“; Part 14: “Presence Mapping“; NOTE: Part 13 has no
16、t been provided as there is currently no defined mapping between ES 202 391-13 11 and the Parlay/OSA APIs. If a mapping is developed, it will become part 13 of this series. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR
17、102 397-1 V1.1.1 (2005-08) 5 1 Scope The Parlay X Web Services provide powerful yet simple, highly abstracted, imaginative, telecommunications functions that application developers and the IT community can both quickly comprehend and use to generate new, innovative applications. The Open Service Acc
18、ess (OSA) specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the Parlay/OSA APIs. The present document specifies the mapping of the Parlay X Common Data to the Parlay/OSA Common Data Definitions.
19、 2 References For the purposes of this Technical (TR), the following references apply: 1 ETSI TR 121 905: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905)“. 2 W3C Recommendation (2 May 2001)
20、: “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 3 IETF RFC 2806: “URLs for Telephone Calls“. NOTE: Available at http:/www.ietf.org/rfc/rfc2806.txt. 4 IETF RFC 3261: “SIP: Session Initiation Protocol“. NOTE: Available at http:/www.ietf.org/rfc/
21、rfc3261.txt. 5 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. 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 Standa
22、rd 200401 (March 2004): “Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)“. NOTE: Available 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 h
23、ttp:/www.w3.org/TR/2002/REC-xmldsig-core-20020212/. 9 ISO 4217: “Codes for the representation of currencies and funds“. 10 IETF RFC 2368: “The mailto URL Scheme“. NOTE: Available at http:/www.ietf.org/rfc/rfc2368.txt. 11 ETSI ES 202 391-13: “Open Service Access (OSA); Parlay X Web Services; Part 13:
24、 Address List Management“. ETSI ETSI TR 102 397-1 V1.1.1 (2005-08) 6 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: application: computer program that accesses a Web Service SOAP: protocol used for XML messaging NO
25、TE: It is not an acronym. 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 Requester: entity which operates applications that access web
26、 services 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in TR 121 905 1 and the following apply: 3GPP Third Generation Partnership Project ETSI European Telecommunications Standards Institute IMS IP Multimedia Subsystem IP Internet Protocol IT Information Tech
27、nology OASIS Organization for the Advancement of Structured Information Standards OSA Open Service AccessRFC Request For Comment SIP Session Initiation Protocol URI Uniform Resource Identifier W3C World Wide Web Consortium WSDL Web Service Definition Language WS-I Web Services - Interoperability org
28、anization XML Extensible Markup Language 4 Mapping description There are mappings from both data definitions and exceptions defined in the Parlay/OSA Common Data Definitions (Part 2) and Parlay X Web Services. These mappings are applicable to all Parlay/OSA releases, i.e. ETSI OSA 1.x/2.x/3.x, Parla
29、y/OSA 3.x/4.x/5.x and 3GPP Releases 4/5/6, with specific release references specified for each mapped item. 5 Sequence diagrams No sequence diagrams. ETSI ETSI TR 102 397-1 V1.1.1 (2005-08) 7 6 Detailed Mapping Information 6.1 Data Types 6.1.1 Mapping of URI address to TpAddressPlan This mapping fol
30、lows Parlay/OSA rules for formatting, as defined in ES 201 915-2, ES 202 915-2 and ES 203 915-2: i.e. clause 5.6 of Common Data Definitions (Part 2). This mapping follows Parlay/OSA rules for formatting, as defined in ES 20X 915-2: i.e. clause 5.6 of Common Data Definitions (Part 2). URI TpAddressPl
31、an Notes P_ADDRESS_PLAN_E164 An international number without the international access code, including the country code and excluding the leading zero of the area code. P_ADDRESS_PLAN_NATIONAL Reserved for National Specific use - refer to relevant National Numbering Plan Specification. This mapping i
32、s not supported in Parlay/OSA 3.2, 4.0 or earlier versions, or in the equivalent ETSI and 3GPP releases. tel P_ADDRESS_PLAN_UNDEFINED Default if not mappable to “E164“ or “NATIONAL“ sip P_ADDRESS_PLAN_SIP mailto P_ADDRESS_PLAN_SMTP 6.1.2 Mapping of TpAddressPlan to URI address TpAddressPlan URI Note
33、s P_ADDRESS_PLAN_E164 tel Conformant to 2, using either a national address syntax (no leading “+“ and country code) or an international address syntax (with leading “+“ and country code). P_ADDRESS_PLAN_NATIONAL tel Conformant to 2, using a national address syntax (no leading “+“ and country code).
34、This mapping is not supported in Parlay/OSA 3.2, 4.0 or earlier versions, or in the equivalent ETSI and 3GPP releases. P_ADDRESS_PLAN_SIP sip Conformant to 3 P_ADDRESS_PLAN_SMTP mailto Conformant to 11 6.1.3 Mapping of TimeMetric to TpDuration If a message part is of type TimeMetric, but not of type
35、 TimeMetric 0 unbounded, then the TimeMetric data type maps to the TpDuration data type, as follows: If the Metric element of TimeMetric has a value of Millisecond, then TpDuration is assigned the value of the Units element of TimeMetric. If the Metric element of TimeMetric has any other value, then
36、 TpDuration is assigned the value the Units element of TimeMetric multiplied by the number of milliseconds in the Metric element. For example if the Metric element of TimeMetric has a value of Hour, then the multiplier is 3.6*106(i.e.1000*60*60). NOTE: If the Metric element of TimeMetric has a calen
37、dar-sensitive value of Month or Year, then the multiplier should be computed based on a calendar interval commencing at the time of the message receipt and associated mapping operation. ETSI ETSI TR 102 397-1 V1.1.1 (2005-08) 8 6.1.4 Mapping of TpDuration to TimeMetric TpDuration maps to TimeMetric
38、as follows: The Metric element of TimeMetric is assigned a value of Millisecond. The Units element of TimeMetric is assigned the value of the TpDuration parameter. 6.1.5 Mapping of TimeMetric0 unbounded to TpDate(AndTime),TpTime If a message part is of type TimeMetric 0 unbounded with at least two e
39、lements, then the following table specifies the valid combinations of TimeMetric elements and how they are mapped. Note that: the Units elements of the TimeMetric elements must together represent a valid calendar date and/or time of day. EXAMPLE: “29 February 2005“ is invalid. The time zone associat
40、ed with the date and/or time information contained in the TimeMetric elements is unspecified.: time zone should be specified explicitly in a parameter of the message or in a web service policy. TimeMetric0 unbounded TpXxx Notes 1 Metric=Year,Units=YYYY Metric=Month,Units=MM TpDate Default: the Day f
41、ield is assumed to be “01“ 2 Metric=Year,Units=YYYY Metric=Month,Units=MM Metric=Day,Units=DD TpDate 3 Metric=Hour,Units=HH Metric=Minute,Units=MM TpTime Default: the Second field is assumed to be “00“ and the Millisecond field “000“ 4 Metric=Hour,Units=HH Metric=Minute,Units=MM Metric=Second,Units=
42、SS TpTime Default: the Millisecond field is assumed to be “000“ 5 Metric=Hour,Units=HH Metric=Minute,Units=MM Metric=Second,Units=SS Metric=Millisecond,Units=mmm TpTime 6 1+3; 1+4; 1+5; 2+3; 2+4; 2+5 TpDateAndTime 7 Metric=Year,Units=YYYY Metric=Hour,Units=HH TpDateAndTime Default: the Month field i
43、s assumed to be “01“, the Day field “01“, the Minute field “00“, the Second field “00“ and the Millisecond field “000“ 8 Metric=Year,Units=YYYY + 3,4 or 5 TpDateAndTime Default: the Month field is assumed to be “01“ and the Day field “01“, 9 Metric=Hour,Units=HH + 1 or 2 TpDateAndTime Default: the M
44、inute field is assumed to be “00“, the Second field “00“ and the Millisecond field “000“ 6.1.6 Mapping of TpDate(AndTime),TpTime to TimeMetric0 unbounded The mapping is symmetric - see preceding clause for details. 6.1.7 Mapping of ChargingInformation to TpAoCInfo The following table specifies a def
45、ault common parameter mapping for the ChargingInformation parameter. This mapping may be overridden for a specific web service. For example, for the Third Party Call web service, the ChargingInformation parameter may be mapped instead to TpCallChargePlan. ETSI ETSI TR 102 397-1 V1.1.1 (2005-08) 9 Ch
46、argingInformation TpAoCInfo Notes Description Currency Currency Amount Map be mapped instead to TpPrice Code ChargeOrder:NetworkCharge i.e. TpCallAoCOrderCategory = P_CHARGE_NETWORK 6.2 Exceptions 6.2.1 Mapping of TpCommonExceptions to ServiceException The following table lists the default mapping o
47、f the Parlay/OSA TpCommonExceptions class. Parlay/OSA Exception Service Exception Notes P_RESOURCES_UNAVAILABLE SVC0001 With error number P_TASK_REFUSED SVC0001 With error number P_TASK_CANCELLED SVC0001 With error number P_NO_CALLBACK_ADDRESS_SET SVC0001 With error number P_METHOD_NOT_SUPPORTED SVC
48、0001 With error number P_INVALID_STATE SVC0001 With error number 6.2.2 Mapping of Common Parlay/OSA Exceptions to ServiceException The following table lists the default mapping of the Parlay/OSA exception classes that are available to all Parlay/OSA APIs. These mappings may be overridden for a speci
49、fic web service. For example, for the Account Management web service, the P_INVALID_ASSIGNMENT_ID exception may be mapped instead to SVC0251 Unknown Voucher since the voucher ID is explicitly specified as a web service interface message part. Parlay/OSA Exception Service Exception Notes P_APPLICATION_NOT_ACTIVATED SVC0001 With error number P_INFORMATION_NOT_AVAILABLE SVC0001 With error number P_INVALID_ADDRESS SVC0004 P_INVALID_AMOUNT SVC0002 SVC0003 P_INVALID_ASSIGN
