ETSI ES 204 915-4-3-2008 Open Service Access (OSA) Application Programming Interface (API) Part 4 Call Control Sub-part 3 Multi-Party Call Control SCF (Parlay 6)《开放业务接入(OSA) 应用编程接口_1.pdf

1、 ETSI ES 204 915-4-3 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 4: Call Control;Sub-part 3: Multi-Party Call Control SCF(Parlay 6)floppy3 ETSI ETSI ES 204 915-4-3 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01032-4-03-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 2008. The Parlay Group 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for

7、 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 204 915-4-3 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights7 Foreword.7 1 Scope 9 2 References 9 3 Definitions and abbreviations.9 3.1

8、Definitions9 3.2 Abbreviations .9 4 MultiParty Call Control Service Sequence Diagrams 10 4.1 Application initiated call setup.10 4.2 Call Barring 2 .11 4.3 Call forwarding on Busy Service .13 4.4 Call Information Collect Service14 4.5 Complex Card Service17 4.6 Hotline Service.20 4.7 Network Control

9、led Notifications 23 4.8 Use of the Redirected event24 5 Class Diagrams.24 6 MultiParty Call Control Service Interface Classes.26 6.1 Interface Class IpMultiPartyCallControlManager26 6.1.1 Method createCall() 27 6.1.2 Method createNotification()27 6.1.3 Method destroyNotification() .29 6.1.4 Method

10、changeNotification()29 6.1.5 Method setCallLoadControl().29 6.1.6 Method enableNotifications() .30 6.1.7 Method disableNotifications() 31 6.1.8 Method getNextNotification() 31 6.2 Interface Class IpAppMultiPartyCallControlManager.32 6.2.1 Method reportNotification()32 6.2.2 Method callAborted() .33

11、6.2.3 Method managerInterrupted().33 6.2.4 Method managerResumed()34 6.2.5 Method callOverloadEncountered()34 6.2.6 Method callOverloadCeased() 34 6.2.7 Method abortMultipleCalls() 34 6.3 Interface Class IpMultiPartyCall34 6.3.1 Method getCallLegs().35 6.3.2 Method createCallLeg()35 6.3.3 Method cre

12、ateAndRouteCallLegReq() .36 6.3.4 Method release() .37 6.3.5 Method deassignCall()37 6.3.6 Method getInfoReq() 37 6.3.7 Method setChargePlan() .38 6.3.8 Method setAdviceOfCharge().38 6.3.9 Method superviseReq().38 6.4 Interface Class IpAppMultiPartyCall .39 6.4.1 Method getInfoRes().39 6.4.2 Method

13、getInfoErr()39 6.4.3 Method superviseRes() .40 6.4.4 Method superviseErr() 40 6.4.5 Method callEnded() 40 6.4.6 Method createAndRouteCallLegErr().40 6.5 Interface Class IpCallLeg.41 ETSI ETSI ES 204 915-4-3 V1.1.1 (2008-05) 4 6.5.1 Method routeReq()42 6.5.2 Method eventReportReq() 42 6.5.3 Method re

14、lease() .43 6.5.4 Method getInfoReq() 43 6.5.5 Method getCall().43 6.5.6 Method attachMediaReq() 44 6.5.7 Method detachMediaReq() .44 6.5.8 Method getCurrentDestinationAddress()44 6.5.9 Method continueProcessing() .45 6.5.10 Method setChargePlan() .45 6.5.11 Method setAdviceOfCharge().45 6.5.12 Meth

15、od superviseReq().46 6.5.13 Method deassign() 46 6.5.14 Method getProperties() .46 6.5.15 Method setProperties()47 6.6 Interface Class IpAppCallLeg 48 6.6.1 Method eventReportRes().48 6.6.2 Method eventReportErr()49 6.6.3 Method attachMediaRes().49 6.6.4 Method attachMediaErr() .49 6.6.5 Method deta

16、chMediaRes()49 6.6.6 Method detachMediaErr().49 6.6.7 Method getInfoRes().50 6.6.8 Method getInfoErr()50 6.6.9 Method routeErr().50 6.6.10 Method superviseRes() .50 6.6.11 Method superviseErr() 51 6.6.12 Method callLegEnded() 51 7 MultiParty Call Control Service State Transition Diagrams51 7.1 State

17、 Transition Diagrams for IpMultiPartyCallControlManager 51 7.1.1 Active State.52 7.1.2 Interrupted State52 7.1.3 Overview of allowed methods 52 7.2 State Transition Diagrams for IpMultiPartyCall 52 7.2.1 IDLE State 53 7.2.2 ACTIVE State.53 7.2.3 RELEASED State.53 7.2.4 Overview of allowed methods 54

