CN113760382B

CN113760382B - Plug-in starting method and device, terminal equipment and storage medium

Info

Publication number: CN113760382B
Application number: CN202011103659.1A
Authority: CN
Inventors: 郝文欣; 章�露�; 贾侦修; 王斌; 李泱
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2020-10-15
Filing date: 2020-10-15
Publication date: 2024-05-17
Anticipated expiration: 2040-10-15
Also published as: CN113760382A

Abstract

The embodiment of the invention discloses a plug-in starting method, a device, terminal equipment and a storage medium, wherein the method comprises the following steps: the client sends a triggering instruction of the function entry to the server so that the server judges whether the function entry is provided with an intercommunication protocol or not, and if so, the client inquires plug-in information according to the intercommunication protocol; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins; and the client starts the plugin according to the plugin information fed back by the server and the protocol information of the intercommunication protocol deployed by the function portal. By deploying the intercommunication protocol for the function entry, the function entry of the client can correspond to a plurality of plugins, so that the function entry is utilized to replace the traditional plugin entry, and each function can be conveniently triggered by a user; in addition, the server side can ensure that the client side can perform normal plug-in starting according to the corresponding plug-in information when judging that the triggered function entry deploys the intercommunication protocol.

Description

Plug-in starting method and device, terminal equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of computers, in particular to a plug-in starting method, a plug-in starting device, terminal equipment and a storage medium.

Background

In the prior art, an Application (APP) will typically tile the entry of some plug-ins on top of the head screen. After a user clicks an entry of a certain plug-in, the APP can start the plug-in to realize a corresponding function, where the functions realized by the APP starting different plug-ins may be the same or different.

In the process of implementing the present invention, the inventor finds that at least the following technical problems exist in the prior art: because the number of the inlets is limited and the number of the plug-ins is more, the plug-ins with some business functions cannot be displayed on the first screen, and when a user needs to trigger the plug-ins with functions not on the first screen, the user needs to enter a second-level interface to search, so that the plug-ins are complicated in starting steps, and user experience is reduced.

Disclosure of Invention

The embodiment of the invention provides a plug-in starting method, a device, terminal equipment and a storage medium, which can realize more convenient plug-in starting and improve user experience.

In a first aspect, an embodiment of the present invention provides a method for starting a plug-in, which is applied to a client, and includes:

Sending a triggering instruction of a function entry to a server side so that the server side judges whether an intercommunication protocol is deployed in the function entry, and if yes, inquiring plug-in information according to the intercommunication protocol; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

And receiving plug-in information fed back by the server side and protocol information of the intercommunication protocol, and starting the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entrance.

In a second aspect, an embodiment of the present invention provides a method for starting a plug-in, which is applied to a server, and includes:

Responding to a triggering instruction of a function entry sent by a client, judging whether the function entry is provided with an intercommunication protocol, and inquiring plug-in information according to the intercommunication protocol if the function entry is provided with the intercommunication protocol; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

And feeding back the plug-in information and the protocol information of the intercommunication protocol to the client so that the client starts the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entry.

In a third aspect, an embodiment of the present invention provides a plug-in starting apparatus, applied to a client, including:

The access triggering module is used for sending a triggering instruction of the function access to the server so that the server judges whether the function access is provided with an intercommunication protocol or not, and if yes, the server inquires plug-in information according to the intercommunication protocol; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

And the plug-in starting module is used for receiving the plug-in information fed back by the server and the protocol information of the intercommunication protocol, and starting the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entrance.

In a fourth aspect, an embodiment of the present invention provides a plug-in starting apparatus, which is applied to a server, including:

The plug-in information determining module is used for responding to a triggering instruction of a function entry sent by the client and judging whether the function entry is provided with an intercommunication protocol, if so, the plug-in information is queried according to the intercommunication protocol; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

And the information feedback module is used for feeding back the plug-in information and the protocol information of the intercommunication protocol to the client so that the client starts the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entrance.

In a fifth aspect, an embodiment of the present invention provides a terminal device, including:

one or more processors;

A memory for storing one or more programs;

The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the plug-in launch method according to any embodiment of the present invention.

In a sixth aspect, an embodiment of the present invention provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements a plug-in starting method according to any embodiment of the present invention.

According to the plug-in starting method, device, terminal equipment and storage medium provided by the embodiment of the invention, a client sends a triggering instruction of a function entry to a server so that the server judges whether an intercommunication protocol is deployed in the function entry, and if so, plug-in information is queried according to the intercommunication protocol; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins; and the client starts the plugin according to the plugin information fed back by the server and the protocol information of the intercommunication protocol deployed by the function portal. By deploying the intercommunication protocol for the function entry, the function entry of the client can correspond to a plurality of plugins, so that the function entry is utilized to replace the traditional plugin entry, and each function can be conveniently triggered by a user; in addition, the server side can ensure that the client side can perform normal plug-in starting according to the corresponding plug-in information when judging that the triggered function entry deploys the intercommunication protocol.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description will be given below of the drawings required for the embodiments or the prior art descriptions, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 shows a flowchart of a plug-in starting method according to a first embodiment of the present invention;

Fig. 2 is an interface schematic diagram of a client in a plug-in starting method according to a first embodiment of the present invention;

Fig. 3 shows a flowchart of a plug-in starting method according to a second embodiment of the present invention;

Fig. 4 shows a flowchart of a plug-in starting method according to a third embodiment of the present invention;

Fig. 5 shows a flowchart of a plug-in starting method according to a fourth embodiment of the present invention;

Fig. 6 is a schematic diagram of an architecture supporting plug-in startup in a plug-in startup method according to a fifth embodiment of the present invention;

Fig. 7 is a schematic structural diagram of a plug-in starting device according to a seventh embodiment of the present invention;

Fig. 8 is a schematic structural diagram of a plug-in starting device according to an eighth embodiment of the present invention;

Fig. 9 shows a schematic hardware structure of a terminal device according to a ninth embodiment of the present invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described by means of implementation examples with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention. In the following embodiments, optional features and examples are provided in each embodiment at the same time, and the features described in the embodiments may be combined to form multiple alternatives, and each numbered embodiment should not be considered as only one technical solution.

Example 1

Fig. 1 shows a flowchart of a plug-in starting method provided by the first embodiment of the present invention, where the plug-in starting method provided by the first embodiment of the present invention is applicable to a case of plug-in starting, for example, a case of starting a corresponding plug-in by triggering a function entry of a home page of a client. The method may be performed by a plug-in enabling device implemented in software and/or hardware, preferably in a terminal device, for example in a terminal-device such as a smart phone, tablet, notebook, etc. As shown in fig. 1, the plug-in starting method provided in the embodiment of the present invention is applied to a client, and includes the following steps:

S110, sending a triggering instruction of the function entry to the server side so that the server side can judge whether the function entry is provided with an intercommunication protocol or not, and if so, inquiring plug-in information according to the intercommunication protocol.

In the embodiment of the invention, the function portal can represent a portal for realizing service functions, and the portal can be arranged in the client APP interface, for example, the portal can be arranged in the first screen interface. Functional portals corresponding to various service functions can be set in an APP interface of the client, and when a user operation acts on any one functional portal position in the interface, for example, when the user clicks any one functional portal in the interface, the client can respond to the user operation to generate a trigger instruction of the corresponding functional portal. The client can interact with the server based on the trigger instruction to complete the starting of a certain plug-in for the service function capable of realizing the function entry characterization.

The number of the plug-ins capable of realizing the service functions represented by the function inlets can be multiple, and in the embodiment, by enabling all the plug-ins realizing the same service function to meet the same protocol, the effect that one function inlet is used for replacing a plurality of plug-in inlets for realizing one service function in the traditional scheme in the client interface can be achieved, and each function can be conveniently triggered by a user. The protocol corresponding to the same service function may be regarded as the interworking protocol of the function entry deployment proposed in the present embodiment. The function entrance with the deployed intercommunication protocol corresponds to at least two plug-ins.

