Hot update method and device of application, electronic equipment and storage medium

Abstract

The invention discloses an application hot update method and device, electronic equipment and a storage medium, and relates to a distributed technology, and the method comprises the steps: obtaining a plurality of modified patch files; respectively obtaining the file modification times of each patch file; determining an updating sequence of the patch files according to the file modification times; and performing hot update of the application according to the update sequence and the patch file. Compared with the prior art that the module needing to be updated preferentially cannot be updated preferentially, the technical scheme provided by the embodiment of the invention has the advantages that the modification times of each patch file can be obtained, and the updating sequence of the patch files is determined according to the modification times. As the files which are modified frequently have functions which are high in attention and high in demand feedback frequency, whether the patch files need to be updated preferentially can be determined according to the number of the modification frequencies, then the updating sequence is determined, the functions which need to be updated preferentially can be subjected to hot updating preferentially by updating according to the updating sequence, and the hot updating efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of artificial intelligence technology, and in particular to a method, device, electronic device and storage medium for hot updating of an application. Background Art

[0002] There are scenarios where hot updates are required during the use of an application (Application, APP). Hot updates are a common update method used by software developers of an application.

[0003] After the user downloads and installs the application, the instant update encountered when the application is opened. The user does not need to exit the application, and the update performed while the application is running is called hot update.

[0004] Different hot update solutions can be adopted according to the framework adapted by the application. However, the update order of the current hot update solution is to update according to the order of the received update packages. In banking business scenarios, it often happens that with hot updates, the modules that need to be optimized first are not optimized first, but are optimized after the hot update lasts for a certain period of time, resulting in low hot update efficiency. Summary of the invention

[0005] The present invention provides a hot update method, device, electronic device and storage medium for an application, so as to solve the problem that currently the hot update of modules that need to be optimized first cannot be performed first.

[0006] According to one aspect of the present invention, there is provided a method for hot updating an application, comprising:

[0007] Get multiple patch files that have been modified;

[0008] Get the file modification count of each patch file separately;

[0009] Determining the update order of the patch files according to the number of file modification times;

[0010] Perform a hot update of the application according to the update sequence and the patch file.

[0011] According to another aspect of the present invention, there is provided a hot update device for an application, comprising:

[0012] A patch file acquisition module is used to acquire multiple patch files that have been modified;

[0013] A modification count acquisition module is used to obtain the file modification count of each patch file;

[0014] An update sequence determination module, used to determine the update sequence of the patch files according to the number of file modification times;

[0015] An update module is used to perform a hot update of the application according to the update sequence and the patch file.

[0016] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0017] at least one processor; and

[0018] a memory communicatively connected to the at least one processor; wherein,

[0019] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the hot update method for an application described in any embodiment of the present invention.

[0020] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the hot update method of an application described in any embodiment of the present invention when executed.

[0021] The technical solution provided by the embodiment of the present invention obtains multiple patch files that have been modified; obtains the number of file modification times of each patch file respectively; determines the update order of the patch files according to the number of file modification times; and performs hot updates on applications according to the update order and the patch files. Compared with the current inability to give priority to updating modules that need to be updated first, the technical solution provided by the embodiment of the present invention can obtain the number of modifications of each patch file and determine the update order of the patch files according to the number of modifications. Since files with many modifications are often functions with high attention and high demand feedback, it can be determined whether the patch file needs to be updated first based on the number of modifications, and then the update order can be determined. Updating according to this update order can give priority to hot updates of functions that need to be updated first, thereby improving the efficiency of hot updates.

[0022] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1is a flow chart of a hot update method for an application provided by an embodiment of the present invention;

[0025] Figure 2 is a flow chart of another application hot update method provided by an embodiment of the present invention;

[0026] Figure 3 is a schematic diagram of the structure of a hot update device for an application provided by an embodiment of the present invention;

[0027] Figure 4 It is a structural schematic diagram of an electronic device for implementing the hot update method of the application of the embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] The information collected by the embodiments of the present invention is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of relevant countries and regions, take necessary confidentiality measures, do not violate public order and good customs, and provide corresponding operation portals for users to choose to authorize or refuse. Provide users with corresponding operation portals for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered to avoid relevant legal risks and public opinion risks.

