11.1. OMA Lightweight M2M

GEISA Application & Device Management uses the Open Mobile Alliance Lightweight M2M [LwM2M] protocol for application management. Specifically,

• ADM conformant platforms and Edge Management Systems (EMS) SHALL support LwM2M protocol version 1.2 as defined by approved revision 1.2.2 of the LwM2M Core and Transport specifications. [LwM2M-Core] [LwM2M-Transport]

• ADM conformant platforms and EMS are required to support only the LwM2M interfaces, operations, Objects, Resources, features, and behaviors made applicable by the GEISA specification. GEISA does not require every optional LwM2M feature or every Object in the OMA registry.

• ADM conformant platforms and EMS MAY support later LwM2M protocol or Object versions, provided they continue to support the GEISA-pinned baseline and do not require later-version behavior for GEISA interoperability.

• ADM conformant platforms and EMS SHALL support CoAP over UDP for message transport. [LwM2M-Transport]

• ADM conformant platforms and EMS SHALL support DTLS for CoAP security.

• ADM conformant platforms and EMS SHALL support Certificate mode with EST as per [LwM2M-Transport] 5.2.4.

• ADM conformant platforms and EMS SHALL support EST over CoAP per [RFC9148]

• ADM conformant platforms and EMS SHALL support the Bootstrap, Registration, Device Management and Information Reporting interfaces.

• ADM conformant platforms and EMS SHALL support the applicable Resources and behaviors of the required LwM2M Objects at the versions in the fixed GEISA ADM Object-version baseline below.

• ADM conformant EMS SHALL support the following LwM2M Objects:

  • /0 – Security

  • /1 – Server

  • /3 – Device

  • /4 – Connectivity Monitoring

  • /5 – Firmware Update

  • /6 – Location

  • /9 – Software Management

  • /10 – Cellular Network Connectivity

  • /11 – APN Connection Profile

  • /12 – WLAN Connectivity

  • /13 – Bearer Selection

  • /20 – Event Log

  • /504 – Remote SIM Provisioning

  • /3600 – GEISA App Messaging

  • /3601 – GEISA Host Monitoring

  • /3602 – GEISA App Accounting

  • /3604 – GEISA App Monitoring

  • /3605 – GEISA Platform Monitoring

  • /3606 – GEISA Platform Effective Configuration

  • /3607 – GEISA Platform Requested Configuration

• ADM conformant platforms SHALL support the following LwM2M Objects:

  • /0 – Security

  • /1 – Server

  • /3 – Device

  • /4 – Connectivity Monitoring

  • /5 – Firmware Update

  • /9 – Software Management

  • /20 – Event Log

  • /3600 – GEISA App Messaging

  • /3601 – GEISA Host Monitoring

  • /3602 – GEISA App Accounting

  • /3604 – GEISA App Monitoring

  • /3605 – GEISA Platform Monitoring

  • /3606 – GEISA Platform Effective Configuration

  • /3607 – GEISA Platform Requested Configuration

For each required Object, all Mandatory Resources SHALL be implemented.

Object /3608 GEISA Platform Component Monitoring is optional and MAY be implemented.

• ADM conformant platforms with 3GPP network interfaces SHALL support the following LwM2M Objects:

  • /10 – Cellular Network Connectivity

  • /11 – APN Connection Profile

  • /13 – Bearer Selection

  • /504 – Remote SIM Provisioning

• ADM conformant platforms with WLAN interfaces SHALL support the following LwM2M Objects:

  • /12 – WLAN Connectivity

• ADM conformant platforms with GNSS interfaces SHALL support the following LwM2M Objects:

  • /6 – Location

• ADM conformant platforms and EMS with Wi-SUN interfaces SHALL support the following LwM2M Objects:

  • /3603 – Wi-SUN Radio Management

11.1.1. GEISA ADM Object-version baseline

The following Object versions form the fixed GEISA 1.0 ADM baseline. Where an updated definition is available, the XML link identifies the pinned definition audited for this baseline. Pending definition updates are identified below.

Table 11.1 GEISA 1.0 ADM Object versions

