Update of configuration

By using database management terminal identifiers and configuration files in the communication system between the server and the terminal, the application update complexity caused by multiple terminal devices and firmware versions is solved, and more efficient update management and resource utilization is achieved, ensuring that Compatibility and stability of the application.

CN119096228APending Publication Date: 2024-12-06STREAMWIDE
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034965.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-26
Filing Date
2023-04-05
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the case of multiple end devices and firmware versions, application updates are complex and inefficient, resulting in applications incompatible with new end models, resulting in frequent full cluster updates, wasting resources and increasing costs.

Method used

By establishing a communication system between the server and the terminal, using the database to store the identifier collection and configuration files, the terminal and the server coordinate the matching and update of the configuration files, reduce unnecessary application updates, and switch to test mode for verification when needed.

Benefits of technology

Reduces the frequency and size of full updates to all terminals, improves update efficiency, reduces resource consumption, and intervenes only when necessary to ensure application compatibility and stability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096228A_ABST
    Figure CN119096228A_ABST
Patent Text Reader

Abstract

The invention relates to a system comprising a terminal (1) and a server (2) configured for, when a communication session is on, sending a set of identifiers from the terminal to the server; comparing it with the content of the database, and in the event of a complete match, continuing the communication session without updating the configuration of the terminal; in the event of a partial match, sending the associated profile as a return; -in the event of a mismatch, identifying a pair of similar identifiers and sending the associated profile marked with the temporary indicator; populating the database with the received set and any associations generated by the identification; after receiving the file, the file is implemented in a front-end application of the terminal, and when and only when the configuration file contains an indicator that marks the file as temporary, the front-end application is switched to a test mode.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the technical field of configuring and updating software and applications installed on devices that communicate with one or more servers. More specifically, it is directed to the situation where a device cluster contains devices with various internal software ("firmware") that is initially unknown from the perspective of the server. Background Art

[0002] In the field of software application maintenance, the responsibility for updates lies almost entirely with the provider of the software, typically the application installed on a smartphone. However, such devices may have a wide variety of firmware, generated by a variety of manufacturers, device models, and even firmware versions of the same device model. Therefore, from the perspective of application providers such as applicants, new firmware appears very frequently. When a new firmware version appears, it is usually accompanied by a new terminal model, and the operation of the application may be degraded or even completely incompatible with the new terminal model. In order to maintain application compatibility with as many devices as possible over time, application providers regularly deploy application updates to the entire fleet of devices, even if only a small portion of them (the most recent) require such updates. Such maintenance is complex, expensive, and inefficient. Summary of the Invention

[0003] The present disclosure improves this situation.

[0004] A system is proposed. The system includes at least one terminal and a server capable of communicating with each other. A backend application and a corresponding frontend application are installed on the server and the terminal respectively. The server can access at least one database.

[0005] The database includes:

[0006] - A list of identifier sets, each identifier set consisting of

[0007] *Terminal identifier,

[0008] * Hardware layer identifier, and

[0009] * Operating system identifier;

[0010] - A lookup table mapping between

[0011] * each pair of hardware layer identifier and operating system identifier that exists in the list, and

[0012] * a configuration file stored in the at least one database.

[0013] When a communication session is initiated between the terminal and the server, the terminal and the server are configured to perform the following operations in coordination with each other:

[0014] a. Sending a set of identifiers from the terminal to the server, the set of identifiers including a terminal identifier, a hardware layer identifier of the terminal's hardware layer, and an operating system identifier of the operating system implemented on the terminal;

[0015] b. After the server receives the set of identifiers from the terminal, it compares this set with the contents of the database, and

[0016] - in the event of a match between the set of identifiers sent and the set of identifiers in said list, continuing the communication session without updating the configuration of the terminal;

[0017] - in case of no match between the sent set of identifiers and the set of identifiers in said list, and in case of a match with a pair of hardware layer and operating system identifiers in the lookup table,

[0018] in return, sending from the server to the terminal a configuration file associated with the pair in the lookup table;

[0019] - In the event of a mismatch between a pair of hardware layer and operating system identifiers in the lookup table,

