ETSI TR 129 998-4-1-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi.pdf

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

1、 ETSI TR 129 998-4-1 V9.0.0 (2010-01)Technical Report Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA);Application Programming Interface (API)Mapping for Open Service Access;Part 4: Call Control Service Mapping;Subp

2、art 1: API to CAP Mapping (3GPP TR 29.998-04-1 version 9.0.0 Release 9)ETSI ETSI TR 129 998-4-1 V9.0.0 (2010-01) 13GPP TR 29.998-04-1 version 9.0.0 Release 9 Reference RTR/TSGC-0029998-04-1v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92

3、 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 i

4、n 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 specif

5、ic 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 i

6、n 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 me

7、dia. 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 TR 129 998-4-1 V9.0.0 (2010-01) 23GPP TR 29.998

9、-04-1 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 0

10、00 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 Pol

11、icy, 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 Tec

12、hnical Report (TR) 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 ETSI deli

13、verables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TR 129 998-4-1 V9.0.0 (2010-01) 33GPP TR 29.998-04-1 version 9.0.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introducti

14、on 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Generic Call Control CAMEL Call Flows . 6g34.1 Call Control Manager . 6g34.1.1 enableCallNotification 6g34.1.2 disableCallNotification . 7g34.1.3 changeCallNotification . 8g34.1.4 getCri

15、teria . 9g34.1.5 setCallLoadControl . 9g34.1.6 callNotificationInterrupted 10g34.1.7 callNotificationContinued . 11g34.1.8 callAborted . 11g34.1.9 callEventNotify . 12g34.2 Call . 14g34.2.1 routeReq 14g34.2.2 routeRes 18g34.2.3 routeErr . 19g34.2.4 release . 20g34.2.5 deassignCall 21g34.2.6 getCallI

16、nfoReq 21g34.2.7 getCallInfoRes 22g34.2.8 getCallInfoErr . 23g34.2.9 superviseCallReq 24g34.2.10 superviseCallRes . 24g34.2.11 superviseCallErr . 25g34.2.12 setAdviceOfCharge . 26g34.2.13 setCallChargePlan . 27g34.2.14 callFaultDetected 28g34.2.15 callEnded 28g35 Detailed Parameter Mappings 29g35.1

17、TpCallMonitorMode 29g35.2 TpCallReportType 30g35.3 TpCallEventName 30g35.4 TpCallAdditionalReportInfo 31g3Annex A: Change history 32g3History 33g3ETSI ETSI TR 129 998-4-1 V9.0.0 (2010-01) 43GPP TR 29.998-04-1 version 9.0.0 Release 9 Foreword This Technical Report has been produced by the 3rdGenerati

18、on 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 document, it will be re-released by the TSG with an identifying change of release date and

19、 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. y the second digit is incremented for all changes of substance, i.e. technical en

20、hancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction Structure of the OSA API Mapping (3GPP TR 29.998) The present document is part 4 subpart 1 of a multi-part deliverable covering the Open Service Ac

21、cess (OSA); Application Programming Interface (API) Mapping for OSA. Table: Overview of the OSA APIs Application Programming Interface (API); Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for the Open Service Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“.

22、 4 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 5 3GPP TS 29.198-4-1/5: “Open Service Access (OSA); Application Programming Interface (API); 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“.

23、 Sub-part 4: “Multi-Media Call Control SCF“. Sub-part 5: “Conference call control SCF“. 6 3GPP TS 29.002: “Mobile Application Part (MAP) specification“. 7 3GPP TS 29.078: “Customised Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification“. 8 3GPP TS 22.101

24、: “Service Aspects; Service Principles“. 9 ITU-T Recommendation Q.850: “Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part“. 10 3GPP TR 29.998-1: “Open Service Access (OSA); Application Programming Interface (API) Mapping for

