CN106453494A - A plug-in update method, system, client and server - Google Patents

Abstract

The invention discloses a plug-in update method, system, client and server, belonging to the field of communication, including: the server confirms the functions to be loaded by the client APP; the server loads components corresponding to the functions from the registration module; The component is loaded into the plug-in, and the plug-in is sent to the client APP; the client APP loads the plug-in into the plug-in environment, and loads the components in the plug-in through the plug-in environment. The plug-in is loaded into the plug-in environment through the client APP, and the components in the plug-in are loaded through the plug-in environment, which avoids updating the client by downloading and installing the APP, thereby saving system processing resources and operating resources, and improving user experience.

Description

A plug-in update method, system, client and server

technical field

The invention relates to the communication field, in particular to a plug-in updating method, system, client and server.

Background technique

On current smart terminals, users can install third-party application programs (Application, APP) to meet their own usage needs. In order to facilitate the use of users and improve the user experience, it is often necessary to update some built-in functions of the APP, or to optimize some algorithms of the APP.

However, in the existing technology, the update of some built-in functions of the APP, or the optimization of some algorithms of the APP is realized by releasing a new version of the APP. This process usually releases a new version of the APP for the APP provider, and the user needs to download and install it. This new version of the APP is to realize the update of some built-in functions of the APP and the optimization of some algorithms of the APP.

Since the user is downloading the new version of the APP, the required transmission traffic is relatively large, and the storage space occupied is also relatively large, and during the installation of the APP, it will occupy more system processing resources, thereby reducing the user's ability to use the APP. User experience in the process.

Contents of the invention

In order to avoid updating the client by downloading and installing an APP, save system processing resources and operating resources, and improve user experience, embodiments of the present invention provide a plug-in update method, system, client, and server. Described technical scheme is as follows:

In the first aspect, a method for updating a plug-in is provided, and the method includes:

The server confirms the functions to be loaded by the client APP;

The server loads components corresponding to the functions from the registration module;

The server loads the component into a plug-in, and sends the plug-in to the client APP;

The client APP loads the plug-in into a plug-in environment, and loads components in the plug-in through the plug-in environment.

With reference to the first aspect, in a first possible implementation manner, the server confirms the function to be loaded by the client APP through at least one of the following operations:

Obtain a loading request triggered by the user on the client APP, and confirm the function to be loaded by the client APP according to the loading request; or

After the client APP detects the update, according to the update request sent by the client APP, confirm the functions to be loaded by the client APP.

With reference to the first possible implementation of the first aspect, in a second possible implementation, the server loading components corresponding to the functions from the registration module includes:

According to the function name in the registration module, the component corresponding to the function to be loaded is selected from a plurality of components included in the executable file group.

With reference to the second possible implementation of the first aspect, in a third possible implementation, loading the component to the plug-in by the server includes:

Setting communication configuration data between the component and the data layer;

Encapsulating the communication configuration data and the component into the plug-in.

In combination with the third possible implementation of the first aspect, in the fourth possible implementation,

The client APP loading the plug-in to the plug-in environment includes:

Loading the communication configuration data into the plug-in environment;

According to the communication configuration data, a communication mechanism between the component and the data layer is set.

With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, loading the components in the plug-in by the client APP through the plug-in environment includes:

The client APP loads the component.

With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner, loading the component by the client APP includes:

After the user loading event is detected, the component is loaded, and after the loading is completed, the client APP is run;

Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the duration of the user's continuous clicking on the interface meeting a threshold.

In a second aspect, a server is provided, and the server includes:

The confirmation module is used to confirm the functions to be loaded by the client APP;

The first loading module is configured to load components corresponding to the functions from the registration module;

a second loading module, configured to load the component into the plug-in;

A sending module, configured to send the plug-in to the client APP, so that the client APP loads the plug-in into a plug-in environment, and loads components in the plug-in through the plug-in environment.

With reference to the second aspect, in a first possible implementation manner, the confirmation module includes:

An acquisition submodule, configured to acquire a loading request triggered by a user on the client APP;

The first confirmation submodule is used to confirm the function to be loaded by the client APP according to the loading request;

The second confirmation submodule is configured to confirm the functions to be loaded by the client APP according to the update request sent by the client APP after the client APP detects the update.

In combination with the first possible implementation of the second aspect, in the second possible implementation,

The first loading module is specifically used for:

According to the function name in the registration module, the component corresponding to the function to be loaded is selected from a plurality of components included in the executable file group.

In combination with the second possible implementation of the second aspect, in the third possible implementation,

The second loading module includes:

The communication configuration data setting submodule is used to set the communication configuration data between the components and the data layer;

The encapsulation sub-module is used for encapsulating the communication configuration data and the components into the plug-in.

In a third aspect, a client is provided, and the client includes:

A sending module, configured to send the function to be loaded to the server, so that the server can confirm the function, load the component corresponding to the function from the registration module, and load the component to the plug-in;

A receiving module, configured to receive the plug-in sent by the server;

The first loading module is used to load the plug-in into the plug-in environment;

The second loading module is used to load the components in the plug-in through the plug-in environment.

With reference to the third aspect, in a first possible implementation manner, the sending module includes:

A first sending submodule, configured to send a loading request triggered by a user to the server;

The detection sub-module is used to detect updates;

The second sending submodule is configured to send an update request to the server after the detection submodule detects an update.

With reference to the first possible implementation of the third aspect, in a second possible implementation, the first loading module is specifically configured to:

Loading the communication configuration data into the plug-in environment;

According to the communication configuration data, a communication mechanism between the component and the data layer is set.

With reference to the second possible implementation of the third aspect, in a third possible implementation, the second loading module includes:

Load submodule for loading said components.

In combination with the third possible implementation of the third aspect, in a fourth possible implementation, the loading submodule is specifically used for:

After the user loading event is detected, the component is loaded, and after the loading is completed, the APP is run;

Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the duration of the user's continuous clicking on the interface meeting a threshold.

In a fourth aspect, a server is provided, wherein the server includes a memory and a processor connected to the memory, wherein the memory is used to store a set of program codes, and the processor calls the The program code stored in the memory is used to perform the following operations:

Confirm the functions to be loaded by the client APP;

Loading components corresponding to the functions from the registration module;

loading said component into the plugin;

sending the plug-in to the client APP, so that the client APP loads the plug-in into a plug-in environment, and loads components in the plug-in through the plug-in environment.

With reference to the fourth aspect, in a first possible implementation manner, the processor calls the program code stored in the memory to perform the following operations:

Obtain a loading request triggered by the user on the client APP;

According to the loading request, confirm the function to be loaded by the client APP; or

After the client APP detects the update, according to the update request sent by the client APP, confirm the functions to be loaded by the client APP.

With reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the processor invokes the program code stored in the memory to perform the following operations:

According to the function name in the registration module, the component corresponding to the function to be loaded is selected from a plurality of components included in the executable file group.

With reference to the second possible implementation manner of the fourth aspect, in a third possible implementation manner, the processor invokes the program code stored in the memory to perform the following operations:

Setting communication configuration data between the component and the data layer;

Encapsulating the communication configuration data and the component into the plug-in.

According to a fifth aspect, a client is provided, wherein the client includes a memory and a processor connected to the memory, wherein the memory is used to store a set of program codes, and the processor calls the The program code stored in the memory is used to perform the following operations:

sending the function to be loaded to the server, so that the server confirms the function, loads the component corresponding to the function from the registration module, and loads the component into the plug-in;

receiving the plug-in sent by the server;

loading the plug-in into a plug-in environment;

The components in the plug-in are loaded through the plug-in environment.

With reference to the fifth aspect, in a first possible implementation manner, the processor invokes the program code stored in the memory to perform the following operations:

sending a user-triggered loading request to said server; or

After an update is detected, an update request is sent to the server.