[0020] identifying, in a lookup table and by applying pre-established rules, a pair of hardware layer and operating system identifiers that is closest to an identifier in the set of identifiers sent from the terminal, and then in return, sending from the server to the terminal a configuration file associated with the combination identified according to the lookup table, the configuration file being sent with an indicator marking the configuration file as temporary;

[0021] c. populating the database with the received set of identifiers and any associations generated by the identification;

[0022] d. After the terminal receives the configuration file from the server, implement the configuration file in the front-end application, and

[0023] If and only if the configuration file carries an indicator marking the file as temporary, the front-end application is switched to a test mode.

[0024] The terminal and the server may be further configured to:

[0025] e. in response to a predetermined verification action performed by the user via the terminal,

[0026] removing, on the terminal, an indicator marking the file as temporary,

[0027] Switch the front-end application to normal mode,

[0028] Sending a command to verify the temporary configuration file from the terminal to the server;

[0029] f. After the server receives the command to verify the temporary configuration file from the terminal, the indicator marking the file as temporary is deleted from the corresponding association in the database.

[0030] According to another aspect, a configuration method implemented by a terminal is proposed, the configuration method comprising the above operations a and d, and optionally e.

[0031] According to another aspect, a configuration method implemented by a server is proposed, the configuration method comprising the above operations b and c, and optionally f.

[0032] According to another aspect, a terminal is proposed, which is configured to implement the method as defined above.

[0033] According to another aspect, a server is proposed, which is configured to implement the method as defined above.

[0034] According to another aspect, a computer program is provided, comprising instructions for implementing all or part of the method as defined herein when this program is executed by a processor. According to another aspect, a non-transitory computer-readable storage medium is provided, on which this program is stored.

[0035] By providing a configuration file adapted for each new terminal (or terminal in a new configuration) connected to the server, it is possible to reduce the number and frequency of complete updates of applications to be deployed to all terminals. Creating a configuration file is much easier than deploying a complete update, specifically because compatibility is verified with the terminal or configuration in question rather than with the entire terminal fleet. The size of a configuration file is much smaller than the size of a complete update to an application, thus reducing the time and hardware and software resources required to send such a file over the telecommunications network and then install it. From the perspective of the end user, there is no need to update the application as long as the terminal being used has not been modified.

[0036] From an overall perspective, providing a new profile benefits each user of a terminal with the corresponding configuration, without affecting other users of the service. Upstream, users of the application profile in "test" mode verify its proper operation, so that intervention by the application provider's operators is only necessary in the event of a malfunction. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Other features, details, and advantages will become apparent upon reading the following detailed description and analyzing the accompanying drawings, in which:

[0038] Figure 1

[0039] [ Figure 1 ] represents an element of a system according to one embodiment.

[0040] Figure 2

[0041] [ Figure 2 ] is a diagram of an implementation scheme according to an embodiment.

[0042] Figure 3

[0043] [ Figure 3 ] represents data exchange between elements of a system according to one embodiment. DETAILED DESCRIPTION

[0044] background

[0045] Hereinafter, the terms "front-end application" and "back-end application" are used to distinguish what technicians call the front-end and back-end, respectively. Similarly, the terms "internal software" and "application software" are used to distinguish what technicians call "firmware" and "software," respectively.

[0046] The following description has been implemented by the applicant in the context of half-duplex communication via a mobile phone network, commonly known by the acronym "PTT," which stands for "Push-to-Talk," and in particular by services known under the trademarks "Team on the run" and "Team on mission." Essentially, this involves providing a communication solution that, from the user's perspective, appears to behave similarly to a "walkie-talkie" radio transceiver (holding the button down speaks on the channel, releasing it stops speaking on the channel and switches to listening mode), while offering the properties enabled by recent communication networks and protocols (combined audio / video; compatibility and interoperability with a large number of mobile or fixed terminals; encryption of communications; geolocation; on-the-fly network switching; etc.). In practice, the following embodiments are therefore particularly beneficial in the context of PTT communications (but not limited thereto).

