1. Parlay/OSA: an open API for service development
joint-API-grou
Chelo Abarca, Andy Bennett, Ard-Jan Moerdijk, Musa Unmehopa
joint API group

2. Outline 0- Introduction: the Parlay/OSA API: why, where, what?
1- A closer look at Parlay/OSA
- Parlay/OSA Framework and Service Capability Features
- Parlay/OSA current functionality
2- The Parlay/OSA Framework
- Framework functionality
- How does it work?
3- Example Parlay/OSA applications

3. Outline 4- Parlay/OSA standardisation
- Bodies involved in Parlay/OSA standardisation
- The Joint API Group
5- The next Parlay/OSA release
6- Summary, contacts

4. Outline 0- Introduction: the Parlay/OSA API: why, where, what?
1- A closer look at Parlay/OSA
2- The Parlay/OSA Framework
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
5- The next Parlay/OSA release
6- Summary, contacts

5. The Parlay/OSA API: Why? (1/2)
A change in business models has introduced new players in the telecom business
User
New Player
services
connectivity
Operator
Some want to address users directly
User
New Player
connectivity + services
Operator
connectivity
Some prefer to do it via the Network Operator
But they have something in common:
They compete in the services market...
and they have no network!

6. The Parlay/OSA API: Why? (2/2)
This is a win-win situation!
- It opens new sources of revenue for incumbent Network Operators
- traffic in their networks increases
- they may enrich their service offering
- It opens the telecom business to newcomers
- VNOs, MVNOs, ASPs, ...
Parlay/OSA
So we only need a technical enabler:

7. The Parlay/OSA API: Where? (1/2)
Services/application layer
Service network
OSA/Parlay API’s
exposing network service capabilities
Control layer
Service Capability Servers
Core network
Distribution via middleware
Connectivity layer
Core & Radio Networks
2G 2.5G & 3G

8. The Parlay/OSA API: Where? (2/2)
Application
OSA API
OSA Gateway
PLMN
GSM/UMTS
(CS/PS)
SGSN
MSC
PSTN / ISDN
(CS)
SSP
PLMN
UMTS (IMS)
S-CSCF
Enterprise
PBX

9. The Parlay/OSA API: What? (1/2)
Parlay/OSA (Open Service Access) is an API that enables operator and 3rd party applications to make use of network functionality through a set of open, standardised interfaces
3GPP ETSI Parlay JAIN SPA
App1
App2
AppN
Applications (independent of underlying network technology)
Parlay/OSA API
OSA Gateway
Mapping to network specific protocols
Network
Network complexity hidden from applications

10. The Parlay / OSA API: What (2/2)
Opening up of network by means of standardized APIs based on open technology. This leads to :
Shorter TTM for applications / services due to abstraction and open technology (developer community orders of magnitude larger than telco developer community)
Applications can also be developed and deployed by 3rd parties (creative, new innovative services).
Applications can be network independent (multi-access / multi-service)
Applications can be combination of
different capabilities
enterprise data with network functionality
leading to new innovative services.
Combining Telecom & Datacom
The developer community is out there

11. Outline 0- Introduction 1- A closer look at Parlay/OSA
- Parlay/OSA Framework and Service Capability Features
- Parlay/OSA current functionality
2- The Parlay/OSA Framework
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
5- The next Parlay/OSA release
6- Summary, contacts

12. Parlay/OSA Terminology: SCSs and SCFs
- The Parlay/OSA Gateway consists of several Service Capability Servers (SCS): functional entities that provide Parlay/OSA interfaces towards applications.
Interface
SCF
- Each SCS is seen by applications as one or more Service Capability Features (SCF): abstractions of the functionality offered by the network, accessible via the Parlay/OSA API. Sometimes they are also called services
SCS
- The Parlay/OSA SCFs are specified in terms of interface classes and their methods

