This document provides an overview of service-oriented architecture (SOA) and its role in the telecommunications industry. It defines SOA and discusses how SOA principles can be applied through technologies like web services. The document also examines SOA adoption in telecom, including how SOA can help accelerate service creation and monetization. It explores SOA implementations for telecom like service delivery platforms and the integration of OSS/BSS systems with IMS. Finally, the document notes some challenges for service providers and the value proposition of SOA in addressing issues like increasing revenue and reducing costs.

1. An SOA Overview and Role in Telecom

2. Content
 Introduction to SOA – Principles, Milestones, Architecture, Tech & Business perspective,
SOA/Web services
 SOA Market Size
 SOA for Telecom – Telecom web services, SDP, IMS, Challenges, migrating to SOA
 Summary & Conclusion
2

3. Definitions
SOA is a design for linking business and computational resources
(principally organizations, applications and data) on demand to achieve
the desired results for service consumers (which can be end users or other
services)
A paradigm for organizing and utilizing distributed capabilities that may be
under the control of different ownership domains. It provides a uniform
means to offer, discover, interact with and use capabilities to produce
desired effects consistent with measurable preconditions and expectations
Service-oriented architecture (SOA) is a style of design, deployment, and
management of software infrastructure and applications to create a more
flexible digital embodiment of an enterprise
service-oriented architecture (SOA) is a higher level of application
development that enables IT to focus on business processes, rather than
the underlying IT infrastructure, to achieve competitive advantage
3

4. Milestones
SOA leverages precious technologies
4

5. SOA – Paradigm shift
5

6. Architecture layers
Business
Process Layer
Service
Layer Account Employee Order Customer
Lotus
Finance
Application Notes
Layer ERP CRM
Directory HR
Technology J2EE Linux
IBM Microsoft
CICS .NET
Layer
6

7. SOA - Business Perspective
7

8. SOA – Technology Perspective
8

9. How SOA Works
9

10. SOA and Web services
 SOA may be built on Web services standards (e.g., using
SOAP) that have gained broad industry acceptance. These
standards (also referred to as web service specifications)
also provide greater interoperability and some protection
from lock-in to proprietary vendor software
 SOA is often defined as services exposed using the Web
Services Protocol Stack . The base level of web services
standards relevant to SOA includes the following:
 XML - a markup language for describing data in message payloads in a document format
 HTTP (or HTTPS) - request/response protocol between clients and servers used to transfer or convey
information
 SOAP - a protocol for exchanging XML-based messages over a computer network, normally using HTTP
 XACML - a markup language for expressing access control rules and policies.
 Web Services Description Language (WSDL) - XML-based service description that describes the public
interface, protocol bindings and message formats required to interact with a web service
 Universal Description, Discovery, and Integration (UDDI) - An XML-based registry to publish service
descriptions (WSDL) and allow their discovery
10

11. Example: Amazon vs Salesforce.com Web Services
Amazon Web Services SalesForce.com Web Services
 Hosted e-commerce as Web Services  Hosted CRM as Web Services
 SOA providing Meaningful Business Services  General purpose API proving simple “CRUD”
 Retrieve price and availability information capability
in real-time  Insert
 Generate lists of best-selling products on
 Update
the fly
 Delete
 Display Amazon.com search results
directly on their Web pages  Consumer needs to understand application and
 Build a recommendations engine using business rules
Amazon “similarities” features  Service consumer has to do all the work
 Enable their visitors to add items to their
Amazon shopping carts without leaving
their Web site
 Automatically manage inventory
 Generate order reports
 Submit refunds in large quantities
 Download competitive pricing information
11

12. SOA Standards/Forum
 SOA Standards fall into roughly three categories:
 Format standards - SOAP, XML-RPC, REST, EDI, etc.
 Service standards - WS-*
 Process standards - BPEL, BPMN, XPDL, ebXML, RosettaNet
 The primary SOA standards bodies are:
 OASIS (Organization for the Advancement of Structured
Information Standards)
 OSOA (Open SOA)
 W3C (World Wide Web Consortium)
 WS-I (Web Services Interoperability Organization)
 Forum
 CBDI (www.cbdiforum.com)
12

