CN103823665A - SDK (software development kit) activeness analyzing method, network server and system - Google Patents

Abstract

The present invention discloses a SDK activity analysis method, comprising: a network server receives an application release request from a user terminal, the application release request carries at least the source file code of the application to be released; The source file code determines the software development kit (SDK) called by the application; the network server performs SDK activity analysis according to the number of times the SDK is called by the application. The invention also correspondingly discloses a network server and an SDK activity analysis system. The present invention analyzes the SDK activity based on the SDK actually used by the published application, so that the actual application of the SDK can be reflected, and the accuracy of the analysis result is high.

Description

A SDK activity analysis method, network server and system

technical field

The present invention relates to the field of software development, in particular to a software development kit (Software Development Kit, SDK) activity analysis method, a network server and a system.

Background technique

The SDK usually includes a collection of relevant documents, examples and tools to assist in the development of a certain type of application. Developers can use the Application Programming Interface (API) provided by the SDK to achieve rapid development of applications in related fields.

With the continuous growth of various application development needs, many manufacturers and even individuals have successively launched their own SDKs to attract developers to build and release applications based on their own SDKs. As the types and quantities of SDKs continue to increase, SDK activity analysis is particularly important. Through SDK activity analysis, developers and SDK providers can quickly identify the application status of the SDK, which facilitates subsequent processing.

At present, the activity analysis of the SDK is usually based on the number of downloads, that is, the activity is measured by the number of downloads of the SDK. In this analysis method, the download server usually opens a download counter service, which is used to update and save the download times of each SDK. When a certain SDK is downloaded by the user, the download service will update the download times of the SDK and save.

However, using downloads as the analysis standard for SDK activity does not actually reflect the real usage of the SDK in many cases. Many developers will download a large number of SDKs at the same time, but the actual use of the SDK is very small; in addition, once the SDK is downloaded, it can be spread infinitely. Many SDK users do not download the SDK from the SDK download portal, but use it through The method of secondary transmission is obtained. Therefore, using downloads as the measure of SDK activity may easily lead to inaccurate SDK activity analysis results.

Contents of the invention

In view of this, the main purpose of the present invention is to provide an SDK activity analysis method, a network server and a system, which can improve the accuracy of analysis results.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A method for analyzing SDK activity, comprising:

The network server receives an application release request from the user terminal, where the application release request at least carries the source file code of the application to be released;

The network server determines the software development kit SDK called by the application according to the source file code of the application;

The network server performs SDK activity analysis according to the number of times the SDK is invoked by the application.

The method also includes: the network server acquires an SDK interface table, and the SDK interface table includes SDK information and interface information of each SDK;

The network server determines according to the source file code of the application that the SDK called by the application is:

The network server scans the source file code of the application to obtain the interface called by the application;

The network server searches the SDK interface table according to the interface invoked by the application, and determines the SDK invoked by the application.

Before the network server determines the SDK called by the application according to the source file code of the application, the method further includes:

The network server performs a code security check on the source file code of the application, and if the check passes, the subsequent process is executed; if the check fails, an application publishing failure response is returned to the user equipment.

Before the network server determines the SDK called by the application according to the source file code of the application, the method further includes:

The network server uses a compiler to compile the source file code of the application. If the compilation is successful, the subsequent process is executed; if the compilation fails, an application publishing failure response is returned to the user equipment.

The method also includes:

When the user debugs the local application on the user equipment, the user equipment synchronizes the compiler version with the network server.

The method also includes:

The network server receives an application test request from the user terminal, where the application test request at least carries application information to be tested;

The network server tests the application to be tested according to preset test resources and/or test times.

A network server, comprising: a receiving module, an SDK determining module and an analyzing module; wherein,

The receiving module is configured to receive an application release request from a user terminal, where the application release request at least carries the source file code of the application to be released;

The SDK determining module is configured to determine the SDK called by the application according to the source file code of the application received by the receiving module;

