Plug-in processing method and device, electronic equipment and plug-in platform

Abstract

The invention discloses a plug-in processing method and device, electronic equipment and a plug-in platform, relates to the technical field of data processing, and adopts a mode of combining a dynamic plug-in loading mechanism based on a target object function requirement and a remote warehouse to instantly acquire a plug-in. The technical problem that the efficiency of deploying the data center platform is low due to the fact that the data center platform supporting plug-in is lacked in the related technology is solved, and the technical effect of improving the efficiency of deploying the data center platform is achieved.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and in particular, to a method and device for processing plugins, an electronic device, and a plugin platform. Background Art

[0002] In the technical field of data center management, traditional monitoring and operation and maintenance platforms generally adopt an integrated design, integrating all functions tightly into the core system. Although this architecture can provide a comprehensive management perspective, it exposes obvious deficiencies in flexibility when facing changing requirements. Existing data center platforms have obvious defects in terms of function expansion, especially the lack of a common development platform that supports pluginization, resulting in duplicate work and resource waste for development teams, and seriously affecting the deployment efficiency of the data center platform. Summary of the Invention

[0003] This application provides a method and device for processing plugins, an electronic device, and a plugin platform, so as to at least solve the technical problem in related technologies that the lack of a data center platform supporting pluginization leads to relatively low efficiency in deploying the data center platform.

[0004] This application provides a method for processing plugins, including: determining a first functional plugin to be loaded according to the functional requirements of a target object; obtaining the first functional plugin from a target plugin repository system through a target plugin platform; inspecting the first functional plugin to obtain an inspection result; and when the inspection result indicates that the inspection is passed, loading the first functional plugin to the target plugin platform to provide services for the target object through the first functional plugin, where the target plugin platform is a data center management platform.

[0005] This application provides a plugin platform, and when the plugin platform is executed, it implements the steps of any of the above-mentioned methods for processing plugins.

[0006] This application also provides a device for processing plugins, including: a first determination unit for determining a first functional plugin to be loaded according to the functional requirements of a target object; a first acquisition unit for obtaining the first functional plugin from a target plugin repository system through the target plugin platform; an inspection unit for inspecting the first functional plugin to obtain an inspection result; and a first loading unit for loading the first functional plugin to the target plugin platform when the inspection result indicates that the inspection is passed to provide services for the target object through the first functional plugin, where the target plugin platform is a data center management platform.

[0007] This application also provides an electronic device, including: a memory for storing a computer program; and a processor for implementing the steps of any of the above-mentioned methods for processing plugins when executing the computer program.

[0008] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned plug-in processing methods are implemented.

[0009] The present application also provides a computer program product, including a computer program. When the computer program is executed by a processor, the steps of any of the above-mentioned plug-in processing methods are implemented.

[0010] Through the present application, since a dynamic plug-in loading mechanism based on the functional requirements of the target object is combined with the immediate acquisition of plug-ins from a remote repository, the technical problem in the related art of the lack of a data center platform supporting plug-inization, resulting in a relatively low efficiency in deploying the data center platform, can be solved. In this solution, the required plug-ins can be quickly determined and loaded according to specific actual requirements, avoiding the large amount of time and resources consumed by the overall software package update in the traditional method, thereby accelerating the speed of function deployment. By immediately downloading plug-ins from a remote plug-in repository and combining with the dynamic loading ability of the plug-in platform, new functions can quickly respond and be put into use, reducing the waiting time for system initialization and update, and thus achieving the technical effect of improving the efficiency of deploying the data center platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] To more clearly illustrate the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0012] Figure 1 is a hardware structural block diagram of plug-in processing provided according to an embodiment of the present application;

[0013] Figure 2 is the flow of the plug-in processing method provided according to an embodiment of the present application Figure 1 ;

[0014] Figure 3 is a schematic diagram of an update setting window provided according to an embodiment of the present application;

[0015] Figure 4 is a schematic diagram of a plug-in management interface provided according to an embodiment of the present application;

[0016] Figure 5 is a schematic diagram of an uninstall setting window provided according to an embodiment of the present application;

[0017] Figure 6 is a schematic diagram of a data backup window provided according to an embodiment of the present application;

[0018] Figure 7 is a schematic diagram of a function plug-in page provided according to an embodiment of the present application;

[0019] Figure 8 is the flowchart of a plug-in processing method provided according to an embodiment of the present application Figure 2 ;

[0020] Figure 9 is a schematic diagram of a plug-in platform provided according to an embodiment of the present application;

[0021] Figure 10 is a schematic diagram of plug-in processing provided according to an embodiment of the present application;

[0022] Figure 11 is a schematic diagram of a plug-in processing device provided according to an embodiment of the present application. Detailed implementation manners

[0023] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0024] It should be noted that in the description of the present application, the terms "including", "comprising" or any other variation thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. The terms "first", "second", etc. in the present application are used to distinguish similar objects and not to describe a specific order or sequence.

[0025] To enable those skilled in the art of the present technology to better understand the solution of the present application, the present application will be further described in detail below in conjunction with the accompanying drawings and specific implementation manners.

[0026] Combined with the specific application environment architecture or specific hardware architecture on which the execution of the plug-in processing method depends, the specific application environment architecture or specific hardware architecture will be described herein.

[0027] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 is a hardware structure block diagram of the execution of the system function in the embodiment of the present application. As Figure 1 shown, the server device may include one or more ( Figure 1Only one processor 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data are shown. Among them, the above server device may further include a transmission device 106 for communication functions and an input / output device 108. Those of ordinary skill in the art can understand that Figure 1 The structure shown is only schematic and does not limit the structure of the above server device. For example, the server device may further include more or fewer components than Figure 1 shown in Figure 1 or have a different configuration from that shown.

[0028] The memory 104 can be used to store computer programs. For example, software programs and modules of application software, such as the computer program corresponding to the execution method of the system function in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implements the above method. The memory 104 may include a high-speed random access memory and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some instances, the memory 104 may further include a memory remotely provided with respect to the processor 102, and these remote memories can be connected to the server device through a network. Examples of the above network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0029] The transmission device 106 is used to receive or send data via a network. Specific examples of the above network may include a wireless network provided by the communication provider of the server device. In one instance, the transmission device 106 includes a network adapter (abbreviated as NIC), which can be connected to other network devices through a base station and thus can communicate with the Internet. In one instance, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0030] Embodiments of the present application provide a method for handling memory faults. In combination with the execution process of the method for handling memory faults, the method is described in detail.

[0031] In this embodiment, a method for handling plugins is provided. Figure 2 is the flow of the method for handling plugins provided according to the embodiments of the present application. Figure 1 As Figure 2 shown, the method for handling plugins includes:

[0032] Step S201: Determine the first functional plug-in to be loaded according to the functional requirements of the target object.

[0033] Optionally, the target plug-in platform can receive the functional requirements of the user (i.e., the above-mentioned target object), such as power optimization, temperature monitoring, device warning, etc. According to the required functional requirements, search for the corresponding plug-in information in the remote plug-in warehouse management system. The plug-in information can include its function description and version information. Determine the first functional plug-in to be loaded according to the plug-in information. The above-mentioned functional plug-ins can include power management plug-ins, temperature monitoring plug-ins, cloud service integration plug-ins, etc.

[0034] Step S202: Obtain the first functional plug-in from the target plug-in warehouse system through the target plug-in platform.

[0035] Optionally, after the target plug-in platform determines the first functional plug-in to be loaded, the target plug-in platform can connect to the target plug-in warehouse system through the HTTPS security protocol. In the target plug-in warehouse system, the required first functional plug-in can be quickly located according to the plug-in ID, name, or version number.

[0036] After locating the required first functional plug-in, download the first functional plug-in from the target plug-in warehouse system to the target plug-in platform.

[0037] Step S203: Inspect the first functional plug-in to obtain an inspection result.

[0038] Optionally, after downloading the first functional plug-in, conduct a comprehensive inspection of the first functional plug-in to ensure its security, compatibility, and functionality, thereby avoiding potential system instability or security vulnerabilities. For example, calculate the hash value of the plug-in file and compare it with the hash value provided by the remote warehouse to ensure that the file has not been damaged or maliciously modified during transmission. For example, check the minimum and maximum platform versions supported by the plug-in to ensure that the plug-in is compatible with the current target plug-in platform version.

