WO2011085631A1

WO2011085631A1 - Method, system and server for collecting version of software

Info

Publication number: WO2011085631A1
Application number: PCT/CN2010/080514
Authority: WO
Inventors: 李世平
Original assignee: 腾讯科技（深圳）有限公司
Priority date: 2010-01-13
Filing date: 2010-12-30
Publication date: 2011-07-21
Also published as: SG182486A1; CN101794222A; BR112012017294A2; BR112012017294B1

Abstract

A method for collecting version of software comprises: a server receives first version information of the software used in the device of a user client, the first version information is sent by the user client. Deciding whether the first version is new than the second version based on the first version information and the second version information of the software recorded in the server. If the result is true, the second version information recorded in the server is updated. According to the user client version number which is sent by the user client, whether the software has a new version is decided. Collecting and recording do not need manual work. The message for obtaining the software updating version is greatly improved. A server, a system for collecting a version of software and a user client are also provided.

Description

Software version collection method, system, server

Technical field

The present invention relates to computer technology, and in particular, to a software version collection method, system, and server. Background of the invention

With the development of computer technology, more and more software is installed on electronic devices such as personal computers, personal digital assistants (PDAs), smart phones, and Internet TVs. These softwares are also used more and more widely, including instant messaging and audio. Video playback, resource downloading, web browsing, input methods, system assistance, etc. With the popularity of the Internet, the software used by ordinary users has been transformed from a CD-ROM distribution ten years ago to a mode of downloading through the Internet, which greatly facilitates users to obtain software. At the same time, the software version upgrade speed has changed from half a year ago or once a year to once a month or even a few days. Updates to the software version may involve adding new features, addressing bugs and vulnerabilities in older versions, and more. Users can experience the latest features of the software with the latest version of the software, and also avoid the security threats to the computer from known vulnerabilities in the software. Therefore, there are currently software installed by the management software management user that allows the user to obtain the version of the installed software and check whether the installed software has an upgraded version.

The traditional management software detects whether there is an upgrade method by storing the latest version of various software and related description information in the server-side device of the management software, and the management software operation personnel download the station from various software official websites or software. Obtain the latest version of the software. When a software is upgraded, the operator will fill in the latest version of the software and related description information into the software upgrade configuration system of the management software server device. In this way, the management software client can get the latest version of the various software from the management software server. This software upgrade detection method requires high operating costs. There are thousands of software that need to be maintained on the management software server. Many operators need to manually collect upgraded versions of the software. Summary of the invention

Based on this, an embodiment of the present invention provides a software version collection method, which can automatically obtain new version information of the software.

The embodiment of the invention provides a server, which can automatically obtain new version information of the software. The embodiment of the invention provides a software version collection system, which can automatically obtain new version information of the software.

A software version collection method, comprising: receiving, by a server, information of a first version of software used in a client device sent by a client;

Determining, according to the information of the first version and the information of the second version of the software recorded in the server, whether the first version is newer than the second version;

If so, the information of the second version of the server record is updated.

A server, comprising:

a first module, configured to receive information about a first version of software used in a client device sent by a client, and notify the second module;

a second module, configured to determine, according to information about the first version received by the first module, and information about a second version of the software recorded by the third module, whether the first version is greater than the second version New; if yes, updating the information of the second version recorded by the third module.

A software version collection system includes: a server and a client;

The server is used to:

Receiving a letter from the first version of the software used in the client device sent by the client Interest rate

Determining, according to the information of the first version and the information of the second version of the software recorded in the server, whether the first version is newer than the second version; if yes, updating the second version of the server record information. BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart of a software version collection method of a client;

2 is a flow chart of a software upgrade detection method;

Figure 3 is a flow chart of the working process of the client;

Figure 4 is a block diagram of the software version management system and the software upgrade detection system. Mode for carrying out the invention

In order to solve the problem that the manual collection software is time-consuming and labor-intensive, the embodiment of the present invention provides a software version collection method. The method mainly includes:

Receiving, by the server, the version information of the software in the client device sent by the client; determining, according to the received version information and the version information of the software recorded in the server, whether the version of the software in the client device is greater than The version of the software recorded in the server is new;

If the version of the software in the client device is newer than the version of the software recorded in the server, the received version information is recorded.

The version information is used to determine the old and new versions of the software, and is usually a version number, a version release time, a version name, and the like.

The above method can automatically obtain a new version of the software because, after the software publisher releases a new software version, some users will download and upgrade first, or some users' software will be set to the automatic upgrade mode. At this time, the network is There are some clients that use the new version of the software. By collecting the version number of these software from the client, you can discover a new software. Version, at this time, the server of the management software can notify the client of the management software of the new version, and the client of the management software prompts the user to upgrade, and the whole process is automatically completed by the computer without manual intervention, thereby greatly improving the acquisition of the software upgrade. The efficiency of the version.

Through the above method, the version information of the software specified by the server can be obtained, and the version information of all software installed in the client, such as web browsing software, file downloading software, office software, antivirus software, media playing software, game software, etc., can be obtained. Software that people may use in their work life.

The above is the processing flow on the server side. The above-mentioned server may be a stand-alone device or a module in other devices; it may be located in one device or in multiple devices, so it is sometimes referred to as a server, a server, or a management software server. It is for the client. The invention does not limit the specific implementation of the server, the number of devices, and the like.

One embodiment of the present invention provides a software upgrade detection method. Software upgrade detection refers to whether the detection software has an upgraded version. It is a specific example of the software version collected in the previous article. The method includes the following steps: receiving a client version number of the software in the software list of the client; determining whether the client version number is new to a server version number corresponding to the client version number; if the client version number If the server version number is new, the server version number is updated.

The client version number is a cartridge name of the version number of the software installed in the client device; the server version number is a cartridge name of the version number of the software recorded in the server.

Determining whether the client version number is new to the server version number corresponding to the client version number may include: counting the client version number of each client, and the number is greater than a threshold and higher than a server version number. The client version number is the client version number new to the server version number.

Another embodiment of the present invention also includes the step of pushing the server version number to the client. Specifically, it may be determined whether the server version number is new to the received client version number, If yes, the server version number new to the client version number is sent to the client.

Correspondingly, an embodiment of the present invention provides a software upgrade detection system, including: a server transceiver unit, receiving a client version number of software in a software list of a client; a storage unit, storing a server version number;

a processing unit, connected to the server transceiver unit and the storage unit, determining whether the client version number is new to a server version number corresponding to the client version number, if the client version number is newer than the The server version number updates the server version number in the storage unit.

The processing unit may count the client version number of each client, and use the client version number whose number is greater than the threshold and higher than the server version number as the client version number new to the server version number. By statistics, only when the number of client version numbers higher than the server version number is greater than the threshold, the new version is recognized, and the wrong version number or the unstable test version is also changed to become a new version, which improves the stability of the user's software. . The client version number, if yes, the server version number new to the client version number is sent to the client through the server transceiver unit.

The following is a processing flow of the client in one embodiment of the present invention. The client, also known as the client of the management software, can be implemented by a hardware module or by software. The physical device on which the client is located, or the physical device that the client can access through direct or indirect connection, wired or wireless connection, belongs to the client device of the present invention. In the following text, the software version collection client and client device are sometimes referred to as the client, but it can be clearly seen from the context that the software version collection operation is to collect the client for the software version, and the software list, software version number, etc. It is extracted from the client device.

A software version collection method includes: obtaining a client of a software in a client's software list The client version number; send the client version number to the server.

The client version number refers to the version number of the software in the client device. The client's software list refers to a list of information obtained by the client to obtain information about one or more of the software in the client device. There may be one software or multiple software in the software list, that is, the client may select one or more software from all the software of the client device to form a software list.