[0031] There are scenarios where applications (Applications, APPs) need to be hot updated during use. Hot update is a common update method used by software developers of applications. After users download and install an application, they encounter instant updates when they open the application. Users do not need to exit the application. The update performed during the application is called hot update.

[0032] Different hot update solutions can be adopted according to the framework adapted by the application. However, the update order of the current hot update solution is to update according to the order of the received update packages. In banking business scenarios, it often happens that with hot updates, the modules that need to be optimized first are not optimized first, but are optimized after the hot update lasts for a certain period of time, resulting in low hot update efficiency.

[0033] Figure 1 This is a flow chart of a hot update method for an application provided by an embodiment of the present invention. This embodiment is applicable to the case of hot updating an application program. The method can be executed by a hot update device for an application. The hot update device for an application can be implemented in the form of hardware and / or software. The hot update device for an application can be configured in electronic devices such as personal computers and servers. Figure 1 As shown, the method includes:

[0034] Step S101: Acquire multiple modified patch files.

[0035] Get updated program files, and generate patch files according to the program files. Each program file has a corresponding header file, that is, the program file and the header file appear in a group. Generate a patch file of the header file according to the header file, and generate a patch file of the program file according to the program file.

[0036] For example, in the Apple system (IOS), the program file of the function logic to be animated is written in Objective-C language, and the format of the program file ends with ".m". Then, the patch file is generated through the tool chain provided by the Objective-C package (Pack), which is also called a patch file and ends with ".bin".

[0037] Step S102: Obtain the file modification times of each patch file respectively.

[0038] For each patch file, the number of times the patch file is modified can be obtained as the number of file modification times. The number of file modification times can also be determined based on the number of times each file frame in the patch file is modified.

[0039] Optionally, the modification count of each patch file can be obtained separately, which can be implemented in the following way:

[0040] The frame modification times of each patch file frame in each patch file are counted respectively; and the file modification times of each patch file are determined according to the sum of the frame modification times.

[0041] The patch file frame includes multiple patch file frames, each of which can correspond to a data row. When the programmer updates the program, the content of the data row will change. Every time a change occurs, the frame modification count of the patch file frame increases by 1. The frame modification count can be reset to zero after completing an update. The frame modification count can also be retained to count the number of modifications to the patch file frame during each update process.

[0042] The number of frame modifications of each patch file frame is accumulated and summed to obtain the number of file modification times of the patch file.

[0043] The above implementation can detect the file frames included in the patch file and determine the file modification times according to the sum of the frame modification times of each file frame. The file modification times can represent the sum of all modification parameters included in the patch file, thereby realizing accurate calculation of the patch file modification times and improving the accuracy of the file modification times calculation.

[0044] Step S103: determining the update order of the patch files according to the number of file modification times.

[0045] The higher the number of times a patch file has been modified, the higher the priority it will be updated.

[0046] Optionally, determining the update order of the patch files according to the number of file modification times may be implemented in the following manner:

[0047] Sorting is performed according to the number of file modification times to obtain a sorting result; and an update order of the patch files is determined according to the sorting result.

[0048] The number of file modification times of each patch file may be sorted in descending order to obtain a sorting result, which determines the update order of the patch files corresponding to each number of modification times.

[0049] The above implementation can accurately determine the update sequence of the patch files based on the sorting results, thereby improving the reliability of the update sequence.

[0050] Optionally, sorting is performed according to the number of file modification times to obtain a sorting result, which can be implemented as follows:

[0051] Determine the weight information of each patch file according to the preset dimension; determine the score of each patch file according to the weight information and the number of file modifications; and sort according to the score to obtain a sorting result.

[0052] Considering that the modification is performed only based on the number of file modification times, there may be a situation where multiple files have the same number of modification times. There may also be a situation where the number of file modification times is close, and the difference is not greater than 3, but the patch file with a smaller number of file modification times needs to be updated first. Based on this, the weight information of each patch file can be determined according to the preset dimension.

[0053] Among them, the preset dimension is a combination of one or more of the following dimensions

[0054] Core data dependencies, style dependencies, or configuration dependencies;

[0055] The core data relevance indicates the degree of association between the patch file and the core data processing;

[0056] The style correlation indicates the degree of association between the patch file and the application interface style;

[0057] The configuration association indicates the association between the patch file and the system interface configuration or the partner interface configuration.

