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

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

1、 ETSI TS 129 198-8 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 8: Data session control Service Capability Feature (SCF) (3GPP

2、TS 29.198-08 version 9.0.0 Release 9)floppy3ETSI ETSI TS 129 198-8 V9.0.0 (2010-01)13GPP TS 29.198-08 version 9.0.0 Release 9Reference RTS/TSGC-0029198-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 47 16 Si

3、ret 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 version

4、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 ETSI Secret

5、ariat. 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, please send

6、 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 Telecommunications St

7、andards 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 Partners. L

8、TE 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-8 V9.0.0 (2010-01)23GPP TS 29.198-08 version 9.0.0 Release 9Intellectua

9、l 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 Rights (IP

10、Rs); 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 IPR sear

11、ches, 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 Specification (TS) has been produc

12、ed 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 betw

13、een GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 198-8 V9.0.0 (2010-01)33GPP TS 29.198-08 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 6g3Introduction 6g31 Scope 8g32 References 8g33 Defin

14、itions and abbreviations . 9g33.1 Definitions 9g33.2 Abbreviations . 9g34 Data Session Control SCF 9g34.1 General requirements on support of methods . 10g35 Sequence Diagrams 10g35.1 Network Controlled Notifications 10g35.2 Enable Data Session Notification . 11g35.3 Address Translation With Charging

15、 . 12g36 Class Diagrams . 13g37 The Service Interface Specifications 15g37.1 Interface Specification Format . 15g37.1.1 Interface Class 15g37.1.2 Method descriptions 15g37.1.3 Parameter descriptions 15g37.1.4 State Model . 15g37.2 Base Interface . 15g37.2.1 Interface Class IpInterface 15g37.3 Servic

16、e Interfaces . 16g37.3.1 Overview 16g37.4 Generic Service Interface . 16g37.4.1 Interface Class IpService 16g37.4.1.1 Method setCallback() 16g37.4.1.2 Method setCallbackWithSessionID() 17g38 Data Session Control Interface Classes 17g38.1 Interface Class IpAppDataSession . 17g38.1.1 Method connectRes

17、() 18g38.1.2 Method connectErr() . 18g38.1.3 Method superviseDataSessionRes() 19g38.1.4 Method superviseDataSessionErr() 19g38.1.5 Method dataSessionFaultDetected() . 19g38.2 Interface Class IpAppDataSessionControlManager . 20g38.2.1 Method dataSessionAborted() 20g38.2.2 Method reportNotification()

18、20g38.2.3 Method dataSessionNotificationContinued() 21g38.2.4 Method dataSessionNotificationInterrupted() . 21g38.2.5 Method abortMultipleDataSessions() . 21g38.3 Interface Class IpDataSession 21g38.3.1 Method connectReq() . 22g38.3.2 Method release() . 23g38.3.3 Method superviseDataSessionReq() . 2

19、3g38.3.4 Method setDataSessionChargePlan() 23g38.3.5 Method setAdviceOfCharge() . 24g38.3.6 Method deassignDataSession() . 24g3ETSI ETSI TS 129 198-8 V9.0.0 (2010-01)43GPP TS 29.198-08 version 9.0.0 Release 98.3.7 Method continueProcessing() . 24g38.4 Interface Class IpDataSessionControlManager 25g3

20、8.4.1 Method destroyNotification() . 25g38.4.2 Method changeNotification() 26g38.4.3 Method enableNotifications() . 26g38.4.4 Method disableNotifications() 27g38.4.5 Method getNotifications() . 27g38.4.6 Method createNotifications() 27g39 State Transition Diagrams 28g39.1 State Transition Diagrams f

21、or IpDataSession. 28g39.1.1 Network Released State 29g39.1.2 Finished State 29g39.1.3 Application Released State . 29g39.1.4 Active State. 29g39.1.5 Setup State 30g39.1.6 Established State . 30g310 Data Session Control Service Properties 30g311 Data Definitions . 31g311.1 Data Session Control Data D

22、efinitions . 31g311.1.1 IpAppDataSession 31g311.1.2 IpAppDataSessionRef . 31g311.1.3 IpAppDataSessionControlManager 31g311.1.4 IpAppDataSessionControlManagerRef 31g311.1.5 IpDataSession . 31g311.1.6 IpDataSessionRef . 32g311.1.7 IpDataSessionControlManager . 32g311.1.8 IpDataSessionControlManagerRef

23、 . 32g311.2 Event Notification data definitions . 32g311.2.1 TpDataSessionEventName . 32g311.2.2 TpDataSessionMonitorMode 32g311.2.3 TpDataSessionEventCriteria . 32g311.2.4 TpDataSessionEventInfo 33g311.2.5 TpDataSessionChargePlan 33g311.2.6 TpDataSessionChargeOrder . 34g311.2.7 TpDataSessionChargeO

24、rderCategory . 34g311.2.8 TpChargePerVolume 34g311.2.9 TpDataSessionIdentifier . 34g311.2.10 TpDataSessionError 35g311.2.11 TpDataSessionAdditionalErrorInfo 35g311.2.12 TpDataSessionErrorType 35g311.2.13 TpDataSessionFault 35g311.2.14 TpDataSessionReleaseCause 36g311.2.15 TpDataSessionSuperviseVolum

25、e 36g311.2.16 TpDataSessionSuperviseReport 36g311.2.17 TpDataSessionSuperviseTreatment 36g311.2.18 TpDataSessionReport . 36g311.2.19 TpDataSessionAdditionalReportInfo 37g311.2.20 TpDataSessionReportRequest. 37g311.2.21 TpDataSessionReportRequestSet . 37g311.2.22 TpDataSessionReportType . 37g311.2.23

