MULTI-BIOMETRIC IoT BRIDGE

Abstract

A method is provided for the capture of biometric or multi-biometric information using: a standard Internet of Things (IoT) data broker in an efficient and distributed IoT architecture. The MQTT information protocol is used in combination with mobile or fixed devices that manage one or more peripherals for capturing biometric information. An IoT platform is provided that allows information to be viewed in real time along with historical information and statistics regarding the use and operation of the devices to be obtained. The invention provides a method based on standard integration protocols and tools for M2M communication in IoT architectures, which acts as an information bridge, facilitating implementation to capture any type of biometric or multibiometric information, which information can be in any format (biometric templates or images in standard or proprietary formats), so that the captured information can be used in any type of biometric process.

Claims

1. A procedure for capturing biometric information, characterized in that it comprises the steps of: implementing an MQTT communication protocol on a device (integrated hardware, application, service or software component) that manages one or multiple biometric information capture peripherals, enabling an M2M (Machine To Machine) communication model in a IoT architecture between the device and an integrating client, such as API, software application, web service, integrated device, to capture one or multiple biometric factors; and applying an MQTT messaging broker for the publication and subscription of asynchronous messages.

2. The procedure of claim 1, which further comprises implementing dynamic, secure and manageable messaging routes based on MQTT messages topics, which allow the biometric information capture device that implements it to act autonomously and independently and decide the information it wants to receive or publish through its internal operation logic without depending on a specific central system that manages or controls it, allowing the reception of asynchronous messages corresponding only to the client to which it is assigned in an information system, administrable access token to its messaging routes and additional combination of access or security parameters applicable to the messaging route filters for the operations that the device is designed to execute, publishing asynchronous events based on MQTT messages with the captured biometric information as a response.

3. The procedure of claim 1, wherein the device captures biometric or multi-biometric information (one or multiple biometric factors), which corresponds to images and/or templates of the captured biometric factors and are in any standard or proprietary format.

4. The procedure of claim 1, wherein said method makes use of the connection in a local or remote network to an MQTT messaging broker for asynchronous messages publication and subscription, receiving asynchronous messages with the biometric information captured by the devices as a response.

5. The procedure of claim 1, wherein said procedure requires the following parameters to implement the request for capturing biometric information sent to the devices, which are part of the necessary specification for establishing the connection to the broker, the configuration of the peripherals managed by the device and the messages and filters of the specific messaging routes for implementation based on the MQTT protocol: Unique identifier of the client to which the devices are associated in an information system; Access token to the messaging path of the device (or devices); Information security and connection parameters to the MQTT messaging broker; Biometric information capture peripheral's configuration parameters; Command(s) to execute for capturing information on one or multiple biometric factors

6. The procedure of claim 5, wherein dynamic, secure and administrable messaging routes are implemented based on topics of MQTT messages to which the integrator client subscribes and publishes that allow filtering, in an autonomous and independent way, the reception of asynchronous messages corresponding only to the client to which the biometric capture devices are associated in an information system, administrable access tokens to device messaging routes and other access and security filters that apply to the messaging routes for the operations for which the devices are designed to execute, receiving asynchronous messages with the captured biometric information.

7. The procedure of claim 1 or 5, wherein the integrator client that implements it captures biometric or multi-biometric information, which corresponds to images and/or templates of the captured biometric factors, and is in any standard or proprietary format.

8. The procedure of claim 1 or 5, wherein the integrator client that implements it enables the capture of biometric or multi-biometric information remotely or in the local network, making use of the connection to an MQTT messaging broker, which can be of public or private access, that distributes asynchronous messages to device messaging routes.

9. The procedure of claim 1 or 5, wherein said procedure allows capturing biometric or multi-biometric in a single transaction from one or multiple biometric information capture devices that implement the procedure, receiving asynchronous messages to messaging routes with the captured biometric information

10. The procedure of claim 5, wherein the procedure is implemented, integrated and/or exposed as an integration method in any type of application, integration library, web service, software component, integrated hardware and others.

11. The procedure of claims 1 and 5, where the implementation of any structure, type and format of the messages associated with the messaging routes to which the integrating devices and clients subscribe or publish is accepted, which are interpreted by the parties autonomously and independently without the intervention of an intermediate system that interprets, synchronizes or processes the information.

