CN116483466A

CN116483466A - Plug-in acquisition method, device, equipment and storage medium

Info

Publication number: CN116483466A
Application number: CN202310361981.1A
Authority: CN
Inventors: 王铭喜; 苍鹏; 陈斌; 唐堃
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2023-04-06
Filing date: 2023-04-06
Publication date: 2023-07-25

Abstract

The disclosure relates to a plug-in acquisition method, a plug-in acquisition device, electronic equipment and a storage medium. The method comprises the following steps: responding to a plug-in preloading request initiated by a client, and acquiring user account operation data associated with the client; the user account operational data includes operational data of a user account associated with the client for application functions installed in the client; determining at least two function plugins associated with application function requirements of a user account and installation priorities of the function plugins according to user account operation data; and according to the installation priority of each function plug-in, sequentially returning the data resources of each function plug-in to the client for the client to install each function plug-in. The present disclosure may optimize the efficiency with which a user obtains a desired functional plug-in.

Description

Plug-in acquisition method, device, equipment and storage medium

Technical Field

The disclosure relates to the field of computer technology, and in particular, to a method and device for obtaining a plug-in, an electronic device and a storage medium.

Background

With the development of computer technology and the continuous expansion of mobile application functions, the volume of application installation packages is also continuously increased.

In the related art, in order to reduce the reference to the application installation package, various function codes of an application are respectively designed into corresponding function plug-ins, and when a user needs to use a certain function, the corresponding function plug-ins are downloaded and installed. However, this approach often requires a user to wait a period of time to acquire the function plug-in and use the related functions, which has a problem of low plug-in acquisition efficiency.

Disclosure of Invention

The disclosure provides a method, a device, an electronic device and a storage medium for obtaining a plug-in, so as to at least solve the problem of low plug-in obtaining efficiency in the related art. The technical scheme of the present disclosure is as follows:

according to a first aspect of an embodiment of the present disclosure, there is provided a plug-in obtaining method, including:

responding to a plug-in preloading request initiated by a client, and acquiring user account operation data associated with the client; the user account operational data includes operational data of a user account associated with the client for application functions installed in the client;

determining at least two function plugins associated with application function requirements of the user account and installation priorities of the function plugins according to the user account operation data;

And according to the installation priority of each function plug-in, returning the data resource of each function plug-in to the client in turn, wherein the data resource is used for the client to install each function plug-in.

In one embodiment, the obtaining user account operational data associated with the client comprises:

inquiring an access record of a user account corresponding to the account identifier to an application interface in the client based on the account identifier carried in the plug-in preloading request; each application interface is associated with at least one application function of the client;

and acquiring user account operation data of the user account based on the access record.

In one embodiment, the obtaining the user account operation data of the user account based on the access record includes:

and generating user account operation data of the user account based on the access record of the user account to the application interfaces in the client and the browsing duration of each application interface.

In one embodiment, the determining, according to the user account operation data, at least two function plugins associated with the application function requirement of the user account and the installation priority of each function plugin includes:

Extracting features of the user account operation data and account attribute information of the user account, and acquiring portrait features of the user account based on feature extraction results;

inputting the portrait features into a trained functional plug-in predictive model to obtain a model predictive result; the model prediction result comprises at least two function plugins associated with application function requirements of the user account and installation priorities of the function plugins;

the trained functional plug-in prediction model is obtained by training an initial functional plug-in prediction model based on portrait features of a plurality of sample user accounts and corresponding labels; the tag comprises the installation priority of the at least two function plug-ins.

In one embodiment, the sequentially returning, to the client, the data resources of each functional plugin according to the installation priority of each functional plugin includes:

determining a basic plug-in to be loaded of the client;

determining the installation sequence of the basic plug-in and the functional plug-in based on the importance degree of the basic plug-in and the installation priority of each functional plug-in; the installation priority among the functional plug-ins in the installation sequence is unchanged;

And returning the data resources of the basic plug-ins and the data resources of the functional plug-ins to the client according to the installation sequence.

returning the installation priority of each functional plug-in to the client so as to instruct the client to sequentially send a downloading request for the corresponding functional plug-in to a server according to the installation priority of each functional plug-in;

and returning the data resources of the functional plugin aimed at by the download request to the client based on the received download request.

According to a second aspect of the embodiments of the present disclosure, there is provided a plug-in obtaining method, including:

sending a plug-in preloading request to a server; the plug-in preloading request is used for indicating the server to acquire user account operation data associated with a client, and determining at least two function plug-ins associated with application function requirements of the user account and installation priorities of the function plug-ins according to the account behavior data; the user account operation data comprises operation data of the user account associated with the client for implementing the application function installed in the client;

And acquiring the data resources of the function plugins returned by the server according to the installation priority of the function plugins so as to install the function plugins.

In one embodiment, the obtaining the data resource of each functional plugin returned by the server according to the installation priority of each functional plugin includes:

receiving the installation priority of each functional plug-in unit returned by the service end;

and according to the installation priority of each function plug-in, sequentially sending a downloading request for the corresponding function plug-in to the server, and acquiring the data resource of the function plug-in returned by the server after responding to the downloading request.

In one embodiment, the sending a plug-in preloading request to the server includes:

and sending a plug-in preloading request to the server in the cold start stage of the client.

According to a third aspect of the embodiments of the present disclosure, there is provided a card acquisition apparatus including:

an operation data acquisition unit configured to perform acquisition of user account operation data associated with a client in response to a plug-in preloading request initiated by the client; the user account operational data includes operational data of a user account associated with the client for application functions installed in the client;

A priority determining unit configured to perform determining, according to the user account operation data, installation priorities of at least two function plugins and each of the function plugins associated with application function requirements of the user account;

and the plug-in resource providing unit is configured to execute the data resources of the function plug-ins to be returned to the client in turn according to the installation priority of the function plug-ins, and is used for the client to install the function plug-ins.

In one embodiment, the operation data acquisition unit includes:

the access record inquiring module is configured to execute inquiring the access record of the user account corresponding to the account identifier to the application interface in the client based on the account identifier carried in the plug-in preloading request; each application interface is associated with at least one application function of the client;

and the operation data determining module is configured to execute the user account operation data of the user account acquired based on the access record.

In one embodiment, the operation data determination module is configured to perform:

In one embodiment, the priority determining unit is configured to perform:

In one embodiment, the plug-in resource providing unit is configured to perform:

determining a basic plug-in to be loaded of the client;

According to a fourth aspect of the embodiments of the present disclosure, there is provided a card acquisition apparatus including:

a request sending unit configured to perform sending of a plug-in preloading request to a server; the plug-in preloading request is used for indicating the server to acquire user account operation data associated with a client, and determining at least two function plug-ins associated with application function requirements of the user account and installation priorities of the function plug-ins according to the account behavior data; the user account operation data comprises operation data of the user account associated with the client for implementing the application function installed in the client;

And the plug-in resource acquisition unit is configured to acquire the data resources of the function plug-ins returned by the server according to the installation priority of the function plug-ins so as to install the function plug-ins.

In one embodiment, the plug-in resource acquisition unit is configured to perform:

In one embodiment, the request sending unit is configured to perform:

According to a fifth aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the method of any one of the above.

According to a sixth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the method as set forth in any one of the preceding claims.

According to a seventh aspect of embodiments of the present disclosure, there is provided a computer program product comprising instructions therein, which when executed by a processor of an electronic device, enable the electronic device to perform the method as set forth in any one of the preceding claims.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

in the method, on one hand, the client actively initiates the plug-in preloading request, and triggers the server to provide data resources of a plurality of function plug-ins for the client, so that the client installs each function plug-in advance, the situation that a user loads related plug-ins when the plug-ins are needed can be avoided, waiting time is reduced, on the other hand, the user can individually and accurately predict the function plug-ins needed by the user and arrange the installation priorities of the function plug-ins based on user account operation data, the user can finish the installation of the function plug-ins more needed by the user preferentially, and the efficiency of the user for obtaining the needed function plug-ins is optimized.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.

Fig. 1 is an application environment diagram illustrating a plug-in acquisition method according to an exemplary embodiment.

Fig. 2 is a flow chart illustrating a plug-in acquisition method according to an example embodiment.

FIG. 3 is a flowchart illustrating another plug-in acquisition method according to an example embodiment.

Fig. 4 is a timing diagram illustrating a plug-in acquisition method according to an example embodiment.

Fig. 5 is a block diagram illustrating a plug-in acquisition device according to an example embodiment.

Fig. 6 is a block diagram of another plug-in acquisition device, shown according to an example embodiment.

Fig. 7 is a block diagram of an electronic device, according to an example embodiment.

Fig. 8 is a block diagram of another electronic device, shown in accordance with an exemplary embodiment.

Detailed Description

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

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

It should be further noted that, the user information (including, but not limited to, user equipment information, user personal information, etc.) and the data (including, but not limited to, data for presentation, analyzed data, etc.) related to the present disclosure are information and data authorized by the user or sufficiently authorized by each party.

The plug-in acquisition method provided by the disclosure can be applied to an application environment as shown in fig. 1. In this application environment, a client may communicate with a server through a network. The server may have a corresponding data storage system, where the data storage system may store data that needs to be processed by the server, for example, a plug-in associated with the client or related data resources of a plug-in associated with the client, and in practical application, the data storage system may be integrated on the server, or may be placed on a cloud or other network server.