26、 TpDataSessionEventCriteriaResult . 37g311.2.24 TpDataSessionEventCriteriaResultSet 37g3Annex A (normative): OMG IDL Description of Data Session Control SCF . 38g3Annex B (informative): W3C WSDL Description of Data Session Control SCF . 39g3Annex C (informative): Java API Description of the Data Ses

27、sion Control SCF . 40g3Annex D (informative): Description of Data Session Control for 3GPP2 cdma2000 networks 41g3ETSI ETSI TS 129 198-8 V9.0.0 (2010-01)53GPP TS 29.198-08 version 9.0.0 Release 9D.1 General Exceptions. 41g3D.2 Specific Exceptions 41g3D.2.1 Clause 1: Scope 41g3D.2.2 Clause 2: Referen

28、ces 41g3D.2.3 Clause 3: Definitions and abbreviations . 41g3D.2.4 Clause 4: Data Session Control SCF 41g3D.2.5 Clause 5: Sequence Diagrams 41g3D.2.6 Clause 6 Class Diagrams 42g3D.2.7 Clause 7: The Service Interface Specifications 42g3D.2.8 Clause 8: Data Session Control Interface Classes 42g3D.2.9 C

29、lause 9: State Transition Diagrams 42g3D.2.10 Clause 10: Data Session Control Service Properties 42g3D.2.11 Clause 11: Data Definitions 42g3D.2.12 Annex A (normative): OMG IDL Description of Data Session Control SCF 42g3D.2.13 Annex B (informative): W3C WSDL Description of Data Session Control SCF 4

30、2g3Annex E (informative): Change history . 43g3History 44g3ETSI ETSI TS 129 198-8 V9.0.0 (2010-01)63GPP TS 29.198-08 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to con

31、tinuing 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 version number as follows: Version x.y.z where: x the first digit: 1 p

32、resented 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, corrections, updates, etc. z the third digit is incremented when editorial

33、 only changes have been incorporated in the document. Introduction The present document is part 8 of a multi-part TS covering the 3rdGeneration Partnership Project: Technical Specification Group Core Network; Open Service Access (OSA); Application Programming Interface (API), as identified below. Th

34、e API specification (3GPP TS 29.198) 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 Call Control SCF“; Sub-part 3: “Multi-Party Call Control

35、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 Messaging SCF“; (not part of 3GPP Release 8) Part 10: “Connec

36、tivity Manager SCF“; (new in Release 8) 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“; Part 16: “Service Broker SCF“; The Mapping specification of the OSA APIs an

37、d network protocols (3GPP TR 29.998) is also structured as above. A mapping to network protocols is however not applicable 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-8 V9.0.0 (20

38、10-01)73GPP TS 29.198-08 version 9.0.0 Release 9Table: Overview of the OSA APIs Application Programming Interface; 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 ISO 4217: “Codes for th

39、e representation of currencies and funds“. ETSI ETSI TS 129 198-8 V9.0.0 (2010-01)93GPP TS 29.198-08 version 9.0.0 Release 93 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 the purp

40、oses of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 Data Session Control SCF The Data Session Control network SCF consists of two interfaces: 1) Data Session manager, containing management functions for data session related issues; 2) Data Session, containing methods to c

41、ontrol a session. A session can be controlled by one Data Session Manager only. Data Session Manager can control several sessions. 1 Data Session Manager Data Session 1 n NOTE: The term “data session“ is used in a broad sense to describe a data connection/session. For example, it comprises a PDP con

42、text in GPRS. Figure 1: Data Session control interfaces usage relationship The Data Session Control SCFs are described in terms of the methods in the Data Session Control interfaces. Table 1 gives an overview of the Data Session Control methods and to which interfaces these methods belong. Table 1:

43、Overview of Data Session Control interfaces and their methods Data Session Manager Data Session createNotifications connectReq destroyNotification connectResdataSessionNotificationInterrupted connectErr dataSessionNotificationContinued release reportNotification superviseDataSessionReq dataSessionAb

44、orted superviseDataSessionResgetNotifications superviseDataSessionErrchangeNotification dataSessionFaultDetected enableNotifications setAdviceofCharge disableNotifications setDataSessionChargePlanThe session manager interface provides the management functions to the data session service capability f

45、eatures. The application programmer can use this interface to enable or disable data session-related event notifications. The following clauses describe each aspect of the Data Session Control Service Capability Feature (SCF). The order is as follows: the Sequence diagrams give the reader a practica

46、l idea of how each of the SCF is implemented; the Class relationships clause shows how each of the interfaces applicable to the SCF, relate to one another; the Interface specification clause describes in detail each of the interfaces shown within the Class diagram part; ETSI ETSI TS 129 198-8 V9.0.0

47、 (2010-01)103GPP TS 29.198-08 version 9.0.0 Release 9 the State Transition Diagrams (STD) show the transition between states in the SCF. The states and transitions are well-defined; either methods specified in the Interface specification or events occurring in the underlying networks cause state tra

48、nsitions; the Data definitions clause shows a detailed expansion of each of the data types associated with the methods within the classes. Note that some data types are used in other methods and classes and are therefore defined within the Common Data types part of this specification. 4.1 General re

49、quirements on support of methods An implementation of this API which supports or implements a method described in the present document, shall support or implement the functionality described for that method, for at least one valid set of values for the parameters of that method. Where a method is not supported by an implementation of a Service interface, the exception P_METHOD_NOT_SUPPORTED shall be returned to any call of that method. Where a method is not supported by an implementation of an Application interface, a call to that method shall be possible