<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Increasingly-Autonomous CPS: Taming Emergent Behaviors from an Architectural Perspective</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jerome Hugues</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniela Cancila</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Carnegie Mellon University, Software Engineering Institute</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Université Paris-Saclay, CEA, List</institution>
          ,
          <addr-line>F-91120, Palaiseau</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The safety demonstration of Increasingly-Autonomous Cyber-Physical Systems is posing new challenges for the safety community: standards and practices must be adjusted to account for the system's new capabilities and operations. In this position paper, we advocate for consideration of the CPS architecture in both its functional and non-functional dimensions as a cornerstone for safety assessment. We discuss challenges to support our claim. The IJCAI-ECAI-22 Workshop on Artificial Intelligence Safety (AISafety Current safety standards (such as MIL-STD882 for mili*20C2o2r)r,eJsuployn2d4i-n2g5,a2u0t2h2o, rV.ienna, Austria tary systems, ARP4761 for avionics, or ISO26262 for auto† These authors contributed equally. motive) and more generally the existing body of practice $ jhugues@andrew.cmu.edu (J. Hugues); daniela.cancila@cea.fr usually consider faults as a conjunction of basic events, (D. Cancila) attached to their probability of occurrence. This led to 0000-0003-0148-7175 (J. Hugues); 0000-0002-3483-7947 successful applications in the safety-critical industry. Yet, (D. Cancila) © 2022 Copyright 2022 Carnegie Mellon University and Daniela Cancila. This material is based these standards do not apply to IA-CPS, as the following 1u5p-oDn-0w0o0r2kwfuitnhdCedarannedgiseupMpeolrlotendUinnipvaerrtsibtyytfhoer tDheepoaprtemraetniotnofoDftehfeenSsoeftuwnadreerECnognitnreaecrtiNngo.InFAst8it7u0t2e-, premises are invalid or insuficient for complex AI-based aUNfeIdVeEraRllSyITfuYnAdeNdDreSsOeaFrTcWhaAnRdEdEevNeGloIpNmEeEnRtINceGntIeNr.SNTIOTWUTAERRMAANTTEYR.IATHLIISSCFAURRNNEISGHIEEDMOELNLAONN systems: "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, WEIATRHREARNETXYPROEFSFSIETDNEOSRSIFMOPRLIPEUDR,PAOSSTEOOARNMYEMRCAHTATNERTAINBCILLIUTYD,IENXGC, LBUUSTIVNIOTYT,LOIRMRITEESDULTTOS, • A Human operator can act as the final judge to AONBTYAWINAERDRAFRNOTMY UOSFEAONFYTKHIENMDAWTIETRHIARLE.SCPAERCNTETGOIEFMREEELDLOONMUFNRIOVMERPSAITTEYNDTO,ETSRNAODTEMMAARKKE, control the system: the system can reach a safe CPWrEooUrckReshdoinpgs IhStpN:/c1e6u1r3-w-0s.o7r3g 4OC.0REICnUOtePrRnYaRtWIiGonHoaTlr(ICkNCFsRBhIYNo4Gp.0E)M.PErNoT.cUeseepdeirnmigttesd(uCndEerUCrRea-tiWve CSo.momrogn)s License Attribution state (space, nuclear, train) or the operator can</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Increasingly-Autonomous Cyber-Physical Systems</kwd>
        <kwd>Resilience</kwd>
        <kwd>Architecture</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        ate emerging faulty behaviors with hardware, AI-enabled
