SIST ES 201 915-1 V1.4.1:2005

• Abstract:

  Maintenance update of ES 201 915 v1.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-1 V1.4.1 (2003-07) - Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 3)

SIST ES 201 915-1 V1.4.1:2005 is the SIST adoption of ETSI ES 201 915-1, Open Service Access (OSA); Application Programming Interface (API) - Part 1: Overview. It explains the structure and methodology of the OSA API set, which lets application developers use network service capability features through a standardized interface.

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

SIST ES 201 915-1 V1.4.1:2005 specifies the overview for the OSA API specification and the relationship between its parts and related standards. It is the Stage 3 overview for an API family that exposes network capabilities to applications through the OSA interface.

Clause 4 describes the three interface classes used in the OSA API:

• applications to the Framework for basic mechanisms such as authentication
• applications to Service Capability Features (SCF)
• Framework to SCF for multi-vendorship support

Clause 5 explains the document structure, including sequence diagrams, class relationships, interface specifications, state transition diagrams and data definitions. The same clause also notes that the purpose of the API is to hide network complexity and protocol details from applications.

Clause 1 to Clause 7 cover scope, references, definitions and abbreviations, the OSA API model, document structure, methodology, and the relationship between ETSI, Parlay and 3GPP OSA releases.

Annex	What it covers
Annex A	OMG IDL and CORBA-oriented interface definition details
Annex B	Bibliography

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

SIST ES 201 915-1 V1.4.1:2005 sets out how the OSA API is described, named and represented so that different implementations can interwork. The practical effect is that developers and tool builders have a common modeling and naming approach for the interfaces.

OSA interface model

Clause 4 states that OSA API interfaces are organized around applications, the Framework and SCF. This matters because it separates generic functions such as authentication from service-specific functions such as messaging or call control.

Modeling and specification language

Clause 5 and Clause 6.1 say that UML is used for class and state transition diagrams, and that interfaces are specified in IDL. In practice, this gives both a readable model and a machine-oriented interface definition.

Packaging and names

Clause 6.2 and Clause 6.4 define a hierarchical packaging scheme rooted at org.csapi, plus naming rules for packages, interfaces, classes, methods, constants and collections. This helps keep names consistent across languages and avoids clashes in large API sets.

State and error handling

Clause 6.5 gives the text convention used for State Transition Diagrams, and Clause 6.6 says methods report errors through exceptions while results are returned through the return value. In practice, this means no method out parameters are used, which simplifies mapping to many programming languages.

References and type passing

Clause 6.7 says in parameters are passed by reference using a Ref suffix on the type name. Clause 6.8 says String is used for character strings and homogeneous collections use the <datatype>Set pattern. This supports predictable data handling in interface implementations.

Release relationships

Clause 7 relates ETSI, Parlay and 3GPP OSA releases and explains that 3GPP updates may occur more frequently. This matters when matching an implementation or procurement decision to the correct release family.

Normative IDL

Annex A makes OMG IDL the normative interface definition language and shows how IDL is checked and how collections and namespaces are handled in CORBA-oriented implementations. That is the part to use when turning the API model into code.

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

SIST ES 201 915-1 V1.4.1:2005 defines the vocabulary used across the OSA API set, including several key abbreviations.

• Open Service Access (OSA) - the standardized interface approach that lets applications access network service capability features.
• Service Capability Feature (SCF) - functionality offered by service capabilities and accessible through the OSA interface.
• Service Capability Server - the functional entity that provides OSA interfaces toward an application.
• Personal Service Environment (PSE) - personalized information that defines how subscribed services are provided and presented.
• Virtual Home Environment (VHE) - the portability concept for the personal service environment across networks and terminals.
• Value Added Service Provider (VASP) - a provider of services beyond basic telecommunications service.
• Application Programming Interface (API) - the interface used by software applications to access functions.

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

SIST ES 201 915-1 V1.4.1:2005 is used by service application developers, service designers, network architects, and implementers working with telecom service platforms. It is also relevant to operators, service suppliers, and teams responsible for framework administration tools and enterprise operator administration tools.

The document fits environments where OSA services are exposed over standardized interfaces in telecommunications systems. The references to UMTS, GSM, PLMN, WAP, MAP and CAP show the intended ecosystem of mobile and network-service integration.

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

SIST ES 201 915-1 V1.4.1:2005 is a maintenance update of ES 201 915 v1.3.1. The updated document is also known as Parlay 3.3, and it states that only the parts requiring modification are updated, with most parts receiving maintenance fixes.

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

SIST ES 201 915-1 V1.4.1:2005 relies on several referenced documents for vocabulary, service principles, network protocols and data formats.

