Skip to content

Latest commit

 

History

History
100 lines (59 loc) · 5.22 KB

README.md

File metadata and controls

100 lines (59 loc) · 5.22 KB

Peter Moss MedTech Research Project

HIAS MQTT IoT Agent

HIAS MQTT IoT Agent

CURRENT RELEASE UPCOMING RELEASE Contributions Welcome! Issues

PEP8 Documentation Status CII Best Practices

LICENSE

 

Table Of Contents

 

Introduction

A HIAS IoT Agent is a bridge between HIAS network devices and applications, and the HIASCDI Contextual Data Interface. The HIAS MQTT IoT Agent communicates with HIAS devices and applications using the MQTT machine to machine communication protocol.

 

MQTT

The Message Queuing Telemetry Transport (MQTT) is a lightweight machine to machine communication protocol designed to provide communication between low resource devices.

The protocol is publish-subscribe (Pub/Sub) communication protocol that runs over the Internet Protocol Suite (TCP/IP).

 

HIAS

HIAS - Hospital Intelligent Automation Server

HIAS - Hospital Intelligent Automation Server is an open-source server for hospitals and medical centers, designed to control and manage a network of intelligent IoT connected devices and applications.

HIAS IoT Agents

The HIAS iotJumpWay IoT Agents are based on FIWARE IoT Agents and are a selection of protocol/transfer specific applications that act as a bridge between the HIASCDI Contextual Data Interface & the HIASHDI Historical Data Interface and the devices and applications connected to the HIAS network via the iotJumpWay. Supported protocols currently include HTTP, MQTT, Websockets, AMQP and Bluetooth/Bluetooth Low Energy (BLE).

Each IoT Agent provides a North & South Port interface that allows communication to and from the Context Broker.

SOUTHBOUND TRAFFIC (COMMANDS)

Source: FIWARE IoT Agents

The North Port interface of an IoT Agent listens to southbound traffic coming from the Context Broker towards the devices and applications.

NORTHBOUND TRAFFIC (MEASUREMENTS)

Source: FIWARE IoT Agents

The IoT Agent sends southbound traffic to devices and applications using a protocol that is supported by the device/application, and receives northbound traffic from the devices/applications which it then forwards to the Context Broker.

 

GETTING STARTED

To get started follow the following guides:

 

Contributing

Peter Moss Leukaemia MedTech Research CIC encourages and welcomes code contributions, bug fixes and enhancements from the Github community.

Please read the IOT AGENT CONTRIBUTING guide for a full guide to contributing to our IoT Agent projects. You will also find our code of conduct in the CODE OF CONDUCT document.

Contributors

 

Versioning

We use SemVer for versioning.

 

License

This project is licensed under the MIT License - see the LICENSE file for details.

 

Bugs/Issues

We use the repo issues to track bugs and general requests related to using this project. See IOT AGENT CONTRIBUTING guide for more info on how to submit bugs, feature requests and proposals.