WO2020228033A1 - Sdk plug-in loading method and apparatus, and mobile terminal and storage medium - Google Patents

Abstract

Disclosed are an SDK plug-in loading method and apparatus, and a mobile terminal and a storage medium, relating to the technical field of the Internet of Things. The method is applied to a mobile terminal, an application program is installed on the mobile terminal, and a quick application is added to the application program. The method comprises: a mobile terminal receiving a first start instruction for an application program, and when the first start instruction is responded to and a designated download condition is met, downloading and saving a target SDK plug-in corresponding to a quick application, and when a second start instruction for the quick application is received, responding to the second start instruction to locally load the target SDK plug-in from the mobile terminal. The SDK plug-in loading method and apparatus, the mobile terminal and the storage medium provided in the embodiments of the present application facilitate the optimization and management of an SDK plug-in by means of separating the downloading and loading of the SDK plug-in.

Description

SDK plug-in loading method, device, mobile terminal and storage medium Technical field

This application relates to the technical field of the Internet of Things, and more specifically, to a method, device, mobile terminal, and storage medium for loading an SDK plug-in.

Background technique

Mobile terminals, such as tablet computers and smart phones, have become one of the most commonly used consumer electronic products in people's daily lives. Users can install applications on mobile terminals to implement various functions.

Summary of the invention

In view of the above problems, this application proposes a method, device, mobile terminal, and storage medium for loading an SDK plug-in to solve the above problems.

In the first aspect, an embodiment of the present application provides a method for loading an SDK plug-in, which is applied to a mobile terminal, where an application is installed on the mobile terminal, and a quick application is added to the application, and the method includes: the mobile The terminal receives the first start instruction for the application; when it responds to the first start instruction and meets the specified download conditions, downloads and saves the target software development kit SDK plug-in corresponding to the fast application; when it receives When the second startup instruction for the quick application is executed, the target SDK plug-in is loaded locally from the mobile terminal in response to the second startup instruction.

In the second aspect, an embodiment of the present application provides a device for loading an SDK plug-in, which is applied to a mobile terminal, the mobile terminal is installed with an application program, and a quick application is added to the application program, and the device includes: an instruction receiving module , For the mobile terminal to receive the first startup instruction for the application; the SDK plug-in download module, for downloading the corresponding fast application when responding to the first startup instruction and meeting specified download conditions The target software development kit SDK plug-in is saved; the SDK plug-in loading module is used to load the target from the mobile terminal locally in response to the second start instruction when a second start instruction for the fast application is received SDK plugin.

In a third aspect, an embodiment of the present application provides a mobile terminal, including a memory and a processor, the memory is coupled to the processor, and the memory stores instructions that are executed when the instructions are executed by the processor. The processor executes the above method.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium stores program code, and the program code can be invoked by a processor to execute the foregoing method.

The SDK plug-in loading method, device, mobile terminal, and storage medium provided by the embodiments of the present application. The mobile terminal receives the first startup instruction for the application. When the first startup instruction is responded to and the specified download conditions are met, the download and fast Apply the corresponding target SDK plug-in and save it. When receiving the second startup instruction for the fast application, load the target SDK plug-in locally from the mobile terminal in response to the second startup instruction, thereby separating the download and loading of the SDK plug-in, Facilitate the optimization and management of SDK plug-ins.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

Fig. 1 shows a schematic structural diagram of a smart home system provided by an embodiment of the present application.

FIG. 2 shows a schematic structural diagram of another smart home system provided by an embodiment of the present application;

FIG. 3 shows a schematic diagram of a fast application engine architecture provided by an embodiment of the present application.

Fig. 4 shows a schematic diagram of an operating environment of a method for adding a quick application provided by an embodiment of the present application.

FIG. 5 shows a schematic flowchart of a method for loading an SDK plug-in provided by an embodiment of the present application;

FIG. 6 shows a schematic flowchart of a method for loading an SDK plug-in provided by another embodiment of the present application;

FIG. 7 shows a schematic flowchart of step S220 of the method for loading the SDK plug-in shown in FIG. 6 of the present application;

FIG. 8 shows a schematic flowchart of step S230 of the method for loading the SDK plug-in shown in FIG. 6 of the present application;

FIG. 9 shows a schematic flowchart of step S232 of the method for loading the SDK plug-in shown in FIG. 8 of the present application;

FIG. 10 shows a schematic flowchart of step S250 of the method for loading the SDK plug-in shown in FIG. 6 of the present application;

FIG. 11 shows a schematic flow chart of a method for loading an SDK plug-in provided by another embodiment of the present application;

FIG. 12 shows a schematic flowchart of a method for loading an SDK plug-in provided by another embodiment of the present application;

FIG. 13 shows a schematic flow chart of a method for loading an SDK plug-in provided by another embodiment of the present application;

FIG. 14 shows a block diagram of a module of a device for loading an SDK plug-in provided by an embodiment of the present application;

FIG. 15 shows a block diagram of an electronic device used to execute the method for loading an SDK plug-in according to an embodiment of the present application;

Fig. 16 shows a storage unit used to store or carry the program code implementing the method for loading the SDK plug-in according to the embodiment of the present application.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

With the advancement of science and technology, smart homes have penetrated into various families and are loved by many families because of the convenience it brings. Smart home connects various smart home devices in the home (such as air conditioners, lights, refrigerators, washing machines, etc.) through the Internet of Things technology to provide home appliance control, lighting control, telephone remote control, indoor and outdoor remote control, anti-theft alarm, and environmental monitoring , HVAC control, infrared forwarding and programmable timing control and other controls.

Since applications can be installed on the mobile terminal to implement various functions, by installing an application program for managing and controlling home equipment on the mobile terminal, the management and control of the home equipment can be realized remotely. Among them, household equipment can be air conditioners, lighting fixtures, smart lights, smart cameras, smart sockets, wireless switches, smart curtain motors, smart speakers, and various sensors (such as human sensors, door and window sensors, smoke alarms, etc.).

Referring to Fig. 1, at present, the home equipment is managed and controlled through a mobile terminal, usually by establishing a wireless connection with the smart gateway 300 through the mobile terminal 100, and establishing a wireless connection between the home equipment 200 and the smart gateway 300 to realize the mobile terminal 100 and Data interaction between household devices. In addition, the mobile terminal 100 and the smart gateway 300 are in communication connection with the server 400, and the mobile terminal 100 can interact with household equipment through the server 400 and the smart gateway 300.

Referring to FIG. 2, the mobile terminal 100 may be in communication connection with the first cloud server 402 to realize data interaction with the first cloud server 402. The household equipment 200 communicates with the second cloud server 401 through the smart gateway 300 to realize data interaction between the second and the server 401. In addition, data interaction can be performed between the first cloud server 402 and the second cloud server 401, so that the mobile terminal 100 can communicate with the household equipment 200 through the first cloud server 402, the second cloud server 404, and the smart gateway 300. Data interaction.

At present, home appliances of different manufacturers usually need to be controlled through different applications. That is to say, the communication between the applications of the home equipment of different manufacturers and the servers of different manufacturers requires more applications to be installed, thus occupying mobile More storage space for the terminal.

