Date post: | 27-Mar-2015 |
Category: |
Documents |
Upload: | diego-howe |
View: | 212 times |
Download: | 0 times |
A tale of two worldsManaging Convergence of Web and Mobility DEP
Dave Milham
TMF Distinguished Fellow
BT Group CTO Office
© British Telecommunications plc
Two Worlds
Networked IT MMS Communications
IMS
© British Telecommunications plc
What is the Vision?
• Web 2.0– Webs Services combined to give innovative new services– Web’ Mash Up’ E.g. Google Earth API– Dynamic service provision
• IMS– New Applications assembled from Service Components– Access to Network based information in real time– Presence and Location– Agile new services
Aren’t these both different views ofService Oriented Architecture?
© British Telecommunications plc
What’s the differences?
• Web2.0– Comes from a ‘free’ web mind set– Revenue from eyeballs, mouse clicks and advertisements– Some how somebody will create something ‘cool’
e.g. YouTube, MySpaces, Google Earth
• IMS– Comes from a Telecom Billing mind set– Charge for content, application and session– Don’t know what the ‘killer app is’ but let’s provide a
framework– Managed Service Quality
© British Telecommunications plc
What do both need?
• Component Based framework
• Managed QoS
• Distribution of income through a supply chain
© British Telecommunications plc
Component Based Framework
Food Now@net
Content Aggregator
MVNO
7-10Food chain
Ethnic Food
Facilities Mobile N/W
Operator
Exposed Service
Revenue
x$
v$ n$m$
e$
SLA
SLA
SLA
SLA
SLASLA
And these relationships are being changed dynamically!
© British Telecommunications plc
(NGOSS) Component/
Service
NGOSSBusiness Aware Contracts (BAC)
e.g. OperationalServicesConfigure DirectoryEntry
Exposed NGOSS Framework Aware Contract Servicese.g. process, policy, data management,systems management
ConsumedNGOSS Contracts
What do components consist of?
DirectoryLookupQuery
© British Telecommunications plc
And what else?
• TMF O53D NGOSS metamodel
• Configuration Management
• Service Assembly Model based on SID…
© British Telecommunications plc
Product – Service – Resource
ProductComponent
ResourceService
LogicalResourceResourceFacingService
0..1 1..n0..1 1..n
LogicalResourcesImplementRFS
ProductBundle
CustomerFacingService
0..n1..n 0..n1..n
CFServiceRequiresRFServices
PhysicalResource
0..n0..n 0..n0..n
PResourceSupportsLResource
0..1 1..n0..1 1..n
PhysicalResourcesHostRFS
Product
0..n0..n 0..n
ProductReferences
0..n
0..1
0..n
0..1
0..n
ProductBundleComprisedOf
0..n
0..1
0..n
0..1
ProductHasCustomerFacingServices
0..n
0..1
0..n
0..1
ProductHasPhysicalResources
Services and Resources are delivered through Products
© British Telecommunications plc
Summary
• Many of the technical challenges for Web2.0 and IMS are the same
• Web2.0 and IMS different sides of the same coin? • Both need
– Component based Service Model– Meta-models– SLA Models– Service assembly model
• SID Models
– Supply chain models– Configuration Management
• How will this happen?
© British Telecommunications plc