A capability opening method, apparatus and device

Abstract

The application provides a capability opening method, device and equipment, the method comprises the following steps: a capability server constructs a plurality of capability applications, the plurality of capability applications have independent technology stacks from each other; the capability server routes a target capability application in the plurality of capability applications to a capability client, and the capability client applies the target capability application.In this way, the capability server constructs a plurality of capability applications with independent technology stacks from each other, and the capability server uniformly manages and maintains the plurality of capability applications, a capability user can directly obtain and apply the target capability application through the capability client after authentication, the target capability can be a capability application determined by the capability user in the plurality of capability applications according to requirements, so that the threshold for accessing the capability opening platform is reduced; when the capability server manages and maintains the target capability application, the influence on other capability applications is reduced, so that the convenience of the capability opening platform is improved.

Description

Technical Field

[0001] This invention relates to the field of micro-frontend architecture technology, and in particular to a capability opening method, apparatus and device. Background Technology

[0002] Currently, the capability open platform mainly provides services through application programming interfaces (APIs), and users need to develop functions based on the open APIs according to their own business needs.

[0003] However, opening up traditional API functions requires users to invest a high cost in access, and subsequent business changes and interface updates will also bring high maintenance costs to users, which is not conducive to the promotion and maintenance of the capability open platform.

[0004] It is evident that existing capability open platforms suffer from poor convenience. Summary of the Invention

[0005] This invention provides a capability opening method, apparatus, and device to address the problem of poor convenience in existing capability opening platforms.

[0006] In a first aspect, embodiments of the present invention provide a capability opening method, the method comprising:

[0007] The capability server builds multiple capability applications, and these multiple capability applications have independent technology stacks.

[0008] The capability server receives a first request from the capability client to apply the target capability;

[0009] After the capability server authenticates the first request, it routes the target capability application to the capability client. The target capability application is obtained by the capability server from the plurality of capability applications based on the first request.

[0010] Secondly, embodiments of the present invention provide a capability opening method, the method comprising:

[0011] The capability client sends a first request to the capability server for the target capability application;

[0012] The capability client receives the target capability application sent by the capability server after the first request has been authenticated. The target capability application is obtained by the capability server from multiple capability applications built by the capability server based on the first request.

[0013] The target capability is applied by the client application.

[0014] Thirdly, embodiments of the present invention provide a capability open platform, the platform comprising:

[0015] A building module is used by the capability server to build multiple capability applications, which have independent technology stacks.

[0016] The sending module is used for the capability server to receive a first request for the application of a target capability sent by the capability client;

[0017] The routing module is used to route the target capability application to the capability client after the capability server authenticates the first request. The target capability application is obtained by the capability server from the plurality of capability applications based on the first request.

[0018] Fourthly, embodiments of the present invention provide a capability open platform, the platform comprising:

[0019] The first sending module is used for the capability client to send a first request for the target capability application to the capability server;

[0020] The receiving module is used for the capability client to receive the target capability application sent by the capability server after the capability server has authenticated the first request, wherein the target capability application is obtained by the capability server from multiple capability applications constructed by the capability server based on the first request;

[0021] The application module is used by the capability client to apply the target capability.

[0022] Fifthly, embodiments of the present invention provide an electronic device, comprising:

[0023] At least one processor; and

[0024] A memory communicatively connected to the at least one processor; wherein,

[0025] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the capability opening method as described in the first aspect.

[0026] Sixthly, embodiments of the present invention provide an electronic device, comprising:

[0027] At least one processor; and

[0028] A memory communicatively connected to the at least one processor; wherein,

[0029] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the capability opening method as described in the second aspect.

[0030] In a seventh aspect, embodiments of the present invention provide a non-transitory computer-readable storage medium storing computer instructions, the computer instructions being configured to cause the computer to perform the capability opening method as described in the first aspect, or the computer instructions being configured to cause the computer to perform the capability opening method as described in the second aspect.

[0031] In this embodiment of the invention, the capability server constructs multiple capability applications with independent technology stacks, and the capability server uniformly manages and maintains these multiple capability applications. After authentication, capability users can directly obtain and apply the target capability application through a capability client. The target capability can be a capability application determined by the capability user from among the multiple capability applications according to actual needs, thus lowering the threshold for accessing the capability open platform. When the capability server manages and maintains the target capability application, it reduces the impact on other capability applications, thereby improving the convenience of the capability open platform. Attached Figure Description

