Plugin Generation Method, Device, Equipment and Storage Medium

Abstract

An embodiment of the present disclosure provides a plug-in generation method, apparatus, device, and storage medium. The method includes: determining a program configuration file of the plug-in to be generated, then based on the program configuration file, determining first protocol mapping information between the system platform corresponding to the plug-in to be generated and the low-code platform, and then based on the first protocol mapping information, mapping the program configuration file to a corresponding program configuration parsing file, and finally based on the program configuration parsing file, performing an instantiation process on the plug-in to be generated to obtain a plug-in program corresponding to the plug-in to be generated. The technical solution of the embodiment of the present disclosure solves the problem in the related art that plug-ins developed based on a low-code platform are prone to compatibility issues due to changes in communication protocols, and significantly improves the compatibility, customizability, scalability, and reliability of the generated plug-in programs.

Description

Technical Field

[0001] The present disclosure relates to the technical field of robot program development, and in particular, to a method, device, equipment, and storage medium for generating plugins. Background Art

[0002] In the field of industrial robot development, it has become a common development mode to develop programs and plugins for robots through program development platforms such as low-code development platforms and import them into the robots for application.

[0003] However, in the above mode, when the system communication protocol in the robot system platform, the communication protocol of the low-code development platform, or the communication protocol of a third-party service relied on by the low-code development platform changes, compatibility problems will occur in the developed programs and plugins, resulting in the inability to be normally applied in the robot. Summary of the Invention

[0004] Embodiments of the present disclosure provide a method, device, equipment, and storage medium for generating plugins to solve the problem in related technologies that plugins developed based on a low-code platform are prone to compatibility issues due to changes in communication protocols.

[0005] In a first aspect, an embodiment of the present disclosure provides a method for generating a plugin, which is applied to a low-code platform. The method for generating a plugin includes:

[0006] Determine a program configuration file of the plugin to be generated, where the program configuration file is used to generate an instantiated plugin to be generated, and the program configuration file is stored in the low-code platform;

[0007] Based on the program configuration file, determine first protocol mapping information between the system platform corresponding to the plugin to be generated and the low-code platform, where the first protocol mapping information is stored in a mapping configuration file; the mapping configuration file is used to store the communication protocol of the low-code platform, the communication protocols of devices other than the low-code platform, and the protocol mapping information between devices other than the low-code platform and the low-code platform; the mapping configuration file is further used to update the protocol mapping information based on received version update data of the communication protocol; the protocol mapping information is used to represent the configuration information required for mapping between the communication protocol of the low-code platform and the communication protocols of devices other than the low-code platform, and the protocol mapping information includes the first protocol mapping information;

[0008] Based on the first protocol mapping information, map the program configuration file to a corresponding program configuration parsing file, where the program configuration parsing file is used to represent the corresponding file version of the program configuration file that supports running in the system platform corresponding to the plugin to be generated;

[0009] Based on the program configuration parsing file, instantiate the plugin to be generated to obtain the plugin program corresponding to the plugin to be generated, where the plugin program is applied to the system platform.

[0010] Optionally, based on the program configuration file, determine the first protocol mapping information between the system platform corresponding to the plugin to be generated and the low-code platform from the preset mapping configuration file, including: based on the program configuration file, determine the first communication protocol supported by the system platform corresponding to the plugin to be generated; determine the second communication protocol supported by the low-code platform; retrieve the first protocol mapping information from the mapping configuration file based on the identification codes of the first communication protocol and the second communication protocol.

[0011] Optionally, before determining the program configuration file of the plugin to be generated, it further includes: based on the program configuration file modification operation of the plugin to be generated, determine the modified program configuration file.

[0012] Optionally, before determining the program configuration file of the plugin to be generated, it further includes: obtain the configuration modification information corresponding to the plugin to be generated, and the configuration modification information includes the corresponding first communication sender; based on the third communication protocol supported by the first communication sender, determine the configuration modification data included in the configuration modification information, where the configuration modification data is used to represent the data for modifying the program configuration file of the plugin to be generated included in the configuration modification information; based on the third communication protocol and the second communication protocol supported by the low-code platform, determine the second protocol mapping information between the first communication sender and the low-code platform from the mapping configuration file; based on the second protocol mapping information, map the configuration modification data to platform data, where the platform data is used to represent the data recognized and processed by the low-code platform; based on the platform data, modify the program configuration file to obtain the modified program configuration file.

[0013] Optionally, the second protocol mapping information includes communication protocol mapping information and plugin data mapping information; the communication protocol mapping information includes the corresponding relationship between the elements in the configuration modification data and the elements in the configuration file of the plugin to be generated; the plugin data mapping information includes the attribute information of the elements in the configuration file of the plugin to be generated.

[0014] Optionally, the platform data includes element logical data and element attribute data; mapping the configuration modification data to platform data based on the second protocol mapping information includes: based on the communication protocol mapping information in the second protocol mapping information, determine the element logical data corresponding to the configuration modification data, where the element logical data is used to represent the logical data of the element corresponding to the plugin to be generated corresponding to the configuration modification data; based on the plugin data mapping information in the second protocol mapping information, determine the element attribute data corresponding to the configuration modification data, where the element attribute data is used to represent the attribute data of the element corresponding to the plugin to be generated corresponding to the configuration modification data.

[0015] Optionally, after parsing the program configuration file and instantiating the to-be-generated plug-in to obtain the plug-in program corresponding to the to-be-generated plug-in, the following steps are further included: in response to receiving the first service request information sent by the plug-in program, determining the second communication sending end corresponding to the service request information; based on the first communication protocol supported by the system platform corresponding to the plug-in program and the first protocol mapping information, determining the service request data included in the service request information, where the service request data is used to represent the data included in the service request information that supports reading in the low-code platform; determining the fourth communication protocol supported by the second communication sending end; determining the third protocol mapping information between the second communication sending end and the low-code platform; based on the third protocol mapping information, converting the service request data into the second service request information supported by the second communication sending platform; and sending the second service request information to the second communication sending end.

[0016] Optionally, after sending the second service request information to the second communication sending end, the following steps are further included: in response to receiving the request result information returned by the second communication sending end, based on the fourth communication protocol, determining the request result data corresponding to the request result information, where the request result data is used to represent the data included in the request result information that supports reading in the second communication sending end; based on the third protocol mapping information, mapping the request result data to the corresponding platform result data, where the platform result data is used to represent the data corresponding to the request result data that supports reading in the low-code platform; based on the first protocol mapping information, mapping the result platform data to the corresponding plug-in result data, where the platform result data is used to represent the data corresponding to the request result data that supports reading in the system platform where the plug-in program is located; and returning the plug-in result data to the plug-in program.

[0017] Optionally, the program configuration file is developed through the low-code platform or obtained by referring to the dependency link provided by an external server.

[0018] Optionally, the program configuration file further includes a corresponding running environment file, and the running environment file is developed through the low-code platform.

