1、 ETSI ES 203 915-4-2 V1.2.1 (2007-01)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 4: Call Control;Sub-part 2: Generic Call Control SCF(Parlay 5)floppy3 ETSI ETSI ES 203 915-4-2 V1.2.1 (2007-01) 2 Reference RES/TISPAN-01029-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 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 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 203 915-4-2 V1.2.1 (2007-01) 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.14 4.6 Number Translat
9、ion 1 (with callbacks) 16 4.7 Number Translation 2.18 4.8 Number Translation 3.20 4.9 Number Translation 4.21 4.10 Number Translation 5.23 4.11 Prepaid24 4.12 Pre-Paid with Advice of Charge (AoC)26 5 Class Diagrams.29 6 Generic Call Control Service Interface Classes .30 6.1 Interface Class IpCallCon
10、trolManager.31 6.1.1 Method createCall() 31 6.1.2 Method enableCallNotification() 32 6.1.3 Method disableCallNotification() .33 6.1.4 Method setCallLoadControl().33 6.1.5 Method changeCallNotification() .34 6.1.6 Method getCriteria() .34 6.2 Interface Class IpAppCallControlManager 35 6.2.1 Method ca
11、llAborted() .35 6.2.2 Method callEventNotify().35 6.2.3 Method callNotificationInterrupted()36 6.2.4 Method callNotificationContinued().37 6.2.5 Method callOverloadEncountered()37 6.2.6 Method callOverloadCeased() 37 6.2.7 Method abortMultipleCalls()37 6.3 Interface Class IpCall .37 6.3.1 Method rou
12、teReq()38 6.3.2 Method release() .39 6.3.3 Method deassignCall()39 6.3.4 Method getCallInfoReq()40 6.3.5 Method setCallChargePlan().40 6.3.6 Method setAdviceOfCharge().40 6.3.7 Method getMoreDialledDigitsReq().41 6.3.8 Method superviseCallReq() 41 6.3.9 Method continueProcessing().41 6.4 Interface C
13、lass IpAppCall 42 6.4.1 Method routeRes() 42 6.4.2 Method routeErr().43 6.4.3 Method getCallInfoRes() 43 6.4.4 Method getCallInfoErr().43 6.4.5 Method superviseCallRes().44 ETSI ETSI ES 203 915-4-2 V1.2.1 (2007-01) 4 6.4.6 Method superviseCallErr() .44 6.4.7 Method callFaultDetected() 44 6.4.8 Metho
14、d getMoreDialledDigitsRes() .44 6.4.9 Method getMoreDialledDigitsErr() 45 6.4.10 Method callEnded() 45 7 Generic Call Control Service State Transition Diagrams.45 7.1 State Transition Diagrams for IpCallControlManager .45 7.1.1 Active State.46 7.1.2 Notification terminated State 46 7.2 State Transit
15、ion Diagrams for IpCall46 7.2.1 Network Released State 47 7.2.2 Finished State47 7.2.3 Application Released State .47 7.2.4 No Parties State.47 7.2.5 Active State.48 7.2.6 1 Party in Call State 48 7.2.7 2 Parties in Call State48 7.2.8 Routing to Destination(s) State.48 8 Generic Call Control Service
16、 Properties 49 8.1 List of Service Properties .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 TpCallEventCrit
17、eria53 9.1.4 TpCallEventInfo .53 9.2 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 IpCallContro
18、lManagerRef 54 9.2.10 TpCallAppInfo54 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 TpCallReport 56 9.2.17 TpCallAdditionalReportInfo.57 9.2.18 TpCallReportRequest57 9.2.19 TpCallAdditionalReportCriteria .57 9
19、.2.20 TpCallReportRequestSet 57 9.2.21 TpCallReportType 58 9.2.22 TpCallTreatment.58 9.2.23 TpCallEventCriteriaResultSet.58 9.2.24 TpCallEventCriteriaResult58 Annex A (normative): OMG IDL Description of Generic Call Control SCF.59 Annex B (informative): W3C WSDL Description of Generic Call Control S
20、CF .60 Annex C (informative): Java API Description of the Call Control SCFs61 Annex D (informative): Contents of 3GPP OSA Rel-6 Call Control .62 ETSI ETSI ES 203 915-4-2 V1.2.1 (2007-01) 5 Annex E (informative): Description of Call Control Sub-part 2: Generic call control SCF for 3GPP2 cdma2000 netw
21、orks 63 E.1 General Exceptions.63 E.2 Specific Exceptions63 E.2.1 Clause 1: Scope 63 E.2.2 Clause 2: References 63 E.2.3 Clause 3: Definitions and abbreviations.63 E.2.4 Clause 4: Generic Call Control Service Sequence Diagrams .63 E.2.5 Clause 5: Class Diagrams.63 E.2.6 Clause 6: Generic Call Contro
22、l Service Interface Classes63 E.2.7 Clause 7: Generic Call Control Service State Transition Diagrams .64 E.2.8 Clause 8: Generic Call Control Service Properties.64 E.2.9 Clause 9: Generic Call Control Data Definitions .64 E.2.10 Annex A (normative): OMG IDL Description of Generic Call Control SCF 64
23、 E.2.11 Annex B (informative): W3C WSDL Description of Generic Call Control SCF.64 E.2.12 Annex C (informative): Java API Description of the Call Control SCFs.64 Annex F (informative): Record of changes 65 F.1 Interfaces 65 F.1.1 New 65 F.1.2 Deprecated65 F.1.3 Removed.65 F.2 Methods65 F.2.1 New 65
24、F.2.2 Deprecated66 F.2.3 Modified.66 F.2.4 Removed.66 F.3 Data Definitions .66 F.3.1 New 66 F.3.2 Modified.66 F.3.3 Removed.67 F.4 Service Properties.67 F.4.1 New 67 F.4.2 Deprecated67 F.4.3 Modified.67 F.4.4 Removed.67 F.5 Exceptions 68 F.5.1 New 68 F.5.2 Modified.68 F.5.3 Removed.68 F.6 Others .68
25、 History 69 ETSI ETSI ES 203 915-4-2 V1.2.1 (2007-01) 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
26、 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/home.asp). Pu
27、rsuant 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 the present d
28、ocument. 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 Access (OSA); Applic
29、ation 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“; Part 3: “Framework“; Part 4: “Call Control“; Sub-part 1: “Call Control Common Definitions“; Sub-part 2: “Generic Cal
30、l 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: “Generic Messagi
31、ng 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“. ETSI ETSI ES 203 915-4-2 V1.2.1 (2007-01) 7 The present document has
32、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 5.1 set of specifications. The present document is equivalent to 3GPP TS 29.198-4-2 V6.4.0
33、(Release 6). ETSI ETSI ES 203 915-4-2 V1.2.1 (2007-01) 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
34、make use 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
35、. 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. The process by which this task is accomplished is
36、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 provisions which, through reference in this text, constitute provisions of the present document. ETSI ES 203 915-1: “Open Service A
37、ccess (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 5)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 203 915-1 apply. 3.2 Abbreviations For the purposes of the present document, the abbrevi
38、ations given in ES 203 915-1 apply. ETSI ETSI ES 203 915-4-2 V1.2.1 (2007-01) 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
39、 can not 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: enableCal
40、lNotification( )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
41、: The enableCallNotification 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
42、for this 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.
43、 5: 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 forwarded to the first instance of t
44、he logic. ETSI ETSI ES 203 915-4-2 V1.2.1 (2007-01) 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
45、 available). 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
46、at a certain 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: n
47、ew()10: sendInfoRes( )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: Assumin
48、g 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 reminder message. ETSI ETSI ES 2
49、03 915-4-2 V1.2.1 (2007-01) 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 thi
