Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment
  • G06F8/65—Updates
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment
  • G06F8/61—Installation
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment
  • G06F8/61—Installation
  • G06F8/62—Uninstallation
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/08—Configuration management of networks or network elements
  • H04L41/0803—Configuration setting

Definitions

• the present invention relates to a method of deploying a set of software application (s) software (s) in a telecommunication network comprising at least one server of telecommunications terminals and telecommunications means between said server and said terminals, and including the following steps implemented by the server:
• the terminals include for example mobile or fixed equipment, smart phones, tablets, laptops or fixed, multimedia equipment.
• the central management entity knows the list of applications and operating system version implemented in each terminal and, for each of these terminals, it performs calculations. from this information to generate a dedicated deployment order to the terminal, indicating the installations, deletions and updates of applications that this terminal must perform to comply with the set of applications defined by the administrator. The terminal then applies the own deployment order.
• Solutions are based on the principle that the central entity sends a notification to the terminals to signify that a deployment order or an update is available. This principle requires the central entity to know the availability of the terminals to ensure that all have received the notification, thereby causing additional workload for that entity.
• the invention proposes a method of deploying a set of software application (s) of the aforementioned type characterized in that said data intended for the terminals comprises a deployment list determined by the server by implementing the following steps:
• the method of deploying a set of software application (s) according to the invention further comprises one or more of the following characteristics:
• the server determines whether the installation or the uninstallation of the application is dependent on another application and that in the positive case, the server adds the identifier of said other application in said sub-list associated with the operating system, with an indication of dependence between said application and said other application;
• the applications and the operating systems being associated with respective security levels: the comparison between the security level of the application and the level of security of the operating system;
• each operating system is associated with a mandatory security application and the applications and operating systems are associated with respective security levels: the determination of the mandatory security application associated with the operating system, and the comparison between the security levels of the given application and the specified mandatory security application.
• the present invention proposes a method of deploying a set of software application (s) in a telecommunications network comprising at least one server, telecommunication terminals and telecommunication means. between said server and said terminals, said method comprising the steps of:
• a terminal obtains, from the server, via the telecommunication means, a deployment list listing sub-lists indicating identifiers applications and each associated with a respective terminal operating system of a set of terminal operating system (s);
• the terminal determines the applications and the operating system then installed on the terminal, compares said determined applications and the sub-list associated with said determined operating system, and according to this comparison:
• the terminal uninstalls said application
• the terminal performs the following steps:
• the terminal determines if said application is already installed on the terminal
• the terminal downloads from the server (Serv d ) said application and installs it;
• the deployment method further comprises the steps of the deployment method according to the first aspect of the invention.
• this method of deploying a set of software application (s) according to the invention further comprises one or more of the following characteristics:
• the sub-list associated with each operating system indicates application identifiers each associated with an application version number, and according to which the following steps are implemented:
• the terminal determines that the application is already installed on the terminal, it compares the version number of the installed application to that associated with the identifier of said application in the sub-list;
• the terminal 10 downloads from the server the version of the application indicated by the version number indicated in the sub-list and installs the downloaded software application;
• an identifier of an application is mapped to an identifier of another application, indicating that the installation or the uninstallation of said application is dependent on said other application and according to which the terminal installs , or uninstalls, said applications in an order according to said indication.
• the present invention proposes a computer program to be installed in a server intended to be implemented in a network of computers. telecommunication further comprising telecommunication terminals and telecommunication means between said server and said terminals, said program comprising instructions for implementing the steps of a method according to the first aspect of the invention during execution of the program by server processing means.
• the present invention proposes a computer program to be installed in a telecommunication terminal intended to be implemented in a telecommunication network comprising at least one server, a plurality of telecommunication terminals and telecommunication means between said server and said terminals, said program comprising instructions for implementing the steps of a method according to the second aspect of the invention during execution of the program by means of processing the terminal.
• the present invention provides a server for a telecommunication network further comprising telecommunication terminals, said server comprising telecommunication means between said server and said terminals;
• said server being adapted to receive a set of software application (s) to be deployed on the terminals, for determining, based on said set of software application (s) received, deployment data for the terminals;
• said server being characterized in that it is adapted, when determining the deployment data, to select, for each operating system of a group of operating systems implemented on the terminals, software applications among said set of software application (s) to be deployed according to criteria relating to the compatibility between said applications and said operating system; and to determine a deployment sub-list associated with said operating system and including the identifiers of said selected applications;
• said server being adapted to insert, in a deployment list, sub-lists determined for the application systems of the group and to provide terminals said deployment list.
• the present invention proposes a telecommunication terminal intended for a telecommunication network comprising at least one server, telecommunication terminals and telecommunication means between said server and said terminals,
• said terminal being adapted to obtain, from the server, via the telecommunication means, a deployment list listing sub-lists indicating application identifiers each associated with a respective terminal operating system of a set of terminal operating system (s);
• said terminal being adapted to determine the applications and the operating system then installed on the terminal, comparing said determined applications and the sub-list associated with said determined operating system, and according to this comparison:
• FIG. 1 represents a view of a telecommunication system in one embodiment of the invention
• FIG. 2 represents steps implemented in one embodiment of the invention
• FIG. 3 represents steps implemented in one embodiment of the invention
• FIG. 4 is a view of part of a content of a deployment file F2 in one embodiment of the invention.
• Figure 1 is a view of a system 100 embodying an embodiment of the invention.
• the telecommunication system 100 comprises a plurality of user terminals 10. These terminals 10 are connected by telecommunications links 11 (wired or not) to a telecommunications network R1.
• a distribution server, Serv d is also connected to the network R1 by a telecommunications link 1 1.
• the terminals 10 comprise, for example, smart mobile telephones connected to the network R1 by wireless links 11. Terminals include for example fixed or portable computers etc.
• the distribution server, Serv d , and a generation server Serv g are connected by a respective telecommunication link 12 to a telecommunications network R2.
• the network R1 is a public network, for example the Internet
• the network R2 is a private network, for example an enterprise network.
• Each terminal 10 notably comprises a memory 11 and a microprocessor 12.
• the memory 11 is particularly adapted to store an operating system and software applications, and to implement them using the microprocessor 12.
• the system 100 implements a secure environment, called a security strain, implemented using mandatory security software applications.
• a terminal 10 in which a mandatory security software application is installed is adapted so that any software application installed on the terminal 10 and compatible security strain, is secured, for example as follows: the data generated by the software application and / or exchanged by the software application with the network R1 are encrypted, the application is protected from fraudulent intrusion by means of software partitioning. This partitioning controls the input and output of the secure application to prevent an unsecure third-party application from interacting in a dangerous way with the secure application. .
• FIG. 2 represents steps implemented in the system 100 in one embodiment of the invention.
• each server Serv g , Serv d is performed following the execution, on server computing means, of corresponding software instructions stored in a memory of the server.
• the server Ser g imports a configuration file F1, for example protected cryptographically integrity and authenticated.
• This file is for example provided by the editor of the solution and inserted by the administrator U of the server Serv g .
• this configuration file F1 indicates:
• a list of the dependencies comprising the identifiers of the applications whose installation in a terminal, or the uninstallation, makes use of other applications; in the list of dependencies, each application identifier being associated with the identifiers of said other applications; - the list of security application identifiers that must imperatively be installed on the terminals on which applications are to be deployed, in accordance with the security strain considered in the system 1.
• This F1 file is stored in the Servg server memory.
• a step 102 instructions are provided to the server Serv g , for example by the administrator U requiring the importation of software applications A, each associated with an application identifier and a version number.
• the Servg server When receiving an import instruction from an application A, the Servg server imports the software application A (through the network R2, other networks or media), and then requires its storage in the distribution server. Serv. D. In a step 103, the server Serv g analyzes the contents of this software application A and extracts data from the application, for example metadata present in its source code or in a manifest file present in the application indicating:
• the operating systems for example the type (s) of operating system (for example Android, Windows, Linux etc.) and the version or versions of the operating system (for example V4.0, V3.2 etc.) whose application is compatible,
• This information is stored in the memory of the server Serv g , in correspondence with the identifier of the application A and its version number.
• a step 104 the administrator U selects at least some imported applications A (including one or more mandatory security applications, this selection possibly being made by default) and indicates this selection to the server Serv g .
• These selected applications A define the software package that the administrator wishes to deploy on a set T of terminals 10.
• the server Serv g determines the contents of a deployment list corresponding to the defined software package, according to the selected applications and associated information stored in its memory, and further according to the configuration information of the file. F1.
• the software package may contain more applications than those selected by the administrator U, because depending on the information in F1, the server Serv g may need to add applications if it is necessary the operation of the selected applications.
• This deployment list includes in the embodiment considered, a file F2 shown schematically in FIG.
• the deployment list F2 as determined by the generation server Serv g comprises successive sections S os, each section S os being associated with a respective operating system.
• a SOSX section is associated with the operating system X.
• each operating system is characterized by the type of operating system (Windows, Linus, Android) and its version.
• Each section associated with an operating system S os comprises a list of application identifiers A2 elements of the software package defined above and for each of these application identifiers, furthermore includes, associated with said application identifier A2, a version code indicating a version number of the application, the size of the application, an integrity word allowing the terminal to perform an integrity check of the application that he uploaded, and a list of dependencies.
• Step 105 implemented by the generation server Serv g is now described in more detail with reference to FIG.
• the server Serv g extracts from its memory:
• the server Serv g For each of these information systems indicated as compatible with the application A2 and considered successively, the server Serv g , in a step 105_2, extracted from its memory (according to the stored data from the configuration file F1 and data extracted from the mandatory applications) the version of the security strain of the mandatory security application compatible with this information system.
• This information system is referenced below as follows: operating system OS version X.
• the server Serv g compares the security strain version of the application A2 and the security strain version of the mandatory security application compatible with this information system.
• step 105_4 the application A2 in the version in question is not added to the section of the file F2 associated with the operating system OS version X (step 105_4) and the operating system indicated as next compatible (s) is then considered.
• the application having a most recent version ie a higher version code
• the server Serv g will be automatically selected by the server Serv g and added to the section in F2 associated with the operating system version X.
• the server Serv g verifies in the list of dependencies stored in its memory and from the configuration file F1, if the application A2 is indicated as dependent on other applications.
• step 105_7 the fields relating to the application A2 are filled in the section of the file F2 associated with the operating system OS version X: application identifier, version code, size, integrity word.
• the identifiers of said other applications of which A2 depends are indicated in the field "list of dependencies" associated with the application A2 in the Sosx section of the file F2 associated with the system.
• OS version X operation, and the other fields relating to the application A2 are indicated in the Sosx section of the file F2 are also filled.
• step 105 is stopped in a step 105_8.
• the deployment list F2 is transmitted by the generation server Serv g to the distribution server Serv d via the links 12 and the network R2 for provision to the terminals 10.
• information defining the set T of the terminals 10 are also transmitted (to the server Serv d ) in correspondence with the list of Deployment F2.
• the generation server Serv g provides the deployment list F2 for a given set T or for a single terminal 10.
• the server Serv g provides the definition of the set T or sets to the distribution server Serv d . which results in the creation of folders (directories) for storing generic data to each set T and folders specific to each terminal 10.
• the distribution server Serv d then stores this new deployment list F2 associated with the terminals 10, where appropriate with the information defining the set T of the terminals 10.
• the generation server Serv g incorporated in the file F2 generated the applications of the software package defined by the administrator U and which fulfilled the following 2 criteria, according to which such an application must be:
• the deployment list includes sub-lists respectively associated with each operating system managed by the system 100 according to the invention. Each sublist lists by package application identifiers selected for the operating system and associated data.
• Each terminal 10 is adapted for, regularly (for example once a day), via the telecommunications links 1 1 and the network R 1, to authenticate, and to establish a communication with the distribution server Serv d so as to download a new F2 deployment list that would be available on the server and then carry out actions based on this new deployment list.
• the terminal 10 via the telecommunications links 1 1 and the network R1, establishes a communication with the server Serv d and requires a connection to the distribution server Serv d .
• secure mutual authentication for example cryptographic authentication.
• the terminal 10 exchanges with the distribution server Serv d and determines, as a function of these exchanges, whether the deployment list F2 then made available on the server Serv d to the terminals 10 has already been downloaded by the terminal 10.
• the deployment list F2 is downloaded by the terminal 10 from the distribution server Serv d (if necessary this download is authorized only after it has been, moreover, verified by the server Serv d that said terminal 10 is part of the set T terminals 10 corresponding to this deployment list F2).
• the terminal 10 exploits the downloaded F2 deployment list. It implements in particular the following treatments: for each software application, hereinafter referred to as A 10 , installed on the terminal 10: if A 10 is not listed in the SOSX section of the deployment list F2 (X indicating the version and the type of the system; exploitation) which corresponds to the operating system X implemented by the terminal 10, then the terminal 10 uninstalls the software application A 10 ;
• the terminal performs the actions i / to Ni /:
• the terminal 10 determines whether the application A2 is already installed on the terminal 10.
• the terminal compares the version of the application A2 installed and that indicated by the version code of A2 indicated in the section Sosx- Following this comparison: if these compared versions are identical, there is no action relating to A2 to be carried out by the terminal 10; and if these compared versions of A2 are different, the terminal 10 downloads from the server Serv of the version of A2 indicated by the version code of A2 indicated in the section Sosx and replaces the software application A2 installed by the downloaded one (via conventionally a software update procedure).
• the terminal 10 downloads from the server Serv of the application A2 in the version indicated in the section Sosx, and it installs it while respecting the software dependencies of A2 indicated in the list of dependencies of the application A2 in the section Sosx: if the application A3 is identified in the list of dependencies of the application A2, the application A3 is downloaded and installed by the terminal 10 before A2.
• the terminals 10 are adapted to periodically query the Serv D server for the existence of a new deployment file F2. In another embodiment, the terminals 10 are notified of the existence of a new deployment file F2 to download by a message, or such a new deployment file F2 is sent to them directly.
• the deployment list (file F2) thus comprises for each type of operating system considered, in each version considered, a list of applications extracted from the set of applications E indicated by the administrator.
• the list of applications determined for the first version of the operating system may differ from that determined for the second version of the operating system for the following reasons:
• an application chosen by the administrator is not compatible with one of the two versions of the operating system
• the deployment list (file F2) in the embodiment considered, does not include any command. It gives the list of applications defined by the administrator in the set of applications E.
• the F2 deployment list has been constituted by the server Serv g consistently, ie the incompatible applications of the security strain of the mandatory security applications are not present.
• the invention also makes it possible to increase the performances and to reduce the necessary processing resources.
• the processes are indeed distributed between a central entity (above the generation server Serv g ) and the mobile terminals.
• the server Serv g is in charge of the listing of applications, consistency checks and the production of the generated deployment list (in the case above, the file F2) while each terminal, from the common file F2, performs processing to deduce the actions necessary to achieve according to the state of the terminal.
• the deployment list generated via the F2 file is unique (the server Serv g generates only one file F2 for a set of terminals and not one file per terminal).
• the file F2 that a terminal exploits has not been established by the server according to the state of this particular terminal, in particular has been established independently of the applications and operating system specifically implemented on this particular terminal.
• the embodiment described with reference to the figures above uses two servers Serv g and Serv d connected via a network R2. This is only one embodiment of the invention among others. In other embodiments, for example, only one server is used to perform the operations performed by these servers Serv g and Serv d .

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• General Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Computer Security & Cryptography (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Stored Programmes (AREA)
• Information Transfer Between Computers (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=51564677

Family Applications (1)

Country Status (6)

Families Citing this family (13)

Family Cites Families (6)

• 2014
  • 2014-02-17 FR FR1400428A patent/FR3017725A1/fr not_active Withdrawn
• 2015
  • 2015-02-13 KR KR1020167025578A patent/KR20160122254A/ko unknown
  • 2015-02-13 WO PCT/EP2015/053098 patent/WO2015121418A2/fr active Application Filing
  • 2015-02-13 CN CN201580019121.3A patent/CN106164861A/zh active Pending
  • 2015-02-13 EP EP15704785.3A patent/EP3108361A2/de not_active Withdrawn
  • 2015-02-13 US US15/119,409 patent/US20170068531A1/en not_active Abandoned

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events