To ensure user experience, the client may support a user to select a plug-in that is started when the function portal is triggered from among a plurality of plug-ins that satisfy the interworking protocol of the function portal. Correspondingly, the server can record the plug-in which is selected to be started by each function entry in each client into the intercommunication protocol. When the server receives a trigger instruction of the client to a certain function entry, whether the function entry is deployed with an intercommunication protocol can be judged, if so, a plug-in selected by the client for the function entry can be searched from a record of the intercommunication protocol, and plug-in information is determined according to the searched plug-in. In addition, when the client does not select the plug-in information for the triggered function entry, the server may also search the plug-in information that is generated according to the plug-in recommended to the user in the interworking protocol, or may be plug-in information that is generated according to all plug-ins corresponding to the interworking protocol of the function entry, which is not exhaustive herein.

S120, receiving plug-in information and protocol information of an intercommunication protocol fed back by the server side, and starting the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entry.

In this embodiment, after receiving the plug-in information fed back by the server, the client APP may determine the plug-in information of the plug-in to be started, and may open a detail function page of the plug-in to be started at the client interface, that is, start the plug-in. The client executes the process of opening the plug-in detail function page, and can request the server again according to the plug-in information of the plug-in to be started and the protocol information of the intercommunication protocol so that the server finds the corresponding plug-in development terminal; and analyzing the plug-in information by using the plug-in development terminal to carry out corresponding jump, and reaching the detail page corresponding to the functional scene.

By deploying the intercommunication protocol for the function entry, when the service end deploys the intercommunication protocol for the function entry triggered by the client end, the corresponding plug-in information can be fed back, and the client end can start a certain plug-in corresponding to the function entry based on the intercommunication protocol, so that the normal start of the plug-in is ensured.

In some alternative embodiments, the plug-in activation method further comprises: sending a triggering instruction of the function entry to a server side so that the server side judges whether the function entry is provided with an intercommunication protocol or not, and if not, inquiring plug-in starting information; and receiving plug-in starting information fed back by the server side, and starting the plug-in according to the plug-in starting information.

For some service functions in the client, there are cases where only one plug-in can support the service functions. In this case, the function portal for implementing these service functions is characterized without implementing the interworking protocol. When the function entry of the undeployed intercommunication protocol in the client is triggered, the server can directly feed back the plug-in starting information based on the triggering instruction, wherein the plug-in starting information can be, for example, a uniform resource locator (Uniform Resource Locator, URL), a key of an applet, or other starting information, and is not exhaustive.

The plug-in starting information and the corresponding relation between the function entry and the plug-in starting information can be maintained in the server in advance, and the step of determining the plug-in starting information by the server can be as follows: acquiring an application program interface (Application Programming Interface, API) of the function entry by analyzing the trigger instruction; and based on the corresponding relation between the function entry and the plug-in starting information, the plug-in starting information corresponding to the function entry is searched.

Correspondingly, after receiving the plug-in starting information corresponding to the function entry, the client can directly start the plug-in based on the plug-in starting information, and the plug-in starting is not required to be performed according to the intercommunication protocol. For example, the client may directly access the URL to open the corresponding functional details page of the plug-in, or directly invoke the applet according to the applet key.

Fig. 2 is an interface schematic diagram of a client in a plug-in startup method according to an embodiment of the present invention. In order to highlight the advantage of the functional portal in the client interface in the embodiment of the present invention, the existing client interface is also shown in fig. 2. Referring to fig. 2, (a) is an interface schematic diagram of a client APP in the market, and (b) is an interface schematic diagram of the client APP in the present embodiment.

In the existing APP interface, plug-ins implementing various service functions are tiled in a functional scene entry area, for example, plug-in entries such as "function a-plug-in 1" and "function a-plug-in 2" are tiled, and these entries usually support user editing. When the number of the plug-in inlets corresponding to the single service function is large after the user editing, the display of the plug-in inlets corresponding to other service functions is liable to be reduced, and the situation that some plug-ins with the service functions cannot be displayed on the interface easily occurs. The situation not only affects the business function to perform flow rate change, but also needs to enter a secondary interface to search when a user needs to trigger a plug-in of the function not in the interface, so that the plug-in starting step is complicated.

In the interface schematic diagram of the client APP provided in this embodiment, function portals corresponding to each function service are displayed in the function scene portal area, for example, function portals such as "function a" and "function B" are displayed. When the function portal is deployed with an interworking protocol, the function portal can correspond to a plurality of plugins, and can support a user to select a plugin started when the function portal is triggered from the plurality of plugins corresponding to the function portal. The plug-in that is started when the function entry is triggered may be selected based on a setting control in the interface, and the setting control may be, for example, a gear type control in the (b) diagram, or another type control, where the position of the setting control is designed to be set in a region that is easier to find, which is not limited in particular.

For example, if the user sets the plugin 1 for the function a in advance as a plugin started when the function a triggers the function entry, when the function entry "function a" in the client interface is triggered, the server may feed back plugin information corresponding to the plugin 1; the client can request the server again according to the plug-in information corresponding to the plug-in 1 and the intercommunication protocol corresponding to the function entry function A so that the server can find the plug-in development end of the plug-in 1; and analyzing the plug-in information of the plug-in 1 by using the plug-in development terminal to carry out corresponding jump to reach the detail page corresponding to the function A.

By deploying the intercommunication protocol for the function portal, the function portal can be used for replacing the plug-in portal in the interface, so that the platform can introduce more third-party plug-ins or develop plug-ins for some core function scenes, and the portal position is not occupied in the interface. For users, each service function has a function entry in the primary interface, so that each function can be conveniently triggered by the user, and plug-in units with the best functions and experience can be selected for use, thereby greatly improving the user experience. For the third party developer, only the plug-in with better development and use experience and more comprehensive functions can acquire more flow on the platform, so that fair competition of the third party developer is realized. For the platform, the entrance position in each interface is utilized efficiently, better experience can be provided for users, better flow rate can be realized, and better ecological value of the platform is built.

According to the plug-in starting method provided by the embodiment of the invention, the client sends the triggering instruction of the function entrance to the server, so that when the server deploys an intercommunication protocol in the function entrance, corresponding plug-in information is fed back; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins; and the client starts the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entry. By deploying the intercommunication protocol for the function entry, the function entry of the client can correspond to a plurality of plugins, so that the function entry is utilized to replace the traditional plugin entry, and each function can be conveniently triggered by a user; in addition, the server side can ensure that the client side can perform normal plug-in starting according to the corresponding plug-in information when judging that the triggered function entry deploys the intercommunication protocol.

Example two

Based on the embodiment, the method subdivides the plug-in information, optimizes the plug-in starting step according to different plug-in information, and enriches the starting modes of plug-in starting. The present embodiment and the plug-in starting method proposed in the foregoing embodiment belong to the same inventive concept, and technical details that are not described in detail in the present embodiment can be seen in the foregoing embodiment.

Fig. 3 shows a flowchart of a plug-in starting method according to a second embodiment of the present invention. Referring to fig. 3, the plug-in starting method includes the following steps:

s310, sending a triggering instruction of the function entry to the server side so that the server side judges whether the function entry is provided with an intercommunication protocol or not, and if so, inquiring plug-in information according to the intercommunication protocol.

The function entrance with the deployed intercommunication protocol corresponds to at least two plug-ins.

The plug-in information is a plug-in identifier or a plug-in list; the plug-in identification is the plug-in identification of the default starting plug-in corresponding to the function entry acquired by the server; the plug-in list is determined by the server according to the plug-ins downloaded by the client and corresponding to the intercommunication protocol.

In this embodiment, the default starting plug-in of the function entry may be considered as a plug-in started when the function entry is triggered, which is set by the user; the plug-in identification can be considered as an identification of a unique corresponding plug-in, and can be composed of at least one element such as characters, numbers, special symbols and the like; the plug-in list may be considered to be a list containing one or more plug-in identifications.

When the user has set a plug-in started when the function entry is triggered, the plug-in information fed back can be a plug-in identifier of a default starting plug-in corresponding to the function entry; when the user does not set a plug-in started when triggering the function entry, the plug-in information fed back can be a plug-in list.

