ETSI ES 203 915-4-3-2007 Open Service Access (OSA) Application Programming Interface (API) Part 4 Call Control Sub-part 3 Multi-Party Call Control SCF (Parlay 5) (V1 2 1 Includes D_1.pdf

1、 ETSI ES 203 915-4-3 V1.2.1 (2007-01)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 4: Call Control;Sub-part 3: Multi-Party Call Control SCF(Parlay 5)floppy3 ETSI ETSI ES 203 915-4-3 V1.2.1 (2007-01) 2 Reference RES/TISPAN-01029-04-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

3、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, t

4、he 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 do

5、cuments 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 p

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

7、the 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 203 915-4-3 V1.2.1 (2007-01) 3 Contents Intellectual Property Rights7 Fore

8、word.7 1 Scope 9 2 References 9 3 Definitions and abbreviations.9 3.1 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

9、 4.5 Complex Card Service17 4.6 Hotline Service.20 4.7 Network Controlled 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 creat

10、eNotification()27 6.1.3 Method destroyNotification() .29 6.1.4 Method changeNotification()29 6.1.5 Method getNotification().29 6.1.6 Method setCallLoadControl().30 6.1.7 Method enableNotifications() .30 6.1.8 Method disableNotifications() 31 6.1.9 Method getNextNotification() 32 6.2 Interface Class

11、IpAppMultiPartyCallControlManager.32 6.2.1 Method reportNotification()33 6.2.2 Method callAborted() .34 6.2.3 Method managerInterrupted().34 6.2.4 Method managerResumed()34 6.2.5 Method callOverloadEncountered()35 6.2.6 Method callOverloadCeased() 35 6.2.7 Method abortMultipleCalls()35 6.3 Interface

12、 Class IpMultiPartyCall35 6.3.1 Method getCallLegs().36 6.3.2 Method createCallLeg()36 6.3.3 Method createAndRouteCallLegReq() .37 6.3.4 Method release() .38 6.3.5 Method deassignCall()38 6.3.6 Method getInfoReq() 38 6.3.7 Method setChargePlan() .39 6.3.8 Method setAdviceOfCharge().39 6.3.9 Method s

13、uperviseReq().39 6.4 Interface Class IpAppMultiPartyCall .40 6.4.1 Method getInfoRes().40 6.4.2 Method getInfoErr()40 6.4.3 Method superviseRes() .41 6.4.4 Method superviseErr() 41 6.4.5 Method callEnded() 41 6.4.6 Method createAndRouteCallLegErr().42 ETSI ETSI ES 203 915-4-3 V1.2.1 (2007-01) 4 6.5

14、Interface Class IpCallLeg.42 6.5.1 Method routeReq()43 6.5.2 Method eventReportReq() 44 6.5.3 Method release() .44 6.5.4 Method getInfoReq() 45 6.5.5 Method getCall().45 6.5.6 Method attachMediaReq() 45 6.5.7 Method detachMediaReq() .46 6.5.8 Method getCurrentDestinationAddress()46 6.5.9 Method cont

15、inueProcessing() .46 6.5.10 Method setChargePlan() .47 6.5.11 Method setAdviceOfCharge().47 6.5.12 Method superviseReq().47 6.5.13 Method deassign() 48 6.5.14 Method getProperties().48 6.5.15 Method setProperties() .49 6.6 Interface Class IpAppCallLeg 49 6.6.1 Method eventReportRes().50 6.6.2 Method

16、 eventReportErr()50 6.6.3 Method attachMediaRes().51 6.6.4 Method attachMediaErr() .51 6.6.5 Method detachMediaRes()51 6.6.6 Method detachMediaErr().51 6.6.7 Method getInfoRes().51 6.6.8 Method getInfoErr()52 6.6.9 Method routeErr().52 6.6.10 Method superviseRes() .52 6.6.11 Method superviseErr() 53

17、 6.6.12 Method callLegEnded() 53 7 MultiParty Call Control Service State Transition Diagrams53 7.1 State Transition Diagrams for IpMultiPartyCallControlManager 53 7.1.1 Active State.54 7.1.2 Interrupted State54 7.1.3 Overview of allowed methods 54 7.2 State Transition Diagrams for IpMultiPartyCall 5

18、4 7.2.1 IDLE State 55 7.2.2 ACTIVE State.55 7.2.3 RELEASED State.55 7.2.4 Overview of allowed methods 56 7.3 State Transition Diagrams for IpCallLeg .56 7.3.1 Originating Call Leg .57 7.3.1.1 Initiating State .57 7.3.1.2 Analysing State .59 7.3.1.3 Active State.60 7.3.1.4 Releasing State62 7.3.1.5 O

19、verview of allowed methods, Originating Call Leg STD.64 7.3.2 Terminating Call Leg65 7.3.2.1 Idle (terminating) State .65 7.3.2.2 Active (terminating) State .66 7.3.2.3 Releasing (terminating) State69 7.3.2.4 Overview of allowed methods and trigger events, Terminating Call Leg STD 71 8 Multi-Party C

20、all Control Service Properties 72 8.1 List of Service Properties .72 8.2 Service Property values for the CAMEL Service Environment .74 9 Multi-Party Call Control Data Definitions.75 9.1 Event Notification Data Definitions.75 9.2 Multi-Party Call Control Data Definitions .75 9.2.1 IpCallLeg 75 9.2.2

21、IpCallLegRef 75 9.2.3 IpAppCallLeg .75 ETSI ETSI ES 203 915-4-3 V1.2.1 (2007-01) 5 9.2.4 IpAppCallLegRef .76 9.2.5 IpMultiPartyCall .76 9.2.6 IpMultiPartyCallRef .76 9.2.7 IpAppMultiPartyCall 76 9.2.8 IpAppMultiPartyCallRef 76 9.2.9 IpMultiPartyCallControlManager.76 9.2.10 IpMultiPartyCallControlMan

22、agerRef .76 9.2.11 IpAppMultiPartyCallControlManager76 9.2.12 IpAppMultiPartyCallControlManagerRef 76 9.2.13 TpAppCallLegRefSet .76 9.2.14 TpMultiPartyCallIdentifier .76 9.2.15 TpAppMultiPartyCallBack.77 9.2.16 TpAppMultiPartyCallBackRefType .77 9.2.17 TpAppCallLegCallBack .77 9.2.18 TpMultiPartyCal

23、lIdentifierSet 77 9.2.19 TpCallAppInfo78 9.2.20 TpCallAppInfoType78 9.2.21 TpCallAppInfoSet.78 9.2.22 TpCallEventRequest .78 9.2.23 TpCallEventRequestSet 79 9.2.24 TpCallEventType79 9.2.25 TpAdditionalCallEventCriteria.81 9.2.26 TpCallEventInfo .81 9.2.27 TpCallAdditionalEventInfo 82 9.2.28 TpCallNo

24、tificationRequest .82 9.2.29 TpCallNotificationScope 82 9.2.30 TpCallNotificationInfo .82 9.2.31 TpCallNotificationReportScope .83 9.2.32 TpNotificationRequested 83 9.2.33 TpNotificationRequestedSet.83 9.2.34 TpReleaseCause83 9.2.35 TpReleaseCauseSet.83 9.2.36 TpCallLegIdentifier 83 9.2.37 TpCallLeg

25、IdentifierSet .84 9.2.38 TpCallLegAttachMechanism84 9.2.39 TpCallLegConnectionProperties.84 9.2.40 TpCallLegInfoReport84 9.2.41 TpCallLegInfoType 85 9.2.42 TpCallLegSuperviseTreatment.85 9.2.43 TpCallHighProbabilityCompletion.85 9.2.44 TpNotificationRequestedSetEntry 85 9.2.45 TpCarrierSet .85 9.2.4

26、6 TpCarrier 85 9.2.47 TpCarrierID 86 9.2.48 TpCarrierSelectionField86 9.2.49 TpCallLegPropertyName86 9.2.50 TpCallLegPropertyNameList86 9.2.51 TpCallLegPropertyValue86 9.2.52 TpCallLegProperty .86 9.2.53 TpCallLegPropertyList .86 Annex A (normative): OMG IDL Description of Multi-Party Call Control S

27、CF87 Annex B (informative): W3C WSDL Description of Multi-Party Call Control SCF 88 Annex C (informative): Java API Description of the Call Control SCFs89 Annex D (informative): Contents of 3GPP OSA Rel-6 Call Control .90 Annex E (informative): Description of Call Control Sub-part 3: Multi-party cal

28、l control SCF for 3GPP2 cdma2000 networks 91 ETSI ETSI ES 203 915-4-3 V1.2.1 (2007-01) 6 E.1 General Exceptions.91 E.2 Specific Exceptions91 E.2.1 Clause 1: Scope 91 E.2.2 Clause 2: References 91 E.2.3 Clause 3: Definitions and abbreviations.91 E.2.4 Clause 4: MultiParty Call Control Service Sequenc

29、e Diagrams 91 E.2.5 Clause 5: Class Diagrams.91 E.2.6 Clause 6: MultiParty Call Control Service Interface Classes .91 E.2.7 Clause 7: MultiParty Call Control Service State Transition Diagrams 92 E.2.8 Clause 8: Multi-Party Call Control Service Properties.92 E.2.9 Clause 9: Multi-Party Call Control D

30、ata Definitions .92 E.2.10 Annex A (normative): OMG IDL Description of Multi-Party Call Control SCF.92 E.2.11 Annex B (informative): W3C WSDL Description of Multi-Party Call Control SCF.92 E.2.12 Annex C (informative): Java API Description of the Multi-Party Call Control SCF .92 Annex F (informative

31、): Record of changes 93 F.1 Interfaces 93 F.1.1 New 93 F.1.2 Deprecated93 F.1.3 Removed.93 F.2 Methods94 F.2.1 New 94 F.2.2 Deprecated94 F.2.3 Modified.94 F.2.4 Removed.94 F.3 Data Definitions .95 F.3.1 New 95 F.3.2 Modified.95 F.3.3 Removed.95 F.4 Service Properties.95 F.4.1 New 95 F.4.2 Deprecated

32、96 F.4.3 Modified.96 F.4.4 Removed.96 F.5 Exceptions 96 F.5.1 New 96 F.5.2 Modified.96 F.5.3 Removed.97 F.6 Others .97 History 98 ETSI ETSI ES 203 915-4-3 V1.2.1 (2007-01) 7 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. T

33、he 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 f

34、rom 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 E

35、TSI 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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISP

36、AN). The present document is part 4, sub-part 3 of a multi-part deliverable covering Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (ES 203 915) is structured in the following parts: Part 1: “Overview“; Part 2: “Common Data Definitions“

