ETSI TR 129 998-4-1-2004 Universal Mobile Telecommunications System (UMTS) Open Service Access (OSA) Application Programming Interface (API) Mapping for Open Service Access Part 4 .pdf

1、 ETSI TR 129 998-4-1 V6.0.0 (2004-12)Technical Report Universal Mobile Telecommunications System (UMTS);Open Service Access (OSA)Application Programming Interface (API)Mapping for Open Service Access;Part 4: Call Control Service Mapping;Sub-part 1: API to CAP Mapping(3GPP TR 29.998-04-1 version 6.0.

2、0 Release 6)ETSI ETSI TR 129 998-4-1 V6.0.0 (2004-12) 1 3GPP TR 29.998-04-1 version 6.0.0 Release 6 Reference RTR/TSGN-0529998-04-1v600 Keywords UMTS 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

3、 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 in more than one electronic version or in print. In any case of exist

4、ing 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 specific network drive within ETSI Secretariat. Users of the present docum

5、ent 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 in the present document, please send your comment to one of the follo

6、wing 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 media. European Telecommunications Standards Institute 2004. All right

7、s reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the 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

8、 the 3GPP Organizational Partners. ETSI ETSI TR 129 998-4-1 V6.0.0 (2004-12) 2 3GPP TR 29.998-04-1 version 6.0.0 Release 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,

9、if any, is publicly available for ETSI members 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 availa

10、ble on the ETSI Web server (http:/webapp.etsi.org/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 serv

11、er) which are, or may be, or may become, essential to the present document. Foreword This Technical 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 G

12、SM identities. These should be interpreted as being references to the corresponding ETSI deliverables. 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 V6.0.0 (2004-12) 3 3GPP TR 29.998-04-1 version

13、6.0.0 Release 6 Contents Intellectual Property Rights2 Foreword.2 Foreword.4 Introduction 4 1 Scope 5 2 References 5 3 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .6 4 Generic Call Control CAMEL Call Flows.6 4.1 Call Control Manager.6 4.1.1 enableCallNotification6 4.1.2 disabl

14、eCallNotification .7 4.1.3 changeCallNotification .7 4.1.4 getCriteria .8 4.1.5 setCallLoadControl.9 4.1.6 callNotificationInterrupted10 4.1.7 callNotificationContinued.10 4.1.8 callAborted .11 4.1.9 callEventNotify.11 4.2 Call .13 4.2.1 routeReq13 4.2.2 routeRes 17 4.2.3 routeErr.18 4.2.4 release .

15、19 4.2.5 deassignCall20 4.2.6 getCallInfoReq20 4.2.7 getCallInfoRes 21 4.2.8 getCallInfoErr.22 4.2.9 superviseCallReq 23 4.2.10 superviseCallRes.23 4.2.11 superviseCallErr .24 4.2.12 setAdviceOfCharge.25 4.2.13 setCallChargePlan.26 4.2.14 callFaultDetected 27 4.2.15 callEnded 27 5 Detailed Parameter

16、 Mappings 28 5.1 TpCallMonitorMode 28 5.2 TpCallReportType29 5.3 TpCallEventName29 5.4 TpCallAdditionalReportInfo 30 Annex A: Change history 31 History 32 ETSI ETSI TR 129 998-4-1 V6.0.0 (2004-12) 4 3GPP TR 29.998-04-1 version 6.0.0 Release 6 Foreword This Technical Report has been produced by the 3

17、rdGeneration 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 releas

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

19、chnical enhancements, 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 3rdGe

