SIST ES 201 915-8 V1.4.1:2005

SLOVENSKI STANDARD
01-januar-2005
Odprti dostop do storitve (OSA) – Vmesnik za aplikacijsko programiranje (API) – 8.
del: Krmiljenje podatkovne seje SCF
Open Service Access (OSA); Application Programming Interface (API); Part 8: Data
Session Control SCF (Parlay 3)
Ta slovenski standard je istoveten z: ES 201 915-8 Version 1.4.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Part 8: Data Session Control SCF
(Parlay 3)
�
2 ETSI ES 201 915-8 V1.4.1 (2003-07)

Reference
RES/SPAN-120095-8
Keywords
API, OSA, IDL, UML
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 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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 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, send your comment to:
editor@etsi.org
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 2003.
© The Parlay Group 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 201 915-8 V1.4.1 (2003-07)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations.6
4 Data Session Control SCF.7
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 Specifications.11
7.1 Interface Specification Format .11
7.1.1 Interface Class.11
7.1.2 Method descriptions.11
7.1.3 Parameter descriptions.11
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 Interface Class IpService .12
8 Data Session Control Interface Classes.13
8.1 Interface Class IpAppDataSession .13
8.2 Interface Class IpAppDataSessionControlManager .15
8.3 Interface Class IpDataSession .17
8.4 Interface Class IpDataSessionControlManager.20
9 State Transition Diagrams.24
9.1 State Transition Diagrams for IpDataSession.24
9.1.1 Network Released State .24
9.1.2 Finished State.24
9.1.3 Application Released State.25
9.1.4 Active State.25
9.1.5 Setup State.25
9.1.6 Established State.25
10 Data Session Control Service Properties.25
11 Data Definitions.26
11.1 Data Session Control Data Definitions.26
11.1.1 IpAppDataSession.26
11.1.2 IpAppDataSessionRef.26
11.1.3 IpAppDataSessionControlManager.26
11.1.4 IpAppDataSessionControlManagerRef.26
11.1.5 IpDataSession.27
11.1.6 IpDataSessionRef.27
11.1.7 IpDataSessionControlManager.27
11.1.8 IpDataSessionControlManagerRef.27
11.2 Event Notification data definitions.27
ETSI
4 ETSI ES 201 915-8 V1.4.1 (2003-07)
11.2.1 TpDataSessionEventName.27
11.2.2 TpDataSessionMonitorMode.27
11.2.3 TpDataSessionEventCriteria.27
11.2.4 TpDataSessionEventInfo.28
11.2.5 TpDataSessionQosClass.28
11.2.6 TpDataSessionChargePlan.28
11.2.7 TpDataSessionChargeOrder.29
11.2.8 TpDataSessionChargeOrderCategory.29
11.2.9 TpChargePerVolume.30
11.2.10 TpDataSessionIdentifier.30
11.2.11 TpDataSessionError.30
11.2.12 TpDataSessionAdditionalErrorInfo.30
11.2.13 TpDataSessionErrorType.30
11.2.14 TpDataSessionFault.31
11.2.15 TpDataSessionReleaseCause.31
11.2.16 TpDataSessionSuperviseVolume.31
11.2.17 TpDataSessionSuperviseReport.31
11.2.18 TpDataSessionSuperviseTreatment.32
11.2.19 TpDataSessionReport.32
11.2.20 TpDataSessionAdditionalReportInfo.32
11.2.21 TpDataSessionReportRequest.32
11.2.22 TpDataSessionReportRequestSet.32
11.2.23 TpDataSessionReportType.33
11.2.24 TpDataSessionEventCriteriaResult.33
11.2.25 TpDataSessionEventCriteriaResultSet.33
12 Exception Classes.33
Annex A (normative): OMG IDL Description of Data Session Control SCF.34
Annex B (informative): Contents of 3GPP OSA R4 Data Session Control.35
Annex C (informative): Record of changes .36
C.1 Interfaces.36
C.1.1 New.36
C.1.2 Deprecated.36
C.1.3 Removed.36
C.2 Methods.36
C.2.1 New.36
C.2.2 Deprecated.36
C.2.3 Modified.37
C.2.4 Removed.37
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 Deprecated.38
C.4.3 Modified.38
C.4.4 Removed.38
C.5 Exceptions.38
C.5.1 New.38
C.5.2 Modified.38
C.5.3 Removed.38
C.6 Others.38
History .39

