Internet of Everything (IoE) Taxonomies: History
Please note this is an old version of this entry, which may differ significantly from the current revision.

The paradigm of the Internet of everything (IoE) is advancing toward enriching people’s lives by adding value to the Internet of things (IoT), with connections among people, processes, data, and things. This paper provides a survey of the literature on IoE research, highlighting concerns in terms of intelligence services and knowledge creation. The significant contributions of this study are as follows: (1) a systematic literature review of IoE taxonomies (including IoT); (2) development of a taxonomy to guide the identification of critical knowledge in IoE applications, an in-depth classification of IoE enablers (sensors and actuators); (3) validation of the defined taxonomy with 50 IoE applications; and (4) identification of issues and challenges in existing IoE applications (using the defined taxonomy) with regard to insights about knowledge processes.

  • Internet of everything
  • Internet of things
  • IoE
  • IoT
  • taxonomy
  • sensors
  • big-data
  • knowledge

1. Introduction

The Internet of everything (IoE) is a term that was first defined by CISCO in 2012 [1] as a network of networks that reunites people, processes, data, and things in network connections more significant and valuable than ever [2,3,4]. While the Internet of things (IoT) is a dynamic global network infrastructure [5] concerned about things (i.e., physical devices, accessed through the Internet), IoE lays an upper foundation over IoT and is concerned with intelligent network connections and technologies [6,7,8,9].

IoE supports creating new capacities, better-off competencies, and outstanding economic opportunities for businesses and society [1]. For Fiaidhi and Mohammed [10], IoE expands on the IoT concept by connecting devices and people in one network. Beyond the concept of IoT, the IoE paradigm covers a wide range of Internet-based concepts; for example, the Internet of people (IoP), which considers social networks and connections among people; and the industrial Internet (II), which is focused on data of interest to industry [7]. The concept of IoE incorporates nanosensors in diverse objects using nano-networks. It provides access to data that had previously been impossible to sense. This technology transition involving IoE is a concept called the Internet of Nano things [11].

With more relevant connections than machine-to-machine communications, IoE has enabled the global democratization of skills, including person-to-machine and person-to-person connections [12,13].

Accordingly, Auger et al. [4] argue that IoE extends the concept of IoT by exceeding the connections of things and integrating common impacts, risks, and economic benefits for the novel interconnected society. Thus, “intelligent services”, together with the “things”, represent the “everything” in IoE [14].

For Raj and Prakash [13], IoE is a superset of IoT and requires advanced capabilities within the area of information sharing. The IoE paradigm can extract and analyze real-time data collected from diverse and heterogeneous IoE environments, from simple sensors and actuators to complex robotic devices, and from autonomous service agents to human actors [3]. Thus, IoE applications require appropriate measures to be taken in the initial phases of their design and implementation [13]. Artificial intelligence (AI) integrated into smart devices provides the increasing deployment of innovative and useful IoE-based applications, where people and things interact appropriately within a social context and multi-user environment [11].

Processes are the core of IoE; they represent network “connections” and real-time data/information flows [15] among IoE nodes [16]. The result is smartness and intelligence [17], and real-time insights working in concert [18], far beyond IoT context disruptions [19], addressing the societal and organizational needs for more data and more actionable intelligence.

Actions and interactions within the IoE environment create and expand knowledge in a transcending process through which entities (people, things, and data) acquire new knowledge and new interactions are created in knowledge-creation cycles [20]. This transformation from data to knowledge in IoE provides essential insights and various possible applications [21,22].

Value-generating activities come through knowledge processes that filter data, information, and knowledge into a decision context, in which it becomes actionable intelligence [23]. A knowledge-based strategy for selecting and managing technologies and decision support artifacts (big data, data, information, knowledge, and intelligence) assists in the management and governance of data and technologies to ensure great benefit from IoE’s capacity to provide enhanced intelligent services.

Figure 1 shows the “four enablers” (people, data, processes, and things) in IoE.

Figure 1. Internet of everything, adapted from [16].

Several taxonomies for IoT [24,25,26,27,28,29,30] and IoE [6,13,15,17,31,32], have been proposed. However, there are challenges concerning the ranking and managing of knowledge processes in IoE applications.

First, there is still a fragmented framework: (1) A lack of consensus and new demands are unique to the IoE context (e.g., empowering people and providing intelligence services and insights through the collaboration of IoE enablers [sensors and actuators]); and (2) A lack of consideration for the integration of IoE connections (machine-to-machine, people-to-people, and people to machine) from perspectives that support the high heterogeneity of existing IoE devices and the expected value creation in IoE applications—the perspective of knowledge that refers to actions, comprehension, and meaning derived from the information inside a context; the perspective of sensors and actuators physical characteristics and usage in IoE context, the perspective of information observation within ever-changing IoE contexts, and the perspective of infrastructure capabilities and resources required.

