FR3140970A1 - Method for deploying at least one software application, electronic device and corresponding computer program product - Google Patents

Abstract

Method for deploying applications, electronic device and corresponding computer program product The invention relates to a method for deploying a passive software application in a communications network, said method comprising: Obtaining the binary code of said passive application and a designation of the type(s) of data consumed and/or produced by said application; An at least partially automatic selection of access to data from at least one data source of said network and/or to at least a data consumer of said network, said selection taking into account said at least one designated type and at least one type of data expected via said access; Automatic creation of an active executable of which at least one software process comprises an invocation of said passive application with as input parameter(s) at least one piece of data obtained via said access and/or with as output parameter(s) at least one piece of data to be transmitted via said access. The invention also relates to the corresponding electronic device, system, computer program product and recording medium. Figure for abstract: Fig. 3

Description

Method for deploying at least one software application, electronic device and corresponding computer program product1. Technical area

This application relates to the general field of application deployment, in various sectors such as for example in the industrial, agricultural and/or medical sectors.

It relates in particular to a method for deploying software application(s) as well as an electronic device adapted to the implementation of such a method, and the corresponding computer program product and recording medium.

2. State of the art

The industry is experiencing environmental and societal challenges today more than ever (personnel safety, lack of availability of qualified personnel, competition, etc.) pushing it to automate certain operations, such as quality control, safety and security tasks. predictive maintenance, linked to production stations. To face these challenges, manufacturers often rely on multiple external suppliers, each specialized in providing automated solutions responding to a particular problem. Examples of such supplies include a computer vision fault detection application, a vibration analysis fault detection application, a passage detection application, etc. Each solution provider brings its own environment to the manufacturer: dedicated sensors, mostly wired, its own computer hardware (such as a proximity server to be installed in the industrial site concerned, or its own connections with the client's machines, in majority wired etc.)

This leads to an increase in the complexity of a manufacturer's hardware and software portfolio and to difficulties in maintaining an overall vision of this portfolio for a manufacturer.

The purpose of this application is to propose improvements to at least some of the disadvantages of the state of the art.

3. Presentation of the invention

• Une obtention du code binaire de ladite application passive et d’une désignation du ou des type(s) de données consommées et/ou produites par ladite application ;
• Une sélection au moins partiellement automatique d’au moins un accès aux données d’au moins une source de données dudit réseau et/ou vers au moins un consommateur de données dudit réseau, ladite sélection tenant compte dudit au moins un type désigné et d’au moins un type de données attendu via ledit accès;
• Une création automatique d’un exécutable actif dont au moins un processus logiciel comprend une invocation de ladite application passive avec en paramètre(s) d’entrée au moins une donnée obtenue via ledit accès et/ou avec en paramètre(s) de sortie au moins une donnée à émettre via ledit accès.

The present application aims to improve the situation using in particular a method of at least partially automatic deployment of a passive software application in a communications network, said method comprising:

• Obtaining the binary code of said passive application and a designation of the type(s) of data consumed and/or produced by said application;
• An at least partially automatic selection of at least one access to data from at least one data source of said network and/or to at least one data consumer of said network, said selection taking into account said at least one designated type and at least one type of data expected via said access;
• An automatic creation of an active executable of which at least one software process includes an invocation of said passive application with as input parameter(s) at least one piece of data obtained via said access and/or with as output parameter(s) at least one piece of data to be transmitted via said access.

In at least some embodiments, said method comprises adding said first active executable created to a library of active executables of said communication network. In at least certain embodiments, said first added executable is associated in said library with said at least one data source and/or said at least one data consumer.

In at least some embodiments, said method comprises launching said first active executable or proposing such a launch.

In at least certain embodiments, said designation is obtained by accessing a descriptive file of the data consumed and/or produced by said application.

In at least some embodiments, said access is access to a database. In at least certain embodiments, said at least one type of data via said access is obtained by scanning said network. In at least certain embodiments, said access is a channel of a data bus of said network.

In at least some embodiments, said data obtained via said channel is obtained by subscribing said software process to said data channel to receive data from said at least one data source.

In at least some embodiments, said software process comprises a transmission of said data of said data to be transmitted on said channel. In at least some embodiments, said data channels are channels of an MQTT data bus

The characteristics, presented separately in this application in connection with certain embodiments of the process of the present application, can be combined with each other according to other embodiments of this process. According to another aspect, the present application also relates to an electronic device adapted to implement the method of the present application in any of its embodiments.

• Une obtention du code binaire de ladite application passive et d’une désignation du ou des type(s) de données consommées et/ou produites par ladite application ;
• Une sélection au moins partiellement automatique d’au moins un accès aux données d’au moins une source de données dudit réseau et/ou vers au moins un consommateur de données dudit réseau, ladite sélection tenant compte dudit au moins un type désigné et d’au moins un type de données attendu via ledit accès;
• Une création automatique d’un exécutable actif dont au moins un processus logiciel comprend une invocation de ladite application passive avec en paramètre(s) d’entrée au moins une donnée obtenue via ledit accès et/ou avec en paramètre(s) de sortie au moins une donnée à émettre via ledit accès.

For example, the present application thus concerns an electronic device comprising at least one processor configured for at least partially automatic deployment of a passive software application in a communications network, the processor being configured in particular for:

• Obtaining the binary code of said passive application and a designation of the type(s) of data consumed and/or produced by said application;
• An at least partially automatic selection of at least one access to data from at least one data source of said network and/or to at least one data consumer of said network, said selection taking into account said at least one designated type and at least one type of data expected via said access;
• An automatic creation of an active executable of which at least one software process includes an invocation of said passive application with as input parameter(s) at least one piece of data obtained via said access and/or with as output parameter(s) at least one piece of data to be transmitted via said access.

• au moins un dispositif électronique comprenant un moins un processeur configuré pour un déploiement au moins partiellement automatique d’une première application logicielle passive dans un réseau de communication, le processeur étant notamment configuré pour:
• Une obtention du code binaire de ladite application passive et d’une désignation du ou des type(s) de données consommées et/ou produites par ladite application ;
• Une sélection au moins partiellement automatique d’au moins un accès aux données d’au moins une source de données dudit réseau et/ou vers au moins un consommateur de données dudit réseau, ladite sélection tenant compte dudit au moins un type désigné et d’au moins un type de données attendu via ledit accès;
• Une création automatique d’un exécutable actif dont au moins un processus logiciel comprend une invocation de ladite application passive avec en paramètre(s) d’entrée au moins une donnée obtenue via ledit accès et/ou avec en paramètre(s) de sortie au moins une donnée à émettre via ledit accès. Au moins un dispositif source et/ou un consommateur de données dudit réseau.

The present application also relates, for example, to a system comprising:

• at least one electronic device comprising at least one processor configured for at least partially automatic deployment of a first passive software application in a communications network, the processor being configured in particular for:
• Obtaining the binary code of said passive application and a designation of the type(s) of data consumed and/or produced by said application;
• An at least partially automatic selection of at least one access to data from at least one data source of said network and/or to at least one data consumer of said network, said selection taking into account said at least one designated type and at least one type of data expected via said access;
• An automatic creation of an active executable of which at least one software process includes an invocation of said passive application with as input parameter(s) at least one piece of data obtained via said access and/or with as output parameter(s) at least one piece of data to be transmitted via said access. At least one source device and/or one data consumer of said network.

The present application also relates to a computer program comprising instructions for implementing the various embodiments of the above method, when the computer program is executed by a processor and a recording medium readable by a device electronic device on which the computer program is recorded.

• Une obtention du code binaire de ladite application passive et d’une désignation du ou des type(s) de données consommées et/ou produites par ladite application ;
• Une sélection au moins partiellement automatique d’au moins un accès aux données d’au moins une source de données dudit réseau et/ou vers au moins un consommateur de données dudit réseau, ladite sélection tenant compte dudit au moins un type désigné et d’au moins un type de données attendu via ledit accès;
• Une création automatique d’un exécutable actif dont au moins un processus logiciel comprend une invocation de ladite application passive avec en paramètre(s) d’entrée au moins une donnée obtenue via ledit accès et/ou avec en paramètre(s) de sortie au moins une donnée à émettre via ledit accès.

For example, the present application thus relates to a computer program comprising instructions for the implementation, when the program is executed by a processor of an electronic device, of a method of at least partially automatic deployment of a first passive software application in a communications network, said method comprising:

• Obtaining the binary code of said passive application and a designation of the type(s) of data consumed and/or produced by said application;
• An at least partially automatic selection of at least one access to data from at least one data source of said network and/or to at least one data consumer of said network, said selection taking into account said at least one designated type and at least one type of data expected via said access;
• An automatic creation of an active executable of which at least one software process includes an invocation of said passive application with as input parameter(s) at least one piece of data obtained via said access and/or with as output parameter(s) at least one piece of data to be transmitted via said access.

• Une obtention du code binaire de ladite application passive et d’une désignation du ou des type(s) de données consommées et/ou produites par ladite application ;
• Une sélection au moins partiellement automatique d’au moins un accès aux données d’au moins une source de données dudit réseau et/ou vers au moins un consommateur de données dudit réseau, ladite sélection tenant compte dudit au moins un type désigné et d’au moins un type de données attendu via ledit accès;
• Une création automatique d’un exécutable actif dont au moins un processus logiciel comprend une invocation de ladite application passive avec en paramètre(s) d’entrée au moins une donnée obtenue via ledit accès et/ou avec en paramètre(s) de sortie au moins une donnée à émettre via ledit accès.

Furthermore, the present application also relates to a recording medium readable by a processor of an electronic device and on which is recorded a computer program comprising instructions for the implementation, when the program is executed by the processor, of a method for at least partially automatic deployment of a first passive software application in a communications network, said method comprising:

• Obtaining the binary code of said passive application and a designation of the type(s) of data consumed and/or produced by said application;
• An at least partially automatic selection of at least one access to data from at least one data source of said network and/or to at least one data consumer of said network, said selection taking into account said at least one designated type and at least one type of data expected via said access;
• An automatic creation of an active executable of which at least one software process includes an invocation of said passive application with as input parameter(s) at least one piece of data obtained via said access and/or with as output parameter(s) at least one piece of data to be transmitted via said access.

The programs mentioned above may use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in partially compiled form, or in n any other desirable shape.

The information carriers mentioned above can be any entity or device capable of storing the program. For example, a medium may comprise a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or even a magnetic recording means.

Such a storage means can for example be a hard disk, flash memory, etc.

On the other hand, an information carrier may be a transmissible medium such as an electrical or optical signal, which may be carried via an electrical or optical cable, by radio or by other means. A program according to the invention can in particular be downloaded onto an Internet-type network.

Alternatively, an information carrier may be an integrated circuit in which a program is incorporated, the circuit being adapted to execute or to be used in the execution of any one of the embodiments of the method which is the subject of this application. patent.

In general, by obtaining an element, we mean in the present application for example a reception of this element from a communication network, an acquisition of this element (via for example user interface elements or sensors or other measurement components), a creation of this element by various means of processing such as by copying, encoding, decoding, transformation etc. and/or access to this element from a local or remote storage medium accessible to at least one device implementing, at least partially, this obtaining.

4. Brief description of the drawings

Other characteristics and advantages of the invention will appear more clearly on reading the following description of particular embodiments, given by way of simple illustrative and non-limiting examples, and the appended drawings, among which:

There presents a simplified view of a system, cited by way of example, in which at least certain embodiments of the method of the present application can be implemented.

There presents a simplified view of a device adapted to implement at least certain embodiments of the method of the present application.

There presents an overview of the method of the present application, in some of its embodiments.

There illustrates an example of architecture of an active executable obtained by the method of the present application, in at least some of its embodiments.

There illustrates an example of implementation of the method of the present application, in at least some of its embodiments.

5. Description of embodiments

The present application proposes a method, at least partially automatic, for deploying software applications within a physical environment, more or more complex, such as an industrial unit (possibly distributed over several sites). Applications may, for example, correspond to software solutions implementing artificial intelligence (AI) techniques or to more traditional compiled and/or interpreted programs, provided by various suppliers.

In the present application, the term “passive” application or software resource is understood to mean a software resource in binary or textual format that executes only if another executable has invoked (or “called”) it by providing it with any possible parameters. entry he is waiting for. Such a resource may correspond, for example, to the binary code obtained by compiling the source code of a method or software function.

A passive resource has not been designed to obtain its input parameters itself. It is the executable (passive or active) which invokes it, or the operator which invokes it via a command line for example, which will assign values to its input parameters. Likewise, the passive resource simply “returns”, at the end of execution, its possible output parameter(s), to the executable (passive or active) or the operator which invokes it.

In contrast, what is meant here by “active” application or resource, or “active” or autonomous executable, is software binary code capable of executing without being invoked by another executable, by acquiring the values by itself. variables it uses. Such a resource may correspond for example to the binary code of a software process obtained by coupling (or “link” according to English terminology) of the binary code obtained by compilation of the source code of this process and the binary codes resulting from the compilations of the methods, functions, dictionaries it uses. Such executable code can be launched by a software application (thus creating the process object of the code) and then run in the background, acquiring the values of its input parameters on its own.

In an automated infrastructure, an active executable can for example obtain its input parameters from the raw data available on a data management infrastructure, which it knows and with which it can interact (such as a database, a bus data and/or another application). Such an interaction can be planned for example during the development of the source code of the executable, or via a configuration file. For example, it can obtain its input parameters by connecting to a database, or by subscribing to at least one channel of a data bus making data available. By “made available” data, we mean here both the data transported by the bus coming from at least one data source (which the executable will consume) and the data transmitted on the bus (by the executable ) and likely to be consumed by other executables, or to serve as commands to machines connected to this bus.

The method of the present application aims to modify a “passive” software resource to make it an “active” executable, and this in an at least partially (or even completely) automatic manner, for example without rewriting code, and/or, at least in certain embodiments, to deploy this active executable simply, for example by offering it on a user interface.

For example, in at least some embodiments, the active executable created from the passive application may be made accessible (e.g. in an executable library) to a software platform providing a user interface for launching such executables assets.

These active executables can, for example, be defined so as to run continuously, in the background, by sharing among themselves the software or hardware resources at their disposal, such as sensors, or the machines that they control. Thus, several “passive” applications can share (via their encapsulation in active executables) the same data source (like the same sensor for example).

Executables and their software or hardware resources can in certain embodiments communicate together asynchronously.

• de s’alimenter au fil de l’eau avec des données provenant de cette ou de ces source(s) (par exemple des données acquises par un ou plusieurs capteurs connectés à la plateforme), par exemple via des mécanismes de souscription à au moins un canal de données véhiculant de telles données;
• d’invoquer l’application passive avec des donnée d’entrée résultant de données provenant de cette/ces source(s);
• transmettre au fil de l’eau des données résultants de l’invocation de l’application passive à d’autres exécutables (par exemple via des mécanismes de publication de ces résultats dans au moins un canal du bus de données adapté à véhiculer de telles données.

In certain embodiments, an active executable can for example have the capacity to both:

• to be fed over time with data coming from this or these source(s) (for example data acquired by one or more sensors connected to the platform), for example via subscription mechanisms to at least a data channel carrying such data;
• to invoke the passive application with input data resulting from data coming from this/these source(s);
• transmit over time data resulting from the invocation of the passive application to other executables (for example via mechanisms for publishing these results in at least one channel of the data bus adapted to convey such data .

Depending on the embodiments, the data coming from these data sources may be “raw” or “unprocessed” data (ie data acquired by this/these data source(s), for example as measured by these sources data, such as a speed when a data source is a speed sensor), or “processed” data, obtained by processing “raw” data. This may for example be data integrating an interpretation of a speed measured by a speed sensor, such as a qualification of this speed (too fast, too slow) possibly correlated with other data (state of the tires on a car, wet road or not, etc.)).

The passive application itself may for example be an application not implementing any asynchronous data communication mechanism (such as a subscription to, or publication to, at least one data channel)

The invocation of the active application can for example allow the created active executable to interact (via the passive application) with equipment (for example industrial machines) connected to the platform and to which the passive application is dedicated . The transmission of (output) data resulting from the invocation of the passive application to other executables responsible for controlling equipment such as industrial machines can also allow indirect control (via these “other” executables) of this equipment.

In at least some of its embodiments, the method can thus help to simply generate combinations of executables, to obtain for example completely automated and personalized complex functionalities, dedicated for example to the particular needs of a company.

In at least some of its embodiments, the method can help a user to implement various applications, by integrating them in a simple manner, at least partially automatically, into their own environment, and this without multiplying user interfaces, hardware etc...

We now describe, in connection with the , in more detail this application. There represents a telecommunications system 100 in which certain embodiments of the invention can be implemented. The system 100 comprises one or more electronic devices, at least some of which can communicate with each other via one or more communication networks, possibly interconnected, such as a local network or LAN (Local Area Network) and/or a wide area network, or WAN. (Wide Area Network). For example, the network may include a corporate or home LAN network and/or an internet or cellular WAN network, GSM - Global System for Mobile Communications, UMTS - Universal Mobile Telecommunications System, Wi-Fi - Wireless, etc. .) . An example of such a communication network is the data bus 420 illustrated in .

As illustrated in , the system 100 can also include several electronic devices, such as terminals (such as a laptop 110, a smartphone 130, a tablet 120), connected objects 160 (for example production machines (such as electronic tools) or sensors, and/or a server 140 (for example an applications server) and/or a storage device 150.

The system may also include network management and/or interconnection elements (not shown).

There illustrates a simplified structure of an electronic device 200 of the system 100, for example one of the devices 110, 120, 130, 140, 150, 160 of the , suitable for implementing the method of the present application. As illustrated, depending on the embodiments, it may be a server, a terminal or a connected object. The device 200 can for example play the role of an executable management platform in the present application. In certain embodiments, it can be compatible with commercial platforms (such as the “Kubernetes” © platform) for deploying applications.

The device 200 notably comprises at least one memory M 210 such as a buffer memory, a volatile memory, for example of the RAM type (for “Random Access Memory” according to English terminology), and/or a non-volatile memory (for example of the RAM type). ROM (for “Read Only Memory” according to English terminology) The device 200 can also include a processing unit UT 220, equipped for example with at least one processor P 222, and controlled by a stored computer program PG 212. in memory M 210. At initialization, the code instructions of the computer program PG are for example loaded into a RAM memory before being executed by the processor P. Said at least one processor P 222 of the processing unit processing UT 220 can in particular implement, individually or collectively, any of the embodiments of the method of the present application (described in particular in relation to Figures 3), according to the instructions of the computer program PG.

The device can also include, or be coupled to, at least one I/O input/output module 230, such as a communication module, allowing for example the device 200 to communicate with other devices of the system 100, via wired or wireless communication interfaces, and/or such as an interfacing module with a user of the device (also called more simply in this application “user interface”).

By user interface of the device, we mean for example an interface integrated into the device 200, or a part of a third-party device coupled to this device by wired or wireless communication means. For example, it may be a secondary screen of the device or a set of speakers connected by wireless technology to the device.

A user interface may in particular be a so-called “output” user interface, adapted to a rendering (or to the control of a rendering) of an output element of a computer application used by the device 200, for example an application running at least partially on the device 200 or an “online” application running at least partially remotely, for example on the server 140 of the system 100. Examples of output user interfaces of the device include one or more screens, in particular at least one graphic screen (touchscreen for example), one or more speakers, a connected headset.

Furthermore, a user interface may be a so-called "input" user interface, adapted to acquiring a command from a user of the device 200. It may in particular be an action to be carried out in connection with an item rendered on an output interface of the device, and/or a command to be transmitted to a computer application used by the device 200 (for example an active executable as introduced above), for example an application running at less partially on the device 200 or an "online" application running at least partially remotely, for example on the server 140 of the system 100. Examples of input user interface of the device 200 include an acquisition means audio and/or video (microphone, camera (webcam) for example), a keyboard, a mouse.

Such input/output means can for example be adapted to management (creation, storage, selection, launch, configuration, etc.) of at least one executable. They can allow for example a configuration of the inputs/outputs of a “passive” resource (or application) to be deployed in the form of an active executable (for example a designation of at least one data channel to be used to provide parameters input to the resource via the executable to be deployed and/or a designation of at least one data channel to be supplied, via the executable, with output parameters provided by this resource, a designation of at least one data source for this executable to be deployed and/or a data recipient for this executable).

In certain embodiments, the input/output modules may also include communication means adapted to receive data (for example data acquired by another device such as images, measurements, etc.) and/or means acquisition of this data. These acquisition means may include physical or software sensors capable of acquiring such data. Such input/output modules can in particular be adapted to consume data circulating on at least one channel 422, 424 of a data bus 420 and/or to transmit data on at least one channel 426 of a bus 420 data (see ).

• Une obtention du code binaire de ladite application passive et d’une désignation du ou des type(s) de données consommées et/ou produites par ladite application ;
• Une sélection au moins partiellement automatique d’au moins une source de données dudit réseau et/ou d’au moins un consommateur de données dudit réseau, ladite sélection tenant compte dudit au moins un type désigné et d’au moins un type de données mises à disposition et/ou attendues dans ledit réseau;
• Une création automatique d’un exécutable actif dont au moins un processus logiciel comprend une invocation de ladite application passive avec en paramètre(s) d’entrée au moins une donnée mise à disposition par ladite source de données sélectionnée et/ou avec en paramètre(s) de sortie au moins une donnée attendue par ledit au moins un consommateur sélectionné.

Said at least one microprocessor of the device 200 can in particular be adapted for at least partially automatic deployment of a first passive software application in a communication network. Said processor can in particular be configured to:

• Obtaining the binary code of said passive application and a designation of the type(s) of data consumed and/or produced by said application;
• An at least partially automatic selection of at least one data source of said network and/or of at least one data consumer of said network, said selection taking into account said at least one designated type and at least one type of data put available and/or expected in said network;
• An automatic creation of an active executable of which at least one software process comprises an invocation of said passive application with as input parameter(s) at least one piece of data made available by said selected data source and/or with as parameter ( s) output at least one piece of data expected by said at least one selected consumer.

In certain embodiments, the method of the present application can be implemented in a distributed manner between at least two devices 110, 120, 130, 140, 150 or 160 of the system 100. Thus, in certain embodiments, a first device (for example a server 140 of the system 100) can construct an “active” executable (according to the method of the present application) which it communicates to at least a second device (for example a terminal 110 or the storage device 150 of the system 100), from which a third device (such as terminal 110, or server 140) can subsequently obtain this model. The executable can then be launched on the second and/or third device (for example the server 140, or another server, or the terminal 110) (according to the method of the present application).

In other embodiments, the method of the present application can be implemented locally by the device 200.

A distributed implementation of the method can make it possible to deploy the same executable in parallel on several devices (for example to allow redundancy of critical processing) by pooling certain processing operations to obtain the "active" executable from 'a passive application.

Furthermore, a local implementation of a device can help to simplify the implementation of the solution which is the subject of this application, and therefore help to limit its implementation cost. It can also help preserve the confidentiality of certain sensitive data or certain secret processing operations (such as manufacturing secrets forming part of a company's know-how) whose dissemination we wish to avoid.

Some of the above input-output modules are optional and may therefore be absent from the device 200 in certain embodiments. In particular, when the process is implemented locally, certain input/output modules linked to the transmission or reception of data may be absent.

By the term "module" or the term "component" or "element" of the device, we mean here a hardware element, in particular wired, or a software element, or a combination of at least one hardware element and at least one software element. The method according to the invention can therefore be implemented in various ways, depending on its embodiments, in particular in wired form and/or in software form.

We now present, in connection with Figures 3 and 4, certain implementations of the method 300 of the present application on an electronic device (which may be similar to the device 200 of the ). such as the server 140 or the terminal 110 of the .

As illustrated, the method 300 may include obtaining 310 the characteristics of at least one software application to be deployed in said communication network.

This obtaining may include in particular obtaining 312 of the application itself and obtaining 314 of its description. Depending on the embodiments, these two steps can be carried out in parallel, or successively (without prejudice to their respective order), or else, these two steps can be combined in a single step, where the application and its description are obtained together ( for example in the same data flow).

In certain embodiments, the application and/or its description can be received from another device (via means of communication); for example downloaded from an application server (for example by an operator, via a web interface), or loaded from an internal or external storage medium (such as an external hard drive or a USB key for example), After obtaining, the application and/or its description received can for example be loaded to be stored there, on a storage medium (such as a non-transitory medium such as a hard disk) of the platform.

For example, an application provider or a provider of equipment to be controlled may provide an application (for example an application for controlling this equipment), in the form of a binary code or a text file (such as a script), and a description of the application. This description can for example specify whether the application has input and/or output parameters, and if so, the number, type, order, and/or possible default value of these parameters. It may for example be an exhaustive and ordered list (according to the order of the parameters when invoking the application), indicating the type of each of the input and/or output parameters.

Depending on the embodiments, the description can be transmitted in various forms, such as a paper or electronic document, transmitted via a storage medium, or downloaded, jointly with the application or separately.

The format of the electronic document may differ depending on the embodiments. In the case of an electronic document, it may be a document in "pdf" format, or based on the "HTML" format (for "HyperText Markup Language" in English), or an interpretable descriptive file automatically. For example, it may use a format specific to the application provider or equipment to be ordered or use a standard data serialization format, such as the format known as YAML, or a format using a markup language, like HTML.

Obtaining 314 the description can for example implement a transcription of at least part of a paper or electronic document (such as a document in “pdf” format) in an automatically interpretable format. This transcription can for example be carried out manually by an operator via a human machine interface (such as a web interface) of the device 200 or automatically, for example via automatic document analysis techniques such as automatic character recognition techniques. , syntactic and/or semantic analysis etc.

As illustrated in , the method may include in certain embodiments, obtaining 320 a description of the data likely to be conveyed to devices of the system 100 (such as sensors, cameras, etc. or other active executables of the system 100 ) (and therefore capable of supplying, via an active executable, the application obtained 310) and vice versa with data likely to be expected by devices of the system 100.

In the example of the , the devices of the system 100 use one or more channels of a data bus to asynchronously exchange information using for example a messaging protocol using a subscription mechanism (or subscriptions) to events and/or or event publications.

Depending on the embodiments, the messaging protocol can be diverse, for example it can be a messaging protocol based on a standard communication protocol such as TCP/IP (from the English Transmission Control Protocol (TCP) and Internet Protocol (IP), such as MQTT (for Message Queuing Telemetry Transport).

A description of the data circulating on the data bus can for example be obtained from an entity managing the data bus.

For example, certain embodiments can use a “Broker” type entity in the case of an MQTT bus and/or a dynamic analysis 322 of the data actually made available on the bus.

For example, in the case of an MQTT bus, a subscription to channel ‘#’ allows you to receive data circulating on all active channels. Each data message can then indicate, for example, the channel used.

In certain embodiments, a declarative system can also be implemented to allow a data source (a sensor for example) to signal that it is active and that it is using a specific channel.

Thus, a dedicated channel can for example be used to generate (and/or broadcast) a directory of available channels. Each source can for example emit a signal on this channel (for example in a well-defined format). Executables (subscribed to this channel) can then be notified of the channel used by the source and register (or not) in the recipients of the source channel.

A dynamic channel analysis can for example use a type detection tool (such as the “Java Data Type” type detector), in order to dynamically obtain the data type of at least one channel of the bus (for example automatically when of the use of the method of the present application, before or during the execution of the active executable. In the case of the Java Data Type tool, the dynamic analysis of data circulating on a data channel can allow. for example to find a primitive, low-level Java type, such as the “boolean” type, the “character” type, the “integer” type, the “floating number” type, or the “double” type. , the formats identified during the dynamic analysis may vary depending on the embodiments (for example depending on the type detection tool used).

The description of the data likely to circulate on the data bus may in particular include an identifier of at least one device and/or process source of such data (such as elements 442, 444 of the ) and/or a device and/or process consuming such data (such as element 446 of the ), and/or at least one format of this data. It may also include in certain embodiments, a probable and/or requested frequency of making such data available, a probable, minimum or maximum size of this data, etc.

In the example of the , the method may include a mapping 330 between at least a portion of the description of the application, relating to the input and/or output parameters of the application, and the data likely to circulate on the data bus .

For example, when a type (primitive for example) of data circulating on the bus is identical to a type (primitive for example) of an input or output parameter of the application, the circulation channel will be considered as a possible channel for making data available (by or for an executable invoking the application) and stored in association 334 with the input or output parameter of the application concerned.

When a type of data capable of circulating on at least one of the bus channels is different from a type of an input or output parameter of the application, the method can include a reading 332 of a table of conversion associating at least one pair consisting of a first and a second type of data (primitives for example) with at least one conversion method to be used to convert data of this first type into data of this second type.

The conversion table (like element 430 of the ) can be stored for example on the device 200 or in a storage device such as the device 150 of the system 100).

Reading 332 of the conversion table can make it possible to identify a conversion method to be used to convert at least one piece of data circulating on at least one of the bus channels into at least one application input parameter, or to convert at least one output parameter of the application in data adapted to circulate on at least one of the channels of the bus.

If reading the conversion table makes it possible to identify a method of conversion between a data channel and an input or output parameter of the application, the circulation channel will be considered as a possible channel for making the data available. data (by or for an executable invoking the application), using the conversion method. This data channel will then be stored in association with the input and/or output parameter of the application concerned, and the conversion method (or a link to this method) to use.

The matching thus results, in the example illustrated, in a possible association 334, with input or output data, with at least one data provision channel, as well as optionally with at least one associated conversion method.

When at least one input or output parameter is not associated with any channel, and, in the case of an input parameter, has no default value, the method may include generating a message alert and its transmission to another remote device and/or its rendering to a human machine interface of the device 200. Indeed, it may be necessary to manually assign a default value to an input parameter and/or modify or add a channel and/or a data source to the system 100 to enable the provision of data of a type corresponding (possibly via conversion) to the input parameter.

Note that an output parameter which is not associated with any channel can simply be ignored by the executable invoking the passive application.

In certain embodiments, the method may comprise a selection, among the channels associated with an input or output parameter of the application, of at least one data channel to be used during an invocation of the application passive. In certain embodiments, this selection may be automatic.

For example, the selection of at least one data channel may be automatic in cases where a single channel is associated with an input and/or output parameter of the application, or when the selection is based on the application of previously configured rules. For example, a rule can indicate that the data from all channels associated with an input parameter must be used as the application's input parameter (the executable then monitors all of these channels), or that 'an output parameter must be made available (emitted for example) on all channels associated with this output parameter.

In certain embodiments, the method may include a rendering 336 of the channels associated with a parameter of the application, as well as for example characteristics of these channels (such as an identifier of at least one source or consumer device of the data circulating on a channel), so as to allow an operator to make a choice among the channel(s) associated with the parameter concerned and/or to confirm the (automatic) selection of one or more channels.

In such an embodiment, the method may include an acquisition 338 of a designation of at least one of the channels associated with the parameter. The designation may for example include at least one identifier of at least one data channel to be selected (or alternatively not to be used) and/or at least one identifier of at least one data source or consumer device using a channel of data to select (or alternatively not to use).

In the example of the , the method may include an automatic creation 340 of an active executable 410 responsible for invoking the passive application using the data made available via the channels selected during the matching 330. illustrates an example of the software architecture of such an executable 410 and its environment.

• un élément logiciel offrant une fonctionnalité de souscription (ou abonnement) et/ou de désabonnement à au moins un premier canal 422, 424 d’un bus de données 420 (par exemple les canaux associés à un paramètre d’entrée de l’application sélectionnés lors de la mise en correspondance 330) ou en variante, plus spécifiquement, aux mises à disposition de données, via ce premier canal 422, 424, en provenance d’au moins une première source 442, 444 de données ;
• un élément logiciel en charge d’écouter en permanence sur le premier canal 422, 424, et d’obtenir les données circulant sur ce premier canal 422, 424 ou , en variante, les données en provenant de la première source 442, 444;de données utilisant ce premier canal)
• un élément logiciel offrant une conversion éventuelle d’au moins une donnée (« brute » par exemple) mise à disposition sur le premier canal, en au moins une donnée d’un type connu (« donnée primitive ») et/ou une conversion éventuelle d’au moins une donnée primitive en au moins une donnée de format adapté au paramètre d’entrée 414 associé au premier canal 422, 424, en utilisant par exemple une méthode de conversion associée à ce paramètre d’entrée 414 et à ce premier canal 422, 424 lors de la mise en correspondance 330;
• un élément logiciel adapté à une invocation de l’application « passive » 412 avec en paramètre(s) d’entrée 414 au moins une donnée obtenue via l’écoute sur le premier canal 422, 424 (et éventuellement convertie) (ou une donnée fonction de la donnée obtenue)
• un élément logiciel offrant une conversion éventuelle d’au moins un paramètre(s) 416 de sortie de l’application 412 invoquée, en utilisant la méthode de conversion associée à ce paramètre de sortie 416 lors de la mise en correspondance 330 et
• un élément logiciel adapté à une mise à disposition du paramètre de sortie 416 (ou d’une donnée fonction de ce paramètre) sur un deuxième canal 426 associé à ce paramètre de sortie 416 et sélectionné lors de la mise en correspondance 330 et éventuellement converti

Such an executable 410 may include:

• a software element offering a subscription (or subscription) and/or unsubscription functionality to at least a first channel 422, 424 of a data bus 420 (for example the channels associated with an input parameter of the selected application during matching 330) or alternatively, more specifically, to the provision of data, via this first channel 422, 424, coming from at least a first data source 442, 444;
• a software element responsible for permanently listening on the first channel 422, 424, and obtaining the data circulating on this first channel 422, 424 or, alternatively, the data coming from the first source 442, 444; data using this first channel)
• a software element offering a possible conversion of at least one piece of data (“raw” for example) made available on the first channel, into at least one piece of data of a known type (“primitive data”) and/or a possible conversion of at least one primitive data into at least one data of format adapted to the input parameter 414 associated with the first channel 422, 424, using for example a conversion method associated with this input parameter 414 and this first channel 422, 424 when matching 330;
• a software element adapted to an invocation of the “passive” application 412 with as input parameter(s) 414 at least one piece of data obtained via listening on the first channel 422, 424 (and possibly converted) (or a piece of data depending on the data obtained)
• a software element offering a possible conversion of at least one output parameter(s) 416 of the invoked application 412, using the conversion method associated with this output parameter 416 during the matching 330 and
• a software element adapted to making the output parameter 416 (or data based on this parameter) available on a second channel 426 associated with this output parameter 416 and selected during the matching 330 and possibly converted

Depending on the embodiments, the executable may include various other software elements. For example, in certain embodiments, it may include a module for generating traces of the invocation of the passive application (ie alerts reporting this invocation) towards an operator's device.

These software elements can be implemented in separate or common software modules. For example, in certain embodiments, at least some of these software elements may be implemented by a common software module hereinafter called Publish/subscrib Proxy. The code of at least some of these software elements and/or module(s) may be identical regardless of the passive application of the system 100, the instantiation of the element(s) and/or module(s) software(s) being done for example using the description obtained 310 of the application, the description obtained 320 of the data put into circulation on the bus and/or the associations stored during the matching 330 of the method of the present application .

The active (or autonomous) executable can for example be created 342 automatically, from the passive application and (for example) the software modules and/or above, via executable generation tools; such as tools using encapsulation techniques such as Docker © technology. So, in the example of the , the active executable can be obtained via the “Image Docker” © program. Such a program can help, for example, to obtain an executable in a few seconds.

In the example of the , the method may include storing the active executable created. This storage can for example include an addition 344 in a library of executables, accessible to an operator, to allow subsequent deployment 360 of this executable on the device 200 (or another device of the system 100). This addition may be optional in certain embodiments.

As illustrated in , the method may include a rendering 350 of information representative of the active executables available to an operator (via a library as mentioned above for example). For example, the information representative of an active executable may include information relating to the system 100 (such as the devices present in the system, their memory and/or processing capacities, their connections (USB, serial, bus), etc.) information relating to the active executable itself (such as an identifier of the active executable and/or its memory size), information relating to the passive application from which this active executable was generated (for example a information present in the description of the passive application, such as an identifier of the application, a label (explanatory for example) associated with the application, a format and/or a minimum or maximum size of at least one parameter of input or output of the application), information relating to at least one device or process, source and/or consumer of data made available on a channel selected for the application (for example information present in the description of the channels of the data bus, such as an identifier and/or a label of this device or process, source and/or consumer of data, a format and/or a minimum or maximum size of at least one piece of data made available by/for this device on the bus, etc. An operator can thus have the possibility, for example, of checking the configuration of the active executable.

Information relating to the current state of the bus, to the device and/or process, source and/or consumer of data, present at the current time on the bus and/or to other executables currently running on the platform and to the device or process, source and/or consumer of data for these other executables can also be rendered.

Rendering may be optional in certain embodiments.

In certain embodiments, the method may include a possible update 352 of the active executable. Such an update 352 can for example take the form of replacing a previous version of an active process with a later version (generated as already explained by the process of the present application). In certain embodiments, the active executable can for example receive via a specific channel of the data bus a command to unsubscribe to at least one selected channel (or alternatively a command to unsubscribe to a data source using this channel) and a new subscription command to a new channel (or alternatively a new subscription command to a data source using this channel). The execution of such a command may for example include automatic validation of the command, using the conversion table introduced previously.

Such an update can, for example, occur when the data from a data source newly present in the system (a sensor for example), are more relevant than those from a data source already present in the system.

Such an update possibility may be optional in certain embodiments.

In the example illustrated in , the method may include a 360 deployment of the created active executable. This 360 deployment includes a 362 launch of the active executable (on the platform giving access to several executables introduced above for example). Thus, in the example illustrated in , where the active executable is created in the form of a “Docker” © type execution environment, when deploying the docker, the main program (ie the active executable) of the docker is launched. In some embodiments, where the matching is performed before creation of the active executable, it automatically subscribes to the selected channels corresponding to the input parameter(s) of the passive application. When receiving at least one piece of data via at least one of these channels, the executable optionally converts it then invokes the “passive” executable as explained above, if it has obtained all of the parameters. entry (or at least those without a default value) of the application. If a first data corresponding to a first input parameter is received while no data is yet available for a second input parameter, the first data can be stored temporarily (at least until the expiration of a first duration (time out according to English terminology) until reception of data corresponding to the other input parameters of the application. The invocation of the application can therefore be carried out asynchronously with respect to the provision. data on a channel.

In some embodiments, the matching may be performed manually, for example after launching the active executable. In such embodiments, the matching can be performed several times (for example when a new data channel, or a new data source appears interesting to an operator, or when a new data consumer, who may be interested in the result of the execution of the passive application is newly present in the system). In such embodiments, which may induce a modification of subscriptions to data bus channels, the software module may include an unsubscription of certain channels.

Such embodiments may make it possible, for example, to modify the data sources used as input parameters of the passive application, such as to modify the use of the execution results of the application, without stopping the execution of the application. 'active executable.

The process which is the subject of the present application has been detailed above.

Such a method, in at least some of its embodiments; can for example help an operator to build and launch (for example in a simple way) active or autonomous executables, using automated procedures, and possibly to easily combine these executables (for example via action chaining functionalities offered by a human machine interface of the platform), for example via chaining functionalities known as “low code” (such as the “NodeRed” tool).

An example of use of the method of the present application is presented in connection with the : In this example, it is assumed that the system 100 includes an industrial machine such as a conveyor M1 512, M2 514, installed in an industrial zone Z1 510.

• d’une part pour obtenir une première procédure P1 automatique effectuant un contrôle visuel de la qualité des pièces produites par la machine industrielle, avec arrêt du convoyeur et génération d’un message (email, sms) en cas de défaut,
• et d’autre part pour obtenir une seconde procédure P2 automatique limitant l’accès à une zone Z1 510 dans laquelle est effectué le contrôle par la procédure P1 car celle-ci peut présenter un danger pour des opérateurs du fait des arrêt et redémarrage du convoyeur.

The process is implemented:

• on the one hand to obtain a first automatic P1 procedure carrying out a visual check of the quality of the parts produced by the industrial machine, with stopping of the conveyor and generation of a message (email, SMS) in the event of a defect,
• and on the other hand to obtain a second automatic P2 procedure limiting access to a zone Z1 510 in which the control is carried out by the P1 procedure because this can present a danger for operators due to stopping and restarting of the conveyor .

The automation of the procedure P1 requires for example the deployment of an active executable (here a Docker Image) I1 created, according to the method of the present application, from an application IA1 from a supplier F1, specialized in vision by computer.

• un paramètre d’entrée au format Base64, JPEG (pour « Joint Photographic Expert Group »), PNG (pour » Portable Network Graphics »), SVG (pour « Scalable Vector Graphics »), ou WebP (pour « Web Picture » ), permettant à l’application d’acquérir une photo de l’objet ;
• un paramètre de sortie sous forme d’un booléen, ou JSON représentatif de la détection ou non d’une fissure et/ou éventuellement de la localisation sur l’image de la fissure.

For example, the passive application A1 can be an application implementing artificial intelligence (AI) techniques to detect cracks in an object, and having:

• an input parameter in Base64, JPEG (for “Joint Photographic Expert Group”), PNG (for “Portable Network Graphics”), SVG (for “Scalable Vector Graphics”), or WebP (for “Web Picture”) format, allowing the application to acquire a photo of the object;
• an output parameter in the form of a Boolean, or JSON representing the detection or not of a crack and/or possibly the location on the image of the crack.

In a supervision zone 530, a data collector 532 from sensors collects sensor data 522 in real time. Thus, at each detection the camera C1 transmits its data (here images) to the collector 532 which distributes them via the data bus 538 (for example on specific channels) to the executables I1 534 and I2 536.

The active executable I1 subscribes for example to a data channel S1 conveying base 64 format data (corresponding for example to images published by a camera C1 512 located near the conveyor).

The active executable I1 thus receives the images from the camera C1 and uses them to invoke the application IA1 which analyzes these images.

The images can for example be conveyed in a binary format via one of the channels or be conveyed in Base64 format.

The executable I1 publishes each time an image is analyzed by the application IA1 the result (Boolean) of this analysis in a second channel S2.

In this example, a lowcode executable LC1 can additionally be created to use the results provided via the S2 channel by the executable I1. For example, the LC1 executable can subscribe to the S2 channel and each time data is received via this channel (“True” for example) indicating a fault, it sends an email or SMS alert to a contact whose contact details are accessible to the LC1 executable.

Furthermore, the automation of the P2 procedure requires, for example, the deployment of an active executable (here also a Docker Image) I2 created, according to the method of the present application, from an IA2 application from a supplier F2 , specialized in crossing detection.

The active executable I2 subscribes for example to the same data channel S1 as the active executable I1 (carrying base 64 format data corresponding for example to images published by the same camera C1.

The active executable I2 536 thus receives the images from camera C1 and uses them to invoke the IA2 application which analyzes these images to detect the crossing of a zone delimiter (here Z1). The I2 executable publishes each time an image is analyzed by the IA2 application the result (Boolean) of this analysis in a third S3 channel. A “low code” type executable (for example the LC1 executable or another executable) subscribes to the S3 channel and each time data is received via this S3 channel (“True” for example) indicating a crossing of the delimiter of the zone Z1, it sends an email or SMS alert to a contact whose contact details are accessible to the LC1 executable. The executable IA2 publishes data (for example Boolean data whose value corresponds to a stop command for example) in the channel of the controllers of the machines M1 and M2 which in turn detect this data and interpret this value and stop 524 the M1 and M2 conveyors (e.g. digital twins of the M1 and M2 machines).

The example above shows the application of the method of the present application to obtain, in an at least partially automatic manner, and more easily than certain solutions of the prior art, complex control procedures, particular to the needs of a system and/or its users.

• une machine disposant au minimum de 2 CPU, 2Go de RAM,
• une latence inférieure à 10ms,
• un nombre d’ exécutables actifs de l’ordre d’une dizaine ;
• des connectiques USB ;
• des capacité de connectivité par Ethernet ;
• des machines industrielles du client avec automate connectable via Ethernet ou sans fil ;
• des capteurs connectables via Ethernet ou sans fil ;
• des applications comportant des techniques d’Intelligence Artificielle et/ou des services, de fournisseurs du marché.

Implementation examples have been tested by the inventors, for example:

• a machine with at least 2 CPUs, 2GB of RAM,
• a latency less than 10ms,
• a number of active executables of around ten;
• USB connectors;
• Ethernet connectivity capabilities;
• customer's industrial machines with PLC connectable via Ethernet or wireless;
• sensors connectable via Ethernet or wireless;
• applications comprising Artificial Intelligence techniques and/or services from market suppliers.

At least certain embodiments of the method of the present application can help a company/operator (or user) to limit the cost and/or impact of the automation of operations relating to its activity, while helping to maintain a level of performance of these operations.

At least certain embodiments of the method of the present application can for example help an industrial company to limit the costs of installation or use of equipment (such as sensors or servers) in connection with an application (for example by using hardware already operational in connection with other applications).

At least certain embodiments of the method of the present application can, for example, help an industrial company to limit the material density in a physical environment such as an industrial site.

At least certain embodiments of the method of the present application can for example help an industrial company to limit the heterogeneity of its software and/or hardware fleet and/or to simplify the methods of monitoring, evolution and/or maintenance of this park.

At least certain embodiments of the method of the present application can, for example, help an industrial company to limit conflicts of access to machine automation, the impact of which can be disastrous.

At least certain embodiments of the method of the present application can for example help to obtain, in at least a relatively simple manner, end-to-end analyzes of certain production chains.

This application may apply to various “passive” software applications and in particular applications related to any type of equipment (such as “IoT” type (for “Internet of Things” according to English terminology) or industrial, fixed or mobile, etc.)

For example, the process of the present application can be implemented in industrial sites having a fleet of machines equipped with automation, to help automate complex procedures. For example, it can create active executables from “passive” applications from various suppliers, for example suppliers specializing in the following issues:

Area security control with automated shutdown and alert notification to authorized personnel;

Quality control of machined parts at the exit of machining machines with isolation of defective parts (for example in different areas depending on their level and/or type of defect);

Application of automatic calibration after fault detection;

Preventive fault detection via vibration sensors and applications implementing associated Artificial Intelligence techniques

Data collection and generation of statistics and metrics

Modifications to production procedures on the fly and measurement of the impacts of different versions of procedures.

Claims (10)

Method for at least partially automatic deployment of a passive software application in a communications network, said method comprising:

• Obtaining the binary code of said passive application and a designation of the type(s) of data consumed and/or produced by said application;
• An at least partially automatic selection of at least one access to data from at least one data source of said network and/or to at least one data consumer of said network, said selection taking into account said at least one designated type and at least one type of data expected via said access;
• An automatic creation of an active executable of which at least one software process includes an invocation of said passive application with as input parameter(s) at least one piece of data obtained via said access and/or with as output parameter(s) at least one piece of data to be transmitted via said access.

A method according to claim 1 wherein said method comprises adding said created active executable to an active executable library of said communication network. Method according to claim 2 wherein said added executable is associated in said library with said at least one data source and/or said at least one data consumer. Method according to any one of claims 1 to 3 wherein said method comprises launching said active executable or proposing such a launch. Method according to any one of claims 1 to 4 where said designation is obtained by access to a descriptive file of the data consumed and/or produced by said application. Method according to any one of claims 1 to 5 where said access is access to a database. Method according to any one of claims 1 to 5 where said at least one type of data expected via said access is obtained by scanning said network. Method according to any one of claims 1 to 5 or 7 where said access is a channel of a data bus of said network. A method according to claim 8 wherein said data obtained via said channel is obtained by subscribing said software process to said data channel to receive data from said at least one data source. Method according to one of claims 8 or 9 where said software process comprises a transmission of said data to be transmitted on said channel.