Plug-in generation method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a plug-in generation method and device, equipment and a storage medium. The method comprises the steps of determining a program configuration file of a to-be-generated plug-in, determining first protocol mapping information between a system platform corresponding to the to-be-generated plug-in and a low-code platform based on the program configuration file, mapping the program configuration file into a corresponding program configuration analysis file based on the first protocol mapping information, and generating the to-be-generated plug-in according to the program configuration analysis file. And finally, based on the program configuration analysis file, instantiating the to-be-generated plug-in to obtain a plug-in program corresponding to the to-be-generated plug-in. According to the technical scheme, the problem that the compatibility of a plug-in developed on the basis of a low-code platform is not supported due to the change of a communication protocol in the related technology is solved, the compatibility, the customizability and the expandability of the generated plug-in program are remarkably improved, and the reliability of the plug-in program is improved.

Description

Technical Field

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

[0002] In the field of industrial robot development, it has become a common development model to develop programs and plug-ins used by robots through program development platforms such as low-code development platforms, and import them into 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 the third-party service on which the low-code development platform depends changes, compatibility issues will arise in the developed programs and plug-ins, resulting in an inability to be used normally in the robot. Summary of the invention

[0004] The embodiments of the present disclosure provide a plug-in generation method, apparatus, device and storage medium to solve 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.

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

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

[0007] 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, wherein 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 protocol 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 version update data of the communication protocol received; 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;

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

[0009] Based on the program configuration parsing file, the plug-in to be generated is instantiated to obtain a plug-in program corresponding to the plug-in to be generated, wherein the plug-in program is applied to the system platform.

[0010] Optionally, based on the program configuration file, the first protocol mapping information between the system platform corresponding to the plug-in to be generated and the low-code platform is determined from a preset mapping configuration file, including: based on the program configuration file, determining the first communication protocol supported by the system platform corresponding to the plug-in to be generated; determining 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, retrieving the first protocol mapping information from the mapping configuration file.

[0011] Optionally, before determining the program configuration file of the plug-in to be generated, the method further includes: determining a modified program configuration file based on a modification operation of the program configuration file of the plug-in to be generated.

[0012] Optionally, before determining the program configuration file of the plug-in to be generated, it also includes: obtaining configuration modification information corresponding to the plug-in to be generated, the configuration modification information includes the corresponding first communication sending end; based on the third communication protocol supported by the first communication sending end, determining the configuration modification data contained in the configuration modification information, wherein the configuration modification data is used to represent the data contained in the configuration modification information for modifying the program configuration file of the plug-in to be generated; based on the third communication protocol and the second communication protocol supported by the low-code platform, determining the second protocol mapping information between the first communication sending end and the low-code platform from the mapping configuration file; based on the second protocol mapping information, mapping the configuration modification data to platform data, wherein the platform data is used to represent the data supported for identification and processing by the low-code platform; based on the platform data, modifying the program configuration file to obtain a modified program configuration file.

[0013] Optionally, 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.

[0014] Optionally, the platform data includes element logical data and element attribute data; based on the second protocol mapping information, the configuration modification data is mapped to the platform data, including: based on the communication protocol mapping information in the second protocol mapping information, determining the element logical data corresponding to the configuration modification data, wherein the element logical data is used to represent the logical data corresponding to the element 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, determining the element attribute data corresponding to the configuration modification data, wherein the element attribute data is used to represent the attribute data of the element in the plug-in to be generated corresponding to the configuration modification data.

[0015] Optionally, 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, and it also includes: in response to receiving the first business request information sent by the plug-in program, determining that the business request information corresponds to the second communication sending end; based on the first communication protocol and the first protocol mapping information supported by the system platform corresponding to the plug-in program, determining the business request data contained in the business request information, wherein the business request data is used to represent the data contained in the business request information supported to be read 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 business request data into the second business request information supported by the second communication sending platform; and sending the second business request information to the second communication sending end.