[0032] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 This is a flowchart illustrating a capability opening method provided in an embodiment of the present invention;

[0034] Figure 2 This is an architecture diagram of the capability open platform system provided in the embodiments of the present invention;

[0035] Figure 3 This is a schematic diagram of the structure of the management system provided in an embodiment of the present invention;

[0036] Figure 4 This is a flowchart illustrating the capability application management process provided in an embodiment of the present invention;

[0037] Figure 5 This is a flowchart illustrating another capability opening method provided in an embodiment of the present invention;

[0038] Figure 6 This is a schematic diagram of the structure of a capability open platform provided in an embodiment of the present invention;

[0039] Figure 7 This is a schematic diagram of another capability open platform provided in an embodiment of the present invention;

[0040] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention;

[0041] Figure 9 This is a schematic diagram of the structure of another electronic device provided in an embodiment of the present invention. Detailed Implementation

[0042] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0043] In the embodiments of this invention, the terms "first," "second," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or devices.

[0044] See Figure 1 , Figure 1 This is a flowchart illustrating a capability opening method provided in an embodiment of the present invention, as shown below. Figure 1 As shown, the method includes the following steps:

[0045] Step 101: The capability server constructs multiple capability applications, each with its own independent technology stack.

[0046] In this embodiment of the invention, the physical entity corresponding to the capability server can be a micro-frontend architecture server with frontend capability module decomposition. The micro-frontend architecture includes a parent application and child applications. The functions provided by the parent application of the micro-frontend architecture can include: access identity verification, usage permission verification, and route distribution. The child applications of the micro-frontend architecture can be the multiple capability applications built by the capability server. The capability server can provide the same or different capability services to the multiple capability applications through a capability service layer. The capability server also has an interface construction layer and a database layer to provide data support for the capability server.

[0047] Because of the advantage that the micro-frontend architecture does not impose mandatory requirements on the technology selection of the multiple capability applications, the constructed multiple capability applications can have independent technology stacks, which decouples the various capability applications and reduces the impact on other capability applications during independent iteration and modification.

[0048] Step 102: The capability server receives a first request from the capability client to apply the target capability;

[0049] In this step, the physical entity corresponding to the capability client can be the browser of the capability user, and the capability server can be the capability provider. The user initiates access to the capability server through the capability client, and the capability server receives the first request for the target capability application sent by the user through the capability client.

[0050] Step 103: After the capability server authenticates the first request, it routes the target capability application to the capability client. The target capability application is obtained by the capability server from the plurality of capability applications based on the first request.

[0051] The capability server authenticates the first request. If the first request is successfully authenticated, the target capability application is routed to the capability client through the micro-frontend architecture parent application. The target capability application may be a sub-application corresponding to the micro-frontend architecture parent application. The target capability application may be uniformly maintained and managed by the capability provider. The capability user uses the target capability application through the capability client.

[0052] In this embodiment of the invention, the capability server constructs multiple capability applications with independent technology stacks, and the capability server uniformly manages and maintains these multiple capability applications. After authentication, capability users can directly obtain and apply the target capability application through a capability client. The target capability can be a capability application determined by the capability user from among the multiple capability applications according to actual needs, thus lowering the threshold for accessing the capability open platform. When the capability server manages and maintains the target capability application, it reduces the impact on other capability applications, thereby improving the convenience of the capability open platform.

[0053] In step 103, the capability server can identify whether a user requesting access to the target capability has the necessary permissions through the customer permission management module; manage the identity information and additional user information of registered users on the capability open platform through the customer access management module; and manage the version, release, and decommissioning functions of the multiple capability applications through the capability application management module. Each capability application is managed as an independent application in the application management center. The micro-frontend architecture parent application, i.e., the capability application access base, provides user access authentication capabilities, serves as the communication bus of the capability server, and handles routing and distribution of sub-applications. Each capability sub-application in the multiple capability applications is provided with independent capability services by the capability service layer of the capability server. Therefore, each capability application in the multiple capability applications has the characteristics of independent development, independent deployment, and independent authorization to users, reducing the high R&D capabilities and workload requirements for capability users in traditional API opening methods. Capability users obtain a complete target capability application that can be used directly.

[0054] After the capability server authenticates the first request, it routes the target capability application to the capability client, which may include the following steps:

