HK1168216A1 - Method, system and related device for obtaining plug-in - Google Patents

Abstract

The invention discloses a plug-in obtaining method and system as well as relevant devices, and provides a simple, convenient and practicable scheme which is used for obtaining a plug-in and simultaneously can save storage and processing resources of a user terminal. The method comprises the following steps that: a host program client sends a plug-in download request with a user identifier to a server, wherein the user attributes of the user identifier comprise a service platform identifier and a business identifier corresponding to the service platform identifier; and the host program client receives a plug-in list which is sent by the server and is corresponding to the service platform identifier and the business identifier, wherein the plug-in list comprises at least one plug-in identifier; and the host program client downloads the plug-in according to the received plug-in list.

Description

Plug-in acquisition method, system and related device

Technical Field

The present application relates to the field of computer application technologies, and in particular, to a plug-in obtaining method, a plug-in obtaining system, a host client, and a server.

Background

The plug-in is a program module, conforms to the access specification of the service platform, and can run on the service platform and is not a function or business module required by the service platform. From a physical form, the plug-in includes, but is not limited to, a Dynamic Link Library (DLL). At present, for different plug-in scenes, various service platforms often continuously push various plug-ins for users to select in order to provide richer and personalized functions for the users. The plug-in scenario refers to a service platform on which the plug-in runs.

The prior art solutions for obtaining plug-ins mainly include the following two categories:

firstly, all plug-ins on one service platform are installed in advance. For example, after a user registers on a service platform, an installation package including all plug-ins on the service platform is downloaded from the service platform, and each plug-in the installation package is installed; subsequently, when the user logs in the service platform, the functions provided by the plug-in installed before can be used. Such a solution is only suitable for relatively closed service platforms, e.g. service platforms that are not open to other third parties than registered users and service platform providers, in which case the number of plug-ins is small and the amount of memory space required to be occupied by the plug-ins is controllable. However, this solution is obviously not suitable for an open service platform with many plug-ins, because as the number of plug-ins and the required storage capacity increase, the storage capacity required by the installation package including all plug-ins will also increase sharply, and downloading and running the installation package will occupy a large amount of storage resources and processing resources of the user terminal, thereby reducing the running efficiency of the user terminal.

And secondly, selecting to download the plug-in by the user according to the self requirement. By adopting the scheme, a user does not need to download and run an installation package containing all the plug-ins of the service platform, and the user can download the plug-ins which are distributed on the webpage and are suitable for the additional functions of the service platform through the webpage or a plug-in management tool. The application premise of the scheme is that a user needs to have higher professional knowledge, can select a plug-in suitable for a certain service platform or master the using method of a plug-in management tool through plug-in introduction on a webpage, and has the problem of high using difficulty for general users.

Disclosure of Invention

The embodiment of the application provides a plug-in obtaining method, which is used for providing a plug-in obtaining scheme which is simple and feasible and can save storage and processing resources of a user terminal.

Correspondingly, the embodiment of the application also provides a plug-in obtaining system, a host program client and a server.

The technical scheme provided by the embodiment of the application is as follows:

a plug-in acquisition method comprising:

a host program client sends a plug-in downloading request carrying a user identifier to a server, wherein the user attribute of the user identifier comprises a service platform identifier and a service identifier corresponding to the service platform identifier; receiving a plug-in list which is sent by a server and corresponds to the service platform identification and the service identification, wherein the plug-in list comprises at least one plug-in identification; and downloads the plug-ins according to the received plug-in list.

A plug-in acquisition method comprising: receiving a plug-in downloading request carrying a user identifier sent by a host program client; searching the user attribute of the user identifier carried in the plug-in downloading request from the stored user attributes of the user identifiers, and determining the service platform identifier and the service identifier corresponding to the service platform identifier in the searched user attribute; searching a corresponding plug-in list according to the determined service platform identification and the service identification, wherein the plug-in list corresponds to at least one service identification and comprises at least one plug-in identification; and sending the found corresponding plug-in list to the host program client.

A plug-in acquisition system comprises a host program client and a server, wherein:

the host program client is used for sending a plug-in downloading request carrying a user identifier to a server, wherein the user attribute of the user identifier comprises a service platform identifier and a service identifier corresponding to the service platform identifier, and downloading the plug-in according to a plug-in list which is sent by the server and corresponds to the service platform identifier and the service identifier, wherein the plug-in list comprises at least one plug-in identifier;

the server is used for receiving the plug-in downloading request sent by the host program client, searching the user attribute of the user identifier carried in the plug-in downloading request from the stored user attributes of each user identifier, and determining the service platform identifier and the service identifier corresponding to the service platform identifier in the searched user attribute; searching a corresponding plug-in list according to the determined service platform identification and the service identification, and sending the searched corresponding plug-in list to the host program client; the plug-in list corresponds to at least one service identifier, and the plug-in list comprises at least one plug-in identifier.

A host client, comprising: the system comprises a first sending unit, a second sending unit and a third sending unit, wherein the first sending unit is used for sending a plug-in downloading request carrying a user identifier to a server, and the user attribute of the user identifier comprises a service platform identifier and a service identifier corresponding to the service platform identifier; a plug-in list receiving unit, configured to receive a plug-in list sent by a server and corresponding to the service platform identifier and the service identifier included in the user attribute of the user identifier sent by the first sending unit, where the plug-in list includes at least one plug-in identifier; and the first downloading unit is used for downloading the plug-in according to the plug-in list received by the plug-in list receiving unit.

A server, comprising: the first receiving unit is used for receiving a plug-in downloading request which is sent by a host program client and carries a user identifier; the user attribute searching unit is used for searching the user attribute of the user identifier carried in the plug-in downloading request received by the first receiving unit from the stored user attributes of each user identifier; the identification determining unit is used for determining the service platform identification and the service identification corresponding to the service platform identification which are included in the user attributes searched by the user attribute searching unit; a first plug-in list searching unit, configured to search a corresponding plug-in list according to the service platform identifier and the service identifier determined by the identifier determining unit, where the plug-in list corresponds to at least one service identifier, and the plug-in list includes at least one plug-in identifier; and the first plug-in list sending unit is used for sending the corresponding plug-in list searched by the first plug-in list searching unit to the host program client.