In the present disclosure, before a user account actively triggers the installation of a plug-in, a client may send a plug-in preloading request to a server in advance; in response to a plug-in preloading request initiated by a client, the server may obtain user account operation data associated with the client, which may include operation data of a user account associated with the client for application functions installed in the client; and the server side can determine at least two function plugins related to the application function requirement of the user account and the installation priority of each function plugin according to the user account operation data, and sequentially return the data resources of each function plugin to the client side according to the installation priority of each function plugin so as to enable the client side to install each function plugin subsequently.

The client can be deployed on a terminal, the terminal can be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things equipment and portable wearable equipment, and the internet of things equipment can be an intelligent sound box, an intelligent television, an intelligent air conditioner, intelligent vehicle-mounted equipment and the like; the portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server may be implemented by a stand-alone server or a server cluster formed by a plurality of servers.

Fig. 2 is a flowchart of a plug-in obtaining method according to an exemplary embodiment, and as shown in fig. 2, the method is applied to a server side for explanation, and may include the following steps.

In step S210, user account operation data associated with the client is obtained in response to the plug-in preloading request initiated by the client; the user account operational data includes operational data that a user account associated with the client implements for installed application functions in the client.

The user account may be an account held by a user using the client, and may be represented by information having an identifier, for example, a pre-allocated account identifier, or a terminal identifier corresponding to a terminal on which the client is installed.

The client may refer to a client deployed on a terminal, and the client may be one client deployed on the terminal or may be multiple clients deployed in the terminal.

In this embodiment, the client may trigger the installation of the plug-in advance, that is, the client may actively trigger the preloading of the client plug-in advance before detecting an operation event of loading the client related plug-in actively triggered by the user account (e.g., when detecting that the user account actively sends an installation request for a preset plug-in or a preset type plug-in).

Specifically, before receiving an installation request of a user account for a preset plugin (the preset plugin may be specified by the user account), the client may send a plugin preloading request to the server, so as to trigger the server to provide a data resource of a related plugin, so that the client performs preloading and installation of the plugin in advance before the user account actively downloads the plugin.

In response to a client-initiated plug-in preload request, the server may determine a user account associated with a current client and take account operational data of the user account as user account operational data associated with the client. The user account operation data includes operation data of the user account for implementing the application function installed in the client, specifically, in practical application, when the user account implements related user operation on the application function installed in the client, recording may be performed to obtain the user account operation data, and the user account operation data is stored, where the user account operation data may reflect the use condition or the dependency degree of the user account on the application function installed in the client.

In an alternative embodiment, the user account operation data associated with the client may include user account operation data of the client for which the add-in preload request is directed, and may also include user account operation data of one or more other clients on the terminal, for example, the add-in preload request is initiated by the client a to the server, where the server may acquire user account operation data of the client a itself and may acquire user account operation data of the client B in addition to user account operation data of the client a, and the client a and the client B may be the same type of client, for example, both be video publishing type clients or instant messaging type clients, and of course, the client a and the client B may also be different types of clients.

In step S220, at least two function plugins associated with the application function requirement of the user account and the installation priority of each function plugin are determined according to the user account operation data.

As an example, the application function requirements may characterize the application functions that the user account needs to use, which may include the application functions that the application account currently needs, as well as application functions that the application account expects may need.

The installation priority of the function plug-ins may indicate an installation order of each of the plurality of function plug-ins.

In this step, after obtaining the operation data of the user account, because the operation data of the user account includes operation data of the user account for implementing the application function installed on the client, the server may obtain, based on the operation data of the user account, a use condition of the user account for the application function installed on the client, and identify an application function requirement of the user account based on the use condition.

And then according to the user account operation data, the server side can determine at least two function plug-ins and the installation priority of each function plug-in associated with the application function requirement of the user account. Wherein each of the at least two functional inserts may correspond to an application function, respectively, for example, for image capturing, an image filter insert and an image super processing insert may be determined.

In some embodiments, the user account may perform corresponding operations on a plurality of application functions installed on the client, through the user account operation data, in addition to determining that the application functions required to be used by the user account (may include being used or expecting to be possibly used), the requirement level or the dependency level of the user account on each application function required to be used may also be determined, for example, in the plurality of application functions installed on the client, a part of the application functions is frequently used by the user account, another part of the application functions are not used for a long time by the user account, the requirement level of the application account on each function plug-in may be predicted based on the use duration or the use frequency of the application functions by the user account, and the installation priority of each function plug-in may be determined according to the requirement level.

In step S230, the data resources of each function plug-in are sequentially returned to the client according to the installation priority of each function plug-in, so that the client can install each function plug-in.

As an example, the data resource of the function plugin may be an installation package of the function plugin, or may be an acquisition path of the function plugin, such as a download address of the function plugin.

After the installation priority of the plurality of function plugins is obtained, the server side can sequentially return the data resources of the function plugins to the client side according to the installation priority, so that the client side can preferentially install the function plugins with higher installation priority, the user account can preferentially obtain the function plugins with higher demand or higher dependence degree of application functions, and the user can rapidly and accurately provide the function plugins really required by the user while avoiding waiting for downloading and installing the plugins.

