CN113568645B - Software updating method, device, electronic equipment and storage medium - Google Patents

Software updating method, device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113568645B
CN113568645B CN202110918030.0A CN202110918030A CN113568645B CN 113568645 B CN113568645 B CN 113568645B CN 202110918030 A CN202110918030 A CN 202110918030A CN 113568645 B CN113568645 B CN 113568645B
Authority
CN
China
Prior art keywords
file
compressed
files
modification
update
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110918030.0A
Other languages
Chinese (zh)
Other versions
CN113568645A (en
Inventor
吴家宏
冯帆
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Netease Hangzhou Network Co Ltd
Original Assignee
Netease Hangzhou Network Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Netease Hangzhou Network Co Ltd filed Critical Netease Hangzhou Network Co Ltd
Priority to CN202110918030.0A priority Critical patent/CN113568645B/en
Publication of CN113568645A publication Critical patent/CN113568645A/en
Application granted granted Critical
Publication of CN113568645B publication Critical patent/CN113568645B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/174—Redundancy elimination performed by the file system
    • G06F16/1744—Redundancy elimination performed by the file system using compression, e.g. sparse files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The invention discloses a software updating method, a device, electronic equipment and a storage medium; the invention can acquire the modification records of a plurality of files of the target software; determining the update frequency of the file according to the modification record of the file, wherein the update frequency characterizes the probability of the file being modified; compressing the file according to the update frequency of the file to obtain a compressed package of the target software; acquiring a plurality of update files corresponding to target software; the compressed package of the target software is updated based on the update file so that the target software is updated with the updated compressed package. According to the method, the probability that the file is possibly modified in the future is determined according to the modification record of the file of the target software; then compressing the files of the target software according to the probability that the files are possibly modified, and compressing the files with higher updating frequency together; thus, when the target software is updated, fewer compressed files can be updated. Therefore, the scheme can improve the efficiency of software updating.

Description

Software updating method, device, electronic equipment and storage medium
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a software updating method, a device, an electronic apparatus, and a storage medium.
Background
In order to enhance the functions of the software and improve the safety and stability of the software, the software is frequently updated. The software update is mainly to update files in an installation package of the software, such as modifying, deleting or adding files. Therefore, when the client updates the software, the client needs to download the patch package of the software through the internet, and the downloading process needs to pay corresponding downloading time and flow.
Currently, software updates are less efficient.
Disclosure of Invention
The invention provides a software updating method, a device, electronic equipment and a storage medium, which can improve the software updating efficiency.
The invention provides a software updating method, which comprises the following steps:
acquiring modification records of a plurality of files of the target software;
determining the update frequency of the file according to the modification record of the file, wherein the update frequency characterizes the probability of the file being modified;
compressing the file according to the update frequency of the file to obtain a compressed package of the target software;
acquiring a plurality of update files corresponding to target software;
the compressed package of the target software is updated based on the update file so that the target software is updated with the updated compressed package.
The invention also provides a software updating device, which comprises:
The first acquisition unit is used for acquiring modification records of a plurality of files of the target software;
the determining unit is used for determining the update frequency of the file according to the modification record of the file, wherein the update frequency represents the probability of the file being modified;
the compression unit is used for compressing the file according to the update frequency of the file to obtain a compression packet of the target software;
the second acquisition unit is used for acquiring a plurality of update files corresponding to the target software;
and the updating unit is used for updating the compression package of the target software based on the updating file so as to update the target software by adopting the updated compression package.
In some embodiments, the determining unit is specifically configured to:
determining the type of the file;
and determining the update frequency of the file according to the modification record of the file and the type of the file.
In some embodiments, the types of the file include an art resource type, a script type, the art resource type includes an art resource index subtype, an art resource subtype, and the determining unit is specifically configured to:
when the type of the file is an art resource index sub-type, determining the update frequency of the file as a first level;
when the type of the file is script type or art resource subtype, determining the update frequency of the file according to the modification record of the file.
In some embodiments, the file types further include other file types, and the determining unit is specifically configured to:
determining the directory of the file;
determining the directory grade corresponding to the file according to the directory in which the file is located;
determining the update frequency of the file according to the modification record of the file;
and weighting the update frequency of the file based on the directory grade corresponding to the file to obtain the weighted update frequency of the file.
In some embodiments, the modification record of the file includes a modification time and a modification number, and the determining unit is specifically configured to:
determining a standard time difference and a time aggregation degree according to the modification time, wherein the standard time difference represents a time difference relation between the modification time of the file and the current time, and the time aggregation degree represents the aggregation degree of the modification time of the file;
when the number of modification times is not less than the preset number of modification times and the standard time difference is not greater than the preset time difference threshold, determining the update frequency of the file as a first level;
when the modification times are not less than the preset modification times and the standard time difference is greater than the preset time difference threshold, determining the update frequency of the file as a second level;
when the time aggregation degree is within a preset time aggregation degree range, determining the update frequency of the file as a third level;
And when the number of modification times is smaller than the preset number of modification times, determining the update frequency of the file according to the standard time difference and the preset time difference threshold value.
In some embodiments, the compression unit is specifically configured to:
sorting the files according to the update frequency of the files to obtain sorted files;
and compressing the sequenced files to obtain a compressed package of the target software.
In some embodiments, the compression package of the target software includes a plurality of compression files, and the compression unit is specifically configured to:
determining a compressed file size threshold according to the network environment;
the ordered files are compressed into a plurality of compressed files based on a compressed file size threshold.
In some embodiments, the updating unit is specifically configured to:
when a compressed file corresponding to the updated file exists in the compressed package of the target software, updating the compressed file corresponding to the updated file based on the updated file to obtain an updated compressed file;
when the compressed file corresponding to the updated file does not exist in the compressed package of the target software, generating a new compressed file according to the updated file;
uploading the updated compressed file and the new compressed file so that the client terminal updates the target software based on the updated compressed file and the new compressed file.
In some embodiments, the updating unit is specifically further configured to:
acquiring file information of an updated file;
updating the compressed file corresponding to the updated file based on the updated file, and further comprising:
acquiring file information of a compressed file corresponding to the updated file;
generating an update guide file based on file information of the compressed file corresponding to the update file and file information of the update file;
and uploading the updated guide file so that the client downloads the updated compressed file and the new compressed file according to the updated guide file.
The invention also provides an electronic device, which comprises a memory and a processor, wherein the memory stores a plurality of instructions; the processor loads instructions from the memory to perform steps in any of the software updating methods provided by the present invention.
The present invention also provides a computer readable storage medium storing a plurality of instructions adapted to be loaded by a processor to perform the steps of any of the software updating methods provided by the present invention.
The method and the device can acquire the modification record of the file of the target software, and determine the update frequency of the file according to the modification record, thereby obtaining the probability that the file is possibly modified in the future; then compressing the files of the target software according to the update frequency of the files, so that the files with higher update frequency can be compressed together; therefore, when the file is modified, only a few compressed files can be updated, so that the time for decompressing the file and recompressing the file can be reduced; and when the target software is updated, fewer compressed files can be downloaded, so that the downloading speed can be improved. Therefore, the scheme can improve the efficiency of software updating.
Drawings
In order to more clearly illustrate the technical solutions of the present invention, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1a is a schematic diagram of a software update method provided by the present invention;
FIG. 1b is a flowchart of a software update method provided by the present invention;
FIG. 2a is a schematic flow chart of the software update method of the present invention applied in a game software scenario;
FIG. 2b is a schematic illustration of a full patch provided by the present invention;
FIG. 2c is a schematic illustration of a delta patch provided by the present invention;
FIG. 3 is a schematic diagram of a software updating apparatus according to the present invention;
fig. 4 is a schematic structural diagram of an electronic device provided by the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made more apparent and fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to fall within the scope of the invention.
The invention provides a software updating method, a software updating device, electronic equipment and a storage medium.
The software updating device can be integrated in an electronic device, and the electronic device can be a terminal, a server and other devices. The terminal can be a mobile phone, a tablet computer, an intelligent Bluetooth device, a notebook computer, a personal computer (Personal Computer, PC) or the like; the server may be a single server or a server cluster composed of a plurality of servers. In some embodiments, the server may also be implemented in the form of a terminal.
In some embodiments, the software updating apparatus may also be integrated in a plurality of electronic devices, for example, the software updating apparatus may be integrated in a plurality of servers and terminal devices, and the software updating method of the present invention is implemented by the plurality of servers and terminal devices.
For example, referring to fig. 1a, fig. 1a is a schematic view of a software update method according to an embodiment of the present invention. In the context of the software update method, a first server, a second server, and a client may be included. Wherein the first server may be a server corresponding to a version control system (Version Control System, VCS), e.g., the version control system may be SVN (Subversion), git, etc., which may record content changes of a plurality of files of the target software. The second server may be a device corresponding to a content delivery network (Content Delivery Network, CDN). The client may be a terminal device in which the target software is installed, or a terminal device in which the target software is ready to be installed.
The method comprises the steps that a first server obtains modification records of a plurality of files of target software; determining the update frequency of the file according to the modification record of the file, wherein the update frequency characterizes the probability of the file being modified; compressing the file according to the update frequency of the file to obtain a compressed package of the target software; acquiring a plurality of update files corresponding to target software; and updating the compression package of the target software based on the update file so that the client adopts the updated compression package to update the target software.
In this embodiment, the first server may obtain a modification record of the file of the target software, and determine the update frequency of the file according to the modification record, so as to obtain the probability that the file may be modified in the future; then compressing the files of the target software according to the update frequency of the files, so that the files with higher update frequency can be compressed together; when the file is modified, the first server can update only less compressed files in the compression package of the target software, so that the time for decompressing the file and recompressing the file can be reduced; and the client can download less compressed files when updating the target software, so that the downloading speed can be improved. Therefore, the scheme can improve the efficiency of software updating.
The following will describe in detail. The numbers of the following examples are not intended to limit the preferred order of the examples.
In this embodiment, a software updating method is provided, as shown in fig. 1b, and the specific flow of the software updating method may be as follows:
110. a modification record of a plurality of files of the target software is obtained.
The target software may be a set of computer data and instructions organized in a specific order, and may be system software or application software, where the application software may include game software, instant messaging software, and the like.
The plurality of files of the target software may include all files required for installation and operation of the target software. For example, taking game software as an example, a plurality of files of the game software may be divided by file types, which may include, but are not limited to, art resource types, script types, and other file types, including art resource index sub-types, art resource sub-types; the plurality of files may include, but are not limited to, a file corresponding to a script type, a file corresponding to an art asset type, and a file corresponding to other types. The files of the art resource type may include files of an art resource sub-type (such as a game virtual character resource file, a map resource file, a user interface map file, etc.), files of an art resource index sub-type (such as a meta file resource of an art resource), etc.; other types of files may be files under a target directory that may include, but are not limited to, a user interface directory (UI), a game avatar directory (Char), a pre-cast directory (Prefab), a virtual scene directory (Worlds), a routing grid directory (navigator), an audio directory (SoundBanks), a game configuration directory (GameConfig), a font directory (nts), a still picture directory (UIImage). It will be appreciated that the file type of the file may also be associated with a catalog, such as a Script type may correspond to a Script catalog, and an art asset type may correspond to a repository (repo) catalog that includes subdirectories of virtual models, animations, special effects, skins, bones, materials, maps, etc.
The modification record may be information when the file content changes, and may include, for example, but not limited to, modification time, and number of modifications; the modification time may be a standard time when the file is modified. In some embodiments, the modification time may be counted to obtain the number of modifications.
Each time a plurality of files of the target software are modified, the version control system records a modification record of the files. In some embodiments, the version control system may obtain modification records of a plurality of files of the target software within a preset period of time; the preset time period may be set in a user-defined manner according to an actual application situation, for example, if the setting is performed according to the frequency of the software update, the higher the frequency of the software update is, the preset time period may be correspondingly shortened, for example, may be half a year, two months, etc. In some embodiments, the version control system may obtain all of the modified records for the plurality of files of the target software.
120. And determining the update frequency of the file according to the modification record of the file, wherein the update frequency characterizes the probability of the file being modified.
Wherein the update frequency may be classified into different levels. In some embodiments, the update frequency may include a first level, a second level, a third level, a fourth level, and a fifth level, where from the first level to the fifth level may indicate that the probability that the file is modified decreases in order, i.e., the update frequency decreases in order. It can be understood that each level can be divided into a plurality of small levels, N can be used to represent the update frequency, and the value of N can be any integer, for example, can be 5 or 6; for example, the first level may be expressed as N levels, the third level may be expressed as N/2+1 to N-1 levels, the second level may be expressed as N/2 levels, the fourth level may be expressed as 2 to N/2+1 levels, and the fifth level may be expressed as 1 level; a larger value indicates a higher probability that the file is modified, i.e., a higher update frequency. In some embodiments, the division of update frequency may be determined according to the type of software, e.g., the update frequency of game software may be divided into more levels, and instant messaging software may be divided into relatively fewer levels.
For software updating, part of files in a general compressed package are updated frequently, while some files are not updated basically, so that the update frequency of the files can be determined according to the modification records of the files, thereby obtaining the probability that the files are possibly modified.
In some embodiments, the type of file may be determined, and then the update frequency of the file may be determined based on the file's modification record and the file's type.
Wherein determining the update frequency of the file according to the modification record of the file and the type of the file may include, but is not limited to: when the type of the file is an art resource index subtype, the update frequency of the file is determined to be a first level. When the type of the file is script type or art resource subtype, determining the update frequency of the file according to the modification record of the file. For other types of files, the directory in which the file is located can be determined; determining a directory grade corresponding to the file according to the directory in which the file is located, wherein the directory grade can be divided into M grades; determining the update frequency of other types of files according to the modification records of the files; the update frequency of the files of other types is weighted based on the directory level corresponding to the file, so that the weighted update frequency of the file is obtained, for example, the directory level and the update frequency of the file can be overlapped.
The specific embodiment of determining the update frequency of the file according to the modification record of the file is not limited. In some embodiments, the standard time difference and the degree of time aggregation may be determined from the modified time. The time difference relation between the modification time and the current time of the standard time difference representation file can be calculated by adopting the following formula:
where n represents the number of modifications, t represents the current time, which may be the time to obtain the modification record.
The time aggregation level represents the aggregation level of the modification time of the file, and the time aggregation level can be calculated by adopting the following formula:
wherein->
Wherein x is i Represents the modification time when the i-th file is modified, and μ represents the average value of the file modification times.
And when the number of modification times is not less than the preset number of modification times and the standard time difference is not greater than the preset time difference threshold, determining the update frequency of the file as a first level.
And when the number of modification times is not smaller than the preset number of modification times and the standard time difference is larger than the preset time difference threshold, determining the update frequency of the file as a second level.
And when the time aggregation degree is within the range of the preset time aggregation degree, determining the update frequency of the file as a third level.
When the modification times are smaller than the preset modification times, determining the update frequency of the file according to the standard time difference and the preset time difference threshold value; setting a corresponding time difference threshold range according to a preset time difference threshold; when the standard time difference of the file is out of the time difference threshold range and the standard time difference is larger than the maximum value of the time difference threshold range, determining the update frequency of the file as a fourth level; when the standard time difference of the file is within the time difference threshold range, determining the update frequency of the file as a second level; and when the standard time difference of the file is out of the time difference threshold range and the standard time difference is smaller than the minimum value of the time difference threshold range, determining the update frequency of the file as a third level. It can be known that the update frequency of the file can be determined by combining experience and statistical methods through the modification record of the file, so that the probability that the file is possibly modified in the future is obtained, and the mode of software update is met.
For example, taking game software as an example, for a script type file, the update frequency of the file is determined according to the modification record of the file.
For art asset type files: 1) And determining the update frequency of the file according to the modification record of the file when the common virtual game role and the mapping resource file are used. 2) The resource is a metafile (file of the art resource index type) of the resource, and the update frequency of the resource is determined as N-level. 3) The files under the local directory are mainly UI mapping files after mapping, and the UI mapping files are files which are updated relatively frequently, so that the changed resources are extremely easy to cause the redistribution of mapping, and the updating frequency of the files can be independently determined according to the modification records.
For files under the target directory (other types): 1) Files under UI, char and Prefab directory are frequently updated files, and directory level is determined to be M level. 2) Worlds, navigate and SoundBanks directory files are the next most frequently updated files, and directory ranks are determined to be M-1 level. 3) The frequency of updating the files under other directories such as GameConfig, fonts, UIImage is low, and the directory rank is determined to be M-2. And determining the update frequency of the files under different directory grades according to the modification records of the files, and superposing the directory grades on the update frequency of the files to obtain the final update frequency of the files.
In some embodiments, for the newly added file at the time of the last software update, when the newly added file is a hot update file or __ init __. Py file, etc., the update frequency of the newly added file is determined to be the fifth rank. And determining the update frequency as a second level according to other newly added files.
In some embodiments, the update frequency of the file may be determined based solely on the file's modification record.
In some embodiments, the update frequency of the files under each directory may be determined independently according to the directory corresponding to the target software, or may be determined according to the modification record of the files.
130. And compressing the file according to the update frequency of the file to obtain a compressed package of the target software.
The compression package of the target software can comprise a plurality of compression files, or can be a large compression file formed by secondarily compressing the plurality of compression files; the compression format of the compressed file is not limited, and may be RAR, ZIP, or the like. The compressed package of the target software may also be referred to as a full patch or full patch of the target software; which may also be referred to as an installation package for the target software in certain situations.
The compressing of the file according to the update frequency of the file may include, but is not limited to, the steps of:
s1: sorting the files according to the update frequency of the files to obtain sorted files; the files may be sorted according to the update frequency from high to low, or sorted according to the update frequency from low to high.
S2: and compressing the sequenced files to obtain a compressed package of the target software. In some embodiments, the compressed file size threshold may be determined based on the network environment; for example, windows and other relatively stable platforms, the compressed file size threshold may be 10M; other network-unstable platforms, compressed file size thresholds may be 4M, etc. The compressed file size threshold is determined according to different network environments, and the flexibility is high.
And compressing the ordered files into a plurality of compressed files based on the compressed file size threshold, thereby obtaining a compressed package of the target software. In some embodiments, the compressed files may be numbered, where the higher the update frequency of the file corresponding to the compressed file, the greater the number; and the number of each compressed file may be unique.
In some embodiments, the files under each directory may be independently sorted according to the update frequency of the files by taking the directory corresponding to the file as a unit. And then compressing the files sequenced under each catalogue to obtain a compressed package of the target software. In some embodiments, when the ordered files corresponding to each file type are compressed, if the files remaining under each directory are not sufficiently compressed into compressed files with a compressed file size threshold, the files under multiple directories may be compressed into one compressed file.
In some embodiments, the files corresponding to each file type may be independently sorted according to the update frequency of the files by taking the file type of the file as a unit. And then compressing the ordered files corresponding to the file types to obtain a compressed package of the target software.
In some embodiments, after the version control system obtains the compressed package of the target software, the compressed package may be uploaded to the content distribution network. If the client corresponding to the user has installed the target software, the client can download a compressed package of the target software from the content distribution network (the compressed package is equivalent to a patch package at this time) and update the target software; if the client corresponding to the user has not installed the target software, the compression package of the target software (the compression package corresponds to the installation package at this time) can be downloaded for installation.
140. And acquiring a plurality of update files corresponding to the target software.
Update files may include, but are not limited to, modified files (modified files) and newly added files. In some embodiments, the developer may upload the update file to the version control system, thereby obtaining a plurality of update files corresponding to the target software.
In some embodiments, file information of the update file may also be obtained; the file information may be an update file List (List) storing file identifications (e.g., file names, file numbers, etc.) of the update files, etc.
150. The compressed package of the target software is updated based on the update file so that the target software is updated with the updated compressed package.
In some embodiments, when a compressed file corresponding to the updated file exists in the compressed package of the target software, the compressed file corresponding to the updated file is updated based on the updated file, so as to obtain an updated compressed file. If the updated file is a modified target file, the compressed file corresponding to the target file is a target compressed file, and the target compressed file is any compressed file in a compressed package of target software; the target compressed file can be decompressed to obtain a target file set, the target file set comprises an original target file, the original target file is replaced by the modified target file, and then the target file set is compressed again to obtain an updated compressed file.
And when the compressed file corresponding to the updated file does not exist in the compressed package of the target software, generating a new compressed file according to the updated file. In some embodiments, the update file is an additional file, and the compressed file compressed by the additional file may be numbered based on the number of the previous compressed file.
Uploading the updated compressed file and the new compressed file so that the client terminal updates the target software based on the updated compressed file and the new compressed file. In some embodiments, the updated compressed file and the new compressed file may also be collectively referred to as a delta patch or delta patch, and the version control system uploads the delta patch to the content distribution network. Only the compressed file with the modified file is decompressed and replaced, so that the time for decompression and recompression can be reduced; and the file size uploaded to the content distribution network and downloaded to the client can be controlled in a smaller range, so that the uploading and downloading speeds are improved.
In some embodiments, when updating the compressed file corresponding to the updated file based on the updated file, file information of the compressed file corresponding to the updated file may also be obtained; the file information of the compressed file may be a file list, which may store an identification of the file in the compressed file, or the like.
Generating an update guide file based on file information of the compressed file corresponding to the update file and file information of the update file; the update guide file may store the number of the compressed file and the file under the compressed file to which the number corresponds.
Uploading the updated guide file so that the client downloads the updated compressed file and the new compressed file according to the updated guide file; the version control system can upload the update guide file to the content distribution network, and after the client starts the target software, the update program of the software can acquire the update guide file, then download the delta patch according to the update guide file, and update the target software based on the delta patch.
In some embodiments, the version control system may also upload the delta patch to a content distribution network that updates the previously stored compressed package of the target software; after the client starts the target software, the update program of the software can acquire the update guide file, then download the updated compression package from the content distribution network according to the update guide file, and update the target software based on the updated compression package.
In some embodiments, file compression under various directories may limit files that need to be modified to within a single directory, which may further reduce the size of the delta patch.
From the above, the invention can obtain the modification record of the file of the target software, and then determine the update frequency of the file by combining experience and statistical methods, thus obtaining the probability that the file is possibly modified in the future; then, according to the update frequency of the files, the files of the target software are compressed by taking the catalogue as a unit, and the files with higher update frequency can be compressed together; therefore, when the file is modified, only a few compressed files can be updated, so that the time for decompressing the file and recompressing the file can be reduced; and when the target software is updated, fewer compressed files can be uploaded to the content distribution network, and the client can download fewer compressed files, so that the uploading and downloading speeds can be improved. Therefore, the scheme can improve the efficiency of software updating.
The software updating scheme provided by the invention can be applied to various software updating scenes. For example, the method of the present invention will be described in detail using a game software update as an example.
As shown in fig. 2a, a specific flow of a software updating method is as follows:
210. a modified record of a plurality of files of game software is obtained.
The version control system can acquire modification records of a plurality of files of the game software in a preset time period, wherein the modification records comprise records of files modified and records of newly added files; the preset time period is related to the game software update frequency and may be typically set to 1-2 months. The record of the file being modified may include a modification time, from which the number of modifications may be counted.
220. And determining the update frequency of the file according to the modification record of the file, wherein the update frequency characterizes the probability of the file being modified.
In some embodiments, for a script type file, the update frequency of the file is determined from a modification record of the file.
For art asset type files: 1) And determining the update frequency of the file according to the modification record of the file when the common virtual game role and the mapping resource file are used. 2) The resource is a metafile (file of an art resource index type) of a resource, and the update frequency of the resource is determined as N-level. 3) The files under the local directory are mainly UI map files, which are a type of files that are updated relatively frequently, so that the changed resources are extremely easy to cause the redistribution of maps, and thus the update frequency of the files can be independently determined according to the modification records.
For files under the target directory (other types): 1) Files under UI, char and Prefab directory are frequently updated files, and directory level is determined to be M level. 2) Worlds, navigate and SoundBanks directory files are the next most frequently updated files, and directory ranks are determined to be M-1 level. 3) The frequency of updating the files under other directories such as GameConfig, fonts, UIImage is low, and the directory rank is determined to be M-2. And determining the update frequency of the files under different directory grades according to the modification records of the files, and superposing the directory grades on the update frequency of the files to obtain the final update frequency of the files. It can be known that the update frequency of the file is determined by the modification record of the file of the game software and by combining experience and a statistical method, so that the probability that the file is possibly modified in the future is obtained, the mode of updating the game software is met, and the accuracy of the update frequency is higher.
In some embodiments, determining the update frequency of the file from the modification record of the file includes:
1) The standard time difference and the time convergence may be determined based on the modification time. The time difference relation between the modification time and the current time of the standard time difference representation file can be calculated by adopting the following formula:
Where n represents the number of modifications, t represents the current time, which may be the time to obtain the modification record.
The time aggregation level represents the aggregation level of the modification time of the file, and the time aggregation level can be calculated by adopting the following formula:
wherein->
Wherein x is i Represents the modification time when the ith file is modified, μ represents the average of the file modification timesValues.
2) The preset modification times are m t Preset time difference threshold D t 。
i. When n is greater than or equal to m t And modDis is less than or equal to D t When the update frequency of the file is determined as N-level.
When n is greater than or equal to m t And mod Dis>D t When the update frequency of the file is determined as N/2 level.
ii. The range of the aggregation degree of the preset time is (S t1 ,S t2 ) When S t1 ≤modStd≤S t2 When the file modification time distribution is uniform, the update frequency of the file is determined to be N/2+1-N-1 level.
iii, when n<m t When the modification time appears in early mod Dis > D t I.e. modDis is significantly larger than D t The method comprises the steps of carrying out a first treatment on the surface of the The update frequency of the file is determined to be 2-N/2+1 level; if the modification time occurs in the middle mod Dis≡D t The method comprises the steps of carrying out a first treatment on the surface of the Determining the update frequency of the file as N/2 level; if the modification time occurs at the later stage mod Dis > D t I.e. modDis is significantly smaller than D t The method comprises the steps of carrying out a first treatment on the surface of the The update frequency of the file is determined as N/2+ 1-N-1 level.
In some embodiments, for the newly added file at the time of the last software update, when the newly added file is a hot update file and __ init __. Py file, etc., the update frequency of the newly added file is determined to be level 1. And other newly added files determine that the update frequency is N/2 level.
In some embodiments, the probability of future resumption of the deleted file is low, so the deletion case may be essentially disregarded.
In some implementations, the update frequency of the script type, the art resource type, and other types of files and sub-types of files thereof is normalized, and a mapping table between the normalized update frequency and the files is obtained. The files are ordered from low to high according to the update frequency, so that a set of files arranged from low to high according to the probability of the files being modified can be obtained.
230. And compressing the file according to the update frequency of the file to obtain a compressed package of the game software.
And compressing the ordered files by using compression software to obtain a plurality of compressed files (also called big files), namely compression packages of game software.
When the compressed file size threshold is set during compression, if the compressed file exceeds 4M, a compressed file with different numbers needs to be newly built, and for platforms with relatively stable networks such as windows, the compressed file size threshold of the compressed file can be appropriately set to be larger, for example, 10M. A compressed package of game software as shown in fig. 2b may be generated based on the update frequency and the compressed file size threshold. The compressed file size threshold is determined according to different network environments, and the flexibility is high.
After the version control system obtains the compressed package of game software, the compressed package may be uploaded to the content distribution network. The client may download a compressed package of game software from the content distribution network and update the game software.
240. And acquiring a plurality of update files corresponding to the game software.
The version control system compares the compressed package of the game software to obtain a set of update files and an update file list of the update files.
250. The compressed package of the game software is updated based on the update file so that the game software is updated with the updated compressed package.
Inquiring a compressed file corresponding to the updated file in a compressed package of the game software, decompressing the target compressed file if the file in the target compressed file is modified, deleting the file corresponding to the updated file, and then merging the rest files into a set of updated files; and updating the file list in the target compressed file to the file list of the updated file to obtain the updated guide file.
For the newly added file (no corresponding compressed file exists in the compressed package of game software), it is merged at the end of the collection of updated files.
And recompressing the set of updated files according to the size threshold of the compressed files to obtain the delta patch. The number of compressed files may be incremented, uniquely numbered, as shown in fig. 2 c.
The version control system uploads the delta patch and the update boot file to the content distribution network. After the client starts the game software, the update program of the software can acquire the update guide file, then download the delta patch according to the update guide file, and update the game software based on the delta patch. Only the compressed file with the modified file is decompressed and replaced, so that the files uploaded to the content distribution network and downloaded to the client can be controlled in a smaller range, and the uploading and downloading speeds are improved.
From the above, the invention can obtain the modification record of the file of the game software, and then determine the update frequency of the file by combining experience and statistical methods, thus obtaining the probability that the file is possibly modified in the future; then, according to the update frequency of the files, the files of the game software are compressed by taking the catalogue as a unit, and the files with higher update frequency can be compressed together; therefore, when the file is modified, only a few compressed files can be updated, so that the time for decompressing the file and recompressing the file can be reduced; and when the game software is updated, fewer compressed files can be uploaded to the content distribution network, and the client can download fewer compressed files, so that the uploading and downloading speeds can be improved. Therefore, the scheme can improve the efficiency of software updating.
In order to better implement the method, the invention also provides a software updating device which can be integrated in electronic equipment, and the electronic equipment can be a terminal, a server and other equipment. The terminal can be a mobile phone, a tablet personal computer, an intelligent Bluetooth device, a notebook computer, a personal computer and other devices; the server may be a single server or a server cluster composed of a plurality of servers.
For example, in this embodiment, the method of the present invention will be described in detail by taking the example that the software updating apparatus is specifically integrated in the first server.
For example, as shown in fig. 3, the software updating apparatus may include a first acquisition unit 301, a determination unit 302, a compression unit 303, a second acquisition unit 304, and an updating unit 305, as follows:
first acquisition unit 301
A first obtaining unit 301, configured to obtain modification records of a plurality of files of the target software.
(two) determination unit 302
A determining unit 302, configured to determine an update frequency of the file according to the modification record of the file, where the update frequency characterizes a probability that the file is modified.
(III) compression Unit 303
And the compression unit 303 is configured to compress the file according to the update frequency of the file, so as to obtain a compressed package of the target software.
(fourth) the second acquisition unit 304
The second obtaining unit 304 is configured to obtain a plurality of update files corresponding to the target software.
(fifth) updating unit 305
An updating unit 305 for updating the compression package of the target software based on the update file so as to update the target software with the updated compression package.
In some embodiments, the determining unit 302 is specifically configured to:
determining the type of the file;
and determining the update frequency of the file according to the modification record of the file and the type of the file.
In some embodiments, the types of the file include an art resource type, a script type, and the art resource type includes an art resource index subtype, and an art resource subtype, and the determining unit 302 is specifically configured to:
when the type of the file is an art resource index sub-type, determining the update frequency of the file as a first level;
when the type of the file is script type or art resource subtype, determining the update frequency of the file according to the modification record of the file.
In some embodiments, the file types further include other file types, and the determining unit 302 is specifically configured to:
determining the directory of the file;
determining the directory grade corresponding to the file according to the directory in which the file is located;
Determining the update frequency of the file according to the modification record of the file;
and weighting the update frequency of the file based on the directory grade corresponding to the file to obtain the weighted update frequency of the file.
In some embodiments, the modification record of the file includes a modification time and a modification number, and the determining unit 302 is specifically configured to:
determining a standard time difference and a time aggregation degree according to the modification time, wherein the standard time difference represents a time difference relation between the modification time of the file and the current time, and the time aggregation degree represents the aggregation degree of the modification time of the file;
when the number of modification times is not less than the preset number of modification times and the standard time difference is not greater than the preset time difference threshold, determining the update frequency of the file as a first level;
when the modification times are not less than the preset modification times and the standard time difference is greater than the preset time difference threshold, determining the update frequency of the file as a second level;
when the time aggregation degree is within a preset time aggregation degree range, determining the update frequency of the file as a third level;
and when the number of modification times is smaller than the preset number of modification times, determining the update frequency of the file according to the standard time difference and the preset time difference threshold value.
In some embodiments, the compression unit 303 is specifically configured to:
sorting the files according to the update frequency of the files to obtain sorted files;
and compressing the sequenced files to obtain a compressed package of the target software.
In some embodiments, the compression package of the target software includes a plurality of compression files, and the compression unit 303 is specifically configured to:
determining a compressed file size threshold according to the network environment;
the ordered files are compressed into a plurality of compressed files based on a compressed file size threshold.
In some embodiments, the updating unit 305 is specifically configured to:
when a compressed file corresponding to the updated file exists in the compressed package of the target software, updating the compressed file corresponding to the updated file based on the updated file to obtain an updated compressed file;
when the compressed file corresponding to the updated file does not exist in the compressed package of the target software, generating a new compressed file according to the updated file;
uploading the updated compressed file and the new compressed file so that the client terminal updates the target software based on the updated compressed file and the new compressed file.
In some embodiments, the updating unit 305 is specifically further configured to:
acquiring file information of an updated file;
Updating the compressed file corresponding to the updated file based on the updated file, and further comprising:
acquiring file information of a compressed file corresponding to the updated file;
generating an update guide file based on file information of the compressed file corresponding to the update file and file information of the update file;
and uploading the updated guide file so that the client downloads the updated compressed file and the new compressed file according to the updated guide file.
In the implementation, each unit may be implemented as an independent entity, or may be implemented as the same entity or several entities in any combination, and the implementation of each unit may be referred to the foregoing method embodiment, which is not described herein again.
As can be seen from the above, the software updating apparatus of the present embodiment may obtain a modification record of a file of the target software, and determine the update frequency of the file according to the modification record, so as to obtain the probability that the file may be modified in the future; then compressing the files of the target software according to the update frequency of the files, so that the files with higher update frequency can be compressed together; therefore, when the file is modified, only a few compressed files can be updated, so that the time for decompressing the file and recompressing the file can be reduced; and when the target software is updated, fewer compressed files can be downloaded, so that the downloading speed can be improved. Therefore, the scheme can improve the efficiency of software updating.
Correspondingly, the embodiment of the application also provides electronic equipment which can be the first server or the second server or the client.
As shown in fig. 4, fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application, where the electronic device 400 includes a processor 401 having one or more processing cores, a memory 402 having one or more computer readable storage media, and a computer program stored in the memory 402 and executable on the processor. The processor 401 is electrically connected to the memory 402. It will be appreciated by those skilled in the art that the electronic device structure shown in the figures is not limiting of the electronic device and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
The processor 401 is a control center of the electronic device 400, connects various parts of the entire electronic device 400 using various interfaces and lines, and performs various functions of the electronic device 400 and processes data by running or loading software programs and/or modules stored in the memory 402, and calling data stored in the memory 402, thereby performing overall monitoring of the electronic device 400.
In the embodiment of the present application, the processor 401 in the electronic device 400 loads the instructions corresponding to the processes of one or more application programs into the memory 402 according to the following steps, and the processor 401 executes the application programs stored in the memory 402, so as to implement various functions:
acquiring modification records of a plurality of files of the target software;
determining the update frequency of the file according to the modification record of the file, wherein the update frequency characterizes the probability of the file being modified;
compressing the file according to the update frequency of the file to obtain a compressed package of the target software;
acquiring a plurality of update files corresponding to target software;
the compressed package of the target software is updated based on the update file so that the target software is updated with the updated compressed package.
The specific implementation of each operation above may be referred to the previous embodiments, and will not be described herein.
Optionally, as shown in fig. 4, the electronic device 400 further includes: a touch display 403, a radio frequency circuit 404, an audio circuit 405, an input unit 406, and a power supply 407. The processor 401 is electrically connected to the touch display 403, the radio frequency circuit 404, the audio circuit 405, the input unit 406, and the power supply 407, respectively. Those skilled in the art will appreciate that the electronic device structure shown in fig. 4 is not limiting of the electronic device and may include more or fewer components than shown, or may combine certain components, or may be arranged in different components.
The touch display 403 may be used to display a graphical user interface and receive operation instructions generated by a user acting on the graphical user interface. The touch display screen 403 may include a display panel and a touch panel. Wherein the display panel may be used to display information entered by a user or provided to a user as well as various graphical user interfaces of the electronic device, which may be composed of graphics, text, icons, video, and any combination thereof. Alternatively, the display panel may be configured in the form of a liquid crystal display (LCD, liquid Crystal Display), an Organic Light-Emitting Diode (OLED), or the like. The touch panel may be used to collect touch operations on or near the user (such as operations on or near the touch panel by the user using any suitable object or accessory such as a finger, stylus, etc.), and generate corresponding operation instructions, and the operation instructions execute corresponding programs. Alternatively, the touch panel may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends the touch point coordinates to the processor 401, and can receive and execute commands sent from the processor 401. The touch panel may overlay the display panel, and upon detection of a touch operation thereon or thereabout, the touch panel is passed to the processor 401 to determine the type of touch event, and the processor 401 then provides a corresponding visual output on the display panel in accordance with the type of touch event. In the embodiment of the present application, the touch panel and the display panel may be integrated into the touch display screen 403 to realize the input and output functions. In some embodiments, however, the touch panel and the touch panel may be implemented as two separate components to perform the input and output functions. I.e. the touch-sensitive display 403 may also implement an input function as part of the input unit 406.
In an embodiment of the application, the game software executed by the processor 401 generates a graphical user interface on the touch display 403. The touch display 403 is used for presenting a graphical user interface and receiving an operation instruction generated by a user acting on the graphical user interface.
The radio frequency circuitry 404 may be used to transceive radio frequency signals to establish wireless communication with a network device or other electronic device via wireless communication.
The audio circuitry 405 may be used to provide an audio interface between a user and an electronic device through a speaker, microphone. The audio circuit 405 may transmit the received electrical signal after audio data conversion to a speaker, where the electrical signal is converted into a sound signal for output; on the other hand, the microphone converts the collected sound signals into electrical signals, which are received by the audio circuit 405 and converted into audio data, which are processed by the audio data output processor 401 and sent via the radio frequency circuit 404 to e.g. another electronic device, or which are output to the memory 402 for further processing. The audio circuit 405 may also include an ear bud jack to provide communication of the peripheral headphones with the electronic device.
The input unit 406 may be used to receive input numbers, character information, or user characteristic information (e.g., fingerprint, iris, facial information, etc.), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.
The power supply 407 is used to power the various components of the electronic device 400. Alternatively, the power supply 407 may be logically connected to the processor 401 through a power management system, so as to implement functions of managing charging, discharging, and power consumption management through the power management system. The power supply 407 may also include one or more of any of a direct current or alternating current power supply, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
Although not shown in fig. 4, the electronic device 400 may further include a camera, a sensor, a wireless fidelity module, a bluetooth module, etc., which are not described herein.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.
As can be seen from the above, the electronic device provided in this embodiment may obtain a modification record of the file of the target software, and determine the update frequency of the file according to the modification record, so as to obtain the probability that the file may be modified in the future; then compressing the files of the target software according to the update frequency of the files, so that the files with higher update frequency can be compressed together; therefore, when the file is modified, only a few compressed files can be updated, so that the time for decompressing the file and recompressing the file can be reduced; and when the target software is updated, fewer compressed files can be downloaded, so that the downloading speed can be improved. Therefore, the scheme can improve the efficiency of software updating.
Those of ordinary skill in the art will appreciate that all or a portion of the steps of the various methods of the above embodiments may be performed by instructions, or by instructions controlling associated hardware, which may be stored in a computer-readable storage medium and loaded and executed by a processor.
To this end, an embodiment of the present application provides a computer readable storage medium having stored therein a plurality of computer programs that can be loaded by a processor to perform the steps of any of the software updating methods provided by the embodiments of the present application. For example, the computer program may perform the steps of:
acquiring modification records of a plurality of files of the target software;
determining the update frequency of the file according to the modification record of the file, wherein the update frequency characterizes the probability of the file being modified;
compressing the file according to the update frequency of the file to obtain a compressed package of the target software;
acquiring a plurality of update files corresponding to target software;
the compressed package of the target software is updated based on the update file so that the target software is updated with the updated compressed package.
The specific implementation of each operation above may be referred to the previous embodiments, and will not be described herein.
Wherein the storage medium may include: read Only Memory (ROM), random access Memory (RAM, random Access Memory), magnetic or optical disk, and the like.
The steps of any software updating method provided by the embodiment of the present application can be executed by the computer program stored in the storage medium, so that the beneficial effects of any software updating method provided by the embodiment of the present application can be achieved, and detailed descriptions of the foregoing embodiments are omitted.
The foregoing describes in detail a software updating method, apparatus, storage medium and electronic device provided in the embodiments of the present application, and specific examples are applied to illustrate the principles and implementation of the present application, where the foregoing examples are only used to help understand the method and core idea of the present application; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in light of the ideas of the present application, the present description should not be construed as limiting the present application.