ETSI
5 ETSI ES 201 915-8 V1.4.1 (2003-07)
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 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 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 updates 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 Services and Protocols for Advanced
Networks (SPAN).
The present document 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 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";
Part 10: "Connectivity Manager SCF";
Part 11: "Account Management SCF";
Part 12: "Charging SCF".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP,
in co-operation with a number of JAIN™ Community (http://www.java.sun.com/products/jain) member companies.
The present document forms part of the Parlay 3.3 set of specifications.
The present document is equivalent to 3GPP TS 29.198-8 V4.6.0 (Release 4).
ETSI
6 ETSI ES 201 915-8 V1.4.1 (2003-07)
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 functionality
through an open standardised 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
• Interface 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
The 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 abbreviations
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
7 ETSI ES 201 915-8 V1.4.1 (2003-07)
4 Data Session Control SCF
The Data 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 Session Manager can control several sessions.
Data Session Data Session
1 n
Manager
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 Session 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
Data Session Manager Data Session
createNotification connectReq
destroyNotification connectRes
dataSessionNotificationInterrupted connectErr
dataSessionNotificationContinued release
reportNotification superviseDataSessionReq
dataSessionAborted superviseDataSessionRes
getNotification superviseDataSessionErr
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 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 practical idea of how each of the SCF is implemented.
• The Class relationships clause show 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.
• 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 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 and classes and are therefore defined
within the Common Data types part of this specification.
ETSI
8 ETSI ES 201 915-8 V1.4.1 (2003-07)
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
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, and no exception shall be returned.
5 Sequence Diagrams
5.1 Enable Data Session Notification
Application Data Session Manager : Data Session :
IpDataSessionControlManager IpDataSession
1: createNotification( )
ETSI
9 ETSI ES 201 915-8 V1.4.1 (2003-07)
5.2 Address Translation With Charging
Application Data Session Manager : Data Session :
IpDataSessionControlManager IpDat aSessi on
1: createNotification( )
2: reportNotification()
3: 'translate address'
4: setCallback( )
5: superviseDataSessionReq(  )
6: connectReq(  )
7: superviseDataSessionRes()
8: superviseDataSessionReq(  )
9: superviseDataSessionRes()
10: ConnectRes( )
ETSI
10 ETSI ES 201 915-8 V1.4.1 (2003-07)
6 Class Diagrams
Data Session Control Class Diagram:
<>
IpInterface
(from csapi)
<>
<>
IpAppDataSession
IpAppDataSessionControlManager
(from dsc)
(from dsc)
connectRes()
dataSessionAborted()
1100.nn
connectErr()
reportNotification()
superviseDataSessionRes()
dataSessionNotificationContinued()
superviseDataSessionErr()
dataSessionNotificationInterrupted()
dataSessionFaultDetected()
<>
<>
<>
<> IpDataSession
IpDataSessionControlManager
(from dsc)
(from dsc)
connectReq()
createNotification() release()
11 00.n.n
destroyNotification() superviseDataSessionReq()
changeNotification() setDataSessionChargePlan()
<> getNotification() setAdviceOfCharge()
<> getNotifications() deassignDataSession()
continueProcessing()
<>
IpService
(from csapi)
setCallback()
setCallbackWithSessionID()
Figure 2: Package Overview
ETSI
11 ETSI ES 201 915-8 V1.4.1 (2003-07)
7 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 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 applications 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 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 identified 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 returns.
7.1.4 State Model
If relevant, a state model is shown to illustrate the states of the objects that implement the described interface.
7.2 Base Interface
7.2.1 Interface Class IpInterface
All application, framework and service interfaces inherit from the following interface. This API Base Interface does not
provide any additional methods.
<>
IpInterface
ETSI
12 ETSI ES 201 915-8 V1.4.1 (2003-07)
7.3 Service Interfaces
7.3.1 Overview
The Service Interfaces provide the interfaces into the capabilities of the underlying network - such as call control, user
interaction, messaging, mobility and connectivity management.
The interfaces that are implemented by the services are denoted as 'Service Interface'. The corresponding interfaces that
must be implemented by the application (e.g. for API callbacks) are denoted as 'Application Interface'.
7.4 Generic Service Interface
7.4.1 Interface Class IpService
Inherits from: IpInterface
All service interfaces inherit from the following interface.
<>
IpService
setCallback (appInterface : in IpInterfaceRef) : void
setCallbackWithSessionID (appInterface : in IpInterfaceRef, sessionID : in TpSessionID) : void

Method
setCallback()
This method specifies the reference address of the callback interface that a service uses to invoke methods on the
application. It is not allowed to invoke this method on an interface that uses SessionIDs.
Parameters
appInterface : in IpInterfaceRef
Specifies a reference to the application interface, which is used for callbacks
Raises
TpCommonExceptions, P_INVALID_INTERFACE_TYPE

Method
setCallbackWithSessionID()
This method specifies the reference address of the application's callback interface that a service uses for interactions
associated with a specific session ID: e.g. a specific call, or call leg. It is not allowed to invoke this method on an
interface that does not use SessionIDs.
ETSI
13 ETSI ES 201 915-8 V1.4.1 (2003-07)
Parameters
appInterface : in IpInterfaceRef
Specifies a reference to the application interface, which is used for callbacks
sessionID : in TpSessionID
Specifies the session for which the service can invoke the application's callback interface.
Raises
TpCommonExceptions, P_INVALID_SESSION_ID, P_INVALID_INTERFACE_TYPE

8 Data Session Control Interface Classes
The Data Session Control provides a means to control per data session basis the establishment of a new data session.
This means especially in the GPRS context that the establishment of a PDP session is modelled not the attach/detach
mode. Change of terminal location is assumed to be managed by the underlying network and is therefore not part of the
model. The underlying assumption is that a terminal initiates a data session and the application can reject the request for
data session establishment, can continue the establishment or can continue and change the destination as requested by
the terminal.
The modelling is similar to the Generic Call Control but assumes a simpler underlying state model. An
IpDataSessionControlManager object and an IpDataSession object are the interfaces used by the application, whereas
the IpAppDataSessionControlManager and the IpAppDataSession interfaces are implemented by the application.
8.1 Interface Class IpAppDataSession
Inherits from: IpInterface.
The application side of the data session interface is used to handle data session request responses and state reports.
<>
IpAppDataSession
connectRes (dataSessionID : in TpSessionID, eventReport : in TpDataSessionReport, assignmentID : in
TpAssignmentID) : void
connectErr (dataSessionID : in TpSessionID, errorIndication : in TpDataSessionError, assignmentID : in
TpAssignmentID) : void
superviseDataSessionRes (dataSessionID : in TpSessionID, report : in TpDataSessionSuperviseReport,
usedVolume : in TpDataSessionSuperviseVolume, qualityOfService : in TpDataSessionQosClass) : void
superviseDataSessionErr (dataSessionID : in TpSessionID, errorIndication : in TpDataSessionError) : void
dataSessionFaultDetected (dataSessionID : in TpSessionID, fault : in TpDataSessionFault) : void

Method
connectRes()
This asynchronous method indicates that the request to connect a data session with the destination party was successful,
and indicates the response of the destination party (e.g. connected, disconnected).
ETSI
14 ETSI ES 201 915-8 V1.4.1 (2003-07)
Parameters
dataSessionID : in TpSessionID
Specifies the session ID of the data session.
eventReport : in TpDataSessionReport
Specifies the result of the request to connect the data session. It includes the network event, date and time, monitoring
mode, negotiated quality of service and event specific information such as release cause.
assignmentID : in TpAssignmentID

Method
connectErr()
This asynchronous method indicates that the request to connect a data session with the destination party was
unsuccessful, e.g. an error detected in the network or the data session was abandoned.
Parameters
dataSessionID : in TpSessionID
Specifies the session ID.
errorIndication : in TpDataSessionError
Specifies the error which led to the original request failing.
assignmentID : in TpAssignmentID

Method
superviseDataSessionRes()
This asynchronous method reports a data session supervision event to the application. In addition, it may also be used to
notify the application of a newly negotiated set of Quality of Service parameters during the active life of the data
session.
Parameters
dataSessionID : in TpSessionID
Specifies the data session.
report : in TpDataSessionSuperviseReport
Specifies the situation, which triggered the sending of the data session supervision response.
usedVolume : in TpDataSessionSuperviseVolume
Specifies the used volume for the data session supervision (in the same unit as specified in the request).
qualityOfService : in TpDataSessionQosClass
Specifies the newly negotiated Quality of Service parameters for the data session.

ETSI
15 ETSI ES 201 915-8 V1.4.1 (2003-07)
Method
superviseDataSessionErr()
This asynchronous method reports a data session supervision error to the application.
Parameters
dataSessionID : in TpSessionID
Specifies the data session ID.
errorIndication : in TpDataSessionError
Specifies the error which led to the original request failing.

Method
dataSessionFaultDetected()
This method indicates to the application that a fault in the network has been detected which cannot be communicated by
a network event, e.g. when the user aborts before any establishment method is called by the application.
The system purges the Data Session object. Therefore, the application has no further control of data session processing.
No report will be forwarded to the application.
Parameters
dataSessionID : in TpSessionID
Specifies the data session ID of the Data Session object in which the fault has been detected
fault : in TpDataSessionFault
Specifies the fault that has been detected.
8.2 Interface Class IpAppDataSessionControlManager
Inherits from: IpInterface.
The data session control manager application interface provides the application data session control management
functions to the data session control SCF.
<>
IpAppDataSessionControlManager

dataSessionAborted (dataSession : in TpSessionID) : void
reportNotification (dataSessionReference : in TpDataSessionIdentifier, eventInfo : in
TpDataSessionEventInfo, assignmentID : in TpAssignmentID) : IpAppDataSessionRef
dataSessionNotificationContinued () : void
dataSessionNotificationInterrupted () : void

ETSI
16 ETSI ES 201 915-8 V1.4.1 (2003-07)
Method
dataSessionAborted()
This method indicates 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.
Parameters
dataSession : in TpSessionID
Specifies the session ID of the data session that has aborted or terminated abnormally.

Method
reportNotification()
This method notifies the application of the arrival of a data session-related event.
Returns appDataSession: Specifies a reference to the application object which implements the callback interface for the
new data session. If the application has previously explicitly passed a reference to the IpAppDataSession interface using
a setCallback() invocation, this parameter may be null, or if supplied must be the same as that provided during the
setCallback().
This parameter will be null if the notification is in NOTIFY mode.
Parameters
dataSessionReference : in TpDataSessionIdentifier
Specifies the session ID and the reference to the Data Session object to which the notification relates. If the notification
is being given in NOTIFY mode, this parameter shall be ignored by the application client implementation, and
consequently the implementation of the SCS entity invoking reportNotification may populate this parameter as it
chooses.
eventInfo : in TpDataSessionEventInfo
Specifies data associated with this event. This data includes the destination address provided by the end-user and the
quality of service requested or negotiated for the data session.
assignmentID : in TpAssignmentID
Specifies the assignment id which was returned by the createNotification() method. The application can use assignment
ID to associate events with event-specific criteria and to act accordingly.
Returns
IpAppDataSessionRef
Method
dataSessionNotificationContinued()
This method indicates to the application that all event notifications are resumed.
Parameters
No Parameters were identified for this method

ETSI
17 ETSI ES 201 915-8 V1.4.1 (2003-07)
Method
dataSessionNotificationInterrupted()
This method indicates to the application that event notifications will no longer be sent (for example, due to faults
detected).
Parameters
No Parameters were identified for this method
8.3 Interface Class IpDataSession
Inherits from: IpService.
The Data Session interface provides basic methods for applications to control data sessions.
This interface shall be implemented by a Data Session Control SCF. As a minimum requirement, the connectReq(),
release(), deassignDataSession() and continueProcessing() methods shall be implemented.
<>
IpDataSession
connectReq (dataSessionID : in TpSessionID, responseRequested : in TpDataSessionReportRequestSet,
targetAddress : in TpAddress) : TpAssignmentID
release (dataSessionID : in TpSessionID, cause : in TpDataSessionReleaseCause) : void
superviseDataSessionReq (dataSessionID : in TpSessionID, treatment : in
TpDataSessionSuperviseTreatment, bytes : in TpDataSessionSuperviseVolume) : void
setDataSessionChargePlan (dataSessionID : in TpSessionID, dataSessionChargePlan : in
TpDataSessionChargePlan) : void
setAdviceOfCharge (dataSessionID : in TpSessionID, aoCInfo : in TpAoCInfo, tariffSwitch : in TpDuration) :
void
deassignDataSession (dataSessionID : in TpSessionID) : void
continueProcessing (dataSessionID : in TpSessionID) : void

Method
connectReq()
This asynchronous method requests the connection of a data session with the destination party (specified in the
parameter TargetAddress). The Data Session object is not automatically deleted if the destination party disconnects
from the data session.
Returns assignmentID : Specifies the ID assigned to the request. The same ID will be returned in the connectRes or Err.
This allows the application to correlate the request and the result.
Parameters
dataSessionID : in TpSessionID
Specifies the session ID.
responseRequested : in TpDataSessionReportRequestSet
Specifies the set of observed data session events that will result in a connectRes() being generated.
ETSI
18 ETSI ES 201 915-8 V1.4.1 (2003-07)
targetAddress : in TpAddress
Specifies the address of destination party.
Returns
TpAssignmentID
Raises
TpCommonExceptions, P_SERVICE_INFORMATION_MISSING,
P_SERVICE_FAULT_ENCOUNTERED, P_INVALID_NETWORK_STATE, P_INVALID_ADDRESS,
P_INVALID_SESSION_ID
Method
release()
This method requests the release of the data session and associated objects.
Parameters
dataSessionID : in TpSessionID
Specifies the session.
cause : in TpDataSessionReleaseCause
Specifies the cause of the release.
Raises
TpCommonExceptions, P_SERVICE_INFORMATION_MISSING,
P_SERVICE_FAULT_ENCOUNTERED, P_INVALID_NETWORK_STATE,
P_INVALID_SESSION_ID
Method
superviseDataSessionReq()
The application calls this method to supervise a data session. The application can set a granted data volume for this data
session. If an application calls this function before it calls a connectReq() or a user interaction function the time
measurement will start as soon as the data session is connected. The Data Session object will exist after the data session
has been terminated if information is required to be sent to the application at the end of the data session
Parameters
dataSessionID : in TpSessionID
Specifies the data session.
treatment : in TpDataSessionSuperviseTreatment
Specifies how the network should react after the granted data volume has been sent.
bytes : in TpDataSessionSuperviseVolume
Specifies the granted number of bytes that can be transmitted for the data session.
ETSI
19 ETSI ES 201 915-8 V1.4.1 (2003-07)
Raises
TpCommonExceptions, P_SERVICE_INFORMATION_MISSING,
P_SERVICE_FAULT_ENCOUNTERED, P_INVALID_NETWORK_STATE,
P_INVALID_SESSION_ID
Method
setDataSessionChargePlan()
Allows an application to include charging information in network generated CDR.
Parameters
dataSessionID : in TpSessionID
Specifies the session ID of the data session.
dataSessionChargePlan : in TpDataSessionChargePlan
Specifies the charge plan used.
Raises
TpCommonExceptions, P_SERVICE_INFORMATION_MISSING,
P_SERVICE_FAULT_ENCOUNTERED, P_I
...