Updating method, electronic device and computer storage medium

Abstract

The embodiments of the present application provide an update method, an electronic device, and a computer storage medium. The update method includes: sending update detection information to a server when an application is started, wherein the update detection information carries information about existing functional units and usage feature information in the application; obtaining update indication information in response to the update detection information, wherein the update indication information is used to indicate functional units to be updated, wherein the functional units to be updated are part or all of the existing functional units with new versions determined based on the server update load and the usage feature information; and updating the functional units to be updated according to the update indication information.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to an updating method, an electronic device, and a computer storage medium. Background Art

[0002] Existing applications may include multiple functional units to meet different functional requirements. Some or all of these functional units are continuously developed and updated. When a new version of a function is released, it is difficult to ensure that the application obtains the new version of the functional unit in a timely manner and that the server load is controllable. Summary of the Invention

[0003] In view of this, an embodiment of the present application provides an updated solution to at least partially solve the above-mentioned problem.

[0004] According to a first aspect of an embodiment of the present application, an update method is provided, comprising: sending update detection information to a server when an application is started, wherein the update detection information carries information about existing functional units and usage characteristic information in the application; obtaining update indication information in response to the update detection information, wherein the update indication information is used to indicate functional units to be updated, and the functional units to be updated are part or all of the existing functional units with new versions determined based on the server update load and the usage characteristic information; and updating the functional units to be updated according to the update indication information.

[0005] According to the second aspect of an embodiment of the present application, an update method is provided, including: obtaining update detection information, wherein the update detection information carries information about existing functional units and usage characteristic information in an application; determining that there is a new version of an existing functional unit as a candidate functional unit; determining a functional unit to be updated based on an update load and usage characteristic information of each candidate functional unit; and generating update indication information for responding to the update detection information based on the functional unit to be updated.

[0006] According to a third aspect of an embodiment of the present application, an update device is provided, comprising: a first sending module, for sending update detection information to a server when an application is started, wherein the update detection information carries information about existing functional units and usage characteristic information in the application; a first acquisition module, for acquiring update indication information in response to the update detection information, wherein the update indication information is used to indicate a functional unit to be updated, and the functional unit to be updated is part or all of the existing functional units with a new version determined based on the server update load and the usage characteristic information; an update module, for updating the functional unit to be updated according to the update indication information.

[0007] According to the fourth aspect of an embodiment of the present application, an update device is provided, including: a second acquisition module for acquiring update detection information, wherein the update detection information carries existing functional unit information and usage characteristic information in the application; a first determination module for determining the existence of a new version of an existing functional unit as a candidate functional unit; a second determination module for determining the functional unit to be updated based on the update load and the usage characteristic information of each of the candidate functional units; and a second generation module for generating update indication information for responding to the update detection information based on the functional unit to be updated.

[0008] According to the fifth aspect of the embodiments of the present application, an electronic device is provided, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the update method described in the first aspect or the second aspect.

[0009] According to a sixth aspect of an embodiment of the present application, a computer storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the updating method as described in the first aspect or the second aspect is implemented.

[0010] According to the update solution provided in the embodiment of the present application, update detection information carrying usage feature information is sent when the application is started, and update indication information in response to the update detection information is obtained. The functional unit to be updated indicated in the update indication information is determined based on the update load and usage feature information of the server. Therefore, the timeliness of the update according to the update indication information is guaranteed, and excessive load on the server can be avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0012] Figure 1A This is a flowchart of the steps of an updating method according to the first embodiment of the present application;

[0013] Figure 1B Flowchart of another updating method according to the first embodiment of the present application;

[0014] Figure 1C Schematic diagram of sub-steps of step S106 according to the first embodiment of the present application;

[0015] Figure 2 This is a flowchart of the steps of an updating method according to the second embodiment of the present application;

[0016] Figure 3 This is a structural block diagram of an updating device according to the third embodiment of the present application;

[0017] Figure 4 This is a structural block diagram of an updating device according to the fourth embodiment of the present application;

[0018] Figure 5 This is a structural diagram of an electronic device according to the fifth embodiment of the present application. DETAILED DESCRIPTION

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

[0020] The specific implementation of the embodiment of the present application is further explained below in conjunction with the accompanying drawings of the embodiment of the present application.

[0021] Example 1

[0022] Reference Figure 1A , shows a step flow chart of the updating method of embodiment 1 of the present application.

