tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TS 29.198-04-5 (CT)
Open Service Access (OSA) API
Part 4: Call Control
Subpart 5: Conference Call Control Service Capability Feature

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V9.0.0    2009/12    42 p.
(P) V8.0.2    2009/01    42 p.
(P) V7.0.1    2009/01    42 p.


Rapporteur:  Mr. Lundqvist, Thomas
See also:  –


The Conference call control Service enhances the multi-media call control service. The conference call control service gives the application the ability to manipulate subconferences within a conference. A subconference defines the grouping of legs within the overall conference call. Only parties in the same subconference have a bearer connection (or media channel connection) to each other (e.g. can speak to each other). The application can:
  • create new subconferences within the conference, either as an empty subconference or by splitting an existing subconference in two subconferences;
  • move legs between subconferences;
  • merge subconferences;
  • get a list of all subconferences in the call;
The generic conference also gives the possibility to manipulate typical multi-media conference details, such as:
  • interworking with network signalled conference protocols (e.g. H.323);
  • manipulation of the media in the MCU, e.g., broadcasting of video;
  • handling of multi-media conference policies, e.g., how video should be handled, voice controlled switched or chair controlled.
Furthermore the conference call control service adds support for the reservation of resources needed for conferencing. The application can:
  • reserve resources for a predefined time period;
  • free reserved resources;
  • search for the availability of conference resources based on a number of criteria.
There are two ways to initiate a conference:
  • the conferences can be started on the pre-arranged time by the service, at the start time indicated in the reservation. The application is notified about this. The application can then add parties to the conference and/or parties can dial-in to the conference using the address provided during reservation;
  • the conference can be created directly on request of the application using the createConference method in the IpConfCallControlManager interface.
Each Conference call control interface inherits from a Multi Media Call Control interface, which in turn inherits from Multi Party Call Control. It is possible to implement conference call control without any multi-media features, using only those inherited methods which come from Multi Party Call Control, in addition to the Conference call control methods. The minimum required method set for each Conference call control interface reflects this possibility, by not requiring the Multi Media Call Control methods.


 

Here          Top

 

 

1   Scope   PDF-p. 7
2   References
3   Definitions and abbreviations   PDF-p. 8
4   Conference call control Service Sequence Diagrams
5   Class Diagrams   PDF-p. 16      Up
6   Conference call control Service Interface Classes   PDF-p. 18
7   Conference call control Service State Transition Diagrams   PDF-p. 31
8   Conference call control Data Definitions      Up
A  (Normative)   OMG IDL Description of Conference call control SCF   PDF-p. 35
B   W3C WSDL Description of Conference call control SCF   PDF-p. 36
C   Java™ API Description of the Call Control SCFs   PDF-p. 37
D   Description of Call Control Sub-part 5: Conference call control SCF for 3GPP2 cdma2000 networks   PDF-p. 38
E   Change history   PDF-p. 40

Up          Top