According to the method and the device, the plug-in lists corresponding to various services on different service platforms are stored on the server side, when the plug-ins need to be downloaded, a plug-in downloading request carrying user identification is sent to the server firstly by the host program, the server side sends the corresponding plug-in lists to the host program according to the service platform identification and the service platform identification contained in the user attribute of the user identification in the received plug-in downloading request, and the host program client downloads the plug-ins according to the received plug-in lists. According to the scheme, all plug-ins on the server platform do not need to be downloaded by the client, so that transmission resources and storage resources are saved; meanwhile, the method does not need the user to have higher professional knowledge, and is simple and easy to implement.

Drawings

FIG. 1a is a schematic diagram of a plug-in acquisition system in an embodiment of the present application;

FIG. 1b is a flow chart of the main implementation principle of the embodiment of the present application;

FIG. 2 is a flowchart illustrating a plug-in download process according to an embodiment of the present invention;

FIG. 3 is a flow chart of a preferred embodiment of step 205 of FIG. 2, an example of the present application;

FIG. 4 is a flowchart illustrating a server obtaining a list of plug-ins according to an embodiment of the present disclosure;

FIG. 5 is a flowchart illustrating a plug-in download process according to a second embodiment of the present application;

fig. 6 is a schematic structural diagram of a host client according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a server provided in the embodiment of the present application.

Detailed Description

The host program refers to a carrier for the plug-in to run, such as an instant messaging software program. The user scene refers to a scene corresponding to the user attribute of the user identifier. In the embodiment of the application, the service platform is provided with a service platform identifier, at least one service is opened on the service platform, each service is provided with a service identifier, and the service identifiers correspond to a plug-in list. I.e. the service corresponds to a service platform, and thus the service identity corresponds to a service platform identity; and the plug-in list corresponds to the service, and the plug-in identified by each plug-in identifier in the plug-in list conforms to the access specification of the service platform based on the service corresponding to the service identifier. And the user attribute of the user identifier comprises at least one service platform identifier and at least one service identifier corresponding to the service platform identifier. For example, suppose that the service platform a opens the service X, if the user attribute of the user identifier includes the service platform identifier of the service platform a and the service identifier of the corresponding service X, it indicates that the user can use the service X provided by the service platform a by using the user identifier. Of course, the function that the user wants to use the service X provided by the service platform a by using the user identifier needs to be registered or opened on the service platform a in advance.

The basic idea of the application is as follows: firstly, storing a plug-in list corresponding to each service on different service platforms in a server, wherein the plug-in list corresponding to the service comprises plug-in identifiers which are in accordance with the access specification of the service platform and are suitable for plug-ins of users who have opened the service, namely, the server generates the plug-in list corresponding to the service identifier of the service according to the service on the adapted service platform. According to the service platform identification and the service identification corresponding to the service platform identification included in the user attribute of each user identification, when a user uses a host program by using the user identification, for example, when the user logs in or runs the host program, the user identification is transmitted to a server by using the host program, the service platform identification corresponding to the user identification and the service identification corresponding to the service platform identification are determined according to the user attribute in the user identification, the plug-in list corresponding to the service identification is determined according to the determined service identification, and the plug-in corresponding to the service which the user may need to use is acquired for each user in an individualized manner according to the user scene of the user identification.

The main implementation principle, the specific implementation mode and the corresponding beneficial effects of the technical scheme of the embodiment of the present application are explained in detail below with reference to the drawings.

Fig. 1a is a schematic diagram of a plug-in obtaining system provided in an embodiment of the present application, where the plug-in obtaining system includes a host program client and a server connected to the client through a network.

As shown in fig. 1b, the main implementation principle flow of the embodiment of the present application is as follows:

step 10, a host program client sends a plug-in downloading request carrying a user identifier to a server, wherein the user attribute of the user identifier comprises a service platform identifier and a service identifier of a service opened by a service platform corresponding to the service platform identifier;

step 20, after receiving a plug-in downloading request carrying user identification sent by a host program client, a server searches user attributes of the user identification carried in the plug-in downloading request from stored user attributes of each user identification;

step 30, the server sends a plug-in list to the host program client, the plug-in list comprises each plug-in identifier in the plug-in list corresponding to at least one service identifier contained in the user attribute of the user identifier, and the plug-in identified by each plug-in the plug-in list corresponding to the service identifier conforms to the access specification of the service platform based on the service corresponding to the service identifier;

step 40; and the host program client downloads the plug-ins according to the received plug-in list.

Two embodiments will be described in detail below to illustrate and explain the main implementation principles of the method of the present application by taking the host program as an example of the instant messaging program according to the above inventive principles of the present application. The host program may also be an email client or the like.

Example one

Referring to fig. 2, a flowchart of a plug-in downloading process according to a first embodiment of the present application is shown.

Step 201, a user inputs a user identifier Tom1970 in an instant messaging client, and the category of the user identifier is an electronic commerce account, and the instant messaging client sends a plug-in downloading request carrying the user identifier Tom1970 to a server;

generally, in order to facilitate user operation, an instant messaging client provides several types of supported user identification category options for a user to select in a radio box or pull-down menu mode, wherein the user identification categories comprise a mobile phone number, a mailbox address, an e-commerce account and the like;

preferably, when the instant messaging client sends the user identifier Tom1970 to the server, the identifier reassembly rule corresponding to the input identifier category is selected from the correspondence between the stored identifier categories and the identifier reassembly rules according to the user identifier category input by the user; and according to the selected mark reorganization rule, reorganizing the input user mark; and the instant communication client carries the user identification with the recombination mark obtained after the recombination processing in the plug-in downloading request and sends the user identification to the server. For example, the identifier reassembly rule corresponding to the e-commerce account is to add a prefix "EB _" before the input user identifier, and then the user identifier of the user Tom after the prefix "EB _" is added is EB _ Tom1970, and EB _ Tom1970 is sent to the server. Wherein "EB _" can be regarded as a recombination marker.

Step 202, after receiving a plug-in downloading request carrying a user identifier sent by an instant messaging client, a server searches the user attribute of the user identifier Tom1970 carried in the plug-in downloading request from the stored user attributes of each user identifier;

preferably, when the user identifier is a user identifier with a reorganization mark obtained through reorganization, the server needs to determine a reorganization rule corresponding to the reorganization identifier from a correspondence between the stored reorganization identifier and the reorganization rule according to the reorganization identifier, and determine a corresponding identifier type from a correspondence between the stored identifier type and the identifier reorganization rule according to the determined reorganization rule; and searching the user attribute corresponding to the determined identification category from the stored user attributes of the user identifications corresponding to different identification categories.