[0019] In a second aspect, an embodiment of the present disclosure provides a plug-in generation device applied to a low-code platform. The plug-in generation device includes:

[0020] A determination module, configured to determine the program configuration file of the to-be-generated plug-in, where the program configuration file is used to generate an instantiated to-be-generated plug-in, and the program configuration file is stored in the low-code platform;

[0021] A search module, which is used to determine the first protocol mapping information between the system platform corresponding to the plugin to be generated and the low-code platform based on the program configuration file; wherein, the first protocol mapping information is stored in the mapping configuration file; the mapping configuration file is used to store the communication protocols of the low-code platform, the communication protocols of devices other than the low-code platform, and the protocol mapping information between devices other than the low-code platform and the low-code platform; the mapping configuration file is further used to update the protocol mapping information based on the received version update data of the communication protocol; the protocol mapping information is used to represent the configuration information required for mapping between the communication protocol of the low-code platform and the communication protocol of devices other than the low-code platform, and the protocol mapping information includes the first protocol mapping information.

[0022] A parsing module, which is used to map the program configuration file to a corresponding program configuration parsing file based on the first protocol mapping information, wherein the program configuration parsing file is used to represent the corresponding file version of the program configuration file that supports running in the system platform corresponding to the plugin to be generated.

[0023] A processing module, which is used to instantiate the plugin to be generated based on the program configuration parsing file to obtain a plugin program corresponding to the plugin to be generated, wherein the plugin program is applied to the system platform.

[0024] Optionally, the search module is specifically used to determine the first communication protocol supported by the system platform corresponding to the plugin to be generated based on the program configuration file; determine the second communication protocol supported by the low-code platform; and retrieve the first protocol mapping information from the mapping configuration file based on the identification codes of the first communication protocol and the second communication protocol.

[0025] Optionally, the determination module is further used to determine the modified program configuration file based on the program configuration file modification operation of the plugin to be generated before determining the program configuration file of the plugin to be generated.

[0026] Optionally, the determination module is further used to, before determining the program configuration file of the plugin to be generated, obtain the configuration modification information corresponding to the plugin to be generated, and the configuration modification information includes a corresponding first communication sender; determine the configuration modification data included in the configuration modification information based on the third communication protocol supported by the first communication sender, wherein the configuration modification data is used to represent the data for modifying the program configuration file of the plugin to be generated included in the configuration modification information; determine the second protocol mapping information between the first communication sender and the low-code platform from the mapping configuration file based on the third communication protocol and the second communication protocol supported by the low-code platform; map the configuration modification data to platform data based on the second protocol mapping information, wherein the platform data is used to represent the data that the low-code platform supports for identification and processing; and modify the program configuration file based on the platform data to obtain the modified program configuration file.

[0027] Optionally, the determination module specifically includes that the second protocol mapping information includes communication protocol mapping information and plug-in data mapping information; the communication protocol mapping information contains the correspondence between the elements in the configuration modification data and the elements in the configuration file of the plug-in to be generated; the plug-in data mapping information contains the attribute information of the elements in the configuration file of the plug-in to be generated.

[0028] Optionally, the determination module is specifically configured to, if the platform data includes element logical data and element attribute data, based on the communication protocol mapping information in the second protocol mapping information, determine the element logical data corresponding to the configuration modification data, where the element logical data is used to represent the logical data corresponding to the elements in the plug-in to be generated corresponding to the configuration modification data; based on the plug-in data mapping information in the second protocol mapping information, determine the element attribute data corresponding to the configuration modification data, where the element attribute data is used to represent the attribute data of the elements in the plug-in to be generated corresponding to the configuration modification data.

[0029] Optionally, the processing module is further configured to, based on the program configuration parsing file, instantiate the plug-in to be generated, and after obtaining the plug-in program corresponding to the plug-in to be generated, in response to receiving the first service request information sent by the plug-in program, determine the second communication sending end corresponding to the service request information; based on the first communication protocol supported by the system platform corresponding to the plug-in program and the first protocol mapping information, determine the service request data included in the service request information, where the service request data is used to represent the data included in the service request information supported to be read in the low-code platform; determine the fourth communication protocol supported by the second communication sending end; determine the third protocol mapping information between the second communication sending end and the low-code platform; based on the third protocol mapping information, convert the service request data into the second service request information supported by the second communication sending platform; and send the second service request information to the second communication sending end.

[0030] Optionally, after the processing module sends the second service request information to the second communication sending end, it further includes: in response to receiving the request result information returned by the second communication sending end, based on the fourth communication protocol, determine the request result data corresponding to the request result information, where the request result data is used to represent the data included in the request result information supported to be read in the second communication sending end; based on the third protocol mapping information, map the request result data to the corresponding platform result data, where the platform result data is used to represent the data supported to be read in the low-code platform corresponding to the request result data; based on the first protocol mapping information, map the result platform data to the corresponding plug-in result data, where the platform result data is used to represent the data supported to be read in the system platform where the plug-in program is located corresponding to the request result data; and return the plug-in result data to the plug-in program.

[0031] Optionally, the determination module specifically includes that the program configuration file is developed through a low-code platform, or the program configuration file is obtained by referring to a dependency link provided by an external server.

[0032] Optionally, the determination module specifically includes that the program configuration file further includes a corresponding running environment file, and the running environment file is developed based on a low-code platform.

[0033] In a third aspect, an embodiment of the present disclosure further provides a control device, and the control device includes:

[0034] At least one processor;

[0035] And a memory communicatively connected to at least one processor;

[0036] Wherein, the memory stores instructions executable by at least one processor, and the instructions are executed by at least one processor to enable the control device to execute the plug-in generation method according to the first aspect of the present disclosure.

[0037] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, and computer-executable instructions are stored in the computer-readable storage medium. When the computer-executable instructions are executed by a processor, they are used to implement the plug-in generation method according to the first aspect of the present disclosure.

[0038] In a fifth aspect, an embodiment of the present disclosure further provides a computer program product, and the computer program product includes computer-executable instructions. When the computer-executable instructions are executed by a processor, they are used to implement the plug-in generation method according to the first aspect of the present disclosure.

[0039] The plug-in generation method, device, device, and storage medium provided by the embodiments of the present disclosure determine the program configuration file of the plug-in to be generated, then determine the first protocol mapping information between the system platform corresponding to the plug-in to be generated and the low-code platform based on the program configuration file, and then map the program configuration file to the corresponding program configuration parsing file based on the first protocol mapping information. Finally, based on the program configuration parsing file, an instantiation process is performed on the plug-in to be generated to obtain the plug-in program corresponding to the plug-in to be generated. Thus, it is possible to generate the plug-in to be generated corresponding to the program configuration file without modifying the code in the program configuration file, and no matter whether the communication protocol version of the system platform changes or the communication protocol version of the low-code platform changes, the first protocol mapping information with corresponding configurations can ensure the generation of a plug-in program that can run on the system platform, thereby significantly reducing or avoiding the increased development workload due to protocol changes and customization requirements, saving human resources and testing resource costs, and ensuring the scalability and compatibility of the plug-in to a certain extent. Description of the Drawings