In the plug-in obtaining method, in response to a plug-in preloading request initiated by a client, a server may obtain user account operation data associated with the client, where the user account operation data may include operation data implemented by a user account associated with the client on an application function installed in the client; and the installation priority of at least two function plugins and each function plugin associated with the application function requirement of the user account can be determined according to the user account operation data, and the data resources of each function plugin are sequentially returned to the client according to the installation priority of each function plugin so as to enable the client to install each function plugin. In the method, on one hand, the client actively initiates the plug-in preloading request, and triggers the server to provide data resources of a plurality of function plug-ins for the client, so that the client installs each function plug-in advance, the situation that a user loads related plug-ins when the plug-ins are needed can be avoided, waiting time is reduced, on the other hand, the user can individually and accurately predict the function plug-ins needed by the user and arrange the installation priorities of the function plug-ins based on user account operation data, the user can finish the installation of the function plug-ins more needed by the user preferentially, and the efficiency of the user for obtaining the needed function plug-ins is optimized.

In addition, through the method and the device, the function plug-in which is not used by the user can be prevented from being installed and downloaded, waste of limited bandwidth resources is reduced, and the utilization rate of network resources is improved.

In an exemplary embodiment, in step S210, acquiring user account operation data associated with a client may include the steps of:

in step S310, based on the account identifier carried in the plug-in preloading request, querying an access record of the user account corresponding to the account identifier to the application interface in the client; each application interface is associated with at least one application function of the client.

The client can be provided with different application interfaces, and a user can trigger corresponding application functions through the different application interfaces. For example, the client may be provided with an application interface for publishing media resources, and after the client displays the application interface, the user may edit the media resources to be published in the application interface and publish the media resources; for another example, the client may be provided with an application interface for browsing media resources, and after the client displays the application interface, the user may browse media resources published by others.

In practical application, after obtaining a plug-in preloading request initiated by a client, an account identifier can be read from the plug-in preloading request, and access records of a user account corresponding to the account identifier to one or more application interfaces in the client are queried. Specifically, for example, after a user account enters an application interface of a client, the client may acquire an access record of the user account for a current application interface and return the access record to a server, and the server may store the access record in association with an account identifier of the user account, so that after receiving a plug-in preloading request carrying the account identifier, the client may query the access record of the corresponding user account for the application interface based on the account identifier.

In step S320, user account operation data of the user account is acquired based on the access record.

After obtaining the access record of the user account to one or more application interfaces in the client, the server may determine that the user account browses through the application interfaces based on the access record, thereby determining operation data of the user account based on the access record.

In this embodiment, corresponding application functions may be associated with different application interfaces in the client, and by querying an access record of the user account corresponding to the account identifier to the application interface in the client, the application function focused by the user and the user account operation data may be obtained quickly, so as to provide a basis for determining the function plugin required by the user subsequently.

In an exemplary embodiment, in step S320, user account operation data of a user account is acquired based on an access record:

In a specific implementation, after the access record of the user account to the application interface in the client is obtained, for each application interface browsed by the user account, the browsing duration of the application interface may also be obtained, where the browsing duration may represent the residence time of the user in the application interface corresponding to the browsing duration, and the browsing duration reflects the attention degree or the dependency degree of the user account on the application function associated with the application interface, and in some examples, the browsing duration may be positively related to the attention degree or the dependency degree of the user account on the application function in the application interface.

And obtaining the access record of the application interface of the user account and the browsing time length of each accessed application interface, and obtaining the user account operation data of the user account based on the access record and the browsing time length of the application interface. Of course, in other embodiments, in addition to obtaining the browsing duration of the application interface, the browsing frequency of the application interface may be obtained, and the user account operation data may be obtained based on the access record of the application interface and the browsing duration and/or the browsing frequency.

In this embodiment, the user account operation data may also be generated based on the browsing duration of the user on the application interface, so that the user may further combine the browsing duration of the user on the application interface to determine the priority of the functional plugin and the functional plugin required by the user.

In an exemplary embodiment, in step S220, determining at least two function plugins associated with the application function requirement of the user account and the installation priority of each function plugin according to the user account operation data may include the steps of:

in step S410, feature extraction is performed on the user account operation data and the account attribute information of the user account, and portrait features of the user account are acquired based on the feature extraction result.

In practical application, account attribute information of the user account can be obtained, wherein the account attribute information can represent account attributes corresponding to the user account, for example, the account attribute information can include account names.

After the account attribute information of the user account is obtained, feature extraction can be performed on the user account operation data and the account attribute information, and portrait features of the current user account are obtained based on feature extraction results. The feature extraction may be understood as feature screening, and extracts information associated with a subsequent model prediction from user account operation data and account basic information.

In step S420, the portrait features are input into a trained functional plug-in prediction model to obtain a model prediction result; the model forecast results include at least two function plugins associated with the application function requirements of the user account and installation priorities of the respective function plugins.