[0047] The following embodiment is also particularly advantageous in situations where it is difficult or even impossible for the application software administrator to have physical access to the terminal and certain information related to its configuration. This is often the case when the terminal is used by persons performing "sensitive" activities (police, law enforcement, civil security, emergency services in disaster events, operations in areas with unreliable network coverage, etc.) for privacy and security reasons.

[0048] Description of Embodiments

[0049] Now refer to [ Figure 1 ]. The system includes at least one terminal 1 (here three), a server 2 and a database 3. The terminal 1 and the server 2 are each a device suitable for communicating (specifically, communicating with each other) (i.e., exchanging data) via one or more telecommunication networks. Thus, the terminal 1 may correspond to a fixed or mobile communication device available to a user, such as a smartphone or a computer. The server 2 designates a device that is remote from the terminal 1 and is managed by a service provider such as an application provider. The server 2 has access to the database 3. The database 3 is represented here as an entity different from the server 2. Alternatively, the database 3 is a subset of the server 2. The data exchange between the terminal 1, the server 2 and the database 3 may involve intermediate components. In other words, the data transmission between the aforementioned elements is not necessarily direct.

[0050] Terminal 1 includes a human-machine interface. This term is used as a general term to designate all devices and software components of terminal 1 that enable a user to interact with terminal 1, both for receiving information from terminal 1 and for inputting information into terminal 1. The human-machine interface takes the form of, for example, a touch screen, which is known per se. Alternatively, the human-machine interface may take other forms, such as a microphone for capturing voice commands, a speaker for providing information in audio form, a vibrator for providing information in tactile form, or a combination of such components.

[0051] The terminal 1 includes at least one processor and a memory unit, wherein the memory unit is configured to cause the processor to execute a program stored in the memory unit. The program includes:

[0052] - internal software ("firmware"), which is typically installed at the time of manufacture and factory setup configuration of the terminal 1 and which is subsequently updated under the responsibility of the entity that sells the terminal 1;

[0053] - Application software ("Software"), usually installed at a later time at the initiative of the user of the terminal 1 and updated under the responsibility of an entity that is usually different from the provider of the terminal 1 .

[0054] The front end of the application is installed on the terminal 1 , while the back end of the application is installed on the server 2 .

[0055] Herein, server 2 may include several devices and software components arranged to interact with each other. In other words, server 2 does not necessarily consist of a single, physically integrated device, but may include several distinct modules that are remote from each other. Server 2 includes, for example, at least one processor and one or more memory units capable of storing a database accessible by the at least one processor. In the examples described herein, server 2 further includes an application programming interface, or API. The API interfaces between the communication module of server 2 and database 3. One or more APIs may also be provided to enable an operator to access the API.

[0056] Database 3 contains at least the following data:

[0057] - a list I of sets of identifiers;

[0058] - Lookup Table II;

[0059] - a configuration file D, which optionally contains one or more "temporary" configuration files denoted D,Z.

[0060] Each identifier set in List I includes:

[0061] *Terminal identifier A,

[0062] * Hardware layer identifier B, and

[0063] * Operating system identifier C. In practice, list I identifies each terminal 1 connected to server 2 using information about its hardware layer and its operating system. When a terminal 1 changes its hardware layer and / or its operating system and then connects again to server 2, it thus generates a new entry in list I (a new set of identifiers different from the set generated during its previous connection).

[0064] Lookup Table II includes the associations between:

[0065] * Each pair of hardware layer identifier and operating system identifier B; C, and

[0066] *Configuration File D.

[0067] Thus, list I may include several sets of identifiers that differ from the identifier of terminal A but have the same hardware layer identifier B and the same operating system identifier C. In this case, lookup table II includes a single association between the pair of identifiers B; C and profile D. Thus, several different terminals with a common configuration are indirectly associated with the same profile D. This scenario effectively corresponds to a cluster of similar terminals that can be configured in a similar manner.