[0058] Exemplarily, core data may include account information and other data related to the core content of the transaction. For data on the interface style of the application, such as the interface layout, color scheme, and icons, the style relevance is determined. After the operating system is updated, the configuration update of the new underlying interface has a higher configuration relevance. Some interfaces that need to be provided by partners need to be updated first when the partners modify the interfaces. Therefore, the patch files involving the partner interface configuration have a higher configuration relevance.

[0059] The weight calculation rules can be pre-configured. The higher the core data relevance, the higher the weight. The higher the style relevance, the lower the weight. The higher the configuration relevance, the higher the weight. The specific rules can be configured according to the specific situation, and there is no limitation here.

[0060] Through various types of preset dimensions, the weight information of the patch file can be accurately determined from different dimensions, thereby improving the accuracy of the weight information.

[0061] The obtained weight information is multiplied by the number of file modifications to obtain the score of the patch file. After sorting according to the score, the update order is determined according to the sorting result.

[0062] The above implementation method can calculate the score of each patch file by combining the weight information and the number of modifications. The score reflects the comprehensive result of the weight information and the number of modifications, making the sorting result more accurate.

[0063] Step S104: perform a hot update of the application according to the update sequence and the patch file.

[0064] Optionally, performing hot update of the application according to the update sequence and the patch file may be implemented in the following manner:

[0065] Acquire address information of patch files in sequence according to the update sequence;

[0066] The address information is sent to the update unit, so that the update unit obtains the patch files according to the address information and performs hot updates in sequence.

[0067] The above implementation can control the update unit in the terminal to read the patch file based on the address information of the patch file. The update unit does not need to determine the update order of the patch file. For update units with different operating systems, the original function of reading the patch file according to the address information and executing the hot update of the patch file can be retained, without modifying the update unit, thereby improving versatility.

[0068] Optionally, performing hot update of the application according to the update sequence and the patch file may be implemented in the following manner:

[0069] The patch files involved in the update are determined according to the update sequence and a preset threshold; and the application is hot updated according to the patch files involved in the update.

[0070] The preset threshold can be a ranking order threshold or a file modification count threshold. Optionally, the patch files corresponding to the sorting results from the first sorting result to the ranking order threshold position in the sorting results are determined as patch files participating in the update. Optionally, the number of file modifications whose value is greater than the file modification count threshold is searched from the sorting results, and the patch file corresponding to the number of file modifications is determined as the patch file participating in the update. This achieves the purpose of dynamically downloading the file until it is updated. For patch files that are not determined to participate in the update, the memory address mark is recycled, so that the update unit will not download the file, and will download and update it again when it is needed next time.

[0071] The above implementation can realize updating by intercepting some patch files from the update sequence based on a preset threshold, and patch files with fewer changes can be retained for updating at the next update, thereby realizing selective updating and improving usability.

[0072] The hot update method for an application provided in an embodiment of the present invention obtains multiple patch files that have been modified; obtains the number of file modification times for each patch file respectively; determines the update order of the patch files according to the number of file modification times; and performs hot update of the application according to the update order and the patch files. Compared with the current inability to give priority to updating modules that need to be updated first, the hot update method for an application provided in an embodiment of the present invention can obtain the number of modification times for each patch file, and determine the update order of the patch files according to the number of modification times. Since files with many modification times are often functions with high attention and high demand feedback times, it can be determined whether the patch file needs to be updated first based on the number of modification times, and then the update order can be determined. Updating according to this update order can give priority to hot updating of functions that need to be updated first, thereby improving the efficiency of hot updates.

[0073] Figure 2 A schematic flow chart of a hot update method for an application provided in an embodiment of the present invention includes:

[0074] Step S201: Acquire multiple modified patch files.

[0075] Step S202, counting the frame modification times of each patch file frame in each patch file respectively; and determining the file modification times of each patch file according to the sum of the frame modification times.

[0076] Step S203: determine the weight information of each patch file according to the preset dimension; determine the score of each patch file according to the weight information and the number of file modifications; and sort according to the score to obtain a sorting result.

[0077] The preset dimension is a combination of one or more of the following dimensions:

[0078] Core data dependencies, style dependencies, or configuration dependencies;

[0079] The core data relevance indicates the degree of association between the patch file and the core data processing;

[0080] The style correlation indicates the degree of association between the patch file and the application interface style;

