Home | Reports | Technical Documents | Tech-Blog | One-Shot Gallery | Korea ICT News | About Us | List of Contributors | Become a Contributor |  How to Advertise  
Section 5G 4G LTE C-RAN/Fronthaul Gigabit Internet IPTV/Video Streaming IoT SDN/NFV Wi-Fi KT SK Telecom LG U+ Network Protocol Samsung   Korean Vendors
CHANNELS HFRFRONTHAUL NetvisionMPTCP Springwave1588 PTP        


Working to get to the telco cloud
February 14, 2018 | By Prayson Pate @ ADVA (PPate@advaoptical.com)
Online viewer:
Comments (0)

We are pleased to share with you all an interesting article contributed by Prayson Pate.


Prayson Pate

Chief Technology Officer for Ensemble at ADVA Optical Networking


All Articles by Prayson Pate

  How to contribute your article to Netmanias.com !  
  List of Contributors  




We are all moving to the cloud – our apps, our pictures, our entertainment. Telcos are doing the same thing. They want to get the benefits of the cloud. These include low-cost hardware, multi-vendor systems, rapid development and deployment of services, and automation. But getting to the cloud is about more than technology. It’s also about the way we work. In particular, telcos have to change how they roll out new services. They have to move from “waterfall” methods to agile development and DevOps.


What is waterfall development?

Waterfall development refers to a method of sequential steps in a process. A different group handles each step, and departmental boundaries separate these groups. Each step must be completed and pass a “gate” before the next step is started. Because the boundary can become rigid, this handoff is sometimes referred to as “throwing it over the wall.” Below is an example of classic waterfall development, with different colors identifying different functional groups:


Developers have used waterfall and hybrid waterfall development for decades, and there are well-understood methods and tools for supporting it. But it has one big drawback: it takes a long time to get from start to finish. Each of the steps shown above can take months, and the time from start to finish can be years.


The slowness of the process introduces risks:

  • Schedule and cost risk: The longer a project is, the less predictable it becomes with regards to time and cost.
  • Market risk: The market opportunity may be gone by the time the development finishes.
  • Requirements risk: Dynamically evolving requirements create gaps between what is needed and what is built. Without interim feedback, a long development cycle delays resolution of this gap.

New ways of working

Software engineers have devised a family of methods to address the drawbacks of classic waterfall development. The most popular methods are called agile development and DevOps.

  • Agile development converts mega-projects into smaller projects that capture a use case or small set of features. These smaller projects are developed in a multi-disciplinary fashion, ideally including the external suppliers and the end user.
  • DevOps is short for development operations. A DevOps approach unites development and deployment. DevOps sometimes include continuous integration / continuous delivery (CI/CD) to maximize speed and automation. DevOps can take early customer feedback on requirements and implementation and feed it into the development and delivery of technologies and applications.

Here is a comparison of waterfall development with agile development and DevOps.


An example of agile development is shown below:


Source: https://crowdsourcedtesting.com/resources/continuously-improve-agile-development-process/


Telcos can combine agile development and DevOps for some big advantages, including:

  • Shorter and more predictable schedules
  • Reduction of time between identifying a need and delivering a product
  • Closing the gap between the telco and its customers
  • Breaking down the barriers between internal groups
  • Adopting a mindset of continuous improvement
  • Treating customers and suppliers as partners in success

Walking the walk – with our customers

We’re not just talking the talk. At ADVA, we have embraced agile development and DevOps for several years. We have done this with our software, and more unusually, with our hardware developments. As a result, we have accelerated our product development. In addition, we have been able to improve quality by rapidly responding to problems or changes in requirements or markets.


On the software side, we have introduced the notion of “software drops,” which are pre-production versions of the software. These drops are appropriate for demos, proofs of concept, or collaboration with our customer. Most often, these software drops take on the form of agile “minimum viable product” (or feature) content. With early feedback and customer use case alignments, we validate whether the drop captures the correct functionality and correct implementation before we move to a full release. The full release is substantially the same as the sum of iterative software drops, but with the matured documentation and internal DevOps CI/CD processes to meet telco requirements. In other words, the best of both worlds.


The benefits of these new styles are especially significant when working in an advanced area of technology, such as network functions virtualization (NFV). New technology has the promise of benefits, but there are also many unknowns. An agile/DevOps approach empowers immediate development of solutions, rapid identification and feedback of issues, continuous improvement, and customer verification of the value of a solution.


Our telco customers want to make the move from waterfall development to agile development and DevOps. They need suppliers like ADVA that can work with them in this new model. In their race from requirements to deployments, customers are embracing the software drop model and gaining the highest value first.


Change is hard – but worth it

And we are ready and willing to help. We believe that this transition to new ways of working will enable innovation today, and will power the telco cloud of tomorrow.


p.s. - Thanks to my colleague Richard Jenny for his valuable insights.



For more articles by Prayson Pate on Technically Speaking, please see: http://blog.advaoptical.com/en/About/prayson-pate.aspx

Thank you for visiting Netmanias! Please leave your comment if you have a question or suggestion.





Subscribe FREE >>

Currently, 49,000+ subscribed to Netmanias.

  • You can get Netmanias Newsletter

    (New contents, Korea ICT News)

  • You can view all netmanias' contents

  • You can download all netmanias'

    contents in pdf file











Open vs. Proprietary 5G Fronthaul Interface: SK Telecom Case

Published: January 11, 2018










How to contribute articles to Netmanias!

We always welcome contributed articles. Share your expertise and inspire others!






View All (764)
4.5G (1) 5G (76) AI (4) AR (1) ARP (3) AT&T (1) Akamai (1) Authentication (5) Big Data (2) Blockchain (3) C-RAN/Fronthaul (17) CDN (4) CPRI (4) Carrier Ethernet (3) China (1) China Mobile (2) Cisco (1) Cloud (4) CoMP (6) Connected Car (4) DHCP (5) Ericsson (2) FTTH (6) GSLB (1) GiGAtopia (2) Gigabit Internet (19) Google (7) Google Global Cache (3) HLS (5) HSDPA (2) HTTP Adaptive Streaming (5) Handover (1) Huawei (1) IEEE 802.1 (1) IP Routing (7) IPTV (21) IoST (3) IoT (53) KT (40) Korea (19) Korea ICT Market (1) Korea ICT Service (13) Korea ICT Vendor (1) LG U+ (18) LSC (1) LTE (76) LTE-A (16) LTE-B (1) LTE-H (2) LTE-M (3) LTE-U (4) LoRa (7) MPLS (1) MPTCP (3) MWC 2015 (8) NB-IoT (6) Netflix (2) Network Protocol (20) Network Slicing (4) New Radio (8) Nokia (1) OSPF (2) OTT (3) PCRF (1) Platform (2) QoS (3) RCS (3) SD-WAN (15) SDN/NFV (59) SK Broadband (2) SK Telecom (33) Samsung (5) Security (15) Self-Driving (1) Small Cell (2) Spectrum Sharing (2) Switching (6) TAU (2) UHD (5) VR (2) Video Streaming (12) VoLTE (8) VoWiFi (2) Wi-Fi (27) YouTube (6) eICIC (1) eMBMS (1) iBeacon (1) telecoin (1)
Password confirmation
Please enter your registered comment password.