[0068] Now refer to [ Figure 2 ]and[ Figure 3 ]. The at least one terminal 1 and the server 2 are configured to coordinate with each other in order to perform operations. "Coordinate" is used to indicate that some operations are performed from the terminal 1 while other operations are performed from the server 2. Figure 2 ], according to the embodiment described, icons representing the terminal 1 and the server 2 are linked to operations in order to identify the element of the system from which each operation originates. However, for a better understanding, the operations performed are presented in chronological order, independent of the elements of the system in which they are performed. It is still easy to decompose the operations according to the elements of the system in which they are performed, as in [ Figure 3 ] in order to clearly define the method implemented by the terminal and the method implemented by the server, which are bound together in a way that they form a single overall inventive concept.

[0069] In the example described herein, initiating a communication session between Terminal 1 and Server 2 is the triggering factor for the operations described below. In other words, the configuration update is triggered by the connection between Terminal 1 and Server 2. Alternatively, other triggers may be provided, such as actions / operations performed by the user of Terminal 1 via its human-machine interface.

[0070] The method for which the terminal 1 and the server 2 are configured includes the operations described below.

[0071] The first operation 101 includes:

[0072] a. Sending a set of identifiers from the terminal to the server. The set of identifiers includes:

[0073] - identifier A1 of terminal 1,

[0074] - the hardware layer identifier B1 of the hardware layer of terminal 1, and

[0075] - operating system identifier C1 of the operating system implemented on the terminal 1 .

[0076] The set of identifiers A1 , B1 , C1 may be sent in the form of a response to a request sent by the server 2 , or may be initiated by the terminal 1 , for example contained in a request to update a configuration file or to establish or access a communication session.

[0077] Operation 102 includes:

[0078] b. After the server 2 receives the set of identifiers A1 , B1 , C1 from the terminal 1 , it compares it with the content of the database 3 .

[0079] Based on the comparison results, different operations are performed. Specifically:

[0080] i / In case of a match between the sent set of identifiers A1, B1, C1 and the set of identifiers in list I,

[0081] The communication session is continued without updating the configuration of terminal 1. In this case, terminal 1 in its current configuration is considered to have been previously connected to server 2 and its configuration file is therefore up to date: there is no need to update it again and the updating method can therefore be terminated and the communication session continues in a manner known per se.

[0082] ii / In case of a mismatch between the sent set of identifiers A1, B1, C1 and the set of identifiers in said list I,

[0083] And in case of a match with the hardware layer and operating system identifier pair B1, C1 in lookup table II,

[0084] Operation 103 described below is performed.

[0085] iii / Compare the hardware layer and operating system identifiers in lookup table II to B x ,C y In case of mismatch,

[0086] Operation 104 and operation 105 described below are performed.

[0087] Operation 103 includes:

[0088] In return, the configuration file D associated with the pair B1, C1 is sent from the server 2 to the terminal 1 according to the lookup table II. 1,1 This situation corresponds to the case of a terminal 1 that is connected to the server 2 for the first time, at least in its current configuration (since it has never been stored in the database 3 with the identifiers B1, C1). However, the presence of the identifier pair B1, C1 means that the profile D is presumably applicable to this type of configuration. 1,1 Available in database 3. This presence may be due to the operator previously implementing configuration file D on server 2 1,1 And / or for example caused by another terminal having the same configuration (B1 and C1) having previously implemented the method as described herein. It should therefore be understood that implementation of the method described herein by the first terminal thus benefits terminals having similar configurations.

[0089] At the conclusion of operation 103 , the method may continue by performing operations 106 and / or 107 described below.

[0090] Operation 104 includes:

[0091] In the lookup table II and by applying pre-established rules, the hardware layer and operating system identifier pair B that is closest to the identifier in the identifier set B1, C1 sent from terminal 1 is identified. x ,C y .

