SIST ES 202 915-8 V1.2.1:2005

• Abstract:

  Maintenance update of ES 202 915-8 V1.1.1 to produce ES 202 915-8 V1.2.1 Updated document will also be known as PARLAY 4.1. Only those parts requiring modification will be updated ( most parts require maintenance fixes )

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.01 - Telecommunication systems in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI ES 202 915-8 V1.2.1 (2003-08) - Open Service Access (OSA); Application Programming Interface (API); Part 8: Data Session Control SCF (Parlay 4)

SIST ES 202 915-8 V1.2.1:2005 is the Slovenian adoption of ETSI ES 202 915-8 Version 1.2.1 for Open Service Access (OSA) Application Programming Interface (API), Part 8: Data Session Control SCF (Parlay 4). It specifies the interface that lets application developers control data sessions and receive data-session events through the OSA API, using the same structure and behavior defined for Parlay 4.1.

What does SIST ES 202 915-8 V1.2.1:2005 specify?

SIST ES 202 915-8 V1.2.1:2005 specifies the Data Session Control Service Capability Feature (SCF) part of the OSA API. The document defines how an application can request, supervise, release, deassign, and receive notifications about data sessions, with the interfaces modeled using Unified Modelling Language (UML).

The document is organized around the service behavior first, then the interface details. It includes sequence diagrams, class diagrams, interface specifications, state transition diagrams, data definitions, and formal IDL and WSDL descriptions.

Annex	What it covers
Annex A	OMG IDL description of Data Session Control SCF
Annex B	W3C WSDL description of Data Session Control SCF
Annex C	Contents of 3GPP OSA R5 Data Session Control
Annex D	Record of changes

The scope also states that this is a maintenance update from ES 202 915-8 V1.1.1 to ES 202 915-8 V1.2.1, and that the updated document is also known as Parlay 4.1.

What are the key requirements of SIST ES 202 915-8 V1.2.1:2005?

SIST ES 202 915-8 V1.2.1:2005 defines two core service areas in Clause 4 - the Data Session manager and the Data Session object. In practice, this means one interface manages notifications and session-level administration, while the other controls the session itself. A session is controlled by one Data Session Manager only, but one manager can control several sessions.

Clause 4.1 sets a basic implementation rule: if an implementation supports a method, it shall implement that method for at least one valid set of parameter values. If a service method is not supported, the call shall return P_METHOD_NOT_SUPPORTED. For application interfaces, unsupported methods may still be callable and shall not raise an exception. This matters because service-side and application-side behavior are treated differently.

Clause 7 defines the interface style and callback pattern. Synchronous and asynchronous methods are both used, and asynchronous requests use the Req suffix with matching Res or Err callbacks. The application or service developer therefore has to implement the matching callback interface when responses or reports are expected.

The generic service interface in Clause 7.4 provides two callback registration methods:

• setCallback()
• setCallbackWithSessionID()

These methods let a service point its callbacks to an application interface, either generally or for a specific session ID. The document states that setCallbackWithSessionID() is only allowed when SessionIDs are used, and setCallback() is not allowed on an interface that uses SessionIDs.

The main service interface in Clause 8.3, IpDataSession, is the operational interface for session control. The minimum methods that shall be implemented are connectReq(), release(), deassignDataSession(), and continueProcessing(). In practice, these are the functions a platform needs for establishing, ending, clearing, and resuming a data session.

Clause 8.4, IpDataSessionControlManager, is the SCF manager interface for notification handling. The document says that at minimum either createNotifications() and destroyNotification(), or enableNotifications() and disableNotifications(), shall be implemented. This gives two notification models:

• application-created notifications with createNotifications()
• network-provisioned notifications with enableNotifications()

The notification methods are tightly controlled. createNotifications() uses event criteria, assignment IDs, and callback references, and overlapping criteria can be refused with P_INVALID_CRITERIA. enableNotifications() is for notifications provisioned from within the network, and repeated calls return the same assignment ID. This matters for integration because notification ownership and overlap rules affect how service logic is configured.

The state model in Clause 9 shows how the data session object moves through Setup, Established, Active, Finished, Network Released, and Application Released states. In practice, this tells implementers when they may call supervision, charging, release, or continue-processing functions, and when the network or application has control.

Clause 10 lists service properties used to describe supported events, address plans, monitor modes, charging permissions, charge-plan mappings, and allowed currencies. These properties are important for service-level agreement checks and for limiting what an application may request on a given deployment.

What terms does SIST ES 202 915-8 V1.2.1:2005 define?

Open Service Access (OSA) is the architecture that lets application developers use network functionality through an open standardized interface.

Application Programming Interface (API) is the interface set that applications use to invoke service functions and receive callbacks.

