Techniques for configuring and updating software and applications on stalled on devices communicating with one or more servers

A configuration method implemented by a terminal capable of communicating with a server, a back-end application and a corresponding front-end application being installed respectively on the server and on the terminal, the server having access to at least one database comprising:

• a list of sets of identifiers, each set of identifiers comprising
• a terminal identifier,
• a hardware layer identifier, and
• an operating system identifier;
• a lookup table mapping between
• each pair of hardware layer identifier and operating system identifier that exists in said list, and
• a configuration file, stored in the at least one database
• the method comprising, upon a communication session being opened between the terminal and the server:
• a. sending, from the terminal to the server, a set of identifiers comprising a terminal identifier, a hardware layer identifier for a hardware layer of the terminal, and an operating system identifier for the operating system implemented on the terminal;
• d. upon the terminal receiving a configuration file from the server, implementing said configuration file in the front-end application, and
• if and only if said configuration file carries an indicator tagging the file as temporary, switching the front-end application to a test mode,
• e. in response to a predetermined validation action by the user via the terminal,
• deleting an indicator tagging the file as temporary, on the terminal,
• switching the front-end application to a normal mode,
• sending, from the terminal to the server, a command to validate said temporary configuration file.

A configuration method implemented by a server capable of communicating with at least one terminal, a back-end application and a corresponding front-end application being installed respectively on the server and on the terminal, the server having access to at least one database comprising:

• a list of sets of identifiers, each set of identifiers comprising
• a terminal identifier,
• a hardware layer identifier, and
• an operating system identifier;
• a lookup table mapping between
• each pair of hardware layer identifier and operating system identifier that exists in said list, and
• a configuration file, stored in the at least one database
• the method comprising, upon a communication session being opened between the terminal and the server:
• b. upon the server receiving a set of identifiers from the terminal, comparing this set with the content of the database, and
• in the event of a match between the set of identifiers sent and a set of identifiers in said list, continuing the communication session without updating the configuration of the terminal;
• in the event of no match between the set of identifiers sent and the sets of identifiers in said list, and in the event of a match with a pair of hardware layer and operating system identifiers in the lookup table,
• sending in return, from the server to the terminal, the configuration file associated with said pair in the lookup table;
• in the event of no match with a pair of hardware layer and operating system identifiers in the lookup table,
• identifying, in the lookup table and by applying pre-established rules, a pair of hardware layer and operating system identifiers which is closest to that in the set of identifiers sent from the terminal, then sending in return, from the server to the terminal, the configuration file associated with the combination identified according to the lookup table, said file being sent with an indicator tagging the configuration file as temporary;
• c. populating the database with the set of identifiers received and any association resulting from the identification.