The opportunities of network-as-a-service
Enabling network-as-a-service (NaaS) functionality is becoming an important capability for many CSPs as they map out their future technology and services roadmaps. Raj Yavatkar, CTO of Juniper Networks, explains why operators should consider a NaaS model, given that the industry is going through a deep transformation with cloud, edge computing and more distributed workforces and applications. But how close are we to achieving NaaS capabilities and what key activities are taking place now in terms of this technology?
You’ll learn
How NaaS has evolved
Why operators should consider adopting an NaaS model
Who is this for?
Host
Guest speakers
Transcript
0:03 foreign
0:08 Telecom TV I'm Guy Daniels director of
0:11 content
0:12 enabling Network as a service
0:14 functionality is becoming an important
0:16 capability for many csps as they map out
0:19 their future technology and services
0:21 roadmaps we're here to discuss the
0:23 potential value of Nars 2 operators is
0:26 Raj yaveka who is Chief technology
0:29 officer for Juniper Networks hello Raj
0:32 very good to see you now as we know
0:34 there are many different views and
0:36 definitions of network as a service so
0:39 how do you define US
0:42 that's a very good question I think I
0:45 just want to give you some history of
0:47 how the network as a service came about
0:49 it really started with software defined
0:52 networking as a principle where people
0:54 wanted to centralize a control plane to
0:58 configure a layer to their three
0:59 switches then it evolved to what we call
1:02 SD band as a service today where we went
1:04 away from circuits to more providing a
1:06 tunnels On Demand right and then sassy
1:09 is adding security to that that's how
1:12 the network as a service has evolved and
1:15 it has been now considered equivalent to
1:18 pay as you go service but that is not
1:20 sufficient because at the same time the
1:22 last few years networking has evolved
1:24 rapidly because of the hyperscalers
1:27 providing public Cloud so you have
1:29 public Cloud they have VPC networking
1:31 within public Cloud you have Edge Cloud
1:33 you have Metro or van you have on-prem
1:38 both virtual oral networking and
1:40 physical networking then of course you
1:42 have private 5G Wi-Fi and so on so
1:45 really if you want to consider Network
1:46 as a service you have to consider it
1:48 across all these domains
1:50 so I look at Network as a service
1:54 as a on-demand creation and termination
1:57 of end-to-end networks across all these
2:00 domains in minutes with security
2:03 functions enabled and with proper
2:07 performance isolation and security
2:09 isolation
2:10 thanks Raj now as you explained there
2:13 the industry is going through this this
2:15 Evolution this deep transformation with
2:17 Cloud Edge Computing and more
2:19 distributed workforces and applications
2:22 why therefore should operators consider
2:25 adopting a network as a service model
2:28 I think that's a very uh good point
2:31 right because if you look at Enterprises
2:33 due to public Cloud first of all they're
2:35 getting used to this consumption-based
2:37 module
2:38 right as you said we are going to a big
2:42 transformation with distributed
2:43 Workforce people come and go they join
2:45 the networks and go they are no longer
2:46 sitting in offices you have distributed
2:49 applications SAS Transformations all of
2:52 those if you look at it the Enterprises
2:54 are looking at the public Cloud as a
2:55 model where the network whether in the
2:58 VPC inter VPC connecting to the cloud
3:00 it's all software driven it's all
3:03 virtual it's API driven they expect the
3:06 same model to be enabled across all the
3:09 domains they have to deal with it may be
3:12 Wi-Fi it could be private 5G it could be
3:14 on-prem data center networking it could
3:16 be Cloud connectivity and so on so
3:18 that's number one number two I think
3:23 um if you look at it from operatives
3:25 perspective this is a opportunity for
3:27 them to create new sources of soft
3:29 Revenue
3:31 because today they are getting more and
3:33 more relegated to be bit pipe providers
3:36 if you can enable such Services
3:39 on-demand Services across these domains
3:42 you can start monetizing
3:44 and that's a consumption-based model is
3:46 software driven but underlying physical
3:48 infrastructure continues to play an
3:50 important role to enable that
3:54 finally The Operators also have to be
3:56 very much aware of the fact that
3:58 hyperscalers are moving closer and
4:00 closer to the edge of the network
4:02 and closer to the Enterprises
4:05 so if you want to continue to be
4:07 relevant you have to provide services on
4:12 part with hyperscalers to the
4:13 Enterprises so they continue to be your
4:15 customers and this is very important in
4:17 the context of what has happened if you
4:19 look at it from nvnos perspective
4:22 The Operators already enabled mvno as a
4:26 model to allow virtual end-to-end
4:28 Network to be residing on top of the
4:30 physical Network so any third party
4:32 could provide a virtual network service
4:34 but that is not sufficient because
4:36 that's still going back to providing
4:38 only bit pipes
4:40 what network as a service enables or
4:42 allows operators to do to really offer
4:45 value-added services based on security
4:47 isolation performance acceleration using
4:50 end-to-end slicing so that they can
4:53 start
4:54 generating revenues from Enterprises for
4:57 different types of services
5:00 Raj this is all very encouraging news
5:02 but how far are we from achieving
5:04 Network as a service and what are the
5:07 key activities happening now around this
5:09 technology that's a very good question I
5:12 think we are evolving we are not dead
5:15 yet but we have made a very good start
5:17 so for example Beyond sassy and his
5:20 demand which are really truly a network
5:22 as a service being delivered today right
5:24 people are beginning to look at
5:26 extending that model to Edge cloud
5:30 to the kubernetes based Overland
5:32 networks both in Cloud as well as
5:34 on-prem to Wi-Fi and so on so I think
5:38 there are multiple efforts such as an
5:40 industry standardization such as nepheo
5:43 Encore
5:44 which is age multi-cloud orchestration
5:47 project in Linux Foundation uh you have
5:49 kubernetes based networking which allows
5:51 you to really
5:53 automate uh intent driven configuration
5:56 and operation of the networks so those
5:59 are the new developments which are
6:00 happening in different domains the
6:03 problem is that each of these domains is
6:04 being addressed in isolated values
6:07 this is where an opportunity is there to
6:09 really Define Network as a service which
6:12 is uniformly defined API driven across
6:15 all these domains starting from 5G Edge
6:18 Metro Cloud as well as on
6:22 and what are the market opportunities
6:24 for operators and why are you and
6:27 Juniper excited about its future
6:31 so operators are very important part of
6:34 our customer just like hyperscalers are
6:36 big customers of ours operators
6:38 traditionally have been a big customers
6:40 with delivered products and services to
6:42 them and we look at this as an
6:44 opportunity for operators to continue to
6:46 evolve and take advantage of the market
6:48 transformations
6:50 we are excited about it because we have
6:53 this strategy to deliver what we call
6:57 client to Cloud secure Azure networks
7:01 which is cloud managed AI Ops driven
7:04 and we started with missed Wi-Fi
7:07 right where we it's a cloud managed apps
7:10 driven assured service we extended that
7:13 to campus and Branch networks and access
7:15 networks now we are extending that to
7:17 Cloud Metro and data center and private
7:20 5G and 5G
7:22 when you do that I think you start
7:24 defining a uniform architecture uniform
7:27 platform client to Cloud which is API
7:31 driven which allows you to abstract out
7:33 Network as a service no matter which
7:35 domain you are in
7:36 delivering on
7:38 Enterprises get to see it as a client to
7:40 Cloud Model so they can now start
7:43 consuming Services across all these
7:45 topics without having to worry about
7:47 they get security they get that
7:49 performance Assurance but also they get
7:52 On Demand creation and termination of
7:55 networks so we are excited that we can
7:56 enable our customers operators to start
7:59 delivering the services in a uniform
8:01 manner
8:02 now for mobile service providers that
8:05 already deliver Services via the cloud
8:07 how is this Evolution different for the
8:10 mobile service operators is important to
8:12 understand that they have not just think
8:14 about the mobile networks or radio
8:16 Access Network
8:17 they have to start thinking about their
8:19 applications their end users are using
8:22 applications Enterprises are using
8:23 application which are client to Cloud
8:25 they go across all these domains so the
8:28 concept of slicing has to be now end to
8:31 end because if you can create the slices
8:33 of the networks on demand and deliver
8:35 services using that you can protect the
8:38 traffic you can provide
8:39 satisfy use cases that we have not
8:42 thought for example an Enterprise might
8:45 say or some network provider might say I
8:48 want to create a network end-to-end
8:51 network which is isolated from the
8:53 production environment so that I can try
8:55 out new security functionality you have
8:57 to be able to do that you have to be
8:59 able to do end-to-end networks which are
9:01 specific to a particular application
9:03 so that you can isolate that application
9:05 from other applications other traffic
9:08 those kind of possibilities have to be
9:10 considered not just in the context of
9:12 mobile network but across the domains
9:16 because applications are distributed use
9:19 cases are distributed and requirements
9:21 are distribute
9:22 that's msps but why should Enterprises
9:26 also be excited
9:29 I think the Enterprises have to be
9:30 excited because as I said earlier at the
9:33 beginning right you have distributed
9:35 Workforce you have distributed
9:37 applications with SAS Transformations
9:39 increasingly use up the cloud either
9:41 with public Cloud Edge cloud or even
9:44 on-prem Cloud across all these things
9:46 the old model of I submitted ticket and
9:50 debate for services to be enabled does
9:52 not work you will want more API driven
9:55 virtual network software driven
9:57 networking even though underlying
9:59 infrastructure still has to be supported
10:00 in physical appliances given that
10:03 enterprises now can ask for
10:07 such on demand pay-as-you-go model where
10:11 you do you are able to add a new
10:14 Workforce if you have a employee who
10:17 moves from one place to another but
10:19 still wants to connect to the network
10:20 all those connectivities should be
10:22 enabled on demand very easily and
10:25 they're getting used to that using the
10:27 public clouds so they expect that model
10:29 to be extended everywhere and that's why
10:31 I think Enterprises are excited about
10:33 this ability to consume networks in a
10:36 uniform manner Cloud to a client to
10:38 cloud and in Azure map
10:40 well final question Raj for operators
10:43 that want to explore this journey where
10:45 do you recommend that they start
10:47 that's the excellent question I think we
10:49 have multiple of these initiatives and
10:52 they need to start looking at it as a
10:54 end-to-end problem
10:56 which means think of a uniform platform
10:58 layer that abstracts out underlying
11:01 connectivity no matter where you're an
11:03 edge Cloud you are in public Cloud you
11:06 are in a Metro or on-prem and Sumo if
11:09 you can think of that uniform platform
11:12 layer that exposes apis by the way 3gp
11:15 recently announced that they are going
11:17 to create such a service creation model
11:18 agile on demand using a uniform platform
11:22 layer but that's for the mobile networks
11:24 I'm saying do that across the all of
11:27 these domains you can use kubernetes as
11:29 a very good foundation for that because
11:31 it provides this intent driven
11:33 configuration automation deployment
11:35 automation some of the industry
11:38 initiatives such as nephew MCO and
11:40 kubernetes itself are very much ripe to
11:44 be exploited so operators should start
11:46 from that but take the end-to-end view
11:48 and take advantage of slicing you are
11:51 looking at doing slicing if you look at
11:53 mvno that's a very primitive model for
11:57 providing overlay Network to a customer
12:00 from the operator right it doesn't do
12:03 much but if you combine that kind of
12:05 model with end-to-end slicing where you
12:07 could have slices per application slices
12:10 per customer slices per even subscriber
12:14 and each slice is isolated from
12:16 performance and security point of view
12:19 then now suddenly you are making your
12:22 network a lot more valuable from which
12:25 you can derive revenues so think of
12:27 investing in end-to-end slicing think of
12:29 investing in this uniform platform layer
12:32 I'm talking about which allows you to
12:34 have API driven service creation across
12:37 all these domains that could be a great
12:39 start great advice Raj it was a pleasure
12:41 talking with you thanks so much for
12:42 joining us today and sharing your views
12:44 on network as a service
12:47 thank you guys it was a pleasure