With the popularization of Quick APP, mobile terminal developers expect to use Quick APP to achieve the same functions as the aforementioned client, so as to improve the development efficiency of smart home functions and at the same time save the storage space of the mobile terminal. Among them, the fast application is a new application form based on the hardware platform of the terminal device. It does not need to be installed, it is click-to-use, and it has the original application experience (performance, system integration, interaction, etc.). As shown in Figure 3, the structure diagram of the fast application engine, the front-end design of the fast application draws on and integrates the design ideas of mainstream front-end frameworks (Vue, React, etc.): build applications in a componentized way, with data binding as the core The MVVM design mode uses V-DOM to improve performance, while choosing a concise and clear Vue-like template.

In addition, as shown in FIG. 4, in the mobile terminal 100 shown in FIG. 4, a quick application and an application program 110 are running. The fast application runs on the fast application engine, and the fast application engine is provided with an extension interface 97 provided by the application program. The application program 110 is provided with an expansion interface 96 that communicates with the expansion interface 97. The application program 110 may call software development kit (SDK, Software Development Kit) plug-ins of various manufacturers through an extended interface. For example, the SDK plug-in 111 of manufacturer A, the SDK plug-in 112 of manufacturer B, and the SDK plug-in 113 of manufacturer C in the figure can be called. In this case, the data processing instructions triggered in the fast application can be transferred to the extended interface 96 in the client through the extension interface 97 set in the fast application engine, and then the data processing instructions are transmitted to the SDK plug-ins of various manufacturers .

Further, the application program 110 may provide an entrance to the quick application, that is, the application program 110 may enter the quick application. The communication between the fast application and the application 110 may be through a cross-application communication method, such as using AIDL interaction. Specifically, a parameter transfer interface can be set between the application 110 and the embedded fast application for data transfer between the application 110 and the fast application. For example, a channel class can be defined between the fast application and the application 110 Interface, all interface functions are implemented using a channel class interface. When entering the quick application through the application 110, the application 110 may instruct the quick application engine to access the corresponding quick application according to the link of the quick application, thereby displaying the interface of the quick application. The interface of the quick app can receive control information, and after the application program 110 learns the control information, it transmits the control information to the server of the home device through the above-mentioned SDK to realize the management and control of the home device. In addition, the quick application engine can also receive the information transmitted by the application program 110, and display the information that needs to be displayed on the quick application control page.

After long-term research, the inventor found that when the current application enters the fast application, the SDK plug-in corresponding to the fast application will be checked and updated and judged whether to download, and the update judgment is complicated, the process is longer, and it is easy to compare with the loading time of the SDK plug-in. The overlap causes the slow loading of the SDK plug-in. In response to the above problems, the inventors proposed the method, device, mobile terminal, and storage medium for loading the SDK plug-in provided by the embodiments of the present application. By separating the downloading and loading of the SDK plug-in, it is convenient to optimize and manage the SDK plug-in. Wherein, the specific method for loading the SDK plug-in is described in detail in the subsequent embodiments.

Please refer to FIG. 5, which shows a schematic flowchart of a method for loading an SDK plug-in provided by an embodiment of the present application. The method for loading the SDK plug-in is used to facilitate the optimization and management of the SDK plug-in by separating the downloading and loading of the SDK plug-in. In a specific embodiment, the SDK plug-in loading method is applied to the SDK plug-in loading device 200 as shown in FIG. 14 and the mobile terminal 100 (FIG. 15) equipped with the SDK plug-in loading device 500 (FIG. 15), An application is installed on the mobile terminal, and a quick application is added to the application. The following will take a mobile terminal as an example to illustrate the specific process of this embodiment. Of course, it is understandable that the mobile terminal applied in this embodiment can be a smart phone, a tablet computer, a wearable electronic device, a vehicle-mounted device, a gateway, etc. , There is no specific limitation here. The following will elaborate on the process shown in FIG. 5, and the loading method of the SDK plug-in may specifically include the following steps:

Step S110: The mobile terminal receives a first start instruction for the application.

In this embodiment, an application is installed on the mobile terminal and a quick application is added to the application. When the user wants to start the quick application, the user needs to start the application first, and then start the quick application added to the application Therefore, the user can send a startup instruction instructing to start the application to the mobile terminal, where the startup instruction is recorded as the first startup instruction, and accordingly, the mobile terminal receives the first startup instruction for the application.

As a way, the first start instruction may be generated when the user performs a touch operation on the icon of the application, for example, it may be generated when a single-finger click operation on the icon of the application is detected, or It is generated when a pressing operation on the icon of the application is detected, it can be generated when a multi-finger click operation on the icon of the application is detected, or it can be generated when a long operation on the icon of the application is detected. Generated by operation, etc., which are not limited here; the first start instruction can be generated when it is detected that the user searches for an application in the search box of the mobile terminal, for example, when the mobile terminal detects that the user searches for " When the mobile terminal detects that the user searches for “application B” in the search box, it generates the first instruction to start “application B”. A startup instruction; the first startup instruction can also be generated when it is detected that the user inputs voice information to start the application on the mobile terminal. For example, when the mobile terminal detects the voice information of the user "start application A", it is generated The first startup instruction instructing to start the "application A", when the mobile terminal detects the voice information of the user "starting the application B", it generates the first startup instruction instructing to start the "application B".

Step S120: When the first start instruction is responded to and the specified download condition is satisfied, download and save the target software development kit SDK plug-in corresponding to the fast application.

Further, the mobile terminal is set with designated download conditions, where the designated download conditions can be stored locally in the mobile terminal after pre-setting, or can be obtained from the server in real time. In addition, the designated download conditions can be configured by the mobile terminal or by User configuration is not limited here. Therefore, when the mobile terminal receives the first start instruction, it can determine whether the mobile terminal currently satisfies the specified download condition, wherein, when the mobile terminal meets the specified download condition, it downloads the target SDK corresponding to the fast application in response to the first start instruction The plug-in is saved; when the mobile terminal does not meet the specified download conditions, it does not respond to the first start instruction. Among them, the specified download conditions include, but are not limited to, network conditions, SDK plug-in update conditions, etc. Taking network conditions as an example, if the current network status of the mobile terminal is poor, that is, the network conditions are not met, which means that the mobile terminal cannot be accessed via the network. If the server downloads the target SDK plug-in corresponding to the fast application, the mobile terminal may not respond to the first start instruction; and if the current network status of the mobile terminal is good, that is, the network condition is satisfied, which means that the mobile terminal can download the fast application from the server through the network Corresponding to the target SDK plug-in, the mobile terminal responds to the first start instruction to download and save the target SDK plug-in.

Step S130: When a second startup instruction for the quick application is received, load the target SDK plug-in locally from the mobile terminal in response to the second startup instruction.

In this embodiment, when the user wants to start the quick application in the application, he can send a startup instruction instructing to start the quick application to the mobile terminal, where the startup instruction is recorded as the second startup instruction, and correspondingly, the mobile terminal Receive a second start instruction for the fast application.

As a way, the second start instruction may be generated when the user performs a touch operation on the controls of the quick application in the application, for example, may be a single-finger click operation on the controls of the quick application is detected Time generation, it can be generated when a pressing operation on the control of the quick application is detected, it can be generated when a multi-finger click operation on the control of the quick application is detected, or it can be generated when the It is generated during long-press operation on the control of the application, etc., which are not limited here; the second start instruction may be generated when it is detected that the user searches for the fast application in the search box of the application, for example, when the mobile terminal detects the user When searching for "Quick Application A" in the search box of the application, a second startup instruction instructing to start "Quick Application A" is generated. When the mobile terminal detects that the user searches for "Quick Application B" in the search box of the application , A second start instruction indicating to start "Quick Application B" is generated; the second start instruction can also be generated when it is detected that the user enters the voice information to start the application in the application, for example, when the mobile terminal detects that the user is in When the voice message of "Launch Quick App A" is input in the application, a second start instruction instructing to start "Quick App A" is generated. When the mobile terminal detects that the user enters the "Launch Quick App B" in the application In the case of voice information, a second start instruction instructing to start "Quick Application B" is generated.

