CN106790432A - Method and device for updating software - Google Patents

Abstract

The invention discloses a software updating method, which comprises the following steps: acquiring updated software data in the SVN server; comparing the updated software data with local software data to screen files which are different from the local software data; dividing and packaging the files with differences; sending the divided and packaged package files to a cache end, and recording file information of files with differences; updating the software version number according to the issuing instruction, wherein the software version number corresponds to the package file; and after the software version number is updated, sending file information and package files according to the request of the end to be updated so as to realize the hot update of the software of the end to be updated. The invention also discloses a software updating device and a system. By the mode, the invention can submit the updating data by adopting the uniform updating submitting interface, and can simply, conveniently and controllably update the software.

Description

Method and device for updating software

technical field

The invention relates to the technical field of computers, in particular to a software updating method and device.

Background technique

In the field of software research and development, version hot update is an indispensable function. Version hot update means that the software can be updated online without re-downloading the client, and only need to download the data package to complete the version update. For game software, its version update usually includes game data, art resources and function codes. Game data refers to various types of definition data that need to be used in the game, such as item information, character attributes, etc. Art resources refer to maps, Character models and various UI screens, function codes refer to the implementation codes of various functions in the game.

For the game software version hot update function, its design, operation, and management are difficult. The specific reasons are as follows: the version hot update frequency is high. In order to keep players fresh, content updates will be carried out according to a certain period during the game operation process. , constantly launching new game content, in addition, data optimization and adjustment will be carried out according to the feedback during the game process; the version hot update is mainly used for the generation environment, and each update is directly facing the player, so it is necessary to ensure the hot update process Accurate, especially to ensure the controllability of the process, to avoid problems caused by human errors in the hot update process; the version hot update involves a lot of people, hot update involves multiple parts, such as game data, art resources, function codes , in the development process, each part belongs to different personnel for development management.

How to use a unified update submission interface to submit update data and perform software updates in a simple and controllable manner is one of the problems to be solved urgently in hot update of game software versions.

Contents of the invention

The technical problem mainly solved by the present invention is to provide a software update method and device, which can submit update data through a unified update submission interface, and perform software hot update in a simple and controllable manner.

In order to solve the above-mentioned technical problems, the present invention provides a method for updating software, comprising the steps of: obtaining updated software data in the SVN server; comparing the updated software data with local software data, to screen for the presence of local software data. Different files; divide and package the files with differences; send the divided and packaged package files to the cache end, and record the file information of the files with differences; update the software version number according to the release instruction, and the software version number corresponds to the package file ; When the software version number is updated, send the file information and package file according to the request of the terminal to be updated, so as to realize the hot update of the software of the terminal to be updated.

Wherein, the updated software data adopts the submission interface of the SVN server for data submission.

Wherein, the cache end is a content delivery network.

Wherein, the terminal to be updated is a client or a server.

Wherein, when the software version number is updated, send file information and package files according to the request of the terminal to be updated, so as to realize the hot update of the software at the terminal to be updated. The steps include: after the software version number is updated, sending a software version number update message to the server ; Return the software version number, file information and package file according to the request from the server to realize the hot update of the server software.

In order to solve the above technical problems, the present invention provides a software update device, including: an acquisition module, used to acquire updated software data in the SVN server; a comparison module, used to compare the updated software data with local software data Yes, to filter files that are different from the local software data; the packaging module is used to divide and package the files with differences; the sending record module is used to send the divided and packaged package files to the cache end, and record the differences The file information of the file; the update module is used to update the software version number according to the release instruction, and the software version number corresponds to the package file; the sending module is used to send the file information and the package file according to the request of the terminal to be updated after the software version number is updated, In order to realize the hot update of the terminal software to be updated.

Wherein, the updated software data adopts the submission interface of the SVN server for data submission.

Wherein, the terminal to be updated is a client or a server.

Wherein, the sending module includes: a sending unit, used to send a software version number update message to the server after the software version number is updated; a return unit, used to return the software version number, file information and package files according to the request of the server side, to realize Hot update of server-side software.

