ETSI ES 202 915-4-5-2006 Open Service Access (OSA) Application Programming Interface (API) Part 4 Call Control Sub-part 5 Conference Call Control SCF (Parlay 4) (V1 4 1 Includes Di.pdf

1、 ETSI ES 202 915-4-5 V1.4.1 (2006-12)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 4: Call Control;Sub-part 5: Conference Call Control SCF(Parlay 4)floppy3 ETSI ETSI ES 202 915-4-5 V1.4.1 (2006-12) 2 Reference RES/TISPAN-01028-04-05-OSA Keywords API, IDL, OSA,

2、UML 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 Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document c

3、an 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, th

4、e 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 doc

5、uments 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 pe

6、rmission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. The Parlay Group 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand t

7、he TIPHON logo are Trade Marks currently being registered by ETSI 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. ETSI ETSI ES 202 915-4-5 V1.4.1 (2006-12) 3 Contents Intellectual Property Rights5 Forew

8、ord.5 1 Scope 6 2 References 6 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .6 4 Conference Call Control Service Sequence Diagrams.7 4.1 Meet-me conference without subconferencing.7 4.2 Non-add hoc add-on with subconferencing9 4.3 Non-addhoc add-on multimedia .11 4.4 Resource

9、 Reservation.13 5 Class Diagrams.15 6 Conference Call Control Service Interface Classes16 6.1 Interface Class IpConfCallControlManager.17 6.1.1 Method createConference() 17 6.1.2 Method checkResources().18 6.1.3 Method reserveResources() 19 6.1.4 Method freeResources()20 6.2 Interface Class IpAppCon

10、fCallControlManager 20 6.2.1 Method conferenceCreated() 20 6.3 Interface Class IpConfCall .21 6.3.1 Method getSubConferences() .21 6.3.2 Method createSubConference() 22 6.3.3 Method leaveMonitorReq() 22 6.3.4 Method getConferenceAddress() .22 6.4 Interface Class IpAppConfCall 23 6.4.1 Method partyJo

11、ined()23 6.4.2 Method leaveMonitorRes().24 6.5 Interface Class IpSubConfCall .24 6.5.1 Method splitSubConference().25 6.5.2 Method mergeSubConference()25 6.5.3 Method moveCallLeg().26 6.5.4 Method inspectVideo() .26 6.5.5 Method inspectVideoCancel() 26 6.5.6 Method appointSpeaker() .27 6.5.7 Method

12、chairSelection() .27 6.5.8 Method changeConferencePolicy().27 6.6 Interface Class IpAppSubConfCall 28 6.6.1 Method chairSelection() .28 6.6.2 Method floorRequest()28 7 Conference Call Control Service State Transition Diagrams.29 8 Conference Call Control Data Definitions .29 8.1 Event Notification D

13、ata Definitions.29 8.2 Conference Call Control Data Definitions .29 8.2.1 IpConfCall 29 8.2.2 IpConfCallRef.29 8.2.3 IpAppConfCall .29 8.2.4 IpAppConfCallRef29 8.2.5 IpSubConfCall 29 8.2.6 IpSubConfCallRef 30 ETSI ETSI ES 202 915-4-5 V1.4.1 (2006-12) 4 8.2.7 IpAppSubConfCall .30 8.2.8 IpAppSubConfCa

14、llRef30 8.2.9 TpSubConfCallIdentifierSet .30 8.2.10 TpConfCallIdentifier 30 8.2.11 TpSubConfCallIdentifier 30 8.2.12 IpAppConfCallControlManager .30 8.2.13 IpAppConfCallControlManagerRef .30 8.2.14 TpConfPolicyType30 8.2.15 TpConfPolicy31 8.2.16 TpMonoMediaConfPolicy31 8.2.17 TpJoinEventInfo .31 8.2

15、.18 TpConfSearchCriteria.31 8.2.19 TpConfSearchResult.32 8.2.20 TpMultiMediaConfPolicy.32 8.2.21 TpResourceReservation32 8.2.22 TpVideoHandlingType .32 Annex A (normative): OMG IDL Description of Conference Call Control SCF.33 Annex B (informative): W3C WSDL Description of Conference Call Control SC

16、F .34 Annex C (informative): Java API Description of the Call Control SCFs35 Annex D (informative): Contents of 3GPP OSA Rel-5 Call Control .36 Annex E (informative): Record of changes 37 E.1 Interfaces 37 E.1.1 New 37 E.1.2 Deprecated37 E.1.3 Removed.37 E.2 Methods38 E.2.1 New 38 E.2.2 Deprecated38

17、 E.2.3 Modified.38 E.2.4 Removed.38 E.3 Data Definitions .39 E.3.1 New 39 E.3.2 Modified.39 E.3.3 Removed.39 E.4 Service Properties.40 E.4.1 New 40 E.4.2 Deprecated40 E.4.3 Modified.40 E.4.4 Removed.40 E.5 Exceptions 41 E.5.1 New 41 E.5.2 Modified.41 E.5.3 Removed.41 E.6 Others .41 History 42 ETSI E

18、TSI ES 202 915-4-5 V1.4.1 (2006-12) 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 found in E

19、TSI 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

20、 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

21、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 4, sub-part 5 of a multi-part deliverable covering Open Service Access (OSA); Application Programming

22、Interface (API), as identified below. The API specification (ES 202 915) 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“; Su

23、b-part 3: “Multi-Party Call Control SCF“; Sub-part 4: “Multi-Media 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“; Part 10:

24、“Connectivity Manager SCF“; Part 11: “Account Management SCF“; Part 12: “Charging SCF“; Part 13: “Policy Management SCF“; Part 14: “Presence and Availability Management SCF“. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP, in co-opera

25、tion with a number of JAIN Community (http:/ member companies. The present document forms part of the Parlay 4.3 set of specifications. ETSI ETSI ES 202 915-4-5 V1.4.1 (2006-12) 6 1 Scope The present document is part 4, sub-part 5 of the Stage 3 specification for an Application Programming Interface

26、 (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 present document specifies the Conference Call Control Service Capability Featur

27、e (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 Descripti

28、on 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). 2 References The references listed in clause 2 of ES 202 915-1 contain pr

29、ovisions which, through reference in this text, constitute provisions of the present document. ETSI ES 202 915-1: “Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 4)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present documen

30、t, the terms and definitions given in ES 202 915-1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in ES 202 915-1 apply. ETSI ETSI ES 202 915-4-5 V1.4.1 (2006-12) 7 4 Conference Call Control Service Sequence Diagrams 4.1 Meet-me conference without subcon

31、ferencing 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

32、the conference. The application can also be notified when parties are leaving the conference. ETSI ETSI ES 202 915-4-5 V1.4.1 (2006-12) 8 : (Logical View:IpAppLogic): IpAppConfCallControlManager: IpAppConfCall: IpConfCallControlManager: IpConfCall1: new()5: new()2: reserveResources( )6: leaveMonitor

33、Req( )9: partyJoined( )10: “forward event“3: conferenceCreated( )4: “forward event“12: leaveMonitorRes( )13: “forward event“11: attachMediaReq( )14: release( )8: attachMediaReq.7: partyJoined( )1: The application creates a new object to receive the callbacks from the conference call control manager.

34、 2: The application reserves resources for some time in the future. ETSI ETSI ES 202 915-4-5 V1.4.1 (2006-12) 9 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 implem

35、entation 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

36、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

37、 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 co

38、nference. 13: The message is forwarded to the application. 14: The application decides to release the entire conference. 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 appli

39、cation via a web interface (not shown). By dragging and dropping names from the addressbook, the end-users add 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. ETSI ETSI ES 202 915-

40、4-5 V1.4.1 (2006-12) 10: IpConfCallControlManager: IpAppConfCall: (Logical View:IpAppLogic): IpConfCall first : IpSubConfCallsecond : IpSubConfCall: IpCallLeg : IpAppCallLeg2: createConference ()1: new()3: getSubConferences( )5: createAndRouteCallLegReq( )7: createAndRouteCallLegReq( )8: createAndRo

41、uteCallLegReq( )12: splitSubConference( )9: createAndRouteCallLegReq( )13: moveCallLeg( )14: release( )10: eventReportRes( )11: “forward event“4: new()6: new()1: The application creates a new interface to receive the callbacks from the conference call. 2: The application initiates the conference. Th

42、ere 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 returne

43、d as a result of the createConference, therefore the application uses this method to get the subconference. 4: The application creates a new IpAppCallLeg interface. 5: The application adds the first party to the subconference. This process is repeated for all 4 parties. Note that in the following no

44、t all steps are shown. 6: The gateway creates a new IpCallLeg interface. 7: The application adds parties to the subconference. 8: The application adds parties to the subconference. 9: The application adds parties to the subconference. 10: When a party A answers the application is notified. ETSI ETSI

45、 ES 202 915-4-5 V1.4.1 (2006-12) 11We assume that all parties answer. This happens in the same way as for party A and is not shown in the following. 11: The message is forwarded to the application. 12: The application decides to split the conference. Party C the conference interfaces are specialisat

46、ions of the corresponding multi-party call interfaces. Communication between the application and service packages is done via the relations; the interfaces can communicate with callback methods in the corresponding application interfaces. IpAppConfCallpartyJoined()leaveMonitorRes()(from cccs)IpAppCo

47、nfCallControlManagerconferenceCreated()(from cccs)IpAppSubConfCallchairSelection()floorRequest()(from cccs)IpConfCallgetSubConferences()createSubConference()leaveMonitorReq() getConferenceAddress()(from cccs)IpSubConfCallsplitSubConference()mergeSubConference()moveCal lLe g()inspectVideo()inspectVid

48、eoCancel()ap po intSpeaker()chai rSe le ct ion ()chan ge Conferen ce Po li cy()(from cccs)IpConfCallControlManagercreateConference()checkResources()reserveResources()freeResources()(from cccs)1 0n1 0nIpA ppM ul tiMe dia Call Co nt rolMan ag erreportMediaNotification()(from mmccs)IpAppMultiMediaCalls

49、uperviseVolumeRes()superviseVolumeErr()(from mmccs)IpMultiMediaCallLegmediaStreamAllow()mediaStreamMonitorReq()getMediaStreams()(from mmccs)IpAppMultiMediaCallLegmediaStreamMonitorRes()(from mmccs)1 0n10n10n1 0n10n10nFigure 1: Application Interfaces This class diagram shows the interfaces that make up the conference call control service package. The diagram also shows the inheritance relation between the multi-party call interfaces and the conference call interfaces; the conference interfaces are specialisat