[0040] The accompanying drawings herein are incorporated into and constitute a part of this specification, showing embodiments consistent with the present application, and are used in conjunction with the specification to explain the principles of the present application.

[0041] Figure 1 A scenario diagram for an application of the plug-in generation method provided by an embodiment of the present disclosure;

[0042] Figure 2 A flowchart of the plug-in generation method provided by an embodiment of the present disclosure;

[0043] Figure 3 A flowchart of the plug-in generation method provided by another embodiment of the present disclosure;

[0044] Figure 4 A flowchart of the plug-in generation method provided by another embodiment of the present disclosure;

[0045] Figure 5 A schematic structural diagram of the plug-in generation device provided by another embodiment of the present disclosure;

[0046] Figure 6 A schematic structural diagram of the control device provided by an embodiment of the present disclosure.

[0047] Through the above accompanying drawings, specific embodiments of the present application have been shown, and there will be more detailed descriptions hereinafter. These accompanying drawings and textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed Embodiments

[0048] Exemplary embodiments will be described in detail herein, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0049] The technical solutions of the present disclosure and how the technical solutions of the present disclosure solve the above technical problems will be described in detail below with specific embodiments. These several specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present disclosure will be described below with reference to the accompanying drawings.

[0050] The following are the concept explanations involved in the embodiments of the present disclosure:

[0051] Low-code platform: A program development platform that can quickly generate application programs without coding or with a small amount of code. In the embodiments of the present disclosure, it is used to represent a program development platform for developing the required plug-in programs for robots through a visual interface.

[0052] Communication protocol: In the embodiments of the present disclosure, it is used to represent the rules that need to be followed when performing data communication (such as sending data or service call requests) in a certain platform, including the header information of fixed data packets, data format requirements (such as data for performing a certain function must be in a specific format, such as json files, xml files, etc.).

[0053] In the field of industrial robot development, robots rely on pre-developed programs, plug-ins, etc. to perform preset actions and functions. Therefore, program development is the core of the robot development field. Developing the programs and plug-ins used by robots through program development platforms such as low-code development platforms and importing them into the robots for application is a common development mode.

[0054] However, in the above mode, program development platforms such as robot platforms and low-code platforms each have their own supported communication protocols. At the same time, there may also be communication protocols for third-party services on which the low-code development platform or program depends. When any communication protocol changes, it may result in the inability to read in the low-code platform, or the inability to be normally applied in the robot, or the inability to communicate with the third-party service, leading to compatibility problems with the developed programs and plug-ins.

[0055] To solve this problem, the embodiments of the present disclosure provide a plug-in generation method. By pre-configuring the mapping configuration files and communication protocols between different platforms, the program configuration file of the plug-in to be generated is mapped to a program configuration parsing file supported by the robot system platform, and then the program configuration parsing file is instantiated, so that the obtained plug-in program can always meet the communication protocol requirements of the corresponding platform, thereby fully ensuring the scalability and compatibility of the generated plug-in program.

[0056] The application scenario of the embodiments of the present disclosure is explained below:

[0057] Figure 1 This is an application scenario diagram of the plug-in generation method provided by the embodiments of the present disclosure. As Figure 1 shown, during the plug-in development process, the low-code platform 101 in the development end 100 will instantiate the developed program configuration file 102 to obtain the corresponding plug-in program 103, and publish the plug-in program 104 to the corresponding robot system 110 so that the robot can run the plug-in program 104 to complete the corresponding functions or operations.

[0058] It should be noted that Figure 1In the described scenario, only one example of the development end, low-code platform, program configuration file, plug-in program, and robot system is used for illustration, but the present disclosure is not limited thereto. That is to say, the number of the development end, low-code platform, program configuration file, plug-in program, and robot system can be arbitrary.

[0059] The following details the plug-in generation method provided by the present disclosure through specific embodiments.

[0060] Figure 2 It is a flowchart of the plug-in generation method provided by an embodiment of the present disclosure. As Figure 2 shown, the plug-in generation method provided by this embodiment includes the following steps:

[0061] Step S201, determine the program configuration file of the plug-in to be generated.

[0062] Among them, the program configuration file is used to generate the instantiated plug-in to be generated, and the program configuration file is stored in the low-code platform.

[0063] Specifically, when the plug-in to be generated is saved in the low-code platform, it exists in the form of a program configuration file. By instantiating the plug-in to be generated, the corresponding plug-in program can be obtained, and the plug-in program is imported into the robot system, and then it can be applied in the robot system.

[0064] Before instantiation, the low-code platform can modify the program configuration file to perform operations such as extension, customization, and maintenance on the plug-in to be generated.

[0065] Therefore, the program configuration file will be saved in a state that supports the communication protocol in the low-code platform so that it can be edited on the low-code platform.

[0066] In order for the generated plug-in program to run normally in the robot system, it is necessary to make the code file of the instantiated plug-in program support the communication protocol corresponding to the robot's corresponding system platform (that is, the system platform corresponding to the plug-in to be generated). Therefore, before instantiation, the corresponding program configuration file needs to be converted into a format that supports the communication protocol corresponding to the robot's corresponding system platform, that is, converted into a program configuration parsing file.

[0067] Step S202, based on the program configuration file, determine the first protocol mapping information between the system platform corresponding to the plug-in to be generated and the low-code platform.

[0068] Among them, the first protocol mapping information is stored in a mapping configuration file; the mapping configuration file is used to store the communication protocols of the low-code platform, the communication protocols of devices outside the low-code platform, and the protocol mapping information between devices outside the low-code platform and the low-code platform; the mapping configuration file is also used to update the protocol mapping information based on the received communication protocol version update data; the protocol mapping information is used to represent the configuration information required for mapping between the communication protocol of the low-code platform and the communication protocol of devices outside the low-code platform, and the protocol mapping information includes the first protocol mapping information.

[0069] Specifically, to convert the program configuration file, it is necessary to determine the first protocol mapping information required for the conversion.

[0070] The first protocol mapping information contains the rules to be followed for protocol mapping between the low-code platform and the system platform corresponding to the plugin to be generated, including the correspondence between the data types in the low-code platform and the corresponding data types in the system platform corresponding to the plugin to be generated, and the necessary information required when mapping the data formats supported by the communication protocol in the low-code platform to the data formats supported by the communication protocol in the system platform corresponding to the plugin to be generated (such as adding function libraries to be referenced, etc.).

[0071] In the low-code platform, the mapping configuration files between the low-code platform and each other (platforms that will communicate with the low-code platform) can be stored in the form of a database. Therefore, it is necessary to determine the corresponding protocol mapping information (in this step, that is, to determine the first protocol mapping information) according to the identification information of the system platform corresponding to the plugin to be generated recorded in the program configuration file or the identification information of the communication protocol of the system platform corresponding to the plugin to be generated (such as the key value of the communication protocol, the key value of the corresponding system platform, or the version number of the system platform, etc.).

