PT. Telekomunikasi Indonesia, tbk

Contents ActionsTitle & Opening

SDN & NFV Asia 2014

SDN OrchestrationBy Tanto Suratno, Senior Manager IT Business Platform Acqusition

Telkom Indonesia

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.

Public 46.9%

Government 53.1%

Shares : Government 53.1%, Public 46.9% ; Market Cap : IDR 302.4 Tril (USD 24.79 Bil)

http://www.bloomberg.com/quote/TLKM:IJ/chart

Telkom Indonesia Product & Customer Portfolio

Fixed Phone

Fixed

Broadband

WiFi

Full MobilityInterconnection &

International

TrafficNetwork Service

Satellite

Tower

Fixed

Services

Mobile

Services

NW & Infra

Services

Platform

Services

Data Center

& Cloud

E-PaymentBPM

Premise

Integration

Managed Apps &

SI

Digital Life

Ttelecommunication

Iinformation

ProductPortfolio

CustomerPortfolio

Serv

ice

s

Limited Mobility

M2M

E-Logistic

E-Tourism

E-Gov

Ecosystem

Solution

E-Transportation

E-Health

Big

Data

Digital HomeMEmedia

edutainment

Big Data

Digital Advertising

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 CoreOptic

Transport

GPONNMS

GPONNMS

GPONNodes

GPONNodes

MetroNMS

MetroNMS

MetroNodes

MetroNodes

IP CoreNMS

IP Core

Nodes

IP CoreNMS

IP Core

Nodes

Optic Transport

NMS

Optic Transport

Nodes

Service management systems

Service provisioning systems

Networks Nodes

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

The Promise: SDN Network Controller APIs

SDN Network Controller APIs Implementation

Source: http://blogs.cisco.com/datacenter/opendaylight-the-start-of-something-big-for-sdn/

SDN Orchestration Basic

Source: www.convergedigest.com

SDN Applications Use Cases

Source: www.convergedigest.com

Old Fashion IT Ecosystems

legacynetwork

CloudData Center

Service Provisioning Activation

Unified Inventory

OSS

Customer Experience Customer Relationship Mgt.

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.

Next Gennetwork

Service Provisioning Activation

Unified Inventory

How should SDN Orchestration…

?

How should SDN Orchestration…

On DemandFlexible

Converged IT & NetAgile

Efficient

Old Fashion IT Ecosystems

legacynetwork

CloudData Center

Service Provisioning Activation

Unified Inventory

OSS

Customer Experience Customer Relationship Mgt.

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.

Next Gennetwork

Service Provisioning Activation

Unified Inventory

Enabling Cloud Orchestration

legacynetwork

CloudData Center

Service Provisioning Activation

Unified Inventory

OSS

Customer Experience Customer Relationship Mgt.

SOA

Business Application Layer

Business Process (BPM)

Service Orchestration Layer

Operation Support System

Backend Layer

Network & Resources

Layer

VirtualisationMgt.

OpenStack Real time Charging

Billing

Master Data Mgt.

Next Gennetwork

Service Provisioning Activation

Unified Inventory

Cloud Service Composition

legacynetwork

CloudData Center

Service Provisioning Activation

Unified Inventory

OSS

Customer Experience Customer Relationship Mgt.

SOA

Business Application Layer

Business Process (BPM)

Service Orchestration Layer

Operation Support System

Backend Layer

Network & Resources

Layer

VirtualisationMgt.

OpenStack Real time Charging

Billing

Master Data Mgt.

Next Gennetwork

Service Provisioning Activation

Unified Inventory

Virtual Net. & Public Cloud Orchestration

legacynetwork

Next Gennetwork

CloudData Center

Service Provisioning Activation

Unified Inventory

Service Provisioning Activation

Unified Inventory

OSS

Real time Charging

Billing

Master Data Mgt.

Customer Experience Customer Relationship Mgt.

SOA

Business Application Layer

Business Process (BPM)

Service Orchestration Layer

Operation Support System

Backend Layer

Network & Resources

Layer

VirtualisationMgt.

OpenStack

VPublic & Partner

Cloud

SDN Controller and Applications

legacynetwork

Next Gennetwork

CloudData Center

OSS

Real time Charging

Billing

Master Data Mgt.

Customer Experience Customer Relationship Mgt.

SOA

Business Application Layer

Business Process (BPM)

Service Orchestration Layer

Operation Support System

Backend Layer

Network & Resources

Layer

VirtualisationMgt.

OpenStack

VPublic & Partner

Cloud

SDN Apps(Service Prov, Net Mgt.)

SDN Controller

legacynetwork

NFV Implementation

Next Gennetwork

CloudData Center

OSS

Real time Charging

Billing

Master Data Mgt.

Customer Experience Customer Relationship Mgt.

SOA

Business Application Layer

Business Process (BPM)

Service Orchestration Layer

Operation Support System

Backend Layer

Network & Resources

Layer

VirtualisationMgt.

OpenStack

VPublic & Partner

Cloud

SDN Apps(Service Prov, Net Mgt.)

SDN Controller

NFV Implementation

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.

Thank You