Data Solutions (DATA); Extension to SAREF; Part 15: Device Management Domain

DTS/DATA-00103410-15

General Information

Status
Not Published
Technical Committee
DATA - Data Solutions
Current Stage
12 - Citation in the OJ (auto-insert)
Due Date
01-May-2026
Completion Date
26-May-2026

Buy Documents

Standard

ETSI TS 103 410-15 V1.1.1 (2026-05) - Data Solutions (DATA); Extension to SAREF; Part 15: Device Management Domain

English language (38 pages)
sale 15% off
Preview
sale 15% off
Preview

Buy Documents

Standard

ETSI TS 103 410-15 V1.1.1 (2026-05) - Data Solutions (DATA); Extension to SAREF; Part 15: Device Management Domain

English language (38 pages)
sale 15% off
Preview
sale 15% off
Preview

Frequently Asked Questions

ETSI TS 103 410-15 V1.1.1 (2026-05) is a standard published by the European Telecommunications Standards Institute (ETSI). Its full title is "Data Solutions (DATA); Extension to SAREF; Part 15: Device Management Domain". This standard covers: DTS/DATA-00103410-15

DTS/DATA-00103410-15

ETSI TS 103 410-15 V1.1.1 (2026-05) is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


TECHNICAL SPECIFICATION
Data Solutions (DATA);
Extension to SAREF;
Part 15: Device Management Domain

2 ETSI TS 103 410-15 V1.1.1 (2026-05)

