1、 ETSI TS 129 199-2 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 2: Third party call (3GPP TS 29.199-02 version 9.0.0 Release 9)floppy3ETSI ETSI
2、TS 129 199-2 V9.0.0 (2010-01)13GPP TS 29.199-02 version 9.0.0 Release 9Reference RTS/TSGC-0029199-02v900 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 no
3、n 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 made available in more than one electronic version or in print. In any case of existing or perceived diff
4、erence 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 kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware t
5、hat 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 you find errors in the present document, please send your comment to one of the following services: http:/
6、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 reproduction in all media. European Telecommunications Standards Institute 2010. All rights reserved. DECTTM, P
7、LUGTESTSTM, 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
8、for the benefit 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-2 V9.0.0 (2010-01)23GPP TS 29.199-02 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentially essent
9、ial 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 Property Rights (IPRs); Essential, or potentially Essential, IPRs notifie
10、d 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, including IPR searches, has been carried out by ETSI. No guarantee can b
11、e 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 Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
12、The present 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 u
13、nder http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 199-2 V9.0.0 (2010-01)33GPP TS 29.199-02 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 A
14、bbreviations . 7g34 Detailed service description . 7g35 Namespaces 9g36 Sequence diagrams . 9g36.1 Click to Dial call setup 9g36.2 Third party call with announcement between broker and customer . 10g37 XML Schema data type definition . 10g38 Web Service interface definition 11g38.1 Interface: ThirdP
15、artyCall 11g38.1.1 Operation: MakeCallSession 11g38.1.1.1 Input message: MakeCallSessionRequest . 11g38.1.1.2 Output message : MakeCallSessionResponse . 12g38.1.1.3 Referenced faults. 12g38.1.1a Operation: AddCallParticipant 12g38.1.1a.1 Input Message : AddCallParticipantRequest . 12g38.1.1a.2 Outpu
16、t message : AddCallParticipantResponse 12g38.1.1a.3 Referenced faults. 12g38.1.1b Operation: TransferCallParticipant . 13g38.1.1b.1 Input Message : TransferCallParticipantRequest 13g38.1.1b.2 Output message : TransferCallParticipantResponse . 13g38.1.1b.3 Referenced faults . 13g38.1.2 Operation: Get
17、CallParticipantInformation 14g38.1.2.1 Input message: GetCallParticipantInformationRequest 14g38.1.2.2 Output message : GetCallParticipantInformationResponse 14g38.1.2.3 Referenced faults . 14g38.1.3 Void 14g38.1.4 Void 14g38.1.5 Operation: GetCallSessionInformation . 14g38.1.5.1 Input message: GetC
18、allSessionInformationRequest . 14g38.1.5.2 Output message : GetCallSessionInformationResponse . 15g38.1.5.3 Referenced faults . 15g38.1.6 Operation: DeleteCallParticipant 15g38.1.6.1 Input message: DeleteCallParticipantRequest . 15g38.1.6.2 Output message: DeleteCallParticipantResponse 15g38.1.6.3 R
19、eferenced faults . 15g38.1.7 Operation: EndCallSession . 16g38.1.7.1 Input message: EndCallSessionRequest 16g38.1.7.2 Output message: EndCallSessionResponse . 16g38.1.7.3 Referenced faults. 16g39 Fault definitions 17g39.1 ServiceException 17g39.1.1 SVC0260: Void 17g3ETSI ETSI TS 129 199-2 V9.0.0 (20
20、10-01)43GPP TS 29.199-02 version 9.0.0 Release 99.1.2 SVC0261: Call Session already terminated 17g310 Service policies 17g3Annex A (normative): WSDL for Third Party Call 18g3Annex B (informative): Description of Parlay X Web Services Part 2: Third party call for 3GPP2 cdma2000 networks 19g3B.1 Gener
21、al Exceptions. 19g3B.2 Specific Exceptions 19g3B.2.1 Clause 1: Scope 19g3B.2.2 Clause 2: References 19g3B.2.3 Clause 3: Definitions and abbreviations . 19g3B.2.4 Clause 4: Detailed service description 19g3B.2.5 Clause 5: Namespaces 19g3B.2.6 Clause 6: Sequence diagrams . 20g3B.2.7 Clause 7: XML Sche
22、ma data type definition 20g3B.2.8 Clause 8: Web Service interface definition 20g3B.2.9 Clause 9: Fault definitions 20g3B.2.10 Clause 10: Service policies . 20g3B.2.11 Annex A (normative):WSDL for Third Party Call . 20g3Annex C (informative): Change history . 21g3History 22g3ETSI ETSI TS 129 199-2 V9
23、.0.0 (2010-01)53GPP TS 29.199-02 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). 3GPP acknowledges the contribution of the Parlay X Web Services specifications from The Parlay Group. The Parlay Group is pleased to see 3G
24、PP 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 document. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval.
25、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 number 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 gre
26、ater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The pre
27、sent document is part 2 of a multi-part deliverable covering the 3rdGeneration Partnership Project; Technical Specification Group Core Network and Terminals; Open Service Access (OSA); Parlay X Web Services, as identified below: Part 1: “Common“ Part 2: “Third party call“ Part 3: “Call Notification“
28、 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“ Part 13: “Address list management“ Part 14: “Presence“ Part 1
29、5: “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: “Multimedia multicast session management“ Part 21: “Content Management“ Part 22: “Policy“ ETSI ETSI TS
30、129 199-2 V9.0.0 (2010-01)63GPP TS 29.199-02 version 9.0.0 Release 91 Scope The present document is Part 2 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers to make use of network functi
31、onality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.127 3. The requirements for OSA are contained in 3GPP TS 22.127 2. The present document specifies the Third Party Call Web Service aspects of the in
32、terface. All aspects of the Third Party Call Web Service are defined here, these being: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method descriptions. Fault definitions. Service Policies. WSDL Description of the interfaces. The present document has been
33、defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number,
34、version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of
35、that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.127: “Service Requirement for the Open Services Access (OSA); Stage 1“. 3 3GPP TS 23.127: “Virtual Home Environment (VHE) / Open Service Access (OSA); Stage 2“. 4 3GPP TS 2
36、2.101: “Service aspects; Service principles“. 5 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 6 3GPP TS 29.199-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common“. 7 3GPP TS 29.199-12: “Open Service Access (OSA)
37、; Parlay X Web Services; Part 12: Multimedia conference. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 29.199-1 6 apply. ETSI ETSI TS 129 199-2 V9.0.0 (2010-01)73GPP TS 29.199-02 version 9.0.0 Release 93.2 Abbrevi
38、ations For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 6 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
39、 provided by network elements (specifically operations to initiate a 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 usuall
40、y perceived to be quite complex by application IT developers. Developers must have advanced telecommunication skills to use Call Control OSA interfaces. In this subclause we describe a Parlay X Web Service, Third Party Call, for creating and managing a call initiated by an application (third party c
41、all). The overall scope of this Web Service is to provide functions to 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. The underlying model of the
42、service is based on the following entities: Call Session: a call (uniquely identified) to which participants can be added/removed. Call Participant: each of the call parties (uniquely identified) involved in the call session. Media: the call can utilize multiple media types to support the participan
43、ts communication. In particular both audio and video streams are available, including the specific stream direction (i.e. incoming, outgoing, bidirectional). NOTE 1: Call participants in a Call Session are anticipated to be uniquely identifiable using their URI address. An application setting up a c
44、all session must initially invoke the makeCallSession. The result of such invocation is the creation of a “context“ that represents a call session with usually two participants, or at a minimum one participant connected, a unique identifier is assigned to the just-created call session. Subsequently
45、the application may wish to add, remove, park or transfer call participants. In order to do so the operations addCallParticipant, transferCallParticipant, deleteCallParticipant can be used. Furthermore the call session or call participant status including the media details can be read. In order to d
46、o so the operations getCallParticipantInformation, and getCallSessionInformation can be used. It is also possible to retrieve the media details on its own using the getMediaForParticipant or getMediaForCall operations of the Audio Call web service. The application can also force the call session and
47、 all its participants to be terminated with the operation endCallSession. NOTE 2: A call session allows 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 partic
48、ipants in the call session (playXXXMessage operation) and furthermore control of the media types for the call participants thus enabling conversational multimedia communication including voice, video, chat, and data. Media can be added/removed for each participant. Figure 4.1 shows a scenario using
49、the Third Party Call Web Service to handle third party call functions. The application invokes a Web Service 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 corresponding customers to decide actions to be taken. After invocation (3) by the application, the Third Party Call Web Service
