SIST ES 203 915-1 V1.3.1:2008

• Abstract:

  Update of ES 203 915 to become Parlay 5.2. Only those parts requiring modification will be updated (most parts require maintenance fixes).The present document is part 1 of the Stage 3 specification for an Application Programming Interface 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.

• Status: Published
• Publication Date: 15-Jul-2008
• 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: 11-Jun-2008
• Due Date: 16-Aug-2008
• Completion Date: 16-Jul-2008
• Ref Project: ETSI ES 203 915-1 V1.3.1 (2008-04) - Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 5)

SIST ES 203 915-1 V1.3.1:2008 is the overview part of the ETSI Open Service Access (OSA) Application Programming Interface (API) specification for Parlay 5. It explains how OSA lets service application developers use network functionality through a standardized interface, and it sets out the document structure, design rules, and technology mappings used across the API set. The document is written for people implementing, integrating, or evaluating OSA interfaces and service capability features.

What does SIST ES 203 915-1 V1.3.1:2008 specify?

SIST ES 203 915-1 V1.3.1:2008 specifies the overview for the Stage 3 OSA API specification. Its scope is to explain the content and structure of the other parts of ES 203 915 and the relationship to related standards documents.

The document also explains the OSA architecture: service application developers use network functionality through an open standardized interface, and the network functions are described as Service Capability Features or Services. Clause 4 states that the API is split into four interface classes, and that the interfaces outside those four roles are not yet in scope for this version.

The specification is organized as follows.

Annex / part	What it covers
Part 1	Overview
Part 2	Common Data Definitions
Part 3	Framework
Part 4	Call Control, with sub-parts for common definitions, Generic Call Control SCF, Multi-Party Call Control SCF, Multi-Media Call Control SCF, and Conference Call Control SCF
Parts 5-15	The individual SCFs: User Interaction, Mobility, Terminal Capabilities, Data Session Control, Generic Messaging, Connectivity Manager, Account Management, Charging, Policy Management, Presence and Availability Management, and Multi-Media Messaging
Annex A	OMG IDL realisation
Annex B	W3C WSDL realisation
Annex C	Java™ Realisation API
Annex D	Overview for 3GPP2 cdma2000 networks
Annex E	Bibliography

What are the key requirements of SIST ES 203 915-1 V1.3.1:2008?

SIST ES 203 915-1 V1.3.1:2008 is mainly a rulebook for how the OSA API family is structured and how it is realized in different technologies. The most important points are the interface model, the naming and packaging rules, the way calls and callbacks work, and the compatibility rules for later releases.

Interface model and scope

Clause 4 distinguishes four interface classes: application-to-framework, application-to-SCF, framework-to-SCF, and enterprise-operator-to-framework. In practice, this tells implementers which side of the system owns each interaction, such as basic access, service use, multi-vendor support, or account administration.

Clause 7 adds that interfaces can be application side, SCF side, shared, or framework side, and it gives the naming prefixes used for each type. That matters because generated APIs, code reviews, and integration tests all depend on consistent role naming.

Method, session, and callback behavior

Clause 7 describes the Service Manager pattern, where a separate object is created for each application that uses an SCF. It also explains sessions, session IDs, and when a single interface instance represents one session or many sessions.

The same clause defines callback registration and the two callback-setting methods, setCallback() and setCallbackWithSessionID(). For a user of the API, this is the rule that decides how events, results, and errors are returned to the application.

Clause 7 also separates synchronous methods from asynchronous Req / Res / Err methods. Asynchronous operations return an Assignment ID so requests can be matched with later responses, which is important when several requests are active at once.

Naming, data, and error handling

Clause 6 sets the packaging and naming conventions, including the org.csapi root package, Ip interface names, Tp data types, P_ constants, and the Ref suffix for input references. This keeps the API consistent across UML, IDL, WSDL, and Java™ mappings.

Clause 6 also states that methods use input parameters only, that results are returned through the return value, and that out parameters are not used. In practice, that makes the API easier to map to multiple middleware technologies.

Clause 7.9 to 7.11 define an exception hierarchy, common exceptions, and the use of NULL. That gives developers a standard way to handle resource limits, invalid state, unsupported methods, policy problems, and optional values.

Notifications and compatibility

Clause 7.12 describes notification handling, including application-created and network-controlled notifications, NOTIFY and INTERRUPT modes, and the way callback references override the default callback. This matters for service logic that must report events such as answer, busy, or on-hook conditions.

Clause 8 and Clause 9 cover the relationship between ETSI, Parlay, and 3GPP OSA releases, and the backwards-compatibility rules. For upgrades, the key practical point is that older clients are intended to continue working with newer servers or gateways when the versioning rules are followed.

Technology realisations

Annex A is the normative CORBA IDL realisation, Annex B is the WSDL mapping for SOAP/HTTP, and Annex C is the Java™ realisation API. These annexes give the concrete mapping rules that code generators and platform teams need for implementation, testing, and interoperability work.

What terms does SIST ES 203 915-1 V1.3.1:2008 define?

• OSA - Open Service Access, the architecture that lets applications access network functionality through a standardized interface.
• SCF - Service Capability Feature, functionality offered by service capabilities and reachable through the OSA interface.
• SCS - Service Capability Server, the functional entity that provides OSA interfaces towards an application.
• PSE - Personal Service Environment, the personalized information that defines how subscribed services are provided and presented to the user.
• VHE - Virtual Home Environment, the concept of making the personal service environment portable across network boundaries and between terminals.
• HE-VASP - Home Environment Value Added Service Provider, a VASP that has an agreement with the Home Environment to provide services.
• API - Application Programming Interface, the standardized interface used by applications and service components to exchange calls and data.

Who uses SIST ES 203 915-1 V1.3.1:2008?

SIST ES 203 915-1 V1.3.1:2008 is used by telecommunications application developers, service platform vendors, and network architects working on OSA-based services. It is also used by people who implement Framework, SCF, and gateway components, because the document defines the interface model and the technology mappings.

Quality managers, buyers, and system integrators use it to check whether a product or platform supports the expected OSA structure, callback behavior, and release compatibility rules. Enterprise operators and service providers use the framework-side concepts when they need to manage client application accounts, service contracts, and profiles.

What changed in SIST ES 203 915-1 V1.3.1:2008 from the previous edition?

This edition updates ES 203 915 to become Parlay 5.2. The scope states that only the parts requiring modification are updated, while most parts receive maintenance fixes.

The foreword also places this document in the Parlay 5.2 set and identifies it as part 1 of the multi-part OSA specification family.

Which standards are used with SIST ES 203 915-1 V1.3.1:2008?

Clause 2 names a broad set of companion standards and reference documents. The most directly relevant ones for this overview are:

Standard	What it contributes
TR 121 905	Vocabulary for 3GPP specifications, including many abbreviations used in the document
TS 122 101	Service principles and definitions used for OSA terminology
ES 203 915-2	Common Data Definitions for the OSA API family
ES 203 915-3	Framework part of the OSA API family
ES 203 915-4-1 to ES 203 915-4-5	Call Control common definitions and the Call Control SCFs
ES 203 915-5 to ES 203 915-15	The other SCF parts listed in the foreword

The normative references also include technology and domain standards used by the service parts and annex mappings, such as ITU-T signaling recommendations, ISO date and code standards, IETF protocol and policy RFCs, CORBA 2.4.2, and standards for WSDL and Java™.

What does the SIST ES 203 915-1 V1.3.1:2008 document contain?

