Aerospace and Electronic Systems Magazine May 2018 - 76

CONASENSE
ENSE aims to integrate the academia, industries, research centers, institutes, and organizations to achieve the convergence
of communication, navigation, sensing, and services. Its main
goal is to combine research innovations from domains to make
them accessible to users and to support generalized user mobility. In particular, CONASENSE addresses the rapidly evolving and radically changing manner through which traditional
communication and services are being used, demanded, and
performed.

Figure 2.

Human bond sensorium architecture [2].

Brain-to-brain transmission, in which a person sends information directly to another person. This method is commonly
used by parents communicating with their children or by
specialists communicating with disabled individuals.
Device-to-device transmission, in which sensors directly
send data to data centers or smartphones. This method is often used to address healthcare or safety concerns.

HBC is evidently an important advancement in wireless technology and requires numerous requirements to be fulfilled before
actual implementation. Figure 3 shows four essential considerations for HBC implementation. A previous study [13] has already
discussed physical layer improvements. The current work proposes
to use a platform for the full implementation of the HBC concept.
CONASENSE supports the HBC concept by providing diverse
activities and services. This study comprehensively discusses security and standardizations and introduces the full options and possibilities that can be achieved with CONASENSE. The following
section describes CONASENSE for HBC implementation.

CONASENSE
CONASENSE, a complete platform for future wireless communication, serves as a foundation for the HBC concept. CONAS-

SECURITY
Traditional security architectures protect audio information and
data. They possess the following common security features.
C

User identity management based on (U)Subscriber Identity
Module

Mutual authentication between networks and users

Hop-by-hop path security between communicating parties

Wireless communication in the future is expected to be service
oriented. This expectation implies that special emphasis will be
placed on security requirements that originate from services, thus
leading to different security issues for different services. To fulfill
the security which is needed for HBC, a new and flexible security architecture should be introduced [1412]. Table 1 illustrates
the security requirement for HBC in details. A flexible security
architecture is required in this case to support and protect different
services. New security and privacy implications in future wireless
communication require at least four specifications, namely, new
trust models, new service delivery models, an evolved threat landscape, and increased privacy concerns.

Table 1.

Summary of Security Requirement for HBC
Security
requirement
Confidentially

Personal data should be
considered confidential at nodes,
servers, and transmission stages

Integrity

Destruction in data should be
considered in all levels and user
should be warned about it

Dependability

Retrievability of data should be
possible all the time even after
destruction

Scalability

Access controls should be
scalable based on different
load of nodes to avoid storage
overhead

Flexibility

Nodes could be able to choose
access points any time anywhere
to transmit data

Figure 3.

Essential components of HBC to be considered in architecture design.

Description

IEEE A&E SYSTEMS MAGAZINE

MAY - JUNE 2018

Table of Contents for the Digital Edition of Aerospace and Electronic Systems Magazine May 2018