Interactions between Parlay Gateways - PowerPoint PPT Presentation

Loading...

PPT – Interactions between Parlay Gateways PowerPoint presentation | free to view - id: ce18-OTZhO



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

Interactions between Parlay Gateways

Description:

The Proxy manager looks like an SCF from the 'Receiver' Gateway perspective ... short-term solution, the Parlay Proxy. Proxy component can be used for ... – PowerPoint PPT presentation

Number of Views:49
Avg rating:3.0/5.0
Slides: 14
Provided by: serge5
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: Interactions between Parlay Gateways


1
Framework Federation integrated Parlay Gateways
Parlay Open Meeting in Bangkok, 2003 Serge
Popov spopov_at_jnetx.com
2
Outline
  • Introduction
  • What is Framework Federation?
  • Business cases
  • High-level requirements
  • Seamless integration of gateways from different
    vendors
  • Interpretability of geographically distributed
    Parlay Gateways
  • Implementation strategies for the Framework
    Federation concept
  • SCSs registered in multiple Frameworks
  • Proxy Manager
  • Thank you!

3
Introduction
Value-Added Services
Core Network Services
Enterprise Domain
DB
Application 1
Application 2
Application 3
What if there are two Parlay Gateways?
?
Parlay Gateways JAIN SLEE apps
Parlay Gateway 1
Parlay Gateway 2
The topic Integrated Parlay Gateways
Telecom network
Telecom Network
4
Business cases for the Framework Federation
  • High-level requirements
  • Integration of Parlay Gateways from different
    vendors
  • Interpretability of geographically distributed
    Parlay Gateways
  • Business cases
  • Multiple gateways owned by different departments
    of a large organization Core Network,
    Value-Added Services, Research Development
  • An operator that owns a fixed-line network and a
    mobile network
  • Virtual Network Operator that owns its own Parlay
    Gateway

5
Framework Federation Standard-based approach
Donor gateway
Receiver gateway
Step 3 Announce availability of the new SCFs
As a result of these configuration steps the
application may seamlessly use SCSs provided by
both gateways
Step 1 Register a donor SCS in the receiver
Framework
Framework 2
Framework
Step 2 Restrict usage of the SCS (setup service
properties)
SCS 2
SCS 3
SCS 1
SCS 4
6
Framework Federation Standard-based approach, 2
  • The current specification of the Parlay Framework
    provides a standard way for implementation of the
    Framework Federation. Below are the configuration
    steps
  • Step 1 Register a donor SCS in the receiver
    Framework
  • Step 2 Restrict usage of the SCS by assigning
    proper values to service properties (e.g. maximum
    number of simultaneous calls)
  • Step 3 Announce availability of the new SCFs
  • As a result of these configuration steps an
    application can seamlessly use SCSs provided by
    both Parlay Gateways

7
Framework Federation Standard-based approach, 3
  • Advantages
  • Based on the standard Framework APIs
  • Framework-to-Service API
  • Framework-to-Application API (event
    notifications, service discovery)
  • Requirements
  • SCS shall support
  • First, standard service registration procedures
  • Second, simultaneous registration in multiple
    Frameworks (this is not clearly stated in the
    specification)
  • SCS shall be able to register with a new
    Framework while still being registered with
    original Framework
  • SCS shall support usage thresholds based on
    service properties. The values of the service
    properties are given to an SCF by a Framework
    during the process of assigning a Service Manager
    to an application
  • The Framework shall support
  • The standard procedure of the service
    registration
  • Service properties

8
Framework Federation Standard-based approach, 3
  • Today, its difficult to integrate Parlay
    Gateways this way because
  • Not all the vendors implement all of the Parlay
    features required for implementation of the
    Framework Federation
  • The Parlay specification doesnt clearly support
    this scenario
  • Parlay specifications dont provide a standard
    set of service properties that would allow usage
    control across SCSs and Frameworks of different
    vendors
  • As a result, integration of gateways from
    different vendors is not as straightforward as
    it could be

9
Framework Federation regular approach, 4
  • The Parlay addresses the Framework Federation
    concept in OSA Rel. 6
  • There is a short-term solution for the
    integration of Parlay gateways

10
Framework Federation Proxy approach
Donor gateway
Receiver gateway
Application
Framework 2
SCS
Framework
Proxy
SCS 2
SCS 3
SCS 1
SCS 4
11
Framework Federation Proxy approach (2)
  • Two interfaces
  • The Proxy manager looks like an SCF from the
    Receiver Gateway perspective
  • It looks like an application from the Donor
    gateway perspective
  • Features
  • Proxy increases security
  • Load-balancing
  • Fault-tolerance

12
Summary
  • Implementation of the Framework Federation
    concept requires support by Parlay specs
  • There is a short-term solution, the Parlay Proxy.
  • Proxy component can be used for different
    purposes other than just implementation of the
    Framework Federation
  • Framework Federation is proposed for Parlay 5.0

13
  • Thank you!

Serge Popov spopov_at_jnetx.com
About PowerShow.com