ETSI TS 129 198-4-2-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi_1.pdf

《ETSI TS 129 198-4-2-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 129 198-4-2-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi_1.pdf（71页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 129 198-4-2 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA)Application Programming Interface (API);Part 4: Call control;Subpart 2: Generic call control Service Capab

2、ility Feature (SCF) (3GPP TS 29.198-04-2 version 9.0.0 Release 9)floppy3ETSI ETSI TS 129 198-4-2 V9.0.0 (2010-01) 13GPP TS 29.198-04-2 version 9.0.0 Release 9 Reference RTS/TSGC-0029198-04-2v900 Keywords GSM, LTE, ULTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 9

3、2 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 be downloaded from: http:/www.etsi.org The present document may be made available

4、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 reference shall be the printing on ETSI printers of the PDF version kept on a speci

5、fic 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 documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors

6、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 permission. The copyright and the foregoing restriction extend to reproduction in all m

7、edia. European Telecommunications Standards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of

8、 the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 198-4-2 V9.0.0 (2010-01) 23GPP TS 29.19

9、8-04-2 version 9.0.0 Release 9 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

10、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). Pursuant to the ETSI IPR Po

11、licy, 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 document. Foreword This Te

12、chnical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding E

13、TSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 198-4-2 V9.0.0 (2010-01) 33GPP TS 29.198-04-2 version 9.0.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 6g3In

14、troduction 6g31 Scope 8g32 References 8g33 Definitions and abbreviations . 9g33.1 Definitions 9g33.2 Abbreviations . 9g34 Generic Call Control Service Sequence Diagrams . 9g34.1 Additional Callbacks 9g34.2 Alarm Call 11g34.3 Application Initiated Call . 12g34.4 Call Barring 1 . 14g34.5 Number Transl

15、ation 1 . 16g34.6 Number Translation 1 (with callbacks) 18g34.7 Number Translation 2 . 20g34.8 Number Translation 3 . 22g34.9 Number Translation 4 . 24g34.10 Number Translation 5 . 26g34.11 Prepaid 27g34.12 Pre-Paid with Advice of Charge (AoC) 29g35 Class Diagrams . 32g36 Generic Call Control Servic

16、e Interface Classes . 33g36.1 Interface Class IpCallControlManager . 34g36.1.1 Method createCall() 34g36.1.2 Method enableCallNotification() 35g36.1.3 Method disableCallNotification() . 36g36.1.4 Method setCallLoadControl() . 36g36.1.5 Method changeCallNotification() . 37g36.1.6 Method getCriteria()

17、 . 38g36.2 Interface Class IpAppCallControlManager 38g36.2.1 Method callAborted() . 39g36.2.2 Method callEventNotify() . 39g36.2.3 Method callNotificationInterrupted() 40g36.2.4 Method callNotificationContinued() . 40g36.2.5 Method callOverloadEncountered() 40g36.2.6 Method callOverloadCeased() 40g3

18、6.2.7 Method abortMultipleCalls() 41g36.3 Interface Class IpCall . 41g36.3.1 Method routeReq() 42g36.3.2 Method release() . 43g36.3.3 Method deassignCall() 43g36.3.4 Method getCallInfoReq() 44g36.3.5 Method setCallChargePlan() . 44g36.3.6 Method setAdviceOfCharge() . 44g36.3.7 Method getMoreDialledD

19、igitsReq() . 45g36.3.8 Method superviseCallReq() 45g36.3.9 Method continueProcessing() . 45g36.4 Interface Class IpAppCall 46g36.4.1 Method routeRes() 46g3ETSI ETSI TS 129 198-4-2 V9.0.0 (2010-01) 43GPP TS 29.198-04-2 version 9.0.0 Release 9 6.4.2 Method routeErr() . 47g36.4.3 Method getCallInfoRes(

20、) 47g36.4.4 Method getCallInfoErr() . 47g36.4.5 Method superviseCallRes() . 48g36.4.6 Method superviseCallErr() . 48g36.4.7 Method callFaultDetected() 48g36.4.8 Method getMoreDialledDigitsRes() . 49g36.4.9 Method getMoreDialledDigitsErr() 49g36.4.10 Method callEnded() 49g37 Generic Call Control Serv

21、ice State Transition Diagrams . 50g37.1 State Transition Diagrams for IpCallControlManager . 50g37.1.1 Active State . 50g37.1.2 Notification terminated State 50g37.2 State Transition Diagrams for IpCall 50g37.2.1 Network Released State 51g37.2.2 Finished State 51g37.2.3 Application Released State .

22、51g37.2.4 Active State. 52g37.2.5 1 Party in Call State 52g37.2.6 2 Parties in Call State 52g37.2.7 No Parties State . 52g37.2.8 Routing to Destination(s) State . 53g38 Generic Call Control Service Properties 54g38.1 List of Service Properties . 54g38.2 Service Property values for the CAMEL Service

23、Environment. 55g39 Generic Call Control Data Definitions . 56g39.1 Generic Call Control Event Notification Data Definitions . 56g39.1.1 TpCallEventName 56g39.1.2 TpCallNotificationType 57g39.1.3 TpCallEventCriteria 57g39.1.4 TpCallEventInfo . 57g39.2 Generic Call Control Data Definitions . 57g39.2.1

24、 IpCall 57g39.2.2 IpCallRef 57g39.2.3 IpAppCall . 58g39.2.4 IpAppCallRef 58g39.2.5 TpCallIdentifier 58g39.2.6 IpAppCallControlManager . 58g39.2.7 IpAppCallControlManagerRef . 58g39.2.8 IpCallControlManager 58g39.2.9 IpCallControlManagerRef 58g39.2.10 TpCallAppInfo 58g39.2.11 TpCallAppInfoType 59g39.