The analysis module is used to analyze the SDK activity according to the number of times the SDK is called by the application.

The network server also includes an SDK interface table acquisition module,

The SDK interface table obtaining module is used to obtain the SDK interface table, and the SDK interface table includes SDK information and interface information of each SDK;

The SDK determination module is specifically used to scan the source file code of the application to obtain the interface called by the application; after that, search the SDK interface table obtained by the SDK interface table acquisition module according to the interface called by the application to determine the SDK called by the application.

The web server also includes a code security check module,

The code security check module is used to perform a code security check on the source file code of the application received by the receiving module. If the check passes, the SDK will be notified to determine the module to determine the SDK called by the application; if the check fails, the user device will be notified Returns the application publishing failure response.

The web server also includes compilation modules,

The compiling module is configured to use a compiler to compile the source file code of the application received by the receiving module. If the compiling is successful, the SDK will be notified to determine the module to determine the SDK called by the application; if the compiling fails, the user device will be notified Returns the application publishing failure response.

The compilation module is also used to synchronize the compiler version with the user equipment when the user equipment debugs the local application.

The web server also includes an application testing module,

The receiving module is further configured to receive an application test request from a user terminal, where the application test request at least carries application information to be tested;

The testing module is configured to test the application to be tested according to preset testing resources and/or testing times.

A SDK activity analysis system, including user equipment and network server; wherein,

The user equipment is configured to send an application release request to a network server according to user operations, where the application release request at least carries the source file code of the application to be released;

The network server is the network server according to any one of claims 7 to 10.

The user equipment is further configured to synchronize the compiler version with the network server when the user debugs the local application.

The user equipment is further configured to send an application test request to a network server according to a user operation, where the application test request at least carries application information to be tested;

The network server is further configured to test the application to be tested according to preset test resources and/or test times.

The SDK activity analysis method, network server and system of the present invention, the network server receives the application release request from the user terminal, the application release request at least carries the source file code of the application to be released; the network server according to the source of the application The file code determines the SDK called by the application; the network server analyzes the activity of the SDK according to the number of times the SDK is called by the application. The present invention analyzes the SDK activity based on the SDK actually used by the published application, so that the actual application of the SDK can be reflected, and the accuracy of the analysis result is high.

Description of drawings

Fig. 1 is a schematic flow chart of an SDK activity analysis method according to an embodiment of the present invention;

Fig. 2 is a schematic flow chart of an SDK activity analysis method according to another embodiment of the present invention;

Fig. 3 is a schematic flow chart of an SDK activity analysis method according to yet another embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a network server according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a network server according to another embodiment of the present invention;

FIG. 6 is a schematic diagram of obtaining an SDK interface table according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of generating an application temporary information table according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of generating an SDK calling table according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of generating an SDK activity statistical table according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a network server according to yet another embodiment of the present invention;

FIG. 11 is a schematic structural diagram of a network server according to yet another embodiment of the present invention;

FIG. 12 is a schematic structural diagram of a network server according to yet another embodiment of the present invention.

Detailed ways

The basic idea of the present invention is: the network server receives an application release request from a user terminal, and the application release request at least carries the source file code of the application to be released; the network server determines the application release request according to the source file code of the application The called SDK; the network server performs SDK activity analysis according to the number of times the SDK is called by the application.

Fig. 1 is a schematic flow chart of an SDK activity analysis method according to an embodiment of the present invention. As shown in Fig. 1, the method includes:

Step 101: The network server receives an application release request from a user terminal, and the application release request at least carries the source file code of the application to be released;

Step 102: The network server determines the SDK called by the application according to the source file code of the application;

Step 103: The network server analyzes the activity of the SDK according to the number of times the SDK is called by the application.