The successful adoption of a particular technology depends on the comprehension of its use and features [33]. Research on knowledge management has focused on understanding the complex relationships between data, information, and knowledge creation, and how they are impacted and benefited by the sources (or spaces) of data and information and the contexts in which they are analyzed and shared [34]. Therefore, an in-depth classification of IoE enablers (sensors and actuators) identifies issues and challenges in existing IoE applications regarding insights about managing knowledge processes that create value from the IoT context.

2. Proposed IoE Taxonomy

This section presents the proposed IoE taxonomy. For the conception of this taxonomy, we selected a method proposed by Nickerson et al. [88] for taxonomy development that has been adequately addressed for taxonomy development in the information systems (IS) domain. The proposed taxonomy identifies and categorizes sensors, attributes, and characteristics that are essential for developing IoE applications. This study is the first attempt to represent the types of knowledge (from sensors and actuators) in the IoE domain and how knowledge processes lead to intelligent services in IoE applications.

The development of an IoE taxonomy involves determining the characteristics of the sensors in IoE applications that arise from a refinement process at various stages to sufficiently satisfy the following qualitative attributes from Nickerson et al. [88] regarding the taxonomy:

  • Concise: has a limited number of dimensions and characteristics, restricted to what is relevant and understandable;
  • Robust: contains suitable dimensions and characteristics to distinguish the objects of interest;
  • Comprehensive: includes appropriate and enough dimensions to classify all known objects within the domain under regard;
  • Extendable: allows for the insertion of additional dimensions and characteristics within a size to contemplate new incorporated objects;
  • Explanatory: provides useful explanations and valuable descriptions of the nature of the objects under study.

Additionally, developing a useful taxonomy is a search process of design [88]. Kotis et al. [90] presented requirements for a well-defined collaborative and iterative methodology, addressing practical aspects that drive consensus on developments—a “live” method of development in which the artifacts evolve over time. An artifact must preserve its liveness, evolution, and reusability during its life cycle (i.e., it may be in-use in a particular time or instant, be under constant maintenance or update and be used in applications/projects beyond its original purpose).

We followed an iterative method during the development process, as suggested by Nickerson et al. [88], and a conceptual to the empirical approach, based on the surveyed existing taxonomies related to IoT and IoE (Section 3). Furthermore, a collaborative approach that relied on authors´ insight, experience, intuition led to proper identification of the proposed dimensions and characteristics, as resumed in the following stages of the development.

For Nickerson et al. [88], the taxonomy’s purpose (meta-characteristic) drives the taxonomy’s dimensions and characteristics. Each element or classification proposed in the taxonomy should be a logical outcome of the meta-characteristic. Our aim was “to guide the identification of critical knowledge in IoE applications, an in-depth classification of IoE enablers (sensors and actuators) based on the knowledge they provide in intelligent tasks”.

The development process ended when both objective and subjective conditions have been met [88]. During the iterations processes, new characteristics were identified and included, and when any characteristic turned out not to be relevant, they were eliminated after consensus. Further analysis succeeded until reach the ending conditions, engaging authors in close collaboration towards shaping commonly agreed dimensions and characteristics. We used two objectives ending conditions: no new dimensions were added in the last iteration, and every characteristic was unique within its dimension. Subjectively, the process ended when the taxonomy was determined to be concise, robust, comprehensive, extendible, and explanatory [88] and fulfilled the quality requirements of liveness, evolution, and reusability [90] that are suitable to dynamics of the IoE pervasive environment.

Accordingly, ranking knowledge in IoE sensors is a matter of eliciting the main characteristics in IoE applications. In order to understand the IoE domain, we applied specific questions by answering the 4 ws (what, when, who, and where) and 1 h (how) identified using the 4W1H methodology [91,92]. This methodology addresses the challenge imposed due to the high heterogeneity of existing IoE devices. A similar approach was proposed in [68] to measure the quality and value of information when considering the value created by the IoE in applications. These questions guided the definition of the following four complementary categories that drive the purpose of taxonomy dimensions and characteristics:

(a)
Knowledge: regarding knowledge in action; that is, the artifact or information inside a context (what) with comprehension and meaning;
(b)
Type: typifies sensors and actuators—who they are, their physical characteristics, their usage, and their role in IoE context: sensors or actuators in cyber, physical, or cyber-physical presentation;
(c)
Observation: the physical context in time (when) and space (where); that is, the instant and location that the information content was sensed or perceived within ever-changing IoE contexts;
(d)
Capabilities: how the information is flowing, the infrastructure capabilities, and the resources required.

For this stage of development, we used the top-down development process, starting with defining the most general categories (knowledge, type, observation, and capabilities). We then selected dimensions and characteristics previously derived from a theoretical foundation from reviewing the related literature, as presented in Section 3 and grouped them in related knowledge, type, observation, and capabilities categories, revealing the resulting taxonomy. Our IoE taxonomy consists of four categories (see Figure 2) and groups 18 dimensions, each comprising of mutually exclusive and generally collectively exhaustive characteristics. Section 4.1 describes the knowledge category, which analyses the knowledge characteristics and the value created by IoE applications. Section 4.2 details sensor characteristics related to their use in IoE applications (types). Section 4.3 presents the observation category, which classifies how data are sensed and gathered in IoE observations. Finally, in Section 4.4, the sensors’ capabilities are classified into a few dimensions that address the technological aspects for designing IoE applications.

