FR2822563A1 - Method for saving and restoring platform configuration parameters on a server, uses program sent by server to analyze platform, which returns data to server to prepare program used by platform to save configuration and send to server - Google Patents

Abstract

The configuration data is saved on an Internet/intranet server, using a save request to the server to initiate sending of data to the platform to analyze the platform. The analysis results are returned to the server and the data prepared for saving on the server. The prepared data is sent to the platform, which saves the configuration data, then transmits it to the server for storage.

Description

<Desc / Clms Page number 1>

The subject of the present invention is a method for saving and restoring all of the configuration parameters of a computer platform, for example a personal computer or a fleet of computers, by means of a server for example. an Intranet or Internet server. It concerns both the configuration of the platform's operating system and that of specialized software (word processors, spreadsheets, Internet browsers, email managers, etc.) installed on this platform.

The method which is the subject of the invention has the property of being independent of the operating system used by the platform whose configuration is saved, this configuration being able to be restored on machines equipped with a different operating system. Similarly, the software configuration parameters can be restored to different software programs which may have similar functionalities. The method also offers the possibility of carrying out all the operations of modification, insertion or deletion of the saved configurations and of protecting their confidentiality.

The invention applies in particular, but not exclusively, to the recovery of its configuration by a user forced to change platform, to the

<Desc / Clms Page number 2>

 standardization of configurations on a fleet of computers or even reinstallation after replacing hardware. Some partial solutions to the problem of recording and repeating computer configurations are already known, either by the choice of hardware or by software tools.

Among the hardware solutions, we can cite the laptop, which meets the need to transport a configuration, but not that of its repetition. It also has the known drawbacks of a relatively high cost and limited ergonomics. The network computer brings standardization by nature within the network, the system and software configuration being centralized in the main server. But we know the speed limits of networks, which can hardly be used for example for the animation of complex graphic objects.

Many software on the market also provide partial facilities for saving and reproducing user configurations.

A first family of software [ref: "Webshot", "Stardock"] only facilitate the personalization of the computer, only at the level of the configuration of the screen.

In a second category, we find software that allows you to locally create and save only the ergonomics of the desktop [ref: "Desktop Architect"].

Another software group offers the deployment to all computers of the same fleet of a single system configuration [ref: "RapidDeploy"].

<Desc / Clms Page number 3>

There are also software [ref: "User Roaming Profile"] whose function is to transfer the user configuration profile to a local server.

Such a solution does not manage the case of a non-homogeneous fleet of computers, nor that of a change of operating system or a reinstallation.

Other solutions propose saving files on an Internet site [ref: "Visto. Com"]. In this approach, as with the previously mentioned software, it is clear that the system configuration itself is not saved and therefore cannot be restored.

Another type of service offered on the Internet uses the procedure called "Application Service Provider" (ASP) in which application software is transferred to the server site [ref: "webos. Com"]. In this solution, the configuration of remote software is well standardized for all users, but the possibilities for customization are very limited.

Finally, we can cite specialized software for saving on the Internet the complete configuration of a single tool or set of software tools, "Office 2000" for example [ref: "Save My Settings Wizard"]. This service obviously does not concern the system configuration or that of other software.

The present invention therefore aims to eliminate these drawbacks and limitations, and to offer a general means of backing up and restoring all of the configuration parameters of an IT platform and user preferences, as well as operating system level as specialized software, with the essential property of allowing the recovery of this configuration on a system or software different from those from which the backup was made.

<Desc / Clms Page number 4>

- la préparation par le serveur des données pour sauvegarder la configuration de la plateforme et la transmission à la plateforme des données pour sauvegarder la configuration de la plateforme, - la sauvegarde par la plateforme des données de configuration de la plateforme et la transmission de ces données au serveur,

- la conversion des données de configuration de la plateforme puis la sauvegarde par le serveur de ces données. To this end, it proposes a method for saving and restoring the configuration of a computer platform such as, for example, a computer, by connection to a server, for example an Internet / Intranet server, this method comprising a phase of backup comprising: the request to save the platform on a server, - the acceptance of the request by the server and the transmission by the server to the data platform to analyze the platform, - the internal analysis of the platform from data transmitted by the server and the transmission to the server of the results of the analysis,

