D1.1:ESTIMED First Progress Report
The deliverable outlines the activities carried out up to month 12, the coordination efforts among the involved tasks, and the preparation of the deliverables planned in the work plan.
The deliverable outlines the activities carried out up to month 12, the coordination efforts among the involved tasks, and the preparation of the deliverables planned in the work plan.
The deliverable summarizes the activities carried out up to month 24, the coordination of these activities, and the preparation of the deliverables anticipated in the work plan.
This report summarizes the oneM2M and MEC implementations investigated, outlining the use case selection criteria and the assessment of each implementation for potential use in the PoC. It evaluates the required existing features, estimates the development effort needed for new functionalities, and identifies the selected implementations along with the rationale behind their selection.
MEC Technical Report providing a detailed description of the selected use cases and the required architectural evolutions, such as components and mappings within the oneM2M and MEC frameworks. Building on the outcomes of the joint MEC and oneM2M White Paper, the STF will identify use cases that leverage IoT and edge computing technologies, with a particular focus on standards-based scenarios where oneM2M and ETSI MEC can be effectively applied.
Specification contributions to oneM2M TR-0001(link) and TS-0002 (link) to address any new requirements. The report will also detail the oneM2M features to be used in the PoCs and the MEC APIs that will be integrated or interworked with oneM2M in TR-0080(link).
Slide decks and hands-on exercises covering the use of the selected MEC and oneM2M solutions.
Based on the identified use cases and requirements that leverage IoT and edge computing technologies, this GR proposes a set of solutions to support the enhancements needed for enabling MEC–oneM2M deployments.
Based on the use cases, requirements, and recommendations identified in D3.1, this GS specifies how MEC can interwork and be deployed in the context of oneM2M.
This deliverable defines the requirements for an ETSI MEC Interworking Proxy Entity, intended to extend existing oneM2M and MEC deployments that lack native interworking capabilities. It outlines the architectures needed to support IoT edge services, examines real-world scenarios where oneM2M services are delivered through MEC platforms, and specifies the standards, interfaces, and data flows required for interoperability. The report also identifies key integration challenges, proposes corresponding solutions, and highlights standardization gaps that must be addressed to achieve seamless oneM2M–MEC interworking.
This deliverable outlines the background and motivation for interworking between oneM2M and MEC and standardizes the high-level architecture enabling this integration. It defines the functions required to support interworking with MEC and specifies the detailed procedures necessary to ensure seamless operation between the two systems.
This deliverable presents the project team’s contributions to oneM2M specifications, addressing the change requests identified to support MEC–oneM2M integration.
This deliverable covers the investigation of deploying Federated Learning within the MEC–oneM2M node, exploring methods to identify data suitable for training machine learning models in a privacy-preserving manner, and examining the sharing and deployment of trained models to clients based on location-specific conditions of the deployed ETSI MEC node and local oneM2M CSE.
The software implemented for the MEC system should include MEC APIs for IoT services, both updated and new MEC communication APIs where applicable, and the Interworking Proxy Entity (IPE) application to ensure seamless integration. The software for the oneM2M system should support offloading oneM2M resources to MEC, enable MEC interworking, and instantiate the oneM2M Cloud platform to manage IoT services. Additionally, the MEC open-source implementations used in the STF should interwork with oneM2M APIs and host a oneM2M edge instance to facilitate IoT service provisioning for oneM2M devices within the MEC system.
Application software (web-based or host platform-based) and device software (for sensors or actuators) for each node in the selected simulation scenario. This software will serve as support for PoC implementations.
This deliverable includes reports on the continuously updated documentation and deployment scripts for MEC–oneM2M implementations (e.g., hosted on GitHub/GitLab repository).
PoC report documenting the use case design and implementation, deploying oneM2M as a cloud and MEC as an edge (Option A). It includes instructions for (re)creating the prototypes from the selected framework and components, lessons learned, and references to the developed PoC software available in a public repository.
PoC report documenting the use case design and implementation deploying oneM2M and MEC as an edge across different physical nodes (Option B). It includes instructions for (re)creating the prototypes from the selected framework and components, lessons learned, and references to the developed PoC software available in a public repository.
PoC report documenting the use case design and implementation deploying oneM2M and MEC in the same physical edge node (Option C). It includes instructions for (re)creating the prototypes from the selected framework and components, lessons learned, and references to the developed PoC software available in a public repository.
PoC report documenting the use case design and implementation deploying oneM2M and MEC tightly coupled in the same edge node (Option D). It includes instructions for (re)creating the prototypes from the selected framework and components, lessons learned, and references to the developed PoC software available in a public repository.
Guidelines for testing interoperability in MEC–oneM2M interworking.
This document compiles all conformance test requirements and procedures to verify MEC–oneM2M interworking, covering T5.2 and T5.3. It includes the identification of requirements to be tested, definition of development test objectives, creation of the Abstract Test Suite, and preparation of the validation report.
This will provide a list of the planned dissemination activities for the ESTIMED project.
This deliverable provides light teaching material for education on IoT deployment using oneM2M and MEC, illustrated with practical examples. The associated application software will be available in a public repository.
An introduction to oneM2M and MEC interworking aimed at a broad audience, covering a mix of technical, industry, and policy topics.
Focusing on technical aspects of oneM2M and MEC interworking.
Post-event report summarizing key projects, attendance figures, and participant profiles.
Post-event report summarizing key projects, attendance figures, and participant profiles.
Post-event report summarizing key projects, attendance figures, and participant profiles.
Report compiling the complete list of ESTIMED ecosystem engagements and dissemination activities.
A library of articles, technical papers, and slide presentations for promotional use throughout the project. Additional video content will include short developer presentations and webinar recordings, disseminated via oneM2M and MEC websites, YouTube, etsi.org, and professional media platforms such as LinkedIn and developer forums.