[0055] The capability server authenticates the first signature information in the first request;

[0056] When the first signature information is authenticated by the capability server, the capability server parses the first signature information and reads the target capability application information and user information.

[0057] The capability server obtains the target capability application from the plurality of capability applications based on the target capability application information;

[0058] The capability server routes the target capability application to the capability client and adds an identification tag to the target capability application. The identification tag is used to decouple the target capability application from the capability client after the capability client is embedded in the target capability application.

[0059] In this embodiment, such as Figure 2 As shown, Figure 2This is an architecture diagram of the capability open platform system provided in this embodiment of the invention. After a user requests access, the capability server can intercept the first signature information from the unified resource locator (URL) through the micro-frontend architecture parent application. The client permission management module identifies whether the user requesting access to the target capability has the right to use it. When the first signature information of the accessing user is authenticated, the capability server decrypts the first signature information using the user encryption key in the database layer, reads the user information and the target capability application information, and feeds it back to the micro-frontend parent application. The parent application routes to the corresponding capability sub-application according to the received target capability application information and adds a unique identification mark (identification ID) to the root element of the capability sub-application. The identification mark is used to decouple the capability client after the target capability application embeds the capability client.

[0060] Once inside the capability application, that is, after the target capability application is integrated into the capability client, the capability client reads the user information from the shared temporary cache and requests the current user's custom UI configuration for the target capability application from the capability server;

[0061] The capability server generates a user interface (UI) configuration based on the user information. The UI configuration is used by the user to customize the interface of the target capability application in the capability client.

[0062] It should be noted that the capability client can add a unique identification mark to the root element of the target capability application as a restriction condition, and add the user-defined UI configuration to the HyperText Markup Language (HTML) document of the current window to complete the rendering of the custom style.

[0063] Optionally, the capability server constructs multiple capability applications, including:

[0064] The capability server receives a second request from the capability client to edit the multiple capability applications;

[0065] After the capability server authenticates the second request, the capability server adds the multiple capability applications.

[0066] In this embodiment, the capability server identifies access users through the management system, such as... Figure 3 As shown, Figure 3This is a schematic diagram of the structure of the management system provided in an embodiment of the present invention. When the user type is a capability access user, the customer permission management module identifies whether the user requesting access to the target capability has the right to use it. After the capability server authenticates the first request, it routes the target capability application to the capability client.

[0067] When the user type is a system administrator, after the capability server authenticates the second request, the multiple capability applications are added to the capability server. System administrator permissions include: access customer management, customer authorization management, and system log querying. The capability server can manage the identity information and additional user information of registered users on the capability open platform through the customer access management module; it can identify whether a user requesting access to the target capability has the necessary permissions through the customer permission management module; and it can query management function operation logs and capability application usage logs through the system log query function.

[0068] Among them, such as Figure 4 As shown, Figure 4 This is a schematic diagram of the capability application management process provided in an embodiment of the present invention. After the capability server authenticates the second request, the capability server adds the plurality of capability applications, including:

[0069] The capability server authenticates the second signature information in the second request;

[0070] If the second signature information is authenticated by the capability server, the capability server grants the capability client administrator privileges.

[0071] The capability server obtains capability application data sent by the capability client, and the capability application data includes the addition and / or removal of the plurality of capability applications;

[0072] The capability server adds and / or removes the multiple capability applications based on the capability application data.

[0073] In this embodiment, the addition and / or removal of the multi-capability applications can be automatically completed by the management module of the capability server. The process of releasing the multiple capability applications can include three processes: application addition, application update, and application removal. The procedural steps of these processes are described below:

[0074] When an application is added, the capability server grants administrator privileges to the capability client. The administrator can fill in the basic information of the new application in the system management module through the capability client, such as: proxy server nginx routing information, version number, application name, etc.; transmit the basic information of the new application to the database layer in the form of a data compressed file in ZIP format; save the edited application information, go to the application list page and click the "Publish" function; the system obtains the list of applications currently in the published state, aggregates the nginx routing information of each application, and generates the current nginx configuration file through file read and write technology; automatically uploads the new nginx configuration file and application publishing package to the nginx deployment server; in the background, a remote script on the nginx deployment server is called to decompress the application publishing package and execute the "nginx -s reload" command to update the nginx server configuration.