Further, the mobile terminal loads the target SDK plug-in locally from the mobile terminal in response to the second start instruction, so that the fast app can obtain corresponding control and services from its corresponding vendor server through the target SDK plug-in. Therefore, in this embodiment of the application, the download and loading of the target SDK plug-in is time-sharing processing, making the processing of downloading and loading the target SDK plug-in more flexible and more conducive to optimization. In addition, the target SDK plug-in is downloaded and saved in the mobile terminal in advance. Locally, it also makes the target SDK plug-in load faster when entering the fast application, improving the user experience.

In addition, in this embodiment, the target SDK plug-in may be implemented through the main process of the mobile terminal, and the loading of the target SDK plug-in may be implemented through the ipc process or main thread of the mobile terminal; or the target SDK plug-in may be implemented through the main process of the mobile terminal. The target SDK plug-in can be loaded in a mixed manner, for example, through the main process and the ipc process of the mobile terminal at the same time, or through the main process and the main thread of the mobile terminal at the same time. For example, because the SDK plug-in has the main process UI, so this part of the trustworthy part can be loaded separately in the main process, while the other parts can be implemented by the ipc process or main thread of the mobile terminal. Since the technical side is loaded separately, it can facilitate subsequent optimization of the SDK plug-in .

In the method for loading the SDK plug-in provided by an embodiment of the present application, the mobile terminal receives the first startup instruction for the application, and when it responds to the first startup instruction and meets the specified download conditions, downloads the target SDK plug-in corresponding to the fast application and Save, when receiving the second startup instruction for the quick application, load the target SDK plug-in locally from the mobile terminal in response to the second startup instruction, so as to facilitate the optimization and optimization of the SDK plug-in by separating the download and loading of the SDK plug-in management.

Please refer to FIG. 6, which shows a schematic flowchart of a method for loading an SDK plug-in provided by another embodiment of the present application. The method is applied to the above-mentioned mobile terminal. The process shown in FIG. 6 will be described in detail below. The method for loading the SDK plug-in may specifically include the following steps:

Step S210: The mobile terminal receives a first start instruction for the application.

For the specific description of step S210, please refer to step S110, which will not be repeated here.

Step S220: Acquire parameter information of the quick application when the first start instruction is responded to and the specified download condition is satisfied.

In this embodiment, when it is determined that the mobile terminal satisfies the specified download conditions, it can also respond to the first start instruction to obtain the parameter information of the fast application, where the parameter information can be used as the mobile terminal corresponding to the fast application The input parameters of the download interface of the target SDK plug-in.

Please refer to FIG. 7. FIG. 7 shows a schematic flowchart of step S220 of the method for loading the SDK plug-in shown in FIG. 6 of the present application. The process shown in FIG. 7 will be described in detail below, and the method may specifically include the following steps:

Step S221: Obtain brand information corresponding to the quick application.

As an implementation manner, the mobile terminal can obtain the brand information corresponding to the quick app, where the mobile terminal can obtain the brand information corresponding to the quick app from its corresponding terminal server, or obtain the brand information from the manufacturer server corresponding to the quick app. Quickly apply the corresponding brand information, which is not limited here.

Taking the mobile terminal obtaining the brand information corresponding to the quick application from its corresponding terminal server as an example, the mobile terminal can obtain the identification information of the quick application and send the identification information to the terminal server, and the terminal server searches for the quick application according to the identification information. Identify the brand information corresponding to the identification information and return the brand information to the mobile terminal. As an implementable way, the terminal server stores multiple identification information and the mapping relationship between multiple brand information. When the mobile terminal obtains When the identification information A of the fast application is applied, the identification information A can be sent to the terminal server, and the terminal server searches for the brand information corresponding to the identification information A from the saved mapping relationship, and when it finds that the brand information corresponding to the identification information A is the brand In the case of information A, the brand information A can be returned to the mobile terminal.

Step S222: Obtain a first protocol version number of the application program, where the first protocol version number is used to characterize the largest version among the protocol version numbers supported by the application program.

Further, the mobile terminal obtains the first protocol version number of the application program, where the first protocol version number is used to characterize the largest version among the protocol version numbers supported by the application program, and the first protocol version number is hard-coded It is written, that is, the version number of the first protocol is fixed. Of course, when the version of the application program is updated, the version number of the first protocol can remain unchanged, or it can remain unchanged after the update. This is not limited. For example, when the version number of the application program is "version number 1", the first protocol version number is fixed as "version number 1", and when the version number of the application program is updated to "version number 2", the first protocol version number The protocol version number can remain unchanged, that is, continue to be fixed as "version number 1", or it can be updated and fixed as "version number 2", which is not limited here.

Step S223: Generate parameter information of the quick application based on the brand information and the first protocol version number.

In this embodiment, after acquiring the brand information corresponding to the quick application and the first protocol version number of the application, the parameter information of the quick application can be generated based on the brand information and the first protocol version number, and The parameter information is used as the input parameter of the download interface of the target SDK plug-in corresponding to the fast application by the mobile terminal.

Step S230: Download and save the target SDK plug-in corresponding to the fast application based on the parameter information.

Among them, after obtaining the parameter information of the quick application, a judgment can be made based on the parameter information, and the target SDK plug-in corresponding to the quick application can be downloaded and saved, so as to improve the accuracy of downloading the target SDK plug-in. In this embodiment, the latest version of the SDK plug-in corresponding to the quick application can be downloaded and saved based on the parameter information. For example, if the protocol version number includes protocol version number 1 and protocol version number 2, and the protocol version number of the protocol is 2 The version number is greater than the protocol version number of the protocol version number 1, where the protocol version number is the version number of the jar package defining the interface specification of the SDK plug-in.

As the first method, if the first protocol version number is protocol version number 2, then the vendor server corresponding to the fast app will first search for the SDK plug-in of the protocol version number 2. If it finds that the protocol version number 2 includes For SDK plug-in, search for the latest version of SDK plug-in from protocol version number 2, and return the latest version of SDK plug-in to the mobile terminal as the target SDK plug-in; if no SDK plug-in of protocol version number 2 is found For example, when the mobile terminal requests the target SDK plug-in from the server, if the protocol version number requested by the mobile terminal is protocol version number 2, and the protocol version number used by the manufacturer’s server corresponding to the fast app is protocol version number 1, it means If the SDK plug-in of this manufacturer’s server does not have a version of protocol version number 2 (only the SDK protocol version of protocol version number 1), then look for the SDK plug-in of protocol version number 1. If it is found that the protocol version number 1 includes the SDK plug-in, then Find the latest version of the SDK plug-in from the protocol version number 1, and return the latest version of the SDK plug-in to the mobile terminal as the target SDK plug-in.

As the second way, if the first protocol version number is the protocol version number 1, then the vendor server corresponding to the fast app will only search for the SDK plug-in of the protocol version number 1. If the protocol version number 1 includes When the SDK plug-in is used, the latest version of the SDK plug-in is retrieved from the protocol version number 1, and the latest version of the SDK plug-in is returned to the mobile terminal as the target SDK plug-in. Therefore, in this embodiment, the SDK plug-in is downward compatible.

