Cloud Nets VideosAugust 31, 2023

Season 3 Ep 9: KDDI deploys Network Cloud

Why is the KDDI deployment, a major deployment, of Network Cloud so important?

We’re going to talk about KDDI, one of Japan’s major Tier 1 operators. They recently announced that they implemented DriveNets Network Cloud solution in its network and they are very satisfied. They are talking about huge TCO advantages, about 46% saving in power and 40% savings in rackspace, etc.

Listen on your favorite podcast platform

Listen on Apple Podcasts
Listen on Spotify

Full Transcript

Hi, and welcome back to CloudNets, where networks meet cloud.
And today we’re going to talk about KDDI, one of Japan’s major tier-1 operators, that recently announced that it has implemented Drivenets’ Network Cloud solution in its network.
And they are very satisfied. They are talking about huge TCO advantages.
They’re talking about 46% saving in power and 40% saving in rackspace, etc.
And we have our Japan expert.
Run, thank you for coming all the way from Tokyo.
Yeah, Run, let’s talk about KDDI.

And why is this deployment of Network Cloud so important?
It’s a major deployment, but it is a unique one.
It is unique and unique for three main reasons.
Well, it’s true.
With all the benefits that KDDI gained from this put this aside.
It’s very important, obviously, from their perspective.
What does it mean for DriveNets?
Well, the first thing is that we’re talking about a different use case.
Up until now, we’ve been talking about core as a use case, aggregation.
In this case, it’s a peering router.

It’s a third version or a third type of a router, all of which are imposed or deployed onto the same DDC infrastructure.
Same solution, new use case or new implementation method.
The classic disaggregation of software from hardware functionality is here.
Hardware is a different place.
Second item is that we are not using Ufispace as the ODM, in this case, it’s a new ODM.
We’re using Delta in this case, preference of the customer.
So the customer could actually choose who is the hardware vendor with which he’s working with Because in a disaggregated system, you select the software and pick any hardware
vendor which is compatible.
As you choose.

And then the third item, and perhaps third and a half, this is a non US customer.
There is talk, there is rumor that DDC has been built specifically for AT&T.
That’s not the case.
It’s a uniform solution.
It applies for multiple use cases.
And any customer, any tier-1 operator worldwide, can take this model and adopt it into their use case.
In this case, it’s a customer in Japan.
So everything to do with reliability, even though we passed AT&T, of course.
But in this case, Japan is kind of a higher limit of …
And it was a long and very detailed process of checking.
One, two, three things.

So, just to recap the three reasons the DDBR or DDC implementation of the Network Cloud in KDDI is so important,

One, it’s a new use case.
It’s an additional use case to the ones we are used to when deploying DDC.
it’s a peering routing implementation with the same infrastructure.

The second is that it introduced a new flavor of hardware, a new ODM, in this case, Delta.
It could have been Ufispace, it could have been Edgecore.
And this is the nice thing about disaggregation.
You choose the hardware vendor which is most suitable for you

And the third is it’s a new geography.
First time in Japan for commercial deployment and again just to show that this solution fits not only the North American carriers but carriers worldwide.
And we see it with other customers. It’s a generic solution.

Thank you very much, Run, for this

Thank you for joining and watching us.
See you next time on CloudNets