13. Worldwide SOA based services spending
US$ M 2006 2007 2008 2009 2010 2011 CAGR
Americas 3,439 5,584 8,717 11,898 15,274 18,104 39.4
EMEA 2,072 3,185 5,125 7,710 10,946 13,815 46.1
APAC 825 1,582 2,788 4,484 6,485 8,906 60.9
Total 6,336 10,351 16,630 24,092 32,705 40,825 45.2
SI: developing an SOA governance structure
and a services management
approach, setting up an SOA competency
center, and/or consolidating applications
Consulting: transformation services
(e.g., cultural change, organizational
redesign, leadership effectiveness, business
process reengineering, communication
plan, IT/business alignment, and training)
Software deploy and support: new IT and
business services
13

14. Market predictions
 Smaller vendors will struggle even more, the justifications for picking niche
products will increase
 Hardware virtualisation will become the "norm" for new deployments
 Business level modeling will continue to be a pipe dream, filled either with
overly complex tools or insanely technical ones
 Indian enterprises graduating to the second level of dynamic IT infrastructure,
where IT infrastructure would be able to bring about changes instantly to suit
the dynamic business scenario
14

15. The Next Big SOA Challenge
Moving Past the Division
Enterprise level
services
SOA
Maturity Cross divisional SOA
Level services Optimized
Division level
SOA
services
Managed
Project level
services SOA
Repeatable
No
SOA
implementations
Defined
SOA
Ad Hoc
No SOA
Exploring Expanding Exploiting
15

16. SOA in Telecom
 Accelerates service creation, delivery and monetization, using a very cost-effective services layer
architecture
 For service providers, SOAs and Web services have the power to open lucrative new markets and
generate substantial new revenues by facilitating communication and interaction between the internal
and external applications of their customers
 SOAs and Web services can profoundly increase the revenue-generation and market-expansion
opportunities offered by next-generation network environments
 The principles of SOA are currently being applied to the field of network management. eg: SOA
network management architectures are TS 188 001 NGN Management OSS Architecture from ETSI, and
the recently published M.3060 Principles for the Management Of Next Generation Networks
recommendation from the ITU-T SOA
 SOA is primarily intended to provide business-level software modularity and rapid reuse of software
components
 SOA community and Telecoms Operators have not explored enough such an architecture for telecom
and network services
16

17. Telecom Web Services
 Telecom Web Services provide the core building blocks that enable a carrier to expose the capabilities of
its network to third party application providers and enterprise customers in a secure, controlled, and
billable manner
 In addition to underpinning a carrier’s so-called “Service Delivery Platform”, providing internal and
external access to network resources, Telecom Web Services may be sold as a revenue generating service
marketed by the carrier to enterprise customers
 Within 3GPP/OSA there is increasing focus on the Telecom Web Service standards and the associated
SOA. There is a strong drive to identify and standardize the Telecom Web Services that are necessary to
support next generation ASPs and carriers
 The evolving OSA Parlay/Parlay X standard, defined by 3GPP, 3GPP2, ETSI and the Parlay Group (the
3GPP TS 29.199 set of standards) provide the essential standards base for Telecom Web Services
 With the increasing use of the SOA the TMF NGOSS TAM (Telecom applications map) may become a
useful framework for organizing and categorizing Web Services that specify accessibility to offered
application/component capability
 Telecom Web Services allows network operators to accelerate the adoption of enterprise/IT software
concepts such as SOA into the telecoms domain
 Provides operators with a cost saving, standardised interface between its network services, its content
delivery and applications
17

18. Telecom Web Services Architecture
18

19. OSS/BSS Realities
 The convergence of OSS/BSS Systems with IMS based upon SOA principles is underway in telecom enterprises
 Service providers see SOA as enabling significant improvements in OSS/BSS
 Vendors see SOA as driving down OSS/BSS costs
 SOA may be particularly beneficial to OSS/BSS development because it is designed to foster communication among
many disparate, horizontally distributed components
TDM Services TDM Services
IP/IMS Services IP/IMS Services
Converged Services Market Converged Services
Wireless Services requirements Wireless Services
Meas/Validation Services Meas/Validation Services
lower cost RTUs
OSS 1 OSS 2 Cheaper/Faster OSS 1 OSS 2 OSS 3 OSS 4
Integration
services
Enterprise service bus
OSS 3 OSS 4
OSS 5 OSS 6
New OSS
OSS 5 OSS 6
Yesterday’s OSS & BSS Systems Today’s SOA – Based OSS & BSS Systems
• Common shared service interfaces (opens data)
• Pair wise proprietary Point-to-point interfaces
• Cheaper/faster integration
• Expensive/ Time consuming Integration
• Abstracts/Simplifies interfaces
• Adding new interfaces impacts existing interfaces
• No impact to existing interfaces to add new ones
• Complexity not needed in IP world
• Flexible coupling/decoupling
19

