Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.

eu/public/requirements/

Requirements
Up one level

Welcome to the IoT-A Unified Requirements list !

Preamble

Requirements in IoT-A are mainly targeted at supporting and validating the work on the Architectural Reference Model (ARM). While requirement work within the project tries to
follow requirement best practices (by using as much as possible Volere methodology, by using input from both potential end-users and developers), producing and exploiting
requirements on a Reference Architecture (and Model) level is somewhat different than for a concrete system (for which the state of the art methodology is largely targeted). This
results in a number of specifics that the reader should keep in mind:
Prioritization of requirements for the ARM is largely inapplicable – while it is largely considered best practice in concrete system specification.
Formulation (description field) of requirements expressed by external or internal stakeholder may sometimes refer directly to the ARM, but in most cases they apply to a
concrete system. In that latter case, they express characteristics on the system that the ARM should enable to specify.
Mapping to perspective/views/functional groups and components is done on a lowest common denominator basis – e.g. it indicates which aspect is definitely impacted by a
given requirement, but the reader should keep in mind that in certain (concrete system) specific cases, other components may need to be considered.

How to use this list?

The requirements are presented as a dynamic table, with the following fields for each requirement:
ID: Each requirement is uniquely identified by a three-digit number: UNI.klm. The numbering scheme indicates where requirements come from (e.g. all requirements with
klm <200 are issued from stakeholders, those with klm > 200 are either based on state of the art or about our understanding of the IoT domain, with the 600 range being
devoted to security and 700 devoted to management) and is not continuous due to discards/merges.
Requirement Type: Type of requirement among the three categories Functional Requirements / Non-Functional Requirements / Design Constraints.
Category: general keywords applicable to the requirement to ease their grouping regardless of ARM specificities (e.g. allows to tag all requirements that impact privacy
regardless of their origin)
Description: The description is the intent of the requirement. It is a statement about what the system has to fulfil according to the rationale.
Rationale: The rationale is the reason behind the requirement’s existence. It explains why the requirement is important and how it contributes to the system’s purpose. It
typically refers to direct stakeholder input for stakeholder-originated requirements, or an explanation/reference for internally-originated requirements.
View: One or several ARM Views to which the requirement is related.
Functionality Group: One or several Functionality Groups in the functional decomposition of the ARM to which the requirement is related.
Functional Component: One or several Functional Components in the functional decomposition of the ARM to which the requirement is related. These functional
components are part of the groups listed in the functionality-group field.
Domain Model: One or several Domain Model entities to which the requirement is related.
Perspective: One or several Perspectives to which a requirement is related.

Filtering

The table is highly dynamic, with the possibility to perform a global search, as well as filter for each column. For example, one can perform a global search on the word
'communication' (search all columns box), or filter all requirements categorized with the tag privacy (Category column filter), or those which apply to the Management
Functionality Group (Functionality Group column filter).

I'm missing an important requirement in the list...

We have put a lot of care in building this list based on many different sources. If you think an important aspect is missing, please contact us.
For details on the requirement gathering process and complete list with more characteristics (e.g. business originating scenarios, fit criterions, etc), please refer to the most

1 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

recent WP6 requirement deliverable.

UNI Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
ID Type Component
A system built using
the ARM shall
provide a means to "Citizens want to
Non-functional Security and Identity User, Service,
UNI.001 Privacy allow people to use protect their Functional Security
Requirements Privacy Management Resource, Device
Internet of Things private data"
services
anonymously
Users have control
"Citizens want to
Non-functional how their data is Security and Human User,
UNI.002 Privacy, Usage protect their Functional Security Authorisation
Requirements exposed to other Privacy Service, Resource
private data"
users
A system built using
the ARM shall "I would like a way
enable the to create and
provision and exchange
Non-functional Self-description, Evolution and
UNI.003 exchange of semantics (none) (none specific) (none specific) Service, Resource
Requirements Semantics Interoperability
semantics between between objects in
services in order to order to design
support the design new applications"
of new applications
"I would like a way
A system built using
to create and
the ARM shall
exchange
Non-functional Self-description, enable the
UNI.004 semantics Information (none) (none specific) (none specific) (none)
Requirements Semantics semantic
between objects in
description of
order to design
physical entities
new applications"
"The remote
monitoring device
A system built using gathers patient
the ARM shall measurements,
Autonomicity,
Functional support event- data and or
UNI.005 Data handling & Functional (none) IoT Service IoT Service (none)
Requirements based, periodic, events. Data may
Communication
and/or autonomous be communicated
communication each time the
device gathers the

2 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
data, accumulated
measurements
may be
communicated
periodically (e.g.,
hourly, daily), or
data may be
delivered upon
request or upon
certain events"
"The problem is to
provide a
framework, a set of
scenarios where
A system built using
these applications
the ARM shall be
could be
able to run
Non-functional developed in Performance
UNI.008 Interoperability applications and (none) (none specific) (none specific) Service
Requirements harmony, in an and Scalabiltiy
services in an
interoperable way
interoperable
and in a way that
manner
responses to the
real needs of
organization and
people"
"I would expect
that the traffic
A system built using lights collaborate
the ARM shall for a goal" - Smart
enable autonomous objects should
Non-functional goal-driven (task- collaborate in Evolution and
UNI.010 Autonomicity (none) (none specific) (none spedific) Device, Service
Requirements driven) order to realize a Interoperability
collaboration common goal
between devices or (such as traffic
services lights in order to
reduce traffic or
pollution).
Radio- A system built using "In order to
Non-functional Evolution and Hop to Hop
UNI.012 awareness, the ARM shall be achieve a reliable (none) Communication Service, Device
Requirements Interoperability Communication
Data handling & able to handle eHealth service

3 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
interference
the system must
communication, between IoT
be interference-
Resilience devices (avoidance
free"
and detection)
"The remote
monitoring device
is prepared for use
and
communication by
the action of the
patient or clinician.
This may involve
physically
attaching or
A system built using placing the device,
the ARM shall registering the
Functional Device, Service,
UNI.014 Autonomicity support devices to device, setting up Deployment (none) Management Configuration
Requirements Resource
activate themselves the
into a collaboration communications
channels to M2M
application
entities, setting up
the
communications
capabilities of the
device and
providing for
secure
communications."
"The remote
monitoring device
may be configured
A system built using
by via the M2M
the RA shall be
Functional Resource network by the Deployment, Configuration, Device, Service,
UNI.015 able to remotely (none) Management
Requirements control M2M application Operation Member, State Resource
control and
entities. The
configure devices
configuration
capability could
span simple

4 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
parametric
changes, such as,
reporting rates,
event or alarm
trigger levels, and
dosing levels to
downloading and
securely restarting
new operating
software"
A system built using "High value assets
the ARM shall need to be tracked VE Resolution,
Discovery & support physical in order to avoid VE & IoT
Functional Information, Augmented Entity,
UNI.016 lookup, entity location theft and also to (none) Virtual Entity Service
Requirements Functional Resource, Service
Geolocation tracking (geo know where they Monitoring, VE
spatial and/or are currently Service
logical location) located"
"The remote
monitoring device
gathers patient
measurements,
data and or
A system built using
events. Data may
the ARM shall
be communicated
support data
each time the
processing
device gathers the
Functional Data handling & (filtering,
UNI.018 data, accumulated Functional (none) IoT Service IoT Service Service
Requirements communication aggregation/fusion,
measurements
...) on different IoT-
may be
system levels (for
communicated
instance device
periodically (e.g.,
level)
hourly, daily), or
data may be
delivered upon
request or upon
certain events"
Data handling & A system built using "Providers can
Functional
UNI.019 communication, the ARM shall initiate Functional (none) IoT Service IoT Service (none)
Requirements
Usage support user- communication

5 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
with the patients
health monitoring
device for a
number of
reasons. Examples
initiated
of this include a
communication
provider querying
the device for a
reading or for
configuring such a
device"
A system built using
"The application
the ARM shall
knows the current
Functional Radio- support real-time Hop to Hop
UNI.020 radio transmission Functional (none) Communication Device
Requirements awareness monitoring of radio Communication
activity of the M2M
usage of devices
device"
and gateways
Radio- The user shall be
"The application Hop to Hop
Functional awareness, able to control the Communication,
UNI.021 can control the Functional (none) Communication, Device
Requirements Usage, Energy- radio activity of the Management
radio transmission" Configuration
awareness system
"Patients are able
to initiate
communication to
the providers
Electronic Medical
Record (EMR) or
health database
A system built using
application using
the ARM shall IoT Service,
Functional Security, Usage, the secure
UNI.022 provide end users Functional (none) IoT Service, Security Key Exchange (none)
Requirements Access Control messaging tool for
with secure access & Management
a variety of
to resources
purposes.
Examples include
providing manually
gathered
information on
existing self-
monitoring and/or

6 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
chronic care
regiments."
"Patients are able
to initiate
communication to
the providers
Electronic Medical
Record (EMR) or
health database
A system built using application using
the ARM shall the secure
Interoperability,
Non-functional provide access to messaging tool for Evolution and
UNI.023 Enterprise (none) (none specific) (none specific) Resource, Storage
Requirements external information a variety of Interoperability
Integration
sources, e.g. health purposes.
databases Examples include
providing manually
gathered
information on
existing self-
monitoring and/or
chronic care
regiments."
A system built using "In case of
the ARM shall emergency the
QoS, Data
Functional support time-critical Remote Monitoring Performance
UNI.026 handling and Functional Communication (none specific) (none)
Requirements message handling Device has to send and Scalabiltiy
communication
and delivery on a or receive time
second time scale. critical messages"
"In case of time-
A system built using
sensitive services
the ARM shall
Functional the system needs Performance
UNI.027 QoS support Functional (none specific) (none specific) (none specific)
Requirements to assure that and Scalabiltiy
prioritization of
important services
services
are prioritized"
A system built using
QoS, Data the ARM shall "Not every
Functional Performance
UNI.028 handling and provide a message- message has the Functional Communication (none specific) (none specific)
Requirements and Scalabiltiy
communication prioritization same priority"