[0016] Optionally, after sending the second business request information to the second communication sending end, it also includes: in response to the request result information received and returned by the second communication sending end, based on the fourth communication protocol, determining the request result data corresponding to the request result information, wherein the request result data is used to represent the data contained in the request result information and supported for reading in the second communication sending end; based on the third protocol mapping information, mapping the request result data to corresponding platform result data, wherein the platform result data is used to represent the data corresponding to the request result data and supported for reading in the low-code platform; based on the first protocol mapping information, mapping the result platform data to corresponding plug-in result data, wherein the platform result data is used to represent the data corresponding to the request result data and supported for reading in the system platform where the plug-in program is located; returning the plug-in result data to the plug-in program.

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

[0018] Optionally, the program configuration file also includes a corresponding operating environment file, and the operating environment file is developed based on a low-code platform.

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

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

[0021] A search module, used to determine, based on a program configuration file, the first protocol mapping information between the system platform corresponding to the plug-in to be generated and the low-code platform; wherein 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 protocol 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 version update data of the communication protocol received; 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, used for mapping 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 a corresponding file version of the program configuration file that supports running in the system platform corresponding to the plug-in to be generated;

[0023] The processing module is used to parse the file based on the program configuration, instantiate the plug-in to be generated, and obtain the plug-in program corresponding to the plug-in to be generated, wherein the plug-in program is applied to the system platform.

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

[0025] Optionally, the determination module is further configured to, before determining the program configuration file of the plug-in to be generated, determine a modified program configuration file based on a modification operation of the program configuration file of the plug-in to be generated.

[0026] Optionally, the determination module is also used to, before determining the program configuration file of the plug-in to be generated, obtain configuration modification information corresponding to the plug-in to be generated, the configuration modification information includes the corresponding first communication sending end; based on a third communication protocol supported by the first communication sending end, determine the configuration modification data contained in the configuration modification information, wherein the configuration modification data is used to represent the data contained in the configuration modification information for modifying the program configuration file of the plug-in to be generated; 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 sending end 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, wherein the platform data is used to represent the data supported for identification and processing by the low-code platform; based on the platform data, modify the program configuration file to obtain a modified program configuration file.

[0027] Optionally, the determination module specifically includes: 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 used to, if the platform data includes element logical data and element attribute data, determine the element logical data corresponding to the configuration modification data based on the communication protocol mapping information in the second protocol mapping information, wherein the element logical data is used to represent the logical data corresponding to the element in the plug-in to be generated corresponding to the configuration modification data; and 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, wherein the element attribute data is used to represent the attribute data of the element in the plug-in to be generated corresponding to the configuration modification data.

[0029] Optionally, the processing module is also used to instantiate the plug-in to be generated based on the program configuration parsing file, and after obtaining the plug-in program corresponding to the plug-in to be generated, determine that the business request information corresponds to the second communication sending end in response to receiving the first business request information sent by the plug-in program; determine the business request data contained in the business 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, wherein the business request data is used to represent the data contained in the business request information supported by 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 business request data into the second business request information supported by the second communication sending platform; and send the second business request information to the second communication sending end.

[0030] Optionally, the processing module is also used to, after sending the second business request information to the second communication sending end, also include: in response to the request result information received and returned by the second communication sending end, determine the request result data corresponding to the request result information based on the fourth communication protocol, wherein the request result data is used to represent the data contained in the request result information and supported for reading in the second communication sending end; based on the third protocol mapping information, map the request result data to corresponding platform result data, wherein the platform result data is used to represent the data corresponding to the request result data and supported for reading in the low-code platform; based on the first protocol mapping information, map the result platform data to corresponding plug-in result data, wherein the platform result data is used to represent the data corresponding to the request result data and supported for reading in the system platform where the plug-in program is located; and return the plug-in result data to the plug-in program.

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

[0032] Optionally, the determination module specifically includes that the program configuration file also includes a corresponding operating environment file, and the operating 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, the control device comprising:

[0034] at least one processor;

[0035] and a memory communicatively coupled to the at least one processor;

[0036] The memory stores instructions that can be executed 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 as described in 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, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the plug-in generation method as in the first aspect of the present disclosure.

[0038] In a fifth aspect, an embodiment of the present disclosure further 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 plug-in generation method as in the first aspect of the present disclosure.

