EP1818822A1 - Method and server for the distribution of software components, and update method and corresponding terminal und computer program products - Google Patents

Abstract

The method involves identifying a software component that belongs to a set of software components corresponding to a service subscribed by a programmable terminal. Difference between versions of the software component and another software component that belongs to another set of software components previously installed in the programmable terminal is determined. The latter software component is replaced by the former software component when the former software component is in older version. Independent claims are also included for the following: (1) a system for distributing a software component (2) a terminal comprising a unit for updating a software component (3) a computer program product downloaded from a communication network and executable by a microprocessor comprising program code instructions for implementing software component distributing method.

Description

1. Field of the invention

The present invention is particularly intended for software component management applications.

More specifically, the invention relates to the management of software components and versions of these components on programmable terminals.

The invention particularly relates to the field of updating software on computers, mobile phones, PDAs, STBs "Set Top Box" for "Digital Interactive Terminal" and more generally, any programmable terminal having a access to a communication network or device for updating software.

The growth in household equipment, both in terms of the number of personal computers and the number of Internet connections, has increased the exchange of data between users and produced a large software installations on the programmable terminals of these users. However, a large majority of these users are not part of the IT professionals. For these people, installing and updating software can become problematic.

2. Solutions of the prior art 2.1. Prior art

Most current programmable terminals offer the possibility of installing software components: computer applications, games, device management software. However, the installation of these components is interactive and requires some skills on the part of users. The installation of these components is done according to established principles such as component adaptation to the terminal, automatic component installation, use of boot zones or file manifests, and software version management. These notions are explained later.

2.1.1. Terminal adaptation

In the current state of knowledge, the process of downloading and installing software components makes it possible to adapt the components to the technical possibilities of the target terminal equipment. For example, the installation of software for controlling a graphics card.

2.1.2 Semi-automatic installation

Certain methods for taking into account a new subset also allow the installation during an operating state of the equipment and with automatic recognition of the components and their installation almost without user intervention, for example the "plug-in". -play "(" connect and play ") some operating systems.

2.1.3. "Primer"

Many programmable devices use a "bootstrap" concept: a minimal program element that initiates a boot process. The action of this "bootstrap" consists of checking a presence, downloading if necessary, and then starting the execution of a next software component in the boot process. This first step makes it possible to obtain, modify and install other software components automatically, the bootstrap being however not modifiable automatically.

2.1.4. "Manifesto"

Other methods also use a notion of "Manifest"("Manifest" in English) which is a list of files constituting an application. This "manifest" is downloaded first so that you know what to download next. Programmable equipment will only download files that have not already been downloaded. This operating mode makes it possible to share certain files between applications.

2.1.5. versions

When broadcasting a component that relies on other components, dependencies between the evolutions of each of the components constitute a major difficulty when interactions between components are modified.

Many of today's software programs are based on a development principle linked to an "API" (abbreviation for "Application Programming Interface"), which defines a set of routines, protocols and tools for developing applications. application software. A good API makes it easier to develop a program by providing all the blocks for building applications. A programmer then assembles these blocks.

Thus, for an API change all the components based on this API must be modified. In general, this problem is solved by a version number management system for each component. The version number of a component is incremented each time the component is changed. If this component uses other components, compatible minimum version numbers of the components used are associated with it to form dependency rules.

On equipment, for each component, if a new version is available (that is, the version number on the server is greater than the version number on the device), the component is downloaded and installed after at least one dependency rule check. If these rules impose a new version of a used component, the latter is previously updated and this recursively.

In order to limit server queries about version numbers of components, it is possible to build a list of versions of all components on the server and download this list to the device. The versioning system makes it possible to evolve co-operating software components.

2.2. Disadvantages of prior art

A disadvantage of the prior art is posed in particular by the case of non-techie users. Indeed, for a user of this type, the programmable equipment at his disposal remains difficult to change, either during a change of equipment, or during an evolution of this equipment, or even when subscribing to a new service using this equipment.

The operations of transfer of a software component from a software server, the information requested during the installation of this software component, the waiting time (linked to the bit rate of the line used for downloading and the update time). day) without understanding what the equipment does before actually being able to use can represent unacceptable elements that penalize the penetration of technologies.

Another disadvantage of this technique of the prior art is related to the establishment of new services. For a user who subscribes to a new service, the necessary software (he must know which) must be downloaded (he must know from which server) by the user who then proceeds to its installation with the succession of information entries (sometimes technical requirements) required by the software developer. These two operations require a considerable level of technical expertise and waiting times without the possibility of using the equipment.

Yet another disadvantage of this prior art technique is related to the installation or reinstallation of new equipment. Indeed when installing on new equipment or reinstallation on a device (for example in the case of the change of operating system or hard disk on a PC), the user must re-install all software components of all the services to which he has subscribed. It is a long task that requires a high level of technicality.

