ATIS’ Service Oriented Networks (SON) Activity Andrew White, Nokia Siemens Networks DOCUMENT #:GSC15-PLEN-81r1 FOR:Presentation SOURCE:ATIS AGENDA ITEM:PLEN 6.13 CONTACT(S):Andrew White Global Standards Collaboration (GSC) GSC-15

2 SON Value Proposition  It is about people! It is not about devices. People are mobile, and they use services not technologies. SON is about services and services are everywhere.  It is about Globalization! Service supply chains are distributed and real time. Best of breed capabilities come from many industries.  It is about Technology! Great technology melts into the background. Reusable infrastructure reduces cost of new services. Software and integration skills are keys to success.

3 Service Oriented Network Service Oriented Networking abstracts resources (applications, hardware, and networks) into defined and reusable service enablers to facilitate cross-domain blending.

4 Factorial Value of SON  Traditional networks increase in value by power law with the number of connections. (Metcalf’s Law) ½ * n * (n – 1), n = connections  Service inventories generate factorial value through permutations of service enablers. (White’s Law) n! / (r! (n – r)!), n = enabler inventory, r = enablers per service Service Inventory 1 Service Enabler (SE) 25 Service Enablers (SEs) 50 Service Enablers (SEs) Silos12550 Combined in threes* 12,30019,600 * Order not important (only one order makes sense). Repetition not allowed.

5 SON Forum Current Highlights  A Service Enabler Characterization Technical Report has been published. Service Enabler Characterization provides key information such as lifecycle details, chargeability, and capacity. These are details not contained in the functional definition of a service enabler. A goal is to provide maximum flexibility in where service enablers can be deployed or consumed. This document does not address how Service Enablers get published or discovered. SON solicited industry comments in November  Two additional work items are progressing towards completion: Common Namespace Requirements. 3rd Party Service Provider Interface Profile.

6  SON Forum is focused on data aspects of service architecture.  Documents in the SON Forum support that view: Service Enabler Characterization. Common Namespace Requirements. 3rd Party Service Provider Interface Profile. Strategic Direction

7  Service Oriented Networks is a new standards area and substantial work remains to be done to achieve a comprehensive view.  There are multiple PSOs working in SON-related areas. Harmonizing this work into a cohesive service inventory is a significant task.  Horizontal frameworks such as SONs that optimize long term reusability continue to compete with integrated silo solutions that optimize first service delivery. Challenges

8  Progress other priority areas to completion by end of  SON Forum technical program. Next face to face meeting: 18 October 2010 Washington, DC Next Steps/Actions

9 Proposed Resolution  ATIS proposes a new Resolution on Service Oriented Networks contained in GSC15-PLEN-86.

Service Oriented Networks (ATIS) Summary  Presentations 2 SON contributions from CCSA (60) and ATIS (81).  Summary Frameworks facilitate integration and adaptation of service enablers  A minimum set of common functions is required in the framework  These frameworks allow interworking across technologies: IMS, SOA, Web 2.0, Cloud, etc. Service Providers use the framework to integrate service inventories into multiple products Support for flexible reuse of service enablers allows the same functions to be used for multiple retail and wholesale products Service Oriented Networks are structured cloud implementations  Resolution Proposed new Resolution from ATIS (GSC15-PLEN-86)

11 Supplementary Slides

12 Service Enabler Packaging Applications Storage and Computing Networks Service Enablers Applications End Users User Service Reuse Resource Service AppAppApp DataDataData ServiceInteraction Subscriber Access & Transport The Service Enablers expose resources (applications, data, and connectivity) through a defined, reusable interface. Service Interaction Management is used to blend service enablers into a business application. End users interact with the business application oblivious of the component parts. User preferences should be separated from the application and included with the user profile.

13 Technology Centric Services are delivered through common transport. The customer experience is fragmented because each service requires a separate login and is in a distinct silo. Data is not shared across applications so the customer must manually input and synchronize preferences, contacts, and other metadata.

14 User Centric Services are delivered through common transport. The user experience is unified by a common SON service enabler, profile, and metadata. Key data is shared across applications. The services work together in a single user experience. UserProfile Presence PIM ServiceInteraction The number of discrete service experiences increase as a factorial function of the service inventory.

15 Common Namespace CentralizedSubscriberDatabase Identity Management Common Preferences Service Specific Preferences Invariant Identity Common Identity Broadband Identity eCommerce Identity Portal Identity IPTV Identity User ID Credential Attributes User ID Credential Attributes User ID Credential Attributes User ID Credential Attributes User ID Credential Attributes Major Functions Schema Representation

16 Globalization – Service Supply Chain  The traditional supply chain integrates raw materials into a finished product that is delivered to a customer. Globalization facilitates multiple suppliers with specialized roles working together in bringing a product to market.  Service supply chains operate in a similar way except there is real time interaction between the suppliers during service invocation.  The ability to manage the service supply chain is a core competency of SON companies.