9 Parlay X Web Services: OSA at a higher level of abstraction

23.1273GPPRelease 6TSVirtual Home Environment (VHE) / Open Service Access (OSA)

9.1 General

The general architecture of a solution including Web Services and/or OSA links in deployment allows a number of deployment configurations. These configurations are derivatives of a basic architecture model, enabling a variety of deployment options.

A typical Parlay X Web Services deployment model is shown in the Figure 9.1. This model shows the publication of Parlay X Web Services through a registry, making those Web Services available for discovery, and for applications to use Web Services access methods to interact with the Gateway, where the Web Service interfaces are implemented.

Figure 9.1 Parlay X Web Services deployment model

Interfaces to the Web Services Registry are drawn in Figure 9.1 for consistency with Web Service architectures, but they are not in the scope of the Parlay X Web Services.

This architecture may be combined with existing OSA deployment configurations, providing the overall architecture as illustrated in Figure 9.2.

EMBED Word.Picture.8

Figure 9.2 The overall Parlay X Web Services architecture

9.1.1 Deployment Scenario A: Web Services to OSA

This scenario addresses solutions that combine Web Services interfaces facing the exterior of the network with OSA interfaces facing the interior of the network.

Figure 9.3 Deployment Scenario A: Web Services to OSA

Environment Description

The Application will utilize Web Services to discover and interact with the network, and will not have visibility to the OSA implementation behind the Parlay X Web Services Gateway. The Parlay X Web Services Gateway attaches to the OSA Gateway through an OSA interface. The information published to the Web Services Registry provides the Application with the connection information required to connect with the Parlay X Web Services Gateway.

9.1.2 Deployment Scenario B: Web Services to Network Element

This scenario addresses solutions that combine Web Services interfaces facing the exterior of the network with network element specific interfaces facing the interior of the network.

Figure 9.4 Deployment Scenario B: Web Services to Network Element

Environment Description

The Application will utilize Web Services to discover and interact with the network, and will not have visibility to the implementation behind the Parlay X Web Services Gateway. The Parlay X Web Services Gateway attaches to the Network Element through an interface defined by the Network E lement. These interfaces (i.e. Element defined interface) are not in the scope of this specificaiton. The information published to the Web Services Registry provides the Application with the connection information required to connect with the Parlay X Web Services Gateway.

The next sections describe the Web Services supported by OSA Rel6.

9.2 Third Party Call

This Web Service supports the functionality to create and manage a call initiated by an application (third party call). Using the Third Party Call Web Service, applications can invoke call handling functions without detailed telecommunication knowledge. The functionality provided is:

– Make a call which sets up a call between two addresses

– Get call information gives information about how the call progressed in the network

– End call will cease the call

– Cancel Call Request allows the network to prevent call setup before completion

9.3 Network-Initiated Third Party Call

These functions are for handling calls initiated by a subscriber in the network. A (third party) application determines how the call should be treated. The overall scope of this Web service is to provide simple functions to application developers to determine how a call should be treated. Using the Network-Initiated Third Party Call Web Service, application developers can perform simple handling of network-initiated calls without specific Telco knowledge. The Web services allow the application to handle the following conditions occurring in the set-up of a call:

– Destination busy

– Address is not Reachable

– Destination is not answering

– A specific number has been called by subscriber

– The subscriber has taken the terminal "off-hook"

9.4 SMS

The overall scope of this Web Service is to provide to applications the means to handle SMS in a simple way. For receiving a message from the network, the application may use either polling or notification mechanisms. The notification mechanism is more common: network-initiated messages are sent to autonomous application-side web services. Both mechanisms are supported, but the provisioning of the notification-related criteria is not specified. Services are specified to enable an application to:

– Send any SMS

– Send a logo embodied in an SMS

– Send a ringtone embodied in an SMS

– Retrieve the delivery status of an SMS

– Request to be notified of received SMSs

– Retrieve SMS messages sent to an address

9.5 Multimedia Message

This is additional to the SMS web services and handles more general messaging case. Multimedia Message services provide generic messaging features (including SMS) to send and receive messages. For receiving a message from the network the application may use either polling or notification mechanisms. Network-initiated messages are sent to autonomous application-side web services. The following functions are supported:

