ETSI TS 129 198-4-5-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi.pdf

1、 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 controlService Cap

2、ability Feature (SCF) (3GPP TS 29.198-04-5 version 9.0.0 Release 9)floppy3ETSI ETSI TS 129 198-4-5 V9.0.0 (2010-01) 13GPP TS 29.198-04-5 version 9.0.0 Release 9 Reference RTS/TSGC-0029198-04-5v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4

3、 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 present document may be made availabl

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

5、cific 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 error

6、s 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

7、 media. European Telecommunications Standards Institute 2010. 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 of ETSI registered for the benefit of its Members and

8、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 ETSI TS 129 198-4-5 V9.0.0 (2010-01) 23GPP TS 29.

9、198-04-5 version 9.0.0 Release 9 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 S

10、R 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

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

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

13、 ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 198-4-5 V9.0.0 (2010-01) 33GPP TS 29.198-04-5 version 9.0.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3

14、Introduction 5g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Conference call control Service Sequence Diagrams . 8g34.1 Meet-me conference without subconferencing . 8g34.2 Non-add hoc add-on with subconferencing 11g34.3 Non-addhoc add-on

15、 multimedia . 13g34.4 Resource Reservation . 15g35 Class Diagrams . 16g36 Conference call control Service Interface Classes . 18g36.1 Interface Class IpConfCallControlManager . 19g36.1.1 Method createConference() 19g36.1.2 Method checkResources() . 20g36.1.3 Method reserveResources() 20g36.1.4 Metho

16、d freeResources() 21g36.2 Interface Class IpAppConfCallControlManager 22g36.2.1 Method conferenceCreated() 22g36.3 Interface Class IpConfCall . 22g36.3.1 Method getSubConferences() . 23g36.3.2 Method createSubConference() 23g36.3.3 Method leaveMonitorReq() 24g36.3.4 Method getConferenceAddress() 24g

17、36.4 Interface Class IpAppConfCall 25g36.4.1 Method partyJoined() 25g36.4.2 Method leaveMonitorRes() . 25g36.5 Interface Class IpSubConfCall . 26g36.5.1 Method splitSubConference(). 27g36.5.2 Method mergeSubConference() 27g36.5.3 Method moveCallLeg() . 27g36.5.4 Method inspectVideo() . 28g36.5.5 Met

18、hod inspectVideoCancel() 28g36.5.6 Method appointSpeaker() . 28g36.5.7 Method chairSelection() . 29g36.5.8 Method changeConferencePolicy(). 29g36.6 Interface Class IpAppSubConfCall 30g36.6.1 Method chairSelection() . 30g36.6.2 Method floorRequest() 30g37 Conference call control Service State Transit

19、ion Diagrams . 31g38 Conference call control Data Definitions . 31g38.1 Event Notification Data Definitions . 31g38.2 Conference call control Data Definitions . 31g38.2.1 IpConfCall 31g38.2.2 IpConfCallRef . 31g38.2.3 IpAppConfCall . 31g3ETSI ETSI TS 129 198-4-5 V9.0.0 (2010-01) 43GPP TS 29.198-04-5

20、 version 9.0.0 Release 9 8.2.4 IpAppConfCallRef 31g38.2.5 IpSubConfCall 32g38.2.6 IpSubConfCallRef 32g38.2.7 IpAppSubConfCall . 32g38.2.8 IpAppSubConfCallRef 32g38.2.9 TpSubConfCallIdentifierSet . 32g38.2.10 TpConfCallIdentifier 32g38.2.11 TpSubConfCallIdentifier 32g38.2.12 IpAppConfCallControlManag

21、er . 32g38.2.13 IpAppConfCallControlManagerRef . 32g38.2.14 TpConfPolicyType 32g38.2.15 TpConfPolicy 33g38.2.16 TpMonoMediaConfPolicy 33g38.2.17 TpJoinEventInfo . 33g38.2.18 TpConfSearchCriteria . 33g38.2.19 TpConfSearchResult . 34g38.2.20 TpMultiMediaConfPolicy . 34g38.2.21 TpResourceReservation 34