For example, the server determines that the user identifier type is e-commerce according to the received prefix "EB _" of the user identifier, and then searches the service platform attribute of the user identifier Tom1970 from the stored service platform attributes of the user identifier of the e-commerce type. In this embodiment, the user attributes of each user identifier of the e-commerce category are shown in table 1, where Platform1 is an identifier of a shopping Platform, Platform2 is an identifier of a payment Platform, S _ mobile is an identifier of a mobile phone binding service based on the shopping Platform, and S _ identity is an identifier of a real-name authentication service based on the payment Platform.

The user attributes found out by the user identification comprise Tom1970 identification Platform1 with a shopping Platform, identification Platform2 of a mobile phone binding service and a payment Platform, and identification of a real name authentication service based on the payment Platform.

TABLE 1 user Attribute possessed by each user identifier of E-commerce category

Step 203, the server searches a plug-in list corresponding to each service identifier in the user attribute of the user identifier Tom1970 from a plug-in list corresponding to each service identifier which is stored and opened based on the service platform corresponding to the service platform identifier;

the plug-in identified by each plug-in identification in the plug-in list corresponding to one service identification accords with the service platform access specification based on the service corresponding to the service identification. In this embodiment, a list of plug-ins corresponding to each service identifier is shown in table 2. The server finds out the plug-in List1 corresponding to the identifier S _ mobilephone of the mobile phone binding service on the shopping Platform identified as Platform1 and the plug-in List2 corresponding to the identifier S _ identity of the real name authentication service on the payment Platform identified as Platform 2. For example, the plug-in identified by the plug-in identifier included in the plug-in List1 conforms to the shopping platform access specification, for example, the plug-in providing the collection function is identified as plug-in of Addon _ ID1, the plug-in providing the visitor volume statistics function is identified as plug-in of Addon _ ID2, the plug-in providing the attention ranking function is identified as plug-in of Addon _ ID3, and the like. The plug-in identified by the plug-in identification included in the plug-in List2 conforms to the payment platform access specification, such as a plug-in providing monthly expense reports identifying the plug-in Addon _ ID11, a plug-in providing reminder functionality identifying the plug-in Addon _ ID12, and so on.

In addition to the plug-in List1 corresponding to the identifier S _ mobile phone of the mobile phone binding service on the shopping Platform identified as Platform1 and the plug-in List2 corresponding to the identifier S _ identity of the real name authentication service on the payment Platform identified as Platform2, table 2 further includes a plug-in List3 corresponding to the query service on the logistics management Platform identified as Platform3 and a plug-in List4 corresponding to the important customer service on the shopping Platform identified as Platform1 and identified as S _ VIP. The plug-in identified by the plug-in identification included in the plug-in List3 conforms to the payment platform access specification, for example, a plug-in providing a monthly query report identifying the plug-in of Addon _ ID28, a plug-in providing a reminder function identifying the plug-in of Addon _ ID29, and the like. The plug-in identified by the plug-in identification included in the plug-in List4 conforms to the shopping platform access specification, e.g., the plug-in providing album functionality is identified as plug-in Addon _ ID 8.

Table 2 plug-in list corresponding to each service identifier

Service identification	Plug-in list
		Platform1-S_mobilephone	List1＝{Addon_ID1、Addon_ID2、Addon_ID3}
Platform1-S_VIP	List4＝{Addon_ID8}
		Platform2-S_identify	List2＝{Addon_ID11、Addon_ID12}
Platform3-S_query	List3＝{Addon_ID28、Addon_ID29}
		......	......

Step 204, the server sends a plug-in List _ AV to the instant messaging client, wherein the plug-in List _ AV includes the plug-in identifiers in the plug-in List corresponding to each service identifier in the user attribute which is possessed by the user identifier Tom1970 and found in step 203;

in this embodiment, the List1 includes plug-ins with plug-in identifiers Addon _ ID1, Addon _ ID2 and Addon _ ID 3; the List2 includes plug-ins with plug-in identifications Addon _ ID21 and Addon _ ID22, respectively. The plug-in identification contained in List _ AV is therefore List _ AV ═ Addon _ ID1, Addon _ ID2, Addon _ ID3, Addon _ ID21, Addon _ ID22 }.

In step 205, the instant messaging client downloads the plug-in according to the plug-in List _ AV sent by the server.

Preferably, in order to avoid the repeated downloading occupying network transmission resources and local storage resources, in step 205, the specific process of downloading the plug-in by the instant messaging client according to the plug-in List _ AV sent by the server is as shown in fig. 3:

step 301, an instant messaging client creates a List to be downloaded List _ DL with empty content;

step 302, the instant messaging client adds the plug-in identifier to the List to be downloaded when the plug-in corresponding to the plug-in identifier is not stored locally for each plug-in identifier in the plug-in List _ AV in sequence; otherwise, the plug-in identification is not added into the List to be downloaded List _ DL;

step 303, the instant messaging client determines whether the content of the List to be downloaded List _ DL is empty, if yes, step 304 is performed, otherwise, the processing is ended;

in step 304, the instant messaging client downloads the plug-in corresponding to each plug-in identifier in the List to be downloaded List _ DL until the last plug-in identifier in the List to be downloaded List _ DL.

Certainly, the process shown in fig. 3 may further include a step for the user to select, that is, displaying, to the user, the plug-in identifier of the plug-in that is not locally stored in the plug-in list, receiving a selection instruction input by the user based on the displayed plug-in identifier, selecting, according to the selection instruction, the plug-in identifier from the plug-in identifiers of the plug-ins that are not locally stored, adding the selected plug-in identifier into the list to be downloaded, and then performing steps 303 to 304. This has the advantage that when the plug-in List listav sent by the server contains a large number of plug-in identifiers for which corresponding plug-ins are not stored locally, for example, 1000 plug-in identifiers for which corresponding plug-ins are not stored locally, a plug-in can be selected according to the user's needs and interests, without downloading the plug-ins identified by the plug-in identifiers for which corresponding plug-ins are not stored locally in the plug-in List listav, thereby further reducing the network transmission resources required for downloading the plug-ins and the local storage resources required for storing the plug-ins.

Preferably, the plugin list corresponding to each service identifier stored in the server in step 203 in fig. 2 is obtained in the manner shown in fig. 4:

step 401, receiving an plugin and a plugin description file corresponding to the plugin; when a plug-in developer (including a service platform provider and a third party provider) submits a plug-in, a plug-in description file corresponding to the plug-in is attached to the plug-in, wherein the plug-in description comprises a service platform identifier and a service identifier, the service platform identifier is used for indicating that the plug-in is in accordance with an access specification of a service platform corresponding to the service platform identifier, the service identifier is used for indicating that the plug-in is suitable for a user who has opened a service corresponding to the service identifier, and the plug-in description file also comprises additional information such as the name, the version number and the operation mode of the plug-in;