[0092] Construct a method for defining the identifier pair B closest to the sent identifier pair B1, C1 x ,C y The pre-established rules to make the corresponding profile D x,y The probability that the configuration of terminal 1 (B1, C1) is compatible with the configuration of terminal 1 is maximized, even if the configuration of terminal 1 is compatible with the configuration file D x,y The configurations targeted are not strictly identical. For example, the concept of proximity can be defined by applying a first rule that would have a common identifier B (B1 = B x ) are classified as pairs with a common identifier C(C1=C y ) are closer to each other, and pairs with a common identifier C are closer to each other than pairs with neither a common identifier B nor a common identifier C. The second rule can then rank pairs that achieve the same classification by applying the first rule (in a more fine-tuned way). x or C1 and C x ) corresponds to versions from the same developer / manufacturer and / or when their version numbers are close. As a visual example, a rule can be constructed so that a pair of identifiers B1 = "gadget_phone_13" and C1 = "eOS_13.4" is considered as being closest to each other compared to the pair of identifiers B x = "G_phone_4"; C y = "gOS_4.42" is closer to the identifier pair B x = "gadget_phone_13" and C y = "eOS_13.3". The construction of the rules can vary widely, but is still within the capabilities of those skilled in the art and depends on the context of use.

[0093] Alternatively, the pre-established rule may be basic, for example constructed to select the last pair of identifiers recorded in Table II by default.

[0094] At the end of operation 104, operation 105 is performed. Operation 105 includes:

[0095] In return, the server 2 sends to the terminal 1 the combination B identified according to the lookup table II (identified in operation 104). x ,C y Associated configuration file Dx,y .

[0096] In the example described herein, file D x,y Sent with an indicator or "tag" (here in the form of a reference "Z") that configures the profile D x,y , Z is marked as "provisional." In other words, the profile is identified as not yet verified / final. In other words, it is a "beta version" of the profile.

[0097] At the end of operation 105, operations 106 and / or 107-108 are performed. It should be noted here that operations 106 and 107-108 have no dependencies on each other. Therefore, they can be performed in parallel with each other, or one after another in a chronological order in one direction or the other.

[0098] Operation 106 includes:

[0099] c. Use the received identifier set A1, B1, C1 and the identifiers B1, C1, D x,y , any associations generated by Z populate database 3.

[0100] Adding the set of identifiers A1, B1, C1 to the list I is equivalent to recording the connection of the terminal 1 at the server 2. Therefore, if the terminal 1 reconnects to the server 2 later with the same configuration, the embodiment of the method of the invention will lead to the situation "i" described above: the process will terminate, so that the communication session continues without updating the configuration of the terminal 1. The association of the identifiers B1, C1, D1 is only made if this association has just been established (in the above situation "iii", not in the situation "ii"). x,y , Z are added to lookup table II. It should be noted that adding an association pointing to a "temporary" profile does not necessarily mean that this association is immediately accessible to future terminals connecting to server 2. This is a design choice that depends on the context: associations related to profiles marked as temporary and the corresponding profiles can be hidden or inaccessible to prevent the deployment of unverified profiles. Conversely, associations related to profiles marked as temporary and the corresponding profiles can be made accessible to other terminals, for example, to speed up deployment.

[0101] Operation 107 includes:

[0102] d. Receive configuration file D from server 2 on terminal 1 1,1 ;D x,y , Z, and finally, implement the configuration file in the front-end application (on terminal 1).

[0103] Through operation 107, applications installed on terminal 1 are not updated in this manner, but rather their interactions with the hardware layer of terminal 1 are corrected using the configuration file. For example, "raw" control signals from the hardware layer, such as those corresponding to actions performed by a user via the human-machine interface of terminal 1, are better recognized by the application and thus better translated into software input by the application. For example, in the context of PTT communication, pressing, holding, and then releasing a physical or virtual button is better recognized as a command for speaking mode.

[0104] At the end of operation 107, operation 108 is performed. Operation 108 includes:

[0105] If and only if the configuration file carries an indicator marking the file as temporary, the front-end application of terminal 1 is switched to test mode.Test mode allows a user to carry out control tests from his or her terminal without interfering with the functionality of other terminals.