[0039] The plug-in generation method, apparatus, device and storage medium provided by the embodiments of the present disclosure determine the program configuration file of the plug-in to be generated, and then determine the first protocol mapping information between the system platform and the low-code platform corresponding to the plug-in to be generated 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, and finally instantiate the plug-in to be generated based on the program configuration parsing file to obtain the plug-in program corresponding to the plug-in to be generated. As a result, the plug-in to be generated corresponding to the program configuration file can be generated 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 corresponding configured first protocol mapping information can be used to ensure that the plug-in program that can run on the system platform is generated, 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

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

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

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

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

[0045] Figure 5 A schematic diagram of the structure of a plug-in generating device provided in yet another embodiment of the present disclosure;

[0046] Figure 6 A schematic diagram of the structure of a control device provided in one embodiment of the present disclosure.

[0047] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope 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 DESCRIPTION

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

[0049] The following specific embodiments are used to describe in detail the technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems. The following specific embodiments can 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 invention will be described below in conjunction with the accompanying drawings.

[0050] The following is a description of the concepts involved in the embodiments of the present disclosure:

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

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

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

[0054] However, in the above model, program development platforms such as robot platforms and low-code platforms have their own supported communication protocols. At the same time, there may also be communication protocols of third-party services that the low-code development platform or program depends on. When any communication protocol changes, it may not be able to be read in the low-code platform, or cannot be used normally in the robot, or cannot communicate with third-party services, resulting in compatibility issues in the developed programs and plug-ins.

[0055] In order to solve this problem, an embodiment of the present disclosure provides a plug-in generation method, which pre-configures mapping configuration files and communication protocols between different platforms, maps the program configuration file of the plug-in to be generated to a program configuration parsing file supported by the robot system platform, and then instantiates the program configuration parsing file, 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 scenarios of the embodiments of the present disclosure are explained below:

[0057] Figure 1 This is an application scenario diagram of the plug-in generation method provided in the embodiment of the present disclosure. Figure 1 As 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, 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 function or operation.

[0058] It should be noted that Figure 1In the scenario shown, only one of the development end, low-code platform, program configuration file, plug-in program, and robot system is used as an example for illustration, but the present disclosure is not limited to this. In other words, the number of development ends, low-code platforms, program configuration files, plug-in programs, and robot systems can be arbitrary.

[0059] The plug-in generation method provided by the present disclosure is described in detail below through specific embodiments.

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

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

[0062] Among them, the program configuration file is used to generate instantiated plug-ins 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. The plug-in program can be imported into the robot system and applied in the robot system.

[0064] Before instantiation, the low-code platform can modify the program configuration file to expand, customize, maintain, and perform other operations on the generated plug-in.

[0065] Therefore, the program configuration file is 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, the code file of the instantiated plug-in program needs to 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 protocol of the low-code platform, the communication protocol 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 protocol of devices other than 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 includes the rules that need to be followed for protocol mapping between the low-code platform and the system platform corresponding to the plug-in 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 plug-in to be generated, as well as the necessary information required to map the data format supported by the communication protocol in the low-code platform to the data format supported by the communication protocol in the system platform corresponding to the plug-in to be generated (such as adding function libraries that need to be referenced, etc.).

[0071] The low-code platform can store mapping configuration files between the low-code platform and other platforms (that will communicate with the low-code platform) in the form of a database. Therefore, it is necessary to determine the corresponding protocol mapping information (in this step, the first protocol mapping information is determined) based on the identification information of the system platform corresponding to the plug-in to be generated or the identification information of the communication protocol of the system platform corresponding to the plug-in to be generated recorded in the program configuration file (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).

[0072] Since the first protocol mapping information involves the protocol mapping between the system platform corresponding to the plug-in to be generated and the low-code platform, the communication protocol corresponding to the low-code platform also needs to be considered when specifically determining the first protocol mapping information.

[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 on the low-code platform), or it can be obtained from the low-code platform when querying the first protocol mapping information. There is no restriction here.