an example of a plug-in description file is given below, where the tag content in the underlined part indicates that the plug-in conforms to the access specification of the service Platform identified as Platform1, i.e. is applicable to the user who has opened the handset binding service identified as S _ mobile phone on the service Platform identified as Platform 1.

Plug-in description file example:

<？xml version＝″1.0″encoding＝″utf-8″？>

<Plugin>

<AppID>6000</AppID>

< Name > Community hotspot </Name >

<Version>1</Version>

<WWSDK_Version>3400</WWSDK_Version>

<RunMode>1000</RunMode>

<BindSet>

<Bind>Platform1-S_mobilephone</Bind>

</BindSet>

</Plugin>

Step 402, classifying the plug-ins according to the service platform identifiers and the service identifiers in the plug-in description files, and correspondingly storing the identifiers of the plug-ins with the same service platform identifier and service identifier in the corresponding plug-in description files into a plug-in list corresponding to the service identifier of the service platform corresponding to the service platform identifier.

Still taking the List1 of the plug-in List1 corresponding to the identifier S _ mobilephone of the mobile phone binding service on the shopping Platform identified as Platform1 shown in table 2 as an example, assuming that three plug-ins including Addon _ ID1, Addon _ ID2 and Addon _ ID3 exist in the List1 to identify corresponding plug-ins, the added List1 is List1 ═ Addon _ ID1, Addon _ ID2, Addon _ ID3 and 6000 }.

Example two

In order to enable the instant messaging client to have higher flexibility when downloading the plug-in, before the server sends the plug-in list to the instant messaging client, the user attribute of the user identifier Tom1970 carried in the plug-in downloading request can be sent to the instant messaging client, the instant messaging client selects at least one service platform identifier from a plurality of service platform identifiers contained in the user attribute, then selects at least one service identifier from a plurality of service identifiers opened by a service platform corresponding to the identifier based on the selected service platform contained in the user attribute, then the server sends the plug-in list to the instant messaging client according to the service platform identifier and the service identifier selected by the instant messaging client, and at this time, the plug-in list only contains the plug-in identifier in the plug-in list corresponding to the selected service identifier. The specific process is shown in fig. 5:

step 501, a user inputs a user identifier Tom1970 in an instant messaging client, the category of the user identifier is an electronic commerce account, and the instant messaging client sends a plug-in downloading request carrying the user identifier Tom1970 to a server;

step 502, after receiving a plug-in download request carrying a user identifier sent by an instant messaging client, a server searches user attributes of a user identifier Tom1970 carried in the plug-in download request from user attributes of each user identifier stored in table 3;

step 503, the server finds out the user attribute UserProfile ═ Platform1-S _ mobilephone of the user identifier Tom 1970; platform2-S _ identification } is sent to the instant messaging client;

step 504, the instant messaging client receives the user attribute UserProfile ═ Platform1-S _ mobilephone of Tom1970 sent by the server; platform2-S _ identification }, selecting at least one service Platform identification from the service Platform identifications contained in the user attribute of Tom1970, and selecting at least one service identification corresponding to the selected service Platform identification from the service identifications contained in the user attribute of Tom 1970;

preferably, the instant messaging client displays the received service Platform identifications Platform1, Platform2 and service identifications S _ mobile phone, S _ identification contained in the user attribute of the user identification Tom1970 through a display device; receiving a selection instruction input by a user based on the displayed service Platform identifier and the service identifier, selecting at least one service Platform identifier from the service Platform identifiers contained in the user attribute of the user identifier according to the selection instruction, and selecting at least one service identifier from the service identifiers contained in the user attribute of the user identifier, wherein the identifier Platform1 of the shopping Platform and the identifier S _ mobilephone of the mobile phone binding service based on the shopping Platform are assumed to be selected.

Step 505, the instant messaging client sends the selected identifier Platform1 of the shopping Platform and the identifier S _ mobilephone of the mobile phone binding service to the server;

step 506, after receiving the identifier Platform1 of the shopping Platform and the identifier S _ mobile phone of the mobile phone binding service sent by the instant messaging client, the server selects a plug-in list corresponding to the identifier S _ mobile phone of the mobile phone binding service from the plug-in list corresponding to each service identifier shown in table 2;

the plug-in List1 corresponding to the identifier S _ mobilephone of the mobile phone binding service includes plug-in identifiers Addon _ ID1, Addon _ ID2, and Addon _ ID 3.

Step 507, the server sends a plug-in List _ AV1 to the instant messaging client, where the plug-in List _ AV1 includes plug-in identifiers Addon _ ID1, Addon _ ID2, and Addon _ ID3 included in the plug-in List1 corresponding to the S _ mobilephone found in step 506;

in step 508, the instant messaging client downloads the plug-in according to the plug-in List _ AV1 sent by the server.

Preferably, in step 508, in order to avoid the repeated downloading occupying network transmission resources and local storage resources, a specific downloading scheme similar to that shown in fig. 3 may be adopted.

Preferably, the instant messaging client is logged in the user identifier Tom1970, and in step 503, the server finds out a service Platform attribute UserProfile that the user identifier has { Platform1-S _ mobile phone; after Platform2-S _ identity } is sent to the instant messaging client, the instant messaging client may store the user attribute, when the user attribute of the user identifier Tom1970 is modified, the server may bear the modified user attribute in a notification message by sending a notification message and send the notification message to the instant client, and the instant client updates the stored user attribute to the modified user attribute. Some cases where user attributes change are as follows:

the user registers and opens the service on other electronic commerce platforms with cooperation agreement in advance except shopping Platform and payment Platform, for example, logistics management Platform with user identification Tom1970, so that the user identification Tom1970 can enjoy the function provided by the logistics management Platform, at this time, the identification Platform3 of the logistics management Platform and the identification S _ query of the opened query service are added in the user attribute of the user identification; or the user opens other services except the mobile phone binding service on the existing shopping Platform, such as important customer service, and the Platform1-S _ VIP of the important user service is added to the user attribute possessed by the user identifier at this time; or the user permanently logs out the user identification Tom1970 on the existing shopping platform or payment platform, the user identification Tom1970 is no longer used for enjoying the functions of the shopping platform or payment platform, and the user identification Tom1970 has the user attribute to delete the identification of the shopping platform or payment platform; or the user closes the mobile phone binding service that has been opened on the shopping platform, and at this time, the user identifier Tom1970 deletes the identifier S _ mobilephone of the mobile phone binding service in the user attribute.