Figure 2. IoE taxonomy.

4.1. Knowledge

The knowledge category contains five dimensions related to knowledge creation and information flow: explicitness, structure, trust, outcome, and action. Each has its own specific sub-dimensions or characteristics, as shown in Figure 3.

Figure 3. IoE Taxonomy: knowledge category with dimensions and characteristics.

4.1.1. Explicitness

IoE environment architectures consist of IoT standard architecture [93], but with the addition of the human element (which acts as a node) and intelligent services to the IoT network [32]. knowledge discovery approaches used in developing IoT solutions [82], which involve sharing information from smart objects, should be optimized by examining how humans process data sources of information to form knowledge [41]. For Perera et al. [36], this requires knowledge from different perspectives, for example, knowledge of sensors, applications, users, and so forth. Moreover, these uncovered knowledge patterns are analyzed and integrated for subsequent use in real time, using multiple knowledge management approaches [76,94,95]. The intelligence of connected things varies from non-existent to absolutely rational [24]. There are different kinds of knowledge, and it demands distinct representations. A taxonomy is a central link between knowledge engineering and knowledge management [96]. Regarding explicitness, this work classifies knowledge provided by sensors in IoE applications into three distinct types:

  • Tacit: This knowledge is rooted in actions, experiences, and involvement in specific contexts. Tacit knowledge consists of people’s knowledge based on intuitive evaluations of sensory inputs and perceptions, which is sometimes hard to express (i.e., feelings, beliefs, insights, values, and ideals) [97]. The increase of human senses through sensor and data fusion and context awareness is the essence that supports smarter wearable devices for relating mutually with human cognitive memories [98].

  • Explicit: This knowledge is codified and articulated knowledge (i.e., the form of knowledge that is easy to codify using formal language, procedures or principles) [97]. Explicit knowledge from hard sensing-based data acquisition results in discovering hidden patterns in the aggregated sensor data [42,66]. The explicitness denotes awareness of a fact or artifact, which means the application of knowledge [98] from efficient scheduling of the resources in IoE applications [82,99]. Sensors continuously generate enormous amounts of data, with the value created being conditioned to its analysis.

  • Implicit: Knowledge is not explicitly represented in the knowledge base but is inferred from it by using several assumptions [100]. Thus, implicit knowledge may be implicit information intertwined in information systems and data sources [97]. Myriad data analytic algorithms can be executed to extract a higher level of information from sensed data [99]. The value created by implicit knowledge emerges from machine learning and AI technologies, mainly in machine intelligence services [101]. It consists of outputs to make predictions oriented toward decision support and automation in diverse IoE application scenarios [102].

4.1.2. Structure

The combination of data streams with background knowledge enables meaningful analysis to derive higher levels of abstraction and deliver quality actionable information to IoE services [71,95,99]. Sensor data are a piece of explicit knowledge with metadata characterizing the body of evidence [68]. The distinctions between data, information, and knowledge are largely irrelevant [97]. Knowledge is created by transforming the multiple data formats collected (structured, semi-structured, and unstructured) [103] into high-level information [36,64,94,104], and useful knowledge patterns [36]. Descriptions of these data formats are given below:

  • Structured: These data have an identified format and a relational structure, frequently accessed using a standard SQL-type language and stored in relational database management systems. Typical examples of structured data are string, numeral, and date. [105].
  • Semi-structured: These data cannot be managed by conventional database management system techniques, but the interpretation and analysis of these data require comprehensive and intelligent rules. Typical examples of semi-structured data are extensible markup language (XML) and JavaScript object notation (JSON) data. [50,101,105].
  • Unstructured: These data do not follow any specific format and are often represented in a rather complex structure that contains hidden relationships. Examples of unstructured data are videos, text, time information, and geographic location [40]. With the amount of data generated by sensors, devices constantly produce large volumes of structured, unstructured, and semi-structured data, which results in ”big data” [73,74].

IoT processing of sensing data streams provides ubiquitous sensing services [42,102,106]. Data aggregation processes are vital for improving the quality of the designed system [107]. Big data technologies assist in data processing [76], the uncovering of new and valuable insights and information from incorporated data sources [28,69], and in improving prediction and decision-making [102].

4.1.3. Trust

In a hybrid human-based and device-based environment, such as IoE, data’s trustworthiness can be estimated mostly by the sensor nodes’ reputation [37]. Trust management is a decisive challenge for data access and data storage on IoE applications [49,108].

Dynamic and heterogeneous network environments and the diversity of devices connected in the IoT generate an extensive array of potential security threats [27,60,61,109]. The network interoperability level should address concerns such as the security of the data to be transmitted [64], and a coherent IoT architecture would provide a layer of data security [110,111] since the IoT has no uniform architecture. Approaches and methods to improve users’ awareness about the effects of potential IoT threats may mitigate the risk of exposure [53,65,68,112].

