<li>Web frontend User Interface (UI) that consists of mainly two portal categories: <ol>
<li>Web frontend User Interface (UI) that consists of mainly three portal categories: <ol>
<li>An NFV portal allowing users to onboard VNFDs/NSDs to facility’s NFVOs and self-service management </li>
<li>Several TMF-family portals (Product, Service, Resource, Testing) which allow users to browse the respective layers of a modern BSS/OSS solution</li>
<li>An AI assistant that aggregates the offered functionalities into a chat-based interaction</li>
</ol>
</li>
<li>An API gateway that proxies the internal APIs, which are used by the Web frontend as well as any other 3rd party services, and consist of:<ol>
@@ -3434,20 +3413,25 @@
<li>A microservice offering NFV-compliant API services (e.g. VNFD/NSD onboarding and management, etc) allowing to manage multiple NFVOs and store VNFDs and NSDs in the respective catalogues</li>
</ol>
</li>
<li>A Service Orchestrator (SO) solution that will fulfill Service Ordering requests by propagating the orchestration actions to underlying components (e.g. NFVOs, Kubernetes, or other controllers) or to external SOs</li>
<li>A MANO Client microservice which interfaces with SOL005-compliant NFVOs (synchronizing artifacts and propagating actions)</li>
<li>A Custom Resource (CR) to TMF bridge (CRIDGE) microservice which interfaces with Kubernetes</li>
<li>A Metrics Retrieval Component (METRICO) which interfaces with external monitoring tools, retrieving and injecting desired metrics into OpenSlice orchestration pipeline</li>
<li>A pool of several controllers (e.g., Sylva, Camara, 3GPP, gitops, etc.), offered as optionally enabled addons</li>
<li>An AI layer, integrating the built-in MCP Server and open-source LLMs, which interfaces and interworks with the rest components</li>
<li>A Message Bus used by all microservices to exchange messages either via message Queues or via publish/subscribe Topics</li>
<li>An Authentication Server implementing Oauth2 authentication scheme</li>
<li>A microservice that is capable to interface with an issue management system (e.g. it raises an issue to all related stakeholders - CSPs, NOPs, CSCs - that a new Service Order is requested)</li>
<li>A Central Logging microservice that logs all distributed actions into an Elasticsearch cluster</li>
<li>A Service Orchestrator (SO) solution that will fulfill Service Ordering requests by propagating the orchestration actions to underlying components (e.g. NFVOs or Kubernetes) or to external SOs</li>
<li>A MANO Client microservice which interfaces with SOL005-compliant NFVOs (synchronizing artifacts and propagating actions)</li>
<li>A Custom Resource (CR) to TMF bridge (CRIDGE) microservice which interfaces with Kubernetes</li>
<li>A Metrics Retrieval Component (METRICO) which interfaces with external monitoring tools, retrieving and injecting desired metrics into OpenSlice orchestration pipeline</li>
<li>An Assurance Services component which generates and monitors alerts, as well executing defined actions based on the latter</li>
<li>A visualization server (KROKI) microservice which enables a intuitive illustration of dependency graphs and interactions</li>