[0106] At the end of operation 107 or 108, the method for updating the configuration can be considered terminated: the configuration file is in the process of being tested. If necessary, the user of terminal 1 can perform the test with the help of an operator. A guided test mode can be integrated into the application. For example, the user can follow instructions for interacting with the human-machine interface of terminal 1 so that a sequence of human actions can be recognized. For example, the user can be asked to simulate speaking in a PTT communication channel by pressing, holding, and then releasing a button (physical or virtual) of the terminal 1 selected by the user for a predefined duration (e.g., 3 seconds). The application's registration of control signals from the hardware layer of terminal 1 then allows the control signals to be associated with the correct action or event to be triggered by the software layer (application), i.e., the speaking mode in the above example. When operational, the same user actions will therefore be better "recognized" by the application.

[0107] The tests performed by the user are intended to verify whether the behavior / operation of the application is correct in order to validate or not validate the temporary profile. Optionally, the actions simulated by the user can be stored in order to help correct the temporary profile (if certain human actions do not generate the behavior expected by the application).

[0108] The following are examples of tested settings and functions that can be adapted with the help of configuration files:

[0109] - pressing a physical or virtual button, keeping said button pressed for one or more predetermined durations, and then releasing said button at the end of said durations, for example in correspondence with a talk mode in a PT communication channel, and then releasing said channel;

[0110] - a brief press of a (physical or virtual) button, or a series of presses on one or more (physical and / or virtual) buttons, e.g. to trigger a warning such as sending an "SOS";

[0111] - a brief press of a (physical or virtual) button, or a series of presses on one or more (physical and / or virtual) buttons, e.g. to change from one communication channel to another (a function often called "handover").

[0112] - Detecting and adapting to terminal 1 -specific properties related to the management of audio and / or video streams, in particular the delay resulting from the hardware configuration of the terminal 1 , said delay being a key parameter in real-time communications.

[0113] In the examples, buttons are mentioned. However, interface alternatives may be provided, such as movement on a touch screen.

[0114] If the user validates the temporary profile by action via the human-machine interface of the terminal 1 (“OK”), the updating process can continue, for example, by implementing an operation 109 described below.

[0115] If, on the other hand, the user does not validate the temporary file by a specific action or by a lack of action within a predetermined time period, a signal of invalidation of the configuration file ("NOK") may be sent from the terminal 1 to the server 2. Preferably, the invalidation signal is accompanied by data from the test carried out by the user in the test mode. Such data may include, for example:

[0116] - the association between commands from the hardware layer of the terminal 1 and the expected behavior of the application; and / or

[0117] - A modified configuration file (partial or complete) determined by the backend of the application itself.

[0118] Depending on the nature of the correction data sent by terminal 1 to server 2 , the corrected profile may be generated automatically (by running the correction module of server 2 without human intervention) or may be created by a human operator accessing the correction data received on server 2 .