[0072] Since the first protocol mapping information involves the protocol mapping between the system platform corresponding to the plugin to be generated and the low-code platform, when specifically determining the first protocol mapping information, it is also necessary to consider the communication protocol corresponding to the low-code platform.

[0073] The identification information related to the communication protocol corresponding to the low-code platform can be directly stored in the program configuration file (to ensure that the program configuration file can be correctly read and edited in the low-code platform), or obtained from the low-code platform when querying the first protocol mapping information, and there is no restriction here.

[0074] According to the obtained identification information of the communication protocol corresponding to the low-code platform and the identification information of the communication protocol of the system platform corresponding to the plugin to be generated, the corresponding first protocol mapping information can be queried from the database.

[0075] Since the communication protocols in different platforms may be updated or changed over time, the mapping configuration file is configured to automatically receive the version update data of each communication protocol through an interface, and adaptively modify the corresponding parameters and fields in the protocol mapping information between the corresponding communication protocols according to these version update data, so as to achieve the adaptive update of the protocol mapping information, and ensure that the program configuration parsing file mapped from the first protocol mapping information can adaptively run in the system platform after the communication protocol changes.

[0076] Step S203: Based on the first protocol mapping information, map the program configuration file to the corresponding program configuration parsing file.

[0077] Among them, the program configuration parsing file is used to represent the corresponding file version of the program configuration file that supports running in the system platform corresponding to the plugin to be generated.

[0078] Specifically, after obtaining the first protocol mapping information, the program configuration file can be mapped (that is, parsed) to the corresponding program configuration parsing file based on the rules recorded in the first protocol mapping information.

[0079] Step S204: Based on the program configuration parsing file, perform instantiation processing on the plugin to be generated to obtain the plugin program corresponding to the plugin to be generated.

[0080] Among them, the plugin program is applied to the system platform.

[0081] Specifically, by instantiating the program configuration parsing file, a plugin program that supports running in the robot system (i.e., the system platform) can be obtained.

[0082] At this time, a corresponding running environment library can also be configured in the low-code platform to simulate the running environment in the robot system, and the plugin program is imported into the simulated running environment to run, so as to check whether the generated plugin program meets the requirements.

[0083] Furthermore, the plugin program that supports the instantiation of the program configuration parsing file can be a part of the program running in the robot system or a separate application program. Thus, it is convenient to edit and partially instantiate some plugins and controls inside the application program to improve the degree of customization and debugging efficiency.

[0084] The plug-in generation method provided by the embodiments of the present disclosure determines the program configuration file of the plug-in to be generated, and then based on the program configuration file, determines the first protocol mapping information between the system platform and the low-code platform corresponding to the plug-in to be generated from the preset mapping configuration file. Then, based on the first protocol mapping information, the program configuration file is parsed into a corresponding program configuration parsing file. Finally, based on the program configuration parsing file, the plug-in to be generated is instantiated to obtain the plug-in program corresponding to the plug-in to be generated. Thus, it is possible to generate the plug-in to be generated corresponding to the program configuration file without modifying the code in the program configuration file, and no matter whether the communication protocol version of the system platform changes or the communication protocol version of the low-code platform changes, the first protocol mapping information with corresponding configurations can ensure that the generated plug-in program can run on the system platform, thereby significantly reducing or avoiding the development workload increased due to protocol changes and customization requirements, saving human resources and test resource costs, and ensuring the scalability and compatibility of the plug-in to a certain extent.

[0085] Figure 3 It is a flowchart of the plug-in generation method provided by an embodiment of the present disclosure. As Figure 3 shown, the plug-in generation method provided in this embodiment includes the following steps:

[0086] Step S301, based on the program configuration file modification operation of the plug-in to be generated, determine the modified program configuration file.

[0087] Specifically, before performing protocol mapping on the program configuration file, it can be directly edited and modified on the low-code platform, and then protocol mapping processing is performed based on the modified program configuration file. Thus, the scalability and customizability of the plug-in to be generated are ensured.

[0088] Step S302, obtain the configuration modification information corresponding to the plug-in to be generated.

[0089] Among them, the configuration modification information includes the corresponding first communication sending end.

[0090] Specifically, the modification of the program configuration file can also be made by a third-party platform (or third-party device outside the low-code platform, that is, the first communication sending end). For example, developers can modify and edit some information in the program configuration file on their own computers, and then transmit the edited configuration modification information to the low-code platform. The low-code platform then updates the program configuration file according to the transmitted configuration modification information and continues to perform instantiation processing on the updated program configuration file.

[0091] Thus, the file sent from the first communication sending end is the configuration modification information.

[0092] Step S303: Determine the configuration modification data included in the configuration modification information based on the third communication protocol supported by the first communication sender.

[0093] Among them, the configuration modification data is used to represent the data for modifying the program configuration file of the to-be-generated plugin included in the configuration modification information.

[0094] Specifically, since the configuration modification information is generated and edited based on the third communication protocol supported by the first communication sender, there may be differences between the third communication protocol and the second communication protocol supported by the low-code platform (for example, the second communication protocol is the communication protocol supported by the windows platform, and the third communication protocol is the communication protocol supported by the linux platform). Therefore, it is necessary to process the configuration modification information into a state that can be edited on the low-code platform.

[0095] The configuration modification information is a file generated based on the third communication protocol, which contains specific formats and data packet header information, etc. To extract the content related to the modification of the program configuration file (i.e., the configuration modification data) from it, it is necessary to parse the configuration modification information based on the third communication protocol to obtain the configuration modification data therein (for example, according to the file compression format specified in the third communication protocol, use the corresponding decompression tool to extract the configuration modification data).

[0096] Step S304: Determine the second protocol mapping information between the first communication sender and the low-code platform from the mapping configuration file based on the third communication protocol and the second communication protocol supported by the low-code platform.

[0097] Specifically, to map the configuration modification data into a format supported for editing in the low-code platform, corresponding second protocol mapping information is also required. Therefore, it is necessary to determine the mapping configuration file containing the second protocol mapping information and the corresponding second protocol mapping information from the database of the low-code platform based on the identification information of the third communication protocol and the identification information of the second communication protocol.

[0098] Furthermore, the second protocol mapping information includes communication protocol mapping information and plugin data mapping information;

[0099] The communication protocol mapping information contains the correspondence between the elements in the configuration modification data and the elements in the configuration file of the to-be-generated plugin; the plugin data mapping information contains the attribute information of the elements in the configuration file of the to-be-generated plugin.

[0100] Specifically, the protocol mapping information contains the correspondence between elements between different platforms (i.e., the communication protocol mapping information) and the configuration information required for the execution or implementation of the functions of the corresponding elements (i.e., the plugin data mapping information).

