+ All Categories
Home > Technology > Processes and Telecom APIs

Processes and Telecom APIs

Date post: 29-Nov-2014
Category:
Upload: alan-quayle
View: 614 times
Download: 1 times
Share this document with a friend
Description:
Review of some of the structural issues impacting the industries competitiveness with some Game of Thrones quotes. The a review of the technologies and processes we can copy for API processes across Simplicity, Security, Governance, Certification, Architecture, Process Automation, and Service Management Interface. And wrapping up on the major process gap on go-to-market and the work of TADSummit to address that on 12-13 November, www.tadsummit.com
Popular Tags:
43
Telecom API Processes Wednesday 8 th October 2014
Transcript
Page 1: Processes and Telecom APIs

Telecom API Processes

Wednesday 8th October 2014

Page 2: Processes and Telecom APIs

What is an API?

•  http://www.telco.com/api.php?action=remove_friction

APIs reduce business friction by making it easy for software systems to work together using existing well understood web technology that any IT person can understand

Page 3: Processes and Telecom APIs
Page 4: Processes and Telecom APIs
Page 5: Processes and Telecom APIs
Page 6: Processes and Telecom APIs
Page 7: Processes and Telecom APIs
Page 8: Processes and Telecom APIs

Diameter signaling is dark and full of terrors. The Lord of Light must consume all standards engineers.

Page 9: Processes and Telecom APIs

VoLTE interop is dark and full of terrors. The Lord of Light must consume all standards engineers.

Page 10: Processes and Telecom APIs

RCS is dark and full of terrors. The Lord of Light must consume all standards engineers.

Page 11: Processes and Telecom APIs
Page 12: Processes and Telecom APIs

There is nothing new under the sun. So let’s see if this problem has already been solved.

Page 13: Processes and Telecom APIs
Page 14: Processes and Telecom APIs

Copy what’s already there and working

•  Simple REST JSON

•  Security OAuth

•  Governance RBAC

•  Certification

•  Architecture SOA

•  Process Automation

•  Service Management Interface

Page 15: Processes and Telecom APIs
Page 16: Processes and Telecom APIs
Page 17: Processes and Telecom APIs

Copy what’s already there and working

•  Simple REST JSON

•  Security OAuth

•  Governance RBAC

•  Certification

•  Architecture SOA

•  Process Automation

•  Service Management Interface

Page 18: Processes and Telecom APIs
Page 19: Processes and Telecom APIs

Hybrid Enterprise Resources Applications

Users / Admin

(Product Groups)

Page 20: Processes and Telecom APIs
Page 21: Processes and Telecom APIs

Copy what’s already there and working

•  Simple REST JSON

•  Security OAuth

•  Governance RBAC

•  Certification

•  Architecture SOA

•  Process Automation

•  Service Management Interface

Page 22: Processes and Telecom APIs
Page 23: Processes and Telecom APIs

Copy what’s already there and working

•  Simple REST JSON

•  Security OAuth

•  Governance RBAC

•  Certification

•  Architecture SOA

•  Process Automation

•  Service Management Interface

Page 24: Processes and Telecom APIs
Page 25: Processes and Telecom APIs

Copy what’s already there and working

•  Simple REST JSON

•  Security OAuth

•  Governance RBAC

•  Certification

•  Architecture SOA

•  Process Automation

•  Service Management Interface

Page 26: Processes and Telecom APIs

Amazon 2002

•  1) All teams will henceforth expose their data and functionality through service interfaces.

•  2) Teams must communicate with each other through these interfaces. •  3) There will be no other form of interprocess communication allowed: no direct

linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.

•  4) It doesn’t matter what technology they use. HTTP, Corba, Pubsub, custom protocols — doesn’t matter. Bezos doesn’t care.

•  5) All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.

•  6) Anyone who doesn’t do this will be fired.

Page 27: Processes and Telecom APIs

Copy what’s already there and working

•  Simple REST JSON

•  Security OAuth

•  Governance RBAC

•  Certification

•  Architecture SOA

•  Process Automation

•  Service Management Interface

Page 28: Processes and Telecom APIs
Page 29: Processes and Telecom APIs
Page 30: Processes and Telecom APIs
Page 31: Processes and Telecom APIs

Defining what is meant by Telecom App Developer R

even

ue

Product

Internal Telco Developers

Partner Developers

Telecom App Developers

Mobile App Developers

Long Tail Developers

Page 32: Processes and Telecom APIs

This Is A More Accurate Representation R

even

ue

Product

Internal Telco Developers

Partner Developers

Telecom App Developers

Mobile App Developers

Long Tail Developers

Page 33: Processes and Telecom APIs

DIY versus Partner R

even

ue

Product

DIY

Partners

Customers

Page 34: Processes and Telecom APIs

Customers

Services

Page 35: Processes and Telecom APIs

“Most men would rather deny a hard truth than face it.”

Page 36: Processes and Telecom APIs

Make Telecoms an Essential Spice for every Business Recipe

Page 37: Processes and Telecom APIs

Uber Revolution

Page 38: Processes and Telecom APIs

Communications is Core to On-demand Services

Page 38

Page 39: Processes and Telecom APIs

Do more VAS!

Page 40: Processes and Telecom APIs

Go-to-Market is Critical, and a Critical Telco Value

Customers

Selling Services

Selling Capabilities

Internal

Partners

External

Telco

Telco GTM

This is the biggest process gap we face

Page 41: Processes and Telecom APIs

$100B Ecosystem!

Page 42: Processes and Telecom APIs

Grassroots of the Industry

Page 43: Processes and Telecom APIs

Now for Some Group Therapy


Recommended