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

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

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

2、 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 can

3、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, the r

4、eference 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 docume

5、nts 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 permi

6、ssion. 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 the

7、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-2 V1.4.1 (2006-12) 3 Contents Intellectual Property Rights6 Foreword

8、.6 1 Scope 8 2 References 8 3 Definitions and abbreviations.8 3.1 Definitions8 3.2 Abbreviations .8 4 Generic Call Control Service Sequence Diagrams.9 4.1 Additional Callbacks 9 4.2 Alarm Call10 4.3 Application Initiated Call .11 4.4 Call Barring 1 .13 4.5 Number Translation 1.15 4.6 Number Translat

9、ion 1 (with callbacks) 17 4.7 Number Translation 2.19 4.8 Number Translation 3.21 4.9 Number Translation 4.22 4.10 Number Translation 5.24 4.11 Prepaid25 4.12 Pre-Paid with Advice of Charge (AoC)27 5 Class Diagrams.30 6 Generic Call Control Service Interface Classes .31 6.1 Interface Class IpCallCon

10、trolManager.32 6.1.1 Method createCall() 32 6.1.2 Method enableCallNotification() 33 6.1.3 Method disableCallNotification() .34 6.1.4 Method setCallLoadControl().34 6.1.5 Method changeCallNotification() .35 6.1.6 Method getCriteria() .35 6.2 Interface Class IpAppCallControlManager 35 6.2.1 Method ca

11、llAborted() .36 6.2.2 Method callEventNotify().36 6.2.3 Method callNotificationInterrupted()37 6.2.4 Method callNotificationContinued().37 6.2.5 Method callOverloadEncountered()37 6.2.6 Method callOverloadCeased() 38 6.3 Interface Class IpCall .38 6.3.1 Method routeReq()39 6.3.2 Method release() .40

12、 6.3.3 Method deassignCall()40 6.3.4 Method getCallInfoReq()40 6.3.5 Method setCallChargePlan().41 6.3.6 Method setAdviceOfCharge().41 6.3.7 Method getMoreDialledDigitsReq().41 6.3.8 Method superviseCallReq() 42 6.3.9 Method continueProcessing().42 6.4 Interface Class IpAppCall 42 6.4.1 Method route

13、Res() 43 6.4.2 Method routeErr().43 6.4.3 Method getCallInfoRes() 44 6.4.4 Method getCallInfoErr().44 6.4.5 Method superviseCallRes().44 6.4.6 Method superviseCallErr() .45 ETSI ETSI ES 202 915-4-2 V1.4.1 (2006-12) 4 6.4.7 Method callFaultDetected() 45 6.4.8 Method getMoreDialledDigitsRes() .45 6.4.

14、9 Method getMoreDialledDigitsErr() 45 6.4.10 Method callEnded() 46 7 Generic Call Control Service State Transition Diagrams.46 7.1 State Transition Diagrams for IpCallControlManager .46 7.1.1 Active State.47 7.1.2 Notification terminated State 47 7.2 State Transition Diagrams for IpCall47 7.2.1 Netw

15、ork Released State 48 7.2.2 Finished State48 7.2.3 Application Released State .48 7.2.4 No Parties State.48 7.2.5 Active State.48 7.2.6 1 Party in Call State 48 7.2.7 2 Parties in Call State49 7.2.8 Routing to Destination(s) State.49 8 Generic Call Control Service Properties 49 8.1 List of Service P

16、roperties .49 8.2 Service Property values for the CAMEL Service Environment .50 9 Generic Call Control Data Definitions.51 9.1 Generic Call Control Event Notification Data Definitions.52 9.1.1 TpCallEventName 52 9.1.2 TpCallNotificationType52 9.1.3 TpCallEventCriteria53 9.1.4 TpCallEventInfo .53 9.2

17、 Generic Call Control Data Definitions .53 9.2.1 IpCall 53 9.2.2 IpCallRef 53 9.2.3 IpAppCall .53 9.2.4 IpAppCallRef53 9.2.5 TpCallIdentifier 54 9.2.6 IpAppCallControlManager .54 9.2.7 IpAppCallControlManagerRef .54 9.2.8 IpCallControlManager 54 9.2.9 IpCallControlManagerRef 54 9.2.10 TpCallAppInfo5

18、4 9.2.11 TpCallAppInfoType55 9.2.12 TpCallAppInfoSet.55 9.2.13 TpCallEndedReport 55 9.2.14 TpCallFault.55 9.2.15 TpCallInfoReport56 9.2.16 TpCallReleaseCause .56 9.2.17 TpCallReport 56 9.2.18 TpCallAdditionalReportInfo.57 9.2.19 TpCallReportRequest57 9.2.20 TpCallAdditionalReportCriteria .57 9.2.21

19、TpCallReportRequestSet 57 9.2.22 TpCallReportType 58 9.2.23 TpCallTreatment.58 9.2.24 TpCallEventCriteriaResultSet.58 9.2.25 TpCallEventCriteriaResult58 Annex A (normative): OMG IDL Description of Generic Call Control SCF.59 Annex B (informative): W3C WSDL Description of Generic Call Control SCF .60

20、 Annex C (informative): Java API Description of the Call Control SCFs61 Annex D (informative): Contents of 3GPP OSA Rel-5 Call Control .62 ETSI ETSI ES 202 915-4-2 V1.4.1 (2006-12) 5 Annex E (informative): Record of changes 63 E1 Interfaces 63 E.1.1 New 63 E.1.2 Deprecated63 E.1.3 Removed.63 E.2 Met