- the preparation by the server of the data to save the configuration of the platform and the transmission to the platform of the data to save the configuration of the platform, - the saving by the platform of the configuration configuration data and the transmission of this data to the server,

- the conversion of the platform configuration data then the backup by the server of this data.

This process may also include a phase of restoring the configuration data saved by the server site on the requesting platform, possibly separate from the aforementioned platform, this phase of restoration comprising the following steps: - the request for restoration sent by the requesting platform to destination of the server, - acceptance of the request by the server site and transmission by the latter to the requesting platform, of analysis data, - internal analysis of the platform using the analysis data and the transmission by the platform to the server of the results of the analysis,

<Desc / Clms Page number 5>

- la conversion par le serveur, en fonction de ces résultats, des données pour la restauration de la configuration de la plateforme et la transmission par le serveur de ces données à la plateforme, - la restauration de la configuration sur la plateforme.

- the conversion by the server, according to these results, of the data for the restoration of the configuration of the platform and the transmission by the server of this data to the platform, - the restoration of the configuration on the platform.

Advantageously, the application for backing up and restoring configurations can be offered to users in the form of an ASP procedure on the Internet or on the Intranet (defined above). Such a choice has the following advantages: - elimination of installation and deployment operations in the case of sites with several platforms, since there is no specific software to be installed on the user's machine; - absence of incompatibility with the already installed software and absence of power or capacity problems, the application object of the invention being executed on the server site; - centralized updates of the application, necessary when new software versions appear on the market, without any user intervention; - elimination of the risks of copying the application; - savings for the ASP supplier of distribution and installation support costs.

In this solution, the method according to the invention comprises at least, in general, the following subsets, which are therefore all installed on the site of the server: - a Database, preferably on the relational model, including the different parts are: - an Application Base, containing the data necessary for the proper functioning of the application, - a General Public Base, relating to information on the users of the application,

<Desc / Clms Page number 6>

- un Serveur Applicatif, assurant l'ensemble des fonctions de connexion des utilisateurs, de sauvegarde et de restauration des configurations ; - une Appliquette ou applet (petit programme intégré dans une page HTML et qui accomplit une fonction), préférentiellement programmée en langage
JAVA, téléchargée sur l'ordinateur de l'utilisateur lors de la connexion, qui sera dénommée AP par commodité dans la suite de la description. - a Company Database, providing commercial information related to its use; (The two databases, General Public and Enterprise, manage user configurations, the Enterprise Database having a supplement for the administration of employee configurations for companies); - an Interface (Web server using the HTTP protocol), managing the interactions between the different subsets of the application;

- an Application Server, ensuring all the functions for connecting users, saving and restoring configurations; - an Appliquette or applet (small program integrated into an HTML page and which performs a function), preferably programmed in language
JAVA, downloaded on the computer of the user during the connection, which will be called AP for convenience in the rest of the description.

The Application Server and the Applet use a tree model, in which each tree is defined by a root and can contain a list of dependent trees. Inside each tree, the data is organized into a chain, a system of pointers allowing access to the element contained in a link in the chain, or else to move to the next link or the previous link. Associated functions allow you to insert or destroy trees or elements.

The operation of the Application Server implements a listening "socket" (channel) which remains pending a connection request. It receives a request from the Server which previously identified the user (by verifying its password) and then associates with this user one of its "sockets". The "Login" process on the Web server has indeed initialized a User Object. This performs the processing requested by the request step by step. This Object is put into action thanks to a set of Execution Units ("threads") associated with the "socket".

<Desc / Clms Page number 7>

 These Execution Units are normally dormant and returned to the active state by the responses to the read or write operations requested by the User Object. They then send the latter the order to continue the treatment until the requested result is obtained. Verification devices for exceeding the limited durations make it possible to eliminate unsuccessful connections.

Preferably, the data will be encrypted in RSA.

The unencrypted part of the requests (data) will be hidden.