Optionally, the method further includes: the network server acquires an SDK interface table, and the SDK interface table includes SDK information and interface information of each SDK. Correspondingly, the network server determines the SDK called by the application according to the source file code of the application as follows: the network server scans the source file code of the application to obtain the interface called by the application; The server searches the SDK interface table according to the interface called by the application, and determines the SDK called by the application.

FIG. 2 is a schematic flow chart of an SDK activity analysis method according to another embodiment of the present invention. As shown in FIG. 2 , optionally, before step 102, the method further includes:

Step 102': The network server performs a code security check on the source file code of the application, and if the check is passed, then step 102 is executed; if the check fails, an application publishing failure response is returned to the user equipment.

Fig. 3 is a schematic flow chart of an SDK activity analysis method according to another embodiment of the present invention. As shown in Fig. 3, optionally, before step 102, the method further includes:

Step 102": The network server uses a compiler to compile the source file code of the application. If the compilation is successful, step 102 is executed; if the compilation fails, an application publishing failure response is returned to the user equipment.

It should be noted that the step 102' of performing security review and the step 102" of performing remote compilation result review can also coexist in the method flow. At this time, the source file code passes the code security check and the application source file code is compiled successfully. Afterwards, step 102 is executed again. Apps that pass the review can be put into operation.

Under normal circumstances, the user (developer) logs in to the SDK download portal, selects the SDK required for application development to download, and after downloading the SDK locally, the application can be developed based on the SDK. Since the application development process requires constant debugging and modification, the application system compilation after each modification needs to call the local compilation environment. Therefore, optionally, the method further includes: when the user debugs the local application on the user equipment, the user equipment synchronizes the compiler version with the network server.

For applications in the development and debugging phases, they are test applications. The test application should be able to access the network server for real environment testing. However, for a test application, the web server may limit the resources available to the application and/or limit the maximum number of application tests. For example, when the execution times of the application exceed the maximum number of tests corresponding to the application, the web server may stop the application. The specific implementation method may be as follows: the network server receives the application test request from the user terminal, and the application test request carries at least the application information to be tested; application for testing.

It should be noted that, in the present invention, the network server may be one server, or a combination of multiple servers.

The embodiment of the present invention also correspondingly proposes a network server, as shown in Figure 4, the network server includes: a receiving module, an SDK determination module and an analysis module; wherein,

The receiving module is configured to receive an application release request from a user terminal, where the application release request at least carries the source file code of the application to be released;

The SDK determining module is configured to determine the SDK called by the application according to the source file code of the application received by the receiving module;

The analysis module is used to analyze the SDK activity according to the number of times the SDK is called by the application.

Fig. 5 is a schematic structural diagram of a network server according to another embodiment of the present invention. As shown in Fig. 5, the network server also includes an SDK interface table acquisition module,

The SDK interface table acquisition module is used to obtain the SDK interface table, and the SDK interface table includes SDK information and interface information of each SDK; generally, the SDK interface table acquisition module scans and analyzes the SDK package on the server side, and Generate the SDK interface table. In addition to auxiliary development materials such as development documents and usage examples, the core of the SDK is an API development kit that provides external interface calls. Taking the C language as an example, the API development package of the SDK includes header files, lib libraries, and dynamic dlls. Among them, the header file and the lib library are used to call the SDK application for static system compilation, and the dynamic dll is used for the system dynamic interface call. The SDK interface table can include two parts: the header file area and the lib library area, which are used to record the static call interfaces exposed by the SDK. As shown in Figure 6, in order to generate the SDK interface table, the SDK interface table acquisition module needs to scan the SDK files and extract the file name part of all header files in the SDK to generate the header file area records in the SDK interface table. At the same time, scan the file name part of all lib libraries in the SDK to generate lib library records in the SDK interface table.

