OSS at the Edge for Service and Application Enablement Brian Cappellani CTO Sigma System
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
OSS at the Edge for Service and Application EnablementBrian Cappellani
CTO
Sigma System
The Evolution of Services• The service delivery paradigm
is changing…
• Future service offerings will be defined by a different set of characteristics:– Greater numbers of services– Shorter service lifecycles– Personalized : “niche driven” and
user-controlled– On-demand, real-time and session
based– “Blended” - Delivered across multiple
access technologies
Service and Application Needs• Need not just “VoD”, but “XoD”• Common Model and Interfaces for:
– Authentication, Authorization and Subscriber Entitlements– Business Rule based Orchestration/Coordination of
Subscriber information and policy– Ability to access/utilize key network capabilities or enablers
such as QoS, presence, etc– Billing, Payment, key demographic information
• Similar requirements to existing OSS, but to support the application session– Abstraction– Subscriber Information Federation– SOA
Partners and Third Party Application Developers• Different types of application
developers– Traditional, “in house” – “Web 2.0” Mash-Ups
• Customers themselves – UGC, UGA
• Different characteristics– Level of trust, access– Level of telecom knowledge– Revenue opportunities– Speed of “on boarding”
Traditional OSS Role
• Define & re-use service & application building blocks• Assemble blended application bundles• Make services portable to multiple network and consumer
domains• Integrated orchestration of business rules, policies, entitlements
and device/network qualification to network-facing elements and repositories to support service/application execution
Increase Velocity of Service/Application Introduction
Telecom IT Enabler Building Blocks New Services
Months/Years Days/Weeks
What we could end up withDevice
CapabilityDevice
Capability
Network Elements /
App Servers
PresenceLocation
QoS / PCMM / Network Policy
Billing / Charging
Device Capability
TraditionalOSS
In House App 1
In House App 2
Partner App1 Partner App 2
Subscriber Repositories
Sub Data
Entitlement,Policy,Device
Capability,Charging
Device CapabilityDevice
CapabilitySub Data
Entitlement,Policy,Device
Capability,Charging
Device CapabilityDevice
CapabilitySub Data
Entitlement,Policy,Device
Capability,Charging
What we need
OSS at the Edge
Network Elements /
App Servers
PresenceLocation
QoS / PCMM / Network Policy
Billing / Charging
Device Capability
TraditionalOSS
In HouseApp 1
In HouseApp 2
Partner App 1 Partner App 2
Subscriber Repositories
Partner & Access Control Layer Partner Mgmt
OSS at the Edge• OSS in the “delivery path” of the service
– Subscriber information, business rules and policy decisions are orchestrated in real-time
– Integration of SDPs and 3rd party applications delivery
– Access to key enablers and information
• Subscriber policies are modeled across service lines – not limited by silo or application
• Subscriber policy execution includes mix of subscriber entitlements, network and device
– Subscriber-centric, federated information model with appropriate business rules
– Infrastructure APIs with appropriate level of service abstraction
– Ability to reuse existing systems in SOA-based environment
• Providing “5 Nines” of On-Demand Reliability
OSS at the Edge
Network Elements /
App Servers
PresenceLocation
QoS / PCMM / Network Policy
Billing / Charging
Device Capability
TraditionalOSS
In HouseApp 1
In HouseApp 2
Partner App 1 Partner App 2
Subscriber Repositories
Partner & Access Control Layer Partner Mgmt
Partner and Access Control Layer• Authentication• Security• User and Operator data
protection• Partner-based Policies for
– Access and Use– SLA– Settlement, Reporting
• Appropriate, simplified APIs• Partner Management
interfaces – Automated on-boarding
OSS at the Edge
Network Elements /
App Servers
PresenceLocation
QoS / PCMM / Network Policy
Billing / Charging
Device Capability
TraditionalOSS
In HouseApp 1
In HouseApp 2
Partner App 1 Partner App 2
Subscriber Repositories
Partner & Access Control Layer Partner Mgmt
In Summary
• New requirements for OSS driven by:– New on-demand services and applications– New partners and interactions
• Key to realizing the value of this environment will be OSS that can deliver both current “back office” and future “edge” requirements in an integrated fashion
Related Documents