7 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
mechanism
"A system may be
provided which is
operable to
determine a
routing node for a
data object. The
system can
comprise an
A system built using identifier generator
the ARM shall operable to
provide a resolution generate an
Discovery & VE Resolution,
Functional infrastructure for identifier for the Virtual Entity, IoT VE, Service,
UNI.030 lookup, Naming, Functional (none) IoT Service
Requirements naming, addressing data object on the Service Resource
Addressing Resolution
and assignment of basis of data
virtual entities and content thereof,
services and a lookup
engine operable to
compare the
identifier for the
data object to a
routing table to
determine a
routing node for
the data element."
"Today, due to
sub-optimal
processes, a lot of
time and money is
A system built using wasted. This Business
the ARM shall situation could be Process
Service
Functional enable centralized improved a lot by IoT Business Process Modeling,
UNI.031 composition & Functional (none) Service
Requirements or decentralized tracking all the Management Business
programmability
automated activities items/things, Process
(control loops) providing context Execution
data on them at
any time and
location, allowing
for automated

8 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
evaluation of the
collected data and
reacting
immediately on a
dangerous
situation to protect
against the break
down of items."
"Today, due to
sub-optimal
processes, a lot of
time and money is
wasted. This
situation could be
improved a lot by
tracking all the
items/things, Business
Service A system built using providing context Process
Functional composition & the ARM shall data on them at IoT Business Process Modeling,
UNI.032 Functional (none) Service
Requirements programmability, enable the planning any time and Management Business
Usage of automated tasks location, allowing Process
for automated Execution
evaluation of the
collected data and
reacting
immediately on a
dangerous
situation to protect
against the break
down of items."
"My wish is to
retrieve the
A system built using capacity of a thing.
Self-description, the ARM shall Thus, I can plan a
Functional
UNI.036 Usage, enable the retrieval change Functional (none) Virtual Entitty VE Resolution Service, Resource
Requirements
Semantics of the self- maintenance of all
description of things my bulbs if they
can say when they
should be

9 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
changed"
A system built using "Road users and
the ARM shall energy providers Availability
Non-functional Security,
UNI.040 provide ways to want to avoid (none) and (none specific) (none specific) (none specific)
Requirements Resilience
ensure security and shortages/ Resilience
resilience blackouts"
"A method for
clarification
whether the
Cold/Hot Chain
has been violated
or not is required.
To be able to do
this, the
A system built using continuous context
the ARM shall information (e.g.,
Functional Data handling & Information,
UNI.041 provide historical temperature) of the (none) IoT Service IoT Service Physical Entity
Requirements communication Functional
information about things needs to be
the physical entity collected. This is
for example of
major importance
to avoid any
damage to the
pharmaceutics
during the
transport and
storage process."
A system built using
"Both the M2M
the ARM shall
server and the
enable both user
Non-functional Data handling & M2M device must Evolution and User, Device,
UNI.042 and device to (none) (none specific) (none specific)
Requirements communication be able to provide Interoperability Service, Resource
exchange
information about
information about
the current state"
their state
A system built using "The costs for
Service
Service the ARM shall complex logistics
Functional Composition,
UNI.043 composition & enable the and healthcare Functional (none) Service Organization Service
Requirements Service
programmability composition of processes need to
Orchestration

10 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
be kept on a low
level. A modular
setup of the
applications and
services is one
important
ingredient to
achieve this.
Therefore it should
entity-related
be very easy to
services
integrate things
together with their
atomic services
into other services,
and it should be
easy for things to
use services
provided by
others."
"As an example,
CCTV system
could inform traffic
management of
the length of the
waiting queue at a
The system must
crossroad. Having
ensure
smart traffic lights
Non-functional interoperability Evolution and Key Exchange
UNI.047 Interoperability receiving such (none) Security (none specific)
Requirements between objects or Interoperability & Mangement
input from the
between
CCTV system
applications
could, could help
changing the
schedule of
green/red light to
optimize the
traffic."
Interoperability, A system built using "IoT-A will play a Hop to Hop
Functional Evolution and
UNI.048 Discovery & the ARM shall role in terms of Functional Communication Communication, (none)
Requirements Interoperability
lookup, Naming, provide providing a kind of Network

11 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
novel resolution
infrastructure. We
need to
understand how
interoperable best IoT could be
Addressing naming and served by scheme Communication
addressing regarding the
naming of objects,
the addressing and
assigning
problems."
"The use of M2M
Devices for
A system built using
Discovery & monitoring health Availability
Non-functional the ARM shall
UNI.050 lookup, related information (none) and (none specific) (none specific) Augmented Entity
Requirements support mobility of
Geolocation is not confined to Resilience
the physical entity
the residence of
the patient."
"Communication
blackouts are not
QoS, The system shall accepted from Availability
Non-functional
UNI.058 Availability, provide high client side and (none) and (none specific) (none specific) (none specific)
Requirements
Resilience availability particularly if they Resilience
are paying for
premium services"
"Communication
blackouts are not
The system shall accepted from Availability
Non-functional
UNI.060 QoS, Usage support different client side and (none) and (none specific) (none specific) Service
Requirements
SLA particularly if they Resilience
are paying for
premium services"
A system built using "A method for
Security, Trust, the ARM shall clarification
Data handling & provide trusted and whether the
Design Security and
UNI.062 communication secure Cold/Hot Chain (none) (none specific) (none specific) (none)
constraints Privacy
Availability, communication and has been violated
Integrity information or not is required.

12 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
To be able to do
this, the detailed
context information
(e.g., temperature)
of the things, which
have been
collected in some
database need to
be easily made
management
available. This is
for example of
major importance
to avoid any
damage to the
pharmaceutics
during the
transport and
storage process."
"Security, why?
Simply because
the IoT - I am sure
you will
demonstrate it - is
a kind of critical
information
infrastructure Security and
A system built using
Availability, which means that Privacy,
Non-functional the ARM shall
UNI.064 Resilience, if ever for whatever (none) Availability (none specific) (none specific) Service
Requirements provide availability
Reliability reason there is a and
through resilience
failure somewhere Resilience
on the IoT the
impact will be so
high that it would
be a social loss,
like if we do not
have more
electricity."
Non-functional A system built using "In order to Availability
UNI.065 QoS, Reliability (none) (none specific) (none specific) Service
Requirements the ARM shall accommodate and

13 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
certain scenario,
support of a certain
provide reliable
degree of reliability Resilience
services
might be
necessary"
"In certain life-
A system built using
critical applications
the ARM shall
the device may be
provide integrity Virtual Entity,
Functional Security, required to perform Performance
UNI.066 validation of virtual (none) Management Member, State Service, Device,
Requirements Integrity a secure start-up and Scalabiltiy
entities, devices, Resource
procedure that
resources, and
includes integrity
services
checking."
"Sensitive data of
patients must be
A system built using
kept secure in
the ARM shall
Functional Security, Access order to assure
UNI.067 provide different Functional (none) Security Authorisation Resource
Requirements Control trust between the
access permissions
patients and to
to information
allow access to
certain people"
"I would like a way
A system built using
to create and
the ARM shall
exchange
Functional Self-description, provide
UNI.070 semantics Information (none) (none specific) (none specific) Service
Requirements Semantics interoperability
between objects in
through the use of
order to design
semantics
new applications"
"Standard
communications
A system built using between objects,
the ARM shall from a
Data handling &
provide communication
Design communication, Evolution and
UNI.071 standardized and channel point of (none) (none specific) (none specific) Service
constraints Semantics, Interoperability
semantic view but also from
Interoperability
communication a semantic point of
between services view.
(Standardization of

14 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
object semantic is
somehow similar to
the standardization
of MIB
(Management
Information Base)
of
telecommunication
equipments)."
A system built using "I would like a way
the ARM shall allow to create and
the semantic exchange
Functional Semantics, Virtual Entity,
UNI.073 description of semantics Information (none) (none specific) (none specific)
Requirements Usage Service, Resource
physical entities between objects in
and services by a order to design
user new applications"

"A service is
something that
originates at a
certain time for
accomplishing
goals…that lives
for a certain
A system built using reason, may
endure for a time,
Service the ARM shall and may or may
Functional
UNI.087 composition & support service not be retired" Operation (none) (none specific) (none specific) Service
Requirements
programmability lifecycle [Bell, Michael
management (2008).
"Introduction to
Service-Oriented
Modeling".
Service-Oriented
Modeling: Service
Analysis, Design,
and Architecture.
Wiley & Sons]
"Services which
A system built using
depend on a
the ARM shall
Non-functional precise time need Performance
UNI.089 N/A support reliable (none) (none specific) (none specific) (none)
Requirements a guarantee that and Scalabiltiy
time
the devices they
synchronization
are communicating

15 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
to have the right
time."
"The mobile phone
of the consumer
Remote services Availability
Non-functional can and should be
UNI.092 Usage shall be accessible (none) and (none specific) (none specific) Service
Requirements used for interacting
by human users Resilience
with product
centric services"
"The reference
architecture shall
provide an integral
A system built using
approach that
Non-functional Interoperability, the ARM shall be Evolution and
UNI.093 combines legacy (none) (none specific) (none specific) (none)
Requirements Extensibility extensible for future Interoperability
aspects as well as
technologies.
an imaginating
vision on the
Internet of Things."
"The reference
architecture shall
The Architectural
provide the
Reference Model
Non-functional building blocks in a Evolution and
UNI.094 N/A shall support any (none) (none specific) (none specific) (none)
Requirements creative way Interoperability
IoT business
coming from a
scenario.
business
perspective."
"The reference
architecture shall
consider that we
have gateways to
A system built using IP everywhere, so
VE Resolution,
the ARM shall we must have a
Data handling & IoT Service Service, Resource,
Design include an interface global addressing Virtual Entity, IoT
UNI.095 communication, Functional (none) Resolution, Device, Virtual
constraints to IP system with Service, Communication
Addressing Network Entity
communication protocol and so on.
Communication
protocols. That would be an
evolution of IPv6.
Or we need an
integration