The detailed operation of the User Object calls on the following general concepts: - a Module includes all the parameters of a given operating system or specialized software; during the preparatory phase of a backup or restore procedure, before receiving the values of the parameters concerned; - a Pre-module is a set of minimal data characterizing the
Module; - a Package includes all the Modules of the same software family (Word Processing for example); - a Configuration is the set of Packages for a user.

In the case of Backup, the operating mechanism of the User Object according to the invention comprises at least the following steps: - Connection * recovery of the request from the AP * recovery in the Base of the Packages concerned and of the Analysis Tool * generation of the Analysis Tool

<Desc / Clms Page number 8>

* récupération d'une demande de Module venant de l'AP * envoi vers l'AP de tous les Modules en attente - Réception * récupération d'un Module en provenance de l'AP * acquittement de cette réception * utilisation des moyens de conversion pour reformer un Paquet * envoi du Paquet reconstitué à la Base * reprise au début de la Réception jusqu'à ce que tous les Modules soient reçus * send the Analysis Tool to the user via the AP - Analysis * retrieve the Analysis Tool returned by the AP * if the Analysis Tool indicates the presence of two Modules at least belonging to the same Package: - generation of the Choice of Modules (whose role is the recovery of the names of Modules) - sending of the Choice of Modules to the AP * recovery in the Base of the corresponding Pre-modules with the means of associated conversion * sending of these Pre-modules to the AP - Processing * recovery of a Pre-module from the AP * sending of an acknowledgment of this reception to the AP * if all the Modules have been processed , passage to the Sending stage * generation of the Module processed * resumed at the start of the Processing - Sending

* recovery of a Module request from the AP * sending to the AP of all pending Modules - Reception * recovery of a Module from the AP * acknowledgment of this reception * use of conversion means to reform a Package * send the reconstituted Package to the Base * resumed at the start of Reception until all the Modules are received

<Desc / Clms Page number 9>

* récupération d'un Pré-module à partir de l'AP * envoi d'un acquittement de cette réception vers l'AP * si tous les Modules ont été traités, passage à l'étape d'Envoi * génération du Module traité * reprise au début du Traitement - Envoi * récupération d'une demande de Module venant de l'AP * envoi vers l'AP de tous les Modules en attente - Fin de la procédure - End of the procedure A similar mechanism, according to the invention, is used for the Restoration. It includes at least the following phases: - Connection * recovery of the request from the AP * recovery in the Base of the Packages concerned and the Analysis Tool * generation of the Analysis Tool * sending of the 'Analysis tool towards the user via the AP - Analysis * recovery of the Analysis Tool returned by the AP * recovery in the Base of the corresponding Pre-modules with the associated conversion means * sending of these Pre-modules to the AP - Processing

* recovery of a Pre-module from the AP * sending an acknowledgment of this reception to the AP * if all the Modules have been processed, go to the Sending step * generation of the Module processed * resumption at the start of Processing - Sending * retrieving a Module request from the AP * sending to the AP all the modules on hold - End of the procedure

<Desc / Clms Page number 10>

 In all transfers between the User, the Server and the Database of information necessary for the implementation of the invention, it is advantageous to use a method of serializing the different objects, so as to obtain a flow of easily transferable data.

In this approach, each transmitted object is represented by a series of formatted bytes, which successively comprises: - a start byte, - a class identifier, which defines the class to which the object belongs, - the data area itself , - an end byte.

The start and end bytes are redundancies intended to ensure data integrity.

The different object classes can be, in a non-exhaustive manner: - tree, - main tree, - main root, - main root with identifier, - absolute parameter root, - user parameter root, - command root (whose content corresponds to orders to be executed), - identifier root, - identifier root with value, - external root, - action root for the Server, - action root for the User.

<Desc / Clms Page number 11>

 The length and format of the data string contained in the serialized object depend of course on the class to which the object belongs. After transmission, each object is de-serialized before being used, the reading of the class identifier allowing the interpretation of the data area.

According to the invention, the data exchanges between the AP, which provides the interface function with the User, and the Application Server, which performs the requested processing, will preferably be carried out by integrating the data flow in an HTTP protocol . This choice has, among other things, the advantage of allowing the crossing of any fire walls that may be installed on the Server site.