The SDK determination module is specifically used to scan the source file code of the application to obtain the interface called by the application; after that, search the SDK interface table obtained by the SDK interface table acquisition module according to the interface called by the application to determine the SDK called by the application. Taking the C language as an example, after the SDK determination module scans the source file code of the application, it can extract all the header files and lib libraries used by the application according to the scanning results, and save them in the application temporary information table. The application of the first embodiment The generation process of the temporary information table is shown in Figure 7. After that, by comparing the application temporary information table with the SDK interface table, determine the SDK called by the application, generate the SDK call table of the application, and generate the SDK call table, and Only when a header file (hfilen.h in the following table) and a lib library (lfilen.lib in the following table) of the application temporary information table correspond to an SDK interface in the SDK interface table, the The SDK information is recorded in the SDK call table. Embodiment 1 The generation process of the SDK call table is shown in FIG. 8 .

Correspondingly, the analysis module can analyze the SDK call table of each application, generate a statistical table of SDK activity, and use this to perform statistical analysis on the activity of the SDK. Specifically, firstly, according to the SDK calling table of all applications, count the calling situation of each SDK, generate the SDK calling record table, and sort according to the calling times field of each SDK calling table, and generate the SDK activity statistics table. Based on the SDK activity statistics table, the SDK activity can be further analyzed in conjunction with other strategies. The process of generating the SDK activity statistics table in an embodiment of the present invention is shown in FIG. 9 .

Fig. 10 is a schematic structural diagram of a network server according to another embodiment of the present invention. As shown in Fig. 10, the network server also includes a code security check module,

The code security check module is used to perform a code security check on the source file code of the application received by the receiving module. If the check passes, the SDK will be notified to determine the module to determine the SDK called by the application; if the check fails, the user device will be notified Returns the application publishing failure response. This module can integrate existing code security inspection tools. Generally, code security inspection mainly uses the static code scanning technology of software application security to scan the code of the application source files submitted by developers, and combined with the code security inspection module to confirm the application code. security. For applications that detect code security vulnerabilities, the review will not pass, and the developer will be notified of the reason for the review failure.

Fig. 11 is a schematic structural diagram of a network server according to another embodiment of the present invention. As shown in Fig. 11, the network server also includes a compiling module,

The compiling module is configured to use a compiler to compile the source file code of the application received by the receiving module. If the compiling is successful, the SDK will be notified to determine the module to determine the SDK called by the application; if the compiling fails, the user device will be notified Returns the application publishing failure response. Here, the compilation module compiles the source file code of the application submitted by the developer through the user device through the compiler on the network server side. If it can be compiled into an application executable file, it means that the compilation is successful; if the compilation is wrong, the application is rejected. , and notify the developer of compilation errors.

In order to ensure that the compiler version used locally by the developer is consistent with the compiler version used by the application release server, optionally, the compilation module is also used to synchronize the compiler version with the user device when the user device is debugging a local application .

Fig. 12 is a schematic structural diagram of a network server according to another embodiment of the present invention. As shown in Fig. 12, the network server also includes an application testing module,

The receiving module is further configured to receive an application test request from a user terminal, where the application test request at least carries application information to be tested;

The testing module is configured to test the application to be tested according to preset testing resources and/or testing times.

The embodiment of the present invention also correspondingly proposes an SDK activity analysis system, the system includes user equipment and a network server; wherein,

The user equipment is configured to send an application release request to a network server according to user operations, where the application release request at least carries the source file code of the application to be released;

The network server is the above-mentioned network server.

Optionally, the user equipment is further configured to synchronize the compiler version with the network server when the user debugs the local application.

Optionally, the user equipment is further configured to send an application test request to the network server according to a user operation, where the application test request carries at least application information to be tested;

The network server is further configured to test the application to be tested according to preset test resources and/or test times.

In the present invention, the network server determines the SDK called by the application, so it can reflect the real situation of the application using the SDK, which is more objective and true as the basis for analyzing the activity of the SDK.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (15)

1. An SDK activity analysis method, comprising:

the method comprises the steps that a network server receives an application issuing request from a user terminal, wherein the application issuing request at least carries a source file code of an application to be issued;