The trained functional plug-in prediction model is obtained by training the initial functional plug-in prediction model based on portrait features of a plurality of sample user accounts and corresponding labels; the tag comprises the installation priority of at least two function plugins, and the at least two function plugins can comprise the function plugins which are subsequently issued to the client.

Specifically, the portrait features of the sample user accounts and the labels with the installation priorities of the functional plugins can be used in advance to conduct supervision training on the initial functional plugin prediction model, specifically, for example, the portrait features of the sample user accounts can be input into the initial functional plugin prediction model, the installation priorities of the functional plugins and the functional plugins associated with the sample user accounts can be predicted by the model based on the portrait features of the input sample user accounts, and further, a model loss value can be determined according to differences (such as differences of the functional plugins and differences of the installation priorities) of the installation priorities of the functional plugins in the labels, and model parameters of the functional plugin prediction model can be adjusted according to the model loss value until training end conditions are met, so that a trained functional plugin prediction model is obtained.

Further, after obtaining the portrait features of the user account, the portrait features may be input into a trained functional plugin prediction model to obtain a model prediction result, where the model prediction result may include at least two functional plugins associated with application functional requirements of the user account and installation priorities of the functional plugins.

In this embodiment, the functional plugins required by the user may be predicted by pre-training a functional plugin prediction model and combining with various portrait features of the user account, so that accuracy of installation priorities of the functional plugins obtained by final prediction may be effectively improved.

In an exemplary embodiment, in step S230, sequentially returning, to the client, the data resources of each function plugin according to the installation priority of each function plugin may include:

in step S510, the base plug-in to which the client is to be loaded is determined.

The basic plug-in can comprise a plug-in associated with normal running of the client, and the plug-in needs to be downloaded by using each application account of the client; the base plug-in may also include a pre-set fixed plug-in, in some examples, for example, the user account operation data of the user account is not acquired for the newly registered user account, or it is difficult to determine a specific functional plug-in based on the user account operation data, and the pre-set plug-in may be returned to the client, and illustratively, the pre-set plug-in may be a plug-in whose download heat satisfies the condition (the download number is greater than the threshold or one or more plug-ins whose download number is highest).

After receiving the plug-in preloading request sent by the client, the basic plug-in to be loaded by the client can be determined.

In step S520, the installation order of the base plug-ins and the function plug-ins is determined based on the importance degree of the base plug-ins and the installation priority of each function plug-in; the installation priority among the function plug-ins in the installation sequence is unchanged.

Specifically, after determining the basic plugin, the importance degree of the basic plugin can also be obtained, for example, if the basic plugin is a plugin associated with normal operation of the client, the basic plugin can be downloaded first, and if the basic plugin is a preset fixed plugin, the installation can be delayed. Based on this, after the importance degree of each basic plug-in is obtained, since the importance degree of the basic plug-in may affect the installation order of the function plug-ins, for example, the installation priority of the basic plug-in associated with the normal operation of the client may be higher than that of the function plug-in, so the importance degree of the basic plug-in and the installation priority of the function plug-in may be collected, the installation order of the basic plug-in and the function plug-in may be redetermined, and the installation priority among the function plug-ins in the installation order may be unchanged, but the installation order of the function plug-ins may be changed.

Specifically, for example, the installation priority of the determined function plug-ins A, B, C is sequentially reduced, the original installation order is a→b→c, and if the base plug-ins include the base plug-in C associated with the normal operation of the client and the preset base plug-in D, the installation order may be modified to c→a→b→c→d.

In step S530, the data resources of the base plug-in and the data resources of the function plug-ins are returned to the client in the installation order.

After the installation sequence is acquired, the server side can return the data resources of the basic plug-in and the data resources of the functional plug-ins to the client side according to the installation sequence.

In this embodiment, by returning the data resources of the basic plug-ins and the data resources of the functional plug-ins to the client according to the installation order, multiple plug-ins combined can be returned to the client, and by determining the installation order by combining the importance degree of the basic plug-ins and the installation priority of the functional plug-ins, the client can be ensured to obtain important basic plug-ins or functional plug-ins preferentially, and normal operation of the client or rapid acquisition of the required functional plug-ins by the user can be ensured.

Returning the installation priority of each function plug-in to the client so as to instruct the client to sequentially send downloading requests for the corresponding function plug-ins to the server according to the installation priority of each function plug-in; and returning the data resources of the functional plugin aimed at by the download request to the client based on the received download request.

After obtaining the installation priorities of the plurality of functional plug-ins, the server side can send the installation priorities to the client side; the client may, after receiving the installation priority, sequentially send a download request for the corresponding function plugin to the server based on the installation priority of each function plugin. Specifically, for example, after a download request is sent for a function plug-in with the highest installation priority, the client may send a corresponding download request for the next function plug-in based on the installation priority after the downloaded function plug-in is installed or the related data resource is completely acquired. And after receiving the downloading request, the server side can determine the functional plugin aimed at by the downloading request and acquire the data resource of the functional plugin, and then can return the data of the functional plugin to the client side.