Object	Name	Version	Linked XML definition
/0	LwM2M Security	1.2	0.xml
/1	LwM2M Server	1.2	1.xml
/3	Device	1.2	3.xml
/4	Connectivity Monitoring	1.3	4.xml
/5	Firmware Update	1.2	5.xml
/6	Location	1.0	6.xml
/9	Software Management	1.1	Current 9.xml
/10	Cellular Network Connectivity	1.1	10.xml
/11	APN Connection Profile	1.1	11.xml
/12	WLAN Connectivity	1.1	12.xml
/13	Bearer Selection	1.1	13.xml
/20	Event Log	3.1	20.xml
/504	Remote SIM Provisioning	1.0	504.xml
/3600	GEISA App Messaging	1.1	3600.xml
/3601	GEISA Host Monitoring	1.1	3601.xml
/3602	GEISA App Accounting	1.1	3602.xml
/3603	GEISA Wi-SUN Radio Management	TBD	Definition pending
/3604	GEISA App Monitoring	1.0	3604.xml
/3605	GEISA Platform Monitoring	1.0	3605.xml
/3606	GEISA Platform Effective Configuration	1.0	3606.xml
/3607	GEISA Platform Requested Configuration	1.0	3607.xml
/3608	GEISA Platform Component Monitoring	1.0	3608.xml

The Wi-SUN Radio Management /3603 definition and version are pending coordination with the Wi-SUN work and must be resolved before release.

11.1.2. GEISA ADM Object Model

GEISA ADM uses LwM2M as the interoperable management protocol and OMA objects as the management resource model. LwM2M defines the mechanisms used by an EMS and a GEISA platform to discover objects, read resources, write configuration, execute operations, and observe resources for notifications.

GEISA ADM conformance is separate from GEISA API, LEE, and VEE conformance. ADM object requirements therefore apply in the context of ADM conformance and the relevant platform capability. They do not imply that every GEISA device implements every GEISA API, every execution environment, or every optional hardware capability. ADM implementations MAY provide alternate or additional mechanisms for device, platform, or application management. Such mechanisms do not replace the GEISA ADM requirements; an implementation claiming GEISA ADM conformance SHALL support the applicable LwM2M interfaces, operations, Objects, Resources, and behaviors defined by this specification.

The host is not the GEISA Platform. The GEISA Platform is not an application. A conformant ADM system needs enough visibility into all three scopes to manage the device, operate the platform, and monitor applications consistently.

ADM implementations should keep these distinct:

• Host / Device

  The physical or logical device, including CPU, memory, storage, network interfaces, firmware, power, location, connectivity, and other device-level resources.

• GEISA Platform

  The platform implementation that enables GEISA behavior on the device, including the EMA or equivalent management functions, LwM2M client, GEISA API services, MQTT broker, app message bridge, local monitoring engine, event/log service, policy enforcement, and queue or spool handling.

• Application

  An edge application instance running inside the LEE or VEE and subject to manifest-driven permissions, resource limits, lifecycle controls, and application-specific state.

The following list summarizes the GEISA-relevant LwM2M object model. The list describes object purpose and boundaries only. The detailed resource definitions, mandatory resource flags, data types, operations, and versioning are defined by the corresponding OMA object XML files and GEISA object definitions.

• /0 Security

  Scope: ADM baseline

  Provides LwM2M security configuration and credentials required for secure ADM operation.

• /1 Server

  Scope: ADM baseline

  Provides LwM2M server configuration, registration lifetime, binding, and related server behavior.

• /3 Device

  Scope: Host / Device

  Provides device identity, firmware and hardware details, time, reboot, factory reset, storage/memory, and device-level error state. This object is for device-level information and controls, not application lifecycle, app messages, or app accounting.

• /4 Connectivity Monitoring

  Scope: Host / Device

  Provides current network bearer and connectivity visibility. This object provides context for management connectivity and app-facing connectivity status, but it does not define application permissions or per-application quota state.

• /5 Firmware Update

  Scope: Host / Device

  Provides the platform firmware update workflow. The application package lifecycle remains under Software Management /9 and is not part of Firmware Update.

• /6 Location

  Scope: conditional host / device capability

  Provides device or platform location when GPS, GNSS, or provisioned location is available through ADM.

• /9 Software Management

  Scope: application lifecycle

  Provides application package download, install, activation, execution state where supported, uninstall, and purge behavior.

• /10 Cellular Network Connectivity

  Scope: conditional network capability

  Provides cellular network and module behavior where cellular capability is present.