Please refer to FIG. 8. FIG. 8 shows a schematic flowchart of step S230 of the method for loading the SDK plug-in shown in FIG. 6 of the present application. The process shown in FIG. 8 will be described in detail below, and the method may specifically include the following steps:

Step S231: Obtain a vendor server corresponding to the fast application based on the brand information.

Among them, the vendor server corresponding to the fast application can be obtained based on the brand information in the parameter information. As a way, different fast apps correspond to different brand information, and different brand information corresponds to different vendor servers. Therefore, it can be based on the correspondence between fast apps-brand information-vendor servers, and based on the brand information Obtain the vendor server corresponding to the quick app.

For example, as shown in Table 1, Table 1 shows a correspondence between fast apps, brand information, and vendor servers. Among them, fast application is represented by K, brand information is represented by P, and vendor server is represented by C.

Table 1

Quick application (K)	Brand Information (P)	Vendor Server (C)
K1	P1	C1
K2	P2	C2
K3	P3	C3
K4	P4	C4
...	...	...

If the fast app is K1, then based on the correspondence between K1-P1-C1, it can be determined that the brand information corresponding to the fast app K1 is brand P1, and the manufacturer server corresponding to the fast app K1 is the manufacturer server C1; if The fast application is K2, then, based on the correspondence between K2-P2-C2, it can be determined that the brand information corresponding to the fast application K2 is brand P2, and the manufacturer server corresponding to the fast application K2 is the manufacturer server C2, etc. This will not be repeated here.

Step S232: Based on the first protocol version number, search for the latest version of the SDK plug-in under the first protocol version number in the vendor server and save it.

Further, after obtaining the vendor server corresponding to the quick app based on the brand information in the parameter information, the latest version under the first protocol version number can be searched in the vendor server based on the first protocol version number in the parameter information SDK plug-in and save. For example, if the first protocol version number is protocol version number 2, search for the latest version of the SDK plug-in of protocol version number 2 in the manufacturer’s server and save it; if the first protocol version number is protocol version number 1, then Find the latest version of the SDK plug-in with protocol version 1 in the manufacturer's server and save it.

Please refer to FIG. 9. FIG. 9 shows a schematic flowchart of step S232 of the method for loading the SDK plug-in shown in FIG. 8 of the present application. The process shown in FIG. 9 will be described in detail below, and the method may specifically include the following steps:

Step S2321: Determine whether the vendor server includes the SDK plug-in under the first protocol version number.

As a way, after determining the vendor server corresponding to the quick application, it can be determined whether the mall server includes the SDK plug-in under the first protocol version number. For example, if the first protocol version number is the protocol version number 2, it can be judged whether the manufacturer’s server includes the SDK plug-in of the protocol version number 2; if the first protocol version number is the protocol version number 1, the manufacturer’s server can be judged Whether to include the SDK plug-in of the protocol version number 1.

Step S2322: If the vendor server includes the SDK plug-in under the first protocol version number, based on the first protocol version number, search the vendor server for the latest version of the SDK under the first protocol version number Plug-in and save.

Wherein, if the judgment result indicates that the manufacturer's server includes the SDK plug-in under the first protocol version number, the latest version of the SDK plug-in under the first protocol version number can be searched and saved in the manufacturer's server. For example, if the first protocol version number is protocol version number 2, and the manufacturer’s server includes the SDK plug-in under protocol version number 2, then the manufacturer’s server can search for the latest version of all SDK plugins under protocol version number 2. SDK plug-in to obtain the latest version of the SDK plug-in and save it.

Step S2323: If the vendor server does not include the SDK plug-in under the first protocol version number, obtain the second protocol version number of the application, where the second protocol version number is smaller than the first protocol version number.

Wherein, if the judgment result indicates that the manufacturer's server does not include the SDK plug-in under the first protocol version number, the second protocol version number of the application can be obtained, where the second protocol version number is smaller than the first protocol version For example, if the first protocol version number is protocol version number 5, and the manufacturer’s server does not include the SDK plug-in under protocol version number 5, you can select from protocol version number 1, protocol version number 2, and protocol version number 3. , Protocol version number 4 and other protocol version numbers less than protocol version number 5, select a second protocol version number, for example, select protocol version number 4 as the second protocol version number, and protocol version number 2 as the second Protocol version number, etc.

As a way, the second protocol version number is only smaller than the first protocol version number. For example, if the first protocol version number is the protocol version number 5, then the second protocol version number is the protocol version number 4; if the first protocol version number is the protocol version number 4, then the second protocol The version number is the protocol version number 3. It will not be repeated here.

Step S2324: Based on the second protocol version number, search for the latest version of the SDK plug-in under the second protocol version number in the vendor server.

Further, after the second protocol version number is determined, the latest version of the SDK plug-in under the second protocol version number can be searched in the manufacturer’s server to improve the possibility that the mobile terminal can obtain the latest version of the SDK plug-in that can be run , Improve user experience.

Step S240: When receiving the second startup instruction for the fast application, respond to the second startup instruction to obtain the target SDK plug-in locally from the mobile terminal.

For the specific description of step S240, please refer to step S130, which will not be repeated here.

Step S250: Separate the target file from the target SDK plugin and load the target SDK plugin.

In this embodiment, after the target SDK plug-in is obtained locally from the mobile terminal, the target file in the SDK plug-in can be separated and the target SDK plug-in can be loaded, where the target file includes at least a configuration file and a so file, thereby Ensure that the SDK plugin reads files quickly when in use. As a way, when loading, the target SDK plug-in can be directly loaded dynamically, but the so file in the target file still needs to be loaded separately. Among them, the so file can be loaded using loadlibrary, and the configuration file can be loaded when loading. Read in the code.

Please refer to FIG. 10, which shows a schematic flowchart of step S250 of the method for loading the SDK plug-in shown in FIG. 6 of the present application. The following will elaborate on the process shown in FIG. 10, and the method may specifically include the following steps:

Step S251: Separate the target file from the target SDK plug-in, and determine whether the target file is complete.

As an implementation manner, after the mobile terminal separates the target file from the target SDK plug-in, it can determine whether the target file is complete, for example, whether the configuration file and the so file are complete.

Step S252: If the target file is complete, load the target SDK plug-in.

As a way, if the judgment result indicates that the target file is complete, the target SDK file can be loaded directly.

As another way, if the judgment result indicates that the target file is incomplete, it may cause the file to be missing and cannot be used normally. Since the target file such as the configuration file and the so file is separated from the SDK plug-in, it can be removed from the SDK again The target file is separated from the plug-in, so as to ensure that when the target file such as the configuration file or the so file is accidentally damaged or deleted, it can be processed again. This can ensure that there will be no errors when loading, and ensure the safety and security of the SDK plug-in loading. The integrity of the loaded SDK plug-in, while ensuring the speed of loading.

Step S260: When the mobile terminal downloads the SDK plug-in corresponding to the quick application to be loaded, it is determined whether the application is killed after the target SDK plug-in is loaded.

Further, if the mobile terminal downloads the SDK to be loaded corresponding to the fast application again after loading the target SDK, it can judge whether the application is killed after loading the target SDK plug-in, that is, it can be judged Whether the application completely exits after loading the target SDK plug-in.

Step S270: If the mobile terminal is not killed after loading the target SDK plug-in, save the SDK plug-in to be loaded, and keep the target SDK plug-in as the current SDK plug-in of the fast application.