16 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
package for
existing addressing
systems."
"Future systems
implementing the
A system built using
reference End-to-End
the ARM shall
architecture shall Communication,
Autonomicity, support the
Functional allow for a Evolution and Communication, Service Service
UNI.096 Self- autonomous and Functional Device, Service
Requirements dynamic selection Interoperability Organization Composition,
Configuration dynamic selection
of protocols and Service
of protocols without
layers without any Orchestration
human intervention.
human
intervention."
"Deal with the
lifecycle of
A system built using
information (how to
the ARM shall
Functional Data handling & distinguish, if
UNI.097 support information Information (none) (none specific) (none specific) (none)
Requirements communication information (tag) is
(data) lifecycle
temporary not
management.
available or not
valid any more?)"
"It is necessary to
A system built using
make the system
the ARM shall have
know what defines IoT Service
Functional Semantics, a semantic IoT Service, Virtual Service, Virtual
UNI.098 a distance." - this Information (none) Resolution, VE
Requirements Geolocation understanding of Entity Entity
is necessary to Resolution
distance and
discover location-
location.
based services
"When searching
A system built using for a certain object
the ARM shall you need an IoT Service
Non-functional IoT Service, Virtual
UNI.099 N/A guarantee implemented Functional (none) Resolution, VE (none)
Requirements Entity
correctness of system that Resolution
resolutions. actually gives you
the correct result."
A system built using "We must look out
Functional Resource the ARM should also for some way Functional Hop to Hop
UNI.100 (none) Communication (none)
Requirements control include means to to wake up sleepy Communication

17 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
communications in
wake-up sleepy
order to manage
devices.
energy consume."
A system built using
Energy- the ARM shall
"We must look out Hop to Hop
Functional awareness, include means to Performance Communication,
UNI.101 for a highly energy Functional Communication, (none)
Requirements Resource manage the energy and Scalabiltiy Management
efficient system." Configuration
Control consumption of
devices.
A system built using
"Maybe there
Interoperability, the ARM shall take
should be some
Non-functional Enterprise into account Performance
UNI.102 part of processing (none) (none specific) (none specific) (none)
Requirements Integration, external computing and Scalabiltiy
information in the
Extensibility resources, e.g. 'the
cloud."
cloud'.
The process-
modeling notation
has to be extensible
in terms of the The reuse of an
definition of new existing process-
Enterprise Business
Functional symbols, the modeling notation IoT Business Process
UNI.211 Integration, Information (none) Process (none)
Requirement specification of new allows to focus the Management
Usage Modeling
syntax, the effort on the IoT-
definition of extension.
serialisation and
execution
semantics.
The projects task
The process- 2.2 and 2.3 should
Business
Functional Enterprise modeling notation closly work IoT Business Process
UNI.212 Functional (none) Process (none)
Requirement Integration has to be together and Management
Modeling
executable. represent a hand
in hand solution.
The process
The standard
Enterprise modeling notation established Business
Non-functional shall be able to process notations IoT Business Process
UNI.213 Integration, Information (none) Process (none)
Requirement describe IoT- cannot cope with Management
Usage IoT specific Modeling
specific aspects, aspects, but in

18 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
order to address
IoT aware
processes, one
needs to be able to
describe them
appropriately.
[Sonja Meyer,
Klaus Sperner,
as, for instance, Carsten
availability. Magerkurth,
Jacques Pasquier
(2011): Towards
Modeling Real-
World Aware
Business
Processes. Web of
Things 2011. San
Francisco, USA,
June 6, 2011.]
A graphical
The specification of
process notation
the system's
Enterprise offers a symbolism Business
Non-functional process-modeling IoT Business Process
UNI.214 Integration, to easily model Information (none) Process (none)
Requirement notation shall Management
Usage and document Modeling
include a graphical
business
representation.
processes.
A common
standard
The used process-
maximizes the Business
Non-functional Enterprise modeling notation IoT Business Process
UNI.215 potential Information (none) Process (none)
Requirement Integration shall adhere to a Management
application of Modeling
standard.
industrial
stakeholders.
The process-
The development
execution functional Business
Non-functional should focus on IoT Business Process
UNI.229 Extensibility component shall be Information (none) Process Service
Requirement the IoT related Management
"easily and fastly" Execution
extension.
extendable.
The process- One WP central Business
execution engine process execution Availability IoT Business Process Process
Functional
UNI.232 Interoperability shall support the engine including Functional and Management, Service Execution, (none)
Requirement
integration with a the CEP enables a Resilience Organization Service
complex-event- bigger research Orchestration

19 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
processing (CEP)
contribution.
component.
Many physical
entities such as
mobile phones,
Mobile entities shall products in a retail
Availability
Design Data Handling & be able to provide store, etc. are Active Digital
UNI.233 (none) and (none specific) (none specific)
Constraint communication events to the mobile and IoT-A Artefact
Resilience
platform must be able to
detect changes
related to those
entities
A distributed
architecture
provides more
flexibility in the
Service
Events shall be way events are
Non-functional Data Handling & Performance Composition,
UNI.234 processed on a set processed, saves (none) Service Organization (none)
Requirement communication and Scalability Service
of distributed nodes energy and allows
Orchestration
minimal
functionality if
there is no network
connectivity
Processing of In IoT the quality of
Service
QoS, Data events shall take information
Functional Composition,
UNI.235 Handling and quality of stemming from Functional (none) Service Organization (none)
Requirement Service
communication informaton (QoI) events is often
Orchestration
into account questionable.
Different devices
A system built using
provide information
the ARM shall offer
QoS, Data with varying
services for the
Functional Handling and quality. An
UNI.236 retrieval of quality Functional (none) IoT Service IoT Service Service
Requirement communication, application may
of information
Usage have certain
related to virtual
quality
entities.
requirements.

Functional QoS, Data A system built using Different devices

UNI.237 Handling and the ARM shall offer provide information Information (none) (none specific) (none specific) Resource
Requirement

20 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
with varying
data types for
quality. An
describing
application may
communication the quality of
have certain
information related
quality
to virtual entities.
requirements.
Due to resources
could not be online
A system built using
all the time it could
the ARM shall
be necessary to
provide a Storage
incorporate an
Resource with a
Functional Resource intermediate
UNI.239 shared cache, in Functional (none) IoT Service IoT Service Service
Requirement Control shared memory in
which an
order to store this
observable
information, so it
phenomenon is
could be accessed
stored
by services using
these information.
This will enable
A system built using
WP4 discovery
the ARM shall
and identification
provide unified
Functional Interoperability, and also reasoning Virtual Entity, IoT VE Service, IoT
UNI.240 interfaces to access Functional (none) Service
Requirement Self-Description mechanisms to Service Service
and query the
access the
resource/entity
required
meta data
descriptions
A system built using
the ARM shall
provide unified This will enable
Interoperability, interfaces to access integration of IoT
Functional
UNI.241 Resource and query the data into business Functional (none) IoT Service IoT Service Service
Requirement
Control observation and layer and high-
measurement data level applications.
emerging from
resources
The orchestration Service
Service Service
Functional engine shall orchestration Composition,
UNI.244 composition & Functional (none) Service Organization Service
Requirement interpret service needs to be done Service
programmability based on IOPE

21 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
information
provided in service
descriptions.
descriptions [Bell, Michael. Orchestration
2008. Service-
Oriented Modeling.
Chichester: John
Wiley & Sons.]
Composite
The service Service
Service services allow
Functional organization shall Composition,
UNI.245 composition & added value Functional (none) Service Organization Service
Requirement support creation of Service
programmability services based on
new applications Orchestration
simple services

Services involved
in compositions
can fail and need
to be replaced by
The service some serving Service
Service equal needs.
Functional organization shall Composition,
UNI.247 composition & Functional (none) Service Organization Service
Requirement support flexible [Kephart, J. O., & Service
programmability Chess, D. M.
composition Orchestration
(2003). The vision
of autonomic
computing.
Computer, 36(1),
41-50.]

The service user

needs to be
informed whether
The service or not the
Service organization shall composition Service
Functional composition & provide a feedback request has Composition,
UNI.251 succeded or failed Functional (none) Service Organization Service
Requirement programmability, to the user who due to uncertainty Service
Usage sent a composition of service Orchestration
request availability.
[Nielsen, J. (1993).
Usability
Engineering].
The service A time out must be Service
organization shall set for
Non-functional request/response Operation Composition,
UNI.252 Usage provide feedback (none) Service Organization Service
Requirement loops. For Service
within a reasonable requests entered Orchestration
amount of time. by human users a

22 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
limit of 10 seconds
could be
reasonable. After
that an error is
assumed.
[Nielsen, J. (1993).
Usability
Engineering].
The orchestration
engines shall Users can have
Service Service
support setting the possibility to
Functional composition & Composition,
UNI.253 preferences for prefer one service Functional (none) Service Organization Service
Requirement programmability, Service
selecting services over another for
Usage Orchestration
involved in any reason
composition
In order to support
direct collaboration
between devices
(e.g.
choreography),
one needs to
A system built using provide direct one
the ARM shall to one
support one to one communication.
Functional Data handling & Network Devices (Sensors,
UNI.301 communication This is refered to Functional (none) Communication
Requirement communication Communication Tags, Actuators)
between devices as local gossip in
(e.g. unicast [S. S. Kulkarni,
messages). “TDMA Services
for Sensor
Networks,” Proc.
24th Int’l. Conf.
Distrib. Comp.
Sys. Wksps. , Mar.
2004, pp. 604–09]
A system built using
In order to support
the ARM shall collaboration
Functional Data handling & support between groups of Network Devices (Sensors,
UNI.302 communication devices (e.g. Functional (none) Communication
Requirement communication choreography), Communication Tags, Actuators)
between groups of one needs to
devices (e.g. provide group to

23 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
group
communication.
[Tian He;
Stankovic, J.A.;
Chenyang Lu;
Abdelzaher, T.,
"SPEED: a
stateless protocol
multicast for real-time
messages). communication in
sensor networks,"
Distributed
Computing
Systems, 2003.
Proceedings. 23rd
International
Conference on ,
vol., no., pp.46,55,
19-22 May 2003]
Typical IoT sensor
scenarios like
having a group of
terminals to send
data (possibly
aggregated at
some intermediate
point) to a single
terminal located
A system built using within the same or
the ARM shall a different network
Functional Data handling & Network Devices (Sensors,
UNI.303 support reverse domain, should be Functional (none) Communication
Requirement communication Communication Tags, Actuators)
multicast covered. This is
messages. refered to as
convergecast in [S.
S. Kulkarni,
“TDMA Services
for Sensor
Networks,” Proc.
24th Int’l. Conf.
Distrib. Comp.
Sys. Wksps. , Mar.
2004, pp. 604–09]

