How Telkom Indonesia implement SDN & NFV in a view of Orchestration. It has been presented in SDN & NFV Asia 2014, Suntec, 3-4 Dec 2014, Singapaore.

1. SDN & NFV Asia 2014
PT. Telekomunikasi Indonesia, tbk
Title & Opening Contents Actions
SDN Orchestration
By Tanto Suratno, Senior Manager IT Business Platform Acqusition

2. Telkom Indonesia
Shares : Government 53.1%, Public 46.9% ; Market Cap : IDR 302.4 Tril (USD 24.79 Bil)
Telkom Indonesia is listed at
Indonesia Stock Exchange (IDX),
New York Stock Exchange (NYSE),
London Stock Exchange (LSE) and also
Publicly Offering Without Listing (POWL)
in Japan.
Government 53.1%
Public 46.9%
http://www.bloomberg.com/quote/TLKM:IJ/chart

3. Telkom Indonesia Product & Customer Portfolio
ME
Digital Life
Digital Home media
Managed Apps &
BPM
E-Payment
SI
Premise
Integration
Data Center
& Cloud
Fixed Phone
Fixed
Broadband
WiFi
Full Mobility
E-Health
E-Transportation
Interconnection &
International
Traffic
Network Service
Satellite
Tower
Fixed
Services
Mobile
Services
NW & Infra
Services
Platform
Services
I
information
T
telecommunication
Product
Portfolio
Customer
Portfolio
Services
Limited Mobility
M2M
E-Logistic
E-Tourism
E-Gov
Ecosystem
Solution
Big
Data
edutainment
Big Data
Digital Advertising

4. Network operation is very complex and expensive
Network Operation is not adaptably easy to maintain
• Multiple manual configuration actions are needed in core network nodes
• Network solutions from different vendors typically use particularized Network Management
System (NMS) implementations
• Very long service provisioning times
voice Data Internet Cloud SaaS
OSS Provisioning Subsystems
G.PON Metro IP Core
Optic
Transport
GPON
NMS
GPON
NMS
GPON
Nodes
GPON
Nodes
Metro
NMS
Metro
NMS
Metro
Nodes
Metro
Nodes
IP
Core
NMS
IP
Core
Nodes
IP
Core
NMS
IP
Core
Nodes
Optic
Transport
NMS
Optic
Transport
Nodes
Service management systems
Service provisioning systems
Networks Nodes

5. Technically Complex and Geographically Challenging
Network Operation is not adaptably easy to maintain
• Multiple manual configuration actions are needed in core network nodes
• Network solutions from different vendors typically use particularized Network Management
System (NMS) implementations
• Very long service provisioning times

6. The Promise: SDN Network Controller APIs

7. SDN Network Controller APIs Implementation
Source: http://blogs.cisco.com/datacenter/opendaylight-the-start-of-something-big-for-sdn/

8. SDN Orchestration Basic
Source: www.convergedigest.com

9. SDN Applications Use Cases
Source: www.convergedigest.com

10. Old Fashion IT Ecosystems
Customer Experience Customer Relationship Mgt.
legacy
network
Cloud
Data Center
Service
Provisioning
Activation
Unified
Inventory
OSS
SOA
Business Application Layer
Business Process (BPM)
Service Orchestration Layer
Operation Support System
Backend Layer
Network & Resources
Layer
Real time
Charging
Billing
Master
Data
Mgt.
Service
Provisioning
Activation
Unified
Inventory
Next Gen
network

11. How should SDN Orchestration…
?

12. How should SDN Orchestration…
On Demand
Flexible
Converged IT & Net
Agile
Efficient

13. Old Fashion IT Ecosystems
Customer Experience Customer Relationship Mgt.
legacy
network
Cloud
Data Center
Service
Provisioning
Activation
Unified
Inventory
OSS
SOA
Business Application Layer
Business Process (BPM)
Service Orchestration Layer
Operation Support System
Backend Layer
Network & Resources
Layer
Real time
Charging
Billing
Master
Data
Mgt.
Service
Provisioning
Activation
Unified
Inventory
Next Gen
network

14. Enabling Cloud Orchestration
Customer Experience Customer Relationship Mgt.
legacy
network
OpenStack Real time
Cloud
Data Center
Service
Provisioning
Activation
Unified
Inventory
OSS
SOA
Business Application Layer
Business Process (BPM)
Service Orchestration Layer
Operation Support System
Backend Layer
Network & Resources
Layer
Virtualisation
Mgt.
Charging
Billing
Master
Data
Mgt.
Service
Provisioning
Activation
Unified
Inventory
Next Gen
network

15. Cloud Service Composition
Customer Experience Customer Relationship Mgt.
legacy
network
OpenStack Real time
Cloud
Data Center
Service
Provisioning
Activation
Unified
Inventory
OSS
SOA
Business Application Layer
Business Process (BPM)
Service Orchestration Layer
Operation Support System
Backend Layer
Network & Resources
Layer
Virtualisation
Mgt.
Charging
Billing
Master
Data
Mgt.
Service
Provisioning
Activation
Unified
Inventory
Next Gen
network

16. Virtual Net. & Public Cloud Orchestration
Customer Experience Customer Relationship Mgt.
legacy
network
Next Gen
network
OpenStack
Cloud
Data Center
Service
Provisioning
Activation
Unified
Inventory
Service
Provisioning
Activation
Unified
Inventory
OSS
Real time
Charging
Billing
Master
Data
Mgt.
SOA
Business Application Layer
Business Process (BPM)
Service Orchestration Layer
Operation Support System
Backend Layer
Network & Resources
Layer
Virtualisation
Mgt.
V
Public & Partner
Cloud

17. SDN Controller and Applications
Customer Experience Customer Relationship Mgt.
legacy
network
Next Gen
network
OSS
OpenStack
Cloud
Data Center
Real time
Charging
Billing
Master
Data
Mgt.
SOA
Business Application Layer
Business Process (BPM)
Service Orchestration Layer
Operation Support System
Backend Layer
Network & Resources
Layer
Virtualisation
Mgt.
V
Public & Partner
Cloud
SDN Apps
(Service Prov, Net Mgt.)
SDN Controller

18. NFV Implementation
Customer Experience Customer Relationship Mgt.
legacy
network
Next Gen
network
OSS
OpenStack
Cloud
Data Center
Real time
Charging
Billing
Master
Data
Mgt.
SOA
Business Application Layer
Business Process (BPM)
Service Orchestration Layer
Operation Support System
Backend Layer
Network & Resources
Layer
Virtualisation
Mgt.
V
Public & Partner
Cloud
SDN Apps
(Service Prov, Net Mgt.)
SDN Controller
NFV Implementation

19. Orchestration Principles
• Abstraction: On a fundamental level, this principle emphasizes the need
to hide as much of the underlying details
• Decoupling: This principle advocates the creation of a specific type of
relationship within and outside of service boundaries, with a constant
emphasis on reducing ("loosening") dependencies between the services, its
implementation, and its service consumers.
• Autonomy: underlying solution logic needs to have a significant degree
of control over its environment and resources. The principle of Service
Autonomy supports the extent to which other design principles can be
effectively realized in real world production environments by fostering design
characteristics that increase a service's reliability and behavioral
predictability.

20. Thank You