In some alternative embodiments, the plug-in activation method further comprises: and calling a setting interface of the server in response to the plug-in setting operation of the function entry, so that the server sets a default starting plug-in for the function entry through the setting interface.

In these embodiments, when a setting control in the client interface is triggered, the setting interface may be opened, and multiple plugins corresponding to each function entry may be presented in the setting interface; the client can receive the selected operation of any plug-in a plurality of plug-ins and can take the selected operation as the plug-in setting operation of the function entry; and responding to the plug-in setting operation of the function entry, and calling a setting interface of the server to set a default starting plug-in for the function entry. Through the setting step, the first setting of the default starting plug-in of the function inlet can be realized, and the set default starting plug-in can be changed, so that the user can be supported to select the plug-in with the best function and experience, and the user experience is improved.

S320, receiving plug-in information and protocol information of an intercommunication protocol fed back by the server side.

S331, when the plug-in information is a plug-in identifier, plug-in starting is performed according to the plug-in identifier and protocol information of the intercommunication protocol deployed by the function entry.

In the process of starting the plug-in according to the plug-in identification, the client can start the plug-in without perception of a user. Namely, when the received plug-in information is a plug-in identification and protocol information of an intercommunication protocol of a function entrance fed back by the server is also received, the server can be automatically requested according to the plug-in identification and the protocol information of the intercommunication protocol, so that the server can find a corresponding plug-in development terminal; and analyzing the plug-in information by using the plug-in development terminal to carry out corresponding jump, and reaching the detail page corresponding to the functional scene.

And S332, when the plug-in information is a plug-in list, responding to the selection operation of the plug-in identification in the plug-in list, and starting the plug-in according to the selected plug-in identification and the protocol information of the intercommunication protocol deployed by the function entry.

In the process that the client starts the plugins according to the plugin list, the client pops up a popup window interface according to the plugin list, and each plugin identifier in the plugin list and a selection control of each plugin identifier can be displayed in the popup window interface; then, the client can respond to the selection operation of the selection control of the plug-in identification, and plug-in starting is carried out according to the selected plug-in identification and the protocol information of the intercommunication protocol deployed by the function entry.

In addition, in response to the selection operation of the plug-in identifier in the plug-in list, the client can start the plug-in, and can set the plug-in corresponding to the selected plug-in identifier as a default starting plug-in, so that the first setting of the default starting plug-in can be realized under the condition that the user does not set the default starting plug-in of the function entry yet, but the function entry is triggered for the first time, the setting mode of the default starting plug-in is enriched, and the user experience is further improved.

In some alternative embodiments, the starting of the plugin according to the plugin identification and the protocol information of the interworking protocol deployed by the function portal includes: and taking the protocol identifier and the protocol parameter of the intercommunication protocol deployed by the plug-in identifier and the function entry as calling parameters, calling a plug-in starting interface of the server side so that the server side obtains plug-in starting information corresponding to the plug-in identifier through the plug-in starting interface, splicing the protocol identifier and the protocol parameter with the plug-in starting information, and starting the plug-in according to a splicing result.

The plug-in identification in the calling parameter can be the plug-in identification fed back to the client by the server, or the plug-in identification selected from the plug-in list by the client. The protocol information of the interworking protocol may include a protocol identifier and a protocol parameter. Wherein, since the interworking protocols of the function portals are different, the identity of the API of the function portal can be used as the protocol identity. Wherein the protocol parameter may be a path parameter related to a detail page presented after the plug-in is started. The client side performs plug-in calling based on the plug-in identification and the protocol information, so that the functional detail page can be ensured to be presented at the client side.

After the client calls the plug-in starting interface of the server, firstly, the server can search the plug-in starting information corresponding to the plug-in identifier, for example, the plug-in starting information can be a home page URL or an applet key of the plug-in; then, the protocol identification and the protocol parameter can be spliced after the plug-in starting information; finally, the new plug-in starting information obtained by splicing can be sent to a development end of the plug-in; when receiving the spliced plug-in starting information, the development terminal can analyze the protocol identification and the protocol parameters based on the realized intercommunication protocol and carry out corresponding jump.

By splicing the protocol identification and the protocol parameter to the plug-in starting information, the page corresponding to the functional scene can be presented at the client instead of the plug-in opening page, and user experience is improved.

Based on the embodiment, the embodiment of the invention subdivides the plug-in information, optimizes the plug-in starting step according to different plug-in information, and enriches the starting mode of plug-in starting. In addition, the embodiment of the present invention and the plug-in starting method proposed by the foregoing embodiment belong to the same inventive concept, and technical details not described in detail in this embodiment can be seen in the foregoing embodiment, and this embodiment has the same beneficial effects as the foregoing embodiment.

Example III

Fig. 4 shows a flowchart of a plug-in starting method according to a third embodiment of the present invention, where the plug-in starting method according to the third embodiment of the present invention is applicable to a case of plug-in starting, for example, a case that a background server feeds back plug-in information according to a trigger instruction of a function entry of a first page of a client, so that the client starts a corresponding plug-in according to the plug-in information. The method may be performed by a plug-in enabling device implemented in software and/or hardware, preferably arranged in a terminal device, e.g. in a server. The embodiment of the present invention and the method for starting the plug-in unit applied to the client provided by the above embodiment belong to the same inventive concept, and technical details not described in detail in this embodiment can be referred to the above embodiment, and are not described herein.

As shown in fig. 4, the plug-in starting method provided in the embodiment of the present invention is applied to a server, and includes the following steps:

S410, responding to a triggering instruction of the function entry sent by the client, judging whether the function entry is provided with an intercommunication protocol, and if so, inquiring plug-in information according to the intercommunication protocol.

In this embodiment, the server may maintain a correspondence between each function entry in the APP and the interworking protocol, for example, the identifier of the API of each function entry may be set as the protocol identifier of the interworking protocol. When the server receives a trigger instruction for triggering the function entry sent by any client, the server can judge that the function entry is not deployed with an intercommunication protocol according to the API information of the function entry in the trigger instruction.

When there is a protocol identifier matched with the parsed information of the API, the server may further determine plug-in information corresponding to the function entry of the client that sends the trigger instruction. The determining the corresponding plug-in information may be, for example, determining plug-in information of a plug-in selected by the client for the function entry in a record of the server according to the intercommunication protocol; for example, when the client does not select the plugin information for the triggered function entry, the server searches for plugins recommended to the user for use in the interworking protocol, and generates plugin information according to plugins recommended to the user for use, or may be plugin information generated according to all plugins corresponding to the interworking protocol of the function entry, and the like.

S420, feeding back the plug-in information and the protocol information of the intercommunication protocol to the client so that the client starts the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entrance.

In this embodiment, after the plug-in information is fed back to the client, the client may determine plug-in information of a plug-in to be started from the fed-back plug-in information, and may open a detail function page of the plug-in to be started at the client interface, that is, start the plug-in. The client executes the process of opening the plug-in detail function page, and may request the server again according to the plug-in information of the plug-in to be started and the protocol information of the intercommunication protocol, so that the server finds a corresponding plug-in development terminal; and analyzing the plug-in information by using the plug-in development terminal to carry out corresponding jump, and reaching the detail page corresponding to the functional scene.

In some optional embodiments, feeding back protocol information of an interworking protocol to the client includes: the protocol identification and the protocol parameters of the intercommunication protocol deployed by the function entrance are fed back to the client;

correspondingly, the plug-in starting method further comprises the following steps: receiving a plug-in starting interface call request of a client, and analyzing call parameters of the call request to obtain a plug-in identifier, a protocol identifier and protocol parameters; and acquiring plug-in starting information corresponding to the plug-in identification through a plug-in starting interface, splicing the protocol identification, the protocol parameter and the plug-in starting information, and starting the plug-in according to the splicing result.