In other examples, if the server side further provides the data resource of the basic plugin to the client side, the client side may also be triggered by the client side, that is, after sending a download request for the basic plugin to the server side, the server side responds to the download request and returns the data resource of the basic plugin to the client side.

In this embodiment, the data resource of the functional plugin aimed at by the download request is returned to the client based on the received download request, so that the client can actively trigger to acquire the data resource of the functional plugin from the server, and the client can adjust the acquisition progress of the data resource of the functional plugin according to the network state or the installation condition of the functional plugin.

Fig. 3 is a flowchart illustrating another plug-in acquisition method according to an exemplary embodiment, as illustrated in fig. 3, in which the method is applied to a client for illustration, may include the following steps.

In step S610, a plug-in preloading request is sent to a server; the plug-in preloading request is used for indicating a server to acquire user account operation data associated with a client, and determining at least two function plug-ins associated with application function requirements of a user account and installation priorities of the function plug-ins according to account behavior data; the user account operational data includes operational data that a user account associated with the client implements for application functions installed in the client.

In practical applications, the client may trigger the installation of the plug-in advance, that is, the client may actively trigger the preloading of the client plug-in advance before detecting an operation event of loading the client related plug-in actively triggered by the user account (e.g., when detecting that the user account actively sends an installation request for the preset plug-in or the preset type plug-in).

In response to a client-initiated plug-in preload request, the server may determine a user account associated with a current client and take account operational data of the user account as user account operational data associated with the client. Furthermore, after obtaining the user account operation data, the server may determine, according to the user account operation data, at least two function plugins associated with the application function requirement of the user account and an installation priority of each function plugin.

In step S620, the data resources of each function plugin returned by the server according to the installation priority of each function plugin are obtained, so as to install each function plugin.

In the above plug-in obtaining method, the client may send a plug-in preloading request to the server, where the plug-in preloading request may instruct the server to obtain user account operation data associated with the client, and determine, according to account behavior data, at least two function plug-ins associated with application function requirements of the user account and an installation priority of each function plug-in, where the user account operation data includes operation data implemented by a user account associated with the client on an application function installed in the client; furthermore, the client can acquire the data resources of each function plug-in returned by the server according to the installation priority of each function plug-in, so as to install each function plug-in. In the method, on one hand, the client actively initiates the plug-in preloading request, and triggers the server to provide data resources of a plurality of function plug-ins for the client, so that the client installs each function plug-in advance, the situation that a user loads related plug-ins when the plug-ins are needed can be avoided, waiting time is reduced, on the other hand, the user can individually and accurately predict the function plug-ins needed by the user and arrange the installation priorities of the function plug-ins based on user account operation data, the user can finish the installation of the function plug-ins more needed by the user preferentially, and the efficiency of the user for obtaining the needed function plug-ins is optimized.

In an exemplary embodiment, in step S620, the obtaining the data resources of each functional plugin returned by the server according to the installation priority of each functional plugin may include the following steps:

receiving the installation priority of each functional plug-in unit returned by the server; according to the installation priority of each function plug-in, sequentially sending a downloading request for the corresponding function plug-in to the server, and acquiring the data resource of the function plug-in returned by the server after responding to the downloading request.

After obtaining the installation priorities of the plurality of function plug-ins, the server may send the installation priorities to the client. The client may, after receiving the installation priority, sequentially send a download request for the corresponding function plugin to the server based on the installation priority of each function plugin. Specifically, for example, after a download request is sent for a function plug-in with the highest installation priority, the client may send a corresponding download request for the next function plug-in based on the installation priority after the downloaded function plug-in is installed or the related data resource is completely acquired. And after receiving the downloading request, the server side can determine the functional plugin aimed at by the downloading request and acquire the data resource of the functional plugin, and then can return the data of the functional plugin to the client side.

In an exemplary embodiment, in step S610, sending a plug-in preloading request to the server may include:

In a specific implementation, the starting mode of the client may include two starting modes, namely a cold start and a hot start. Wherein, the cold start of the client may refer to: when a client is started, the background of the terminal does not have the progress of the client; at this point the terminal will recreate a new process for the client and assign it to the client. The hot start of a client may refer to: the client has been opened and allocated to the corresponding process, but after the user triggers a return key or other keys such as a key for displaying a homepage, the terminal interface switches to other pages except the current client interface, and when the user restarts the client, the mode at this time is called hot start.

In this embodiment, a plug-in preloading request may be sent to the server during a cold start stage of the client, for example, the plug-in preloading request may be sent to the server during each cold start stage of the client; of course, the plug-in preloading request may also be sent to the server in the cold start stage of the client if the plug-in updating condition is satisfied, and the plug-in updating condition may be any one or more of the following, for example: the pre-loading of the plug-in unit in the last time meets a preset time interval, and the fact that the version of the client is updated is detected, wherein the degree of data difference between the current user account operation data and the past user account operation data of the same user account exceeds a threshold value.