[0023] The method is applied to a map application (i.e., a client) in a terminal device to update some or all functional units in the map application. Of course, in other embodiments, the method can be applied to other applications with independently updateable functional units, without limitation. The method includes:

[0024] Step S102: When the application is started, update detection information is sent to the server.

[0025] The update detection information carries information about existing functional units and usage characteristics in the application.

[0026] In one example, the existing functional unit is a functional unit that runs based on the map application and can be updated independently.

[0027] Different applications can contain different functional units. For example, a map application may contain functional units for searching the surrounding area, calling a ride-hailing service, purchasing tickets, and so on, but this is not limited to these. These functional units run based on the application, but different functional units can be updated independently of each other.

[0028] The usage characteristic information is used to indicate the usage frequency of different functional units by the user of the application program, thereby characterizing the functional units frequently used by the user, so that the frequently used functional units are updated first to ensure the timeliness of the update.

[0029] Alternatively, as Figure 1B As shown, in one feasible manner, in order to obtain more accurate usage feature information, step S100a and step S100b may be performed before step S102.

[0030] Step S100a: obtaining the usage count of the existing functional unit in at least one historical time interval and the adjustment coefficient of each historical time interval.

[0031] Step S100b: determining the usage frequency of each existing functional unit as the usage characteristic information according to the number of times each existing functional unit is used in each historical time interval and the corresponding adjustment coefficient.

[0032] The historical time interval can be one or more than one. When there are more than one, different historical time intervals can be divided according to the length of time from now. For example, a historical time interval can be one week, one month, or 15 days, etc. This embodiment does not limit this.

[0033] Taking the historical time interval of the past week as an example, the number of times an existing functional unit is used in the past week may be the number of times it is clicked, but is not limited thereto.

[0034] To ensure that usage profile information more accurately reflects the user's usage frequency of different functional units, the usage frequency in the usage profile information is determined based on the number of times the corresponding existing functional unit was used within at least one historical time interval and the adjustment coefficient for each historical time interval. Because different historical time intervals have different lengths of time between them, they correspond to different adjustment coefficients. For example, the adjustment coefficient for the past week is w1, and the adjustment coefficient for the week before that is w2.

[0035] The usage frequency of existing functional units can be expressed as: w1x1+w2x2+…+wNxN, where x1 is the number of uses in the past week, w1 is the adjustment coefficient corresponding to the past week (recorded as the first historical time interval), x2 is the number of uses in the week before the past week (the second historical time interval), w2 is its adjustment coefficient, xN is the number of uses corresponding to the Nth historical time interval, and wN is the adjustment coefficient of the Nth historical time interval.

[0036] It should be noted that the adjustment coefficient of each historical time interval can be determined as needed. In order to improve accuracy, the adjustment coefficient of the historical time interval farther away from the current moment is smaller, so that its impact on the frequency of use is smaller.

[0037] By sending update detection information to the server, it can determine whether each functional unit has a new version. If a new version is available, the server can further determine whether it needs to be updated. When determining whether to update a functional unit, the server determines the functional unit to be updated based on the server's update load and the usage characteristics of each functional unit in order to balance the server's load (to avoid excessive server resource occupation) and the timeliness of the update.

[0038] For example, existing functional unit information indicates that a map application includes functional units A, B, C, and D, where new versions of functional units A, B, and C exist. Based on the usage characteristics of functional units A, B, and C and the update load on the server, the functional units to be updated are determined, such as functional units A and B. Based on the relevant information about the functional units to be updated, update indication information can be generated and sent to the application.

[0039] Step S104: Acquire update indication information in response to the update detection information.

[0040] The update indication information is used to indicate the functional units to be updated. As previously mentioned, the functional units to be updated are some or all of the existing functional units with new versions, determined based on the server's update load and the usage characteristic information. Because the update indication information is determined based on the update load and usage characteristic information, it can balance the server load and the timeliness of functional unit updates to a certain extent, thereby improving the user experience.

[0041] In this embodiment, the update indication information includes the identifier, version information, and download address of the functional unit to be updated.

[0042] The identifier of the functional unit to be updated may be the name or number of the functional unit to be updated, etc., as long as the functional unit can be uniquely identified.

[0043] The version information is used to indicate the version number of the functional unit to be updated.

[0044] The download address is used to indicate a download address of update data of the functional unit to be updated.

[0045] Step S106: updating the functional unit to be updated according to the update indication information.

[0046] For example, the update data corresponding to the functional unit to be updated is obtained from the download address in the update instruction information, and the update data is used to update the functional unit. This not only realizes the update of the functional unit, but also effectively controls the update load of the server and avoids excessive resource occupation.

