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

《ETSI ES 202 915-4-3-2006 Open Service Access (OSA) Application Programming Interface (API) Part 4 Call Control Sub-part 3 Multi-Party Call Control SCF (Parlay 4) (V1 4 1 Includes D_1.pdf》由会员分享，可在线阅读，更多相关《ETSI ES 202 915-4-3-2006 Open Service Access (OSA) Application Programming Interface (API) Part 4 Call Control Sub-part 3 Multi-Party Call Control SCF (Parlay 4) (V1 4 1 Includes D_1.pdf（95页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI ES 202 915-4-3 V1.4.1 (2006-12)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 4: Call Control;Sub-part 3: Multi-Party Call Control SCF(Parlay 4)floppy3 ETSI ETSI ES 202 915-4-3 V1.4.1 (2006-12) 2 Reference RES/TISPAN-01028-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 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

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 202 915-4-3 V1.4.1 (2006-12) 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() .28 6.1.4 Method changeNotification()29 6.1.5 Method getNotification().29 6.1.6 Method setCallLoadControl().29 6.1.7 Method enableNotifications().30 6.1.8 Method disableNotifications()31 6.1.9 Method getNextNotification()31 6.2 Interface Class IpA

11、ppMultiPartyCallControlManager.32 6.2.1 Method reportNotification()32 6.2.2 Method callAborted() .33 6.2.3 Method managerInterrupted().34 6.2.4 Method managerResumed()34 6.2.5 Method callOverloadEncountered()34 6.2.6 Method callOverloadCeased() 34 6.3 Interface Class IpMultiPartyCall34 6.3.1 Method

12、getCallLegs().35 6.3.2 Method createCallLeg()35 6.3.3 Method createAndRouteCallLegReq() .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 Ip

13、AppMultiPartyCall .39 6.4.1 Method getInfoRes().39 6.4.2 Method 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().41 6.5 Interface Class IpCallLeg.41 ETSI ETSI ES 202 915-4-3 V1.4.1 (2006-12) 4 6.5.1 Meth

14、od routeReq()42 6.5.2 Method eventReportReq() 43 6.5.3 Method release() .43 6.5.4 Method getInfoReq() 44 6.5.5 Method getCall().44 6.5.6 Method attachMediaReq() 44 6.5.7 Method detachMediaReq() .45 6.5.8 Method getCurrentDestinationAddress()45 6.5.9 Method continueProcessing() .45 6.5.10 Method setC

15、hargePlan() .46 6.5.11 Method setAdviceOfCharge().46 6.5.12 Method superviseReq().46 6.5.13 Method deassign() 47 6.6 Interface Class IpAppCallLeg 47 6.6.1 Method eventReportRes().48 6.6.2 Method eventReportErr()48 6.6.3 Method attachMediaRes().49 6.6.4 Method attachMediaErr() .49 6.6.5 Method detach

16、MediaRes()49 6.6.6 Method detachMediaErr().49 6.6.7 Method getInfoRes().49 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 T

17、ransition 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 7

18、.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 (termina

19、ting) 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 70 8.1 List of Service Properties .70 8.2 Service Property values for the C

20、AMEL Service Environment .72 9 Multi-Party Call Control Data Definitions.73 9.1 Event Notification Data Definitions.73 9.2 Multi-Party Call Control Data Definitions .74 9.2.1 IpCallLeg 74 9.2.2 IpCallLegRef 74 9.2.3 IpAppCallLeg .74 9.2.4 IpAppCallLegRef .74 9.2.5 IpMultiPartyCall .74 9.2.6 IpMultiP

21、artyCallRef .74 ETSI ETSI ES 202 915-4-3 V1.4.1 (2006-12) 5 9.2.7 IpAppMultiPartyCall 74 9.2.8 IpAppMultiPartyCallRef 74 9.2.9 IpMultiPartyCallControlManager.74 9.2.10 IpMultiPartyCallControlManagerRef .74 9.2.11 IpAppMultiPartyCallControlManager74 9.2.12 IpAppMultiPartyCallControlManagerRef 74 9.2.

22、13 TpAppCallLegRefSet .74 9.2.14 TpMultiPartyCallIdentifier .75 9.2.15 TpAppMultiPartyCallBack.75 9.2.16 TpAppMultiPartyCallBackRefType .75 9.2.17 TpAppCallLegCallBack .75 9.2.18 TpMultiPartyCallIdentifierSet 75 9.2.19 TpCallAppInfo76 9.2.20 TpCallAppInfoType76 9.2.21 TpCallAppInfoSet.76 9.2.22 TpCa

23、llEventRequest .76 9.2.23 TpCallEventRequestSet 77 9.2.24 TpCallEventType77 9.2.25 TpAdditionalCallEventCriteria.79 9.2.26 TpCallEventInfo .79 9.2.27 TpCallAdditionalEventInfo 80 9.2.28 TpCallNotificationRequest .80 9.2.29 TpCallNotificationScope 80 9.2.30 TpCallNotificationInfo .80 9.2.31 TpCallNot

24、ificationReportScope .81 9.2.32 TpNotificationRequested 81 9.2.33 TpNotificationRequestedSet.81 9.2.34 TpReleaseCause81 9.2.35 TpReleaseCauseSet.81 9.2.36 TpCallLegIdentifier 81 9.2.37 TpCallLegIdentifierSet .82 9.2.38 TpCallLegAttachMechanism82 9.2.39 TpCallLegConnectionProperties.82 9.2.40 TpCallL

25、egInfoReport82 9.2.41 TpCallLegInfoType 83 9.2.42 TpCallLegSuperviseTreatment.83 9.2.43 TpCallHighProbabilityCompletion.83 9.2.44 TpNotificationRequestedSetEntry 83 9.2.45 TpCarrierSet .83 9.2.46 TpCarrier 83 9.2.47 TpCarrierID 84 9.2.48 TpCarrierSelectionField84 Annex A (normative): OMG IDL Descrip

26、tion of Multi-Party Call Control SCF85 Annex B (informative): W3C WSDL Description of Multi-Party Call Control SCF 86 Annex C (informative): Java API Description of the Call Control SCFs87 Annex D (informative): Contents of 3GPP OSA Rel-5 Call Control .88 Annex E (informative): Record of changes 89

27、E.1 Interfaces 89 E.1.1 New 89 E.1.2 Deprecated89 E.1.3 Removed.89 E.2 Methods90 E.2.1 New 90 E.2.2 Deprecated90 E.2.3 Modified.90 E.2.4 Removed.90 ETSI ETSI ES 202 915-4-3 V1.4.1 (2006-12) 6 E.3 Data Definitions .91 E.3.1 New 91 E.3.2 Modified.91 E.3.3 Removed.91 E.4 Service Properties.92 E.4.1 New

28、 92 E.4.2 Deprecated92 E.4.3 Modified.92 E.4.4 Removed.93 E.5 Exceptions 93 E.5.1 New 93 E.5.2 Modified.93 E.5.3 Removed.93 E.6 Others .94 History 95 ETSI ETSI ES 202 915-4-3 V1.4.1 (2006-12) 7 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been

29、 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“,

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

31、 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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advan

32、ced Networking (TISPAN). 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 202 915) is structured in the following parts: Part 1: “Overview“; Part 2: “Comm

33、on 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: “Multi-Media Call Control SCF“; Sub-part 5: “Conference Call Control SCF“; Part 5: “User I

34、nteraction SCF“; Part 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

35、 Availability Management SCF“. ETSI ETSI ES 202 915-4-3 V1.4.1 (2006-12) 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 th

36、e Parlay 4.3 set of specifications. The present document is equivalent to 3GPP TS 29.198-4-3 V5.10.0 (Release 5). ETSI ETSI ES 202 915-4-3 V1.4.1 (2006-12) 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 Servic

37、e 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 (SCF) aspects of th

38、e 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 of the interfaces

39、. 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 provisions which, thro

40、ugh 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 document, the terms and def

41、initions 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-3 V1.4.1 (2006-12) 104 MultiParty Call Control Service Sequence Diagrams 4.1 Application initiated call setup The following sequen

42、ce 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 call is being

43、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 parties (or more). A

44、fter 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 the A-party by en

45、tering 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:

46、 (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: createCallLeg( )14: new()AppPartyA : (IpAppMultiPartyCallLeg)AppPartyB : (IpAppMultiPart

47、yCallLeg)9: ev entReportRes ()17: ev entReportRes ()8: ro uteR eq( )16: routeReq( )12: sendInfoRes( ): IpUIManager10: createUICall( )19: deassignCall( )1: This message is used to create an object implementing the IpAppMultiPartyCall interface. 2: This message requests the object implementing the IpM

48、ultiPartyCallControlManager interface to create an object implementing the IpMultiPartyCall interface. 3: Assuming that the criteria for creating an object implementing the IpMultiPartyCall interface (e.g. load control values not exceeded) is met it is created. ETSI ETSI ES 202 915-4-3 V1.4.1 (2006-

49、12) 114: Once the object implementing the IpMultiPartyCall interface is created it is used to pass the reference of the object implementing the IpAppMultiPartyCall interface as the callback reference to the object implementing the IpMultiPartyCall interface. Note that the reference to the callback interface could already have been passed in the createCall. 5: This message instructs the object implementing the IpMultiPartyCall interface to create a call leg for customer A. 6: Assuming that the criteria for creating a