Reference
DTS/DATA-00103410-15
Keywords
IIoT, IoT, IoT platforms, management, ontology,
SAREF, semantic
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2026.
All rights reserved.
ETSI
3 ETSI TS 103 410-15 V1.1.1 (2026-05)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definition of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 9
3.3 Abbreviations . 9
4 SAREF4DMGT ontology and semantics . 10
4.1 Introduction and overview . 10
4.2 SAREF4DMGT . 12
4.2.1 Introduction. 12
4.2.2 Domain resources . 13
4.2.2.1 General overview . 13
4.2.2.2 Manageable Device . 14
4.2.2.3 Client . 14
4.2.2.4 Server . 15
4.2.2.5 Management Connection . 15
4.2.2.6 Management Service . 15
4.2.3 DM Capabilities . 15
4.2.3.1 General overview . 15
4.2.3.2 Identity . 15
4.2.3.3 Firmware . 16
4.2.3.4 Package . 16
4.2.3.5 Module . 17
4.2.3.6 Device Control . 18
4.2.4 Datamodels, technical representation of capabilities . 18
4.2.4.1 General overview . 18
4.2.4.2 Supported datamodel . 19
4.2.4.3 Datamodel parameters . 19
Annex A (informative): Bibliography . 21
Annex B (normative): Ontology Reference . 22
B.1 Classes . 22
s4dmgt:Client — Client . 22
s4dmgt:DatamodelParameterCommandCategory — Datamodel Parameter Command Category . 22
s4dmgt:DeviceControlCommandCategory — Device Control Command Category . 22
s4dmgt:DeviceIdentityCommandCategory — Device Identity Command Category . 22
s4dmgt:DeviceManagementCommandCategory — Device Management Command Category . 23
s4dmgt:DeviceManagementFunctionCategory — Device Management Function Category . 23
s4dmgt:DeviceManagementState — Device Management State . 23
s4dmgt:DeviceModule — Device Module . 23
s4dmgt:DeviceModuleState — Device Module State . 23
s4dmgt:DevicePackage — Device Package . 24
s4dmgt:DevicePackageState — Device Package State . 24
s4dmgt:FirmwareManagementCommandCategory — Firmware Management Command Category . 24
s4dmgt:ManageableDevice — Manageable Device . 24
s4dmgt:ManagementConnection — Management Connection . 24
s4dmgt:ManagementService — Management Service . 25
s4dmgt:ModuleManagementCommandCategory — Module Management Command Category . 25
ETSI
4 ETSI TS 103 410-15 V1.1.1 (2026-05)
s4dmgt:PackageManagementCommandCategory — Package Management Command Category . 25
s4dmgt:Server — Server . 25
s4dmgt:SupportedDatamodelCommandCategory — Supported Datamodel Command Category . 26
B.2 Object Properties . 26
s4dmgt:connectedToServer — connected to server . 26
s4dmgt:enablesDeviceModule — enables device module . 26
s4dmgt:enablesManagementService — enables management service . 26
s4dmgt:hasConnectedClient — has connected client . 26
s4dmgt:hasConnection — has connection . 27
s4dmgt:hasDevicePackage — has device package. 27
s4dmgt:isRepresentedBy — is represented by . 27
s4dmgt:representsDevice — represents device . 27
B.3 Named Individuals . 27
s4dmgt:DatamodelParameterCreationCommand — Datamodel parameter creation command. 27
s4dmgt:DatamodelParameterDeletionCommand — Datamodel parameter deletion command. 27
s4dmgt:DatamodelParameterFunction — Datamodel parameter function . 28
s4dmgt:DatamodelParameterInstanceName — Datamodel parameter instance name . 28
s4dmgt:DatamodelParameterInstanceProperty — Datamodel parameter instance property . 28
s4dmgt:DatamodelParameterInstanceValue — Datamodel parameter instance value . 28
s4dmgt:DatamodelParameterOperateCommand — Datamodel parameter operate command . 28
s4dmgt:DatamodelParameterRetrievalCommand — Datamodel parameter retrieval command . 29
s4dmgt:DatamodelParameterUpdateCommand — Datamodel parameter update command . 29
s4dmgt:DeviceControlFunction — Device control function . 29
s4dmgt:DeviceIdentityFunction — Device identity function . 29
s4dmgt:DeviceIdentityProperty — Device identity property . 29
s4dmgt:DeviceInfoRetrievalCommand — Device info retrieval command. 29
s4dmgt:DeviceModuleActivated — Device module activated . 29
s4dmgt:DeviceModuleDeactivated — Device module deactivated . 30
s4dmgt:DevicePackageDownloaded — Device package downloaded. 30
s4dmgt:DevicePackageDownloading — Device package downloading . 30
s4dmgt:DevicePackageInitialized — Device package initialized . 30
s4dmgt:DevicePackageInstalled — Device package installed . 30
s4dmgt:DevicePackageInstalling — Device package installing . 30
s4dmgt:DevicePackageUninstalling — Device package uninstalling . 31
s4dmgt:DevicePackageValidated — Device package validated . 31
s4dmgt:FirmwareInformationRetrievalCommand — Firmware information retrieval command . 31
s4dmgt:FirmwareManagementFunction — Firmware management function . 31
s4dmgt:FirmwareProperty — Firmware property . 31
s4dmgt:FirmwareUpdateCommand — Firmware update command . 31
s4dmgt:FirmwareVersion — Firmware version . 32
s4dmgt:HardwareVersion — Hardware version . 32
s4dmgt:Manufacturer — Manufacturer . 32
s4dmgt:ModelName — Model name . 32
s4dmgt:ModelNumber — Model number . 32
s4dmgt:ModuleActivationCommand — Module activation command . 32
s4dmgt:ModuleDeactivationCommand — Module deactivation command . 32
s4dmgt:ModuleDiscoveryCommand — Module discovery command . 33
s4dmgt:ModuleInformationRetrievalCommand — Module information retrieval command . 33
s4dmgt:ModuleManagementFunction — Module management function . 33
s4dmgt:ModuleName — Module name . 33
s4dmgt:ModuleProperty — Module property . 33
s4dmgt:ModuleVersion — Module version . 33
s4dmgt:PackageCreationCommand — Package creation command . 33
s4dmgt:PackageDeletionCommand — Package deletion command . 34
s4dmgt:PackageDiscoveryCommand — Package discovery command. 34
s4dmgt:PackageDownloadCommand — Package download command . 34
s4dmgt:PackageInformationRetrievalCommand — Package information retrieval command . 34
s4dmgt:PackageInstallCommand — Package install command . 34
s4dmgt:PackageManagementFunction — Package management function . 34
s4dmgt:PackageName — Package name . 34
ETSI
5 ETSI TS 103 410-15 V1.1.1 (2026-05)
s4dmgt:PackageProperty — Package property . 35
s4dmgt:PackageUninstallCommand — Package uninstall command . 35
s4dmgt:PackageUpdateCommand — Package update command . 35
s4dmgt:PackageVersion — Package version . 35
s4dmgt:RebootCommand — Reboot command . 35
s4dmgt:ResetCommand — Reset command . 35
s4dmgt:SerialNumber — Serial number . 35
s4dmgt:SupportedDatamodelFunction — Supported datamodel function . 36
s4dmgt:SupportedDatamodelParameterName — Supported datamodel parameter name . 36
s4dmgt:SupportedDatamodelParameterPrimitives — supported datamodel parameter primitives . 36
s4dmgt:SupportedDatamodelParameterProperty — Supported datamodel parameter property . 36
s4dmgt:SupportedDatamodelParameterType — Supported datamodel parameter type . 36
s4dmgt:SupportedDatamodelRetrievalCommand — Supported datamodel retrieval command . 37
History . 38