[0074] Based on the acquired communication protocol identification information corresponding to the low-code platform and the identification information of the communication protocol of the system platform corresponding to the plug-in 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, changed, etc. over time, the mapping configuration file is configured to automatically receive 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 based on these version update data, thereby achieving adaptive update of the protocol mapping information and ensuring that the program configuration parsing file obtained by mapping the first protocol mapping information can adaptively run in the system platform after the communication protocol changes.

[0076] Step S203: Map the program configuration file to a corresponding program configuration parsing file based on the first protocol mapping information.

[0077] The program configuration parsing file is used to indicate the corresponding file version of the program configuration file that supports running in the system platform corresponding to the plug-in to be generated.

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

[0079] Step S204: based on the program configuration parsing file, instantiate the plug-in to be generated to obtain a plug-in program corresponding to the plug-in to be generated.

[0080] Among them, the plug-in program is applied to the system platform.

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

[0082] At this time, the corresponding operating environment library can also be configured in the low-code platform to simulate the operating environment in the robot system, and the plug-in program can be imported into the simulated operating environment for operation to check whether the generated plug-in program meets the requirements.

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

[0084] The plug-in generation method provided by the embodiment of the present disclosure determines the program configuration file of the plug-in to be generated, and then determines the first protocol mapping information between the system platform and the low-code platform corresponding to the plug-in to be generated from a preset mapping configuration file based on the program configuration file, and then parses the program configuration file into the corresponding program configuration parsing file based on the first protocol mapping information, and finally instantiates the plug-in to be generated based on the program configuration parsing file to obtain the plug-in program corresponding to the plug-in to be generated. As a result, the plug-in to be generated corresponding to the program configuration file can be generated 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 corresponding configured first protocol mapping information can be used to ensure that the plug-in program that can run on the system platform is generated, 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.

[0085] Figure 3 A flowchart of a plug-in generation method provided by an embodiment of the present disclosure. Figure 3 As 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 a modified program configuration file.

[0087] Specifically, before performing protocol mapping on the program configuration file, you can directly edit and modify it on the low-code platform, and then perform protocol mapping based on the modified program configuration file, thereby ensuring the scalability and customizability of the plug-in to be generated.

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

[0089] The configuration modification information includes the corresponding first communication sending end.

[0090] Specifically, modifications to the program configuration file can also be made by a third-party platform (or third-party device, that is, the first communication sending end) other than the low-code platform. For example, the developer can modify and edit part of the information in the program configuration file on his own computer, and then transmit the edited configuration modification information to the low-code platform. The low-code platform then updates the program configuration file based on the transmitted configuration modification information, and continues to instantiate the updated program configuration file.

[0091] Therefore, 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 sending end.

[0093] The configuration modification data is used to represent the data included in the configuration modification information for modifying the program configuration file of the plug-in to be generated.

[0094] Specifically, since the configuration modification information is generated and edited based on the third communication protocol supported by the first communication sending end, the third communication protocol may differ from the second communication protocol supported by the low-code platform (such as the second communication protocol is a communication protocol supported by the Windows platform, and the third communication protocol is a communication protocol supported by the Linux platform). Therefore, the configuration modification information needs to be processed 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 a special format 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), it is necessary to parse the configuration modification information based on the third communication protocol to obtain the configuration modification data (such as using the corresponding decompression tool to extract the configuration modification data in accordance with the file compression format specified in the third communication protocol).

[0096] Step S304, 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 sending end and the low-code platform from the mapping configuration file.

[0097] Specifically, in order to map the configuration modification data into a format that supports 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] Further, the second protocol mapping information includes communication protocol mapping information and plug-in data mapping information;

[0099] The communication protocol mapping information includes 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 includes the attribute information of the elements in the configuration file of the plug-in to be generated.

[0100] Specifically, the protocol mapping information includes the correspondence between elements of different platforms (ie, communication protocol mapping information) and the configuration information required for the functional execution or realization of the corresponding elements (ie, plug-in data mapping information).

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

[0102] In addition to recording the data type that the data in the configuration modification data depends on when running on the low-code platform, the communication protocol mapping information also records the corresponding default assignment of the data type, 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 type class 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: Map the configuration modification data into platform data based on the second protocol mapping information.

[0104] Among them, platform data is used to represent the data that the low-code platform supports identification and processing.

