the report history, or generate a new on through calls on the other Management
FCs.
The State FC monitors and predicts state of the IoT system. For a ready
diagnostic of the system, as required by Fault FC, the past, current and
predicted (future) state of the system are provided. This functionality can also
support billing. The rationale is that Functions/Services such as Reporting need
to know the current and future state of the system. For a ready diagnostic of the
system one also needs to know its current performance.
This FC also encompasses a behaviour functionality, which forces the system
into a particular state or series of states. An example for an action for which
such functionality is needed is an emergency override and the related kill of run-
time processes throughout the system. Since such functionality easily can
disrupt the system in an unforeseen manner this FC also offers a consistency
checks of the commands issued by the changeState functionality in the State
FC.
The functions of the State FC are to change or enforce a particular state on the
system. This function generates sequence of commands to be sent to other
FCs. This function also offers the opportunity to check the consistency of the
commands provided to this function, as well as to check predictable outcomes
(through the predictState function).
A second function is to monitor the state. This function is mainly used in
subscription mode, where it monitors the state of the system and notifies
subscribers of relevant changes in state.
Other functions of the FC are to predict the state for a given time, to retrieve the
state of the system through access to the state history and to update the state
by changing or creating a state entry.
4.2.2.9 Mapping of Functional View to the Red Thread example
In this section, the ―Red Thread‖ example will be mapped on the Functional
View and the main Functional Components used for the example are
highlighted as can be seen in Figure 40 :