13. Parlay/OSA = Framework + A Set Of SCFs
Application
server
Application
OSA API
interface
The OSA Gateway is viewed by the Applications as a set of interfaces, grouped in terms of functionality into discoverable Service Capability Features, of two kinds:
- One is a single, always present (one per network) SCS, called the Framework. The OSA Framework is in charge of controlling the access to network capabilities by Applications, as well the integrity of the operator’s network.
- The rest are a set of Service Capability Features, which abstract the network functionality so that Applications can use the network without needing to understand its underlying technology. These SCFs are mappable to network functionality, but the mapping is not standardized (note that the Framework functionality does not have a mapping).
As the slide shows, besides the OSA API between the OSA Gateway and the 3rd Party Applications, there is an OSA Internal API between the Framework and the rest of the OSA Service Capability Servers. This Internal API supports multi-vendorship for the OSA SCSs, as well as the possibility that the Framework functionality is a business in itself.
class
User
Call control
framework
Location
Service Capability Servers
Not standardized
OSA Internal API
WGW
HLR
CSE
Servers
WPP
E.g. Location server
Billing server
One of the Parlay/OSA SCSs is called the Parlay/OSA Framework, and is always present, one per network

14. Outline 0- Introduction 1- A closer look at Parlay/OSA
- Parlay/OSA Framework and Service Capability Features
- Parlay/OSA current functionality
2- The Parlay/OSA Framework
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
5- The next Parlay/OSA release
6- Summary, contacts

15. Current Parlay/OSA SCFs
Note 1: Multimedia and Conference Call Control not part of 3GPP OSA Release 4
Note 2: Not part of 3GPP OSA Release 4

16. Outline 0- Introduction 1- A closer look at Parlay/OSA
2- The Parlay/OSA Framework
- Framework functionality
- How does it work?
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
5- The next Parlay/OSA release
6- Summary, contacts

17. The Parlay/OSA Framework
- control of access to the network
- integrity management
- discovery of network functionality
Client Application
The functionality of the OSA Framework is grouped in two main sets of interfaces:
- Interfaces to the 3rd Party Applications, which provide mechanisms for controlling their access to the network (Authentication and Authorization), for ensuring the integrity of the network (e.g. Load and Fault Management), and for the Applications to Discover the functionality that the operator’s network exports via the OSA API.
- Interfaces to the other Service Capability Servers, which provide mechanisms for registration in the Framework of their Service Capability Features so that the Applications may discover them; they also provide the necessary access control mechanisms to allow the Framework functionality to be provided by an independent business entity (multi-domain). 1 2 2
Enterprise Operator
Registered Services
Framework
Call
Control
Mobility
etc 4 3
- Application subscription
to services
- SCF registration
- support of multi-domain

18. Outline 0- Introduction 1- A closer look at Parlay/OSA
2- The Parlay/OSA Framework
- Framework functionality
- How does it work?
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
5- The next Parlay/OSA release
6- Summary, contacts

19. How does the FW work ? Application Service / Framework SCS
4: authentication
5: request Discovery interface
6: discover Service
7: Select Service + sign SLA
10: return Service Manager
11: Use service
1: authentication
Framework
Service /
SCS
2: request Registration interface
3: register factory
8: create Service Manager
9: return Service Manager

20. Outline 0- Introduction 1- A closer look at Parlay/OSA
2- The Parlay/OSA Framework
- Framework functionality
- How does it work?
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
5- The next Parlay/OSA release
6- Summary, contacts

21. Information Application
The user dials in to the application to access information,
traffic
weather,
stocks,
etc
via voice.

22. Information Application : interaction flow before traffic
The Application registers to the Framework
The Framework starts a suitable Call Manager, and passes a reference to the application

23. Information Application : interaction flow during traffic
User calls service number
SCS checks subscription to service
Information presented to user via UI SCS
Application charges subscriber (either via Charging API, or indirectly via CC API)

24. Location Service
This is an example of combination of enterprise data with network capabilities
Bank services
Location services
Leisure
News

25. Location Service
The idea is that the user is able to find out the nearest ATM machine
Now we have moved money to our cash card. The nest problem is get cash from that card and for that we need to find an automatic teller machine - an ATM. Hopefully using a language I know.
For this we use a local location service, which include positioning and giving you a map on the terminal and if you want with certain things pointed out.
Positioning is one of the applications least people in our industry seams to be argue against being important as a service. Our strong believe is that he success comes from including positioning a component in services to refine them more. To give me more specific information to the end-user.
Directions
From To
ATM
Bank
Police
Default

26. Location service

27. Location service: interaction flow during traffic
The terminal interacts via WAP with application, selects ATM location option
The application invokes ‘userLocationRequest’ method, gets response
The application produces suitable map (including term.caps from WAP GW), provides this to terminal
This is a Parlay demo we provided in London:
Workforce organization (typically data from an enterprise domain), using the positioning/location information of the network.

