Often a central component of an IoT project, the gateway acts both as the guarantor and the interpreter of data exchanges between connected devices and the cloud platform. This is a crucial role that may justify the development of a
Often a central component of an IoT project, the gateway acts both as the guarantor and the interpreter of data exchanges between connected devices and the cloud platform. This is a crucial role that may justify the development of a
Often a central component of an IoT project, the gateway acts both as the guarantor and the interpreter of data exchanges between connected devices and the cloud platform. This is a crucial role that may justify the development of a bespoke solution.
Setting up an IoT project essentially involves creating a network of devices that collect information, such as sensors, and, on the other hand, an IT system responsible for aggregating the data to facilitate its analysis and enable value to be extracted from it. The gateway, or IoT gateway, is the component responsible for connecting these two elements when the devices do not have internet access.
In terms of hardware, it is generally composed of various interfaces (radio and/or fieldbus interfaces) enabling it to communicate with the devices and the cloud platform. For example, using radio protocols such as Zigbee, Bluetooth or Z-Wave to communicate with devices scattered across the field, then utilising a ‘standard broadband’ Internet connection (Ethernet, GSM) to route the collected data to the company’s information system or cloud.
Alongside this physical layer, the gateway can operate at the software level to secure access, verify the integrity of communications, monitor devices and prepare data so that it can be more easily interpreted by the platform.
For example, it can encrypt information before sending it over a public network, convert data from one IT protocol to another, perform local processing, etc.
The first instinct is usually to look at the various off-the-shelf solutions offered by the big names in the IoT. Designed for common requirements, these off-the-shelf gateways require only minimal configuration, which in theory speeds up and simplifies project implementation. However, this generic nature can sometimes limit customisation options.
Aware of this shortcoming, some manufacturers offer programming interfaces that allow an application layer to be added on top of a generic gateway. This makes it possible to add specific features to the existing functionality, but only within the scope of the uses intended by the manufacturer.
The user therefore remains dependent on the technological choices made by their supplier, particularly regarding functional developments or security updates.
A bespoke approach removes all these obstacles, as it takes the user’s stated requirements as its starting point. The specifications therefore incorporate all the business functions specific to the project.
The company also has a complete overview of the flow of information and any transformations applied to it. It can thus ensure that its strategic data does not pass through a public cloud or an intermediary that does not comply with its security policy or any regulatory compliance requirements.
Designing a bespoke solution ultimately ensures full and complete ownership of your IoT gateway. Companies that opt for a customised gateway, such as the one offered by Rtone, have, for example, full access to the source code of their device, which allows for in-house development or the reuse of certain application components within other projects.
Once the gateway has been delivered, Rtone then acts as a service provider capable of carrying out maintenance tasks, but the company is free to choose how it wishes to oversee the security of its system or develop it over time. It thus protects itself from the constraints of technical or commercial lock-in.
Off-the-shelf solutions are generally more attractively priced than bespoke solutions, but beware of the ‘window-dressing’ effect: cost analysis must take into account the entire lifecycle of the gateway. Developing and integrating an application layer dedicated to specific business needs at a later stage represents a significant effort, ultimately resulting in a hybrid solution whose lack of flexibility will hinder future developments.
Conversely, a bespoke gateway involves a higher upfront cost, but it constitutes an asset for the company that can be adapted or reused as needs evolve. It also represents an element of intellectual property that can be monetised either directly or through new projects. Finally, it allows the company to capitalise on developments already undertaken.
Ultimately, developing a bespoke gateway is not necessarily more expensive than a generic solution, whilst offering significantly greater assurance in terms of scalability, reliability and security across the entire IoT chain.
As always, therefore, it is the exact purpose of the project, its strategic imperatives and the expected return on investment that should guide the decision-making process. Are you looking to design an IoT solution for industry?
Contact UsUn peu de lecture
Des articles, des podcasts, des webinars… et surtout des conseils pratiques ! En bref, une collection de ressources pour mener à bien votre projet.