In order to solve the above-mentioned technical problems, the present invention provides a software update system, including the above-mentioned software update device and an SVN server for storing updated software data.

The beneficial effects of the present invention are: different from the situation of the prior art, the software update method of the present invention is specifically: first obtain the updated software data in the SVN server, wherein, the updated software data adopts the submission interface of the SVN server for data processing. Submit; then compare the updated software data with the local software data to screen files that are different from the local software data, divide and package the files with differences, send the divided and packaged package files to the cache end, and Record the file information of the files with differences; finally, update the software version number according to the release instruction, where the software version number corresponds to the package file. When the software version number is updated, send the file information and package file according to the request of the terminal to be updated, to realize the Hot update of updater software. Through the above method, the software update of the present invention is simple and controllable, meets the requirement of high hot update frequency of the game software version, and reduces human operations in the hot update process; the submission interface of the SVN server is used to submit the updated software data, due to the submission The unified interface can ensure the reliability of updated software data.

Description of drawings

Fig. 1 is a schematic flow chart of an embodiment of the software update method of the present invention;

Fig. 2 is a schematic structural diagram of an embodiment of a software updating device of the present invention.

detailed description

The present invention will be described in detail below in conjunction with the accompanying drawings and embodiments.

Please refer to FIG. 1. FIG. 1 is a schematic flow chart of an embodiment of the software update method of the present invention, as shown in FIG. 1, including the following steps:

S11, acquiring updated software data in the SVN server.

The method of this embodiment is realized by the game software version hot update platform, and is a game software version hot update method based on SVN (Subversion) management. In this embodiment, the updated software data is submitted through the submission interface of the SVN server.

For software version hot updates, the primary requirement is a low error rate, because errors in the production environment will lead to major operational accidents. Utilizing SVN as the management of updated data can avoid errors in updating data. The main reasons are: different data providers are very familiar with the use of SVN, reducing human errors caused by using unfamiliar tools; using the SVN synchronization mechanism can Prevent information overwriting errors caused by different data providers modifying the same data; use the SVN version control feature, you can easily trace back the historical version, and you can easily search for data update errors; SVN is a mature version management , the stability is very high, which can increase the stability of version hot update.

For the updated software data, the submission process is as follows: the data publisher connects to the SVN server through the local SVN client, first updates the latest database to the local to ensure the synchronization of the local and SVN server data, and then updates the required data Copy the data files to the local data storage directory, and store them according to the preset directory. The directory can be set according to the game, and then use the comparison function of the SVN client to check the data to confirm the correctness of the data update. Finally, after confirming that the updated data is correct, submit it to the SVN server, and the SVN server will store the updated software data. During the submission process, if some materials cannot be submitted, it means that there is a data file conflict, and the materials need to be updated and merged by themselves.

S12. Comparing the updated software data with the local software data, so as to screen files that are different from the local software data.

S13, dividing and packaging the files with differences.

S14. Send the divided and packaged package files to the cache end, and record the file information of the files with differences.

The version release of the game software is managed by the manager. When the update data is submitted, the manager issues a version generation instruction. The version generated at this time is a releasable version, but it will not be released immediately. The process of version generation is as follows: when the manager issues a version generation instruction, the game software version hot update platform obtains the updated software data in the SVN server; compares the updated software data with the local software data to screen For files with differences in software data, all files with changes are screened out, and the screened files are used to generate materials for subsequent version packages; after files with differences are screened out, they are automatically divided and packaged, and specifically packaged into compressed files for easy download file; transfer the packaged package file to the cache end for download; after the package file is transmitted to the cache end, record the file information of the files with differences.

In this embodiment, the cache end is a content delivery network (Content Delivery Network, CDN).

S15. Update the software version number according to the release instruction, where the software version number corresponds to the package file.

After the administrator receives the message that the version generation is completed, it will be received by email, and the version can be released according to the needs of the game. The administrator logs in to the game software version hot update platform, can view a list of all version information, select the version to be released, and issue a release instruction, and the platform will update the software version number according to the release instruction. For publishing, only the latest version can be published, and the old version is invalid.