24 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component

This is required by
scenarios such as
when a single
terminal sends
data to a
destination
terminal which is
selected based on
a set of attributes
specified by the
sender rather than
on id or location.
A system built using
[Tian He;
Functional Data handling & the ARM shall Stankovic, J.A.; Network Devices (Sensors,
UNI.304 Functional (none) Communication
Requirement communication support anycast Chenyang Lu; Communication Tags, Actuators)
messages. Abdelzaher, T.,
"SPEED: a
stateless protocol
for real-time
communication in
sensor networks,"
Distributed
Computing
Systems, 2003.
Proceedings. 23rd
International
Conference on ,
vol., no., pp.46,55,
19-22 May 2003]

In certain IoT
scenarios (e.g.
sensor networks),
a single node (the
sender) sends
A system built using
data to all nodes of
the ARM shall a network, for
support one to example for
Functional Data handling & configuration Hop to Hop Devices (Sensors,
UNI.305 many / one to all Functional (none) Communication
Requirement communication purposes. Communication Tags, Actuators)
communication
(e.g. broadcast [S. S. Kulkarni,
“TDMA Services
messages). for Sensor
Networks,” Proc.
24th Int’l. Conf.
Distrib. Comp.
Sys. Wksps., Mar.
2004, pp. 604–09]

25 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
Data-memory-
In some IoT
constrained devices
scenarios,
must be able to constrained
participate in devices with in
particular a very
communication.
small amount of
Functional Data handling & This means that a data memory Devices (Sensors,
UNI.306 Functional (none) Communication (none specific)
Requirement communication system built using needs to be able to Tags, Actuators)
join
the ARM shall
communication.
support
communication [IETF Routing over
Low Power and
stacks with small Lossy Networks
data footprint. WG charter]
Network-stack-
In some IoT
constrained devices scenarios,
must be able to constrained
participate in devices with in
particular
communication.This simplified network
Functional Data handling & Devices (Sensors,
UNI.307 means that a stacks may need Functional (none) Communication (none specific)
Requirement communication Tags, Actuators)
system built using to engage in
communication.
the ARM shall
support constrained [IETF Routing over
Low Power and
communication Lossy Networks
stacks. WG charter]

In some IoT
scenarios, IoT-
devices need to
communicate
across an non-
A system built using reliable networks,
like Low-power
the ARM shall and Lossy Hop to Hop
Data handling & support networks. There is
Functional a wide scope of Communication, Devices (Sensors,
UNI.308 communication, communication Functional (none) Communication
Requirement application areas Network Tags, Actuators)
Resilience over Low-power for LLNs, including Communication
and Lossy industrial
networks. monitoring,
building
automation
(HVAC,lighting,
access
control,fire),
connected homes,

26 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
healthcare,
environmental
monitoring, urban
sensor networks
(e.g. Smart Grid),
asset tracking.
[IETF Routing over
Low Power and
Lossy Networks
WG charter]

In some IoT
scenarios, power-
less devices may
need to engage in
communication,
e.g. by harvesting
A system built using energy before
triggering
the ARM shall constrained
Data handling & support power-less communication. Hop to Hop
Functional communication, devices (in [Aman Kansal, Communication, Devices (Sensors,
UNI.309 Functional (none) Communication
Requirement Energy- particular the latter Jason Hsu, Sadaf Network Tags, Actuators)
awareness may be able to Zahedi, and Mani Communication
B. Srivastava.
participate in 2007. Power
communication). management in
energy harvesting
sensor networks.
ACM Trans.
Embed. Comput.
Syst. 6, 4, Article
32 (September
2007).]
A system built using Communication
the ARM shall must be open also
for devices with
Data handling & support power- Hop to Hop
constrainend
Functional communication, constrained devices power, like battery- Communication, Devices (Sensors,
UNI.310 Functional (none) Communication
Requirement Energy- (in particular the powered devices. Network Tags, Actuators)
awareness latter may be able [IETF Routing over Communication
to participate in Low Power and
communication). Lossy Networks
WG charter]
A system built using
In some IoT
Functional Data handling & the ARM shall scenarios, Devices (Sensors,
UNI.311 Functional (none) Communication (none specific)
Requirement communication support stateless stateless-devices Tags, Actuators)
must be able to

27 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
participate in
communication.
[Tian He;
Stankovic, J.A.;
Chenyang Lu;
Abdelzaher, T.,
"SPEED: a
stateless protocol
communication for real-time
methods. communication in
sensor networks,"
Distributed
Computing
Systems, 2003.
Proceedings. 23rd
International
Conference on ,
vol., no., pp.46,55,
19-22 May 2003]

The usage of IPv6

is common
practice in IoT
systems.
A system built using [N. Kushalnagar,
the ARM shall G. Montenegro, C.
Data handling & use/support Schumacher, IPv6
Functional Over Low-Power Evolution and Network Devices (Sensors,
UNI.312 communication, common- Wireless Personal Functional Communication
Requirement Interoperability Communication Tags, Actuators)
Interoperability addressing- Area Networks
schemes such as (6LoWPANs):
Overview,
IPv6. Assumptions,
Problem
Statement, and
Goals, IETF RFC
4919, August
2007.]
A system built using
the ARM shall
support mapping Communication
Data handling & from different with non-IPv6
Functional Evolution and Network Devices (Sensors,
UNI.313 communication, addressing networks must be Functional Communication
Requirement Interoperability Communication Tags, Actuators)
Interoperability schemes to IP v6 possible (IPv4,
(Compatible- others).
addressing-scheme
support).