22、g38.2.22 TpVideoHandlingType . 34g3Annex A (normative): OMG IDL Description of Conference call control SCF . 35g3Annex B (informative): W3C WSDL Description of Conference call control SCF 36g3Annex C (informative): Java API Description of the Call Control SCFs 37g3Annex D (informative): Description

23、of Call Control Sub-part 5: Conference call control SCF for 3GPP2 cdma2000 networks 38g3D.1 General Exceptions. 38g3D.2 Specific Exceptions 38g3D.2.1 Clause 1: Scope 38g3D.2.2 Clause 2: References 38g3D.2.3 Clause 3: Definitions and abbreviations . 38g3D.2.4 Clause 4: Conference call control Service

24、 Sequence Diagrams . 38g3D.2.5 Clause 5: Class Diagrams . 38g3D.2.6 Clause 6: Conference call control Service Interface Classes 39g3D.2.7 Clause 7: Conference call control Service State Transition Diagrams . 39g3D.2.8 Clause 8: Conference call control Data Definitions . 39g3D.2.9 Clause 9: Multi-Par

25、ty Call Control Data Definitions . 39g3D.2.10 Annex A (normative): OMG IDL Description of Conference call control SCF. 39g3D.2.11 Annex B (informative): W3C WSDL Description of Conference call control SCF . 39g3D.2.12 Annex C (informative): Java API Description of the Call Control SCFs . 39g3Annex E

26、 (informative): Change history . 40g3History 41g3ETSI ETSI TS 129 198-4-5 V9.0.0 (2010-01) 53GPP TS 29.198-04-5 version 9.0.0 Release 9 Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continu

27、ing 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 prese

28、nted 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 onl

29、y changes have been incorporated in the document. Introduction The present document is part 4, sub-part 5 of a multi-part TS covering the 3rdGeneration Partnership Project: Technical Specification Group Core Network and Terminals; Open Service Access (OSA); Application Programming Interface (API), a

30、s 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: “Mul

31、ti-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 Releas

32、e 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 Map

33、ping 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 maintain

34、ed. ETSI ETSI TS 129 198-4-5 V9.0.0 (2010-01) 63GPP TS 29.198-04-5 version 9.0.0 Release 9 Table: Overview of the OSA APIs 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:

35、 “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 ETSI TS 129 198-4-5 V9.0.0 (2010-01) 83GPP TS 29.198-04-5 version 9.0.0 Release 9 6 3GPP TS 24.002: “GSM-UMTS Public Land Mobile Network

36、(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) U

37、ser 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 S

38、equence 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 a

39、pplication can decide to accept the participant in to the conference. The application can also be notified when parties are leaving the conference. ETSI ETSI TS 129 198-4-5 V9.0.0 (2010-01) 93GPP TS 29.198-04-5 version 9.0.0 Release 9 : (Logical View:IpAppLogic): IpAppConfCallControlManager: IpAppCo

40、nfCall: IpConfCallControlManager: IpConfCall1: new()5: new()2: reserveResources( )6: leaveMonitorReq( )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

41、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 ETSI TS 129 198-4-5 V9.0.0 (2010-01) 103GPP TS 29.198-04-5 version 9.0.0 Release 9 With this same method the application registe

42、rs 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, t

43、his 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 conferen

44、ce. 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:

45、 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 ETSI TS 129 198-4-5 V9.0.0 (20

46、10-01) 113GPP TS 29.198-04-5 version 9.0.0 Release 9 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 nam

47、es 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. : IpConfCallControlManager: IpAppConfCall: (Logical View:IpAppLogic): IpConfCall first :

48、IpSubConfCallsecond : IpSubConfCall: IpCallLeg : IpAppCallLeg2: createConference( )1: new()3: getSubConferences( )5: createAndRouteCallLegReq( )7: createAndRouteCallLegReq( )8: createAndRouteCallLegReq( )12: splitSubConference( )9: createAndRouteCallLegReq( )13: moveCallLeg( )14: release( )10: event

49、ReportRes( )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. 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