Knowledge assets vary in veracity levels [97], between the extremes of truth and untruth [52]. In some broad sense, the value of knowledge depends on the quality of the sensors’ information. Security approaches must be made self-sufficient and autonomic, with the minimal manual human intervention [53]. Sensor networks’ applications need support regarding privacy, security accuracy, timeliness, relevance, completeness, and provenance [46,68]. The data source’s reputation represents the source’s truthfulness in providing quality content to handle changing external requirements and contexts [101]. Any direct or indirect connections of user information with connected objects within IoT landscapes categorize trust in communication and security issues [108] [110]. The trust values are considered based on the reliability of devices and the level of security and trust engaged in implementing and operating the connectivity [113,114]. Knowledge of sensors and sensor data in IoE applications is either trustful or untrustful:

  • Trustful: Based on protecting both user and service provider privacy precedents [40]. Constituting meaningful identity, using trusted communication paths, and preserving contextual information is essential to guarantee the protection of users’ privacy in the IoE environment [115]. The work in [55] addressed the security of IoT objects and privacy issues by merging identification, authentication, and authorization into one argument: access control. The security dimension encompasses five concepts: access control, confidentiality, integrity, availability, and non-repudiation. Different studies have covered concerns such as anonymity, liability, and moral, ethical, legal, cultural, and regional parameters, among other things [39,45,47,116].

  • Untrustful: False or misleading data culminates in wrong decisions and critical consequences and lead to uncertainty at all knowledge transformation levels. Incompleteness in data occurs at the lower layer of the sensor readings or raw data collected. Vagueness frequently appears at a higher level of contextual information [37,69]. Possible security risks associated with IoT data are the heterogeneity of the smart devices and the nature of sensed data or authentication among different trust domains [56], which further complicates access control decisions.

4.1.4. Outcome

The IoE paradigm impacts human interaction with everyday objects. Considering the type of information exchanged between humans and the system [84], the expected outcomes from IoE applications provide multiple tiers of cognition with the fine-tuning sensory acquisition from heterogeneous contexts [57]. Distinct levels of collaboration between IoE resources require efficient solutions. Human sensors peculiarities contemplated by collaboration theory and technical aspects of user interaction are challenges in computer network theory [28]. It is imperative to provide awareness of collective intelligence and where the intelligence is [113], representing the outcomes expected in designing the IoE solutions, based on the application domain [28,104].

The outcome dimension refers to the degree to which knowledge sources (things and humans) contribute to knowledge creation in IoE intelligent services. Relevant knowledge contributions from human or non-human enablers (sensors or actuators) either complement or substitute (or both in some cases) to provide improved outcomes reached through knowledge sharing processes, and sometimes automating or transforming traditional tasks [55] into IoE environment disruptions:

  • Complementing: Represents knowledge sharing between IoE sensors and actuators. Complementing outcomes occurs when humans utilize mobile devices like sensors to collect their observations and information about the environment and infrastructures [25,51,65] or when artificial intelligence complements human knowledge.

  • Substituting: Provides insights and novel interpretation of reality to enhance the quality of life (livability), regarding knowledge acquisition as the “core element” and the realization of “intelligence” [77].

4.1.5. Action

The Action dimension refers to knowledge creation. Actionable intelligence is meaningful for humans to promote automated processes [51], ranging from creating value when used in a specific usage context [25,68,117] to transforming and changing the state of their environment [24]. Big data analytics aims to improve the understanding of data, thereby supporting useful and timely decision-making with the refined information gathered [40,42,69].

The goals of IoT systems range between general and specific and include monitoring, reducing costs, and improving processes [109].

For Russell et al. [117], even in the case of uncertainty, a rational agent is one that acts to achieve the best outcome or the best-expected outcome. There is a close interrelationship between intelligence and automation [55], or creating and pursuing goals through transformation. Sensor information in IoE applications provides either automation or transformation of the IoE environment, which are defined as follows:

  • Automation: the aptitude to make cognitive decisions related to a given situation, which guarantees the right action is performed. The automation of tasks and dependency on machines may reduce human abilities [105]. When combined with AI and machine learning, new applications will benefit from automated decision-making [106], with efficient usage of network resources, minimization of operational costs, coordination of computational resources, and efficient and effective data management mechanisms [60] associated with the quality of experience [104,118].
  • Transformation: an enormous number of raw observations (created by the machine and human sensors) can be transformed into higher-level abstractions [57] that are meaningful for human or automated decision-making processes [55]. When an IoE solution provides transformation, smart things act independently, with minimal or no human intervention [51]. With the support of wireless communications and AI, humans benefit from improvements in technological advancements [42,101] by collecting, modeling, and reasoning the context [36].

Considering how actions generate changes in the environment to achieve the desired goal, automation and transformation processes may occur in the short or long term or may represent a prominent solution. Some works have explored the implications of the IoE for value creation and decision-making provided by smart things and big data [15,39]. However, our study is concerned with how humans respond and interact with the environment in assisting the evolutions of future systems (defined in [15]), which can be:

  • Reactive: having the ability to promptly react to a changing environment;

  • Adaptive: having the steadier ability to adapt their behavior to changes;

  • Predictive: having the ability to use computation and analytics techniques to identify relevant patterns, in-depth knowledge of the environment, and the most appropriate solutions or possible evolutions to each IoE system situation.