functionality, human operators, and the system
architecIncreasingly-Autonomous Cyber-Physical Systems (IA- ture itself as fault sources. Recent incidents involving
CPS for short) are emerging as the natural evolution of CPS at large, e.g. autonomous vehicles, are posing new
embedded real-time systems[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The first generations of challenges both from an engineering and a safety
evaluaembedded systems were basic control loops operating tion perspective [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ]. A general concern is that, if the
over a self-repeating cycle. Growth in computational safety of operations does not meet expectations, human
power and sensor capabilities lead to several evolutions, operators will eventually distrust the system.
from deterministic to optimal controllers, and then Arti- In this position paper, we advocate that the safety
ifcial Intelligence (AI) functions built around Markov de- assessment of IA-CPS requires a careful review of the
cision process, machine learning, deep neural networks, coupling between AI functions (e.g. image classification,
etc. Hence, IA-CPS have a complex architecture that decision-making processes) and the architecture of the
weaves hardware, AI-enabled or decision-making pro- CPS that hosts it. In section 2 we introduce the general
cesses, human operators, and safety-critical software. context of safety for IA-CPS. In section 3 we introduce
They are time-sensitive and substitute human actions the general issues. In section 4 we illustrate how
emerwith high-frequency real-time algorithms. Their archi- gent behaviors arise at the AI/CPS boundary. In section 5
tecture involves more coupling between multiple data we discuss resilience assurance and we provide some
lfows, and is more prone to timing or data corruption/bias research direction we are doing in our respective
institucascading errors. tions. Finally, in section 6 we provide the conclusion.
      </p>
      <p>Generally speaking, IA-CPS depend on fault
mitigation mechanisms correctly integrated into a functional
architecture to fulfill their mission. If not so integrated,
safety mechanisms can play an adversarial role and
cre</p>
    </sec>
    <sec id="sec-2">
      <title>2. On Safety Assessment and</title>
    </sec>
    <sec id="sec-3">
      <title>Faults in IA-CPS</title>
      <p>
        take over close control of the system (aircraft, car). The Three Mile Island accident, known as TMI-2,
ocThis assumption is no longer true for IA-CPS: the curred in a nuclear reactor in 1979 [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. TMI-2 is one
pace of action or the size of the system state space of the most studied accidents for its lessons learned.
Aloutweighs human capacity. though the TMI-2 accident did not cause deaths or
con• Confidence in the system safety stems from the tamination cases, it has been a societal shock, with the
application of rigorous safety standards. How- birth of the antinuclear movement, and modified the
ever, current standards do not consider a high standardization process of nuclear safety standards [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
level of autonomy, having embedded artificial in- TMI-2 happened because an accident in the secondary
telligence, and consider only functions defined circuit of the nuclear power plant has had consequences
through requirements engineering. Yet, most IA on the primary circuit.
functions are not defined by explicit requirements
but rather from training data sets [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. TMI-2 Scenario The chain of the main events can be
• Each function is fully characterized by a finite summarized as follows1. A simple accident in the
secset of requirements, and the system is validated ondary circuit automatically involved a safety command.
against them. Instead, autonomous artificial
intelligence based functions are grey boxes [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. One
can demonstrate general properties of the system,
but validation relies on incomplete simulation or
tests [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>• First failure: one safety valve was expected to be
opened, it was closed after a maintenance
procedure. This error indirectly contributed to a reactor
overheating.
• Second failure: another safety valve (PORV
pilot-operated relief valve) received the “close
command” however it remained in the open
position.
• Software design error: data reported on the
operational control monitor were referred to send
command status “close the valve” and not
on its execution on the system (i.e. actual state of
the valve, still opened).</p>
      <p>
        One path to improve the state of practice is to increase
trust in AI functions [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], in other words to improve
conifdence that an AI function is either correct or at least
resilient to some faults. In [
        <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
        ], the authors propose a
fault taxonomy that discusses the class of faults and when
they are most likely to appear in the system lifecycle, yet
they focus mostly on the engineering of AI functions
and associated activities. They do not contemplate the
system as a whole.
      </p>
      <p>This approach is incomplete. First, the functions of
an IA-CPS cannot be fully characterized; second, they
operate in an environment that is sampled by a network
of sensors, processors, and software functions. Thus, we
advocate for an alternative approach: we consider faults
in IA-CPS as emergent behavior that a system must resist
or eventually control.</p>
      <p>In this situation, the emergent behavior arose from a
set of events, never even imagined, which have resulted
in inconsistent data that have been presented to the
operator. And on this information, the operators made
choices, which turned out to be incorrect. The design of
the TMI-2 Nuclear Power Plant was robust enough and
resilient to mitigate the consequences of this unexpected
emergent behavior.</p>
      <p>
        Although TMI-2 demonstrates far less autonomy that
3. Emergent Behaviors and modern AI-based systems, it allows us to propose a
charSystem’s Architecture acterisation for the root cause of some emergent
behaviors. Indeed, TMI-2 illustrates that emergent behaviors
Sifakis and al. define the emergent properties of a system arise from the conjunctions of multiple minor events
such as those properties that were not in the original whose confluence creates a major safety hazard.
test specifications [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Moreover, the authors classify an To better understand these conjunctions, one must
emergent behavior of the system under study as desired, understand the organizational structure of a system: its
undesired, and not yet specified. architecture. In [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], the author provides a first
character
      </p>
      <p>Emergent properties and emergent behavior are well- ization of an autonomous system from an architectural
known phenomena in systems engineering. Designers perspective. An autonomous system is organized around
must pay careful attention to emergent behavior to en- five blocks: Perception, Refection, Goal management,
sure the correctness of a system, especially in the critical Planning and Self-adaptation. These blocks are
orgasystems domain. A capital example of an emergent unde- nized to fulfill a particular mission and may be subject to
sired and not specified behavior happened in a Nuclear emergent behaviors.</p>
      <p>
        Power Plant. Reviewing this example is indicative of the
impact of a system architecture to mitigate these emer- 1See Chapter 9 of [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] for a complete description and analysis of this
gent behaviors. incident.
      </p>
      <p>
        The attention to emergent behaviors requires an even
more exacerbated analysis when we expand the study
from traditional cyber-physical systems, such as a
Nuclear Power Plant [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], to autonomous and mobile
AIdriven cyber-physical systems. In those later systems,
complexity is given by two more components: the
supporting runtime architecture made of sensors, processors,
and actuators to support the system functions as a
decentralized distributed system; and the system’s ability to
automatically adapt itself to the environment and signals.
      </p>
      <p>Let us focus on the origin of emergent behaviors in
IACPS. We mentioned we focus on the confluence of minor
events that may have a significant safety impact. An
IACPS covers multiple domains: control, energy, real-time,
vision. First, we segregate them by the two high-level
ones: CPS and AI. This leads to three potential sources
of emergent behaviors, two of which are well-studied:
• emergence in CPS: elements of a CPS
architecture may present emergent behavior due to the
inherent nature of the interactions between
computational (cyber) and physical part, which is
surveyed in [15].
• emergence in AI: Similarly, emergence in AI
systems is a large topic, under heavy research
investigation, e.g. in [16].
• emergence at the AI/CPS boundary: to the best
of the authors’ knowledge, this situation is less
investigated. However, it is also the source of
many emergent behaviors. In particular, typical
CPS components may present a threat to AI ones,
and vice versa. We review such scenarios in the
next section.</p>
      <p>We note that each domain developed specific
engineering methodologies and tailored safety assessment
processes. Several groups analyze emergent behaviors
within CPS or AI systems. We claim this line of research
must be complemented by research work on the AI/CPS
boundary.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Emergent behaviors at the</title>
    </sec>
    <sec id="sec-5">
      <title>AI/CPS boundary</title>
      <sec id="sec-5-1">
        <title>Artificial Intelligence and CPS are two disjoint research</title>
        <p>and engineering communities, yet their collaboration.
We mentioned in the previous section that the coupling
between AI and CPS topics be the source of emergent
behaviors. We motivate the existence of these emergent
behaviors by introducing one support case study (in
figure 1) and multiple scenarios.</p>
        <p>The robot in figure 1 has a LEN (Lifelong Exploratory
Navigation) architecture [17]. LEN is based on a
crosslayer architecture from the robot’s sensors to the
occupation grid map, to the generalized Voronoi graph (GVG)
until to the navigation and exploration algorithms and
rising up to the high-level AI, and from here down across
the architecture until the actuators. LEN allows robot
navigation and space exploration in dynamic and
unknown environments.</p>
        <p>LEN is developed by CEA. We chose this example,
because for some years now, we have seen an industrial
trend to the development of mobile robots, with diferent
levels of autonomy with/without AI, in diferent civil
applications, such as household robots or toys. Compared
to the past, where robots were mainly used in industry
with little direct contact with the operator, the current
type of applications target the masses and have a closer
interaction to humans. This trend is expected to grow
over the next decades.</p>
        <p>To increase the presence of robots near humans, a few
guarantees should be met. First, robots have to operate
safely and not hurt users. Second, the user should not be
required to program, reset or maintain the robot. Third,
unlike a factory, the environments in which the robot
operates are not controlled in any way by the constructor
or the developer. Thus, the robot must adapt itself to
its environment, manage its own resources (memory,
computing power and battery), and perform its missions.</p>
        <sec id="sec-5-1-1">
          <title>4.1. Resource Management</title>
        </sec>
      </sec>
      <sec id="sec-5-2">
        <title>Embedded or Edge AI is resource-demanding [18]. In</title>
        <p>the context of robotic IA-CPS, these resources are (but
not limited to): (1) the use of energy (battery), (2) the
extensive use of the processor, and (3) the use of the
network to exchange messages with other systems.</p>
        <p>Let us be consider the following mission for the LEN
robot: to bring an object from location A to location B,
without having a predefined cartography of the
environment in memory. Moreover, the robot has to recognize a
given person to whom to deliver the transported object.</p>
        <p>To move from A to B, the robot requires a navigation A system that has been compromised exhibit an
inconand exploration system. Such a subsystem may require sistent behavior, akin to an emergent behavior.
an excessive use of the processor and then an important In [22], we showed that from a system perspective,
amount of energy for its execution. a faulty sensor and an attacked sensor have a similar</p>
        <p>Two emergent behaviors may arise from a bad cou- behavior. We propose a review of attacks and faults and
pling between AI functions and the supporting CPS plat- how to detect them. In particular, we show that the
form. In this case, we show that the CPS architecture architecture of an IA-CPS can be extended with specific
may have an adversarial efect on the AI functions. fault or attack detectors to improve the system resilience.</p>
        <p>First, the aforementioned subsystem may use so many Furthermore, adding a fault or attack detector may in
resources that it interferes with the nominal mission of turn generate new emergent behaviors in the case of false
the robot. For example, the subsystem requires and con- positive: the system may overreact to non-existent
atsumes the entire battery, making impossible to fulfill tacks. This is a well-known paradox due to fault detectors
the mission. This potential conflict situation increases that are not absolute, but rely on some state evaluation.
with the deployment of autonomous subsystems in the
robot (e.g., the perception of the environment, the recog- 4.3. Conclusive Remarks
nition of the person, ensuring the security level of the
document). An on-line optimization (i.e., after the de- In this section, we listed some scenarios for emergent
velopment of subsystems from diferent teams and their behaviors at the boundary of AI and CPS. We focused
deployment in the robot) could involve emergent behav- on non-functional properties and discussed security and
iors. Second, the AI or robotics function may induce performance (energy and CPU). This could be extended
a significant computation overload. It is well-known to all timing aspects (latency, jitter, scheduling, . . . ), but
that the performance evaluation of robotics platform is also safety.
a challenge, e.g. [19]. Uncontrolled CPU workload may We note that the increased complexity of those systems
trigger timing violations, leading ultimately to errors in calls for an impossible holistic engineering approach: one
computations that could impact multiple subsystems. needs to “tame" emergent behaviors that stem from AI,</p>
        <p>An approach to overcome the emergent behaviour by and CPS subdomains, but also evaluate the cross-domain
guarantying performance of IA-CPS could be twofold. impact of CPS non-functional properties to AI and
viceFrom one hand, the design and development of versa.
lightweight solutions for autonomous subsystems. For ex- We deem this approach as impossible not from a
sciample, LEN uses resources eficiently [ 20]. From the other entific perspective, but from an economic one: we used
hand, to understand which solutions can be developed to TMI-2 as an example of a system that mitigated a
signifidetect, control and mitigate emergent behaviors, by guar- cant emergent behavior. However, the nuclear industry
anteeing the performance of the AI embedded in the sys- can spend more time and efort to improve its design.
tem. LEN is built on a cross-layer architecture. This latter This is not possible for general CPS: the time to deliver a
includes two macro blocks. Each block has more layers. new product should be reduced.</p>
        <p>The low-level macro-block (the one from the sensors to In this context, we consider one should instead focus
GVG) implements the safety-related control-command on assuring the system is suficiently resilient rather than
and is devoid of AI functionality. The high-level macro safe.
block contains Machine Learning-based making-decision
and interfaces with other AI-driven functionality of the 5. From Safety assessment to
robot. The management of errors and emergent
behaviors between layers uses a contract-based approach [17] Resilience assurance
(See section 5.2).</p>
      </sec>
      <sec id="sec-5-3">
        <title>Of the extensive literature on methodology and analy</title>
        <p>4.2. Cybersecurity and Cyber-Physical ses for safety-related properties, we here discuss
existing work that is closer to our approach. This literature</p>
        <p>Security ranges from traditional analysis techniques, such as FTA
We mentioned that IA-CPS are ultimately networked and FMEA, to pattern-based, contract-based, GSN (Goal
software-intensive systems. As such, they can be subject Structuring Notation).
to cyber-security attacks, i.e. the malicious tampering of An interesting and mature approach is the one based
some CPU or software functions. In addition, sensors and on the use of design patters for achieving security or
actuators can be subject to additional attacks, leading to safety objectives [23] and for which today we have
encyber-physical attacks [21]. In these situations, the sys- couraging and positive feedback. In this context, design
tem may no longer fulfill this mission: data are corrupted, patterns provide an architectural description that
imthe system reprogrammed, or resource mismanaged, etc. prove the resilience of the system to specific scenarios,
combined with fragments of an assurance case. As an an autonomous mobile robot should be resilient to
extension, the authors in [24] promote a methodology internal software errors, manage battery properly,
that combines patterns with contract-based and GSN - execute a command, detect physical damage of
thus obtaining a modular and structural result for safety sensors and control it, etc.
argument.</p>
        <p>The main benefit of patterns and, more generally, of Exogenous Resilience deals with the system’s
extertechniques such as GSN and contracts, is the ability to nal environment in which it is operated., e.g.,
ensure both safety- and cybersecurity-related proper- avoiding an obstacle or malicious attacks
ties [25, 26]. In [27], the authors propose a safety and To ensure Safety-I, traditional techniques (such as
redunsecurity co-engineering framework, based on patters of dancy) are dificult to deploy on IA-CPS systems where
process and argumentation. the physical space of the product and its final cost are</p>
        <p>However, despite the essential help of the above ap- much more limited than traditional systems. Techniques
proaches, safety assurance and safety analysis remain on resilience appear more appropriated for this new
genvery expensive. They require redundancy, diversity and eration of systems and could be based on the design and
independence at software, architectural and physical lev- the control of a modular architecture, having diferent
els. Such an option is not always possible in IA-CPS , levels of trust.
where the limitations of the physical space and cost
constitute stronger constraints for IA-CPS applications than
traditional ones. In many cases, heterogeneous architec- 5.1. Conclusive Remarks
tures cannot be applied.</p>
        <p>
          To overcome these dificulties, an interesting approach,
albeit not without live debates in the community (see
e.g. [28]), is to widen the safety definition to Safety I and
Safety II [29]. In [30], the author states that “a system
cannot be resilient, but a system can have a potential for
resilient performance". Hollnagel proposes to change the
classical safety analysis process that focuses mainly on
reducing the number of adverse outcomes by taking into
account the success stories that tend to become invisible
and insignificant, because they are considered as
normal, i.e. as planned. Hollnagel introduces the following
definitions [29]:
Unlike traditional critical systems, in IA-CPS systems,
the emergent behavior is expected to increase. It could
arise from how IA-CPS are used and from the
interaction of IA-CPS with its environment. In [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], for example,
the authors discuss how “the assurance is insuficient to
address the emergent properties derived from the
network weights” with respect to the avionics safety norms
DO-178C and DO-254. Therefore, preventing accidents
in IA-CPS requires using models that include the entire
socio-technical aspects and treat safety as a dynamic
control problem. Future intelligent autonomous systems
need to be able to appraise safety issues in their
environment, self-learn from experience and interactions with
humans, and adapt and regulate their behavior.
        </p>
      </sec>
      <sec id="sec-5-4">
        <title>Safety-I aim is to be sure that the number of unwanted outputs will be as low as possible.</title>
        <sec id="sec-5-4-1">
          <title>5.2. Way Forward</title>
        </sec>
      </sec>
      <sec id="sec-5-5">
        <title>Safety-II concerns the condition of being certain that</title>
        <p>the success of outputs will be as high as possible.</p>
      </sec>
      <sec id="sec-5-6">
        <title>Within the IC and Digital System Division, at CEA LIST,</title>
        <p>In [28], the author introduces the notion of Safety III we are interested in Trustworthy Artificially Intelligent
as follows Adaptive Autonomous CPS. As discussed in the
previous sections, these systems can be afected by emergent
Safety-III freedom from unacceptable losses as identi- behaviors, particularly if we consider them in dynamic
ifed by the system stakeholders. The goal is to and unpredictable environments. In this research
coneliminate, mitigate, or control hazards, which are text, we focus on the navigation and exploration system
the states that can lead to these losses. and we use LEN [17] as an excellent case study to
experiment the achieved scientific results. More precisely, we</p>
        <p>Moreover, Lavenson argues the importance of improv- would like firstly to understand what methods and
teching and extending Safety-III. We introduce resilience as niques are needed to guarantee and ensure a sustainable
a subclass of Safety III. Resilience could allow us to re- and trustable low-level architecture, i.e from sensors to
lease some hard constraints related to safety (e.g. redun- the occupancy grid and the Generalized Voronoi Graph
dancy, sensor quality) and provide a given level of no (GVG) and then back down to the actuators. In this first
longer safety but system resilience. In this regard, we architectural block, the main safety control-commands
should distinguish between Exogenous and Endogenous are implemented (including the control of the
admissiresilience. ble incertitude). As argued in section 4.1, the design of
Endogenous Resilience is the ability of the system to lightweight solutions has a paramount importance to
redetect and manage internal faults. For example, duce the risk of uncontrolled emergent behaviours. In</p>
      </sec>
      <sec id="sec-5-7">
        <title>LEN, we wish to (1) individualize and categorize the other factors that could lead to emergent behaviors; (2) qualitatively and quantitatively assess resilience for LEN, by adapting approaches such as [31].</title>
        <p>At the SEI, the MBE team is working on the definition
of languages and tool-supported processes to engineer
safety-critical systems. This encompasses model-based
techniques such as the AADL architecture description
language along with code generation techniques, safety
analysis capabilities. We have developed a collection of
techniques to ensure the correctness of code generated
from models, along with model checking or Digital Twins
capabilities [32]. These provide the foundations to fully
analyze a system either analytically or through
simulations, with a close link to the engineering models. The
SEI is currently engaged in a project to further strengthen
the link between MBSE, resilience in the context of
IACPS. Most notable, we plan to address solutions to all
challenges highlighted in the previous section.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <sec id="sec-6-1">
        <title>In this paper, we have discussed emergent properties. We</title>
        <p>have shown through the TMI-2 nuclear accident, how
undesirable emergent behavior can occur in traditional
systems. In Increasingly-Autonomous Cyber-Physical
Systems, emergent properties are becoming more critical.
Unlike traditional application domains, the potential
consequences of undesired emergent behavior may be more
dificult to mitigate, given the limitation of the physical
space and cost. We discussed the emergent properties
from three perspective, performance of AI, cyber-security
and resilience, and we have briefly illustrated some of the
solutions available in the literature. From our analysis
of the state of the art and practice, we advocate that the
resilience assurance of Increasingly-Autonomous
CyberPhysical Systems requires a careful review of the coupling
between AI functions and the architecture of the CPS that
hosts it.</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <sec id="sec-7-1">
        <title>We thank Laurent Soulier (CEA) for the discussions on LEN.</title>
        <p>[15] S. Tyszberowicz, D. Faitelson, Emergence in cyber- [27] H. Martin, R. Bramberger, C. Schmittner, Z. Ma,
physical systems: potential and risk, Frontiers of In- T. Gruber, A. Ruiz, G. Macher, Safety and Security
formation Technology &amp; Electronic Engineering 21 Co-engineering and Argumentation Framework, in:
(2020) 1554–1566. doi:10.1631/FITEE.2000279. Computer Safety, Reliability, and Security, Springer
[16] Z. Li, C. Sim, M. Hean Low, A Survey of Emergent International Publishing, 2017, pp. 286–297.</p>
        <p>Behavior and Its Impacts in Agent-based Systems, [28] N. Leveson, Safety III: A Systems Approach to
in: 2006 IEEE International Conference on Indus- Safety and Resilience, http://sunnyday.mit.edu/
trial Informatics, IEEE, Singapore, 2006, pp. 1295– safety-3.pdf, 2020.
1300. URL: http://ieeexplore.ieee.org/document/ [29] E. Hollnagel, R. Wears, J. Braithwaite, From Safety-I
4053581/. doi:10.1109/INDIN.2006.275846. to Safety-II: A White Paper, 2015.
[17] F. Mayran de Chamisso, D. Cancila, L. Soulier, [30] E. Hollnagel, Rag - the resilience analysis grid,
R. Passerone, M. Aupetit, Lifelong Exploratory Nav- Resilience engineering in practice: a guidebook.
igation: an Architecture for Safer Mobile Robots, Ashgate Publishing Limited, Farnham, Surrey (2011)
IEEE Design and Test (2019). 275–296.
[18] Z. Zhou, X. Chen, E. Li, L. Zeng, K. Luo, J. Zhang, [31] R. Bloomfield, G. Fletcher, H. Khlaaf, L. Hinde,
Edge intelligence: Paving the last mile of artificial P. Ryan, Safety Case Templates for Autonomous
intelligence with edge computing, Proceedings of Systems, CoRR (2021).
the IEEE 107 (2019). doi:10.1109/JPROC.2019. [32] J. Hugues, A. Hristosov, J. J. Hudak, J. Yankel,
2918951. Twinops - devops meets model-based
engineer[19] T. Kronauer, J. Pohlmann, M. Matthé, T. Sme- ing and digital twins for the engineering of cps,
jkal, G. P. Fettweis, Latency overhead of in: Proceedings of the 23rd ACM/IEEE
InternaROS2 for modular time-critical systems, CoRR tional Conference on Model Driven Engineering
abs/2101.02074 (2021). URL: https://arxiv.org/abs/ Languages and Systems: Companion Proceedings,
2101.02074. arXiv:2101.02074. MODELS ’20, Association for Computing
Machin[20] F. Mayran de Chamisso, L. Soulier, M. Aupetit, ery, New York, NY, USA, 2020. doi:10.1145/
Robust topological skeleton extraction from oc- 3417990.3421446.
cupancy grids for mobile robot navigation, in:
Proceedings of the twentieth national congress
on Shape Recognition and Artificial Intelligence
(RFIA’16), 2016.
[21] A. Humayed, J. Lin, F. Li, B. Luo, Cyber-physical
systems security—a survey, IEEE Internet of Things
Journal 4 (2017) 1802–1831. doi:10.1109/JIOT.</p>
        <p>2017.2703172.
[22] L. Zhai, A. Kanellopoulos, F. Fotiadis, K. G.</p>
        <p>Vamvoudakis, J. Hugues, Towards intelligent
security for unmanned aerial vehicles: A taxonomy
of attacks, faults, and detection mechanisms, in:
AIAA SCITECH 2022 Forum, 2022. doi:10.2514/
6.2022-0969.
[23] C. Preschern, N. Kajtazovic, A. Höller, C. Kreiner,</p>
        <p>Pattern-based safety development methods:
overview and comparison, in: EuroPLoP ’14, 2014.
[24] I. Sljivo, G. J. Uriagereka, S. Puri, B. Gallina, Guiding
assurance of architectural design patterns for
critical applications, J. Syst. Archit. 110 (2020) 101765.
[25] J. Dobaj, D. Ekert, J. Stolfa, S. Stolfa, G. Macher,</p>
        <p>R. Messnarz, Cybersecurity threat analysis, risk
assessment and design patterns for automotive
networked embedded systems: A case study, JUCS
Journal of Universal Computer Science 27 (2021)
830–849.
[26] S. Mouelhi, E. Laarouchi, D. Cancila, H. Chaouchi,</p>
        <p>Predictive Formal Analysis of Resilience in
CyberPhysical Systems, IEEE Access 7 (2019).</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>E. E.</given-names>
            <surname>Alves</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Devesh</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Hall</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Driscoll</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Murugesan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Rushby</surname>
          </string-name>
          , Considerations in Assuring Safety of Increasingly Autonomous Systems,
          <source>Technical Report NASA/CR-2018-220080</source>
          ,
          <issue>NF1676L30426</issue>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>National</given-names>
            <surname>Transport Safety Board</surname>
          </string-name>
          ,
          <source>Collision Between Vehicle Controlled by Developmental Automated Driving System and Pedestrian Tempe, Arizona March 18</source>
          ,
          <year>2018</year>
          ,
          <string-name>
            <given-names>Accident</given-names>
            <surname>Report</surname>
          </string-name>
          <string-name>
            <surname>NTSB</surname>
          </string-name>
          /HAR-19/03 PB2019-
          <fpage>101402</fpage>
          , National Transport Safety Board,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>P.</given-names>
            <surname>Koopman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Kuipers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W. H.</given-names>
            <surname>Widen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Wolf</surname>
          </string-name>
          , Ethics, safety, and autonomous vehicles,
          <source>Computer</source>
          <volume>54</volume>
          (
          <year>2021</year>
          )
          <fpage>28</fpage>
          -
          <lpage>37</lpage>
          . doi:
          <volume>10</volume>
          .1109/
          <string-name>
            <surname>MC</surname>
          </string-name>
          .
          <year>2021</year>
          .
          <volume>3108035</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A.</given-names>
            <surname>Vogelsang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Borg</surname>
          </string-name>
          ,
          <article-title>Requirements engineering for machine learning: Perspectives from data scientists</article-title>
          , CoRR abs/
          <year>1908</year>
          .04674 (
          <year>2019</year>
          ). arXiv:
          <year>1908</year>
          .04674.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>A.</given-names>
            <surname>Kane</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Chowdhury</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Datta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Koopman</surname>
          </string-name>
          ,
          <article-title>A case study on runtime monitoring of an autonomous research vehicle (ARV) system</article-title>
          , in: Runtime Verification International Conference, volume
          <volume>9333</volume>
          of Lecture Notes in Computer Science, Springer,
          <year>2015</year>
          , pp.
          <fpage>102</fpage>
          -
          <lpage>117</lpage>
          . doi:
          <volume>10</volume>
          .1007/ 978-3-
          <fpage>319</fpage>
          -23820-3\_7.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>L.</given-names>
            <surname>Myllyaho</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Raatikainen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Männistö</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Mikkonen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. K.</given-names>
            <surname>Nurminen</surname>
          </string-name>
          ,
          <article-title>Systematic literature review of validation methods for ai systems</article-title>
          ,
          <source>Journal of Systems and Software</source>
          <volume>181</volume>
          (
          <year>2021</year>
          )
          <article-title>111050</article-title>
          . doi:https: //doi.org/10.1016/j.jss.
          <year>2021</year>
          .
          <volume>111050</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>B.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Qi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Di</surname>
          </string-name>
          , J. Liu,
          <string-name>
            <given-names>J.</given-names>
            <surname>Pei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Yi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Zhou</surname>
          </string-name>
          ,
          <string-name>
            <surname>Trustworthy</surname>
            <given-names>AI</given-names>
          </string-name>
          :
          <article-title>from principles to practices</article-title>
          ,
          <source>CoRR abs/2110</source>
          .01167 (
          <year>2021</year>
          ). arXiv:
          <volume>2110</volume>
          .
          <fpage>01167</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>N.</given-names>
            <surname>Humbatova</surname>
          </string-name>
          , G. Jahangirova,
          <string-name>
            <given-names>G.</given-names>
            <surname>Bavota</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Riccio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Stocco</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Tonella</surname>
          </string-name>
          ,
          <article-title>Taxonomy of Real Faults in Deep Learning Systems</article-title>
          , arXiv:
          <year>1910</year>
          .11015 [cs] (
          <year>2019</year>
          ). ArXiv:
          <year>1910</year>
          .11015.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Nikanjam</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. M. Morovati</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Khomh</surname>
            ,
            <given-names>H. B.</given-names>
          </string-name>
          <string-name>
            <surname>Braiek</surname>
          </string-name>
          ,
          <article-title>Faults in Deep Reinforcement Learning Programs: A Taxonomy and A Detection Approach</article-title>
          , arXiv:
          <fpage>2101</fpage>
          .00135 [cs] (
          <year>2021</year>
          ). ArXiv:
          <volume>2101</volume>
          .
          <fpage>00135</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>J.</given-names>
            <surname>Sifakis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Harel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Marron</surname>
          </string-name>
          ,
          <article-title>Autonomics: In search of a foundation for next-generation autonomous systems</article-title>
          ,
          <source>Proceedings of the National Academy of Sciences of the United States of America</source>
          <volume>117</volume>
          (
          <year>2020</year>
          )
          <fpage>17491</fpage>
          -
          <lpage>17498</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>J.</given-names>
            <surname>Couturier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Schwarz</surname>
          </string-name>
          ,
          <source>Current State of Research on Pressurized Water Reactor Safety, Science and Technology Series, EDP Sciences</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>J.</given-names>
            <surname>Samuel</surname>
          </string-name>
          <string-name>
            <surname>Walker</surname>
          </string-name>
          ,
          <source>Three Mile Island: A Nuclear Crisis in Historical Prospective</source>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>J.</given-names>
            <surname>Sifakis</surname>
          </string-name>
          ,
          <source>Autonomous Systems - An Architectural Characterization</source>
          , Springer International Publishing, Cham,
          <year>2019</year>
          , pp.
          <fpage>388</fpage>
          -
          <lpage>410</lpage>
          . doi:
          <volume>10</volume>
          .1007/ 978-3-
          <fpage>030</fpage>
          -21485-2_
          <fpage>21</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>M. D. Franusich</surname>
          </string-name>
          ,
          <article-title>Security Hardened Cyber Components for Nuclear Power Plants</article-title>
          ,
          <source>Technical Report</source>
          Grant No.
          <string-name>
            <surname>DE-SC0013808</surname>
          </string-name>
          , US Department of Energy, Ofice of Science, Chicago Ofice,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>