The server side can obtain the plug-in identification, the protocol identification and the protocol parameter to analyze according to the call parameters in the call request according to the communication fixed format of the plug-in starting interface. After the server side analyzes the plug-in identification, the protocol identification and the protocol parameter, firstly, plug-in starting information corresponding to the plug-in identification can be searched, for example, a home page URL or an applet key of the plug-in; then, the protocol identification and the protocol parameter can be spliced after the plug-in starting information; and finally, the new plug-in starting information obtained by splicing can be sent to the development end of the plug-in. When receiving the spliced plug-in starting information, the development terminal can analyze the protocol identification and the protocol parameters based on the realized intercommunication protocol and carry out corresponding jump.

For example, assuming that the plug-in identifier parsed by the server is "plug-in 1", the protocol identifier is "functionA" corresponding to the function entry "function a", and the protocol parameter is "param1= ceshi, param2=test", the server may implement the following steps through the plug-in start interface:

Firstly, corresponding starting information of a plug-in identification 'plug-in 1' is searched, for example, https:// plugin1.Com; then, the protocol identifier "functionA" and the protocol parameter "param1= ceshi, param2=test" may be spliced to the start information, specifically, the content may be spliced by using a splicer, and the splicer may be "&" for example, and the obtained splicing result may be https:// plugin 1.compi= functionA & param1= ceshi & param2=test; and finally, the new plug-in starting information obtained by splicing can be sent to the development end of the plug-in.

In some alternative embodiments, the plug-in starting method may further include: if the function entry is not deployed with the intercommunication protocol, inquiring plug-in starting information; and feeding back the plug-in starting information to the client so that the client starts the plug-in according to the plug-in starting information.

For some service functions in the client, there are cases where only one plug-in can support the service functions. In this case, the function portal for implementing these service functions is characterized without implementing the interworking protocol. When the function entry of the client where the interworking protocol is not deployed is triggered, the server may directly feed back the plug-in startup information based on the trigger instruction, where the plug-in startup information may be, for example, a URL, may be, for example, a key of an applet, or may be other startup information, which is not exhaustive herein.

The plug-in starting information and the corresponding relation between the function entry and the plug-in starting information can be maintained in the server in advance, and the step of determining the plug-in starting information by the server can be as follows: acquiring an API of a function entry by analyzing the trigger instruction; and based on the corresponding relation between the function entry and the plug-in starting information, the plug-in starting information corresponding to the function entry is searched.

In some alternative embodiments, the plug-in starting method may further include: and receiving a call request of a setting interface of the client, and setting a default starting plug-in for the function entry through the setting interface.

In this embodiment, when the setting interface of the server is called by any client, the client identifier, the protocol identifier corresponding to the function entry and the plug-in identifier of the plug-in selected by the user may be parsed and the plug-in corresponding to the plug-in identifier may be set as a default starting plug-in of the function entry of the client. The server may also record a default startup plugin for each function entry in each client, for example, using a database table, for example, a MySQL table, for subsequent lookup of the default startup plugin.

According to the plug-in starting method provided by the embodiment of the invention, when the server side judges that the triggered function entry deploys the intercommunication protocol, the client side can be ensured to perform normal plug-in starting according to the corresponding plug-in information fed back. In addition, the embodiment of the present invention and the plug-in starting method proposed by the foregoing embodiment belong to the same inventive concept, and technical details not described in detail in this embodiment can be seen in the foregoing embodiment, and this embodiment has the same beneficial effects as the foregoing embodiment.

Example IV

Based on the above embodiment, the step of determining the plug-in information is optimized, and specifically, the determination of the plug-in information can be implemented by calling a protocol addressing interface of the server. The present embodiment and the plug-in starting method proposed in the foregoing embodiment belong to the same inventive concept, and technical details that are not described in detail in the present embodiment can be seen in the foregoing embodiment.

Fig. 5 shows a flowchart of a plug-in starting method according to a fourth embodiment of the present invention. Referring to fig. 5, the plug-in starting method includes the following steps:

s510, responding to a triggering instruction of the function entry sent by the client, and judging whether the function entry is provided with an intercommunication protocol by calling a protocol analysis interface.

S520, if yes, calling a protocol addressing interface to determine a plug-in list according to plug-ins downloaded by the client and plug-ins corresponding to the intercommunication protocol.

The server may determine whether the function entry is configured with a function protocol by calling a protocol parsing interface, and the determining step may be, for example: analyzing the information of the API triggering the function entrance in the instruction; judging whether a protocol identifier matched with the parsed API information exists or not; when the matched protocol identification exists, the function entry can be considered to be deployed with an interworking protocol, and when the matched protocol identification does not exist, the function entry can be considered to be not deployed with the interworking protocol.

In some platform-class client APP, the plug-in provided by the third party development terminal, or self-developed by the platform, capable of implementing the service function may be a charging plug-in. After the client purchases a certain plug-in, the plug-in can be downloaded to realize the business function corresponding to the plug-in.

After the server side calls the protocol addressing interface, the following steps can be implemented firstly: based on the client end identification carried in the triggering instruction, pulling the plug-in identification of all the plug-ins corresponding to the client end identification from the position (for example, the plug-in center) where the plug-in downloading condition is maintained; meanwhile, based on the protocol identification matched with the triggering instruction, the plug-in identification of all plug-ins for realizing the intercommunication protocol can be searched from the position (such as the intercommunication center) for maintaining the plug-ins corresponding to the intercommunication protocol; and the plug-in identification corresponding to the pulled client and the plug-in identification corresponding to the searched intercommunication protocol can be intersected, and a plug-in list is generated according to the plug-in identification in the intersection.

S530, obtaining the plug-in identification of the default starting plug-in corresponding to the function entry, and judging whether the plug-in identification of the default starting plug-in is contained in the plug-in list.

After the server invokes the protocol addressing interface to determine the plug-in list, a default startup plug-in for the function entry in the client may also be obtained from the record. Because the plug-in supporting the service function in the platform often carries out operations such as loading or unloading due to factors such as function realization conditions, the plug-in identification in the determined plug-in list often changes, and whether the default starting plug-in set by a user can still support the service function corresponding to the function entry at present can be judged by judging whether the plug-in identification of the default starting plug-in is contained in the plug-in list.

S541, if yes, taking a plug-in identification of a default starting plug-in as plug-in information.

When the plug-in identification of the default starting plug-in set by the user is contained in the plug-in list, the default starting plug-in set by the user is considered to be not put off the shelf at present and can be used for realizing the service function corresponding to the function entrance, and at the moment, the plug-in identification of the default starting plug-in can be fed back to the client so that the client starts the default starting plug-in.

S542, if not, taking the plug-in list as plug-in information.

When the plug-in identification of the default starting plug-in set by the user is not contained in the plug-in list, the default starting plug-in set by the user is considered to be started, and currently the default starting plug-in set by the user is started and cannot be used for realizing the service function corresponding to the function entry, and at the moment, the plug-in list can be fed back to the client so that the user can reselect the default starting plug-in.

S550, the plug-in information and the protocol information of the intercommunication protocol are fed back to the client, so that the client starts the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entrance.

In this embodiment, the service end can implement the addressing service by calling the protocol addressing interface, that is, implement the service of determining the plug-in list and obtaining the plug-in identifier of the default starting plug-in. The high-efficiency stable addressing service is crucial to ensuring the user experience of the corresponding plug-in unit of the client start function entrance, in some optional embodiments, the addressing service can be supported by a distributed system, and it can be considered that in the process of calling a protocol addressing interface, data of all operation links can be obtained from a distributed deployed cache server, the master cache server and the slave cache server synchronize data in near real time, if a problem occurs, the master cache server can quickly cut off the data obtained from the cache server in the second level, the stability of data reading and writing is ensured, and therefore the situation that the user experience is reduced due to unstable database or poor performance can be avoided. In addition, in the process of calling the protocol addressing interface, the data calculation process can be carried out in a Java virtual machine (Java Virtual Machine, JVM), and the high efficiency and stability of the addressing service can be further ensured.

In some alternative embodiments, after invoking the protocol addressing interface, it may further comprise: and asynchronously sending the log generated by calling the protocol addressing interface to a preset message queue so as to carry out statistical analysis of preset dimensionality according to the log in the preset message queue.