With reference to the first possible implementation manner of the fifth aspect, in a second possible implementation manner, the processor invokes the program code stored in the memory to perform the following operations:

Loading the communication configuration data into the plug-in environment;

According to the communication configuration data, a communication mechanism between the component and the data layer is set.

With reference to the second possible implementation manner of the fifth aspect, in a third possible implementation manner, the processor invokes the program code stored in the memory to perform the following operations:

Load said component.

With reference to the third possible implementation manner of the fifth aspect, in a fourth possible implementation manner, the processor invokes the program code stored in the memory to perform the following operations:

After the user loading event is detected, the component is loaded, and after the loading is completed, the APP is run;

Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the duration of the user's continuous clicking on the interface meeting a threshold.

In a sixth aspect, a plug-in update system is provided, and the system includes a server and a client:

The server includes:

The confirmation module is used to confirm the functions to be loaded by the client APP;

The first loading module is configured to load components corresponding to the functions from the registration module;

a second loading module, configured to load the component into the plug-in;

A first sending module, configured to send the plug-in to the client APP, so that the client APP loads the plug-in into a plug-in environment, and loads components in the plug-in through the plug-in environment;

The clients include:

The second sending module is used to send the function to be loaded to the server, so that the server can confirm the function, load the component corresponding to the function from the registration module, and load the component to the plug-in;

A receiving module, configured to receive the plug-in sent by the server;

The third loading module is used to load the plug-in into the plug-in environment;

The fourth loading module is used to load the components in the plug-in through the plug-in environment.

In combination with the sixth aspect, in the first possible implementation manner,

The confirmation module includes:

An acquisition submodule, configured to acquire a loading request triggered by a user on the client APP;

The first confirmation submodule is used to confirm the function to be loaded by the client APP according to the loading request;

The second confirmation submodule is used to confirm the function to be loaded by the client APP according to the update request sent by the client APP after the client APP detects the update;

The second sending module includes:

A first sending submodule, configured to send a loading request triggered by a user to the server;

The detection sub-module is used to detect updates;

The second sending submodule is configured to send an update request to the server after the detection submodule detects an update.

With reference to the first possible implementation of the sixth aspect, in a second possible implementation, the first loading module is specifically configured to:

According to the function name in the registration module, the component corresponding to the function to be loaded is selected from a plurality of components included in the executable file group.

With reference to the second possible implementation manner of the sixth aspect, in a third possible implementation manner, the second loading module includes:

The communication configuration data setting submodule is used to set the communication configuration data between the components and the data layer;

The encapsulation sub-module is used for encapsulating the communication configuration data and the components into the plug-in.

With reference to the third possible implementation of the sixth aspect, in a fourth possible implementation, the third loading module is specifically configured to:

Loading the communication configuration data into the plug-in environment;

According to the communication configuration data, a communication mechanism between the component and the data layer is set.

With reference to the fourth possible implementation of the sixth aspect, in a fifth possible implementation, the fourth loading module is specifically configured to:

Load said component.

With reference to the fifth possible implementation manner of the sixth aspect, in a sixth possible implementation manner, the loading submodule is specifically used for:

After the user loading event is detected, the component is loaded, and after the loading is completed, the APP is run;

Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the duration of the user's continuous clicking on the interface meeting a threshold.

The embodiment of the present invention provides a plug-in update method, system, client, and server. The method includes: the server confirms the function to be loaded by the client APP; the server loads the component corresponding to the function from the registration module; the server loads the component Load to the plug-in, and send the plug-in to the client APP; the client APP loads the plug-in to the plug-in environment, and loads the components in the plug-in through the plug-in environment. The plug-in is loaded into the plug-in environment through the client APP, and the components in the plug-in are loaded through the plug-in environment, which avoids updating the client by downloading and installing the APP, thereby saving system processing resources and operating resources, and improving user experience.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

Fig. 1 is a flowchart of a method for updating a plug-in provided by an embodiment of the present invention;

