Universal interface docking system, method, device and storage medium

Abstract

The present invention relates to a universal interface docking system, method, device and storage medium, the system comprising: an access layer, which is used to provide a universal and extensible access platform for all types of data, and provide it externally in the form of a standard interface; an engine layer, which is used to access data, parse, merge, transmit and manage data; a visual configuration layer, which is used to create nodes, link nodes and edit nodes, and complete the development of interface configuration; a basic application capability layer, which is used to parse, convert and flow message data by accessing the configuration information of engine information to form a data flow service; a platform service layer, which is used to generate services for configured rules and engine information; and a user layer, which is used to access user access and complete interaction with user operations. The present invention reduces the access time of software, hardware and database, and greatly reduces the cost of establishing and maintaining data processing and data links.

Description

Technical Field

[0001] The present invention relates to the technical field of universal interface docking, and in particular to a universal interface docking system, method, device and storage medium. Background Art

[0002] The existing interface docking methods generally use code access, which is not conducive to maintenance and modification. They also have poor perception of system changes and interface stability and require special operation and maintenance intervention. They are also relatively loose overall and highly dependent on the ability of coders. They are easily affected by staff resignation and job changes, resulting in data knowledge loss. Summary of the invention

[0003] The purpose of the present invention is to overcome the deficiencies of the prior art and provide a universal interface docking system, method, device and storage medium.

[0004] In order to solve the above technical problems, the present invention adopts the following technical solutions:

[0005] Universal interface docking system, including: access layer, engine layer, visualization configuration layer, basic application capability layer, platform service layer and user layer;

[0006] The access layer is used to provide a universal and scalable access platform for all types of data and provide it to the outside in the form of a standard interface;

[0007] The engine layer is used to access data, analyze, merge, transmit and manage data;

[0008] The visual configuration layer is used for creating nodes, linking nodes, and editing nodes to complete the development of interface configuration;

[0009] The basic application capability layer is used to parse, convert and transfer message data by accessing the configuration information of the engine information to form a data flow service;

[0010] The platform service layer is used to generate services based on the configured rules and engine information;

[0011] The user layer is used to access user access and complete interaction with user operations.

[0012] Its further technical solution is: the access layer is also used to collect subsequent data, and the access layer and the engine layer are connected through rule numbers; when the access layer collects the data, it verifies the data and forwards the data to the engine layer.

[0013] Its further technical solution is: the engine layer includes a hardware device access engine, a software platform access engine, a data source access engine and an interface management engine;

[0014] The hardware device access engine is used to support binary protocols and general general protocols, and complete the rapid access of data through the configuration and analysis of corresponding protocol nodes;

[0015] The software platform access engine is used to complete the input and output of the protocol, and complete the data parsing by formulating the protocol endpoints, protocol interfaces, protocol data formats and protocol version information;

[0016] The data source access engine is used to access the database, support online editing of query statements and input into the software platform, and also support merging and transmitting database content downward;

[0017] The interface management engine is used to support the output of the source of dynamic configuration data, the request frequency of the configuration interface, the alarm mechanism of the configuration interface, and provide a status management log, a log management entry and an audit management entry.

[0018] Its further technical solution is: the visual configuration layer is also used to support online low-code programming and support real-time online deployment.

[0019] The universal interface docking method, based on the universal interface docking system as described above, comprises the following steps:

[0020] Sort out the acquired business interfaces and data to obtain sorted documents;

[0021] According to the sorted documents, define the business interface fields and data fields to obtain the definition document;

[0022] According to the definition document, set the start node, process node and end node;

[0023] Trigger the start node to start the process test until the end node is completed to obtain the process interface;

[0024] Publish the process interface.

[0025] A further technical solution is: in the step of combing the acquired business interfaces and data to obtain combed documents, the business interfaces and data are classified and combed according to business types or topics to obtain combed documents.

[0026] Its further technical solution is: according to the definition document, in the steps of setting the start node, process node and end node, setting the start node includes creating the start node, setting the node's input parameter name, parameter type and process variable.

[0027] Its further technical solution is: according to the definition document, in the steps of setting the start node, process node and end node, setting the process node means processing the business interface or data table, adding script nodes or function nodes or network nodes.

[0028] A universal interface docking device, the universal interface docking device comprises a memory and a processor, the memory stores a computer program, and the processor implements the universal interface docking method as described above when executing the computer program.