20、neration Partnership Project; Technical Specification Group Core Network; Open Service Access (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 Ope

21、n Service Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 5 3GPP TS 29.198-4: “Open Service Access (OSA); Application Programming Interface (API); Part 4: Call control“. 6 3GPP TS 29.002: “Mobile Application Part

22、 (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: “Service Aspects; Service Principles“. 9 ITU-T Recommendation Q.850: “Usage of cause and location in the Digital Subscriber Sign

23、alling 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 OSA; Part 1: General Issues on API Mapping“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present docum

24、ent, the terms and definitions given in TS 29.198-1 1 apply. ETSI ETSI TR 129 998-4-1 V6.0.0 (2004-12) 6 3GPP TR 29.998-04-1 version 6.0.0 Release 6 3.2 Abbreviations For 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

25、 Call Control Manager The generic call manager interface class provides the management functions to the generic call SCFs. The application programmer can use this interface to create call objects and to enable or disable call-related event notifications. 4.1.1 enableCallNotification enableCallNotifi

26、cation is used to enable call notifications to be sent to the application. HLRgsmSCFSCS ApplicationenableCallNotificationMAP AnyTimeModificationFigure 4-1: Call Flow for enableCallNotification Two alternatives have been identified. 1. The application requests notifications to be enabled (see table 4

27、-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 provider for the event notification to be enabled 1 The application invokes the enableCallNotification method 2 The gsmSCF sends a MAP

28、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 activation/deactivation of the CSI and not modification of the contents of the CSIs. The O-CSI and D-CSI will be activated if the origin

29、ating address is present and the T-CSI and VT-CSI will be activated if the destination address is present. 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 rej

30、ects the request to update the CSI 2 The gsmSCF sends an internal message to the SCS to indicate the up date failure 3 The SCS invokes the exception on enableCallNotification ETSI ETSI TR 129 998-4-1 V6.0.0 (2004-12) 7 3GPP TR 29.998-04-1 version 6.0.0 Release 6 Table 4-3: Parameter Mapping From: en

31、ableCallNotification To: MAP AnyTimeModification appInterface eventCriteria (TpCallEventCriteria) : DestinationAddress subscriberIdentity (see note) modificationRequestFor-CSI OriginationAddress subscriberIdentity (see Note) modificationRequestFor-CSI CallEventName (TpCallEventName) CAMEL Subscripti

32、on Information: - T-CSI; - VT-CSI; - O-CSI; - D-CSI. CallNotificationType assignmentID modificationRequestFor-SS-Info gsmSCF address NOTE: In case an address range is used, a separate MAP AnyTimeModificationRequest shall be sent for every address in the range. 4.1.2 disableCallNotification disableCa

33、llNotification is used by the application to disable call notifications. HLR ApplicationdisableCallNotificationMAP AnyTimeModificationRequestgsmSCFSCSFigure 4-2: Call Flow for disableCallNotification Table 4-4: Normal Operation Pre-conditions An agreement is established between the network operator

34、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 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 a

35、llows 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 and the T-CSI and VT-CSI will be deactivated if the destination address is present. Table 4-5: Parameter Mapping From: disableCa

36、llNotification To: MAP AnyTimeModification assignmentID gsmSCFAddress 4.1.3 changeCallNotification changeCallNotification is used by the application to change the call notifications previously set by enableCallNotification(). ETSI ETSI TR 129 998-4-1 V6.0.0 (2004-12) 8 3GPP TR 29.998-04-1 version 6.

37、0.0 Release 6 HLR ApplicationchangeCallNotificationMAP AnyTimeModificationgsmSCF SCSFigure 4-3: Call Flow for changeCallNotification Table 4-6: Normal Operation Pre-conditions Notifications have been enabled by the application. 1 The application invokes the changeCallNotification method 2 The gsmSCF

38、 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 determine which CSIs to active and which to de-activate in order to reflect the changed set of notifications. The O-CSI and D-CSI

39、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: changeCallNotification To: MAP AnyTimeModification assignmentID eventCriteria (TpCallEventCriteria): DestinationAddress subscriber

40、Identity (see note) modificationRequestFor-CSI OriginationAddress subscriberIdentity (see note) modificationRequestFor-CSI CallEventName (TpCallEventName) CAMEL Subscription Information: - T-CSI; - VT-CSI; - O-CSI; - D-CSI. CallNotificationType modificationRequestFor-SS-Info gsmSCFAddress NOTE: In c

41、ase an address range is used, a separate MAP AnyTimeModificationRequest shall be sent for every address in the range 4.1.4 getCriteria getCriteria is used by the application to query the event criteria set with enableCallNotification. HLR ApplicationgetCriteriagsmSCFSCSNo appropriate CAP orMAP messa

42、geFigure 4-4: Call Flow for getCriteria ETSI ETSI TR 129 998-4-1 V6.0.0 (2004-12) 9 3GPP TR 29.998-04-1 version 6.0.0 Release 6 Table 4-8: Normal Operation Pre-conditions Notifications have been enabled by the application 1 The application invokes the getCriteria method 2 The SCS returns the criteri

43、a 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 application server. gsmSCF SCS ApplicationCAP CallGapsetCallLoadControlCAP CallGapgsmSSFFigure 4-5: Call Flow for release Table 4-9:

44、 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 gsmSCF 3 The gsmSCF may invoke the CAP CallGap operations towards different gsmSSFs. CallGap can be sent in CAP only after the

45、 dialogue has been opened first by sending InitialDP. Table 4-10: Parameter Mapping From: setCallLoadControl To: CAP CallGap duration gapIndicators duration mechanism callLoadControlPerInterval gapIndicators gapInterval treatment ReleaseCause AdditionalTreatmentInfo InformationToSend gapTreatment Re

46、leaseCause InformationToSend addressRange gapCriteria basicGapCriteria calledAddressValue assignmentID ETSI ETSI TR 129 998-4-1 V6.0.0 (2004-12) 103GPP TR 29.998-04-1 version 6.0.0 Release 6 4.1.6 callNotificationInterrupted callNotificationInterrupted indicates to the application that all event not

47、ifications have been interrupted, for example due to faults detected. HLR gsmSCF SCS ApplicationcallNotificationInterruptedNo appropriate MAP or CAPmessageFigure 4-6: Call Flow for callNotificationInterrupted Table 4-11: Normal Operation Pre-conditions Call notifications have been enabled using the

48、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. 4.1.7 callNotificationContinued callNotificationContinue

49、d indicates to the application that all event notifications have been previously interrupted, have now started again. HLR gsmSCF SCS ApplicationcallNotificationContinuedNo appropriate MAP or CAPmessageFigure 4-7: Call Flow for callNotificationContinued Table 4-12: Normal Operation Pre-conditions Call notifications have been interrupted and callNotificationInterrupted method has been invoked 1 The SCS detects that call notifications are again possible. 2 The SCS invokes the callNotificationContinued method Parameter Mapping None. ETSI ETSI TR 129 998-4-1 V6