4.2. Type

The type category contains five dimensions or subcategories for the classification of sensors and actuators: presentation, nature, use, role, and engagement. Figure 4 highlights the type category, its dimensions, and characteristics.

Figure 4. IoE Taxonomy: type category, its dimensions, and characteristics.

4.2.1. Presentation

Presentation refers to the physical aspects of sensors and actuators that interact with the physical world. The physical and virtual world can be merged by integrating computation and physical processes in one of the following ways: a) physical, b) cyber or virtual, and c) cyber-physical or logical [30,46,62,67,79,84].

Humans are content receivers and can act as a sensor collecting data for the sensory systems or actuators performing actions, but humans are also content providers who share diverse and relevant types of spatial-temporal data [59,63,65]. The physical dimension characterizes the mobility of the system’s things and the dependency of the collaboration of human and non-human devices [28,39]. Accordingly, sensors and actuators can be classified as follows:

  • Physical: Physical entities are tangible devices that generate sensor data or perform actions changing the environment. The data retrieved from physical sensors represent a low-level context [36]. Examples of physical sensors are temperature sensors, pressure sensors, biosensors, light sensors [6], and human sensors [35]. Examples of the physical actuator are a door opener actuator invoked by an intelligent system and human actuators.

  • Cyber or virtual: An abstract information entity that invokes sensor or actuator functions but does not directly interact with the physical world. Examples of cyber or virtual entities are computer programs and systems, communication processes, and monitoring activities with no physical body (e.g., sensing web service) [51,66,74]. Virtual entities use web services technology to send and receive data from many sources [36].

  • Cyber-physical or logical: Represents the connection of the cyber and physical worlds as a combination of physical and virtual entities to generate meaningful information [25,83]. Similar to virtual entities, they commonly use web services technology to send and receive data and interact with the physical world [36]. They are autonomous objects augmented with sensing, actuating, processing, storing capabilities [45]. Examples of cyber-physical entities are web services dedicated to providing weather information resulted from physical sensors that sense weather information and virtual sensors that process historic weather data.

4.2.2. Nature

This dimension is related to sensor or actuator knowledge, intertwined with its architecture and functionality [43]. A sensor is anything that observes, and an actuator is anything that performs defined actions [119]. People can be modeled as sensors and actuators [117], so anything that acts individually to perform a task in the IoE context is an individual IoE device [59]. Knowing the nature of knowledge source devices is crucial for publication, discovery, sharing, reuse, and integration of information within the IoE environment [72]. Human beings with dedicated roles, as well as machines, devices, and services [35,106,110], implies system constraints when it interacts with the physical space [46]. Humans are content receivers through the sensory systems and also content providers—mainly through sensing and actuating abilities [63,120], and through tacit knowledge and experiences that can affect their actuations in IoE applications and cognitive tasks.

The level of autonomy of an IoE sensor or actuator (human or non-human) refers to its ability to act independently [24,83,113]. Several works have identified entities—sensors/actuators—types according to activities carried out in physical and virtual worlds [30,37,62].

According to their built-in nature, sensors and actuators in IoE are classified [62] as follows:

  • Electronic-based: Define physical IoT devices constituted of electronic or mechanical systems that sense or actuate physical phenomena.

  • Software-based: Define virtual entities that process information from data sources or generate analytical results.

  • Human-based: Refers to humans or virtual entities based on knowledge provided or expressed by human perception about any phenomena arising in their physical, virtual, or social environment.

  • Non-human-based: Define biotic sensors/actuators or virtual entities based on knowledge data provided by biotic perception about any phenomena arising in their physical environment. In the constantly growing area of animal cognition, sensor networks monitor the health and well-being of animals in livestock herds and in animal surveillance applications [121].

4.2.3. Use

Refers to the physical characteristics of physical IoE sensors or actuators related to their usage in a particular application. The devices inherit the attributes of their owners or of the entities or places [79] to which or where they are attached [43,66,113]. A wide variety of objects—a group of infrastructures and devices [44] such as embedded devices, sensors, and actuators—have integrated communication and strong interactions to create a ubiquitous environment [71,106,110]. A taxonomy for IoT sensors communicates how distinct types of sensors are combined and used in specific application domains [72].

Smutný [29] described things according to how they are used or applied in relation to humans:

  • Embeddable: Things that are in the user or under the user’s skin, that are non-autonomous, or embedded in carry-on devices [42]. The level of autonomy ranges from human-companion device tasks [65] to opportunistic devices, which decide and act independently [24,28]. For example, a mobile phone is a ubiquitous, convenient and user-friendly device and has many sensors embedded [48], which is why it has turned into a global mobile sensing device [67].

  • Wearable: Things that rest on a person’s body or can be used, worn, or attached to their owners and enable accurate detection of the wearers’ motions [50,63,64,75].

  • Surroundable: Things that are autonomous, near or around the user, but which have no physical contact with the user. Recently, several non-contact techniques have been interpreted as highly valuable in dealing with highly infectious diseases such as COVID-19. In a pandemic scenario, non-contact sensing was able to detect information without direct contact with the patients and without devices physically touching the body [122].

