1、 ETSI ES 201 915-8 V1.6.1 (2006-12)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 8: Data Session Control SCF(Parlay 3)floppy3 ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 2 Reference RES/TISPAN-01027-08-OSA Keywords API, IDL, OSA, UML ETSI 650 Route des Lucioles F-0
2、6921 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 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.et
3、si.org The present document may be made available 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 o
4、n ETSI printers of the PDF version kept on a specific 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
5、.etsi.org/tb/status/status.asp If you find errors 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 for
6、egoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. The Parlay Group 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks curr
7、ently 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 the 3GPP Organizational Partners. ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 3 Defi
8、nitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .6 4 Data Session Control SCF7 4.1 General requirements on support of methods.8 5 Sequence Diagrams 8 5.1 Enable Data Session Notification.8 5.2 Address Translation With Charging.9 6 Class Diagrams.10 7 The Service Interface Specificatio
9、ns11 7.1 Interface Specification Format .11 7.1.1 Interface Class 11 7.1.2 Method descriptions11 7.1.3 Parameter descriptions11 7.1.4 State Model.11 7.2 Base Interface.11 7.2.1 Interface Class IpInterface 11 7.3 Service Interfaces .12 7.3.1 Overview 12 7.4 Generic Service Interface .12 7.4.1 Interfa
10、ce Class IpService 12 8 Data Session Control Interface Classes13 8.1 Interface Class IpAppDataSession .13 8.2 Interface Class IpAppDataSessionControlManager .15 8.3 Interface Class IpDataSession 17 8.4 Interface Class IpDataSessionControlManager20 9 State Transition Diagrams23 9.1 State Transition D
11、iagrams for IpDataSession.23 9.1.1 Network Released State 23 9.1.2 Finished State24 9.1.3 Application Released State .24 9.1.4 Active State.24 9.1.5 Setup State 24 9.1.6 Established State.24 10 Data Session Control Service Properties24 11 Data Definitions .25 11.1 Data Session Control Data Definitio
12、ns.25 11.1.1 IpAppDataSession 25 11.1.2 IpAppDataSessionRef.25 11.1.3 IpAppDataSessionControlManager 25 11.1.4 IpAppDataSessionControlManagerRef 26 11.1.5 IpDataSession .26 11.1.6 IpDataSessionRef .26 11.1.7 IpDataSessionControlManager.26 11.1.8 IpDataSessionControlManagerRef .26 11.2 Event Notifica
13、tion data definitions.26 ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 4 11.2.1 TpDataSessionEventName .26 11.2.2 TpDataSessionMonitorMode26 11.2.3 TpDataSessionEventCriteria.26 11.2.4 TpDataSessionEventInfo 27 11.2.5 TpDataSessionQosClass .27 11.2.6 TpDataSessionChargePlan27 11.2.7 TpDataSessionChargeOrd
14、er .28 11.2.8 TpDataSessionChargeOrderCategory.28 11.2.9 TpChargePerVolume 29 11.2.10 TpDataSessionIdentifier .29 11.2.11 TpDataSessionError29 11.2.12 TpDataSessionAdditionalErrorInfo 29 11.2.13 TpDataSessionErrorType29 11.2.14 TpDataSessionFault30 11.2.15 TpDataSessionReleaseCause 30 11.2.16 TpData
15、SessionSuperviseVolume30 11.2.17 TpDataSessionSuperviseReport30 11.2.18 TpDataSessionSuperviseTreatment 31 11.2.19 TpDataSessionReport .31 11.2.20 TpDataSessionAdditionalReportInfo31 11.2.21 TpDataSessionReportRequest.31 11.2.22 TpDataSessionReportRequestSet .31 11.2.23 TpDataSessionReportType .32 1
16、1.2.24 TpDataSessionEventCriteriaResult.32 11.2.25 TpDataSessionEventCriteriaResultSet32 12 Exception Classes.32 Annex A (normative): OMG IDL Description of Data Session Control SCF.33 Annex B (informative): Contents of 3GPP OSA R4 Data Session Control.34 Annex C (informative): Record of changes 35
17、C.1 Interfaces 35 C.1.1 New 35 C.1.2 Deprecated35 C.1.3 Removed.35 C.2 Methods36 C.2.1 New 36 C.2.2 Deprecated36 C.2.3 Modified.36 C.2.4 Removed.36 C.3 Data Definitions .37 C.3.1 New 37 C.3.2 Modified.37 C.3.3 Removed.37 C.4 Service Properties.37 C.4.1 New 37 C.4.2 Deprecated38 C.4.3 Modified.38 C.4
18、.4 Removed.38 C.5 Exceptions 38 C.5.1 New 38 C.5.2 Modified.39 C.5.3 Removed.39 C.6 Others .39 History 40 ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining
19、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 (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat.
20、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 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 upd
21、ates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document
22、is part 8 of a multi-part deliverable covering Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (ES 201 915) is structured in the following parts: Part 1: “Overview“; Part 2: “Common Data Definitions“; Part 3: “Framework“; Part 4: “Call C
23、ontrol 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“; Part 10: “Connectivity Manager SCF“; Part 11: “Account Management SCF“; Part 12: “Charging SCF“. The present document has bee
24、n defined jointly between ETSI, The Parlay Group (http:/www.parlay.org)and the 3GPP, in co-operation with a number of JAIN Community (http:/ member companies. The present document forms part of the Parlay 3.5 set of specifications. The present document is equivalent to 3GPP TS 29.198-8 V4.9.0 (Relea
25、se 4). ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 6 1 Scope The present document is part 8 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers to make use of network
26、functionality through an open standardized interface, i.e. the OSA APIs. The present document specifies the Data Session Control Service Capability Feature (SCF) aspects of the interface. All aspects of the Data Session Control SCF are defined here, these being: Sequence Diagrams. Class Diagrams. In
27、terface specification plus detailed method descriptions. State Transition diagrams. Data Definitions. IDL Description of the interfaces. The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML). 2 References Th
28、e references listed in clause 2 of ES 201 915-1 contain provisions which, through reference in this text, constitute provisions of the present document. ETSI ES 201 915-1: “Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 3)“. 3 Definitions and abbreviatio
29、ns 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 201 915-1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in ES 201 915-1 apply. ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 7 4 Data Session Control SCF The Da
30、ta Session control network service capability feature consists of two interfaces: 1) Data Session manager, containing management functions for data session related issues. 2) Data Session, containing methods to control a session. A session can be controlled by one Data Session Manager only. Data Ses
31、sion 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 context in GPRS. Figure 1: Data Session control interfaces usage relationship The Data Sess
32、ion Control service capability features 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: Overview of Data Session Control interfaces and their methods Dat
33、a Session Manager Data Session createNotification connectReq destroyNotification connectResdataSessionNotificationInterrupted connectErr dataSessionNotificationContinued release reportNotification superviseDataSessionReq dataSessionAborted superviseDataSessionRes getNotification superviseDataSession
34、Err changeNotification dataSessionFaultDetected setAdviceofCharge setDataSessionChargePlan The session manager interface provides the management functions to the data session service capability features. The application programmer can use this interface to enable or disable data session-related even
35、t 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 practical idea of how each of the SCF is implemented. The Class relationships clause show how each of the interfa
36、ces 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. The State Transition Diagrams (STD) show the transition between states in the SCF. The states and transitions are well-defined; either
37、methods specified in the Interface specification or events occurring in the underlying networks cause state transitions. The Data Definitions clause show 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
38、 and classes and are therefore defined within the Common Data types part of the present document. ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 8 4.1 General requirements on support of methods An implementation of this API which supports or implements a method described in the present document, shall supp
39、ort 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
40、a method is not supported by an implementation of an Application interface, a call to that method shall be possible, and no exception shall be returned. 5 Sequence Diagrams 5.1 Enable Data Session Notification Applicat ion Data Session Manager : IpDataSessionControlManagerData Session : IpDataSes si
41、on1: createNotification( )ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 9 5.2 Address Translation With Charging Application Data Session Manager : IpDataSessionControlManagerData Session : IpDat aS es si on1: createNotification( )2: reportNotification()3: translate address4: setCallback( )5: superviseData
42、SessionReq( )6: connectReq( )7: superviseDataSessionRes()8: superviseDataSessionReq( )9: superviseDataSessionRes()10: ConnectRes( )ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 106 Class Diagrams Data Session Control Class Diagram: IpInterface(from csapi)IpServicesetCallback()setCallbackWithSessionID()(fr
43、om csapi)IpDataSessionControlManagercreateNotification()destroyNotification()changeNotification() getNotification() getNotifications()(from dsc) IpDataSessionconnectReq()release()superviseDataSessionReq()setDataSessionChargePlan()setAdviceOfCharge()deassignDataSession()continueProcessing()(from dsc)
44、1 0nIpAppDataSessionControlManagerdataSessionAborted()reportNotification()dataSessionNotificationContinued()dataSessionNotificationInterrupted()(from dsc)IpAppDataSessionconnectRes()connectErr()superviseDataSessionRes()superviseDataSessionErr()dataSessionFaultDetected()(from dsc)1 0n10Figure 2: Pack
45、age Overview ETSI ETSI ES 201 915-8 V1.6.1 (2006-12) 117 The Service Interface Specifications 7.1 Interface Specification Format This clause defines the interfaces, methods and parameters that form a part of the API specification. The Unified Modelling Language (UML) is used to specify the interface
46、 classes. The general format of an interface specification is described below. 7.1.1 Interface Class This shows a UML interface class description of the methods supported by that interface, and the relevant parameters and types. The Service and Framework interfaces for enterprise-based client applic
47、ations are denoted by classes with name Ip. The callback interfaces to the applications are denoted by classes with name IpApp. For the interfaces between a Service and the Framework, the Service interfaces are typically denoted by classes with name IpSvc, while the Framework interfaces are denoted
48、by classes with name IpFw. 7.1.2 Method descriptions Each method (API method “call“) is described. Both synchronous and asynchronous methods are used in the API. Asynchronous methods are identified by a “Req“ suffix for a method request, and, if applicable, are served by asynchronous methods identif
49、ied by either a “Res“ or “Err“ suffix for method results and errors, respectively. To handle responses and reports, the application or service developer must implement the relevant IpApp or IpSvc interfaces to provide the callback mechanism. 7.1.3 Parameter descriptions Each method parameter and its possible values are described. Parameters described as “in“ represent those that must have a value when the method is called. Those described as “out“ are those that contain the return result of the method when the method