Fig. 2 is a flowchart of a method for updating a plug-in provided by an embodiment of the present invention;

Fig. 3 is a schematic diagram of a client APP interface provided by an embodiment of the present invention;

Fig. 4 is a schematic diagram of a client APP interface provided by an embodiment of the present invention;

Fig. 5 is a schematic diagram of a client APP interface provided by an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a server provided by an embodiment of the present invention;

Fig. 7 is a schematic structural diagram of a client provided by an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a server provided by an embodiment of the present invention;

Fig. 9 is a schematic structural diagram of a client provided by an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a plug-in update system provided by an embodiment of the present invention.

detailed description

In order to make the purpose, technical solutions and advantages of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only Some, but not all, embodiments of the invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Embodiment 1 is a plug-in update method provided by an embodiment of the present invention, as shown in FIG. 1 , the method includes:

101. The server confirms the functions to be loaded by the client APP.

Specifically, the server confirms the function to be loaded by the client APP through at least one of the following operations:

Obtain the loading request triggered by the user on the client APP, and confirm the functions to be loaded by the client APP according to the loading request; or

After the client APP detects the update, it confirms the functions to be loaded by the client APP according to the update request sent by the client APP.

102. The server loads components corresponding to functions from the registration module.

Specifically, according to the function name in the registration module, the component corresponding to the function to be loaded is selected from the multiple components contained in the executable file group.

103. The server loads the component into the plug-in, and sends the plug-in to the client APP.

Specifically, the server loads the component to the plug-in, and the process can be:

Set the communication configuration data between the component and the data layer;

Encapsulate communication configuration data and components into plugins.

104. The client APP loads the plug-in into the plug-in environment, and loads components in the plug-in through the plug-in environment.

Specifically, the client APP loads the plug-in into the plug-in environment, and the process can be:

Load communication configuration data into the plug-in environment;

According to the communication configuration data, set the communication mechanism between the component and the data layer.

The client APP loads the components in the plug-in through the plug-in environment. The process can be:

The client APP loads components.

Among them, the client APP loads components, the process can be:

After the user loading event is detected, the component is loaded, and after the loading is completed, the client APP is run;

Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the duration of the user's continuous clicking on the interface meeting a threshold.

The embodiment of the present invention provides a plug-in update method. The plug-in is loaded into the plug-in environment through the client APP, and the components in the plug-in are loaded through the plug-in environment, which avoids updating the client by downloading and installing the APP, thereby saving system resources. Processing resources and running resources improves user experience.

Embodiment 2 is a plug-in update method provided by the embodiment of the present invention, as shown in FIG. 2 , the method includes:

201. The server confirms the functions to be loaded by the client APP.

Specifically, through at least one of the following operations, the server confirms the functions to be loaded by the client APP, and the process may include:

A. Obtain the loading request triggered by the user on the client APP, and confirm the functions to be loaded by the client APP according to the loading request. The process can be:

Obtain the function addition request input by the user on the client APP function selection interface; wherein, the function addition request includes at least the function selected by the user and the personalized settings for the selected function, and the process can be:

Obtain any one of the gesture, voice and text data triggered by the user on the function selection interface; wherein, the gesture includes but is not limited to the user clicking on the icon used to indicate the function and at least the gesture track of the icon; the voice or text data is at least include keywords used to describe the functionality indicated by the user;

After obtaining at least the icon gesture trajectory triggered by the user on the function selection interface, the above client APP obtains the function addition request triggered by the user can be:

The gesture track and the icons included in the gesture track are identified, and the embodiment of the present invention does not limit the specific identification manner.

After obtaining the voice or text data triggered by the user on the function selection interface, the above client APP obtains the function addition request triggered by the user can be:

The voice or text data is analyzed and recognized, and the embodiment of the present invention does not limit the specific analysis or recognition manner.