[0047] In one possible approach, Figure 1C As shown, step S106 may include the following sub-steps:

[0048] Sub-step S1061: Acquire update data and verification data corresponding to the functional unit to be updated from the download address.

[0049] The update data may be an installation package of a functional unit, an executable file, etc., and is not limited thereto.

[0050] The verification data can be used to verify the security, integrity, and version of the updated data. The verification data can be determined as needed and there is no restriction on this.

[0051] Sub-step S1062: Use the identifier of the functional unit to be updated and the version information to verify the verification data.

[0052] In order to ensure that the version of the downloaded update data matches the version that needs to be updated, the identification and version information can be used to generate verification standard data in the same way as the verification data (such as a hash algorithm), and compared with the verification data. If the two are consistent, the verification passes and sub-step S1063 is executed; otherwise, if they are inconsistent, the verification fails.

[0053] Sub-step S1063: If the verification passes, the functional unit to be updated is updated using the update data.

[0054] If the verification passes, the data can be updated, thereby updating the functional unit to be updated. It should be noted that in order to prevent the updating of the functional unit from blocking the user's operation and affecting the user experience, if the functional unit to be updated is in use during the update, the update can be suspended and the functional unit to be updated can be updated when it is idle.

[0055] This method solves the problem of applications having difficulty obtaining the underlying permissions of the operating system and being unable to update when the application is not in use. It also eliminates the need to block user operations during updates, reducing the time users spend waiting for updates and thus avoiding a negative impact on the user experience. When determining the functional units to be updated, the server's update load and the usage characteristics of each functional unit are combined. This avoids excessive server update loads and enables timely updates of commonly used functional units. This approach ensures the security of server operations and makes the resource usage distribution of functional unit updates more balanced, avoiding the large amount of idle resources and waste caused by load imbalance.

[0056] Through this embodiment, update detection information carrying usage characteristic information is sent when the application is started, and update indication information in response to the update detection information is obtained. The functional unit to be updated indicated in the update indication information is determined based on the update load and usage characteristic information of the server. Therefore, the timeliness of the update according to the update indication information is guaranteed, and excessive load on the server can be avoided.

[0057] The updating method of this embodiment can be executed by any appropriate electronic device with data processing capability.

[0058] Example 2

[0059] Reference Figure 2 , shows a step flow chart of the updating method of embodiment three of the present application.

[0060] In this embodiment, the method is configured on the server side to determine the functional unit to be updated in the application. The method includes the following steps:

[0061] Step S202: Acquire update detection information.

[0062] The update detection information carries information about existing functional units in the application and usage characteristics. The existing functional unit information may include, but is not limited to, functional unit identifiers. The usage characteristics information indicates the usage frequency of the corresponding existing functional units.

[0063] The usage frequency may be determined according to the number of times the corresponding existing functional unit is used in at least one historical time interval and an adjustment coefficient of each of the historical time intervals.

[0064] The length of the historical time interval can be determined as needed, for example, one week, one month, or N days, where N can be a natural number. For each historical time interval, the product of the corresponding usage count and the corresponding adjustment coefficient is calculated, and the products of each historical time interval are summed to obtain the usage frequency of the corresponding existing functional unit.

[0065] For example, functional unit A has been used x1 times in the week closest to the current moment (recorded as the first historical time interval), with an adjustment factor of w1. The week before the most recent week (recorded as the second historical time interval, and so on) has been used x2 times, with an adjustment factor of w2. Similarly, the number of times used in the Nth historical time interval is xN, with an adjustment factor of wN. The usage frequency can be expressed as w1x1+w2x2+…+wNxN.

[0066] Step S204: Determine whether there is an existing functional unit with a new version as a candidate functional unit.

[0067] In one feasible approach, by comparing the version number corresponding to the existing functional unit with the latest version number of the functional unit stored in the server, a new version of the existing functional unit is determined and used as a candidate functional unit. Of course, the method for determining the candidate functional unit is not limited to this, and other appropriate methods may also be used.

[0068] Step S206: Determine the functional unit to be updated according to the update load and the usage characteristic information of each candidate functional unit.

[0069] In one feasible manner, step S206 may be implemented as: calculating the ratio of the usage frequency to the update load; and selecting candidate functional units whose ratio is greater than or equal to a set update threshold as functional units to be updated.