• A figure showing the OSA interface roles and where the in-scope interfaces sit in the wider architecture.
• A structured description of the document family, including the API parts and the mapping document relationship.
• Methodology rules for UML-based specification, packaging, naming, exception handling, references, strings, collections, and prefixes.
• Detailed guidance on service and session handling, callback registration, synchronous and asynchronous methods, and notification behavior.
• Backwards-compatibility rules for versioned Framework and service releases, including deprecation handling.
• Annex mappings for CORBA IDL, WSDL, and Java™, with rules for namespaces, object references, data type mapping, interface mapping, and exceptions.

Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)
ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Part 1: Overview
(Parlay 5)
�
2 Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)

Reference
RES/TISPAN-01055-01-OSA
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, 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 203 915-1 V1.3.1 (2008-02)
Contents
Intellectual Property Rights.6
Foreword.6
1 Scope.7
2 References.7
3 Definitions and abbreviations.10
3.1 Definitions.10
3.2 Abbreviations.11
4 Open Service Access APIs.12
5 Document structure.13
6 Methodology.15
6.1 Tools and Languages.15
6.2 Packaging Structure.15
6.3 Colours.17
6.4 Naming scheme.17
6.5 State Transition Diagram text and text symbols.18
6.6 Exception handling and passing results.18
6.7 References.18
6.8 Strings and Collections.18
6.9 Prefixes.19
7 Introduction to Parlay/OSA APIs.19
7.1 Interface Types.19
7.2 Service Factory.19
7.3 Use of Sessions.19
7.4 Interfaces and Sessions.19
7.5 Callback Interfaces.20
7.6 Setting Callbacks.20
7.7 Synchronous versus Asynchronous Methods .20
7.8 Out Parameters.20
7.9 Exception Hierarchy.21
7.10 Common Exceptions.21
7.11 Use of NULL.21
7.12 Notification Handling.21
8 Relationship between ETSI, Parlay and 3GPP OSA releases .22
9 Backwards Compatibility Considerations .23
9.1 Guidelines to enable backwards compatibility in implementations .24
9.2 Rule summary.24
9.2.1 Server side permitted changes .24
9.2.2 Client side permitted changes .24
9.2.3 Data type permitted changes.24
9.3 Implementation Guidelines for Server Programmers .24
9.4 Implementation Guidelines for Client Programmers.25
9.5 Tracking the changes in the specifications .25
9.5.1 New Tag.25
9.5.2 Deprecated Tag.25
9.6 Technology realization rules .25
9.6.1 Corba IDL Rules.25
9.6.2 Java rules.25
9.7 Rules for removal of deprecated items from the specifications.26
Annex A (normative): OMG IDL .27
ETSI
4 Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)
A.1 Tools and languages .27
A.2 Namespace.27
A.3 Object References.27
A.4 Mapping of Datatypes .27
A.4.1 Basic Datatypes.27
A.4.2 Constants.27
A.4.3 Collections.28
A.4.4 Sequences.28
A.4.5 Enumerations.28
A.4.6 Choices.28
A.5 Use of NULL.29
A.6 Exceptions.29
A.7 Naming space across CORBA modules.29
Annex B (informative): W3C WSDL.30
B.1 Tools and Languages.30
B.2 Proposed Namespaces for the OSA WSDL .30
B.3 Object References.31
B.4 Mapping UML Data Types to XML Schema.31
B.4.1 Data Types.31
B.4.1.1 <>.32
B.4.1.2 <>.32
B.4.1.3 <>.32
B.4.1.4 <>.33
B.4.1.5 <>.33
B.4.1.6 <>.33
B.5 Mapping of UML Interfaces to WSDL .34
B.5.1 Mapping of UML Operations to WSDL message element.34
B.5.2 Mapping of Exception to WSDL message element.34
B.5.3 Mapping of Interface Class to WSDL portType and binding elements.34
B.5.4 Mapping of UML Interfaces to WSDL service element.35
Annex C (informative): Java™ Realisation API .36
C.1 Java™ Realisation Overview .36
C.1.1 J2SE™ API.36
C.1.2 J2EE™ API.36
C 1.3 Javadoc™ .36
C.2 Tools and languages .37
C.3 Generic Mappings (Elements common to J2SE™ and J2EE™).37
C.3.1 Namespace.37
C.3.2 Package Naming Conventions.37
C.3.3 Object References.37
C.3.4 Element Naming.38
C.3.5 Element Naming Collisions.38
C.3.6 Data Type Definitions .38
C.3.6.1 Basic Data Types .38
C.3.6.2 Constants .38
C.3.6.3 NumberedSetsOfDataElements (Collections).39
C.3.6.4 SequenceOfDataElements (Structures).39
C.3.6.5 NameValuePair (Enumerations) .40
C.3.6.6 TaggedChoiceOfDataElements (Unions) .41
C.3.6.7 Exceptions.43
C.3.6.7.1 PlatformException.43
ETSI
5 Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)
C.3.6.7.2 P_XXX_XXX Exceptions.44
C.3.6.7.3 TpCommonExceptions.44
C.3.6.7.4 TpCommonException's associated exceptions.45
C.3.6.7.5 Additional abstract exceptions .45
C.3.6.7.6 InvalidUnionAccessorException.46
C.3.6.7.7 InvalidEnumValueException.46
C.3.6.8 Deprecation.46
C.4 J2SE™ Specific Conventions.47
C.4.1 Removal of "Tp" Prefix.47
C.4.2 Constants.47
C.4.3 Removal of "Ip" prefix .47
C.4.4 Mapping of IpInterface.48
C.4.5 Mapping of IpService.48
C.4.6 Mapping of UML Operations.48
C.4.7 Mapping of TpSessionID .49
C.4.8 Mapping of TpAssignmentID to the creation of an Activity object .49
C.4.9 Callback Rule.52
C.4.10 Factory Rule.53
C.4.11 J2SE™ Specific Exceptions .55
C.4.11.1 PeerUnavailableException.55
C.4.11.2 IllegalStateException.55
C.4.12 User Interaction Specific Rules .56
C.4.12.1 Interfaces representing UML IpUI and IpUICall Rule .56
C.4.12.2 Naming Collisions of IpUI and IpUICall Rule .56
C.4.12.3 Naming Collisions of IpUICall and IpUIAdminManager Rule .56
C.5 J2EE™ Specific Conventions .56
C.5.1 Void.56
C.5.2 Remote Interface Definitions .56
C.5.2.1 IpInterface.56
C.5.2.2 Methods for Remote Interfaces.56
C.5.3 Local Interface Definitions.57
C.5.3.1 Methods for Local Interfaces.57
C.5.4 Multi Party Call Control Specific Rules.57
C.5.4.1 IpCallLeg and IpAppCallLeg method name conflicts .57
Annex D (informative): Description of Overview for 3GPP2 cdma2000 networks.58
D.1 General Exceptions.58
D.2 Specific Exceptions.58
D.2.1 Clause 1: Scope .58
D.2.2 Clause 2: References .58
D.2.3 Clause 3: Definitions and abbreviations.58
D.2.4 Clause 4: Open Service Access APIs .58
D.2.5 Clause 5: Structure of the OSA API (29.198) and Mapping (29.998) documents .58
D.2.6 Clause 6: Methodology .58
D.2.7 Clause 7: Introduction to OSA APIs .58
D.2.8 Annex A (normative): OMG IDL.59
D.2.9 Annex B (informative): W3C WSDL.59
D.2.10 Annex C (informative): Java™ API.59
Annex E (informative): Bibliography.60
History .61