In these alternative embodiments, the server may record an asynchronous interworking addressing log after each call to the addressing interface, specifically, after asynchronously sending the interworking addressing log to a Message Queue (MQ), the server consumes the MQ storage log, so as to ensure that the main flow operation of the server is not affected. The server consumption MQ may store the log in a correlation table commonly used for big data, such as a relational database (for example, a Dom database) or a basic scientific index database (ESSENTIAL SCIENCE indexes, abbreviated as ESI), so as to facilitate big data statistical analysis. Wherein, based on the intercommunication addressing log, the following dimension statistical analysis can be realized at least as follows: and counting the number of users, the user duty ratio and the like of the default starting plugins, or setting the number, the duty ratio and the like of each plugin serving as the default starting plugin for each intercommunication inlet for analysis. Through carrying out statistical analysis of preset dimensions on the logs, a platform operator can be guided to carry out platform optimization, and user experience is further improved.

Based on the embodiment, the step of determining the plug-in information is optimized, and the determination of the plug-in information can be realized by calling a protocol addressing interface of the server. In addition, the embodiment of the present invention and the plug-in starting method proposed by the foregoing embodiment belong to the same inventive concept, and technical details not described in detail in this embodiment can be seen in the foregoing embodiment, and this embodiment has the same beneficial effects as the foregoing embodiment.

Example five

According to the embodiment, on the basis of the embodiment, the step that the developing end applies for the access plug-ins to the service end is optimized, and compared with the technical support that the service end needs to display each access plug-in the APP first screen or the second interface in the traditional technical scheme, in the scheme provided by the embodiment of the invention, the service end can maintain the corresponding plug-ins of the function entrance only by the developing end developing the plug-ins according to the intercommunication protocol and executing the flow of applying for the access plug-ins, so that the maintenance difficulty of the plug-ins can be reduced. And the architecture supporting plug-in starting is also described, and modules involved in the flow of the plug-in of the client starting end are supplemented.

In some alternative embodiments, the plug-in activation method further comprises: receiving a plug-in access request of an opening end for realizing the intercommunication protocol, wherein the plug-in access request comprises starting information of a plug-in to be accessed; and setting the corresponding relation between the plug-in to be accessed and the function entrance when the start information test of the plug-in to be accessed passes.

The platform server can develop a set of flow systems corresponding to the application flow and the approval flow aiming at the plug-in access. The application flow of the development end for applying for the access plug-in may be, for example: the development terminal can firstly acquire an intercommunication protocol corresponding to the function of realizing the target service from the flow system; secondly, after the intercommunication protocol of the function entry is realized, plug-in development can be performed based on the intercommunication protocol; after the plug-in is developed, an APP test environment installation package can be obtained from the flow system, whether a corresponding function entry triggering the APP can start the developed plug-in is tested, and a corresponding function detail page is opened; and finally, when the test passes, a plug-in access request is sent to the server to apply for accessing the plug-in which is developed and becomes an implementer of the service function corresponding to the intercommunication protocol.

The approval process of the server to approve the access plug-in may be, for example: the method comprises the steps that a server firstly analyzes starting information of a plug-in to be accessed in a plug-in access request, such as starting information of a plug-in home page; secondly, testing whether a corresponding function entry of the APP is triggered, starting the developed plugin based on starting information and protocol information of the plugin to be accessed, and opening a corresponding function detail page; and finally, when the test passes, the operation system approves passing after the test passes, and the plug-in to be accessed is set to correspond to the function entrance, so that the plug-in to be accessed becomes an implementer of the service function corresponding to the intercommunication protocol. After the approval is passed, the plug-in identification of the access plug-in can be newly added in the plug-in identification corresponding to the corresponding function entrance in the setting interface of the client so as to enable the user to perform default starting plug-in setting.

By deploying the intercommunication protocol for the function entrance, the development end can conveniently develop the plug-in based on the intercommunication protocol, and then the update of the plug-in corresponding to the intercommunication protocol can be realized through the application flow and the approval flow of plug-in access. Therefore, the platform service end does not need to develop and support for the display of a single plug-in on the client interface, and only needs to prepare for the development end side, thereby greatly facilitating the maintenance operation of the service end on the plug-in corresponding to the intercommunication protocol.

Fig. 6 is a schematic diagram of an architecture supporting plug-in startup in a plug-in startup method according to a fifth embodiment of the present invention. Referring to fig. 6, after the development end applies for the plug-in access to the service end, the service end may maintain the related information of the plug-in to be accessed to the plug-in list when the plug-in to be accessed passes the audit.

The process of starting the plug-in of the development end by the client can be divided into two accesses to the service end, the client accesses to the service end for the first time, and the aim is to acquire plug-in implementer information, namely plug-in information, by calling addressing service of the service end; the client accesses the server for the second time, and aims to open a specific plug-in detail page of the development end, namely, a plug-in is started.

Wherein the first interaction process may involve the following modules in fig. 6:

the client can send the trigger instruction of the function entrance to the intercommunication center of the server through the Router center and the intercommunication component.

The interworking center of the server can firstly call a protocol analysis interface according to the triggering instruction to judge whether the triggered function entrance is provided with an interworking protocol or not; and then calling a protocol addressing interface, determining a plug-in list from a plug-in center, acquiring a plug-in identifier of a default starting plug-in corresponding to the function entry from a data storage module (a distributed cache server or a MySQL database), taking the plug-in identifier of the default starting plug-in as plug-in information when the plug-in identifier of the default starting plug-in is contained in the plug-in list, taking the plug-in list as plug-in information when the plug-in identifier of the default starting plug-in is not contained in the plug-in list, and feeding back the plug-in information and protocol information of an intercommunication protocol deployed by the function entry to a client.

The second interaction process may involve the following modules in fig. 6:

and the client can access the plug-in starting service of the server again according to the plug-in information and the protocol information.

The server can analyze the call parameters in the call request to obtain the plug-in identification, the protocol identification and the protocol parameters; obtaining plug-in starting information corresponding to the plug-in identifier through a plug-in starting interface in the plug-in center, and splicing the protocol identifier, the protocol parameter and the plug-in starting information; and sending the splicing result to a development end through the intercommunication component and the Router center.

When receiving the spliced plug-in starting information, the development terminal can analyze the protocol identification and the protocol parameters based on the realized intercommunication protocol and carry out corresponding jump. The jump page can be respectively called back to the Router from the development end through the Router center, and the Router realization is sent to the client so as to realize the function detail page of the plug-in presented by the client.

In addition, the server may further include a user setting interface, for setting a default startup plug-in of the function entry for the client, and the default startup plug-in may be stored in the data storage module; the server may further include a log collection interface for recording asynchronous interworking addressing logs; the server side can also establish communication connection with the big data analysis platform so that the log analysis interface in the data analysis platform can realize big data analysis based on the intercommunication addressing log. The server may also include other interfaces, which are not exhaustive herein.

According to the embodiment of the invention, on the basis of the embodiment, the step that the development end applies for the plug-in to the service end is optimized, and compared with the technical support that the service end needs to display each plug-in on the APP first screen or the second interface in the traditional technical scheme, in the scheme provided by the embodiment of the invention, the service end can maintain the corresponding plug-in of the function entrance only by the development end according to the intercommunication protocol and executing the flow of applying for the plug-in, so that the maintenance difficulty of the plug-in can be reduced. And the architecture supporting plug-in starting is also described, and modules involved in the flow of the plug-in of the client starting end are supplemented. In addition, the present embodiment and the plug-in starting method proposed in the foregoing embodiment belong to the same inventive concept, and technical details not described in detail in the present embodiment can be seen in the foregoing embodiment.

Example six

Based on the embodiment, the embodiment explains the information such as the intercommunication protocol corresponding to the maintenance function entry of the server and the plug-in for realizing each intercommunication protocol, and the adopted table structure, thereby being beneficial to the unified configuration information of the server.

In order to facilitate maintenance of the interworking protocol corresponding to the function entry and implementation of the information such as the plug-in of each interworking protocol, the server may use a table structure to perform unified configuration of the information. The configured data may be flushed to a distributed cache server so that the addressing service retrieves the data directly from the cache. The design of the table structure needs to consider the association relationship among the intercommunication protocol, the parameters of the intercommunication protocol, the implementer of the intercommunication protocol and the detailed information of the plug-in unit, and the expansibility of the table structure needs to be ensured.