In this perspective, the exchanges between the AP and the Server will essentially take the form of sending requests by the AP, to which actions executed by the Server respond, which returns the resulting data.

- le nombre d'itérations, qui détermine le numéro des connexions simultanées pour un même utilisateur ; - l'en-tête de requête, qui contient l'indication du type (normal ou requête d'erreur) et de la nature de la requête ; - les données nécessaires pour effectuer la requête. The requests issued by the AP will advantageously respond to a format made up of four blocks: - the HTTP header, which can have a form adapted to the format of the following blocks; - the user identifier, encrypted according to the algorithm mentioned above and which itself comprises four parts: - the identifier of the key to be used to decrypt the identity, - the indication of the dimension of the encrypted part, - the actual user identifier,

- the number of iterations, which determines the number of simultaneous connections for the same user; - the request header, which contains the indication of the type (normal or error request) and the nature of the request; - the data necessary to make the request.

<Desc / Clms Page number 12>

The response of the Server to a request may include similarly: - the HTTP header; - the response header, which contains the indication of the type (normal or error case) and the nature of the response; - the response data.

This dialogue can advantageously be associated with the management of a maximum number of errors, beyond which the response from the Server signals a next disconnection.

The communication protocol between the Web Server and the Application Server will include at least connection requests sent by the Web Server, which do not require encryption, and their response by the Application Server.

The function of the Web Server itself is to receive the connection request from the user, with his password. After validation, a Script procedure (text file containing a set of instructions intended to be executed by a script interpreter, this procedure using a DAL dynamic function library) is executed, which allows to: - authenticate the user thanks to the Application Server, - read the data concerning it, - display this information in tree form, offer the user a selection in this tree and the choice of the function to be executed (Backup or Restore).

The AP makes a request, the corresponding parameters are then transmitted to the AP, which performs its processing and manages its data exchanges with the Application Server autonomously, only the processing progress being visible to the user.

<Desc / Clms Page number 13>

The function of the AP itself is to save or restore Modules on the user's workstation. To do this, its execution is controlled by two Execution Units (threads): the main ensures data processing, the other the connection with the Server.

The main execution process, taking into account the functioning according to the invention of the User Object described above, will include at least in the case of the Backup the following steps: - generation and sending to the Server of the options chosen by the user ; - reception of Analysis Tools; - analysis of the platform and return of the Analysis Tools; - in the event of the presence of several Modules in the same Package, receipt of the Choice of Modules, acquisition of the user's choices and return to
Server ; - reception of the Pre-modules; - Module by Module, reading of the current parameters and sending back to the Server
Module evaluated; - when all the Modules are returned, request to the Server to ensure that the procedure has ended correctly.

During a Restoration, the process will follow as follows: - generation and sending to the Server of the options chosen by the user; - reception of Analysis Tools; - reading of the current parameters and return of the Analysis Tools; - reception of the Pre-modules; - Module by Module, reading the current parameters, sending back to the Server
Valued module, reception of the Module to restore and restoration; - end of task signaling to the Server and acknowledgment.

<Desc / Clms Page number 14>

- la restauration d'une Configuration sélectionnée, - la suppression d'une Configuration, - le partage d'une Configuration avec un ou plusieurs autres intemautes, - le changement de nom d'une Configuration, - l'envoi d'une Configuration vers une Communauté, dont les fonctionnalités sont décrites plus loin ; - les mêmes possibilités de manipulation au niveau d'un seul Paquet, seule la possibilité de renommer un Paquet étant exclue ; - la possibilité d'annuler la dernière restauration effectuée, et donc de rétablir la Configuration initiale ; - la constitution d'une Communauté de Configurations, au sein de laquelle l'utilisateur peut au moins : - restaurer sur son poste une Configuration de la Communauté, - se constituer un Panier de Configurations préférentielles, qui peuvent être restaurées sur son poste, - sauvegarder une Configuration de la Communauté vers son compte, - ajouter ou supprimer un partage avec un ou plusieurs autres intemautes de son choix ; The functionalities offered to the user on the website may include, without limitation, from a home page: - the identification and registration functions of the user, who can therefore, after having indicated his personal details, open an account on the site; - access to the Configurations already saved in the user's account, on which the possible manipulations will include at least: - saving the current Configuration,