[0105] Specifically, after obtaining the second protocol mapping information, the configuration modification data can be mapped to data that supports 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, wherein the element logical data is used to represent the logical data corresponding to the element in the plug-in to be generated 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, wherein the element attribute data is used to represent the attribute data of the element in the plug-in to be generated 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 the 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 normally in the low-code platform.

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

[0110] Specifically, based on the obtained platform data, the corresponding content in the program configuration file is modified 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. This type of operation is an existing technology in program editing and is only used as an example here without specific limitation).

[0111] Steps S302 to S306 are optional steps parallel to step S301. Those skilled in the art may select corresponding steps to execute according to actual conditions, and no limitation is made here.

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

[0113] Among them, the program configuration file is used to generate instantiated plug-ins to be generated, 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 may be saved and instantiated.

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

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

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

[0118] Specifically, the confirmation method of the second communication protocol has been described in the above 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 first protocol mapping information from a mapping configuration file.

[0120] Specifically, the first protocol mapping information can be saved in the database of the low-code platform as part of the mapping configuration file, or it can be saved separately in the database of the low-code platform. In the latter method, 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 therein after determining the corresponding mapping configuration file.

[0121] Step S311: Map the program configuration file to a corresponding program configuration parsing file based on the first protocol mapping information.

[0122] The program configuration parsing file is used to indicate the corresponding file version of the program configuration file that supports running in the system platform corresponding to the plug-in to be generated.

[0123] Step S312: based on the program configuration parsing file, instantiate the plug-in to be generated to obtain a plug-in program corresponding to the plug-in to be generated.

[0124] Specifically, step S311 to step S312 are Figure 2 The corresponding steps in the illustrated embodiment are the same in content and will not be described again here.

[0125] The plug-in generation method provided by the embodiment of the present disclosure can be obtained by editing the program configuration file on the low-code platform, or obtaining configuration modification information from the first communication sending end, and modifying the program configuration file accordingly, and then mapping and instantiating based on the modified program configuration file to obtain the urban construction program corresponding to the plug-in to be generated. In this way, the program configuration file can be edited in different ways, and instantiated based on the edited program configuration file, fully ensuring the customizability and extensibility of the plug-in program, while ensuring the compatibility of the obtained plug-in program.

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

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

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

[0129] Specifically, in addition to supporting modification, program configuration files can also be directly developed through the low-code platform, or program configuration files can be referenced based on dependency links provided by external servers. By supporting the instantiation of program configuration files obtained from different sources, the customizability and extensibility of plug-ins generated based on the low-code platform can be maximized.

[0130] Furthermore, the program configuration file also includes a corresponding operating environment file, which is developed based on the low-code platform. Therefore, the low-code platform can also be used to develop and edit in real time the operating environment for simulating the corresponding system platform of the plug-in to be generated. When the communication protocol of the system platform changes, the low-code platform can be used to configure the operating environment file therein to simulate the corresponding communication protocol change, so as to ensure the debugging of the corresponding plug-in program generated in the low-code platform, meet the application requirements of the actual system platform, and thus ensure 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: Map the program configuration file to a corresponding program configuration parsing file based on the first protocol mapping information.

[0133] Step S404: based on the program configuration parsing file, instantiate the plug-in to be generated to obtain a plug-in program corresponding to the plug-in to be generated.

[0134] Specifically, step S402 to step S404 are Figure 2 The corresponding steps in the illustrated embodiment are the same in content and will not be described again here.

[0135] Step S405: in response to receiving the first service request information sent by the plug-in program, determining that the service request information corresponds to the second communication sending end.

[0136] Specifically, after generating the plug-in program, the plug-in program can be published to the corresponding system platform. At this time, if the low-code platform and the system platform where the plug-in program is located are still in communication, communication can be carried out between the plug-in 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 plug-in from the system platform, and determine the third-party device (i.e., the second communication sending end) corresponding to the information. The second communication sending end is usually recorded in the first service request information (such as the header information of the data packet of the first service request information), and can be obtained by reading the corresponding part of the first service request information.

[0138] Step S406: determining the service request data included in 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.

