SIST ES 201 915-7 V1.4.1:2005

• Abstract:

  Maintenance update of ES 201 915-7 v.1.3.1. Updated document will also be known as Parlay 3.3. 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 201 915-7 V1.4.1 (2003-07) - Open Service Access (OSA); Application Programming Interface (API); Part 7: Terminal Capabilities SCF (Parlay 3)

SIST ES 201 915-7 V1.4.1:2005 is the Slovenian standard identical to ETSI ES 201 915-7 V1.4.1 for Open Service Access (OSA) application programming interfaces. It specifies the Terminal Capabilities Service Capability Feature (SCF), which lets an application query the latest available capabilities of a user's terminal through the OSA interface. The document is a maintenance update of ES 201 915-7 v1.3.1 and is also known as Parlay 3.3.

What does SIST ES 201 915-7 V1.4.1:2005 specify?

SIST ES 201 915-7 V1.4.1:2005 specifies the Stage 3 interface for the Terminal Capabilities SCF in the OSA API. In practice, it defines how an application asks the network for a terminal's capabilities, how the interface is structured, and what data comes back.

The scope covers the Terminal Capabilities SCF aspects of the interface, including sequence diagrams, class diagrams, interface specifications, state transition diagrams, data definitions, and the IDL description of the interfaces. The document is organized into clauses for scope, references, definitions and abbreviations, the SCF overview, sequence diagrams, class diagrams, service interface specifications, interface classes, state transition diagrams, data definitions, and exception classes.

Annex	What it covers
Annex A	Normative OMG IDL description of the Terminal Capabilities SCF
Annex B	Informative contents of 3GPP OSA R4 Terminal Capabilities
Annex C	Informative record of changes

What are the key requirements of SIST ES 201 915-7 V1.4.1:2005?

SIST ES 201 915-7 V1.4.1:2005 requires an implementation to support the documented functionality for any method it implements, for at least one valid set of parameter values. This matters because a partial implementation still has to behave predictably for the cases it claims to support.

Method support and error handling

If a Service interface method is not supported, the implementation shall return P_METHOD_NOT_SUPPORTED. If an Application interface method is not supported, the call shall still be possible and no exception shall be returned. For an implementer, this sets the boundary between a rejectable service-side capability and a callback-side interface that must remain callable.

Callback setup through IpService

SIST ES 201 915-7 V1.4.1:2005 uses the generic service interface IpService for callback registration. setCallback() is used to register an application callback interface when the interface does not use SessionIDs, while setCallbackWithSessionID() is used for session-based interactions tied to a specific TpSessionID. This is important for developers because the wrong callback method, or the wrong interface type, must trigger the documented exceptions.

Terminal Capabilities access

The Terminal Capabilities SCF is exposed through IpTerminalCapabilities, which inherits from IpService. The minimum required method is getTerminalCapabilities(), and the application supplies terminalIdentity as input. The method returns the latest available terminal capabilities if they are available in the network, or a status indicating whether they are available. In practice, this is the single query an application needs to retrieve terminal capability information.

Returned capability data

The capabilities returned by getTerminalCapabilities() are described as CC/PP headers, as specified in W3C and adopted in WAP UAProf. The returned information can contain URLs, terminal attributes and values in RDF format, or a combination of both. That tells a developer or integrator what kind of payload to expect and how it may be represented.

Data definitions and error reporting

The data type TpTerminalCapabilities is a structured sequence with the terminal capabilities content and a status flag. The SCF error type TpTerminalCapabilitiesError covers undefined error, invalid terminal ID, and system failure conditions. The exception class P_INVALID_TERMINAL_ID carries extra information in TpString. For test and integration work, these definitions show both the result shape and the failure cases that must be handled.

No sequence or state diagrams for this SCF

The document states that there are no Sequence Diagrams and no State Transition Diagrams for the Terminal Capabilities SCF. For readers, that means the behavior is presented mainly through the interface and data definitions rather than through stateful interaction models.

What terms does SIST ES 201 915-7 V1.4.1:2005 define?

SIST ES 201 915-7 V1.4.1:2005 uses the shared OSA terms from ES 201 915-1 and defines several interface-specific items in this part.

• OSA - Open Service Access, the architecture that lets applications use network functions through an open standardized interface.
• SCF - Service Capability Feature, the functional area of the API covered by this part.
• UML - Unified Modelling Language, the object-modelling notation used for class, interface and state descriptions.
• IDL - Interface Definition Language, used in Annex A to express the interface in OMG IDL form.
• IpTerminalCapabilities - The service interface that provides access to terminal capabilities.
• TpTerminalCapabilities - The structured data type that carries the returned capability information and availability status.
• CC/PP - Composite Capabilities/Preference Profiles, the header format used to represent terminal capability information.
• UAProf - User Agent Profile, the WAP profile model referenced for the returned capability data.

Who uses SIST ES 201 915-7 V1.4.1:2005?