Exemplarily, in order to further illustrate the method of the embodiment of the present invention, it is assumed that the function selection interface is as shown in a in FIG. 3 , and the user can click the icon in a in FIG. As shown in b, the user can also select the indicated function by inputting a gesture track that includes at least an icon. The gesture track can be shown in c in FIG. function, wherein, the voice input interface and the text input interface can refer to d in FIG. 3 and e in FIG. 3 .

B. After the client APP detects the update, according to the update request sent by the client APP, confirm the functions to be loaded by the client APP. The embodiment of the present invention does not limit the specific update detection method.

202. According to the function name in the registration module, select a component corresponding to the function to be loaded from multiple components included in the executable file group.

Specifically, the registration module can be a module registered by APPRegister in the IOS system, the executable file can be a JSBundle, and the process can be:

According to the description data of the function, select the component corresponding to the function to be loaded from the multiple components contained in the executable file group, the description data includes but not limited to the definition data of the function, the interaction realization data and the operation realization data.

203. The server loads the component into the plug-in.

Specifically, the process may include:

Set the communication configuration data between the component and the data layer. The communication configuration data can be the data resource calling method between the plug-in interface and the data layer.

Encapsulating the communication configuration data and components into a plug-in, the process may be to bind the components and communication configuration data to the plug-in according to the system information of the client APP. The embodiment of the present invention does not limit the specific binding method.

204. The server sends the plug-in to the client APP.

Specifically, the embodiment of the present invention does not limit the specific sending manner.

205. The client APP loads the plug-in into the plug-in environment.

Specifically, the process may include:

Load the communication configuration data into the plug-in environment, the process can be:

According to the configuration information, set the corresponding relationship between the functions in the registration module and the plug-in

According to the configuration information, set the data resource calling method between the plug-in interface and the data layer

According to the communication configuration data, set the communication mechanism between the component and the data layer, the process can be:

According to the configuration information, set the corresponding relationship between the functions in the registration module and the plug-in

According to the configuration information, set the data resource calling method between the plug-in interface and the data layer.

206. The client APP loads a component.

Specifically, the process can be:

After the user loading event is detected, the component is loaded, and after the loading is completed, the client APP is run;

Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the user continuing to click on the interface for a time that satisfies a threshold, and the user inputting a preset gesture includes the user inputting a sliding gesture in a preset direction.

After the loading event is detected, the loading interface is displayed, and after the client APP loads the component, the loading interface is closed.

Exemplarily, in order to further illustrate the method of the embodiment of the present invention, assume that the user clicks a preset button, as shown in a in FIG. 4, and the displayed loading interface can be shown in FIG. Different display modes can be set according to the loading progress. The user can input preset gestures as shown in b in FIG. 4 , and the displayed loading interface can refer to FIG. 5 .

It is worth noting that steps 205 to 206 are the process of realizing that the client APP loads the plug-in to the plug-in environment and loads the components in the plug-in through the plug-in environment. In addition to the above steps, this process can also be realized in other ways , the embodiment of the present invention does not limit the specific manner.

The embodiment of the present invention provides a plug-in update method. The plug-in is loaded into the plug-in environment through the client APP, and the components in the plug-in are loaded through the plug-in environment, which avoids updating the client by downloading and installing the APP, thereby saving system resources. Processing resources and running resources improves user experience.

Embodiment 3 is a kind of server 6 provided by the embodiment of the present invention, as shown in FIG. 6, the server 6 includes:

Confirmation module 61, is used for confirming the function that client APP will load;

The first loading module 62 is used to load components corresponding to functions from the registration module;

The second loading module 63 is used to load the component into the plug-in;

The sending module 64 is configured to send the plug-in to the client APP, so that the client APP loads the plug-in into the plug-in environment, and loads components in the plug-in through the plug-in environment.

Optionally, the confirmation module 61 includes:

Obtaining sub-module 611, configured to obtain the loading request triggered by the user on the client APP;

The first confirmation submodule 612 is used to confirm the function to be loaded by the client APP according to the loading request;

