Skip to content

Commit

Permalink
Merge pull request #145 from Tedoshiii/teodor-edit-tutorialpage
Browse files Browse the repository at this point in the history
Website text adaptation
  • Loading branch information
egekorkan authored Apr 14, 2024
2 parents b589f2f + 8cb45b8 commit 0fd4087
Show file tree
Hide file tree
Showing 27 changed files with 303 additions and 247 deletions.
34 changes: 10 additions & 24 deletions Tutorials/whatiswot/website/docs/Application Domains.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,23 +2,15 @@
id: Application Domains
---

We will give a introduction to the W3C Web of Things including its application domains and we will continue with architecture patterns, and building blocks.
WoT, as we already know, is a set of standards defined for the interoperability of different Internet of Things platforms and application domains by the World Wide Web Consortium (W3C). It aims to preserve and complement existing IoT standards and solutions by providing a standardized approach for connecting and integrating smart devices, services, and applications into the Web.

So let's start with what is WoT.

It is a set of standards defined for the interoperability of different Internet of Things platforms and application domains by the World Wide Web Consortium (W3C).

The WoT aims to preserve and complement existing IoT standards and solutions by providing a standardized approach for connecting and integrating smart devices, services, and applications into the Web.

Now, let us introduce some of the WoT application domains: Smart Homes, Industrial Applications, Agriculture, and Smart Cities.
In this section we will introduce some of the WoT application domains: Smart Homes, Industrial Applications, Agriculture, and Smart Cities.

## Smart Homes

In spaces like smart homes, it is very beneficial that multiple assets can be connected and managed over the network.
In smart homes, the ability to connect and manage multiple assets remotely over the network is highly beneficial.

Depending on the conditions at home, various activities can be performed in the house or remotely.

For example, turning on lights, changing room temperature, turning home appliances on and off, managing sound and security with a smartphone. Thus, energy and other resource consumption can be optimized.
This helps within various activities within the home, such as controlling lights, adjusting room temperature, managing home appliances, and enhancing security using smartphones. These capabilities enable optimization of energy and resource consumption.

![smart-home](/img/10-Application-Domains/smart-homes.png)

Expand All @@ -28,20 +20,17 @@ or interactions happen through an intermediary like a cloud application.

Services running in the cloud collect data from edge devices and provide the data to users of the smart home through edge devices such as phones or PCs.

Multiple edge devices are connected to the gateways through local communication protocols such as KNX, ECHONET, ZigBee, DECT ULE, and Wi-SUN.

Multiple gateways can exist in one home, whilst each gateway can support multiple local protocols.
Multiple edge devices are connected to the gateways through local communication protocols such as KNX, ECHONET, ZigBee, DECT ULE, and Wi-SUN. Multiple gateways can exist in one home, with each supporting multiple local protocols.

![smart-home-connection](/img/10-Application-Domains/smart-home-connection.png)

## Industrial Applications

The next one is the Industrial applications of WoT. Let’s zoom in on this factory.
Industrial applications may resemble smart home applications but they have to support more complex use cases such as advanced monitoring of the connected manufacturing equipment as well as the manufactured products and predictions of any possible machine failures.
Industrial applications of WoT involve more complex use cases compared to smart homes. In factories, for instance, advanced monitoring of connected manufacturing equipment and products is essential, along with predictive maintenance to anticipate machine failures.

![inside-of-factory](/img/10-Application-Domains/inside-of-factory.png)

Let's look at one smart factory example in detail. This time, different factory equipment is automated based on industrial protocols such as PROFINET, Modbus, OPC UA TSN, EtherCAT, or CAN. Since industrial environments like factories, have more strict requirements, there are multiple controllers that are connected to the manufacturing equipment.
Let's look at one smart factory example in detail. Here, different factory equipment is automated based on industrial protocols such as PROFINET, Modbus, OPC UA TSN, EtherCAT, or CAN. Since industrial environments like factories, have more strict requirements, there are multiple controllers that are connected to the manufacturing equipment.

An industrial edge device collects data from various controllers and enables remote monitoring via a dashboard or analyzes it for preventative maintenance.

Expand All @@ -57,12 +46,9 @@ With WoT, soil conditions can be monitored and optimal plans for watering and fe

## Smart Cities

The last application domian we will explain is Smart Cities.
The last application domain we will cover is smart cities. Similar to smart homes, monitoring of smart cities is possible. In this case, end users are citizens, municipalities, and government agencies.

Similar to smart homes, monitoring of smart cities is possible.
In this case, end users are citizens, municipalities, and government agencies.
In smart cities, bridges, dams, and canals can be monitored for material conditions or deterioration for maintenance repair work.
Thus, significant damage is prevented.
In smart cities, bridges, dams, and canals can be monitored for material conditions or deterioration for maintenance repair work to prevent significant damage.
Parking slots and street lights can be monitored for crowd management and optimized usage too.


Expand All @@ -71,7 +57,7 @@ Parking slots and street lights can be monitored for crowd management and optimi

### What's More?