[0029] A storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a processor, the universal interface docking method as described above can be implemented.

[0030] Compared with the prior art, the beneficial effects of the present invention are as follows: by generalizing and simplifying the process of data interface development in the form of middleware, the access time of software, hardware and database is greatly reduced, the docking time is shorter than the traditional docking form, and the data flow monitoring and management of the interface also have an out-of-the-box processing method, which greatly reduces the cost of data processing, data link establishment and maintenance.

[0031] The present invention is further described below in conjunction with the accompanying drawings and specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0033] Figure 1 A schematic block diagram of a universal interface docking system provided by an embodiment of the present invention;

[0034] Figure 2 A schematic diagram of a flow chart of a universal interface docking method provided by an embodiment of the present invention;

[0035] Figure 3 A schematic block diagram of a universal interface docking device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0036] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0037] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0038] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0039] It should be further understood that the term "and / or" used in the present description and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0040] See also Figures 1 to 3 The specific embodiment shown, wherein please refer to Figure 1 As shown, the present invention discloses a universal interface docking system, including: an access layer 10, an engine layer 20, a visualization configuration layer 30, a basic application capability layer 40, a platform service layer 50 and a user layer 60;

[0041] The access layer 10 is used to provide a universal and scalable access platform for all types of data and provide it to the outside in the form of a standard interface;

[0042] Among them, all types of data include structured data, semi-structured data, real-time data, and unstructured data.

[0043] The access layer 10 is also used to collect subsequent data. The access layer 10 is connected to the engine layer 20 through rule numbers. After the access layer 10 collects the data, it verifies the data and forwards the data to the engine layer 20.

[0044] The engine layer 20 is used to access data, analyze, merge, transmit and manage data;

[0045] In this embodiment, the engine layer 20 includes a hardware device access engine 21, a software platform access engine 22, a data source access engine 23 and an interface management engine 24;

[0046] The hardware device access engine 21 is used to support binary protocols and general general protocols, and complete fast data access through the configuration and analysis of corresponding protocol nodes;

[0047] Among them, the hardware device access engine 21 is mainly used to support private binary protocols and general protocols based on FTP, and complete the rapid access of data through the configuration and analysis of corresponding protocol nodes; when the general logic cannot be met, the conversion from customized to general can be completed through a customized parser.

[0048] The software platform access engine 22 is used to complete the input and output of the protocol, and complete the data analysis by formulating the protocol endpoint, protocol interface, protocol data format and protocol version information;

[0049] The software platform access engine 22 generally completes the input and output of protocols for common HTTP, WebService, Socket and other nodes. The platform completes customized data analysis and online debugging by formulating information such as protocol endpoints, protocol interfaces, protocol data formats and protocol versions. A single-node system can support real-time transmission of 100,000-level data.

[0050] The data source access engine 23 is used to access the database, support online editing of query statements and input into the software platform, and also support merging and transmitting database content downward;

[0051] The data source access engine 23 is used to access a variety of commonly used relational databases and document databases, supports online editing of query statements and input into the platform, and also supports merging the contents of multiple databases and transmitting them downward.

[0052] The interface management engine 24 is used to support the output of the source of dynamic configuration data, the request frequency of the configuration interface, the alarm mechanism of the configuration interface, and provide a status management log, a log management entry and an audit management entry.

[0053] The visual configuration layer 30 is used for creating nodes, linking nodes and editing nodes, and completing the development of interface configuration;

[0054] Among them, the visual configuration layer is also used to support online low-code programming and real-time online deployment. This part mainly uses the online running characteristics and message queues of NodeJS for research and development.

[0055] The basic application capability layer 40 is used to parse, convert and transfer message data by accessing the configuration information of the engine information to form a data flow service;

[0056] Among them, the basic application capability layer 40 can also form a continuous and reliable data flow service to monitor and alarm data in real time.

[0057] The platform service layer 50 is used to generate services based on the configured rules and engine information;

[0058] Among them, the platform service layer 50 also supports data persistence, detection and alarm, etc. This part is mainly based on the microservice extension capabilities of SpringCloud.

[0059] The user layer 60 is used to access user access and complete interaction with user operations.

[0060] Among them, the system adopts NodeJS as the main engine development language, and uses the characteristics of the language to make the framework; Java language application is used as the overall microservice application framework, responsible for back-end service management, management portal, data management, etc.