[0101] Exemplarily, the configuration modification data contains the data {"type":0}. The type data is a control attribute of a plug-in program displayed on the low-code platform. Therefore, it is necessary to specify the control to which the type data applies so that the low-code platform can correctly implement the function corresponding to the data. However, in the configuration modification data, there may be a situation where the control corresponding to the type data is not specified, making it impossible for the low-code platform to correctly run the type data. At this time, protocol mapping information is needed to record the data type widetype required to run the type data (such as {"widettype": "lineedit"}. The widetype data is used to indicate that the control corresponding to the type data is lineedit, and lineedit is used to represent an edit box control. That is, the type element in the configuration modification data based on the third communication protocol needs to depend on the widetype element in the program configuration file based on the second communication protocol to execute). The information recording the correspondence between the widetype data and the type data is the communication protocol mapping information.

[0102] In addition to recording the data types on which the data in the configuration modification data depends when running on the low-code platform, the communication protocol mapping information also records the corresponding default assignments of the data types, that is, the plug-in data mapping information. For example, the assignment of lineedit in the statement {"widettype": "lineedit"} corresponding to the widetype element is the default assignment when the type data appears in the configuration modification data and dependencies need to be added, that is, the corresponding plug-in data mapping information.

[0103] Step S305, based on the second protocol mapping information, map the configuration modification data into platform data.

[0104] Among them, the platform data is used to represent the data supported, recognized, and processed by the low-code platform.

[0105] Specifically, after obtaining the second protocol mapping information, the configuration modification data can be mapped into data supported for editing on the low-code platform (that is, platform data).

[0106] Furthermore, the platform data includes element logic data and element attribute data. At this time, the process of parsing the configuration modification data into platform data includes two parts:

[0107] One part is to determine the element logical data corresponding to the configuration modification data based on the communication protocol mapping information in the second protocol mapping information, where the element logical data is used to represent the logical data corresponding to the elements in the to-be-generated plug-in corresponding to the configuration modification data; the other part is to determine the element attribute data corresponding to the configuration modification data based on the plug-in data mapping information in the second protocol mapping information, where the element attribute data is used to represent the attribute data of the elements in the to-be-generated plug-in corresponding to the configuration modification data.

[0108] Specifically, the element logical data is the data type widetype corresponding to the type class data in {"type": 0} in the above example (this data type is used to indicate the control corresponding to the type class data), and the element attribute data is lineedit in {"widettype": "lineedit"} in the above example. Combining these two parts of data and adding them to the configuration modification data (such as {"type": 0; "widettype": "lineedit"}) can enable {"type": 0} in the configuration modification data to run properly in the low-code platform.

[0109] Step S306: Modify the program configuration file based on the platform data to obtain the modified program configuration file.

[0110] Specifically, based on the obtained platform data, modify the corresponding content in the program configuration file to obtain the modified program configuration file (if the corresponding content does not exist in the program configuration file, the platform data can be directly added to the program configuration file. Such operations are existing technologies in program editing, and only examples are given here without specific limitations).

[0111] Steps S302 to S306 are optional steps parallel to step S301. Those skilled in the art can select the corresponding steps for execution according to the actual situation, and no restrictions are imposed here.

[0112] Step S307: Determine the program configuration file of the to-be-generated plug-in.

[0113] Among them, the program configuration file is used to generate the instantiated to-be-generated plug-in, and the program configuration file is stored in the low-code platform.

[0114] Specifically, after modifying the program configuration file, the modified program configuration file can be saved and an instantiation operation can be performed on it.

[0115] Step S308: Based on the program configuration file, determine the first communication protocol supported by the system platform corresponding to the to-be-generated plug-in.

[0116] Specifically, when determining the first protocol mapping information required before instantiation, it is first necessary to determine the first communication protocol corresponding to the system platform to which the program configuration file needs to be applied. The relevant content has been described in the foregoing embodiments and will not be elaborated here.

[0117] Step S309: Determine the second communication protocol supported by the low-code platform.

[0118] Specifically, the method for confirming the second communication protocol has been described in the foregoing embodiments and will not be repeated here.

[0119] Step S310: Based on the identification codes of the first communication protocol and the second communication protocol, retrieve the first protocol mapping information from the mapping configuration file.

[0120] Specifically, the first protocol mapping information can be saved as part of the mapping configuration file in the database of the low-code platform, or can be saved separately in the database of the low-code platform. In the latter case, after determining the identification codes of the first communication protocol and the second communication protocol, the first protocol mapping information in the database can be directly retrieved, without the need to retrieve the first protocol mapping information in the corresponding mapping configuration file after determining the corresponding mapping configuration file.

[0121] Step S311: Based on the first protocol mapping information, map the program configuration file to the corresponding program configuration parsing file.

[0122] Among them, the program configuration parsing file is used to represent the corresponding file version of the program configuration file that supports running in the system platform corresponding to the plugin to be generated.

[0123] Step S312: Based on the program configuration parsing file, perform instantiation processing on the plugin to be generated to obtain the plugin program corresponding to the plugin to be generated.

[0124] Specifically, steps S311 to S312 are the same as the corresponding step contents in the Figure 2 illustrated embodiment and will not be repeated here.

[0125] The plugin generation method provided by the embodiments of the present disclosure can edit the program configuration file on the low-code platform, or obtain configuration modification information from the first communication sender, modify the program configuration file accordingly, and then perform mapping and instantiation based on the modified program configuration file to obtain the urban construction program corresponding to the plugin to be generated. Thus, the program configuration file can be edited in different ways, and instantiation can be performed based on the edited program configuration file, fully ensuring the customizability and scalability of the plugin program, and at the same time ensuring the compatibility of the obtained plugin program.

[0126] Figure 4The flowchart of the plug-in generation method provided by an embodiment of the present disclosure. As Figure 4 shown, the plug-in generation method provided by this embodiment includes the following steps:

[0127] Step S401, determine the program configuration file of the plug-in to be generated.

[0128] Among them, the program configuration file is used to generate the instantiated plug-in to be generated, and the program configuration file is stored in the low-code platform.

[0129] Specifically, the program configuration file not only supports modification, but also supports being directly developed through the low-code platform, or the program configuration file is obtained by referring to the dependency link provided by the external server. By supporting the instantiation of program configuration files obtained from different sources, the customizability and scalability of generating plug-ins based on the low-code platform are maximally supported.

[0130] Furthermore, the program configuration file also includes the corresponding running environment file, and the running environment file is developed based on the low-code platform. Thus, it is also possible to develop and edit in real time through the low-code platform the running environment for simulating the system platform corresponding to the plug-in to be generated. When the communication protocol of the system platform changes, the configuration of the running environment file can be adjusted through the low-code platform to simulate the corresponding communication protocol change, so as to ensure the debugging of the plug-in program generated correspondingly in the low-code platform and meet the application requirements of the actual system platform, thereby ensuring the reliability of the generated plug-in program.