20. SOA – BSS Integration
 All communications
between BSS and the
service platform shall go
through the service bus
(or via a dedicated
application in the
service platform).
 The BSS system can
handle the service
platform as one
component.
20

21. Integration Architecture
Customer care Ordering Provisioning Billing Revenue sharing BSS
Adapter Adapter Adapter Adapter Adapter
BSS and OSS Integration Bus
Service and process creation
XML Provisioning OSS/BSS
Service
Process Process
Choreography
Choreography Choreography
Product Service Subscriber Device Process SID
server
server server catalog catalog catalog catalog catalog mapping
UML
Service Integration Bus
SQL
BPEL
EJB
Java
C/C++ Service Domain Service Domain Service Domain Service Domain
Service Delivery Environment
Control
plane
Transmission Core Access Home network Gateway
Network
21

22. IMS – SOA Infrastructure platforms
 These platforms open doors to the new applications and services
 IMS opens up network features (eg. Voice, presence, location) at the
service layer
 SOA helps to monetize IMS investments
 SOA is a defined way of designing, deploying and managing software
applications and infrastructure
 Applications are separated into modular services
 Standard web-based interfaces are used to compile services
 Services and business policies are stored in a single directory
 QoS components can be assigned to the services
22

23. Service Delivery Platform based on SOAs
 Network operators are now facing a new architectural concept, a platform for
service delivery that is entirely decoupled from the network infrastructure and is
built on top of Service Oriented Architectures (SOA) and web services concepts
 SOAs can be used as an application integration technology within an SDP but are
best served when used in the lower performance functions such as connections
between the transactional OSS and BSS applications and the SDP
 SDP is based on the principles of SOA and reusability, providing a common set of
functions and a common way to view the underlying network. Increasingly SDP
standards are coming into the telco world from the IT sector
 Service orchestration technologies (such as BPEL) is becoming part of emerging
SOA SDPs, enabling services to be composed from telecom functional blocks and
blocks of business logic from the IT domain
Next generation SDPs : SOA enabled SDP
23

24. Services….. Caller ID on IPTV
 Using IPTV, the service provider can
provide various value-added services
like caller ID (This service enables a
user who is watching the TV receive
voice call identification on the TV
screen and then provides the option
for pausing & recording the video
stream for the duration of the call)
 If the underlying implementation is
based on SOA, new providers and
new equipments is easily
incorporated and able to produce
services with a fast time to market.
This includes new types of set-top
boxes as well as residential GW’s at
the end-users premises. Also the
network configuration benefits from
the SOA approach, as in new
network equipment can be added
from new vendors as well.
24

25. Why to migrate towards SOA ?
 maturity of SOA basic technologies and products
 reduced gap between: Telco and IT solutions
 service layer not replacing, but complementary to existing service
frameworks (e.g., IMS, Web, IPTV)
 requirements for “blended” applications (eg. content-delivery +
communication)
 push to address new business models aligned with the trends of Internet &
SoC (Service oriented computing)
25

26. Challenges faced by service providers
 Declining revenues
 Displacement of fixed voice services with VoIP
 Declining of ARPU from mobile services & applications
 Increased competition
 Competition from cable operators
 New entrants into the market (Google, Vonage, yahoo….)
 Organization impacts
 Limited collaboration among sales, OSS/BSS & provisioning
 Legacy processes and systems unable to support new models
 Network convergence
 IMS network architecture initiatives
 Consolidation drives FMC
26

27. Value Proposition for a set of Distinct
Business Challenges
Increase revenue Provide a flexible business
create new routes to the market, create model
new value from existing systems React to market changes very quickly
Drive down cost Reduce risk and exposure
Eliminate duplicate systems, Value Improve visibility into business
build once and leverage, Proposition operations
improve time to market
Reduce cycle times and cost of Integrate across the enterprise
External business partners Integrate historically separate systems,
Move from manual to automated facilitate M&A of enterprises
transactions, facilitate flexible dealings with
Business partners
27

28. SOA Professional Services
• Consulting and systems integration
services represent the primary SOA-
related service markets, especially in
the early years of SOA adoption.
• Service vendors are increasingly
embedding SOA in their overall
consulting and SI engagements
28