IPCEI-CIS Reference Architecture - Revision history

Admin: /* Layers */

2025-10-22T13:16:18Z

Layers

← Older revision		Revision as of 13:16, 22 October 2025
Line 52:		Line 52:
	\|Service Compliance Verification in cloud infrastructures is the process of ensuring that all cloud services and their operations adhere to predefined regulatory, security, and organizational standards. This involves conducting regular assessments and audits to verify that the services comply with laws such as GDPR, HIPAA, and industry-specific regulations. Compliance verification includes monitoring service configurations, access controls, and data handling practices to identify and rectify any deviations from the required standards. By implementing comprehensive compliance verification measures, organizations can mitigate legal and security risks, demonstrate due diligence, and maintain trust with stakeholders and customers. This systematic approach is essential for maintaining the integrity, security, and legality of cloud operations.		\|Service Compliance Verification in cloud infrastructures is the process of ensuring that all cloud services and their operations adhere to predefined regulatory, security, and organizational standards. This involves conducting regular assessments and audits to verify that the services comply with laws such as GDPR, HIPAA, and industry-specific regulations. Compliance verification includes monitoring service configurations, access controls, and data handling practices to identify and rectify any deviations from the required standards. By implementing comprehensive compliance verification measures, organizations can mitigate legal and security risks, demonstrate due diligence, and maintain trust with stakeholders and customers. This systematic approach is essential for maintaining the integrity, security, and legality of cloud operations.
	\|-		\|-
	\|rowspan="6"\|'''~~Application Layer~~'''		\|rowspan="6"\|'''Sustainability'''
	\|-		\|-
	\|Benchmark, Metrics and Monitoring		\|Benchmark, Metrics and Monitoring

Admin: /* Layers */

2025-10-22T13:14:46Z

Layers