ETSI
6 Final draft ETSI ES 203 915-1 V1.3.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 1 of a multi-part deliverable covering Open Service Access (OSA); Application
Programming Interface (API), as identified below. The API specification (ES 203 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".
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 5.2 set of specifications.
The present document is equivalent to 3GPP TS 29.198-1 V6.5.0 (Release 6).
ETSI
7 Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)
1 Scope
The present document is part 1 of the Stage 3 specification for an Application Programming Interface 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
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.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the purposes
of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); 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". (http://www.w3.org/TR/NOTE-CCPP/).
ETSI
8 Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)
[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 2.0: "User Agent Profiling Specification" (WAP-
248). (http://www.wapforum.org/what/technical.htm).
[10] 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)".
[11] 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)".
[12] 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)".
[13] ITU-T Recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes".
[14] ITU-T Recommendation Q.931: "ISDN user-network interface layer 3 specification for basic call
control".
[15] ISO 8601: "Data elements and interchange formats - Information interchange - Representation of
dates and times".
[16] ISO 4217: "Codes for the representation of currencies and funds".
[17] ISO 639: "Code for the representation of names of languages".
[18] IETF RFC 822: "Standard for the format of ARPA Internet text messages".
[19] IETF RFC 1738: "Uniform Resource Locators (URL)".
[20] 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)".
[21] ETSI TS 129 198 (all parts): "Universal Mobile Telecommunications System (UMTS); Open
Service Access (OSA) Application Programming Interface (API); (3GPP TS 29.198 Release 6)".
[22] ETSI TS 123 107: "Universal Mobile Telecommunications System (UMTS); Quality of Service
(QoS) concept and architecture" (3GPP TS 23.107)".
[23] ETSI TS 123 271: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Functional stage 2 description of Location Services (LCS)
(3GPP TS 23.271)".
[24] ANSI T1.113: "Signalling System No. 7 (SS7) - Integrated Services Digital Network (ISDN) User
Part".
[25] IETF RFC 3261: "SIP: Session Initiation Protocol".
[26] ITU-T Recommendation Q.932: "Digital subscriber signalling system No. 1 - Generic procedures
for the control of ISDN supplementary services".
[27] ITU-T Recommendation H.221: "Frame structure for a 64 to 1920 kbit/s channel in audiovisual
teleservices".
[28] ITU-T Recommendation H.323: "Packet-based multimedia communications systems".
ETSI
9 Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)
[29] IETF RFC 1994: "PPP Challenge Handshake Authentication Protocol (CHAP)".
[30] IETF RFC 2630: "Cryptographic Message Syntax".
[31] IETF RFC 2313: "PKCS #1: RSA Encryption Version 1.5".
[32] IETF RFC 2459: "Internet X.509 Public Key Infrastructure Certificate and CRL Profile".
[33] IETF RFC 2437: "PKCS #1: RSA Cryptography Specifications Version 2.0".
[34] IETF RFC 1321: "The MD5 Message-Digest Algorithm".
[35] IETF RFC 2404: "The Use of HMAC-SHA-1-96 within ESP and AH".
[36] IETF RFC 2403: "The Use of HMAC-MD5-96 within ESP and AH".
[37] ITU-T Recommendation G.722: "7 kHz audio-coding within 64 kbit/s".
[38] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies".
[39] ITU-T Recommendation G.723.1: "Speech coders: Dual rate speech coder for multimedia
communications transmitting at 5.3 and 6.3 kbit/s".
[40] ITU-T Recommendation G.728: "Coding of speech at 16 kbit/s using low-delay code excited
linear prediction".
[41] ITU-T Recommendation G.729: "Coding of speech at 8 kbit/s using conjugate-structure algebraic-
code-excited linear-prediction (CS-ACELP)".
[42] ITU-T Recommendation H.261: "Video codec for audiovisual services at p x 64 kbit/s".
[43] ITU-T Recommendation H.263: "Video coding for low bit rate communication".
[44] ITU-T Recommendation H.262: "Information technology - Generic coding of moving pictures and
associated audio information: Video".
[45] World Geodetic System 1984 (WGS 84). (http://www.wgs84.com/files/wgsman24.pdf).
NOTE: The above link is temporarily not accessible. The following mirror site may contain the same information,
but has not been verified by ETSI.
http://octopus.hit.bme.hu/tkatona/mirrors/WGS84/www.wgs84.com/files/wgsman24.pdf
[46] ITU-T Recommendation X.400: "Message handling services: Message handling system and
service overview".
[47] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[48] IETF RFC 2445: "Internet Calendaring and Scheduling Core Object Specification (iCalendar)".
[49] IETF RFC 2778: "A Model for Presence and Instant Messaging".
[50] ITU-T Recommendation Q.1238-2: "Interface Recommendation for Intelligent Network
Capability Set 3: SCF - SSF interface".
[51] IETF RFC 3460: "Policy Core Information Model (PCIM) Extensions".
[52] 3GPP2 P.S0001-B: "Wireless IP Network Standard", Version 1.0, October 2002.
[53] 3GPP2 S.R0037-0: "IP Network Architecture Model for cdma2000 Spread Spectrum Systems",
Version 2.0, May 2002.
[54] 3GPP2 X.S0013: "All-IP Core Network Multimedia Domain", December 2003.
[55] ETSI ES 201 915: "Open Service Access (OSA); Application Programming Interface (API)
(Parlay 3)".
[56] ETSI ES 202 915: "Open Service Access (OSA); Application Programming Interface (API)
(Parlay 4)".
ETSI
10 Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)
[57] ETSI ES 203 915-2: "Open Service Access (OSA); Application Programming Interface (API); Part
2: Common Data Definitions (Parlay 5)".
[58] IETF RFC 1737: "Functional Requirements for Uniform Resource Names".
[59] ITU-T Recommendation T.120: "Data protocols for multimedia conferencing".
[60] ISO/IEC 11172-2: "Information technology - Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s - Part 2: Video".
[61] ISO/IEC 11172-3: "Information technology - Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s - Part 3: Audio".
[62] ISO/IEC 13818-3: "Information technology - Generic coding of moving pictures and associated
audio information - Part 3: Audio".
[63] ISO/IEC 14496-2: "Information technology - Coding of audio-visual objects - Part 2: Visual".
[64] draft-ietf-simple-message-sessions-15.txt: "The Message Session Relay Protocol".
[65] IETF RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet
Message Bodies".
[66] IETF RFC 2183: "Communicating Presentation Information in Internet Messages: The Content-
Disposition Header Field".
[67] CORBA 2.4.2: "The Common Object Request Broker: Architecture and Specification", February
2001. http://www.omg.org/cgi-bin/doc?formal/01-02-33.
[68] IETF RFC 2822: "Internet Message Format".
[69] IETF RFC 3060: "Policy Core Information Model - Version 1 Specification".
[70] IETF RFC 2591: "Definitions of Managed Objects for Scheduling Management Operations".
[71] DMTF CIM: "Common Information Model" http://www.dmtf.org/spec/cims.html.
[72] IEEE 754: "IEEE Standard for Binary Floating-Point Arithmetic".
[73] ETSI ES 203 915-4-5: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 5: Conference Call Control SCF (Parlay 5)".
[74] ETSI ES 203 915-4-1: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 1: Call Control Common Definitions (Parlay 5)".
[75] ETSI ES 203 915-4-2: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 2: Generic Call Control SCF (Parlay 5)".
[76] ETSI ES 203 915-4-3: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 3: Multi-Party Call Control SCF (Parlay 5)".
[77] IEEE Std 1003.2 (POSIX 1003.2): "IEEE Standard for Information Technology-Portable
Operating System Interface (POSIX®)-Part 2: Shell and Utilities".
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
gateway: synonym for Service Capability Server
ETSI
11 Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)
NOTE: From the viewpoint of applications, a Service Capability Server can be seen as a gateway to the core
network.
HE-VASP: Home Environment Value Added Service Provider
NOTE: This is a VASP that has an agreement with the Home Environment to provide services.
Home Environment (HE): 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 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 (SCS): Functional Entity providing OSA interfaces towards an application
service: alternative for Service Capability Feature (in ES 203 915-1)
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 (VASP): provides services other than basic telecommunications service for which
additional charges may be incurred
Virtual Home Environment (VHE): 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:
AoC Advice of Charge
API Application Programming Interface
ASP Application Service Provider
CAMEL Customized Application for Mobile network Enhanced Logic
CGI Cell Global Identification
CI Cell Identification
CIC Carrier Identification Code
CIM DMTF Common Information Model
CMS Cryptographic Message Syntax
CNF Conjunctive Normal Form
CSE Camel Service Environment
DMTF Distributed Management Task Force
DNF Disjunctive Normal Form
FSM Finite State Model
GCC Generic Call Control
GCCS Generic Call Control Service
GMS Generic Messaging Service
GPS Global Positioning System
ETSI
12 Final draft ETSI ES 203 915-1 V1.3.1 (2008-02)
GUIS Generic User Interaction Service
HE Home Environment
HE-VASP Home Environment Value Added Service Provider
HPLMN Home Public Land Mobile Network
IDL Interface Description Language
IMEI International Mobile station Equipment Identity
JSR Java™ Specification Request
LAC Location Area Code
LAI Location Area Identification
LCS LoCation Services
MAP Mobile Application Part
MCC Mobile Country Code
MExE Mobile station (application) Execution Environment
MMCC Multi-Media Call Control
MNC Mobile Network Code
MPCC Multi-Party Call Control
MS Mobile Station
MSC Mobile Switching Centre
NA-ESRD North American Emergency Services Routing Digits
NA-ESRK North American Emergency Services Routing Key
OSA Open Service Access
PAM Presence and Availability Management
PCIM Policy Core Information Model, as defined in RFCs 3060 and 3460
PLMN Public Land Mobile Network
PM Policy Management
PPA Pre-Paid Application
PSE Personal Service Environment
QoS Quality of Service
RMI Java™ Remote Method Invocation
SAG Subscription Assignment Group
SAP Service Access Point
SC Service Capabilities
SCF Service Capability Feature
SCS Service Capability Server
SIM Subscriber Identity Module
SMS Short Message Service
SMTP Simple Mail Transfer Protocol
SOAP Simple Object Access Protocol
SPA Service Provider API
STD State Transition Diagrams
UI User Interaction
ULE User Location Emergency
UML Unified Modelling Language
USSD Unstructured Supplementary Service Data
VASP Value Added Service Provider
VHE Virtual Home Environment
VLR Visited Location Register
VPLMN Visited Public Land Mobile Network
WAP Wireless Application Protocol
WSDL Web Services Defi
...

ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Part 1: Overview
(Parlay 5)
�
2 ETSI ES 203 915-1 V1.3.1 (2008-04)