Exemplary, the table structure provided by the embodiment of the invention can be as follows:

In some alternative embodiments, the three-layer table structure may be used to configure related information of the interworking protocol, the first layer table structure may be an interworking protocol category table structure, the second layer table structure may be an interworking protocol table structure, and the third layer table structure may be an interworking protocol parameter table structure.

The interworking protocol category table may be considered as a category table formed by grouping interworking protocols corresponding to each function entry according to function types and identifying various protocol categories. Exemplary, table 1 shows a table of interworking protocol categories provided in a fifth embodiment of the present invention.

Referring to table 1, the interworking protocol category table may include, but is not limited to, data of a self-increment id field "id", a category identification field "category_id", a category name field "category_name", a release environment field "release_status" and a status field "status". Wherein, the "id" field can be regarded as a "serial number" field, and each function type (i.e. category) is added in the field, a serial number can be automatically added; the category_id field and the category_name field can both uniquely represent categories, and the category identification is beneficial to computer reading and writing, and the category name can improve user readability, for example, the category identification can be English abbreviation "Ord", and the corresponding category name can be "order category"; wherein, the "Release_status" field may characterize whether the category is actually published, and the "status" field may characterize whether the category is in a valid state.

TABLE 1

The interworking protocol table may be considered as a next layer table of various category identifiers in the interworking protocol category table, and may be considered as a table structure formed by at least one interworking protocol identifier associated with various target identifiers. Exemplary, table 2 shows an interworking protocol table provided in a fifth embodiment of the present invention.

Referring to table 2, the interworking protocol table may include, but is not limited to, data of a self-increment id field "id", a protocol identification field "api_code", a protocol name field "api_name", a category identification field "category_id" and a status field "status". Wherein, the "id" field can be regarded as a "serial number" field, and each new intercommunication protocol is added in the field, a serial number can be automatically added; the 'api_code' field and the 'api_name' field can uniquely represent the intercommunication protocol, and the protocol identification is beneficial to the reading and writing of a computer, and the protocol name can improve the user readability; wherein, the category_id can be the category identification in the intercommunication protocol category table, and can be associated with the intercommunication protocol category table through the category_id field; wherein the status field may characterize whether the interworking protocol is in a valid state.

TABLE 2

The interworking protocol parameter table may be considered as a next layer table of each protocol identifier in the interworking protocol table, and may be considered as a table structure formed by parameters of at least one interworking protocol associated with each protocol identifier. Exemplary, table 3 shows an interworking protocol parameter table provided in the fifth embodiment of the present invention.

Referring to table 3, the interworking protocol parameter table may include, but is not limited to, data of a self-increment id field "id", a protocol identification field "api_code", a parameter name field "parameter_name", a parameter description field "parameter_desc", whether an identification field "must_flag", an example field "example", a parameter type field "parameter_type", and a status field "status". The "id" field may be considered as a "sequence number" field, in which a sequence number may be automatically added when a parameter of an interworking protocol is newly added; the 'api_code' field can be a protocol identifier in the intercommunication protocol table, and can be associated with the intercommunication protocol table through the 'api_code' field; wherein, the "param_name" field characterizes the parameter name, the "param_desc" field stores the parameter description, and the "param_type" field characterizes the parameter type; wherein, the "must_flag" field characterizes whether the parameter is necessary to be filled, and the "sample" field gives a specific example of the parameter; wherein the status field may characterize whether the parameter is in a valid state.

TABLE 3 Table 3

Illustratively, the "category_id" field in the interworking protocol category table may include data "Ord", which characterizes the category identification of the order function type in the interworking protocol category table, and may also include the category identification of other function types, which is not intended to be exhaustive herein.

Accordingly, there may be an interworking protocol table with the "category_id" field as data "Ord", i.e., the interworking protocol table is associated with the order function type in the interworking category table. In addition, the "api_code" field in the interworking protocol table may include "ord_list" (i.e. a protocol identifier corresponding to a service function for opening an order list), may also include "ord_detail" (i.e. a protocol identifier corresponding to a service function for opening order details), and may also include a protocol identifier corresponding to another service function under an order type, which is not exhaustive herein.

Accordingly, there may be an interworking protocol parameter table with an "api_code" field being the data "ord_list", i.e. the interworking protocol parameter table contains specific parameter information in the interworking protocol "ord_ lis".

In these embodiments, the server side can manage the relevant information of the interworking protocol conveniently by configuring the relevant information of the interworking protocol using a three-layer table structure. In addition, since the plug-in developed by the developer is usually a plug-in of a certain service function, for example, company a mainly relates to the plug-in development of the financial field, company B mainly relates to the plug-in development of the take-away field, and the developer can search the intercommunication protocols of the same type of function type by grouping the intercommunication protocols according to the function types, without searching the intercommunication protocols individually, thereby being beneficial to realizing a plurality of intercommunication protocols at one time and improving the development efficiency of the plug-in to a certain extent.

In some embodiments, the related information of the plugin is configured by using a two-layer table structure, where the first layer table structure may be an interworking protocol implementer table structure and the second layer table structure may be a plugin parameter table structure.

The interworking protocol implementer table may be considered as a table structure formed by plug-in identifiers capable of implementing all protocols under a certain interworking protocol class or capable of implementing the interworking protocol corresponding to a certain function entry. Exemplary, table 4 shows an interworking protocol implementer table provided by the fifth embodiment of the present invention.

Referring to table 4, the interworking protocol implementer table may include, but is not limited to, data of a self-increment id field "id", a category identification "category_id" field, or a protocol identification field "api_code", a plug-in identification field "plug_id", and a status field "status". Wherein, the "id" field can be regarded as a "serial number" field, and a serial number can be automatically added by each implementer newly adding an intercommunication protocol in the field; wherein, the category_id can be the category identification in the intercommunication protocol category table, and can be associated with the intercommunication protocol category table through the category_id field; the 'api_code' field can be a protocol identifier in the intercommunication protocol table, and can be associated with the intercommunication protocol table through the 'api_code' field; the plugin_id is a plugin identifier and can be used as plugin information fed back by a server; wherein the status field may characterize whether the plug-in is in a valid state.

TABLE 4 Table 4

The general transmitting end can realize all intercommunication protocols under one category, and develop a plug-in unit capable of completing each service function under the category, and at the moment, the plug-in unit implementer list can be associated with the intercommunication protocol category list. In addition, when implementing some unusual service functions, the development end usually needs to develop an interworking protocol for a certain function entry, where a plug-in implementer table may be associated with the interworking protocol table.

The plug-in parameter person table may be considered as a next layer table of each plug-in identifier in the interworking protocol implementer table, and may be considered as a table structure formed by parameters of at least one plug-in associated with each plug-in identifier. Illustratively, table 5 shows a plug-in parameter table provided in the fifth embodiment of the present invention.

Referring to table 5, the plug-in parameter table may include, but is not limited to, data of a self-increment id field "id", a plug-in identification field "plug in_id", a plug-in name field "plug in_name", a plug-in type field "plug in_type", a plug-in start information field "plug in_start up" and a status field "status". Wherein, the "id" field can be regarded as a "serial number" field, and each time a plug-in parameter is added in the field, a serial number can be automatically added; the 'plugin_id' can be a plug-in identifier in the interworking protocol realization table, can be associated with the interworking protocol realization table through a 'plugin_id' field, and can be used as plug-in information to be fed back to the client; the plug-in name field 'plugin_name' and the plug-in type field 'plugin_type' can also be fed back to the client side simultaneously when the server side feeds back plug-in information, so that a user of the client side can know the specific name and type of the plug-in; wherein "plug_start" may be start information of the plug-in, including, for example, URL or applet key; wherein the status field may characterize whether the plug-in is in a valid state.

TABLE 5

