• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    METHOD, SYSTEM AND SERVER TO COLLECT SOFTWARE VERSIONS. The present invention relates to a method for collecting software versions: a server receiving information from a first version of software installed on a client's client device; judges whether the first version is newer than a second version based on information from the first version and information from the second version of the software written on the server; updates the second version information saved on the server in response to a determination that the first version is newer than the second version. A new version of a software can be detected based on client-side versions reported by the client without manual collection and insertion work, so the efficiency of obtaining updated software versions is greatly improved. In addition, a server, a system and a client to collect software versions are also provided.
    公开号:BR112012017294B1
    申请号:R112012017294-8
    申请日:2010-12-30
    公开日:2020-12-22
    发明作者:Shiping Li
    申请人:Tencent Technology (Shenzhen) Company Limited；
    IPC主号:
    专利说明:

    TECHNICAL FIELD
    [0001] The present invention relates to computer technology, and specifically to a method, a system and a server for collecting software versions. BACKGROUND
    [0002] With the development of computer technology, electronic devices, such as personal computers, personal digital assistants (PDAs), smart phone devices, Internet televisions and so on, are increasingly installing software applications. Software applications are used in more and more fields, such as instant messaging, audio / video playback, resource downloads, web browsing, text, system assistance and so on. As the Internet becomes more and more popular, ordinary users now generally go to the Internet to obtain software applications which were distributed over compact discs ten years ago, which is more convenient for users to obtain software. Meanwhile, the interval between two updates to a software application is shrinking from a year or half a year ten years ago to a month or a few days now. A new version of a software application can provide new functions, and fix vulnerabilities and defects in older versions. Using a new version of a software application, a user can experience new functions of the software and can avoid security risks brought about by known vulnerabilities in the software. Therefore, there is currently a management software to manage the software applications installed by a user, helping the user to obtain the version of the installed software applications, and to detect whether an installed software application has a new version.
    [0003] Conventional software management detects whether a software application needs an update by storing the latest version information and corresponding description information for various software applications on a management software server device. Operating personnel obtain the latest versions of the various software applications from their respective official websites or from websites that provide a software download. When a software application is updated, operating personnel will insert the latest version and corresponding description information for the software application into a software update configuration system on the management software server device. Thus, a management software client is able to gain knowledge of the latest versions of various management software server applications.
    [0004] The above way of detecting software updates generates high costs, because there are tens of thousands of software applications needed to be maintained on the management software server and a large number of operating people are required to manually collect updated versions of software applications. SUMMARY
    [0005] Therefore, the modalities of the present invention provide a method for collecting software versions which can obtain information about new software versions automatically.
    [0006] The modalities of the present invention also provide a server which is able to obtain information from new software versions automatically.
    [0007] The modalities of the present invention still provide a system for collecting software versions which can obtain information about new software versions automatically.
    [0008] A method for collecting software versions may include: receiving, by a server, information from a first version of software installed on a client device sent by a client; judging whether the first version is newer than a second version based on information from the first version and information from the second version of the software written on the server, update the information from the second version written on the server in response to a determination that the first version is newer than the second version.
    [0009] A server can include: a first module, to receive information from a first version of software installed on a client device sent by a client, and provides the information for a second module; a second module, to judge whether the first version is newer than a second version based on the information from the first version received by the first module and information from the second version of the software recorded in a third module; update the second version information recorded in the third module in response to a determination that the first version is newer than the second version.
    [00010] A system for collecting software versions can include a server and a client; and the server is for: receiving information from a first version of software installed on a client device sent by a client; judge whether the first version is newer than a second version based on information from the first version and information from the second version of the software written on the server; update the information from the second version written on the server in response to a determination that the first version it is newer than the second version. BRIEF DESCRIPTION OF THE DRAWINGS
    [00011] Figure 1 is a flow chart that illustrates a method of a customer collecting software versions.
    [00012] Figure 2 is a flow chart illustrating a method for detecting software updates.
    [00013] Figure 3 is a flow chart that illustrates a customer's work-process.
    [00014] Figure 4 is a block diagram that illustrates a structure of a software version management system and a software update detection system. MODALITIES OF THE INVENTION
    [00015] In order to solve the problem of high cost and time consuming results of collecting software versions manually, the modalities of the present invention provide a method for collecting software versions. The method mainly includes: receiving, by a server, the version information of software installed on a client device sent by a client; judging whether a first version on the client device is newer than a second version of software recorded in the server based on version information received and information from the second software version recorded on the server; recording version information received in response to a determination that the software version on the client device is newer than the recorded software version in the server.
    [00016] Information for a version refers to information which can be used which can be used to determine whether the version is newer or older than another version. The version information can generally be a version number, or the version release date, or the version name, and so on, and are not limited to the present invention.
    [00017] The above method can automatically obtain knowledge of a new version of a software. As there are always some users who download a new version of a software and update the software immediately after the new version is released by the software editor or configure their software in an automatic update mode, there are always some clients on the network who use the latest version of software. By collecting client software version numbers, the management software server device can identify a new version of software, and inform clients of the new version management software. Then management software customers can induce information by suggesting users update the software. The entire process is implemented by computers without involving any manual work, thus greatly improving the efficiency of updated software versions.
    [00018] The above method can be used to obtain version information for software specified by a server, or to obtain version information for all software used on a daily basis and installed on clients, including Internet browsing software. Web, file download software, office software, antivirus software, media player software, game software, and so on.
    [00019] The above is the working process of the server device. The server above can be a standalone device, or a module on another device; it can reside on one device or can be distributed across multiple devices, so it is also referred to as a server-side device, server-end device or server-end of the management software, which is from the customer's perspective. The present invention does not limit the mode of implementation of the server-side device or the number of server devices.
    [00020] One embodiment of the present invention provides a method for detecting software updates. Software update detection refers to detecting whether a software has an updated version, and is an example of the above process for collecting software versions. The method may include the following procedures: receiving a client-side version number of software in a list of client software; judge whether the client-side version number represents a newer version than a version represented by a server-side version number of the software; update the server side version number if the client side version number represents a newer version than the version represented by the server side version number.
    [00021] The client side version number refers to the version number of the software installed on the client device; the server side version number refers to the version number of the software written on the server.
    [00022] Specifically, the procedure of judging whether the client-side version number represents a newer version than a version number represented by the server-side version number may include: collecting statistics from the version side of the server side. client, take a version number which represents a newer version than a version represented by the server side version and the number of which exceeds a limit according to the client side version number which represents a newer version of than a version represented by the server side version number.
    [00023] An embodiment of the present invention also provides a procedure of pushing the server side version number to a client. Specifically, it is judged whether the server side version number is a newer version than a version that corresponds to the client side version number received from the client, and the server side version number is sent to the client if the server side version number is a newer version than a version that matches the client side version number.
    [00024] Consequently, an embodiment of the present invention provides a system for detecting software updates. The system can include: a server-side send / receive unit to receive a client-side version number of software in a list of software on the client; a storage unit for storing a server-side version number; a processing unit, connected to the server-side send / receive unit and the storage unit, to judge whether the client-side version number is a newer version than a version that matches the version number of the server side of the software, update the server side version number on the storage unit if the client side version number is a newer version than the version that corresponds to the server side version number.
    [00025] The processing unit can collect statistics on client client side version numbers, and take a client side version number whose value exceeds a threshold and which is of a newer version than a version that matches the server side version number as the client side version number of a newer version than the version that matches the server side version number. Collecting statistics, only the client-side version number whose value is greater than a threshold is considered a new version to prevent an incorrect version or an unstable beta version from being considered the new version, which can thus increase the stability of the software provided to the user.
    [00026] The processing unit can also judge whether the server-side version number is a newer version than a version that corresponds to a client-side version number received from a client, and send the number of server side version for the client if the server side version number is a newer version than the version represented by the client side version number.
    [00027] Below is an exemplary customer processing flow according to an embodiment of the present invention. The client, which is also referred to as the management software client, can be implemented by hardware modules or by software. A physical device where the customer resides and / or a physical device accessible by the customer directly or indirectly via wired or wireless connections can be considered as the customer device of the present invention. Throughout the description, the so-called customer can sometimes refer the customer to collect software versions, and sometimes refer to a customer device. But from the context it is clear that the entity that performs the software version collection is the client to collect the software versions, while information such as the software list, the software version number and so on is obtained from the device customer.
    [00028] A method for collecting software versions may include: obtaining a client-side version number of software from a list of software on the client, sending the client-side version number to the server.
    [00029] The client side version number refers to a version number of the software installed on the client device. The list of software on the client refers to a list formed by the client with the information of one or multiple software installed on the client. The software list can include one or multiple software, that is, the customer can select one or multiple software from all the software installed on the client device to form the software list.
    [00030] The client-side version number can be obtained from a DisplayVersion key value from a software uninstallation node in a registry, or from executable resources in the main software program, or from a configuration file in a directory installation software. It is very simple and convenient to obtain the client-side version number of the DisplayVersion key value from the software uninstall node in a registry, or from executable features of the main software program, or from a configuration file in a directory. software installation.
    [00031] A list of software installed on the client can also be obtained.
    [00032] The client software list can be obtained from a registry software uninstall list, or from desktop shortcuts, or from the list of applications in the Windows start menu, or from shortcuts on a launch toolbar Windows fast.
    [00033] One embodiment of the present invention provides a system for managing software versions which can obtain an updated version number of software. The system can include: a version number obtaining unit, to obtain a client side version number of software from a list of software installed on a client; a client-side send / receive unit, connected with the version number obtaining unit, to send the client-side version number to a server-side device.
    [00034] The client-side version number can be obtained from a DisplayVersion key value from a software uninstallation node in a registry, or from executable resources in the main software program, or from a configuration file in a directory installation software.
    [00035] The system may also include a unit for obtaining a software list which is connected with the unit for obtaining a version number and is for obtaining a list of software installed on the client.
    [00036] The software list retrieval unit can obtain the client's software list from a registry software uninstallation list, or from desktop shortcuts, or from the list of applications in the Windows start menu, or from shortcuts in a Windows quick launch toolbar.
    [00037] The system can also include a trial unit and an update unit. The client-side send / receive unit may also be for receiving a server-side version number; the trial unit is connected to the client side send / receive unit and to judge whether the server side version number is a newer version than a version represented by the client side version number. The update unit is connected to the judgment unit, to update the software automatically or provide warning information to the user and update the software according to a user instruction when the judgment unit determines that the version number of the server is a newer version than the version represented by the client side version number. Judging whether a server-side version number is a newer version than the version represented by the client-side version number, warning the user when the server-side version number represents a newer version than the version represented by the client side version number, and updating the software automatically or providing warning information to the user and updating the software according to a user's instruction, the update process is allowed to be performed either in the background or in according to the user's needs, whichever is more convenient for the user.
    [00038] The above system illustrates a client side structure.
    [00039] The above method and management for collecting software versions, and the management method and system for detecting software updates determine whether a software has an updated version by having the customer report the version number of the client side of the software. software or receiving the client-side version number sent by the client, and does not require manual labor to collect and insert, thus speeding up the process of obtaining an updated version of software.
    [00040] The modalities of the present invention will be described in detail with reference to the following examples.
    [00041] Figure 1 is a flow chart that illustrates a method of a customer collecting software versions. As shown in figure 1, the process can include the following procedures.
    [00042] In block S110, a list of software installed on a client device is obtained.
    [00043] The client device software list can be obtained from a registry software uninstall list, or from desktop shortcuts, or from the list of applications in the Windows start menu, or from shortcuts on a toolbar Windows quick launch and so on. For example, the registry location can be: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows CurrentVersion Uninstal 1.
    [00044] The client can obtain the information of all the software installed on the client device to form the software list, or it can obtain the information of only some of the software to generate the software list. The adopted mode can be decided by pre-set configuration parameters or configuration information obtained from the server-side device at fixed intervals or each time when the client starts. The configuration parameters can be: form the software list based on one or multiple pre-designated software, or form the software list based on all the software installed on the client device, or form the software list based on most frequently used software. The time and number of times a software is visited can be obtained from statistics collected by certain statistical software on the client device, or can be collected by the client. The configuration information obtained from the server-side device can be a list on the server which lists all software whose information needs to be collected by the server. After obtaining the list, the customer can obtain the software information listed in the client device list to form the software list.
    [00045] If the client of the management software already had a list of software, whose information needs to be collected, configured in advance, the procedure in this block can be omitted. The software in the software list can include IM software, audio / video playback software, resource download software, web browsing software, text software, and so on. The time to obtain the client's software list can be determined according to pre-set parameters, for example, at pre-set intervals, or each time when the client device is started, or each time when the client of the software management starts, and so on.
    [00046] In block S120, a client-side version number of a software in the client's software list is obtained. The client-side version number can be obtained from a DisplayVersion key value from a software uninstall node in a registry, or from exe resources (executable resources) of the main software program, or from a configuration file in a software installation directory. In the registration of a Windows system, the DisplayVersion key value of a software uninstallation node records the software version number. A version identifier in the main program's exe resource attributes also records the software version number. The configuration file in a software installation directory can usually record the version number of the software.
    [00047] In block S130, the client side version number is sent to a server side device. After the client side version number is collected, the client side version number of each software can be sent to the server side device along with the software name and / or the software codes. The customer can send the client side version number immediately after the client side version number is obtained, either at a pre-set time or according to the network conditions (for example, when the network is not busy) ).
    [00048] The client side version number is reported by the client without manual collection and insertion work, so the process to obtain an updated version of a software is less time consuming.
    [00049] Figure 2 is a flow chart that illustrates a method for detecting software updates. As shown in figure 2, the method can include the following procedures.
    [00050] In block S210, a client-side version number of a software in a software list is received from a client. The client side version number and a software name and / or codes are received over a network. The server can store the information received, or it can analyze the information received and update the statistics stored on the server. For example, the server can count the number of times information for a certain version of software is received, the time when information is received, a client ID that sends the information, a client device ID, and so on.
    [00051] In block S220, it is judged whether the version number on the client side is a newer version than a version that corresponds to a version number on the server side of the software. Specifically, the server can compare the version number of the software received from the client with the version number of the software stored on the server to determine whether the version received is more recent.
    [00052] The server can compare the client side version number with the server side version number on a one-to-one basis, and determine that the client side version is newer than the side version. if the client side version number is greater than the server side version number. According to another modality, the processing unit can collect statistics of client-side version numbers of the software on all clients, and take a client-side version number which is received a number of times which exceeds a limit and which is of a newer version than the version corresponding to the server side version number as the client side version number of a newer version than the version corresponding to the version number of the server side. Collecting statistics, only the client-side version whose value is greater than a threshold is considered a new version to prevent an incorrect version number or an unstable beta version from being considered as the new version, which can thus increase the stability of the software provided to the user. For example, the version number of the latest version of a software is 5.0, and a total of 1 million items of data about the version numbers of the software are received. Among the data items received, a client-side version number of 6.0 is received 10 times (this version may be a beta test version from the software publisher). Since the 10 data items make up a small proportion of the total number of data items, the 10 data items can be filtered using a threshold. For example, the limit can be set to 128, and version number 6.0 is only considered as a new version when the number of data items received from version number 6.0 exceeds the limit of 128. The limit can be adjusted to reflect a specified ratio of the number of a version number received to the total number of all data items received, for example, can be 5%, 1/10, and so on. The calculation can be performed at predefined intervals, for example, once every day, once every three days, or once in a week and so on, and can also be performed when the total number of data items received reaches a specified value. For example, the calculation can be performed when every 10,000 items of software information sent by customers are received. When calculating, the server can perform a repeat removal for version information received from customers, that is, erase version information received from a customer from which the same version information was received previously to only save information received from different customers. The collected data can be erased after the calculation is performed according to pre-set configurations on the server, or can be accumulated according to a pre-set policy. The way of collecting the statistics can be designed according to practical needs, and is not limited in the present invention.
    [00053] The above examples take version numbers in the conventional form (ie Arabic numbers with a root point) as an example. In other examples, version numbers can be represented in other forms such as letters or even symbols.
    [00054] In block S230, the server side version number is updated in response to a determination that the client side version number represents a newer version than that represented by the server side version number. Through the update procedure, the version number recorded on the server side device of the management software is changed to be the new version number to maintain the status of the software written on the updated server end.
    [00055] In block S240, the server side version number is sent to a client side device. The server-side version number of the software can be sent to a client over the network along with the software name or codes. As the version number recorded on the server side is updated after the procedures described above, the server side version number sent to the client can be used to inform the user and advise the user to update and synchronize the software installed on the client .
    [00056] In other examples, the procedures in this block can be omitted. Instead, the client can send a query request, and the server responds to the request with the server side version number. In addition, in other examples, the procedures in this block may alternatively include: judging whether the server side version number is of a newer version than the version represented by the client side version number received in the S210 block, and send the server-side version number to the client in response to a determination that the server-side version is newer than the client-side version. According to this example, when there are mass quantities of software and clients, clients can be informed about which software has updated versions even if the client does not query the server, and at the same time there is no need to transmit a large amount of data . The above server procedure judging whether the software version stored on the server is newer than the software version received from the client can be run next time when the software version information is received from the client, or run after the server have recorded the software versions sent by customers and have updated the version information. Alternatively, the server can record a list which associates a version of a software with an identification of a customer who reported the version information. For example, a version 4.0 is correlated with clients 1, 2, 3, and a version 5.0 is correlated with clients 4, 5 and 6; after the server has updated the version information, the server can identify the customer IDs that are associated with an old version, and send the new version information to the customers. In order to reduce the server's workload, the server can send the new version information to all clients, so the client judges whether the version on the client device is the latest version and notifies the user that a new version exists of the software.
    [00057] After a large number of client-side version number reports have been received, it can be judged whether a new version exists based on the large number of client-side version number reports. As there are always some users who would download and update to a new version of a software immediately after the new version is released by the software editor or who sets their software in an automatic update mode, there are always some clients on the network who use the latest software version. By collecting client software version numbers, the management software server can identify a new version of software.
    [00058] Figure 3 illustrates a client's workflow when the server sends a server-side version number to the client at the server's own initiative or when the client sends a query request and the device from the server responds to the request with a server-side version number. Figure 3 is a flow chart that illustrates a customer's work process. The process may include the following procedures.
    [00059] In block S310, a server side version number is received.
    [00060] In block S320, it is judged whether there is a new version. The client judges whether the server-side version number is a newer version than a version represented by a client-side version number, and the procedure in block S330 is performed in response to a determination that the version of the server side is newer than a client side version, or the process is terminated in response to a determination that the server side version is not newer than the client side version.
    [00061] In block S330, the user is prompted to update or an automatic update is performed. For example, a warning box opens to inform the user that a new version is available and ask the user to update and the software is updated when the user chooses to update. Or, the warning information may not be displayed to the user, but stored on the local device, and provided to the user when the user submits a query request.
    [00062] Judging whether the server side version is newer than the client side version, notifying the user when the server side version is newer than the client side version, and updating the software automatically , or by providing warning information to the user and updating the software according to a user's instruction, the update process is performed either in the background or according to the user's needs, whichever is more convenient for the user.
    [00063] In addition, a system for managing software versions on the client side and a system for detecting software updates on the server side are provided, and are as shown in figure 4.
    [00064] The system for managing software versions may include a software list retrieval unit, a version number retrieval unit, a client-side send / receive unit, a trial unit and a update.
    [00065] The software list retrieval unit is for obtaining a list of software installed on a client. The software list retrieval unit can retrieve the software list from a registry software uninstall list, or from desktop shortcuts, or from a list of applications on a Windows start menu, or from shortcuts on a bar of Windows quick launch tools.
    [00066] The version number retrieval unit is connected with the software list retrieval unit, to obtain a client side version number of a software from the client's software list. The client-side version number can be obtained from a DisplayVersion key value from a software uninstall node in a registry, or from executable features of the main software program, or from a configuration file in an installation directory of the software.
    [00067] A client-side send / receive unit, connected with the version number obtaining unit, to send the client-side version number to a server-side device.
    [00068] The sending / receiving unit on the client side may also be to receive a version number on the server side. The judgment unit is connected to the client side send / receive unit to judge the server side version number to be a newer version than a version that corresponds to the client side version number. The update unit is connected to the judgment unit, to notify a user when the judgment unit determines that the server side version is newer than the client side version and to perform the update according to an instruction from the user or perform an automatic update.
    [00069] The system for detecting software updates may include a server-side send / receive unit, a storage unit and a processing unit.
    [00070] The server-side send / receive unit is for receiving a client-side version number of software in a list of software installed on the client.
    [00071] The storage unit is for storing a server side version number.
    [00072] The processing unit is connected to the sending / receiving unit on the server side and the storage unit, to judge whether the version number on the client side is a newer version than a version corresponding to the number version of the software server side, update the server side version number on the storage unit if the client side version is newer than the server side version. According to another modality, the processing unit can collect statistics on client-side version numbers of the software on all clients, and take a client-side version number whose information has been received a number of times which exceeds a limit and which is of a newer version than the version corresponding to the server side version number as the client side version number of a newer version than the version corresponding to the version number of the server side. The processing unit can also judge whether the server side version number is a newer version than a version that corresponds to a client side version number received from a client, and send the version number on the side from server to client if the server side version is newer than the client side version.
    [00073] The above modalities are merely examples of implementations of the present invention, and may include unnecessary details, so they should not be used to limit the scope of protection of the present invention. It should be clear to those skilled in the art that any modification or improvement within the principle of the invention must be covered within the scope of protection of the invention. Therefore, the scope of protection of the present invention must be determined by the degree defined by the indispensable technical characteristics presented in the claims.
    权利要求:
    Claims (20)
    [0001]
    1. Method for collecting software versions, comprising the steps of: receiving (S210), by a server, information from a first version of software installed on a client device sent by a client; judge (S220) if the first version is newer than a second version based on information from the first version and information from the second version of the software written on the server; update (S230) the information of the second version recorded on the server in response to a determination that the first version is newer than the second version; the method characterized by the fact that it still understands: to judge if the information of the first version was received a number of times which exceeds a first limit when the first version is newer than the second version, perform the step of updating the information of the second version recorded on the server when the first version information was received a number of times which exceeds the first limit; or judge whether a proportion of the number of times that the first version information was received in relation to the total number of times that the software version information was received exceeds a second limit when the first version is newer than the second version, perform the step of updating the second version information recorded on the server when the ratio of the number of receipts of the first version information to the total number of recorded receipts of the software version information exceeds the second limit.
    [0002]
    2. Method, according to claim 1, characterized by the fact that: the number of times the first version was received is the number of times the first version was received within a predefined period of time.
    [0003]
    3. Method, according to claim 1, characterized by the fact that it still comprises: judging whether the information from the first version was received from the customer after receiving the information from the first version from the customer, not making a change in the number of times that first version information was received when the first version information was received from a customer.
    [0004]
    4. Method, according to claim 1, characterized by the fact that it still comprises: providing (S240) recorded information of the second version for the customer.
    [0005]
    5. Method, according to claim 1, characterized by the fact that it still comprises: obtaining, by the customer, information from the first version of the software installed on a customer device; send the information from the first version to the server.
    [0006]
    6. Method, according to claim 5, characterized by the fact that the information of the first version is obtained from a key value of DisplayVersion in a software uninstallation node in a registry, or from executable resources of a main program or configuration file in a software installation directory.
    [0007]
    7. Method, according to claim 5, characterized by the fact that it still comprises: obtaining a list of software installed on a client device, performing the step of obtaining information on the first version of the software installed on the client device for each software in the software list.
    [0008]
    8. Method, according to claim 7, characterized by the fact that the software list is obtained from a software uninstallation list in a registry, or from desktop shortcuts, or from a list of applications in a start menu Windows, or shortcuts on a Windows quick launch bar.
    [0009]
    9. Server, comprising: a first module, to receive information from a first version of software installed on a client device sent by a client, and provides the information for a second module; a second module, to judge whether the first version is newer than a second version based on information from the first version received by the first module and information from the second version of the software recorded in a third module; update the information of the second version recorded in the third module in response to a determination that the first version is newer than the second version; characterized by the fact that: the second module is to judge whether the number of times the information from the first version has been received exceeds a first limit in response to a determination that the first version is newer than the second version, perform the step to update the second version information recorded in the third module when the number of times the first version information was received exceeds the first limit; or judge whether a proportion of the number of times that the first version information was received in relation to the total number of times that the software version information was received exceeds a second limit in response to a determination that the first version is newer than the second version, perform the step of updating the second version information recorded in the third module when the ratio of the number of receipts of the first version information to the total number of recorded receipts of the software version information exceeds the second limit.
    [0010]
    10.Server, according to claim 9, characterized by the fact that: the second module is to compare the number of times that the information from the first version was received within a predefined period of time with the first limit.
    [0011]
    11. Server, according to claim 9, characterized by the fact that: the first module is still for: judging whether the information from the first version was received from the client after receiving the information from the first version from the client, skip the step of informing the second module in response to a determination that information from the first version was received.
    [0012]
    12. Server, according to claim 9, characterized by the fact that it still comprises: a fourth module, to provide the information of the second version recorded in the third module for the client.
    [0013]
    13. System for collecting software versions, comprising: a server and a client; where the server is for: receiving (S210) information from a first version of software installed on a client device sent by a client; judge (S220) if the first version is newer than a second version based on information from the first version and information from the second version of the software written on the server; update (S230) the information of the second version recorded on the server in response to a determination that the first version is newer than the second version; characterized by the fact that the server is still: to judge if the number of times the information from the first version was received exceeds a first limit in response to a determination that the first version is newer than the second version, perform the step to update the second version information recorded on the server when the number of times the first version information was received exceeds the first limit; or judge whether a proportion of the number of times that the first version information was received in relation to the total number of times that the software version information was received exceeds a second limit in response to a determination that the first version is newer than that the second version, perform the step of updating the second version information recorded on the server when the ratio of the number of times the first version information was received to the total number of times the software version information was received exceeds the second limit.
    [0014]
    14. System, according to claim 13, characterized by the fact that: the server is still for: the second module is for comparing the number of times that the information of the first version was received within a predefined period of time with the first limit.
    [0015]
    15. System, according to claim 13, characterized by the fact that: the server is still to: judge whether the first version information was received from the client after receiving the first version information from the client, do not make any changes to the number times the first version information was received when the first version information was received from the customer.
    [0016]
    16. System, according to claim 13, characterized by the fact that: the server is still for: providing the recorded information of the second version to the client.
    [0017]
    17. System, according to claim 13, characterized by the fact that: the customer is still to: obtain the information of the first version of the software installed on the client device; send the information from the first version to the server.
    [0018]
    18. System, according to claim 17, characterized by the fact that: the customer is to obtain the information of the first version of a DisplayVersion key value in a software uninstallation node in a registry, or of executable resources of a main software program, or a configuration file in a software installation directory.
    [0019]
    19. System, according to claim 17, characterized by the fact that: the customer is still to: obtain a list of software installed on the client device, performing the obtaining step for each software in the software list.
    [0020]
    20. System, according to claim 19, characterized by the fact that: the client is to obtain the software list from an uninstall list of the registry, or from desktop shortcuts, or from a list of applications in a menu. Windows start, or shortcuts on a Windows quick launch bar on the client device.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112012017294B1|2020-12-22|method, system and server for collecting software versions
    US20120144379A1|2012-06-07|System and method for updadting software
    CN101789888B|2012-04-11|Detection method and device for software installation
    US20080126439A1|2008-05-29|Change verification in a configuration management database
    BRPI0807464B1|2019-05-14|Computer storage media and method implemented on a computational device
    US8869111B2|2014-10-21|Method and system for generating test cases for a software application
    US7721332B2|2010-05-18|Integrated software for managing add-ons
    JP2009512960A5|2010-03-04|
    WO2014166292A1|2014-10-16|Application program management method and apparatus, server, and terminal device
    US20060136892A1|2006-06-22|Embedded agent for self-healing software
    CN105094811A|2015-11-25|Method can device for processing events
    US9116808B2|2015-08-25|Method and system for determining device configuration settings
    US20110296395A1|2011-12-01|Systems and methods for generating client qualification to execute package update manager
    CN109831358B|2021-01-01|Client flow statistical method and device, server and readable storage medium
    CN109165259B|2021-12-21|Index table updating method based on network attached storage, processor and storage device
    CN112000971A|2020-11-27|File permission recording method, system and related device
    CN109491962B|2022-02-22|File directory tree management method and related device
    CN108964990A|2018-12-07|Implementor name display methods and device in a kind of multiple equipment management system
    WO2012083613A1|2012-06-28|Multiversion upgrade method and apparatus for user self-defined performance indicator
    CN106155736B|2019-04-12|Software installation starts type detection method, apparatus and user terminal
    WO2017107679A1|2017-06-29|Historical information display method and apparatus
    US8135664B2|2012-03-13|Change management using collective data
    US7783662B2|2010-08-24|Federated information management
    KR101546581B1|2015-08-21|Application download method and user termial for processing the method
    CN109450874B|2021-09-21|User account monitoring method and device
    同族专利:
    公开号 | 公开日
    BR112012017294A2|2016-03-22|
    WO2011085631A1|2011-07-21|
    CN101794222A|2010-08-04|
    SG182486A1|2012-08-30|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US7447799B2|2002-04-24|2008-11-04|Good Technology, Inc.|System and method for automatically updating a wireless device|
    CN1690961A|2004-04-30|2005-11-02|鸿富锦精密工业（深圳）有限公司|Client program automatic updating system and method|
    CN101026464A|2006-02-25|2007-08-29|宇龙计算机通信科技有限公司|Wireless terminal wireless upgrding method and wireless upgrading system|
    CN100557567C|2007-12-21|2009-11-04|深圳市迅雷网络技术有限公司|A kind of method, system and device of prompting software version update|
    CN101794222A|2010-01-13|2010-08-04|腾讯科技（深圳）有限公司|Software version collecting method, management system and software upgrading detection method and system|CN101794222A|2010-01-13|2010-08-04|腾讯科技（深圳）有限公司|Software version collecting method, management system and software upgrading detection method and system|
    CN102486725A|2010-12-02|2012-06-06|上海可鲁系统软件有限公司|Distributed platform and method for managing life cycle of functional module in platform|
    CN102495733A|2011-12-08|2012-06-13|方正国际软件有限公司|Methods for detecting compatibility of application program and relevant database script and performing upgrading maintenance on application program and relevant database script|
    CN102622252B|2012-03-08|2015-07-15|神州数码国信信息技术（苏州）有限公司|Automatic upgrading method for meat traceability system|
    CN104202401B|2012-10-16|2019-03-22|北京奇虎科技有限公司|Application upgrade system|
    CN102882978A|2012-10-16|2013-01-16|北京奇虎科技有限公司|Server and application updating method|
    CN103049283A|2012-11-28|2013-04-17|镇江为天下信息服务有限公司|Automatic updating method for setting version numbers for every software file|
    CN103605546B|2013-11-22|2017-02-01|中国广核集团有限公司|Software version detecting method and device|
    CN104780189A|2014-01-13|2015-07-15|中兴通讯股份有限公司|Software upgrading method and software upgrading device|
    CN103986969B|2014-04-28|2017-12-05|小米科技有限责任公司|application management method, device and system|
    CN104090807A|2014-07-18|2014-10-08|广州金山网络科技有限公司|Application software new version information obtaining method and device|
    CN104239098A|2014-09-09|2014-12-24|北京金山安全软件有限公司|Automatic upgrading method and device for software and mobile terminal|
    CN104298757B|2014-10-22|2018-01-12|福建星网视易信息系统有限公司|A kind of method and system of compatible multi version mobile client and database|
    CN105653298A|2014-11-12|2016-06-08|Tcl集团股份有限公司|Application program update method and terminal|
    US9792154B2|2015-04-17|2017-10-17|Microsoft Technology Licensing, Llc|Data processing system having a hardware acceleration plane and a software plane|
    US10198294B2|2015-04-17|2019-02-05|Microsoft Licensing Technology, LLC|Handling tenant requests in a system that uses hardware acceleration components|
    US10270709B2|2015-06-26|2019-04-23|Microsoft Technology Licensing, Llc|Allocating acceleration component functionality for supporting services|
    US10216555B2|2015-06-26|2019-02-26|Microsoft Technology Licensing, Llc|Partially reconfiguring acceleration components|
    CN105700917A|2016-01-04|2016-06-22|浪潮通用软件有限公司|Method and apparatus for synchronizing DLL and database|
    CN106897053B|2016-07-08|2020-06-26|阿里巴巴集团控股有限公司|Code publishing method and device|
    CN108459950A|2017-02-20|2018-08-28|宏碁股份有限公司|verification method and verification device|
    CN108733391A|2017-04-18|2018-11-02|北京京东尚科信息技术有限公司|A kind of method and apparatus of dynamic resource allocation|
    CN109192262B|2018-09-17|2020-11-20|北京惠每云科技有限公司|Data transmission method and device|
    CN109360029B|2018-10-30|2021-09-10|深圳市亿晟科技有限公司|Self-management method of remote terminal advertising machine|
    法律状态:
    2019-01-08| B06F| Objections, documents and/or translations needed after an examination request according art. 34 industrial property law|
    2019-08-06| B06U| Preliminary requirement: requests with searches performed by other patent offices: suspension of the patent application procedure|
    2020-05-26| B06A| Notification to applicant to reply to the report for non-patentability or inadequacy of the application according art. 36 industrial patent law|
    2020-09-08| B09A| Decision: intention to grant|
    2020-12-22| B16A| Patent or certificate of addition of invention granted|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 30/12/2010, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    CN201010042816A|CN101794222A|2010-01-13|2010-01-13|Software version collecting method, management system and software upgrading detection method and system|
    CN201010042816.2|2010-01-13|
    PCT/CN2010/080514|WO2011085631A1|2010-01-13|2010-12-30|Method, system and server for collecting version of software|
    [返回顶部]