[0061] The universal interface docking system of the present invention connects a large number of fully functional protocol nodes through a low-code platform, completes interface docking in the form of dragging and dropping and based on parsing language, and supports online modification, online deployment, online testing, and supports system process status management, process log management, process alarm management and process audit management and other functions to improve stability, ensuring long-term effective, continuous and stable access to data; simple and common docking protocols such as Http, Tcp, complex and rare protocols such as Bacnet, Socket, various PLC protocols, private binary protocols of various hardware, etc. can all be tested and accessed in real time through interactive exploration, reducing the cost of establishing and maintaining links.

[0062] See also Figure 2 As shown, the present invention also discloses a universal interface docking method, based on the universal interface docking system as described above, comprising the following steps:

[0063] S1, sort out the acquired business interfaces and data to obtain sorting documents;

[0064] Among them, in step S1, the business interfaces and data are classified and sorted according to business types or topics, and recorded in an Excel document to obtain a sorted document.

[0065] S2, based on the sorted documents, define the business interface fields and data fields to obtain a definition document;

[0066] In step S2, mapping between business interface fields and data fields or data tables is defined and recorded in an Excel document to obtain a definition document.

[0067] S3, according to the definition document, set the start node, process node and end node;

[0068] Among them, in step S3, setting the start node includes creating the start node, setting the node's input parameter name, parameter type and process variables; parameter types and process variables include string, number, Boolean value, JSON and other types; the start node can be divided into manual trigger node, passive trigger node and timed trigger node.

[0069] Among them, setting the process node means processing the business interface or data table. You can add script nodes such as Javascript, Python, SQL, etc., you can add function nodes such as switch, change, exec, etc., you can add network nodes such as mqtt, http, websocket, tcp, udp, etc.

[0070] If the end node is published via http, tcp, udp, mqtt, or websocket, you need to set the corresponding repsonse node in the last step of the process.

[0071] S4, trigger the start node and start the process test until the end node is completed to obtain the process interface;

[0072] Among them, the process is tested on the low-code platform by triggering the start node. Generally, the test process is mainly based on manual triggering of the process, and the logs can be viewed and debugged.

[0073] S5, publish the process interface.

[0074] Among them, when publishing a process on a low-code platform, if the process interface is a scheduled task, the process will be triggered at the set time; if the process interface is an interface process, interface calls can be provided to other platforms or systems.

[0075] The present invention generalizes and simplifies the process of data interface development in the form of middleware, greatly reducing the access time of software, hardware and database. The docking time is shorter than that of traditional docking forms, and the data flow monitoring and management of the interface also have an out-of-the-box processing method, which greatly reduces the cost of data processing, data link establishment and maintenance.

[0076] It should be noted that technicians in the relevant field can clearly understand that the specific implementation process of the above-mentioned universal interface docking system and each unit can refer to the corresponding description in the aforementioned method embodiment, and for the convenience and brevity of description, it will not be repeated here.

[0077] The above universal interface docking system can be implemented in the form of a computer program. The computer program can be used in Figure 3 The generic interface shown runs on the docking device.

[0078] See also Figure 3, Figure 3 : is a schematic block diagram of a universal interface docking device provided in an embodiment of the present application; the universal interface docking device 500 can be a terminal or a server, wherein the terminal can be an electronic device with communication functions such as a smart phone, a tablet computer, a laptop computer, a desktop computer, a personal digital assistant, and a wearable device. The server can be an independent server or a server cluster composed of multiple servers.

[0079] See also Figure 3 The universal interface docking device 500 includes a processor 502 , a memory and a network interface 505 connected via a system bus 501 , wherein the memory may include a non-volatile storage medium 503 and an internal memory 504 .

[0080] The non-volatile storage medium 503 can store an operating system 5031 and a computer program 5032. The computer program 5032 includes program instructions, and when the program instructions are executed, the processor 502 can execute the universal interface docking method.

[0081] The processor 502 is used to provide computing and control capabilities to support the operation of the entire universal interface docking device 500 .

[0082] The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can execute the universal interface docking method.