[0039] Step S204: When the inspection result indicates that the inspection is passed, load the first functional plug-in to the target plug-in platform to provide services for the target object through the first functional plug-in, where the target plug-in platform is a data center management platform.

[0040] Optionally, when the inspection result indicates that the inspection is passed, load the first functional plug-in based on the open service gateway architecture. After the plug-in is loaded, it can automatically register the services and interfaces it provides with the target plug-in platform. For example, the power management plug-in can register the power monitoring service, and the temperature monitoring plug-in can register the temperature sensor data collection interface, etc., thereby providing services for users through the target plug-in platform.

[0041] In summary, through steps S201 to S204, the target plug-in platform realizes dynamic function expansion based on user requirements. Users can flexibly select and load corresponding plug-ins according to the actual operation requirements of the data center, such as power optimization, temperature monitoring, equipment warning and other functions, improving the deployment efficiency of the target plug-in platform.

[0042] Optionally, in the plug-in processing method provided in the embodiment of the present application, after loading the first functional plug-in into the target plug-in platform, the method further includes: receiving, by the target plug-in platform, a first operation instruction of a target object; presenting, based on the first operation instruction, an update setting window to the target object; and receiving, through the update setting window, an update policy used by the target object to update the plug-ins in the target plug-in platform.

[0043] In an optional embodiment, in order to implement the full life cycle management of plug-ins, after loading the first functional plug-in into the target plug-in platform, a first operation instruction of a user (i.e., the above-mentioned target object) can be received through the plug-in management interface in the target plug-in platform. It should be noted that the first operation instruction may refer to an operation instruction of the target object regarding plug-in update.

[0044] After receiving the first operation instruction, the target plug-in platform presents an update setting window to the user. Update policy configuration options can be set in the update setting window. For example, automatic update: allows the plug-in platform to automatically check and apply plug-in updates. Manual update: the user needs to manually confirm and trigger plug-in updates. Update frequency: set the period for checking for updates, such as once a day, once a week, etc. Update source: select the repository source for updating plug-ins, the default online repository or a custom enterprise repository. After selecting an update policy in the update setting window, the target plug-in platform saves the update setting information and applies it to subsequent plug-in management processes.

[0045] For example, if the user selects the automatic update policy, the target plug-in platform will regularly automatically check for plug-in updates in the repository source according to the set update frequency. If there is a new version of the plug-in, the target plug-in platform will automatically download it and pass the preset integrity check, and then decide whether to apply the update based on the compatibility and security evaluation of the plug-in.

[0046] For example, if the user selects the manual update policy, the target plug-in platform will check for plug-in updates in the repository source when it receives an update operation instruction.

[0047] In an optional embodiment, when the update button in the plug-in management interface of the target plug-in platform is triggered by the user, Figure 3 the update setting window shown jumps to the current interface, as Figure 3As shown, the update policy can be set in the update settings window. For example, automatic update: allows the plugin platform to automatically check and apply plugin updates. Manual update: the administrator needs to manually confirm and trigger plugin updates. Update source: select the repository source for updating plugins, the default online repository or a custom enterprise repository, and whether to update the functional plugin in the target plugin platform after the plugin is downloaded.

[0048] Through the above steps, users can flexibly set the update policy according to the specific requirements and risk preferences of the data center, so as to obtain the latest functions and performance optimizations in a timely manner, and avoid potential risks and interruptions brought by unnecessary updates.

[0049] Optionally, in the plugin processing method provided in the embodiment of the present application, after receiving the update policy used by the target object to update the plugin in the target plugin platform through the update settings window, the method further includes: if the update policy is the first update policy, detecting whether there is a new version of the plugin in the target plugin platform based on a preset time period through the target plugin platform, and displaying the detection result to the target object; if the update policy is the second update policy, detecting whether there is a new version of the plugin in the target plugin platform when receiving the second operation instruction of the target object, and displaying the detection result to the target object.

[0050] In an optional embodiment, the target plugin platform (i.e., the data center management platform) can not only receive the update policy of the target object, but also execute different plugin update detection processes accordingly. If the target object selects the first update policy (i.e., the automatic update policy), the target plugin platform will automatically and regularly detect whether there are new versions of the plugins available for download and update. Preset time period: the user will specify a time period (such as daily, weekly or monthly) in the update policy. During this period, the platform will automatically detect whether there are new versions of the currently installed plugins in the remote plugin repository. After the detection is completed, the target plugin platform can feedback the detection result to the target object through the plugin management interface, informing which plugins have available new versions.

[0051] If the target object selects the second update policy, the target plugin platform will not automatically perform the update detection. Only when receiving the second operation instruction triggered by the user, the target plugin platform will start the detection process. After receiving the instruction, the target plugin platform immediately connects to the remote plugin repository to query the latest version information of all plugins. Finally, the detection result is feedback to the target object through the plugin management interface, informing which plugins have available new versions.

[0052] In an optional embodiment, the schematic diagram of the detection result displayed on the plugin management interface is as Figure 4As shown, the current detection results can be displayed in the plugin management interface, and update detection requests triggered by users can be received.

[0053] Through the design of the above update strategy, the flexibility of the target plugin platform and the customization ability of users are enhanced. Users can flexibly adjust the update strategy according to the actual situation to achieve the best operation and maintenance effect, while ensuring the stable operation of the system and information security.

[0054] Optionally, in the plugin processing method provided in the embodiments of the present application, after loading the first functional plugin into the target plugin platform, the method further includes: receiving a third operation instruction of a target object through the target plugin platform; displaying an uninstallation setting window to the target object based on the third operation instruction; receiving a selection operation of a plugin in the target plugin platform by the target object through the uninstallation setting window to determine the plugin to be uninstalled.

[0055] In an optional embodiment, in order to implement the full life cycle management of plugins, after loading the first functional plugin into the target plugin platform, an uninstall operation of the functional plugin by the user (i.e., the above-mentioned third operation instruction) can be received through the plugin management interface in the target plugin platform.

[0056] After receiving the third operation instruction, an uninstallation setting window will be displayed to the user. In the uninstallation setting window, the plugin to be uninstalled can be selected from the list of currently installed plugins in the target plugin platform. For example, the plugin name and the current version information of the plugin can be displayed in the uninstallation setting window. After the user confirms that it is correct, the plugin to be uninstalled is selected in the uninstallation setting window and the uninstallation instruction is submitted, for example, clicking Next.

[0057] In an optional embodiment, the uninstallation setting window is as Figure 5 As shown, in this interface, the user can select the plugin to be uninstalled and click Next after the selection is completed to perform the uninstallation operation.

[0058] By providing the uninstallation function, the target plugin platform can dynamically adjust the number of plugins according to actual needs, avoiding unnecessary resource occupation and cost expenditure. For example, when a certain function is no longer needed or when a new plugin occupies too much resources, the user can choose to uninstall it to release system resources and reduce the operating cost.

[0059] Optionally, in the plugin processing method provided in the embodiments of the present application, after determining the plugin to be uninstalled, the method further includes: receiving a fourth operation instruction of a target object through the target plugin platform; displaying a data backup window to the target object based on the fourth operation instruction to prompt the target object whether to perform a data backup operation.

[0060] In an optional embodiment, to avoid data loss during plug-in uninstallation, after determining the plug-in to be uninstalled, the target plug-in platform receives a fourth operation instruction from the user. For example, the user clicks "Next" in the uninstallation settings window. After receiving the fourth operation instruction, a data backup window is presented to the user. For example, as Figure 6 shown in the data backup window, the user selects the plug-ins for which data backup is required through this data backup window and clicks the "Confirm Backup" button to perform data backup.

[0061] By providing a data backup window before uninstalling the plug-in, it is ensured that the data related to the uninstalled plug-in is properly processed. Even if an accident occurs during the uninstallation process, the user can recover the data from the backup, preventing service interruption or data loss and enhancing the reliability of data center management.

[0062] Optionally, in the plug-in processing method provided in the embodiments of the present application, loading the first functional plug-in into the target plug-in platform includes: loading the backend module corresponding to the first functional plug-in into the plug-in container of the target plug-in platform, where the plug-in container is built based on the Open Service Gateway architecture; injecting the frontend module corresponding to the first functional plug-in into the Document Object Model node of the target plug-in platform to implement the display of the frontend interface corresponding to the first functional plug-in to the target object.