12. The procedure of claims 1 and 5, wherein the integrator device or client, connects to an MQTT messaging broker that is in a local or remote network, through any type of wired or wireless connectivity that enables access to the network.

13. A fingerprint biometric information capture device that implements the procedure of claim 1 using the MQTT communication protocol and connection to an MQTT messaging broker in a IoT architecture for M2M communication with other devices and/or applications enabling capturing biometric information by publishing and subscribing asynchronous messages to messaging routes.

14. The fingerprint biometric information capture device of claim 13, wherein the device captures templates and/or images of the fingerprint that can be found in any standard or proprietary format.

15. The fingerprint biometric information capture device of claim 13, which obtains connectivity to the data network to connect to an MQTT messaging broker through an external hardware device that exposes a WiFi wireless access point.

16. The fingerprint biometric information capture device of claim 13, further comprising an internal battery to enable its mobile operation.

17. The fingerprint biometric information capture device of claim 13, wherein said device implements the specification of messaging routes based on MQTT topics to decide to subscribe or publish, asynchronously, messages that correspond to it, according to information programmed in its internal logic, of the client's identifier to which it is assigned in an information system, manageable access token to its messaging routes, additional access or security filters and commands that it can execute, behaving autonomously and independently and deciding on the information and format of the data that it wants to receive or publish without depending on a specific system that controls it centrally.

18. The biometric mobile fingerprint capture device of claim 13, which comprises sensors and publishes MQTT messages reporting the status of its sensors, alerts and internal parameters to be viewed and/or stored in real time in an information system, where said sensors correspond to battery level, tamper sensor status, charge status and other sensors information measurable or subject to be reported in its internal operation.

19. The fingerprint biometric information capture device of claim 13, wherein said device publishes MQTT messages notifying its connection status, for an automatic notification to any client or information system that can receive the notification through messaging routes.

20. The fingerprint biometric information capture device of claim 13, wherein the device establishes the connection with an MQTT messaging broker through various authentication and security methods, implemented individually or jointly, such as encryption of communication channel through standards such as SSL/TLS, User/password and digital certificates for authentication (server and/or client).

Description

BRIEF DESCRIPTION OF THE FIGURES

[0047] FIG. 1. General operation diagram of the MQTT protocol using the asynchronous message publication and subscription pattern for M2M communication in IoT architectures

[0048] FIG. 2. General architecture of the IoT platform

[0049] FIG. 3. General flow diagram of the disclosed procedure for capturing biometric information

[0050] FIG. 4. General architecture of integration of a multi-biometric device with a IoT data broker for MQTT messaging, the IoT platform and integration applications.

DETAILED DESCRIPTION OF THE INVENTION

[0051] The invention discloses a procedure that describes a specification for capturing biometric or multi-biometric information (one or multiple biometric factors. E.g.: fingerprint, iris, veins, face, etc.), making use of a standard IoT data broker in an efficient and distributed IoT architecture implementing the MQTT information protocol and applicable to mobile or fixed devices that manage one or multiple biometric information capture peripherals; a mobile electronic device for capturing biometric information that implements the described procedure and a IoT platform that allows viewing information in real time and obtaining historical information and statistics on the use and operation of the devices.

[0052] In more detail, the procedure described makes use of a IoT broker that allows the distribution of asynchronous messages based on the MQTT protocol in a publication and subscription model totally agnostic to the content or format of the messages that is implemented between the parties, allowing the creation of autonomous mobile or fixed devices for capturing biometric information with any type of connectivity to data networks and integration applications based on asynchronous processing by events that allow M2M (Machine to Machine) interaction between client and device in a IoT architecture, eliminating the restrictions of traditional client/server models and taking advantage of the characteristics of message distribution, decoupling and independence between the parties, reliability, scalability and security provided by IoT brokers and the MQTT protocol.

[0053] In a higher level of detail, the invention discloses a biometric mobile fingerprint capture device called BioVerif IoT WiFi with WiFi wireless connection technology that implements the procedure disclosed in the invention based on the MQTT standard, acting as an autonomous and fully self-managed device for capturing biometric information asynchronously based on events. The invention also discloses a IoT platform that allows to dynamically view in real time, information published through MQTT messages by the devices, store and analyze the information with Big Data tools.