[0081] The configuration association indicates the association between the patch file and the system interface configuration or the partner interface configuration.

[0082] Step S204: Determine the update order of the patch files according to the sorting result.

[0083] Step S205: determining the patch files involved in the update according to the update sequence and a preset threshold; and performing a hot update of the application according to the patch files involved in the update.

[0084] Step S206: sequentially obtain address information of patch files involved in the update.

[0085] Step S207: Send the address information to the update unit, so that the update unit obtains patch files according to the address information and performs hot updates in sequence.

[0086] Figure 3 FIG. 1 is a schematic diagram of a hot update device for an application provided by an embodiment of the present invention, and the device is suitable for hot updating an application program. Figure 3 As shown, the device includes: a patch file acquisition module 31, a modification number acquisition module 32, an update sequence determination module 33 and an update module 34.

[0087] A patch file acquisition module 31 is used to acquire a plurality of modified patch files;

[0088] A modification count acquisition module 32 is used to respectively acquire the file modification count of each patch file;

[0089] An update sequence determination module 33, used to determine the update sequence of the patch files according to the number of file modification times;

[0090] The update module 34 is used to perform hot update of the application according to the update sequence and the patch file.

[0091] Based on the above embodiment, optionally, the modification times acquisition module 32 is used to:

[0092] Count the number of frame modifications of each patch file frame in each patch file respectively;

[0093] The file modification times of each patch file are determined according to the sum of the frame modification times.

[0094] Based on the above embodiment, optionally, the update sequence determination module 33 is used to:

[0095] Sorting the files according to the number of modification times to obtain a sorting result;

[0096] An update order of the patch files is determined according to the sorting result.

[0097] Based on the above embodiment, optionally, the update sequence determination module 33 is used to:

[0098] Determine the weight information of each patch file according to the preset dimension;

[0099] Determine a score for each patch file according to the weight information and the number of file modifications;

[0100] Sorting is performed according to the scores to obtain a sorting result.

[0101] Based on the above embodiment, optionally, the preset dimension is a combination of one or more of the following dimensions:

[0102] Core data dependencies, style dependencies, or configuration dependencies;

[0103] The core data relevance indicates the degree of association between the patch file and the core data processing;

[0104] The style correlation indicates the degree of association between the patch file and the application interface style;

[0105] The configuration association indicates the association between the patch file and the system interface configuration or the partner interface configuration.

[0106] Based on the above embodiment, optionally, the updating module 34 is used to:

[0107] Determine the patch files involved in the update according to the update sequence and a preset threshold;

[0108] Perform a hot update of the application according to the patch file involved in the update.

[0109] Based on the above embodiment, optionally, the updating module 34 is used to:

[0110] Acquire address information of patch files in sequence according to the update sequence;

[0111] The address information is sent to the update unit, so that the update unit obtains the patch files according to the address information and performs hot updates in sequence.

[0112] The hot update device for an application provided in an embodiment of the present invention comprises a patch file acquisition module 31 for acquiring multiple patch files that have been modified; a modification count acquisition module 32 for respectively acquiring the file modification counts of each patch file; an update sequence determination module 33 for determining the update sequence of the patch files according to the file modification counts; and an update module 34 for hot updating the application according to the update sequence and the patch files. Compared with the current inability to give priority to updating modules that need to be updated first, the hot update device for an application provided in an embodiment of the present invention can obtain the modification count of each patch file and determine the update sequence of the patch files according to the modification counts. Since files with many modifications are often functions with high attention and high feedback requirements, it is possible to determine whether the patch file needs to be updated first based on the number of modifications, and then determine the update sequence. Updating according to the update sequence can give priority to hot updating of functions that need to be updated first, thereby improving the efficiency of hot updates.

[0113] The application hot update device provided in the embodiment of the present invention can execute the application hot update method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0114] Figure 4 1 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0115] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0116] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0117] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a hot update method for an application.

[0118] In some embodiments, the hot update method of the application may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the hot update method of the application described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the hot update method of the application in any other appropriate manner (e.g., by means of firmware).

[0119] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0120] The computer program for implementing the hot update method of the application of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program can be executed completely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or completely on a remote machine or server.

[0121] An embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to execute a hot update method for an application, the method comprising:

[0122] Get multiple patch files that have been modified;