[0131] Step S402, based on the program configuration file, determine the first protocol mapping information between the system platform corresponding to the plug-in to be generated and the low-code platform.

[0132] Step S403, based on the first protocol mapping information, map the program configuration file to the corresponding program configuration parsing file.

[0133] Step S404, based on the program configuration parsing file, perform an instantiation process on the plug-in to be generated to obtain the plug-in program corresponding to the plug-in to be generated.

[0134] Specifically, steps S402 to S404 are the same as the corresponding step contents in the Figure 2 shown embodiment, and will not be elaborated here.

[0135] Step S405, in response to receiving the first service request information sent by the plug-in program, determine the second communication sender corresponding to the service request information.

[0136] Specifically, after generating the plugin program, it can be published to the corresponding system platform. At this time, if the low-code platform and the system platform where the plugin program is located are still in a communication state, communication can be carried out between the plugin program and the external server through the low-code platform.

[0137] At this time, the low-code platform will receive the request information (i.e., the first service request information) sent by the plugin program from the system platform and determine the third-party device (i.e., the second communication sender) corresponding to this information. The second communication sender is usually recorded in the first service request information (such as in the header information of the data packet of the first service request information), and only the corresponding part in the first service request information needs to be read to obtain it.

[0138] Step S406: Based on the first communication protocol supported by the system platform corresponding to the plugin program and the first protocol mapping information, determine the service request data included in the service request information.

[0139] Among them, the service request data is used to represent the data included in the service request information that supports being read in the low-code platform.

[0140] Specifically, since the first service request information is generated based on the first communication protocol of the system platform, it is necessary to obtain the data therein based on the first communication protocol and convert it into service request data that supports being read in the low-code platform based on the first protocol mapping information. The principle of the relevant steps is the same as that of the relevant part of configuring and modifying data in the foregoing embodiments, and will not be elaborated here.

[0141] Step S407: Determine the fourth communication protocol supported by the second communication sender.

[0142] Specifically, the first service request information will contain the corresponding recipient, that is, the second communication sender. Therefore, the communication protocol (i.e., the fourth communication protocol) corresponding to it recorded in the database of the low-code platform can be determined based on the identification information of the second communication sender; or, if the fourth communication protocol (or its identification information) corresponding to the second communication sender is recorded in the first service request information, the corresponding fourth communication protocol can be directly determined from the first service request information.

[0143] Step S408: Determine the third protocol mapping information between the second communication sender and the low-code platform.

[0144] Specifically, based on the fourth communication protocol and the identification information of the second communication protocol, the corresponding protocol mapping information (i.e., the third protocol mapping information) can be queried. The relevant principle has been fully explained in the foregoing embodiments and will not be elaborated here.

[0145] Step S409: Based on the third protocol mapping information, convert the service request data into the second service request information supported by the second communication sending platform.

[0146] Specifically, based on the third protocol mapping information, the service request data supported for editing on the robot system platform can be mapped to a version supported for editing on the second communication sender, that is, the corresponding second service request information is obtained. The relevant principles of protocol mapping have been fully described in the foregoing embodiments and will not be elaborated here.

[0147] Step S410: Send the second service request information to the second communication sender.

[0148] Specifically, after obtaining the second service request information, it can be sent to the corresponding second communication sender.

[0149] In some embodiments, if the sending of the second service request information fails, the low-code platform can perform error handling based on pre-configured processing rules, such as resending or reporting an error to the system platform where the plug-in program is located.

[0150] Step S411: In response to the request result information returned by the second communication sender, determine the request result data corresponding to the request result information based on the fourth communication protocol.

[0151] Among them, the request result data is used to represent the data supported for reading in the second communication sender included in the request result information.

[0152] Specifically, after sending the second service request information, the low-code platform will wait for the request result returned by the second communication sender. When the corresponding request result information is received, it will be parsed based on the fourth communication protocol determined in the foregoing steps to obtain the request result data included therein. The principle is the same as that for obtaining the configuration modification data and will not be elaborated here.

[0153] Step S412: Based on the third protocol mapping information, map the request result data to the corresponding platform result data.

[0154] Among them, the platform result data is used to represent the data supported for reading in the low-code platform corresponding to the request result data.

[0155] Specifically, after obtaining the request result data, it can be parsed into a version supported for reading in the low-code platform through the third protocol mapping information determined in the foregoing steps, that is, the platform result data.

[0156] Step S413: Based on the first protocol mapping information, map the result platform data to the corresponding plug-in result data.

[0157] Among them, the plug-in result data is used to represent the data corresponding to the request result data that supports reading in the system platform where the plug-in program is located.

[0158] Specifically, after obtaining the platform result data, it can be converted based on the first protocol mapping information into a version that supports reading in the system platform where the plug-in program is located, that is, the plug-in result data.

[0159] Step S414: Return the plug-in result data to the plug-in program.

[0160] Specifically, after obtaining the plug-in result data, it can be sent to the plug-in program (the system platform where it is located), thereby completing the transmission of the service request data.

[0161] Through the transmission of the low-code platform, when the communication protocol of either the system platform where the plug-in program is located or the second communication sending end changes, it can also ensure the normal progress of data communication, thereby ensuring the compatibility and reliability of the plug-in program.

[0162] In the plug-in generation method provided by the embodiments of the present disclosure, after the plug-in program is generated, the plug-in program can also perform data communication with the corresponding third-party device through the low-code platform and return the corresponding communication result through the low-code platform. Thus, when the communication protocol of any one of the system platforms changes, it effectively ensures the normal progress of the data communication between the plug-in program and the outside, thereby ensuring the compatibility and reliability of the plug-in program.

[0163] Figure 5 It is a schematic structural diagram of a plug-in generation device provided by an embodiment of the present disclosure. As Figure 5 shown, the plug-in generation device 500 is applied to the low-code platform and includes: a determination module 510, a search module 520, a parsing module 530, and a processing module 540. Among them:

[0164] The determination module 510 is used to determine the program configuration file of the plug-in to be generated. Among them, the program configuration file is used to generate the instantiated plug-in to be generated, and the program configuration file is stored in the low-code platform;

[0165] A search module 520, configured to determine first protocol mapping information between the system platform corresponding to the plugin to be generated and the low-code platform based on a program configuration file; wherein, the first protocol mapping information is stored in a mapping configuration file; the mapping configuration file is used to store the communication protocols of the low-code platform, the communication protocols of devices other than the low-code platform, and the protocol mapping information between devices other than the low-code platform and the low-code platform; the mapping configuration file is further configured to update the protocol mapping information based on received version update data of the communication protocol; the protocol mapping information is used to represent the configuration information required for mapping between the communication protocol of the low-code platform and the communication protocols of devices other than the low-code platform, and the protocol mapping information includes the first protocol mapping information.