[0054] The invention, therefore, making use of the disclosed procedure, provides a method based on standard integration tools and protocols for M2M communication in IoT architectures, which acts as an information bridge, facilitating the implementation to capture any type of biometric information. or multi-biometric, which can be found in any format (images or biometric templates in standard or proprietary formats) in order for the information captured to be used in any type of biometric process that requires it.

[0055] Procedure for Capturing Biometric Information Using the MQTT Protocol and an MQTT Messaging IoT Broker

[0056] The procedure revealed in this invention implements the MQTT communication protocol, which is a widely used standard for IoT systems, allowing the creation of an M2M (Machine To Machine) communication model in IoT architectures between an integrator client that requires the capture of information of one or multiple biometric factors of any type and devices that manage one or multiple biometric information capture peripherals. This communication scheme uses a standard MQTT messaging IoT broker, which serves as a dispatcher of asynchronous messages through publish and subscribe events using messaging routes based on MQTT topics, implementing a distributed IoT architecture which grants total independence and decoupling of applications and devices between them and with the central system, as well as high scalability of the solution, taking into consideration that the MQTT messaging brokers are agnostic to the format or content of the information they distribute and their operation is based in asynchronous message publishing and subscription to topics, takes away responsibility for common tasks in traditional client/server systems, such as control of connected devices, information synchronization, data processing, management of proprietary protocols, etc.

[0057] The procedure is based on devices that are registered and linked to unique customers who are defined as the owners of the devices and who have a unique customer identifier that is assigned in an information system, which serves as the first filter of the MQTT topic that initially achieves a self-managed device regarding the information that it wishes to receive from a specific client, since this client identifier is part of the device's messaging routes and will not receive any data from a client that does not correspond to it, since it autonomously decides not to receive them through this initial filter applied to the topic.

[0058] The second filter parameter of the topic will be an access token to the messaging route that in the system is a code (represented in text) of manageable access that is related to the client of the first filter and the device or several devices, in addition to not being a visible parameter that is easily accessible on the devices, providing additional security in the information filter and it is also a dynamic token that can be modified if the security of the devices is compromised in such a way that it prevents the messaging path from functioning as it does not correspond to the complete information filter (topic). Thus, the device will not receive any messaging event that does not fully correspond to its messaging routes which are dynamic and manageable.

[0059] The topic can also be filtered by parameters such as the type of device, version and other parameters that may be relevant, additionally other filters are specified for the topic, which correspond to the commands or events published, for example: CapturaHuella, Capturaris, CapturaFoto, CapturaFotoFoto etc. Along with the additional specification of filters in the topics that you want to add to the device's messaging route (E.g.: . . ./ID_Tipo_Device/Version/ID_Cliente/Token_Acceso/MAC/Command/. . . ).

[0060] This, thanks to the MQTT specification, allows a device not to process invalid or unnecessary information and not receive information that does not correspond to it or does not want to receive, since it decides it autonomously through its logic of filtered topics or messaging routes, ensuring that you only receive the message through an asynchronous event that is explicitly published with all the filters applied by a client and that is also complemented by the access rules that are defined in the IoT broker as additional security to avoid unauthorized publications or subscriptions.