Among them, if the judgment result indicates that the mobile terminal was not killed after loading the target SDK plug-in, as a way, the SDK plug-in to be loaded can be saved as the SDK plug-in to be loaded next time, and the target SDK plug-in can be kept as the Kuaiapp’s current SDK plug-in, that is, even if the mobile terminal downloads the SDK plug-in to be loaded again, if the application is not killed during the process from loading the target SDK plug-in to downloading to the SDK plug-in to be loaded, it will not be restarted Load other SDK plugins, such as not reloading the SDK plugin to be loaded. Specifically, if the application pulls up the fast application and then exits and then enters, but the fast application did not exit last time, you can load the SDK plugin in the fast application. At this time, the latest version of the local SDK plugin is loaded. When a newer version of the SDK plug-in to be loaded is downloaded, Kuaiapp will continue to use the previously loaded target SDK plug-in, unless the application is killed and then restarted to ensure that multiple versions of the SDK plug-in will not be loaded together.

In the method for loading the SDK plug-in provided by another embodiment of the present application, the mobile terminal receives the first startup instruction for the application, and when it responds to the first startup instruction and satisfies the specified download conditions, obtains the parameter information of the quick application, based on the The parameter information downloads the target SDK plug-in corresponding to the quick application and saves it. When receiving the second startup instruction for the quick application, in response to the second startup instruction, the target SDK plug-in is obtained locally from the mobile terminal, the target file is separated from the target SDK plug-in, and the target SDK plug-in is loaded. When the mobile terminal downloads the SDK plug-in to be loaded corresponding to the quick application again, judge whether the application is killed after loading the target SDK plug-in, if the mobile terminal is not killed after loading the target SDK plug-in, save The SDK plug-in to be loaded, and the target SDK plug-in is retained as the current SDK plug-in of the fast application. Compared with the method for loading the SDK plug-in shown in FIG. 5, this embodiment can download the SDK plug-in based on the parameter information of the fast application to improve the speed and accuracy of obtaining the SDK plug-in. In addition, the target file can be separated from the target SDK plug-in. And load it to improve the loading speed of the target SDK plug-in and the security of records.

Please refer to FIG. 11, which shows a schematic flowchart of a method for loading an SDK plug-in provided by another embodiment of the present application. The method is applied to the above-mentioned mobile terminal. The process shown in FIG. 11 will be described in detail below. The method for loading the SDK plug-in may specifically include the following steps:

Step S310: The mobile terminal receives a first start instruction for the application.

Step S320: Acquire parameter information of the quick application when the first start instruction is responded to and the specified download condition is satisfied.

Step S330: Download and save the target SDK plug-in corresponding to the fast application based on the parameter information.

Step S340: When receiving a second startup instruction for the quick application, respond to the second startup instruction to obtain the target SDK plug-in locally from the mobile terminal.

Step S350: Separate the target file from the target SDK plugin and load the target SDK plugin.

For the specific description of step S310 to step S350, please refer to step S210 to step S250, which will not be repeated here.

Step S360: When the mobile terminal downloads the SDK plug-in to be loaded corresponding to the quick application, it is determined whether the target SDK plug-in is deleted.

Further, if after loading the target SDK plug-in, the mobile terminal downloads the SDK plug-in to be loaded corresponding to the fast application again, it can determine whether the target SDK plug-in is deleted, that is, it can detect whether the target SDK plug-in It is deleted from the memory of the mobile terminal.

Step S370: If the target SDK plug-in is not deleted, save the SDK plug-in to be loaded, and keep the target SDK plug-in as the current SDK plug-in of the quick application.

Among them, if the judgment result indicates that the target SDK plug-in has not been deleted, as a way, the SDK plug-in to be loaded can be saved as the SDK plug-in to be loaded next time, and the target SDK plug-in can be kept as the current SDK plug-in of the fast application. That is, even if the mobile terminal downloads the SDK plug-in to be loaded again, if the target SDK plug-in is not deleted from the memory of the mobile terminal from loading the target SDK plug-in to downloading to the SDK plug-in to be loaded, it will not be reloaded Other SDK plug-ins, such as not reloading the SDK plug-in to be loaded, so as to ensure that multiple versions of SDK plug-ins will not be loaded together.

In the method for loading the SDK plug-in provided by another embodiment of the present application, the mobile terminal receives the first startup instruction for the application, and when it responds to the first startup instruction and satisfies the specified download conditions, obtains the parameter information of the quick application, based on the The parameter information downloads the target SDK plug-in corresponding to the quick application and saves it. When receiving the second startup instruction for the quick application, in response to the second startup instruction, the target SDK plug-in is obtained locally from the mobile terminal, the target file is separated from the target SDK plug-in, and the target SDK plug-in is loaded. When the mobile terminal downloads the SDK plug-in to be loaded corresponding to the quick app again, it is judged whether the target SDK plug-in is deleted. If the target SDK plug-in is not deleted, save the SDK plug-in to be loaded, and keep the target SDK plug-in as The current SDK plugin for fast application. Compared with the method for loading the SDK plug-in shown in FIG. 5, this embodiment can download the SDK plug-in based on the parameter information of the fast application to improve the speed and accuracy of obtaining the SDK plug-in. In addition, the target file can be separated from the target SDK plug-in. And load it to improve the loading speed of the target SDK plug-in and the security of records.

Please refer to FIG. 12, which shows a schematic flowchart of a method for loading an SDK plug-in provided by another embodiment of the present application. The method is applied to the above-mentioned mobile terminal, the mobile terminal is installed with an application program, and multiple quick applications are added to the application program. The process shown in FIG. 12 will be described in detail below. The loading method of the SDK plug-in is specifically It can include the following steps:

Step S410: The mobile terminal receives a first start instruction for the application.

For the specific description of step S410, please refer to step S110, which will not be repeated here.

Step S420: In response to the first start instruction, start the application and display the home page of the application.

As a way, after receiving the first start instruction, the mobile terminal can start the application in response to the first start instruction, and enter and display the home page of the application.

Step S430: Obtain the device information displayed on the home page, and obtain the target quick application corresponding to the device information.

Further, the homepage of the application can display device information of multiple devices, and the device information can be displayed in text form. For example, the homepage of the application displays "XX air conditioner", "XX refrigerator", "XX TV", etc. Among them, "XX" can characterize the brand; device information can be displayed in the form of pictures, for example, the home page of the application displays pictures including XX air conditioning text, displays pictures including XX refrigerator text, displays pictures including XX TV text, etc. For another example, the home page display of the application program includes controls for XX air conditioner text, controls for display including XX refrigerator text, and controls for display including XX TV text, which are not limited here. As a way, the display content of the homepage of the application can be recognized. For example, the picture displayed on the homepage of the mobile terminal, the text displayed on the homepage, and the controls displayed on the homepage can be recognized to obtain the device displayed on the homepage of the application. information.

In addition, after obtaining the device information, the target quick application corresponding to the device information can be obtained according to the device information. As a way, the corresponding relationship between the quick application and the device information can be established, so as to determine the quick application corresponding to the device identification according to the device identification. As a way, the correspondence between quick apps and device information can be stored in the mobile terminal where the application is installed in the form of a list. In the list, each device information corresponds to one quick app, or multiple device information corresponds to A quick application.

Step S440: download and save the target SDK plug-in corresponding to the target quick application among the multiple quick applications first.

Further, since the device information corresponding to the target fast application is displayed on the home page of the application, the control corresponding to the device information is most likely to be selected by the user. Therefore, in order to ensure that the user selects the control corresponding to the device information, The SDK plug-in corresponding to the target quick application corresponding to the device information has been downloaded to improve user experience, and the target SDK plug-in corresponding to the target quick application among the multiple quick applications can be downloaded first and saved.