Through the design of the table structure, the service end is convenient for maintaining the intercommunication protocol, the plug-in units for realizing the intercommunication protocol and other information, and the expansion is convenient. It should be noted that the table structure designed by the server for maintaining the above information is not limited to the above structure, and other table structures may be applied thereto, which is not exhaustive herein.

Based on the embodiment of the invention, the table structure adopted by the embodiment of the invention is described for the intercommunication protocol corresponding to the server as the maintenance function entry and the information such as plug-in and the like for realizing each intercommunication protocol, thereby being beneficial to the unified configuration information of the server. In addition, the present embodiment and the plug-in starting method proposed in the foregoing embodiment belong to the same inventive concept, and technical details not described in detail in the present embodiment can be seen in the foregoing embodiment.

Example seven

Fig. 7 shows a schematic structural diagram of a plug-in starting device according to a seventh embodiment of the present invention, where the embodiment of the present invention is applicable to a case where a plug-in is started, for example, a case where a corresponding plug-in is started by triggering a function entry of a home page of an application program of a platform class. The plug-in starting device provided by the invention can realize the plug-in starting method applied to the client.

As shown in fig. 7, in an embodiment of the present invention, a plug-in starting apparatus is applied to a client, and includes:

the entry triggering module 710 is configured to send a triggering instruction of the function entry to the server, so that the server determines whether the function entry is configured with an interworking protocol, and if so, queries plug-in information according to the interworking protocol; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

The plug-in starting module 720 is configured to receive plug-in information and protocol information of the interworking protocol fed back by the server, and perform plug-in starting according to the plug-in information and the protocol information of the interworking protocol deployed by the function portal.

In some alternative embodiments, the plug-in information is a plug-in identification or a plug-in list; the plug-in identification is the plug-in identification of the default starting plug-in corresponding to the function entry acquired by the server; the plug-in list is determined according to the plug-ins downloaded by the client and corresponding to the intercommunication protocol by the server;

correspondingly, when the plug-in information is a plug-in identifier, the plug-in starting module is specifically used for starting the plug-in according to the plug-in identifier and protocol information of an intercommunication protocol deployed by the function entry;

correspondingly, when the plug-in information is a plug-in list, the plug-in starting module is specifically configured to respond to a selection operation of the plug-in identifier in the plug-in list, and perform plug-in starting according to the selected plug-in identifier and protocol information of the interworking protocol deployed by the function portal.

In some further embodiments, the plug-in module is specifically configured to:

And taking the protocol identifier and the protocol parameter of the intercommunication protocol deployed by the plug-in identifier and the function entry as calling parameters, calling a plug-in starting interface of the server side so that the server side obtains plug-in starting information corresponding to the plug-in identifier through the plug-in starting interface, splicing the protocol identifier and the protocol parameter with the plug-in starting information, and starting the plug-in according to a splicing result.

In some optional embodiments, the portal triggering module is further configured to send a triggering instruction of the function portal to the server, so that the server determines whether the function portal is deployed with an interworking protocol, and if not, queries the plug-in starting information;

Correspondingly, the plug-in starting module is also used for receiving plug-in starting information fed back by the server side and starting the plug-in according to the plug-in starting information.

In some alternative embodiments, the card activation device further comprises:

the default starting plug-in setting module is used for responding to the plug-in setting operation of the function entry and calling a setting interface of the server so that the server can set the default starting plug-in for the function entry through the setting interface.

The plug-in starting device provided by the embodiment of the invention belongs to the same conception as that of the plug-in starting method applied to the client provided by the embodiment, technical details which are not described in detail in the embodiment of the invention can be seen from the embodiment, and the embodiment of the invention has the same beneficial effects as the embodiment.

Example eight

Fig. 8 shows a schematic structural diagram of a plug-in starting device according to an eighth embodiment of the present invention, where the embodiment of the present invention is applicable to a case where a plug-in is started, for example, a background server feeds back plug-in information according to a trigger instruction of a function entry of a first page of a client, so that the client starts a corresponding plug-in according to the plug-in information. The plug-in starting device provided by the invention can realize the plug-in starting method applied to the server.

As shown in fig. 8, in an embodiment of the present invention, a plug-in starting device is applied to a server, and includes:

the plug-in information determining module 810 is configured to determine whether an interworking protocol is deployed in the function entry in response to a trigger instruction of the function entry sent by the client, and if so, query plug-in information according to the interworking protocol; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

And the information feedback module 820 is used for feeding back the plug-in information and the protocol information of the intercommunication protocol to the client so that the client can start the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entry.

In some alternative embodiments, the plug-in information determining module includes:

The deployment judging sub-module is used for judging whether the function entry is deployed with an intercommunication protocol by calling a protocol analysis interface;

the plug-in list determining submodule is used for calling the protocol addressing interface if yes, so as to determine a plug-in list according to plug-ins downloaded by the client and plug-ins corresponding to the intercommunication protocol;

the plug-in identification acquisition sub-module is used for acquiring the plug-in identification of the default starting plug-in corresponding to the function entry and judging whether the plug-in identification of the default starting plug-in is contained in the plug-in list;

the plug-in information determining submodule is used for taking the plug-in identifier of the default starting plug-in as plug-in information if the plug-in identifier is contained in the plug-in list; and if the plug-in identification is not contained in the plug-in list, taking the plug-in list as plug-in information.

In some alternative embodiments, the card activation device further comprises:

And the log collection module is used for asynchronously sending the log generated by calling the protocol addressing interface to a preset message queue after calling the protocol addressing interface so as to carry out statistic analysis of preset dimensionality according to the log in the preset message queue.

In some optional embodiments, feeding back protocol information of the interworking protocol to the client includes: the protocol identification and the protocol parameters of the intercommunication protocol deployed by the function entrance are fed back to the client;

correspondingly, the plug-in starting device further comprises:

The assistant starting module is used for receiving a plug-in starting interface calling request of the client and analyzing calling parameters of the calling request to obtain a plug-in identifier, a protocol identifier and a protocol parameter; and acquiring plug-in starting information corresponding to the plug-in identification through a plug-in starting interface, splicing the protocol identification, the protocol parameter and the plug-in starting information, and starting the plug-in according to the splicing result.

In some optional embodiments, the plug-in information determining module is further configured to query plug-in startup information if the function portal is not deployed with an interworking protocol;

correspondingly, the plug-in information feedback module is further used for feeding back plug-in starting information to the client so that the client can start the plug-in according to the plug-in starting information.

In some alternative embodiments, the card activation device further comprises:

And the assistance setting module is used for receiving a call request of a setting interface of the client and setting a default starting plug-in for the function entry through the setting interface.

In some alternative embodiments, the card activation device further comprises:

the access plug-in module is used for receiving a plug-in access request of an opening end for realizing the intercommunication protocol, and the plug-in access request contains starting information of a plug-in to be accessed; and setting the corresponding relation between the plug-in to be accessed and the function entrance when the start information test of the plug-in to be accessed passes.

The plug-in starting device provided by the embodiment of the invention belongs to the same conception as the plug-in starting method provided by the embodiment and applied to the server, technical details which are not described in detail in the embodiment of the invention can be seen in the embodiment, and the embodiment of the invention has the same beneficial effects as the embodiment.

Example nine

