Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Brian cappellani scte et 2008 presentation

652 Aufrufe

Veröffentlicht am

Veröffentlicht in: Technologie, Business
  • Login to see the comments

  • Gehören Sie zu den Ersten, denen das gefällt!

Brian cappellani scte et 2008 presentation

  1. 1. OSS at the Edge for Service and Application Enablement <ul><li>Brian Cappellani </li></ul><ul><li>CTO </li></ul><ul><li>Sigma System </li></ul>
  2. 2. The Evolution of Services <ul><li>The service delivery paradigm is changing… </li></ul><ul><li>Future service offerings will be defined by a different set of characteristics: </li></ul><ul><ul><li>Greater numbers of services </li></ul></ul><ul><ul><li>Shorter service lifecycles </li></ul></ul><ul><ul><li>Personalized : “niche driven” and user-controlled </li></ul></ul><ul><ul><li>On-demand, real-time and session based </li></ul></ul><ul><ul><li>“ Blended” - Delivered across multiple access technologies </li></ul></ul>
  3. 3. Service and Application Needs <ul><li>Need not just “VoD”, but “XoD” </li></ul><ul><li>Common Model and Interfaces for: </li></ul><ul><ul><li>Authentication, Authorization and Subscriber Entitlements </li></ul></ul><ul><ul><li>Business Rule based Orchestration/Coordination of Subscriber information and policy </li></ul></ul><ul><ul><li>Ability to access/utilize key network capabilities or enablers such as QoS, presence, etc </li></ul></ul><ul><ul><li>Billing, Payment, key demographic information </li></ul></ul><ul><li>Similar requirements to existing OSS, but to support the application session </li></ul><ul><ul><li>Abstraction </li></ul></ul><ul><ul><li>Subscriber Information Federation </li></ul></ul><ul><ul><li>SOA </li></ul></ul>
  4. 4. Partners and Third Party Application Developers <ul><li>Different types of application developers </li></ul><ul><ul><li>Traditional, “in house” </li></ul></ul><ul><ul><li>“ Web 2.0” Mash-Ups </li></ul></ul><ul><ul><ul><li>Customers themselves – UGC, UGA </li></ul></ul></ul><ul><li>Different characteristics </li></ul><ul><ul><li>Level of trust, access </li></ul></ul><ul><ul><li>Level of telecom knowledge </li></ul></ul><ul><ul><li>Revenue opportunities </li></ul></ul><ul><ul><li>Speed of “on boarding” </li></ul></ul>
  5. 5. Traditional OSS Role <ul><li>Define & re-use service & application building blocks </li></ul><ul><li>Assemble blended application bundles </li></ul><ul><li>Make services portable to multiple network and consumer domains </li></ul><ul><li>Integrated orchestration of business rules, policies, entitlements and device/network qualification to network-facing elements and repositories to support service/application execution </li></ul>Increase Velocity of Service/Application Introduction Telecom IT Enabler Building Blocks New Services Months/Years Days/Weeks
  6. 6. What we could end up with
  7. 7. What we need
  8. 8. OSS at the Edge <ul><li>OSS in the “delivery path” of the service </li></ul><ul><ul><li>Subscriber information, business rules and policy decisions are orchestrated in real-time </li></ul></ul><ul><ul><li>Integration of SDPs and 3 rd party applications delivery </li></ul></ul><ul><ul><li>Access to key enablers and information </li></ul></ul><ul><li>Subscriber policies are modeled across service lines – not limited by silo or application </li></ul><ul><li>Subscriber policy execution includes mix of subscriber entitlements, network and device </li></ul><ul><ul><li>Subscriber-centric, federated information model with appropriate business rules </li></ul></ul><ul><ul><li>Infrastructure APIs with appropriate level of service abstraction </li></ul></ul><ul><ul><li>Ability to reuse existing systems in SOA-based environment </li></ul></ul><ul><li>Providing “5 Nines” of On-Demand Reliability </li></ul>
  9. 9. Partner and Access Control Layer <ul><li>Authentication </li></ul><ul><li>Security </li></ul><ul><li>User and Operator data protection </li></ul><ul><li>Partner-based Policies for </li></ul><ul><ul><li>Access and Use </li></ul></ul><ul><ul><li>SLA </li></ul></ul><ul><ul><li>Settlement, Reporting </li></ul></ul><ul><li>Appropriate, simplified APIs </li></ul><ul><li>Partner Management interfaces </li></ul><ul><ul><li>Automated on-boarding </li></ul></ul>
  10. 10. In Summary <ul><li>New requirements for OSS driven by: </li></ul><ul><ul><li>New on-demand services and applications </li></ul></ul><ul><ul><li>New partners and interactions </li></ul></ul><ul><li>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 </li></ul>

×