25、OSA; Part 1: General Issues on API Mapping“. ETSI ETSI TR 129 998-4-1 V9.0.0 (2010-01) 63GPP TR 29.998-04-1 version 9.0.0 Release 9 3 Definitions and 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

26、the purposes of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 Generic Call Control CAMEL Call Flows 4.1 Call Control Manager The generic call manager interface class provides the management functions to the generic call SCFs. The application programmer can use this interfac

27、e to create call objects and to enable or disable call-related event notifications. 4.1.1 enableCallNotification enableCallNotification is used to enable call notifications to be sent to the application. HLRgsmSCFSCS ApplicationenableCallNotificationMAP AnyTimeModificationFigure 4-1: Call Flow for e

28、nableCallNotification Two alternatives have been identified. 1. The application requests notifications to be enabled (see table 4-1). 2. HLR rejects CSI updates (see table 4-2). Table 4-1: Normal Operation Pre-conditions An agreement is established between the network operator and the service provid

29、er for the event notification to be enabled 1 The application invokes the enableCallNotification method 2 The gsmSCF sends a MAP AnyTimeModification to the HLR in order to Activate the necessary CAMEL Subscription Information (O-CSI, D-CSI, T-CSI, VT-CSI). NOTE: CAMEL phase 3 only allows for activat

30、ion/deactivation of the CSI and not modification of the contents of the CSIs. The O-CSI and D-CSI will be activated if the originating address is present and the T-CSI and VT-CSI will be activated if the destination address is present. ETSI ETSI TR 129 998-4-1 V9.0.0 (2010-01) 73GPP TR 29.998-04-1 v

31、ersion 9.0.0 Release 9 Table 4-2: Error condition Pre-conditions gsmSCF had previously sent a MAP AnyTimeModification message to the HLR as a result of an enableCallNotification request from the application 1 HLR rejects the request to update the CSI 2 The gsmSCF sends an internal message to the SCS

32、 to indicate the up date failure 3 The SCS invokes the exception on enableCallNotification Table 4-3: Parameter Mapping From: enableCallNotification To: MAP AnyTimeModification appInterface eventCriteria (TpCallEventCriteria) : DestinationAddress subscriberIdentity (see note) modificationRequestFor-

33、CSI OriginationAddress subscriberIdentity (see Note) modificationRequestFor-CSI CallEventName (TpCallEventName) CAMEL Subscription Information: - T-CSI; - VT-CSI; - O-CSI; - D-CSI. CallNotificationType assignmentID modificationRequestFor-SS-Info gsmSCF address NOTE: In case an address range is used,

34、 a separate MAP AnyTimeModificationRequest shall be sent for every address in the range. 4.1.2 disableCallNotification disableCallNotification is used by the application to disable call notifications. HLR ApplicationdisableCallNotificationMAP AnyTimeModificationRequestgsmSCFSCSFigure 4-2: Call Flow

35、for disableCallNotification Table 4-4: Normal Operation Pre-conditions An agreement is established between the network operator and the service provider for the event notification to be disabled 1 The application invokes the disableCallNotification method 2 The gsmSCF sends a MAP AnyTimeModification

36、 to the HLR in order to de-activate the CAMEL subscription Information (O-CSI, D-CSI, T-CSI, VT-CSI). NOTE: CAMEL Phase 3 only allows the capability to activate/deactivate CSI and not to modify the triggering information. The O-CSI and D-CSI will be deactivated if the originating address is present

37、and the T-CSI and VT-CSI will be deactivated if the destination address is present. ETSI ETSI TR 129 998-4-1 V9.0.0 (2010-01) 83GPP TR 29.998-04-1 version 9.0.0 Release 9 Table 4-5: Parameter Mapping From: disableCallNotification To: MAP AnyTimeModification assignmentID gsmSCFAddress 4.1.3 changeCal

38、lNotification changeCallNotification is used by the application to change the call notifications previously set by enableCallNotification(). HLR ApplicationchangeCallNotificationMAP AnyTimeModificationgsmSCF SCSFigure 4-3: Call Flow for changeCallNotification Table 4-6: Normal Operation Pre-conditio