In this embodiment, by sending the plug-in preloading request at the cold start stage of the client, the data resources of the functional plug-ins required by the user account can be acquired in advance and installed, so that the triggering operation and waiting time required to be executed by the user are reduced, and the acquisition efficiency of the functional plug-ins is effectively improved.

In order that those skilled in the art may better understand the above steps, the embodiments of the present disclosure will be exemplified below by way of one example, but it should be understood that the embodiments of the present disclosure are not limited thereto. In this embodiment, the server may include a request processing server, a decision platform, and a content delivery network (Content Delivery Network, CDN).

As shown in fig. 4, after the user starts the client, if the client is currently in the cold start stage, the client may acquire the ID of the user account or the account identifier of the terminal as the user account, generate a plug-in preloading request carrying the account identifier, and send the request to the request processing server to query the preloaded plug-in and the installation sequence of the plug-in. Upon receiving the request, the request processing server may request that the installation order of the plug-ins be obtained from the decision platform by way of RPC (remote procedure call ). After receiving a request from a request processing server, the decision platform can read an account identifier from the received request, initialize a basic plug-in, determine the basic plug-in preset for a client, acquire account identifier, acquire user account operation data of a corresponding user account, combine a pre-trained functional plug-in prediction model to make an algorithm decision, obtain the installation priority of the functional plug-in, combine the initialized basic plug-in, finally combine to obtain the installation sequence of the plug-in, and return the installation sequence to the client through the server.

After receiving the installation sequence, the client can sequentially initiate a downloading request and send the downloading request to the content distribution network, obtain the data resources of the plug-in units returned by the content distribution network and install the plug-in units.

In some embodiments, the client may send a plug-in preload request during the first cold start phase of a preset period and record the install order into the cache, which will not require re-acquisition later in the period. And in the same period, other cold starts can be used for detecting whether the downloading and the installation of each plug-in to be installed indicated in the installation sequence are finished, if so, no further processing is needed, and if not, the downloading and the installation process can be continuously executed.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the present disclosure further provides a card acquiring device for implementing the card acquiring method referred to above.

Fig. 5 is a block diagram of a plug-in acquisition device, according to an example embodiment. Referring to fig. 5, the apparatus includes an operation data acquisition unit 501, a priority determination unit 502, and a plug-in resource providing unit 503.

An operation data obtaining unit 501 configured to obtain user account operation data associated with a client in response to a plug-in preloading request initiated by the client; the user account operational data includes operational data of a user account associated with the client for application functions installed in the client;

a priority determining unit 502 configured to determine, according to the user account operation data, installation priorities of at least two function plugins and each of the function plugins associated with application function requirements of the user account;

and a plug-in resource providing unit 503 configured to perform the step of sequentially returning, to the client, the data resources of each of the function plug-ins according to the installation priority of each of the function plug-ins, for the client to install each of the function plug-ins.

In an exemplary embodiment, the operation data acquisition unit 501 includes:

In an exemplary embodiment, the operation data determination module is configured to perform:

In an exemplary embodiment, the priority determining unit 502 is configured to perform:

In an exemplary embodiment, the plug-in resource providing unit 503 is configured to perform:

determining a basic plug-in to be loaded of the client;

Fig. 6 is a block diagram of another plug-in acquisition device, shown in accordance with an exemplary embodiment. Referring to fig. 6, the apparatus includes a request transmitting unit 601 and a plug-in resource acquiring unit 602.

A request sending unit 601 configured to perform sending a plug-in preloading request to a server; the plug-in preloading request is used for indicating the server to acquire user account operation data associated with a client, and determining at least two function plug-ins associated with application function requirements of the user account and installation priorities of the function plug-ins according to the account behavior data; the user account operation data comprises operation data of the user account associated with the client for implementing the application function installed in the client;

and a plug-in resource obtaining unit 602 configured to obtain the data resource of each functional plug-in returned by the server according to the installation priority of each functional plug-in, so as to install each functional plug-in.

In an exemplary embodiment, the plug-in resource obtaining unit 602 is configured to perform:

In an exemplary embodiment, the request sending unit 601 is configured to perform:

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

The respective modules in the above-described plug-in acquisition apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

Fig. 7 is a block diagram illustrating an electronic device 700 for implementing a plug-in acquisition method, according to an example embodiment. For example, the electronic device 700 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, exercise device, personal digital assistant, or the like.

Referring to fig. 7, an electronic device 700 may include one or more of the following components: a processing component 702, a memory 704, a power component 706, a multimedia component 708, an audio component 710, an input/output (I/O) interface 712, a sensor component 714, and a communication component 716.