In order to solve the problem that after the server has sent the service platform attribute possessed by the user identifier to the instant messaging client, the attribute possessed by the user identifier is changed, after step 503, the server may further execute step 510,

step 510, when the user attribute of the user identifier Tom1970 changes, the server sends a notification message to the instant messaging client, where the notification message includes the service platform identifier and the service identifier included in the modified user attribute of the user identifier Tom 1970;

assume that, in this embodiment, in step 504, the instant messaging client receives a user attribute UserProfile of Tom1970 sent by the server { Platform1-S _ mobile phone; after Platform2-S _ identity } the user opens the query service of the user identification Tom1970 on a logistics management Platform other than a shopping Platform or a payment Platform, and then the user attribute of the user identification Tom1970 is modified to be user profile { Platform1-S _ mobile, Platform2-S _ identity, Platform3-S _ query }.

Step 511, after receiving the notification message, the instant messaging client compares the identifier included in the modified user attribute of Tom1970 included in the notification message with the user attribute of Tom1970 received in step 504, determines that the user attribute of Tom1970 is modified to be an increased identifier or a decreased identifier, and enters step 512 when the user attribute is modified to be an increased identifier; when the reduction identification is modified at this time, a prompt message is output;

step 512, the instant messaging client determines that the added identifier is an identifier and a service identifier of a service platform added at the same time, or only a service identifier; if the service platform identifier and the service identifier are determined to be added at the same time, the step 513 is performed, and if the service identifier is modified to be only added at this time, the step 516 is performed;

step 513, sending the identifier Platform3 of the added logistics management Platform and the service identifier S _ query of the added query service to the server;

step 514, after receiving the identification Platform3 of the logistics Platform and the service identification S _ query of the query function sent by the instant messaging client, the server selects a plug-in List3 corresponding to the service identification S _ query of the query service on the identification Platform3 of the logistics management Platform from the plug-in List corresponding to each service identification shown in table 2;

step 515, the server sends the plug-in List _ AV2 of each plug-in identifier in the plug-in List3 corresponding to the service identifier S _ query of the query function on the identifier Platform3 of the selected outflow management Platform to the instant messaging client;

in step 516, the instant messaging client downloads the plug-in according to the List _ AV2 sent from the server in step 515 or step 518.

In this embodiment of the present application, the server may also only bear the added service platform identifier and the corresponding service identifier in the notification message and send the notification message to the instant messaging client, where the instant messaging client updates the user attribute stored by the instant messaging client according to the added service platform identifier and the corresponding service identifier, sends a plug-in download request carrying the added service platform identifier and the corresponding service identifier to the server, and downloads the plug-in according to the plug-in list corresponding to the added service platform identifier and the corresponding service identifier sent by the server. The processing flow of the server side is similar to the above steps, and is not described herein again.

Assuming that the user opens an important user service of the user identifier Tom1970 on the shopping Platform in step 510, the user attribute of the user identifier Tom1970 will be modified to user profile { Platform1-S _ mobile; platform1-S _ VIP; platform3-S _ query }, after the server sends a notification message containing the modified user attribute to the instant messaging client in step 510, the instant messaging client determines that the modification is only to add the service identifier when executing step 512, and then executes steps 513 'to 516' to replace the steps 513 to 516;

step 513', the instant messaging client sends the identifier S _ VIP for adding the important customer service and the identifier Platform1 of the shopping Platform based on which the important customer service is based to the server;

step 514', after the server receives the identifier S _ VIP of the important customer service sent by the instant messaging client, the server selects a plug-in List4 corresponding to the service identifier S _ VIP of the important customer service on the shopping platform from the plug-in List corresponding to each service identifier shown in table 2;

step 515', the server sends the plug-in List _ AV3 containing the respective plug-in identifiers in the plug-in List4 corresponding to the service identifier S _ VIP of the important customer service on the selected shopping platform to the instant messaging client;

in step 516 ', the instant messaging client downloads the plug-in according to the List _ AV3 sent from the server in step 515'.

Preferably, in step 516 and step 516', in order to avoid the occupation of network transmission resources and local storage resources by repeated downloading, a specific downloading scheme similar to that shown in fig. 3 may also be adopted.

Preferably, in step 504, when the instant messaging client selects at least one service Platform identifier and at least one service identifier on the service Platform corresponding to the selected service Platform identifier from the service Platform identifiers and the service identifiers included in the user attribute of Tom1970, a logical relationship identifier may be further selected from the alternative logical relationship identifiers, where the logical relationship identifier includes identifiers of logical relationships such as "and", "or", "not", for example, when the user attribute is UserProfile { Platform1-S _ mobilephone; platform1-S _ VIP; platform2-S _ identity }, if the user selects Platform1-S _ mobile phone, Platform1-S _ VIP and the logical relationship "and" identifier, the server will select plug-ins applicable to both the handset binding service corresponding to S _ mobile phone and the important customer service corresponding to S _ VIP on the shopping Platform identified as Platform1, i.e. plug-ins existing in both the plug-in List1 corresponding to S _ mobile phone and the plug-in List4 corresponding to S _ VIP, and send the plug-in List containing the selected plug-ins to even the communication client; if the user selects Platform1-S _ mobile phone, Platform1-S _ VIP and the logical relationship "or" identification, the server will select the plug-in List1 corresponding to S _ mobile phone and the plug-in List4 corresponding to S _ VIP on the shopping Platform identified as Platform1 and send the plug-in lists containing the respective plug-ins in the selected lists 1 and List4 to the communication client; the other logical relationship identifications are also similar and are not listed here.

In the embodiment of the application, the server stores user attributes of user identifications and a plug-in list corresponding to service identifications of services opened on a service platform corresponding to each service platform identification; when a user inputs a user identifier in a host program client, the host program client sends a plug-in downloading request carrying the user identifier to a server; the server searches the user attribute of the user identifier in the plug-in downloading request, searches a plug-in list corresponding to each service identifier in the user attribute of the user identifier, and sends the plug-in list to the host program, wherein the plug-in list comprises the plug-in identifiers in the plug-in list corresponding to the service identifiers contained in the user attribute of the user identifier carried in the plug-in downloading request, and the plug-ins identified by the plug-in identifiers contained in the plug-in list corresponding to the service identifiers conform to the access specification of the service platform based on which the service corresponding to the service identifiers is based. Therefore, a scheme for downloading the plug-ins by using the host program is provided, and a user does not need to install an installation package containing all the plug-ins, so that the method is suitable for an open service platform with more plug-ins; meanwhile, a user does not need to master professional knowledge to select a proper plug-in, and the corresponding plug-in can be provided for the user identification with different service platform attributes conveniently.