the network server determines a Software Development Kit (SDK) called by the application according to the source file code of the application;

and the network server analyzes the SDK activity according to the number of times of the SDK being applied and called.

2. The method of claim 1, further comprising: the network server acquires an SDK interface table, wherein the SDK interface table comprises SDK information and interface information of each SDK;

the network server determines that the SDK called by the application is as follows according to the source file code of the application:

the network server scans the source file code of the application to acquire an interface called by the application;

and the network server searches the SDK interface table according to the interface called by the application and determines the SDK called by the application.

3. The method of claim 1, wherein the web server determines the SDK of the application call before it is invoked from a source file code of the application, the method further comprising:

the network server carries out code security check on the source file code of the application, and if the check is passed, the subsequent flow is executed; and if the check is not passed, returning an application release failure response to the user equipment.

4. The method of claim 1, wherein the web server determines the SDK of the application call before it is invoked from a source file code of the application, the method further comprising:

the network server adopts a compiler to compile the source file code of the application, the compilation is successful, and the subsequent flow is executed; and if the compiling fails, returning an application release failure response to the user equipment.

5. The method of claim 4, further comprising:

and when a user debugs a local application on user equipment, the user equipment and the network server carry out compiler version synchronization.

6. The method of any one of claims 1 to 5, further comprising:

the network server receives an application test request from a user terminal, wherein the application test request at least carries application information to be tested;

and the network server tests the application to be tested according to preset test resources and/or test times.

7. A network server, comprising: the system comprises a receiving module, an SDK determining module and an analyzing module; wherein,

the receiving module is used for receiving an application issuing request from a user terminal, wherein the application issuing request at least carries a source file code of an application to be issued;

the SDK determining module is used for determining the SDK called by the application according to the source file code of the application received by the receiving module;

and the analysis module is used for analyzing the SDK activity according to the number of times of the SDK being applied and called.

8. The network server of claim 7, further comprising an SDK interface table acquisition module,

the SDK interface table acquisition module is used for acquiring an SDK interface table, and the SDK interface table comprises SDK information and interface information of each SDK;

the SDK determining module is specifically configured to scan a source file code of the application to obtain an interface called by the application; and then, searching the SDK interface table obtained by the SDK interface table obtaining module according to the interface called by the application, and determining the SDK called by the application.

9. The network server of claim 7, wherein the network server further comprises a code security check module,

the code security check module is used for carrying out code security check on the source file code of the application received by the receiving module, and if the check is passed, the SDK determining module is informed to determine the SDK called by the application; and if the check is not passed, returning an application release failure response to the user equipment.

10. The network server of claim 7, wherein the network server further comprises a compiling module,

the compiling module is used for compiling the source file code of the application received by the receiving module by adopting a compiler, and if the compiling is successful, the SDK determining module is informed to determine the SDK called by the application; and if the compiling fails, returning an application release failure response to the user equipment.

11. The network server of claim 10,

the compiling module is further configured to perform compiler version synchronization with the user equipment when the user equipment debugs the local application.

12. The network server according to any of claims 7 to 11, characterized in that the network server further comprises an application test module,

the receiving module is further configured to receive an application test request from a user terminal, where the application test request at least carries application information to be tested;

and the test module is used for testing the application to be tested according to preset test resources and/or test times.

13. An SDK liveness analysis system, comprising a user device and a network server; wherein,

the user equipment is used for sending an application issuing request to the network server according to user operation, wherein the application issuing request at least carries a source file code of an application to be issued;

the network server according to any one of claims 7 to 10.

14. The system of claim 13,

the user equipment is also used for performing compiler version synchronization with the network server when a user debugs a local application.

15. The system of claim 13 or 14,

the user equipment is also used for sending an application test request to the network server according to user operation, wherein the application test request at least carries application information to be tested;

and the network server is also used for testing the application to be tested according to preset testing resources and/or testing times.

Images