ETSI TR 104 027 V1.1.1 (2025-10)

User-Centric Approach in the digital ecosystem; The User Information System and Smart Customized Services; Concept, definition and services

DTR/USER-0055

General Information

• Status: Not Published
• Technical Committee: USER - User Group
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 18-Nov-2025
• Completion Date: 31-Oct-2025

Standards Content (Sample)

TECHNICAL REPORT
User-Centric Approach in the digital ecosystem;
The User Information System and
Smart Customized Services;
Concept, definition and services

2 ETSI TR 104 027 V1.1.1 (2025-10)

Reference
DTR/USER-0055
Keywords
QoS, security, UIS, USER
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

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

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

© ETSI 2025.
All rights reserved.
ETSI
3 ETSI TR 104 027 V1.1.1 (2025-10)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 9
3.3 Abbreviations . 9
4 Smart Customized Services for UIS . 10
4.1 Identification of the problem to be solved . 10
4.2 Application of the ACIFO model in SCS . 12
5 Use cases for User Information Systems . 13
5.1 Introduction to use cases for UIC and their service composition . 13
5.2 Urban mobility use case (Smart Urban Mobility Assistant) . 14
5.3 Agriculture . 16
5.4 Health . 19
5.5 Assurance of Health and Safety in an IoT enabled construction environment . 20
6 Regulatory and other constraints that may apply to UIS/SCS . 21
6.1 Data governance . 21
6.2 Privacy and data protection . 22
6.3 Security . 22
6.4 Data semantics and ontology . 23
6.5 Accessibility . 23
6.6 Ethics Considerations . 23
7 Recommendations for further specification of ACIFO in SCS . 25
7.1 General requirements for the Digital Ecosystem . 25
7.1.1 Overview and introduction . 25
7.1.2 The architectural dimension . 26
7.1.3 The communication dimension . 27
7.1.4 The Informational Dimension: . 28
7.1.5 The functional Dimension . 29
7.1.6 The Organizational Dimension . 31
7.2 UIS/SCS requirements User side (userware) . 31
7.2.1 Userware Interactions with the ecosystem components . 31
7.2.2 User Centric Vision . 33
Annex A: Assist-IoT project overview . 34
Annex B: i-Tour project overview . 35
Annex C: i-locate project overview . 37
Annex D: Detail of regulatory factors to be considered in UIC/SCS. 38
D.1 Privacy aspects . 38
D.1.1 General overview . 38
D.1.2 Identification of Data Controller . 38
D.1.3 Identification of Data Processor . 38
D.1.4 Identification of affected user (data subject) . 38
D.1.5 Other privacy impacting aspects . 39
ETSI
4 ETSI TR 104 027 V1.1.1 (2025-10)
D.2 Security. 40
D.3 Data semantics and ontology . 41
D.4 Data portability . 41
D.5 Accessibility aspects. 42
Annex E: Example of Application of ACIFO model to tomato cultivation (user side ). 45
E.1 Overview . 45
E.2 Functions and features . 45
E.2.1 Real-time environmental (Sensors → UIS) . 45
E.2.2 Anomaly detection (Userware) . 46
E.2.3 Expert validation and AI model selection (Agronomy Expert) . 46
E.2.4 AI-based anomaly analysis (AI Engine) . 46
E.2.5 Corrective recommendations (Userware + Expert support) . 46
E.2.6 Farmer decision-making and feedback (Farmer → Userware) . 46
Annex F: Bibliography . 47
History . 48