25、2.12 TpCallAppInfoSet . 59g39.2.13 TpCallEndedReport 59g39.2.14 TpCallFault . 59g39.2.15 TpCallInfoReport 60g39.2.16 TpCallReleaseCause . 60g39.2.17 TpCallReport 61g39.2.18 TpCallAdditionalReportInfo . 61g39.2.19 TpCallReportRequest 61g39.2.20 TpCallAdditionalReportCriteria . 62g39.2.21 TpCallReport

26、RequestSet 62g39.2.22 TpCallReportType 62g39.2.23 TpCallTreatment . 63g39.2.24 TpCallEventCriteriaResultSet. 63g39.2.25 TpCallEventCriteriaResult 63g3Annex A (normative): OMG IDL Description of Generic Call Control SCF . 64g3ETSI ETSI TS 129 198-4-2 V9.0.0 (2010-01) 53GPP TS 29.198-04-2 version 9.0.

27、0 Release 9 Annex B (informative): W3C WSDL Description of Generic Call Control SCF . 65g3Annex C (informative): Java API Description of the Call Control SCFs 66g3Annex D (informative): Description of Call Control Sub-part 2: Generic call control SCF for 3GPP2 cdma2000 networks 67g3D.1 General Excep

28、tions. 67g3D.2 Specific Exceptions 67g3D.2.1 Clause 1: Scope 67g3D.2.2 Clause 2: References 67g3D.2.3 Clause 3: Definitions and abbreviations . 67g3D.2.4 Clause 4: Generic Call Control Service Sequence Diagrams . 67g3D.2.5 Clause 5: Class Diagrams . 67g3D.2.6 Clause 6: Generic Call Control Service I

29、nterface Classes 68g3D.2.7 Clause 7: Generic Call Control Service State Transition Diagrams . 68g3D.2.8 Clause 8: Generic Call Control Service Properties . 68g3D.2.9 Clause 9: Generic Call Control Data Definitions . 68g3D.2.10 Annex A (normative): OMG IDL Description of Generic Call Control SCF 68g3

30、D.2.11 Annex B (informative): W3C WSDL Description of Generic Call Control SCF. 68g3D.2.12 Annex C (informative): Java API Description of the Call Control SCFs . 68g3Annex E (informative): Change history . 69g3History 70g3ETSI ETSI TS 129 198-4-2 V9.0.0 (2010-01) 63GPP TS 29.198-04-2 version 9.0.0 R

31、elease 9 Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present documen

32、t, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control

33、. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 4, sub-part 2 of a multi-part TS co

34、vering the 3rdGeneration Partnership Project: Technical Specification Group Core Network; Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (3GPP TS 29.198) is structured in the following Parts: Part 1: “Overview“; Part 2: “Common Data Def

35、initions“; 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

36、SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities SCF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SCF“; (not part of 3GPP Release 8) Part 10: “Connectivity Manager SCF“; (new in 3GPP Release 8) Part 11: “Account Management SCF“; Part 12: “Charging SCF“. Part 13: “Poli

37、cy Management SCF“; Part 14: “Presence and Availability Management SCF“; Part 15 “Multi Media Messaging SCF“; Part 16: “Service Broker SCF“. . The Mapping specification of the OSA APIs and network protocols (3GPP TR 29.998) is also structured as above. A mapping to network protocols is however not a

38、pplicable for all Parts, but the numbering of Parts is kept. Also in case a Part is not supported in a Release, the numbering of the parts is maintained. ETSI ETSI TS 129 198-4-2 V9.0.0 (2010-01) 73GPP TS 29.198-04-2 version 9.0.0 Release 9 Table: Overview of the OSA APIs Application Programming Int

39、erface; Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for the Open Services Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TS 22.002: “Circuit Bearer Services Supported by a PLMN“. 5 ISO 4217 (1995): “Codes for the representation of currencies and

40、funds “. 6 3GPP TS 24.002: “GSM-UMTS Public Land Mobile Network (PLMN) Access Reference Configuration“. 7 3GPP TS 22.003: “Circuit Teleservices supported by a Public Land Mobile Network (PLMN)“. ETSI ETSI TS 129 198-4-2 V9.0.0 (2010-01) 93GPP TS 29.198-04-2 version 9.0.0 Release 9 3 Definitions and

41、abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 29.198-1 1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 Generic Call Control Service Sequence Diagrams The Generic Cal

42、l Control API of 3GPP Rel.4 relies on the CAMEL Service Environment (CSE) and thus some restrictions exist to the use of the interface. The most significant one is that there is no support for createCall method. The detailed description of the supported methods and further restrictions is given in t

43、he chapter 8. 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, e.g. because the application crashed, the other call back interface is used instead. ETSI ETSI TS

44、 129 198-4-2 V9.0.0 (2010-01) 103GPP TS 29.198-04-2 version 9.0.0 Release 9 first instance : (Logical View:IpAppLogic)second instance : (Logic.: IpAppCallControlManager : IpAppCal lControlManager : IpCallControlManager1: new()2: enableCallNotification( )3: new()4: enableCallNotification( )8: callEve

45、ntNotify( )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 enableCallNotificati

46、on 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 instance o

47、f 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 the trigger occur

48、s 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. 7: When the fir

49、st 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: The event is forwarded to the second instance of the logic. ETSI ETSI TS 129 198-4-2 V9.0.0 (2010-01) 113GPP TS 29.198-04-2 version 9.0.0 Release 9 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 a