The manager can operate on the version information list, specifically, can perform operations such as version deletion, information modification, and release.

S16. After the software version number is updated, send the file information and the package file according to the request of the terminal to be updated, so as to realize the hot update of the software of the terminal to be updated.

When the software version number is updated, it indicates that the new version is in the state to be updated. In this embodiment, the terminal to be updated is the client or the server.

For the game client, it belongs to the active update mode. When the player logs in the game through the game client, the updated software version number is obtained. If the obtained software version number is higher than the version recorded by the client, the file information and package file for hot update of the software.

For the game server side, it belongs to the passive update mode. When the software version number is updated, the game software version hot update platform sends a software version number update message to the server side. After receiving the message, the server side requests to obtain the software version number, file information and package information. file for hot update of the software.

As mentioned above, the software update method of this embodiment is simple and controllable, meets the high requirement of hot update frequency of the game software version, and reduces human operations in the hot update process; utilizes the submission interface of the SVN server to submit the updated software data, Due to the uniform submission interface, the reliability of updated software data can be ensured.

Please refer to Fig. 2, Fig. 2 is a structural representation of an embodiment of the software updating device of the present invention, as shown in Fig. Send module 26.

The functions of the above modules are as follows:

Obtaining module 21 is used for obtaining the updated software data in the SVN server; Comparison module 22 is used for comparing the updated software data with the local software data, so as to screen files that differ from the local software data; Packing module 23 uses The files with differences are divided and packed; the sending recording module 24 is used to send the package files after the splits and packages to the cache end, and records the file information of the files with differences; the update module 25 is used to update the software version number according to the release instruction , the software version number corresponds to the package file; the sending module 26 is used to send the file information and the package file according to the request of the terminal to be updated after the software version number is updated, so as to realize the hot update of the terminal software to be updated.

In this embodiment, the updated software data is submitted through the submission interface of the SVN server. For the updated software data, the submission process is as follows: the data publisher connects to the SVN server through the local SVN client, first updates the latest database to the local to ensure the synchronization of the local and SVN server data, and then updates the required data Copy the data files to the local data storage directory, and store them according to the preset directory. The directory can be set according to the game, and then use the comparison function of the SVN client to check the data to confirm the correctness of the data update. Finally, after confirming that the updated data is correct, submit it to the SVN server, and the SVN server will store the updated software data. During the submission process, if some materials cannot be submitted, it means that there is a data file conflict, and the materials need to be updated and merged by themselves.

In this embodiment, the version release of the game software is managed by the manager. When the update data is submitted, the manager issues a version generation instruction. After the manager sends the version generation instruction, the acquisition module 21, the comparison module 22, and the packaging module 23. The sending and recording module 24 works sequentially to complete the generation of the software version. After the software version is generated, the manager issues a release instruction, and the update module 25 updates the software version number according to the release instruction. When the software version number is updated, it indicates that the new version has entered the state to be updated. In this embodiment, the terminal to be updated is a client or a server, and the sending module 26 sends file information and package files to the terminal to be updated, so as to realize hot update of the software of the terminal to be updated.

For the game client, it belongs to the active update mode. When the player logs in the game through the game client, the updated software version number is obtained. If the obtained software version number is higher than the version recorded by the client, the file information and package file for hot update of the software.

For the game server end, it belongs to the passive update mode, and its update process is: the sending module 26 includes a sending unit (not shown) and a return unit (not shown); the sending unit is used to send the software version number after the software version number is updated The update message is sent to the server side; the return unit is used to return the software version number, file information and package file according to the request of the server side, so as to realize the hot update of the server side software.

In this embodiment, the cache end is a content delivery network.

The software update system of the present invention includes the device of the embodiment shown in FIG. 2 and an SVN server for storing updated software data.

The software update system of the present invention will be described in detail below through a specific embodiment.

The software update system includes the SVN system, version generation system, version management system, and version distribution system, wherein the SVN system corresponds to the SVN server, and the version generation system, version management system, and version distribution system correspond to the game software version hot update platform or as shown in Figure 2 Example device.