– Send a message to an address

– Retrieve the delivery status of a message

– Retrieve by polling for received messages

– Retrieve message parts by URI references

– Retrieve whole messages as SOAP attachments

– Notification to the application that a message has been received for a specific address

9.6 Payment

The Payment Web Services support payment reservation, pre-paid payments, and post-paid payments. They support charging of both volume and currency amounts, a conversion function, and a settlement function in case of a financially resolved dispute. The functions supported enable the application to:

– Charge/refund an account by a currency amount

– Charge/refund an account by volume (e.g. minutes)

– Calculate a currency amount from a volume for a specific account

– Reserve a currency amount on an account

– Charge a prior reservation to the account

– Release a reservation by returning to an account the amount remaining in a reservation

– Reserve a volume amount of an account

9.7 Account Management

The Parlay X Account Management supports account querying, direct recharging and recharging through vouchers. The application can manage various aspects of an account using the functionality to:

Return the currency balance on an account

– Request what date the credit on an account is due to expire

– Update the currency/account balance on an account

– Return the transaction history on an account

9.8 User Status

The Parlay X User Status Web Service is used for getting user status information. The functionality supported is simple:

– Requests a user’s status subject to the user’s policies.

9.9 Terminal Location

The Parlay X Terminal Location Web Service is used for getting location information, it does not require specific telecommunication skills, but a knowledge of location co-ordinates is required. One service is specified to:

Request the location of one terminal subject to user’s privacy policies.

Annex A (informative):
Change History

Change history

TSG SA#

Version

CR

Tdoc SA

New Version

Subject/Comment

SA_09

3.1.0

012

SP-000452

3.2.0

CR on Parlay-OSA alignment: basic service interface

SA_09

3.1.0

013

SP-000452

3.2.0

CR on Parlay-OSA alignment: initial contact interfaces

SA_09

3.1.0

014

SP-000452

3.2.0

CR on Parlay-OSA alignment : access SCF

SA_09

3.1.0

015

SP-000452

3.2.0

CR on Parlay-OSA alignment: load manager SCF

SA_09

3.1.0

016

SP-000452

3.2.0

CR on Parlay-OSA alignment: fault manager SCF

SA_09

3.1.0

017

SP-000452

3.2.0

CR on Parlay-OSA alignment: service factory SCF

SA_09

3.1.0

018

SP-000452

3.2.0

CR on Parlay-OSA alignment: authentication interface

SA_09

3.2.0

011r1

SP-000452

4.0.0

Change of TS 23.127 title for version 4.0.0 and up

SA_11

4.0.0

020

SP-010118

4.1.0

Alignment of 23.127 due to transfer of stage 3 content to 29.198

SA_11

4.0.0

021

SP-010118

4.1.0

Alignment due to additional Release 4 capabilities.

SA_12

4.1.0

026

SP-010332

4.2.0

CR on addition of transport examples in addition to CORBA

SA_14

4.2.0

027r1

SP-010710

5.0.0

CR on creation of VHE Stage 2 for Release 5 and change of name to include "OSA" in title

SA-15

5.0.0

032

SP-020133

5.1.0

OSA Internal API, Integrity Management

SA-15

5.0.0

034r1

SP-020133

5.1.0

Refinement of OSA Mobility SCF

SA-15

5.0.0

035r1

SP-020133

5.1.0

Correction in Mobility SCF definition

SA-15

5.0.0

037r1

SP-020133

5.1.0

Mapping of OSA API-s to Presence

SA-16

5.1.0

041r1

SP-020314

5.2.0

Removal of Mapping of Presence OSA APIs

SA-16

5.1.0

042r1

SP-020314

5.2.0

Proposal to remove the feature "Retrieval of visited network capabilities"

SA-16

5.1.0

043r1

SP-020314

5.2.0

Reduction of scope of OSA Rel5

SA-18

5.2.0

044

SP-020777

6.0.0

Mapping of OSA APIs to Presence

SA-24

6.0.0

047r1

SP-040315

6.1.0

Add descriptions of OSA high-level abstraction interfaces