3.1 Terms

For the purposes of the present document, the following terms apply:

Application Entity (AE): logical entity in the oneM2M architecture that provides application service logic.
Application Dedicated Node (ADN): oneM2M node hosting only AEs.
Common Service Entity (CSE): core oneM2M functional entity providing service layer functions.
Federated Learning (FL): machine learning technique in which model training is performed locally on multiple nodes and only parameters/weights are exchanged with aggregators.
Federation Group: logical grouping of MEC/oneM2M instances that intercommunicate and cooperate in executing distributed tasks.
Federation Registry: registry that stores the identity, capabilities, and services of MEC/oneM2M instances participating in federation.
Handover: process of transferring control of a device or service from one MEC/oneM2M instance to another to maintain service continuity.
Interworking Proxy Entity (IPE): functional entity that bridges MEC/oneM2M with external devices or services.
Mca Proxy: proxy component enabling communication between oneM2M devices and a CSE when direct communication is not possible.
Multi-access Edge Computing (MEC): ETSI-defined framework for providing cloud-computing capabilities at the edge of networks.
Swarm Agent: software entity that performs local computation and participates in cooperative swarm behaviour.
Swarm Collector: node that aggregates results from multiple swarm entities and produces unified outputs.
Swarm Orchestrator: coordination entity that manages task distribution, synchronization, and resilience across swarm nodes.
Swarm Computing: coordination of multiple MEC/oneM2M instances to perform distributed computing tasks.