- restoring a selected Configuration, - deleting a Configuration, - sharing a Configuration with one or more other Internet users, - changing the name of a Configuration, - sending a Configuration to a Community, the functionalities of which are described below; - the same possibilities of manipulation at the level of a single Package, only the possibility of renaming a Package being excluded; - the possibility of canceling the last restoration carried out, and therefore restoring the initial configuration; - the constitution of a Community of Configurations, within which the user can at least: - restore on his station a Community Configuration, - constitute a Basket of preferential Configurations, which can be restored on his station, - save a Community Configuration to his account, - add or delete a share with one or more other Internet users of his choice;

<Desc / Clms Page number 15>

 - all the aids and explanations necessary for using the process which is the subject of the invention, as well as for creating and updating the Configurations.

The process according to the invention is illustrated by the appended drawings in which:
FIG. 1 gives the general architecture of the method according to the invention;
Figure 2 is the block diagram of a Backup procedure;
Figure 3 is the block diagram of a Restoration procedure;
Figure 4 gives the operating principle of the User Object;
FIG. 5 represents the diagram of states of the User Object during a backup;
FIG. 6 represents the same diagram in the case of restoration;
Figure 7 illustrates the general format of a serialized object;
FIG. 8 gives the format of the requests sent by the AP to the server;
Figure 9 shows the format of responses to requests returned by the server.

In FIG. 1 are represented the main sub-assemblies forming the general architecture of the method according to the invention: the Database 1 communicates through the Interface 2 with the Web Server 3 and the Server

<Desc / Clms Page number 16>

 Application 4. The Web Server 3 and the Application Server 4 exchange information with the Appliquette (AP) 5 downloaded on the platform, here the user's computer.

The functional diagram in Figure 2 represents the circulation of the Pre-modules and Configuration Modules between the Database, the Server and the User during a Backup procedure: the Pre-modules are transmitted to the AP on the user's computer, where the choice of Modules to be saved is made; the selected Pre-modules are sent back to the Server which constitutes the data block of the Modules to be saved before returning them to the AP where the current configuration parameters are integrated into the Modules; the Modules are finally sent again to the Server, which performs the reconversion operations necessary for the reconstitution of the Packages concerned, before replacing them in the Database; at each movement of a Pre-module or a Module, the corresponding data are serialized at the start and de-serialized at the finish.

Similarly, the functional diagram of Figure 3 shows the processing of Pre-modules and Modules during a Restoration procedure: the Pre-modules are extracted from the Database and transmitted to the AP where s 'operates the selection; the Pre-modules concerned are returned to the Server, which performs the conversions necessary to reform the Package to be restored with the parameters extracted from the Database, before returning this Package to the AP, which proceeds with the restoration.

FIG. 4 illustrates the operation of the User Object on the Server under the action of the Execution Units: each time that the User Object 6 requests a data input (read) or output (write) operation at port 7 corresponding to the input / output socket, the return of the acknowledgment of this operation by the port is detected by one of the dormant execution units 8, which then goes into action to give the User object the order of

<Desc / Clms Page number 17>

continue treatment, and so on until the completion of the procedure. On the state diagram of FIG. 5 are represented the successive states of the User Object during a Backup procedure: -the state ES0 (Connection) lasts until the sending of the Analysis Tools; - the ES 1 (Analysis) state which follows is maintained until the Pre-modules are sent; - in the case where a choice of Modules is necessary, the ES1 state ends with the sending of the Choice of Modules and leaves room for an intermediate state
ES until sending the Pre-modules; - the next state ES2 (Processing) ends when the last Module has been processed and the procedure ends with the state ES3 (End).

During a Restoration procedure, the successive states of the User Object appear in Figure 6: the ERO (Connection), ER1 (Analysis) and ER2 (Processing) states are similar to the ESO, ES1 and ES2 states respectively in the Backup case; the following state ER3 (Sending of Modules) is maintained until the transmission of the last Module, before giving way to state ER4 (End).

