<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nitin Singla on Medium]]></title>
        <description><![CDATA[Stories by Nitin Singla on Medium]]></description>
        <link>https://medium.com/@nitinsingla?source=rss-5af5c9d170bb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*V1N9JTXhttletHU0.</url>
            <title>Stories by Nitin Singla on Medium</title>
            <link>https://medium.com/@nitinsingla?source=rss-5af5c9d170bb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 08:53:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nitinsingla/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Cloud Economic for Telecom Network]]></title>
            <link>https://medium.com/@nitinsingla/cloud-economic-for-telecom-network-78a3b222fea8?source=rss-5af5c9d170bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/78a3b222fea8</guid>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[telecommunication]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[nfv]]></category>
            <dc:creator><![CDATA[Nitin Singla]]></dc:creator>
            <pubDate>Sat, 14 Sep 2019 16:04:02 GMT</pubDate>
            <atom:updated>2019-09-18T11:31:06.345Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Economics for Telecom Network</h3><p>This article is about the economics of the Cloud for Telecom Operators. Cloud Service Providers (CSPs) have invested in the cloud for the last 3–4 years. Many of them have seen no value or savings on capital expenses (CapEx) or operational expenses (OpEx) from cloudification, so decisionmakers are confused about the real benefits of future virtualization technologies like containerization, thin hypervisors, etc. In this article, I will explain how we can realize the benefits of cloud computing. While adopting cloud technology, operators should know the value of cloudification can only be realized with deployment and operational automation, proper utilization of resources using cloud pooling features, and innovation in business processes and products. A few operators — such as Telefonica, Vodafone, and Telenor — have already seen reductions in OpEx of as much as 40% from using the right set of tools for automation. To explore how they’ve done it, I will go through the details of cloud economics and its value realization in two parts:<strong> </strong>the<strong> </strong>Impact of cloudification on CapEx, and on OpEx.</p><h3>Part a) Impact of cloudification on Capex</h3><p>This section can be further divided into two parts: CapEx where virtualization is infeasible, and CapEx where virtualization can reduce costs.</p><h3>Infeasible virtualization</h3><p>To better understand this, let’s start by comparing an operator’s level of expenditure with the possible benefits of virtualization. As we know, operating costs can be broadly divided into CapEx and OpEx. The diagram below presents further divisions of these two types of expenditures. Cloudification or virtualization may not have an impact on all parts of a network. The diagram clearly shows that large segments of network capital are nearly impossible to virtualize. This is particularly true of the civil engineering portions of the network such as poles, holes, conduits, towers, fiber optics, etc. Similarly, the distributed geographic nature of networks means that significant portions of mobile radio access networks (RANs) and fixed-line networks remain hard to pool, which affects the ability to quickly shift resources, optimize CapEx, and affect agility at the physical layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*NezkJg7ySxphddNj80Bang.png" /></figure><p><strong>Note:</strong> percentage values are based on writer experience, and may differ from actual realized figures.</p><p>The second major part of the expenditure is spectrum fees, which see no savings from virtualization. So, whenever CSPs consider the financial value of cloud computing, the non-feasible aspects should be excluded while calculating CapEx reductions.</p><p><em>You may wonder why I mentioned this non-feasible part. It was simply to give you a broad understanding so we can more easily dig into the actual purpose of this paper.</em></p><h3>Reduced CapEx as a result of virtualization</h3><p>Now I will discuss different possibilities for virtualization to reduce CapEx and create new business opportunities. We will focus on how CAPEX can be significantly impacted by equipment virtualization (<em>network functions virtualization</em> — NFV), flows (<em>software-defined networking</em> — SDN) and <em>anything as a service </em>(XaaS). These reductions are not automatic; they require a high degree of automation and network self-optimization to realize the full benefits of cloudification.</p><p>I will try to explain cloud features based on how an operator’s CapEx can be reduced using virtualization. One of the pivotal features of cloud, “flexible capacity allocation,” can dramatically improve CapEx. At the macro level, virtualization delivers significant productivity improvements, but these improvements are closely tied to economies of scale. In telecommunications, most network resources must be sized for peak load, but the average load may be anywhere from 25–50% of peak capacity. If virtualization allows for pooling of capital (NFV and SDN infrastructure) and rapid grooming/optimization, a 50–75% savings may be realized.</p><p><strong>The largest and most viable reductions come from improved hardware utilization. This demands broad-based resource pooling and automated methods to move workloads dynamically. For example, in almost all geographic regions, voice traffic has peak times from 9–10 am and 6–8 pm, while data traffic has peak hours of 9 pm onwards. So, if voice and data virtual network functions (VNFs) — i.e. [virtualized infrastructure managers (VIMs)/virtualized IP multimedia subsystem (vIMS)] and virtual Evolved Packet Core (vEPC) — can be scaled out/in according to traffic and share the same hardware, then this can be a great CapEx reduction for operators. The Ideal scenario for this is a scheduled job or KPI-based scale operations of VNF. In the second phase, the same NFV infrastructure (NFVI) resources can be used from 12–6 am for bill dunning and other scheduled billing jobs; which further reduces hardware CapEx by optimizing usage.</strong></p><p>There may be some challenges in achieving this optimization (VNF requirements from NFVI, VNF capability to scale-up/down smoothly). However, these are not very big challenges, considering almost all telecom applications have been virtualized over the last 3–4 years. Needless to say, no financial benefits can be achieved without these capacity optimizations.</p><h3>Part b): Impact of cloudification on OpEx</h3><p><strong>There is no part of OpEx that doesn’t benefit from virtualization. Some benefits are direct, while others are indirect. I strongly believe there is no business case for reducing OpEx through virtualization if CSPs do not combine it with multi-vendor support, rapid service creation, flexible scaling, reduced maintenance, and a high degree of automation</strong>.</p><p>Virtualization has a great impact on OpEx if automation is implemented efficiently, using Orchestrator and service/NF modeling<strong>. </strong>Automation is critical to everything from innovation, to self-service, to self-healing &amp; scaling, to maximizing network utilization. Automation is about cost, customer satisfaction, enhanced service integrity, and competition. There is <em>nothing </em>more important. The rest are “buzz words”. <em>I will now explain operational features and methodologies which should be used to gain financial benefits from virtualization via automation, including a reduction in OpEx.</em></p><p>Ease of deployment:</p><p><strong>The first, immediate benefit of making virtual functions is that automated creation of VNFs &amp; Flows will dramatically lower OpEx provisioning/fulfillment costs. </strong>VNF onboarding, loading all artifacts associated with a VNF, Network and service configuration data, and dependencies can be executed in no time using the latest cloud development and operations (DevOps) tools. DevOps includes test, configuration, and other operational logic used to onboard the service. To achieve all this, CSPs should deploy management and orchestration (MANO/NFVO) software to get their full benefits. A common MANO with an ability to directly use or easily port various VNF models across various suppliers should be able to instantiate VNF and define and configure associated services, as well as secure and test those services. In summary, with only a MANO that can give multi-vendor support, and which has all functionalities discussed in this paragraph, CSPs can get financial benefits by reducing network deployment costs. Many VNFs today operate as “FAT VMs” with high availability (HA) and lifecycle actions provided by the NF itself, or its proprietary virtual network function manager (VNF-M). CSPs should push vendors to comply with open-source MANO or ONAP to gain the actual benefits of virtualization.</p><h3>Closed loop automation via automated scaling &amp; healing:</h3><p>Automated scaling and healing based on Key Performance Indicators (KPI) threshold breach or any other anomaly in a network is called Closed Loop Automation (CLA). Correct implementation of CLA can significantly reduce operational and maintenance costs. Almost all MANO stacks come with this functionality now, so it’s just a matter of the right implementation.</p><h3>Fast service assurance via catalog-driven services and service orchestration:</h3><p>You need a lot of patience to understand this part of automation because it is a combination of changes to not only technical processes but business processes as well. Not only are telecom networks complex and static, but they are also not designed for agile innovation at all. Virtualization can bring agility while reducing costs, but only with service-based architecture, catalog-driven services, and reuse of components.</p><p>The catalog plays a pivotal role in automation because it links each commercial offering (product) to the services and, ultimately, the resources upon which that product depends. Since those services and resources will, in turn, be managed by lower-level OSS (ex. Software Defined Network controllers, orchestration systems, and existing OSS), the catalog acts as the glue that maintains those critical cross-layer relationships as an order flows from an API or portal, to the various OSS involved in its set-up and configuration. The catalog is also typically the interface for product and service innovation. It supports and guides a user (possibly a product manager) through the process of creating a new product or service by reusing pre-existing and pre-defined building blocks already in the catalog.</p><p>Orchestration is a function. It is not a specific box but, rather, exists everywhere in an architecture distributed across many layers. Orchestration occurs at many layers, from infrastructure (VIM) up through E2E product/service orchestration, distributed across many technological or administrative domains. Orchestration may also be native to a specific technology domain, such as NFV (ETSI MANO), SDN, the RAN, etc.</p><p>The diagram below shows the relationship between the catalog and Orchestrator, and services and resources. The point here is that, in order to get all the benefits of virtualization, operators should design, build, and operate services using a catalog-based approach with maximum re-use of existing blocks. <em>Catalogs should be hierarchical and contain the library of re-usable components. They should also contain, or point to, each component’s management logic and order capture/provisioning parameters. They are, therefore, critical enablers of re-use and agility.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*ahwFz6J3-kqVLnM28yKaqw.png" /></figure><p>Hierarchical catalogs are one of the most central and critical OSS functions. Simply having a “catalog” without the associated principles listed above will not maximize long-term productivity gains. <strong>Properly implemented, catalogs greatly simplify many aspects of operations, from service creation through OSS logic design and order handling.</strong></p><p>The term “hierarchical” refers to the three critical layers that exist within proper catalogs: Products, Services, and Resources (“P/S/R”), and to the way that the layers interrelate. At the top is the Product catalog of commercial offerings including prices, service level agreements (SLA), and other commercial terms. Below that is a catalog of Services. Services are an intermediate layer of building blocks; re-usable components such as a transport segment, a voice-mail account, a streaming music library subscription, or a vFirewall. At the bottom are “Resources” — typically, the physical manifestations of services such as a streaming music cluster or voicemail cluster. Virtual resources, unlike physical ones, maybe created on demand. An important point is that a resource may support many different services, and service may be a component of many different products. This is the process by which reuse occurs.</p><p><em>One of the first migration steps, which can yield significant benefits, is to identify “blocks” of functionality in existing OSS that can be isolated, abstracted as an API, and placed in a repository of reusable services. A best practice is to not rebuild most existing logic (which comes at a high cost and is of questionable value) but to simply encapsulate and expose it, as a service. At the same time, the catalog can reflect this service (whether it is a product offering, a service, or a resource) along with its configurable characteristics (needed from a service order, to complete provisioning). In this way, we avoid re-building logic for legacy products and services but begin to gain loose coupling, reuse, and many of the other benefits we want. Several Tier-1 CSPs have, in fact, already begun to implement such a strategy</em><strong><em>. In this way, we also begin to develop a single, unified environment in which both new technology (SDN, NFV, digital services, etc.) and existing technology and services co-exist and can be combined together — an interim necessity</em></strong><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78a3b222fea8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why every cloud computing specialist should get an AWS certification]]></title>
            <link>https://medium.com/@nitinsingla/why-every-cloud-computing-specialist-should-get-an-aws-certification-43ed49071949?source=rss-5af5c9d170bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/43ed49071949</guid>
            <category><![CDATA[certification]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Nitin Singla]]></dc:creator>
            <pubDate>Wed, 31 Jul 2019 14:43:54 GMT</pubDate>
            <atom:updated>2019-07-31T15:20:50.198Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Amazon Web Services (AWS) knowledge for a cloud architect is just as important as a mastery of Linux for a computer science engineer. AWS not only gives insight into cloud technology, but it’s also a great source of information on how to run web applications. If you’re curious, read on to find out why I’ve become an AWS devotee.</strong></p><p>I was working late into the night when my best friend called me to ask if I knew anything about AWS. He wanted some help in reducing the cost of cloud infrastructure for his business. I had never worked with it, but I did have quite a bit of experience with OpenStack, an open-source cloud computing platform. I was curious about the buzz around AWS, so I said I’d help him out. Initially, I asked another friend who is an AWS expert to help, and we checked our friend’s mobile app requirements to see what exactly he needed in a cloud service provider. With that, we made a summary of what he could do to reduce costs.</p><p>A businessman is never satisfied with their current ROI, so we explored the cost of the same setup on other cloud platforms. We took a look at the other big names in the field: Google Cloud Platform (GCP) and Alibaba Yun. Alibaba was definitely the cheapest, but their available documentation couldn’t answer our most important questions, and we were concerned about service availability in our region of India. So, we went with GCP to test the cost of an alternative platform. We shifted his app infrastructure to GCP within in a week, keeping backups on Amazon S3 cloud and using Amazon’s CloudFront for content delivery.</p><p>Within a few weeks, my friend got a call from Amazon offering 100K in credit if he switched back to AWS. One day after moving back to AWS, the QA team reported that the app was working slowly. Analysis of NGINX logs showed requests were taking 4 seconds in the access log. The team asked us to increase the size of our EC2 instance — our cloud-based computing power. Since I work on OpenStack and know about horizontal and vertical scaling, I understood what they needed. I just didn’t know how to implement it.</p><p>So, like any good professional working with computers and web services would do, I Googled stuff. The first 5 links on the results page were from AWS docs, and they gave me exactly what I needed. The procedure was so smooth and easy to execute. <strong><em>At that point, I fell in love with the AWS platform</em>. </strong>I kept reading, clicking links from one document to another. I was so intrigued, I kept on even after the EC2 upgrade. The documentation was so well-written, so well organized and easy to understand, it became like a book I couldn’t put down. For a few weeks, it was my morning read over coffee<em> and my </em>evening reading before bed. <em>I was hooked. I became a diehard fan and learned so much about how to use the platform. </em><strong>It’s like a new George R. R. Martin book for a fantasy fan — you just can’t put it down.</strong></p><p><em>Maybe the best part about AWS is that you don’t need anyone to teach you</em><strong><em> </em></strong><em>how to use it. Their excellent documentation is more than enough</em><strong><em>.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/213/1*ZXkmOr1p26CzPWeUW3EJHg.png" /></figure><p><strong>What Product companies can learn from AWS: </strong>If you work in a B2B product company, you know how difficult it is for developers to write documentation about their projects. It’s mundane work for a developer, describing how to use it after spending so much time getting it to work. A lot of the time, documentation is written or edited by a documentation team that hasn’t been brought in on meetings, or maybe hasn’t even been around for most of the product development cycle, so they don’t have a strong enough understanding of its features to accurately describe them to an audience largely inexperienced with technical jargon. That’s why documentation is rarely a good part of any product. But it should <em>always </em>be. It’s integral to consumer understanding.</p><blockquote><strong>I think the credit for awesome AWS docs goes to one of Amazon’s </strong><a href="https://aws.amazon.com/blogs/apn/the-5-pillars-of-the-aws-well-architected-framework/">five Product Architect pillars</a><strong>: Operational Excellence. It’s all about creating value for customers. If a company sells a complex product, there’s <em>so much value </em>in comprehensive documentation written in plain language. I think AWS really took that to heart in their development process.</strong></blockquote><p>I’ve been reading about AWS services in my free time, and gradually building a thorough understanding of the AWS architecture. In what seemed like a natural next step, I dived into studying for certification. The exam went really well, and my passion for AWS has only grown. Now I am looking forward to learning more and taking a crack at the professional level of exam.</p><p>Useful links:</p><p><a href="https://aws.amazon.com/blogs/apn/the-5-pillars-of-the-aws-well-architected-framework/">https://aws.amazon.com/blogs/apn/the-5-pillars-of-the-aws-well-architected-framework/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43ed49071949" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Public Cloud or Private Cloud for Telecom]]></title>
            <link>https://medium.com/@nitinsingla/public-cloud-or-private-cloud-for-telecom-21f09d719638?source=rss-5af5c9d170bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/21f09d719638</guid>
            <category><![CDATA[public-cloud]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[virtualization]]></category>
            <category><![CDATA[telecommunication]]></category>
            <category><![CDATA[private-cloud]]></category>
            <dc:creator><![CDATA[Nitin Singla]]></dc:creator>
            <pubDate>Sat, 20 Jul 2019 12:05:46 GMT</pubDate>
            <atom:updated>2019-07-20T12:05:46.251Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is written about the Telecom Service Provider’s vision and roadmap for adopting the different types of cloud enablement and deployment strategy for cost efficiency and TCO ( Total cost of ownership) reduction, shorter time to market and making operations leaner. Cloud enablement use case examples include data center modernization, data center extension, application lifecycle management, and access to services.</p><p>Telecom service providers are both consumers and providers of cloud infrastructure and its services as they consume the cloud infrastructure services to run the IT or telecom applications on their network, and also extend cloud services to small-scale industries for running their applications. It is estimated in the next three years, telecom enterprises and their data center planners need to prepare for a major shift in the workloads that will drive data center expansion to support the increasing workload requirement.</p><p>There are four major data center cloud strategies which Telecom Service Providers are using or wish to adopt in the future. Same depicted in below diagram with different domains of the operator network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*OKseppDRllbtuM7OfFwkVQ.png" /><figcaption><strong>Domains of telecom sector with their cloud adoption stage</strong></figcaption></figure><p>a) <strong>Running Multiple (NFVI/MANO) from multiple vendors with bundled applications software</strong>. As cloud technology started to roll-on, this was the first option used by all vendors to run their application on respective clouds, so currently, it is the most deployed option in the operator’s network. Although OEMs have done customization to NFVI to get maximum performance benefits of hardware with new features of container management, SDN integration in NFVI, however applications and NFVI are tightly coupled to supplied hardware by OEM.</p><p>Managing multiple hardware supply chain has been a pain for SPs as they are bound to buy and deploy multiple cloud platforms under this option. In addition, there are other project execution issues which they have to face. For example, one vendor arrange hardware within a week and others could not do it for a month, it adds an unnecessary delay in overall project execution when it has hardware from both vendors. Needless to say, resource competence is another challenge to manage different types of hardware and NFVI platforms. Either they have to hire multiple vendor resources or hire an SI company to manage multiple cloud environments which is always costlier than other options being discussed later.</p><p>On NFVI market share, since NFVI and application are sold bundled, it’s market is directly proportional to the market share of the respective application. If Cisco has 30% market share of vEPC, so they have the almost same share of NFVI in the vEPC domain. <em>This option is most profitable for incumbent OEM vendors ( Ericsson, Huawei, Nokia, and others) due to large profits from hardware, but due to operator inclination towards other deployment strategies, profits are getting a hit apparently.</em></p><p>b) <strong>Common NFVI and MANO from single OEM to run multiple application</strong>. This is the best strategy for operators who wants to reduce the cost, but don’t want to invest in their own development centers. They can choose one common NFVI platform from a single vendor based on features, price, standard compliance and run different network applications on it. This will help to reduce expenditure by giving bulk orders with higher discounts from one vendor’s NFVI hardware and software. It has other advantages too of shorter time to market, reduced maintenance, less supply chain issues, etc. This is easily achievable for a Service provider by arranging a lab of decided vendor NFVI and to test application from multiple vendors. Many operators are trying this option which gives benefits of cost reduction and shorter time to market.</p><p><strong>HP and Dell are leaders for supplying hardware orders. MANO vendors like VMware-vCloud Director, Nokia-CBND, IBM-ALM are trying to get orders for common orchestrator ( MANO).</strong></p><p>c) <strong>Inhouse development of NFVI and MANO using X86 and open-source software:</strong> the Third option which is being tried by few Tier-1 operators like AT&amp;T(US), JIO ( India), Rakuten ( Japan) are developing their inhouse NFVI and MANO. This results in a range of approaches, from using ODMs for building one’s own systems to leveraging open source components for container and microservices. In either scenario, the SPs are procuring processors (often with specific customizations) directly from Intel or its competitors, storage capacity directly from HDD and SSD manufacturers, and next-generation network technologies (e.g., 25/50GbE, 100GbE, and 400GbE) from network component and ODM suppliers. AT&amp;T is using Kubernetes and OpenStack infrastructure rather than VMware to provide greater flexibility and agility to support AT&amp;T’s 5G network.</p><p><strong>The O-RAN Alliance</strong>, founded by AT&amp;T, China Mobile, DT, NTT Docomo, and Orange, recently gained new members, including Verizon, Ericsson, Reliance Jio and TIM. The O-RAN Alliance is focused on evolving radio access networks to make them more intelligent and open, including by leveraging real-time analytics, machine learning systems, and AI. <em>Costs to deploy white-box hardware are significantly lower than deploying proprietary hardware, which will help operators realize savings not only on the hardware itself but also on the implementation and support of the hardware.</em> Reduced complexity of installation and support is a key reason why the white box is less costly to deploy compared to proprietary systems. <strong>Rakuten estimates the cost to be around 50% lower when compared with a network using traditional architecture.</strong></p><p>Off course there is no doubt on the requirement of competent RnD resources to run this option. But investing in this can bring revolutionary future results for operators. This is possible that Tier-1 operator will become a competition to existing OEMs after developing their own RnD centers. <em>Acquisition of Radisys by JIO, Pjazr by JMA Wireless are recent steps towards in this direction.</em></p><p>d) Last but not least strategy is moving the application on public cloud and making <strong>Hybrid cloud for Telecom Infrastructure</strong>. Hybrid cloud solutions are designed to modernize on-premises data centers via access to public cloud services behind the firewall. Specific solutions aim to provide integrated access to private and public cloud environments while easing workload migration between both environments. This option is just taking feet of ground, however, the companies like AWS, VMware, Google are showing great interest to enter this arena with their matured and advanced cloud platforms.</p><p>Small OEMs are doing collaborations with public cloud providers to offer cheaper and feature enriched applications to SPs. Major advancements, in this case, are <em>Optiva BSS launch on GCP</em> ( Google cloud platform), <em>MyCom OSI</em> and <em>Affirmed Networks</em> <em>vEPC</em> launch with AWS. Major ice-breaker would be recent collaboration among ‘Vmware’ and ‘AWS’ which will give high-end private cloud services with most advanced containerized services access of AWS. AWS is very soon launching service OutPost too which is on-Prem AWS cloud. <strong>I think AWS could be a great challenge to incumbent OEM players and I will talk about its details in coming articles.</strong></p><p>This option with a combination of option-c where SPs are trying to use x86 hardware will be most modernized and futuristic data center extension approach. It is highly cost-optimized, flexible, cloud-native and in open-source direction. Network functions traditionally run on purpose-built network appliances will increasingly shift to x86-based hardware, which will house and provision VNFs. Public Cloud providers being expert of scalable, elastic and cheap storage, ML/AI solutions will add-on to reduce cost and fast delivery. Apparently, this is going to be future of Telecom Infrastructure.</p><p><strong>Summary:</strong> In my view Service Providers should move from option-a to any of b-d to bring TCO reduction, bringing uniformity of NFVI platforms, lean operations, faster time to market. The mix of option c and d should be adopted as soon as possible by them. <strong><em>Needless to say, incumbent OEM like Amdocs, Nokia, Huawei, Cisco, Ericsson who have more than 1B$/per quarter revenue from Telecom Infrastructure servicesˠ will get a hit by this change. </em></strong>The disaggregation of hardware and software threatens historical profit pools and forces incumbent vendors to invest in transitioning their businesses to support Everything as a Service (XaaS) and other business models, such as pay as you grow, which in many cases require scale and long duration before attaining profitability. <strong><em>They should carefully balance their shift from the old world to the new reality,</em></strong> whereby hardware upgrades are smaller in scale and targeted, and innovation migrates to the software layer. Companies such as Cisco, Juniper, Nokia, and Ericsson are becoming software-centric, though they are doing so gradually as this trend will take years to fully play out. <strong>Off course, SI companies like TechM, Wipro, Infosys, Capgemini will be benefited due to this change as scope of system integrators will increase year on year.</strong></p><p><strong>Appendix:</strong></p><p><strong>NFVI:</strong> Network functions virtualization infrastructure (NFVI) includes hardware (predominantly data center equipment such as servers and storage) and close-to-the-box software such as operating systems and infrastructure management platforms that compose the physical layer on which VNFs are housed.</p><p><strong>VNF:</strong> In a Network Functions Virtualization architecture, a virtualized network function, or VNF, is responsible for handling specific network functions that run in one or more virtual machines on top of the hardware networking infrastructure, which can include routers, switches, servers, cloud computing systems and more.</p><p><strong>MANO</strong>: Software platforms that manage and orchestrate network resources in a virtualized environment; management and orchestration (MANO) leverages automation and is responsible for policy management.</p><p><strong>SDN:</strong> Software-defined networking (SDN) is an approach to networking in which control is decoupled from the physical infrastructure, allowing network administrators to support a network fabric across multivendor equipment.</p><p>ˠ <strong>Telecom Infrastructure Services include</strong> all Capex and Opex by service providers (wireless, wireline, cable, satellite and cloud operators) on or related to communications and IT infrastructure. four main segments: Deployment Services, Maintenance Services, Professional Services, and Managed Services.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21f09d719638" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>