[0139] Among them, business request data is used to represent the data contained in the business request information that supports reading in the low-code platform.

[0140] Specifically, the first business request information is generated based on the first communication protocol of the system platform. Therefore, it is necessary to obtain the data therein based on the first communication protocol, and convert it into business request data that supports reading in the low-code platform based on the first protocol mapping information. The principles of the relevant steps are the same as the principles of the configuration and modification data related parts in the aforementioned embodiment, and will not be repeated here.

[0141] Step S407, determining a fourth communication protocol supported by the second communication sending end.

[0142] Specifically, the first business request information will include the corresponding recipient, that is, the second communication sending end. Therefore, the corresponding communication protocol (that is, the fourth communication protocol) recorded in the database of the low-code platform can be determined based on the identification information of the second communication sending end; or, if the first business request information records the fourth communication protocol (or its identification information) corresponding to the second communication sending end, the corresponding fourth communication protocol can be directly determined from the first business request information.

[0143] Step S408, determine the third protocol mapping information between the second communication sending end and the low-code platform.

[0144] Specifically, based on the identification information of the fourth communication protocol and the second communication protocol, corresponding protocol mapping information (ie, third protocol mapping information) may be queried and obtained. The relevant principles have been fully described in the aforementioned embodiments and will not be repeated here.

[0145] Step S409: based on the third protocol mapping information, convert the service request data into 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 sending end, that is, the corresponding second service request information is obtained. The relevant principles of protocol mapping have been fully explained in the above embodiments and will not be repeated here.

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

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

[0149] In some embodiments, if the sending of the second business request information is unsuccessful, 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 received 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.

[0151] The request result data is used to indicate the data contained in the request result information and supported to be read in the second communication sending end.

[0152] Specifically, after sending the second business request information, the low-code platform will wait for the request result returned by the second communication sending end. When the corresponding request result information is received, it will be parsed based on the fourth communication protocol determined in the previous steps to obtain the request result data contained therein. The principle is the same as the principle of obtaining configuration modification data, which will not be repeated here.

[0153] Step S412: Map the request result data to corresponding platform result data based on the third protocol mapping information.

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

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

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

[0157] The plug-in result data is used to represent the data corresponding to the request result data and supported to be read in the system platform where the plug-in program is located.

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

[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 given to the plug-in program (the system platform where it is located), thereby completing the transmission of the business 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, data communication can be guaranteed to proceed normally, thereby ensuring the compatibility and reliability of the plug-in program.

[0162] The plug-in generation method provided in the embodiment of the present disclosure can generate a plug-in program, and the plug-in program can also communicate data with the corresponding third-party device through the low-code platform, and return the corresponding communication results through the low-code platform. In this way, it is effectively guaranteed that when the communication protocol of any party's system platform changes, the plug-in program can communicate with the external data normally, thereby ensuring the compatibility and reliability of the plug-in program.

[0163] Figure 5 This is a schematic diagram of the structure of a plug-in generation device provided by an embodiment of the present disclosure. Figure 5 As shown, the plug-in generation device 500 is applied to a 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] A determination module 510 is used to determine a program configuration file of the plug-in to be generated, wherein the program configuration file is used to generate an instantiated plug-in to be generated, and the program configuration file is stored in the low-code platform;

[0165] The search module 520 is used to 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; wherein 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 protocol of devices other than the low-code platform, and the protocol mapping information between the 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 version update data of the communication protocol received; 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;

[0166] The parsing module 530 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 a corresponding file version of the program configuration file that supports running in the system platform corresponding to the plug-in to be generated;

[0167] The processing module 540 is used to instantiate the plug-in to be generated based on the program configuration parsing file, and obtain a plug-in program corresponding to the plug-in to be generated, wherein the plug-in program is applied to the system platform.

[0168] Optionally, the search module 520 is specifically used to determine, based on the program configuration file, a first communication protocol supported by the system platform corresponding to the plug-in to be generated; 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, before determining the program configuration file of the plug-in to be generated, determine a modified program configuration file based on a modification operation of the program configuration file of the plug-in to be generated.