Claims (11)

1. A method of updating software, comprising:
acquiring modification records of a plurality of files of the target software;
Determining the update frequency of the file according to the modification record of the file, wherein the update frequency represents the probability of the file being modified;
compressing the file according to the update frequency of the file to obtain a compressed package of the target software;
acquiring a plurality of update files corresponding to the target software;
updating the compressed package of the target software based on the update file so as to update the target software by adopting the updated compressed package;
the modification record of the file comprises modification time and modification times, and the determining the update frequency of the file according to the modification record of the file comprises the following steps:
determining a standard time difference and a time aggregation degree according to the modification time, wherein the standard time difference represents a time difference relation between the modification time of the file and the current time, and the time aggregation degree represents the aggregation degree of the modification time of the file;
when the modification times are not smaller than the preset modification times and the standard time difference is not larger than a preset time difference threshold, determining the update frequency of the file as a first level;
when the modification times are not smaller than the preset modification times and the standard time difference is larger than the preset time difference threshold, determining the update frequency of the file as a second level;
When the time aggregation degree is within a preset time aggregation degree range, determining the update frequency of the file as a third level;
and when the modification times are smaller than the preset modification times, determining the update frequency of the file according to the standard time difference and the preset time difference threshold value.
2. The software updating method according to claim 1, wherein said determining the update frequency of the file from the modification record of the file comprises:
determining the type of the file;
and determining the update frequency of the file according to the modification record of the file and the type of the file.
3. The software updating method according to claim 2, wherein the types of the file include an art resource type, a script type, the art resource type including an art resource index sub-type, an art resource sub-type, the determining the update frequency of the file according to the modification record of the file and the type of the file includes:
when the type of the file is an art resource index type, determining the update frequency of the file as a first level;
and when the type of the file is a script type or an art resource subtype, determining the update frequency of the file according to the modification record of the file.
4. The software updating method of claim 3, wherein the file types further include other file types, and wherein determining the update frequency of the file according to the file modification record and the file type comprises:
determining the directory of the file;
determining the directory grade corresponding to the file according to the directory where the file is located;
determining the update frequency of the file according to the modification record of the file;
and weighting the update frequency of the file based on the directory grade corresponding to the file to obtain the weighted update frequency of the file.
5. The software updating method according to claim 1, wherein the compressing the file according to the update frequency of the file to obtain the compressed package of the target software includes:
sorting the files according to the update frequency of the files to obtain sorted files;
and compressing the sequenced files to obtain the compressed package of the target software.
6. The software updating method according to claim 5, wherein the compression package of the target software includes a plurality of compression files, and the compressing the ordered files to obtain the compression package of the target software includes:
Determining a compressed file size threshold according to the network environment;
and compressing the ordered files into a plurality of compressed files based on the compressed file size threshold.
7. The software updating method according to claim 1, wherein the updating the compressed package of the target software based on the update file so as to update the target software with the updated compressed package comprises:
when the compressed file corresponding to the updated file exists in the compressed package of the target software, updating the compressed file corresponding to the updated file based on the updated file to obtain an updated compressed file;
when the compressed file corresponding to the updated file does not exist in the compressed package of the target software, generating a new compressed file according to the updated file;
uploading the updated compressed file and the new compressed file so that the client updates the target software based on the updated compressed file and the new compressed file.
8. The software updating method according to claim 7, wherein the acquiring a plurality of update files further comprises:
acquiring file information of the updated file;
The updating of the compressed file corresponding to the updated file based on the updated file further includes:
acquiring file information of a compressed file corresponding to the updated file;
generating an update guide file based on file information of a compressed file corresponding to the update file and file information of the update file;
uploading the updated guide file so that the client downloads the updated compressed file and the new compressed file according to the updated guide file.
9. A software updating apparatus, comprising:
the first acquisition unit is used for acquiring modification records of a plurality of files of the target software;
a determining unit, configured to determine an update frequency of the file according to a modification record of the file, where the update frequency characterizes a probability that the file is modified;
the compression unit is used for compressing the file according to the update frequency of the file to obtain a compression packet of the target software;
the second acquisition unit is used for acquiring a plurality of update files corresponding to the target software;
an updating unit configured to update a compression package of the target software based on the update file, so as to update the target software with the updated compression package;
The modification record of the file comprises modification time and modification times, and the determining unit is used for:
determining a standard time difference and a time aggregation degree according to the modification time, wherein the standard time difference represents a time difference relation between the modification time of the file and the current time, and the time aggregation degree represents the aggregation degree of the modification time of the file;
when the modification times are not smaller than the preset modification times and the standard time difference is not larger than a preset time difference threshold, determining the update frequency of the file as a first level;
when the modification times are not smaller than the preset modification times and the standard time difference is larger than the preset time difference threshold, determining the update frequency of the file as a second level;
when the time aggregation degree is within a preset time aggregation degree range, determining the update frequency of the file as a third level;
and when the modification times are smaller than the preset modification times, determining the update frequency of the file according to the standard time difference and the preset time difference threshold value.
10. An electronic device comprising a processor and a memory, the memory storing a plurality of instructions; the processor loads instructions from the memory to perform the steps of the software updating method according to any of claims 1-8.
11. A computer readable storage medium storing a plurality of instructions adapted to be loaded by a processor to perform the steps of the software updating method of any of claims 1-8.
CN202110918030.0A 2021-08-11 2021-08-11 Software updating method, device, electronic equipment and storage medium Active CN113568645B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110918030.0A CN113568645B (en) 2021-08-11 2021-08-11 Software updating method, device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110918030.0A CN113568645B (en) 2021-08-11 2021-08-11 Software updating method, device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113568645A CN113568645A (en) 2021-10-29
CN113568645B true CN113568645B (en) 2023-09-12

