ETSI TS 129 198-4-5 V9.0.0 (2010-01)

Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Open Service Access (OSA) Application Programming Interface (API); Part 4: Call control; Subpart 5: Conference call control Service Capability Feature (SCF) (3GPP TS 29.198-04-5 version 9.0.0 Release 9)

RTS/TSGC-0029198-04-5v900

General Information

• Status: Published
• Publication Date: 25-Jan-2010
• Technical Committee: 3GPP CT - Technical Specification Group Core Network and Terminals
• Current Stage: 12 - Completion
• Due Date: 05-Jan-2010
• Completion Date: 26-Jan-2010

Standards Content (Sample)

ETSI TS 129 198-4-5 V9.0.0 (2010-01)
Technical Specification

Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
LTE;
Open Service Access (OSA)
Application Programming Interface (API);
Part 4: Call control;
Subpart 5: Conference call control
Service Capability Feature (SCF)
(3GPP TS 29.198-04-5 version 9.0.0 Release 9)




�

---------------------- Page: 1 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 1 ETSI TS 129 198-4-5 V9.0.0 (2010-01)



Reference
RTS/TSGC-0029198-04-5v900
Keywords
GSM, LTE, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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 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:
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.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP 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
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

---------------------- Page: 2 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 2 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
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 found
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 the 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.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (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 be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI

---------------------- Page: 3 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 3 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Foreword . 5
Introduction . 5
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Conference call control Service Sequence Diagrams . 8
4.1 Meet-me conference without subconferencing . 8
4.2 Non-add hoc add-on with subconferencing . 11
4.3 Non-addhoc add-on multimedia . 13
4.4 Resource Reservation . 15
5 Class Diagrams . 16
6 Conference call control Service Interface Classes . 18
6.1 Interface Class IpConfCallControlManager . 19
6.1.1 Method createConference() . 19
6.1.2 Method checkResources() . 20
6.1.3 Method reserveResources() . 20
6.1.4 Method freeResources() . 21
6.2 Interface Class IpAppConfCallControlManager . 22
6.2.1 Method conferenceCreated() . 22
6.3 Interface Class IpConfCall . 22
6.3.1 Method getSubConferences() . 23
6.3.2 Method createSubConference() . 23
6.3.3 Method leaveMonitorReq() . 24
6.3.4 Method getConferenceAddress() . 24
6.4 Interface Class IpAppConfCall . 25
6.4.1 Method partyJoined() . 25
6.4.2 Method leaveMonitorRes() . 25
6.5 Interface Class IpSubConfCall . 26
6.5.1 Method splitSubConference() . 27
6.5.2 Method mergeSubConference() . 27
6.5.3 Method moveCallLeg() . 27
6.5.4 Method inspectVideo() . 28
6.5.5 Method inspectVideoCancel() . 28
6.5.6 Method appointSpeaker() . 28
6.5.7 Method chairSelection() . 29
6.5.8 Method changeConferencePolicy(). 29
6.6 Interface Class IpAppSubConfCall . 30
6.6.1 Method chairSelection() . 30
6.6.2 Method floorRequest() . 30
7 Conference call control Service State Transition Diagrams . 31
8 Conference call control Data Definitions . 31
8.1 Event Notification Data Definitions . 31
8.2 Conference call control Data Definitions . 31
8.2.1 IpConfCall . 31
8.2.2 IpConfCallRef . 31
8.2.3 IpAppConfCall . 31
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 4 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
8.2.4 IpAppConfCallRef . 31
8.2.5 IpSubConfCall . 32
8.2.6 IpSubConfCallRef . 32
8.2.7 IpAppSubConfCall . 32
8.2.8 IpAppSubConfCallRef. 32
8.2.9 TpSubConfCallIdentifierSet . 32
8.2.10 TpConfCallIdentifier . 32
8.2.11 TpSubConfCallIdentifier . 32
8.2.12 IpAppConfCallControlManager . 32
8.2.13 IpAppConfCallControlManagerRef . 32
8.2.14 TpConfPolicyType. 32
8.2.15 TpConfPolicy . 33
8.2.16 TpMonoMediaConfPolicy . 33
8.2.17 TpJoinEventInfo . 33
8.2.18 TpConfSearchCriteria . 33
8.2.19 TpConfSearchResult . 34
8.2.20 TpMultiMediaConfPolicy . 34
8.2.21 TpResourceReservation . 34
8.2.22 TpVideoHandlingType . 34
Annex A (normative): OMG IDL Description of Conference call control SCF . 35
Annex B (informative): W3C WSDL Description of Conference call control SCF. 36
Annex C (informative): Java™ API Description of the Call Control SCFs . 37
Annex D (informative): Description of Call Control Sub-part 5: Conference call control SCF
for 3GPP2 cdma2000 networks . 38
D.1 General Exceptions. 38
D.2 Specific Exceptions . 38
D.2.1 Clause 1: Scope . 38
D.2.2 Clause 2: References . 38
D.2.3 Clause 3: Definitions and abbreviations . 38
D.2.4 Clause 4: Conference call control Service Sequence Diagrams . 38
D.2.5 Clause 5: Class Diagrams . 38
D.2.6 Clause 6: Conference call control Service Interface Classes . 39
D.2.7 Clause 7: Conference call control Service State Transition Diagrams . 39
D.2.8 Clause 8: Conference call control Data Definitions . 39
D.2.9 Clause 9: Multi-Party Call Control Data Definitions . 39
D.2.10 Annex A (normative): OMG IDL Description of Conference call control SCF. 39
D.2.11 Annex B (informative): W3C WSDL Description of Conference call control SCF . 39
D.2.12 Annex C (informative): Java™ API Description of the Call Control SCFs . 39
Annex E (informative): Change history . 40
History . 41

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 5 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
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 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 greater 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
rd
The present document is part 4, sub-part 5 of a multi-part TS covering the 3 Generation Partnership Project: Technical
Specification Group Core Network and Terminals; Open Service Access (OSA); Application Programming Interface
(API), as identified below. The API specification (3GPP TS 29.198) is structured in the following Parts:
Part 1: "Overview";
Part 2: "Common data definitions";
Part 3: "Framework";
Part 4: "Call control";
Sub-part 1: "Call control common definitions";
Sub-part 2: "Generic call control SCF";
Sub-part 3: "Multi-party call control SCF";
Sub-part 4: "Multimedia call control SCF";
Sub-part 5: "Conference call control SCF";
Part 5: "User Interaction SCF";
Part 6: "Mobility SCF";
Part 7: "Terminal capabilities SCF";
Part 8: "Data session control SCF";
Part 9: "Generic Messaging SCF"; (not part of 3GPP Release 8)
Part 10: "Connectivity Manager SCF"; (new in 3GPP Release 8)
Part 11: "Account management SCF";
Part 12: "Charging SCF".
Part 13: "Policy management SCF";
Part 14: "Presence and Availability Management (PAM) SCF";
Part 15: "Multi-media Messaging (MM) SCF";
Part 16: "Service broker SCF".

The Mapping specification of the OSA APIs and network protocols (3GPP TR 29.998) is also structured as above.
A mapping to network protocols is however not applicable for all Parts, but the numbering of Parts is kept.
Also in case a Part is not supported in a Release, the numbering of the parts is maintained.
ETSI

---------------------- Page: 6 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 6 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
Table: Overview of the OSA APIs & Protocol Mappings 29.198 & 29.998-family
OSA API specifications 29.198-family OSA API Mapping - 29.998-family
29.198-01 Overview 29.998-01 Overview
29.198-02 Common Data Definitions 29.998-02 Not Applicable
29.198-03 Framework 29.998-03 Not Applicable
Call 29.198-04-1 29.198- 29.198- 29.198- 29.198- 29.998-04-1 Generic Call Control – CAP mapping
Control Common 04-2 04-3 04-4
04-5 29.998-04-2 Generic Call Control – INAP mapping
(CC) CC data Generic Multi- Multi- Conf.
29.998-04-3 Generic Call Control – Megaco
SCF definitions CC SCF Party CC media CC
mapping
SCF CC SCF
SCF
29.998-04-4 Multiparty Call Control – ISC mapping
29.198-05 User Interaction SCF 29.998-05-1 User Interaction – CAP mapping
29.998-05-2 User Interaction – INAP mapping
29.998-05-3 User Interaction – Megaco mapping
29.998-05-4 User Interaction – SMS mapping
29.198-06 Mobility SCF 29.998-06-1 User Status and User Location – MAP
mapping
29.998-06-2 User Status and User Location – SIP
mapping
29.198-07 Terminal Capabilities SCF 29.998-07 Not Applicable
29.198-08 Data Session Control SCF 29.998-08 Data Session Control – CAP mapping
29.198-09 Generic Messaging SCF 29.998-09 Not Applicable
29.198-10 Connectivity Manager SCF 29.998-10 Not Applicable
29.198-11 Account Management SCF 29.998-11 Not Applicable
29.198-12 Charging SCF 29.998-12 Not Applicable
29.198-13 Policy Management SCF 29.998-13 Not Applicable
29.198-14 Presence & Availability Management SCF 29.998-14 Not Applicable
29.198-15 Multi Media Messaging SCF 29.998-15 Not Applicable
29.198-16 Service Broker SCF 29.998-16 Not Applicable

ETSI

---------------------- Page: 7 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 7 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
1 Scope
The present document is Part 4, Sub-Part 5 of the Stage 3 specification for an Application Programming Interface (API)
for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardised 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 Conference call control Service Capability Feature (SCF) aspects of the interface.
All aspects of the Conference call control SCF are defined here, these being:
• Sequence Diagrams
• Class Diagrams
• Interface specification plus detailed method descriptions
• State Transition diagrams
• Data definitions
• IDL Description of the interfaces
• WSDL Description of the interfaces
• Reference to the Java™ API description of the interfaces
The process by which this task is accomplished is through the use of object modelling techniques described by the
Unified Modelling Language (UML).
This specification has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Group, in co-
operation with a number of JAIN™ Community member companies.
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
document.
• 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 (including
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 TS 29.198-01: "Open Service Access (OSA) Application Programming Interface (API);
Part 1: Overview".
[2] 3GPP TS 22.127: "Service Requirement for the Open Services Access (OSA); Stage 1".
[3] 3GPP TS 23.198: "Open Service Access (OSA); Stage 2".
[4] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network
(PLMN)".
[5] ISO 4217 (1995): "Codes for the representation of currencies and funds ".
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 8 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
[6] 3GPP TS 24.002: "GSM-UMTS Public Land Mobile Network (PLMN) Access Reference
Configuration".
[7] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[8] ITU-T Q.763: "Signalling System No. 7 - ISDN user part formats and codes".
[9] ANSI T1.113: "Signalling System No. 7 (SS7) - Integrated Services Digital Network (ISDN) User
Part".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TS 29.198-1 [1] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TS 29.198-1 [1] apply.
4 Conference call control Service Sequence Diagrams
4.1 Meet-me conference without subconferencing
This sequence illustrates a pre-arranged meet-me conference for a specified time period. During this timeslot parties can
'call in to' the meet-me conference by dialling a special number.
For each participant joining the conference, the application can decide to accept the participant in to the conference.
The application can also be notified when parties are leaving the conference.
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 9 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
: (Logical : : : : IpConfCall
View::IpAppLogic) IpAppConfCallControlManager IpAppConfCall IpConfCallControlManager
1: new()
2: reserveResources(   )
3: conferenceCreated( )
4: "forward event"
5: new()
6: leaveMonitorReq( )
7: partyJoined(  )
8: attachMediaReq( )
9: partyJoined(  )
10: "forward event"
11: attachMediaReq( )
12: leaveMonitorRes( )
13: "forward event"
14: release( )

1: The application creates a new object to receive the callbacks from the conference call control manager.
2: The application reserves resources for some time in the future.
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 10 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
With this same method the application registers interest in the creation of the conference (e.g. when the first party to
joins the conference or at the specified start time, this is implementation dependant).
The reservation also includes the conference policy. One of the elements is whether joined parties must be explicitly
attached. If so, this is treated as an implicit joinMonitorReq.
3: The conference is created.
4: The message is forwarded to the application.
5: The application creates an object to receive the call back messages from the conference call.
6: The application also requests to be notified when parties leave the conference.
7: The application is notified of the first party that joined the conference.
8: When the party is allowed to join the conference, the party is added.
Alternatively, the party could have been rejected with a releaseCallLeg.
9: A new party joins the conference and the application is notified.
10: The message is forwarded to the application.
11: This party also is allowed into the conference by attaching the leg.
12: A party leaves the conference.
13: The message is forwarded to the application.
14: The application decides to release the entire conference.

ETSI

---------------------- Page: 11 ----------------------
3GPP TS 29.198-04-5 version 9.0.0 Release 9 11 ETSI TS 129 198-4-5 V9.0.0 (2010-01)
4.2 Non-add hoc add-on with subconferencing
This sequence illustrates a prearranged add-on conference. The end user that initiates the call, communicates with the
conference application via a web interface (not shown). By dragging and dropping names from the addressbook, the
end-user adds parties to the conference.
Also via the web-interface, the end-user can group parties in subconferences. Only parties in the same subconference
can talk to each other.
: (Logical : : IpAppCallLeg : : IpConfCall first : : IpCallLeg second :
View::IpAppLogic) IpAppConfCall IpConfCallControlManager IpSubConfCall IpSubConfCall
1: new()
2: createConference(   )
3: getSubConferences( )
4: new()
5: createAndRouteCallLegReq(   )
6: new()
7: createAndRouteCallLegReq(   )
8: createAndRouteCallLegReq(   )
9: createAndRouteCallLegReq(   )
10: eventReportRes( )
11: "forward event"
12: splitSubConference(  )
13: moveCallLeg(  )
14: release( )

1: The application creates a new interface to receive the callbacks from the conference call.
2: The application initiates the conference. There has been no prior resource reservation, so there is a chance that no
resources are available when parties are added to the conference.
The conferenceCall interface object is returned.
3: Together with the conference a subconference is implicitly created.
However, the subconference is not returned as a result of the createConference, therefore the applicatio
...