ETSI
6 ETSI TS 103 410-15 V1.1.1 (2026-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Data Solutions (DATA).
The present document is part 15 of a multi-part deliverable covering Data Solutions (DATA); Extension to SAREF, as
identified below:
Part 1: "Energy Domain";
Part 2: "Environment Domain";
Part 3: "Building Domain";
Part 4: "Smart Cities Domain";
Part 5: "Industry and Manufacturing Domains";
Part 6: "Smart Agriculture and Food Chain Domain";
Part 7: "Automotive Domain";
Part 8: "eHealth/Ageing-well Domain";
Part 9: "Wearables Domain";
Part 10: "Water Domain";
Part 11: "Lift Domain";
Part 12: "Smart Grid Domain";
Part 13: "Maritime Domain";
Part 14: "Thermal Energy Storage Systems Domain";
ETSI
7 ETSI TS 103 410-15 V1.1.1 (2026-05)
Part 15: "Device Management Domain".
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
8 ETSI TS 103 410-15 V1.1.1 (2026-05)
1 Scope
The present document presents SAREF4DMGT, the SAREF extension for Device Management.
Device Management (DM) refers to the remote administration of devices by operators, such as service providers or
manufacturers, to ensure proper functioning, configuration, and support, especially as the scope has expanded with the
rise of IoT.
The architecture of device management for operators typically involves DM clients embedded in devices, which expose
management functions, and DM servers operated by service providers, which coordinate and execute commands to
manage and configure devices remotely.
The emergence of numerous heterogeneous IoT devices and proprietary, siloed management solutions has created a
new problem: the need for federating multiple device management systems to achieve interoperability across diverse
protocols and device capabilities.
In the Device Management domain, federation refers to the ability to coordinate and execute commands across multiple
heterogeneous systems.
To achieve this federation, the current scope of the Ontology comprises three items:
• The representation of the device management capabilities of a device, with their associated functions and
commands.
• The representation of the information needed to select which command to execute on a device for a targeted
function.
• The representation of the information retrievable from the device and exposed by the DM server.
The proposed ontology defines the required entities, extending the concepts from the SAREF v4.1.1 ontology.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 103 264: "SmartM2M; Smart Applications; Reference Ontology and oneM2M
Mapping".
[2] ETSI TS 103 548: "SmartM2M; SAREF reference ontology patterns".
[3] ETSI TS 103 673: "SmartM2M; SAREF Development Framework and Workflow, Streamlining
the Development of SAREF and its Extensions".
[4] BBF TR-069 Amendment 6 Corrigendum 1: "Broadband Forum, CPE WAN Management
Protocol".
[5] BBF TR-181 Issue 2 Amendment 20 Corrigendum 1: "oneM2M TR-181 Device Data Model for
CWMP Endpoints and USP Agents".
ETSI
9 ETSI TS 103 410-15 V1.1.1 (2026-05)
[6] BBF TR-369 Issue 1 Amendment 4 Corrigendum 2: "Broadband Forum, The User Services
Platform".
[7] OMA-TS-LightweightM2M_Core-V1_2_2-20240613-A: "Lightweight Machine to Machine
Technical Specification: Core".
[8] oneM2M TS-0001 (v4.24.0): "Functional Architecture".
[9] oneM2M TS-0005 (v4.0.3): "Management Enablement (OMA)".
[10] oneM2M TS-0006 (v4.0.1): "Management Enablement (BBF)".
[11] oneM2M TS-0014: (v4.0.1) "LwM2M Interworking".
[12] oneM2M TS-0023 (v5.7.0): "SDT based Information Model and Mapping for Vertical Industries",
(section 5.8 Device Management).
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
[i.1] Open Mobile Alliance: "LwM2M Registries, objects and resources".
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ETSI TS 103 673 [3] and the following apply:
ontology: formal specification of a conceptualization, used to explicit capture the semantics of a certain reality
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
API Application Programming Interface
BBF BroadBand Forum
CWMP Customer Premises Equipment Wide Area Network Management Protocol
DM Device Management
IoT Internet of Things
IRI Internationalized Resource Identifier
LwM2M LightWeight Machine-to-Machine
OMA Open Mobile AllianceOWL Web Ontology Language
OWL-DL Web Ontology Language Description Logics
SAREF Smart Applications REFerence ontology
SAREF4DMGT SAREF extension for Device Management
ETSI
10 ETSI TS 103 410-15 V1.1.1 (2026-05)
RDF Resource Description Framework
TCP Transmission Control Protocol
TTL Terse RDF Triple Language (Turtle)
UML Unified Modeling Language
USP User Services Platform
4 SAREF4DMGT ontology and semantics
4.1 Introduction and overview
The objective of SAREF4DMGT is to extend the SAREF ontology (see ETSI TS 103 264 [1]) for the Device
Management (DM) domain. Clause 4.1 of the present document shortly introduces a high-level view of the envisioned
SAREF4DMGT semantic model, with the retained concepts (i.e. classes) and their relations.
The Device Management (DM) domain consists in the remote administration of devices for an operator, such as a
service provider or device manufacturer.
The proposal for an ontology for standardization in Device Management is motivated by the need to address challenges
arising from the evolution of DM and the emergence of the Internet of Things (IoT).
Initially, DM was introduced by manufacturers and telecommunication operators to ensure the proper functioning of
devices like gateways and set-top boxes, focusing on firmware management due to the high replacement costs of these
devices. Over time, the scope of DM expanded to include configuration and customer care, enabling Telcos to configure
value-added services, improve Quality of Service, and reduce costs.
With the rise of the IoT, the DM landscape has shifted significantly. The proliferation of heterogeneous IoT devices and
the temptation to produce disposable devices have highlighted the need for remote management for economic and
ecological reasons. However, existing DM solutions face challenges due to the scale and diversity of IoT devices, as
well as the prevalence of proprietary protocols and siloed solutions from various manufacturers. This has created issues
with heterogeneity in device capabilities, DM protocols, and management solutions.
Standardization becomes essential to simplify device integration and DM operations, benefiting both operators and
manufacturers.
The proposed IoT Device Management Ontology provides an abstract semantic model of DM domain-specific concepts,
enabling cross-system data interoperability and knowledge enrichment through reasoning. This ontology aims to unify
and streamline IoT DM practices, overcoming the limitations of existing approaches.
Therefore, the SAREF4DMGT ontology shall allow:
• The representation of the device management capabilities of a device, with their associated functions and
commands.
• The representation of the information needed to select which command to execute on a device for a targeted
function.
• The representation of the information retrievable from the device and exposed by the DM server.
The SAREF4DMGT extension has been specified and formalized by investigating Device Management standard
protocols, such as BBF CWMP [4], BBF USP [5], oneM2M [6] or OMA LwM2M [7].
SAREF4DMGT mainly reuses the SAREF ontology (see ETSI TS 103 264 [1]) and is developed according to the
SAREF Development Framework and Workflow (see ETSI TS 103 673 [3]).
.
The SAREF4DMGT ontology is fully specified and formalized in Clause 4.2 of the present document. Figure 1 presents
the high-level view of the envisioned model of SAREF4DMGT ontology. In Figure 1, classes directly imported from
the SAREF ontology are in yellow, classes specifically developed for SAREF4DMGT are in blue.
ETSI
11 ETSI TS 103 410-15 V1.1.1 (2026-05)

Figure 1: High level view of the envisioned semantic model for the SAREF4DMGT ontology
Within Figure 1, as well as within all the figures that are depicted in Clause 4 of the present document, the following
conventions are used:
• arrows are used to represent properties between classes and to represent some RDF, RDF-S and OWL
constructs, more precisely:
- plain arrows with white triangles represent the rdfs:subClassOf relation between two classes. The origin
of the arrow is the class to be declared as subclass of the class at the destination of the arrow;
- dashed arrows between two classes indicate a local restriction in the origin class, i.e. that the object
property can be instantiated between the classes in the origin and the destination of the arrow. The
identifier of the object property is indicated within the arrow;
- dashed arrows with no identifier are used to represent the rdf:type relation, indicating that the element in
the origin of the arrow is an instance of the class in the destination of the arrow;
• datatype properties are denoted by rectangles attached to the classes, in an UML-oriented way. Dashed boxes
represent local restrictions in the class, i.e. datatype properties that can be applied to the class they are attached
to;
• individuals are denoted by rectangles in which the identifier is underlined.
ETSI
12 ETSI TS 103 410-15 V1.1.1 (2026-05)
SAREF4DMGT is extending the SAREF ontology for the Device Management domain and thus shall logically mainly
model the following concepts (i.e. classes within Figure 1):
• Manageable Device: A tangible object that has at least one Device Management Function. This class extends
the saref:Device class, it is a Feature of Interest by definition.
• Server: A DM Server is the software entity which is responsible for performing DM operations on a fleet of
Devices. It exposes the set of available operations to an entity that needs to trigger an operation, such as a
manufacturer or a Customer Care service. The DM Server is a endpoint, generally secured, with which DM
Clients communicate. The protocol used between Server and Client is not in the scope of this ontology. It can
follow a DM standard such as CWMP or LwM2M, or be completely proprietary.
• Client: Software entity which represents a Device by exposing its DM Functions to one or more DM Server(s).
It is responsible for the triggering of the DM Functions when a Command targeting the represented Device is
received by the Server. The Client is also responsible for the reporting of the results of the Function execution
to the Server. The Client has an identifier that is unique only relatively to each Server it is connected to.
• Device Management Capabilities: these capabilities are represented through categories of saref:Function and
saref:Command. These capabilities rely on a set of high-level DM-specific device resources, namely the
identity, firmware, packages, and modules. These resources can be manipulated through lower-level
representations, namely the Supported Datamodel, and the Datamodel Parameters:
- Device Management Function Category: Category of saref:Function corresponding to the capabilities of
the Device to perform its own diagnostics, maintenance, configuration, monitoring and control.
- Device Management Command Category: Category of saref:Command associated to Device
Management Functions.
• Management Service: A saref:Service that represents functions or functions of interest of the Device
Management Function Category. The Management Service for a function only exists when a Management
Connection connects a Client and a Server that can expose this function.
• Management Connection: Abstract representation of the connection between a DM Client and a DM Server. It
does not necessarily imply that a persistent connection is established between the entities, such as a TCP
connection. It represents the link and the capability of the Server to interact with the Client. For instance, the
Client has been authenticated by the Server with a certificate, and/or the client has received a configuration for
access rights to its functions for the Server.
Table 1: Prefixes and namespaces used within the SAREF4DMGT modular ontology
Prefix Namespace
dcterms http://purl.org/dc/terms/
foaf http://xmlns.com/foaf/0.1/
owl http://www.w3.org/2002/07/owl#
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs http://www.w3.org/2000/01/rdf-schema#
s4dmgt https://saref.etsi.org/saref4dmgt/
s4syst https://saref.etsi.org/saref4syst/
saref https://saref.etsi.org/core/
skos http://www.w3.org/2004/02/skos/core#
vann http://purl.org/vocab/vann/
xml http://www.w3.org/XML/1998/namespace
xsd http://www.w3.org/2001/XMLSchema#

4.2 SAREF4DMGT
4.2.1 Introduction
As already introduced in Clause 4.1 of the present document, SAREF4DMGT is an OWL-DL ontology that describes
the domain of Device Management. To this end, multiple concepts need to be introduced.
ETSI
13 ETSI TS 103 410-15 V1.1.1 (2026-05)
First, SAREF4DMGT relies on a set of SAREF-defined concepts, which are saref:Function, saref:Command, and
saref:Service.
The Function is specialized to represent DM-specific capabilities, while the Command enables the representation of the
exposition of these DM-specific capabilities. Finally, the Service is instantiated with a DM Service, that encompasses
the set of functions related to DM.
These base concepts allow the representation of Device Management specific entities, which were extracted from the
analysis of the major standards used for Device Management by Telecommunication Operators.
For the purpose of the present document, the following standards were analysed:
• BBF CWMP: The Customer Premises Equipment Wide Area Network Management Protocol, a.k.a.
TR-069 [4], was created by the BroadBand Forum to address the Device Management requirement of
Telecommunication Operators, with a specialization on gateway fleets management. While the protocol itself
is defined in the Technical Report 069, the datamodel of devices is described in the Technical Report 181 [5].
• BBF USP: The User Services Platform [6] is the direct evolution of CWMP at the BroadBand Forum. The
core principles are updated to allow a decentralized architecture compared to CWMP, with shared
management through Access Control Lists.
• OMA LwM2M: The LightWeight Machine-to-Machine protocol [7] from the Open Mobile Alliance is a
standardized protocol for remote device management, telemetry, and secure communication in IoT
ecosystems. LwM2M enforces interoperability through standardized capabilities with registries [i.1] promoting
the reuse of resources across vendors and manufacturers.
• oneM2M: oneM2M [8] brings together all components in the IoT solution stack. It avoids reinvention in favor
of reusing existing technology components and standards. oneM2M's architecture defines a common
middleware technology in a horizontal layer between devices and communications networks and IoT
applications. This standardizes links between connected devices, gateways, communications networks and
cloud infrastructure. For the purpose of the present document, the following specifications were explored:
"Management enablement (OMA)" [9], "Management enablement (BBF)" [10], "LwM2M Interworking" [11],
and "SDT based Information Model and Mapping for Vertical Industries, section 5.8 Device Management"
[12].
The SAREF4DMGT ontology represents the set of physical and software entities involved in Device Management, such
as Manageable Device, Client, Server, Connection and Service.
The SAREF4DMGT ontology also models the following specific device capabilities to operate Device Management:
Identity, Firmware, Package, Module, Device Control.
Finally, the SAREF4DMGT ontology models the technical representation of these capabilities in the different protocols.
These capabilities are exposed as datamodels, hierarchical and technical data structures exposing parameters with their
related types and available operations, represented as primitives. Thus, two concepts are introduced: Supported
Datamodel, and Datamodel Parameters.
4.2.2 Domain resources
4.2.2.1 General overview
The Device Management domain involves the following entities: Manageable Device, Client, Server, Connection and
Service. They are necessary to enable the discovery and control of Management functions remotely for a Device
Management Operator.
ETSI
14 ETSI TS 103 410-15 V1.1.1 (2026-05)

Figure 2: Detailed view of SAREF4DMGT Domain Resources
The architecture of Device Management systems consists in a client/server architecture, where the client is responsible
for the local activation of functions, while the server is the remote, secure endpoint that enables the connection with the
Information System of the operator. The representation of this connection relies on the SAREF4SYST patterns [2].
Devices are managed as fleets as well as individuals, whether for fleet-wide campaigns such as firmware upgrades, or
specific actions, e.g. diagnostics destined to Customer Care.
While this architecture used to be centralized with a single server managing every device of the fleet, for instance with
CWMP, newer standard protocols introduce shared management of devices, with multiple actors, servers, and access
rights for each resource.
4.2.2.2 Manageable Device
Specialization of saref:Device, the s4dmgt:ManageableDevice is a saref:FeatureOfInterest that consists in a device that
supports at least one Device Management function, exposed through a command.
4.2.2.3 Client
The client of a device is a s4syst:System which exposes the DM Functions of this device to one or more DM Servers.
The relationship linking a s4dmgt:Client to the s4dmgt:Device is the s4dmgt:representsDevice object property, and its
inverse s4dmgt:isRepresentedBy.
ETSI
15 ETSI TS 103 410-15 V1.1.1 (2026-05)
A client is responsible for a single device, while a device may be managed through multiple clients.
4.2.2.4 Server
The s4dmgt:Server is a s4syst:System, hosted in the network, which is the secured endpoint with which any
s4dmgt:Client communicate. The Server is responsible for perform
...