28 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
Multi-homing and
mobility induce
A system built using
that a network
the ARM shall
nodes's identity
support identity-
(e.g. a device
Functional Data handling & locator split, i.e. Evolution and Network Devices (Sensors,
UNI.314 identity) should be Functional Communication
Requirement communication making the device's Interoperability Communication Tags, Actuators)
distinguished from
identity
its network locator
independent from
(e.g. it's IP
its locator
address). [IETF 79
proceedings]

Device need to
communicate
across
heterogenous
networks. In
particular IoT
A system built using systems shall
the ARM shall support
Functional Data handling & communications Network Devices (Sensors,
UNI.315 support routing over Functional (none) Communication
Requirement communication between different Communication Tags, Actuators)
heterogenous types of networks
networks. (like constrained
and unconstrained
networks).
[IETF Routing over
Low Power and
Lossy Networks
WG charter]
A system built using Some IoT devices,
the ARM shall in particular power-
constrained nodes,
support sleepy Hop to Hop
may have only
Functional Data handling & devices, i.e. intermittent Communication, Devices (Sensors,
UNI.318 Functional (none) Communication
Requirement communication devices with network access. Network Tags, Actuators)
periodic / non- [IETF Routing over Communication
permanent network Low Power and
access. Lossy Networks
WG charter]
A system built using For security Hop to Hop
Data handling & the ARM shall reasons (rogue
Functional Security and Communication,Security, Communication, Devices (Sensors,
UNI.319 communication, support limiting device joining an Functional
Requirement Privacy Management Autorisation, Tags, Actuators)
Access control network access to IoT system), safety
Member

29 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
specific devices
(e.g. devices may reasons (liability)
need to provide and accounting
appropriate reasons, it may be
credentials before necessary to
being granted the control access to
right to join a an IoT system.
network).
A system built using
Devices with more
the ARM shall
than one network
support multi-
interface /
homing, i.e. devices
Functional Data handling & connection should Network Devices (Sensors,
UNI.320 connecting to more Functional (none) Communication
Requirement communication be able to Communication Tags, Actuators)
than one network
communicate in
and to dialing in
several networks
with multiple ids
concurrently.
and locators.
To guaranty
Devices must be
continuity of
able to switch
service, IoT
between different
Data handling & devices may need Availability
Functional networks without Network Devices (Sensors,
UNI.321 communication, to change between Functional and Communication
Requirement losing connections Communication Tags, Actuators)
Availability different networks Resilience
(Network
without losing
handover/handoff
ongoing
support).
connections
A system built using
the ARM shall In some cases, IoT
Data handling & support anonymous devices may need
Functional Security and Identity Devices (Sensors,
UNI.322 communication, communication to communicate Functional Security
Requirement Privacy Management Tags, Actuators)
Privacy between devices without disclosing
(Anonymity its identity
support).
Devices must be To guaranty
able to switch continuity of
Data handling & Availability
Functional between different service, IoT Network Devices (Sensors,
UNI.324 communication, Functional and Communication
Requirement networks when devices may need Communication Tags, Actuators)
Availability Resilience
moving, e.g. to change between

30 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
similar networks
roaming. (Mobility without losing
support) ongoing
connections
The system shall
support
Seamless
interworking
communication
between different
between all kinds
Data handling & application
Functional of applications,e.g. Evolution and End to End Devices (Sensors,
UNI.326 communication, protocols (what to Functional Communication
Requirement business, desktop Interoperability Communication Tags, Actuators)
Interoperability communicate), for
and mobile
example through
applications, must
translation
be possible.
functionality in an
IoT gateway.
The system shall To enable
support communications
interworking between
between different constrained and
Data handling & networking unconstrained
Functional Evolution and Network Devices (Sensors,
UNI.327 communication, protocols (how to devices of an IoT Functional Communication
Requirement Interoperability Communication Tags, Actuators)
Interoperability communicate), for system, adaptation
example through between
translation networking
functionality in an protocols may be
IoT gateway. required.
The usage of
The system shall
Virtual Private
support network
Functional Data handling & Networks (VPN) Network Devices (Sensors,
UNI.328 virtualisation, i.e. Functional (none) Communication
Requirement communication must also be Communication Tags, Actuators)
the usage of virtual
possible in IoT
overlay networks.
systems.
Discovery and
This requirement is
lookup services of derived from
Discovery & the system shall SmartProducts Augmented Entity
Functional (SP) requirement Functional
UNI.401 lookup, allow locating (none) Virtual Entity VE Resolution (Physical Entity
Requirement "A SmartProduct
Geolocation physical entities should be able to +Virtual Entity)
based on locate another
SmartProduct in

31 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
the same
environment w.r.t.
their environment"
[ SmartProduct
Deliverable:
"D6.3.1 & D6.4.1 &
D6.5.1 Initial Smart
geographical Products
Communication
parameters Middleware, Initial
Sensor and
Actuator
Integration
Framework & Initial
Context and
Environment
Model
Framework".]

Derived from SP
requirement "A
SmartProduct
should be able to
access the location
information of
other
SmartProducts"
A system built using
the ARM shall [ SmartProduct
Non- Deliverable:
Self-description, provide "D6.3.1 & D6.4.1 & Functional
UNI.402 Functional (none) Virtual Entity VE Resolution Virtual Entity
Geolocation geographical- D6.5.1 Initial Smart
Requirement
location attributes Products
Communication
for virtual entities Middleware, Initial
Sensor and
Actuator
Integration
Framework &
Initial Context and
Environment
Model
Framework".]
A system built using
Derived from SP
the ARM shall requirement
Functional Self-description, support a "Smart products
UNI.403 standardized shall support a Functional (none) Virtual Entity VE Resolution Virtual Entity
Requirement Geolocation standardized
location model and location model and
location-information location-
information

32 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
representation."
[ SmartProduct
Deliverable:
"D6.3.1 & D6.4.1 &
D6.5.1 Initial Smart
Products
Communication
representation. Middleware, Initial
Sensor and
Actuator
Integration
Framework & Initial
Context and
Environment
Model
Framework".]

Derived from SP
requirement
"Smart products
shall support a
hybrid location
model, that is, it
shall support
A system built using symbolic
the ARM shall coordinates as
well as local and
support a hybrid global geometric
location model, that coordinates"
Functional Self-description, is, it shall support [ SmartProduct
UNI.404 Functional (none) Virtual Entity VE Resolution Virtual Entity
Requirement Geolocation symbolic Deliverable:
coordinates as well "D6.3.1 & D6.4.1 &
D6.5.1 Initial Smart
as local and global Products
geometric Communication
coordinates Middleware, Initial
Sensor and
Actuator
Integration
Framework &
Initial Context and
Environment
Model
Framework".]
Service A system built using
Derived from SP
composition and the ARM shall allow requirement: The
Functional
UNI.405 programmability, programmers to location model Functional (none) Virtual Entity (none) Virtual Entity
Requirement
Extensibility, add new coordinate shall allow
programmers to
Geolocation reference systems add new

33 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
coordinate
reference systems
and shall support
the transformation
of coordinates
among them
[ SmartProduct
Deliverable:
and shall support "D6.3.1 & D6.4.1 &
the transformation D6.5.1 Initial Smart
of coordinates Products
Communication
among them Middleware, Initial
Sensor and
Actuator
Integration
Framework & Initial
Context and
Environment
Model
Framework".]

Derived from SP
requirement: "The
location model
shall support the
following common
location queries:
The discovery position queries,
nearest neighbour
service of the queries,
system shall navigational
support the queries, and range
querie"
Discovery & following location
Functional [ SmartProduct
UNI.406 lookup, queries: position Functional (none) Virtual Entity VE Resolution Virtual Entity
Requirement Deliverable:
Geolocation queries, nearest "D6.3.1 & D6.4.1 &
neighbour queries, D6.5.1 Initial Smart
navigational Products
Communication
queries, and range Middleware, Initial
queries Sensor and
Actuator
Integration
Framework &
Initial Context and
Environment
Model
Framework".]

34 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component

Derived from
BRIDGE
requirement: "A
The look-up service
broad set of data
of the system shall from enterprise
withold or grant applications MAY
be requested
Discovery & information
depending on Augmented Entities
Functional lookup , depending on context, industry, Security and
UNI.407 Functional Security Authorisation (Physical Entity +
Requirement Security, Access context. Context application, etc" Privacy
Virtual Entity)
Control includes application [ BRIDGE
involved, requesting Deliverable "D2.1
entity, and security Requirements
document of serial
permissions level lookup
service for various
industries, Section
C". ]

Opting out of being

found in a data
search was
indicated in the
BRIDGE
requirement list
and also in the
IoT-A Stakeholder
Opinion Report.
The BRIDGE
requirement was
The system's "Data that
services shall companies are
willing to provide
Self-description, indicate what to the Discovery
Functional Security and
UNI.408 Discovery & information can be Services are Deployment Virtual Entity VE Resolution Services
Requirement mainly URL Privacy
Lookup found by a
addresses of
discovery/look-up databases / EPCIS
service repositories"
[ BRIDGE
Deliverable "D2.1
Requirements
document of serial
level lookup
service for various
industries, Section
C".]
[IOT-A Deliverable
"D6.6 Report on

35 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
Stakeholder
Opinions"]

A system built using This is a main

the ARM shall allow functionality of the
BRIDGE system
storage of VE which applies to
changes, including RFID/assets
Functional Data handling & structural changes tracked in the
UNI.409 EPCGlobal Functional (none) Virtual Entity VE Service Virtual Entity
Requirement communication (e.g. changes in the framework
aggregation of
[ BRIDGE
multiple VEs deliverable: "High
constituting one level design for
overarching VE) Discovery
Services".]

The integrity and

trust in the history
storage block
depends on how
"unaltered" it is.
The BRIDGE
project justifies the
present use of the
"history storage"
The storage of component. They
Digital Entity expressed it as
Functional Security, Access History information "Discovery Service Security and
UNI.410 security policies Functional Virtual Entity VE Service Virtual Entity
Requirement Control shall be restricted in may be set to Privacy
who can delete and restrict update and
update it delete actions on
DS records"
[ BRIDGE
Deliverable "D2.1
Requirements
document of serial
level lookup
service for various
industries, Section
C". ]
A system built using BRIDGE
the ARM shall offer mentioned that the
Users (Human,
Functional Security, Access a unique unique client Security and
UNI.411 identification of identification at the Functional Security Authentication Active Digital
Requirement Control Privacy
clients requesting DS is required to Artefact)
data via the control access to

36 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
data stored on the
discovery/lookup DS (particularly
services EPC number and
link).
Data owners should
This addresses
be able to set
privacy by putting
access-control Users (Human,
Functional Security, Access the control in the Security and
UNI.412 rights/ policies (set Functional Security Authorisation Active Digital
Requirement Control hands of the data Privacy
up by data owners) Artefact)
owners (or certain
to their data stored
external groups)
on resources
Access-control Access control
Security, Access
rights/ policies (set policies
Design Control, Privacy, Security and
UNI.413 up by data owners) themselves, if Deployment (none) (none) Resource
Constraint Security Privacy
shall not be known, can give
Management
published publicly. away information.
Augmented
entities are the
A system built using
core concept
the ARM shall
proposed for IoT
enable the dynamic
and to enable
discovery of virtual
Discovery & applications that
Functional entities and their
UNI.414 lookup, Self- do not have to be Functional (none) Virtual Entity VE resolution Virtual Entity
Requirement services. This is to
description a-priori configured
be done based on
for a fixed set of
the specification of
augmented
the service and the
entities, discovery
virtual enities.
at runtime must be
possible.
Geographic
A system built using
location is one of
the ARM shall
the most important
enable the dynamic
aspects for finding
Discovery & discovery of virtual
Functional relevant virtual
UNI.415 lookup, entities and their Functional (none) Virtual Entity VE resolution Virtual Entity
Requirement entities. Spatial
Geolocation related services
relations are of
based on a
prime importance
geographical
in the physical
location

37 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
world.
It is important to
A system built using
find the services
the ARM shall
related to a virtual
enable the lookup
entity that may
of service
provide information
Functional Discovery & descriptions of
UNI.416 about the virtual Functional (none) Virtual Entity VE resolution Virtual Entity
Requirement lookup specified services
entity, allow to
for a virtual entity
actuate the virtual
with the VE
entity, or enable
identifier as key for
interaction with the
the lookup
virtual entity.
Due to the
heterogeneity,
dynamicity and
mobility in the
Internet of Things,
the communication
endpoint may
change or different
endpoints may be
A system built using
suitable for
the ARM shall
different
Functional Discovery & enable the Evolution and IoT Service
UNI.417 applications. Functional IoT Service Service
Requirement lookup resolution of service Interoperability Resolution
Therefore,
identifiers to service
services should be
locators
uniquely identified
by a service
identifier, but this
identifier should
not be used for
locating the
service, so a
resolution step is
necessary.
A system built using Due to the mobility
VE & IoT Augmented Entities
Functional Discovery & the ARM shall be of physical entities
UNI.418 Functional (none) Virtual Entity Service (Physical Entity +
Requirement lookup able to discover as well as devices
monitoring Virtual Entity)
dynamic whose resources

38 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
are accessible
through services,
changing services
may provide
information, allow
actuation or enable
associations interaction with
between virtual physical entities. In
entities and service order to provide
related to virtual the currently
entities relevant services
for a
corresponding
virtual entity, the
dynamic
assoications must
be discovered
Due to the mobility
of things, as well
as devices whose
resources are
accessible through
A system built using
services, changing
the ARM shall be
services may
able to track
provide
dynamic
information, allow
associations
Discovery & actuation, or VE & IoT Augmented Entities
Functional between a virtual
UNI.419 lookup, enable interaction Functional (none) Virtual Entity Service (Physical Entity +
Requirement entity and services
Autonomicity with things. In monitoring Virtual Entity)
related to the virtual
order to provide
entity. This needs to
the currently
be done in order to
relevant services
determine whether
for a thing,
they are still valid.
dynamic
assoications must
be tracked to
determine whether
they are still valid.

39 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
Mobility is one of
the key reasons for
changing
associations. By
monitoring both
the location of
physical entities
and the service
area of resources,
dynamic
associations can
be discovered.
Based on the
proximity of the
physical entity, the
service area of the
A system built using resource and the
the ARM shall be functionality
Discovery & able to discover provided by the VE & IoT Augmented Entities
Functional lookup, dynamic resource, it can be Functional
UNI.420 (none) Virtual Entity Service (Physical Entity +
Requirement Autonomicity, associations based determined
monitoring Virtual Entity)
Geolocation on geographic whether the
location and other resource can
context information. provide any
information about
the physical entity
or enable any
actuation on the
physical entity. If
this is the case, an
association
between the virtual
entity, which
represents the
physical entity in
the system, and
the service, which
makes the
functionality of the

40 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
resource
accessible, can be
established.
Mobility is one of
the key aspects for
changing
associations. By
A system built using monitoring the
the ARM shall be location of physical
able to track entities, e.g., using
dynamic location services, it
Discovery & associations can be determined
VE & IoT Augmented Entities
Functional lookup, between a virtual when associations
UNI.421 Functional (none) Virtual Entity Service (Physical Entity +
Requirement Autonomicity, entity and services become invalid
monitoring Virtual Entity)
Geolocation based on due to the
geographic loaction geographic
to determine distance of
whether they are physical entities
still valid. and the service
areas of resources
and possibly other
and possibly other
aspects.
The Internet of
Things will consist
of multiple
administrative
A system built using
domains with
the ARM shall
different owners
enable the
that generally
discovery and
Design Discovery & manage their Evolution and
UNI.422 lookup of (none) Virtual Entity VE Resolution Virtual Entity
Constraint lookup devices, Interoperability
associations across
resources,
multiple
services virtual
administrative
entities etc.
domains.
independently. To
develop its full
potential
interactions,

41 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
including lookup
and discovery,
across domain
boundaries must
be possible.
When performing
discovery,
resolution or
lookup, the system
must respect any
aspect of privacy,
including the
possibility to
retrieve information
about or related to IoT Service Servicemboussar:
people by using (or Resolution, VE was Services
Functional Privacy is a key IoT Services, Virtual
UNI.423 Privacy subverting the use Functional (none) Resolution, (Intergation &
Requirement aspect for the IoT. Entity, Security
of) the Internet of Identity Interoperability
Things. In addition Management Layer) ?
some services
should be
accessible in an
anonymous way,
while others might
require an explicit
authentication or
authorization of the
user.
A system built using
the ARM shall
For acceptance of
provide privacy
the Internet of
Functional protection for users Security and Identity
UNI.424 Privacy Things privacy Functional Security User, Service
Requirement accessing Privacy Management
during usage must
information about
be guaranteed
physical entities or
services
A system built using The system must Servicemboussar:
Functional IoT Service
UNI.425 Self-description the ARM shall consider the Functional (none) IoT Service was Services
Requirement Resolution
provide a service description of a (Intergation &

42 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
identifier, and the service/resource
identifier shall use a for the semantic
Interoperability
service/resource indexing on which
Layer)
description for the search will be
retrieval. performed
Iot Service
Resolution
A system built using functional
the ARM shall be component has Servicemboussar:
Discovery & able to accept and interfaces to was Services
Functional IoT Service
UNI.426 lookup, manage semantic enable the user Functional (none) IoT Service (Intergation &
Requirement Resolution
Semantics queries from the make queries for Interoperability
user and return the Layer)
Resources/Services discovery,lookup
and resolution
functions.
Users must be
able to discover
Services locally in
their environment.
This is because in
many cases users
a) might not be
able to leverage
The Discovery
infrastructure
Service in a local
services b) Resourcemboussar:
search is required
Discovery & leveraging the was Resources
Functional to find IoT Service
UNI.427 lookup, Infrastructure Functional (none) IoT Service (Computational
Requirement service/resource Resolution
Semantics would be Element for PE
based on (rough)
ineffective and c) Access)
semantic
context-awareness
description
would be higher if
information is
derived from local
network (e.g. in an
underground
garage, proximity
might be
measured with

43 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
higher accuracy
using network
metrics respect to
using A-GPS or
cell-based
localization).
Association
between Ves and
the services is one
A system built using of the key
the ARM shall parameters for the
provide a service resolution
Functional Discovery & that obtains unique functional
UNI.428 Functional (none) Virtual Entity VE Resolution Virtual Entity
Requirement lookup identifiers for component and
associations association
between VE and contains unique
the service. association ID for
example to
manage it (such as
delete, insert)
The IoT resolution
In order for lookup
component shall
and global
provide a service to
discovery to work
insert or update the
properly, a IoT
operational
service-resolution
specifications (i.e. IoT Service
Functional Discovery & component must
UNI.429 type, description, Functional (none) IoT Service Resolution, IoT Service
Requirement lookup provide a way to
locator) of a new Service
insert and update
IoT service into the
the description of
data base that is
services that it will
used for discovery,
then use as a
lookup, and
search basis.
resolution.
A universal
A system built using
identifier should be
the ARM shall Augmented Entities
Functional Discovery & defined as Evolution and
UNI.432 provide a virtual Functional Virtual Entity VE Resolution (Physical Entity +
Requirement lookup standard ID in Interoperability
identification Virtual Entity)
order to map it to
system.
the specific ID

44 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
used in every type
of system (TCP/IP,
RFID, ...)
A system built using
the ARM shall Device Tag
The confidentiality Key Exchange
Non-functional make it difficult to Security & Physical entity
UNI.501 Security of messages must (none) Security & Management,
Requirement spy on Privacy Virtual entity
be ensured. Authentication
communicated Resource
messages.
The unsolicited
scanning of people
shall be avoided. A
device is always
A system built using owned by a person
the ARM shall or an entity. For
prevent a device example, in a retail
Device Tag User
Non-functional (contactless card use case, the Security &
UNI.502 Security (none) Security Authorisation Physical entity
Requirement for example) from owner of an RFID Privacy
Virtual Entity
being activated tag can be a
without the consent retailer and after
of the owner. the checkout the
new owner should
be the client. The
aim is to avoid
skimming attacks
A device is always
owned by a person
or an entity. For
example, in a retail
A system built using use case, the
Usage, Security, the ARM shall owner of an RFID Authorisation, Device Tag
Functional Integrity, Non- make it be possible tag can be a Security & Authentication, Physical entity
UNI.503 (none) Security
Requirement Repudiation, to change the retailer and after Privacy Key Exchange Virtual entity
Privacy owner of a device the checkout the & Management Resource
(tag for example). new owner should
be the client. The
aim is to avoid
skimming attacks.
Privacy preserving

45 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
solutions in RFID
require to share a
secret key
between tag and
reader (or owner
since in this case,
the owner enters
his key in the
reader). It must be
possible to change
this key in tag and
reader (and even
in the databases
where the data
related to the
device is stored) if
the owner has
changed.
The tracking of
items and then
people raise the
problem of privacy.
A system built using To preserve
the ARM shall privacy, only the
prevent tracking of owner of the tag
Autorisation,
Security, the identifier of the shall be able to Device Tag User
Non-functional Security & Authentication,
UNI.504 Privacy, Access device (ID of an read it. So, (none) Security Physical entity
Requirement Privacy Key Exchange
Control RFID tag for authoized persons Virtual Entity
& Management
example) by are the owner and
unauthorised the persons who
entities. are authorized by
the owner. The
"unauthorized
entities" are all the
other people.
A system built using Maintain operation
Configuration,
Functional Energy- the ARM shall in environments
UNI.505 Functional (none) Management, Performance, Device
Requirement awareness support connecting where power
Member
devices able to do supply is not

46 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
energy harvesting. possible.
A system built using
the ARM shall
Use of standard
support
Interoperability, interfaces will
Design communication Evolution & Network
UNI.506 Data handling & enable take up of (none) Communication Device
Constraint accross devices by Interoperability Communication
communication IOTA concept on
aid of standardised
the market
communication
interfaces.
Security in end-to-
A system built using end
Security,
the ARM shall communication Authorisation,
Non-functional Privacy, Data Security &
UNI.507 support data does not address (none) Security Key Exchange Resource, Device
Requirement handling & Privacy
security & privacy security issues & Management
communication
at atomic level pertaining to the
device itself.
A system built using
the ARM shall
support intermittent
Non-functional Data handling & Avoid traffic Evolution &
UNI.508 and command- (none) (none specific) (none specific) (none)
Requirement communication overhead Interoperability
based
communication with
devices
Enable object
Each IoT device
recognition and
shall possess a
Non-functional setup/configuration Evolution &
UNI.509 Self-description universal ID, part of (none) (none specific) (none specific) Resource
Requirement in the context of Interoperability
it read only and part
applications
of it read/write.
development
Atomic-level
Atomic-level protocols are the
protocols must protocols realised
implement only to carry out a
Functional
UNI.510 Security functions related to particular task Functional (none) (none specific) (none specific) Device
Requirement related to device
data acquisition
(e.g. DSP-level), internal functions.
crypto and security E.g. how data are
acquired from the

47 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
environmnet. How
they are
encoded/encrypted
for transportation
of unreliable
networks, etc. This
requirements is
needed to avoid
overlap with user-
level
communication
protocols.
IoT faces many
issues in that
complex features
have been to be
made available on
A system built using restrained devices
the ARM shall be (memory size,
scalable, that is, CPU speed, power
usable on very tight consumption). For
Energy- resources with example, can an Performance
awareness, potentially reduced OS be run on and
Non-functional
UNI.511 Availability, features (e.g., the something like an (none) Scalability, (none specific) (none specific) Device, Resource
Requirement
Autonomicity, level of security 8-bit CPU, 8 KB Security and
Resilience may be different RAM, 64 KB flash Privacy
depending on the platform? Or can
underlying use of symmetric
hardware crypto algorithms
resources) (e.g., AES) be run
on resource-
constraint
platforms w/ AES
co-processor
functionality?
An application shall IoT systems are
Energy-
Non-functional share information often resource Performance
UNI.512 awareness, (none) (none specific) (none specific) Device, Resource
Requirement about resource constrained, and Scalability
Autonomicity
usage (for instance, especially in terms

48 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
of energy
consumption.
when will the Optimum energy
application need to efficency can only
transmit a be achieved by
message) with cross-functional-
other functional layer optimisation,
layers. which is dependent
on application
needs.
The services
provided by the
infrastructure
should always be
available, as their
A system built using operation is critical Availability
Security, the ARM shall to the operation of and IoT Service
Non-functional
UNI.601 Availability, guarantee the Internet of (none) Resilience, IoT Service, Security Resolution, IoT (none)
Requirement
Resilience infrastructure Things. Users (Security and Service
availability should thus be Privacy)
able to reach the
infrastructure. The
infrastructure
services should be
able to operate.
The "infrastructure
services" of a
system built using The services IoT Service
the ARM (i.e. provided by such Resolution, VE
Non-functional Security and IoT Service, Security,
UNI.602 Privacy, Trust resolution services, "infrastructure (none) Resolution, User, Service
Requirement Privacy Management
security services, services" should (none specific),
management be trustworthy. (none specific)
services) shall be
trustable
The "infrastructure Such IoT Service
services" of a "infrastructure Resolution, VE
Functional Operation, IoT Service, Security,
UNI.603 Integrity system built using services" should (none) Resolution, (none)
Requirement (Deployment) Management
the ARM (i.e. operate properly (none specific),
resolution services, according to their (none specific)

49 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
security services,
management
services) shall
comply with the design.
infrastructure
service design and
operate accordingly
Access to the
service shall be
regulated by
Availability
Security, Access A service shall access policies.
and IoT Service
Non-functional control, always be Users entitled in
UNI.604 (none) Resilience, IoT Service, Security Resolution, IoT Service
Requirement Availability, accessible to access policies to
(Security and Service
Resilience entitled users envoke a given
Privacy)
service must be
able to actually
envoke it.
Some scenarios
require Subjects to
take responsibility
for their actions.
Some Services
could be classified
or critical for their
A system built using provider and could
the ARM shall require Users to
support the take responsibility
IoT Service,
Non-functional reversing of the of their action. On Security and
UNI.605 Privacy, Trust (none) IoT Service, Security Identity User, Service
Requirement pseudonymization the other hand Privacy
Management
processes in order Users might need
to guarantee mutual providers to take
accountability responsibility for
the Services they
provide, because
relying on such
Services is critical
for them. The IoT
should support the
reversing of the

50 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
Pseudonymization
processes.
A system built using IoT Service
Subjects should
the ARM shall Resolution, IoT
Non-functional Privacy, Non- not be able to track Security and
UNI.606 make the (none) IoT Service, Security Service, Identity User, Service
Requirement repudiation the digital activities Privacy
traceability of digital Management,
of other subjects
activities impossible Authorization
The exchange of
information
between Subjects
(Users and
Services) should
be understandable
A system built using
only for the
the ARM shall IoT Service,
Functional intended
UNI.607 Privacy, Trust provide Functional (none) IoT Service, Security Key Exchange User, Service
Requirement recipients. This is
communication & Management
a generic
confidentiality
communication
requirement
because it can be
achieved at
different layers of
the the stack.
The messages
exchanged
between subjects
A system built using must be delivered
the ARM shall in a complete and (none specific),
Functional Security, Communication,
UNI.608 support coherent way. It Functional (none) Key Exchange User, Service
Requirement Integrity Security
communication can affect & Management
integrity communications at
different layers
(MAC, NWK,
TRA).
The system should
A system built using
be protected from
Non-functional Security, the ARM shall Security and Key Exchange
UNI.609 replay attacks (none) Security Device, Service
Requirement Integrity ensure Data Privacy & Management
(message replays
Freshness

51 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
at Service level,
packet replay at
network and link
layer level).
Services providing
access to
Resources must
be reachable by
the Users who
might need to rely
on them. This
Availability IoT Service,
A system built using requirement has a
and Authentication,
Non-functional Security, the ARM shall specific IoT
UNI.610 (none) Resilience, IoT Service, Security Authorization, Service, Device
Requirement Availability provide IoT-Service declination as the
(Security and Trust &
availability resources of many
Privacy) Reputation
nodes will be
constrained and
specific ways to
protect from DoS
or exhaustion
attacks will be
needed.
The control of User
access to
Resources must
be supported and,
where needed,
A system built using regulated by IoT Service,
Non-functional Security, Access the ARM shall policies. Security and Authorisation,
UNI.611 (none) IoT Service, Security User, Service
Requirement control support access Anonymous Privacy Identity
control mechanisms interaction must be Management
supported and
group
authorization
should be
supported.
A system built using Subjects (Users IoT Service,
Non-functional Security, Security and
UNI.612 the ARM shall and Services) (none) IoT Service, Security Authentication, User, Service
Requirement Privacy, Trust Privacy
support mutual must be able to Identity

52 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
subject confirm the identity
Management
authentication of other Subjects.
As there is a high
chance of nodes
being
compromised due
A system built using
to their physical IoT Service,
Functional the ARM shall be
UNI.613 Security, Trust availability to Functional (none) IoT Service, Security Trust & Service
Requirement able to meter
malicious users, a Reputation
service reputation
secondary
mechanism for
establishing trust is
needed.
In networks where
nodes are
constrained
devices with
limited
communication
capabilities, QoS
might have a new
IoT Service
(or extended)
Resolution, IoT
meaning
Service, Hop to
compared to the
A system built using Hop
current meaning. Operation, IoT Service,
Functional the ARM shall Communication,
UNI.614 Security, QoS For example, real- (Deployment), (none) Communication, Device
Requirement provide Quality of End to End
time, event- Functional Management
Service Communication,
triggered data with
Network
high time
Communication,
resolution, needs
Performance
to be delivered
with a higher
priority than other
and might need to
ignore the need to
sleep of some
devices in the
network.

53 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
While congestion
avoidance is
A system built using
important in any
Non-functional the ARM shall Perfomance End to End
UNI.615 QoS large network, in (none) Communication Device
Requirement provide transport and Scalability Communication
low bandwidth
layer fairness
mesh networks
this is essential.
The network
functions should
A system built using be available to
Availability
Non-functional Security, the ARM shall network endpoints.
UNI.616 (none) and (none specific) (none specific) Device
Requirement Availability ensure network Appropriate
Resilience
availability measures should
be taken to avoid
network disruption.
Packet routing
over underlying
Link Layer should
be efficient and
should not be
A system built using Hop to Hop
subject to
Non-functional Security, the ARM shall Security and Communication, Communication,
UNI.617 disruption by (none) Device
Requirement Integrity enforce correct Privacy Security Trust Authority,
malicious subjects.
routing Authentication
Disruption could
lead to
worm/blackhole,
exhaustion and
DoS attacks.
In some cases hop
A system built using by hop
the ARM shall have communication Hop to Hop
Non-functional Security, Access Security and Communication,
UNI.618 a communication should only be Functional Communication, Device
Requirement control Privacy Security
control for restricted available to Authentication
usage authenticated
devices.
A system built using Mobile devices Authorisation,
Non-functional Security, Non- the ARM shall should be able to Security and Trust &
UNI.619 (none) Security Device
Requirement repudiation ensure non join peripheral Privacy Reputation,

54 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
networks
belonging to
different provider.
repudiation at
Devices entitled to Authentication
network level
join a given
network must be
able to do so.
The software
A system built using
execution
Non-functional Security, the ARM shall Security and Certification
UNI.620 environment (none) Security Service
Requirement Integrity provide Software Privacy Authority
should preserve
Integrity
software integrity.
A node that is
considered fixed
should not be
A system built using
moved from its
the ARM shall
Functional Security, position. This Security and Trust &
UNI.622 support device Functional Security Device
Requirement Integrity could alter the Privacy Reputation
location
quality of the data
identification
provided as it
refers to a different
position.
The Location of a
Subject should
only be available
to authorized IoT Service,
A system built using
Subjects. Specific Autorisation, VE
Non-functional Privacy, the ARM shall Security and IoT Service, Virtual
UNI.623 methods for Functional Resolution, IoT Service
Requirement Geolocation support location Privacy Entity, Security
obscuring both Service
privacy
network and Resolution
physical location
should be
available.
While complete
A system built using
anonymity is not
the ARM shall
Non-functional feasibe in an IoT Security and Identity Device, Service,
UNI.624 Privacy provide (none) Security
Requirement scenario, Privacy Management User
pseudonymisation
pseudonimity
mechanisms

55 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
should be
supported.
Users should be
A system built using able to monitor
Security,
the ARM shall and control the
Functional Privacy, Security and
UNI.625 provide a device security and Functional Security (none specific) Device
Requirement Security Privacy
security and privacy privacy settings of
management
measurement all the devices that
they own.
The Execution
Environment and
The IoT should
the Services Authorisation,
Security, support secure
Non-functional provided on a Security and Authentication,
UNI.626 Security Over-the-Air/Over- (none) Security, Management Device
Requirement given remote Privacy Device
management the-Network Device
device should be Manager
Management
securely managed
from remote.

"New applications
can change traffic
characteristics in a
few months. In the
past decade
several
applications
dramatically
changed the way
A system built using how the Internet is
used. Nobody has
the ARM shall actually foreseen
accomodate fast the success of
Non-functional P2P networks, and (none) Evolution and
UNI.701 Evolvability developmental (none specific) (none specific) (None)
Requirement especially Youtube Interoperability
changes in and Facebook.
applications and Thus, the question
network is whether it is
possible to design
a Future Internet
without having any
ideas what the
“next big things”
could be. If thus
the traffic changes
are unpredictable,
then we need to
establish a fast

56 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
and stable
infrastructure
without any
assumptions on
the traffic."
[G. Drea Rodosek,
A. Pras, H.
Schulzrinne, and
B. Stiller, "Learning
from the Past:
Implications for the
Future Internet and
its Management?",
Dagstuhl Seminar
11042, 2011]

"The waterfall
model does not
work in practice in
communications,
for sure, software
is not a “one-time
instance”, changes
will occur for some
time. Thus,
A system built using versions are
the ARM needed, and for
Non-functional Evolvability, development shall protocols we may
UNI.702 arrive at the same (none) (none specific) (none) (none specific) (None)
Requirement autonomicity support iterative iterative refinement
approaches (e.g. approach."
spiral model) [G. Drea Rodosek,
A. Pras, H.
Schulzrinne, and
B. Stiller, "Learning
from the Past:
Implications for the
Future Internet and
its Management?",
Dagstuhl Seminar
11042, 2011]

"Full decoupling of
planes
A system built using (management,
Design the ARM shall be user, control) is
UNI.703 Architecture Functional (none specific) (none) (none specific) (None)
constraint based on a cross- good in an “old-
style telco world”,
layered architecture however, it will not
work in the Future
Internet."

57 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component

[G. Drea Rodosek,

A. Pras, H.
Schulzrinne, and
B. Stiller, "Learning
from the Past:
Implications for the
Future Internet and
its Management?",
Dagstuhl Seminar
11042, 2011]

There is no future
for a centralized
management (in
most cases). It is
necessary to move
the research effort
towards self-
management
approaches.
[G. Drea Rodosek,
A. Pras, H.
Schulzrinne, and
A system built using B. Stiller, "Learning
from the Past:
the ARM shall Implications for the
Functional Performance,
UNI.704 Autonomicity exhibit self- Future Internet and Functional (none specific) Management (None)
Requirement its Management?", Member, State
management
Dagstuhl Seminar
behaviour 11042, 2011]
[S. Kim, M. Choi,
H. Ju, M. Ejiri, J.
Hong, "Towards
management
requirements of
Future Internet",
In: "Challenges for
next generation
network operations
and service
management.",
Springer, 2008, pp
156–166]

A system built using The need for self-

configuration in
Functional the ARM shall be access networks, Functional Performance Configuration,
UNI.706 Autonomicity Management (None)
Requirement capable of self- programmable and Scalability Member
configuration nodes.

58 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component

[G. Drea Rodosek,

A. Pras, H.
Schulzrinne, and
B. Stiller, "Learning
from the Past:
Implications for the
Future Internet and
its Management?",
Dagstuhl Seminar
11042, 2011]
[ T. Töyry, "Self-
management in
Internet of Things"]

"The management
plane shoud be
operationally
independent of the
data plane and
should be able to
bootstrap without
any pre-
configuration."
The system
Functional [S. Kim, M. Choi, Performance Configuration,
UNI.708 Autonomicity management shall H. Ju, M. Ejiri, J. Functional Management (None)
Requirement and Scalability Member
auto-bootstrap Hong, "Towards
management
requirements of
Future Internet",
In: "Challenges for
next generation
network operations
and service
management.",
Springer, 2008, pp
156–166]

"The operational
A system built using complexity of
the ARM shall protocols should
be confined to their
provide a single, implementation,
Functional Architecture, simple and they should
UNI.709 express the Functional (none specific) Management (none specific) (None)
Requirement Usability management
information
interface for all required for
communication managing them
protocols through a simple
management
interface. This

59 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
includes the
responsibility on
the protocol
implementer for a
detailed
understanding of
the protocol
operation while
reducing the
burden on
management
applications."
[S. Kim, M. Choi,
H. Ju, M. Ejiri, J.
Hong, "Towards
management
requirements of
Future Internet", In:
"Challenges for
next generation
network operations
and service
management.",
Springer, 2008, pp
156–166]

"Management of
the Future Internet
architecture will
require data on the
current state of the
network, available
in real time. The
challenge is that
A system built using the proposed
the ARM shall instrumentation
systems can
include a potentially gather
Functional
UNI.710 Architecture management vast quantities of Functional (none specific) Management Member, State (None)
Requirement
repository to store high-dimensional
data. This implies
information on the the requirement of
state of the system a repository unit
that will organize
the measurement
data."
[S. Kim, M. Choi,
H. Ju, M. Ejiri, J.
Hong, "Towards
management
requirements of

60 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
Future Internet", In:
"Challenges for
next generation
network operations
and service
management.",
Springer, 2008, pp
156–166]

"[...] the
management
systems and
operations of
Future Internet
must be scalable
in order to support
thousands and
millions of different
network devices
and to provide
services."
[S. Kim, M. Choi,
H. Ju, M. Ejiri, J.
The Internet of Hong, "Towards
Things shall not management
Non-functional impact the requirements of Performance
UNI.711 Scalability Future Internet", (none) (none) (none specific) (None)
Requirement scalability of the In: "Challenges for and Scalability
management of the next generation
Future Internet. network operations
and service
management.",
Springer, 2008, pp
156–166]
[Q. Wang, R.
Jäntti, Y. Ali, "On
Network
Management for
the Internet of
Things", 8th
Swedish National
Computer
Networking
Workshop
(SNCNW) , 2012]
The Management
"We assume that
Non-functional functionalities of there may exist Evolution and
UNI.712 Interoperability two IoT systems different network (none) Management (none specific) (None)
Requirement Interoperability
shall be able to management
systems that play

61 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
different roles such
as security and
performance. Also,
interactions occur
between network
management
systems in
different domains."
[S. Kim, M. Choi,
H. Ju, M. Ejiri, J.
interoperate. Hong, "Towards
management
requirements of
Future Internet", In:
"Challenges for
next generation
network operations
and service
management.",
Springer, 2008, pp
156–166]

Management
system shall react
to dynamic
operation [and
system] changes
Management in real time.
functionalities shall
[Q. Wang, R.
Non-functional react to dynamic Jäntti, Y. Ali, "On Performance
UNI.713 Performance (none) Management (none specific) (None)
Requirement operation and Network and scalability
system changes in Management for
the Internet of
real time Things", 8th
Swedish National
Computer
Networking
Workshop
(SNCNW), 2012]

Management
The system system shall meet
device constraints
Energy- management shall such as energy
Non-functional awareness, pay attention to and memory. Performance Performance,
UNI.714 (none) Management (None)
Requirement Radio- device constraints and scalability Member, State
[Q. Wang, R.
awareness such as energy and Jäntti, Y. Ali, "On
memory Network
Management for
the Internet of

62 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
Things", 8th
Swedish National
Computer
Networking
Workshop
(SNCNW), 2012]

In order to meet
device and system
constraints, the
collection of
system states is
A system built using important.
the ARM shall [Q. Wang, R.
Functional Jäntti, Y. Ali, "On Functional
UNI.715 Autonomicity perform data (none specific) Management (none specific) (None)
Requirement Network
collection on its Management for
current state the Internet of
Things", 8th
Swedish National
Computer
Networking
Workshop
(SNCNW) , 2012]

"Management
should cause as
little overhead as
possible for the
underlying
networks
considering the
resource
constraints of the
IoT. To fulfill this,
Management of the unnecessary
envisioned system communication
Non-functional should be avoided. Performance
UNI.716 Scalability shall incur low For example, (none) Management (none specific) (None)
Requirement and scalability
communication broadcast and
overhead multicast
messages could
be used to replace
unicast messages
if applicable.
History query
results could be
stored at some
proxy points for
future queries
instead of flooding

63 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
all query
messages into the
network. Message
headers and data
should also be
compressed if
possible."
[Q. Wang, R.
Jäntti, Y. Ali, "On
Network
Management for
the Internet of
Things", 8th
Swedish National
Computer
Networking
Workshop
(SNCNW) , 2012]

"The system can

measure its
current
performance and it
is able to compare
it against to the
known optimum
level of
performance. The
A system built using
system will adjust
Functional the ARM shall be its operation to Performance
UNI.717 Autonomicity (none) Management (none specific) (None)
Requirement able to perform self- reach closer the and scalability
optimal
optimisation
performance. The
system is also able
to change its
operation to cope
with new user set
policies."
[ T. Töyry, "Self-
management in
Internet of Things"]

"The system tries

to recover from
Resilience, The system shall be faults or to avoid
Non-functional them. Self-healing Availability
UNI.718 Availability, able to perform self- can be (none) Management (none specific) (None)
Requirement and resilience
Autonomicity healing implemented in
two different
styles. They are
reactive and

64 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
proactive modes.
In reactive mode
the system detects
and recovers from
faults as they
occur. The system
also tries to repair
the faulted
functions if
possible. In
proactive mode the
system monitors its
state to detect and
adjust its
behaviour before
reaching an
undesired state."
[ T. Töyry, "Self-
management in
Internet of Things"]

"The system
defends itself
against internal
and external
threats, which can
be accidental,
such as cascading
failures, or
A system built using malicious attacks
Autonomicity, against the Fault, State,
Non-functional the ARM shall be Security and
UNI.719 Resilience, system. To (none) Management, Security Trust and (None)
Requirement able to perform self- manage the Privacy
Availability Reputation
protection threats the system
must be aware of
its environment
and have means to
react to detected
threats."
[ T. Töyry, "Self-
management in
Internet of Things"]
The system
"The management
management shall plane shoud be
Non-functional be operationally operationally
UNI.721 Architecture independent of the independent of the Functional (none specific) Management (none specific) (None)
Requirement data plane and
specifics of the should be able to
communication bootstrap without
any pre-

65 of 66 25/04/2024, 10:46
Requirements — IOT-A: Internet of Things Architecture https://www.iot-a.eu/public/requirements/

UNI ID Requirement Category Description Rationale View Perspective Functionality Group Functional Domain Model
Type Component
configuration."
[S. Kim, M. Choi,
H. Ju, M. Ejiri, J.
Hong, "Towards
management
requirements of
functionality. Future Internet", In:
"Challenges for
next generation
network operations
and service
management.",
Springer, 2008, pp
156–166]

66 of 66 25/04/2024, 10:46