Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Akraino oneM2M Contact person/PTL- Ike Alisson - 3 September March 2021 through 3 March 2022

...

  • the Application Layer,
  • the Common Services Layer
  • the underlying Network Services Layer.

          Image Removed Image Added

Application Entity (AE): The Application Entity is an Entity in the Application Layer that implements an M2M Application Service Logic. Each Application Service Logic can be resident in a number of M2M Nodes and/or more than once on a Single M2M Node. Each execution instance of an Application Service Logic is termed an "Application Entity" (AE) and is identified with a unique AE-ID.

...

Examples of service functions offered by the CSE include: data storage & sharing with access control and authorization, event detection and notification, group communication, scheduling of data exchanges, device management, and location services.

Underlying Network Services Entity (NSE): A Network Services Entity provides Services from the underlying Network to the CSEs.

oneM2M Common Service functions (CSFs) (applied to all IoT Domains: SAREF IoT UCs (Use Cases))

oneM2M's horizontal Architecture provides a Common Framework for IoT. oneM2M has identified a Set of Common Functionnalities, that are applicable to all the IoT Domains (SAREF). Think of these functions as a large Toolbox with special tools to solve a number of IoT problems across many different domains. Very much like a screw driver can be used to fasten screws in a car as well as in a plane, the oneM2M CSFs are applicable to different IoT Use Cases (UCs)/Domains in different Industry Domains.

...