28. Unified messaging application
The application allows user to access all his messages.
This is an example of combination of information in different business domains

29. Unified messaging application: interaction flow
The user sets messaging preferences (private and corporate combined if desired) via Web/WAP (or via voice recognition)
Notifications of different messages, plus actions, are handled by the application

30. Outline 0- Introduction 1- A closer look at OSA
2- The Parlay/OSA Framework
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
- Bodies involved in Parlay/OSA standardisation
- The Joint API Group
5- The next Parlay/OSA release
6- Summary, contacts

31. Bodies Involved In Parlay/OSA Standardisation
OSA specification and standardisation is a joint effort by the following bodies:
- 3GPP CN5
- ETSI SPAN12
- ITU-T SG11 (only ref. document)
- The Parlay Group
The objective is to have a single API for the whole developer community

32. OSA (Parlay) In 3GPP 3GPP joint-API-group OSA stage 3: protocols
Services and System
Aspects (SA)
Terminals (T)
Radio Access Network (RAN/GERAN)
Core Network (CN)
...
SIP
CAMEL
OSA
Services
Architecture +coordination
Security
Codec
Telecom mgmt
joint-API-group
OSA stage 3: protocols
OSA stage 1: requirements
OSA stage 2: architecture

33. OSA (Parlay) In ETSI
- In mid 2K, ETSI SPAN (Services and Protocols for Advanced Networks) was re-organized
- The group ETSI SPAN12, Application interfaces for service providers and network operators, was created
- An activity in ETSI SPAN14, called Service Provider Access Requirements (SPAR), was also created
- ETSI SPAN12, aware of the identical scope of the work in 3GPP CN5, agreed to work jointly and make all meetings joint meetings
- Today ETSI SPAN12 has an OSA Project, part of the Joint API Group and working also on OSA/Parlay Compliance

34. OSA/Parlay In ITU-T
- ITU-T SG11 has defined a Question 4 called API/Object interface and architecture for signaling, “covering the interface between network control and application layers”
- ITU-T has decided to write a reference document for this activity, and delegate the contents to other bodies
- This way ITU-T will adopt OSA specifications by ETSI (+3GPP +Parlay)
- ITU-T SG11 draft document is called TD 1/11-25, and it is expected to be approved at next SG11 meeting (18/2- 1/3/02)

35. Parlay (OSA) In The Parlay Group
- The Parlay Group ( started in March 98, and today is an open, multi-vendor forum with around 50 members from the IT and Telecom business
- The Parlay Group was aims to create open, technology independent APIs which enable developing applications across multiple networks (=OSA!); and to accelerate the adoption of these APIs and promotes their use and standardisation.
- Technical work in the Parlay Group is done in Work Groups; the Parlay WGs have joined the 3GPP+ETSI OSA (Parlay) joint group to develop together a single API

36. Outline 0- Introduction 1- A closer look at Parlay/OSA
2- The Parlay/OSA Framework
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
- Bodies involved in Parlay/OSA standardisation
- The Joint API Group
5- The next Parlay/OSA release
6- Summary, contacts

37. Today’s Parlay/OSA Joint Activities
- Today 3GPP, ETSI and Parlay have joined forces to specify a single API for the whole developer community
- Requirements coming from the three participating bodies are taken into account:
- 3GPP requirements from SA1 and SA2
- ETSI requirements from SPAN14
- Parlay requirements from the Parlay Group
- All meetings are joint meetings
- The joint work is based on a common (UML) model, Then each body generates its own document format

38. API’s for Open Service Access; ONE API for ONE developer community
1.) Requirements introduced by individual bodies
Parlay
JAIN
3.) Results are transferred back to individual bodies
Joint API Group
ITU-T
UMTS
OSA (Open Service Access)
2.) create the API that supports the superset of all requirements. (Joint meetings)
PSTN/ISDN
OSA (Open Service Access)
Current Workflow
Reference in ITU-T Roadmap

39. Joint Work Synchronization
2001
2002 1Q 2Q 3Q 4Q 1Q 2Q 3Q 4Q
Parlay
2.1
3.0
3.1
4.0
ETSI
1.0
1.1
2.0
3GPP
Release 4
4.0
4.1
4.2
4.3
No further changes accepted
5.0
5.1
5.2
5.3
Release 5
= point of alignment between specifications