Service Capability Feature (SCF) is the functional part of OSA that exposes a specific network capability, here Data Session Control.

IpDataSession is the service-side interface used to control a data session, including connect, release, supervision, and charging actions.

IpDataSessionControlManager is the service manager interface used to create or enable notifications and manage notification criteria.

IpAppDataSession is the application-side callback interface used to receive connect results, supervision results, and fault indications.

IpAppDataSessionControlManager is the application-side callback interface used to receive data-session event notifications and abort indications.

Unified Modelling Language (UML) is the modeling method used in the document to describe interfaces, relationships, and state behavior.

Who uses SIST ES 202 915-8 V1.2.1:2005?

Application developers use SIST ES 202 915-8 V1.2.1:2005 to build software that reacts to data-session setup, release, supervision, and notification events. They use the document to implement the IpAppDataSession and IpAppDataSessionControlManager callback interfaces and to decide when to request supervision or charging actions.

Network and platform engineers use it to expose Data Session Control through OSA/Parlay interfaces. For them, the important tasks are mapping the service to network behavior, handling session state transitions, and configuring notification criteria and service properties.

Test and quality teams use it to verify method behavior, callback flow, state transitions, and notification handling. Buyers and integrators use it to check whether a platform supports the required data-session control functions and the expected API style.

What changed in SIST ES 202 915-8 V1.2.1:2005 from the previous edition?

SIST ES 202 915-8 V1.2.1:2005 updates ES 202 915-8 V1.1.1 and is identified as Parlay 4.1. The record of changes states that network notification support was added through enableNotifications() and disableNotifications(), and that getNotifications() and createNotifications() replace the earlier getNotification() and createNotification() methods.

The change record also notes data definition updates, including the correction of P_DATA_SESSION_USER_ABORTED to P_DATA_SESSION_FAULT_USER_ABORTED, the rename of OriginatingAddress to OriginationAddress in TpDataSessionEventCriteria, and the move of TpDataSessionQoSClass to Part 2, the common data definitions. It also records the removal of P_SERVICE_INFORMATION_MISSING and P_SERVICE_FAULT_ENCOUNTERED.

Which standards are used with SIST ES 202 915-8 V1.2.1:2005?

ES 202 915-1, Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 4), supplies the shared definitions and abbreviations used by this part and the overall OSA API framework.

ES 202 915-2, Open Service Access (OSA); Application Programming Interface (API); Part 2: Common Data Definitions (Parlay 4), supplies common data types that this part references but does not define itself.

The foreword also states that the document is equivalent to 3GPP TS 29.198-8 V5.2.0 (Release 5), and Annex C links the content to 3GPP OSA R5 Data Session Control.

What does the SIST ES 202 915-8 V1.2.1:2005 document contain?

SIST ES 202 915-8 V1.2.1:2005 contains sequence diagrams for network-controlled notifications, enabling data-session notifications, and address translation with charging. It also contains class diagrams, interface method descriptions, state transition diagrams, and a service-properties table that describes supported event types, address plans, monitor modes, and charging constraints.

The data-definition clause expands the main event, report, fault, supervision, and charge-plan types used by the interface methods. Annex A provides the formal OMG IDL form, and Annex B provides the W3C WSDL form, which are useful for implementation, code generation, and interoperability work.

Annex D records the changes by interface, method, data definition, service property, and exception. For implementers, that annex is the quickest way to see which names were added, deprecated, corrected, or removed when moving to this edition.

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 4)
Ta slovenski standard je istoveten z: ES 202 915-8 Version 1.2.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 4)
�
2 ETSI ES 202 915-8 V1.2.1 (2003-08)