Correspondingly, an embodiment of the present application further provides a host program client, a specific structural diagram of the client is shown in fig. 6, and the client includes the following functional units:

a first sending unit 61, configured to send a plug-in download request carrying a user identifier to a server, where a user attribute of the user identifier includes a service platform identifier and a service identifier corresponding to the service platform identifier;

a plug-in list receiving unit 62, configured to receive a plug-in list sent by the server and corresponding to the service platform identifier and the service identifier included in the user attribute of the user identifier sent by the first sending unit 61, where the plug-in list includes at least one plug-in identifier;

a first downloading unit 63, configured to download the plug-in according to the plug-in list received by the plug-in list receiving unit 62.

In a preferred embodiment, the first sending unit 61 may be specifically divided into the following functional modules, so as to implement sending the user identifier to the server after recombining the user identifier. One of the purposes of identifier reorganization is to enable the server to determine the corresponding identifier category according to the reorganization mark of the user identifier. Specifically, the functional modules include:

the input information receiving module is used for receiving the input identification category and the user identification; the recombination rule determining module is used for determining an identification recombination rule corresponding to the input identification category from the corresponding relation between the stored identification category and the identification recombination rule according to the identification category received by the input information receiving module; the recombination processing execution module is used for recombining the user identification received by the input information receiving module according to the identification recombination rule determined by the recombination rule determining module; and the sending module is used for carrying the user identification with the recombination mark obtained by the recombination processing execution module on the plug-in downloading request and sending the user identification to the server.

In a preferred embodiment, the plug-in list receiving unit 62 can be divided into the following functional modules, so that the host program client can flexibly select the service platform or service corresponding to the plug-in to be selected according to the actual requirement:

the user attribute receiving module is used for receiving the user attribute of the user identification which is determined by the server based on the user identification in the plug-in download request and sent in parallel; the identification selection module is used for selecting at least one service platform identification from the service platform identifications contained in the user attributes received by the user attribute receiving module, and selecting at least one service identification corresponding to the selected service platform identification from the service identifications contained in the received user attributes; the identification sending module is used for sending the service platform identification and the service identification selected by the identification selection module to the server; and the plug-in list receiving module is used for receiving a plug-in list which is sent by the server and corresponds to the service platform identification and the service identification which are sent by the identification sending module.

In a preferred embodiment, the plug-in list receiving unit 62 can be further divided into the following functional modules to flexibly instruct the server to select the corresponding plug-in list according to the logical relationship identifier between different service identifiers:

the user attribute receiving module is used for receiving the user attribute which is determined by the server based on the user identifier in the plug-in downloading request and is sent by the server; the identification selection module is used for selecting at least one service platform identification from the service platform identifications contained in the user attributes received by the user attribute receiving module, and selecting at least one service identification corresponding to the selected service platform identification from the service identifications contained in the user attributes; the logic relation identifier selection module is used for selecting a logic relation identifier for indicating the selected logic relation between different service identifiers; the sending module is used for sending the service platform identifier, the service identifier and the logical relationship identifier selected by the logical relationship identifier selection module to the server; and the plug-in list receiving module is used for receiving a plug-in list which is sent by the server and corresponds to the service platform identifier, the service identifier and the logic relation identifier sent by the sending module.

Preferably, the client provided in the embodiment of the present application may further include: the storage unit is used for storing the user attribute received by the user attribute receiving module; a notification message receiving unit, configured to receive a notification message sent by a server and including a service platform identifier and a corresponding service identifier added to the user attribute; the updating unit is used for updating the user attribute stored in the storage unit according to the added service platform identifier and the corresponding service identifier received by the notification message receiving unit; a second sending unit, configured to send, to the server, a plug-in download request carrying the added service platform identifier and the corresponding service identifier included in the user attribute updated by the updating unit; and the second downloading unit is used for downloading the plug-in according to the plug-in list which is sent by the server and corresponds to the added service platform identification and the corresponding service identification which are sent by the second sending unit. Through the units, the client provided by the embodiment of the application can download the plug-ins added correspondingly under the condition that the user attribute changes.

In a preferred embodiment, the first downloading unit 63 can be divided into the following functional modules to avoid the situation of downloading plug-ins repeatedly:

the download list creating module is used for creating a list to be downloaded with empty content; the plug-in identification determining module is used for determining the plug-in identification of the locally stored plug-in and determining the plug-in identification which is inconsistent with the plug-in identification of the locally stored plug-in from the received plug-in list; the plug-in identification adding module is used for adding the plug-in identifications which are determined by the plug-in identification determining module and are not matched with each other into the list to be downloaded; and the plug-in downloading module is used for downloading the plug-ins corresponding to the plug-in identifications added by the plug-in identification adding module in the list to be downloaded when the list to be downloaded created by the downloading list creating module is not empty.

Correspondingly, an embodiment of the present application further provides a server as shown in fig. 7, where the server includes the following functional units:

a first receiving unit 71, configured to receive a plug-in download request carrying a user identifier sent by a host client;

a user attribute searching unit 72, configured to search, from among the stored user attributes of each user identifier, a user attribute of a user identifier carried in the plug-in download request received by the first receiving unit 71;

an identifier determining unit 73, configured to determine the service platform identifier and the service identifier corresponding to the service platform identifier that are included in the user attribute found by the user attribute finding unit 72;

a first plug-in list searching unit 74, configured to search a corresponding plug-in list according to the service platform identifier and the service identifier determined by the identifier determining unit 73, where the searched plug-in list corresponds to at least one service identifier determined by the identifier determining unit 73, and the plug-in list includes at least one plug-in identifier;

a first plug-in list sending unit 75, configured to send the corresponding plug-in list found by the first plug-in list searching unit 74 to the host program client.

In a preferred embodiment, the user attribute searching unit 72 may be divided into the following functional modules to deal with the case that the user identifier carried in the plug-in download request is the user identifier with the reassembly identifier:

the recombination rule determining module is used for determining an identification recombination rule corresponding to the recombination mark from the corresponding relation between the stored recombination mark and the identification recombination rule according to the recombination mark of the user identification carried in the plug-in download request; the identification category determining module is used for determining a corresponding identification category from the corresponding relation between the stored identification categories and the identification recombination rules according to the identification recombination rules determined by the recombination rule determining module; and the user attribute searching module is used for searching the user attribute corresponding to the identification category determined by the identification category determining module from the stored user attributes of the user identifications corresponding to different identification categories according to the user identification carried in the plug-in download request.

