Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map
Top   in Index   Prev   Next

TS 29.199-12 (CT)
Open Service Access (OSA)
Parlay X web services
Part 12: Multimedia Conference

ToC   3GPP‑Page   ETSI‑search   Help    
V9.0.0 (PDF)  2009/12  27 p.
V8.1.0  2009/10  27 p.
V7.1.1  2007/12  27 p.
V6.6.0  2007/06  30 p.

Rapporteur:  Mr. Unmehopa, Musa
See also:  –

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 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 participant 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 the specific stream direction (i.e. in, out, bidirectional).
  • 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 call 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 deleteMediaForParticipants 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 callSessionIdentifier 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 incoming connection request (e.g. the user's 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 "active". 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 participant's terminal.
During the conference session the application 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 deleteMediaForParticipants) 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:
  • The application may invoke the operation endConference, that "forces" the termination of the conference and the disconnection of all participants.
  • 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 the conference (disconnected).
  • The conference duration exceeds a maximum value (specified during the conference creation step).
This TS specifies the Multimedia Conference Web Service aspects of the interface.


Here   Top



1  ScopePDF-p. 6
2  References
3  Definitions and abbreviationsPDF-p. 7
4  Detailed service descriptionPDF-p. 8
5  NamespacesPDF-p. 9
6  Sequence diagramsPDF-p. 10
7  XML Schema data type definitionPDF-p. 14
8  Web Service interface definitionPDF-p. 15
9  Fault definitionsPDF-p. 21
10  Service policies
A (Normative)  WSDL for Multimedia conferencePDF-p. 22
B  Description of Parlay X Web Services Part 12: Multimedia conference for 3GPP2 cdma2000 networksPDF-p. 23
C  Change historyPDF-p. 25

Up   Top