Family

ID=78171216

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110918030.0A Active CN113568645B (en) 2021-08-11 2021-08-11 Software updating method, device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113568645B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI805158B (en) * 2021-12-29 2023-06-11 威聯通科技股份有限公司 Management method and management system used for reducing version dependency

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101655877A (en) * 2008-10-14 2010-02-24 北京大学 Method and device for packing and extracting files
WO2011067343A2 (en) * 2009-12-04 2011-06-09 St-Ericsson (France) Sas Method of and apparatus for providing a logical view of data stored in an non-volatile memory
CN103559139A (en) * 2013-10-23 2014-02-05 华为技术有限公司 Data storage method and device
CN104508636A (en) * 2012-07-31 2015-04-08 英派尔科技开发有限公司 Parting data to improve system performance
CN106897103A (en) * 2017-03-03 2017-06-27 广州四三九九信息科技有限公司 A kind of method that fast speed heat of mobile terminal online game version updates
WO2017157178A1 (en) * 2016-03-15 2017-09-21 阿里巴巴集团控股有限公司 Mobile terminal application update method and device
CN108427539A (en) * 2018-03-15 2018-08-21 深信服科技股份有限公司 Offline duplicate removal compression method, device and the readable storage medium storing program for executing of buffer memory device data
CN108958663A (en) * 2018-07-23 2018-12-07 南京叠嘉信息科技有限公司 Data read-write method based on hard disk and CD mixing storage system
CN109522041A (en) * 2018-10-15 2019-03-26 网易（杭州）网络有限公司 Client resource update method, device, processor, server and terminal
CN109697071A (en) * 2017-10-24 2019-04-30 腾讯科技（深圳）有限公司 Installation kit synthetic method, device, terminal and storage medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012048540A (en) * 2010-08-27 2012-03-08 Canon Inc Image processing apparatus and control method thereof, information processing system, and program
US9170804B2 (en) * 2012-07-05 2015-10-27 Nokia Technologies Oy Method and apparatus for modifying compressed files
US10095501B2 (en) * 2013-03-15 2018-10-09 Oracle International Corporation Deployment and activation of updates on target hosts
CN105808284B (en) * 2014-12-31 2019-10-22 广州市动景计算机科技有限公司 A kind of method for updating increment and the server using it

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101655877A (en) * 2008-10-14 2010-02-24 北京大学 Method and device for packing and extracting files
WO2011067343A2 (en) * 2009-12-04 2011-06-09 St-Ericsson (France) Sas Method of and apparatus for providing a logical view of data stored in an non-volatile memory
CN104508636A (en) * 2012-07-31 2015-04-08 英派尔科技开发有限公司 Parting data to improve system performance
CN103559139A (en) * 2013-10-23 2014-02-05 华为技术有限公司 Data storage method and device
WO2017157178A1 (en) * 2016-03-15 2017-09-21 阿里巴巴集团控股有限公司 Mobile terminal application update method and device
CN106897103A (en) * 2017-03-03 2017-06-27 广州四三九九信息科技有限公司 A kind of method that fast speed heat of mobile terminal online game version updates
CN109697071A (en) * 2017-10-24 2019-04-30 腾讯科技（深圳）有限公司 Installation kit synthetic method, device, terminal and storage medium
CN108427539A (en) * 2018-03-15 2018-08-21 深信服科技股份有限公司 Offline duplicate removal compression method, device and the readable storage medium storing program for executing of buffer memory device data
CN108958663A (en) * 2018-07-23 2018-12-07 南京叠嘉信息科技有限公司 Data read-write method based on hard disk and CD mixing storage system
CN109522041A (en) * 2018-10-15 2019-03-26 网易（杭州）网络有限公司 Client resource update method, device, processor, server and terminal