There are many more domain-specific examples in the WoT Architecture document besides the one that we listed in this video. If you want to learn more, you can check the website:
There are many more domain-specific examples in the WoT Architecture document besides the ones that we listed in this tutorial. If you want to learn more, you can refer to the WoT Architecture document available at:

https://www.w3.org/TR/wot-architecture/

Expand Down
47 changes: 14 additions & 33 deletions Tutorials/whatiswot/website/docs/Architecture Patterns.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,67 +2,48 @@
id: Architecture Patterns
---

In this tutorial, we will explain architecture patterns, and how devices / things interact with controllers, agents, and servers.
In this section, we will introduce and discuss different architecture patterns and how devices interact with controllers, agents, and servers.

Previously we have explained the server and client models and described how this architecture works.

Now we will show how they are used in the WoT architectures.

We will introduce 6 architecture patterns in this tutorial:

- Device Controllers
- Thing-to-Thing
- Gateways
- Digital Twins
- Cross-domain Collaboration
- System Integration
Before, we explained the server and client models and how they operate. Now, let's see how they're applied in WoT architectures.

## Device Controllers

So, first, let’s start with the device controllers. A common deployment pattern is a local device controlled by a user-operated remote controller. Let’s remember the smart house example from the previous tutorial.

A remote controller can interact with the electronic devices through the local home network. In this pattern, at least one device electronic device has a server role that can accept a request and respond.
A common deployment pattern is a local device controlled by a user-operated remote controller.

![smart-home-request](/img/11-Architecture-Patterns/smart-home-request.png)
> Let’s recall the smart house example from the previous section. A remote controller can interact with the electronic devices through the local home network. At least one electronic device acts as a server, capable of receiving and responding to requests, while the remote controller acts as a client, sending messages for actions like sensor readings or device activation.
Another device remote controller has a client role that can send a message with a request like to read a sensor value or to turn on the device.

![smart-home-response](/img/11-Architecture-Patterns/smart-home-response.png)
![smart-home-request](/img/11-Architecture-Patterns/smart-home-request-response.png)

## Thing-to-Thing

Let’s move to the second architecture pattern, Thing-to-Thing. In this scenario we have an electronic device, let's say a heater and a temperature sensor.
In this pattern devices communicate directly with each other.

When a sensor detects a change in room condition such as temperature drops below the threshold, it issues a control message “turn on” to the electronic device to power on the heater.
> Let's take a heater and a temperature sensor. When the sensor detects a change in room condition, for example, as temperature drops below a set threshold, it sends a control message to the electronic device to turn on the heater.
![thing-to-thing](/img/11-Architecture-Patterns/thing-to-thing.png)

## Gateways

Third architecture that we will intorduce is Gateways.

Smart home gateways pattern is achieved by placing a gateway between a home network and the Internet to manage electronic devices inside the house. It can also receive commands from a remote controller over the Internet.

In this pattern, the home gateway has both client and server roles.
The smart home gateways pattern is achieved by placing a gateway between a home network and the internet to manage electronic devices inside the house. They can receive commands from a remote controller over the internet and serve as both clients and servers.

For instance, when the remote controller in this case a smartphone, turns on the electronic device let's say security camera in the client role and the smartphone in the server role.
> For instance, the remote controller - in this case a smartphone, turns on the electronic device - the security camera. Then gateway acts as a client for the camera has the client role and as a server for the smartphone.
On the other way around, when the security camera sends a message to the smartphone, the gateway acts as a server role for the security camera and it acts as a client for the smartphone. If the camera is in a client role, it can pass the firewalls easily.
> Conversely, when the security camera sends a message to the smartphone, the gateway acts as a server for the security camera while it also acts as a client for the smartphone. If the camera plays the client role, it can bypass the firewalls easily.
![gateway](/img/11-Architecture-Patterns/gateway.png)

## Digital Twins

The next one is Digital twins. Digital Twin is a model of a device or a group of devices that resides on a cloud server or edge devices. It is useful to represent real-world devices that may not be continuously online or to test simulations and services before they are deployed to real devices.
Digital twins are models of real-world devices hosted on cloud servers or edge devices. They are useful for representing real-world devices that may not be continuously online or to test simulations and services before they are deployed to real devices.

![digital-twin](/img/11-Architecture-Patterns/digital-twin.png)

It can model one or more devices. Digital Twins can be categorized in different ways depending on weather a device is connected to the cloud or gateway.
Digital twins can model one or more devices. Digital Twins can be categorized in different ways depending on whether the device is connected to the cloud or a gateway.

## Cross-domain Collaboration

Lastly, we will move to cross-domain collaboration. In cross-domain collaborations, each system involves other systems in other domains. For example, Smart Factory with Smart City, Smart City with Smart Home.
Lastly, in cross-domain collaborations, each system interacts with systems from other domains. In those models, this can occur directly in a peer-to-peer manner or indirectly through collaboration platforms.

In those models, you can exchange information directly with each other in a peer-to-peer manner or indirectly via some collaboration platform.
> For example, Smart Factory with Smart City, Smart City with Smart Home may collaborate to exchange information to optimize operations.
![cross-domain-collab](/img/11-Architecture-Patterns/cross-domain-collab.png)
Loading

0 comments on commit 0fd4087

Please sign in to comment.