• TR 121 905 - provides the UMTS vocabulary used for abbreviations and terminology.
• TS 122 101 - supplies service principles and definitions used in Clause 3.
• TS 129 002 and TS 129 078 - provide MAP and CAP references for network-side context.
• ISO 8601, ISO 4217 and ISO 639 - define dates and times, currency codes, and language codes.
• IETF RFC 822 and IETF RFC 1738 - support message format and URL usage.
• OMG IDL and CORBA-related tools - support the interface definition approach in Annex A.

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

SIST ES 201 915-1 V1.4.1:2005 contains an overview of the full OSA API set, plus the structure used by the other parts. It includes the packaging hierarchy, naming rules, state transition text conventions, and the relationship table between ETSI, Parlay and 3GPP releases.

The document also points to the kinds of technical artefacts used elsewhere in the series: sequence diagrams, class relationships, interface specifications, state transition diagrams and data definitions. Annex A adds IDL-oriented interface definition details and namespace examples, which are the pieces most directly used for implementation and code generation.

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

Reference
RES/SPAN-120095-1
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-1 V1.4.1 (2003-07)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope.5
2 References.5
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations.7
4 Open Service Access API's .8
5 Document structure.9
6 Methodology.10
6.1 Tools and Languages.10
6.2 Packaging Structure.10
6.3 Colours.13
6.4 Naming scheme.13
6.5 State Transition Diagram text and text symbols.14
6.6 Exception handling and passing results.14
6.7 References.14
6.8 Strings and Collections.14
6.9 Prefixes.14
7 Relationship between ETSI, Parlay and 3GPP OSA releases .14
Annex A (normative): OMG IDL .16
A.1 Tools and languages .16
A.2 Strings and collections.16
A.3 Naming space across CORBA modules.16
Annex B (informative): Bibliography.17
History .18