Fig. 9 shows a schematic hardware structure of a terminal device according to a ninth embodiment of the present invention. The terminal device in the embodiment of the present invention may include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), car terminals (e.g., car navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. The terminal device shown in fig. 9 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present invention.

As shown in fig. 9, the terminal apparatus 900 may include a processing device (e.g., a central processor, a graphics processor, etc.) 901, which may perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 902 or a program loaded from a storage device 908 into a random access Memory (Random Access Memory, RAM) 903. In the RAM903, various programs and data necessary for the operation of the terminal device 900 are also stored. The processing device 901, the ROM 902, and the RAM903 are connected to each other through a bus 904. An input/output (I/O) interface 905 is also connected to the bus 904.

In general, the following devices may be connected to the I/O interface 905: input devices 906 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, and the like; an output device 907 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 908 including, for example, magnetic tape, hard disk, etc.; and a communication device 909. The communication means 909 may allow the terminal device 900 to communicate with other devices wirelessly or by wire to exchange data. While fig. 9 shows a terminal device 900 having various means, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.

In particular, according to embodiments of the present invention, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via the communication device 909, or installed from the storage device 908, or installed from the ROM 902. When the computer program is executed by the processing apparatus 901, the above-described functions defined in the plug-in startup method applied to the client or applied to the server provided by the embodiment of the present invention are executed.

The terminal provided by the embodiment of the present invention and the plug-in starting method provided by the above embodiment belong to the same inventive concept, technical details which are not described in detail in the embodiment of the present invention can be seen in the above embodiment, and the embodiment of the present invention has the same beneficial effects as the above embodiment.

Examples ten

The embodiment of the invention provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the plug-in starting method applied to a client or a server provided in the above embodiment.

It should be noted that, the computer readable storage medium according to the embodiment of the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access Memory (Random Access Memory, RAM), a Read-Only Memory (ROM), an erasable programmable Read-Only Memory (EPROM) or FLASH Memory (FLASH), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In embodiments of the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in embodiments of the present invention, the computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.

In some embodiments, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The computer-readable storage medium may be included in the terminal device or may exist alone without being incorporated in the terminal device.

The terminal device stores one or more programs that, when executed by the terminal device, cause the terminal device to:

Sending a triggering instruction of the function entry to a server side so that the server side judges whether the function entry is provided with an intercommunication protocol or not, and if so, inquiring plug-in information according to the intercommunication protocol; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

Receiving plug-in information and protocol information of an intercommunication protocol fed back by a server side, and starting the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by a function entry;

Or when the one or more programs are executed by the terminal device, cause the terminal device to:

And feeding back the plug-in information and the protocol information of the intercommunication protocol to the client so that the client starts the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entrance.

Computer program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functional pages noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units involved in the embodiments of the present invention may be implemented in software or in hardware. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.

The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary versions of hardware logic that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.

Claims

1. The plug-in starting method is characterized by being applied to a client and comprising the following steps of:

Sending a triggering instruction of a function entry to a server side so that the server side judges whether an intercommunication protocol is deployed in the function entry, if so, inquiring plug-in information according to the intercommunication protocol, and if not, inquiring plug-in starting information; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

receiving plug-in information and protocol information of the intercommunication protocol fed back by the server, and starting the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entry;

And receiving the plug-in starting information fed back by the server, and starting the plug-in according to the plug-in starting information.

2. The method according to claim 1, wherein the plug-in information is a plug-in identification or a plug-in list; the plug-in identification is a plug-in identification of a default starting plug-in corresponding to the function entry acquired by the server; the plug-in list is determined by the server according to the plug-ins downloaded by the client and corresponding to the intercommunication protocol;

Correspondingly, when the plug-in information is a plug-in identifier, the plug-in starting is performed according to the plug-in information and the protocol information of the interworking protocol deployed by the function entry, including:

Starting the plug-in according to the plug-in identification and the protocol information of the intercommunication protocol deployed by the function entry;

correspondingly, when the plug-in information is a plug-in list, the plug-in starting is performed according to the plug-in information and the protocol information of the interworking protocol deployed by the function entry, including:

And responding to the selection operation of the plug-in identification in the plug-in list, and starting the plug-in according to the selected plug-in identification and the protocol information of the intercommunication protocol deployed by the function entry.

3. The method according to claim 2, wherein performing plug-in startup according to a plug-in identification and protocol information of an interworking protocol deployed by the function portal comprises:

And calling a plug-in starting interface of the server by taking a plug-in identifier and a protocol parameter of an intercommunication protocol deployed by the function entrance as calling parameters, so that the server obtains plug-in starting information corresponding to the plug-in identifier through the plug-in starting interface, splices the protocol identifier and the protocol parameter with the plug-in starting information, and starts the plug-in according to a splicing result.

4. The method as recited in claim 1, further comprising:

And calling a setting interface of the server in response to the plug-in setting operation of the function entry, so that the server sets a default starting plug-in for the function entry through the setting interface.

5. The plug-in starting method is characterized by being applied to a server and comprising the following steps:

responding to a triggering instruction of a function entry sent by a client, judging whether the function entry is provided with an intercommunication protocol, and inquiring plug-in information according to the intercommunication protocol if the function entry is provided with the intercommunication protocol; if the function entry is not deployed with the intercommunication protocol, inquiring plug-in starting information; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

The plug-in information and the protocol information of the intercommunication protocol are fed back to the client so that the client starts the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entry;

And feeding back the plug-in starting information to the client so that the client starts the plug-in according to the plug-in starting information.

6. The method according to claim 5, wherein the determining whether the function portal deploys an interworking protocol, and if so, querying plug-in information according to the interworking protocol, comprises:

Judging whether the function entry is provided with an intercommunication protocol or not by calling a protocol analysis interface;

If yes, calling a protocol addressing interface to determine a plug-in list according to the plug-in downloaded by the client and the plug-in corresponding to the intercommunication protocol;

Obtaining a plug-in identifier of a default starting plug-in corresponding to the function entry, and judging whether the plug-in identifier of the default starting plug-in is contained in the plug-in list;

If yes, taking the plug-in identification of the default starting plug-in as plug-in information;

And if not, taking the plug-in list as plug-in information.

7. The method of claim 6, further comprising, after said invoking the protocol addressing interface:

And asynchronously sending the log generated by calling the protocol addressing interface to a preset message queue, so as to perform statistical analysis of preset dimensionality according to the log in the preset message queue.

8. The method according to claim 5, wherein feeding back the protocol information of the interworking protocol to the client comprises:

the protocol identification and the protocol parameters of the intercommunication protocol deployed by the function entrance are fed back to the client;

correspondingly, the plug-in starting method further comprises the following steps:

receiving a plug-in starting interface call request of the client, and analyzing call parameters of the call request to obtain a plug-in identifier, the protocol identifier and the protocol parameters;

And acquiring plug-in starting information corresponding to the plug-in identifier through the plug-in starting interface, splicing the protocol identifier and the protocol parameter with the plug-in starting information, and starting the plug-in according to a splicing result.

9. The method as recited in claim 5, further comprising:

and receiving a call request of a setting interface of the client, and setting a default starting plug-in for the function entry through the setting interface.

10. The method as recited in claim 5, further comprising:

Receiving a plug-in access request of an opening end for realizing the intercommunication protocol, wherein the plug-in access request comprises starting information of a plug-in to be accessed;

and setting the corresponding relation between the plug-in to be accessed and the function entrance when the starting information test of the plug-in to be accessed passes.

11. A plug-in launch device, for application to a client, comprising:

The access triggering module is used for sending a triggering instruction of the function access to the server side so that the server side can judge whether the function access is provided with an intercommunication protocol or not, if yes, the information of the plug-in is inquired according to the intercommunication protocol, and if not, the starting information of the plug-in is inquired; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

The plug-in starting module is used for receiving plug-in information fed back by the server side and protocol information of the intercommunication protocol, and starting the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entrance; and receiving the plug-in starting information fed back by the server, and starting the plug-in according to the plug-in starting information.

12. A plug-in starting device, which is applied to a server, and comprises:

The plug-in information determining module is used for responding to a triggering instruction of a function entry sent by the client and judging whether the function entry is provided with an intercommunication protocol, if so, the plug-in information is queried according to the intercommunication protocol; if the function entry is not deployed with the intercommunication protocol, inquiring plug-in starting information; the function inlet with the deployed intercommunication protocol corresponds to at least two plug-ins;

The information feedback module is used for feeding back the plug-in information and the protocol information of the intercommunication protocol to the client so that the client starts the plug-in according to the plug-in information and the protocol information of the intercommunication protocol deployed by the function entrance; and feeding back the plug-in starting information to the client so that the client starts the plug-in according to the plug-in starting information.

13. A terminal device, characterized in that the terminal comprises:

one or more processors;

A memory for storing one or more programs;

The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the plug-in launch method of any one of claims 1-4 or 5-10.

14. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the plug-in activation method according to any one of claims 1-4 or 5-10.