TIP Fyuz: Fixed Broadband and Transport – From Farm to Table

That’s exactly what we set up to achieve. Run, so what’s your opinion on that?
Let’s take a step back. When we started this, it was called DDC, it was part of OCP.
So we had a lot of work done with AT&T, it went into deployment. But this is as we know
that this is one operator and the requirements are very are much tailored. Now the
requirements are coming on the network functionality side. Well, everything infrastructure was kind of open and well defined
and this is also what boiled down eventually into DDBR and this is where TIP came in.
And the way the TIP came in is that they kind of formalized inputs not from just one operator but from
multiple carriers. And for us as a software vendor now we are running on the functionality side.
Any type of functionality can be run on the DDBR cluster.
That’s the way that we constructed our architecture to begin with and also aligned with how TIP
has put it into definition. But what we get eventually is a kind of a unified
set of requirements that other operators can then just
take it off the shelf product as what Turkcell has done. In a way it’s kind
of an off-the-shelf ready to deploy. It’s already field-proven for a few last
few years in live commercial environments in
very stringent and robust. So we had all that to back us up as we went into it and
then but TIP came and kind of formalized it and enabled it to the rest of the industry.
Great.
And it’s really encouraging to get the fact in your baking it into your
businesses processes and is your strategy.

Run, what’s the initial response?
It’s spot on. People love to improve and they hate change. So when there’s something new
coming in, it’s hard to adopt it. So this is the type of challenges that we’re facing.
I think this forum, I think this event and what what TIP is doing is exactly
there to solve this issue, to put it on stage. The testing cycle
that you have on TIP, the actual deployment and the commercialization of it and the publication of it will
enable other operators to see that this is the real deal. Now we have other
deployments, obviously other use cases. This is already running several years, so this is stable.
And now the audience and now the entire industry knows about it.
Coming back to what you were saying, getting something new into the network
and who’s in charge because it’s disaggregated, who’s the one call to
make to make it operational. And the way I feel, coming from the perspective of DriveNets,
it’s DriveNets. It’s the control plane that runs multiple devices.
That’s the only element which actually exists in every component of the solution. Therefore, that can only be the
one phone call to make.
And I think that’s always the key for operators. Right?
The one throat to choke.
If I may use that term.
We prefer not to choke our own…

Run, over to you.
When you look at disaggregation it
started on the hyperscale side of things and the one
purpose that they were trying to solve is getting control over their network over
what was going on and into their network, in a way TIP is doing the same but now
on the service provider space eventually when you have one vendor who is providing
all of the solutions, kind of a one-stop-shop, he also has control and when you’re
disaggregating and getting components from multiple vendors no one vendor has full
control it means that the control is at the hands of the customer, so the service provider now has control
the way I see evolution to your question is a growth of the
ecosystem it’s not just UfiSpace as the provider of the hardware, no offense Ray,
but it’s not just drivers on the perspective of the software vendor as well, right?
Multiple components or multiple players can chime into the same ecosystem and expand it
so from a tools perspective, if I don’t know, one year or two years down the line is not satisfied
to me, can swap me out as a software vendor and still run on the same infrastructure that
he got from UfiSpace, but that’s a possibility or a capability that exists in this
type of ecosystem, and another revolution will be use cases
not just routing but additional network functions that can be mounted onto that same
infrastructure management network function that will enable this CDBR is going to be part
of a larger network and include other components this type of an evolution.
Thank you very much and I’m really glad to hear a vendor saying they don’t mind being swapped out
Thank you very much for all of you.