[0083] The network interface 505 is used to communicate with other devices over the network. Figure 3 The structure shown in the figure is merely a block diagram of a portion of the structure related to the solution of the present application, and does not constitute a limitation on the universal interface docking device 500 to which the solution of the present application is applied. The specific universal interface docking device 500 may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0084] It should be understood that in the embodiment of the present application, the processor 502 may be a central processing unit (CPU), and the processor 502 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0085] It can be understood by those skilled in the art that all or part of the processes in the method for implementing the above embodiment can be completed by instructing the relevant hardware through a computer program. The computer program includes program instructions, and the computer program can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiment of the above method.

[0086] Therefore, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium. The storage medium stores a computer program, wherein the computer program includes program instructions, and the program instructions can implement the above-mentioned universal interface docking method when executed by a processor.

[0087] The storage medium may be a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disk, etc., which are computer-readable storage media that can store program codes.

[0088] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0089] In the several embodiments provided by the present invention, 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 each unit is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0090] The steps in the method of the embodiment of the present invention can be adjusted in order, combined and deleted according to actual needs. The units in the device of the embodiment of the present invention can be combined, divided and deleted according to actual needs. In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0091] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a universal interface docking device (which can be a personal computer, terminal, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention.

[0092] The above embodiments are preferred implementation schemes of the present invention. In addition, the present invention may also be implemented in other ways. Any obvious replacement without departing from the concept of the present technical solution is within the protection scope of the present invention.

Claims

1. Universal interface docking system, characterized in that: include: Access layer, engine layer, visualization configuration layer, basic application capability layer, platform service layer and user layer; The access layer is used to provide a universal and scalable access platform for all types of data and provide it to the outside in the form of a standard interface; The engine layer is used to access data, analyze, merge, transmit and manage data; The visual configuration layer is used for creating nodes, linking nodes, and editing nodes to complete the development of interface configuration; The basic application capability layer is used to parse, convert and transfer message data by accessing the configuration information of the engine information to form a data flow service; The platform service layer is used to generate services based on the configured rules and engine information; The user layer is used to access user access and complete interaction with user operations; The engine layer includes a hardware device access engine, a software platform access engine, a data source access engine and an interface management engine; The hardware device access engine is used to support binary protocols and general protocols, and complete fast data access through the configuration and analysis of corresponding protocol nodes; The software platform access engine is used to complete the input and output of the protocol, and complete the data parsing by formulating the protocol endpoints, protocol interfaces, protocol data formats and protocol version information; The data source access engine is used to access the database, support online editing of query statements and input into the software platform, and also support merging and transmitting database content downward; The interface management engine is used to support the output of the source of dynamic configuration data, the request frequency of the configuration interface, the alarm mechanism of the configuration interface, and provide a status management log, a log management entry and an audit management entry.

2. The universal interface docking system according to claim 1, characterized in that: The access layer is also used to collect subsequent data. The access layer and the engine layer are connected through rule numbers. After the access layer collects the data, it verifies the data and forwards the data to the engine layer.

3. The universal interface docking system according to claim 1, characterized in that: The visual configuration layer is also used to support online low-code programming and support real-time online deployment.

4. A universal interface docking method, characterized in that: The universal interface docking system according to any one of claims 1 to 3 comprises the following steps: Sort out the acquired business interfaces and data to obtain sorted documents; According to the sorted documents, define the business interface fields and data fields to obtain the definition document; According to the definition document, set the start node, process node and end node; Trigger the start node to start the process test until the end node is completed to obtain the process interface; Publish the process interface.

5. The universal interface docking method according to claim 4, characterized in that: In the step of combing the acquired business interfaces and data to obtain combed documents, the business interfaces and data are classified and combed according to business types or topics to obtain combed documents.

6. The universal interface docking method according to claim 4, characterized in that: According to the definition document, in the steps of setting the start node, process node and end node, setting the start node includes creating the start node, setting the input parameter name, parameter type and process variable of the node.

7. The universal interface docking method according to claim 4, characterized in that: According to the definition document, set the start node, process node and end node steps. Setting the process node means processing the business interface or data table, adding script nodes or function nodes or network nodes.

8. Universal interface docking device, characterized in that: The universal interface docking device includes a memory and a processor, the memory stores a computer program, and the processor implements the universal interface docking method according to any one of claims 4 to 7 when executing the computer program.

9. A storage medium, characterized in that: The storage medium stores a computer program, which includes program instructions. When the program instructions are executed by a processor, the universal interface docking method according to any one of claims 4 to 7 can be implemented.

Images