@@ Line 8: / Line 8: @@
 {| class="wikitable"
 |-
 |rowspan="7"|'''Application Layer'''

Admin: /* Layers */

2025-10-22T13:05:05Z

Layers

← Older revision		Revision as of 13:05, 22 October 2025
Line 9:		Line 9:
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	\|rowspan="7"\|Application Layer		\|rowspan="7"\|'''Application Layer'''
	\|-		\|-
	\|Application Designer		\|Application Designer
Line 29:		Line 29:
	\|This component implements the accounting of application usage and provides online charging information for the customer to track application expenditure in real-time.		\|This component implements the accounting of application usage and provides online charging information for the customer to track application expenditure in real-time.
	\|-		\|-
	\|rowspan="7"\|Data Layer		\|rowspan="7"\|'''Data Layer'''
	\|-		\|-
	\|Data Pipelines		\|Data Pipelines
Line 49:		Line 49:
	\|Data Federation enables standard mechanisms and interfaces (connectors) for partnering in the provision of datasets, providing a unified view of data catalogs and databases from multiple data providers. This component enables real-time data exchange across companies using data mesh principles, connecting distributed and heterogeneous actors over the cloud-edge continuum, keeping data owners in full control of their data. In order to create and maintain a coherent federated multi-provider Cloud Edge Continuum, Data Federation capabilities should be designed consistently with the other federation capabilities described in this document.		\|Data Federation enables standard mechanisms and interfaces (connectors) for partnering in the provision of datasets, providing a unified view of data catalogs and databases from multiple data providers. This component enables real-time data exchange across companies using data mesh principles, connecting distributed and heterogeneous actors over the cloud-edge continuum, keeping data owners in full control of their data. In order to create and maintain a coherent federated multi-provider Cloud Edge Continuum, Data Federation capabilities should be designed consistently with the other federation capabilities described in this document.
	\|-		\|-
	\|rowspan="7"\|AI Layer		\|rowspan="7"\|'''AI Layer'''
	\|-		\|-
	\|Cloud-Edge Training		\|Cloud-Edge Training
Line 69:		Line 69:
	\|This Explainable AI component ensures transparency by providing interpretable insights into AI decision-making processes. It supports compliance, accountability, and trust by enabling users and regulators to understand, audit, and validate AI models while respecting privacy and data sovereignty.		\|This Explainable AI component ensures transparency by providing interpretable insights into AI decision-making processes. It supports compliance, accountability, and trust by enabling users and regulators to understand, audit, and validate AI models while respecting privacy and data sovereignty.
	\|-		\|-
	\|rowspan="5"\|Service Orchestration		\|rowspan="5"\|'''Service Orchestration'''
	\|-		\|-
	\|Service Orchestrator		\|Service Orchestrator
Line 83:		Line 83:
	\|This component interconnects the Service Orchestrator with those of other federated providers, enabling the deployment and execution of applications (service function chains) across multiple providers in a seamless way, interacting with a single provider. In order to create and maintain a coherent federated multi-provider Cloud Edge Continuum, Service Federation capabilities should be designed consistently with the other federation capabilities described in this document.		\|This component interconnects the Service Orchestrator with those of other federated providers, enabling the deployment and execution of applications (service function chains) across multiple providers in a seamless way, interacting with a single provider. In order to create and maintain a coherent federated multi-provider Cloud Edge Continuum, Service Federation capabilities should be designed consistently with the other federation capabilities described in this document.
	\|-		\|-
	\|rowspan="12"\|Cloud Edge Platform		\|rowspan="12"\|'''Cloud Edge Platform'''
	\|-		\|-
	\|Multi-Cloud Orchestrator (PaaS)		\|Multi-Cloud Orchestrator (PaaS)
Line 118:		Line 118:
	\|The Serverless Orchestrator provides Serverless capabilities, also known as Function as a Service (FaaS), is a cloud computing model that allows developers to build and deploy applications in the form of individual functions, which are executed in response to specific events or triggers. This model eliminates the need to manage server infrastructure, enabling developers to focus solely on writing code. Each function runs in a stateless container, automatically scaling with demand and only consuming resources when invoked, leading to cost savings and efficient resource utilization.		\|The Serverless Orchestrator provides Serverless capabilities, also known as Function as a Service (FaaS), is a cloud computing model that allows developers to build and deploy applications in the form of individual functions, which are executed in response to specific events or triggers. This model eliminates the need to manage server infrastructure, enabling developers to focus solely on writing code. Each function runs in a stateless container, automatically scaling with demand and only consuming resources when invoked, leading to cost savings and efficient resource utilization.
	\|-		\|-
	\|rowspan="6"\|Virtualization		\|rowspan="6"\|'''Virtualization'''
	\|-		\|-
	\|Hardware Resource Manager (BMaaS)		\|Hardware Resource Manager (BMaaS)
Line 135:		Line 135:
	\|This component keeps record of cloud edge sites and the configuration and availability of virtual resources in each one of them (for instance, number of k8s clusters available per site, CPU/memory available per k8s cluster, number of virtual CPUs that are available to setup new k8s clusters, ...) in order to help take decisions on workload placement.		\|This component keeps record of cloud edge sites and the configuration and availability of virtual resources in each one of them (for instance, number of k8s clusters available per site, CPU/memory available per k8s cluster, number of virtual CPUs that are available to setup new k8s clusters, ...) in order to help take decisions on workload placement.
	\|-		\|-
	\|colspan="2"\|Network Systems, SDN controllers		\|colspan="2"\|'''Network Systems, SDN controllers'''
	\|It provides the capabilities to manage physical and virtualized/cloudified networking elements to build network services in the geographically distributed Cloud Edge Continuum.		\|It provides the capabilities to manage physical and virtualized/cloudified networking elements to build network services in the geographically distributed Cloud Edge Continuum.
	\|-		\|-
	\|rowspan="5"\|Virtualization		\|rowspan="5"\|'''Virtualization'''
	\|Compute		\|Compute
	\|Compute resources are fundamental to cloud infrastructure, delivering the computational power required for running applications and services. They facilitate scalable and efficient environments that dynamically adjust to varying workloads, thus enhancing resource utilization and performance while minimizing costs.		\|Compute resources are fundamental to cloud infrastructure, delivering the computational power required for running applications and services. They facilitate scalable and efficient environments that dynamically adjust to varying workloads, thus enhancing resource utilization and performance while minimizing costs.
Line 154:		Line 154:
	\|This component keeps record of cloud edge locations and the configuration and availability of physical hardware resources in each one of them (for instance, number of servers per location, type of servers, type of NIC cards available per location, cost of resources, energy consumption of resources, ...) in order to help take decisions on workload placement and resource lifecycle management.		\|This component keeps record of cloud edge locations and the configuration and availability of physical hardware resources in each one of them (for instance, number of servers per location, type of servers, type of NIC cards available per location, cost of resources, energy consumption of resources, ...) in order to help take decisions on workload placement and resource lifecycle management.
	\|-		\|-
	\|colspan="2"\|Physical Network Resources		\|colspan="2"\|'''Physical Network Resources'''
	\|It includes all the physical hardware resources required to implement the Cloud Edge Continuum (compute, storage and networking). It is closely connected to the physical network infrastructure that supports communication among the computing nodes in the continuum and the connectivity of users to that continuum.		\|It includes all the physical hardware resources required to implement the Cloud Edge Continuum (compute, storage and networking). It is closely connected to the physical network infrastructure that supports communication among the computing nodes in the continuum and the connectivity of users to that continuum.
	\|}		\|}

Admin: /* Layers */

2025-10-22T13:03:28Z

Layers

← Older revision		Revision as of 13:03, 22 October 2025
Line 138:		Line 138:
	\|It provides the capabilities to manage physical and virtualized/cloudified networking elements to build network services in the geographically distributed Cloud Edge Continuum.		\|It provides the capabilities to manage physical and virtualized/cloudified networking elements to build network services in the geographically distributed Cloud Edge Continuum.
	\|-		\|-
	\|rowspan="6"\|Virtualization		\|rowspan="5"\|Virtualization
	\|Compute		\|Compute
	\|Compute resources are fundamental to cloud infrastructure, delivering the computational power required for running applications and services. They facilitate scalable and efficient environments that dynamically adjust to varying workloads, thus enhancing resource utilization and performance while minimizing costs.		\|Compute resources are fundamental to cloud infrastructure, delivering the computational power required for running applications and services. They facilitate scalable and efficient environments that dynamically adjust to varying workloads, thus enhancing resource utilization and performance while minimizing costs.