[0075] When an application is taken offline, the administrator selects a published application on the application management list page to perform the offline operation. The system automatically retrieves the list of currently published applications, removes the applications to be taken offline from the list, aggregates the nginx routing configurations of the applications in the filtered application list, and generates the target nginx configuration file through file read / write technology. The system automatically uploads the newly generated nginx configuration file to the nginx deployment server and executes the remote command "nginx -s reload" to update the nginx server configuration and make the new routing effective.

[0076] When updating an application, the administrator selects the application to be updated, fills in the new version number, and uploads the upgrade package. The administrator saves the edited application information, goes to the application list page, and clicks the "Publish" function. The system retrieves the list of applications currently in the published state, aggregates the nginx routing information for each application, and generates the current nginx configuration file using file read / write technology. The system automatically uploads the new nginx configuration file and application deployment package to the nginx deployment server. In the background, a remote script on the nginx deployment server is called to decompress the application deployment package and execute the "nginx -s reload" command to update the nginx server configuration.

[0077] In this way, routing is automatically configured, file read and write technology is used to aggregate the routing configurations of various applications, and file push technology is used to upload the application to be published and the routing configuration file to be updated. Application publishing and routing updates are realized through remote script calling technology, which improves the convenience of the capability open platform.

[0078] It should be noted that the front end can adopt a micro-frontend architecture to break down the core capabilities of the capability open platform into multiple capability applications, and the back end can adopt a microservice governance framework (Spring Cloud) to realize the business decomposition and independent deployment of backend services.

[0079] See Figure 5 , Figure 5 This is a flowchart illustrating another capability opening method provided in an embodiment of the present invention, such as... Figure 5 As shown, the method includes the following steps:

[0080] Step 501: The capability client sends a first request to the capability server for the application of the target capability;

[0081] Step 502: The capability client receives the target capability application sent by the capability server after the first request has been authenticated. The target capability application is obtained by the capability server from multiple capability applications constructed by the capability server based on the first request.

[0082] Step 503: The capability client applies the target capability application.

[0083] In this embodiment, the user sends the first request to the capability server through the capability client. The parent application of the capability server's micro-frontend architecture authenticates the first request. The capability client receives the target capability application sent by the capability server after the first request has been authenticated. The target capability application is obtained by the capability server from multiple capability applications built based on the first request. Due to the advantage of the micro-frontend architecture, which does not impose mandatory requirements on the technology selection of the multiple capability applications, the constructed multiple capability applications can have independent technology stacks, decoupling the various capability applications and reducing the impact on other capability applications during independent iteration and modification. The user can directly obtain and apply the target capability application through the capability client. The target capability can be a capability application determined by the capability user from the multiple capability applications according to actual needs, lowering the threshold for accessing the capability open platform. When the capability server manages and maintains the target capability application, it reduces the impact on other capability applications, thereby improving the convenience of the capability open platform.

[0084] Optionally, the capability client applies the target capability application, including:

[0085] The capability client reads the identification mark on the target capability application, and the identification mark is used to decouple the capability client from the capability client after the target capability application is embedded with the capability client.

[0086] The capability client obtains UI configuration, which is configuration data generated by the capability server based on user information. The user information is user data obtained by the capability server after parsing the first signature information in the first request.

[0087] After the capability client customizes the interface of the target capability application according to the UI configuration, it applies the target capability application based on the identification mark.

[0088] The capability client can add a unique identifier to the root element of the target capability application as a constraint, and add user-defined UI configurations to the Hyper Text Markup Language (HTML) document of the current window to complete the rendering of custom styles. Thus, after the target application is connected to the capability client, users can customize the front-end UI theme of the target capability application according to their usage habits. Furthermore, the addition of a unique identifier to the root element of the target capability application as a constraint reduces the coupling between the target capability application and other functions in the capability client, thereby improving the convenience of the capability open platform.

[0089] Optionally, the method further includes:

[0090] The capability client sends a second request to the capability server to edit the multiple capability applications, the second request including second signature information;

[0091] The capability client obtains the administrator privileges granted by the capability server after the second signature information has been authenticated;

[0092] The capability client can edit capability application data under the administrator's privileges. The capability application data includes the addition and / or removal of the multiple capability applications.

[0093] The capability client sends the capability application data to the capability server, and the capability server adds and / or removes the multiple capability applications.

