SDK repair method and apparatus, terminal, device, system, and medium
Patent Information
- Application Number
- MYPI2025001276
- Authority / Receiving Office
- MY · MY
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-08-26
- Filing Date
- 2023-03-06
- Publication Date
- 2024-02-26
AI Technical Summary
The existing technology is difficult to meet the software development kit (SDK) repair needs of different channel parties, and a single repair method cannot adapt to the differential anomalies of each channel party and SDK version.
By obtaining SDK information, host information and exception information, the abnormal impact parameters are calculated, and a targeted repair strategy is generated based on the preset exception hierarchical processing rules, and is delivered to the user terminal to achieve SDK repair.
It realizes automatic repair strategy allocation for different channel parties and SDK versions, meets diverse SDK repair needs, and improves the normal operation efficiency of the SDK.
Smart Images

Figure PI2025001276_DRAWING_001 
Figure PI2025001276_DRAWING_002 
Figure PI2025001276_DRAWING_003
Abstract
Description
SDK repair method, device, terminal, equipment, system and medium
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to Chinese patent application No. 202211035360.6, filed on August 26, 2022, entitled “SDK repair method, device, terminal, equipment, system and medium,” and the entire contents of that application are incorporated herein by reference. Technical Field
[0003] The present application relates to the field of data processing, and in particular to a method, apparatus, terminal, device, system and medium for repairing an SDK. Background Art
[0004] A software development kit (SDK) is a toolkit that provides specific functionality for a software framework, hardware platform, operating system, or application. SDKs can be embedded into various host systems, such as software frameworks, hardware platforms, operating systems, or applications. When running with a host, an SDK may experience anomalies, requiring SDK repair to ensure proper operation.
[0005] However, due to differences in the development methods and host environments of different channel parties, the defects in the SDK may also be different. A single repair of the SDK is difficult to meet the repair needs of the SDKs of different channel parties.
[0006] Summary of the Invention
[0007] The embodiments of the present application provide an SDK repair method, apparatus, terminal, device, system, and medium that can meet the SDK repair needs of different channel parties.
[0008] In the first aspect, an embodiment of the present application provides an SDK repair method, which is applied to a repair platform, and the method includes: obtaining software development kit SDK information, host information and SDK exception information of different exception types; obtaining exception impact parameters corresponding to each exception type of the target SDK based on the SDK information, host information and SDK exception information of each exception type, and the target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information; based on the exception impact parameters corresponding to each exception type of the target SDK and preset exception grading processing rules, obtaining a target SDK repair strategy, the target SDK repair strategy including the SDK repair strategy of the exception level corresponding to the exception impact parameters in the exception grading processing rules; issuing the target SDK repair strategy to the user terminal so that the user terminal executes the target SDK repair strategy to repair the target SDK.
[0009] In the second aspect, an embodiment of the present application provides an SDK repair method, which is applied to a user terminal, and the method includes: providing software development kit SDK information, host information and SDK exception information of different exception types to a repair platform, so that the repair platform obtains a target SDK repair strategy based on the exception impact parameters corresponding to each exception type of the target SDK and preset exception grading processing rules, the target SDK repair strategy includes an SDK repair strategy for the exception level corresponding to the exception impact parameters in the exception grading processing rules, the target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information, and the exception impact parameters corresponding to each exception type of the target SDK are obtained according to the SDK information, host information and SDK exception information of each exception type; obtaining the target SDK repair strategy from the repair platform, and executing the target SDK repair strategy to repair the target SDK.
[0010] In a third aspect, an embodiment of the present application provides an SDK repair device, which is applied to a repair platform, and the device includes: an acquisition module for acquiring software development kit SDK information, host information and SDK exception information of different exception types; a calculation module for obtaining exception impact parameters corresponding to each exception type of the target SDK based on the SDK information, host information and SDK exception information of each exception type, and the target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information; a policy configuration module for obtaining a target SDK repair policy based on the exception impact parameters corresponding to each exception type of the target SDK and preset exception grading processing rules, the target SDK repair policy including the SDK repair policy of the exception level corresponding to the exception impact parameters in the exception grading processing rules; a issuing module for issuing the target SDK repair policy to the user terminal so that the user terminal executes the target SDK repair policy to repair the target SDK.
[0011] In a fourth aspect, an embodiment of the present application provides a user terminal, including: a sending module, used to provide software development kit SDK information, host information and SDK exception information of different exception types to a repair platform, so that the repair platform obtains a target SDK repair strategy based on the exception impact parameters corresponding to each exception type of the target SDK and preset exception grading processing rules, the target SDK repair strategy includes an SDK repair strategy of the exception level corresponding to the exception impact parameters in the exception grading processing rules, the target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information, and the exception impact parameters corresponding to each exception type of the target SDK are obtained according to the SDK information, the host information and the SDK exception information of each exception type; a receiving module, used to obtain the target SDK repair strategy from the repair platform; an execution module, used to execute the target SDK repair strategy to repair the target SDK.
[0012] In a fifth aspect, an embodiment of the present application provides an electronic device applied to a repair platform, the electronic device comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the SDK repair method of the first aspect is implemented.
[0013] In a sixth aspect, an embodiment of the present application provides a user terminal comprising: a processor and a memory storing computer program instructions; and when the processor executes the computer program instructions, the SDK repair method of the second aspect is implemented.
[0014] In a seventh aspect, an embodiment of the present application provides an SDK repair system, comprising: a repair platform for executing the SDK repair method of the first aspect; and a user terminal for executing the SDK repair method of the second aspect.
[0015] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium having computer program instructions stored thereon. When the computer program instructions are executed by a processor, the SDK repair method of the first aspect or the SDK repair method of the second aspect is implemented.
[0016] The embodiments of the present application provide a method, apparatus, terminal, device, system and medium for repairing an SDK. The repair platform can obtain an abnormal impact parameter that characterizes the impact of an abnormal type on the SDK based on the SDK information, host information and the collected SDK abnormal information of different abnormal types, thereby obtaining an SDK repair strategy corresponding to the abnormal level based on the abnormal impact parameter corresponding to each abnormal type and the preset abnormal classification processing rules and sending it to the user terminal. The user terminal can execute the SDK repair strategy corresponding to the abnormal level to repair the SDK. Different host information corresponds to different host programs, different host programs correspond to different channel parties, and different versions of SDK also correspond to different SDK information. Different versions of SDK embedded in the host programs of different channel parties generate different SDK abnormal information. Through the collected SDK abnormal information, an SDK repair strategy corresponding to the abnormal level of each version of the SDK embedded in the host program of each channel party can be obtained, that is, an adaptive SDK repair strategy can be automatically assigned to different versions of SDK embedded in the host programs of different channel parties, thereby meeting the repair needs of the SDKs of different channel parties. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0018] FIG1 is a schematic diagram of an example of an application scenario of the SDK repair method provided in an embodiment of the present application;
[0019] FIG2 is a schematic diagram of another example of an application scenario of the SDK repair method provided in an embodiment of the present application;
[0020] FIG3 is a flowchart of an SDK repair method provided in an embodiment of the first aspect of the present application;
[0021] FIG4 is a flowchart of an SDK repair method provided by another embodiment of the first aspect of the present application;
[0022] FIG5 is a flowchart of a method for repairing an SDK according to another embodiment of the first aspect of the present application;
[0023] FIG6 is a flowchart of an SDK repair method provided in an embodiment of the second aspect of the present application;
[0024] FIG7 is a flowchart of an SDK repair method provided by another embodiment of the second aspect of the present application;
[0025] FIG8 is a flowchart of a method for repairing an SDK according to another embodiment of the second aspect of the present application;
[0026] FIG9 is a logic diagram of an example of a method for repairing an SDK provided in an embodiment of the present application;
[0027] FIG10 is a schematic structural diagram of an SDK repair device provided in an embodiment of the third aspect of the present application;
[0028] FIG11 is a schematic structural diagram of a user terminal provided in an embodiment of the fourth aspect of the present application;
[0029] FIG12 is a schematic structural diagram of an electronic device provided in an embodiment of the fifth aspect of the present application. DETAILED DESCRIPTION
[0030] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is merely to provide a better understanding of the present application by illustrating the examples of the present application.
[0031] A Software Development Kit (SDK) is a toolkit that provides a certain function for a software framework, hardware platform, operating system, or application. The SDK can be embedded in hosts such as software frameworks, hardware platforms, operating systems, or applications from different channels. When the SDK runs together with the host, anomalies may occur, and the SDK needs to be repaired so that it can run normally. However, due to differences in the development methods and host environments of different channels, the defects that appear in the SDK may also be different. A single repair of the SDK is difficult to meet the repair needs of the SDKs of different channels.
[0032] The present application provides a method, apparatus, terminal, device, system and medium for repairing an SDK. The repair platform can obtain an abnormal impact parameter that can characterize the impact of the abnormal type on the SDK based on the SDK information, host information and the collected SDK abnormal information of different abnormal types, thereby obtaining an SDK repair strategy corresponding to the abnormal level based on the abnormal impact parameter corresponding to each abnormal type and the preset abnormal classification processing rules, and sending it to the user terminal. The user terminal can execute the SDK repair strategy corresponding to the abnormal level to repair the SDK. Different channel parties have different host information, different versions of SDK have different SDK information, and different channel parties and different versions of SDK generate different SDK abnormal information. Through different information, an SDK repair strategy corresponding to the abnormal level of each channel party and each version of SDK can be obtained, that is, different channel parties and different versions of SDK can obtain an adapted SDK repair strategy, which can meet the repair needs of the SDKs of different channel parties.
[0033] The SDK repair method provided in the embodiments of the present application can be applied to scenarios involving SDK repair, and can involve a repair platform and a user terminal. Figure 1 is a schematic diagram of an example application scenario of the SDK repair method provided in the embodiments of the present application. As shown in Figure 1, a user terminal 11 can communicate and interact with a repair platform 12.
[0034] The user terminal 11 has at least one host program 111 and at least one SDK 112. The same user terminal may have multiple different host programs 111, and different host programs 111 correspond to different channels. SDK 112 may be embedded in the host program 111, and the host program 111 may call SDK 112 to use the functions provided by SDK 112. The user terminal 11 may specifically include a mobile phone, a tablet computer, an electronic computer, a smart wearable device, etc., which is not limited here. SDK 112 may provide SDK information of SDK 112, SDK exception information, and host information of the host program 111 where SDK 112 is located to the repair platform 12 as an information provider. The user terminal 11 may obtain a targeted SDK repair strategy from the repair platform 12 and execute the SDK repair strategy to repair SDK 112, which is the object to be repaired.
[0035] The repair platform 12 can be a backend system for providing SDK repair services to user terminals and can include one or more electronic devices. Electronic devices may include servers, gateways, routers, and other devices, and the type and number of electronic devices in the repair platform 12 are not limited here. The repair platform 12 can provide SDK repair services to multiple user terminals 11. The host programs 111 in different user terminals can be the same or different. The repair platform 12 can maintain correspondences between different channel parties, host programs, users, SDKs, SDK exception information, and SDK repair policies. It can classify and summarize SDK exception types and perform actions such as alarms and prompts. The repair platform 12 can issue repair policies specifically for the SDK 112 that needs to be repaired in different user terminals 11. The repair platform 12 can also issue targeted repair policies to user terminals in a full, grayscale, or user-specific manner, and these are not limited here.
[0036] In some embodiments, the SDK repair method provided in the embodiments of the present application may also involve a channel platform. FIG2 is a schematic diagram of another example of an application scenario of the SDK repair method provided in the embodiments of the present application. As shown in FIG2 , the channel platform 13 can communicate and interact with the repair platform 12.
[0037] The channel platform 13 can be an audit platform for the SDK repair policy and can include more than one electronic device. The electronic devices can include servers, gateways, routers and other devices. The type and quantity of electronic devices in the channel platform 13 are not limited here. Each channel party can open an account on the channel platform 13 and review the SDK repair policy provided for the SDK 112 embedded in the host program 11 of the channel party through the channel platform 13. The SDK repair policy provided for the SDK 112 embedded in the host program 111 can first be sent to the channel platform 13 corresponding to the host program 111 for review. After the channel platform 13 has reviewed and approved the SDK repair policy, the repair platform 13 will send the SDK repair policy to the user terminal 11. In some examples, the channel platform 13 can also provide SDK exception information to the repair platform 13.
[0038] The following describes the SDK repair method, device, terminal, equipment, system and medium in this application respectively.
[0039] In a first aspect, the present application provides a method for repairing an SDK, which can be applied to a repair platform, i.e., the method for repairing an SDK can be executed by the repair platform. FIG3 is a flow chart of the method for repairing an SDK provided in an embodiment of the first aspect of the present application. As shown in FIG3, the method for repairing an SDK may include steps S201 to S204.
[0040] In step S201, SDK information, host information, and SDK exception information of different exception types are obtained.
[0041] SDK information includes basic SDK information. For example, SDK information may include the SDK version, but this is not limited here. SDK information may indicate the SDK version. Host information includes information about the host program embedded in the SDK. For example, host information may include the host program identifier, the channel identifier of the host program, and host program environment information, but this is not limited here. Host information may indicate the host program, and there is a corresponding relationship between the host program and the channel. Exception type refers to the SDK exception type, which can be set based on the scenario, requirements, and experience. For example, exception types may include but are not limited to data exception types, file input and output exception types, service unreachable exception types, and crash exception types. Each SDK exception message corresponds to a single SDK exception. Each SDK exception message includes information related to a single SDK exception. For example, each SDK exception message may include a description of the SDK exception, the channel identifier of the host program embedded in the SDK where the exception occurred, whether there was channel feedback on the SDK exception, the SDK launch time, the users affected by the SDK exception, the terminal types affected by the SDK exception, the service success rate of the SDK where the exception occurred, and the service importance of the SDK where the exception occurred, but this is not limited here.
[0042] In some examples, the SDK exception information includes the first SDK exception information and / or the second SDK exception information, the first SDK exception information is provided by the user terminal, and the second SDK is provided by the channel platform. Furthermore, the first SDK exception information may be provided by the SDK in the user terminal where the SDK exception occurs. The first SDK exception information can be obtained from the log of the SDK in the user terminal, and the second SDK exception information can be obtained from the log of the channel platform. The first SDK exception information may also include buried point information, so that the location, time, cause, etc. of the SDK exception can be traced back in the subsequent analysis process. The second SDK exception information may be the exception information, runtime (i.e., runtime) information, etc. entered by the technicians provided by the channel platform.
[0043] In step S202, the exception impact parameter corresponding to each exception type of the target SDK is obtained according to the SDK information, the host information and the SDK exception information of each exception type.
[0044] The target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information. The target SDK can be determined based on the host information and SDK information. Different target SDKs may have different SDK exception information corresponding to them, and the impact of SDK exceptions represented by different SDK exception information on the SDK program may also be different. The exception impact parameter can represent the degree of impact of the SDK exception on the SDK. The exception impact parameter corresponding to each exception type of the target SDK ensures the degree of impact of the SDK exception of that exception type on the target SDK. The exception impact parameters corresponding to different exception types of different target SDKs may be different, such as the exception impact parameters corresponding to different exception types of SDKs with different versions in different host programs may be different. The exception impact parameters corresponding to the same exception type of different target SDKs may be different, such as the exception impact parameters corresponding to the same exception type of SDKs with different versions in different host programs may be different, the exception impact parameters corresponding to the same exception type of SDKs with the same version in different host programs may be different, and the exception impact parameters corresponding to the same exception type of SDKs with different versions in the same host program may be different.
[0045] The abnormal impact parameter can be a parameter calculated using a standardized algorithm that can characterize the degree of impact of the SDK abnormality on the SDK, that is, the abnormal impact parameter is standardized and comparable. For example, the abnormal impact parameters corresponding to different abnormal types of different target SDKs are comparable. In some examples, corresponding calculated values and weights can be set in advance for at least part of the SDK abnormality information to establish a unified standard, so that the abnormal impact parameters corresponding to different abnormal types under different target SDKs calculated using a weighted algorithm are standardized and comparable.
[0046] In step S203, a target SDK repair strategy is obtained based on the exception impact parameters corresponding to each exception type of the target SDK and preset exception classification processing rules.
[0047] The exception classification processing rules may include a correspondence between the exception type, exception impact parameter, exception level, and SDK repair strategy. The target SDK repair strategy includes the SDK repair strategy for the exception level corresponding to the exception impact parameter in the exception classification processing rules. That is, based on the exception impact parameter corresponding to each exception type of the target SDK, the exception level and SDK repair strategy corresponding to the exception type and exception impact parameter of the target SDK can be determined in the exception classification processing rules. The determined SDK repair strategy can then be used as the target SDK repair strategy.
[0048] The exception level reflects the severity of the exception, and different exception levels correspond to different target SDK repair strategies. The higher the severity of the exception, the more advanced the SDK repair strategy required to fix it. Similarly, for lower severity exceptions, a lower-level SDK repair strategy can be used to fix the exception. In other words, higher severity exception levels correspond to more advanced SDK repair strategies.
[0049] Exception hierarchical processing rules can record multiple SDK repair strategies. Different SDK repair strategies have different repair levels and can repair SDK exceptions of varying severity. Exception hierarchical processing rules can be used to select the appropriate SDK repair strategy for the target SDK. For example, suppose there are two SDKs, SDK1 and SDK2. Based on the exception types and exception impact parameters of the two SDKs, it is determined that SDK1's exception level is level 3 and SDK2's exception level is level 1. Level 3 exceptions are more severe than level 1 exceptions. Therefore, SDK1 is assigned an SDK repair strategy with a higher level of repair, while SDK2 is assigned an SDK repair strategy with a lower level of repair.
[0050] In some examples, the target SDK repair strategy may include, but is not limited to, one or more of the following: a first file, a second file, and a third file.
[0051] The first file includes a cache data clearing instruction, which is used to instruct the clearing of data in at least one cache folder corresponding to the target SDK. The cache data clearing instruction can also be subdivided into sub-instructions of different levels according to the relative degree of repair. For example, the cache data clearing instruction includes a first sub-instruction and a second sub-instruction. The first sub-instruction can be used to instruct the clearing of data in a specific cache folder corresponding to the target SDK, and the second sub-instruction can be used to instruct the clearing of data in all cache folders corresponding to the target SDK. Compared with the first sub-instruction, the second sub-instruction has a higher repair level. The cache data clearing instruction can be implemented through an instruction statement, and the type of instruction statement is not limited here.
[0052] The second file includes an exception source blocking instruction. The exception source blocking instruction is used to instruct to set the switch state of at least one business function and / or sub-business function of the target SDK to the closed state. The SDK can have multiple business functions, and each business function can also have at least one sub-business function. The business functions and sub-business functions can be in a tree structure. Correspondingly, the switch state of the business function and the switch state of the sub-business function can also be in a tree structure. Each business function and sub-business function can be turned on or off by setting the switch state.
[0053] The exception source blocking instruction can be divided into different exception source blocking instructions according to the relative level of repair. Different exception levels can be obtained for different exception types and exception impact parameters. Different exception source blocking instructions can be assigned to different exception levels. Different exception source blocking instructions indicate different closed business functions and / or sub-business functions. For example, if the exception level is level two, the exception source blocking instruction in the second file indicates that the switch status of business function 1 and business function 2 in the target SDK are both set to the closed state; if the exception level is level one, the exception source blocking instruction in the second file indicates that the switch status of business function 1 in the target SDK is set to the closed state. In some examples, the content of the switch status setting of the business function by the exception source blocking instruction can be implemented as a character string, such as "111110" means that the switch status of the sixth business function among the six business functions is set to the closed state. The exception source blocking instruction can perform configuration actions when the business function and / or sub-business function is initialized.
[0054] The third file includes a patch file, which is used to upgrade and repair the target SDK. The patch file contains the difference between the files in the SDK before and after the repair. The patch file can repair the SDK in the required areas. In some examples, the third file can be an .apk file.
[0055] In some examples, the target SDK repair strategy includes a third file. The repair platform can generate a patch file. Specifically, the repair platform can obtain the SDK archive file before and after the repair of the target SDK; obtain a first class file and a second class file, where the first class file includes the class files in the SDK archive file before and the second class file includes the class files in the SDK archive file after the repair; use a comparison algorithm to compare the first and second class files to obtain a third class file, where the third class file includes the class files where there are differences between the second and first class files; and convert the third class file into a patch file.
[0056] The SDK archive file before repair and the SDK archive file after repair can be an arr file or a jar file. If the SDK archive file before repair and the SDK archive file after repair are arr files, the arr file can be decompressed to extract the jar file. The jar file includes class files and manifest files. The jar file can be decompressed to extract the class files, that is, the first class file and the second class file are obtained. The third class file can be compressed into a jar file, and the third class file can be converted into a dex file through the Gradle transform application program interface (Application Program Interface, API). The dex file is the patch file. The dex file is readable, that is, when the dex file is scanned, readable statements, classes, etc. can be obtained from it, which can facilitate the review by the auditor, and there will be no situation where it cannot be restored to a readable statement and cannot be reviewed.
[0057] The third file can implement hot fixes for the SDK. For SDKs of different versions embedded in different host programs, the patch files in the third file can be different.
[0058] The first, second, and third files described above may also be combined with one another. In some examples, the target SDK repair policy resulting from combining two or more files may have a higher degree of repair than the target SDK repair policy corresponding to any one of the two or more files. For example, a target SDK repair policy that includes both the first and second files may have a higher degree of repair than a target SDK repair policy that includes only the first file.
[0059] In step S204, the target SDK repair policy is issued to the user terminal, so that the user terminal executes the target SDK repair policy to repair the target SDK.
[0060] Specifically, the repair platform can issue the target SDK repair policy to the user terminal where the target SDK is located. This does not limit the number of user terminals where the target SDK is located. The repair platform can issue the target SDK repair policy to all user terminals where the target SDK is located, or it can issue the policy in batches using a grayscale release method. It can also issue the policy to specific user terminals where the target SDK is located. The target SDK repair policy can be sent to the user terminal in a file or other form, and the form of the target SDK repair policy is not limited here.
[0061] After the user terminal obtains the target SDK repair policy, it executes the target SDK repair policy to repair the target SDK.
[0062] In some examples, the user terminal can establish a repair process specifically for executing the target SDK repair policy. That is, the target SDK repair policy is executed by the repair process. This repair process is independent of the target SDK process. Even if the target SDK process is interrupted, the repair process can record the repair progress and is not affected by the interruption of the target SDK process. When the target SDK process is restarted, the repair process can continue according to the repair progress without having to restart the repair process, thereby improving the efficiency of SDK repair.
[0063] In an embodiment of the present application, the repair platform can obtain an abnormal impact parameter that characterizes the impact of the abnormal type on the SDK based on the SDK information, host information and the collected SDK abnormal information of different abnormal types, thereby obtaining the SDK repair strategy corresponding to the abnormal level based on the abnormal impact parameter corresponding to each abnormal type and the preset abnormal classification processing rules and sending it to the user terminal. The user terminal can execute the SDK repair strategy corresponding to the abnormal level to repair the SDK. Different host information corresponds to different host programs, different host programs correspond to different channel parties, and different versions of SDK also correspond to different SDK information. Different versions of SDK embedded in the host programs of different channel parties generate different SDK abnormal information. Through the collected SDK abnormal information, the SDK repair strategy corresponding to the abnormal level of each version of the SDK embedded in the host program of each channel party can be obtained, that is, the SDK repair strategy for the different versions of SDK embedded in the host programs of different channel parties can be automatically assigned to meet the repair needs of the SDKs of different channel parties.
[0064] In some embodiments, the exception impact parameter corresponding to each exception type can be determined based on the impact of each exception type on the SDK and the number of SDK exceptions of each exception type that occur. The target SDK repair strategy can also be determined based on the exception type with the largest value of the exception impact parameter, the exception impact parameter of the exception type, and the exception classification processing rules. Figure 4 is a flow chart of the SDK repair method provided by another embodiment of the first aspect of the present application. The difference between Figure 4 and Figure 3 is that step S202 in Figure 3 can be specifically refined into steps S2021 to S2024 in Figure 4, and step S203 in Figure 3 can be specifically refined into steps S2031 and S2032 in Figure 4.
[0065] In step S2021, the target SDK is determined according to the SDK information and the host information, and feature information in the SDK exception information of each exception type of the target SDK and the weight of the feature information are obtained.
[0066] The repair platform will obtain a large amount of SDK information, host information and SDK exception information. In order to provide adaptive SDK repair strategies for different versions of SDKs embedded in different host programs, for a version of SDK embedded in a host program, it is necessary to obtain an SDK repair strategy adapted to the SDK based on the SDK exception information related to the SDK.
[0067] According to the SDK information and host information, the SDK version and the host program in which the SDK is embedded can be determined, and the target SDK is determined. SDK information, host information and SDK exception information are obtained in groups, that is, when an SDK exception occurs, SDK information, host information and SDK exception information can be provided accordingly. To determine the target SDK, the SDK exception information of each exception type of the target SDK can be summarized. In addition to the exception description information, the SDK exception information can also include feature information, which can characterize at least some of the features of the SDK exception. In some examples, the feature information may include but is not limited to the channel party identifier of the host program in which the SDK where the exception occurs is embedded, whether there is channel party feedback for the SDK exception, the SDK online time, the users affected by the SDK exception, the terminal type affected by the SDK exception, the business success rate of the SDK where the exception occurs, the business importance of the SDK where the exception occurs, etc.
[0068] Weights may be pre-set for feature information. Different types of feature information may have different weights. The weights may be set based on application scenarios, requirements, experience, etc., and are not limited here. The sum of the weights of the various types of feature information may be 1.
[0069] In step S2022, the abnormality impact factor corresponding to each abnormality type of the target SDK is calculated based on the feature information and the weight of the feature information.
[0070] For SDK exception information of an exception type, the product of the value of each type of feature information in the SDK exception information of the exception type and the respective weights can be calculated first, and the sum of the products can be determined as the exception impact factor corresponding to the exception type of the target SDK. In some examples, the value of the feature information can be the original value of the feature information. In other examples, the value of the feature information can also be the value obtained after processing the original value of the feature information, such as the value after normalization calculation or standardization calculation, or according to the preset classification rules, according to the category to which the original value of each type of feature information belongs, the set value under the category is determined as the value of the feature information.
[0071] For example, the characteristic information includes the channel party identifier of the host program in which the SDK where the exception occurs is embedded, whether there is any feedback from the channel party for the exception that occurred in the SDK, the business success rate of the SDK where the exception occurred, and the business importance of the SDK where the exception occurred. For a certain exception type of the target SDK, the channel party identifier of the host program in which the SDK where the exception occurs is AA, the SDK has feedback from the channel party, the business success rate of the SDK where the exception occurred is 85%, and the business importance of the SDK where the exception occurred is medium. The preset classification rules can be shown in Tables 1 to 4 below. Table 1 represents the classification rules for the original value of the channel party identifier of the host program in which the SDK where the exception occurs is embedded, Table 2 represents the classification rules for the original value of whether there is any feedback from the channel party for the exception that occurred in the SDK, Table 3 represents the classification rules for the business success rate of the SDK where the exception occurs, and Table 4 represents the classification rules for the business importance of the SDK where the exception occurs.
[0072] Table 1
[0073] Table 2
[0074] Table 3
[0075] Table 4
[0076] If the weights corresponding to the channel party identifier of the host program in which the SDK with the exception is embedded, whether there is feedback from the channel party for the SDK exception, the business success rate of the SDK with the exception, and the business importance of the SDK with the exception are d1, d2, d3, and d4 respectively, then according to Table 1 and Table 4 above, the exception impact factor α corresponding to the exception type of the target SDK can be obtained according to the following formula (1): α=c1×d1+c3×d2+c7×d3+c9×d4 (1)
[0077] The exception impact factor corresponding to an exception type can represent the impact of the SDK exception of the exception type on the SDK. This impact reflects the impact of the exception type on the SDK in the dimension of feature information.
[0078] In step S2023, the output ratio corresponding to each exception type of the target SDK is calculated according to the number of SDK exception information of each exception type of the target SDK and the total number of SDK exception information.
[0079] The output ratio of an exception type of the target SDK can represent the proportion of the exception type in all exception types of the target SDK. The output ratio of an exception type of the target SDK can be the ratio of the number of SDK exception information of the exception type of the target SDK to the number of SDK exception information of all exception types of the target SDK. For example, the target SDK has a total of n exception types of exception information, and the number of exception information of n exception types is b1 to b2. n , then the output ratio corresponding to the i-th abnormal type can be obtained according to the following formula (2):
[0080] Among them, β i is the output ratio corresponding to the i-th abnormal type; b1 is the number of abnormal information of the first abnormal type; b i is the number of abnormal information of the i-th abnormal type, 1≤i≤n; b n The number of exception information for the nth exception type.
[0081] In step S2024, the abnormal impact parameter corresponding to each abnormal type of the target SDK is calculated using the abnormal impact factor and output ratio corresponding to each abnormal type of the target SDK.
[0082] In addition to reflecting the impact of the abnormal type on the SDK in the dimension of feature information, the abnormal impact parameter can also reflect the impact of the abnormal type on the SDK in the dimension of the proportion of all abnormal types in the SDK. The product of the abnormal impact factor corresponding to an abnormal type of the target SDK and the output ratio corresponding to the abnormal type can be used as the abnormal impact parameter corresponding to the abnormal type of the target SDK. For example, the abnormal impact parameter corresponding to the i-th abnormal type can be obtained according to the following formula (3): E(i) = α i ×β i (3)
[0083] Among them, E(i) is the abnormal impact parameter corresponding to the i-th abnormal type; α i is the abnormal impact factor corresponding to the i-th abnormal type; β i is the output ratio corresponding to the i-th abnormal type.
[0084] In step S2031, a target abnormality type is determined according to the abnormality impact parameters corresponding to each abnormality type.
[0085] The target exception type is the exception type corresponding to the exception impact parameter with the largest value. For example, if the target SDK corresponds to SDK exception information with four exception types, the values of the exception impact parameters corresponding to the first exception type to the fourth exception type are f1, f2, f3, and f4, respectively. If f2 < f4 < f1 < f3, the target exception type is the third exception type.
[0086] In step S2032, according to the exception classification processing rules, the exception level corresponding to the target exception type and the exception impact parameter of the target exception type is determined, and the target SDK repair strategy is determined according to the exception level.
[0087] The exception impact parameter corresponding to each exception type of the target SDK ensures the degree of impact of the SDK exception of that exception type on the target SDK. The exception type corresponding to the exception impact parameter with the largest value has the greatest impact on the target SDK among all exception types. The target exception type and the exception impact parameter corresponding to the target exception type can reflect which exception type of SDK exception mainly causes the impact on the target SDK, as well as the degree of impact of the SDK exception of that exception type on the target SDK. Different target exception types and different values of exception impact parameters may correspond to different exception levels in the exception classification processing rules, and the corresponding target SDK repair strategies may also be different.
[0088] For example, assuming that the exception types include data exception type, file input / output exception type, service unreachable exception type, and crash exception type, if the target exception type is a data exception type or a file input / output exception type, the exception level may be a minor level, and the corresponding target SDK repair strategy may include the first file in the above embodiment; if the target exception type is a service unreachable exception type, the exception level may be a medium level, and the corresponding target SDK repair strategy may include the second file in the above embodiment; if the target exception type is a crash exception type, the exception level may be a severe level, and the corresponding target SDK repair strategy may include the third file in the above embodiment.
[0089] In some embodiments, to ensure that the target SDK repair policy is delivered to the user terminal and is only effective for the target SDK, a signature that reflects the host program, i.e., the channel party, may be added to the target SDK repair policy. Specifically, the target SDK repair policy may also include a first signature file. The repair platform may generate a first signature based on the host information, and, based on the first signature, generate a first signature file, where the first signature file includes the first signature. The signature algorithm used to generate the first signature is not limited herein. For example, the first signature may be generated using the SM3 signature algorithm based on the host information.
[0090] After the user terminal obtains the target SDK repair policy, it can verify the first signature to determine the target SDK targeted by the target SDK repair policy, and then execute the target SDK repair policy to repair the target SDK. The host program can be called to verify the first signature. If the verification is successful, it indicates that the host program has the target SDK and the target SDK embedded in the host program can be repaired. If the verification fails, it indicates that the host program does not have the target SDK and the SDK embedded in the host program will not be repaired.
[0091] In some embodiments, after the repair platform obtains the target SDK repair strategy, the repair platform may send the target SDK repair strategy to the channel platform for review. Only after the channel platform passes the review will the target SDK repair strategy be sent to the user terminal to ensure the security of the target SDK repair strategy. Figure 5 is a flowchart of the SDK repair method provided by another embodiment of the first aspect of the present application. The difference between Figure 5 and Figure 3 is that the SDK repair method shown in Figure 5 can also include steps S205 and S206, and step S204 in Figure 3 can be specifically refined into step S2041 in Figure 5.
[0092] In step S205, the target SDK repair strategy is sent to the channel platform.
[0093] The channel platform receives the target SDK repair policy, scans the target SDK repair policy, obtains the content of the target SDK repair policy, and then reviews the target SDK repair policy.
[0094] If the target SDK repair policy passes review, the channel platform authorizes the target SDK repair policy, generates a second signature based on the host information, and generates a second signature file based on the second signature. The second signature file includes the second signature. The channel platform adds the second signature file to the target SDK repair policy and provides feedback to the repair platform. In some examples, the channel platform may use its own signature algorithm to sign the hash value of the target SDK repair policy using the host information to obtain the second signature.
[0095] If the target SDK repair policy fails the review, the channel platform will not authorize the target SDK repair policy. The channel platform may send a notification message to the repair platform to inform the repair platform of the review failure. If the channel platform scans and finds that the target SDK repair policy is not authorized, the repair platform shall not issue the target SDK repair policy.
[0096] In step S206, the target SDK repair strategy fed back by the channel platform is received.
[0097] The feedback target SDK repair policy includes a second signature file. The second signature file includes a second signature. The second signature is generated by the channel platform based on the host information after scanning the target SDK repair policy and authorizing it.
[0098] In step S2041, the target SDK repair strategy fed back by the channel platform is delivered to the user terminal.
[0099] The repair platform can interact with the channel platform to enable the channel platform to review the target SDK repair policy. Only after the channel platform's review is the repair platform allowed to issue the target SDK repair policy to the user terminal, ensuring the security of the target SDK repair policy. In addition, the channel platform can use a second signature to identify the channel party to which the target SDK's host program belongs. Once the user terminal obtains the target SDK repair policy, it can verify the second signature using the host program's host information. The target SDK repair policy will only take effect on the target SDK in the host program that has passed the verification, ensuring the targeted effectiveness of the target SDK repair policy.
[0100] A second aspect of the present application provides a method for repairing an SDK, which can be applied to a user terminal, i.e., the method for repairing an SDK can be executed by the user terminal. Figure 6 is a flow chart of the method for repairing an SDK provided in an embodiment of the second aspect of the present application. As shown in Figure 6, the method for repairing an SDK may include steps S301 and S302.
[0101] In step S301, software development kit SDK information, host information and SDK exception information of different exception types are provided to the repair platform, so that the repair platform obtains the target SDK repair strategy based on the exception impact parameters corresponding to each exception type of the target SDK and the preset exception classification processing rules.
[0102] The target SDK repair strategy includes the SDK repair strategy for the exception level corresponding to the exception impact parameter in the exception classification processing rules. The target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information. The exception impact parameter corresponding to each exception type of the target SDK is obtained based on the SDK information, host information, and SDK exception information for each exception type.
[0103] In step S302, a target SDK repair strategy is obtained from the repair platform, and the target SDK repair strategy is executed to repair the target SDK.
[0104] In some examples, when the target SDK is initialized, it can establish a repair process and send host information, SDK information, user information, etc. to the repair platform. The repair platform can then search for a target SDK repair policy that corresponds to the host and SDK information and issue the target SDK repair policy. The user terminal downloads the target SDK repair policy from the repair platform and executes it through the repair process to repair the target SDK.
[0105] In some examples, the target SDK repair strategy includes, but is not limited to, one or more of the following: a first file, a second file, and a third file.
[0106] The first file includes a cache data clearing instruction, which is used to instruct the target SDK to clear data in at least one cache folder corresponding to the target SDK. If the target SDK repair strategy includes the first file, the user terminal can clear the dirty data in the cache folder of the target SDK according to the cache data clearing instruction.
[0107] The second file includes an exception source blocking instruction, which is used to instruct the target SDK to set the switch state of at least one service function and / or sub-service function to an off state. If the target SDK repair policy includes the second file, the user terminal may set the switch state of the service function and / or sub-service function indicated by the exception source blocking instruction to an off state in accordance with the exception source blocking instruction.
[0108] The third file includes a patch file, which is used to upgrade and repair the target SDK. If the target SDK repair strategy includes the third file, the user terminal can extract the patch file in the third file and load the repaired class in a class loading manner to complete the repair of the target SDK.
[0109] In some examples, the target SDK repair strategy includes a third file, the patch file is converted from a third class file, the third class file includes a class file in which there are differences between the second class file and the first class file, the first class file includes the class file in the SDK archive file of the target SDK before repair, and the second class file includes the class file in the SDK archive file of the target SDK after repair.
[0110] The specific contents of the first file, the second file and the third file can be found in the relevant descriptions in the above embodiments and will not be repeated here.
[0111] The specific contents of the above steps S301 and S302 can be found in the relevant descriptions in the above embodiments, which will not be repeated here.
[0112] In an embodiment of the present application, the repair platform can obtain an abnormal impact parameter that characterizes the impact of the abnormal type on the SDK based on the SDK information, host information and the collected SDK abnormal information of different abnormal types, thereby obtaining the SDK repair strategy corresponding to the abnormal level based on the abnormal impact parameter corresponding to each abnormal type and the preset abnormal classification processing rules and sending it to the user terminal. The user terminal can execute the SDK repair strategy corresponding to the abnormal level to repair the SDK. Different host information corresponds to different host programs, different host programs correspond to different channel parties, and different versions of SDK also correspond to different SDK information. Different versions of SDK embedded in the host programs of different channel parties generate different SDK abnormal information. Through the collected SDK abnormal information, the SDK repair strategy corresponding to the abnormal level of each version of the SDK embedded in the host program of each channel party can be obtained, that is, the SDK repair strategy for the different versions of SDK embedded in the host programs of different channel parties can be automatically assigned to meet the repair needs of the SDKs of different channel parties.
[0113] In some embodiments, the abnormal impact parameter corresponding to each type of abnormality of the target SDK is calculated using the abnormal impact factor and output ratio corresponding to each abnormality type of the target SDK. The output ratio corresponding to each abnormality type of the target SDK is calculated based on the number of SDK abnormality information of each abnormality type of the target SDK and the total number of SDK abnormality information. The abnormal impact factor corresponding to each abnormality type of the target SDK is calculated based on the feature information in the SDK abnormality information of each abnormality type of the target SDK, as well as the weight of the feature information. For the specific content of this part, please refer to the relevant description in the above embodiment and will not be repeated here.
[0114] In some embodiments, the exception level corresponding to the target SDK repair strategy is determined based on the exception classification processing rules, the target exception type, and the exception impact parameter of the target exception type, with the target exception type being the exception type corresponding to the exception impact parameter with the largest value. The details of this section can be found in the relevant descriptions in the above embodiments and will not be repeated here.
[0115] In some embodiments, the target SDK repair strategy also includes a first signature file, which includes a first signature. The first signature is generated by the repair platform based on the host information. For specific content, please refer to the relevant description in the above embodiments and will not be repeated here.
[0116] After obtaining the target SDK repair policy from the repair platform, the user terminal can call the host program indicated by the host information to verify the first signature. If the host program indicated by the host information successfully verifies the first signature, the target SDK repair policy is executed to repair the target SDK. The user terminal can agree in advance with the repair platform on the verification algorithm for the first signature, which is not limited here. The repair platform can use the agreed private key to generate the first signature, and the user terminal can use the agreed public key to verify the first signature. On the one hand, it can verify the integrity of the target SDK repair policy and whether it has been tampered with. On the other hand, it can also verify the uniqueness of the target SDK repair policy to the host program, that is, the channel party, thereby ensuring the content security of the target SDK repair policy and the access security of the channel party.
[0117] In some embodiments, the target SDK repair strategy also includes a second signature file, and the second signature file includes a second signature. The second signature is generated by the channel platform based on the host information after scanning the target SDK repair strategy and determining authorization. For specific content, please refer to the relevant descriptions in the above embodiments, which will not be repeated here. Figure 7 is a flow chart of the SDK repair method provided by another embodiment of the second aspect of the present application. The difference between Figure 7 and Figure 6 is that step S302 in Figure 6 can be specifically refined into steps S3021 to S3023 in Figure 7.
[0118] In step S3021, the target SDK repair strategy is obtained from the repair platform.
[0119] In step S3022, the host program indicated by the host information is called to verify the second signature.
[0120] The verification algorithm for the second signature can be pre-agreed upon between the user terminal and the channel platform and is not limited herein. The channel platform can generate the second signature using the agreed-upon private key, and the user terminal can verify the second signature using the agreed-upon public key. This can firstly verify the integrity of the target SDK repair policy and whether it has been tampered with, secondly verify the uniqueness of the target SDK repair policy to the host program (i.e., the channel party), and thirdly verify the channel party's approval of the target SDK repair policy, thereby ensuring the content security of the target SDK repair policy and the access security of the channel party.
[0121] In step S3023, when the host program indicated by the host information successfully verifies the second signature, the target SDK repair strategy is executed to repair the target SDK.
[0122] In some embodiments, the user terminal can establish a repair process, obtain the target SDK repair strategy from the repair platform through the repair process, and execute the target SDK repair strategy through the repair process to repair the target SDK. The repair process is independent of the target SDK process, which can minimize the impact of the target SDK process on the repair of the SDK and improve the repair efficiency of the SDK. Figure 8 is a flowchart of the SDK repair method provided by another embodiment of the second aspect of the present application. The difference between Figure 8 and Figure 6 is that step S302 in Figure 6 can be specifically refined into steps S3024 to S3026 in Figure 8.
[0123] In step S3024, the process of the target SDK is monitored through the repair process.
[0124] In step S3025, before the target SDK is repaired, if the process of monitoring the target SDK is terminated and the target SDK repair policy has not been downloaded, the target SDK repair policy will continue to be downloaded through the repair process until the target SDK repair policy is downloaded and then the repair process is interrupted. When the process of monitoring the target SDK is started again, the target SDK repair policy will be executed through the repair process to repair the target SDK.
[0125] After downloading the target SDK repair strategy, the content in the target SDK repair strategy that mainly plays a repair role can be encrypted and saved, for example, cache data clearing instructions, abnormal source blocking instructions, patch files, etc. can be encrypted and saved.
[0126] If the repair process is interrupted for other reasons during the download of the target SDK repair strategy, the breakpoint resume function provided by the operating system layer of the user terminal can be used to ensure that the user terminal can obtain the complete target SDK repair strategy.
[0127] In step S3026, before the target SDK is repaired, if it is detected that the target SDK process is terminated and the target SDK repair strategy has begun to be executed, the repair progress of the target SDK is recorded through the repair process. When it is detected that the target SDK process is started again, the target SDK is continued to be repaired based on the repair progress through the repair process.
[0128] From the above, it can be concluded that whether the host program or the target SDK process is alive or not will not affect the user terminal's acquisition of the target SDK repair strategy, which can ensure the effective execution of the target SDK repair strategy and improve the SDK repair rate.
[0129] For ease of understanding, the SDK repair method is explained below through a logical diagram of the interaction between the user terminal, the repair platform and the channel platform. Figure 9 is a logical diagram of an example of the SDK repair method provided in an embodiment of the present application. As shown in Figure 9, the user terminal 41 has a host program 411 and an SDK 412, the SDK 412 is embedded in the host program 411, and the user terminal 41 can establish a repair process 413. The repair platform 42 has a log analysis function 421, a policy configuration function 422 and a file management function 423. The channel platform 43 has a channel party log provision function 431, a policy content review function 432 and a policy signature function 433.
[0130] The repair platform 42 can obtain the SDK log from the SDK 412, which may include host information, SDK information, and SDK exception information. The repair platform 42 can also obtain the channel party's log from the channel platform 43. The channel party log providing function 431 of the channel platform 43 can provide the channel party's log. The log analysis function 421 in the repair platform 42 can extract host information, SDK information, and SDK exception information from the log. The policy configuration function 422 can obtain the host information, SDK information, and SDK exception information from the log analysis function 421, determine the exception level based on the host information, SDK information, and SDK exception information, and determine the target SDK repair policy corresponding to the exception level. The file management function 423 manages various SDK repair policies. The policy configuration function 422 can obtain the target SDK repair policy from the file management function 423. The repair platform 42 sends the target SDK repair policy to the channel platform 43. Channel platform 43 audits the target SDK repair policy through policy content review function 432. If the audit passes, it signs the target SDK repair policy through policy signature function 433 and feeds the signed target SDK repair policy back to repair platform 42. SDK 412 can send host information and SDK information to the repair platform to trigger repair platform 42 to provide the target SDK repair policy to user terminal 41. SDK 412 can initiate repair process 413, which downloads the target SDK repair policy from repair platform 42. User terminal 41 verifies the signature in the target SDK repair policy through repair process 413. If the signature passes verification, the target SDK repair policy is executed to repair SDK 412.
[0131] It should be noted that the acquisition, storage, use, and processing of information and data in this application have been authorized by users or relevant institutions and comply with relevant provisions of national laws and regulations.
[0132] A third aspect of the present application provides an SDK repair device. Figure 10 is a schematic diagram of the structure of the SDK repair device provided in an embodiment of the third aspect of the present application. As shown in Figure 10, the SDK repair device 500 may include an acquisition module 501, a calculation module 502, a policy configuration module 503, and a delivery module 504.
[0133] The acquisition module 501 may be used to acquire SDK information, host information, and SDK exception information of different exception types.
[0134] The calculation module 502 may be configured to obtain an exception impact parameter corresponding to each exception type of the target SDK according to the SDK information, the host information, and the SDK exception information of each exception type.
[0135] The target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information.
[0136] The policy configuration module 503 may be used to obtain a target SDK repair policy based on the exception impact parameters corresponding to each exception type of the target SDK and preset exception classification processing rules.
[0137] In some examples, the target SDK repair strategy includes one or more of the following:
[0138] A first file, the first file including a cache data clearing instruction, the cache data clearing instruction being used to instruct to clear data in at least one cache folder corresponding to the target SDK;
[0139] A second file, the second file including an abnormal source blocking instruction, the abnormal source blocking instruction being used to instruct to set the switch state of at least one business function and / or sub-business function of the target SDK to a closed state;
[0140] The third file includes a patch file, which is used to upgrade and repair the target SDK.
[0141] The target SDK repair strategy includes the SDK repair strategy of the exception level corresponding to the exception impact parameter in the exception classification processing rule.
[0142] The sending module is used to send the target SDK repair strategy to the user terminal, so that the user terminal executes the target SDK repair strategy to repair the target SDK.
[0143] In some examples, the target SDK repair policy is executed by a repair process established by the user terminal, and the repair process is independent of the target SDK process.
[0144] In an embodiment of the present application, the repair platform can obtain an abnormal impact parameter that characterizes the impact of the abnormal type on the SDK based on the SDK information, host information and the collected SDK abnormal information of different abnormal types, thereby obtaining the SDK repair strategy corresponding to the abnormal level based on the abnormal impact parameter corresponding to each abnormal type and the preset abnormal classification processing rules and sending it to the user terminal. The user terminal can execute the SDK repair strategy corresponding to the abnormal level to repair the SDK. Different host information corresponds to different host programs, different host programs correspond to different channel parties, and different versions of SDK also correspond to different SDK information. Different versions of SDK embedded in the host programs of different channel parties generate different SDK abnormal information. Through the collected SDK abnormal information, the SDK repair strategy corresponding to the abnormal level of each version of the SDK embedded in the host program of each channel party can be obtained, that is, the SDK repair strategy for the different versions of SDK embedded in the host programs of different channel parties can be automatically assigned to meet the repair needs of the SDKs of different channel parties.
[0145] In some embodiments, the calculation module 502 can be used to: determine the target SDK based on the SDK information and the host information, and obtain the characteristic information in the SDK exception information of each exception type of the target SDK, as well as the weight of the characteristic information; calculate the abnormal impact factor corresponding to each abnormal type of the target SDK based on the characteristic information and the weight of the characteristic information; calculate the output ratio corresponding to each abnormal type of the target SDK based on the number of SDK exception information of each abnormal type of the target SDK and the total number of SDK exception information; use the abnormal impact factor and output ratio corresponding to each abnormal type of the target SDK to calculate the abnormal impact parameter corresponding to each abnormal type of the target SDK.
[0146] In some embodiments, the policy configuration module 503 can be used to: determine the target exception type based on the exception impact parameters corresponding to each exception type, where the target exception type is the exception type corresponding to the exception impact parameter with the largest value; determine the exception level corresponding to the target exception type and the exception impact parameters of the target exception type based on the exception classification processing rules, and determine the target SDK repair strategy based on the exception level.
[0147] In some embodiments, the target SDK repair strategy includes a third file. The SDK repair device 500 may further include a patch generation module.
[0148] The patch generation module can be used to: obtain the SDK archive file before repair and the SDK archive file after repair of the target SDK; obtain the first class file and the second class file, the first class file includes the class file in the SDK archive file before repair, and the second class file includes the class file in the SDK archive file after repair; use the comparison algorithm to compare the first class file and the second class file to obtain a third class file, the third class file includes the class files where there are differences between the second class file and the first class file; convert the third class file into a patch file.
[0149] In some embodiments, the target SDK repair strategy also includes a first signature file. The SDK repair device may also include a first signature module. The first signature module may be configured to: generate a first signature based on the host information; and generate a first signature file based on the first signature, the first signature file including the first signature.
[0150] In some embodiments, the repair device of the SDK may further include a receiving module.
[0151] The sending module 504 may also be used to send the target SDK repair strategy to the channel platform.
[0152] The receiving module can be used to: receive the target SDK repair strategy fed back by the channel platform, the fed back target SDK repair strategy includes a second signature file, the second signature file includes a second signature, and the second signature is generated by the channel platform based on the host information after scanning the target SDK repair strategy and authorizing it.
[0153] The sending module 504 may be used to send the target SDK repair strategy fed back by the channel platform to the user terminal.
[0154] A fourth aspect of the present application provides a user terminal. Figure 11 is a schematic diagram of the structure of a user terminal provided in an embodiment of the fourth aspect of the present application. As shown in Figure 11, the user terminal 600 may include a sending module 601, a receiving module 602, and an execution module 603.
[0155] The sending module 601 can be used to provide SDK information, host information and SDK exception information of different exception types to the repair platform, so that the repair platform can obtain the target SDK repair strategy based on the exception impact parameters corresponding to each exception type of the target SDK and the preset exception classification processing rules.
[0156] The target SDK repair strategy includes the SDK repair strategy for the exception level corresponding to the exception impact parameter in the exception classification processing rules. The target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information. The exception impact parameter corresponding to each exception type of the target SDK is obtained based on the SDK information, host information, and SDK exception information for each exception type.
[0157] The receiving module 602 may be configured to obtain a target SDK repair strategy from the repair platform.
[0158] In some examples, the target SDK repair strategy includes one or more of the following:
[0159] A first file, the first file including a cache data clearing instruction, the cache data clearing instruction being used to instruct to clear data in at least one cache folder corresponding to the target SDK;
[0160] A second file, the second file including an abnormal source blocking instruction, the abnormal source blocking instruction being used to instruct to set the switch state of at least one business function and / or sub-business function of the target SDK to a closed state;
[0161] The third file includes a patch file, which is used to upgrade and repair the target SDK.
[0162] In some examples, the target SDK repair strategy includes a third file, the patch file is converted from a third class file, the third class file includes a class file in which there are differences between the second class file and the first class file, the first class file includes the class file in the SDK archive file of the target SDK before repair, and the second class file includes the class file in the SDK archive file of the target SDK after repair.
[0163] The execution module 603 may be configured to execute a target SDK repair strategy to repair the target SDK.
[0164] In an embodiment of the present application, the repair platform can obtain an abnormal impact parameter that characterizes the impact of the abnormal type on the SDK based on the SDK information, host information and the collected SDK abnormal information of different abnormal types, thereby obtaining the SDK repair strategy corresponding to the abnormal level based on the abnormal impact parameter corresponding to each abnormal type and the preset abnormal classification processing rules and sending it to the user terminal. The user terminal can execute the SDK repair strategy corresponding to the abnormal level to repair the SDK. Different host information corresponds to different host programs, different host programs correspond to different channel parties, and different versions of SDK also correspond to different SDK information. Different versions of SDK embedded in the host programs of different channel parties generate different SDK abnormal information. Through the collected SDK abnormal information, the SDK repair strategy corresponding to the abnormal level of each version of the SDK embedded in the host program of each channel party can be obtained, that is, the SDK repair strategy for the different versions of SDK embedded in the host programs of different channel parties can be automatically assigned to meet the repair needs of the SDKs of different channel parties.
[0165] In some embodiments, the exception impact parameter corresponding to each type of exception of the target SDK is calculated using the exception impact factor and output ratio corresponding to each exception type of the target SDK. The output ratio corresponding to each exception type of the target SDK is calculated based on the number of SDK exception information of each exception type of the target SDK and the total number of SDK exception information. The exception impact factor corresponding to each exception type of the target SDK is calculated based on the feature information in the SDK exception information of each exception type of the target SDK and the weight of the feature information.
[0166] In some embodiments, the exception level corresponding to the target SDK repair strategy is obtained based on the exception classification processing rule, the target exception type, and the exception impact parameter of the target exception type. The target exception type is the exception type corresponding to the exception impact parameter with the largest value.
[0167] In some embodiments, the target SDK repair strategy further includes a first signature file, the first signature file includes a first signature, and the first signature is generated by the repair platform according to the host information.
[0168] The execution module 603 may also be configured to call the host program indicated by the host information to verify the first signature, and execute the target SDK repair strategy to repair the target SDK if the host program indicated by the host information successfully verifies the first signature.
[0169] In some embodiments, the target SDK repair policy further includes a second signature file, the second signature file includes a second signature, and the second signature is generated by the channel platform according to the host information after scanning the target SDK repair policy and determining authorization.
[0170] The execution module 603 may also be configured to call the host program indicated by the host information to verify the second signature, and execute the target SDK repair strategy to repair the target SDK if the host program indicated by the host information successfully verifies the second signature.
[0171] In some embodiments, the execution module 603 may be used to: establish a repair process that is independent of the target SDK process; obtain a target SDK repair strategy from the repair platform through the repair process, and execute the target SDK repair strategy to repair the target SDK.
[0172] In some embodiments, the above-mentioned execution module 603 can be used to: monitor the process of the target SDK through the repair process; before the target SDK is repaired, if it is monitored that the process of the target SDK is terminated and the target SDK repair policy has not been downloaded, then continue to download the target SDK repair policy through the repair process until the target SDK repair policy is downloaded and then interrupt the repair process. When the target SDK process is monitored to be started again, the target SDK repair policy is executed through the repair process to repair the target SDK; before the target SDK is repaired, if it is monitored that the process of the target SDK is terminated and the target SDK repair policy has started to be executed, then record the repair progress of the target SDK through the repair process. When the target SDK process is monitored to be started again, continue to repair the target SDK based on the repair progress through the repair process.
[0173] The fifth aspect of the present application further provides an electronic device. Figure 12 is a schematic diagram of the structure of an electronic device provided in an embodiment of the fifth aspect of the present application. As shown in Figure 12, the electronic device 700 includes a memory 701, a processor 702, and a computer program stored in the memory 701 and executable on the processor 702.
[0174] In an example, the processor 702 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0175] The memory 701 may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, typically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the repair method of the SDK in the embodiment of the first aspect of the present application.
[0176] The processor 702 runs a computer program corresponding to the executable program code by reading the executable program code stored in the memory 701, so as to implement the SDK repair method in the above-mentioned first aspect embodiment.
[0177] In some examples, the electronic device 700 may further include a communication interface 703 and a bus 704. As shown in FIG12, the memory 701, the processor 702, and the communication interface 703 are connected via the bus 704 and communicate with each other.
[0178] The communication interface 703 is mainly used to implement communication between the modules, devices, units and / or equipment in the embodiment of the present application. Input devices and / or output devices can also be connected through the communication interface 703.
[0179] The bus 704 includes hardware, software, or both that couples the components of the electronic device 700 to each other. By way of example and not limitation, the bus 704 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or a combination of two or more of the above. Where appropriate, the bus 704 may include one or more buses. Although embodiments herein describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.
[0180] In a sixth aspect, the present application provides a user terminal, which may include a memory, a processor, and a computer program stored in the memory and executable on the processor.
[0181] The memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the repair method of the SDK in the embodiment of the second aspect of the present application.
[0182] The processor runs the computer program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the SDK repair method in the above-mentioned second aspect embodiment.
[0183] In some examples, the user terminal may further include a communication interface and a bus. The memory, processor, and communication interface may be connected via the bus and communicate with each other.
[0184] The connection relationship and specific implementation of the memory, processor, communication interface and bus can be referred to the connection relationship and specific implementation of the memory 701, processor 702, communication interface 703 and bus 704 in the electronic device in the above embodiment, and will not be repeated here.
[0185] In a seventh aspect, the present application provides an SDK repair system, which may include the repair platform and user terminal described in the aforementioned embodiments. The repair platform may execute the SDK repair method described in the aforementioned first aspect, and the user terminal may execute the SDK repair method described in the aforementioned second aspect. For details, please refer to the relevant descriptions in the aforementioned embodiments, and the same technical effects can be achieved. To avoid repetition, these details will not be repeated here.
[0186] In some embodiments, the repair system of the SDK may also include the channel platform in the above embodiments. The channel platform can execute the steps performed by the channel platform in the above embodiments. For details, please refer to the relevant instructions in the above embodiments, and the same technical effects can be achieved. To avoid repetition, they will not be repeated here.
[0187] In an eighth aspect of the present application, a computer-readable storage medium is provided, on which a computer program instruction is stored. When the computer program instruction is executed by a processor, the SDK repair method in the embodiment of the first aspect or the SDK repair method in the embodiment of the second aspect can be implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here. The above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc., which is not limited here.
[0188] An embodiment of the present application may also provide a computer program product. When the instructions in the computer program product are executed by the processor of an electronic device, the electronic device executes the SDK repair method in the embodiment of the first aspect or the SDK repair method in the embodiment of the second aspect. For details, please refer to the relevant descriptions in the above embodiments, and the same technical effects can be achieved. To avoid repetition, they will not be repeated here.
[0189] It should be clear that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For device embodiments, equipment embodiments, user terminal embodiments, system embodiments, computer-readable storage medium embodiments, and computer program product embodiments, the relevant parts can be referred to the description part of the method embodiment. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of this application. In addition, for the sake of brevity, a detailed description of known method technologies is omitted here.
[0190] Aspects of the present application have been described above with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed via the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. This processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit. It is also understood that each box in the block diagram and / or the flowchart and the combination of the boxes in the block diagram and / or the flowchart can also be implemented by the dedicated hardware that performs the specified function or action, or can be implemented by the combination of dedicated hardware and computer instructions.
[0191] Those skilled in the art should understand that the above embodiments are illustrative rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on a study of the drawings, the specification and the claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other devices or steps; the quantifier "one" does not exclude a plurality; the terms "first" and "second" are used to identify names rather than to indicate any specific order. Any figure marks in the claims should not be understood as limiting the scope of protection. The functions of multiple parts appearing in the claims can be implemented by a separate hardware or software module. The fact that certain technical features appear in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.
Claims
1. A method for repairing an SDK, applied to a repair platform, comprising: Obtain software development kit (SDK) information, host information, and SDK exception information of different exception types; Obtaining, based on the SDK information, the host information, and the SDK exception information of each exception type, an exception impact parameter corresponding to each exception type of a target SDK, wherein the target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information; Based on the exception impact parameters corresponding to each exception type of the target SDK and the preset exception classification processing rules, a target SDK repair strategy is obtained, wherein the target SDK repair strategy includes the SDK repair strategy of the exception level corresponding to the exception impact parameters in the exception classification processing rules; The target SDK repair policy is issued to the user terminal, so that the user terminal executes the target SDK repair policy to repair the target SDK.
2. The method according to claim 1, wherein Obtaining the exception impact parameter corresponding to each exception type of the target SDK according to the SDK information, the host information, and the SDK exception information of each exception type includes: Determine the target SDK according to the SDK information and the host information, and obtain feature information in the SDK exception information of each exception type of the target SDK, as well as the weight of the feature information; Calculate the abnormality impact factor corresponding to each abnormality type of the target SDK according to the characteristic information and the weight of the characteristic information; Calculate the output ratio corresponding to each exception type of the target SDK according to the number of SDK exception information of each exception type of the target SDK and the total number of SDK exception information; The abnormal impact parameter corresponding to each abnormal type of the target SDK is calculated by using the abnormal impact factor and the output ratio corresponding to each abnormal type of the target SDK.
3. The method according to claim 1, wherein The target SDK repair strategy is obtained based on the exception impact parameters corresponding to each exception type of the target SDK and the preset exception classification processing rules, including: Determine a target abnormality type according to the abnormality impact parameter corresponding to each abnormality type, wherein the target abnormality type is the abnormality type corresponding to the abnormality impact parameter with the largest value; According to the exception classification processing rule, an exception level corresponding to the target exception type and the exception impact parameter of the target exception type is determined, and according to the exception level, the target SDK repair strategy is determined.
4. The method according to claim 1, wherein The target SDK repair strategy includes one or more of the following: A first file, wherein the first file includes a cache data clearing instruction, wherein the cache data clearing instruction is used to instruct to clear data in at least one cache folder corresponding to the target SDK; A second file, the second file including an abnormal source blocking instruction, the abnormal source blocking instruction being used to instruct to set a switch state of at least one business function and / or sub-business function of the target SDK to a closed state; The third file includes a patch file, and the patch file is used to upgrade and repair the target SDK.
5. The method according to claim 4, wherein The target SDK repair strategy includes the third file, The method further comprises: Obtaining the SDK archive file before and after repair of the target SDK; Obtain a first class file and a second class file, where the first class file includes the class file in the SDK archive file before repair, and the second class file includes the class file in the SDK archive file after repair; Comparing the first class file and the second class file using a comparison algorithm to obtain a third class file, where the third class file includes class files where differences exist between the second class file and the first class file; Convert the third class file into the patch file.
6. The method according to claim 1, wherein The target SDK repair strategy also includes a first signature file, The method further comprises: Generate a first signature according to the host information; A first signature file is generated according to the first signature, where the first signature file includes the first signature.
7. The method according to claim 1, after obtaining a target SDK repair strategy based on the abnormality impact factor of each type of SDK abnormality information of the target SDK according to a preset abnormality classification processing rule, further comprising: Send the target SDK repair strategy to the channel platform; Receiving the target SDK repair strategy fed back by the channel platform, where the fed-back target SDK repair strategy includes a second signature file, and the second signature file includes a second signature, where the second signature is generated by the channel platform based on the host information after scanning and authorizing the target SDK repair strategy; The sending the target SDK repair strategy to the user terminal includes: The target SDK repair strategy fed back by the channel platform is issued to the user terminal.
8. The method according to claim 1, wherein The target SDK repair strategy is executed by a repair process established by the user terminal, and the repair process is independent of the target SDK process.
9. A method for repairing an SDK, applied to a user terminal, comprising: Providing software development kit SDK information, host information, and SDK exception information of different exception types to a repair platform, so that the repair platform obtains a target SDK repair strategy based on an exception impact parameter corresponding to each exception type of the target SDK and a preset exception hierarchical processing rule, the target SDK repair strategy including an SDK repair strategy for an exception level corresponding to the exception impact parameter in the exception hierarchical processing rule, the target SDK corresponding to a host program indicated by the host information and an SDK version indicated by the SDK information, and the exception impact parameter corresponding to each exception type of the target SDK obtained based on the SDK information, the host information, and the SDK exception information of each exception type; The target SDK repair strategy is obtained from the repair platform, and the target SDK repair strategy is executed to repair the target SDK.
10. The method according to claim 9, wherein: The exception impact parameter corresponding to each type of exception of the target SDK is calculated using the exception impact factor and output ratio corresponding to each exception type of the target SDK; the output ratio corresponding to each exception type of the target SDK is calculated based on the number of SDK exception information of each exception type of the target SDK and the total number of SDK exception information; the exception impact factor corresponding to each exception type of the target SDK is calculated based on the feature information in the SDK exception information of each exception type of the target SDK, and the weight of the feature information.
11. The method according to claim 9, wherein The exception level corresponding to the target SDK repair strategy is obtained according to the exception classification processing rule, the target exception type and the exception impact parameter of the target exception type, and the target exception type is the exception type corresponding to the exception impact parameter with the largest value.
12. The method according to claim 9, wherein The target SDK repair strategy includes one or more of the following: A first file, wherein the first file includes a cache data clearing instruction, wherein the cache data clearing instruction is used to instruct to clear data in at least one cache folder corresponding to the target SDK; A second file, the second file including an abnormal source blocking instruction, the abnormal source blocking instruction being used to instruct to set a switch state of at least one business function and / or sub-business function of the target SDK to a closed state; The third file includes a patch file, and the patch file is used to upgrade and repair the target SDK.
13. The method according to claim 12, wherein: The target SDK repair strategy includes the third file, the patch file is converted from the third class file, the third class file includes a class file in which there is a difference between the second class file and the first class file, the first class file includes the class file in the SDK archive file of the target SDK before repair, and the second class file includes the class file in the SDK archive file of the target SDK after repair.
14. The method according to claim 9, wherein The target SDK repair strategy also includes a first signature file, the first signature file includes a first signature, and the first signature is generated by the repair platform according to the host information. After obtaining the target SDK repair strategy from the repair platform, the method further includes: calling the host program indicated by the host information to verify the first signature; The executing the target SDK repair strategy to repair the target SDK includes: In a case where the host program indicated by the host information successfully verifies the first signature, the target SDK repair strategy is executed to repair the target SDK.
15. The method according to claim 9, wherein The target SDK repair strategy also includes a second signature file, the second signature file includes a second signature, and the second signature is generated by the channel platform according to the host information when scanning the target SDK repair strategy and determining authorization. After obtaining the target SDK repair strategy from the repair platform, the method further includes: calling the host program indicated by the host information to verify the second signature; The executing the target SDK repair strategy to repair the target SDK includes: In a case where the host program indicated by the host information successfully verifies the second signature, the target SDK repair strategy is executed to repair the target SDK.
16. The method according to any one of claims 9 to 15, wherein: The step of obtaining the target SDK repair strategy from the repair platform and executing the target SDK repair strategy to repair the target SDK includes: Establishing a repair process, wherein the repair process is independent of the target SDK process; The target SDK repair strategy is obtained from the repair platform through the repair process, and the target SDK repair strategy is executed to repair the target SDK.
17. The method according to claim 16, wherein: The step of obtaining the target SDK repair strategy from the repair platform through the repair process and executing the target SDK repair strategy to repair the target SDK includes: Monitor the target SDK process through the repair process; Before the target SDK is repaired, if it is detected that the target SDK process is terminated and the target SDK repair strategy is not downloaded, the target SDK repair strategy will continue to be downloaded through the repair process until the target SDK repair strategy is downloaded. The repair process will be interrupted and the target SDK process will be restarted when it is detected that the target SDK process is started again. The program executes the target SDK repair strategy to repair the target SDK; Before the target SDK is repaired, if it is detected that the process of the target SDK is terminated and the target SDK repair strategy has begun to be executed, the repair progress of the target SDK is recorded through the repair process. When it is detected that the process of the target SDK is started again, the target SDK is continued to be repaired based on the repair progress through the repair process.
18. A SDK repair device, applied to a repair platform, comprising: The acquisition module is used to obtain software development kit SDK information, host information and SDK exception information of different exception types; a calculation module, configured to obtain, based on the SDK information, the host information, and the SDK exception information of each exception type, an exception impact parameter corresponding to each exception type of a target SDK, wherein the target SDK corresponds to the host program indicated by the host information and the SDK version indicated by the SDK information; a policy configuration module for obtaining a target SDK repair policy based on the exception impact parameters corresponding to each exception type of the target SDK and a preset exception classification processing rule, wherein the target SDK repair policy includes an SDK repair policy for the exception level corresponding to the exception impact parameters in the exception classification processing rule; The issuing module is configured to issue the target SDK repair strategy to the user terminal, so that the user terminal executes the target SDK repair strategy to repair the target SDK.
19. A user terminal, comprising: a sending module, configured to provide a repair platform with software development kit (SDK) information, host information, and SDK exception information of different exception types, so that the repair platform obtains a target SDK repair strategy based on an exception impact parameter corresponding to each exception type of the target SDK and a preset exception grading processing rule, wherein the target SDK repair strategy includes an SDK repair strategy for an exception level corresponding to the exception impact parameter in the exception grading processing rule, the target SDK corresponds to a host program indicated by the host information and an SDK version indicated by the SDK information, and the exception impact parameter corresponding to each exception type of the target SDK is obtained based on the SDK information, the host information, and the SDK exception information of each exception type; A receiving module, configured to obtain the target SDK repair strategy from a repair platform; The execution module is used to execute the target SDK repair strategy to repair the target SDK.
20. An electronic device, used for repairing a platform, comprising: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the SDK repair method according to any one of claims 1 to 8 is implemented.
21. A user terminal, comprising: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the SDK repair method according to any one of claims 9 to 17 is implemented.
22. An SDK repair system, comprising: A repair platform, configured to execute the SDK repair method according to any one of claims 1 to 8; A user terminal, configured to execute the SDK repair method according to any one of claims 9 to 17.
23. A computer-readable storage medium, wherein computer program instructions are stored on the computer-readable storage medium, and when the computer program instructions are executed by a processor, the SDK repair method according to any one of claims 1 to 17 is implemented.