[0119] The corrected configuration file remains marked as "temporary" (in [ Figure 3 ] is represented as D' x,y , Z), and can:

[0120] - sent back to Terminal 1 to repeat the test to confirm its validity; and / or

[0121] - Added to database 3, replacing the previous version of the profile, so that it is accessible at least by terminal 1 and optionally by other terminals. In the example described herein, the corrected profile remains marked as "provisional" until manually verified by an operator. Other verification rules may be implemented, such as verification based on a minimum number of users.

[0122] Operation 109 includes:

[0123] e. In response to a predetermined verification action performed by the user via terminal 1,

[0124] The indicator marking the file as provisional is removed on terminal 1. In other words, the configuration file becomes definitive / final at the initiative of the user of terminal 1.

[0125] Operation 110 includes:

[0126] Switch the front-end application to normal mode. In other words, the temporary test mode is deactivated. The application returns to normal operation and is in operational mode.

[0127] Operation 111 includes:

[0128] A command for verifying the temporary profile is sent from the terminal 1 to the server 2 .

[0129] It should be noted that operations 109 , 110 , and 111 are independent and, therefore, may be performed in parallel with each other or one after the other in any order.

[0130] Operation 112 includes:

[0131] f. After the server 2 receives the command to verify the temporary profile from the terminal 1 (eg, after the implementation of operation 111), the corresponding associations B1, C1, D in the database 3 x,y , Z removes the indicator marking the file as temporary. Operation 112 may correspond to making the associated and corresponding configuration files available from the server 2 to other terminals 1. In the example described herein, operation 112 marks the end of the method for updating a configuration file.

[0132] Industrial Applications

[0133] The method for updating the configuration has been presented as being implemented by the terminal 1 and the server 2. It will be understood that the method may take the form of a computer program comprising instructions for implementing the method when these programs are executed by a processor of the terminal 1 or the server 2, respectively. Another object is also a non-transitory computer-readable storage medium having stored thereon a program for implementing the method described herein when these programs are executed by a processor.

[0134] The technical solution of the present invention can be applied in particular in the context of applications for maintaining computer devices. It is particularly advantageous when applied to applications for half-duplex communication via mobile phone networks, in particular because of the wide variety of firmware in circulation in mobile terminals and because the interaction between the user and the terminal in this field is specific (for example, long pressing and releasing a button to speak in a communication channel, then switching to listening mode).

[0135] The present disclosure is not limited to the examples of systems, terminals, servers, methods, programs and program media described above merely as examples, but encompasses all variants that a person skilled in the art can envisage within the context of the protection sought.

[0136] Reference Signs List

[0137] -1: Terminal

[0138] -2: Server

[0139] -3: Database

[0140] -101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112: Operation

[0141] -I: list

[0142] -II: Lookup table -A: Terminal identifier -B: Hardware layer identifier -C: Operating system identifier -D: Configuration file -Z: Temporary file label.

Claims

1. A system comprising at least one terminal (1) and a server (2) capable of communicating with each other, a back-end application and a corresponding front-end application being installed on the server and the terminal respectively, the server being capable of accessing at least one database (3), the database comprising: - a list of identifier sets (I), each identifier set comprising *Terminal identifier (A), * Hardware layer identifier (B), and * Operating system identifier (C); - Lookup table (II) mapping between the following two * Each pair of hardware layer identifier and operating system identifier (B x ; C y ),as well as * A configuration file stored in the at least one database (D x,y ) When a communication session is opened between the terminal and the server, the terminal and the server are configured to perform the following operations in coordination with each other: a. sending (101) an identifier set from the terminal to the server, the identifier set comprising a terminal identifier (A1), a hardware layer identifier (B1) of a hardware layer of the terminal, and an operating system identifier (C1) of an operating system implemented on the terminal; b. After the server receives the set of identifiers (A1, B1, C1) from the terminal, it compares this set with the content of the database (102), and - in case of a match between the set of identifiers (A1, B1, C1) sent and the set of identifiers in the list (I), continuing the communication session without updating the configuration of the terminal; - in case of no match between the set of identifiers (A1, B1, C1) sent and the set of identifiers in the list (I), and in case of a match with a pair of hardware layer and operating system identifiers (B1, C1) in the lookup table (II), In return, the configuration file (D) associated with the pair (B1, C1) in the look-up table is sent (103) from the server to the terminal. 1,1 ); - a pair of hardware layer and operating system identifier (B) in the lookup table (II) x ,C y ) do not match, identifying (104) in the lookup table (II) and by applying pre-established rules a pair of hardware layer and operating system identifiers (B1, C1) that is closest to an identifier in the set of identifiers (B1, C1) sent from the terminal x ,C y ), and then in return, the server sends (105) to the terminal a combination (B) identified according to the lookup table (II). x ,C y ) associated with the configuration file (D x,y ), the file is the configuration file (D x,y , Z) is sent with an indicator (Z) marked as temporary; c. Using the received set of identifiers (A1, B1, C1) and the identifiers (B1, C1, D x,y , Z) populating (106) the database with any resulting associations; d. receiving a configuration file from the server at the terminal (D 1,1 ;D x,y , Z), implementing (107) the configuration file in the front-end application, and The front-end application is switched (108) to a test mode if and only if the configuration file carries an indicator (Z) marking the file as temporary.

2. The system according to claim 1, characterized in that The terminal and the server are further configured to: e. in response to a predetermined verification action performed by the user via the terminal, deleting (109) on said terminal the indicator (Z) marking said file as temporary, Switching (110) the front-end application to a normal mode, Sending (111) a command to verify the temporary configuration file from the terminal to the server; f. After the server receives the command to verify the temporary configuration file from the terminal, the corresponding association (B1, C1, D x,y , Z) and delete (112) an indicator (Z) marking the file as temporary.