[0170] Optionally, the determination module 510 is also used to, before determining the program configuration file of the plug-in to be generated, obtain configuration modification information corresponding to the plug-in to be generated, the configuration modification information includes the corresponding first communication sending end; based on the third communication protocol supported by the first communication sending end, determine the configuration modification data contained in the configuration modification information, wherein the configuration modification data is used to represent the data contained in the configuration modification information for modifying the program configuration file of the plug-in to be generated; 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 sending end 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, wherein the platform data is used to represent the data supported for identification and processing by the low-code platform; based on the platform data, modify the program configuration file to obtain a modified program configuration file.

[0171] Optionally, the determination module 510 specifically includes: 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 used to, if the platform data includes element logical data and element attribute data, determine the element logical data corresponding to the configuration modification data based on the communication protocol mapping information in the second protocol mapping information, wherein the element logical data is used to represent the logical data corresponding to the element in the plug-in to be generated corresponding to the configuration modification data; and 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, wherein the element attribute data is used to represent the attribute data of the element in the plug-in to be generated corresponding to the configuration modification data.

[0173] Optionally, the processing module 540 is also used to instantiate the plug-in to be generated based on the program configuration parsing file, and after obtaining the plug-in program corresponding to the plug-in to be generated, determine that the business request information corresponds to the second communication sending end in response to receiving the first business request information sent by the plug-in program; determine the business request data contained in the business 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, wherein the business request data is used to represent the data contained in the business 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 business request data into the second business request information supported by the second communication sending platform; and send the second business request information to the second communication sending end.

[0174] Optionally, after sending the second business request information to the second communication sending terminal, the processing module 540 is also used to: in response to the request result information received and returned by the second communication sending terminal, determine the request result data corresponding to the request result information based on the fourth communication protocol, wherein the request result data is used to represent the data contained in the request result information and supported for reading in the second communication sending terminal; based on the third protocol mapping information, map the request result data to corresponding platform result data, wherein the platform result data is used to represent the data corresponding to the request result data and supported for reading in the low-code platform; based on the first protocol mapping information, map the result platform data to corresponding plug-in result data, wherein the platform result data is used to represent the data corresponding to the request result data and supported for reading in the system platform where the plug-in program is located; and return the plug-in result data to the plug-in program.

[0175] Optionally, the determination module 540 specifically includes that the program configuration file is obtained through low-code platform development, or that the program configuration file is obtained based on a dependency link reference provided by an external server.

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

[0177] In this embodiment, the plug-in generation device solves the problem that plug-ins developed based on low-code platforms in related technologies are prone to compatibility issues due to changes in communication protocols through the combination of various modules, significantly improves the compatibility, customizability, and scalability of the generated plug-in programs, and improves their reliability.

[0178] Figure 6 A schematic diagram of the structure of a control device provided by an embodiment of the present disclosure, such as Figure 6 As shown, the control device 600 includes: a memory 610 and a processor 620 .

[0179] The memory 610 stores a computer program that can be executed 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 removal method provided in any of the above embodiments or the plug-in generation method provided in any of the above embodiments.

[0180] The memory 610 and the processor 620 may be connected via a bus 630 .

[0181] The relevant instructions can be understood by referring to the relevant descriptions and effects corresponding to the method embodiments, which will not be repeated here.

[0182] The relevant instructions can be understood by referring to the relevant descriptions and effects corresponding to the method embodiments, which will not be repeated here.

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

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

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

[0186] In the several embodiments provided in the present disclosure, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules is only a logical function division, and there may be other division methods in actual implementation, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0187] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the disclosure disclosed 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 knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

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

Claims

1. A plug-in generation method, characterized in that: Applied to the low-code platform, the plug-in generation method includes: Determine a program configuration file of the plug-in to be generated, wherein the program configuration file is used to generate an instantiated plug-in 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 plug-in to be generated and the low-code platform; wherein 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 protocol 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 version update data of the communication protocol received; 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; Based on the first protocol mapping information, mapping the program configuration file to a corresponding program configuration parsing file, wherein the program configuration parsing file is used to indicate a corresponding file version of the program configuration file that supports running in the system platform corresponding to the plug-in to be generated; Based on the program configuration parsing file, the plug-in to be generated is instantiated to obtain a plug-in program corresponding to the plug-in to be generated, wherein the plug-in program is applied to the system platform.

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