Reference
RES/TISPAN-01055-01-OSA
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, 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 203 915-1 V1.3.1 (2008-04)
Contents
Intellectual Property Rights.6
Foreword.6
1 Scope.7
2 References.7
2.1 Normative references.7
2.2 Informative references.10
3 Definitions and abbreviations.11
3.1 Definitions.11
3.2 Abbreviations.11
4 Open Service Access APIs.13
5 Document structure.14
6 Methodology.15
6.1 Tools and Languages.15
6.2 Packaging Structure.15
6.3 Colours.18
6.4 Naming scheme.18
6.5 State Transition Diagram text and text symbols.18
6.6 Exception handling and passing results.19
6.7 References.19
6.8 Strings and Collections.19
6.9 Prefixes.19
7 Introduction to Parlay/OSA APIs.19
7.1 Interface Types.19
7.2 Service Factory.20
7.3 Use of Sessions.20
7.4 Interfaces and Sessions.20
7.5 Callback Interfaces.20
7.6 Setting Callbacks.20
7.7 Synchronous versus Asynchronous Methods .20
7.8 Out Parameters.21
7.9 Exception Hierarchy.21
7.10 Common Exceptions.21
7.11 Use of NULL.22
7.12 Notification Handling.22
8 Relationship between ETSI, Parlay and 3GPP OSA releases .23
9 Backwards Compatibility Considerations .24
9.1 Guidelines to enable backwards compatibility in implementations .24
9.2 Rule summary.24
9.2.1 Server side permitted changes .24
9.2.2 Client side permitted changes .24
9.2.3 Data type permitted changes.25
9.3 Implementation Guidelines for Server Programmers .25
9.4 Implementation Guidelines for Client Programmers.25
9.5 Tracking the changes in the specifications .25
9.5.1 New Tag.25
9.5.2 Deprecated Tag.25
9.6 Technology realization rules .26
9.6.1 Corba IDL Rules.26
9.6.2 Java rules.26
9.7 Rules for removal of deprecated items from the specifications.26
ETSI
4 ETSI ES 203 915-1 V1.3.1 (2008-04)
Annex A (normative): OMG IDL .27
A.1 Tools and languages .27
A.2 Namespace.27
A.3 Object References.27
A.4 Mapping of Datatypes .27
A.4.1 Basic Datatypes.27
A.4.2 Constants.27
A.4.3 Collections.28
A.4.4 Sequences.28
A.4.5 Enumerations.28
A.4.6 Choices.28
A.5 Use of NULL.29
A.6 Exceptions.29
A.7 Naming space across CORBA modules.29
Annex B (informative): W3C WSDL.30
B.1 Tools and Languages.30
B.2 Proposed Namespaces for the OSA WSDL .30
B.3 Object References.31
B.4 Mapping UML Data Types to XML Schema.31
B.4.1 Data Types.31
B.4.1.1 <>.32
B.4.1.2 <>.32
B.4.1.3 <>.32
B.4.1.4 <>.33
B.4.1.5 <>.33
B.4.1.6 <>.33
B.5 Mapping of UML Interfaces to WSDL .34
B.5.1 Mapping of UML Operations to WSDL message element.34
B.5.2 Mapping of Exception to WSDL message element.34
B.5.3 Mapping of Interface Class to WSDL portType and binding elements.34
B.5.4 Mapping of UML Interfaces to WSDL service element.35
Annex C (informative): Java™ Realisation API .36
C.1 Java™ Realisation Overview .36
C.1.1 J2SE™ API.36
C.1.2 J2EE™ API.36
C 1.3 Javadoc™ .36
C.2 Tools and languages .37
C.3 Generic Mappings (Elements common to J2SE™ and J2EE™).37
C.3.1 Namespace.37
C.3.2 Package Naming Conventions.37
C.3.3 Object References.37
C.3.4 Element Naming.38
C.3.5 Element Naming Collisions.38
C.3.6 Data Type Definitions .38
C.3.6.1 Basic Data Types .38
C.3.6.2 Constants.38
C.3.6.3 NumberedSetsOfDataElements (Collections).39
C.3.6.4 SequenceOfDataElements (Structures).39
C.3.6.5 NameValuePair (Enumerations).40
C.3.6.6 TaggedChoiceOfDataElements (Unions).41
ETSI
5 ETSI ES 203 915-1 V1.3.1 (2008-04)
C.3.6.7 Exceptions.43
C.3.6.7.1 PlatformException.43
C.3.6.7.2 P_XXX_XXX Exceptions.44
C.3.6.7.3 TpCommonExceptions.44
C.3.6.7.4 TpCommonException's associated exceptions.45
C.3.6.7.5 Additional abstract exceptions .45
C.3.6.7.6 InvalidUnionAccessorException.46
C.3.6.7.7 InvalidEnumValueException.46
C.3.6.8 Deprecation.46
C.4 J2SE™ Specific Conventions.47
C.4.1 Removal of "Tp" Prefix.47
C.4.2 Constants.47
C.4.3 Removal of "Ip" prefix .47
C.4.4 Mapping of IpInterface.48
C.4.5 Mapping of IpService.48
C.4.6 Mapping of UML Operations.48
C.4.7 Mapping of TpSessionID .49
C.4.8 Mapping of TpAssignmentID to the creation of an Activity object .49
C.4.9 Callback Rule.53
C.4.10 Factory Rule.53
C.4.11 J2SE™ Specific Exceptions .55
C.4.11.1 PeerUnavailableException.55
C.4.11.2 IllegalStateException.55
C.4.12 User Interaction Specific Rules .56
C.4.12.1 Interfaces representing UML IpUI and IpUICall Rule .56
C.4.12.2 Naming Collisions of IpUI and IpUICall Rule .56
C.4.12.3 Naming Collisions of IpUICall and IpUIAdminManager Rule .56
C.5 J2EE™ Specific Conventions .56
C.5.1 Void.56
C.5.2 Remote Interface Definitions .56
C.5.2.1 IpInterface.56
C.5.2.2 Methods for Remote Interfaces.56
C.5.3 Local Interface Definitions.57
C.5.3.1 Methods for Local Interfaces.57
C.5.4 Multi Party Call Control Specific Rules.57
C.5.4.1 IpCallLeg and IpAppCallLeg method name conflicts .57
Annex D (informative): Description of Overview for 3GPP2 cdma2000 networks.58
D.1 General Exceptions.58
D.2 Specific Exceptions.58
D.2.1 Clause 1: Scope .58
D.2.2 Clause 2: References .58
D.2.3 Clause 3: Definitions and abbreviations.58
D.2.4 Clause 4: Open Service Access APIs .58
D.2.5 Clause 5: Structure of the OSA API (29.198) and Mapping (29.998) documents .58
D.2.6 Clause 6: Methodology .58
D.2.7 Clause 7: Introduction to OSA APIs .58
D.2.8 Annex A (normative): OMG IDL.59
D.2.9 Annex B (informative): W3C WSDL.59
D.2.10 Annex C (informative): Java™ API.59
Annex E (informative): Bibliography.60
History .61

