1、 ETSI ES 202 391-2 V1.3.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 2: Third Party Call(Parlay X 2)floppy3 ETSI ETSI ES 202 391-2 V1.3.1 (2008-05) 2 Reference RES/TISPAN-01056-02-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Ced
2、ex - 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 present docume
3、nt 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 printers of the PD
4、F 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/status/statu
5、s.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 restriction extend
6、 to reproduction 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
7、registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 391-2 V1.3.1 (2008-05) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 2.1 Normative references .5 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .6
8、4 Detailed service description .6 5 Namespaces7 6 Sequence diagrams.7 6.1 “Click to Dial“ call setup7 7 XML Schema data type definition .8 7.1 CallStatus enumeration.8 7.2 CallTerminationCause enumeration.9 7.3 CallInformation Structure.9 8 Web Service interface definition9 8.1 Interface: ThirdParty
9、Call9 8.1.1 Operation: makeCall.9 8.1.1.1 Input message: makeCallRequest9 8.1.1.2 Output message : makeCallResponse10 8.1.1.3 Referenced faults.10 8.1.2 Operation: getCallInformation10 8.1.2.1 Input message: getCallInformationRequest 10 8.1.2.2 Output message : getCallInformationResponse 10 8.1.2.3
10、Referenced faults.10 8.1.3 Operation: endCall10 8.1.3.1 Input message: endCallRequest 10 8.1.3.2 Output message: endCallResponse .11 8.1.3.3 Referenced faults.11 8.1.4 Operation: cancelCall .11 8.1.4.1 Input message: cancelCallRequest 11 8.1.4.2 Output message: cancelCallResponse.11 8.1.4.3 Referenc
11、ed faults.11 9 Fault definitions12 9.1 ServiceException12 9.1.1 SVC0260: Call already connected12 9.1.2 SVC0261: Call already terminated .12 10 Service policies 12 Annex A (normative): WSDL for Third Party Call13 Annex B (informative): Bibliography.14 History 15 ETSI ETSI ES 202 391-2 V1.3.1 (2008-0
12、5) 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 IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Pro
13、perty 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 available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, in
14、cluding 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 Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been
15、produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 2 of a multi-part deliverable covering Open Service Access (OSA); Parlay X Web Services, as identified below: Part 1: “Common“; Part 2:
16、 “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 Handling“; Part 11: “Audio Call“; Part 12: “Multimedia Conference“; Par
17、t 13: “Address List Management“; Part 14: “Presence“. 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 X 2.2 set of specifications. The present document is equivalent to 3GPP TS 29.199-02 V
18、6.5.0 (Release 6). ETSI ETSI ES 202 391-2 V1.3.1 (2008-05) 5 1 Scope The present document is part 2 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers to make use of network functionali
19、ty through an open standardized interface, i.e. the OSA APIs. The present document specifies the Third Party Call Web Service. The following are defined here: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method descriptions. Fault definitions. Service Polic
20、ies. WSDL Description of the interfaces. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete documen
21、t or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the ex
22、pected 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 primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
23、 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, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks incl
24、uded 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 application of the present document. For dated references, only the edition cited applies. For non-specific
25、references, the latest edition of the referenced document (including any amendments) applies. 1 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at: http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 391-2 V1.3.1 (2008-05) 6 2 ETSI ES 202 391-1: “Ope
26、n Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 2)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 202 391-1 2 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviation
27、s given in ES 202 391-1 2 apply. 4 Detailed service description Currently, in order to perform a third party call in telecommunication networks we have to write applications using specific protocols to access Call Control functions provided by network elements (specifically operations to initiate a
28、call from applications). This approach requires a high degree of network expertise. We can also use the OSA gateway approach, invoking standard interfaces to gain access to call control capabilities, but these interfaces are usually perceived to be quite complex by application IT developers. Develop
29、ers must have advanced telecommunication skills to use Call Control OSA interfaces. In this clause we describe a Parlay X 2 Web Service, Third Party Call, for creating and managing a call initiated by an application (third party call). The overall scope of this Web Service is to provide functions to
30、 application developers to create a call in a simple way. Using the Third Party Call Web Service, application developers can invoke call handling functions without detailed telecommunication knowledge. Figure 1 shows a scenario using the Third Party Call Web Service to handle third party call functi
31、ons. The application invokes a Web Service to retrieve stock quotes and a Parlay X 2 Interface to initiate a third party call between a broker and his client. In the scenario, whenever a particular stock quote reaches a threshold value (1) and (2), the client application invokes a third party call b
32、etween one or more brokers and their corresponding customers to decide actions to be taken. After invocation (3) by the application, the Third Party Call Web Service invokes a Parlay API method (4) using the Parlay/OSA SCS-CC (Call control) interface. This SCS handles the invocation and sends a mess
33、age (5) to an MSC to set-up a call between user A and user B. In an alternative scenario, the Parlay API interaction involving steps (4) and (5) could be replaced with a direct interaction between the Third Party Call Web Service and the Mobile network. ETSI ETSI ES 202 391-2 V1.3.1 (2008-05) 7 3PC-
34、XcomponentThird PartyCall WebServiceParlay X I/FParlay GatewayMSCMSCSCS-CCSCS-CCParlay APIMobile networkStock QuotesWeb ServiceStock QuotesWeb ServicegetStockQuote()Retrieveuser Profile ( userA,userB).makeACall (userA,userB,)Userprofile12345UserA(broker)UserB(customer)Figure 1: Third party call scen
35、ario 5 Namespaces The ThirdPartyCall interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/third_party_call/v2_4 The data types are defined in the namespace: http:/www.csapi.org/schema/parlayx/third_party_call/v2_3 The “xsd“ namespace is used in the present document to refer to the XML Sche
36、ma data types defined in XML Schema 1. The use of the name “xsd“ is not semantically significant. 6 Sequence diagrams 6.1 “Click to Dial“ call setup A common convergence application is Click to Dial, where a self service portal provides a web page that can initiate a call between two phones. This se
37、quence shows a basic call setup, and ending the call through the portal. ETSI ETSI ES 202 391-2 V1.3.1 (2008-05) 8 : End User : Self Serve Portal: Third Party Call Web ServiceAccess portalUse Click to Dial pageMake callCall identifierReport call in progressSome discussionClick on end callEnd callFig
38、ure 2 7 XML Schema data type definition 7.1 CallStatus enumeration List of call status values. Enumeration value Description CallInitial The call is being established CallConnected The call is active CallTerminated The call was terminated ETSI ETSI ES 202 391-2 V1.3.1 (2008-05) 9 7.2 CallTermination
39、Cause enumeration List of call termination cause values. Enumeration value Description CallingPartyNoAnswer Calling Party did not answer CalledPartyNoAnswer Called Party did not answer CallingPartyBusy Calling Party was busy CalledPartyBusy Called Party was busy CallingPartyNotReachable Calling Part
40、y was not reachable CalledPartyNotReachable Called Party was not reachable CallHangUp The call was terminated by either party hanging up CallAborted The call was aborted (any other termination cause) 7.3 CallInformation Structure Call information for this call. Element name Element type Optional Des
41、cription callStatus CallStatus No It indicates the current status of the call (see possible values below) startTime xsd:dateTime Yes When applicable (callStatus CallInitial), it indicates the time of the beginning of the call duration xsd:int Yes When applicable (callStatus = CallTerminated), it ind
42、icates the duration of the call expressed in seconds terminationCause CallTerminationCause Yes When applicable (callStatus = CallTerminated), it indicates the cause of the termination of the call 8 Web Service interface definition 8.1 Interface: ThirdPartyCall This interface provides the ability to
43、setup, end and determine the status of a call. 8.1.1 Operation: makeCall The invocation of makeCall requests to set-up a voice call between two addresses, callingParty and calledParty, provided that the invoking application is allowed to connect them. Optionally the application can also indicate the
44、 charging information (charging). By invoking this operation the application may monitor the status of the requested call. The returned parameter, callIdentifier, can be used to identify the call. In order to receive the information on call status the application has to explicitly invoke getCallInfo
45、rmation. 8.1.1.1 Input message: makeCallRequest Part name Part type Optional Description callingParty xsd:anyURI No It contains the address of the first user involved in the call calledParty xsd:anyURI No It contains the address of the second user involved in the call charging common:ChargingInforma
46、tion Yes Charge to apply to the call ETSI ETSI ES 202 391-2 V1.3.1 (2008-05) 108.1.1.2 Output message : makeCallResponse Part name Part type Optional Description result xsd:string No It identifies a specific call request 8.1.1.3 Referenced faults ServiceException from ES 202 391-1 2: SVC0001 - Servi
47、ce error. SVC0002 - Invalid input value. PolicyException from ES 202 391-1 2: POL0001 - Policy error. POL0008 - Charging not supported. 8.1.2 Operation: getCallInformation The invocation of getCallInformation retrieves the current status, callInformation, of the call identified by CallIdentifier. Th
48、is method can be invoked multiple times by the application even if the call has already ended. However, after the call has ended, status information will be available only for a limited period of time that is specified in the service policy “StatusRetentionTime“. 8.1.2.1 Input message: getCallInform
49、ationRequest Part name Part type Optional Description callIdentifier xsd:string No It identifies a specific call request 8.1.2.2 Output message : getCallInformationResponse Part name Part type Optional Description result CallInformation No It identifies the status of the call 8.1.2.3 Referenced faults ServiceException from ES 202 391-1 2: SVC0001 - Service error. SVC0002 - Invalid input value. PolicyException from ES 202 391-1 2: POL0001 - Policy error. 8.1.3 Operation: endCall The invocation of endCall terminates the