Reference
RES/SPAN-120096-8
Keywords
API, IDL, OSA, UML
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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:
[e-mail]
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 202 915-8 V1.2.1 (2003-08)
Contents
Intellectual Property Rights.6
Foreword.6
1 Scope.7
2 References.7
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Data Session Control SCF.8
4.1 General requirements on support of methods.9
5 Sequence Diagrams.9
5.1 Network Controlled Notifications .9
5.2 Enable Data Session Notification.10
5.3 Address Translation With Charging.10
6 Class Diagrams.11
7 The Service Interface Specifications.12
7.1 Interface Specification Format .12
7.1.1 Interface Class.12
7.1.2 Method descriptions.12
7.1.3 Parameter descriptions.12
7.1.4 State Model.12
7.2 Base Interface.12
7.2.1 Interface Class IpInterface .12
7.3 Service Interfaces.13
7.3.1 Overview.13
7.4 Generic Service Interface .13
7.4.1 Interface Class IpService .13
7.4.1.1 Method setCallback().13
7.4.1.2 Method setCallbackWithSessionID().13
8 Data Session Control Interface Classes.14
8.1 Interface Class IpAppDataSession .14
8.1.1 Method connectRes().14
8.1.2 Method connectErr().15
8.1.3 Method superviseDataSessionRes().15
8.1.4 Method superviseDataSessionErr().15
8.1.5 Method dataSessionFaultDetected().16
8.2 Interface Class IpAppDataSessionControlManager .16
8.2.1 Method dataSessionAborted().16
8.2.2 Method reportNotification().17
8.2.3 Method dataSessionNotificationContinued().17
8.2.4 Method dataSessionNotificationInterrupted().17
8.3 Interface Class IpDataSession .18
8.3.1 Method connectReq().18
8.3.2 Method release().19
8.3.3 Method superviseDataSessionReq().19
8.3.4 Method setDataSessionChargePlan().20
8.3.5 Method setAdviceOfCharge().20
8.3.6 Method deassignDataSession().20
8.3.7 Method continueProcessing().21
8.4 Interface Class IpDataSessionControlManager.21
8.4.1 Method <> createNotification() .22
8.4.2 Method destroyNotification().22
ETSI
4 ETSI ES 202 915-8 V1.2.1 (2003-08)
8.4.3 Method changeNotification().23
8.4.4 Method <> getNotification().23
8.4.5 Method <> enableNotifications().23
8.4.6 Method <> disableNotifications().24
8.4.7 Method <> getNotifications() .24
8.4.8 Method <> createNotifications() .25
9 State Transition Diagrams.26
9.1 State Transition Diagrams for IpDataSession.26
9.1.1 Network Released State .26
9.1.2 Finished State.26
9.1.3 Application Released State.27
9.1.4 Active State.27
9.1.5 Setup State.27
9.1.6 Established State.27
10 Data Session Control Service Properties.28
11 Data Definitions.29
11.1 Data Session Control Data Definitions.29
11.1.1 IpAppDataSession.29
11.1.2 IpAppDataSessionRef.29
11.1.3 IpAppDataSessionControlManager.29
11.1.4 IpAppDataSessionControlManagerRef.29
11.1.5 IpDataSession.29
11.1.6 IpDataSessionRef.29
11.1.7 IpDataSessionControlManager.29
11.1.8 IpDataSessionControlManagerRef.29
11.2 Event Notification data definitions.29
11.2.1 TpDataSessionEventName.29
11.2.2 TpDataSessionMonitorMode.30
11.2.3 TpDataSessionEventCriteria.30
11.2.4 TpDataSessionEventInfo.30
11.2.5 TpDataSessionChargePlan.31
11.2.6 TpDataSessionChargeOrder.31
11.2.7 TpDataSessionChargeOrderCategory.31
11.2.8 TpChargePerVolume.32
11.2.9 TpDataSessionIdentifier.32
11.2.10 TpDataSessionError.32
11.2.11 TpDataSessionAdditionalErrorInfo.32
11.2.12 TpDataSessionErrorType.32
11.2.13 TpDataSessionFault.33
11.2.14 TpDataSessionReleaseCause.33
11.2.15 TpDataSessionSuperviseVolume.33
11.2.16 TpDataSessionSuperviseReport.33
11.2.17 TpDataSessionSuperviseTreatment.34
11.2.18 TpDataSessionReport.34
11.2.19 TpDataSessionAdditionalReportInfo.34
11.2.20 TpDataSessionReportRequest.34
11.2.21 TpDataSessionReportRequestSet.34
11.2.22 TpDataSessionReportType.35
11.2.23 TpDataSessionEventCriteriaResult.35
11.2.24 TpDataSessionEventCriteriaResultSet.35
Annex A (normative): OMG IDL Description of Data Session Control SCF.36
Annex B (informative): W3C WSDL Description of Data Session Control SCF .37
Annex C (informative): Contents of 3GPP OSA R5 Data Session Control.38
Annex D (informative): Record of changes .39
D.1 Interfaces.39
D.1.1 New.39
ETSI
5 ETSI ES 202 915-8 V1.2.1 (2003-08)
D.1.2 Deprecated.39
D.1.3 Removed.39
D.2 Methods.40
D.2.1 New.40
D.2.2 Deprecated.40
D.2.3 Modified.40
D.2.4 Removed.41
D.3 Data Definitions.41
D.3.1 New.41
D.3.2 Modified.41
D.3.3 Removed.41
D.4 Service Properties.41
D.4.1 New.41
D.4.2 Deprecated.42
D.4.3 Modified.42
D.4.4 Removed.42
D.5 Exceptions.42
D.5.1 New.42
D.5.2 Modified.42
D.5.3 Removed.43
D.6 Others.43
History .44