ETSI
6 ETSI ES 203 915-1 V1.3.1 (2008-04)
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 1 of a multi-part deliverable covering Open Service Access (OSA); Application
Programming Interface (API), as identified below. The API specification (ES 203 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".
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 5.2 set of specifications.
The present document is equivalent to 3GPP TS 29.198-1 V6.5.0 (Release 6).
ETSI
7 ETSI ES 203 915-1 V1.3.1 (2008-04)
1 Scope
The present document is part 1 of the Stage 3 specification for an Application Programming Interface 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
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.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); 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". (http://www.w3.org/TR/NOTE-CCPP/).
ETSI
8 ETSI ES 203 915-1 V1.3.1 (2008-04)
[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 2.0: "User Agent Profiling Specification"
(WAP-248). (http://www.wapforum.org/what/technical.htm).
[10] 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)".
[11] 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)".
[12] 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)".
[13] ITU-T Recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes".
[14] ITU-T Recommendation Q.931: "ISDN user-network interface layer 3 specification for basic call
control".
[15] ISO 8601: "Data elements and interchange formats - Information interchange - Representation of
dates and times".
[16] ISO 4217: "Codes for the representation of currencies and funds".
[17] ISO 639: "Code for the representation of names of languages".
[18] IETF RFC 822: "Standard for the format of ARPA Internet text messages".
[19] IETF RFC 1738: "Uniform Resource Locators (URL)".
[20] 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)".
[21] ETSI TS 129 198 (all parts): "Universal Mobile Telecommunications System (UMTS); Open
Service Access (OSA) Application Programming Interface (API); (3GPP TS 29.198 Release 6)".
[22] ETSI TS 123 107: "Universal Mobile Telecommunications System (UMTS); Quality of Service
(QoS) concept and architecture" (3GPP TS 23.107)".
[23] ETSI TS 123 271: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Functional stage 2 description of Location Services (LCS)
(3GPP TS 23.271)".
[24] ANSI T1.113: "Signalling System No. 7 (SS7) - Integrated Services Digital Network (ISDN) User
Part".
[25] IETF RFC 3261: "SIP: Session Initiation Protocol".
[26] ITU-T Recommendation Q.932: "Digital subscriber signalling system No. 1 - Generic procedures
for the control of ISDN supplementary services".
[27] ITU-T Recommendation H.221: "Frame structure for a 64 to 1920 kbit/s channel in audiovisual
teleservices".
[28] ITU-T Recommendation H.323: "Packet-based multimedia communications systems".
ETSI
9 ETSI ES 203 915-1 V1.3.1 (2008-04)
[29] IETF RFC 1994: "PPP Challenge Handshake Authentication Protocol (CHAP)".
[30] IETF RFC 2630: "Cryptographic Message Syntax".
[31] IETF RFC 2313: "PKCS #1: RSA Encryption Version 1.5".
[32] IETF RFC 2459: "Internet X.509 Public Key Infrastructure Certificate and CRL Profile".
[33] IETF RFC 2437: "PKCS #1: RSA Cryptography Specifications Version 2.0".
[34] IETF RFC 1321: "The MD5 Message-Digest Algorithm".
[35] IETF RFC 2404: "The Use of HMAC-SHA-1-96 within ESP and AH".
[36] IETF RFC 2403: "The Use of HMAC-MD5-96 within ESP and AH".
[37] ITU-T Recommendation G.722: "7 kHz audio-coding within 64 kbit/s".
[38] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies".
[39] ITU-T Recommendation G.723.1: "Speech coders: Dual rate speech coder for multimedia
communications transmitting at 5.3 and 6.3 kbit/s".
[40] ITU-T Recommendation G.728: "Coding of speech at 16 kbit/s using low-delay code excited
linear prediction".
[41] ITU-T Recommendation G.729: "Coding of speech at 8 kbit/s using conjugate-structure
algebraic-code-excited linear-prediction (CS-ACELP)".
[42] ITU-T Recommendation H.261: "Video codec for audiovisual services at p x 64 kbit/s".
[43] ITU-T Recommendation H.263: "Video coding for low bit rate communication".
[44] ITU-T Recommendation H.262: "Information technology - Generic coding of moving pictures and
associated audio information: Video".
[45] World Geodetic System 1984 (WGS 84). (http://www.wgs84.com/files/wgsman24.pdf).
NOTE: The above link is temporarily not accessible. The following mirror site may contain the same information,
but has not been verified by ETSI.
http://octopus.hit.bme.hu/tkatona/mirrors/WGS84/www.wgs84.com/files/wgsman24.pdf
[46] ITU-T Recommendation X.400: "Message handling services: Message handling system and
service overview".
[47] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[48] IETF RFC 2445: "Internet Calendaring and Scheduling Core Object Specification (iCalendar)".
[49] IETF RFC 2778: "A Model for Presence and Instant Messaging".
[50] ITU-T Recommendation Q.1238-2: "Interface Recommendation for Intelligent Network
Capability Set 3: SCF - SSF interface".
[51] IETF RFC 3460: "Policy Core Information Model (PCIM) Extensions".
[52] 3GPP2 P.S0001-B: "Wireless IP Network Standard", Version 1.0, October 2002.
[53] 3GPP2 S.R0037-0: "IP Network Architecture Model for cdma2000 Spread Spectrum Systems",
Version 2.0, May 2002.
[54] 3GPP2 X.S0013: "All-IP Core Network Multimedia Domain", December 2003.
[55] ETSI ES 201 915: "Open Service Access (OSA); Application Programming Interface (API)
(Parlay 3)".
[56] ETSI ES 202 915: "Open Service Access (OSA); Application Programming Interface (API)
(Parlay 4)".
ETSI
10 ETSI ES 203 915-1 V1.3.1 (2008-04)
[57] ETSI ES 203 915-2: "Open Service Access (OSA); Application Programming Interface (API);
Part 2: Common Data Definitions (Parlay 5)".
[58] IETF RFC 1737: "Functional Requirements for Uniform Resource Names".
[59] ITU-T Recommendation T.120: "Data protocols for multimedia conferencing".
[60] ISO/IEC 11172-2: "Information technology - Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s - Part 2: Video".
[61] ISO/IEC 11172-3: "Information technology - Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s - Part 3: Audio".
[62] ISO/IEC 13818-3: "Information technology - Generic coding of moving pictures and associated
audio information - Part 3: Audio".
[63] ISO/IEC 14496-2: "Information technology - Coding of audio-visual objects - Part 2: Visual".
[64] draft-ietf-simple-message-sessions-15.txt: "The Message Session Relay Protocol".
[65] IETF RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet
Message Bodies".
[66] IETF RFC 2183: "Communicating Presentation Information in Internet Messages: The
Content-Disposition Header Field".
[67] CORBA 2.4.2: "The Common Object Request Broker: Architecture and Specification", February
2001. http://www.omg.org/cgi-bin/doc?formal/01-02-33.
[68] IETF RFC 2822: "Internet Message Format".
[69] IETF RFC 3060: "Policy Core Information Model - Version 1 Specification".
[70] IETF RFC 2591: "Definitions of Managed Objects for Scheduling Management Operations".
[71] DMTF CIM: "Common Information Model" http://www.dmtf.org/spec/cims.html.
[72] IEEE 754: "IEEE Standard for Binary Floating-Point Arithmetic".
[73] ETSI ES 203 915-4-5: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 5: Conference Call Control SCF (Parlay 5)".
[74] ETSI ES 203 915-4-1: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 1: Call Control Common Definitions (Parlay 5)".
[75] ETSI ES 203 915-4-2: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 2: Generic Call Control SCF (Parlay 5)".
[76] ETSI ES 203 915-4-3: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 3: Multi-Party Call Control SCF (Parlay 5)".
[77] IEEE Std 1003.2 (POSIX 1003.2): "IEEE Standard for Information Technology-Portable
Operating System Interface (POSIX®)-Part 2: Shell and Utilities".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
ETSI
11 ETSI ES 203 915-1 V1.3.1 (2008-04)
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
gateway: synonym for Service Capability Server
NOTE: From the viewpoint of applications, a Service Capability Server can be seen as a gateway to the core
network.
HE-VASP: Home Environment Value Added Service Provider
NOTE: This is a VASP that has an agreement with the Home Environment to provide services.
Home Environment (HE): 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 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 (SCS): Functional Entity providing OSA interfaces towards an application
service: alternative for Service Capability Feature (in ES 203 915-1)
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 (VASP): provides services other than basic telecommunications service for which
additional charges may be incurred
Virtual Home Environment (VHE): 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:
AoC Advice of Charge
API Application Programming Interface
ASP Application Service Provider
CAMEL Customized Application for Mobile network Enhanced Logic
CGI Cell Global Identification
CI Cell Identification
ETSI
12 ETSI ES 203 915-1 V1.3.1 (2008-04)
CIC Carrier Identification Code
CIM DMTF Common Information Model
CMS Cryptographic Message Syntax
CNF Conjunctive Normal Form
CSE Camel Service Environment
DMTF Distributed Management Task Force
DNF Disjunctive Normal Form
FSM Finite State Model
GCC Generic Call Control
GCCS Generic Call Control Service
GMS Generic Messaging Service
GPS Global Positioning System
GUIS Generic User Interaction Service
HE Home Environment
HE-VASP Home Environment Value Added Service Provider
HPLMN Home Public Land Mobile Network
IDL Interface Description Language
IMEI International Mobile station Equipment Identity
JSR Java™ Specification Request
LAC Location Area Code
LAI Location Area Identification
LCS LoCation Services
MAP Mobile Application Part
MCC Mobile Country Code
MExE Mobile station (application) Execution Environment
MMCC Multi-Media Call Control
MNC Mobile Network Code
MPCC Multi-Party Call Control
MS Mobile Station
MSC Mobile Switching Centre
NA-ESRD North American Emergency Services Routing Digits
NA-ESRK North American Emergency Services Routing Key
OSA Open Service Access
PAM Presence and Availability Management
PCIM Policy Core Information Model, as defined in RFCs 3060 and 3460
PLMN Public Land Mobile Network
PM Policy Management
PPA Pre-Paid Application
PSE Personal Service Environment
QoS Quality of Service
RMI Java™ Remote Method Invocation
SAG Subscription Assignment Group
SAP Service Access Point
SC Service Capabilities
SCF Service Capability Feature
SCS Service Capability Server
SIM Subscriber Identity Module
SMS Short Message Service
SMTP Simple Mail Transfer Protocol
SOAP
...

SLOVENSKI STANDARD
01-september-2008
Odprti dostop do storitve (OSA) - Aplikacijski programski vmesnik (API) - 1. del:
Pregled (Parlay 5)
Open Service Access (OSA) - Application Programming Interface (API) - Part 1:
Overview (Parlay 5)
Ta slovenski standard je istoveten z: ES 203 915-1 Version 1.3.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 5)
�
2 ETSI ES 203 915-1 V1.3.1 (2008-04)