As a way, the mobile terminal can separately download the target SDK plug-in corresponding to each of the multiple quick applications, and save the target SDK plug-in corresponding to each quick application in a different storage area, thereby achieving different brands , SDK plug-ins with different protocol versions and different protocol version numbers are stored in different directories, and will not interfere with each other when downloading and loading.

Step S450: When receiving a second startup instruction for the target flash application, load the target SDK plug-in corresponding to the target flash application from the local of the mobile terminal in response to the second startup instruction, and continue to download the Target SDK plug-ins corresponding to other fast applications in the multiple fast applications except the target fast application.

Further, when the mobile terminal loads the target SDK plug-in corresponding to the target fast application in response to the second start instruction, it can also continue to download the target SDK plug-ins corresponding to other fast apps among the multiple fast apps except the target fast application. Therefore, , Can realize that the download of SDK plug-in will not affect the normal use of users, and improve user experience.

In the method for loading the SDK plug-in provided by another embodiment of the present application, the mobile terminal receives the first startup instruction for the application, responds to the first startup instruction, starts the application and displays the homepage of the application, and obtains the device information displayed on the homepage , And obtain the target fast application corresponding to the device information, download and save the target SDK plug-in corresponding to the target fast application among multiple fast applications first, and respond to the second start instruction for the target fast application when receiving the second start instruction for the target fast application. The start instruction loads the target SDK plug-in corresponding to the target fast application from the local of the mobile terminal, and continues to download the target SDK plug-ins corresponding to other fast applications in the multiple fast applications except the target fast application. Compared with the method for loading the SDK plug-in shown in FIG. 5, this embodiment also preferentially records the target SDK plug-in of the fast application corresponding to the device information displayed by the application program, thereby improving user experience.

Please refer to FIG. 13, which shows a schematic flowchart of a method for loading an SDK plug-in provided by another embodiment of the present application. The method is applied to the above-mentioned mobile terminal, the mobile terminal is installed with an application program, and multiple quick applications are added to the application program. The process shown in FIG. 13 will be described in detail below. The method for loading the SDK plug-in is specifically It can include the following steps:

Step S510: The mobile terminal receives a first start instruction for the application.

For the specific description of step S510, please refer to step S110, which will not be repeated here.

Step S520: In response to the first startup instruction, obtain the current SDK plug-in of the quick application and identify the current version of the current SDK plug-in.

As a way, when the mobile terminal receives the first startup instruction, it can respond to the first startup instruction to obtain the current SDK plug-in of the fast application, and identify the current version of the current SDK plug-in.

Step S530: Determine whether the current version is the latest version.

Further, after obtaining the current version of the current SDK plug-in of the quick application, it can be determined whether the current version is the latest version. As an implementation manner, the version number of the current version and the version number of the latest version can be obtained separately, and whether the version number of the current version is consistent with the version number of the latest version is compared, if the version number of the current version is consistent with the version number of the latest version , It can be determined that the current version is the latest version. If the version number of the current version is inconsistent with the version number of the latest version, it can be determined that the current version is not the latest version.

Step S540: If the current version is not the latest version, download the latest version of the SDK plug-in corresponding to the quick application and save it.

Among them, as a method, if the judgment result indicates that the current version is not the latest version, the latest version of the SDK plug-in corresponding to the quick app can be downloaded and saved to ensure that the SDK plug-in loaded by the quick app is the latest version; as another In this way, if the judgment result indicates that the current version is the latest version, the download processing of the SDK plug-in may not be performed to reduce the power consumption of the mobile terminal.

Step S550: In response to the second start instruction, detect whether the mobile terminal is configured with an original SDK plug-in corresponding to the quick application.

In this embodiment, when the mobile terminal receives the second startup instruction, it can respond to the second startup instruction to detect whether the mobile terminal is configured with the original SDK plug-in corresponding to the quick application, that is, it can respond to the second startup The instruction detects whether the mobile terminal is loaded with the original SDK plug-in corresponding to the fast application.

Step S560: If the mobile terminal is configured with an original SDK plug-in corresponding to the quick application, forcibly update the original SDK plug-in to the target SDK plug-in.

As a way, if the detection result indicates that the mobile terminal is equipped with the original SDK plug-in corresponding to the quick app, the original SDK plug-in can be forced to update to the target SDK plug-in to ensure that the version of the SDK plug-in loaded by the mobile terminal is the latest version .

Step S570: If the mobile terminal is configured with the original SDK plug-in corresponding to the quick application, output a prompt message, wherein the prompt message user prompts the user to choose whether to update the original SDK plug-in to the target SDK plug-in.

As another way, if the detection result indicates that the mobile terminal is configured with the original SDK plug-in corresponding to the quick app, a prompt message can be output to deliberately prompt the user to choose whether to update the original SDK plug-in to the target SDK plug-in, so as to improve user experience.

In the method for loading the SDK plug-in provided by another embodiment of the present application, the mobile terminal receives the first startup instruction for the application, responds to the first startup instruction, obtains the current SDK plug-in of the fast application and identifies the current version of the current SDK plug-in, and judges Whether the current version is the latest version, if the current version is not the latest version, download the latest version of the SDK plug-in corresponding to the quick app and save it, respond to the second start instruction, and detect whether the mobile terminal is configured with the original corresponding to the quick app SDK plug-in, if the mobile terminal is configured with the original SDK plug-in corresponding to the quick app, it is mandatory to update the original SDK plug-in to the target SDK plug-in, or if the mobile terminal is configured with the original SDK plug-in corresponding to the quick app, a prompt message is output, the prompt message Used to prompt the user to choose whether to update the original SDK plugin to the target SDK plugin. Compared with the method for loading the SDK plug-in shown in FIG. 5, this embodiment downloads the target SDK plug-in when the current SDK plug-in version of the fast application is not the latest version, reducing the power consumption of the mobile terminal. In addition, the mobile terminal is configured with a fast When applying the corresponding original SDK plug-in, it is mandatory to update or the user chooses to update to improve user experience.

Please refer to FIG. 14, which shows a block diagram of a device 500 for loading an SDK plug-in according to an embodiment of the present application. The loading device 500 of the SDK plug-in is applied to the above-mentioned mobile terminal, the mobile terminal is installed with an application program, and a quick application is added to the application program. The following will elaborate on the block diagram shown in FIG. 14. The SDK plug-in loading device 500 includes: an instruction receiving module 510, an SDK plug-in downloading module 520, and an SDK plug-in loading module 530, where:

The instruction receiving module 510 is used for the mobile terminal to receive a first start instruction for the application.

The SDK plug-in download module 520 is configured to download and save the target software development kit SDK plug-in corresponding to the fast application when the specified download condition is met in response to the first start instruction. Further, the SDK plug-in download module 520 includes: a parameter information acquisition sub-module and a first SDK plug-in download sub-module, wherein:

The parameter information acquisition sub-module is used to acquire the parameter information of the fast application. Further, the parameter information obtaining submodule includes: a brand information obtaining unit, a first protocol version number obtaining unit, and a parameter information obtaining unit, wherein:

The brand information acquiring unit is used to acquire brand information corresponding to the quick application.

The first protocol version number obtaining unit is configured to obtain the first protocol version number of the application program, where the first protocol version number is used to characterize the largest version of the protocol version numbers supported by the application program.

The parameter information acquiring unit is configured to generate parameter information of the quick application based on the brand information and the first protocol version number.