Another disadvantage of these techniques of the prior art is related to the evolutions of the software components of an application. During an evolution of a software component, devices that use these components update their component versions as they are started by the components. users. Thus, the load due to the downloading of new components in the context of an operation with a large number of equipment (for example several million) is smoothed over time. But, if one finds a malfunction at the beginning of the use of this new version N ', it may be wise, or even necessary, to return to the previous version N. With the current versioning system based on the highest version number, it is necessary to redo a new version N "of the component to increment the version number of the component and to cause its update on the equipment which had already downloaded the bad version N '. This technique must also be applied to all the components dependent on the defective version N '.

In addition, other equipment (those who did not download version N ') will still download the new version N ", but for nothing since the new version N" is identical (in terms of functionality) to the initial version N This prior art technique, widely used, involves a great waste of network resources and a significant loss of time for the users.

3. Objectives of the invention

The invention particularly aims to overcome these disadvantages of the prior art.

More specifically, an objective of the invention, in at least one embodiment, is to provide a technique for eliminating user interventions, avoiding the disadvantages of conventional systems implementing semi-automatic installations.

More specifically, an objective of the invention, in at least one embodiment, is to provide a technique that makes it possible to overcome manual transfer and installation operations when subscribing to a new service that requires new services. software components.

Another object of the invention, in at least one embodiment, is to provide a mechanism which avoids repetition of the transfer operations and manual installation when installing on new equipment or re-installing components on the same equipment.

The invention also aims, in at least one embodiment, to provide a mechanism allowing equipment to limit unnecessary downloads, especially during software version evolutions.

4. Summary of the invention

These objectives, as well as others which will appear more clearly later, are achieved according to the invention by means of a method of distributing at least a first software component, within a programmable terminal, said programmable terminal having previously at least one second software component corresponding to said at least one first software component, in a different version,

Said method comprises a step of replacing said at least one second software component with said at least one first software component, if said at least one first software component is of an earlier version.

It should be noted that the invention is based on an approach quite different from conventional approaches according to which a version change is envisaged only if the current version of a component is earlier than the last available version.

The approach of the method according to the invention goes against the current of this conventional approach by requiring the terminal to use a certain version of a given software component, even though this terminal would have a later version of said component.

According to the techniques of the prior art, the version management systems which are based on the highest version number, cause the construction of a new version N "of a component having the same content as an initial version. N, in order to increment the version number of said component and cause it to update on equipment that would have previously replaced the N version with a bad version N 'These updates are resource-consuming and time-consuming. invention removes these consumptions useless.

• identification d'au moins un premier composant logiciel, appartenant à un premier ensemble de composants logiciels correspondant à au moins un service souscrit par ledit terminal programmable ;
• recherche d'une différence de version entre au moins un composant logiciel dudit premier ensemble et au moins un composant d'un deuxième ensemble de composants logiciels correspondants précédemment installés au sein dudit terminal programmable.

Advantageously, a software component can be associated with at least one service, said method comprising the following steps:

• identifying at least one first software component, belonging to a first set of software components corresponding to at least one service subscribed by said programmable terminal;
• searching for a version difference between at least one software component of said first set and at least one component of a second set of corresponding software components previously installed within said programmable terminal.

Thus, it is possible to effectively and simply update the versions of software components that are gathered within sets: a first set of components from the service management entity and a second set of components installed within the service management entity. programmable terminal. Among other advantages such an update is achieved through the invention without user intervention, and therefore without requiring the latter to acquire particular knowledge about it. This update is based on a concept of services subscribed by the user, and not on the concept of hardware configuration of the programmable terminal thereof. As a result, the software update is no longer related to hardware characteristics, but to service subscription features. These services can advantageously be managed and / or referenced within a management entity of a set of services, associating services with software components.

• constitution d'une première liste de composants logiciels dépendants d'au moins un des composants logiciels dudit premier ensemble ;
• ajout des composants de ladite première liste audit premier ensemble.

Advantageously, said search step further comprises the following steps:

• constituting a first list of software components dependent on at least one of the software components of said first set;
• adding the components of said first list to said first set.

Thus, dependent software components are linked to the services subscribed by the user. The mechanism therefore makes it possible not only to replace software components of the first set, but also to replace all components that depend on at least one component of the first set.

• une étape de détermination d'un arbre de dépendances de composants logiciels dépendants dudit composant logiciel dudit premier ensemble ;
• une étape de construction d'une deuxième liste de composants logiciels dépendant de chaque composant logiciel dudit arbre de dépendances ;
• une étape d'insertion des composants de ladite deuxième liste au sein de ladite première liste.

In this case, said step of constituting said first list advantageously comprises:

• a step of determining a dependency tree of software components dependent on said software component of said first set;
• a step of constructing a second list of software components dependent on each software component of said dependency tree;
• a step of inserting the components of said second list into said first list.

By extension, a set of software components is created that depend on the components of the first set. This new set is based on all the dependencies of the components of the first set. For example, it is possible that the first set contains two components C and C 'that depend on the same component C "(of the dependency tree), in which case the component C" will be added only one times to the second list and the set of dependent components of C "will be added to the second list.

Preferably, said constitution step is performed recursively for each software component of said second list.

In this way, the dependency-seeking steps are applied until the dependencies between the components are exhausted. This ensures that it is not possible to omit dependent components from the list, which ensures the proper operation of the terminal when updates are completed.

Advantageously, said step of constituting said first list further comprises a step of verification of the subscription by said programmable terminal to at least one service related to said software components constituting said first list.

Thus, only the components related to the services subscribed by the users will be taken into account. For example, if the first set contains a component C which has three dependencies C ', C "and C"', but that C '"is part of a service not subscribed by the user, then this component C"' will not be taken into account. This minimizes the resources needed to update and distribute the components.

According to a preferred embodiment of the invention, said step of constituting said first list further comprises a step of checking a hardware adequacy to said programmable terminal to said software components constituting said first list.

In this way, it is ensured that the replaced components are in adequacy with the hardware capabilities of the programmable terminal. This verification step makes it possible to thwart the component updates for services to which the user has subscribed, but that his terminal does not allow to execute.

According to another particular aspect of the invention, said identification step uses a database associating with an identifier of each subscriber, a list of at least one subscribed service on the one hand and said first set of other go.

Thus, the identification of the programmable terminal makes it possible to ensure that the services subscribed are recorded in a database and not within the terminal. Thus, the level of security of the system is increased by not allowing a terminal to download components corresponding to services to which it has not subscribed and thus reduces the risk of piracy.

The invention also relates to a method for updating at least one first software component, within a programmable terminal.

• demande de recherche d'une différence de version entre ledit au moins un premier composant logiciel et au moins un deuxième composant logiciel correspondant précédemment installés au sein dudit terminal programmable ;
• réception dudit au moins un premier composant logiciel dont la version est différente dudit au moins un deuxième composant logiciel ;
• remplacement sur ledit terminal programmable dudit au moins un deuxième composant logiciel par ledit au moins un premier composant logiciel dont la version est antérieure.

According to the invention said first software component is associated with at least one service and said method comprises the following steps:

• requesting a search for a version difference between said at least one first software component and at least one corresponding second software component previously installed within said programmable terminal;
• receiving said at least one first software component whose version is different from said at least one second software component;
• replacing on said programmable terminal of said at least one second software component by said at least one first software component whose version is earlier.

As mentioned above, the invention allows a simple and efficient update. It also makes it easy to return to a previous version, if necessary.

The invention also relates to a system for distributing at least a first software component, within a programmable terminal, said programmable terminal having at least a second software component corresponding to said at least one first software component, in a different version,

According to the invention, such a system comprises means for replacing said at least one second software component with said at least one first software component, if said at least one first software component is of an earlier version.

• des moyens d'identification d'au moins un premier composant logiciel, appartenant à un premier ensemble de composants logiciels correspondant à au moins un service souscrit par ledit terminal programmable ;
• des moyens de recherche d'une différence de version entre au moins un composants logiciels dudit premier ensemble et au moins un composant d'un deuxième ensemble de composants logiciels correspondants précédemment installés au sein dudit terminal programmable ;
• transmission audit terminal programmable des composants logiciels dudit premier ensemble dont la version est différente de ceux dudit deuxième ensemble.

The invention also relates to a server for distributing at least a first software component, within a programmable terminal, said programmable terminal having at least a second software component corresponding to said at least one first software component, in a different version, said server implementing the method described above. Such a server includes in particular:

• means for identifying at least one first software component belonging to a first set of software components corresponding to at least one service subscribed by said programmable terminal;
• means for finding a version difference between at least one software component of said first set and at least one component of a second set of corresponding software components previously installed within said programmable terminal;
• transmission to said programmable terminal of the software components of said first set whose version is different from those of said second set.

Such a server may comprise, more generally, means for implementing all or part of the process steps detailed above.

Thus, the server manages all the verification, identification, search and transmission operations, thus relieving the terminal of these operations and substantially increasing the security of the system by reducing the risk of piracy.

The invention also relates to terminals comprising means for updating at least one first software component, said programmable terminal having at least a second software component corresponding to said at least one first software component, in a different version,

Such a terminal comprises means for replacing said at least one second software component with said at least one first software component, if said at least one first software component is of an earlier version.

• des moyens de demande de recherche d'une différence de version entre ledit au moins un premier composant logiciel et au moins un deuxième composant logiciel correspondant précédemment installés au sein dudit terminal programmable ;
• des moyens de réception dudit au moins un premier composant logiciel dont la version est différente dudit au moins un deuxième composant logiciel.

Advantageously, said first software component is associated with at least one service referenced within a management entity of a set of services, and said programmable terminal comprises:

• version difference search request means between said at least one first software component and at least one corresponding second software component previously installed within said programmable terminal;
• means for receiving said at least one first software component whose version is different from said at least one second software component.

Such a terminal may comprise, more generally, means for implementing all or part of the process steps detailed above.

The invention also relates to computer programs for implementing the methods described above, in a server on the one hand and in a terminal on the other hand.

5. List of figures

• la figure 1 présente un synoptique d'un mode de réalisation conduisant à la mise à jour des composants logiciels ;
• la figure 2 illustre l'architecture matérielle liée à la mise en place des étapes du procédé de la figure 1 ;
• la figure 3 décrit l'emplacement des informations échangées entre les différents acteurs de la figure 2 selon le procédé de la figure 1 ;
• la figure 4 illustre les étapes du procédé en relation avec des acteurs de la figure 2 ;
• la figure 5 illustre l'architecture matérielle du terminal programmable selon l'invention ;
• la figure 6 illustre l'architecture matérielle du serveur de composants logiciels selon l'invention ;
• la figure 7 illustre l'architecture matérielle de l'entité de gestion de services selon l'invention.

Other characteristics and advantages of the invention will appear more clearly on reading the following description of a preferred embodiment, given as a simple illustrative and nonlimiting example, and the appended drawings, among which:

• Figure 1 shows a block diagram of an embodiment leading to the update of the software components;
• FIG. 2 illustrates the hardware architecture related to the implementation of the steps of the method of FIG. 1;
• FIG. 3 describes the location of the information exchanged between the different actors of FIG. 2 according to the method of FIG. 1;
• FIG. 4 illustrates the steps of the method in relation to the actors of FIG. 2;
• FIG. 5 illustrates the hardware architecture of the programmable terminal according to the invention;
• FIG. 6 illustrates the hardware architecture of the software component server according to the invention;
• FIG. 7 illustrates the hardware architecture of the service management entity according to the invention.

6. Detailed description of the invention 6.1. Recall of the principle of invention

• s'affranchissant des opérations de transfert et d'installation manuels lors de la souscription à un service qui nécessite de nouveaux composants logiciels ;
• évitant de répéter les opérations de transfert et d'installation manuels lors de l'installation sur un nouvel équipement ou la re-installation sur le même équipement d'un ensemble de composants logiciels ;
• n'ayant pas le besoin technique ou fonctionnel de télécharger des composants logiciels inutilement afin de ne pas utiliser pas le réseau et de ne pas faire attendre l'utilisateur.

The invention therefore proposes to simplify the use of the equipment by masking to the user the adaptation of the software components and to limit the traffic on the interconnection network in, in at least one embodiment:

• eliminating manual transfer and installation when subscribing to a service that requires new software components;
• avoid repeating manual transfer and installation operations when installing on new equipment or re-installing on the same equipment a set of software components;
• not having the technical or functional need to download software components unnecessarily so as not to use the network and not to wait for the user.

In this context, an embodiment of the invention consists of a mechanism that does not require manipulation on the part of a user who subscribes to a new service, not requiring unnecessary manipulation on the part of the user who wishes to use new equipment or re-install on equipment, and optimize component updates on equipment.
In this embodiment, the invention proposes to update at least one software component of a software package of an application, by comparing whether the number of the current version of a software component is different (lower or higher). the version proposed by the software component server, if this is the case, by replacing the software component with that of the server.

It is important to note that, unlike conventional techniques, the test performed is a difference test, and not a test aimed only at verifying that the current version number is less than the proposed version number. This new approach, which goes against habits, greatly simplifies treatment, including the return to a previous version.

Optionally, the components proposed by the server for a terminal correspond only to those necessary for the implementation of the services identified with a service identification server.

Optionally, when the software component is not present on the terminal, it is loaded on it.

More particularly, in this embodiment, the invention proposes a mechanism for downloading and inserting software components on different types of programmable terminal equipment. These components are provided via an interconnection network from a device Central which has the role of server of software components. The method also relies on a central equipment that serves as a server identifying the services to which the user has subscribed. These two roles can be grouped together or not in the same central equipment accessible via the interconnection network.

• l'analyse des composants logiciels exigés :
  • par les caractéristiques techniques de l'équipement terminal ;
  • et par les services souscrits obtenus par interrogation auprès du serveur d'identification de services.
• l'éventuel téléchargement des composants depuis le serveur de logiciels ;
• leur insertion dans l'application sur ledit équipement terminal ;
• le transfert de l'exécution au composant logiciel de l'application.

The process that takes place on the terminal equipment supports:

• the analysis of the required software components:
  • by the technical characteristics of the terminal equipment;
  • and by subscribed services obtained by querying the service identification server.
• the possible download of the components from the software server;
• their insertion in the application on said terminal equipment;
• the transfer of the execution to the software component of the application.

1. 1. une étape de connexion au serveur de logiciels 200 et de récupération des versions des composants logiciels ;
2. 2. une étape de vérification, au sein du terminal 100, de la validité de la version locale du composant logiciel de gestion des composants logiciels ;
3. 3. une étape facultative de téléchargement du composant logiciel de gestion des composants logiciels ;
4. 4. une étape facultative d'installation du composant logiciel de gestion des composants logiciels, au sein du terminal 100 ;
5. 5. une étape de lancement du composant logiciel de gestion des composants logiciels, au sein du terminal 100 ;
6. 6. une étape de connexion au serveur d'identification de services 300 et de récupération des services souscrits ;
7. 7. une étape de vérification des composants logiciels nécessaires et des versions locales présentes selon les possibilités techniques de l'équipement terminal et les services souscrits au sein du terminal 100 ;
8. 8. une étape facultative de téléchargement de composants logiciels au sein du terminal 100 ;
9. 9. une étape facultative d'installation de composants logiciels au sein du terminal 100 ;
10. 10. une étape de lancement du composant logiciel applicatif au sein du terminal 100 ;

With reference to FIG. 1, the steps leading to the implementation of the actions of the method according to this embodiment are described:

1. 1. a step of connecting to the software server 200 and recovering versions of the software components;
2. 2. a step of verifying, in the terminal 100, the validity of the local version of the software component management component software;
3. 3. an optional step of downloading the software component management component;
4. 4. an optional step of installing the software component management component, within the terminal 100;
5. 5. a launching step of the software component management component, within the terminal 100;
6. 6. a step of connection to the service identification server 300 and recovery of subscribed services;
7. 7. a verification step of the necessary software components and local versions present according to the technical possibilities of the terminal equipment and services subscribed within the terminal 100;
8. 8. an optional step of downloading software components within the terminal 100;
9. 9. an optional step of installing software components within the terminal 100;
10. 10. a step of launching the application software component within the terminal 100;

In this embodiment, the management of the software components is performed jointly by the software component management entity (the software server 200) and the programmable terminal 100 using a software component of the software component management component. . This generic software component is responsible for implementing certain steps of the mechanism, in particular to ensure that the software components to be downloaded are in line with the services subscribed by the users of the programmable terminal. For example, it is not necessary to download components for reception of broadcast channels of digital audiovisual programs if the user has not subscribed to such a service.

This approach greatly reduces download volumes and times by ensuring that only the necessary software components are downloaded. In fact, following the previous example, if one of the components used to receive broadcast channels of audiovisual programs has been modified and this component causes the modification of other software components associated with other services to which users has subscribed, there will be, in this case, to download the mandatory components, without the need to download all the components of reception of broadcast channels audiovisual programs.

6.2. Description of an embodiment

Subsequently, the case of an implementation of the update method is particularly presented in the case of the subscription to on-line terminal equipment services of "personal computer" type. It is clear, however, that the invention is not limited to this particular application, but can also be in many other fields, and for example in mobile telephony and more generally in all cases where at least one of the above-mentioned objectives of the invention is to be achieved.

• un ensemble 10 d'équipements terminaux de différents types, par exemple Ordinateur Personnel 11, Assistant Personnel 12 (« Personnal Digital Assistant ») et STB 13 (« Set Top Box »). La structure générale de ces équipements terminaux est illustrée schématiquement par la figure 5. Il comprend une mémoire 51, et une unité de traitement 50 équipée d'un microprocesseur, qui est piloté par un programme d'ordinateur (ou application) 52. L'unité de traitement 50 reçoit en entrée, via un module d'interface d'entrée réseau 53, des réponses de la part de serveurs ou des composants logiciels 54, que le microprocesseur traite, selon les instructions du programme 52, pour générer des requêtes et/ou des réponses 56, qui sont transmises aux serveurs via un module d'interface de sortie réseau 55.
• des serveurs 20 remplissant deux rôles : le rôle de serveur de composants logiciels 21 et le rôle de serveur d'identification de service 22. La structure d'un serveur de composants est illustrée schématiquement par la figure 6. Il comprend une mémoire 61, et une unité de traitement 60 équipée d'un microprocesseur, qui est piloté par un programme d'ordinateur (ou application) 62. L'unité de traitement 60 reçoit en entrée, via un module d'interface d'entrée réseau 63, des requêtes d'interrogation des terminaux et/ou des réponses 64, que le microprocesseur traite, selon les instructions du programme 62, pour générer des envois de composants logiciels et/ou des réponses et ou des listes de composants 66, qui sont transmises via un module d'interface de sortie réseau 65. La structure d'un serveur de gestion de service est illustrée schématiquement par la figure 7. Il comprend une mémoire 71, et une unité de traitement 70 équipée d'un microprocesseur, qui est piloté par un programme d'ordinateur (ou application) 72. L'unité de traitement 70 reçoit en entrée, via un module d'interface d'entrée réseau 73, des requêtes et/ou des réponses des terminaux quant aux souscriptions de services des clients 74, que le microprocesseur traite, selon les instructions du programme 72, pour générer des commandes et/ou des réponses de compositions de composants logiciels 76, qui sont transmises via un module d'interface de sortie réseau 75.
• un réseau 30 de communications permettant aux équipements terminaux 10 de se connecter entre eux et avec les serveurs 20.

The realization will be better understood from the description given with reference to the following diagrams and figures. In relation with FIG. 2, an embodiment of an updating method implemented in the following hardware architecture is presented:

• a set of terminal equipment 10 of different types, for example Personal Computer 11, Personal Assistant 12 ("Personal Digital Assistant") and STB 13 ("Set Top Box"). The general structure of these end devices is illustrated schematically in FIG. 5. It comprises a memory 51, and a processing unit 50 equipped with a microprocessor, which is controlled by a computer program (or application) 52. processing unit 50 receives, via a network input interface module 53, responses from servers or software components 54, which the microprocessor processes, according to the instructions of the program 52, to generate requests and / or responses 56, which are transmitted to the servers via a network output interface module 55.
• servers 20 fulfilling two roles: the role of software component server 21 and the service identification server role 22. The structure of a component server is illustrated schematically in Figure 6. It comprises a memory 61, and a processing unit 60 equipped with a microprocessor, which is controlled by a computer program (or application) 62. The processing unit 60 receives, via a network input interface module 63, requests interrogating the terminals and / or responses 64, that the microprocessor processes, according to the instructions of the program 62, to generate shipments of software components and / or responses and or lists of components 66, which are transmitted via a module network output interface 65. The structure of a server of Service management is illustrated schematically in Figure 7. It includes a memory 71, and a processing unit 70 equipped with a microprocessor, which is controlled by a computer program (or application) 72. The processing unit 70 receives as input, via a network input interface module 73, requests and / or responses from the terminals as to customer service subscriptions 74, which the microprocessor processes, according to the instructions of the program 72, to generate commands and / or responses of software component compositions 76, which are transmitted via a network output interface module 75.
• a communications network 30 enabling the terminal equipment 10 to connect to each other and to the servers 20.

• sur chaque équipement 10 : un programme exécutable dénommé « bootstrap » 41 installé à demeure sur l'équipement, un composant « updater » (ou « de mise à jour ») 42 pour la gestion des composants, la liste 50 des composants logiciels 60 ;
• sur le serveur de logiciels 21 : un composant « updater » 43 pour la gestion des composants, des composants logiciels, la liste 51 des numéros de versions des composants logiciels 61 ;
• sur le serveur d'identification de services 22 : la liste 52 des services auxquels l'utilisateur a souscrit.

With reference to FIG. 3, the location of the information on the various entities relating to each other during the implementation of the updating process is presented:

• on each device 10: an executable program called "bootstrap" 41 permanently installed on the equipment, a component "updater" (or "update") 42 for the management of the components, the list 50 of the software components 60;
• on the software server 21: a "updater" component 43 for the management of the components, the software components, the list 51 of the version numbers of the software components 61;
• on the service identification server 22: the list 52 of the services to which the user has subscribed.

A software component is a bundle of executable programs used to build applications. The programmer uses these bricks via variables, methods, functions or routines defined in an API.

A version number is a string representative at a certain date of a file containing an executable program or more general information. If the information or the program changes, a new version number is assigned to the file. For example, version numbers can be organized following integers separated by periods. Depending on the degree of modification of the information or the executable program, one of the numbers is incremented by an integer value. The version numbers thus organized are ordered according to increasing numbers over time. For example: "2.3.4.56"

A list of software component version numbers includes the identification of the versioned software components for each service, for example, the service name, version number, and filename of the software component.

• Sur chacun des équipements terminaux 10, le programme « bootstrap » 41 est exécuté pour lancer l'application et comporte le minimum de fonctions pour :
  • se connecter (101) via le réseau de communications 30 au serveur de composants logiciels 21 ;
  • récupérer (102) le numéro de version en cours du composant « updater » 43 sur le serveur de composants logiciels 21 ;
  • récupérer (103) le numéro de la version locale du composant « updater » 42 sur l'équipement 10 ;
  • si (étape 104) la version disponible sur le serveur de composants logiciels 21 est différente ou si l'« updater » 42 est absent sur l'équipement 10 on procède (105) au téléchargement du composant « updater » 43 et à son installation (106) sur l'équipement 10 à la place de l'ancien 42 ;
  • passer (107) le contrôle au composant « updater » 42 sur l'équipement ;

With reference to FIG. 4 and FIGS. 2 and 3 previously described, the steps of the updating method according to the chosen embodiment are presented:

• On each of the terminal equipments 10, the "bootstrap" program 41 is executed to launch the application and comprises the minimum of functions for:
  • connect (101) over the communications network 30 to the software component server 21;
  • retrieving (102) the current version number of the updater component 43 on the software component server 21;
  • retrieving (103) the local version number of the updater component 42 on the equipment 10;
  • if (step 104) the version available on the server of software components 21 is different or if the "updater" 42 is absent on the equipment 10 is proceeded (105) to download the component "updater" 43 and its installation ( 106) on the equipment 10 instead of the old 42;
  • passing (107) the control to the "updater" component 42 on the equipment;

In this particular embodiment, this "bootstrap" 41 is never modified. The "updater" component 42 is automatically updated on the equipment 10 if the version number of the present one is different from that available on the software server 21.

• se connecter (201) au serveur d'identification de service 22 ;
• récupérer (202) la liste 52 des services auxquels l'utilisateur a souscrit ;
• se connecter au serveur (203) de composants logiciels 21 ;
• récupérer (204) la liste des numéros de version 51 des composants nécessaires à chacun de ces services et les règles de dépendance ;
• récupérer (205) localement la liste 50 des numéros de version des composants ;
• sélectionner (206) à partir de la liste 52 des services les briques devant être présentes sur l'équipement 10 ;
• pour chacune des briques sélectionnées (207) dans l'étape précédente (206) : télécharger (209) et installer (210) si (étape 208) la brique est absente ou le numéro de version disponible sur le serveur de logiciel 21 obtenu lors de la récupération de la liste des numéros de version (204) est différent du numéro de version sur l'équipement 10 obtenu lors de la récupération locale des versions des composants (205) ;
• passer le contrôle (211) à la première brique de l'application 44.

The "updater" component 42 then intervenes for:

• connect (201) to the service identification server 22;
• recovering (202) the list 52 of the services to which the user has subscribed;
• connect to the server (203) of software components 21;
• retrieving (204) the list of version numbers 51 of the components required for each of these services and the dependency rules;
• locally retrieving (205) the list 50 of the component version numbers;
• select (206) from list 52 of the services the bricks to be present on the equipment 10;
• for each of the selected bricks (207) in the previous step (206): download (209) and install (210) if (step 208) the brick is missing or the version number available on the software server 21 obtained during the retrieval of the list of version numbers (204) is different from the version number on the equipment 10 obtained during local retrieval of component versions (205);
• pass the control (211) to the first brick of the application 44.

At the end of this update phase, the software components are updated and the application can begin its execution.

6.3. Other optional features and benefits

In this embodiment of the updating method, the programmable terminal equipment and the servers are connected through a communications network. Queries and replies exchanged are done using the protocol "http"("hypertext transport protocol" for "hypertext transport protocol"). Application exchanges (exchanges at the "updater" components level) are carried out using the "SOAP" protocol. "SOAP" is a message transmission protocol. It defines a set of rules for structuring messages that can be used in simple one-way transmissions, but it is particularly useful for executing query-response dialogs. The rules for structuring the exchanges of "SOAP" are based on the language "XML"("eXtensible Markup Language" for "extensible markup language").

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns : SOAP-ENV="http://schemas.xmlsoap .org
/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:TerritoryObject="http://www.domaine.com/TerritoryControler
.xsd"
xmlns:TerritoryControler="urn:territorycontroler">
<SOAP-ENV:Body SOAP-ENV : encodingStyle= "http://schemas.
xmlsoap.org/soap/encoding/">
<TerritoryControler:getVersion>
<aVersionClient>V02.01.00</aVersionClient>
</TerritoryControler:getVersion>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

In connection with FIG. 4, the following "SOAP" code is an example of a request to obtain the list 51:

 <? xml version = "1.0" encoding = "UTF-8"?><SOAP-ENV: Envelope xmlns: SOAP-ENV = "http: //schemas.xmlsoap .org
/ Soap / envelope / "
xmlns: SOAP-ENC = "http://schemas.xmlsoap.org/soap/encoding/"
xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns: xsd = "http://www.w3.org/2001/XMLSchema"
xmlns: TerritoryObject = "http://www.domaine.com/TerritoryControler
.xsd "
xmlns: TerritoryControler = "urn: territorycontroler"><SOAP-ENV: Body SOAP-ENV: encodingStyle = "http: // schemas.
xmlsoap.org/soap/encoding / "><TerritoryControler:getVersion><AVersionClient> V02.01.00 </ aVersionClient></ TerritoryControler: getVersion></ SOAP-ENV: Body></ SOAP-ENV: Envelope> 

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-
ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:TerritoryObject="http://www.domaine.com/TerritoryControler
.xsd1" xmlns:TerritoryControler="urn:territorycontroler">
<SOAP-ENV:Body SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<TerritoryControler:getVersionResponse>
<Return>0</Return>
<aVersionProc>V02.01.00</aVersionProc>
<aVersionServer>V02.02.00</aVersionServer>
<aVersionDba>V01.01.00</aVersionDba>
</TerritoryControler:getVersionResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

This request makes it possible to obtain, from the software component server, the list 51 available on the server by providing the version installed on the client "V02.01.00". The response formulated by the server then has the following form:

 <? xml version = "1.0" encoding = "UTF-8"?><SOAP-ENV: Envelope xmlns: SOAP-
ENV = "http://schemas.xmlsoap.org/soap/envelope/" xmlns: SOAP-
ENC = "http://schemas.xmlsoap.org/soap/encoding/"
xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"
xmlns: xsd = "http://www.w3.org/2001/XMLSchema"
xmlns: TerritoryObject = "http://www.domaine.com/TerritoryControler
.xsd1 "xmlns: TerritoryControler =" urn: territorycontroler "><SOAP-ENV: Body SOAP-
ENV: encodingStyle = "http://schemas.xmlsoap.org/soap/encoding/"><TerritoryControler:getVersionResponse><Return> 0 </ Return><AVersionProc> V02.01.00 </ aVersionProc><AVersionServer> V02.02.00 </ aVersionServer><AVersionDba> V01.01.00 </ aVersionDba></ TerritoryControler: getVersionResponse></ SOAP-ENV: Body></ SOAP-ENV: Envelope> 

In a complementary embodiment, each programmable terminal may also be labeled as "pilot" or "non-pilot" by an identification server, for example according to a parameter associated with the terminal. This labeling makes it possible to characterize certain terminals as being equipment intended to carry out production tests. When a terminal labeled "driver" queries the identification server or the service management server for the presence of a software component of different version (earlier) of its current version, this server will indicate the presence of this new version if she is available. In the case of equipment labeled "non-pilot", the server will indicate that no different version is available. This embodiment therefore makes it possible to take into account a phase of testing the versions of the software components before they are transferred to all the equipment once they have been validated and certified as operating according to its specifications.

Claims (13)

A method of distributing at least a first software component, within a programmable terminal, said programmable terminal having at least a second software component corresponding to said at least one first software component, in a different version,
characterized in that it comprises a step of replacing said at least one second software component with said at least one first software component if said at least one first software component is of an earlier version. Distribution method according to Claim 1, characterized in that a software component which can be associated with at least one service,
said method comprises the following steps: identifying at least one first software component belonging to a first set of software components corresponding to at least one service subscribed by said programmable terminal; - Search for a version difference between at least one software component of said first set and at least one component of a second set of corresponding software components previously installed within said programmable terminal. Dispensing method according to claim 2 characterized in that said search step further comprises the following steps: constituting a first list of software components dependent on at least one of the software components of said first set; adding components from said first list to said first set. Dispensing method according to claim 3, characterized in that said step of forming said first list further comprises: a step of determining a dependency tree of software components dependent on said software component of said first set; a step of constructing a second list of software components depending on each software component of said dependency tree; a step of inserting the components of said second list into said first list. Dispensing method according to claim 4, characterized in that said step of constitution is performed recursively for each software component of said second list. A method of distribution according to any one of claims 4 and 5, characterized in that said step of constituting said first list further comprises a step of verification of the subscription by said programmable terminal to at least one service related to said software components constituting said first list. A method of distribution according to any one of claims 4 to 6, characterized in that said step of constituting said first list further comprises a step of checking a hardware adequacy to said programmable terminal to said software components constituting said first list. A method of distribution according to any one of claims 1 to 7 characterized in that said identification step uses a database associating with an identifier of each subscriber, a list of at least one subscribed service on the one hand , and said first set on the other hand. A method of updating at least one first software component, within a programmable terminal,
characterized in that said first software component is associated with at least one service,
and in that said method comprises the following steps: requesting a search for a version difference between said at least one first software component and at least one corresponding second software component previously installed within said programmable terminal; receiving said at least one first software component whose version is different from said at least one second software component; replacing on said programmable terminal of said at least one second software component by said at least one first component software whose version is earlier. System for distributing at least a first software component, within a programmable terminal, said programmable terminal having at least a second software component corresponding to said at least one first software component, in a different version,
characterized in that it comprises means for replacing said at least one second software component with said at least one first software component, if said at least one first software component is of an earlier version. Terminal comprising means for updating at least a first software component, said programmable terminal having at least a second software component corresponding to said at least one first software component, in a different version,
characterized in that it comprises means for replacing said at least one second software component with said at least one first software component, if said at least one first software component is of an earlier version. Terminal comprising means for updating at least a first software component, according to claim 11,
characterized in that said at least one first software component is associated with at least one service,
and in that it comprises: means for requesting a version difference search between said at least one first software component and at least one corresponding second software component previously installed within said programmable terminal; means for receiving said at least one first software component whose version is different from said at least one second software component. Computer program product downloadable from a communication network and / or stored on a computer readable medium and / or executable by a microprocessor, characterized in that it comprises code instructions program for carrying out the method of at least one of claims 1 to 9.

Images