4.2.4. Role

IoT devices have sensing and actuating capability according to defined rules under various scenarios [59,72]. They perform sensing and actuating functions [24,26,51] that help in interacting with the physical environment [48]. An IoE device or enabler can be a sensor, an actuator, or a sensor and actuator [44,77,106].

  • Sensor: A device that observes and senses. Sensing is a read operation over a context entity. The data collected by a sensor is stored and processed intelligently to derive useful inferences and to support the decision-making process [46]. Sensors are monitor devices and physical entities, which provide the information required to immediately control actuators, whereas actuators act on the physical entity or control other things [28,35,114].

  • Actuator: Affects a particular domain of the physical space or a combination of both. Actuation is a write operation over a context entity, in which the conceptual entity represents the domain of a sensor or an actuator [44]. Actuators perform the decided actions and effect a change in the environment [36,39,48].

  • Sensor and actuator: This device is a hybrid of the two previous categories, and it can gather data and act within its environment.

Processing and analytics (fixed process or algorithm, machine learning, or AI) do not fit within this classification [113].

4.2.5. Engagement

Participation is an interaction between people with existing technologies and occurs at different engagement levels [67]. Engagement refers to sensing tasks. In data acquisition, it can be both opportunistic and participatory, and it provides sensory information that collectively forms knowledge.

For example, enhancing human senses is possible when machines interact with humans or provide remote operation in perceived real time in ubiquitous computing [57,63]. Cooperative smart things can interact with other entities of the IoE in order to achieve a unified objective [15]. With mobile crowdsourcing, the primary information shared voluntarily is user knowledge and opinion, along with location as the only sensor information [65]. The engagement of a sensor node in an IoE application is one of the following:

  • Participatory: The IoE enabler (sensor node or actuator) is actively involved and actively reports observations [120]. It can provide information about the environment or surroundings, as well as any other sensory information that could be on social groups (social sensing) or with everyone (public sensing) or at the community level [37,67,106].

  • Opportunistic: The IoE node has minimal or no involvement—it senses and monitors tasks running in the background. Embedding sensors trigger the data automatically (either periodically or based on events).

4.3. Observation

The observation category contains five dimensions or subcategories related to sensed context: location, reach, mobility, time, and mode. Figure 5 emphasizes the dimensions and their sub-dimensions or characteristics.

Figure 5. IoE taxonomy: observation category, its dimensions, and characteristics.

4.3.1. Location

Location is used to describe the spatial context (physical context) of users/devices within a local or global network [24,113]. It represents the geophysical position of a sensor or actuator in absolute values, identifying the coordinates (latitude and longitude) or relative specifications through location tags [45], which is obtained manually or automatically [120,123]. It represents the definition of an area covered by a particular object [79]. Sensors that are randomly deployed get the required information about the target environment [81].

Location systems can be categorized as context-aware systems [75]. The precise location of an object is critical since location plays a critical role in context-aware computing [36,66,80]. Moreover, aggregation of knowledge patterns facilitates reduced data transfer in distant environments and minimizes bandwidth use [94]. Some physical measurement-based localization schemes are classified as coarse-grained and fine-grained [80].

4.3.2. Reach

Reach classification distinguishes between individual and collective knowledge. It refers to an environment of sensing interest [71]. Sensors are becoming more sophisticated in technology advances, cheaper in price, and smaller in size. This evolution stimulates large-scale deployments [36], and dense geographical distribution [60].

The domain of interest represents the applicative domain in which the device is operative [79,81] and ensures that IoT services are accessible or reached only by authorized access [113,124].

The prevalence of mobile devices, such as smartphones, has triggered challenges for mobile networks worldwide [125], as well as novel classifications, such as collective knowledge classified into individual or group, internal or external, full or partial domains. For example, a conglomeration of sensor data stored on cloud infrastructure can be designed as big data sensing, and based on the reach of its sensing requests and requirements [74], it can be referred to as a) private, b) public, c) community, or d) hybrid big data sensing.

In crowdsourcing, regarding the boundaries of the individual scope in which crowds collaborators are immersed, the reach can be classified as ranging from small to large-scale (from a person to a group, community, city, and so forth) [28,65].

4.3.3. Mobility

Mobility, which is also called monitoring continuity [36], is one of the main characteristics that enables identification of the state of sensors and actuators and their capability of movement [26,36,39,43,44,80], with significant implications on device operation, connectivity, and location management [30,48,80]. Devices are classified into two categories: static/immobile/fixed and mobile [26,77,82,113].

  • Fixed/static/immobile: Objects that remain static to a specific location or cannot move. Their observations are restricted to a specific location, in a static or very constrained (in terms of mobility) environment that is not designed to move (relative to their point of installation) without being uninstalled.

  • Mobile: The objects move [44], and their location may be calculated in absolute coordinates or relative to reference nodes in the network [81], requiring wireless communications to transmit data and allow configuration and control [113]. Their movement and mobility capability are controlled independently (or autonomously) or dependently through device users [43].