ETSI
5 ETSI TR 104 027 V1.1.1 (2025-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Technical Report (TR) has been produced by ETSI Special Committee User Group (USER).
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI
6 ETSI TR 104 027 V1.1.1 (2025-10)
1 Scope
The present document presents an analysis of the user expectations, with respect to the study of data driven technologies
(Artificial Intelligence (AI), deep learning, Machine Learning (ML)) to present the definition and concept of the User
Information System (UIS), that enables Smart Customized Services (SCS) from both user and provider side. These
services aim to provide personalization, adaptability, and intelligent decision support within the digital ecosystem.
NOTE: The UIS and SCS are designed to serve a broad spectrum of users. Their objective is to empower and
protect all citizens. By integrating smart and assistive technologies, the system seeks to enhance
participation in public, social, and economic activities, while also offering advanced users more
autonomy and self-management capabilities.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
[i.1] ETSI TR 103 438: "User Group; User centric approach in Digital Ecosystem".
[i.2] ETSI EG 203 602: "User Group; User Centric Approach: Guidance for users; Best practices to
interact in the Digital Ecosystem".
[i.3] ETSI TR 103 603: "User Group; User Centric Approach; Guidance for providers and
standardization makers".
[i.4] ETSI TR 103 604: "User Group; User centric approach; Qualification of the interaction with the
digital ecosystem".
[i.5] Directive (EU) 2019/882 of the European Parliament and of the Council of 17 April 2019 on the
accessibility requirements for products and services (Text with EEA relevance).
[i.6] EN 301 549 (V3.2.1) (2021-03): "Accessibility requirements for ICT products and services".
[i.7] ISO 9241-210:2019: "Ergonomics of human-system interaction; Part 210: Human-centred design
for interactive systems", Edition 2; 2019.
[i.8] Interaction Design Foundation: "Design for All".
[i.9] Centre for Excellence in Universal Design: "The 7 Principles".
[i.10] ETSI EG 202 116 (V1.2.2) (2009-03): "Human Factors (HF); Guidelines for ICT products and
services; "Design for All"".
[i.11] ETSI TS 102 747 (V1.1.1) (2009-12): "Human Factors (HF); Personalization and User Profile
Management; Architectural Framework".
ETSI
7 ETSI TR 104 027 V1.1.1 (2025-10)
[i.12] ETSI ES 202 746 (V1.1.1) (2010-02): "Human Factors (HF); Personalization and User Profile
Management; User Profile Preferences and Information".
[i.13] University of East London: "Exploring the Ethical Implications of AI-Powered Personalization in
Digital Marketing".
[i.14] EU TAi Guidelines.
[i.15] ETSI TR 104 221: "Securing Artificial Intelligence (SAI); Problem Statement".
[i.16] ETSI TS 104 224: "Securing Artificial Intelligence (SAI); Explicability and transparency of AI
processing".
[i.17] ETSI TS 104 102: "Cyber Security (CYBER); Encrypted Traffic Integration (ETI); ZT-Kipling
methodology".
[i.18] ETSI TR 103 477: "eHEALTH; Standardization use cases for eHealth".
[i.19] Assist-IoT project report D3.2: "Use Cases Manual & Requirements and Business Analysis -
Initial".
[i.20] Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the
protection of natural persons with regard to the processing of personal data and on the free
movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation).
[i.21] The EU project i-Tour.
[i.22] Lazarotto, B.: "The right to data portability: A holistic analysis of GDPR, DMA and the Data Act".
[i.23] ETSI EN 303 760 (V1.1.1) (2024-10): "SmartM2M; SAREF Guidelines for IoT Semantic
Interoperability; Develop, apply and evolve Smart Applications ontologies".
[i.24] ETSI TR 103 875-2: "User Centric approach in Digital Ecosystem; The Smart Interface; Part 2:
Smart Identity: A Proof of Concept".
[i.25] ETSI TR 103 437: "USER; Quality of ICT services; New QoS approach in a digital ecosystem".
® ® ®
[i.26] OMG UML : "OMG Unified Modeling Language ", Version 2.5.1.
[i.27] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on
electronic identification and trust services for electronic transactions in the internal market and
repealing Directive 1999/93/EC (eIDAS).
[i.28] Regulation (EU) 2024/1183 of the European Parliament and of the Council of 11 April 2024
amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity
Framework (eIDAS2).
[i.29] ETSI EN 319 401: "Electronic Signatures and Trust Infrastructures (ESI); General Policy
Requirements for Trust Service Providers".
[i.30] Brandt Dainow: "Digital Alienation as the Foundation of Online Privacy Concerns".
[i.31] ETSI TR 119 476: "Electronic Signatures and Trust Infrastructures (ESI); Analysis of selective
disclosure and zero-knowledge proofs applied to Electronic Attestation of Attributes".
[i.32] ETSI TS 103 486: "CYBER; Identity Management and Discovery for IoT".
[i.33] ISO/IEC 7498-1: "Information technology -- Open Systems Interconnection - Basic Reference
Model: The Basic Model".
[i.34] Foureaux, Simon & Daum, Thomas (2025): ""But don't think it is a game": Agricultural
videogames and "good farming"". Journal of Rural Studies. 117. 10.1016/j.jrurstud.2025.103686.
[i.35] ETSI Directives.
ETSI
8 ETSI TR 104 027 V1.1.1 (2025-10)
[i.36] Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 on
horizontal cybersecurity requirements for products with digital elements and amending
Regulations (EU) No 168/2013 and (EU) 2019/1020 and Directive (EU) 2020/1828 (Cyber
Resilience Act).
[i.37] Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on
measures for a high common level of cybersecurity across the Union, amending Regulation (EU)
No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148
(directive SRI 2).
[i.38] Sasan Rostambeik, Noemi Simoni, Antoine Boutignon: "Userware: A framework for next
generation personalized services", Computer Communications, Volume 30, Issue 3, 2007,
Pages 619-629, ISSN 0140-3664.
[i.39] "OGC City Geography Markup Language (CityGML); Part 1: Conceptual Model Standard".
[i.40] "OGC City Geography Markup Language (CityGML); Part 2: GML Encoding Standard".
[i.41] The EU project iLocate.
[i.42] The EU project Assist-IoT.
[i.43] Waze.
[i.44] Regulation (EU) 2022/1925 of the European Parliament and of the Council of 14 September 2022
on contestable and fair markets in the digital sector and amending Directives (EU) 2019/1937 and
(EU) 2020/1828 (EU Digital Markets Act (DMA)).
[i.45] ETSI TS 102 165-2: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Methods and protocols; Part 2: Protocol Framework Definition;
Security Counter Measures".
NOTE: An update is in preparation to a CYBER document at the time of preparation of the present document.
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the following terms apply:
Architecture Communication Information Function Organization (ACIFO) model: framework for interpreting and
analysing complex systems whole through the five dimensions that characterize it
artificial intelligence: ability of a system to handle representations, both explicit and implicit, and procedures to
perform tasks that would be considered intelligent if performed by a human
avatar: representation of the user in digital form
digital ecosystem: network of interconnected digital technologies, platforms, and services that interact with each other
to create value for businesses and consumers and facilitate access to digital technology for everyone
machine learning: branch of artificial intelligence concerned with algorithms that learn how to perform tasks by
analysing data, rather than explicitly programmed
reinforcement learning: form of machine learning where a policy defining how to act is learned by agents through
experience to maximize their reward; and agents gain experience by interacting in an environment through state
transitions
semi-supervised learning: form of machine learning where the data set is partially labelled. In this case, even the
unlabelled data can be used to improve the quality of the model
supervised learning: form of machine learning where all the training data is labelled and the model can be trained to
predict the output based on a new set of inputs
ETSI
9 ETSI TR 104 027 V1.1.1 (2025-10)
unsupervised learning: form of machine learning where the data set is unlabelled, and the model looks for structure in
the data, including grouping and clustering
User Platform as a Service (UPaaS): userware developed according to the "aas" model
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
aaS as a Service
ACIFO Architecture Communication Information Function Organization
AI Artificial Intelligence
API Application Programming Interface
AR Augmented Reality
DaaS Device as a Service
DAC Discretionary Access Control
DMA Digital Market Act
DTP Data Transfer Project
E2E End-to-End
eIDAS electronic IDentification, Authentication and trust Services
EUDI EU Digital Identity Wallet
GDPR General Data Protection Regulation
GIS Geographic Information Systems
HMI Human Machine Interface
IaC Infrastructure as Code
ICT Information & Communications Technology
IoT Internet of Things
MAC Mandatory Access Control
ML Machine Learning
NaaS Network as a Service
ODA Open Distributed Architecture
OSH Occupational Safety and Health
PaaS Platform as a Service
PPE Personal Protective Equipment
QoE Quality of Experience
QoS Quality of Service
SaaS Software as a Service
SAREF Smart Applications REFerence ontology
SCS Smart Customized Service
SOA Service-Oriented Architecture
SUMA Smart Urban Mobility Assistant
UDR User Digital Representation
UIS User Information System
UML Unified Modelling Language
UPaaS User Platform as a Service
ETSI
10 ETSI TR 104 027 V1.1.1 (2025-10)
4 Smart Customized Services for UIS
4.1 Identification of the problem to be solved
Users of digital services have historically had limited ability to control the use of personal data by digital services and
how a service shares that data with other services, nor is there usually fine-grained control of what is given in terms of
personal data, rather there is often a "share all" approach to how data is released. Whilst users are protected by a number
of legislative instruments (see clause 6 and Annex D, for a broad summary of these instruments), the control is often
passed to the service provider and the user is often not directly involved in the way in which their data is used or how a
service is composed from component services. Whilst there are a number of technical means to restrict the personal data
given to a service, e.g. by selective disclosure as outlined for eIDAS [i.27], [i.28] and the EU Digital Identity Wallet
(EUDI) in ETSI TR 119 476 [i.31], or by application of specific permutations of a user profile following the approach
of ETSI TS 103 486 [i.32], there are wider implications and requirements that are considered in the present document
that seek to empower the user's control of personal data.
NOTE 1: In the eIDAS2 regulation [i.28] it is stated in Recital 59 that "Selective disclosure is a concept
empowering the owner of data to disclose only certain parts of a larger data set, in order for the
receiving entity to obtain only such information as is necessary for the provision of a service requested by
a user. The European Digital Identity Wallet should technically enable the selective disclosure of
attributes to relying parties. It should be technically possible for the user to selectively disclose attributes,
including from multiple, distinct electronic attestations, and to combine and present them seamlessly to
relying parties. This feature should become a basic design feature of European Digital Identity Wallets,
thereby reinforcing convenience and the protection of personal data, including data minimization".
Addressing only the user's data and its selective disclosure is not sufficient, rather the services that are offered to, or
built by the user, also have to be cognizant of the problems that users face in having assurances of the protection of
personal data, including data minimization whilst maximizing the conveniences of the digital ecosystem. To this end the
present document expands the idea of user by considering the user as an information system (the User Information
System (UIS)) in the context of Smart Customized Services (SCS). In this respect it is noted that the concept of user
centric design is well established in many industries and describes an approach wherein products and services are
explicitly developed around the user. This does not imply bespoke design and manufacture, rather it allows the user to
choose aspects of the way the service is presented and accessed, particularly in the ICT domain by personalization of
user interfaces. By allowing for greater control of how data is used and how services are constructed using the UIS/SCS
model the user is afforded control of, and maintenance of, their personal autonomy. The userware (see [i.38]) is then a
means of allowing the user to explicitly control their autonomy within the provision of services.
The role and purpose of SCS is to place the user at the centre of their own digital ecosystem as the UIS (i.e. allows users
to have control of their autonomy), being a virtual representation of the user's preferences as an information element and
active entity. The UIS in SCS is therefore a persistent digital object in the service domain, representing an intelligent
agent of the user (i.e. as an AI-enabled avatar acting as the user).
SCS and UIS together extend and develop prior concepts of users being represented as information elements in order to
allow users to maintain control over their data and more generally their own information system in the way that they
present themselves to services and more generally online.
In order to support SCS/UIS a number of system pre-requisites have to be met. The primary pre-requisite is that service
components are considered as always available and are able to semantically and contextually identify themselves. It is
also expected that service components exhibit the following characteristics (these are expanded upon in clause 7 of the
present document):
• Statelessness: Each service should be able to process requests without retaining any request-specific or
contextual information. Operations should function independently of prior invocations.
• Autonomy: Services should execute their functionalities independently of each other.
• Loose Coupling: Connections between services should be flexible rather than rigid and not require functional
dependency on any other service.
• Cohesive: Services should be logically coherent and self-contained (see also autonomy).
ETSI
11 ETSI TR 104 027 V1.1.1 (2025-10)
• Abstract: The internal service logic should remain abstracted from external environments (i.e. independent
of).
NOTE 2: The term user in the present document is not intended to only refer to a human user but may include a
service using other services.
NOTE 3: Services can have multiple characteristics, they may be information services or interactive services, and if
a composition of services results in a new service then it is the composition that is referred to as the
service.
In addition to the technical pre-requisites identified above there is an attestation in the present document that there is a
consumer demand for more control of services (demand chain), and a matching willingness on the part of providers to
meet that demand (supply chain).
The smart component is identified as an AI element and applies intelligence to ensure that services are configured and
personalized only where the required data from UIS is appropriately acquired and curated (see ETSI TR 104 221 [i.15]
for a wider examination of the role of data in machine learning).
The UIS model and its realization in the management of services with SCS expands the models from each of ETSI
TS 102 747 [i.11] and ETSI ES 202 746 [i.12] to have a persistent user profile able to interact with multiple services.
This is shown in Figure 1 as a Venn diagram where SCS lies at the intersection of these 3 technological design
paradigms:
• User centric design:
- Addressing Quality of Experience (QoE) aligned to Quality of Service (QoS).
• Societal digitization:
- Addresses the increasingly important role of digital devices and their use to connect to services for
business, entertainment and governance representing a digital ecosystem.
• Automation:
- This includes the evolution of smart systems and the application of AI in various forms.
User centric
design
UIS/SCS
Societal
Automation
digitisation
Figure 1: Intersection of domains that identifies the role of SCS
ETSI
12 ETSI TR 104 027 V1.1.1 (2025-10)
Whilst one outcome of loosely controlled release of personal data is that of digital alienation, it is also clear that current
best practices such as for the EUDI [i.31] are not often as widely implemented as would be required to give the same
quality of experience across all user interactions with the digital world with regards to the use of personal data that
would mitigate threats such as those of digital alienation [i.30].
4.2 Application of the ACIFO model in SCS
The Venn diagram of Figure 1 is expanded first into the model given below in Figure 2 which illustrates the role of
elements of each domain on SCS. In the context of Smart Customized Services (SCS), personalization is not limited to
the adaptation of content or functionality to an individual. Analysis, through the ACIFO model, shows that it also
results from organizational choices regarding data processing and governance, which dynamically adapt to the evolving
user context and preferences. The layering that results is: Serviceware where the Platform as a service providers exist;
Networkware that provides the necessary connectivity; and Userware where user-centric services exist (see Figure 2).

