Scribd
Upload
86 views5 pages

IOT ARCHITECTURE and DESIGN PRINCIPLE

The document outlines an IoT architecture with multiple layers and functional groups. It details the purpose of each layer, from the asset layer representing the justification for the IoT application, to the business layer focusing on supporting core business operations. Functional groups like management, security, and IoT data and services are also described.

Uploaded by

abinivesh64
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
86 views5 pages

IOT ARCHITECTURE and DESIGN PRINCIPLE

The document outlines an IoT architecture with multiple layers and functional groups. It details the purpose of each layer, from the asset layer representing the justification for the IoT application, to the business layer focusing on supporting core business operations. Functional groups like management, security, and IoT data and services are also described.

Uploaded by

abinivesh64
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

1. architectural design.

\ buliding an arch model

When creating a model for the reference architecture,one needs to


establish overall objectives for the architecture as well as design
principles that come from understanding some of the desired major
features of the resulting system solution.

The problem domain establishes the foundation for the subsequent


solutions.

The pyramid is a way of representing the different levels of abstraction in


a system design.

The top level of the pyramid is the problem domain. This represents the
realworld problem that the system is trying to solve. It includes the
requirements, needs, problems, and constraints of the system.

The middle level of the pyramid is the solution domain. This represents
the possible solutions to the problem in the problem domain. It includes
the concepts, needed capabilities and functions, and technology
components of the system.

The bottom level of the pyramid is the system solution. This represents
the specific implementation of the solution in the solution domain. It
includes the system design, software components, and hardware
components of the system.
The problem and solution domain partitioning process is a way of
breaking down a complex problem into smaller, more manageable pieces.
It helps to ensure that the system design is focused on solving the
realworld problem and that the chosen solution is feasible and meets the
needs of the stakeholders. [1]

Here are some of the benefits of using problem and solution domain
partitioning:

 It helps to improve communication between stakeholders by


providing a common vocabulary for discussing the system.
 It helps to identify and manage risks early in the development
process.
 It helps to ensure that the system design is modular and reusable.
 It helps to improve the quality of the system by making it easier to
test and maintain.

Overall, problem and solution domain partitioning is a valuable tool for


system designers. It can help to improve the quality, efficiency, and
maintainability of complex systems.

2. design principle

Main design principles and needed capabilities (design objective and


principles) main desired characteristics of an M2M or IoT solution

The overall design objective of IoT architecture shall be to target a


horizontal system of realworld services that are open,
serviceoriented, secure, and offer trust.

1. Design for reuse of deployed IoT resources across application


domains.
2. Design for a set of support services that provide open
serviceoriented capabilities and can be used for application
development and execution.

• To access iot resources

• How to publish and discover resources,

• Tools for modeling contextual information


• Information related to the real world entities

• Capabilities that provide different levels of abstracted and


complex service

• Data filtering and analytics

• Apis & SDK

3. Design for sensing and actors taking on different roles of


providing and using services across different business domains and
value chains.

• technologies,

• data and service representation

• service : information and services, & aggregation of information 4.


Design for sensing and actors taking on different roles of providing
and using services across different business domains and value chains.

• Needs to be provided is a set of mechanisms that ensure security


and trust

• Need to be authentication and authorization of access to use


services as well as to be able to provide services

• Requirement is the capability to be able to do auditing and to


provide accountability so that stakeholders can enforce liability if
the need occurs

• fundamental requirement is to ensure interoperability

4. Design for ensuring trust, security, and privacy. Reliability,


availability of services, security and privacy

5. Design for scalability, performance, and effectiveness.

• Scalability aspects: large number of devices and amounts of data


produced

• Performance: Supervisory Control And Data Acquisition (SCADA)

6. Design for evolvability, heterogeneity, and simplicity of


integration.
7. Design for simplicity of management.

8. Design for different service delivery models (CLOUD SERVICES) for


instance, connected vehicles, and Software as a Service (SaaS) as a
delivery model

9. Design for lifecycle support. The lifecycle phases are: planning,


development, deployment, and execution. Management aspects include
deployment efficiency, design time tools, and runtime

3. An IoT architecture

It seems like you've provided an outline of an IoT architecture, detailing various


layers and functional groups. Each layer serves a specific purpose in facilitating the
functioning of IoT applications. Here's a breakdown based on your outline:

1. Asset Layer: This layer signifies the purpose or justification for the existence of the
IoT application.

2. Resource Layer: Provides the main functional capabilities such as sensing,


actuation, and embedded identities through devices like sensors, actuators,
smartphones, etc.
3. Communication Layer: Facilitates connectivity between resources and computing
infrastructures using different types of networks, like LANs and WANs.

4. Service Support Layer: Executes support services in data centers or cloud


environments, simplifying common tasks for IoT applications.

5. Data and Information Layer: Manages data, information models, and knowledge
representation, focusing on organizing information effectively.

6. Application Layer: Implements specific IoT applications such as Smart Grid,


vehicle tracking, etc.

7. Business Layer: Focuses on supporting the core business or operations of


enterprises or individuals interested in IoT applications, involving systems like CRM
and ERP.

Functional Groups:

Management: Handles the operation, maintenance, administration, and provisioning


of the IoT system, including device management, network management, and IT
infrastructure management.

Security: Ensures protection of the system, its information, and services from
external threats or harm, requiring security measures across all layers.

IoT Data and Services: Manages data processing and services, including event
filtering, aggregation, data mining, analytics, and the flow of data into knowledge.

This architecture provides a comprehensive framework for designing and


implementing IoT solutions, ensuring functionality, connectivity, security, and
effective data management.

You might also like