ETSI
6 ETSI ES 202 915-8 V1.2.1 (2003-08)
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 202 915) is structured in the following
parts:
Part 1: "Overview";
Part 2: "Common Data Definitions";
Part 3: "Framework";
Part 4: "Call Control";
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";
Part 13: "Policy management SCF";
Part 14: "Presence and Availability Management 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 4.1 set of specifications.
The present document is equivalent to 3GPP TS 29.198-8 V5.2.0 (Release 5).
ETSI
7 ETSI ES 202 915-8 V1.2.1 (2003-08)
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
• WSDL 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 202 915-1 contain provisions which, through reference in this text, constitute
provisions of the present document.
ETSI ES 202 915-1: "Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview
(Parlay 4)".
ETSI ES 202 915-2: "Open Service Access (OSA); Application Programming Interface (API); Part 2: Common Data
Definitions (Parlay 4)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 915-1 apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations defined in ES 202 915-1 apply.
ETSI
8 ETSI ES 202 915-8 V1.2.1 (2003-08)
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
enableNotifications setAdviceofCharge
disableNotifications 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 ES 202 915-2.
ETSI
9 ETSI ES 202 915-8 V1.2.1 (2003-08)
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 Network Controlled Notifications
The following sequence diagram shows how an application can receive notifications that have not been created by the
application, but are provisioned from within the network.
AppLogic : :
IpAppDataSessionControlManager IpDataSessionControlManager
1: new ( )
2: enableNotifications( )
3: reportNotification(  )
4: 'forward event'
5: reportNotification(  )
6: 'forward event'
7: disableNotifications( )
ETSI
10 ETSI ES 202 915-8 V1.2.1 (2003-08)
1: The application is started. The application creates a new IpAppDataSessionControlManager to handle callbacks.
2: The enableNotifications method is invoked on the IpDataSessionControlManager interface to indicate that the
application is ready to receive notifications that are created in the network. For illustrative purposes we assume
notifications of type "B" are created in the network.
3: When a network created trigger occurs the application is notified on the callback interface.
4: The event is forwarded to the application.
5: When a network created trigger occurs the application is notified on the callback interface.
6: The event is forwarded to the application.
7: When the application does not want to receive notifications created in the network anymore, it invokes
disableNotifications on the IpDataSessionConrolManager interface. From now on the gateway will not send any
notifications to the application that are created in the network. The application will still receive notifications that it has
created himself until the application removes them.
5.2 Enable Data Session Notification
Applicat ion Data Session Manager : Data Session :
IpDataSessionControlManager IpDataSession
1: createNotification( )
ETSI
11 ETSI ES 202 915-8 V1.2.1 (2003-08)
5.3 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
12 ETSI ES 202 915-8 V1.2.1 (2003-08)
6 Class Diagrams
Data Session Control Class Diagram:
<>
IpInterface
(from csapi)
<>
<>
IpAppDataSession
IpAppDataSessionControlManager
(from dsc)
(from dsc)
connectRes()
dataSessionAborted()
101 0.nn
connectErr()
reportNotification()
superviseDataSessionRes()
dataSessionNotificationContinued()
superviseDataSessionErr()
dataSessionNotificationInterrupted()
dataSessionFaultDetected()
<>
<>
<>
<>
IpDataSessionControlManager
IpDataSession
(from dsc)
(from dsc)
<> createNotification()
connectReq()
destroyNotification()
release()
changeNotification()
11 00.n.n
superviseDataSessionReq()
<> getNotification()
setDataSessionChargePlan()
<> enableNotifications()
setAdviceOfCharge()
<> disableNotifications()
deassignDataSession()
<> getNotifications()
continueProcessing()
<> createNotifications()
<>
IpService
(from csapi)
setCallback()
setCallbackWithSessionID()
Figure 2: Package Overview
ETSI
13 ETSI ES 202 915-8 V1.2.1 (2003-08)
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
14 ETSI ES 202 915-8 V1.2.1 (2003-08)
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

7.4.1.1 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

7.4.1.2 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.
Parameters
appInterface : in IpInterfaceRef
Specifies a reference to the application interface, which is used for callbacks.
ETSI
15 ETSI ES 202 915-8 V1.2.1 (2003-08)
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

8.1.1 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).
Parameters
dataSessionID : in TpSessionID
Specifies the session ID of the data session.
ETSI
16 ETSI ES 202 915-8 V1.2.1 (2003-08)
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

8.1.2 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

8.1.3 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.

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

8.1.5 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

8.2.1 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.

ETSI
18 ETSI ES 202 915-8 V1.2.1 (2003-08)
8.2.2 Method reportNotification()
This meth
...