[0063] In an optional embodiment, loading the first functional plug-in into the target plug-in platform includes the following steps: The plug-in backend module is loaded into the plug-in container of the target plug-in platform. It should be noted that the plug-in container is built based on the Open Service Gateway architecture, and the Open Service Gateway architecture is a modular Java platform framework. The frontend module will be injected into the Document Object Model (DOM) node of the target plug-in platform. The Document Object Model (DOM) node is the structural model of a Web page and represents the source code structure of the page. By injecting the frontend resources (such as HTML, CSS, JavaScript) of the first functional plug-in into the DOM node, the user interface of the plug-in can be dynamically constructed and presented to the user. This method allows the plug-in interface to seamlessly integrate with other interfaces of the platform, providing a consistent user experience.

[0064] By loading the backend module of the first functional plug-in into the plug-in container based on the Open Service Gateway architecture and injecting the frontend module into the DOM node, not only is the rapid loading of the plug-in and the dynamic display of the interface achieved, but also the maintainability, upgrade efficiency, cost-effectiveness, scalability, and flexibility of the platform are significantly improved.

[0065] Optionally, in the plugin processing method provided in the embodiments of the present application, after loading the first functional plugin into the target plugin platform, the method further includes: receiving, by the target plugin platform, a fifth operation instruction of a target object for a second functional plugin; and based on the fifth operation instruction, presenting a function interface corresponding to the second functional plugin to the target object, so as to provide services for the target object through the second functional plugin.

[0066] In an optional embodiment, a user can use the loaded functional plugin through the following steps: when the user wants to access the second functional plugin, a fifth operation instruction can be triggered in the target plugin platform. After receiving the fifth operation instruction, the target plugin platform will present the function interface of the second functional plugin to the target object. For example, as Figure 7 shown in the schematic diagram, each function of the functional plugin is presented in the function interface.

[0067] Through the above steps, the user can see and operate all function options of the second functional plugin without experiencing page reload or system restart, improving the fluency and response speed of the operation.

[0068] Optionally, in the plugin processing method provided in the embodiments of the present application, after presenting the detection result to the target object, the method further includes: if the detection result indicates the existence of a new version of the plugin, loading the new version of the plugin into the target plugin platform; and in the case of successful loading, triggering a target message to the target object through the target plugin platform, where the target message is used to instruct the target object to restart the target plugin platform so that the new version of the plugin becomes effective.

[0069] In an optional embodiment, when it is detected that there is a new version of the plugin, the target plugin platform will automatically download and load the new version of the plugin into the plugin container of the target plugin platform without manual intervention. After the loading of the new version of the plugin is completed, the target plugin platform will generate and send a target message to the user, instructing the user to restart the target plugin platform so that the functions of the new version of the plugin become effective.

[0070] The function of automatically detecting and loading the new version of the plugin improves the automation level and operation and maintenance efficiency of data center management.

[0071] Optionally, in the plugin processing method provided in the embodiments of the present application, the target plugin repository system is at least one of the following: a local plugin repository system, a remote plugin repository system, and an Internet plugin repository system.

[0072] In an alternative embodiment, the local plugin repository system refers to the plugin repository installed on the server where the target plugin-based platform is located. It contains a set of pre-installed plugins, as well as plugins developed and tested locally on the platform. The advantage of the local repository is its fast response speed, as the plugin data is stored in the same network or physical location, reducing network latency and bandwidth consumption.

[0073] The remote plugin repository system refers to a repository located outside the target plugin-based platform that manages and transfers plugin data through a network connection. The remote repository can be a dedicated server cluster or a storage service provided by a cloud service provider. The advantage of the remote repository lies in its high scalability, capable of accommodating a large number of plugins and data, while also supporting large-scale plugin distribution and version control. Additionally, being far from the main platform, it can reduce the load on the main server and improve the operating efficiency of the platform.

[0074] The Internet plugin repository system is more extensive and can be an open plugin repository accessible to multiple target plugin-based platforms. The greatest advantage of the Internet repository is its diversity and innovation, which can attract a large number of third-party developers to contribute plugins, forming a rich plugin ecosystem.

[0075] Through the alternative local, remote, and Internet plugin repository systems, the target plugin-based platform can select the most suitable plugin distribution strategy according to different scenarios. For example, in an environment with high network latency, the local repository is preferred to reduce waiting time; while for scenarios that require frequent plugin updates, the remote or Internet repository is more suitable.

[0076] Optionally, in the plugin processing method provided in the embodiment of the present application, the inspection of the first functional plugin to obtain the inspection result includes: inspecting the digital signature information corresponding to the first functional plugin to obtain a first inspection sub-result; inspecting the checksum corresponding to the first functional plugin to obtain a second inspection sub-result; and obtaining the inspection result based on the first inspection sub-result and the second inspection sub-result.

[0077] In an alternative embodiment, to ensure the security and integrity of the first functional plugin, the inspection of the first functional plugin includes the following steps: when the first functional plugin is downloaded to the target plugin-based platform, the target plugin-based platform inspects the digital signature information of the first functional plugin. The target plugin-based platform decrypts the digital signature using the public key corresponding to the plugin developer or publisher, and then recalculates the hash value of the plugin for comparison. If the decrypted hash value matches the actual hash value of the plugin, the digital signature is valid, the plugin has not been tampered with, and the first inspection sub-result is obtained as passed.

[0078] Then, the checksum corresponding to the first functional plugin can also be verified. It should be noted that when the plugin repository uploads the plugin file, it will calculate the checksum value of the plugin. When the plugin is downloaded to the target plugin platform, the platform will calculate the checksum value of the file again and compare it with the checksum value provided by the plugin repository. If the two values are the same, the second verification sub-result is passed.

[0079] Finally, the verification result is obtained based on the comprehensive judgment of the first verification sub-result (digital signature validity) and the second verification sub-result (file integrity).

[0080] Through the dual verification mechanism of digital signature information and checksum, the security and integrity of the first functional plugin are effectively ensured.

[0081] Optionally, in the plugin processing method provided in the embodiment of the present application, after presenting the detection result to the target object, the method further includes: if the detection result indicates that there is a new version of the plugin, the new version of the plugin is loaded to the target plugin platform through the hot update mechanism to implement the update operation of the old version of the plugin.

[0082] In an optional embodiment, the target plugin platform regularly or according to a user request checks the version information of the first functional plugin in the remote repository to determine whether there is a new version of the plugin available. If a new version of the plugin is detected, the target plugin platform can load the new version of the plugin to the target plugin platform through the hot update mechanism. After the update operation is completed, the target plugin platform can also send a notification to the user indicating that the new version of the plugin has been successfully loaded and can be used normally.

[0083] The hot update mechanism avoids system interruption or restart caused by plugin updates, ensures the continuous operation of the target plugin platform, and improves the overall system availability and stability.

[0084] Optionally, in the plugin processing method provided in the embodiment of the present application, before determining the first functional plugin to be loaded according to the functional requirements of the target object, the method further includes: constructing a functional plugin based on the open service gateway architecture specification to obtain a third functional plugin; obtaining the dependency declaration and function license information corresponding to the third functional plugin; digitally signing the third functional plugin to obtain digital signature information; packaging the third functional plugin, the dependency declaration, the function license information, and the digital signature information to obtain a file package in a preset format; uploading the file package in the preset format to the target plugin repository system.

[0085] In an optional embodiment, the following steps can be used to implement the construction process of the functional plugin, which specifically includes: first, constructing a functional plugin based on the open service gateway architecture to obtain a third functional plugin.

[0086] During the development of a functional plugin, it is necessary to clearly declare other plugins or libraries that the plugin depends on (i.e., the above-mentioned dependency declaration), as well as the function licenses required for the use of the plugin. The dependency declaration ensures that all necessary components can be correctly identified and loaded during plugin installation, while the function license information is used to ensure that the plugin complies with authorization and compliance requirements.

[0087] Moreover, developers can use a private key to digitally sign the functional plugin. The digital signature information is attached to the plugin file and is used for subsequent security verification on the plugin platform. The digital signature information provides source verification and anti-tampering protection for the plugin, ensuring the credibility and security of the plugin. Integrate the functional plugin, dependency declaration, function license information, and digital signature information to obtain a file package in a preset format. For example, a JAR file package. Finally, upload the file package to the target plugin repository system, which can provide secure plugin storage and download services based on the HTTPS protocol. The uploaded plugins can be searched, downloaded, and installed in the repository, thus realizing the distribution and dynamic integration of functional plugins.