The first SDK plug-in download sub-module is configured to download and save the target SDK plug-in corresponding to the fast application based on the parameter information. Further, the SDK plug-in download sub-module includes: a vendor server acquisition unit and an SDK plug-in search unit, wherein:

The vendor server obtaining unit is configured to obtain the vendor server corresponding to the fast application based on the brand information.

The SDK plug-in search unit is configured to search for and save the latest version of the SDK plug-in under the first protocol version number in the vendor server based on the first protocol version number. Further, the SDK plug-in search unit includes: a judgment subunit, a first SDK plug-in search subunit, a second protocol version number acquisition subunit, and a second SDK plug-in search subunit, wherein:

The judging subunit is used to judge whether the vendor server includes the SDK plug-in under the first protocol version number.

The first SDK plug-in search subunit is configured to, if the vendor server includes the SDK plug-in under the first protocol version number, search for the first protocol version in the vendor server based on the first protocol version number Save the latest version of the SDK plug-in under the number.

The second protocol version number obtaining subunit is configured to obtain the second protocol version number of the application program if the vendor server does not include the SDK plug-in under the first protocol version number, where the second protocol version The number is smaller than the first protocol version number.

The second SDK plug-in searching subunit is configured to search for the latest version of the SDK plug-in under the second protocol version number in the vendor server based on the second protocol version number.

Further, multiple quick apps are added to the application, and the SDK plug-in download module 420 further includes: a second target SDK plug-in download sub-module, a target SDK plug-in saving sub-module, a home page display sub-module, and a target quick application acquisition Sub-modules and priority download sub-modules, including:

The second target SDK plug-in downloading sub-module is used to download the target SDK plug-in corresponding to each of the multiple quick applications.

The target SDK plugin saving submodule is used to save the target SDK plugin corresponding to each quick application in a different storage area.

First, a display sub-module is used to respond to the first start instruction to start the application and display the home page of the application.

The target quick app acquisition submodule is used to obtain the device information displayed on the homepage, and obtain the target quick app corresponding to the device information.

The priority downloading sub-module is used to download and save the target SDK plug-in corresponding to the target fast application among the multiple fast applications.

Further, the SDK plug-in download module 520 further includes: a current version acquisition sub-module, a current version judgment sub-module, and a third target SDK plug-in download sub-module, where:

The current version obtaining submodule is used to respond to the first start instruction, obtain the current SDK plug-in of the quick application and identify the current version of the current SDK plug-in.

The current version judgment sub-module is used to judge whether the current version is the latest version.

The third target SDK plug-in download sub-module is used to download and save the latest version of the SDK plug-in corresponding to the quick application if the current version is not the latest version.

The SDK plug-in loading module 530 is configured to load the target SDK plug-in locally in the mobile terminal in response to the second startup instruction when a second startup instruction for the quick application is received. Further, the SDK plug-in loading module 530 includes: an SDK plug-in obtaining sub-module and a first SDK plug-in loading sub-module, wherein:

The SDK plug-in acquiring sub-module is used to respond to the second start instruction to acquire the target SDK plug-in locally from the mobile terminal.

The first SDK plug-in loading sub-module is used to separate the target file from the target SDK plug-in and load the target SDK plug-in. Further, the SDK plug-in loading sub-module includes: a target file separation unit and an SDK plug-in loading unit, wherein:

The target file separating unit is used to separate the target file from the target SDK plug-in and determine whether the target file is complete.

The SDK plug-in loading unit is configured to load the target SDK plug-in if the target file is complete.

Further, the SDK plug-in loading module 530 includes: a second SDK plug-in loading sub-module, wherein:

The second SDK plug-in loading sub-module is used to load the target SDK corresponding to the target flash application from the local of the mobile terminal in response to the second startup instruction when a second startup instruction for the target flash application is received Plug-ins, and continue to download target SDK plug-ins corresponding to other quick apps among the plurality of quick apps except the target quick app.

Further, the SDK plug-in loading module 530 includes: an original SDK plug-in detection sub-module, a mandatory update to the module, and a prompt information output sub-module, wherein:

The original SDK plug-in detection sub-module is configured to respond to the second start instruction and detect whether the mobile terminal is configured with the original SDK plug-in corresponding to the quick application.

The mandatory update sub-module is used to force the original SDK plug-in to be updated to the target SDK plug-in if the mobile terminal is configured with the original SDK plug-in corresponding to the fast application.

The prompt information output sub-module is configured to output prompt information if the mobile terminal is configured with the original SDK plug-in corresponding to the quick application, wherein the prompt information user prompts the user to choose whether to update the original SDK plug-in to all The target SDK plug-in.

Further, the device 500 for loading the SDK plug-in further includes: a first judgment module, a first reservation module, a second judgment module, and a second reservation module, wherein:

The first judging module is configured to judge whether the application is killed after loading the target SDK plug-in when the mobile terminal downloads the SDK plug-in to be loaded corresponding to the quick application.

The first retention module is configured to save the SDK plug-in to be loaded if the mobile terminal is not killed after loading the target SDK plug-in, and retain the target SDK plug-in to continue as the current SDK plug-in of the quick application .

The second judgment module is configured to judge whether the target SDK plug-in is deleted when the mobile terminal downloads the SDK plug-in to be loaded corresponding to the quick application.

The second retention module is configured to save the SDK plug-in to be loaded if the target SDK plug-in is not deleted, and retain the target SDK plug-in to continue as the current SDK plug-in of the quick application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of the description, the specific working process of the device and module described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, the coupling between the modules may be electrical, mechanical or other forms of coupling.

In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.

Please refer to FIG. 15, which shows a structural block diagram of a mobile terminal 100 provided by an embodiment of the present application. The mobile terminal 100 may be an electronic device capable of running application programs, such as a smart phone, a tablet computer, or an e-book. The mobile terminal 100 in this application may include one or more of the following components: a processor 110, a memory 120, a screen 130, a codec 140, and one or more application programs, of which one or more application programs may be stored in the memory 120 and configured to be executed by one or more processors 110, and one or more programs are configured to execute the methods described in the foregoing method embodiments.

The processor 110 may include one or more processing cores. The processor 110 uses various interfaces and lines to connect various parts of the entire mobile terminal 100, and executes by running or executing instructions, programs, code sets, or instruction sets stored in the memory 120, and calling data stored in the memory 120. Various functions and processing data of the mobile terminal 100. Optionally, the processor 110 may use at least one of digital signal processing (Digital Signal Processing, DSP), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), and Programmable Logic Array (Programmable Logic Array, PLA). A kind of hardware form to realize. The processor 110 may be integrated with one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is used for rendering and drawing of display content; the modem is used for processing wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 110, but may be implemented by a communication chip alone.

The memory 120 may include random access memory (RAM) or read-only memory (Read-Only Memory). The memory 120 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 120 may include a program storage area and a data storage area, where the program storage area may store instructions for implementing the operating system and instructions for implementing at least one function (such as touch function, sound playback function, image playback function, etc.) , Instructions for implementing the following method embodiments, etc. The data storage area can also store data (such as phone book, audio and video data, chat record data) created by the terminal 100 during use.

Please refer to FIG. 16, which shows a structural block diagram of a computer-readable storage medium provided by an embodiment of the present application. The computer-readable medium 600 stores program code, and the program code can be invoked by a processor to execute the method described in the foregoing method embodiment.