[0061] FIG. 3 shows the exposed procedure of M2M communication in a IoT architecture through asynchronous events of MQTT messages, making use of secure, dynamic and manageable messaging routes based on MQTT topics with a free specification of the format of the messages associated with the topics (JSON, XML, Binary, etc.), where the following procedures are followed, for which a Device may be any integrated hardware or software application that implements the procedure to enable the capture of one or multiple biometric factors through the management of one or multiple capture peripherals, as well as an Integrator Client could be any software component or Information system that directly implements or exposes a method of integration of the procedure (E.g.: Applicative, web service, Integration component, etc). [0062] 1Procedure executed on the device: [0063] a. The device begins its operation and establishes a connection to a MQTT messaging IoT data broker by means of an encrypted communications channel using, in a preferred embodiment, the SSL/TLS standard and access credentials for authentication, which may correspond to username/password and/or X509 digital certificates that identify it. With the connection established, the device publishes its connection status specifying that it is online. [0064] b. Next, the device makes the subscription with the IoT messaging broker to the topics or messaging routes that it wishes to listen to, taking into account that the device is self-managed and therefore does not depend on any intermediate system that tells it how to act or What information to listen to, it decides the information that he is interested in receiving, everything resides in its internal logic and he will not receive events from MQTT messages to which he has not subscribed (E.g. . . . /ID_Tipo_DepositivoNersion/ID_Cliente/Token_Acceso/CapturarHuella), which are also filtered as specified above and can correspond to any biometric capture command that the device is programmed to execute, which can manage one or multiple biometric devices (E.g.: fingerprint capture module, iris reader, vein reader, photographic camera, etc.) and therefore capture one or multiple simultaneous biometric factors. The command can correspond to any operation, for example: Captura huella, Captura Iris, Captura huella y foto, etc., where the Payload or data associated with the event of the MQTT response message of a device can be found in any format and contains the information of the operation executed by the device including the encrypted biometric information that is captured. [0065] c. Each publication to a messaging route is associated with the message or Payload that is specified and that corresponds to the configuration parameters required by each operation and its associated peripherals, said message can also be found in any format (binary, JSON, XML, etc) since the broker is agnostic to the information exchanged in the M2M communication of the devices and applications. Therefore, this exposed method proposes that in the command received by the device to execute an operation, the integrator client sends the specific configuration that may be necessary for the biometric capture peripherals that the device manages (E.g.: Minimum capture quality, resolution, etc.) and can be exchanged if the security information is required (E.g.: encryption key if a symmetrical encryption is implemented) to be applied to the captured information, taking into account that the initial connection to the IoT broker has been established by means of standard SSL/TLS security which encrypts the channel for transporting the sensitive information.

[0066] Additionally, this procedure proposes the exchange of a dynamic synchronization key contained in the request command to capture biometric information, which allows a mathematical calculation to be carried out using any method known to both the publisher of the message (who sends the message for execution of the command), as well as by the device that will publish the captured biometric information, so that the result of this mathematical calculation is added by the parties to the topics as a publication security filter (by the device or devices that receive the command) and subscription (by the one who published the command or customers interested in hearing the information), in such a way that messages are always exchanged to a random messaging route with an additional assurance that only the parties involved that know said calculation will receive the message (E.g.: . . ./ID_Tipo_Dispositivo/Versin/ID_Cliente/Token_Acceso/Filtro_Seguridad/CapturaFoto), taking into account that the parties are totally autonomous, do not know each other, process messages based on asynchronous events and that the IoT broker will distribute the MQTT message asynchronously to one or many clients that are subscribed to the specific messaging route.