[0088] Through the above standardized plugin development, packaging, and uploading processes, the quality and security of functional plugins are effectively improved, the interoperability of plugins is enhanced, the user's trust is increased, while ensuring the compliance of function usage and simplifying the plugin management process.

[0089] Optionally, in the plugin processing method provided in the embodiment of the present application, when inspecting the first functional plugin, the inspection result includes: inspecting the digital signature information corresponding to the first functional plugin to obtain a third inspection sub-result; performing a legality inspection on the function license information corresponding to the first functional plugin to obtain a fourth inspection sub-result; and obtaining the inspection result based on the third inspection sub-result and the fourth inspection sub-result.

[0090] In an optional embodiment, to improve the security of the first functional plugin, the target plugin platform inspects the digital signature information corresponding to the first functional plugin. If the signature is correct, the third inspection sub-result is passed, indicating that the plugin has not been tampered with and the source is reliable.

[0091] Then, the target plugin platform will further check the legality of the function license information to obtain a fourth inspection sub-result. Finally, the inspection result is obtained based on the third inspection sub-result and the fourth inspection sub-result. If both the third inspection sub-result and the fourth inspection sub-result are passed, the inspection result is passed, and the plugin is allowed to be loaded on the platform. Otherwise, the plugin will be marked as untrusted or unauthorized and will be blocked from loading.

[0092] Through the above inspection of digital signature and function license information, the integrity and source authenticity of the plugin are ensured, effectively preventing the intrusion of malicious software and unauthorized modifications.

[0093] Optionally, in the plugin processing method provided in the embodiments of the present application, loading the first functional plugin into the target plugin platform includes: obtaining the dependency declaration corresponding to the first functional plugin; determining the dependency tree corresponding to the first functional plugin according to the dependency declaration, where the dependency tree is composed of the functional plugins on which the first functional plugin depends; and loading the first functional plugin into the target plugin platform according to the dependency tree.

[0094] In an alternative embodiment, when the target plugin platform loads the first functional plugin, it first parses the metadata file of the first functional plugin and extracts the dependency declaration therefrom. The dependency declaration specifies other plugins or libraries necessary for the plugin to run.

[0095] Construct the dependency tree corresponding to the first functional plugin according to the parsed dependency declaration. The dependency tree is a data structure used to describe the dependency relationships between plugins, including direct dependencies and indirect dependencies. The target plugin platform analyzes all declared dependencies to ensure there are no circular dependencies and determines the correct loading order.

[0096] For example, if the first functional plugin A depends on plugins B and C, and plugin B depends on plugin D, then the dependency tree will have the structure of A->B->D and A->C, ensuring that D is loaded before B, and B and C are loaded before A.

[0097] Finally, the target plugin platform dynamically loads the plugins according to the order of the dependency tree, thereby achieving the loading of the first functional plugin.

[0098] Through the construction of the dependency declaration and the dependency tree, the problem of plugin loading failure caused by missing dependencies or version incompatibilities is avoided.

[0099] Optionally, in the plugin processing method provided in the embodiments of the present application, determining the dependency tree corresponding to the first functional plugin according to the dependency declaration includes: determining the fourth functional plugin on which the first functional plugin depends according to the dependency declaration; judging whether the fourth functional plugin has a dependent functional plugin according to the dependency declaration of the fourth functional plugin; if the fourth functional plugin has a dependent functional plugin, then repeat the step of determining the fifth functional plugin on which the fourth functional plugin depends according to the dependency declaration of the fourth functional plugin until the currently determined functional plugin according to the dependency declaration has no dependent functional plugin, and obtaining the dependency tree based on the functional plugins determined according to the dependency declaration.

[0100] In an optional embodiment, the following steps are adopted to construct the above dependency tree: First, the target plug-in platform determines the fourth functional plug-in directly dependent on the first functional plug-in according to the dependency declaration of the first functional plug-in. This is the starting point for constructing the dependency tree, that is, the first-level dependency. Then, it is determined whether the fourth functional plug-in has dependencies, that is, the fifth functional plug-in, through the dependency declaration of the fourth functional plug-in.

[0101] If the fourth functional plug-in has a dependent fifth functional plug-in, the above steps are repeatedly executed, that is, the dependency declaration of the fifth functional plug-in is checked to determine the sixth functional plug-in it depends on, and so on, until the currently analyzed plug-in has no dependencies. Finally, the target plug-in platform generates a complete dependency tree based on all the dependent plug-ins collected during the recursive process. The dependency tree represents the relationship between the first functional plug-in and all its direct and indirect dependent plug-ins in a hierarchical structure.

[0102] The construction of the dependency tree ensures that all plug-ins are loaded according to their correct dependency relationships, avoiding runtime errors caused by improper loading order. By recursively checking the dependencies of each plug-in, it can be ensured that there are no missing components in the system, thereby improving the stability and reliability of the overall system.

[0103] Optionally, in the plug-in processing method provided in the embodiment of the present application, loading the first functional plug-in into the target plug-in platform according to the dependency tree includes: determining the loading order of the first functional plug-in and the functional plug-ins dependent on the first functional plug-in according to the dependency tree; loading the first functional plug-in and the functional plug-ins dependent on the first functional plug-in into the target plug-in platform according to the loading order.

[0104] In an optional embodiment, the target plug-in platform analyzes the dependency tree to determine the loading order, ensuring that when each functional plug-in is loaded, all its dependent plug-ins have been loaded. According to the determined loading order, the plug-in platform can dynamically load each functional plug-in until the first functional plug-in is loaded. For example, the plug-in loading order may be: D->B->C->A, that is, first load the bottommost fifth functional plug-in D, then load the fourth functional plug-ins B and C in turn, and finally load the first functional plug-in A.

[0105] By ensuring that all dependent plug-ins have been correctly loaded before loading the first functional plug-in, system exceptions caused by missing dependencies or improper loading order can be avoided, thereby significantly improving the stability and reliability of the system.

[0106] Optionally, in the plugin processing method provided by the embodiments of the present application, after loading the first functional plugin into the target plugin platform, the method further includes: receiving, by the target plugin platform, an access instruction for the target object to access the sixth functional plugin; judging, according to the identity information corresponding to the target object, whether the target object has the permission to access the functional interface corresponding to the access instruction; if the target object has the permission to access the functional interface corresponding to the access instruction, pushing the functional interface corresponding to the access instruction to the target object.

[0107] In an optional embodiment, when a user attempts to access the sixth functional plugin through the target plugin platform, based on the user's identity information (such as username, role), the target plugin platform performs permission verification to judge whether the user has the permission to access the specified functional interface. If the user's permission verification passes, the target plugin platform will dynamically push the functional interface corresponding to the access instruction to the user. If the user's permission verification fails, the user will be prompted that they do not have the permission to access this interface.

[0108] Through permission control, it is ensured that sensitive functions cannot be accessed by unauthorized users, thereby improving the security and data protection level of the target plugin platform.

[0109] Optionally, in the plugin processing method provided by the embodiments of the present application, judging, according to the identity information corresponding to the target object, whether the target object has the permission to access the functional interface corresponding to the access instruction includes: obtaining the function permission information corresponding to the sixth functional plugin; judging, according to the identity information and the function permission information, whether the target object has the permission to access the functional interface corresponding to the access instruction.

[0110] In an optional embodiment, when the target plugin platform receives an access instruction from a user for the sixth functional plugin, the first step is to obtain the function permission information (i.e., License) corresponding to this plugin. The function permission information can be included in the metadata of the plugin, which defines the roles and permissions required to access this plugin.

[0111] The target plugin platform checks the user's identity information, including their role, permissions, and authorized License information, and compares it with the function permission information of the sixth functional plugin. If the identity information of the target object matches the function permission information, that is, the target object has the necessary permissions and licenses to access this functional interface, the system will allow the execution of the access instruction, otherwise the permission verification fails and the access is refused.

[0112] Cross-verifying the plugin functions with the user permissions and License authorization information, and only allowing access to relevant functions when all conditions are met effectively prevents unauthorized access and operations, enhances the security of the system, and meets the compliance requirements.