ETSI
4 ETSI ES 201 915-1 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 1 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-1 V4.3.2 (Release 4).
ETSI
5 ETSI ES 201 915-1 V1.4.1 (2003-07)
1 Scope
The present document is part 1 of the Stage 3 specification for an Application Programming Interface (API) for Open
Service Access (OSA), and provides an overview of the content and structure of the various parts of the present
document, and of the relation to other standards documents.
The OSA specifications define an architecture that enables service application developers to make use of network
functionality through an open standardized interface, i.e. the OSA APIs.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
[1] ETSI TR 121 905: "Universal Mobile Telecommunications System (UMTS); Vocabulary for
3GPP Specifications (3GPP TR 21.905)".
[2] ETSI TS 122 024: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Description of Charge Advice Information (CAI)
(3GPP TS 22.024)".
[3] ITU-T Recommendation Q.850: "Usage of cause and location in the Digital Subscriber Signalling
System No. 1 and the Signalling System No. 7 ISDN User Part".
[4] ITU-T Recommendation Q.2931: "Digital Subscriber Signalling System No. 2 - User-Network
Interface (UNI) layer 3 specification for basic call/connection control".
[5] ETSI TS 122 101: "Universal Mobile Telecommunications System (UMTS); Service aspects;
Service principles (3GPP TS 22.101)".
[6] World Wide Web Consortium: "Composite Capability/Preference Profiles (CC/PP): A user side
framework for content negotiation".
NOTE: http://www.w3.org/TR/NOTE-CCPP/.
[7] ETSI TS 129 002: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Mobile Application Part (MAP) specification
(3GPP TS 29.002)".
[8] ETSI TS 129 078: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Customized Applications for Mobile network Enhanced
Logic (CAMEL); CAMEL Application Part (CAP) specification (3GPP TS 29.078)".
[9] Wireless Application Protocol (WAP) Version 1.2: "User Agent Profiling Specification"
(WAP-174).
NOTE: http://www.wapforum.org/what/technical_1_2.htm.
[10] Wireless Application Protocol (WAP) Version 1.2: "WAP Service Indication Specification"
(WAP-167).
NOTE: http://www.wapforum.org/what/technical_1_2.htm.
ETSI
6 ETSI ES 201 915-1 V1.4.1 (2003-07)
[11] Wireless Application Protocol (WAP) Version 1.2: "Push Architectural Overview" (WAP-165).
NOTE: http://www.wapforum.org/what/technical_1_2.htm.
[12] Wireless Application Protocol (WAP) Version 1.2: "Wireless Application Protocol Architecture
Specification" (WAP-100).
NOTE: http://www.wapforum.org/what/technical_1_2.htm.
[13] ETSI TS 122 002: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Circuit Bearer Services (BS) supported by a Public Land
Mobile Network (PLMN) (3GPP TS 22.002)".
[14] ETSI TS 122 003: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Circuit Teleservices supported by a Public Land Mobile
Network (PLMN) (3GPP TS 22.003)".
[15] ETSI TS 124 002: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); GSM-UMTS Public Land Mobile Network (PLMN) access
reference configuration (3GPP TS 24.002)".
[16] ITU-T Recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes".
[17] ITU-T Recommendation Q.931: "ISDN user-network interface layer 3 specification for basic call
control".
[18] ISO 8601: "Data elements and interchange formats - Information interchange - Representation of
dates and times".
[19] ISO 4217: "Codes for the representation of currencies and funds".
[20] ISO 639: "Code for the representation of names of languages".
[21] IETF RFC 822: "Standard for the format of ARPA Internet text messages".
[22] IETF RFC 1738: "Uniform Resource Locators (URL)".
[23] ETSI TS 129 198-1: "ETSI TS 129 198 (V3.4.0): "Universal Mobile Telecommunications System
(UMTS); Open Service Architecture (OSA) Application Programming Interface
(API) - Part 1 (3GPP TS 29.198 version 3.4.0 Release 1999)".".
[24] ETSI TS 129 198 V4 (all parts): "Universal Mobile Telecommunications System (UMTS); Open
Service Access (OSA) Application Programming Interface (API); (3GPP TS 29.198 Release 4)".
[25] ETSI TS 123 107: "Universal Mobile Telecommunications System (UMTS); Quality of Service
(QoS) concept and architecture (3GPP TS 23.107)".
[26] ETSI TS 123 271:"Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Location Services (LCS); Functional description; Stage 2
(3GPP TS 23.271)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TS 122 101 [5] and the following apply:
applications: services, which are designed using service capability features
ETSI
7 ETSI ES 201 915-1 V1.4.1 (2003-07)
gateway: synonym for Service Capability Server
NOTE 1: From the viewpoint of applications, a Service Capability Server can be seen as a gateway to the core
network.
NOTE 2: This is a VASP that has an agreement with the Home Environment to provide services.
Home Environment: responsible for overall provision of services to users
Local Service: service which can be exclusively provided in the current serving network by a Value Added Service
Provider
OSA Interface: standardized Interface used by application to access service capability features
Personal Service Environment (PSE): contains personalized information defining how subscribed services are
provided and presented towards the user
NOTE: The Personal Service Environment is defined in terms of one or more User Profiles.
Service: alternative for Service Capability Feature (in the present document)
Service Capabilities (SC): bearers defined by parameters, and/or mechanisms needed to realize services
NOTE: These are within networks and under network control.
Service Capability Feature (SCF): functionality offered by service capabilities that are accessible via the standardized
OSA interface
Service Capability Server: Functional Entity providing OSA interfaces towards an application
User Interface Profile: contains information to present the personalized user interface within the capabilities of the
terminal and serving network
User Profile: label identifying a combination of one user interface profile, and one user services profile
User Services Profile: contains identification of subscriber services, their status and reference to service preferences
Value Added Service Provider: provides services other than basic telecommunications service for which additional
charges may be incurred
Virtual Home Environment: concept for personal service environment portability across network boundaries and
between terminals
3.2 Abbreviations
For the purposes of the present document, the abbreviations defined in TR 121 905 [1] and the following apply:
API Application Programming Interface
CAMEL Customized Application for Mobile Network Enhanced Logic
CSE Camel Service Environment
HE Home Environment
HE-VASP Home Environment Value Added Service Provider
HLR Home Location Register
IDL Interface Description Language
INAP Intelligent Networks Application Part
MAP Mobile Application Part
ME Mobile Equipment
MExE Mobile Station (Application) Execution Environment
MS Mobile Station
MSC Mobile Switching Centre
OSA Open Service Access
PLMN Public Land Mobile Network
PSE Personal Service Environment
SAT SIM Application Tool-Kit
SC Service Capabilities
ETSI
8 ETSI ES 201 915-1 V1.4.1 (2003-07)
SCF Service Capability Feature
SCP Service Control Point
SIM Subscriber Identity Module
SMS Short Message Service
SMTP Simple Mail Transfer Protocol
STD State Transition Diagrams
USIM User Service Identity Module
VASP Value Added Service Provider
VHE Virtual Home Environment
VLR Visited Location Register
WAP Wireless Application Protocol
WGP Wireless Gateway Proxy
WPP Wireless Push Proxy
4 Open Service Access API's
The OSA specifications define an architecture that enables service application developers to make use of network
functionality through an open standardized interface, i.e. the OSA API's. The network functionality is describes as
Service Capability Features or Services (see note). The OSA Framework is a general component in support of Services
(Service Capabilities) and Applications.
The OSA API is split into three types of int
...