[0070] For example, if the server's current update load is 80% and the usage frequency of candidate functional unit A is 0.9, then its ratio is 0.9 / 0.8 ​​= 1.125. The ratios of the remaining candidate functional units can be calculated similarly, so this will not be described here. The ratio of each candidate functional unit is compared with the set update threshold. If the ratio is greater than or equal to the update threshold, the unit is identified as a functional unit to be updated.

[0071] For example, in one example, the server determines, based on update detection information, existing functional units with new versions as candidate functional units (e.g., functional units A, C, and D). The usage frequencies are 0.9 for functional unit A, 0.5 for functional unit C, and 0.3 for functional unit D. The usage frequencies can be determined locally by the map application or by the server. This usage scenario uses the map application as an example to illustrate the usage frequency determination.

[0072] Case 1: If the configured update threshold is "1" and the server's current update load is 80%, which means the server's current load is large, the processing for functional units A, C, and D is as follows:

[0073] For functional unit A, the ratio of its usage frequency to update load is: 0.9 / 80%=1.125. The ratio is greater than 1, so functional unit A is selected as the functional unit to be updated.

[0074] For functional unit C, the ratio of its usage frequency to update load is: 0.5 / 80%=0.625. The ratio is less than 1, so functional unit C is not used as a functional unit to be updated.

[0075] For functional unit D, the ratio of its usage frequency to update load is: 0.3 / 80%=0.375. The ratio is less than 1, so functional unit D is not used as a functional unit to be updated.

[0076] In this case, functional unit A is the functional unit to be updated.

[0077] Case 2: If the configured update threshold is "1" and the server's current update load is 50%, the processing for functional units A, C, and D is as follows:

[0078] For functional unit A, the ratio of its usage frequency to update load is: 0.9 / 50%=1.8. The ratio is greater than 1, so functional unit A is selected as the functional unit to be updated.

[0079] For functional unit C, the ratio of its usage frequency to update load is: 0.5 / 50%=1.0. The ratio is equal to 1, so functional unit C is selected as the functional unit to be updated.

[0080] For functional unit D, the ratio of its usage frequency to update load is: 0.3 / 50%=0.6. The ratio is less than 1, so functional unit D is not used as a functional unit to be updated.

[0081] In this case, functional units A and C serve as functional units to be updated.

[0082] Case 3: If the configured update threshold is "1" and the server's current update load is 20%, the processing for functional units A, C, and D is as follows:

[0083] For functional unit A, the ratio of its usage frequency to update load is: 0.9 / 20%=4.5. The ratio is greater than 1, so functional unit A is selected as the functional unit to be updated.

[0084] For functional unit C, the ratio of its usage frequency to update load is: 0.5 / 20%=2.5. The ratio is greater than 1, so functional unit C is selected as the functional unit to be updated.

[0085] For functional unit D, the ratio of its usage frequency to update load is: 0.3 / 20%=1.5. The ratio is greater than 1, so functional unit D is selected as the functional unit to be updated.

[0086] In this case, functional units A, C, and D serve as functional units to be updated.

[0087] By calculating the ratio of usage frequency and update load in this way, the information of usage frequency and update load of functional units can be well integrated, so that the functional units to be updated determined based on the ratio can well balance the timeliness of functional unit updates, and can also take into account the update load of the server to avoid excessive update load. In addition, personalized updates can be performed for different users, fully adapting to different usage habits.

[0088] It should be noted that the update threshold can be determined as needed, and can be a floating value or a fixed value. The update threshold can be appropriately determined based on the bandwidth resources, computing resources, etc. of the configured server.

[0089] In another feasible embodiment, step S306 can be implemented as follows: determining the target number of functional units to be updated (the target number can be denoted as M for ease of description) according to the update load, and selecting the M most frequently used functional units from the candidate functional units as the functional units to be updated.

[0090] Of course, other methods may also be used to determine the functional units to be updated, and this is not limited.

[0091] Step S208: Generate update indication information for responding to the update detection information according to the functional unit to be updated.

[0092] In one feasible approach, update indication information is generated according to the identification, version and download address of the functional unit to be updated, and the update indication information can be sent to an application (eg, a map application) to enable it to update the functional unit.

[0093] This method does not require the map application to have underlying permissions, and can avoid blocking its operations when the user is using it, thereby avoiding affecting the user experience. It can also actively update commonly used functional units to avoid the need to wait for updates. It can also avoid peaks and troughs in the server load or reduce the load difference between peak and low loads, reducing resource waste, thereby achieving dynamic adjustment, ensuring the update of frequently used functional units during peak load periods, and ensuring the update of infrequently used functional units during low peak periods, achieving peak shaving and valley filling, and improving service usage efficiency.