Admin: /* Layers */

2025-10-22T13:02:02Z

Layers

← Older revision		Revision as of 13:02, 22 October 2025
Line 154:		Line 154:
	\|This component keeps record of cloud edge locations and the configuration and availability of physical hardware resources in each one of them (for instance, number of servers per location, type of servers, type of NIC cards available per location, cost of resources, energy consumption of resources, ...) in order to help take decisions on workload placement and resource lifecycle management.		\|This component keeps record of cloud edge locations and the configuration and availability of physical hardware resources in each one of them (for instance, number of servers per location, type of servers, type of NIC cards available per location, cost of resources, energy consumption of resources, ...) in order to help take decisions on workload placement and resource lifecycle management.
	\|-		\|-
	\|colspan="2"		\|colspan="2"\|Physical Network Resources
	\|Physical Network Resources
	\|It includes all the physical hardware resources required to implement the Cloud Edge Continuum (compute, storage and networking). It is closely connected to the physical network infrastructure that supports communication among the computing nodes in the continuum and the connectivity of users to that continuum.		\|It includes all the physical hardware resources required to implement the Cloud Edge Continuum (compute, storage and networking). It is closely connected to the physical network infrastructure that supports communication among the computing nodes in the continuum and the connectivity of users to that continuum.
	\|}		\|}

Admin: /* Layers */

2025-10-22T13:01:21Z

Layers

← Older revision		Revision as of 13:01, 22 October 2025
Line 136:		Line 136:
	\|-		\|-
	\|colspan="2"\|Network Systems, SDN controllers		\|colspan="2"\|Network Systems, SDN controllers
			\|It provides the capabilities to manage physical and virtualized/cloudified networking elements to build network services in the geographically distributed Cloud Edge Continuum.
	\|-		\|-
	\|rowspan="6"\|Virtualization		\|rowspan="6"\|Virtualization
Line 153:		Line 154:
	\|This component keeps record of cloud edge locations and the configuration and availability of physical hardware resources in each one of them (for instance, number of servers per location, type of servers, type of NIC cards available per location, cost of resources, energy consumption of resources, ...) in order to help take decisions on workload placement and resource lifecycle management.		\|This component keeps record of cloud edge locations and the configuration and availability of physical hardware resources in each one of them (for instance, number of servers per location, type of servers, type of NIC cards available per location, cost of resources, energy consumption of resources, ...) in order to help take decisions on workload placement and resource lifecycle management.
	\|-		\|-
			\|colspan="2"
			\|Physical Network Resources
			\|It includes all the physical hardware resources required to implement the Cloud Edge Continuum (compute, storage and networking). It is closely connected to the physical network infrastructure that supports communication among the computing nodes in the continuum and the connectivity of users to that continuum.
	\|}		\|}

Admin: /* Layers */

2025-10-22T12:59:25Z

Layers

← Older revision		Revision as of 12:59, 22 October 2025
Line 69:		Line 69:
	\|This Explainable AI component ensures transparency by providing interpretable insights into AI decision-making processes. It supports compliance, accountability, and trust by enabling users and regulators to understand, audit, and validate AI models while respecting privacy and data sovereignty.		\|This Explainable AI component ensures transparency by providing interpretable insights into AI decision-making processes. It supports compliance, accountability, and trust by enabling users and regulators to understand, audit, and validate AI models while respecting privacy and data sovereignty.
	\|-		\|-
	\|rowspan="6"\|Service Orchestration		\|rowspan="5"\|Service Orchestration
	\|-		\|-
	\|Service Orchestrator		\|Service Orchestrator

Admin: /* Layers */

2025-10-22T12:57:35Z

Layers

Show changes

Admin: /* Layers */

2025-10-22T12:56:29Z

Layers

Show changes

Admin: /* Layers */

2025-10-22T12:54:50Z

Layers

← Older revision		Revision as of 12:54, 22 October 2025
Line 134:		Line 134:
	\|Virtual Resource Repository		\|Virtual Resource Repository
	\|This component keeps record of cloud edge sites and the configuration and availability of virtual resources in each one of them (for instance, number of k8s clusters available per site, CPU/memory available per k8s cluster, number of virtual CPUs that are available to setup new k8s clusters, ...) in order to help take decisions on workload placement.		\|This component keeps record of cloud edge sites and the configuration and availability of virtual resources in each one of them (for instance, number of k8s clusters available per site, CPU/memory available per k8s cluster, number of virtual CPUs that are available to setup new k8s clusters, ...) in order to help take decisions on workload placement.
	\|-
	~~\|colspan="2"\|Network Systems, SDN controllers~~
	\|-		\|-
	\|rowspan="6"\|Virtualization		\|rowspan="6"\|Virtualization