Reference
RES/TISPAN-01055-01-OSA
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, 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 203 915-1 V1.3.1 (2008-04)
Contents
Intellectual Property Rights.6
Foreword.6
1 Scope.7
2 References.7
2.1 Normative references.7
2.2 Informative references.10
3 Definitions and abbreviations.11
3.1 Definitions.11
3.2 Abbreviations.11
4 Open Service Access APIs.13
5 Document structure.14
6 Methodology.15
6.1 Tools and Languages.15
6.2 Packaging Structure.15
6.3 Colours.18
6.4 Naming scheme.18
6.5 State Transition Diagram text and text symbols.18
6.6 Exception handling and passing results.19
6.7 References.19
6.8 Strings and Collections.19
6.9 Prefixes.19
7 Introduction to Parlay/OSA APIs.19
7.1 Interface Types.19
7.2 Service Factory.20
7.3 Use of Sessions.20
7.4 Interfaces and Sessions.20
7.5 Callback Interfaces.20
7.6 Setting Callbacks.20
7.7 Synchronous versus Asynchronous Methods .20
7.8 Out Parameters.21
7.9 Exception Hierarchy.21
7.10 Common Exceptions.21
7.11 Use of NULL.22
7.12 Notification Handling.22
8 Relationship between ETSI, Parlay and 3GPP OSA releases .23
9 Backwards Compatibility Considerations .24
9.1 Guidelines to enable backwards compatibility in implementations .24
9.2 Rule summary.24
9.2.1 Server side permitted changes .24
9.2.2 Client side permitted changes .24
9.2.3 Data type permitted changes.25
9.3 Implementation Guidelines for Server Programmers .25
9.4 Implementation Guidelines for Client Programmers.25
9.5 Tracking the changes in the specifications .25
9.5.1 New Tag.25
9.5.2 Deprecated Tag.25
9.6 Technology realization rules .26
9.6.1 Corba IDL Rules.26
9.6.2 Java rules.26
9.7 Rules for removal of deprecated items from the specifications.26
ETSI
4 ETSI ES 203 915-1 V1.3.1 (2008-04)
Annex A (normative): OMG IDL .27
A.1 Tools and languages .27
A.2 Namespace.27
A.3 Object References.27
A.4 Mapping of Datatypes .27
A.4.1 Basic Datatypes.27
A.4.2 Constants.27
A.4.3 Collections.28
A.4.4 Sequences.28
A.4.5 Enumerations.28
A.4.6 Choices.28
A.5 Use of NULL.29
A.6 Exceptions.29
A.7 Naming space across CORBA modules.29
Annex B (informative): W3C WSDL.30
B.1 Tools and Languages.30
B.2 Proposed Namespaces for the OSA WSDL .30
B.3 Object References.31
B.4 Mapping UML Data Types to XML Schema.31
B.4.1 Data Types.31
B.4.1.1 <>.32
B.4.1.2 <>.32
B.4.1.3 <>.32
B.4.1.4 <>.33
B.4.1.5 <>.33
B.4.1.6 <>.33
B.5 Mapping of UML Interfaces to WSDL .34
B.5.1 Mapping of UML Operations to WSDL message element.34
B.5.2 Mapping of Exception to WSDL message element.34
B.5.3 Mapping of Interface Class to WSDL portType and binding elements.34
B.5.4 Mapping of UML Interfaces to WSDL service element.35
Annex C (informative): Java™ Realisation API .36
C.1 Java™ Realisation Overview .36
C.1.1 J2SE™ API.36
C.1.2 J2EE™ API.36
C 1.3 Javadoc™ .36
C.2 Tools and languages .37
C.3 Generic Mappings (Elements common to J2SE™ and J2EE™).37
C.3.1 Namespace.37
C.3.2 Package Naming Conventions.37
C.3.3 Object References.37
C.3.4 Element Naming.38
C.3.5 Element Naming Collisions.38
C.3.6 Data Type Definitions .38
C.3.6.1 Basic Data Types .38
C.3.6.2 Constants.38
C.3.6.3 NumberedSetsOfDataElements (Collections).39
C.3.6.4 SequenceOfDataElements (Structures).39
C.3.6.5 NameValuePair (Enumerations).40
C.3.6.6 TaggedChoiceOfDataElements (Unions).41
ETSI
5 ETSI ES 203 915-1 V1.3.1 (2008-04)
C.3.6.7 Exceptions.43
C.3.6.7.1 PlatformException.43
C.3.6.7.2 P_XXX_XXX Exceptions.44
C.3.6.7.3 TpCommonExceptions.44
C.3.6.7.4 TpCommonException's associated exceptions.45
C.3.6.7.5 Additional abstract exceptions .45
C.3.6.7.6 InvalidUnionAccessorException.46
C.3.6.7.7 InvalidEnumValueException.46
C.3.6.8 Deprecation.46
C.4 J2SE™ Specific Conventions.47
C.4.1 Removal of "Tp" Prefix.47
C.4.2 Constants.47
C.4.3 Removal of "Ip" prefix .47
C.4.4 Mapping of IpInterface.48
C.4.5 Mapping of IpService.48
C.4.6 Mapping of UML Operations.48
C.4.7 Mapping of TpSessionID .49
C.4.8 Mapping of TpAssignmentID to the creation of an Activity object .49
C.4.9 Callback Rule.53
C.4.10 Factory Rule.53
C.4.11 J2SE™ Specific Exceptions .55
C.4.11.1 PeerUnavailableException.55
C.4.11.2 IllegalStateException.55
C.4.12 User Interaction Specific Rules .56
C.4.12.1 Interfaces representing UML IpUI and IpUICall Rule .56
C.4.12.2 Naming Collisions of IpUI and IpUICall Rule .56
C.4.12.3 Naming Collisions of IpUICall and IpUIAdminManager Rule .56
C.5 J2EE™ Specific Conventions .56
C.5.1 Void.56
C.5.2 Remote Interface Definitions .56
C.5.2.1 IpInterface.56
C.5.2.2 Methods for Remote Interfaces.56
C.5.3 Local Interface Definitions.57
C.5.3.1 Methods for Local Interfaces.57
C.5.4 Multi Party Call Control Specific Rules.57
C.5.4.1 IpCallLeg and IpAppCallLeg method name conflicts .57
Annex D (informative): Description of Overview for 3GPP2 cdma2000 networks.58
D.1 General Exceptions.58
D.2 Specific Exceptions.58
D.2.1 Clause 1: Scope .58
D.2.2 Clause 2: References .58
D.2.3 Clause 3: Definitions and abbreviations.58
D.2.4 Clause 4: Open Service Access APIs .58
D.2.5 Clause 5: Structure of the OSA API (29.198) and Mapping (29.998) documents .58
D.2.6 Clause 6: Methodology .58
D.2.7 Clause 7: Introduction to OSA APIs .58
D.2.8 Annex A (normative): OMG IDL.59
D.2.9 Annex B (informative): W3C WSDL.59
D.2.10 Annex C (informative): Java™ API.59
Annex E (informative): Bibliography.60
History .61