The processing component 702 generally controls overall operation of the electronic device 700, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 702 may include one or more processors 720 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 702 can include one or more modules that facilitate interaction between the processing component 702 and other components. For example, the processing component 702 may include a multimedia module to facilitate interaction between the multimedia component 708 and the processing component 702.

The memory 704 is configured to store various types of data to support operations at the electronic device 700. Examples of such data include instructions for any application or method operating on the electronic device 700, contact data, phonebook data, messages, pictures, video, and so forth. The memory 704 may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, optical disk, or graphene memory.

The power supply component 706 provides power to the various components of the electronic device 700. Power supply components 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for electronic device 700.

The multimedia component 708 includes a screen between the electronic device 700 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 708 includes a front-facing camera and/or a rear-facing camera. When the electronic device 700 is in an operational mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 710 is configured to output and/or input audio signals. For example, the audio component 710 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 700 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 704 or transmitted via the communication component 716. In some embodiments, the audio component 710 further includes a speaker for outputting audio signals.

The I/O interface 712 provides an interface between the processing component 702 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 714 includes one or more sensors for providing status assessment of various aspects of the electronic device 700. For example, the sensor assembly 714 may detect an on/off state of the electronic device 700, a relative positioning of the components, such as a display and keypad of the electronic device 700, the sensor assembly 714 may also detect a change in position of the electronic device 700 or a component of the electronic device 700, the presence or absence of a user's contact with the electronic device 700, an orientation or acceleration/deceleration of the device 700, and a change in temperature of the electronic device 700. The sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 714 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 714 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 716 is configured to facilitate communication between the electronic device 700 and other devices, either wired or wireless. The electronic device 700 may access a wireless network based on a communication standard, such as WiFi, an operator network (e.g., 2G, 3G, 4G, or 5G), or a combination thereof. In one exemplary embodiment, the communication component 716 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 716 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the electronic device 700 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.

In an exemplary embodiment, a computer-readable storage medium is also provided, such as memory 704, including instructions executable by processor 720 of electronic device 700 to perform the above-described method. For example, the computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

In an exemplary embodiment, a computer program product is also provided, comprising instructions executable by the processor 720 of the electronic device 700 to perform the above-described method.

Fig. 8 is a block diagram illustrating an electronic device 800 for implementing a plug-in acquisition method, according to an example embodiment. For example, the electronic device 800 may be a server. Referring to fig. 8, electronic device 800 includes a processing component 820 that further includes one or more processors and memory resources represented by memory 822 for storing instructions, such as application programs, executable by processing component 820. The application programs stored in memory 822 may include one or more modules each corresponding to a set of instructions. Further, the processing component 820 is configured to execute instructions to perform the methods described above.

The electronic device 800 may further include: the power component 824 is configured to perform power management of the electronic device 800, the wired or wireless network interface 826 is configured to connect the electronic device 800 to a network, and the input output (I/O) interface 828. The electronic device 800 may operate based on an operating system stored in memory 822, such as Windows Server, mac OS X, unix, linux, freeBSD, or the like.

In an exemplary embodiment, a computer-readable storage medium is also provided, such as memory 822, including instructions executable by a processor of electronic device 800 to perform the above-described method. The storage medium may be a computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

In an exemplary embodiment, a computer program product is also provided, comprising instructions therein, executable by a processor of the electronic device 800 to perform the above-described method.

It should be noted that the descriptions of the foregoing apparatus, the electronic device, the computer readable storage medium, the computer program product, and the like according to the method embodiments may further include other implementations, and the specific implementation may refer to the descriptions of the related method embodiments and are not described herein in detail.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A card acquisition method, characterized by comprising:

2. The method of claim 1, wherein the obtaining user account operational data associated with the client comprises:

3. The method of claim 2, wherein the obtaining user account operation data for the user account based on the access record comprises:

4. The method of claim 1, wherein determining, based on the user account operational data, at least two function plugins associated with application function requirements of the user account and an installation priority for each of the function plugins comprises:

5. The method according to claim 1, wherein the sequentially returning the data resources of each of the function plugins to the client according to the installation priority of each of the function plugins includes:

determining a basic plug-in to be loaded of the client;

6. The method according to any one of claims 1-5, wherein the sequentially returning the data resources of each of the function plugins to the client according to the installation priority of each of the function plugins includes:

7. A card acquisition method, characterized by comprising:

8. The method of claim 7, wherein the obtaining the data resources of each of the function plugins returned by the server according to the installation priority of each of the function plugins includes:

9. The method according to claim 7 or 8, wherein the sending a plug-in preload request to the server includes:

10. A card acquisition apparatus, comprising:

11. A card acquisition apparatus, comprising:

12. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the method of any one of claims 1 to 6 or the method of any one of claims 7 to 9.

13. A computer readable storage medium, characterized in that instructions in the computer readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of any one of claims 1 to 6 or the method of any one of claims 7 to 9.