The client version number can be obtained by uninstalling the DisplayVersion key in the node in the software in the registry, or the executable resource corresponding to the main program or the configuration file in the software installation directory. It is quick and easy to obtain the client version number through the software in the registry to uninstall the DisplayVersion key in the node, the exe resource corresponding to the main program, or the configuration file in the software installation directory.

A list of software for the client can also be obtained.

The client's software list can be obtained through the software uninstall list of the registry, the desktop shortcut, the application list in the Windows Start menu, and the shortcut in the Windows Quick Launch bar.

The embodiment of the invention provides a software version management system for obtaining a software upgrade version number, which includes:

The version number obtaining unit obtains a client version number of the software in the software list of the client; the client transceiver unit is connected to the version number obtaining unit, and sends the client version number to the server.

The version number obtaining unit uninstalls the node through a software in the registry

The client version number is obtained from the DisplayVersion key value, the executable resource corresponding to the main program, or the configuration file in the software installation directory.

The system may further include a software list obtaining unit, connected to the version number obtaining unit, configured to acquire a software list of the client.

The software list obtaining unit uses a software uninstall list of the registry, a desktop shortcut, The list of applications in the Windows Start menu, and the shortcuts in the Windows Quick Launch bar get the list of software for the client.

The system may also include a determination unit and an upgrade unit. The client transceiver unit is further configured to receive a server version number, and the determining unit is connected to the client transceiver unit, and configured to determine whether the server version number is new to the client version number. The upgrading unit is connected to the determining unit, and prompts the user when the determining unit determines that it is YES and upgrades or automatically upgrades according to the user instruction. By judging whether the server version number is newer than the client version number, when the server version number is newer than the client version number, the user is prompted and upgraded or automatically upgraded according to the user instruction, so that the upgrade process is performed according to the user's needs or automatically upgraded in the background. Great convenience for users.

The above is the structure corresponding to the client in the system.

The above software version collection method, management system, and software upgrade detection method and system determine whether there is a new version by reporting the client version number or receiving the client version number reported by the client, and does not need to manually collect and input, thereby greatly improving the acquisition. The speed of the software upgrade version.

The embodiments of the present invention will be described below by way of specific examples.

Figure 1 is a flow chart of the software version collection method of the client. As shown in Figure 1, the method includes the following steps:

Step S110: Obtain a software list of the client device.

The list of software in the client device can be obtained through the software uninstall list of the registry, the desktop shortcut, the application list in the Windows Start menu, and the quick way in the Windows Quick Launch bar. For example, the registry path is: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVers ion\UninstalL

The client obtains all the software in the client device and generates a list of software, or only Take a portion of the software to form a list of software. The specific manner can be determined according to preset configuration parameters, or can be determined by obtaining configuration information from the server side each time or periodically. The configuration parameters may be: forming a software list based on only one or more software specified in advance, or forming a software list based on all software in the client device, or forming a software list based on the most frequently accessed software in the client device. The number of times the software is accessed, the time, etc. can be obtained by using the statistical results of some software with statistical functions already in the client device, or can be counted by the client. The configuration information obtained from the server may be a list in the server, including software that all the servers need to obtain information. After obtaining the list, the client only extracts the information of the software listed in the list from the client device to form a software list. .

This step can also be omitted if it is preset in the client of the management software that the software needs to report the software version number. The software included in the software list may include instant messaging software, audio and video playback software, resource download software, web browsing software, input method software, and the like. The timing of obtaining the client software list may be determined according to preset parameters, for example, may be performed at predetermined intervals, or may be performed each time the power is turned on, or may be performed when the client management software is started, and the like.

Step S120: Obtain a client version number of the software in the software list of the client. The client version number can be obtained from the Display Version key in the software uninstallation node in the registry, the exe resource corresponding to the main program (executable resource), or the configuration file in the software installation directory. In the registry of the Windows system, the Display Version key value in the software uninstallation node records the version number of the software; the version label of the attribute of the exe resource corresponding to the main program also records the version number of the software; The version number of the software is usually also recorded in the configuration file under the installation directory.