[0113] Optionally, in the plugin processing method provided in the embodiments of the present application, after uploading a file package in a preset format to the target plugin repository system, the method further includes: determining a plurality of functional plugins that match the attribute information based on target parameters, where the attribute information is at least one of the following: identity information of the target object, the server machine code corresponding to the target object, and the function license information of the functional plugin; displaying the plurality of functional plugins that match the attribute information to the target object through the target plugin repository system.

[0114] In an alternative embodiment, when a user logs in to the target plugin repository system, the target plugin repository system obtains target parameters. For example, the user's identity information (such as user role, department affiliation), the server machine code (used to identify specific hardware resources), and the function license information (License type, expiration date, etc.). Based on the obtained target parameters, a match is made with the attribute information of the multiple functional plugins stored in the plugin repository, and according to the match result, the functional plugins that match the target parameters are determined. Finally, the information of the functional plugins that match the attribute information of the target object is displayed in the personal interface of the target object, including plugin name, description, version, compatibility information, License requirements, etc., to facilitate the user to select and install according to their own needs.

[0115] Determining the functional plugins that can be displayed through parameters such as the user's identity realizes differentiated plugin publishing and improves the user experience.

[0116] Optionally, in the plugin processing method provided in the embodiments of the present application, after uploading a file package in a preset format to the target plugin repository system, the method further includes: determining a seventh functional plugin to be recommended based on the identity information of the target object; displaying the seventh functional plugin to the target object through the target plugin repository system.

[0117] In an alternative embodiment, when the target object (user) logs in to the target plugin repository system, the system first obtains the user's identity information, including but not limited to user role, department affiliation, etc. The target plugin repository system analyzes the attribute information of the multiple functional plugins stored, including the target user role, applicable department, function description, etc. for each plugin. Then, the system matches this plugin attribute information with the identity information of the target object to determine which plugins best meet the user's needs.

[0118] Then, based on the above match result, the system filters out the functional plugin that best matches the identity information of the target object, that is, the seventh functional plugin, as the plugin to be recommended.

[0119] Finally, the system displays the information of these seventh functional plugins to be recommended in the personal interface of the target object, including plugin name, function description, recommendation reason, etc., to facilitate the user to quickly identify and select according to their own needs.

[0120] In an optional embodiment, the plug-in recommendation can also be implemented through the following steps: Obtain the running status of the target plug-in platform, such as hardware usage, alert level, business priority, etc. Sort the plug-ins according to the relevance between the functions of the plug-ins and the running status, and then display the sorted list of plug-ins to the user. When sorting the plug-ins, different weight coefficients can also be classified for different plug-ins according to business goals and personalized demand information input by the user. And the relevance between the functions of the plug-ins and the running status can also be determined by machine learning methods to achieve more accurate sorting.

[0121] Through the intelligent recommendation mechanism, users can find plug-ins that match their roles and needs more quickly, reducing the time for blind searching and experimentation, and significantly improving the user experience and work efficiency.

[0122] Optionally, in the plug-in processing method provided in the embodiment of the present application, the method further includes: constructing an eighth functional plug-in based on the open service gateway architecture specification according to the personalized needs of the target object; pushing the eighth functional plug-in to the target interface corresponding to the target object in the target plug-in platform through the target plug-in repository system.

[0123] In an optional embodiment, the target plug-in platform can first collect the personalized needs of the target object through user feedback, behavior analysis, or direct requests, etc., such as specific monitoring metrics, customized report formats, or special hardware control requirements, etc. Based on the collected requirements, use the specifications of the open service gateway architecture to design and develop the eighth functional plug-in. The plug-in developer needs to clearly declare the functions, dependencies, service interfaces, and related metadata of the plug-in to ensure that the plug-in can be correctly identified and loaded.

[0124] After development, the eighth functional plug-in needs to be tested to ensure the correctness and stability of its functions. After passing the test, the plug-in is packaged into a file package in a preset format, including the code, resource files, and metadata of the plug-in, and then uploaded to the target plug-in repository system.

[0125] Finally, the eighth functional plug-in can be directly pushed to the personal interface of the target object in the target plug-in platform through the real-time communication protocol, without the user having to actively search or download.

[0126] Constructing plug-ins through the personalized needs of the target object enables each user to obtain the functions that best match their needs, significantly improving the personalization degree of the service experience and meeting the specific needs of different users and scenarios.

[0127] Optionally, in the plugin processing method provided in the embodiments of the present application, plugins in the target plugin platform communicate with each other through a plugin communication bus, where the plugin communication bus is designed based on an event-driven model.

[0128] In an optional embodiment, plugins in the target plugin platform can communicate with each other through a plugin communication bus. The plugin communication bus can be regarded as a centralized information exchange platform. Each plugin can publish events (i.e., messages of a specific type) to the bus and can also subscribe to events published by other plugins. When an event is published, the bus is responsible for forwarding the event to all plugins that have subscribed to the corresponding event type, thereby realizing communication and collaboration between plugins. In the plugin communication bus, the event-driven model enables the interaction between plugins to be triggered by events (such as device state changes, user operations, system alarms, etc.), rather than being achieved through predefined function calls.

[0129] For example, assume that there is a device monitoring plugin that publishes a "ServerFault Event" event to the plugin communication bus when it detects a server failure. At this time, any plugin that has subscribed to such an event (such as an "alarm handling plugin" and a "logging plugin") will receive this event and respond and process it according to its own functional requirements, such as sending an alarm notification and recording a fault log.

[0130] In an optional embodiment, the full life cycle management of plugins can be implemented through a flowchart as Figure 8 shown. Specifically, it includes: uploading the plugin to the target plugin platform or the target plugin platform obtaining the plugin, verifying the plugin, including but not limited to digital signature verification and License legality check. After passing the verification, analyzing the dependencies between plugins and constructing a plugin dependency tree to determine a reasonable plugin loading order. Ensuring that all dependent plugins already exist and can work properly, avoiding plugin loading failures caused by missing or conflicting dependencies. After verification and dependency resolution, plugin installation and plugin activation are performed. After the plugin is activated, the plugin runs on the target plugin platform, and plugin stop and plugin uninstallation can also be performed on the target plugin platform. Pluginization enables functions to be dynamically loaded and unloaded according to user needs without the need for overall platform updates, greatly improving the speed and flexibility of function deployment.

[0131] In the plugin processing method provided by the embodiments of the present application, since a dynamic plugin loading mechanism based on the functional requirements of the target object is combined with the immediate acquisition of plugins from the remote repository, the technical problem in the related art that the lack of a data center platform supporting pluginization leads to low efficiency in deploying the data center platform can be solved. In this solution, the required plugins can be quickly determined and loaded according to specific actual requirements, avoiding the large amount of time and resources consumed by the overall software package update in the traditional method, thereby accelerating the speed of function deployment. By immediately downloading plugins from the remote plugin repository and combining with the dynamic loading ability of the plugin platform, new functions can quickly respond and be put into use, reducing the waiting time for system initialization and update, and thus achieving the technical effect of improving the efficiency of deploying the data center platform.

[0132] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0133] The embodiments of the present application also provide a plugin platform, and when the plugin platform is executed, the steps of any of the above plugin processing methods are implemented. In an optional embodiment, the schematic diagram of the plugin platform can be as Figure 9 shown, including: a plugin management core module, a component dependency resolution module, an interface pluginization engine module, a permission and function license (License) linkage module, a plugin communication bus, and a module plugin verification mechanism.

[0134] Plugin management core module: Build a plugin running container based on the Open Service Gateway Initiative (OSGi) standard, supporting dynamic loading, unloading, and version management of plugins; Component dependency resolution module: Used to analyze the dependency relationships between plugins, automatically build a plugin dependency tree, and ensure a reasonable plugin installation order; Interface pluginization engine module: Package the front-end page code in the form of a plugin, supporting dynamic loading and rendering of resources such as HTML, JS, and CSS; Permission and function license linkage module: Cross-verify the plugin functions with user permissions and License authorization information, and only allow access to relevant functions when all conditions are met; Plugin repository management system: Support tenant-level plugin management and a directed push mechanism, and implement differential plugin release based on customer License information; Plugin life cycle management module: Responsible for the full life cycle control of plugins, such as installation, startup, stop, uninstallation, rollback, etc.; Plugin communication bus module: Provide a standardized message passing interface for plugins to achieve cross-plugin function calls.