[0067] Taking into account the foregoing, when the device asynchronously receives a message to execute a command, it is proposed in this procedure that the device perform the known mathematical calculation, specified above. The result of this calculation is applied as Security filter additional to the topic to which the device must publish to notify the receipt of a command to whoever is subscribed to receive said message and knows the messaging route with the calculated security filter. Therefore, the device publishes the message to the corresponding command confirmation messaging route, which is a specific, filtered and secure route, announcing to who can listen to the message of that messaging route that the message has been received and the biometric information capture operation will be executed. [0068] d. The device (or devices) then captures the biometric information of one or multiple peripherals that it is in charge of managing, applying the configuration received in the request message that the peripherals require to capture information and must then publish the captured biometric information. to the MQTT messaging path (or paths) that correspond to the command (or commands) response and that in addition to the filters such as client identifier, access token, command and others that are defined, it is filtered by the security filter calculated and added to the publication topic, ensuring that the information will be received by the interested and authorized parties that are subscribed to the response messaging routes. The response with captured multi-biometric information (multiple biometric factors captured from different peripherals), can be published in a single message or in individual asynchronous messages of free specification that are interpreted by the client that requested the capture. Once the response message (or messages) is published, the device ends its processing, since this being completely autonomous and independent, it only publishes its message without further validation than the knowledge of the messaging route to which to publish, since being a model based on a IoT architecture that deviates from the traditional client/server architecture, the device is not managed by any central system, so it only takes care of carrying out its task and publishing the message, plus the other party must also be self-managed and have been in charge of subscribing to the corresponding secure messaging route to receive a response and know how to process the message associated with the asynchronous event that it can receive from a device in an M2M communication. [0069] 2Procedure executed in the Integrator Client from where the request to capture information of one or multiple biometric parameters is made: [0070] a. The parameters required to execute the operation must be known, so the parameters required for the information capture process must at least be: [0071] unique identifier of the client to which the device (or devices) is associated in an information system. [0072] Access token to the messaging route of the device or devices. [0073] Information and connection security parameters to the IoT data broker. [0074] Biometric information capture peripherals configuration parameters. [0075] Command(s) to execute to capture information of one or multiple biometric factors (Ex: Fingerprint, Iris, Face, Veins, etc.) [0076] b. The MQTT connection to the IoT broker is established with the corresponding access keys (User/Password, X509 certificate, etc.) and through a session with an encrypted channel using in a preferred embodiment an SSL/TLS standard. [0077] c. Subscription is made to the MQTT topic that allows knowing if there are active and online devices for requesting biometric information, by receiving the corresponding asynchronous event with the MQTT message of the connection status. [0078] d. Subscription is made to the topic of confirmation of receipt of the command by the device, which will allow receiving confirmation events when a capture command is sent and ensures that there is at least one device that belongs to the client, its messaging route is enabled using the access token, it listens to the messaging route with all the specific filters, it will execute the action and that the device has correctly calculated the security filter to add to the topic and make it unique and dynamic, providing additional security. Therefore, being subscribed to the command confirmation topic, the client must mathematically calculate the security filter with the synchronization key that is exchanged in the capture request message and using the desired calculation method, which must also be known by the device or devices, allowing the parties to apply the correct filter to the subscription and publication topics, this taking into consideration that it is using an autonomous communication model, wherein the devices or client/device that want to interact between themselves must decide the information they are interested in receiving and knowing how to talk between them according to the IoT architecture model, without depending on a central system managing the control process of the devices, processing and synchronizing the information. [0079] e. Subscription is carried out to the command execution MQTT topic by the device (where it is expected to receive asynchronous messages of response to the operation once a request command is sent), which is filtered by the parameters already specified, including the security filter already calculated in the answer topic. The executed command can correspond to any biometric or multi-biometric capture operation, for example: Capturar Huella, Capturar Irs, Capturar huella y foto, etc., associated with a messaging route (Ex: . . . /ID_Tipo_Dispositivo/Versin/ID_Cliente/Token_Acceso/Filtro_Seguridad/Capturalris), where the Payload or message associated to the event of the MQTT response message from a device can be found in any format and contain information of the operation executed by the device including biometric information being captured. [0080] f. Publishing of the message is made to the topic of the specific command that it wants to execute (Eg: . . . /ID_Tipo_DispositivoNersin/ID_Cliente/Token_Acceso/CapturaHuella), filtering the MQTT topic by means of all the parameters already specified that enable the messaging route and that one or more devices can access if they have subscribed to it in an autonomous way. In the published message, the specific configuration of the biometric capture peripherals that the device (or devices) manages is sent, as well as security information if required (e.g.: encryption key if symmetric encryption is implemented) to apply to the information captured, taking into account that the initial connection to the IoT broker has been established using the SSL/TLS security standard that encrypts the channel for transporting sensitive information. Additionally, the synchronization key is sent that enables carrying out a mathematical calculation known by the parties to apply to the topic filter of the command confirmation and response to the operation messaging route, in such a way that there is always a response with the biometric information to random messaging routes with an additional security that only the involved parties that know said calculation will receive the message, taking into account that the parties are totally autonomous, process the messages based on asynchronous events and that the IoT broker will distribute the message to one or many clients that are subscribed to a specific messaging route as long as the subscribers have permission for it. [0081] g. With the client already subscribed to the messaging route (topic) of confirmation of receipt of a command (step d), the reception of the asynchronous MQTT message of confirmation of receipt of the message by a device (or devices) is expected letting it know that there are devices that received the command. This operation, by being completely asynchronous and independently executed by the device, must propose the option of a maximum waiting time to receive confirmation of receipt of the command by the devices. [0082] h. With the client already subscribed to the response message path (topic) (step e), it is expected to receive at least one MQTT asynchronous message with the biometric information captured by the device that would contain the data (E.g.: fingerprint template, fingerprint image, Iris image, photograph, etc.). This operation, being completely asynchronous and independently executed by the device, must propose the option of a maximum waiting time to receive the response data of the information capture and if multiple biometric factors are captured, these can even be published as a response by the device or devices asynchronously and individually until the process is complete, taking into account that there is no traditional client/server architecture that synchronizes the parts, but an asynchronous and self-managed M2M communication model by each part of the IoT architecture, such that by the device executing the action it simply publishes messages asynchronously without knowing how the receivers will interpreted them that must know how to manipulate and process the information in their communication model with the devices.

