Hi.
I'm Sujata from Intel.
In this video, I talk about Open Network Edge Services Software,
or OpenNESS.
It is an open platform for enabling Network Edge Services
ecosystem.
How will this help you as a developer?
It abstracts away the complexity of the network infrastructure
so you can build and deploy your Edge
applications in 5G and next generation networks with ease.
It automatically makes available the new hardware enhancements,
open source technologies, and integrates with rich toolkits.
Finally, its service-based architecture
allows your AR application, for example,
to make use of location-based services or a street view
application by another app developer.
Let's talk about 5G first.
Did you know that with the low latencies that 5G brings,
use cases like XR, gaming, autonomous driving,
and real-time analytics need not be restricted by the device
capability and can make use of cloud computing at the Edge.
OpenNESS can help you design your application at the Edge.
Using open source APIs and abstracted network services,
developers can leap from the complexity
of network transformation.
OpenNESS can help developers create and deploy applications
that can run anywhere in the cloud, on any Edge location,
in the public or private domain, on any cloud framework,
in a network managed by any service provider.
This includes AWS Greengrass, Microsoft Azure IOT Edge,
and Baidu Intelliedge Services.
This fosters collaboration for developing, securely
onboarding, and enables the ecosystem
to create and deploy new Edge services and applications.
OpenNESS focuses on two main deployment models, On-Prem Edge
and Network Edge.
The main difference between them is where the Edge services
workload runs.
The On-Premise deployment model is
deployed in a UCP Form Factor Edge platform
within an enterprise location.
The OpenNESS controller would be located
in a centralized telco/public cloud
in a hierarchical configuration.
In the Network Edge deployment model,
the Edge services software is deployed in a network function
virtualization form factor Edge platform
in a central office, next generation central office,
or wireless access aggregation point.
The OpenNESS controller would still
be in a centralized Telco cloud or regional centers
for hierarchical configuration.
The Edge platform runs Edge services workloads, including
accelerators and microservices.
And the Edge controller manages it.
It is important to note that the Edge platform can
continue to work even if the link with the controller
is down.
And the critical information is locally available,
leading to robustness while deploying these applications
in remote areas or under buildout conditions.
It is important to note that OpenNESS
is a microservices-based architecture.
These microservices interact with each other
via gRPC and Swagger interfaces to control the system
as a whole.
OpenNESS comes with a couple of sample Applications.
Cloud Connector is a 5G use case related to massive IoT example
that could be deployed for analytics, aggregation,
or function acceleration and provides
a multi-tenant neutral host for different sets of IoT devices.
The computer vision and influencing app
is based on an OpenVINO sample app for smart city
or smart road use cases.
It consists of the consumer app that
consumes a feed from a street camera and the producer
app, which determines the inference model to be applied.
Using OpenNESS as a tool will help
you quickly and efficiently develop your Edge application.
Follow the links in the description
for more information.
And thanks for watching.