40. Alignment and backwards compatibility
- The current last versions of the three bodies are fully aligned
3GPP Rel4  ETSI Ver1  Parlay 3
- None of them is backwards compatible with any of its previous releases/versions, due to changes based on feedback from implementers
- From now on backwards compatibility is a must

41. Parlay/OSA Document Structure (1/2)
The Parlay/OSA API is contained in two sets of documents:
- The API specification in terms of interfaces and their parameters (UML description and IDL specification), sequence diagrams and state models
- The Mapping specification of the Parlay/OSA API and network protocols : a possible, informative mapping from the API to various network protocols (i.e. MAP, CAP,..)

42. Parlay/OSA Document Structure (2/2)
The specification is in turn contained in the following documents:
- 3GPP : TS /12 parts (API) + TR (Mapping) /Rel4/29_Series - ETSI : ES (API) + TR (Mapping)
- Parlay
Choose your favorite: all are aligned!
Note: the reason for the numbering of parts 9 and 10, which are out of the scope of 3GPP OSA Rel4, is alignment with the ETSI version 1 specification, which does contain
- Part 9: Generic Messaging SCF
- Part 10: Connectivity Manager SCF

43. 3GPP2 And The Joint API Group
During the IP CN Harmonisation Workshop (Toronto, 3-4 April 2002) 3GPP2 expressed a strong interest in adopting the OSA/Parlay specifications
Since then 3GPP2 delegates have attended Joint API Group meetings informally, as guests.
Both “sides” agree that it is beneficial for all parties to continue the efforts to establish a working relationship between 3GPP2 and the Joint API Group.
The way to go is still under discussion in 3GPP and 3GPP2 management bodies; in the meantime cooperation is informal .

44. Outline 0- Introduction 1- A closer look at Parlay/OSA
2- The Parlay/OSA Framework
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
5- The next Parlay/OSA release
6- Summary, contacts

45. Ongoing Work for Parlay/OSA
- During the Montreal, 8-12/July/2002 Joint API Group, Parlay 4 (ETSI OSA version 2, 3GPP OSA Rel5) will be finalised - all backwards compatible with their corresponding previous versions.
A brief description of these new OSA features could be:
- MM Call Control: support of the additional functionality required for an IP Multimedia call, like open/close/modify/monitor media channels, reserve/free conference resources, ...
- User Profile Management:read/add/modify information in the User Profile; security/access rights, ...
- Retrieval of Network Capabilities: enable the applications to discover the capabilities of the user’s serving network.
- Information Services: supply/update/retrieve information, ...
- Presence Service: enable the management of presence entities in the presence service.
- Policy Management: create/modify/delete policies, collect policy statistics, ...
- e-Commerce: secure payment, support of any type of service and/or device, ...
- Journalling:the possibility to log usage of the OSA API.
- After that, based on requirements from all the bodies in the joint activity, Parlay/OSA will be enhanced with features like:
- User Profile Management
- Support for Local Services
- ...
... plus enhancements in the existing SCFs

46. Outline 0- Introduction 1- A closer look at Parlay/OSA
2- The Parlay/OSA Framework
3- Example Parlay/OSA applications
4- Parlay/OSA standardisation
5- The next Parlay/OSA release
6- Summary, contacts

47. Summary Of The Talk
- The Open Service Access API is an open, standardised interface for applications to use the capabilities of a network without owning it or knowing its technology
- It consists of a Framework, in charge of access control and service discovery; and some Service Capability Features, which map to network capabilities
- It is specified and standardised in the Joint API Group, with participation of 3GPP, ETSI and the Parlay Group: a single API for the whole developer community
- Parlay/OSA is available, fully aligned between 3GPP OSA Rel4, Parlay 3 and ETSI ver1. Backwards compatible enhancements soon to be published.

48. Contacts
Any of the authors of this presentation can be contacted for more information:
- Chelo Abarca (Alcatel),
ETSI SPAN OSA Project Leader
- Andy Bennett (Lucent),
Parlay Framework WG Chair
- Ard-Jan Moerdijk (Ericsson),
3GPP CN5 Chair
- Musa Unmehopa (Lucent),
3GPP CN5 Vice Chair