3. A configuration method implemented by a terminal (1) capable of communicating with a server (2), a back-end application and a corresponding front-end application being installed on the server and the terminal respectively, the server being capable of accessing at least one database (3), the database comprising: - a list of identifier sets (I), each identifier set comprising *Terminal identifier (A), * Hardware layer identifier (B), and * Operating system identifier (C); - Lookup table (II) mapping between the following two * Each pair of hardware layer identifier and operating system identifier (B x ; C y ),as well as * A configuration file (Dx,y) stored in the at least one database The method comprises, after a communication session is opened between the terminal and the server: a. sending (101) an identifier set from the terminal to the server, the identifier set comprising a terminal identifier (A1), a hardware layer identifier (B1) of a hardware layer of the terminal, and an operating system identifier (C1) of an operating system implemented on the terminal; d. receiving a configuration file from the server at the terminal (D 1,1 ;D x,y , Z), implementing (107) the configuration file in the front-end application, and The front-end application is switched (108) to a test mode if and only if the configuration file carries an indicator (Z) marking the file as temporary.

4. The method according to claim 3, further comprising: e. in response to a predetermined verification action performed by the user via the terminal, deleting (109) on said terminal the indicator (Z) marking said file as temporary, Switching (110) the front-end application to a normal mode, A command to verify the temporary configuration file is sent (111) from the terminal to the server.

5. A configuration method implemented by a server (2) capable of communicating with at least one terminal (1), a back-end application and a corresponding front-end application being installed on the server and the terminal respectively, the server being capable of accessing at least one database (3), the database comprising: - a list of identifier sets (I), each identifier set comprising *Terminal identifier (A), * Hardware layer identifier (B), and * Operating system identifier (C); - Lookup table (II) mapping between the following two * Each pair of hardware layer identifier and operating system identifier (B x ; C y ),as well as * A configuration file stored in the at least one database (D x,y ) The method comprises, after a communication session is opened between the terminal and the server: b. After the server receives the set of identifiers (A1, B1, C1) from the terminal, it compares this set with the content of the database (102), and - in the event of a match between the set of identifiers (A1, B1, C1) sent and the set of identifiers in the list (I), continuing the communication session without updating the configuration of the terminal; - in case of no match between the set of identifiers (A1, B1, C1) sent and the set of identifiers in the list (I), and in case of a match with a pair of hardware layer and operating system identifiers (B1, C1) in the lookup table (II), In return, the configuration file (D) associated with the pair (B1, C1) in the look-up table is sent (103) from the server to the terminal. 1,1 ); - a pair of hardware layer and operating system identifier (B) in the lookup table (II) x ,C y ) do not match, identifying (104) in the lookup table (II) and by applying pre-established rules a pair of hardware layer and operating system identifiers (B1, C1) that is closest to an identifier in the set of identifiers (B1, C1) sent from the terminal x ,C y ), and then in return, the server sends (105) to the terminal a combination (B) identified according to the lookup table (II). x ,C) the configuration file associated with (D x,y ), the file is the configuration file (D x,y , Z) is sent with an indicator (Z) marked as temporary; c. Using the received set of identifiers (A1, B1, C1) and the identifiers (B1, C1, D x,y , Z) populates (106) the database with any associations generated.

6. The method according to claim 5, further comprising: f. After the server receives a command from the terminal to verify the temporary configuration file, the corresponding association (B1, C1, D x,y , Z) and delete (112) an indicator (Z) marking the file as temporary.

7. A terminal (1) configured to implement the method according to any one of claims 3 to 4.

8. A server (2) configured to implement the method according to any one of claims 5 to 6.

9. A computer program comprising instructions for implementing the method according to any one of claims 3 to 6 when this program is executed by a processor. 10 . A non-transitory computer-readable storage medium having a program stored therein, the program being configured to implement the method according to claim 3 when the program is executed by a processor.