The computer-readable storage medium 600 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, hard disk, or ROM. Optionally, the computer-readable storage medium 600 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 600 has a storage space for the program code 610 for executing any method steps in the above methods. These program codes can be read out from or written into one or more computer program products. The program code 610 may be compressed in a suitable form, for example.

In summary, the SDK plug-in loading method, device, mobile terminal, and storage medium provided in the embodiments of the present application. The mobile terminal receives the first start instruction for the application, and when it responds to the first start instruction and satisfies the specified download condition Download and save the target SDK plug-in corresponding to the quick application. When receiving the second startup instruction for the quick application, load the target SDK plug-in locally from the mobile terminal in response to the second startup instruction. The separation of downloading and loading facilitates the optimization and management of SDK plug-ins.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application, not to limit them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; these modifications or replacements do not drive the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims (20)

1. A method for loading an SDK plug-in, characterized in that it is applied to a mobile terminal, the mobile terminal is installed with an application program, and a quick application is added to the application program, and the method includes:

   Receiving, by the mobile terminal, a first start instruction for the application;

   When responding to the first start instruction and meeting the specified download conditions, download and save the target software development kit SDK plug-in corresponding to the fast application;

   When receiving the second start instruction for the fast application, load the target SDK plug-in from the local of the mobile terminal in response to the second start instruction.
2. The method of claim 1, wherein the downloading and saving the target SDK plug-in corresponding to the quick application comprises:

   Acquiring parameter information of the quick application;

   Download and save the target SDK plug-in corresponding to the fast application based on the parameter information.
3. The method according to claim 2, wherein said acquiring parameter information of said fast application comprises:

   Acquiring brand information corresponding to the quick application;

   Acquiring a first protocol version number of the application program, where the first protocol version number is used to characterize the largest version of the protocol version numbers supported by the application program;

   The parameter information of the quick application is generated based on the brand information and the first protocol version number.
4. The method according to claim 3, wherein the downloading and saving the target SDK plug-in corresponding to the fast application based on the parameter information comprises:

   Obtaining a vendor server corresponding to the fast application based on the brand information;

   Based on the first protocol version number, search for and save the latest version of the SDK plug-in under the first protocol version number in the vendor server.
5. The method according to claim 4, wherein the searching and saving the latest version of the SDK plug-in under the first protocol version number in the vendor server based on the first protocol version number comprises:

   Judging whether the vendor server includes the SDK plug-in under the first protocol version number;

   If the vendor server includes the SDK plug-in under the first protocol version number, based on the first protocol version number, search the vendor server for the latest version of the SDK plug-in under the first protocol version number and save it .
6. The method of claim 5, wherein the method further comprises:

   If the manufacturer's server does not include the SDK plug-in under the first protocol version number, obtain the second protocol version number of the application program, where the second protocol version number is smaller than the first protocol version number;

   Based on the second protocol version number, search for the latest version of the SDK plug-in under the second protocol version number in the vendor server.
7. The method according to claim 6, wherein the second protocol version number is only smaller than the first protocol version number.
8. The method according to any one of claims 1-7, wherein the loading the target SDK plug-in from a local of the mobile terminal in response to the second start instruction comprises:

   In response to the second start instruction, obtain the target SDK plug-in locally from the mobile terminal;

   Separate the target file from the target SDK plug-in and load the target SDK plug-in.
9. The method according to claim 8, wherein the separating the target file from the target SDK plug-in and loading the target SDK plug-in comprises:

   Separate the target file from the target SDK plug-in, and determine whether the target file is complete;

   If the target file is complete, load the target SDK plug-in.
10. The method according to claim 8 or 9, wherein the target file includes at least a configuration file and an so file.
11. The method according to any one of claims 1-10, after the loading the target SDK plug-in from the local of the mobile terminal in response to the second start instruction, further comprising:

    When the mobile terminal downloads the SDK plug-in to be loaded corresponding to the quick application, determining whether the application is killed after loading the target SDK plug-in;

    If the mobile terminal is not killed after loading the target SDK plug-in, save the SDK plug-in to be loaded, and keep the target SDK plug-in as the current SDK plug-in of the fast application.
12. The method according to any one of claims 1-10, after the loading the target SDK plug-in from the local of the mobile terminal in response to the second start instruction, further comprising:

    When the mobile terminal downloads the SDK plug-in to be loaded corresponding to the quick application, determining whether the target SDK plug-in is deleted;

    If the target SDK plugin is not deleted, save the SDK plugin to be loaded, and keep the target SDK plugin as the current SDK plugin of the quick application.
13. The method according to any one of claims 1-12, wherein a plurality of quick applications are added to the application program, and the downloading and saving the target SDK plug-in corresponding to the quick application comprises:

    Separately downloading the target SDK plug-in corresponding to each of the multiple quick applications;

    The target SDK plug-in corresponding to each quick application is stored in a different storage area.
14. The method according to claim 13, wherein after the mobile terminal receives the first start instruction for the application, the method further comprises:

    In response to the first start instruction, start the application and display the homepage of the application;

    Acquiring the device information displayed on the homepage, and acquiring the target quick application corresponding to the device information;

    The target SDK plug-in corresponding to the target quick application among the multiple quick applications is downloaded first and saved.
15. The method according to claim 14, wherein when a second startup instruction for the quick application is received, the target SDK plug-in is loaded from a local of the mobile terminal in response to the second startup instruction ,include:

    When receiving the second start instruction for the target fast application, load the target SDK plug-in corresponding to the target fast application from the local of the mobile terminal in response to the second start instruction, and continue to download the multiple fast apps. Target SDK plug-ins corresponding to other fast applications in the application except the target fast application.
16. The method according to any one of claims 1-15, wherein the downloading and saving the target SDK plug-in corresponding to the quick application when the first start instruction is responded to and a specified download condition is met, include:

    In response to the first start instruction, obtain the current SDK plug-in of the quick application and identify the current version of the current SDK plug-in;

    Determine whether the current version is the latest version;

    If the current version is not the latest version, download the latest version of the SDK plug-in corresponding to the quick application and save it.
17. The method according to any one of claims 1-16, wherein the loading the target SDK plug-in from a local of the mobile terminal in response to the second start instruction comprises:

    In response to the second start instruction, detect whether the mobile terminal is configured with an original SDK plug-in corresponding to the quick application;

    If the mobile terminal is configured with an original SDK plug-in corresponding to the quick application, forcibly update the original SDK plug-in to the target SDK plug-in; or

    If the mobile terminal is configured with the original SDK plug-in corresponding to the quick application, a prompt message is output, wherein the prompt message user prompts the user to choose whether to update the original SDK plug-in to the target SDK plug-in.
18. An SDK plug-in loading device, characterized in that it is applied to a mobile terminal, the mobile terminal is installed with an application program, and a quick application is added to the application program, and the device includes:

    An instruction receiving module, used for the mobile terminal to receive a first start instruction for the application;

    The SDK plug-in download module is configured to download and save the target software development kit SDK plug-in corresponding to the fast application when the specified download condition is met in response to the first start instruction;

    The SDK plug-in loading module is configured to load the target SDK plug-in locally in the mobile terminal in response to the second startup instruction when a second startup instruction for the quick application is received.
19. A mobile terminal, comprising a memory and a processor, the memory is coupled to the processor, the memory stores instructions, and the processor executes the instructions when the instructions are executed by the processor. The method of any one of 1-17 is required.
20. A computer-readable storage medium, wherein the computer-readable storage medium stores program code, and the program code can be invoked by a processor to execute the method according to any one of claims 1-17 .

Images