[0094] In this embodiment, the user sends a second request to the capability server through the capability client to edit the multiple capability applications. The capability client edits the capability application data under the administrator's privileges. The capability application data includes adding and / or decommissioning the multiple capability applications. The capability client sends the capability application data to the capability server, and the capability server adds and / or decommissions the multiple capability applications based on the capability application data.

[0095] It should be noted that the addition and / or removal of the multi-capability applications can be automatically completed by the management module of the capability server. The process of releasing the multiple capability applications can include three processes: application addition, application update, and application removal. The procedural steps of these processes will not be described in detail here to avoid repetition.

[0096] See Figure 6 , Figure 6 This is a schematic diagram of the structure of a capability open platform provided in an embodiment of the present invention, as shown below. Figure 6 As shown, the capability open platform 600 includes:

[0097] Module 601 is used by the capability server to build multiple capability applications, which have independent technology stacks.

[0098] Sending module 602 is used for the capability server to receive a first request for the application of a target capability sent by the capability client;

[0099] The routing module 603 is used to route the target capability application to the capability client after the capability server authenticates the first request. The target capability application is obtained by the capability server from the plurality of capability applications based on the first request.

[0100] Optionally, the routing module 603 includes:

[0101] The first authentication unit is used by the capability server to authenticate the first signature information in the first request;

[0102] The parsing unit is used to parse the first signature information and read the target capability application information and user information when the first signature information is authenticated by the capability server.

[0103] The first acquisition unit is used by the capability server to acquire the target capability application from the plurality of capability applications based on the target capability application information.

[0104] A routing unit is used by the capability server to route the target capability application to the capability client, and to add an identification tag to the target capability application. The identification tag is used to decouple the target capability application from the capability client after it is embedded in the capability client.

[0105] Optionally, the Capability Open Platform 600 also includes:

[0106] A generation module is used by the capability server to generate a user interface (UI) configuration based on the user information. The UI configuration is used by the user to customize the interface of the target capability application in the capability client.

[0107] Optionally, building module 601 includes:

[0108] A receiving submodule is used for the capability server to receive a second request from the capability client to edit the multiple capability applications;

[0109] An editing submodule is used to add the multiple capability applications to the capability server after the capability server has authenticated the second request.

[0110] Optionally, the editing submodule includes:

[0111] The second authentication unit is used by the capability server to authenticate the second signature information in the second request;

[0112] An authorization unit is used to grant the capability client administrator privileges when the second signature information is authenticated by the capability server.

[0113] The second acquisition unit is used for the capability server to acquire capability application data sent by the capability client, the capability application data including the addition and / or removal of the plurality of capability applications;

[0114] An editing unit is used by the capability server to add and / or remove the multiple capability applications based on the capability application data.

[0115] The capability open platform 600 provided in this embodiment of the invention can achieve Figure 1 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0116] See Figure 7 , Figure 7 This is a schematic diagram of another capability open platform provided in an embodiment of the present invention, such as... Figure 7 As shown, the capability open platform 700 includes:

[0117] The first sending module 701 is used for the capability client to send a first request for the target capability application to the capability server;

[0118] The receiving module 702 is used for the capability client to receive the target capability application sent by the capability server after the capability server has authenticated the first request, wherein the target capability application is obtained by the capability server from multiple capability applications constructed by the capability server based on the first request;

[0119] Application module 703 is used for the capability client to apply the target capability application.

[0120] Optionally, application module 703 includes:

[0121] The reading unit is used for the capability client to read the identification mark on the target capability application, the identification mark being used to decouple from the capability client after the target capability application is embedded in the capability client;

[0122] The acquisition unit is used for the capability client to acquire UI configuration, wherein the UI configuration is configuration data generated by the capability server based on user information, and the user information is user data obtained by the capability server after parsing the first signature information in the first request;

[0123] The application unit is used to apply the target capability application based on the identification mark after the capability client customizes the interface of the target capability application according to the UI configuration.

[0124] Optionally, the Capability Open Platform 700 also includes:

[0125] The second sending module is used for the capability client to send a second request to the capability server to edit the plurality of capability applications, the second request including second signature information;

[0126] The acquisition module is used by the capability client to acquire the administrator privileges granted by the capability server after the second signature information has been authenticated.

[0127] An editing module is used by the capability client to edit capability application data under the administrator's privileges. The capability application data includes the addition and / or removal of the multiple capability applications.