[0166] A parsing module 530, configured to map the program configuration file to a corresponding program configuration parsing file based on the first protocol mapping information, wherein the program configuration parsing file is used to represent the corresponding file version of the program configuration file that supports running in the system platform corresponding to the plugin to be generated.

[0167] A processing module 540, configured to perform instantiation processing on the plugin to be generated based on the program configuration parsing file to obtain a plugin program corresponding to the plugin to be generated, wherein the plugin program is applied in the system platform.

[0168] Optionally, the search module 520 is specifically configured to determine a first communication protocol supported by the system platform corresponding to the plugin to be generated based on the program configuration file; determine a second communication protocol supported by the low-code platform; and retrieve the first protocol mapping information from the mapping configuration file based on the identification codes of the first communication protocol and the second communication protocol.

[0169] Optionally, the determination module 510 is further configured to determine a modified program configuration file based on an operation for modifying the program configuration file of the plugin to be generated before determining the program configuration file of the plugin to be generated.

[0170] Optionally, the determination module 510 is further configured to, before determining the program configuration file of the plugin to be generated, obtain configuration modification information corresponding to the plugin to be generated, where the configuration modification information includes a corresponding first communication sender; determine configuration modification data included in the configuration modification information based on a third communication protocol supported by the first communication sender, where the configuration modification data is used to represent data for modifying the program configuration file of the plugin to be generated included in the configuration modification information; determine second protocol mapping information between the first communication sender and the low-code platform from the mapping configuration file based on the third communication protocol and the second communication protocol supported by the low-code platform; map the configuration modification data to platform data based on the second protocol mapping information, where the platform data is used to represent data that can be recognized and processed by the low-code platform; and modify the program configuration file based on the platform data to obtain a modified program configuration file.

[0171] Optionally, the determination module 510 specifically includes that the second protocol mapping information includes communication protocol mapping information and plug-in data mapping information; the communication protocol mapping information contains the correspondence between the elements in the configuration modification data and the elements in the configuration file of the plug-in to be generated; the plug-in data mapping information contains the attribute information of the elements in the configuration file of the plug-in to be generated.

[0172] Optionally, the determination module 510 is specifically configured to, if the platform data includes element logical data and element attribute data, based on the communication protocol mapping information in the second protocol mapping information, determine the element logical data corresponding to the configuration modification data, where the element logical data is used to represent the logical data corresponding to the elements in the plug-in to be generated corresponding to the configuration modification data; based on the plug-in data mapping information in the second protocol mapping information, determine the element attribute data corresponding to the configuration modification data, where the element attribute data is used to represent the attribute data of the elements in the plug-in to be generated corresponding to the configuration modification data.

[0173] Optionally, the processing module 540 is further configured to, based on the program configuration parsing file, instantiate the plug-in to be generated to obtain the plug-in program corresponding to the plug-in to be generated, and then, in response to receiving the first service request information sent by the plug-in program, determine the second communication sending end corresponding to the service request information; based on the first communication protocol supported by the system platform corresponding to the plug-in program and the first protocol mapping information, determine the service request data included in the service request information, where the service request data is used to represent the data included in the service request information supported to be read in the low-code platform; determine the fourth communication protocol supported by the second communication sending end; determine the third protocol mapping information between the second communication sending end and the low-code platform; based on the third protocol mapping information, convert the service request data into the second service request information supported by the second communication sending platform; and send the second service request information to the second communication sending end.

[0174] Optionally, after the processing module 540 sends the second service request information to the second communication sending end, it further includes: in response to receiving the request result information returned by the second communication sending end, based on the fourth communication protocol, determine the request result data corresponding to the request result information, where the request result data is used to represent the data included in the request result information supported to be read in the second communication sending end; based on the third protocol mapping information, map the request result data to the corresponding platform result data, where the platform result data is used to represent the data supported to be read in the low-code platform corresponding to the request result data; based on the first protocol mapping information, map the result platform data to the corresponding plug-in result data, where the platform result data is used to represent the data supported to be read in the system platform where the plug-in program is located corresponding to the request result data; and return the plug-in result data to the plug-in program.

[0175] Optionally, the determining module 540 specifically includes that the program configuration file is developed through a low-code platform, or the program configuration file is obtained by referring to a dependency link provided by an external server.

[0176] Optionally, the determining module 540 specifically includes that the program configuration file further includes a corresponding running environment file, and the running environment file is developed based on a low-code platform.

[0177] In this embodiment, the plug-in generation device, through the combination of each module, solves the problem in the related art that the plug-in developed based on a low-code platform is prone to compatibility issues due to changes in communication protocols, significantly improving the compatibility, customizability, scalability, and reliability of the generated plug-in program.

[0178] Figure 6 The structural schematic diagram of the control device provided by an embodiment of the present disclosure is shown in Figure 6 As shown, the control device 600 includes: a memory 610 and a processor 620.

[0179] Among them, the memory 610 stores a computer program executable by at least one processor 620. The computer program is executed by at least one processor 620 to enable the control device to implement the material extraction method provided in any of the above embodiments or the plug-in generation method provided in any of the above embodiments.

[0180] Among them, the memory 610 and the processor 620 can be connected through a bus 630.

[0181] For relevant descriptions, reference can be made to the corresponding descriptions and effects in the method embodiments, which will not be elaborated here.

[0182] For relevant descriptions, reference can be made to the corresponding descriptions and effects in the method embodiments, which will not be elaborated here.

[0183] An embodiment of the present disclosure provides a computer-readable storage medium, on which a computer program is stored, and the computer program is executed by a processor to implement the material extraction method provided in any of the above method embodiments or the plug-in generation method provided in any of the above embodiments.

[0184] Among them, the computer-readable storage medium can be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0185] An embodiment of the present disclosure provides a computer program product, which includes computer execution instructions, and when the computer execution instructions are executed by a processor, they are used to implement the material extraction method in the above method embodiments or the plug-in generation method provided in any of the above embodiments.

[0186] In several embodiments provided by the present disclosure, it should be understood that the disclosed apparatus and method can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the apparatus or module can be in electrical, mechanical or other forms.

[0187] Those skilled in the art will readily conceive of other embodiments of the present disclosure after considering the specification and practicing the disclosure herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common general knowledge or conventional technical means in the technical field not disclosed herein. The specification and examples are only illustrative, and the true scope and spirit of the present disclosure are pointed out by the following claims.

[0188] It should be understood that the present disclosure is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.

Claims