[0135] In an optional embodiment, the plug-in management core module: The present invention adopts an open service gateway architecture as the core container for plug-in operation, supporting dynamic loading, unloading, version management, and service registration of plug-ins (Bundles). Each plug-in is packaged as an independent JAR file, containing its class path, dependency declarations, and metadata. For example, in the alert plug-in Bundle_A.jar, the com.example.alert.AlertService interface is defined, and its dependency on the log plug-in Bundle_Log.jar is declared through MANIFEST.MF. The plug-in management core module automatically resolves the dependency relationships at startup and loads them in sequence.

[0136] Component dependency resolution module: The component dependency resolution module constructs a dependency graph between plug-ins and determines the plug-in loading order by reading the plug-in metadata (such as the Import-Package and Require-Bundle fields in MANIFEST.MF), avoiding plug-in startup failures caused by dependency loops or missing dependencies.

[0137] Interface plug-in engine module: The plug-ins contain front-end page elements. Each plug-in contains HTML templates, JavaScript business logic, and CSS files. The platform dynamically loads these resources through a plug-in loader and injects them into the specified DOM nodes.

[0138] Permissions and License linkage module: The permissions and License linkage module records the user's role permissions and License authorization information in the database. When a user attempts to access a certain plug-in function, the system first verifies whether the user has the corresponding permissions and checks whether the License is within the valid period and the authorization scope covers the current function.

[0139] For example, the reporting_plugin plug-in requires the user to have the REPORT_VIEW permission and the License type to be Enterprise. If the user does not have this permission or the License is Trial, access is prohibited.

[0140] Plug-in repository management system: The remote plug-in repository provides plug-in download services based on the HTTPS protocol and supports multi-tenant management. The administrator can push specific plug-ins to the target customers according to the customer ID, server machine code, and License information. The push instructions are executed through the background task queue and support timed triggering or manual triggering.

[0141] Plugin Lifecycle Management Module: The plugin lifecycle management module is responsible for the installation, startup, stop, uninstallation, and rollback of plugins. For example, users can click "Upgrade Plugin" through the management interface, and the system will download the new version of the plugin from the remote repository, perform a hot replacement after verifying the signature, without affecting the operation of other plugins.

[0142] Plugin Communication Bus Module: The plugin communication bus module is designed based on the event-driven model, providing a unified message publishing and subscription interface for each plugin. For example, after the alarm plugin detects an anomaly, it broadcasts a message through the communication bus, and the log plugin listens for this event and records relevant information.

[0143] In an optional embodiment, the schematic diagram of plugin processing is as Figure 10 shown, specifically including:

[0144] Plugin Development and Upload: Developers develop plugins according to the specifications of the open service gateway architecture and upload them to the remote plugin repository management system. The plugin contains metadata (such as dependency declarations, License requirements, etc.) and is digitally signed to ensure trustworthiness. It should be noted that the License of the plugin can be obtained through the License generation system.

[0145] Plugin Download and Verification: Users access the plugin-based platform through the browser via the HTTPS protocol and select the plugin to be installed. The plugin-based platform downloads the required plugin from the remote plugin repository management system. After the download is complete, the plugin verification mechanism performs digital signature verification and License legality check on the plugin.

[0146] Plugin Loading and Permission Verification: After passing the verification, the plugin management core module loads the plugin and resolves the dependency relationship through the component dependency resolution module. The permission and function license (License) linkage module checks the user's permissions and License authorization to ensure that the user has the right to access the plugin functions.

[0147] Plugin Running and Communication: After the plugin is successfully loaded, the interface pluginization engine module dynamically loads the front-end resources of the plugin into the user's browser. Plugins communicate with each other and collaborate on functions through the plugin communication bus module.

[0148] Remote Plugin Update: The remote plugin repository management system supports a directed push mechanism. Administrators can release customized or new version plugins based on customer information or server machine codes. The plugin-based platform obtains the updated plugin through the HTTPS protocol and completes the upgrade through the hot update mechanism without restarting the main program.

[0149] License Management: The License generation system is responsible for generating and managing Licenses to ensure the legitimate use of plugin functions. The plugin verification mechanism checks the validity of the License when the plugin is loaded to prevent unauthorized access.

[0150] An embodiment of the present application also provides a plugin processing device. Figure 11 As shown in the schematic diagram of the plugin processing device provided by the embodiment of the present application, Figure 11 as shown, the schematic diagram of the plugin processing device includes:

[0151] A first determination unit 1101, configured to determine a first functional plugin to be loaded according to the functional requirements of the target object;

[0152] A first acquisition unit 1102, configured to obtain the first functional plugin from the target plugin repository system through the target plugin platform;

[0153] An inspection unit 1103, configured to inspect the first functional plugin to obtain an inspection result;

[0154] A first loading unit 1104, configured to load the first functional plugin to the target plugin platform when the inspection result indicates that the inspection is passed, so as to provide services for the target object through the first functional plugin, where the target plugin platform is a data center management platform.

[0155] In the plugin processing device provided by the embodiment of the present application, the first determination unit 1101 determines the first functional plugin to be loaded according to the functional requirements of the target object; the first acquisition unit 1102 obtains the first functional plugin from the target plugin repository system through the target plugin platform; the inspection unit 1103 inspects the first functional plugin to obtain an inspection result; the first loading unit 1104 loads the first functional plugin to the target plugin platform when the inspection result indicates that the inspection is passed, so as to provide services for the target object through the first functional plugin, where the target plugin platform is a data center management platform, which solves the technical problem in the related art that the lack of a data center platform supporting pluginization leads to a relatively low efficiency in deploying the data center platform. In this solution, the required plugin can be quickly determined and loaded according to specific actual requirements, avoiding the large amount of time and resources consumed by the overall software package update in the traditional method, thereby accelerating the speed of function deployment. By instantaneously downloading the plugin from the remote plugin repository and combining the dynamic loading ability of the plugin platform, new functions can quickly respond and be put into use, reducing the waiting time for system initialization and update, and thus achieving the technical effect of improving the efficiency of deploying the data center platform.

[0156] Optionally, in the plugin processing device provided in the embodiments of the present application, the device further includes: a first receiving unit, configured to receive a first operation instruction of a target object through a target plugin platform after loading a first functional plugin to the target plugin platform; a first display unit, configured to display an update setting window to the target object based on the first operation instruction; a second receiving unit, configured to receive an update policy for updating a plugin in the target plugin platform from the target object through the update setting window.

[0157] Optionally, in the plugin processing device provided in the embodiments of the present application, the device further includes: a second display unit, configured to, after receiving an update policy for updating a plugin in the target plugin platform from the target object through the update setting window, if the update policy is a first update policy, detect whether there is a new version of the plugin in the target plugin platform based on a preset time period through the target plugin platform, and display the detection result to the target object; a third display unit, configured to, if the update policy is a second update policy, detect whether there is a new version of the plugin in the target plugin platform when receiving a second operation instruction of the target object, and display the detection result to the target object.

[0158] Optionally, in the plugin processing device provided in the embodiments of the present application, the device further includes: a third receiving unit, configured to receive a third operation instruction of a target object through a target plugin platform after loading a first functional plugin to the target plugin platform; a fourth display unit, configured to display an uninstall setting window to the target object based on the third operation instruction; a fourth receiving unit, configured to receive a selection operation of a plugin in the target plugin platform from the target object through the uninstall setting window to determine the plugin to be uninstalled.

[0159] Optionally, in the plugin processing device provided in the embodiments of the present application, the device further includes: a fifth receiving unit, configured to receive a fourth operation instruction of a target object through a target plugin platform after determining the plugin to be uninstalled; a fifth display unit, configured to display a data backup window to the target object based on the fourth operation instruction to prompt the target object whether to perform a data backup operation.

[0160] Optionally, in the plugin processing device provided in the embodiments of the present application, the first loading unit includes: a first loading subunit, configured to load a backend module corresponding to the first functional plugin into a plugin container of the target plugin platform, where the plugin container is constructed based on an open service gateway architecture; an injection subunit, configured to inject a frontend module corresponding to the first functional plugin into a document object model node of the target plugin platform to implement displaying a frontend interface corresponding to the first functional plugin to the target object.

[0161] Optionally, in the plugin processing device provided in the embodiments of the present application, the device further includes: a sixth receiving unit, configured to receive a fifth operation instruction of a target object on a second functional plugin through the target plugin platform after loading the first functional plugin to the target plugin platform; a sixth display unit, configured to display a functional interface corresponding to the second functional plugin to the target object based on the fifth operation instruction, so as to provide services for the target object through the second functional plugin.