[0094] Example 3

[0095] Reference Figure 3 , shows a structural block diagram of the updating device of Example 3 of the present application.

[0096] In this embodiment, the updating device includes:

[0097] The first sending module 402 is configured to send update detection information to the server when the application is started, wherein the update detection information carries information about existing functional units and usage characteristics of the application;

[0098] A first acquisition module 404 is configured to acquire update indication information in response to the update detection information, wherein the update indication information is used to indicate functional units to be updated, and the functional units to be updated are part or all of the existing functional units with new versions determined based on the server update load and the usage characteristic information;

[0099] The updating module 406 is configured to update the functional unit to be updated according to the updating indication information.

[0100] Optionally, the application is a map application, and the existing functional unit is a functional unit that runs based on the map application and can be updated independently.

[0101] Optionally, the device further comprises:

[0102] A third acquisition module 408 is configured to acquire the number of times the existing functional unit has been used in at least one historical time interval and an adjustment coefficient for each of the historical time intervals;

[0103] The third determining module 410 is configured to determine the usage frequency of each of the existing functional units as the usage characteristic information according to the number of times each of the existing functional units is used in each of the historical time intervals and the corresponding adjustment coefficient.

[0104] Optionally, the update indication information includes the identification, version information and download address of the functional unit to be updated, and the update module 406 is used to obtain the update data and verification data corresponding to the functional unit to be updated from the download address; use the identification and version information of the functional unit to be updated to verify the verification data; if the verification passes, use the update data to update the functional unit to be updated.

[0105] The update device of this embodiment is used to implement the corresponding update methods in the aforementioned multiple method embodiments and has the beneficial effects of the corresponding method embodiments, which will not be described in detail here. In addition, the functional implementation of each module in the update device of this embodiment can refer to the description of the corresponding parts in the aforementioned method embodiments, and will not be described in detail here.

[0106] Example 4

[0107] Reference Figure 4 , shows a structural block diagram of the updating device of the fourth embodiment of the present application.

[0108] In this embodiment, the updating device includes:

[0109] A second acquisition module 502 is configured to acquire update detection information, wherein the update detection information carries information about existing functional units and usage characteristics in the application;

[0110] A first determining module 504 is configured to determine an existing functional unit with a new version as a candidate functional unit;

[0111] A second determining module 506 is configured to determine a functional unit to be updated based on the update load and the usage characteristic information of each candidate functional unit;

[0112] The second generating module 508 is configured to generate update indication information for responding to the update detection information according to the functional unit to be updated.

[0113] Optionally, the usage characteristic information is used to indicate a usage frequency of the corresponding existing functional unit, and the usage frequency is determined according to the number of times the corresponding existing functional unit is used in at least one historical time interval and an adjustment coefficient of each of the historical time intervals.

[0114] Optionally, the second determining module 506 is configured to calculate a ratio of the usage frequency to the update load; and select candidate functional units whose ratio is greater than or equal to a set update threshold as functional units to be updated.

[0115] The update device of this embodiment is used to implement the corresponding update methods in the aforementioned multiple method embodiments and has the beneficial effects of the corresponding method embodiments, which will not be described in detail here. In addition, the functional implementation of each module in the update device of this embodiment can refer to the description of the corresponding parts in the aforementioned method embodiments, and will not be described in detail here.

[0116] Example 5

[0117] Reference Figure 5 , shows a structural diagram of an electronic device according to the fifth embodiment of the present application. The specific embodiment of the present application does not limit the specific implementation of the electronic device.

[0118] like Figure 5 As shown, the electronic device may include: a processor (processor) 602 , a communication interface (Communications Interface) 604 , a memory (memory) 606 , and a communication bus 608 .

[0119] in:

[0120] The processor 602 , the communication interface 604 , and the memory 606 communicate with each other via a communication bus 608 .

[0121] The communication interface 604 is used to communicate with other electronic devices or servers.

[0122] The processor 602 is configured to execute the program 610 , and specifically may execute the relevant steps in the above-mentioned updating method embodiment.

[0123] Specifically, the program 610 may include program codes, which include computer operation instructions.

[0124] Processor 602 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs, or may be processors of different types, such as one or more CPUs and one or more ASICs.