Step S130, sending the client version number to the server. After the client version number is collected, the client version number of each software is sent over the network to the server along with its software name and/or code. It can be that the client uploads immediately after collecting the client version number, or it can be Uploading at a preset time can also be based on network conditions (for example, when the network is idle).

Reporting the client version number through the client does not require manual collection and input, which greatly improves the speed of obtaining the software upgrade version.

FIG. 2 is a flowchart of a software upgrade detection method on the server side. As shown in Figure 2, the method can include the following steps.

Step S210: Receive a client version number of the software in the software list sent by the client. The client version number and the software name and/or code corresponding to the client version number are received over the network. The server can store the received information, analyze the received information, and update the statistics stored in the server. For example, the server can count the number of times a certain version of the software is received, the time, the client identifier that sent the information, the identity of the client device, and so on.

Step S220: Determine whether the client version number is new to a server version number corresponding to the client version number. That is, the version number of the software received from the client is compared with the version number of the same software stored in the server, and it is judged whether the received version number is updated.

The received client version number can be compared with its corresponding server version number - if the client version number is higher than the server version number, it is determined that the client version number is newer than the server version number. In a further improved implementation, the client version number sent by each client may be counted, and the client version number whose number is greater than the threshold and higher than the server version number is used as the client version new to the server version number. number. By statistics, only when the number of client version numbers higher than the server version number is greater than the threshold, the new version is recognized, and the wrong version number or the unstable test version is also changed to become a new version, which improves the stability of the user's software. . For example, the actual latest version number of a software is 5.0, and the client version number data of the software is received in 1 million copies, of which 10 client version numbers are 6.0 (the reason may be the software publisher's non- Official beta), because of 10 data ratios It is very small, so it can be eliminated by the threshold method. For example, if the threshold is set to 128, 6.0 will be considered as a new version only when the client version number is 6.0 or more than 128. It is also possible to set the threshold to the ratio of the number of copies of the new version to the total number of copies of the received version information, for example, 5%, 1/10, and the like. Statistics can be performed periodically at predetermined time intervals, for example, once a day, every three days, or once a week, etc., or based on the total number of copies reported by the client. For example, the software version information sent every 10,000 clients is counted once. When performing statistics, the server needs to perform deduplication on the received version information of the client, that is, the duplicated report information of the same client is removed, and only the information reported by different clients is retained. The statistics can be cleared after each statistics according to the preset configuration in the server, or can be accumulated according to the preset policy. The specific statistical method can be designed according to actual conditions, and the present invention does not limit specific statistical methods.

In the above example, the version number of the common format (the Arabic numeral plus the decimal point format) is explained. In other examples, the version number can also be expressed in the form of letters or even symbols.

Step S230: Update the server version number if the client version number is new to the server version number. By updating, the version number of the server record of the management software server is modified to a new version number, so that the state of the software recorded in the server is in a new state.

Step S240: Push the server version number to the client. Send the server version number of the software to the client along with the software name or code. Because the version number recorded by the server is in a new state through the above steps, it is pushed to the client, which is convenient for reminding the user to the client device. The software is upgraded and synchronized.

In other embodiments, this step may be omitted, but when the client issues a query request, it responds to the request and replies to the server version number. In addition, in an alternative embodiment, this step may be replaced by determining whether the server version number is new to the client version number received in step S210, and if yes, sending the server version number new to the client version number to the client. end. With the present embodiment, in the case of a large variety of software and a very large number of clients, it is possible to avoid pushing a large amount of data, and to ensure that the software version is actively upgraded when the client does not query. The server determines whether the software version stored in the server is newer than the software version reported by the client, and may be performed when the next time the client receives the software version information, or the server records the software version reported by the client, and the updated version. After the information is judged. It may also be that the server records the corresponding relationship between each version of the software and the client identifier that reports the version, for example, version 4.0 corresponds to the client 1, 2, 3, and version 5.0 corresponds to the client 4, 5, 6, server update version information. After that, the corresponding client ID is found according to the old version, and the new version information is sent to the corresponding client. Of course, in order to reduce the workload of the server, the server can send new version information to all clients, and the client determines whether the version of the client device is up to date and reminds the user of a new software version.