39、ns Notifications have been enabled by the application. 1 The application invokes the changeCallNotification method 2 The gsmSCF sends a MAP AnyTimeModification to the HLR in order to active and de-activate the CAMEL subscription Information (O-CSI, T-CSI, VT-CSI). The SCS and gsmSCF will have to det

40、ermine which CSIs to active and which to de-activate in order to reflect the changed set of notifications. The O-CSI and D-CSI will be modified if the originating address is present and the T-CSI and VT-CSI will be modified if the destination address is present Table 4-7: Parameter Mapping From: cha

41、ngeCallNotification To: MAP AnyTimeModification assignmentID eventCriteria (TpCallEventCriteria): DestinationAddress subscriberIdentity (see note) modificationRequestFor-CSI OriginationAddress subscriberIdentity (see note) modificationRequestFor-CSI CallEventName (TpCallEventName) CAMEL Subscription

42、 Information: - T-CSI; - VT-CSI; - O-CSI; - D-CSI. CallNotificationType modificationRequestFor-SS-Info gsmSCFAddressNOTE: In case an address range is used, a separate MAP AnyTimeModificationRequest shall be sent for every address in the range ETSI ETSI TR 129 998-4-1 V9.0.0 (2010-01) 93GPP TR 29.998

43、-04-1 version 9.0.0 Release 9 4.1.4 getCriteria getCriteria is used by the application to query the event criteria set with enableCallNotification. HLR ApplicationgetCriteriagsmSCFSCSNo appropriate CAP orMAP messageFigure 4-4: Call Flow for getCriteria Table 4-8: Normal Operation Pre-conditions Noti

44、fications have been enabled by the application 1 The application invokes the getCriteria method 2 The SCS returns the criteria Parameter Mapping None. 4.1.5 setCallLoadControl setCallLoadControl is a method used to control the number of invoked methods i.e. to restrict the load placed on the applica

45、tion server. gsmSCF SCS ApplicationCAP CallGapsetCallLoadControlCAP CallGapgsmSSFFigure 4-5: Call Flow for release Table 4-9: Normal Operation Pre-conditions Call Control Manager is in active state 1 The application invokes the setCallLoadControl method 2 The SCS sends an equivalent message to the g

46、smSCF 3 The gsmSCF may invoke the CAP CallGap operations towards different gsmSSFs. CallGap can be sent in CAP only after the dialogue has been opened first by sending InitialDP. ETSI ETSI TR 129 998-4-1 V9.0.0 (2010-01) 103GPP TR 29.998-04-1 version 9.0.0 Release 9 Table 4-10: Parameter Mapping Fro

47、m: setCallLoadControl To: CAP CallGap duration gapIndicators duration mechanism callLoadControlPerInterval gapIndicators gapInterval treatment ReleaseCause AdditionalTreatmentInfo InformationToSend gapTreatment ReleaseCause InformationToSend addressRange gapCriteriabasicGapCriteria calledAddressValu

48、e assignmentID 4.1.6 callNotificationInterrupted callNotificationInterrupted indicates to the application that all event notifications have been interrupted, for example due to faults detected. HLR gsmSCF SCS ApplicationcallNotificationInterruptedNo appropriate MAP or CAPmessageFigure 4-6: Call Flow

49、 for callNotificationInterrupted Table 4-11: Normal Operation Pre-conditions Call notifications have been enabled using the enableNotification method on the Call Manager interface 1 The SCS has detected, or has been informed of, a fault which prevents further events from being notified 2 The SCS invokes the callNotificationInterrupted method Parameter Mapping None. ETSI ETSI TR 129 998-4-1 V9.0.0 (2010-01) 113GPP TR 29.998-04-1 version 9.0.0 Release 9 4.1.7 callNotificationContinued callNotificationContinued indicates to the application that all event no