The second confirmation submodule 613 is configured to confirm the functions to be loaded by the client APP according to the update request sent by the client APP after the client APP detects the update.

Optionally, the first loading module 62 is specifically used for:

According to the function name in the registration module, the component corresponding to the function to be loaded is selected from the multiple components contained in the executable file group.

Optionally, the second loading module 63 includes:

The communication configuration data setting sub-module 631 is used to set the communication configuration data of the component and the data layer;

The encapsulation sub-module 632 is used for encapsulating the communication configuration data and components into the plug-in.

The embodiment of the present invention provides a server, the server loads the plug-in to the plug-in environment through the client APP, and loads the components in the plug-in through the plug-in environment, avoiding the update of the client by downloading and installing the APP, thereby saving System processing resources and operating resources improve user experience.

Embodiment 4 is a client 7 provided by an embodiment of the present invention. Referring to FIG. 7, the client 7 includes:

The sending module 71 is used to send the function to be loaded to the server, so that the server can confirm the function, load the component corresponding to the function from the registration module, and load the component to the plug-in;

The receiving module 72 is used to receive the plug-in sent by the server;

The first loading module 73 is used to load the plug-in into the plug-in environment;

The second loading module 74 is configured to load components in the plug-in through the plug-in environment.

Optionally, the sending module 71 includes:

The first sending sub-module 711 is used to send the loading request triggered by the user to the server;

A detection submodule 712, configured to detect updates;

The second sending sub-module 713 is configured to send an update request to the server after the detection sub-module detects the update.

Optionally, the first loading module 73 is specifically used for:

Load communication configuration data into the plug-in environment;

According to the communication configuration data, set the communication mechanism between the component and the data layer.

Optionally, the second loading module 74 includes:

The loading submodule 741 is used for loading components.

Optionally, the loading submodule 741 is specifically used for:

After detecting the user loading event, load the component, and run the APP after the loading is complete;

Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the duration of the user's continuous clicking on the interface meeting a threshold.

The embodiment of the present invention provides a client, the client loads the plug-in to the plug-in environment through the client APP, and loads the components in the plug-in through the plug-in environment, avoiding the update of the client by downloading and installing the APP, thereby saving System processing resources and operating resources improve user experience.

Embodiment 5 is a server 8 provided by an embodiment of the present invention. Referring to FIG. 8, the server 8 includes a memory 81 and a processor 82 connected to the memory 81, wherein the memory 81 is used to store a set of program codes , the processor 82 calls the program code stored in the memory 81 to perform the following operations:

Confirm the functions to be loaded by the client APP;

Load the component corresponding to the function from the registration module;

load the component into the plugin;

Send the plug-in to the client APP, so that the client APP loads the plug-in into the plug-in environment, and loads the components in the plug-in through the plug-in environment.

Optionally, the processor 82 calls the program code stored in the memory 81 to perform the following operations:

Obtain the loading request triggered by the user on the client APP;

According to the loading request, confirm the functions to be loaded by the client APP; or

After the client APP detects the update, it confirms the functions to be loaded by the client APP according to the update request sent by the client APP.

Optionally, the processor 82 calls the program code stored in the memory 81 to perform the following operations:

According to the function name in the registration module, the component corresponding to the function to be loaded is selected from the multiple components contained in the executable file group.

Optionally, the processor 82 calls the program code stored in the memory 81 to perform the following operations:

Set the communication configuration data between the component and the data layer;

Encapsulate communication configuration data and components into plugins.

The embodiment of the present invention provides a server, the server loads the plug-in to the plug-in environment through the client APP, and loads the components in the plug-in through the plug-in environment, avoiding the update of the client by downloading and installing the APP, thereby saving System processing resources and operating resources improve user experience.

Embodiment 6 is a client 9 provided by the embodiment of the present invention. Referring to FIG. 9, the client 9 includes a memory 91 and a processor 92 connected to the memory 91, wherein the memory 91 is used to store a set of program codes , the processor 92 calls the program code stored in the memory 91 to perform the following operations:

Send the function to be loaded to the server, so that the server can confirm the function, load the component corresponding to the function from the registration module, and load the component to the plug-in;

Receive the plug-in sent by the server;

Load the plugin into the plugin environment;

Components in the plugin are loaded through the plugin environment.

Optionally, the processor 92 calls the program code stored in the memory 91 to perform the following operations:

Send a user-triggered loading request to the server; or

After an update is detected, an update request is sent to the server.

Optionally, the processor 92 calls the program code stored in the memory 91 to perform the following operations:

Load communication configuration data into the plug-in environment;

According to the communication configuration data, set the communication mechanism between the component and the data layer.

Optionally, the processor 92 calls the program code stored in the memory 91 to perform the following operations:

Load the component.

Optionally, the processor 92 calls the program code stored in the memory 91 to perform the following operations:

After detecting the user loading event, load the component, and run the APP after the loading is complete;

Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the duration of the user's continuous clicking on the interface meeting a threshold.

The embodiment of the present invention provides a client, the client loads the plug-in to the plug-in environment through the client APP, and loads the components in the plug-in through the plug-in environment, avoiding the update of the client by downloading and installing the APP, thereby saving System processing resources and operating resources improve user experience.

Embodiment 7 is a plug-in update system 10 provided by the embodiment of the present invention. Referring to FIG. 10 , the system 10 includes a server 101 and a client 102;

Server 101 includes:

Confirmation module 1011, used to confirm the functions to be loaded by the client APP;

The first loading module 1012 is configured to load components corresponding to functions from the registration module;

The second loading module 1013 is used to load the component into the plug-in;

The first sending module 1014 is configured to send the plug-in to the client APP, so that the client APP loads the plug-in into the plug-in environment, and loads components in the plug-in through the plug-in environment;

Client 102 includes:

The second sending module 1021 is used to send the function to be loaded to the server, so that the server can confirm the function, load the component corresponding to the function from the registration module, and load the component to the plug-in;

The receiving module 1022 is used to receive the plug-in sent by the server;

The third loading module 1023 is used to load the plug-in into the plug-in environment;

The fourth loading module 1024 is configured to load components in the plug-in through the plug-in environment.

Optionally, the confirmation module 1011 includes:

The acquisition sub-module 10111 is used to acquire the loading request triggered by the user on the client APP;

The first confirmation submodule 10112 is used to confirm the function to be loaded by the client APP according to the loading request;

The second confirmation submodule 10113 is used to confirm the functions to be loaded by the client APP according to the update request sent by the client APP after the client APP detects the update;

The second sending module 1021 includes:

The first sending sub-module 10211 is used to send the loading request triggered by the user to the server;

The detection sub-module 10212 is used to detect and update;

The second sending sub-module 10213 is configured to send an update request to the server after the detection sub-module detects the update.

Optionally, the first loading module 1012 is specifically used for:

According to the function name in the registration module, the component corresponding to the function to be loaded is selected from the multiple components contained in the executable file group.

Optionally, the second loading module 1013 includes:

The communication configuration data setting sub-module 10131 is used to set the communication configuration data of components and data layers;

The encapsulation sub-module 10132 is used for encapsulating the communication configuration data and components into the plug-in.

Optionally, the third loading module 1023 is specifically used for:

Load communication configuration data into the plug-in environment;

According to the communication configuration data, set the communication mechanism between the component and the data layer.

Optionally, the fourth loading module 1024 includes:

Load submodule 10241, used to load components.

Optionally, the loading submodule 10241 is specifically used for:

After detecting the user loading event, load the component, and run the APP after the loading is complete;

Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the duration of the user's continuous clicking on the interface meeting a threshold.

The embodiment of the present invention provides a plug-in update system, the system loads the plug-in to the plug-in environment through the client APP, and loads the components in the plug-in through the plug-in environment, avoiding the update of the client by downloading and installing the APP, thereby saving System processing resources and operating resources improve user experience.