[0125] The memory 606 is used to store the program 610. The memory 606 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0126] The program 610 may be specifically configured to enable the processor 602 to execute operations corresponding to the aforementioned updating method.

[0127] The specific implementation of each step in program 610 can be found in the corresponding descriptions of the corresponding steps and units in the above-mentioned update method embodiment, and will not be repeated here. Those skilled in the art will clearly understand that for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding process descriptions in the above-mentioned method embodiment, and will not be repeated here.

[0128] An embodiment of the present application also provides a computer program product, including computer instructions, which instruct a computing device to execute operations corresponding to any one of the updating methods in the above-mentioned multiple method embodiments.

[0129] It should be pointed out that, according to the needs of implementation, the various components / steps described in the embodiments of the present application can be split into more components / steps, or two or more components / steps or partial operations of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of the present application.

[0130] The above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or be implemented as software or computer code that can be stored in a recording medium (such as CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or be implemented as computer code that is originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded via a network and will be stored in a local recording medium, so that the method described herein can be stored in such software processing on a recording medium using a general-purpose computer, a special-purpose processor or programmable or special-purpose hardware (such as ASIC or FPGA). It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code, and when the software or computer code is accessed and executed by a computer, a processor or hardware, the update method described herein is implemented. In addition, when a general-purpose computer accesses the code for implementing the update method shown here, the execution of the code converts the general-purpose computer into a special-purpose computer for executing the update method shown here.

[0131] Those skilled in the art will appreciate that the units and method steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of this application.

[0132] The above implementation methods are only used to illustrate the embodiments of the present application, and are not intended to limit the embodiments of the present application. Ordinary technicians in the relevant technical field can make various changes and modifications without departing from the spirit and scope of the embodiments of the present application. Therefore, all equivalent technical solutions also fall within the scope of the embodiments of the present application, and the scope of patent protection of the embodiments of the present application should be defined by the claims.

Claims

1. An updating method, comprising: When the application is started, update detection information is sent to the server, wherein the update detection information carries information about existing functional units in the application and usage characteristic information; wherein the usage characteristic information is used to indicate the usage frequency of the corresponding existing functional units; Obtaining update indication information in response to the update detection information, wherein the update indication information is used to indicate functional units to be updated, and the functional units to be updated are part or all of the existing functional units with new versions determined based on the server update load and the usage characteristic information; The functional unit to be updated is updated according to the update indication information.

2. The method according to claim 1, wherein The application is a map application, and the existing functional unit is a functional unit that runs based on the map application and can be updated independently.

3. The method according to claim 1, wherein Before sending the update detection information to the server, the method further includes: Obtaining the number of times the existing functional unit is used in at least one historical time interval and an adjustment coefficient for each of the historical time intervals; The usage frequency of each existing functional unit is determined as the usage characteristic information according to the number of times each existing functional unit is used in each historical time interval and the corresponding adjustment coefficient.

4. The method according to claim 1, wherein The update indication information includes an identifier, version information, and a download address of the functional unit to be updated, and updating the functional unit to be updated according to the update indication information includes: Obtaining update data and verification data corresponding to the functional unit to be updated from the download address; Verifying the verification data using the identifier of the functional unit to be updated and the version information; If the verification passes, the functional unit to be updated is updated using the update data.

5. An updating method, comprising: Acquire update detection information, wherein the update detection information carries information about existing functional units in the application and usage characteristic information; wherein the usage characteristic information is used to indicate the usage frequency of the corresponding existing functional units; Determine an existing functional unit with a new version as a candidate functional unit; Determining a functional unit to be updated based on the update load and usage characteristic information of each candidate functional unit; Generate update indication information for responding to the update detection information according to the functional unit to be updated.

6. The method according to claim 5, wherein: The usage frequency is determined according to the number of times the corresponding existing functional unit is used in at least one historical time interval and an adjustment coefficient of each historical time interval.

7. The method according to claim 5, wherein: The determining of the functional unit to be updated according to the update load and the usage characteristic information of each candidate functional unit includes: Calculating a ratio of the usage frequency to the update load; The candidate functional units whose ratio is greater than or equal to the set update threshold are selected as the functional units to be updated.

8. An electronic device comprising: A processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute an operation corresponding to the updating method according to any one of claims 1 to 7.

9. A computer storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the updating method according to any one of claims 1 to 7 is implemented.

10. A computer program product, comprising computer instructions, wherein the computer instructions instruct a computing device to execute operations corresponding to the updating method according to any one of claims 1 to 7.

Images