[0083] The MQTT specification requires that the topic or messaging route to which information is published, be explicitly specified, otherwise, the device may not receive any event with a message that is published by another party, since the devices decide in their internal logic explicitly which events they want to receive and the IoT messaging broker is completely agnostic to the format or content of the messages sent between devices, so it is not its function to control the devices, process the information contained in the messages or synchronize the information between the parties as in traditional client/server architectures. This allows applications and devices to be decoupled and to implement the capture of any type of biometric information and any functionality, taking care only of the parties that want to communicate, without affecting a central system and, therefore, the whole integral system.

[0084] This procedure opens up infinite possibilities to create solutions that implement the capture of one or multiple biometric characteristics, through the client/device or device/device M2M communication with standard tools of the IoT industry, designed to allow the plurality of any type of device in the same information system and eliminate dependence on proprietary central systems, the limitations in synchronized information management, the complexity in modifying or implementing new functionalities and the difficulty in scaling the solutions, among other security limitations and information distribution of the traditional client/server systems.

[0085] Additionally, this procedure being based on asynchronous messaging routes, would allow that if multiple clients share the messaging routes, a response to capture biometric information can be received instantly by more than one biometric process that requires it (E.g.: Inspection visualization and processing in an automated system) in a single publication of information captured by a device, since the job of the IoT broker is to distribute an asynchronous message to one or many clients that, after validating the access security rules, have subscribed to specific messaging routes.

[0086] The present invention discloses a mobile fingerprint capture device developed using this procedure, plus the possibilities of applications using the same specification remain open to the integration of additional biometric capture peripherals in devices that behave as IoT gateways that incorporate the required functionalities and allow in an efficient and scalable way, through the use of standard and easily accessible tools and protocols in the IoT industry, to integrate the capture of biometric or multi-biometric information of any type and its eventual integration with biometric systems that require it.

[0087] BioVerif IoT WIFI Mobile Biometric Device (1)

[0088] The present invention discloses a mobile biometric fingerprint capture device (1) fully developed by us, named BioVerif IoT WiFi, which has been designed to operate under a IoT scheme, implementing the MQTT communication protocol as the basis for its autonomous and self-managed operation (subscription and publication of messages) and that implements the operation procedure disclosed above which can be evidenced in the flow diagram of FIG. 3 by connecting to an MQTT messaging IoT broker.

[0089] The device incorporates a biometric fingerprint capture module with optical technology that ensures the highest quality in capturing biometric information and that additionally has the following characteristics: [0090] Optical Technology Reader [0091] Live fingerprint and false fingerprint detection [0092] Generation of fingerprint images in biometric standards [0093] Fingerprint template generation in biometric standards [0094] Encryption of biometric templates and fingerprint images

[0095] In addition, the device has the following functionalities: [0096] Touch technology power button [0097] Built-in WiFi communication module [0098] Built-in WiFi Host mode [0099] Rechargeable battery [0100] Connection using SSL/TLS channel security standard and implementing mixed authentication methods such as digital certificates and/or username/password [0101] Hardware intrusion detection (Tamper Detection) that disables the device against unauthorized physical opening (FIPS 140-2 level 3 compliance) [0102] Filtering of WiFi access point authorized for connection through the physical MAC address of the access point. [0103] Status report of sensors, alerts and internal parameters through standard MQTT messages. This allows integrating the functionality of visualizing in real time information on battery status, charge level, tamper sensor status, low battery level alert, etc. [0104] Automatic report of connection status through standard MQTT messages.

