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

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

1、 ETSI TR 129 998-8 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 8: Data Session Control Service Mappin

2、g to CAP (3GPP TR 29.998-08 version 9.0.0 Release 9)ETSI ETSI TR 129 998-8 V9.0.0 (2010-01)13GPP TR 29.998-08 version 9.0.0 Release 9Reference RTR/TSGC-0029998-08v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65

3、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 in more than one electronic

4、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 specific network drive within ETS

5、I 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 in the present document, ple

6、ase 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 media. European Telecommunica

7、tions 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 the 3GPP Organizational Par

8、tners. 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-8 V9.0.0 (2010-01)23GPP TR 29.998-08 version 9.0.0 Release 9Int

9、ellectual 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: “Intellectual Property Ri

10、ghts (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 investigation, including

11、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 Technical Report (TR) has been produ

12、ced 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 deliverables. The cross reference bet

13、ween GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TR 129 998-8 V9.0.0 (2010-01)33GPP TR 29.998-08 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Defi

14、nitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Data Session Control Service CAMEL Call Flows 6g34.1 Data Session Manager 6g34.1.1 enableDataSessionNotification . 6g34.1.2 disableDataSessionNotification 6g34.1.3 dataSessionEventNotify 7g34.1.4 dataSessionAborted 8g34.1.5 d

15、ataSessionNotificationInterrupted . 8g34.1.6 dataSessionNotificationContinued 9g34.2 Data Session . 9g34.2.1 ConnectReq. 10g34.2.2 connectRes 11g34.2.3 connectErr. 11g34.2.4 release . 12g34.2.5 superviseDataSessionReq . 13g34.2.6 superviseDataSessionRes 13g34.2.7 superviseDataSessionErr 14g34.2.8 da

16、taSessionFaultDetected . 15g34.2.9 setAdviceOfCharge . 15g34.2.10 setDataSessionChargePlan 16g3Annex A: Change history 17g3History 18g3ETSI ETSI TR 129 998-8 V9.0.0 (2010-01)43GPP TR 29.998-08 version 9.0.0 Release 9Foreword This Technical Report has been produced by the 3rdGeneration Partnership Pr

17、oject (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 an increase in v

18、ersion 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 enhancements, corre

19、ctions, 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 8 of a multi-part deliverable covering the Open Service Access (OSA); Application Pro

20、gramming 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 Services Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TR 21.905: “Vocabu

21、lary for 3GPP Specifications“. 5 3GPP TS 29.198-8: “Open Service Access (OSA); Application Programming Interface (API); Part 8: Data session control“. 6 3GPP TS 29.002: “Mobile Application Part (MAP) specification“. 7 3GPP TS 29.078: “Customised Applications for Mobile network Enhanced Logic (CAMEL)

22、; 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 Signalling System No. 1 and the Signalling System No. 7 ISDN User Part“. 10 3GPP TR 29.998-1: “Open Service Acc

23、ess (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 document, the terms and definitions given in TS 29.198-1 1 apply. ETSI ETSI TR 129 998-8 V9.0.0 (2010-01)63GPP T

24、R 29.998-08 version 9.0.0 Release 93.2 Abbreviations For the purposes of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 Data Session Control Service CAMEL Call Flows 4.1 Data Session Manager The session manager interface provides the management functions to the data session

25、service capability features. The application programmer can use this interface to enable or disable data session-related event notifications. In order to ensure that the mobility events are transparent to the Data Session SCF, the same gsmSCF address shall be used in the GPRS-CSI for the detection p

26、oints: PDP Context Establishment, PDP Context Establishment Acknowledge and Change of Position. 4.1.1 enableDataSessionNotification enableDataSessionNotification is used to enable data session-related notifications to be sent to the application. HLRgsmSCFSCS ApplicationenableDataSessionNotificationM

27、AP AnyTimeModificationRequestFigure 4-1: Call Flow for enableDataSessionNotification 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 enableDataSessionNo

28、tification method 2 The gsmSCF sends a MAP AnyTimeModification to the HLR in order to activate the necessary CAMEL Subscription Information (GPRS-CSI) Note : CAMEL phase 3 only allows for activation/deactivation of the CSI and not modification of the contents of the CSIs Table 4-2: Parameter Mapping

29、 From: enableDataSessionNotification To: MAP AnyTimeModification appInterface eventCriteria OriginatingAddress GPRS CAMEL Subscription Information GPRS-CSI gsmSCF Address assignmentID 4.1.2 disableDataSessionNotification disableDataSessionNotification is used by the application to disable data sessi

30、on notifications. ETSI ETSI TR 129 998-8 V9.0.0 (2010-01)73GPP TR 29.998-08 version 9.0.0 Release 9HLR ApplicationdisableDataSessionNotificationMAP AnyTimeModificationRequestgsmSCFSCSFigure 4-2: Call Flow for disableDataSessionNotification Table 4-3: Normal Operation Pre-conditions An agreement is e

31、stablished between the network operator and the service provider for the event notification to be disabled 1 The application invokes the disableDataSessionNotification method 2 The gsmSCF sends a MAP AnyTimeModification to the HLR in order to de-activate the necessary CAMEL Subscription Information.

32、 Note that CAMEL Phase 3 only allows the capability to activate/deactivate CSI and not to modify the triggering information Table 4-4: Parameter Mapping From: disableDataSessionNotification To: MAP AnyTimeModification eventCriteria OriginatingAddress GPRS CAMEL Subscription Information GPRS-CSI gsmS

33、CF Address assignmentID 4.1.3 dataSessionEventNotify dataSessionEventNotify notifies the application of the arrival of a data session-related event. gprsSSF gsmSCF SCS ApplicationCAP InitialDPGPRSdataSessionEventNotifyFigure 4-3: Call Flow for dataSessionEventNotify Table 4-5: Normal Operation Pre-c

34、onditions Call notifications have been enabled using the enableDataSessionNotification method on the Data Session Manager interface 1 A data session request arrives at the gsmSSF causing initial triggering to the gsmSCF CAP InitialDPGPRS 2 The gsmSCF recognizes the need for an API service and passes

35、 the triggering information to the SCS 3 The SCS identifies the application responsible for handling the data session and invokes the dataSessionEventNotify method ETSI ETSI TR 129 998-8 V9.0.0 (2010-01)83GPP TR 29.998-08 version 9.0.0 Release 9Table 4-6: Parameter Mapping From: CAP InitialDPGPRS To

36、: dataSessionlEventNotify serviceKey gPRSEventType mSISDN accessPointName eventInfo OriginatingAddress DestinationAddress iMSItimeAndTimeZone gPRSMSClass pDPTypequalityOfServicerouteingAreaIdentity chargeIDsGSNCapabilitiesassignmentID appInterface4.1.4 dataSessionAborted dataSessionAborted indicates

37、 to the application that the Data Session object has aborted or terminated abnormally. No further communication will be possible between the Data Session object and the application. gprsSSFgsmSCFSCS ApplicationdataSessionAbortedNo appropriate MAP or CAPmessageFigure 4-4: Call Flow for dataSessionAbo

38、rted Table 4-7: Normal Operation Pre-conditions 1 The SCS detect a catastrophic failure in its communication with the gsmSCF 2 The SCS, invokes the dataSessionAborted method. The data session running in the network may continue and will not have been affected by this failure betweeen the gsmSCF and

39、the SCS Parameter Mapping None. 4.1.5 dataSessionNotificationInterrupted dataSessionlNotificationInterrupted indicates to the application that event notifications will no longer be sent (for example, due to faults detected). ETSI ETSI TR 129 998-8 V9.0.0 (2010-01)93GPP TR 29.998-08 version 9.0.0 Rel

40、ease 9HLR gsmSCF SCS ApplicationdataSessionNotificationInterruptedNo appropriate MAP or CAPmessageFigure 4-5: Call Flow for dataSessionNotificationInterruptedNormal Operation Table 4-8 Pre-conditions Data session notifications have been enabled using the enableNotification method on the Data Session

41、 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 dataSessionNotificationInterrupted method Parameter Mapping None. 4.1.6 dataSessionNotificationContinued dataSessionNotificationContinued indicates to t

42、he application that all event notifications will be sent again. HLR gsmSCF SCS ApplicationdataSessionNotificationContinuedNo appropriate MAP or CAPmessageFigure 4-6: Call Flow for dataSessionNotificationContinued Table 4-9: Normal Operation Pre-conditions Data session notifications have been interru

43、pted and dataSessionNotificationInterrupted method has been invoked 1 The SCS detects that data session notifications are again possible 2 The SCS invokes the dataSessionNotificationContinued method Parameter Mapping None. 4.2 Data Session The Data Session interface provides basic methods for applic

44、ations to control data sessions. ETSI ETSI TR 129 998-8 V9.0.0 (2010-01)103GPP TR 29.998-08 version 9.0.0 Release 94.2.1 ConnectReq connectReq requests the connection of a data session with the destination party (specified in the parameter TargetAddress). The Data Session object is not automatically

45、 deleted if the destination party disconnects from the data session. The mapping to continueGPRS is also possible. gprsSSFgsmSCFSCS ApplicationconnectReqCAP requestReportGPRSEvent (if appropriate)CAP connectGPRSFigure 4-7: Call Flow for connectReq Table 4-10: Normal Operation Pre-conditions The appl

46、ication has been notified of a new data session and the data session object exists 1 The application invokes the connectReq method 2 The SCS sends an equivalent internal message to the gsmSCF 3 The gsmSCF sends a CAP requestReportGPRSEvent if the application needs to be informed about the outcome of

47、 the request 4 The gsmSCF sends a CAP connectGPRS message Table 4-11: Parameter Mapping From: connectReq To: CAP requestReportGPRSEvent gPRS-ReferenceNumber dataSessionID responseRequested gPRSEvent targetAddresspDPID assignmentID Table 4-12 From: connectReq To: CAP connectGPRS dataSessionID respons

48、eRequestedtargetAddress accessPointName pdpIDassignmentID ETSI ETSI TR 129 998-8 V9.0.0 (2010-01)113GPP TR 29.998-08 version 9.0.0 Release 94.2.2 connectRes connectRes indicates that the request to connect a data session with the destination party was successful, and indicates the response of the de

49、stination party (e.g. connected, disconnected). gprsSSF gsmSCF SCS ApplicationCAP eventReportGPRSconnectResFigure 4-8: Call Flow for connectRes Table 4-13: Normal Operation Pre-conditions Data session routing attempted 1 If event reports have been requested, the gprsSSF sends a CAP eventReportGPRS to the gsmSCF 2 The gsmSCF sends an equivalent message to the SCS 3 The SCS invokes the connectRes method Table 4-14: Parameter Mapping From: CAP eventReportGPRS To: connectRes dataSessionID gPRS-ReferenceNumber gPRSEventType miscGPRSInfo gPRSEventSpecificInfor