> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/references/mymove-concepts.md).

# MyMove Concepts

During the exploration of MyMove and its documentation, you will encounter various concepts, variables, and terms. Below, you will find additional information on these concepts and guidance on how to locate them within MyMove.

## About Move Solutions

Wireless IoT solutions for safer infrastructures and proactive asset management. 

Move Solutions provides organizations with actionable data to ensure the safety and performance of valuable assets. We offer a wireless system for remote, continuous, and comprehensive analysis of the health of the structures. We promote more sustainable and resilient infrastructure by integrating cutting-edge Internet of Things (IoT) technology with Structural Health Monitoring practices. 

Users can identify structural damage, conduct static, dynamic, geotechnical, and environmental analyses, and gain a clear view of the evolving health of the structure over time. Move Solutions sensors, integrated with the MyMove platform, provide the necessary information to foster a proactive approach to monitoring, helping to make infrastructures safer, more sustainable, and more resilient.

For more detailed information and services offered by Move Solutions, visit our website: [www.movesolutions.it](http://www.movesolutions.it)

## **System Structure**

The Move Solutions system is based on the synergy between hardware and software, consisting of the following main components:

1. **End Node Devices**: Sensors or communication nodes that collect and transmit data.
2. **Gateways**: Devices that collect data from the end node devices and forward it to the network server.
3. **Network Server**: Manages the [LoRaWAN](/untitled/references/lorawan.md) network, authenticates devices, and handles communication between devices and the MyMove Platform. Gateways are connected to the internet via mobile SIM or Ethernet connection.
4. **MyMove IoT Platform**: Receives and manages data from end node devices, performs analyses, and provides applications for end-users.

<figure><img src="/files/it8ILTxqTZXdIHbZsFgs" alt=""><figcaption><p>System architecture</p></figcaption></figure>

{% hint style="info" %}
**Uplink**

This involves the transfer of data from the device to the Network Server. For instance, when a sensor sends collected data or status information, an uplink operation occurs.
{% endhint %}

{% hint style="info" %}
**Downlink**

This involves the transmission of data from the Network Server to the device. For example, when a new configuration is sent from the MyMove platform to a remote device, a downlink operation takes place.
{% endhint %}

{% hint style="info" %}
**Downlink multicast**

This involves the transfer of data from the Network Server to multiple devices simultaneously. For example, when a command to start a scheduled acquisition is sent from the MyMove platform to several devices, a downlink multicast operation is performed.
{% endhint %}

***

## **Sensor Network**

The devices are key elements for collecting data on the structural health of the infrastructures they are installed on. The system offers a wide range of wireless sensors and communication devices. [Learn more about Move Solutions devices.](/untitled/references/devices.md)

## **MyMove IoT Platform**

MyMove is Move Solutions' IoT platform dedicated to managing structural monitoring projects. View, monitor, and analyze data from sensors installed on the infrastructure in real-time. Connect, control, and manage IoT devices remotely, all from a single interface.

This single interface includes advanced analysis through specialized algorithms and data processing tools designed for various applications, such as bridges, railways, geotechnics, and more.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://move-solutions.gitbook.io/untitled/references/mymove-concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.