1、 ETSI ES 202 504-2 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 2: Third Party Call(Parlay X 3)floppy3 ETSI ETSI ES 202 504-2 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01034-2-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cede
2、x - 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 documen
3、t 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 PDF
4、 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/status
5、.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 r
7、egistered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 504-2 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 2.1 Normative references .6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4
8、 Detailed service description .7 5 Namespaces8 6 Sequence diagrams.8 6.1 Click to Dial call setup8 7 XML Schema data type definition .9 8 Web Service interface definition9 8.1 Interface: ThirdPartyCall9 8.1.1 Operation: makeCallSession.10 8.1.1.1 Input message: makeCallSessionRequest .10 8.1.1.2 Out
9、put message: makeCallSessionResponse 10 8.1.1.3 Referenced faults.10 8.1.1a Operation: addCallParticipant.11 8.1.1a.1 Input message: addCallParticipantRequest .11 8.1.1a.2 Output message: addCallParticipantResponse 11 8.1.1a.3 Referenced faults.11 8.1.1b Operation: transferCallParticipant 11 8.1.1b.
10、1 Input message: transferCallParticipantRequest.12 8.1.1b.2 Output message: transferCallParticipantResponse12 8.1.1b.3 Referenced faults.12 8.1.2 Operation: getCallParticipantInformation.12 8.1.2.1 Input message: getCallParticipantInformationRequest .13 8.1.2.2 Output message: getCallParticipantInfo
11、rmationResponse 13 8.1.2.3 Referenced faults.13 8.1.3 Void 13 8.1.4 Void 13 8.1.5 Operation: getCallSessionInformation13 8.1.5.1 Input message: getCallSessionInformationRequest 13 8.1.5.2 Output message: getCallSessionInformationResponse .13 8.1.5.3 Referenced faults.13 8.1.6 Operation: deleteCallPa
12、rticipant.14 8.1.6.1 Input message: deleteCallParticipantRequest14 8.1.6.2 Output message: deleteCallParticipantResponse 14 8.1.6.3 Referenced faults.14 8.1.7 Operation: endCallSession14 8.1.7.1 Input message: endCallSessionRequest 14 8.1.7.2 Output message: endCallSessionResponse .15 8.1.7.3 Refere
13、nced faults.15 9 Fault definitions15 9.1 ServiceException15 9.1.1 SVC0260: Void 15 9.1.2 SVC0261: Call session already terminated.15 10 Service policies 15 ETSI ETSI ES 202 504-2 V1.1.1 (2008-05) 4 Annex A (normative): WSDL for Third Party Call16 Annex B (informative): Bibliography.17 History 18 ETS
14、I ETSI ES 202 504-2 V1.1.1 (2008-05) 5 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
15、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 available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETS
16、I 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 Web server) which are, or may be, or may become, essential to the present document. Foreword
17、 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 2 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 Web Services, as identif
18、ied 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 Handling“; Part 11: “Audio Call“; P
19、art 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 Streaming Control“; Part 20: “M
20、ultimedia Multicast Session Management“. The present document is equivalent to 3GPP TS 29.199-02 V7.4.0 (Release 7). ETSI ETSI ES 202 504-2 V1.1.1 (2008-05) 6 1 Scope The present document is part 2 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA). The OSA specificat
21、ions define an architecture that enables application developers to make use of network functionality 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 defini
22、tions. Interface specification plus detailed method descriptions. Fault definitions. Service Policies. 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
23、, subsequent revisions do not apply. Non-specific reference may be made only to a complete document 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 i
24、nformative 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 primary so
25、urce 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, with
26、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 applicatio
27、n 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 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/20
28、01/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 504-2 V1.1.1 (2008-05) 7 2 ETSI ES 202 504-1: “TISPAN; Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 3)“. 3 ETSI ES 202 504-12: “TISPAN; Open Service Access (OSA); Parlay X Web Services; Part 12: Multimedia Conference (Parla
29、y X 3)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 202 504-1 2 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ES 202 504-1 2 apply. 4 Detailed service description Curr
30、ently, 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 call from applications). This approach requires a high degree of net
31、work 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. Developers must have advanced telecommunication skills to use Call Control
32、OSA interfaces. In this clause we describe a Parlay X 3 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 application developers to create a call in a simple way. Using the
33、Third Party Call Web Service, application developers can invoke call handling functions without detailed telecommunication knowledge. The underlying model of the service is based on the following entities: Call Session: a call (uniquely identified) to which participants can be added/removed. Call Pa
34、rticipant: each of the call parties (uniquely identified) involved in the call session. Media: the call can utilize multiple media types to support the participants communication. In particular both audio and video streams are available, including the specific stream direction (i.e. incoming, outgoi
35、ng, bidirectional). NOTE 1: Call participants in a Call Session are anticipated to be uniquely identifiable using their URI address. An application setting up a call session must initially invoke the makeCallSession. The result of such invocation is the creation of a “context“ that represents a call
36、 session with usually two participants, or at a minimum one participant connected; a unique identifier is assigned to the just-created call session. Subsequently the application may wish to add, remove, park or transfer call participants. In order to do so the operations addCallParticipant, transfer
37、CallParticipant, deleteCallParticipant can be used. Furthermore the call session or call participant status including the media details can be read. In order to do so the operations getCallParticipantInformation, and getCallSessionInformation can be used. It is also possible to retrieve only the med
38、ia details using the getMediaForParticipant or getMediaForCall operations of the Audio Call web service. The application can also force the call session and all its participants to be terminated with the operation endCallSession. ETSI ETSI ES 202 504-2 V1.1.1 (2008-05) 8 NOTE 2: A call session allow
39、s the application to avail of other web service features that can add value to the created call session. For example the Audio Call web service can provide multimedia message delivery to call participants in the call session (playXxxMessage operations) and furthermore control of the media types for
40、the call participants thus enabling conversational multimedia communication including voice, video, chat, and data. Media can be added/removed for each participant. Figure 1 shows a scenario using the Third Party Call Web Service to handle third party call functions. The application invokes a Web Se
41、rvice to retrieve stock quotes and a Parlay X 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 between one or more brokers and their co
42、rresponding 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 message (5) to an MSC to set-up a call betw
43、een 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. 3PC-XcomponentThird PartyCall WebServiceParlay X I/FParlay GatewayMSCMSCSCS-CCSCS-CCP
44、arlay APIMobile networkStock QuotesWeb ServiceStock QuotesWeb ServicegetStockQuote()Retrieveuser Profile ( userA,userB).makeACall (userA,userB,)Userprofile12345UserA(broker)UserB(customer)Figure 1: Third party call scenario 5 Namespaces The ThirdPartyCall interface uses the namespace: http:/www.csap
45、i.org/wsdl/parlayx/third_party_call/v3_4 The xsd namespace is used in the present document to refer to the XML Schema 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 Clic
46、k to Dial, where a self service portal provides a web page that can initiate a call between two phones. This sequence shows a basic call setup, and ending the call through the portal. ETSI ETSI ES 202 504-2 V1.1.1 (2008-05) 9 : End User : Self Serve Portal : Third Party Call Web Service Access porta
47、l Use Click to Dial page Make call session Call session identifier Report call in progress Some discussion Click on end call End call session Figure 2 7 XML Schema data type definition None. 8 Web Service interface definition 8.1 Interface: ThirdPartyCall This interface provides the ability to setup
48、 a call session, add and delete a call participant, transfer a call participant from one call session into another call session, determine the status of an individual call participant or a complete call session, and finally to end a call session. ETSI ETSI ES 202 504-2 V1.1.1 (2008-05) 108.1.1 Opera
49、tion: makeCallSession The invocation of makeCallSession requests to set-up a call session between two addresses, a first callParticipant (“A-Party“) and a second callParticipant (“B-Party“), provided that the invoking application is allowed to connect them. Optionally, the callers (“A-Partys“) name is provided. Optionally a call session with only a single callParticipant (“A-party“) can be set-up, for example to play media to the call participant using Audio Call web service capabilities (e.g. PlayMedia interface). Optiona