ETSI
6 ETSI ES 203 915-1 V1.3.1 (2008-04)
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 1 of a multi-part deliverable covering Open Service Access (OSA); Application
Programming Interface (API), as identified below. The API specification (ES 203 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".
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 5.2 set of specifications.
The present document is equivalent to 3GPP TS 29.198-1 V6.5.0 (Release 6).
ETSI
7 ETSI ES 203 915-1 V1.3.1 (2008-04)
1 Scope
The present document is part 1 of the Stage 3 specification for an Application Programming Interface 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
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.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TR 121 905: "Digital cellular telecommunications system (Phase 2+); 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". (http://www.w3.org/TR/NOTE-CCPP/).
ETSI
8 ETSI ES 203 915-1 V1.3.1 (2008-04)
[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 2.0: "User Agent Profiling Specification"
(WAP-248). (http://www.wapforum.org/what/technical.htm).
[10] 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)".
[11] 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)".
[12] 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)".
[13] ITU-T Recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes".
[14] ITU-T Recommendation Q.931: "ISDN user-network interface layer 3 specification for basic call
control".
[15] ISO 8601: "Data elements and interchange formats - Information interchange - Representation of
dates and times".
[16] ISO 4217: "Codes for the representation of currencies and funds".
[17] ISO 639: "Code for the representation of names of languages".
[18] IETF RFC 822: "Standard for the format of ARPA Internet text messages".
[19] IETF RFC 1738: "Uniform Resource Locators (URL)".
[20] 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)".
[21] ETSI TS 129 198 (all parts): "Universal Mobile Telecommunications System (UMTS); Open
Service Access (OSA) Application Programming Interface (API); (3GPP TS 29.198 Release 6)".
[22] ETSI TS 123 107: "Universal Mobile Telecommunications System (UMTS); Quality of Service
(QoS) concept and architecture" (3GPP TS 23.107)".
[23] ETSI TS 123 271: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Functional stage 2 description of Location Services (LCS)
(3GPP TS 23.271)".
[24] ANSI T1.113: "Signalling System No. 7 (SS7) - Integrated Services Digital Network (ISDN) User
Part".
[25] IETF RFC 3261: "SIP: Session Initiation Protocol".
[26] ITU-T Recommendation Q.932: "Digital subscriber signalling system No. 1 - Generic procedures
for the control of ISDN supplementary services".
[27] ITU-T Recommendation H.221: "Frame structure for a 64 to 1920 kbit/s channel in audiovisual
teleservices".
[28] ITU-T Recommendation H.323: "Packet-based multimedia communications systems".
ETSI
9 ETSI ES 203 915-1 V1.3.1 (2008-04)
[29] IETF RFC 1994: "PPP Challenge Handshake Authentication Protocol (CHAP)".
[30] IETF RFC 2630: "Cryptographic Message Syntax".
[31] IETF RFC 2313: "PKCS #1: RSA Encryption Version 1.5".
[32] IETF RFC 2459: "Internet X.509 Public Key Infrastructure Certificate and CRL Profile".
[33] IETF RFC 2437: "PKCS #1: RSA Cryptography Specifications Version 2.0".
[34] IETF RFC 1321: "The MD5 Message-Digest Algorithm".
[35] IETF RFC 2404: "The Use of HMAC-SHA-1-96 within ESP and AH".
[36] IETF RFC 2403: "The Use of HMAC-MD5-96 within ESP and AH".
[37] ITU-T Recommendation G.722: "7 kHz audio-coding within 64 kbit/s".
[38] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies".
[39] ITU-T Recommendation G.723.1: "Speech coders: Dual rate speech coder for multimedia
communications transmitting at 5.3 and 6.3 kbit/s".
[40] ITU-T Recommendation G.728: "Coding of speech at 16 kbit/s using low-delay code excited
linear prediction".
[41] ITU-T Recommendation G.729: "Coding of speech at 8 kbit/s using conjugate-structure
algebraic-code-excited linear-prediction (CS-ACELP)".
[42] ITU-T Recommendation H.261: "Video codec for audiovisual services at p x 64 kbit/s".
[43] ITU-T Recommendation H.263: "Video coding for low bit rate communication".
[44] ITU-T Recommendation H.262: "Information technology - Generic coding of moving pictures and
associated audio information: Video".
[45] World Geodetic System 1984 (WGS 84). (http://www.wgs84.com/files/wgsman24.pdf).
NOTE: The above link is temporarily not accessible. The following mirror site may contain the same information,
but has not been verified by ETSI.
http://octopus.hit.bme.hu/tkatona/mirrors/WGS84/www.wgs84.com/files/wgsman24.pdf
[46] ITU-T Recommendation X.400: "Message handling services: Message handling system and
service overview".
[47] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[48] IETF RFC 2445: "Internet Calendaring and Scheduling Core Object Specification (iCalendar)".
[49] IETF RFC 2778: "A Model for Presence and Instant Messaging".
[50] ITU-T Recommendation Q.1238-2: "Interface Recommendation for Intelligent Network
Capability Set 3: SCF - SSF interface".
[51] IETF RFC 3460: "Policy Core Information Model (PCIM) Extensions".
[52] 3GPP2 P.S0001-B: "Wireless IP Network Standard", Version 1.0, October 2002.
[53] 3GPP2 S.R0037-0: "IP Network Architecture Model for cdma2000 Spread Spectrum Systems",
Version 2.0, May 2002.
[54] 3GPP2 X.S0013: "All-IP Core Network Multimedia Domain", December 2003.
[55] ETSI ES 201 915: "Open Service Access (OSA); Application Programming Interface (API)
(Parlay 3)".
[56] ETSI ES 202 915: "Open Service Access (OSA); Application Programming Interface (API)
(Parlay 4)".
ETSI
10 ETSI ES 203 915-1 V1.3.1 (2008-04)
[57] ETSI ES 203 915-2: "Open Service Access (OSA); Application Programming Interface (API);
Part 2: Common Data Definitions (Parlay 5)".
[58] IETF RFC 1737: "Functional Requirements for Uniform Resource Names".
[59] ITU-T Recommendation T.120: "Data protocols for multimedia conferencing".
[60] ISO/IEC 11172-2: "Information technology - Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s - Part 2: Video".
[61] ISO/IEC 11172-3: "Information technology - Coding of moving pictures and associated audio for
digital storage media at up to about 1,5 Mbit/s - Part 3: Audio".
[62] ISO/IEC 13818-3: "Information technology - Generic coding of moving pictures and associated
audio information - Part 3: Audio".
[63] ISO/IEC 14496-2: "Information technology - Coding of audio-visual objects - Part 2: Visual".
[64] draft-ietf-simple-message-sessions-15.txt: "The Message Session Relay Protocol".
[65] IETF RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet
Message Bodies".
[66] IETF RFC 2183: "Communicating Presentation Information in Internet Messages: The
Content-Disposition Header Field".
[67] CORBA 2.4.2: "The Common Object Request Broker: Architecture and Specification", February
2001. http://www.omg.org/cgi-bin/doc?formal/01-02-33.
[68] IETF RFC 2822: "Internet Message Format".
[69] IETF RFC 3060: "Policy Core Information Model - Version 1 Specification".
[70] IETF RFC 2591: "Definitions of Managed Objects for Scheduling Management Operations".
[71] DMTF CIM: "Common Information Model" http://www.dmtf.org/spec/cims.html.
[72] IEEE 754: "IEEE Standard for Binary Floating-Point Arithmetic".
[73] ETSI ES 203 915-4-5: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 5: Conference Call Control SCF (Parlay 5)".
[74] ETSI ES 203 915-4-1: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 1: Call Control Common Definitions (Parlay 5)".
[75] ETSI ES 203 915-4-2: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 2: Generic Call Control SCF (Parlay 5)".
[76] ETSI ES 203 915-4-3: "Open Service Access (OSA); Application Programming Interface (API);
Part 4: Call Control; Sub-part 3: Multi-Party Call Control SCF (Parlay 5)".
[77] IEEE Std 1003.2 (POSIX 1003.2): "IEEE Standard for Information Technology-Portable
Operating System Interface (POSIX®)-Part 2: Shell and Utilities".
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
ETSI
11 ETSI ES 203 915-1 V1.3.1 (2008-04)
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
gateway: synonym for Service Capability Server
NOTE: From the viewpoint of applications, a Service Capability Server can be seen as a gateway to the core
network.
HE-VASP: Home Environment Value Added Service Provider
NOTE: This is a VASP that has an agreement with the Home Environment to provide services.
Home Environment (HE): 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 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 (SCS): Functional Entity providing OSA interfaces towards an application
service: alternative for Service Capability Feature (in ES 203 915-1)
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 (VASP): provides services other than basic telecommunications service for which
additional charges may be incurred
Virtual Home Environment (VHE): 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:
AoC Advice of Charge
API Application Programming Interface
ASP Application Service Provider
CAMEL Customized Application for Mobile network Enhanced Logic
CGI Cell Global Identification
CI Cell Identification
ETSI
12 ETSI ES 203 915-1 V1.3.1 (2008-04)
CIC Carrier Identification Code
CIM DMTF Common Information Model
CMS Cryptographic Message Syntax
CNF Conjunctive Normal Form
CSE Camel Service Environment
DMTF Distributed Management Task Force
DNF Disjunctive Normal Form
FSM Finite State Model
GCC Generic Call Control
GCCS Generic Call Control Service
GMS Generic Messaging Service
GPS Global Positioning System
GUIS Generic User Interaction Service
HE Home Environment
HE-VASP Home Environment Value Added Service Provider
HPLMN Home Public Land Mobile Network
IDL Interface
...