1、 ETSI TS 129 199-12 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 12: Multimedia conference (3GPP TS 29.199-12 version 9.0.0 Release 9)floppy3ETS
2、I ETSI TS 129 199-12 V9.0.0 (2010-01)13GPP TS 29.199-12 version 9.0.0 Release 9Reference RTS/TSGC-0029199-12v900 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 Associatio
3、n 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 made available in more than one electronic version or in print. In any case of existing or percei
4、ved 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 kept on a specific network drive within ETSI Secretariat. Users of the present document should be
5、 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 you find errors in the present document, please send your comment to one of the following services
6、: 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 reproduction in all media. European Telecommunications Standards Institute 2010. All rights reserved. D
7、ECTTM, 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 for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being reg
8、istered 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-12 V9.0.0 (2010-01)23GPP TS 29.199-12 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potential
9、ly 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 Property Rights (IPRs); Essential, or potentially Essential, IPR
10、s 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, including IPR searches, has been carried out by ETSI. No guaran
11、tee 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 Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project
12、 (3GPP). 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 b
13、e found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 199-12 V9.0.0 (2010-01)33GPP TS 29.199-12 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definition
14、s 7g33.2 Abbreviations . 7g34 Detailed service description . 8g35 Namespaces 9g36 Sequence diagrams . 10g36.1 Setting up a conference 10g36.2 Void 11g36.3 Conference owner disconnects . 11g36.4 All participants disconnect . 12g36.5 Conference ended by application . 13g37 XML Schema data type definit
15、ion . 14g37.1 ConferenceStatus enumeration . 14g37.2 ConferenceInfo structure 14g37.3 ParticipantInfo structure . 14g37.4 ParticipantStatus enumeration 14g37.5 Void 14g37.6 Void 14g37.7 Void 14g38 Web Service interface definition 15g38.1 Interface: MultimediaConference . 15g38.1.1 Operation: createC
16、onference 15g38.1.1.1 Input message: createConferenceRequest . 15g38.1.1.2 Output message: createConferenceResponse 15g38.1.1.3 Referenced faults . 16g38.1.2 Operation: getConferenceInfo 17g38.1.2.1 Input message: getConferenceInfoRequest . 17g38.1.2.2 Output message: getConferenceInfoResponse 17g38
17、.1.2.3 Referenced faults . 17g38.1.3 Operation: endConference 17g38.1.3.1 Input message: endConferenceRequest . 17g38.1.3.2 Output message: endConferenceResponse 17g38.1.3.3 Referenced faults . 17g38.1.4 Operation: inviteParticipant 18g38.1.4.1 Input message: inviteParticipantRequest . 18g38.1.4.2 O
18、utput message: inviteParticipantResponse . 18g38.1.4.3 Referenced faults . 18g38.1.5 Operation: disconnectParticipant 19g38.1.5.1 Input message: disconnectParticipantRequest . 19g38.1.5.2 Output message: disconnectParticipantResponse 19g38.1.5.3 Referenced faults . 19g38.1.6 Operation: getParticipan
19、tInfo 19g38.1.6.1 Input message: getParticipantInfoRequest 19g38.1.6.2 Output message: getParticipantInfoResponse . 19g3ETSI ETSI TS 129 199-12 V9.0.0 (2010-01)43GPP TS 29.199-12 version 9.0.0 Release 98.1.6.3 Referenced faults . 19g38.1.7 Operation: getParticipants . 20g38.1.7.1 Input message: getP
20、articipantsRequest . 20g38.1.7.2 Output message: getParticipantsResponse 20g38.1.7.3 Referenced faults . 20g38.1.8 Void 20g38.1.9 Void 20g39 Fault definitions 21g39.1 PolicyException . 21g39.1.1 POL0240: Too many participants . 21g39.1.2 Void 21g39.1.3 POL0242: Maximum duration exceeded 21g39.2 Serv
21、iceException 21g39.2.1 Void 21g39.2.2 Void 21g310 Service policies 21g3Annex A (normative): WSDL for Multimedia conference . 22g3Annex B (informative): Description of Parlay X Web Services Part 12: Multimedia conference for 3GPP2 cdma2000 networks . 23g3B.1 General Exceptions. 23g3B.2 Specific Excep
22、tions 23g3B.2.1 Clause 1: Scope 23g3B.2.2 Clause 2: References 23g3B.2.3 Clause 3: Definitions and abbreviations . 23g3B.2.4 Clause 4: Detailed service description 23g3B.2.5 Clause 5: Namespaces 23g3B.2.6 Clause 6: Sequence diagrams . 24g3B.2.7 Clause 7: XML Schema data type definition 24g3B.2.8 Cla
23、use 8: Web Service interface definition 24g3B.2.9 Clause 9: Fault definitions 24g3B.2.10 Clause 10: Service policies . 24g3B.2.11 Annex A (normative):WSDL for Multimedia conference 24g3Annex C (informative): Change history . 25g3History 26g3ETSI ETSI TS 129 199-12 V9.0.0 (2010-01)53GPP TS 29.199-12
24、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 3GPP acknowledge and publish the pr
25、esent 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. Should the TSG modify the content
26、s 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 greater indicates TSG approved docum
27、ent 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 present document is part 12 of a mul
28、ti-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“ Part 4: “Short Messaging“ Part
29、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 15: “Message Broadcast“ Part 16:
30、“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 129 199-12 V9.0.0 (2010-01)63GPP
31、 TS 29.199-12 version 9.0.0 Release 91 Scope The present document is Part 12 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 functionality through an open standa
32、rdized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 3. The requirements for OSA are contained in 3GPP TS 22.127 2. The present document specifies the Multimedia Conference Web Service aspects of the interface. All aspects of t
33、he Multimedia Conference 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 defined jointly betw
34、een 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present doc
35、ument. References are either specific (identified by date of publication, edition number, 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 (inclu
36、ding a GSM document), a non-specific reference implicitly refers to the latest version of 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
37、23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TS 22.101: “Service aspects; Service principles“. 5 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 6 3GPP TS 29.199-1: “Open Service Access (OSA); Parlay X We
38、b Services; Part 1: Common“. ETSI ETSI TS 129 199-12 V9.0.0 (2010-01)73GPP TS 29.199-12 version 9.0.0 Release 93 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. 3.2 Abbreviations For the purposes of
39、the present document, the abbreviations given in 3GPP TS 29.199-1 6 apply. ETSI ETSI TS 129 199-12 V9.0.0 (2010-01)83GPP TS 29.199-12 version 9.0.0 Release 94 Detailed service description The Multimedia Conferencing is a simple Web Service that allows the creation of a multimedia conference and the
40、dynamic management of the participants involved. The underlying model of the service is based on the following entities: Conference: a “context“ (uniquely identified) to which participants can be added/removed. Participant: each of the parties involved in the conference. There may exist a participan
41、t that is also the “owner“ of the conference, i.e. the user who can end the call and/or be the reference user for billing purposes. Media: the conference can utilize multiple media streams to support the participants communication. In particular both audio and video streams are available, including
42、the specific stream direction (i.e. in, out, bidirectional). NOTE: 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 participants in the c
43、all session (playXXXMessage operation) and furthermore control of the media streams for the call participants thus enabling conversational multimedia communication including voice, video, chat, and data. Media can be added/removed for participants using the operations addMediaForParticipants and del
44、eteMediaForParticipants in Audio Call An application setting up a multimedia conference must initially invoke the createConference operation. The result of such invocation is the creation of a “context“ that represents a “virtual“ room where users can “meet“. A unique identifier, a callSessionIdenti
45、fier is assigned to the just-created conference. At this stage no participant is connected yet. Subsequently the application may wish to add participants to the conference. In order to do so the operation inviteParticipant can be used. The result of such operation is to alert the user of the incomin
46、g connection request (e.g. the users terminal rings). If the application wishes to check whether the user has accepted the invitation (i.e. is connected) it can invoke (at a later time) the getParticipantInfo operation. Note that: As soon as the first participant connects, the conference becomes “ac
47、tive“. The duration of the conference is then measured starting from the moment the conference has became active. The initial media set utilized by the participant will depend on the conference type and the media actually supported by the participants terminal. During the conference session the appl
48、ication is able to: Add (or remove) a specific media stream to a single participant: e.g. adding a video bidirectional stream to a participant that has an audio connection to the conference. This can be obtained by invoking the media control (addMediaForParticipants and the deleteMediaForParticipant
49、s) operations of the Audio Call web service. Disconnect a participant from the conference, by invoking the disconnectParticipant operation. Retrieve information related to the conference and its status, by invoking getConferenceInfo and getParticipants. There are different conditions that can determine the end of the conference: 1) The application may invoke the operation endConference, that “forces“ the termination of the conference and the disconnection of all participants. 2) The owner of the conference (if define