In a preferred embodiment, in order to enable the host program client to flexibly select the service platform identifier and the service identifier corresponding to the plug-in to be downloaded, the first plug-in list searching unit 74 may be divided into the following functional modules: a user attribute sending module, configured to send the user attribute found by the user attribute finding unit 72 to the host program client; the identification receiving module is used for receiving at least one service platform identification and at least one service identification corresponding to the service platform identification, which are selected and sent by the host program client according to the service platform identification and the service identification contained in the user attribute sent by the user attribute sending module; and the plug-in list searching module is used for searching the corresponding plug-in list according to the service platform identification and the service identification received by the identification receiving module.

In a preferred embodiment, in order to make the sink

The main program client can timely download the plug-in components corresponding to the added service platform identification and the corresponding service identification, and the server provided by the embodiment of the application can further include: a notification message sending unit, configured to send a notification message to a host program client when a service platform identifier or a service identifier included in a user attribute increases after the user attribute is sent to the host program client by a user attribute sending module, where the notification message includes the increased service platform identifier and a corresponding service identifier; a second receiving unit, configured to receive a plug-in download request sent by the host client, where the plug-in download request includes the added service platform identifier and the corresponding service identifier sent by the notification message sending unit; the second plug-in list searching unit is used for searching the added service platform identification received by the second receiving unit and the plug-in list corresponding to the corresponding service identification; and the second plug-in list sending unit is used for sending the plug-in list searched by the second plug-in list searching unit to the host program client.

In addition, the server provided in the embodiment of the present application may further include: the system comprises a plug-in description file receiving unit, a first receiving unit and a second receiving unit, wherein the plug-in description file receiving unit is used for receiving a submitted plug-in description file before a plug-in downloading request of the first receiving unit, and the plug-in description file comprises a service platform identifier, a service identifier and a plug-in identifier; and the corresponding storage unit is used for correspondingly storing the service platform identifier, the service identifier and the plug-in identifier contained in the plug-in description file received by the plug-in description file receiving unit into the plug-in list.

Those skilled in the art will appreciate that all or part of the steps in the method for implementing the above embodiments may be implemented by relevant hardware instructed by a program, and the program may be stored in a computer readable storage medium, such as: ROM/RAM, magnetic disk, optical disk, etc.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (13)

1. A plug-in acquisition method, comprising:

the method for sending the plug-in downloading request carrying the user identifier to the server by the host program client specifically comprises the following steps: the host program client receives the input identification category and the user identification; according to the input identification category, determining an identification recombination rule corresponding to the input identification category from the corresponding relation between the stored identification category and the identification recombination rule; and according to the determined identification reorganization rule, reorganizing the input user identification; carrying a user identification with a recombination mark obtained after recombination processing on a plug-in downloading request and sending the user identification to a server, wherein the user attribute of the user identification comprises a service platform identification and a service identification corresponding to the service platform identification; and

receiving a plug-in list which is sent by a server and corresponds to the service platform identification and the service identification, wherein the plug-in list comprises all plug-in identifications in the plug-in list corresponding to at least one service identification contained in the user attribute of the user identification, and the plug-ins identified by all the plug-ins in the plug-in list corresponding to the service identification conform to the access specification of the service platform based on the service corresponding to the service identification; and are

And downloading the plug-in according to the received plug-in list.

2. The method of claim 1, wherein receiving a plug-in list corresponding to the service platform identifier and the service identifier sent by a server specifically includes:

the host program client receives the user attribute of the user identification which is determined by the server based on the user identification in the plug-in download request and sent by the server; and are

Selecting at least one service platform identification from the service platform identifications contained in the sent user attribute, and selecting at least one service identification corresponding to the selected service platform identification from the service identifications contained in the sent user attribute; and

sending the selected service platform identification and the selected service identification to a server; and are

And receiving a plug-in list which is sent by the server and corresponds to the service platform identification and the service identification.

3. The method according to claim 1, wherein the host program client receives a plug-in list corresponding to the service platform identifier and the service identifier and sent by a server, and specifically includes:

the host program client receives the user attribute which is determined by the server based on the user identifier in the plug-in download request and is provided with the user identifier; and are

Selecting at least one service platform identification from the service platform identifications contained in the sent user attribute, and selecting at least one service identification corresponding to the selected service platform identification from the service identifications contained in the sent user attribute; and

selecting a logic relation identifier for indicating the logic relation between the selected different service identifiers;

the host program client sends the selected service platform identifier, the selected service identifier and the selected logic relation identifier to the server;

and receiving a plug-in list which is sent by the server and corresponds to the selected service platform identification, the selected service identification and the selected logic relation identification.

4. The method of claim 2 or 3, wherein after receiving the user attributes, the host client further comprises:

the host program client stores the received user attribute; and are

Receiving a notification message sent by a server and added with a service platform identifier and a corresponding service identifier in the user attribute, wherein the notification message comprises the added service platform identifier and the corresponding service identifier; and are

Updating the stored user attribute according to the added service platform identification and the corresponding service identification;

and sending a plug-in downloading request carrying the added service platform identification and the corresponding service identification to a server, and downloading the plug-in according to a plug-in list which is sent by the server and corresponds to the added service platform identification and the corresponding service identification.

5. The method of claim 1, wherein the host program client downloads the plug-in according to the received plug-in list, and specifically comprises:

creating a list to be downloaded with empty content;

determining the plug-in identification of the locally stored plug-in, and determining the plug-in identification which is inconsistent with the plug-in identification of the locally stored plug-in from the received plug-in list;

adding the determined plug-in identifiers which are not matched with each other into a list to be downloaded; and are

And when the list to be downloaded is not empty, downloading the plug-ins corresponding to the plug-in identifications in the list to be downloaded.

6. A plug-in acquisition method, comprising:

receiving a plug-in downloading request carrying a user identifier sent by a host program client, wherein the plug-in downloading request is the identifier category and the user identifier received and input by the host program client; according to the input identification category, determining an identification recombination rule corresponding to the input identification category from the corresponding relation between the stored identification category and the identification recombination rule; and according to the determined identification reorganization rule, reorganizing the input user identification; carrying the user identification with the recombination mark obtained after the recombination treatment on the plug-in downloading request; and