• /11 APN Connection Profile

  Scope: conditional network capability

  Provides APN profile configuration and state. APN counters are bearer or profile-level data and do not replace GEISA per-application accounting.

• /12 WLAN Connectivity

  Scope: conditional network capability

  Provides Wi-Fi interface configuration, state, and counters where WLAN capability is present.

• /13 Bearer Selection

  Scope: conditional network capability.

  Provides bearer preference and selection policy where bearer selection is supported. This object does not replace GEISA app-message priority, TTL, or per-application accounting.

• /20 Event Log

  Scope: durable records

  Provides durable event, log, audit, diagnostic, platform, and application records. Current state should be exposed through the relevant monitoring objects; durable history belongs here.

• /504 Remote SIM Provisioning

  Scope: conditional network capability.

  Provides eSIM or eUICC profile lifecycle and remote SIM provisioning where supported.

• /3600 GEISA App Messaging

  Scope: application / EMS bridge

  Provides an app-scoped messaging exchange and defaults surface for a specific application or application instance. It is intended for application-facing message configuration and transport metadata, not durable event history, accounting, runtime health, or platform configuration.

  Resource 4050 AppID is a system-unique identifier for the logical application within the applicable management domain. Resource 4051 Software Instance links to the corresponding LwM2M Software Management /9 instance for the installed application.

• /3601 GEISA Host Monitoring

  Scope: Host / Device

  Provides host-level monitoring information used by the GEISA platform, including CPU, memory, storage, process, scheduler, and network interface observability. It also reports the aggregate monitoring state of the host environment, the reason for that state, optional diagnostic detail, and the time of the last state transition. This object is not specific to the EMA or GEISA Platform services.

• /3602 GEISA App Accounting

  Scope: application accounting

  Provides operations-facing application accounting and policy summary state for an application or application accounting scope. It exposes current-period usage counters, quotas and limits, throttle, block, or disabled state, selected enforcement evidence, operator or EMS/ADM action resources, and application or accounting-scope operational monitoring.

  Multiple AppAccounting object instances may exist for the same AppID, Accounting Class, and Accounting Scope to expose different accounting windows such as configured collection period, daily, since-reboot, rolling-window, lifetime, or operator-defined accounting.

• /3603 GEISA Wi-SUN Radio Management

  Scope: conditional network capability

  Provides Wi-SUN radio and interface management for Wi-SUN-capable platforms.

• /3604 GEISA App Monitoring

  Scope: application runtime

  Provides app-scoped runtime monitoring and health visibility. It represents the platform view of one installed or running application instance. This Object reports the platform’s runtime lifecycle view, current application monitoring state, exit history, resource consumption, restart behavior, watchdog state, and platform actions.

• /3605 GEISA Platform Monitoring

  Scope: GEISA Platform

  This Object represents the platform’s aggregate monitoring view. Values may be produced from bounded read-time checks, cached local checks, platform status snapshots, or retained platform telemetry.

  This Object is intended for authoritative aggregate platform monitoring together with upstream communication, queue, API, and event telemetry, but does not require continuous telemetry collection. It does not imply a specific daemon, service, process, or engine architecture.

• /3606 GEISA Platform Effective Configuration

  Scope: GEISA Platform

  This Object captures the effective GEISA Platform configuration for an edge device and the reconciliation status of the most recently evaluated requested configuration. An EMS can compare the Effective Configuration Hash with the requested configuration hash before deciding whether a larger Object read is needed.

  Before the first runtime configuration update, this Object represents the effective configuration corresponding to the System Owner-approved requested baseline represented by Object 3607. The platform generates the initial Effective Configuration Revision and computes the Effective Configuration Hash.

• /3607 GEISA Platform Requested Configuration

  Scope: GEISA Platform

  This LwM2M Object reports the GEISA Platform configuration requested by an EMS or operator for an edge device. Writable requested configuration resources express the desired configuration, and the platform computes and exposes the Requested Configuration Hash after accepting or updating those values. Object 3606 reports the effective result. Each configuration resource follows its defined Mandatory or Optional status. Optional resources depend on supported capabilities.

• /3608 GEISA Platform Component Monitoring

  Scope: logical component monitoring

  This optional Object provides logical component monitoring state for GEISA-capable platform functions, services, queues, APIs, and operational paths. Each Object Instance represents one logical component, service, function, or operational path used by the implementation to realize the relevant platform requirements.