[0123] Get the file modification count of each patch file separately;

[0124] Determining the update order of the patch files according to the number of file modification times;

[0125] Perform a hot update of the application according to the update sequence and the patch file.

[0126] Based on the above embodiment, optionally, the modification times of each patch file are obtained respectively, including:

[0127] Count the number of frame modifications of each patch file frame in each patch file respectively;

[0128] The file modification times of each patch file are determined according to the sum of the frame modification times.

[0129] Based on the above embodiment, optionally, determining the update order of the patch files according to the number of file modification times includes:

[0130] Sorting the files according to the number of modification times to obtain a sorting result;

[0131] An update order of the patch files is determined according to the sorting result.

[0132] On the basis of the above embodiment, optionally, sorting is performed according to the number of file modification times to obtain a sorting result, including:

[0133] Determine the weight information of each patch file according to the preset dimension;

[0134] Determine a score for each patch file according to the weight information and the number of file modifications;

[0135] Sorting is performed according to the scores to obtain a sorting result.

[0136] Based on the above embodiment, optionally, the preset dimension is a combination of one or more of the following dimensions:

[0137] Core data dependencies, style dependencies, or configuration dependencies;

[0138] The core data relevance indicates the degree of association between the patch file and the core data processing;

[0139] The style correlation indicates the degree of association between the patch file and the application interface style;

[0140] The configuration association indicates the association between the patch file and the system interface configuration or the partner interface configuration.

[0141] Based on the above embodiment, optionally, performing hot update of the application according to the update sequence and the patch file includes:

[0142] Determine the patch files involved in the update according to the update sequence and a preset threshold;

[0143] Perform a hot update of the application according to the patch file involved in the update.

[0144] Based on the above embodiment, optionally, performing hot update of the application according to the update sequence and the patch file includes:

[0145] Acquire address information of patch files in sequence according to the update sequence;

[0146] The address information is sent to the update unit, so that the update unit obtains the patch files according to the address information and performs hot updates in sequence.

[0147] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0148] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0149] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0150] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0151] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0152] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A hot update method for an application, characterized in that: include: Get multiple patch files that have been modified; Get the file modification count of each patch file separately; Determining the update order of the patch files according to the number of file modification times; Perform a hot update of the application according to the update sequence and the patch file.

2. The method according to claim 1, characterized in that Get the modification times of each patch file separately, including: Count the number of frame modifications of each patch file frame in each patch file respectively; The file modification times of each patch file are determined according to the sum of the frame modification times.

3. The method according to claim 1, characterized in that Determining the update order of the patch files according to the number of file modification times includes: Sorting the files according to the number of modification times to obtain a sorting result; An update order of the patch files is determined according to the sorting result.

4. The method according to claim 3, characterized in that: Sorting is performed according to the number of modification times of the files to obtain a sorting result, including: Determine the weight information of each patch file according to the preset dimension; Determine a score for each patch file according to the weight information and the number of file modifications; Sorting is performed according to the scores to obtain a sorting result.

5. The method according to claim 4, characterized in that The preset dimension is a combination of one or more of the following dimensions: Core data dependencies, style dependencies, or configuration dependencies; The core data relevance indicates the degree of association between the patch file and the core data processing; The style correlation indicates the degree of association between the patch file and the application interface style; The configuration association indicates the association between the patch file and the system interface configuration or the partner interface configuration.

6. The method according to claim 3, characterized in that Performing a hot update of the application according to the update sequence and the patch file includes: Determine the patch files involved in the update according to the update sequence and a preset threshold; Perform a hot update of the application according to the patch file involved in the update.

7. The method according to claim 1, characterized in that: Performing a hot update of the application according to the update sequence and the patch file includes: Acquire address information of patch files in sequence according to the update sequence; The address information is sent to the update unit, so that the update unit obtains the patch files according to the address information and performs hot updates in sequence.

8. A hot update device for an application, characterized in that: include: A patch file acquisition module is used to acquire multiple patch files that have been modified; A modification count acquisition module is used to obtain the file modification count of each patch file; An update sequence determination module, used to determine the update sequence of the patch files according to the number of file modification times; An update module is used to perform a hot update of the application according to the update sequence and the patch file.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the hot update method for an application according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the hot update method of an application according to any one of claims 1 to 7 when the instructions are executed.

Images