5GMETA is an open data-centric Internet of Things (IoT) messaging platform for Connected and Automated Mobility (CAM) applications and service providers. The 5GMETA Platform creates a CAM data monetization ecosystem that allows different stakeholders along the data value chain to exploit data in a more effective and profitable way.
A fundamental principle supported by the 5GMETA Platform is that of achieving a total decoupling between Data Producers and Data Consumers. This means that Data Producers do not need to be directly connected to Data Consumers. The 5GMETA Platform acts as a broker between Data Producers (vehicles or RSUs) and Data consumers (third-party applications or services). However, the 5GMETA Platform is not a simple publish-subscribe broker, and it includes functions for data management, data monetization and cybersecurity as well as providing data access mechanisms. In contrast with a Data Lake, the 5GMETA Platform provides live data delivery. The users of the 5GMETA Platform receive the data from the subscribed dataflows in a continuous manner with no storage service within the 5GMETA Platform rather than the required memory buffering.
These two videos are a good starting point to learn more about the motivation and the basic concepts of the 5GMETA Platform:
- Video 1: The 5GMETA Project
- Video 2: The 5GMETA Platform
The Road to Lisbon hackathon webinars are also a great resource:
- Road to Lisbon_5GMETA Hackathon Webinar #1_Introduction to the Platform
- Road to Lisbon 5GMETA Hackathon Webinar #2 How to interface with the platform
- Road to Lisbon 5GMETA Hackathon Webinar #3 Choosing and using available data
More info can also be found on the 5GMETA website.
| Repository | Description |
|---|---|
| 5gmeta-dev | Contains the documentation, examples and tutorials related to the 5GMETA platform. |
| cloud_instanceapi | This API is the central access point to request to the different MECs that are part of the platform to deploy instances on them depending on instancetype and datatype. |
| dashboard | The main objective of the dashboard is to provide a graphical interface to the data consumers allowing them to benefit from the 5GMETA platform features that are otherwise only accessible using API requests. |
| data_quality | Contains the data quality assessment module based on ETSI TS 103 759 V2.1.1 (2023-01). This module assigns to each dataflow a quality value from 1 to 7. |
| dataflow-api | Contains all the components needed to implement a Flask web server providing the Dataflow APIs to a third-party application. |
| dataflow_cloud | Related to the dataflow database Cloud building block of the 5GMETA Platform, and to be deployed at the 5GMETA Cloud level for storing the metadata (commonly named dataflow in the project) related to produced & consumed data. |
| discovery | This API is in charge of managing all necessary information about MECs and their capabilities, coverage zones (tiles) and services provided by them to 3rd party applications and to 5GMETA platform members. |
| helmcharts | Includes the HELM charts required by K8s to deploy platform systems at Cloud and MEC and to instantiate data pipelines in a specific MEC triggered by a request from a data consumer. |
| identity | Hosts the code and the resources regarding the Identity module: the identity manager based on Keycloak and the user information manager based on Spring Boot. |
| license | Hosts the source code for the license API of the 5GMETA platform. For the platform operator, the license API allows the management of the dataflow licenses to be made available to the data consumers i.e. creation, update and deletion. For the data consumers, the license API allows the retrieval of the available dataflow licenses. |
| llccam | Shows how to deploy a CCAM Application in the MEC Platform of 5GMETA (using 5GMETA HW resources instead of deploying it in the Third-Party premises). |
| message-data-broker | Contains an ActiveMQ message broker to be deployed in the MEC. |
| metering | Contains the documentation and resources to deploy the monitoring tools to meter the computer usage and the data consumption volume. This information could be used to charge users in a pay-as-you go pricing approach. |
| orchestrator | Contains all the components necessary to get a working Edge Stack where the pipelines requested from a third party will be deployed to handle specific data types. |
| platform-config | Includes all the guidelines to deploy both, the MEC and the Cloud systems of the 5GMETA platform. |
| registration | Contains all the components needed to implement the Registration API, a Flask web server running on the Edge, providing REST APIs to interact with a dataflow database. |
| stream-data-gateway | Contains all the components and connectors necessary to retrieve data from MEC data pipelines and make them accessible to consumers on internet through the 5GMETA Cloud platform. |
| video-anonymizator | Contains all the necessary stuff to build video and image anonimizator modules for the 5GMETA platform. |
| video-stream-broker | Provides the modules to push a video stream to the MEC infrastructure and how the Broker performs the signalling and the streaming of Video flows in a standard way. |
| vnfdescriptors | Includes the VNF descriptors required by OSM to instantiate data pipelines in a specific MEC triggered by a request from a data consumer |
Contributions are welcome 😊 See how to contribute.