[0105] The device, by implementing the disclosed procedure, acts as a IoT Gateway with the particularity of managing a module for capturing biometric fingerprint information, it is completely autonomous and self-managed, since by subscribing to MQTT topics that act as routes for specific messaging, allows filtering the information it wants to receive or publish, ensuring that the message corresponds to it according to its messaging route and even the client to which it belongs, since both the client's identifier and all the filters applied to the messaging route are found in its internal configuration and are processed internally, therefore without requiring control or validation from a centralized system. All this allows the device to be decoupled from the central system in terms of its operation, information protocol or interaction with other costumers or devices, without further requiring an additional software intermediary application managing the device or the information it generates since everything resides in its internal logic and only requires connectivity to the data network, achieving a scheme one hundred percent oriented towards and IoT architecture without being affected by a specific central system, according to the theory of IoT system that allow a plurality of devices and models to communicate in the same platform, where the IoT broker does not have how to control de devices, process the information contained in the messages or synchronize the information between the parties as in traditional client/server architectures.

[0106] The device behaves as a IoT Gateway, so the invention allows the integration of the MQTT messages published by the device with the IoT platform revealed in this invention (FIG. 4), this allows to have a comprehensive system, by which, through an interactive platform, it is possible to manage in real time the operating status of the devices, record information from sensors and meters, generate information statistics, define access rules and other functionalities that the IoT platform has.

[0107] IoT Platform

[0108] The present invention made possible the integration of the disclosed mobile biometric device with a comprehensive IoT platform, fully developed by us, which connects to a standard IoT messaging broker MQTT and it allows the connection of any type of device or IoT Gateway that allows the collection of signals from sensors and management of actuators in the field, which behave as completely autonomous and self-managed devices, since they publish and subscribe to topics that act as messaging routes to exchange information dynamically and in real time with other devices, integration applications and with the management web portal of the IoT platform through the IoT MQTT messaging protocol, as can be seen in FIG. 2. To this platform, thanks to being designed under a IoT architecture with standard tools, multiple devices have been integrated for multiple use cases (energy management, cold chain management, machine monitoring, etc.) and, in the case of the mobile biometric device disclosed in this invention, by acting as a IoT Gateway that connects to the IoT broker, it reports the connection status, status of its sensors and internal counters through standard MQTT messages allowing be monitored on the IoT platform like any other device that implements MQTT messaging and obtain relevant information in real time on its operation, connection status and internal sensors, as well as store, visualize and export historical and statistical information through big data tools.

[0109] The IoT platform creates an environment that allows it to be multi-client, multi-device, with independent management characteristics of the real-time information of the devices and providing a graphical environment to the user for viewing information in real time, consulting historical data and data processing to generate statistics and trends on millions of stored data using tools employed in IoT systems for the analysis of unstructured data and big data.

[0110] The functionalities and characteristics of the platform disclosed in this invention include and are not limited to: [0111] View and audit the connection and operation status of each device, broken down by customer, grouping devices and interactively in real time [0112] Visualize and audit the information of the sensors and actuators reported by the devices interactively and in real time. These signals can be associated with different types of sensors, such as battery levels, electrical measurements, temperatures, activation relays and any relevant data either obtained from external sensors or from internal sensors of the IoT Gateway. [0113] View interactive dashboards with relevant information about the devices (Sensor measurements, device messages, connection status, etc.). Dashboards listen to information in real time through the MQTT protocol and have graphic information components that can be dynamically incorporated by the user, which not only show instant information on sensor measurements or connection states, but also allow the incorporation, in a dynamic and interactive way, of information with visual graphic statistics (trends, comparisons, mathematical calculations, etc.) and exportable in different formats. [0114] Interact remotely and bi-directionally with devices. [0115] View operation logs, generate statistical reports and consult historical activity information and measurement data of sensors and actuators reported by the devices. [0116] Manage credentials and access rules of system devices and users. [0117] Manage the creation, edition and elimination of clients, devices, groups, users, alerts, notifications and other implicit functionalities of the platform. [0118] Register information on signals, alerts, messages and other information received in real time by the devices on the platform. [0119] Dispatch alerts and notifications (emails, chats, webhooks, etc.) received in real time by the devices. [0120] Visualize and monitor the operation and alerts of the devices through georeferencing in interactive maps and in real time

REFERENCES