After receiving a large number of client version numbers reported by the client, a large number of client version numbers can be used to determine whether there is a new version. After the software publisher releases a new software version, some users will download and upgrade first. Or some users' software is set to the automatic upgrade mode. At this time, there are some new versions of software on the network. By collecting the version numbers of these softwares, a new version of a certain software can be found.

When the server actively pushes the server version number or the client sends a query request, and the server responds to the request and replies to the server version number, the working process of the client is as shown in FIG. 3. Figure 3 is a flow chart of the working process of the client, which mainly includes the following steps.

Step S310, receiving a server version number.

In step S320, it is determined whether there is a new version. The client determines whether the server version number is newer than the client version number, and if yes, proceeds to step S330, otherwise the process ends.

Step S330, prompting the user or automatically upgrading. For example, a pop-up prompt box prompts the user to have a new version, whether to upgrade, and upgrade according to user instructions when the user selects the upgrade. In addition, also Instead of prompting the user to automatically upgrade, it is recorded locally, and is provided to the user when the user makes a query request.

By judging whether the server version number is newer than the client version number, when the server version number is newer than the client version number, the user is prompted and upgraded or automatically upgraded according to the user instruction, so that the upgrade process is performed according to the user's needs or automatically upgraded in the background. Great convenience for users. In addition, as shown in FIG. 4, a software version management system of the client and a software upgrade detection system of the server are also provided.

The software version management system includes a software list obtaining unit, a version number obtaining unit, a client transceiver unit, a judging unit, and an upgrading unit.

The software list obtaining unit acquires a software list of the client. The software list obtaining unit obtains the software list of the client through a software uninstall list of the registry, a desktop shortcut, an application sequence table in the Windows start menu, and a shortcut in the Windows quick launch bar.

The version number obtaining unit is connected to the software list obtaining unit to obtain the client version number of the software in the software list of the client. The version number obtaining unit obtains the client version number by using the Display Version key value in the software uninstallation node in the registry, the exe resource corresponding to the main program, or the configuration file in the software installation directory.

The client transceiver unit is connected to the version number obtaining unit to send the client version number to the server.

The client transceiver unit is further configured to receive the server version number, and the determining unit is connected to the client transceiver unit to determine whether the server version number is new to the client version number, and the upgrading unit is connected to the determining unit, and the user is prompted when the determining unit determines to be Upgrade or auto-upgrade according to user instructions. The software upgrade detection system includes a server transceiver unit, a storage unit and a processing unit. The server transceiver unit is configured to receive a client version number of the software in the client's software list.

The storage unit is used to store the server version number.

The processing unit is connected to the server transceiver unit and the storage unit, and determines whether the client version number is new to the server version number corresponding to the client version number. If the client version number is new to the server version number, the processing unit is updated. Server version number. In a preferred embodiment, the processing unit counts the client version number of each client, and uses the client version number whose number is greater than the threshold and higher than the server version number as the client version number new to the server version number. Further, the processing unit further determines whether the server version number is new to the received client version number, if the client. And the detailed description is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the invention. Therefore, the scope of the invention should be determined by the appended claims.

Claims

Claim

A software version collection method, characterized in that:

The server receives information of the first version of the software used in the client device sent by the client;

If so, the information of the second version of the server record is updated.

2. The method of claim 1 wherein:

When the first version is newer than the second version, the method further includes: determining whether the number of times the information of the first version is received is greater than a first threshold, if the number of times the information of the first version is received is greater than a threshold value, performing the step of updating the second version information recorded by the server; or

When the first version is newer than the second version, the method further includes: determining whether a ratio of the number of times the information of the first version is received to the total number of times of all the version information of the received software is greater than a second threshold, if the ratio of the number of times the first version of the information is received to the total number of times the recorded version information of the software is received is greater than the second threshold, performing the second version information recorded by the update server step.