37、; 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: “Multi-Media Call Control SCF“; Sub-part 5: “Conference Call Control SCF“; Part 5: “User Interaction SCF“; Par

38、t 6: “Mobility SCF“; Part 7: “Terminal Capabilities SCF“; Part 8: “Data Session Control SCF“; Part 9: “Generic 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 Manage

39、ment SCF“; Part 15: “Multi-Media Messaging SCF“. ETSI ETSI ES 203 915-4-3 V1.2.1 (2007-01) 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 documen

40、t forms part of the Parlay 5.1 set of specifications. The present document is equivalent to 3GPP TS 29.198-4-3 V6.6.0 (Release 6). ETSI ETSI ES 203 915-4-3 V1.2.1 (2007-01) 9 1 Scope The present document is part 4, sub-part 3 of the Stage 3 specification for an Application Programming Interface (API

41、) 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 Multi-Party Call Control Service Capability Feature (S

42、CF) aspects of the interface. All aspects of the Multi-Party 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

43、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 203 915-1 contain provi

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

45、the terms and definitions given in ES 203 915-1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ES 203 915-1 apply. ETSI ETSI ES 203 915-4-3 V1.2.1 (2007-01) 104 MultiParty Call Control Service Sequence Diagrams 4.1 Application initiated call setup The f

46、ollowing sequence diagram shows an application creating a call between party 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

47、 call is being set up to party B. While the announcement is being played, 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 parti

48、es (or more). After the two party call is established, the application can 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 th

49、e A-party by entering a service code (mid-call event). The procedure for call 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: new()2: createCall( )3: new()7: ev entReportReq( ): IpAppUICall: IpUICall11: sendInf oReq( )15: ev entReportReq( )18: abortActionReq( )5: createCallLeg( )6: new()13: