User-Centric NaaS

User-Centric NaaS API is for NaaS users/subscribers to describe their E2E
(End-to-End) networking service requirements among user endpoints.
User endpoints may be DC gateway, branch office gateway, enterprise gateway,
home gateway, server, VM, laptops, desktops, phones. NaaS users/subscribers
mainly care about their E2E networking service requirements in the form of
service contracts, including SLA (Service Level Agreement), bandwidth
profile, time schedule and fine-grained value-added service parameters. These
E2E networking service requirements are platform-agnostic and should be
automatically compiled and mapped into underlying platform-specific network
control or configuration APIs by the User-Centric NaaS Engine with conflicts
checking and resolution.

With the User-Centric NaaS API, NaaS users/subscribers can easily describe
their E2E NaaS service instances. A service instance specifies which
service_type and service_contract can be accessed by a UEP or a list of UEPs
with the same NaaS service requirements to communicate with other UEPs. A
tenant ID is used to identify a NaaS user/subscriber. A tenant may have
multiple service graphs. With the same service_name string, multiple service
instances are associated into a P2Net (Point-to-external-Network), P2P
(Point-to-Point), MP2MP (MultiPoint-to-MultiPoint), or RMP (Rooted-MultiPoint)
basic service. With the same service_graph_id value, multiple basic services
are associated into a service graph in a hybrid way.

This User-Centric NaaS API will also be used in E2E WANaaS blueprint for
Enterprise applications or self-service subscribers to describe their E2E
WAN service requirements across one or multiple domains.