Your SlideShare is downloading. ×
Evolving from Legacy SDH to Packet Transport Network
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Evolving from Legacy SDH to Packet Transport Network

1,583
views

Published on

Presented on Optical Transport Vision APAC, 19-21 October 2009 @ Suntec City, Singapore

Presented on Optical Transport Vision APAC, 19-21 October 2009 @ Suntec City, Singapore


0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,583
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Case Study: Evolving from Legacy SDH to Packet Transport Network Arief Hamdani Gunawan Senior Officer TELKOM INDONESIA Singapore 19th – 21st October 2009
  • 2. AGENDA Current Condition •Existing Domestic Backbone •The Legacy SDH Facing The Broadband and Interconnectivity •Broadband Configuration and Challenges •Palapa Ring Preparing for Future •Evolving Towards NGN •Architecture 2014: DWDM, 1GB, 10GB and Tera Router Singapore 19th – 21st October 2009
  • 3. The Legacy SDH signal levels and physical layer data rates • The SDH signal structures are very similar to SONET, with the difference that SDH does not have an equivalent for STS-1.Instead, it starts from the equivalent of STS-3, or 155.52 Mbps. • In SDH, such a signal would be called a synchronous transport module level 1, or STM-1 signal.
  • 4. Existing Domestic Backbone TELKOM INDONESIA to Asia Pacific to India EXCELCOMINDO INDONESIA COMNET PLUS Sabang to Thailand Kalimantan Banda Aceh INDOSAT SMW о Meulaboh Tapaktuanо Medan Tarakan Tobelo о о Singkawang о Sulawesi Toli-toli Sibolga о Manado o Batam о о Manokwari Padang о о о о Samarinda Gorontalo Biak Natal Pontianak о о Balikpapan Paluо o о о о Salaw o o Bengkulu Palembang o ati о о Palopo Luwuk o о о o Kendari o Belitung o Nabire о Sampit o Jakarta Banjarmasin о о AmbonTual Cirebon Ujungpandang Kalianda о Semarang o o Dobo о Maumere Reo Surabaya о Larantuka о о Gilimanuk o o o оо о о о о о о о Saumlaki Kalabahi Sumatera Ketapang Karangasem o о Atambua Merauke Mataram Kupang Maluku - Irian Sumbawa Waingapu Jawa Nusa Tenggara to Perth, Australia
  • 5. Part of Existing Domestic Backbone (Telkom Indonesia) (2000) Surabaya – Banjarmasin – Makassar 2.088 Km (2000) Trans Java 2.605 Km (2004) Jakarta – Medan – Batam 2.990 Km (2004) Batam – Singapore – Bangkok 1.043 Km (2005) Dumai – Malaka 161 Km (2005) Banjarmasin – Balikpapan 955 Km (2005) Makasar – Palu 974 Km TOTAL 10.816 Km
  • 6. AGENDA Current Condition •Existing Domestic Backbone •The Legacy SDH Facing The Broadband and Interconnectivity •Broadband Configuration and Challenges •Palapa Ring Preparing for Future •Evolving Towards NGN •Architecture 2014: DWDM, 1GB, 10GB and Tera Router Singapore 19th – 21st October 2009
  • 7. Broadband Configuration
  • 8. Broadband Challenges • Optical Packet Backbone (OPB) – Optical Backbone (Include ): National Consortium – Tera Router – Core Router • Optical Packet Metro – Metro Ethernet – Selected DWDM Regional Plan • Access – Metro – DSL – MSAN – WiMAX
  • 9. • Palapa Ring is the project to design, build, self finance and operate the national fiber optic backbone network in Indonesia. • Consisting of several groups of fiber optic around specific islands/groups of islands ,1 national ring connecting all rings, reaching 440 districts and cities. • Main backbone for all telecommunications operators • Phase I : Build in the eastern part of Indonesia • Phase II : Integrated with the existing western backbone network and build new extension network to reach unserved cities
  • 10. Basic Design • Ring Configuration • Landing Point : 15 Terminal Stations through 21 of District • Length Cable : 4,450 Km – Inland Cable 3.850 km – Submarines Cable 600 km • Cable system – 2 pairs for Repeater system – 12 pairs for inland and Repeater-less system • Capacity : 7λ (~ 70 Gbps) – Upgradeable to 16 λ (~ 160 Gbps)
  • 11. Section#1: 2.513,8 km Current Configuration of Palapa Ring Project : Bitung - 1.1 Land: Manado - Bitung 1.2 SubRL Ternate 1.3 SubR: Ternate – Sorong 1.4 SubR: Sorong - Ambon 1.5 SubR: Ambon - Kendari Investment Cost (after crisis) Section#2: 1.937,1 km US$ 180,4 million 2.1 SubRL: Mataram –KawindaNae 2.2 SubRL: KawindaNae – Raba 2.3 SubRL: Raba – Waingapu 2.4 SubRL: Waingapu – Ende 2.5 SubRL: Ende – Kupang 2.6 Land: Kendari – Kolaka 2.7 SubRL: Kolaka – Watampone 2.8 Land: Watampone – Bulukumba 2.9 Land: Bulukumba - Makasar
  • 12. AGENDA Current Condition •Existing Domestic Backbone •The Legacy SDH Facing The Broadband and Interconnectivity •Broadband Configuration and Challenges •Palapa Ring Preparing for Future •Evolving Towards NGN •Architecture 2014: DWDM, 1GB, 10GB and Tera Router Singapore 19th – 21st October 2009
  • 13. Evolving Towards NGN
  • 14. Architecture 2014
  • 15. Metro Ethernet 1 Gbps Gigabit Ethernet physical layer specification
  • 16. Metro Ethernet 10 Gbps 10G Ethernet physical layer specification
  • 17. Tera Router: IP Optical Vision Tera Router is the technology to fulfill the requirements as following: • To accommodate 10 Gbps Ethernet traffic from edge network • To accommodate the growth of Terabit traffic projection in the backbone network • To provide simply architecture 40 Gbps and more for IP Traffic and Optical Network Integration trough the implementation of IP over Lambda technology • To provide seamless integration with existing MPLS core and edge network
  • 18. Selected DWDM Regional Plan Driver Factors: • Capacity Expansion • IP Traffic • Protection • New Service (Data Service & Triple Play)
  • 19. Thank You Arief Hamdani Gunawan hamdani2@telkom.co.id

×