1、 ETSI ES 204 915-4-2 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 4: Call Control;Sub-part 2: Generic Call Control SCF(Parlay 6)floppy3 ETSI ETSI ES 204 915-4-2 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01032-4-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 b
3、e 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 re
4、ference 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 documen
5、ts 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 permis
6、sion. 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 the
7、 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-2 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights6 Foreword.6 1 Scope 8 2 References 8 3 Definitions and abbreviations.8 3.1 Defi
8、nitions8 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 .12 4.4 Call Barring 1 .14 4.5 Number Translation 1.16 4.6 Number Translation 1 (with callbacks) 17 4.7 Number Translation 2.19 4.8 Number Trans
9、lation 3.21 4.9 Number Translation 4.23 4.10 Number Translation 5.25 4.11 Prepaid26 4.12 Pre-Paid with Advice of Charge (AoC)28 5 Class Diagrams.31 6 Generic Call Control Service Interface Classes .32 6.1 Interface Class IpCallControlManager.33 6.1.1 Method createCall() 33 6.1.2 Method enableCallNot
10、ification() 34 6.1.3 Method disableCallNotification() .35 6.1.4 Method setCallLoadControl().35 6.1.5 Method changeCallNotification() .36 6.1.6 Method getCriteria() .36 6.2 Interface Class IpAppCallControlManager 37 6.2.1 Method callAborted() .37 6.2.2 Method callEventNotify().37 6.2.3 Method callNot
11、ificationInterrupted()38 6.2.4 Method callNotificationContinued().38 6.2.5 Method callOverloadEncountered()39 6.2.6 Method callOverloadCeased() 39 6.2.7 Method abortMultipleCalls() 39 6.3 Interface Class IpCall .39 6.3.1 Method routeReq()40 6.3.2 Method release() .41 6.3.3 Method deassignCall()41 6.
12、3.4 Method getCallInfoReq()42 6.3.5 Method setCallChargePlan().42 6.3.6 Method setAdviceOfCharge().42 6.3.7 Method getMoreDialledDigitsReq().43 6.3.8 Method superviseCallReq() 43 6.3.9 Method continueProcessing() .43 6.4 Interface Class IpAppCall 44 6.4.1 Method routeRes() 44 6.4.2 Method routeErr()
13、.45 6.4.3 Method getCallInfoRes() 45 6.4.4 Method getCallInfoErr().45 6.4.5 Method superviseCallRes().46 ETSI ETSI ES 204 915-4-2 V1.1.1 (2008-05) 4 6.4.6 Method superviseCallErr() .46 6.4.7 Method callFaultDetected() 46 6.4.8 Method getMoreDialledDigitsRes() .47 6.4.9 Method getMoreDialledDigitsErr
14、() 47 6.4.10 Method callEnded() 47 7 Generic Call Control Service State Transition Diagrams.48 7.1 State Transition Diagrams for IpCallControlManager .48 7.1.1 Active State.48 7.1.2 Notification terminated State 48 7.2 State Transition Diagrams for IpCall49 7.2.1 Network Released State 49 7.2.2 Fini
15、shed State49 7.2.3 Application Released State .49 7.2.4 No Parties State.50 7.2.5 Active State.50 7.2.6 1 Party in Call State 50 7.2.7 2 Parties in Call State50 7.2.8 Routing to Destination(s) State.51 8 Generic Call Control Service Properties 51 8.1 List of Service Properties .51 8.2 Service Proper
16、ty values for the CAMEL Service Environment .52 9 Generic Call Control Data Definitions.53 9.1 Generic Call Control Event Notification Data Definitions.53 9.1.1 TpCallEventName 53 9.1.2 TpCallNotificationType54 9.1.3 TpCallEventCriteria54 9.1.4 TpCallEventInfo .54 9.2 Generic Call Control Data Defin
17、itions .54 9.2.1 IpCall 54 9.2.2 IpCallRef 54 9.2.3 IpAppCall .55 9.2.4 IpAppCallRef55 9.2.5 TpCallIdentifier 55 9.2.6 IpAppCallControlManager .55 9.2.7 IpAppCallControlManagerRef .55 9.2.8 IpCallControlManager 55 9.2.9 IpCallControlManagerRef 55 9.2.10 TpCallAppInfo55 9.2.11 TpCallAppInfoType56 9.2
18、.12 TpCallAppInfoSet.56 9.2.13 TpCallEndedReport 56 9.2.14 TpCallFault.56 9.2.15 TpCallInfoReport57 9.2.16 TpCallReleaseCause .57 9.2.17 TpCallReport 57 9.2.18 TpCallAdditionalReportInfo.58 9.2.19 TpCallReportRequest58 9.2.20 TpCallAdditionalReportCriteria .58 9.2.21 TpCallReportRequestSet 58 9.2.22
19、 TpCallReportType 59 9.2.23 TpCallTreatment.59 9.2.24 TpCallEventCriteriaResultSet.59 9.2.25 TpCallEventCriteriaResult59 Annex A (normative): OMG IDL Description of Generic Call Control SCF.60 Annex B (informative): W3C WSDL Description of Generic Call Control SCF .61 Annex C (informative): Java API
20、 Description of the Call Control SCFs62 ETSI ETSI ES 204 915-4-2 V1.1.1 (2008-05) 5 Annex D (informative): Contents of 3GPP OSA Rel-7 Call Control .63 Annex E (informative): Description of Call Control Sub-part 2: Generic call control SCF for 3GPP2 cdma2000 networks 64 E.1 General Exceptions.64 E.2
21、Specific Exceptions64 E.2.1 Clause 1: Scope 64 E.2.2 Clause 2: References 64 E.2.3 Clause 3: Definitions and abbreviations.64 E.2.4 Clause 4: Generic Call Control Service Sequence Diagrams .64 E.2.5 Clause 5: Class Diagrams.64 E.2.6 Clause 6: Generic Call Control Service Interface Classes64 E.2.7 Cl
22、ause 7: Generic Call Control Service State Transition Diagrams .65 E.2.8 Clause 8: Generic Call Control Service Properties.65 E.2.9 Clause 9: Generic Call Control Data Definitions .65 E.2.10 Annex A (normative): OMG IDL Description of Generic Call Control SCF 65 E.2.11 Annex B (informative): W3C WSD
23、L Description of Generic Call Control SCF.65 E.2.12 Annex C (informative): Java API Description of the Call Control SCFs.65 Annex F (informative): Record of changes 66 F.1 Interfaces 66 F.1.1 New 66 F.1.2 Deprecated66 F.1.3 Removed.66 F.2 Methods66 F.2.1 New 66 F.2.2 Deprecated66 F.2.3 Modified.67 F
24、.2.4 Removed.67 F.3 Data Definitions .67 F.3.1 New 67 F.3.2 Modified.67 F.3.3 Removed.67 F.4 Service Properties.67 F.4.1 New 67 F.4.2 Deprecated67 F.4.3 Modified.68 F.4.4 Removed.68 F.5 Exceptions 68 F.5.1 New 68 F.5.2 Modified.68 F.5.3 Removed.68 F.6 Others .68 History 69 ETSI ETSI ES 204 915-4-2 V
25、1.1.1 (2008-05) 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 and non-members, and can be found in ETSI SR 000 314: “Int
26、ellectual 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 Policy, no inve
27、stigation, 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 ETSI Standard (
28、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 Access (OSA); Application Programming Interface (API), as
29、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: “Generic Call Control SCF“; Sub-part 3: “Multi-Par
30、ty 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: “Generic Messaging SCF“; Part 10: “Connectivity Manage
31、r 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-2 V1.1.1 (2008-05) 7 The present document has been def
32、ined 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 is equivalent to 3GPP TS 29.198-4-2 V7.0.0 (Release
33、 7). ETSI ETSI ES 204 915-4-2 V1.1.1 (2008-05) 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
34、 of network 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
35、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. The process by which this task is accomplished is through
36、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 present document. ETSI ES 204 915-1: “Open Service Access (O
37、SA); 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 For the purposes of the present document, the abbreviations g
38、iven in ES 204 915-1 apply. ETSI ETSI ES 204 915-4-2 V1.1.1 (2008-05) 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
39、 be used, e.g. because the application crashed, the other call back interface is used instead. first instance : (Logical View:IpAppLogic)second instance : (Logic.: IpAppCallControlManager : IpAppCallControlManager : IpCallControlManager1: new()2: enableCallNotification( )3: new()4: enableCallNotific
40、ation( )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 en
41、ableCallNotification 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
42、 second 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. 5: When
43、 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 forwarded to the first instance of the logic
44、. ETSI ETSI ES 204 915-4-2 V1.1.1 (2008-05) 107: 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 availab
45、le). 9: 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 cer
46、tain time, 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:
47、sendInf oRes( )11: f orward ev ent12: release( )13: release( )1: 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 the IpCall interface. 3: Assuming that
48、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 “reminder message“. ETSI ETSI ES 204 91
49、5-4-2 V1.1.1 (2008-05) 115: 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, 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 re