FIG. 7 represents the general format of the serialized objects transmitted between the Server and the AP. Each object is successively formed from: - a start byte OD, - the identifier of the class to which the IC object belongs, - the object data, whose format and length depend on the class, - a OF end byte.

Figure 8 shows the format of requests sent by the AP to the Server. This format successively includes: - the HTTP header;

<Desc / Clms Page number 18>

- l'identifiant de l'utilisateur IU, crypté selon l'algorithme RSA et qui comporte lui-même quatre parties : l'identifiant de la clé à utiliser pour le décryptage IDC, la taille totale de la zone cryptée, l'identifiant de l'utilisateur lui-même IDU et le nombre d'itérations NBI ; - l'en-tête de requête ETR, qui comporte deux parties : le type TR (normal ou erreur) et la nature de la requête NR ; - les données nécessaires au traitement de la requête.

- the identifier of the user UI, encrypted according to the RSA algorithm and which itself comprises four parts: the identifier of the key to be used for IDC decryption, the total size of the encrypted area, the identifier of the user himself IDU and the number of NBI iterations; - the ETR request header, which has two parts: the TR type (normal or error) and the nature of the NR request; - the data necessary for processing the request.

Finally, Figure 9 gives the format of the Server response to a request, which includes: - the HTTP header; - the response header, the format of which is identical to that of the request header; - the response data.

Claims (9)

1. Method for backing up and restoring the configuration of an IT platform by connection to an Internet or Intranet site, this process requiring no prior installation on the platform concerned of software specialized in these backup or restoration tasks , characterized in that it comprises a backup phase comprising the following operational phases: - the request to save the platform on an Internet server site or Intranet, - acceptance of the request by the server and transmission by the server to the data platform to analyze the platform, - internal analysis of the platform from the data transmitted by the server and the transmission to the server of results of the analysis,

 - the preparation by the server of the data to save the configuration of the station and the transmission to the platform of the data to save the configuration of the platform, - the saving by the platform of the configuration configuration data and the transmission of this data to the server, - the conversion of the platform configuration data then the backup by the server of this data.  2. Method according to claim 1, characterized in that it comprises a phase of restoration of the configuration data saved by the server site on the requesting platform possibly separate from the aforementioned platform, this phase of restoration comprising the following steps: <Desc / Clms Page number 20>  the restoration request sent by the requesting platform to the server, the acceptance of the request by the server site and the transmission by the latter to the requesting platform, of analysis data, the internal analysis of the platform at using the analysis data and the transmission by the platform to the server of the results of the analysis, the conversion by the server, according to these results, of the data for restoring the configuration of the platform and the transmission by the server of this data to the platform, restoring the configuration on the platform.  3. Method according to claim 1, characterized in that it comprises at least the following sub-assemblies installed on the site of the server: - a Database, containing the saved configurations and the other data necessary for the operation of the application ; - an Interface, ensuring the connections between the different sub-assemblies; - an Application Server, which controls all configuration backup and restore operations; - a Web Server, managing user connections and the interface User; - an Appliquette, downloaded to the user's platform and carrying out internal processing for the acquisition or implementation of configuration parameters.  4. Method according to one of the preceding claims, characterized in that the configuration saved or restored comprises the configuration of the operating system used by the platform and / or the configuration of the specialized software installed on this platform. <Desc / Clms Page number 21>  5. Method according to claim 4, characterized in that the aforesaid specialized software consists of Word processors, Spreadsheets, Internet browsers or E-mail managers.  6. Method according to claim 4, characterized in that, if one designates by Module the set of parameters of a given software, the Modules of the same family of specialized software and the Modules relating to the operating systems are grouped in a Package assigned to this family, which allows, thanks to a prior analysis, to restore the configuration of a software saved from another software of the same family.  7. Method according to one of the preceding claims, characterized in that a local prior backup operation is carried out prior to a restore operation, thus making it possible to cancel the restore operation and restore the original configuration.  8. Method according to one of claims 1 and 2, characterized in that all the information circulating between the user platform and the server is coded in a serialized format, so that it can be transmitted using standard protocols.  9. Method according to one of the preceding claims, characterized in that it comprises facilities for adding, deleting, modifying, sharing, and / or sharing the saved configurations.