The SVN system is used for data storage and management. It is the entrance for data upload and submission, and also the entrance for the version generation system.

The version generation system consists of a comparison subsystem, a packaging subsystem, and a version recording subsystem. The function of the comparison subsystem is to complete the comparison of file differences between two different versions, and filter out the difference files, which are elements used for updating. The packaging subsystem is to divide and package the selected differential files. The function of dividing and packaging is to provide better download services, because too small update packages will bring a lot of connection loss to the update, and too large update packages It is prone to download failure. The version record subsystem prepares for the release of subsequent versions and provides update information to the terminal to be updated. The version generated by the version generation system is pre-release, so that the software update system has enough time to complete the release deployment. The version generation system uses an automatic comparison mechanism to replace the manual screening of update files, which greatly reduces the possible errors caused by manual operations.

The version management system is used by managers to manage released and unreleased versions, and managers can also perform other operations, such as small package management.

The version distribution system is used to face the terminal to be updated, including a version acquisition interface and a cache terminal. The version acquisition interface provides software version number and file information acquisition functions, and the cache terminal is a content distribution network. The version acquisition interface can be connected to the update information acquisition interface of different heterogeneous devices in a unified manner, and can be connected to any development language or system.

For the case where the terminal to be updated is a game server, the version distribution system also includes an update notification interface, which is used for the server to obtain software version update information.

The software update system of the present invention is highly efficient and orderly, solves the problems of complex version hot update process, low efficiency, and error-prone in the current game research and development field, and makes version hot update simple, efficient and highly fault-tolerant.

The above is only an embodiment of the present invention, and does not limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the description of the present invention and the contents of the accompanying drawings, or directly or indirectly used in other related technologies fields, are all included in the scope of patent protection of the present invention in the same way.

Claims (10)

1. A method for updating software, characterized in that, comprising the following steps: Obtain the updated software data in the SVN server; Comparing the updated software data with the local software data to screen files that differ from the local software data; dividing and packaging the files with differences; Send the divided and packaged package files to the cache end, and record the file information of the files with differences; Updating the software version number according to the release instruction, the software version number corresponding to the package file; After the software version number is updated, the file information and the package file are sent according to the request of the terminal to be updated, so as to realize the hot update of the software of the terminal to be updated. 2. The software update method according to claim 1, characterized in that, the updated software data is submitted by using the submission interface of the SVN server. 3. The software update method according to claim 1, wherein the cache end is a content distribution network. 4. The software update method according to claim 1, wherein the terminal to be updated is a client or a server. 5. The software update method according to claim 4, characterized in that, after the software version number is updated, the file information and the package file are sent according to the request of the terminal to be updated, so as to realize the hot update of the software at the terminal to be updated. The updated steps include: After the software version number is updated, send a software version number update message to the server; Returning the software version number, file information and package file according to the request of the server end, so as to realize the hot update of the server end software. 6. A software update device, characterized in that it comprises: The acquisition module is used to acquire updated software data in the SVN server; A comparison module, configured to compare the updated software data with local software data, so as to screen files that differ from the local software data; A packaging module, configured to divide and package the files with differences; A sending recording module, configured to send the divided and packaged package files to the cache end, and record the file information of the files with differences; An update module, configured to update the software version number according to the release instruction, the software version number corresponding to the package file; The sending module is configured to send the file information and package file according to the request of the terminal to be updated after the software version number is updated, so as to realize the hot update of the software of the terminal to be updated. 7 . The software update device according to claim 6 , wherein the updated software data is submitted through a submission interface of the SVN server. 8 . 8. The software update method according to claim 6, wherein the terminal to be updated is a client or a server. 9. The software update device according to claim 8, wherein the sending module comprises: A sending unit, configured to send a software version number update message to the server after the software version number is updated; The returning unit is used to return the software version number, file information and package file according to the request of the server, so as to realize the hot update of the server software. 10. A software update system, characterized in that it comprises the device according to claims 6-9 and an SVN server for storing updated software data.