1. A plug-in generation method, characterized in that, Applied to a low-code platform, the method for generating the plugin includes: Determine the program configuration file of the plugin to be generated. Among them, the program configuration file is used to generate the instantiated plugin to be generated, and the program configuration file is stored in the low-code platform; Based on the program configuration file, determine the first protocol mapping information between the system platform corresponding to the plugin to be generated and the low-code platform; among them, the system platform is the system platform corresponding to the robot; the first protocol mapping information is stored in the mapping configuration file; the mapping configuration file is used to store the communication protocol of the low-code platform, the communication protocols of devices other than the low-code platform, and the protocol mapping information between devices other than the low-code platform and the low-code platform; the mapping configuration file is also used to update the protocol mapping information based on the received version update data of the communication protocol; the protocol mapping information is used to represent the configuration information required for mapping between the communication protocol of the low-code platform and the communication protocols of devices other than the low-code platform, and the protocol mapping information includes the first protocol mapping information; Based on the first protocol mapping information, map the program configuration file to a corresponding program configuration parsing file, where the program configuration parsing file is used to represent the corresponding file version of the program configuration file that supports running in the system platform corresponding to the plugin to be generated; Based on the program configuration parsing file, perform instantiation processing on the plugin to be generated to obtain the plugin program corresponding to the plugin to be generated, where the plugin program is applied in the system platform.

2. The method according to claim 1, characterized in that The step of determining the first protocol mapping information between the system platform corresponding to the plugin to be generated and the low-code platform from the preset mapping configuration file based on the program configuration file includes: Based on the program configuration file, determine the first communication protocol supported by the system platform corresponding to the plugin to be generated; Determine the second communication protocol supported by the low-code platform; Based on the identification codes of the first communication protocol and the second communication protocol, retrieve the first protocol mapping information from the mapping configuration file.

3. The method according to claim 1, wherein Before determining the program configuration file of the plugin to be generated, it further includes: Based on the modification operation of the program configuration file of the plugin to be generated, determine the modified program configuration file.

4. The method according to claim 1, characterized in that, Before determining the program configuration file of the plugin to be generated, it further includes: Obtain the configuration modification information corresponding to the plugin to be generated, and the configuration modification information includes a corresponding first communication sender; Based on the third communication protocol supported by the first communication sender, determine the configuration modification data included in the configuration modification information, where the configuration modification data is used to represent the data for modifying the program configuration file of the plugin to be generated included in the configuration modification information; Based on the third communication protocol and the second communication protocol supported by the low-code platform, determine the second protocol mapping information between the first communication sender and the low-code platform from the mapping configuration file; Based on the second protocol mapping information, map the configuration modification data into platform data, where the platform data is used to represent the data supported by the low-code platform for recognition and processing; Based on the platform data, modify the program configuration file to obtain a modified program configuration file.

5. The method according to claim 4, wherein The second protocol mapping information includes communication protocol mapping information and plug-in data mapping information; The communication protocol mapping information contains the correspondence between the elements in the configuration modification data and the elements in the configuration file of the plug-in to be generated; The plug-in data mapping information contains the attribute information of the elements in the configuration file of the plug-in to be generated.

6. The method according to claim 5, wherein The platform data includes element logic data and element attribute data; The mapping of the configuration modification data into platform data based on the second protocol mapping information includes: Based on the communication protocol mapping information in the second protocol mapping information, determine the element logic data corresponding to the configuration modification data, where the element logic data is used to represent the logic data corresponding to the elements in the plug-in to be generated corresponding to the configuration modification data; Based on the plug-in data mapping information in the second protocol mapping information, determine the element attribute data corresponding to the configuration modification data, where the element attribute data is used to represent the attribute data of the elements in the plug-in to be generated corresponding to the configuration modification data.

7. The method according to any one of claims 1 to 6, characterized in that After the plug-in to be generated is instantiated based on the program configuration parsing file to obtain the plug-in program corresponding to the plug-in to be generated, it further includes: In response to receiving the first service request information sent by the plug-in program, determine the second communication sending end corresponding to the service request information; Based on the first communication protocol and the first protocol mapping information supported by the system platform corresponding to the plug-in program, determine the service request data included in the service request information, where the service request data is used to represent the data included in the service request information supported for reading in the low-code platform; Determine the fourth communication protocol supported by the second communication sending end; Determine the third protocol mapping information between the second communication sending end and the low-code platform; Based on the third protocol mapping information, convert the service request data into the second service request information supported by the second communication sending end; Send the service request information to the second communication sending end.

8. The method according to claim 7, wherein After sending the service request information to the second communication sending end, it further includes: In response to receiving the request result information returned by the second communication sending end, based on the fourth communication protocol, determine the request result data corresponding to the request result information, where the request result data is used to represent the data included in the request result information supported for reading in the second communication sending end; Based on the third protocol mapping information, map the request result data into the corresponding platform result data, where the platform result data is used to represent the data corresponding to the request result data supported for reading in the low-code platform; Based on the first protocol mapping information, map the platform result data to corresponding plug-in result data, where the plug-in result data is used to represent the data corresponding to the request result data that supports reading in the system platform where the plug-in program is located; Return the plug-in result data to the plug-in program.

9. The method according to any one of claims 1 to 6, characterized in that The program configuration file is developed through the low-code platform, or the program configuration file is obtained by referring to the dependency link provided by an external server.

10. The method according to any one of claims 1 to 6, characterized in that, The program configuration file further includes a corresponding runtime environment file, and the runtime environment file is developed through the low-code platform.

11. A plug-in generation device, characterized in that, Applied to a low-code platform, the plug-in generation device includes: A determination module, configured to determine a program configuration file of a to-be-generated plug-in, where the program configuration file is used to generate an instantiated to-be-generated plug-in, and the program configuration file is stored in the low-code platform; A search module, configured to determine first protocol mapping information between the system platform corresponding to the to-be-generated plug-in and the low-code platform based on the program configuration file; where the system platform is the system platform corresponding to the robot; the first protocol mapping information is stored in a mapping configuration file; the mapping configuration file is used to store the communication protocol of the low-code platform, the communication protocols of devices outside the low-code platform, and the protocol mapping information between devices outside the low-code platform and the low-code platform; the mapping configuration file is further used to update the protocol mapping information based on the received version update data of the communication protocol; the protocol mapping information is used to represent the configuration information required for mapping between the communication protocol of the low-code platform and the communication protocols of devices outside the low-code platform, and the protocol mapping information includes the first protocol mapping information; An analysis module, configured to map the program configuration file to a corresponding program configuration analysis file based on the first protocol mapping information, where the program configuration analysis file is used to represent the corresponding file version of the program configuration file that supports running in the system platform corresponding to the to-be-generated plug-in; A processing module, configured to perform instantiation processing on the to-be-generated plug-in based on the program configuration analysis file to obtain a plug-in program corresponding to the to-be-generated plug-in, where the plug-in program is applied in the system platform.

12. A control device, characterized in that, Includes: At least one processor; And a memory communicatively connected to the at least one processor; Wherein, the memory stores instructions executable by the at least one processor, and when the instructions are executed by the at least one processor, the control device is caused to execute the plug-in generation method according to any one of claims 1-10.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the plug-in generation method according to any one of claims 1 to 10.

14. A computer program product, characterized in that, The computer program product includes computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the plug-in generation method according to any one of claims 1 to 10.

Images