3. The method of claim 2, wherein:

The number of times the first version information is received is the number of times the first version information is received within a predetermined time period.

The method according to claim 2, further comprising: after receiving the information of the first version sent by the client, determining whether the information of the first version is received from the client If received, the number of times the information of the first version is received is not increased.

5. The method according to claim 1, further comprising: The recorded second version of the information is provided to the client.

6. The method according to claim 1, further comprising: obtaining, by the client, information of the first version of the software in the client device;

Sending the first version of the information to the server.

The method according to claim 6, wherein the information of the first version is a Display Version key value in a node from a software in a registry, an executable resource corresponding to a main program, or a software installation directory. Obtained in the configuration file.

8. The method of claim 6, further comprising: obtaining a list of software in the client device; performing the obtaining step for each software in the list.

9. The method according to claim 8, wherein the list of software is a software uninstall list from a registry, a desktop shortcut, an application list in a Windows Start menu, and a shortcut in a Windows Quick Launch bar. Obtained in .

10. A server, comprising:

11. The server of claim 10, wherein:

The second module is configured to determine, when the first version is newer than the second version, whether the number of times the information of the first version is received is greater than a first threshold, if the first version is received The step of updating the information of the second version recorded by the third module when the number of times of the information is greater than the first threshold; or determining that the first version is newer than the second version, Whether the ratio of the number of times the first version of the information is received to the total number of times the recorded version information of the software is received is greater than a second threshold, if the first version is received The step of updating the information of the second version recorded by the third module is performed when the ratio of the number of times of the information to the total number of times the recorded all the version information of the software is received is greater than the second threshold.

12. The server of claim 11 wherein:

The second module is configured to compare the number of times the first version information is received within a predetermined time period with the first threshold.

13. The server of claim 11 wherein:

The first module is further configured to: after receiving the information of the first version sent by the client, determine whether the information of the first version is received from the client, and if not received, not notify The second module.

The server according to claim 10, further comprising: a fourth module, configured to provide information about the second version recorded by the third module to the client.

15. A software version collection system, comprising: a server and a client; the server is configured to:

Receiving information of the first version of the software used in the client device sent by the client;

Determining, according to the information of the first version and the information of the second version of the software recorded in the server, whether the first version is newer than the second version; if yes, updating the second version of the server record information.

16. The system of claim 15 wherein:

The server is used to:

When it is determined that the first version is newer than the second version, further determining whether the number of times the information of the first version is received is greater than a first threshold, if the number of times the information of the first version is received is greater than the first At the threshold, performing the step of updating the second version information recorded by the server; or When it is determined that the first version is newer than the second version, further determining whether the ratio of the number of times the first version of the information is received to the total number of times the recorded version information of the software is received is greater than the second a threshold, if the ratio of the number of times the first version of the information is received to the total number of times the received version information of the software is received is greater than a second threshold, performing the step of updating the second version information recorded by the server .

17. The system of claim 16 wherein:

The server is used to:

The number of times the first version information is received within a predetermined period of time is compared to the first threshold.

18. The system of claim 16 wherein:

The server is further used to:

After receiving the information of the first version sent by the client, determining whether the information of the first version is received from the client, and if received, not adding the information of the first version. The number of times.

19. The system of claim 15 wherein:

The server is further used to:

The recorded second version of the information is provided to the client.

20. The system of claim 15 wherein:

The client is used to:

Obtaining information of the first version of the software in the client device;

Sending the information of the first version to the server.

21. The system of claim 20 wherein:

The client is configured to obtain the information of the first version from a Display Version key in a software uninstallation node in the registry, an executable resource corresponding to the program, or a configuration file in a software installation directory.

22. The system according to claim 20, wherein: the client is further configured to: obtain a list of software in the client device, and perform the obtaining step for each software in the list.

23. The system of claim 22, wherein:

The client is configured to obtain the list from a software uninstall list of a registry in the client device, a desktop shortcut, an application list in a Windows Start menu, and a shortcut in a Windows Quick Launch bar.