18、 7.3 State Transition Diagrams for IpCallLeg .54 7.3.1 Originating Call Leg .55 7.3.1.1 Initiating State .55 7.3.1.2 Analysing State .57 7.3.1.3 Active State.58 7.3.1.4 Releasing State60 7.3.1.5 Overview of allowed methods, Originating Call Leg STD.62 7.3.2 Terminating Call Leg63 7.3.2.1 Idle (termi

19、nating) State .63 7.3.2.2 Active (terminating) State .64 7.3.2.3 Releasing (terminating) State67 7.3.2.4 Overview of allowed methods and trigger events, Terminating Call Leg STD 69 8 Multi-Party Call Control Service Properties 69 8.1 List of Service Properties .69 8.2 Service Property values for the

20、 CAMEL Service Environment. 71 9 Multi-Party Call Control Data Definitions.72 9.1 Event Notification Data Definitions.72 9.2 Multi-Party Call Control Data Definitions .73 9.2.1 IpCallLeg 73 9.2.2 IpCallLegRef 73 9.2.3 IpAppCallLeg .73 9.2.4 IpAppCallLegRef .73 ETSI ETSI ES 204 915-4-3 V1.1.1 (2008-0

21、5) 5 9.2.5 IpMultiPartyCall .73 9.2.6 IpMultiPartyCallRef .73 9.2.7 IpAppMultiPartyCall 73 9.2.8 IpAppMultiPartyCallRef 73 9.2.9 IpMultiPartyCallControlManager.73 9.2.10 IpMultiPartyCallControlManagerRef .73 9.2.11 IpAppMultiPartyCallControlManager73 9.2.12 IpAppMultiPartyCallControlManagerRef 73 9.

22、2.13 TpAppCallLegRefSet .73 9.2.14 TpMultiPartyCallIdentifier .74 9.2.15 TpAppMultiPartyCallBack.74 9.2.16 TpAppMultiPartyCallBackRefType .74 9.2.17 TpAppCallLegCallBack .74 9.2.18 TpMultiPartyCallIdentifierSet 74 9.2.19 TpCallAppInfo75 9.2.20 TpCallAppInfoType75 9.2.21 TpCallAppInfoSet.75 9.2.22 Tp

23、CallEventRequest .75 9.2.23 TpCallEventRequestSet 76 9.2.24 TpCallEventType76 9.2.25 TpAdditionalCallEventCriteria.78 9.2.26 TpCallEventInfo .78 9.2.27 TpCallAdditionalEventInfo 79 9.2.28 TpCallNotificationRequest .79 9.2.29 TpCallNotificationScope 79 9.2.30 TpCallNotificationInfo .79 9.2.31 TpCallN

24、otificationReportScope .80 9.2.32 TpNotificationRequested 80 9.2.33 TpNotificationRequestedSet.80 9.2.34 TpReleaseCause80 9.2.35 TpReleaseCauseSet.80 9.2.36 TpCallLegIdentifier 80 9.2.37 TpCallLegIdentifierSet .81 9.2.38 TpCallLegAttachMechanism81 9.2.39 TpCallLegConnectionProperties.81 9.2.40 TpCal

25、lLegInfoReport81 9.2.41 TpCallLegInfoType 82 9.2.42 TpCallLegSuperviseTreatment.82 9.2.43 TpCallHighProbabilityCompletion.82 9.2.44 TpNotificationRequestedSetEntry 82 9.2.45 TpCarrierSet .82 9.2.46 TpCarrier 82 9.2.47 TpCarrierID 83 9.2.48 TpCarrierSelectionField83 9.2.49 TpCallLegPropertyName83 9.2

26、.50 TpCallLegPropertyNameList83 9.2.51 TpCallLegPropertyValue83 9.2.52 TpCallLegProperty .83 9.2.53 TpCallLegPropertyList .83 Annex A (normative): OMG IDL Description of Multi-Party Call Control SCF84 Annex B (informative): W3C WSDL Description of Multi-Party Call Control SCF 85 Annex C (informative

27、): Java API Description of the Call Control SCFs86 Annex D (informative): Contents of 3GPP OSA Rel-7 Call Control .87 Annex E (informative): Description of Call Control Sub-part 3: Multi-party call control SCF for 3GPP2 cdma2000 networks 88 E.1 General Exceptions.88 ETSI ETSI ES 204 915-4-3 V1.1.1 (

28、2008-05) 6 E.2 Specific Exceptions88 E.2.1 Clause 1: Scope 88 E.2.2 Clause 2: References 88 E.2.3 Clause 3: Definitions and abbreviations.88 E.2.4 Clause 4: MultiParty Call Control Service Sequence Diagrams 88 E.2.5 Clause 5: Class Diagrams.88 E.2.6 Clause 6: MultiParty Call Control Service Interfac