Also Published As

Publication number Publication date
CN113568645A (en) 2021-10-29

Similar Documents

Publication Publication Date Title
CN108228270B (en) Starting resource loading method and device
US10922193B2 (en) Data backup method, storage medium, and terminal
CN105227598B (en) Resource sharing method, device and system based on cloud storage
CN112114849A (en) Resource updating method and device
CN113568645B (en) Software updating method, device, electronic equipment and storage medium
CN111580851A (en) Data management method and related device
CN114419229A (en) Image rendering method and device, computer equipment and storage medium
CN112235629B (en) Barrage shielding method and device, computer equipment and storage medium
CN112044061B (en) Game picture processing method and device, electronic equipment and storage medium
CN114238223A (en) Picture removing method and device, computer equipment and computer readable storage medium
CN115269517A (en) File management method, device, storage medium and terminal
CN114676371A (en) Page element information replacement method and device, computer equipment and storage medium
CN114090911A (en) Interface processing method and device, computer equipment and computer readable storage medium
CN114372032A (en) Resource file synchronization method, device, equipment and storage medium
CN110442361B (en) Gray release method and device and electronic equipment
CN114356927A (en) Data storage method and device, computer equipment and storage medium
CN113836343A (en) Audio recommendation method and device, electronic equipment and storage medium
CN112138397A (en) Trigger management method and device, computer equipment and storage medium
CN110688344A (en) File scanning method and device, computer readable storage medium and terminal
CN112245911B (en) Method and device for issuing game program, storage medium and computer equipment
CN114726849B (en) File transmission method, device, server and computer readable storage medium
CN116271848A (en) File updating method, device, electronic equipment and computer readable storage medium
CN111104566B (en) Feature index encoding method, device, electronic equipment and storage medium
CN114100117B (en) Game loading method, game loading device, computer equipment and storage medium
CN112783860B (en) Method, device, storage medium and computer equipment for constructing mirror image database

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant