Wednesday, October 15, 2008

SOA Solutions in Telecom Today

SOA workshop session 2 SOA Solutions in Telecom Today has three speakers, Babak Sadighi, Axiomatics ; James Aitken, Aepona Ltd; Antonio Fontan, Microsoft.

Key messages

Axiomatics

  • How does standardized authorization mnagement support SOA in Telecom Networks (focus on use of XACML, at service and device configuration level)
  • Authorization is meant as a service to other applications and services
  • As well as location, IPTV … it would be important to provide also Authorization as a “telecom service”
  • Operators would like to avoid micro-management of services and features of service providers (avoid micro-management)
  • SPs need to control their services themselves
  • Gave examples on access permissions (e.g. end user access to service) and on specific services for users (e.g. parking service… different policies)
  • Issues: policy enforcement, policy administration, attribute management
  • Authorization service shall be provided by Operators to SPs and XACML 3.0 can play an important role


Aepona

  • Core Telco service enablers: payments, messages, presence, location --> they are assets
  • SOA is about the interface for 3rd parties to access such enablers
  • 3 “killer capabilities”: contextual presence, location – flexible media and conference switching – Intelligent notification services
  • WS for telecom exist: Parlay-X: enphasis must be put on refining and making them popular
  • Concrete examples of application of WS in Telecom (automated appointment reminder, public sector property maintenance … enhanced)
  • Real web services need policy and security control – SDOs must work on this

Microsoft Mediaroom

  • Brand name for IPTV solution: platform for delivery of video over (reliable) IP network
  • Broad view of the End-2-End IPTV solution: content acquisition, content protection, service management, subscriber management, service delivery, service consumption
  • Provided high level view o the architecture
  • SOA enables highly decoupled, modular and interoperable architecture
  • Understood OSS and BSS functionalities applied to the platform

Use SOAP based web services

  • Loosely coupled services

Lessons learned

  • Web services ala RPC increased coupling and reduced agility
  • SOAP limitations (exposing/retrieving large resources and low end hardware)
  • It is critical adding better control for accessing server resources
  • Modeling unknown applications is hard
  • Saying “contract first” is not good enough

Future needs

  • Better control of workflow
  • Simplify access to resources to facilitate application extensibility
  • Emphasis on modeling (access profiles, layering of interfaces)
  • Need standards on SLA management


No comments:

  • Categories

  •