29、e Classes .88 E.2.7 Clause 7: MultiParty Call Control Service State Transition Diagrams 89 E.2.8 Clause 8: Multi-Party Call Control Service Properties.89 E.2.9 Clause 9: Multi-Party Call Control Data Definitions .89 E.2.10 Annex A (normative): OMG IDL Description of Multi-Party Call Control SCF.89 E

30、.2.11 Annex B (informative): W3C WSDL Description of Multi-Party Call Control SCF.89 E.2.12 Annex C (informative): Java API Description of the Multi-Party Call Control SCF .89 Annex F (informative): Record of changes 90 F.1 Interfaces 90 F.1.1 New 90 F.1.2 Deprecated90 F.1.3 Removed.90 F.2 Methods90

31、 F.2.1 New 90 F.2.2 Deprecated90 F.2.3 Modified.91 F.2.4 Removed.91 F.3 Data Definitions .91 F.3.1 New 91 F.3.2 Modified.91 F.3.3 Removed.91 F.4 Service Properties.91 F.4.1 New 91 F.4.2 Deprecated91 F.4.3 Modified.92 F.4.4 Removed.92 F.5 Exceptions 92 F.5.1 New 92 F.5.2 Modified.92 F.5.3 Removed.92

32、F.6 Others .92 History 93 ETSI ETSI ES 204 915-4-3 V1.1.1 (2008-05) 7 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 no

33、n-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

34、/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

35、 the present document. Foreword 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 3 of a multi-part deliverable covering Open Service Access

36、 (OSA); Application Programming Interface (API), as identified below. The API specification (ES 204 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

37、: “Generic Call Control SCF“; Sub-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: “G

38、eneric Messaging SCF“; Part 10: “Connectivity Manager SCF“; Part 11: “Account Management SCF“; Part 12: “Charging SCF“; Part 13: “Policy Management SCF“; Part 14: “Presence and Availability Management SCF“; Part 15: “Multi-Media Messaging SCF“ Part 16: “Service Broker SCF“. ETSI ETSI ES 204 915-4-3

39、V1.1.1 (2008-05) 8 The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP, in co-operation with a number of JAIN Community (http:/ member companies. The present document forms part of the Parlay 6.0 set of specifications. The present document

40、 is equivalent to 3GPP TS 29.198-4-3 V7.0.0 (Release 7). ETSI ETSI ES 204 915-4-3 V1.1.1 (2008-05) 9 1 Scope The present document is part 4, sub-part 3 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA). The OSA specifications define an architec

41、ture 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 Multi-Party Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Multi-Party Call Control

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

43、. 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 204 915-1 contain provisions which, through reference in this text, constitute provisions of the

44、present document. ETSI ES 204 915-1: “Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 6)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 204 915-1 apply. 3.2 Abbreviations F

45、or the purposes of the present document, the abbreviations given in ES 204 915-1 apply. ETSI ETSI ES 204 915-4-3 V1.1.1 (2008-05) 104 MultiParty Call Control Service Sequence Diagrams 4.1 Application initiated call setup The following sequence diagram shows an application creating a call between par

46、ty A and party B. Here, a call is created first. Then party As call leg is created before events are requested on it for answer and then routed to the call. On answer from Party A, an announcement is played indicating that the call is being set up to party B. While the announcement is being played,

47、party Bs call leg is created and then events are requested on it for answer. On answer from Party B the announcement is cancelled and party B is routed to the call. The service may as a variation be extended to include 3 parties (or more). After the two party call is established, the application can

48、 create a new leg and request to route it to a new destination address in order to establish a 3 party call. The event that causes this to happen could for example be the report of answer event from B-party or controlled by the A-party by entering a service code (mid-call event). The procedure for c

49、all setup to party C is exactly the same as for the set up of the connection to party B (sequence 13 to 17 in the sequence diagram). PartyB : IpCallLeg: IpMultiPartyCallControlManager: IpAppMultiPartyCall: IpMultiPartyCallPartyA : IpCallLeg: (Logical View:IpAppLogic)4: setCallback( )1: n ew()2: createCall( )3: new()7: ev entReportReq( ): IpAppUICall: IpUICall11: sendInf oReq( )15: ev entReportReq( )18: abortActionReq( )5: createCallLeg( )6: new()13: createCallLeg( )14: new()AppPartyA : (IpAppMultiPartyCallLeg)AppPartyB :