21、hods64 E.2.1 New 64 E.2.2 Deprecated64 E.2.3 Modified.64 E.2.4 Removed.64 E.3 Data Definitions .65 E.3.1 New 65 E.3.2 Modified.65 E.3.3 Removed.65 E.4 Service Properties.66 E.4.1 New 66 E.4.2 Deprecated66 E.4.3 Modified.66 E.4.4 Removed.66 E.5 Exceptions 67 E.5.1 New 67 E.5.2 Modified.67 E.5.3 Remov

22、ed.67 E.6 Others .67 History 68 ETSI ETSI ES 202 915-4-2 V1.4.1 (2006-12) 6 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

23、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 from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.o

24、rg/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 ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essent

25、ial 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 (TISPAN). The present document is part 4, sub-part 2 of a multi-part deliverable covering Open Service

26、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: “Common Data Definitions“; Part 3: “Framework“; Part 4: “Call Control“; Sub-part 1: “Call Control Common Definitions“; Sub-

27、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“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities SCF“; Part 8: “Data Session Control SCF“; Part

28、 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 Management SCF“. ETSI ETSI ES 202 915-4-2 V1.4.1 (2006-12) 7 The present document has been defined joint

29、ly 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 4.3 set of specifications. The present document is equivalent to 3GPP TS 29.198-4-2 V5.9.0 (Release 5). ETSI

30、ETSI ES 202 915-4-2 V1.4.1 (2006-12) 8 1 Scope The present document is part 4, sub-part 2 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers to make use of networ

31、k functionality through an open standardised interface, i.e. the OSA APIs. The present document specifies the Generic Call Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Generic Call Control SCF are defined here, these being: Sequence Diagrams. Class Diagrams.

32、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. The process by which this task is accomplished is through the use of

33、 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, through reference in this text, constitute provisions of the present document. ETSI ES 202 915-1: “Open Service Access (OSA); Appli

34、cation 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 definitions given in ES 202 915-1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in

35、ES 202 915-1 apply. ETSI ETSI ES 202 915-4-2 V1.4.1 (2006-12) 9 4 Generic Call Control Service Sequence Diagrams 4.1 Additional Callbacks The following sequence diagram shows how an application can register two call back interfaces for the same set of events. If one of the call backs can not be used

36、, e.g. because the application crashed, the other call back interface is used instead. first instance : (Logical View:IpAppLogic)second instance : (Logic.: IpAppCallControlManager : IpAppCal lControlManager : IpCallControlManager1: new()2: enableCallNotification( )3: new()4: enableCallNotification(

37、)8: callEventNotify( )9: “forward event“5: callEventNotify( )7: “call Notify result: failure“6: forward event1: The first instance of the application is started on node 1. The application creates a new IpAppCallControlManager to handle callbacks for this first instance of the logic. 2: The enableCal

38、lNotification is associated with an applicationID. The call control manager uses the applicationID to decide whether this is the same application. 3: The second instance of the application is started on node 2. The application creates a new IpAppCallControlManager to handle callbacks for this second

39、 instance of the logic. 4: The same enableCallNotification request is sent as for the first instance of the logic. Because both requests are associated with the same application, the second request is not rejected, but the specified callback object is stored as an additional callback. ETSI ETSI ES 2

40、02 915-4-2 V1.4.1 (2006-12) 105: When the trigger occurs one of the first instance of the application is notified. The gateway may have different policies on how to handle additional callbacks, e.g. always first try the first registered or use some kind of round robin scheme. 6: The event is forward

41、ed to the first instance of the logic. 7: When the first instance of the application is overloaded or unavailable this is communicated with an exception to the call control manager. 8: Based on this exception the call control manager will notify another instance of the application (if available). 9:

42、 The event is forwarded to the second instance of the logic. 4.2 Alarm Call The following sequence diagram shows a reminder message, in the form of an alarm, being delivered to a customer as a result of a trigger from an application. Typically, the application would be set to trigger at a certain ti

43、me, however, the application could also trigger on events. : IpCallControlManager: IpAppCall : IpCall : IpUICall : IpAppUIManager: IpAppUICall: (Logical View:IpAppLogic)1: new()2: createCall( )3: new()4: routeReq( )5: routeRes( )9: sendInfoReq( )6: f orward ev ent7: createUICall()8: new()10: sendInf

44、 oRes( )11: f orward ev ent12: release( )13: release( )ETSI ETSI ES 202 915-4-2 V1.4.1 (2006-12) 111: This message is used to create an object implementing the IpAppCall interface. 2: This message requests the object implementing the IpCallControlManager interface to create an object implementing th

45、e IpCall interface. 3: Assuming that the criteria for creating an object implementing the IpCall interface (e.g. load control values not exceeded) is met it is created. 4: This message instructs the object implementing the IpCall interface to route the call to the customer destined to receive the “r

46、eminder message“. 5: This message passes the result of the call being answered to its callback object. 6: This message is used to forward the previous message to the IpAppLogic. 7: The application requests a new UICall object that is associated with the call object. 8: Assuming all criteria are met,

47、 a new UICall object is created by the service. 9: This message instructs the object implementing the IpUICall interface to send the alarm to the customers call. 10: When the announcement ends this is reported to the call back interface. 11: The event is forwarded to the application logic. 12: The a

48、pplication releases the UICall object, since no further announcements are required. Alternatively, the application could have indicated P_FINAL_REQUEST in the sendInfoReq in which case the UICall object would have been implicitly released after the announcement was played. 13: The application releas

49、es the call and all associated parties. 4.3 Application Initiated Call The following sequence diagram shows an application creating a call between party A and party B. This sequence could be done after a customer has accessed a Web page and selected a name on the page of a person or organisation to talk to. ETSI ETSI ES 202 915-4-2 V1.4.1 (2006-12) 12: IpCallControlManager: IpAppCall : IpCall : (Logical View:IpAppLo.5: routeRes( )1: new()2: createCall( )3: new()4: routeReq( )7: routeReq( )8: routeR