[0128] The third sending module is used for the capability client to send the capability application data to the capability server, and for the capability server to add and / or remove the multiple capability applications.

[0129] The capability open platform 700 provided in this embodiment of the invention can achieve Figure 5 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0130] See Figure 8 , Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention, such as... Figure 8 As shown, electronic device 800 includes:

[0131] At least one processor 801; and

[0132] Memory 802 communicatively connected to the at least one processor; wherein,

[0133] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform... Figure 1 The various processes of an embodiment of the capability opening method.

[0134] It should be noted that the electronic device 800 in this embodiment can be any implementation of the capability server in the method embodiment of the present invention. Any implementation of the capability server in the method embodiment of the present invention can be implemented by the electronic device 800 in this embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0135] See Figure 9 , Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention, such as... Figure 9 As shown, electronic device 900 includes:

[0136] At least one processor 901; and

[0137] Memory 902 communicatively connected to the at least one processor; wherein,

[0138] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform... Figure 5 The various processes of an embodiment of the capability opening method.

[0139] It should be noted that the electronic device 900 in this embodiment can be any implementation of the capability client in the method embodiment of the present invention. Any implementation of the capability client in the method embodiment of the present invention can be implemented by the electronic device 900 in this embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0140] In this embodiment of the invention, a non-transitory computer-readable storage medium storing computer instructions is also provided, the computer instructions being used to cause the computer to execute... Figure 1 The various processes of an embodiment of the capability-opening method, or the computer instructions for causing the computer to perform Figure 5 The various processes of the embodiments of the capability-opening method, and the ways to achieve the same beneficial effects, will not be described in detail here.

[0141] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of the present invention is not limited to performing functions in the order discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0142] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0143] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of the present invention.

Claims

1. A capability opening method, characterized in that, The method includes: The capability server builds multiple capability applications, and these multiple capability applications have independent technology stacks. The capability server receives a first request from the capability client to apply the target capability; After the capability server authenticates the first request, it routes the target capability application to the capability client. The target capability application is obtained by the capability server from the plurality of capability applications based on the first request. After the capability server authenticates the first request, it routes the target capability application to the capability client, including: The capability server authenticates the first signature information in the first request; When the first signature information is authenticated by the capability server, the capability server parses the first signature information and reads the target capability application information and user information. The capability server obtains the target capability application from the plurality of capability applications based on the target capability application information; The capability server routes the target capability application to the capability client and adds an identification tag to the target capability application. The identification tag is used to decouple the target capability application from the capability client after the capability client is embedded in the target capability application. The method further includes: The capability server generates a user interface (UI) configuration based on the user information. The UI configuration is used by the user to customize the interface of the target capability application in the capability client. The capability client adds a unique identification mark to the root element of the target capability application as a restriction condition and adds the user-customized UI configuration to the HTML document of the current window.

2. The method according to claim 1, characterized in that, The capability server builds multiple capability applications, including: The capability server receives a second request from the capability client to edit the multiple capability applications; After the capability server authenticates the second request, the capability server adds the multiple capability applications.

3. The method according to claim 2, characterized in that, After the capability server authenticates the second request, the capability server adds the plurality of capability applications, including: The capability server authenticates the second signature information in the second request; If the second signature information is authenticated by the capability server, the capability server grants the capability client administrator privileges. The capability server obtains capability application data sent by the capability client, and the capability application data includes the addition and / or removal of the plurality of capability applications; The capability server adds and / or removes the multiple capability applications based on the capability application data.

4. A capability opening method, characterized in that, The method includes: The capability client sends a first request to the capability server for the target capability application; The capability client receives the target capability application sent by the capability server after the first request has been authenticated. The target capability application is obtained by the capability server from multiple capability applications built by the capability server based on the first request. The target capability is applied by the client application. The capability client application of the target capability application includes: The capability client reads the identification mark on the target capability application, and the identification mark is used to decouple the capability client from the capability client after the target capability application is embedded with the capability client. The capability client obtains UI configuration, which is configuration data generated by the capability server based on user information. The user information is user data obtained by the capability server after parsing the first signature information in the first request. After the capability client customizes the interface of the target capability application according to the UI configuration, it applies the target capability application based on the identification mark. The capability client adds a unique identification mark to the root element of the target capability application as a restriction condition, and adds the user-defined UI configuration to the HTML document of the current window.