All the above optional technical solutions can be combined in any way to form an optional embodiment of the present invention, which will not be repeated here.

It should be noted that when the server, client and system provided in the above embodiments execute the plug-in update method, the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned functions can be assigned by different The functional modules are completed, that is, the server, client and the internal structure of the system are divided into different functional modules to complete all or part of the functions described above. In addition, the server, client, system, and plug-in update method embodiments provided in the above embodiments belong to the same idea, and the specific implementation process thereof is detailed in the method embodiments, and will not be repeated here.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above embodiments can be completed by hardware, and can also be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned The storage medium mentioned may be a read-only memory, a magnetic disk or an optical disk, and the like.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection of the present invention. within range.

Claims (10)

1. A plug-in update method, characterized in that the method comprises: The server confirms the functions to be loaded by the client APP; The server loads components corresponding to the functions from the registration module; The server loads the component into a plug-in, and sends the plug-in to the client APP; The client APP loads the plug-in into a plug-in environment, and loads components in the plug-in through the plug-in environment. 2. The method according to claim 1, characterized in that the step of the server confirming the function to be loaded by the client APP is realized by at least one of the following operations: Obtain a loading request triggered by the user on the client APP, and confirm the function to be loaded by the client APP according to the loading request; or After the client APP detects the update, according to the update request sent by the client APP, confirm the functions to be loaded by the client APP. 3. The method according to claim 2, wherein the loading of the component corresponding to the function by the server from the registration module includes: According to the function name in the registration module, the component corresponding to the function to be loaded is selected from a plurality of components included in the executable file group. 4. The method according to claim 3, wherein loading the component to the plug-in by the server comprises: Setting communication configuration data between the component and the data layer; Encapsulating the communication configuration data and the component into the plug-in. 5. The method according to claim 4, wherein the client APP loading the plug-in to the plug-in environment comprises: Loading the communication configuration data into the plug-in environment; According to the communication configuration data, a communication mechanism between the component and the data layer is set. 6. The method according to claim 5, wherein loading the components in the plug-in by the client APP through the plug-in environment comprises: The client APP loads the component. 7. The method according to claim 6, wherein loading the component by the client APP comprises: After the user loading event is detected, the component is loaded, and after the loading is completed, the client APP is run; Wherein, the loading event includes the user clicking a preset button, the user inputting a preset gesture, and the duration of the user's continuous clicking on the interface meeting a threshold. 8. A server, characterized in that the server includes: The confirmation module is used to confirm the functions to be loaded by the client APP; The first loading module is configured to load components corresponding to the functions from the registration module; a second loading module, configured to load the component into the plug-in; A sending module, configured to send the plug-in to the client APP, so that the client APP loads the plug-in into a plug-in environment, and loads components in the plug-in through the plug-in environment. 9. A client, characterized in that the client includes: A sending module, configured to send the function to be loaded to the server, so that the server can confirm the function, load the component corresponding to the function from the registration module, and load the component to the plug-in; A receiving module, configured to receive the plug-in sent by the server; The first loading module is used to load the plug-in into the plug-in environment; The second loading module is used to load the components in the plug-in through the plug-in environment. 10. A plug-in update system, characterized in that the system includes a server and a client: The server includes: The confirmation module is used to confirm the functions to be loaded by the client APP; The first loading module is configured to load components corresponding to the functions from the registration module; a second loading module, configured to load the component into the plug-in; A first sending module, configured to send the plug-in to the client APP, so that the client APP loads the plug-in into a plug-in environment, and loads components in the plug-in through the plug-in environment; The clients include: The second sending module is used to send the function to be loaded to the server, so that the server can confirm the function, load the component corresponding to the function from the registration module, and load the component to the plug-in; A receiving module, configured to receive the plug-in sent by the server; The third loading module is used to load the plug-in into the plug-in environment; The fourth loading module is used to load the components in the plug-in through the plug-in environment.