SIST ES 204 915-7 V1.1.1:2008
Open Service Access (OSA) - Application Programming Interface (API) - Part 7: Terminal Capabilities SCF (Parlay 6)
- Abstract
ETSI OSA APIs Phase 4. Based on ES 203 915 and the new requirements for OSA Phase 4, to produce ES 204 915 V1.1.1. ETSI OSA Phase 4 incorporates 3GPP OSA Release 7 and is also known as Parlay 6.0.The present document is part 7 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 Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All aspects of the Terminal Capabilities 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).
- Status
- Published
- Publication Date
- 02-Jul-2008
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 11-Jun-2008
- Due Date
- 16-Aug-2008
- Completion Date
- 03-Jul-2008
Buy Documents
ETSI ES 204 915-7 V1.1.1 (2008-02) - Open Service Access (OSA); Application Programming Interface (API); Part 7: Terminal Capabilities SCF (Parlay 6)
ETSI ES 204 915-7 V1.1.1 (2008-05) - Open Service Access (OSA); Application Programming Interface (API); Part 7: Terminal Capabilities SCF (Parlay 6)
SIST ES 204 915-7 V1.1.1:2008 is an ETSI standard for the Open Service Access (OSA) Application Programming Interface (API), Part 7: Terminal Capabilities SCF, also known as Parlay 6. It specifies how an application can retrieve a terminal’s capabilities and, when the network supports it, receive reports when those capabilities change. The document is written for application developers, service platform implementers, and network engineers who need the Terminal Capabilities interface in an OSA environment.
What does SIST ES 204 915-7 V1.1.1:2008 specify?
SIST ES 204 915-7 V1.1.1:2008 specifies the Stage 3 interface definition for the Terminal Capabilities Service Capability Feature (SCF) within OSA. It defines the interface behavior, data types, diagrams, and machine-readable interface descriptions needed to implement the service.
The document is organized from general context to detailed interface content:
- Clauses 1 to 3 cover scope, references, definitions, and abbreviations.
- Clause 4 introduces the Terminal Capabilities SCF and the basic support rules for methods.
- Clauses 5 and 6 provide a sequence example and the class relationships.
- Clause 7 describes the service interface specification format.
- Clause 8 defines the Terminal Capabilities interface classes and methods.
- Clauses 9 to 12 cover state model, service properties, data definitions, and exception classes.
- Annexes A to F provide IDL, WSDL, Java API, 3GPP alignment notes, a cdma2000 interpretation, and a change record.
| Annex | What it covers |
|---|---|
| Annex A | Normative OMG IDL description of the Terminal Capabilities SCF |
| Annex B | Informative W3C WSDL description of the Terminal Capabilities SCF |
| Annex C | Informative Java API description, including J2SE and J2EE forms |
| Annex D | Informative contents mapping for 3GPP OSA R7 Terminal Capabilities |
| Annex E | Informative description for 3GPP2 cdma2000 networks |
| Annex F | Informative record of changes |
What are the key requirements of SIST ES 204 915-7 V1.1.1:2008?
SIST ES 204 915-7 V1.1.1:2008 focuses on two core functions: getting terminal capabilities and monitoring changes in those capabilities. In practice, this means an application can either query the current capability data once or subscribe to reports when the terminal changes.
Method support and error handling
Clause 4.1 sets the basic rule for implemented methods: if an implementation supports a method, it shall support the defined behavior for at least one valid parameter set. For a service interface method that is not supported, the call shall return P_METHOD_NOT_SUPPORTED. For an application interface method that is not supported, the call shall still be possible and shall not raise an exception. This matters because clients must be prepared for optional service behavior and must not assume every interface is implemented.
Callback setup
Clause 7.4.1 defines the generic service callback methods setCallback() and setCallbackWithSessionID(). setCallback() is used for interfaces that do not use session IDs, while setCallbackWithSessionID() is used for interactions tied to a specific session, such as a call or call leg. The service keeps the most recent callback reference and can fall back to an earlier one if the latest reference fails. In practice, applications must register the correct callback interface so the network can send reports back to the right place.
Retrieving terminal capabilities
Clause 8.1 defines IpTerminalCapabilities and the synchronous getTerminalCapabilities() method. The application provides terminalIdentity, and the network returns the latest available terminal capabilities if they are available. The returned information can be expressed as CC/PP headers, including URLs, terminal attributes and values in RDF format, or both. This is the basic read operation for discovering what a terminal can do.
Triggered reporting
Clause 8.2 defines IpExtendedTerminalCapabilities, which supports reporting when capabilities change. triggeredTerminalCapabilityStartReq() takes the application callback interface, a set of terminals, a capability scope, and change criteria, then returns an assignmentID. triggeredTerminalCapabilityStop() uses that assignmentID to stop reporting. This lets an application subscribe only to the kinds of changes it cares about, such as hardware updates, software updates, or general capability changes.
Reports and errors
Clause 8.3 defines IpAppExtendedTerminalCapabilities, the application-side callback interface. triggeredTerminalCapabilityReport() delivers the updated capabilities, while triggeredTerminalCapabilityReportErr() reports a failure and its cause. This separation is important because the application has to handle both successful updates and monitoring failures.
Data model and service property
Clause 11 defines the main data types used by the interface, including TpTerminalCapabilities, TpTerminalCapabilitiesError, TpTerminalCapabilityChangeCriteria, TpTerminalCapabilityScopeType, and TpTerminalCapabilityScope. Clause 10 defines P_TRIGGERED_REPORTING_SUPPORTED, a service property that states whether triggered terminal capability reporting is supported. For implementers, these definitions determine how capability data is structured, how change triggers are filtered, and whether subscription-based monitoring is available.
What terms does SIST ES 204 915-7 V1.1.1:2008 define?
SIST ES 204 915-7 V1.1.1:2008 uses the definitions from ES 204 915-1 and adds the following key interface terms and data types:
terminalIdentity- The identifier of the terminal, which may be a logical address known by the WAP Gateway/PushProxy.TpTerminalCapabilities- A structured data type that carries the latest available terminal capability information and a status code.TpTerminalCapabilitiesError- The error type used when terminal capability reporting fails.TpTerminalCapabilityChangeCriteria- A set of change triggers, such as general change, hardware update, software update, or initial report.TpTerminalCapabilityScopeType- The type used to express the scope format, including CC/PP.TpTerminalCapabilityScope- The structure that combines scope type and scope content.assignmentID- The identifier returned by triggered reporting start requests and used to stop them later.P_TRIGGERED_REPORTING_SUPPORTED- The service property that indicates whether triggered reporting is supported.
Who uses SIST ES 204 915-7 V1.1.1:2008?
SIST ES 204 915-7 V1.1.1:2008 is used by telecom application developers, OSA/Parlay platform vendors, and network integration engineers. They use it to build applications that query terminal capabilities, subscribe to updates, and implement the callback behavior required by the API.
It is also relevant to teams producing UML models, IDL definitions, WSDL descriptions, and Java API realisations for enterprise-based client applications. In practice, this makes it useful for design, implementation, integration testing, and interoperability work in OSA-based service platforms, including 3GPP and 3GPP2-oriented environments.
What changed in SIST ES 204 915-7 V1.1.1:2008 from the previous edition?
SIST ES 204 915-7 V1.1.1:2008 is part of the Parlay 6.0 set of specifications and is equivalent to 3GPP TS 29.198-7 V7.0.0 (Release 7). Annex F records changes by interfaces, methods, data definitions, service properties, exceptions, and other items using new, deprecated, modified, and removed categories.
Which standards are used with SIST ES 204 915-7 V1.1.1:2008?
| Standard | How it is used |
|---|---|
| ETSI ES 204 915-1 | Provides the overview, the shared definitions and abbreviations, the reference list for the series, and the Java realization rules |
| ETSI ES 204 915-2 | Provides common data definitions referenced but not defined in this part |
| 3GPP TS 29.198-7 V7.0.0 | Equivalent Release 7 specification for the same Terminal Capabilities SCF |
What does the SIST ES 204 915-7 V1.1.1:2008 document contain?
SIST ES 204 915-7 V1.1.1:2008 contains one sequence example, one class diagram, detailed method descriptions, and the data definitions needed to implement the Terminal Capabilities SCF. Clause 7 explains the interface notation, including synchronous and asynchronous methods, parameter roles, and state model conventions.
It also contains machine-readable interface artefacts and implementation views. Annex A provides the normative OMG IDL description, Annex B the W3C WSDL description, and Annex C the Java API description in J2SE and J2EE forms. Annex E gives a cdma2000 interpretation for 3GPP2 network environments, and Annex F records the changes by category for this version.
Buy Documents
ETSI ES 204 915-7 V1.1.1 (2008-02) - Open Service Access (OSA); Application Programming Interface (API); Part 7: Terminal Capabilities SCF (Parlay 6)
ETSI ES 204 915-7 V1.1.1 (2008-05) - Open Service Access (OSA); Application Programming Interface (API); Part 7: Terminal Capabilities SCF (Parlay 6)
Get Certified
Connect with accredited certification bodies for this standard
BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
NYCE
Mexican standards and certification body.
Sponsored listings
Frequently Asked Questions
SIST ES 204 915-7 V1.1.1:2008 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Open Service Access (OSA) - Application Programming Interface (API) - Part 7: Terminal Capabilities SCF (Parlay 6)". This standard covers: ETSI OSA APIs Phase 4. Based on ES 203 915 and the new requirements for OSA Phase 4, to produce ES 204 915 V1.1.1. ETSI OSA Phase 4 incorporates 3GPP OSA Release 7 and is also known as Parlay 6.0.The present document is part 7 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 Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All aspects of the Terminal Capabilities 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).
ETSI OSA APIs Phase 4. Based on ES 203 915 and the new requirements for OSA Phase 4, to produce ES 204 915 V1.1.1. ETSI OSA Phase 4 incorporates 3GPP OSA Release 7 and is also known as Parlay 6.0.The present document is part 7 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 Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All aspects of the Terminal Capabilities 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).
SIST ES 204 915-7 V1.1.1:2008 is classified under the following ICS (International Classification for Standards) categories: 35.100.01 - Open systems interconnection in general. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST ES 204 915-7 V1.1.1:2008 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Part 7: Terminal Capabilities SCF
(Parlay 6)
�
2 Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
Reference
DES/TISPAN-01032-7-OSA
Keywords
API, IDL, OSA, 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, 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 foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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 Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
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 Terminal Capabilities SCF .6
4.1 General requirements on support of methods.7
5 Sequence Diagrams.7
5.1 Terminal capabilities example.7
6 Class Diagrams.9
7 The Service Interface Specifications.10
7.1 Interface Specification Format .10
7.1.1 Interface Class.10
7.1.2 Method descriptions.10
7.1.3 Parameter descriptions.10
7.1.4 State Model.10
7.2 Base Interface.10
7.2.1 Interface Class IpInterface .10
7.3 Service Interfaces.11
7.3.1 Overview.11
7.4 Generic Service Interface .11
7.4.1 Interface Class IpService .11
7.4.1.1 Method setCallback().11
7.4.1.2 Method setCallbackWithSessionID().11
8 Terminal Capabilities Interface Classes .12
8.1 Interface Class IpTerminalCapabilities .12
8.1.1 Method getTerminalCapabilities().12
8.2 Interface Class IpExtendedTerminalCapabilities .13
8.2.1 Method triggeredTerminalCapabilityStartReq().13
8.2.2 Method triggeredTerminalCapabilityStop().14
8.3 Interface Class IpAppExtendedTerminalCapabilities .14
8.3.1 Method triggeredTerminalCapabilityReport().15
8.3.2 Method triggeredTerminalCapabilityReportErr().15
9 State Transition Diagrams.16
10 Service Properties.16
11 Terminal Capabilities Data Definitions.16
11.1 terminalIdentity.16
11.2 TpTerminalCapabilities.16
11.3 TpTerminalCapabilitiesError .17
11.4 TpTerminalCapabilityChangeCriteria.17
11.5 TpTerminalCapabilityScopeType.17
11.6 TpTerminalCapabilityScope.17
12 Exception Classes.18
Annex A (normative): OMG IDL Description of Terminal Capabilities SCF .19
Annex B (informative): W3C WSDL Description of Terminal Capabilities SCF.20
ETSI
4 Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
Annex C (informative): Java™ API Description of the Terminal Capabilities SCF .21
Annex D (informative): Contents of 3GPP OSA R7 Terminal Capabilities .22
Annex E (informative): Description of Terminal Capabilities SCF for 3GPP2 cdma2000
networks.23
E.1 General Exceptions.23
E.2 Specific Exceptions.23
E.2.1 Clause 1: Scope .23
E.2.2 Clause 2: References .23
E.2.3 Clause 3: Definitions and abbreviations.23
E.2.4 Clause 4: Terminal Capabilities SCF .23
E.2.5 Clause 5: Sequence Diagrams .23
E.2.6 Clause 6: Class Diagrams.23
E.2.7 Clause 7: The Service Interface Specifications .23
E.2.8 Clause 8: Terminal Capabilities Interface Classes .24
E.2.9 Clause 9: State Transition Diagrams .24
E.2.10 Clause 10: Service Properties.24
E.2.11 Clause 11: Terminal Capabilities Data Definitions .24
E.2.12 Clause 12: Exception Classes.24
E.2.13 Annex A (normative): OMG IDL Description of Terminal Capabilities SCF .24
E.2.14 Annex B (informative): W3C WSDL Description of Terminal Capabilities SCF .24
E.2.15 Annex C (informative): Java™ API Description of Terminal Capabilities SCF.24
Annex F (informative): Record of changes .25
F.1 Interfaces.25
F.1.1 New.25
F.1.2 Deprecated.25
F.1.3 Removed.25
F.2 Methods.25
F.2.1 New.25
F.2.2 Deprecated.25
F.2.3 Modified.26
F.2.4 Removed.26
F.3 Data Definitions.26
F.3.1 New.26
F.3.2 Modified.26
F.3.3 Removed.26
F.4 Service Properties.26
F.4.1 New.26
F.4.2 Deprecated.27
F.4.3 Modified.27
F.4.4 Removed.27
F.5 Exceptions.27
F.5.1 New.27
F.5.2 Modified.27
F.5.3 Removed.27
F.6 Others.27
History .28
ETSI
5 Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
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 Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN), and is now submitted for the ETSI standards
Membership Approval Procedure.
The present document is part 7 of a multi-part deliverable covering Open Service Access (OSA); Application
Programming Interface (API), as identified below. The API specification (ES 204 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";
Part 15: "Multi-Media Messaging SCF"
Part 16: "Service Broker 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 6.0 set of specifications.
The present document is equivalent to 3GPP TS 29.198-7 V7.0.0 (Release 7).
ETSI
6 Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
1 Scope
The present document is part 7 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 Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All
aspects of the Terminal Capabilities 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 204 915-1 contain provisions which, through reference in this text, constitute
provisions of the present document.
ETSI ES 204 915-1: "Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview
(Parlay 6)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 204 915-1 apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 204 915-1 apply.
4 Terminal Capabilities SCF
The following clauses describe each aspect of the Terminal Capabilities 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 shows how each of the interfaces applicable to the SCF, relate to one another.
ETSI
7 Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
• 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 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 ES 204 915-2.
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 Terminal capabilities example
The following example sequence diagram illustrates how the terminal capabilities can be retrieved and their changes
monitored.
ETSI
8 Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
Application : : :
IpAppExtendedTerminalCapabilities IpTerminalCapabilities IpExtendedTerminalCapabilities
1: getTerminalCapability( )
2: new( )
3: triggeredTerminalCapabilityStartReq( )
4: triggeredTerminalCapabilityReport( )
5: forward notification
6: triggeredTerminalCapabilityReport( )
7: forward notification
8: triggeredTerminalCapabilityReportErr( )
9: forward error
10: triggeredTerminalCapabilityReport( )
11: forward notification
12: triggeredTerminalCapabilityStop( )
1: The application retrieves the terminal capability of a terminal.
2: The application creates an object to implement IpAppExtendedTerminalCapabilities.
3: The terminal capabilities changes are started to be monitored.
4: The terminal capabilities have changed and they are reported as requested.
5: The report is forwarded internally to the application.
6: The terminal capabilities have changed and they are reported as requested.
7: The report is forwarded internally to the application.
8: An error has happened in the monitoring and it is reported.
9: The error report is forwarded internally to the application.
10: The terminal capabilities have changed and they are reported as requested.
11: The report is forwarded internally to the application.
12: The terminal capability monitoring is stopped.
ETSI
9 Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
6 Class Diagrams
Terminal Capabilities Class Diagram:
<>
IpInterface
(from csapi)
<>
IpAppExtendedTerminalCapabilities
(from termcap)
triggeredTerminalCapabilityReport()
triggeredTerminalCapabilityReportErr()
<>
<>
IpExtendedTerminalCapabilities
(from termcap)
triggeredTerminalCapabilityStartReq()
triggeredTerminalCapabilityStop()
<>
IpTerminalCapabilities
(from termcap)
getTerminalCapabilities()
<>
IpService
(from csapi)
setCallback()
setCallbackWithSessionID()
Figure 1: Terminal Capabilities Class Diagram
ETSI
10 Final draft ETSI ES 204 915-7 V1.1.1 (2008-02)
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 parameter
...
ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Part 7: Terminal Capabilities SCF
(Parlay 6)
�
2 ETSI ES 204 915-7 V1.1.1 (2008-05)
Reference
DES/TISPAN-01032-7-OSA
Keywords
API, IDL, OSA, 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, 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 foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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 204 915-7 V1.1.1 (2008-05)
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 Terminal Capabilities SCF .6
4.1 General requirements on support of methods.7
5 Sequence Diagrams.7
5.1 Terminal capabilities example.7
6 Class Diagrams.9
7 The Service Interface Specifications.10
7.1 Interface Specification Format .10
7.1.1 Interface Class.10
7.1.2 Method descriptions.10
7.1.3 Parameter descriptions.10
7.1.4 State Model.10
7.2 Base Interface.10
7.2.1 Interface Class IpInterface .10
7.3 Service Interfaces.11
7.3.1 Overview.11
7.4 Generic Service Interface .11
7.4.1 Interface Class IpService .11
7.4.1.1 Method setCallback().11
7.4.1.2 Method setCallbackWithSessionID().11
8 Terminal Capabilities Interface Classes .12
8.1 Interface Class IpTerminalCapabilities .12
8.1.1 Method getTerminalCapabilities().12
8.2 Interface Class IpExtendedTerminalCapabilities .13
8.2.1 Method triggeredTerminalCapabilityStartReq().13
8.2.2 Method triggeredTerminalCapabilityStop().14
8.3 Interface Class IpAppExtendedTerminalCapabilities .14
8.3.1 Method triggeredTerminalCapabilityReport().15
8.3.2 Method triggeredTerminalCapabilityReportErr().15
9 State Transition Diagrams.16
10 Service Properties.16
11 Terminal Capabilities Data Definitions.16
11.1 terminalIdentity.16
11.2 TpTerminalCapabilities.16
11.3 TpTerminalCapabilitiesError .17
11.4 TpTerminalCapabilityChangeCriteria.17
11.5 TpTerminalCapabilityScopeType.17
11.6 TpTerminalCapabilityScope.17
12 Exception Classes.18
Annex A (normative): OMG IDL Description of Terminal Capabilities SCF .19
Annex B (informative): W3C WSDL Description of Terminal Capabilities SCF.20
ETSI
4 ETSI ES 204 915-7 V1.1.1 (2008-05)
Annex C (informative): Java™ API Description of the Terminal Capabilities SCF .21
Annex D (informative): Contents of 3GPP OSA R7 Terminal Capabilities .22
Annex E (informative): Description of Terminal Capabilities SCF for 3GPP2 cdma2000
networks.23
E.1 General Exceptions.23
E.2 Specific Exceptions.23
E.2.1 Clause 1: Scope .23
E.2.2 Clause 2: References .23
E.2.3 Clause 3: Definitions and abbreviations.23
E.2.4 Clause 4: Terminal Capabilities SCF .23
E.2.5 Clause 5: Sequence Diagrams .23
E.2.6 Clause 6: Class Diagrams.23
E.2.7 Clause 7: The Service Interface Specifications .23
E.2.8 Clause 8: Terminal Capabilities Interface Classes .24
E.2.9 Clause 9: State Transition Diagrams .24
E.2.10 Clause 10: Service Properties.24
E.2.11 Clause 11: Terminal Capabilities Data Definitions .24
E.2.12 Clause 12: Exception Classes.24
E.2.13 Annex A (normative): OMG IDL Description of Terminal Capabilities SCF .24
E.2.14 Annex B (informative): W3C WSDL Description of Terminal Capabilities SCF .24
E.2.15 Annex C (informative): Java™ API Description of Terminal Capabilities SCF.24
Annex F (informative): Record of changes .25
F.1 Interfaces.25
F.1.1 New.25
F.1.2 Deprecated.25
F.1.3 Removed.25
F.2 Methods.25
F.2.1 New.25
F.2.2 Deprecated.25
F.2.3 Modified.26
F.2.4 Removed.26
F.3 Data Definitions.26
F.3.1 New.26
F.3.2 Modified.26
F.3.3 Removed.26
F.4 Service Properties.26
F.4.1 New.26
F.4.2 Deprecated.27
F.4.3 Modified.27
F.4.4 Removed.27
F.5 Exceptions.27
F.5.1 New.27
F.5.2 Modified.27
F.5.3 Removed.27
F.6 Others.27
History .28
ETSI
5 ETSI ES 204 915-7 V1.1.1 (2008-05)
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 Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 7 of a multi-part deliverable covering Open Service Access (OSA); Application
Programming Interface (API), as identified below. The API specification (ES 204 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";
Part 15: "Multi-Media Messaging SCF"
Part 16: "Service Broker 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 6.0 set of specifications.
The present document is equivalent to 3GPP TS 29.198-7 V7.0.0 (Release 7).
ETSI
6 ETSI ES 204 915-7 V1.1.1 (2008-05)
1 Scope
The present document is part 7 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 Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All
aspects of the Terminal Capabilities 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 204 915-1 contain provisions which, through reference in this text, constitute
provisions of the present document.
ETSI ES 204 915-1: "Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview
(Parlay 6)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 204 915-1 apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 204 915-1 apply.
4 Terminal Capabilities SCF
The following clauses describe each aspect of the Terminal Capabilities 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 shows how each of the interfaces applicable to the SCF, relate to one another.
ETSI
7 ETSI ES 204 915-7 V1.1.1 (2008-05)
• 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 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 ES 204 915-2.
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 Terminal capabilities example
The following example sequence diagram illustrates how the terminal capabilities can be retrieved and their changes
monitored.
ETSI
8 ETSI ES 204 915-7 V1.1.1 (2008-05)
Application : : :
IpAppExtendedTerminalCapabilities IpTerminalCapabilities IpExtendedTerminalCapabilities
1: getTerminalCapability( )
2: new( )
3: triggeredTerminalCapabilityStartReq( )
4: triggeredTerminalCapabilityReport( )
5: forward notification
6: triggeredTerminalCapabilityReport( )
7: forward notification
8: triggeredTerminalCapabilityReportErr( )
9: forward error
10: triggeredTerminalCapabilityReport( )
11: forward notification
12: triggeredTerminalCapabilityStop( )
1: The application retrieves the terminal capability of a terminal.
2: The application creates an object to implement IpAppExtendedTerminalCapabilities.
3: The terminal capabilities changes are started to be monitored.
4: The terminal capabilities have changed and they are reported as requested.
5: The report is forwarded internally to the application.
6: The terminal capabilities have changed and they are reported as requested.
7: The report is forwarded internally to the application.
8: An error has happened in the monitoring and it is reported.
9: The error report is forwarded internally to the application.
10: The terminal capabilities have changed and they are reported as requested.
11: The report is forwarded internally to the application.
12: The terminal capability monitoring is stopped.
ETSI
9 ETSI ES 204 915-7 V1.1.1 (2008-05)
6 Class Diagrams
Terminal Capabilities Class Diagram:
<>
IpInterface
(from csapi)
<>
IpAppExtendedTerminalCapabilities
(from termcap)
triggeredTerminalCapabilityReport()
triggeredTerminalCapabilityReportErr()
<>
<>
IpExtendedTerminalCapabilities
(from termcap)
triggeredTerminalCapabilityStartReq()
triggeredTerminalCapabilityStop()
<>
IpTerminalCapabilities
(from termcap)
getTerminalCapabilities()
<>
IpService
(from csapi)
setCallback()
setCallbackWithSessionID()
Figure 1: Terminal Capabilities Class Diagram
ETSI
10 ETSI ES 204 915-7 V1.1.1 (2008-05)
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
...
SLOVENSKI STANDARD
01-september-2008
Odprti dostop do storitve (OSA) - Aplikacijski programski vmesnik (API) - 7. del:
Lastnost storitvene zmožnosti (SCF) za zmožnosti terminalov (Parlay 6)
Open Service Access (OSA) - Application Programming Interface (API) - Part 7: Terminal
Capabilities SCF (Parlay 6)
Ta slovenski standard je istoveten z: ES 204 915-7 Version 1.1.1
ICS:
35.100.01 Medsebojno povezovanje Open systems
odprtih sistemov na splošno interconnection 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 7: Terminal Capabilities SCF
(Parlay 6)
�
2 ETSI ES 204 915-7 V1.1.1 (2008-05)
Reference
DES/TISPAN-01032-7-OSA
Keywords
API, IDL, OSA, 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, 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 foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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 204 915-7 V1.1.1 (2008-05)
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 Terminal Capabilities SCF .6
4.1 General requirements on support of methods.7
5 Sequence Diagrams.7
5.1 Terminal capabilities example.7
6 Class Diagrams.9
7 The Service Interface Specifications.10
7.1 Interface Specification Format .10
7.1.1 Interface Class.10
7.1.2 Method descriptions.10
7.1.3 Parameter descriptions.10
7.1.4 State Model.10
7.2 Base Interface.10
7.2.1 Interface Class IpInterface .10
7.3 Service Interfaces.11
7.3.1 Overview.11
7.4 Generic Service Interface .11
7.4.1 Interface Class IpService .11
7.4.1.1 Method setCallback().11
7.4.1.2 Method setCallbackWithSessionID().11
8 Terminal Capabilities Interface Classes .12
8.1 Interface Class IpTerminalCapabilities .12
8.1.1 Method getTerminalCapabilities().12
8.2 Interface Class IpExtendedTerminalCapabilities .13
8.2.1 Method triggeredTerminalCapabilityStartReq().13
8.2.2 Method triggeredTerminalCapabilityStop().14
8.3 Interface Class IpAppExtendedTerminalCapabilities .14
8.3.1 Method triggeredTerminalCapabilityReport().15
8.3.2 Method triggeredTerminalCapabilityReportErr().15
9 State Transition Diagrams.16
10 Service Properties.16
11 Terminal Capabilities Data Definitions.16
11.1 terminalIdentity.16
11.2 TpTerminalCapabilities.16
11.3 TpTerminalCapabilitiesError .17
11.4 TpTerminalCapabilityChangeCriteria.17
11.5 TpTerminalCapabilityScopeType.17
11.6 TpTerminalCapabilityScope.17
12 Exception Classes.18
Annex A (normative): OMG IDL Description of Terminal Capabilities SCF .19
Annex B (informative): W3C WSDL Description of Terminal Capabilities SCF.20
ETSI
4 ETSI ES 204 915-7 V1.1.1 (2008-05)
Annex C (informative): Java™ API Description of the Terminal Capabilities SCF .21
Annex D (informative): Contents of 3GPP OSA R7 Terminal Capabilities .22
Annex E (informative): Description of Terminal Capabilities SCF for 3GPP2 cdma2000
networks.23
E.1 General Exceptions.23
E.2 Specific Exceptions.23
E.2.1 Clause 1: Scope .23
E.2.2 Clause 2: References .23
E.2.3 Clause 3: Definitions and abbreviations.23
E.2.4 Clause 4: Terminal Capabilities SCF .23
E.2.5 Clause 5: Sequence Diagrams .23
E.2.6 Clause 6: Class Diagrams.23
E.2.7 Clause 7: The Service Interface Specifications .23
E.2.8 Clause 8: Terminal Capabilities Interface Classes .24
E.2.9 Clause 9: State Transition Diagrams .24
E.2.10 Clause 10: Service Properties.24
E.2.11 Clause 11: Terminal Capabilities Data Definitions .24
E.2.12 Clause 12: Exception Classes.24
E.2.13 Annex A (normative): OMG IDL Description of Terminal Capabilities SCF .24
E.2.14 Annex B (informative): W3C WSDL Description of Terminal Capabilities SCF .24
E.2.15 Annex C (informative): Java™ API Description of Terminal Capabilities SCF.24
Annex F (informative): Record of changes .25
F.1 Interfaces.25
F.1.1 New.25
F.1.2 Deprecated.25
F.1.3 Removed.25
F.2 Methods.25
F.2.1 New.25
F.2.2 Deprecated.25
F.2.3 Modified.26
F.2.4 Removed.26
F.3 Data Definitions.26
F.3.1 New.26
F.3.2 Modified.26
F.3.3 Removed.26
F.4 Service Properties.26
F.4.1 New.26
F.4.2 Deprecated.27
F.4.3 Modified.27
F.4.4 Removed.27
F.5 Exceptions.27
F.5.1 New.27
F.5.2 Modified.27
F.5.3 Removed.27
F.6 Others.27
History .28
ETSI
5 ETSI ES 204 915-7 V1.1.1 (2008-05)
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 Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 7 of a multi-part deliverable covering Open Service Access (OSA); Application
Programming Interface (API), as identified below. The API specification (ES 204 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";
Part 15: "Multi-Media Messaging SCF"
Part 16: "Service Broker 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 6.0 set of specifications.
The present document is equivalent to 3GPP TS 29.198-7 V7.0.0 (Release 7).
ETSI
6 ETSI ES 204 915-7 V1.1.1 (2008-05)
1 Scope
The present document is part 7 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 Terminal Capabilities Service Capability Feature (SCF) aspects of the interface. All
aspects of the Terminal Capabilities 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 204 915-1 contain provisions which, through reference in this text, constitute
provisions of the present document.
ETSI ES 204 915-1: "Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview
(Parlay 6)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 204 915-1 apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 204 915-1 apply.
4 Terminal Capabilities SCF
The following clauses describe each aspect of the Terminal Capabilities 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 shows how each of the interfaces applicable to the SCF, relate to one another.
ETSI
7 ETSI ES 204 915-7 V1.1.1 (2008-05)
• 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 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 ES 204 915-2.
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 Terminal capabilities example
The following example sequence diagram illustrates how the terminal capabilities can be retrieved and their changes
monitored.
ETSI
8 ETSI ES 204 915-7 V1.1.1 (2008-05)
Application : : :
IpAppExtendedTerminalCapabilities IpTerminalCapabilities IpExtendedTerminalCapabilities
1: getTerminalCapability( )
2: new( )
3: triggeredTerminalCapabilityStartReq( )
4: triggeredTerminalCapabilityReport( )
5: forward notification
6: triggeredTerminalCapabilityReport( )
7: forward notification
8: triggeredTerminalCapabilityReportErr( )
9: forward error
10: triggeredTerminalCapabilityReport( )
11: forward notification
12: triggeredTerminalCapabilityStop( )
1: The application retrieves the terminal capability of a terminal.
2: The application creates an object to implement IpAppExtendedTerminalCapabilities.
3: The terminal capabilities changes are started to be monitored.
4: The terminal capabilities have changed and they are reported as requested.
5: The report is forwarded internally to the application.
6: The terminal capabilities have changed and they are reported as requested.
7: The report is forwarded internally to the application.
8: An error has happened in the monitoring and it is reported.
9: The error report is forwarded internally to the application.
10: The terminal capabilities have changed and they are reported as requested.
11: The report is forwarded internally to the application.
12: The terminal capability monitoring is stopped.
ETSI
9 ETSI ES 204 915-7 V1.1.1 (2008-05)
6 Class Diagrams
Terminal Capabilities Class Diagram:
<>
IpInterface
(from csapi)
<>
IpAppExtendedTerminalCapabilities
(from termcap)
triggeredTerminalCapabilityReport()
triggeredTerminalCapabilityReportErr()
<>
<>
IpExtendedTerminalCapabilities
(from termcap)
triggeredTerminalCapabilityStartReq()
triggeredTerminalCapabilityStop()
<>
IpTerminalCapabilities
(from termcap)
getTerminalCapabilities()
<>
IpService
(from csapi)
setCallback()
setCallbackWithSessionID()
Figure 1: Terminal Capabilities Class Diagram
ETSI
10 ETSI ES 204 915-7 V1.1.1 (2008-05)
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 Langu
...