Figure 2: User Centric Approach: Personalization
SCS can be further developed using the 5-dimensions of Architecture, Communication, Information, Function,
Organization (ACIFO) in the ACIFO model described in ETSI TR 103 438 [i.1], ETSI EG 203 602 [i.2], ETSI
TR 103 603 [i.3], ETSI TR 103 604 [i.4]) examined in detail for the UIS/SCS environment in clause 7. In particular
recommendations for application in a service centric environment are addressed in clause 7.1, and recommendations for
application in a user centric environment (e.g. userware) are addressed in clause 7.2 of the present document:
• Architectural Model: defines the global structure, including semantics and is optimized for the stated
objectives.
• Communication (Relational) Model: defines the exchange protocols, including HMIs (User) and APIs
(provider) exchange and management protocols over three planes: (1) Management (Monitoring), (2) Control,
and (3) Usage.
• Information Model: defines the different Profiles (User, device, service). The information covers the whole
ecosystem (equipment, network, applications, services, HMIs, User, etc.) from the offer to the resource's
availability for Users, Providers and any other partners. It is a knowledge data base representing the whole
ecosystem.
EXAMPLE 1: In the present document the information model is the UIS, which includes all of the user
preferences and contextual knowledge.
• Functional Model: defines services and service composition. The functionalities (the process) to compose any
service based on "micro-service".
ETSI
13 ETSI TR 104 027 V1.1.1 (2025-10)
EXAMPLE 2: In the present document the functional model requires that functions are available using the "as a
Service" model.
• Organization Model: defines the role of any actor and which actor is responsible of each action. ("Who is
doing what?" in terms of responsibility for processing and data governance).
The particular use of ACIFO in the present documented is augmented by application of the ZT-Kipling criteria from
ETSI TS 104 102 [i.17] which gathers knowledge of every interaction of the user (as UIS) with the system components
(via the SCS) by requiring answers to the following questions on each use: What?, Why?, When?, How?, Where?, and
Who? Whilst the application of [i.17] primarily impacts the Communication and Information elements of the ACIFO
model, the consequence is that each of the other elements of the ACIFO model (i.e. the Architectural, Functional and
Organizational elements) have to be designed in such a way that the ZT-Kipling criteria can be fulfilled.
NOTE: The ACIFO approach does not infer a specific order of addressing the dimensions but for the purposes of
the present document are presented in the order of the acronym.
5 Use cases for User Information Systems
5.1 Introduction to use cases for UIC and their service
composition
The present document adopts the model given in ETSI TR 103 477 [i.18] where it is stated that use cases are developed
to examine problem statements that are a concise description of issues that need to be solved in the context of the use
case. The purpose of the use case is to clearly describe:
• What the problem is.
• Who has that problem i.e. who will benefit when it is solved.
• What are the consequences of the problem.
• What a possible solution would be, this sets the expectations and the scope of the solution (is it a new process,
an application, etc.).
In the context of standardization the problem is multi-fold but is primarily concerned with determination of
interoperability. This may be at the application level where syntactic and semantic coherence is critical, or at any of the
layers of the OSI stack (see ISO/IEC 7498-1 [i.33]). For communications interoperability the main concerns are to give
assurance of connectivity, of routing (i.e. the ability of devices to connect in order to provide reliable transport of
information from source to sink), and of mutuality of transfer rates (i.e. to ensure that data produced at a given rate can
be consumed at the same rate). The purpose of the use cases given in the present document are to identify common
requirements of UIS and SCS. The uses cases identify multiple functions to build relatively complex systems, although
it is recognized that such systems (e.g. the urban mobility use case) are extensions of how users typically interact with
the transport systems of their local environment, the potential of UIS/SCS to accelerate interventions and to act "in the
loop" is identified by the use cases that follow. The use cases are presented to show how they impact different forms of
user (in the form of actors in the use cases), and what information is required from and between actors to enable the use
cases. It is noted that for most use cases there is a rational decomposition into multiple use cases.
Each use case identifies the actors in the use case, the principal interactions and the expected output in terms of the role
of UIS and SCS. The use cases are drawn using the conventions of the Unified Modelling Language (UML) [i.26].
NOTE: The UIS/SCS is modelled as an UML Class for the present document but may be modelled in other ways.
The generalized use case model of UIS/SCS is given in Figure 3 where each actor manages their preference set as UIS,
and creates SCSs which combine the data from the UIS of the actors with the microservices available.
ETSI
14 ETSI TR 104 027 V1.1.1 (2025-10)

Figure 3: Generalized use case model of UIS/SCS
The services used in SCS via the Compose Service use-case are micro-services that have the characteristics outlined in
clause 4.1 above.
In all cases it is assumed that the user controls which elements of the UIS are released, and that critically, the UIS has a
means of selective disclosure available natively.
5.2 Urban mobility use case (Smart Urban Mobility Assistant)
Taking the general model suggested in clause 5.1 above the following outlines the role of SUMA.
• What is the problem that SUMA seeks to solve in the UIS/SCS context?
- Existing methods of determining an optimized personal travel plan are deficient in addressing in-depth
the personal preferences and context of the user. SUMA seeks to optimize the selection and integration
of travel modes for each individual, in terms of time, cost, or environmental impact. It considers user
preferences and the context: schedules, weather, traffic disruptions, etc. Thus SUMA facilitates
user-optimized and personalized multi-modal urban travel (i.e. by the most effective mix of foot, bus,
metro, car, or bike) whether for work, leisure, shopping, health, school, social relations, etc.
• Who has that problem i.e. who will benefit when it is solved.
- The primary affected user is the person travelling. In addition having more knowledge of the real travel
requirements and the preferences and contexts in which travel solutions are required may be of benefit to
providers of travel solutions in optimizing their service composition and delivery.
• What are the consequences of the problem?
- The primary consequence at the heart of SUMA is in data collection and processing. The following data
is collected and processed:
 Personal data: (taken from the UIS and augmented on request of the service). As not all personal
data of the user is required the user consents to selective disclosure of only part of the UIS dataset
(e.g. the user's calendar or diary, health information (where such data has a consequential impact on
routing and accessibility (e.g. permanent or temporary disability), subscriptions to specific service
providers in the context of SUMA).
 Transport offer data: transport offer including prices and timetables.
 Cartographic data (GIS): Geographic Information to enable route visualization and route
calculation.
ETSI
15 ETSI TR 104 027 V1.1.1 (2025-10)
 Contextual and environmental data: weather, air pollution, connectivity…
- In addition to the data collection consequences of SUMA the following specific functionalities are
embedded:
 Route calculation: the route calculation finds and proposes a path depending on the availability of
the transport offer, the user's preferences, and the environment (e.g. the user may set preferences
for any of the fastest or shortest or least expensive routing taking into account the current context
(i.e. things that impact the plan such as congestion, industrial action and so forth)).
 Notifications and alerts: departure notification, guidance notification, recommendations,
subscription renewal.
 guidance: information regarding direction to take step by step.
 Recommendations on the way: possibility of partnership with businesses or services present on
the route and able to meet needs of the user identified in the agenda for example.
 Subscription management: bus, metro, parking, self-service bike or vehicle…
 Statement: finance, health, environment: a reporting in term of expense, health, impact
environment.
• What a possible solution would be?
- The wider deployment of user centric "as a service" components in the transport domain.
The user preferences for SUMA are taken from the UIS and SUMA as a whole represents an instantiation of the SCS
model.
Figure 4: SUMA data and functional architecture
ETSI
16 ETSI TR 104 027 V1.1.1 (2025-10)
A specific example within the SUMA us
...