ETSI TR 104 411 V1.1.1 (2026-07)
Data Solutions (DATA); Pandesys use cases and requirements
General Information
- Abstract
DTR/DATA-00104411
- Status
- Not Published
- Technical Committee
- DATA - Data Solutions
- Current Stage
- 12 - Citation in the OJ (auto-insert)
- Due Date
- 15-Jul-2026
- Completion Date
- 17-Jul-2026
Frequently Asked Questions
ETSI TR 104 411 V1.1.1 (2026-07) is a standard published by the European Telecommunications Standards Institute (ETSI). Its full title is "Data Solutions (DATA); Pandesys use cases and requirements". This standard covers: DTR/DATA-00104411
DTR/DATA-00104411
ETSI TR 104 411 V1.1.1 (2026-07) 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 REPORT
Data Solutions (DATA);
Pandesys use cases and requirements
2 ETSI TR 104 411 V1.1.1 (2026-07)
Reference
DTR/DATA-00104411
Keywords
ACT, IoT, semantic, use cases
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 of this document may be reproduced in any form, by any means and in any media, without the prior written
authorization of ETSI and except as expressly permitted below.
By way of exception and when the document is a normative deliverable (European Standard (EN),
Technical Specification (TS), Group Specification (GS) or ETSI Standard (ES)), ETSI authorizes to reproduce
and incorporate into products, services and technical documentation only those extracts (e.g. templates) that are strictly
necessary for the technical implementation of the normative deliverable, to ensure compliance with the latter.
Nothing in this notice shall be construed as limiting any mandatory exceptions to copyright provided by applicable law.
© ETSI 2026.
All rights reserved.
ETSI
3 ETSI TR 104 411 V1.1.1 (2026-07)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 6
3.1 Terms . 6
3.2 Symbols . 6
3.3 Abbreviations . 7
4 Background . 7
4.1 Motivation . 7
4.2 Objective of the use case analysis . 8
5 Use Cases . 9
5.1 Health Care Use Case . 9
5.1.1 Use Case A.1: Adoption of an AI-based system for supporting citizens . 9
5.1.1.1 Description . 9
5.1.1.2 Source . 9
5.1.1.3 Actors . 9
5.1.1.4 Pre-conditions . 9
5.1.1.5 Triggers . 9
5.1.1.6 Normal Flow . 10
5.1.1.7 Alternative Flow . 10
5.1.1.8 Post-conditions . 10
5.1.1.9 High Level Illustration . 10
5.1.1.10 Use case analysis . 11
5.2 Public and Emergency Services Use Cases . 11
5.2.1 Use Case B.1: Detection of emergency signals from IoT device . 11
5.2.1.1 Description . 11
5.2.1.2 Source . 11
5.2.1.3 Actors . 11
5.2.1.4 Pre-conditions . 12
5.2.1.5 Triggers . 12
5.2.1.6 Normal flow . 12
5.2.1.7 Alternative flow . 12
5.2.1.8 Post-conditions . 12
5.2.1.9 High Level Illustration . 13
5.2.1.10 Use case analysis . 13
5.2.2 Use Case B.3: Cooperative Fog Services with Drones . 13
5.2.2.1 Description . 13
5.2.2.2 Source . 14
5.2.2.3 Actors . 14
5.2.2.4 Pre-conditions . 15
5.2.2.5 Triggers . 15
5.2.2.6 Normal Flow . 15
5.2.2.7 Alternative Flow . 16
5.2.2.8 Post-conditions . 16
5.2.2.9 High Level Illustration . 17
5.2.2.10 Use case analysis . 17
5.3 Agriculture and Farming . 17
5.3.1 Use Case E.1: Fertilization/Irrigation/Pest management service . 17
5.3.1.1 Description . 17
5.3.1.2 Source . 18
ETSI
4 ETSI TR 104 411 V1.1.1 (2026-07)
5.3.1.3 Actors . 18
5.3.1.4 Pre-conditions . 18
5.3.1.5 Triggers . 18
5.3.1.6 Normal flow . 18
5.3.1.7 Alternative flow . 18
5.3.1.8 Post-conditions . 18
5.3.1.9 High Level Illustration . 19
5.3.1.10 Use case analysis . 19
5.4 Smart Cities use cases . 19
5.4.1 Use Case L.1: Smart Lightning . 19
5.4.1.1 Description . 19
5.4.1.2 Source . 20
5.4.1.3 Actors . 20
5.4.1.4 Pre-conditions . 20
5.4.1.5 Triggers . 20
5.4.1.6 Normal flow . 20
5.4.1.7 Alternative flow . 21
5.4.1.8 Post-conditions . 21
5.4.1.9 High Level Illustration . 21
5.4.1.10 Use case analysis . 21
5.5 ROP - UxV Patrolling . 21
5.5.1 Description . 21
5.5.2 Source . 21
5.5.3 Actors . 21
5.5.4 Pre-conditions . 22
5.5.5 Triggers . 22
5.5.6 Normal Flow (alarm) . 22
5.5.7 Alternative Flow (low/hot interest) . 22
5.5.8 Alternative Flow 2 . 22
5.5.9 Post-conditions . 22
5.5.10 High Level Illustration (Normal Flow) . 23
6 Conclusions . 23
History . 24
ETSI
5 ETSI TR 104 411 V1.1.1 (2026-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables (European Standard (EN), Technical Specification (TS),
Group Specification (GS) or ETSI Standard (ES)) 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 Report (TR) has been produced by ETSI Technical Committee Data Solutions (DATA).
Modal verbs terminology
In the present document "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
6 ETSI TR 104 411 V1.1.1 (2026-07)
1 Scope
The present document identifies meaningful eco-bio emergencies use cases that cannot be captured by ETSI
TS 103 757 [i.3] using oneM2M as the IoT inter-connexion framework. In particular real-time, forecasting, and identity
issues will be focused.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
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] ETSI TR 103 533: "SmartM2M; Security; Standards Landscape and best practices".
[i.2] ETSI TR 103 591: "SmartM2M; Privacy study report; Standards Landscape and best practices".
[i.3] ETSI TS 103 757: "SmartM2M; Asynchronous Contact Tracing System; Fighting pandemic
disease with Internet of Things (IoT)".
[i.4] ETSI TR 103 509: "SmartM2M; SAREF extension investigation; Requirements for
eHealth/Ageing-well".
[i.5] ETSI TR 103 510: "SmartM2M; SAREF extension investigation; Requirements for Wearables".
[i.6] ETSI TR 103 582: "EMTEL; Study of use cases and communications involving IoT devices in
provision of emergency situations".
[i.7] ETSI TR 118 501: "oneM2M Use Case collection".
[i.8] Luigi Liquori and Egan Perais: "oneM2M Executive Viewpoint series: interview Luigi Liquori
(Inria)".
3 Definition of terms, symbols and abbreviations
3.1 Terms
Void.
3.2 Symbols
Void.
ETSI
7 ETSI TR 104 411 V1.1.1 (2026-07)
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACT Asynchronous Contact Tracing
AI Artificial Intelligence
IoT Internet of Things
PAMAC Patrolling and Monitoring Administration Centre
ROV Remoted Operated Vehicles
UxV Unmanned x Vehicles
4 Background
4.1 Motivation
ETSI TS 103 757 [i.1] (Asynchronous Contact Tracing (ACT)) was conceived in opposition with synchronous contact
tracing protocols, the latter tracking two individuals on the basis of the anonymous transmission of the identities of two
mobile phones staying in the range of 2 meters for at least 15 minutes, but relying on the fact the one of the two
individual, when infected, notifies its illness to the tracking system, notification that was largely disattended because of
social fears.
ACT takes the contact tracing from another point that could be resumed as follows:
1) using IoT sensors to record viruses, called Detection Services;
2) equip them with a uniquely identified ID; ®
3) broadcast the ID using a Peripheral Service (e.g. Wi-Fi transmitter); and
4) communicate the virus results to a Base Control Station Service thought an intermediary Local Service to load
balance the message charge.
An human, usually equipped with a smartphone in its pocket, can continuously listen and record the IDs related with the
position he visited, but he will never communicate anytime anywhere such information (hence its name, asynchronous).
The user can at any time query the Base Control Station Service about the virus status in a geographic area recorded by
one or more ID-Detection Service and eventually match those IDs with the footprint recorded in its Smart Mobile
Application: in case of non-empty intersection, he will take countermeasures.
Figure 4.1-1 resume the mapping of ACT in the common oneM2M framework.
ETSI
8 ETSI TR 104 411 V1.1.1 (2026-07)
Figure 4.1-1: Mapping of the ACT Architecture in the common oneM2M Framework
4.2 Objective of the use case analysis
The use cases presented in clause 5 are collected from real life scenarios, industries, and practices. What the present
document presents is the analysis of these use cases from the "use of data generated" viewpoint concerning their
exploitation within an ACT system.
The domain areas covered by the use cases in clause 5 are as follows:
• Health Care.
• Public and Emergency Services.
• Industry and Manufacturing.
• Agriculture and Farming.
• Energy.
• Smart Cities.
• Patrolling.
Many of the use cases may also trigger concerns about the privacy of the IoT data and the cyber-security of the related
devices and processes. These topics are addressed in details in ETSI TR 103 533 [i.1] and ETSI TR 103 591 [i.2]. The
present document considers that both issues, when relevant to the use cases of clause 5, have been addressed separately
and resolved.
ETSI
9 ETSI TR 104 411 V1.1.1 (2026-07)
5 Use Cases
5.1 Health Care Use Case
5.1.1 Use Case A.1: Adoption of an AI-based system for supporting
citizens
5.1.1.1 Description
• Citizens may be exposed to communicable disease pathogens that may affect their health.
• A user may need to know if she passed through a certain area during a specific timeframe.
• IoT network detects the presence of specific pathogens.
• A user should be able to provide anonymous information concerning the presence of a specific pathogen
within a given area.
• A user should be able to define a geographical area and a time period and then to search for data related to
such area-time combination.
5.1.1.2 Source
• ETSI TR 103 509 [i.4].
• ETSI TR 103 510 [i.5].
5.1.1.3 Actors
• [Human] Physicians.
• [Human] Citizens.
• [Human] Users.
• [Machine] AI engine: which is in charge of acquiring data explicitly provided by users and/or acquired
through sensors. The AI engine applies a strategy (e.g. statistical, symbolic, or mixed) for verifying the
compliance of acquired data with respect to the guidelines and monitoring rules defined by physicians.
• Data user/consumer: Physicians, Patients, Users, AI engine.
5.1.1.4 Pre-conditions
• The physicians' monitoring platform, the patients' and users' smartphone applications, and the IoT devices are
deployed and in operational condition.
• The AI engine services are up and running.
5.1.1.5 Triggers
• The AI engine detects a set of data that is not compliant with respect to the guidelines that a given physician
assigned to a specific user.
• The AI engine detects a set of data highlighting a potentially dangerous situation in a patient affected by a
specific disease.
ETSI
10 ETSI TR 104 411 V1.1.1 (2026-07)
5.1.1.6 Normal Flow
• The user (or the patient) provides data about consumed food and performed activity through the use of mobile
application and/or devices like smartwatches.
• The system stores the data into a knowledge graph and performs reasoning activities for detecting potential
undesired behaviours by matching user's (or the patient's) data with the guidelines provided in advance by the
physician.
• If an undesired behaviour is detected, the user (or the patient) is alerted about the undesired event together
with the related explanation.
• Together with the user (or the patient), the physician is alerted as well in order to make her aware about the
violated guideline.
• The system keeps track of the event and updates the policies used for generating the next feedback in the case
that the same undesired event would be detected.
5.1.1.7 Alternative Flow
None.
5.1.1.8 Post-conditions
The physician and the patient (or the user) are informed about the dangerous (or undesired) situation through the
notification manager integrated within the AI engine.
5.1.1.9 High Level Illustration
Figure 5.1.1.9-1: High level illustration of the described use case
ETSI
11 ETSI TR 104 411 V1.1.1 (2026-07)
5.1.1.10 Use case analysis
Clause 5.1.1.1 provides an extensive description of the use case.
Here, the focus is on the risks connected with the amount of data provided by both patients (or users) and IoT devices to
the AI engine.
Data that may compromise data usability:
• Data provided explicitly by users.
• Data provided by IoT devices.
Indeed, the adoption of IoT technology can create new safety risks if it is not designed appropriately, implemented
carefully, and used thoughtfully. Data integrity errors as a result of incorrect or missing data in the patients' Electronic
Health Records (EHRs) and other health IT systems are a crucial issue in the healthcare sector that can dramatically
affect patients (and users) health. Data integrity issues occurred with the use of paper medical records as well, but now,
as EHRs become more interoperable and hackable, incorrect information is more readily available, more easily shared,
and harder to eliminate. One patient's data appearing in another patient's record, missing data or delayed data delivery,
and clock synchronization errors between medical devices and systems are examples of data integrity failures.
These issues can lead to wrong inference or classification outcomes by the AI engine
...



