Content for TS 22.127 Word version: 9.0.0
1 Scope
2 References
2.1 Normative references
2.2 Informative references
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 General Description of OSA
...
...
1 Scope p. 6
This document specifies the stage 1 requirements for realisation of an Open Service Access (OSA).
OSA enables applications to make use of network functionality through an open standardised interface (the OSA API). OSA provides the glue between applications and network functionality. In this way applications implementing the services become independent from the underlying network technology.
Applications which make use of network functionality offered through the OSA interface are not standardised by 3GPP.
The network functionality offered through the OSA interface may or may not be standardised by 3GPP.
OSA is one toolkit, amongst others, that enables certain aspects of the requirements of the Virtual Home Environment (VHE) concept to be realised.
2 References p. 6
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, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
2.1 Normative references p. 6
[1] Void
[2]
TS 22.101: "Service principles".
[3]
TR 21.905: "Vocabulary for 3GPP Specifications".
[4]
TS 23.107: "QoS Concept and Architecture".
[5]
TS 22.024: "Description of Charge Advice Information (CAI)".
[6]
TS 29.198: "Open Service Architecture; Application Programming Interface".
[7]
TS 22.141: "Presence Service Stage 1".
[8]
TS 22.228: "IP Multimedia Subsystem (IMS) Stage 1".
[9]
TS 22.071: "Location Services (LCS) Stage 1".
[10]
TS 29.240: "3GPP Generic User Profile (GUP); Stage 3; Network"
2.2 Informative references p. 6
[10a]
World Wide Web Consortium Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation (www.w3.org)
3 Definitions and abbreviations p. 7
3.1 Definitions p. 7
For the purposes of the present document, the following terms and definitions apply:
Access Rules:
For the definition see [7].
Applications:
software components providing services to users by utilising service capability features.
Application Interface:
standardised Interface used by applications to access service capability features.
Availability:
a property of a user denoting his/her ability and willingness to communicate based on factors such as the identity or properties of the requester of the information and the preferences and/or policies that are associated with the user. This property may be computed through information available from various capabilities within the network including (but not necessarily) the presence service.
Call:
A logical association between several users pertaining to the CS CN domain..
Charging:
A function whereby information related to a chargeable event is formatted and transferred in order to make it possible to determine usage for which the charged party may be billed.
HE-VASP:
Home Environment Value Added Service Provider. For the definition see [3]
Home Environment:
For the definition see [3]
IM :
IP Multimedia. For definition see [8]
IM Session:
For definition see [8]
Local Service:
For the definition see [3]
Personal Service Environment:
For the definition see [3]
Policy:
is a formalism that may be used to express business, engineering or management criteria. A policy is represented by a set of rules. Rules are expressed as condition(s)-actions(s) pairs. When the conditions associated with a rule are satisfied the associated actions are executed.
Policy Event :
A policy event is associated with the action part of designated rule(s). The event is generated when the action part is executed.
Policy Management:
is the capability to create, modify and delete policy related information, including policy events.
Policy Enabled Service:
is a Service which has some or all of its properties expressed in terms of policy rules. E.g. Charging Service wherein charging criteria are expressed in terms of policy rules
Policy Decision Point:
A function of the network where the applicable policy is chosen.
Policy Enforcement Point:
A function of the network where the chosen policy is applied.
Policy Repository:
A function of the network where policies are stored.
Policy Enabled network:
is a network that supports at least one instance of a Policy Repository and Policy Decision Point and Policy Enforcement Point.
Presence Service:
For the definition see [7].
Presence Information:
For the definition see [7].
Presence Entity (presentity):
For the definition see [7].
Service Capabilities:
bearers defined by parameters, and/or mechanisms needed to realise services. These are within networks and under network control.
Service Capability Feature:
functionality offered by service capabilities that are accessible via the standardised application interface.
Service Provider:
an organisation which delivers services to the subscriber. This can be e.g. the operator of the subscriber's Home Environment or an authorised VASP.
Services:
a service is the user experience provided by one or more applications.
User:
For the definition see [3]
Virtual Home Environment:
For the definition see [3]
Watcher:
For the definition see [7].
Watcher Information:
For the definition see [7].
Further 3G related definitions are given in 3G TR 21.905.
3.2 Abbreviations p. 8
For the purposes of this TS the following abbreviations apply:
API
Application Programming Interface
CAMEL
Customised Application For Mobile Network Enhanced Logic
HE
Home Environment
PS
Packet Switched
PSE
Personal Service Environment
VHE
Virtual Home Environment
OSA
Open Service Access
SCF
Service Capability Feature
MExE
Mobile Execution Environment
Further 3G related abbreviations are given in 3G TS 21.905.
4 General Description of OSA p. 8
In order to be able to implement future applications/end user services that are not yet known today, a highly flexible Framework for Services is required. The Open Service Access (OSA) enables applications implementing the services to make use of network functionality. Network functionality offered to applications is defined in terms of a set of Service Capability Features (SCFs). These SCFs provide functionality of network capabilities which is accessible to applications through the standardised OSA interface upon which service developers can rely when designing new services (or enhancements/variants of already existing ones).
The aim of OSA is to provide a standardised, extensible and scalable interface that allows for inclusion of new functionality in the network with a minimum impact on the applications using the OSA interface.