[0162] Optionally, in the plugin processing device provided in the embodiments of the present application, the device further includes: a second loading unit, configured to load a new version of the plugin to the target plugin platform if the detection result indicates the existence of a new version of the plugin after displaying the detection result to the target object; a triggering unit, configured to trigger a target message to the target object through the target plugin platform in the case of successful loading, where the target message is used to instruct the target object to restart the target plugin platform so that the new version of the plugin becomes effective.

[0163] Optionally, in the plugin processing device provided in the embodiments of the present application, the verification unit includes: a first verification subunit, configured to verify the digital signature information corresponding to the first functional plugin to obtain a first verification sub-result; a second verification subunit, configured to verify the checksum corresponding to the first functional plugin to obtain a second verification sub-result; a first determination subunit, configured to obtain a verification result based on the first verification sub-result and the second verification sub-result.

[0164] Optionally, in the plugin processing device provided in the embodiments of the present application, the target plugin repository system is at least one of the following: a local plugin repository system, a remote plugin repository system, and an Internet plugin repository system.

[0165] Optionally, in the plugin processing device provided in the embodiments of the present application, the device further includes: a third loading unit, configured to load a new version of the plugin to the target plugin platform through a hot update mechanism to implement an update operation on the old version of the plugin if the detection result indicates the existence of a new version of the plugin after displaying the detection result to the target object.

[0166] Optionally, in the plugin processing device provided in the embodiments of the present application, the device further includes: a first construction unit, configured to construct a functional plugin based on the open service gateway architecture specification to obtain a third functional plugin before determining the first functional plugin to be loaded according to the functional requirements of the target object; a first acquisition unit, configured to acquire the dependency declaration and function license information corresponding to the third functional plugin; a signature unit, configured to perform digital signature on the third functional plugin to obtain digital signature information; a packaging unit, configured to package the third functional plugin, the dependency declaration, the function license information, and the digital signature information to obtain a file package in a preset format; an upload unit, configured to upload the file package in the preset format to the target plugin repository system.

[0167] Optionally, in the plug-in processing device provided in the embodiments of the present application, the inspection unit includes: a third inspection subunit, configured to inspect the digital signature information corresponding to the first functional plug-in to obtain a third inspection sub-result; a fourth inspection subunit, configured to perform a legality inspection on the function license information corresponding to the first functional plug-in to obtain a fourth inspection sub-result; and a second determination subunit, configured to obtain an inspection result based on the third inspection sub-result and the fourth inspection sub-result.

[0168] Optionally, in the plug-in processing device provided in the embodiments of the present application, the first loading unit includes: a first obtaining subunit, configured to obtain a dependency statement corresponding to the first functional plug-in; a third determination subunit, configured to determine a dependency tree corresponding to the first functional plug-in according to the dependency statement, where the dependency tree is composed of functional plug-ins on which the first functional plug-in depends; and a second loading subunit, configured to load the first functional plug-in into the target plug-in platform according to the dependency tree.

[0169] Optionally, in the plug-in processing device provided in the embodiments of the present application, the third determination subunit includes: a first determination module, configured to determine a fourth functional plug-in on which the first functional plug-in depends according to the dependency statement; a judgment module, configured to judge whether the fourth functional plug-in has a dependent functional plug-in according to the dependency statement of the fourth functional plug-in; and an execution module, configured to, if the fourth functional plug-in has a dependent functional plug-in, repeatedly execute the step of determining a fifth functional plug-in on which the fourth functional plug-in depends according to the dependency statement of the fourth functional plug-in until the currently determined functional plug-in according to the dependency statement has no dependent functional plug-in, and obtain a dependency tree based on the functional plug-ins determined according to the dependency statement.

[0170] Optionally, in the plug-in processing device provided in the embodiments of the present application, the second loading subunit includes: a second determination module, configured to determine the loading order of the first functional plug-in and the functional plug-ins on which the first functional plug-in depends according to the dependency tree; and a loading module, configured to load the first functional plug-in and the first functional plug-in into the target plug-in platform according to the loading order.

[0171] Optionally, in the plug-in processing device provided in the embodiments of the present application, the device further includes: a seventh receiving unit, configured to receive an access instruction for the target object to access the sixth functional plug-in through the target plug-in platform after loading the first functional plug-in into the target plug-in platform; a judgment unit, configured to judge whether the target object has the permission to access the functional interface corresponding to the access instruction according to the identity information of the target object; and a first pushing unit, configured to push the functional interface corresponding to the access instruction to the target object if the target object has the permission to access the functional interface corresponding to the access instruction.

[0172] Optionally, in the plug-in processing device provided in the embodiments of the present application, the determination unit includes: a second acquisition subunit, configured to acquire function license information corresponding to a sixth function plug-in; a determination subunit, configured to determine whether a target object has the permission to access the function interface corresponding to the access instruction according to the identity information and the function license information.

[0173] Optionally, in the plug-in processing device provided in the embodiments of the present application, the device further includes: a second determination unit, configured to determine a plurality of function plug-ins matching the attribute information based on target parameters after uploading a file package in a preset format to a target plug-in repository system, where the attribute information is at least one of the following: identity information of a target object, a server machine code corresponding to the target object, and function license information of the function plug-in; a seventh display unit, configured to display the plurality of function plug-ins matching the attribute information to the target object through the target plug-in repository system.

[0174] Optionally, in the plug-in processing device provided in the embodiments of the present application, the device further includes: a third determination unit, configured to determine a seventh function plug-in to be recommended based on the identity information of the target object after uploading a file package in a preset format to a target plug-in repository system; an eighth display unit, configured to display the seventh function plug-in to the target object through the target plug-in repository system.

[0175] Optionally, in the plug-in processing device provided in the embodiments of the present application, the device further includes: a second construction unit, configured to construct an eighth function plug-in based on the Open Service Gateway Initiative (OSGi) specification according to the personalized requirements of the target object after uploading a file package in a preset format to a target plug-in repository system; a second push unit, configured to push the eighth function plug-in to a target interface corresponding to the target object in a target plug-in platform through the target plug-in repository system.

[0176] Optionally, in the plug-in processing device provided in the embodiments of the present application, the plug-ins in the target plug-in platform communicate through a plug-in communication bus, where the plug-in communication bus is designed based on an event-driven model.

[0177] For the description of the features in the corresponding embodiments of the plug-in processing device, reference may be made to the relevant descriptions in the corresponding embodiments of the plug-in processing method, which will not be elaborated herein one by one.

[0178] The embodiments of the present application further provide an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above embodiments of the plug-in processing method.

[0179] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. Wherein, the computer program is configured to execute the steps in any of the above-described embodiments of the plug-in processing method when running.

[0180] In an exemplary embodiment, the above computer-readable storage medium may include, but is not limited to: various media such as USB flash drives, read-only memories (ROM for short), random access memories (RAM for short), external hard drives, magnetic disks, or optical discs that can store computer programs.

[0181] An embodiment of the present application also provides a computer program product. The above computer program product includes a computer program, and when the computer program is executed by a processor, it implements the steps in any of the above-described embodiments of the plug-in processing method.

[0182] An embodiment of the present application also provides another computer program product, including a non-volatile computer-readable storage medium. The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the steps in any of the above-described embodiments of the plug-in processing method.

[0183] Those skilled in the art can further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed in this article can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0184] The above has introduced in detail a plug-in processing method provided by the present application. Specific examples are used in this article to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application. It should be noted that for those of ordinary skill in the art in the technical field, without departing from the principle of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

Claims

1. A plug-in processing method, characterized in that, Including: Determine a first functional plug-in to be loaded according to the functional requirements of the target object; Obtain the first functional plug-in from the target plug-in repository system through the target plug-in platform; Inspect the first functional plug-in to obtain an inspection result; When the inspection result indicates that the inspection is passed, load the first functional plug-in to the target plug-in platform to provide services for the target object through the first functional plug-in, where the target plug-in platform is a data center management platform.

2. The plug-in processing method according to claim 1, wherein After loading the first functional plug-in to the target plug-in platform, the method further includes: Receive a first operation instruction of the target object through the target plug-in platform; Based on the first operation instruction, display an update setting window to the target object; Receive, through the update setting window, an update policy of the target object for updating the plug-ins in the target plug-in platform.