A self-moving device moves autonomously and relative to its setup/installation point, without being uninstalled (e.g., smart car), whereas a non-self-moving device does not move autonomously but can still move relative to its original location without being uninstalled [26,77].

Mobility of the things in the system is dependent on the collaboration of the items physically coupled with the humans in the system [28], as in crowdsensing applications, in which geographically dispersed users actively (participatory) or passively (opportunistic) collect data with their smartphones [51,75]. Classifications between mobility-agnostic and mobility-aware [82] highlight an approach that ignores knowledge about mobility and the ones that consider and exploit it for optimization [12].

Challenges related to mobility include frequent disconnections and handoffs, which affect perfect connectivity [126]. Mobility techniques in the cloud, fog, and edge architectures [60] support mobility, and other protocols apply routing and resource discovery mechanisms [39].

4.3.4. Time

Time represents the instant of observation (i.e., timestamp) [79]. Information about time and location are critical features of some applications (called spatial-temporal-aware applications) that require tasks to make observations at a specific location during a defined period [120]. In [24], latency relates to the time an IoE system needs to answer to a stimulus. Interaction between IoE smart devices can influence the service’s response time to end-users. The time interval between the initiation and the conclusion of the task is the response time [49,107,109].

The time dimension depends on how sensors are requested or provide data to the system in specific periods or on an ad-hoc basis (as software system makes a request), which is characterized as the following two distinct methods that were proposed in [107]:

  • Pull method: The software component in the control of obtaining sensor data from sensors makes a requisition periodically (after specific intervals) or instantly obtains sensed data [107].
  • Push method: The physical or virtual sensor pushes data to the software component in the control of obtaining sensor data periodically [36,107]. In many cases, a sensor observation can be the result of a local sensor data fusion [68].

Real-time applications monitor the state of the environment and react to changes accordingly and in a timely manner.

The deployment of IoE applications in real-world scenarios creates a massive amount of data from real-time interactions, usually at high data rates. It faces challenges as temporal data consistency related to the coherency between the value of the data in the system and its environment state [107]; and high latency during interactions [39], when inferred contexts evolve with time [91,94], and the exchanged data may not be accurate.

Hard real-time data cannot accept any delay; in contrast, soft real-time data can accept various bounded delays. Delay-tolerant applications can be categorized as nonreal time [60,107]. In offline circumstances, the delayed transmission may be crucial to address quality and security constraints [37,65].

In real-time situations, timeliness [69,107] describes data processing in a specific deadline, which is real time, near real time, or batch processing [113].

  • Real time: refers to the immediate data processing to provide instant results for a time-sensitive application.

  • Near real time: refers to situations when the delay time is still relevant for the application, but the computation process is not as immediate as real time.

  • Batch-processing: refers to situations when data are first collected and processed at a predetermined interval or when a specified volume of data is available [37].

4.3.5. Mode

The combination of sensors serving different purposes and data generated in IoE applications implies the need to classify data sources and information in the IoT context [72]. During real-time data harvesting, it can be challenging to determine the possible relationships among heterogeneous knowledge sources [69]. Smart device sensors are either active or passive sensors, depending on their usage and functionalities. If the sensor data collected are reflected in the same way as designed, this is called active functionality. However, sensors operate passively when collected data are interpreted or processed in new ways [17,65].

Eris et al. [28] defined how much interaction is required within the network in three levels of collaboration interdependence [28]:

  • Pooled interdependence: The lowest level of collaboration, in which each collaborator barely contributes to the collaboration environment and benefits from the contributions of others. The collaborators neither synchronize nor negotiate the nature of each other’s contributions.
  • Sequential interdependence: The middle level, in which the contributions of one collaborator become the inputs to another collaborator contributions. In this case, there is a temporal ordering of the collaboration efforts.
  • Reciprocal interdependence: The highest interdependence level, in which one collaborator’s contributions are the next collaborator’s inputs, and collaborators must also negotiate the nature of each other’s contributions to the collaboration environment.

The Mode dimension refers to the way of linking the physical and digital world in order to acquire context [127], and it can be either sensed, derived, or manually provided:

  • Sensed: Data gathered through sensors.

  • Derived: Includes the sensed data stored in databases or the information generated by performing computational operations on sensor data. Data aggregation is the ground for the application’s workflow and unconditionally impacts the application’s quality. Distinct aggregations may have specific requirements to be supported by design [107].

  • Manually provided: Human sensors provide the context information [36].

4.4. Capabilities

The capabilities category contains three dimensions or subcategories (communication, processing, and storage) and refers to the processing power and storage capacity of the underlying technologies and communication protocols. Each dimension has its specific sub-dimensions or characteristics, as represented in Figure 6.

Figure 6. IoE Taxonomy: capability category, its dimensions, and characteristics.

