1、 ETSI ES 202 504-12 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 12: Multimedia Conference(Parlay X 3)floppy3 ETSI ETSI ES 202 504-12 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01034-12-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antip
2、olis 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 presen
3、t 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 printers o
4、f 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/stat
5、us/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 restrictio
6、n extend 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
7、of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 504-12 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 7 2 References 7 2.1 Normative references .7 3 Definitions and abbreviations.8 3.1 Definitions8 3.2 Abbrevia
8、tions .8 4 Detailed service description .8 5 Namespaces9 6 Sequence diagrams.9 6.1 Setting up a conference 9 6.2 Void11 6.3 Conference owner disconnects .11 6.4 All participants disconnect .12 6.5 Conference ended by application .13 7 XML Schema data type definition .14 7.1 ConferenceStatus enumerat
9、ion.14 7.2 ConferenceInfo structure14 7.3 ParticipantInfo structure .14 7.4 ParticipantStatus enumeration14 7.5 Void14 7.6 Void14 7.7 Void14 8 Web Service interface definition15 8.1 Interface: MultimediaConference.15 8.1.1 Operation: createConference 15 8.1.1.1 Input message: createConferenceRequest
10、 .15 8.1.1.2 Output message: createConferenceResponse15 8.1.1.3 Referenced faults.16 8.1.2 Operation: getConferenceInfo 16 8.1.2.1 Input message: getConferenceInfoRequest .16 8.1.2.2 Output message: getConferenceInfoResponse16 8.1.2.3 Referenced faults.16 8.1.3 Operation: endConference 16 8.1.3.1 In
11、put message: endConferenceRequest.16 8.1.3.2 Output message: endConferenceResponse17 8.1.3.3 Referenced faults.17 8.1.4 Operation: inviteParticipant17 8.1.4.1 Input message: inviteParticipantRequest.17 8.1.4.2 Output message: inviteParticipantResponse .17 8.1.4.3 Referenced faults.17 8.1.5 Operation
12、: disconnectParticipant 17 8.1.5.1 Input message: disconnectParticipantRequest.18 8.1.5.2 Output message: disconnectParticipantResponse18 8.1.5.3 Referenced faults.18 8.1.6 Operation: getParticipantInfo18 8.1.6.1 Input message: getParticipantInfoRequest 18 8.1.6.2 Output message: getParticipantInfoR
13、esponse .18 8.1.6.3 Referenced faults.18 8.1.7 Operation: getParticipants.18 ETSI ETSI ES 202 504-12 V1.1.1 (2008-05) 4 8.1.7.1 Input message: getParticipantsRequest .19 8.1.7.2 Output message: getParticipantsResponse 19 8.1.7.3 Referenced faults.19 8.1.8 Void 19 8.1.9 Void 19 9 Fault definitions19
14、9.1 PolicyException .19 9.1.1 POL0240: Too many participants.19 9.1.2 Void 19 9.1.3 POL0242: Maximum duration exceeded 19 9.2 ServiceException20 9.2.1 Void 20 9.2.2 Void 20 10 Service policies 20 Annex A (normative): WSDL for Multimedia Conference 21 Annex B (informative): Bibliography.22 History 23
15、 ETSI ETSI ES 202 504-12 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 foun
16、d 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 available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to th
17、e 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 Web server) which are, or may be, or may become, essential to the present document. For
18、eword 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 12 of a multi-part deliverable covering Open Service Access (OSA); Parlay X Web Services, as ide
19、ntified 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
20、“; Part 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
21、: “Multimedia Multicast Session Management“. ETSI ETSI ES 202 504-12 V1.1.1 (2008-05) 6 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 3.0 set of specifications. The present document is
22、 equivalent to 3GPP TS 29.199-12 V7.1.0 (Release 7). ETSI ETSI ES 202 504-12 V1.1.1 (2008-05) 7 1 Scope The present document is part 12 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application developer
23、s to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The present document specifies the Multimedia Conference Web Service. The following are defined here: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method descr
24、iptions. 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, subsequent revisions do not apply. Non-specific referen
25、ce 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 informative references. Referenced documents which are not
26、 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 source of the referenced document should be cited, in order
27、 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 the same punctuation and use of upper case and lower case
28、 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 application of the present document. For dated references, only the
29、 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/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 504-12 V1.
30、1.1 (2008-05) 8 2 ETSI ES 202 504-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay 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
31、of the present document, the abbreviations given in ES 202 504-1 2 apply. 4 Detailed service description The Multimedia Conferencing is a simple Web Service that allows the creation of a multimedia conference and the dynamic management of the participants involved. The underlying model of the servic
32、e 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 participant that is also the “owner“ of the conference, i.e. the user who can end the call an
33、d/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 the specific stream direction (i.e. in, out, bidirectional). NOTE: A call session a
34、llows 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 operation) and furthermore control of the media streams
35、 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 deleteMediaForParticipants in Audio Call. An application setting up a multimedia confe
36、rence 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 callSessionIdentifier, is assigned to the just-created conference. At this stage no participant is
37、connected. 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 an operation is to alert the user of the incoming connection request (e.g. the users terminal rings). If the application wishes to
38、 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 “active“. The duration of the conference is then measured starting from the moment th
39、e 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. ETSI ETSI ES 202 504-12 V1.1.1 (2008-05) 9 During the conference session the application is able to: Add (or remove) a s
40、pecific 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 deleteMediaForParticipants) operations of the Audio Call web ser
41、vice. 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 a
42、pplication 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 defined) leaves the conference. If the owner is not defined this condition will apply when all the participants have left t
43、he conference (disconnected). 3) The conference duration exceeds a maximum value (specified during the conference creation step). 5 Namespaces The Multimedia Conference interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/multimedia_conference/v3_1 The data types are defined in the namespa
44、ce: http:/www.csapi.org/schema/parlayx/multimedia_conference/v3_1 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 The following sequence diagrams illustra
45、te typical scenarios of interaction between an application and the Multimedia Conferencing Web Service. 6.1 Setting up a conference Set up a multimedia conference call. ETSI ETSI ES 202 504-12 V1.1.1 (2008-05) 10: Application Logic: Multimedia Conferencing: User ParticipantscreateConferencegetConfer
46、enceInfoStore conference infoinviteParticipantStore participant infoSend alertingConference status: InitialgetParticipantInfogetConferenceInfoReturn info for participantParticipant status: invitedConference status: InitialParticipant RingingReturn info for conferenceParticipant AnsweringParticipant
47、answerStore participant infogetParticipantInfogetConferenceInfoinviteParticipantParticipant status: ConnectedConference status: ActiveRepeat previous steps to invite and connect many participants to the conferenceFigure 1 ETSI ETSI ES 202 504-12 V1.1.1 (2008-05) 116.2 Void Figure 2: Void 6.3 Confere
48、nce owner disconnects During a conference call, the conference owner disconnects. : Application Logic: Multimedia Conferencing: User ParticipantsCreate conference and invite participants phase (see the related sequence diagram)getParticipantInfoReturn info for participantgetConferenceInfoReturn info
49、 for conferenceMany participants are connected to the conferencegetParticipantInfo( )Return info for participantOwner participant (Party A) disconnectsParty A (Owner) disconnectionConference ending. Disconnect all participants. Update conference infogetParticipantInfogetConferenceInfoReturn info for participantReturn info for conferenceParticipant status (Party A):ConnectedParticipant status (Party n):ConnectedParticipant status (Party A):DisconnectedConference status:TerminatedConference status:ActiveOwner: Party AFigure 3 E