SIST ES 201 915-7 V1.4.1:2005 is used by application developers, service developers, and telecom system integrators working with OSA/Parlay interfaces. It is also relevant to QA and test teams that need to verify callback setup, terminal identity handling, return data, and exception behavior.

In practice, it is used when building or validating applications that need to query terminal capability information from the network. Buyers and architects use it when they need to confirm that a platform exposes the Terminal Capabilities SCF and that the interface behavior matches the OSA model.

What changed in SIST ES 201 915-7 V1.4.1:2005 from the previous edition?

SIST ES 201 915-7 V1.4.1:2005 is a maintenance update of ES 201 915-7 v1.3.1 and is also identified as Parlay 3.3. The change record highlights that IpTerminalCapabilities was changed to inherit from IpService, and that the element order in TpTerminalCapabilities was adjusted to match the IDL.

The annex also organizes change tracking by interfaces, methods, data definitions, service properties, exceptions, and other items. That helps readers check where a revised behavior or data structure belongs when comparing versions.

Which standards are used with SIST ES 201 915-7 V1.4.1:2005?

SIST ES 201 915-7 V1.4.1:2005 uses ES 201 915-1 for the shared OSA overview, terms, abbreviations, and referenced provisions. It relies on ES 201 915-2 for common data definitions that are not defined again in this part.

The foreword also places this part within the broader ES 201 915 series, where Part 1 is the overview and Part 2 is the common data definitions. For implementers, that means this part should be read together with the shared framework and data model in the other parts.

What does the SIST ES 201 915-7 V1.4.1:2005 document contain?

SIST ES 201 915-7 V1.4.1:2005 contains the interface model for the Terminal Capabilities SCF, including the generic service interface, the IpTerminalCapabilities interface, and the data types used by getTerminalCapabilities(). It also contains the method descriptions, parameter descriptions, and the data definitions for terminalIdentity, TpTerminalCapabilities, and TpTerminalCapabilitiesError.

Annex A provides the OMG IDL representation as a companion file named termcap.idl. Annex B relates the document to 3GPP OSA R4 Terminal Capabilities, and Annex C records the interface, method, data definition, service property, and exception changes tracked for this version.

SLOVENSKI STANDARD
01-januar-2005
Odprti dostop do storitve (OSA) – Vmesnik za aplikacijsko programiranje (API) – 7.
del: Terminalske zmožnosti SCF
Open Service Access (OSA); Application Programming Interface (API); Part 7: Terminal
Capabilities SCF (Parlay 3)
Ta slovenski standard je istoveten z: ES 201 915-7 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 7: Terminal Capabilities SCF
(Parlay 3)
�
2 ETSI ES 201 915-7 V1.4.1 (2003-07)

Reference
RES/SPAN-120095-7
Keywords
API, OSA, IDL, 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 201 915-7 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 Terminal Capabilities SCF .6
4.1 General requirements on support of methods.7
5 Sequence Diagrams.7
6 Class Diagrams.7
7 The Service Interface Specifications.8
7.1 Interface Specification Format .8
7.1.1 Interface Class.8
7.1.2 Method descriptions.8
7.1.3 Parameter descriptions.8
7.1.4 State Model.8
7.2 Base Interface.9
7.2.1 Interface Class IpInterface .9
7.3 Service Interfaces.9
7.3.1 Overview.9
7.4 Generic Service Interface .9
7.4.1 Interface Class IpService .9
8 Terminal Capabilities Interface Classes .10
8.1 Interface Class IpTerminalCapabilities .10
9 State Transition Diagrams.11
10 Terminal Capabilities Data Definitions.11
10.1 terminalIdentity.11
10.2 TpTerminalCapabilities.11
10.3 TpTerminalCapabilitiesError.12
11 Exception Classes.12
Annex A (normative): OMG IDL Description of Terminal Capabilities SCF .13
Annex B (informative): Contents of 3GPP OSA R4 Terminal Capabilities .14
Annex C (informative): Record of changes .15
C.1 Interfaces.15
C.1.1 New.15
C.1.2 Deprecated.15
C.1.3 Modified.15
C.1.4 Removed.15
C.2 Methods.15
C.2.1 New.15
C.2.2 Deprecated.16
C.2.3 Modified.16
C.2.4 Removed.16
C.3 Data Definitions.16
ETSI
4 ETSI ES 201 915-7 V1.4.1 (2003-07)
C.3.1 New.16
C.3.2 Modified.16
C.3.3 Removed.16
C.4 Service Properties.17
C.4.1 New.17
C.4.2 Deprecated.17
C.4.3 Modified.17
C.4.4 Removed.17
C.5 Exceptions.17
C.5.1 New.17
C.5.2 Modified.17
C.5.3 Removed.18
C.6 Others.18
History .19

ETSI
5 ETSI ES 201 915-7 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 7 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-7 V4.5.0 (Release 4).
ETSI
6 ETSI ES 201 915-7 V1.4.1 (2003-07)
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
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 l
...