oneM2M Architecture Interactive Visualization

Step through AEs, CSEs, reference points, resource trees, and CRUD+N primitives in the oneM2M service layer

Interactive oneM2M architecture workbench showing Application Entities, Common Services Entities, Network Services Entities, Mca/Mcc/Mcn reference points, node types, resource trees, and CRUD+N operations.

Application Protocols oneM2M Service Layer Intermediate

Trace how oneM2M turns mixed IoT devices into a shared service-layer resource tree.

Choose a scenario, then step through the primitives. The diagram highlights which entity is active, which reference point carries the exchange, and how the CSE resource tree changes.

McaActive reference point

CREATEPrimitive operation

<AE>Resource focus

CoAP bindingTransport mapping

oneM2M Architecture Workbench

Entity Layer

AE is application logic, CSE hosts common service functions, and NSE represents underlying network services.

Reference Points

Mca connects AE to CSE, Mcc connects CSEs, and Mcn connects CSEs to network services.

Resource Model

The resource tree starts at CSEBase, then grows through AE, container, contentInstance, subscription, group, and ACP resources.

Binding Caveat

HTTP, CoAP, MQTT, and WebSocket bindings carry the same service-layer primitives; they do not change the resource model itself.

Controls

Run a flow, inspect each primitive, then compare how the path changes by scenario.

Playback

Scenario

Protocol binding HTTP CoAP MQTT WebSocket Show access-control and security checks in the trace

Current diagnosis

Service-layer handoff

The AE asks its local CSE to create a resource. The CSE applies common service functions before storing or forwarding the request.

Gateway telemetry publish

A sensor AE creates a contentInstance at a gateway CSE, then the CSE path can synchronize toward an infrastructure CSE for cloud applications.

Mca: AE to CSE Mcc: CSE to CSE Mcn: CSE to NSE Local legacy link

Device AE

An Application Entity hosts application logic. Here it is a sensor application that creates oneM2M resources through a nearby CSE.

AE-ID Mca client

Primitive frame

CREATE /in-cse/mn-gw/temp-sensor/telemetry with originator C-AE-therm-01.

Resource tree

ADN AE -> MN-CSE -> IN-CSE Logical path for the selected step

Registration + data management Common Service Functions in use

Privileges checked Security and access-control reminder

Event log

How To Read The Diagram

Start with the active orange token. Ask: which entity originated the primitive, which reference point is highlighted, and which resource changed?

What oneM2M Standardizes

oneM2M standardizes a horizontal service layer: common functions, primitives, resources, protocol bindings, and reference points. It does not require one fixed physical topology.

Common Misread

Do not treat the gateway as just a byte converter. A CSE can also provide registration, discovery, storage, subscription, group management, security, and other service functions.

Reference Point And Entity Quick Reference

Item	Meaning	Typical learner check
AE	Application Entity. It is an execution instance of application service logic and has an AE-ID.	Is this application using CSE services, or is it the service layer itself?
CSE	Common Services Entity. It hosts one or more Common Service Functions such as data management, security, discovery, notification, grouping, location, and device management.	Which CSFs are needed for this primitive?
NSE	Network Services Entity. It represents underlying network services used by the CSE, such as connectivity, triggering, and location support.	Is the service-layer primitive asking for network support?
Mca	Reference point between an AE and a CSE.	Is an application talking to a CSE?
Mcc	Reference point between two CSEs. Mcc' is used between different service providers.	Did the request cross from one CSE tree segment to another?
Mcn	Reference point between a CSE and the Network Services Entity.	Is the CSE depending on underlying network capabilities?

Technical Accuracy Notes

• The diagram is a teaching model of the functional architecture. Real products may implement only a subset of Common Service Functions and may deploy nodes differently.
• An ASN contains one CSE and at least one AE in the field domain. An ADN contains at least one AE but no CSE. A MN has a CSE and is often a gateway. An IN has a CSE in the infrastructure domain.
• CRUD+N means Create, Retrieve, Update, Delete, and Notify. Access-control policies can also include discovery-related privileges.
• REST is an architectural style, not a transport protocol. oneM2M protocol bindings map service-layer primitives to protocols such as HTTP, CoAP, MQTT, and WebSocket.
• Interworking Proxy Entities are represented here as specialized AEs that map non-oneM2M models to oneM2M resources before using Mca.

Official Basics

oneM2M developer basics describe the service layer, AE, CSE, NSE, node types, and interworking concept.

Official API

oneM2M API guidance covers CRUD+N primitives, resources, attributes, protocol bindings, and Mca/Mcc/Mcc' exchanges.

Resource Model

oneM2M REST resources define CSEBase, AE, container, contentInstance, access-control, subscriptions, discovery, and groups.

Check Yourself

A dashboard creates a subscription on a container. Which primitive is used first, and which reference point carries it when the dashboard talks to an IN-CSE?

Design Prompt

Move a constrained sensor from ASN to ADN. What disappears from the field node, and which nearby entity must now host the CSE services?

Debug Prompt

A notification never reaches the subscriber. Inspect the subscription resource, the ACP, the target AE point of access, and any Mcc hop between CSEs.

M2M fundamentals M2M communication IoT reference models M2M gateway animation