Internet of Things Architecture

VE Service

VE & IoT

Service Monitoring

VE Resolution

IoT ServiceResolution IoT Service

CommunicationEnd To End CommunicationNetwork CommunicationHop to Hop

OrchestrationService

CompositionService

Management Security

Application

Communication

Configuration

Fault

Authorisation

Key Exchange &Management

Trust & Reputation

Identity Management

Authentication

Device

Reporting

Member

State

Process Management IoT

ModelingProcess

ExecutionProcess

ChoreographyService

OrganisationService Virtual Entity IoT Service

Figure 37 : Communication FG

The Hop To Hop Communication FC provides the first layer of abstraction
from the device‘s physical communication technology. The functional
component is an abstraction to enable the usage and the configuration of any
different link layer technology.

Its main functions are to transmit a frame from the Network Communication FC
to the Hop To Hop Communication FC and from a Device to the Hop To Hop
Communication FC. The arguments for the frame transmission can be set and
example of arguments include: reliability, integrity, encryption and access
control.

The Hop To Hop Communication FC is also responsible for routing a frame.
This function allows routing a packet inside a mesh network such as for
instance 802.15.4 (mesh-under routing). Note that this function is not
mandatory for all implementations of the Hop To Hop Communication FC. It is
required only for meshed link layer technologies.

Finally, the Hop To Hop Communication FC allows to manage the frame queue
and set the size and priorities of the input and output frame queues. This
function can be leveraged in order to achieve QoS.

The Network Communication FC takes care of enabling communication
between networks through Locators (addressing) and ID Resolution. The FC
includes routing, which enables linking different network address spaces.
Moreover different network technologies can be converged through network
protocol translations.