5. The method according to claim 4, characterized in that, The method further includes: The capability client sends a second request to the capability server to edit the multiple capability applications, the second request including second signature information; The capability client obtains the administrator privileges granted by the capability server after the second signature information has been authenticated; The capability client can edit capability application data under the administrator's privileges. The capability application data includes the addition and / or removal of the multiple capability applications. The capability client sends the capability application data to the capability server, and the capability server adds and / or removes the multiple capability applications.

6. A capability opening device, characterized in that, The device includes: A building module is used by the capability server to build multiple capability applications, which have independent technology stacks. The sending module is used for the capability server to receive a first request for the application of a target capability sent by the capability client; A routing module is used to route the target capability application to the capability client after the capability server authenticates the first request. The target capability application is obtained by the capability server from the plurality of capability applications based on the first request. The routing module includes: The first authentication unit is used by the capability server to authenticate the first signature information in the first request; The parsing unit is used to parse the first signature information and read the target capability application information and user information when the first signature information is authenticated by the capability server. The first acquisition unit is used by the capability server to acquire the target capability application from the plurality of capability applications based on the target capability application information. A routing unit is used by the capability server to route the target capability application to the capability client, and to add an identification tag to the target capability application. The identification tag is used to decouple the target capability application from the capability client after it is embedded in the capability client. The device further includes: The generation module is used by the capability server to generate a user interface (UI) configuration based on the user information. The UI configuration is used by the user to customize the interface of the target capability application in the capability client. The capability client adds a unique identification mark to the root element of the target capability application as a restriction condition and adds the user-customized UI configuration to the HTML document of the current window.

7. The apparatus according to claim 6, characterized in that, The building module includes: A receiving submodule is used for the capability server to receive a second request from the capability client to edit the multiple capability applications; An editing submodule is used to add the multiple capability applications to the capability server after the capability server has authenticated the second request.

8. The apparatus according to claim 7, characterized in that, The editing submodule includes: The second authentication unit is used by the capability server to authenticate the second signature information in the second request; An authorization unit is used to grant the capability client administrator privileges when the second signature information is authenticated by the capability server. The second acquisition unit is used for the capability server to acquire capability application data sent by the capability client, the capability application data including the addition and / or removal of the plurality of capability applications; An editing unit is used by the capability server to add and / or remove the multiple capability applications based on the capability application data.

9. A capability opening device, characterized in that, The device includes: The first sending module is used for the capability client to send a first request for the target capability application to the capability server; The receiving module is used for the capability client to receive the target capability application sent by the capability server after the capability server has authenticated the first request, wherein the target capability application is obtained by the capability server from multiple capability applications constructed by the capability server based on the first request; Application module, used by the capability client to apply the target capability; The application module includes: The reading unit is used for the capability client to read the identification mark on the target capability application, the identification mark being used to decouple from the capability client after the target capability application is embedded in the capability client; The acquisition unit is used for the capability client to acquire UI configuration, wherein the UI configuration is configuration data generated by the capability server based on user information, and the user information is user data obtained by the capability server after parsing the first signature information in the first request; The application unit is used to apply the target capability application based on the identification mark after the capability client customizes the interface of the target capability application according to the UI configuration; wherein, the capability client adds a unique identification mark to the root element of the target capability application as a restriction condition, and adds the user-customized UI configuration to the Hypertext Markup Language (HTML) document of the current window.

10. The apparatus according to claim 9, characterized in that, The device further includes: The second sending module is used for the capability client to send a second request to the capability server to edit the plurality of capability applications, the second request including second signature information; The acquisition module is used by the capability client to acquire the administrator privileges granted by the capability server after the second signature information has been authenticated. An editing module is used by the capability client to edit capability application data under the administrator's privileges. The capability application data includes the addition and / or removal of the multiple capability applications. The third sending module is used for the capability client to send the capability application data to the capability server, and for the capability server to add and / or remove the multiple capability applications.

11. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the capability opening method as described in any one of claims 1 to 3.

12. An electronic device, characterized in that, include: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the capability opening method as described in any one of claims 4 to 5.

13. A non-transitory computer-readable storage medium storing computer instructions, characterized in that, The computer instructions are used to cause the computer to perform the capability opening method as described in any one of claims 1 to 3, or the computer instructions are used to cause the computer to perform the capability opening method as described in any one of claims 4 to 5.

Images