searching the user attributes of the user identifiers carried in the plug-in downloading request from the stored user attributes of the user identifiers, and determining the service platform identifiers and the service identifiers corresponding to the service platform identifiers in the searched user attributes;

searching a corresponding plug-in list according to the determined service platform identification and the service identification, wherein the plug-in list corresponds to at least one service identification, the plug-in list comprises all plug-in identifications in the plug-in list corresponding to at least one service identification contained in the user attribute of the user identification, and the plug-ins identified by all plug-ins in the plug-in list corresponding to the service identification conform to the access specification of the service platform on which the service corresponding to the service identification is based; and

and sending the found corresponding plug-in list to the host program client.

7. The method according to claim 6, wherein when the user identifier carried in the plug-in download request is a user identifier with a reassembly identifier, the searching for the user attribute of the user identifier carried in the plug-in download request specifically includes:

according to the recombination mark, determining an identification recombination rule corresponding to the recombination mark from the corresponding relation between the stored recombination mark and the identification recombination rule;

determining a corresponding identification category from the corresponding relation between the stored identification categories and the identification recombination rules according to the determined identification recombination rules; and are

And searching the user attribute corresponding to the determined identification category from the stored user attributes of the user identifications corresponding to different identification categories according to the user identification carried in the plug-in downloading request.

8. The method according to claim 6, wherein searching for a corresponding plug-in list according to the determined service platform identifier and the service identifier specifically includes:

sending the searched user attribute to the host program client;

receiving at least one service platform identifier and at least one service identifier corresponding to the service platform identifier, which are selected and sent by the host program client according to the service platform identifier and the service identifier contained in the user attribute;

and searching a corresponding plug-in list according to the service platform identification and the service identification sent by the host program client.

9. The method as claimed in claim 8, wherein after sending the found user attribute to the host program client, further comprising:

when the service platform identification and the corresponding service identification contained in the user attribute are increased, sending a notification message to the host program client, wherein the notification message contains the increased service platform identification and the corresponding service identification; and are

And when receiving the plug-in list which is sent by the host program client and contains the added service platform identification and the corresponding service identification, searching the plug-in list corresponding to the added service platform identification and the corresponding service identification and sending the plug-in list to the host program client.

10. The method of claim 6, wherein before receiving the plug-in download request carrying the user identifier from the host client, the method further comprises:

receiving a submitted plug-in description file, wherein the plug-in description file comprises a service platform identifier, a service identifier and a plug-in identifier;

and correspondingly storing the service platform identifier, the service identifier and the plug-in identifier contained in the plug-in description file into a plug-in list.

11. A plug-in acquisition system comprising a host client and a server, wherein:

the host program client is used for sending a plug-in downloading request carrying a user identifier to the server, and specifically comprises: the host program client receives the input identification category and the user identification; according to the input identification category, determining an identification recombination rule corresponding to the input identification category from the corresponding relation between the stored identification category and the identification recombination rule; and according to the determined identification reorganization rule, reorganizing the input user identification; carrying a user identification with a recombination mark obtained after recombination processing on a plug-in downloading request and sending the user identification to a server, wherein the user attribute of the user identification comprises a service platform identification and a service identification corresponding to the service platform identification, and downloading the plug-in according to a plug-in list which is sent by the server and corresponds to the service platform identification and the service identification, wherein the plug-in list comprises all plug-in identifications in the plug-in list corresponding to at least one service identification contained in the user attribute of the user identification, and the plug-ins identified by all plug-ins in the plug-in list corresponding to the service identification conform to the access specification of the service platform on which the service corresponding to the service identification is based;

the server is used for receiving the plug-in downloading request sent by the host program client, searching the user attribute of the user identifier carried in the plug-in downloading request from the stored user attributes of each user identifier, and determining the service platform identifier and the service identifier corresponding to the service platform identifier in the searched user attribute; searching a corresponding plug-in list according to the determined service platform identification and the service identification, and sending the searched corresponding plug-in list to the host program client; wherein the plug-in list corresponds to at least one of the service identifiers.

12. A host client, comprising:

the first sending unit is configured to send a plug-in download request carrying a user identifier to a server, and specifically includes: the host program client receives the input identification category and the user identification; according to the input identification category, determining an identification recombination rule corresponding to the input identification category from the corresponding relation between the stored identification category and the identification recombination rule; and according to the determined identification reorganization rule, reorganizing the input user identification; carrying a user identification with a recombination mark obtained after recombination processing on a plug-in downloading request and sending the user identification to a server, wherein the user attribute of the user identification comprises a service platform identification and a service identification corresponding to the service platform identification;

a plug-in list receiving unit, configured to receive a service platform identifier included in the user attribute of the user identifier and a plug-in list corresponding to the service identifier, where the service platform identifier and the plug-in list are sent by a server and included in the user attribute of the user identifier sent by the first sending unit, the plug-in list includes each plug-in identifier in the plug-in list corresponding to at least one service identifier included in the user attribute of the user identifier, and a plug-in identified by each plug-in the plug-in list corresponding to the service identifier conforms to an access specification of a service platform on which a service corresponding to the service identifier is;

and the first downloading unit is used for downloading the plug-in according to the plug-in list received by the plug-in list receiving unit.

13. A server, comprising:

the first receiving unit is used for receiving a plug-in downloading request carrying a user identifier sent by a host program client, wherein the plug-in downloading request is the identifier category and the user identifier received and input by the host program client; according to the input identification category, determining an identification recombination rule corresponding to the input identification category from the corresponding relation between the stored identification category and the identification recombination rule; and according to the determined identification reorganization rule, reorganizing the input user identification; carrying the user identification with the recombination mark obtained after the recombination treatment on the plug-in downloading request;

the user attribute searching unit is used for searching the user attribute of the user identifier carried in the plug-in downloading request received by the first receiving unit from the stored user attributes of each user identifier;

the identification determining unit is used for determining the service platform identification and the service identification corresponding to the service platform identification which are included in the user attributes searched by the user attribute searching unit;

a first plug-in list searching unit, configured to search a corresponding plug-in list according to the service platform identifier and the service identifier determined by the identifier determining unit, where the plug-in list corresponds to at least one service identifier, the plug-in list includes each plug-in identifier in the plug-in list corresponding to at least one service identifier included in a user attribute of the user identifier, and a plug-in identified by each plug-in the plug-in list corresponding to the service identifier meets an access specification of a service platform on which a service corresponding to the service identifier is based;

and the first plug-in list sending unit is used for sending the corresponding plug-in list searched by the first plug-in list searching unit to the host program client.