3. The method according to claim 1, characterized in that Before determining the program configuration file of the plug-in to be generated, it also includes: Based on the program configuration file modification operation of the to-be-generated plug-in, a modified program configuration file is determined.

4. The method according to claim 1, characterized in that: Before determining the program configuration file of the plug-in to be generated, the method further includes: Obtaining configuration modification information corresponding to the plug-in to be generated, wherein the configuration modification information includes a corresponding first communication sending end; Determining, based on a third communication protocol supported by the first communication sending end, configuration modification data contained in the configuration modification information, wherein the configuration modification data is used to represent data contained in the configuration modification information for modifying a program configuration file of the plug-in to be generated; Based on the third communication protocol and the second communication protocol supported by the low-code platform, determining the second protocol mapping information between the first communication sending end and the low-code platform from the mapping configuration file; Based on the second protocol mapping information, mapping the configuration modification data into platform data, wherein the platform data is used to represent data supported for identification and processing by the low-code platform; Based on the platform data, the program configuration file is modified to obtain a modified program configuration file.

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

6. The method according to claim 5, characterized in that The platform data includes element logic data and element attribute data; The mapping of the configuration modification data to platform data based on the second protocol mapping information includes: Determine, based on the communication protocol mapping information in the second protocol mapping information, element logic data corresponding to the configuration modification data, wherein the element logic data is used to represent logic data corresponding to an element in the to-be-generated plug-in corresponding to the configuration modification data; Based on the plug-in data mapping information in the second protocol mapping information, element attribute data corresponding to the configuration modification data is determined, wherein the element attribute data is used to represent attribute data of an element 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 instantiating the plug-in to be generated based on the program configuration parsing file to obtain the plug-in program corresponding to the plug-in to be generated, the method further includes: In response to receiving the first service request information sent by the plug-in program, determining that the service request information corresponds to the second communication sending end; Based on the first communication protocol and first protocol mapping information supported by the system platform corresponding to the plug-in program, determine the business request data contained in the business request information, wherein the business request data is used to represent the data contained in the business request information supported for reading in the low-code platform; Determining a fourth communication protocol supported by the second communication sending end; Determine 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 second service request information supported by the second communication sending platform; The service request information is sent to the second communication sending end.

8. The method according to claim 7, characterized in that After sending the service request information to the second communication sending end, the method further includes: In response to the received 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, wherein the request result data is used to represent the data contained in the request result information and supported to be read in the second communication sending end; Based on the third protocol mapping information, the request result data is mapped to corresponding platform result data, wherein the platform result data is used to represent the data corresponding to the request result data and supported for reading in the low-code platform; Based on the first protocol mapping information, the result platform data is mapped into corresponding plug-in result data, wherein the plug-in result data is used to represent the data corresponding to the request result data and supported to be read in the system platform where the plug-in program is located; The plug-in result data is returned 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 based on a dependency link reference provided by an external server.

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

11. A plug-in generating device, characterized in that: Applied to the low-code platform, the plug-in generating device includes: A determination module, used to determine a program configuration file of a plug-in to be generated, wherein the program configuration file is used to generate an instantiated plug-in to be generated, and the program configuration file is stored in the low-code platform; A search module is used to determine, based on the program configuration file, the first protocol mapping information between the system platform corresponding to the plug-in to be generated and the low-code platform; wherein 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 protocol 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 version update data of the communication protocol received; 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; A parsing module, used for mapping 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 indicate a corresponding file version of the program configuration file that supports running in the system platform corresponding to the plug-in to be generated; A processing module is used to instantiate the plug-in to be generated based on the program configuration parsing file to obtain a plug-in program corresponding to the plug-in to be generated, wherein the plug-in program is applied to the system platform.

12. A control device, characterized in that: include: at least one processor; and a memory communicatively coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the control device to execute the plug-in generation method according to any one of claims 1 to 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 comprises computer-executable instructions, and when the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the plug-in generation method according to any one of claims 1 to 10.

Images