3. The plug-in processing method according to claim 2, wherein After receiving, through the update setting window, an update policy of the target object for updating the plug-ins in the target plug-in platform, the method further includes: If the update policy is a first update policy, detect whether there is a new version of the plug-ins in the target plug-in platform based on a preset time period through the target plug-in platform, and display the detection result to the target object; If the update policy is a second update policy, when receiving a second operation instruction of the target object, detect whether there is a new version of the plug-ins in the target plug-in platform, and display the detection result to the target object.

4. The plug-in processing method according to claim 1, wherein After loading the first functional plug-in to the target plug-in platform, the method further includes: Receive a third operation instruction of the target object through the target plug-in platform; Based on the third operation instruction, display an uninstall setting window to the target object; Receive, through the uninstall setting window, a selection operation of the target object on the plug-ins in the target plug-in platform to determine the plug-ins to be uninstalled.

5. The plug-in processing method according to claim 4, wherein After determining the plug-ins to be uninstalled, the method further includes: Receive a fourth operation instruction of the target object through the target plug-in platform; Based on the fourth operation instruction, display a data backup window to the target object to prompt the target object whether to perform a data backup operation.

6. The plug-in processing method according to claim 1, wherein Loading the first functional plug-in to the target plug-in platform includes: Load the backend module corresponding to the first functional plug-in into the plug-in container of the target plug-in platform, where the plug-in container is constructed based on the open service gateway architecture; Inject the frontend module corresponding to the first functional plug-in into the document object model node of the target plug-in platform to implement the display of the frontend interface corresponding to the first functional plug-in to the target object.

7. The plug-in processing method according to claim 1, wherein After loading the first functional plug-in to the target plug-in platform, the method further includes: Receive a fifth operation instruction of the target object on a second functional plug-in through the target plug-in platform; Based on the fifth operation instruction, display the function interface corresponding to the second function plugin to the target object, so as to provide services for the target object through the second function plugin.

8. The plug-in processing method according to claim 3, characterized in that After displaying the detection result to the target object, the method further includes: If the detection result indicates the existence of a new version of the plugin, load the new version of the plugin into the target plugin platform; In the case of successful loading, trigger a target message to the target object through the target plugin platform, where the target message is used to instruct the target object to restart the target plugin platform so that the new version of the plugin becomes effective.

9. The plug-in processing method according to claim 1, characterized in that Inspect the first function plugin, and the obtained inspection result includes: Inspect the digital signature information corresponding to the first function plugin to obtain a first inspection sub-result; Inspect the checksum corresponding to the first function plugin to obtain a second inspection sub-result; Based on the first inspection sub-result and the first inspection sub-result, obtain the inspection result.

10. The plug-in processing method according to claim 3, wherein The target plugin repository system is at least one of the following: a local plugin repository system, a remote plugin repository system, and an Internet plugin repository system.

11. The plug-in processing method according to claim 3, wherein After displaying the detection result to the target object, the method further includes: If the detection result indicates the existence of a new version of the plugin, load the new version of the plugin into the target plugin platform through a hot update mechanism to implement the update operation of the old version of the plugin.

12. The plug-in processing method according to claim 1, characterized in that, Before determining the first function plugin to be loaded according to the functional requirements of the target object, the method further includes: Construct a function plugin based on the open service gateway architecture specification to obtain a third function plugin; Obtain the dependency declaration and function license information corresponding to the third function plugin; Digitally sign the third function plugin to obtain digital signature information; Package the third function plugin, the dependency declaration, the function license information, and the digital signature information to obtain a file package in a preset format; Upload the file package in the preset format to the target plugin repository system.

13. The plug-in processing method according to claim 12, wherein Inspect the first function plugin, and the obtained inspection result includes: Inspect the digital signature information corresponding to the first function plugin to obtain a third inspection sub-result; Conduct a legality inspection on the function license information corresponding to the first function plugin to obtain a fourth inspection sub-result; Based on the third inspection sub-result and the fourth inspection sub-result, obtain the inspection result.

14. The plug-in processing method according to claim 12, wherein Loading the first function plugin into the target plugin platform includes: Obtain the dependency declaration corresponding to the first function plugin; According to the dependency declaration, determine the dependency tree corresponding to the first function plugin, where the dependency tree is composed of the function plugins on which the first function plugin depends; According to the dependency tree, load the first function plugin into the target plugin platform.

15. The plug-in processing method according to claim 14, wherein Determining the dependency tree corresponding to the first function plugin according to the dependency declaration includes: According to the dependency declaration, determine the fourth function plugin on which the first function plugin depends; According to the dependency declaration of the fourth function plugin, determine whether the fourth function plugin has a dependent function plugin; If there are dependent functional plugins for the fourth functional plugin, repeat the step of determining the fifth functional plugin on which the fourth functional plugin depends according to the dependency declaration of the fourth functional plugin until the currently determined functional plugin according to the dependency declaration has no dependent functional plugins, and obtain the dependency tree based on the functional plugins determined according to the dependency declaration.

16. The plug-in processing method according to claim 14, characterized in that Loading the first functional plugin into the target plug-in platform according to the dependency tree includes: Determining the loading order of the first functional plugin and the functional plugins on which the first functional plugin depends according to the dependency tree; Loading the first functional plugin and the functional plugins on which the first functional plugin depends into the target plug-in platform according to the loading order.

17. The plug-in processing method according to claim 1, wherein After loading the first functional plugin into the target plug-in platform, the method further includes: Receiving, by the target plug-in platform, an access instruction for the target object to access a sixth functional plugin; Judging whether the target object has the permission to access the functional interface corresponding to the access instruction according to the identity information corresponding to the target object; If the target object has the permission to access the functional interface corresponding to the access instruction, pushing the functional interface corresponding to the access instruction to the target object.

18. The plug-in processing method according to claim 17, wherein Judging whether the target object has the permission to access the functional interface corresponding to the access instruction according to the identity information corresponding to the target object includes: Obtaining the functional permission information corresponding to the sixth functional plugin; Judging whether the target object has the permission to access the functional interface corresponding to the access instruction according to the identity information and the functional permission information.

19. The plug-in processing method according to claim 1, wherein The method further includes: Determining a plurality of functional plugins that match the attribute information based on target parameters, where the attribute information is at least one of the following: the identity information of the target object, the server machine code corresponding to the target object, and the functional permission information of the functional plugin; Displaying the plurality of functional plugins that match the attribute information to the target object through the target plug-in repository system.

20. The plug-in processing method according to claim 12, wherein After uploading the file package in the preset format to the target plug-in repository system, the method further includes: Determining a seventh functional plugin to be recommended based on the identity information of the target object; Displaying the seventh functional plugin to the target object through the target plug-in repository system.

21. The plug-in processing method according to claim 1, characterized in that, The method further includes: Constructing an eighth functional plugin based on the open service gateway architecture specification according to the personalized requirements of the target object; Pushing the eighth functional plugin to the target interface corresponding to the target object in the target plug-in platform through the target plug-in repository system.

22. The plug-in processing method according to claim 1, wherein The plugins in the target plug-in platform communicate with each other through a plug-in communication bus, where the plug-in communication bus is designed based on an event-driven model.

23. A plugin-based platform, characterized in that, The target plug-in platform is used to execute the steps of the plug-in processing method according to any one of claims 1 to 22.

24. A plug-in processing device, characterized in that Including: A first determination unit, configured to determine a first functional plugin to be loaded according to the functional requirements of the target object; A first acquisition unit, configured to acquire the first functional plugin from the target plug-in repository system through the target plug-in platform; An inspection unit for inspecting the first functional plug-in to obtain an inspection result; A first loading unit for loading the first functional plug-in to a target plug-in platform to provide services for the target object through the first functional plug-in when the inspection result indicates a passing inspection, wherein the target plug-in platform is a data center management platform.

25. An electronic device, characterized in that, Comprising: A memory for storing a computer program; A processor for implementing the steps of the plug-in processing method according to any one of claims 1 to 22 when executing the computer program.

26. A non-volatile computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, wherein the computer program implements the steps of the plug-in processing method according to any one of claims 1 to 22 when executed by a processor.

27. A computer program product comprising a computer program, characterized in that, The computer program implements the steps of the plug-in processing method according to any one of claims 1 to 22 when executed by a processor.

Images