[0121] 1. https://aws.amazon.comes/pub-sub-messaaing/Amazon Web Services. April 2018 [0122] 2. https://aws.amazon.com/es/pub-sub-messaging/benefits/Amazon Web Services. April 2018 [0123] 3. http://docs.oasis-open.org/mqttUmqttv3.1.1/mgtt-v3.1.1.html OASIS. April 2018 [0124] 4. https://www.oasis-open.org/committees/mqtt/charter.php OASIS. April 2018 [0125] 5. http://mgtt.ora/MQTT. April 2018 [0126] 6. https://www.lbm.com/deveioperworks/nbrary/IQt-mqtt-whv-qood-for--IoT/IQt-mgtt-why-good-for-iot-odf.pdf (pdf). IBM. April 2018 [0127] 7. https-/aws.amazon.com/es/bioqs/aws/aws-iot-doud-services-for-connected-devices/. Amazon Web Services. April 2018

Glossary of Terms and Definitions Used in this Document

[0128] Biometrics

[0129] Techniques that seek to analyze and measure the physical or behavioral traits of an individual in order to detect and compare characteristic points to unequivocally verify their identity. Some examples are fingerprints, retina, ins, facial patterns, veins, hand geometry, voice, or even behavior such as signature, step or click.

[0130] Biometric Template

[0131] It is constituted by the significant data extracted from a biometric factor captured from a sensor. From this small data set, storage and verification is facilitated.

[0132] Message Publication and Subscription Model

[0133] The publishing and subscription based messaging model is a form of asynchronous service-to-service communication used in modern IoT architectures and those based on microservices. This model allows the construction of completely independent and distributed processing blocks that are based on asynchronous events of publication and subscription of one-to-many messages, allowing simultaneous processing in distributed services, optimizing performance, reliability and scalability. In this communication model, publishers and subscribers are decoupled, without knowledge of the other's existence, and they work completely independently of each other, allowing independent scaling without restrictions on the other party or in an intermediate system. Subscribers express their interest in certain topics and publishers publish messages to topics, then the message is delivered to all the subscribers to the topics.

[0134] Topic

[0135] A messaging broker in a publishing and subscription model uses topics that function as specific messaging routes of the messages published to the subscribers of the topics. Topics are defined as a hierarchy that filters the information of interest, allowing a subscriber to only listen to the information that interests him without depending on the other party or an intermediate system and avoids erroneous distribution or unnecessary information processing. The symbol / is used as a separator of the filters in the topic hierarchy and it is possible to use wildcards (Wildcards) to define broader information filters. Some examples of topics which would have associated messages: Casa/Temperatura/Cuartol/Reporte, Dispositivo1/Sensores/Humedad/Reporte, Dispositivo/Comandos/Activacin Actuadores/Actuador1.

[0136] MQTT

[0137] MQTT (MQ Telemetry Transport or Message Queuing Telemetry Transport) is a standard protocol (ISO/IEC PRF 20922) based on the pattern of publishing and subscripting asynchronous messages that provides one-to-many message distribution and application decoupling, which is widely used in M2M applications and solutions based on IoT architectures due to its open, simple, lightweight, and easy-to-deploy design. It is renowned for its low bandwidth requirements and low resource consumption, which makes it ideal for working on wireless and bandwidth-constrained networks, as well as implement the publication and subscription model, it provides one-to-many message distribution based on messaging topics without limiting the format or content of the associated messages, making it an ideal protocol for the IoT (Internet of Things) favoring heterogeneity of any type of device in a distributed information system.

[0138] IoT (Internet of Things or Internet of Things)

[0139] Internet of things (in English, Internet of things, abbreviated IoT) is a concept that refers to the digital interconnection of everyday objects with the internet, as well as any machine or device that collects information from sensors and actuators. The internet of things refers to the interaction of these objects or machines with each other and with other information systems, therefore, IoT solutions are generally based on architectures oriented to asynchronous messages publication and subscription events that facilitate the distribution of information in real time, scalability and the incorporation of any type of device or functionality in a dynamic way.

[0140] API (Application Programming Interface)

[0141] An API or Application Programming Interface is a set of routines, functions, and procedures exposed in one software component to be used by another software component as an abstraction layer. They can be exposed as web services (SOAP, RPC, REST), libraries, classes or functions of operating systems.