4.4.1. Communication

The communication capability refers to the sensors’ ability to communicate and change information locally. This ability may vary at different levels of interoperability between IoE sensors and systems and be classified as no connection (no connectivity between enablers), technical (basic network connectivity), syntactical (basic interoperability and data exchange), semantic (understanding about the semantics of the data), pragmatic or dynamic (applicability of the information), conceptual (shared view of the pervasive world) [27], or organizational (coordination and alignment of business processes across organizational boundaries) [128]. Additionally, based on communication capabilities, IoT devices are classified into two categories: gateway devices and constrained devices [43,45]. Moreover, according to their abilities to interact with other objects, IoT objects can be classified into four levels (Level 0–Level 3). Level 0 objects only receive, and Level 1 objects only send information. Level 2 objects can perform both operations with one object, while Level 3 extends the interaction to any other object [50].

Different networking protocols and technologies provide networking interoperability in IoT [27,48,114]. IoT systems can exploit several types of networks with different characteristics in terms of size, data transfer, coverage, latency requirements, capacity, and supported reachability [69,74,75,83,110]. The central networking and communication technologies are local area networks, wireless local area networks, wireless personal area networks, wide area networks, metropolitan area networks, wireless regional area networks, body area networks, mobile communication networks, wireless metropolitan area networks, satellite networks (e.g., GPS) [24,118,129], Neul, IPv6 over low-power personal area networks (6LowPAN), low-range wireless area networks, cellular Sigfox, narrowband-IoT, and thread or mesh technologies such as Zigbee and SDNs [25,30,113].

There are three types of communication protocol that enable IoT to interconnect and communicate: (1) device-to-device, which is applied to communication between mobile phones within reach and is the next-generation of mobile networks; (2) device to the server, in which the sensed data are sent to the servers, nearby or away from devices (applies to cloud processing); and (3) server-to-server, in which servers transmit data between each other—mainly used for mobile networks [99].

4.4.2. Processing

The sensors and devices used for data collection also vary in their processing capabilities [130]. The study of Mon et al. [127] classifies sensors as high-end or low-end devices, depending on resources and computational capabilities. Low-end devices are resource-constrained with regard to energy, processing power, and communication capacities. The processing capability refers to the sensors’ ability to process aggregated data locally [55].

For IoE systems, data are automatically processed to deduce knowledge and generate actionable insights. In general, data processing techniques are either historical or proactive. Historical data processing is related to knowledge discovery, whereas proactive data processing provides predictive and actionable insights [24]. A broad category of applications participates in the continuous generation and analysis of high-volume heterogeneous stream data. Next-generation applications will be developed to handle the data in streaming mode and on-the-fly as the value of data resides in its real-time processing [131].

Analytics technology refers to the systematic computational analysis of transforming a variety of data from different sources into information [105] and applying data fusion and mining techniques [94] to make intelligent decisions at the following distribution levels: (1) the device level, where devices are responsible for storage and computing process; (2) the network level, which demands remote communication to fog computing nodes (hubs, base stations, gateways, routers, and servers); and (3) cloud level, which demands remote communication within a group of interconnected servers [24,38,73,114,118].

Cloud, edge and fog computing are critical aspects of the centralized and decentralized IoE environment, considering that devices that have restricted compute and memory capacity need to delegate these functions [25,26,29]. Integrated with cloud computing, edge computing can efficiently address the processing problems related to edge big data. Since in the edge computing paradigm, the data are at the edge of the network [28,56].

A variety of cloud computing and edge computing paradigms are mobile cloud computing, mobile edge computing, and fog computing [32,60,126]. Cloudlets, mobile edge computing, and fog computing are edge computing technologies and rely on virtualization, while mobile cloud computing processes the data of mobile applications at a remote cloud data center.

4.4.3. Storage

This capability refers to an IoE system’s storage function, based on the paradigm where its storage function resides: cloud, fog, or edge [73]. A storage platform (public, virtual, or private) offers the flexibility and scalability that an IoE application needs, from development to deployment [29]. Storage refers to storing data internally, and it varies intensively from one object to another [55]. Storage interactions between IoE enablers may be distinguished significantly depending on the object’s storage capabilities. Some objects may have restricted capabilities and store minimum information [132]. Most mobile devices at the edge of the network are resource-constrained in terms of storage, computation capability and battery life [56]. Although almost all of the objects have the capacity to store embedded codes to function internally, they differ in storing aggregated and processed data [104]. An object’s storage should also be based on the sensitivity of the information stored [55].

Analytics processing requires real-time data stream processing for supporting the rate of data arrival, data management, and data storage [105] at diverse distribution levels.

Depending on the storage and compute capabilities, the storage capability of an IoE node or application is [114]:

  • Device-level: devices are participants in the storage and compute process;

  • Network-level: the storage process uses remote connections to fog computing nodes;

  • Cluster level: storage function is provided between a set of interconnected servers [114].

This entry is adapted from the peer-reviewed paper 10.3390/s21020568

This entry is offline, you can click here to edit this entry!
Video Production Service