Heterogeneous system data interaction method and system, electronic equipment and storage medium

Abstract

The invention belongs to a data interaction method, and provides a heterogeneous system data interaction method and system, electronic equipment and a storage medium aiming at the technical problem of low data analysis efficiency when data interaction is carried out between different service subsystems in an electricity market. The data self-description interaction protocol comprises total data information, data structure information and data content information, and due to the fact that the data self-description interaction protocol can self-describe the structure and the content of the data, different service modules do not need to concern the internal data formats of each other in practical application, and the data self-description interaction protocol can be used for self-describing the structure and the content of the data. And the data is packaged and analyzed only according to the data self-description interaction protocol, so that the interoperability between the systems is greatly improved.

Description

Technical Field

[0001] The present application relates to a data interaction method, and specifically to a heterogeneous system data interaction method, system, electronic device and storage medium. Background Art

[0002] With the deepening of power market reform, the rapid development of new energy industry, and the rapid growth of installed capacity of renewable energy power generation such as wind power and photovoltaic power, these new energy power needs to participate in market transactions more widely to realize their economic value and social value. However, with the deepening of power market reform and the large-scale entry of new energy green electricity into the market, the business subsystems involved in the power system are gradually increasing, including power generation, transmission, distribution, sales and other links. A large amount of data interaction is required between various business subsystems to ensure the safe, stable and efficient operation of the power system. These data can include power data, electricity price data, load data, etc.

[0003] Different business subsystems may use different technology stacks, data structures, data formats, and data standards, resulting in technical difficulties and complexity in data analysis. Due to the differences between heterogeneous systems, the data analysis process often requires operations such as data format conversion, data cleaning, and data integration, which consume a lot of time and computing resources, resulting in low data analysis efficiency. Summary of the invention

[0004] The present application aims to solve the technical problem of low data parsing efficiency when data is interacted between different business subsystems in the power market, and provides a heterogeneous system data interaction method, system, electronic device and storage medium.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions: In a first aspect, the present application proposes a heterogeneous system data interaction method, comprising: The data sender encapsulates the data to be sent according to the data self-description interaction protocol to obtain encapsulated data; the data self-description interaction protocol includes data overall information, data structure information and data content information; Enables the encapsulated data to be exchanged to the data receiver; The data receiver can parse the received encapsulated data according to the data self-description interaction protocol.

[0006] Furthermore, the overall data information includes a data packet success identifier and a total number of records in the data packet.

[0007] Furthermore, the data content information includes data records organized in a row-column table, wherein each row corresponds to a data record and each column corresponds to a field.

[0008] Furthermore, the data structure information includes the English name of the field, the Chinese name of the field, the field type, the field length, and whether the field is a primary key.

[0009] Furthermore, the data source of the data sender includes a relationship library, tag data, file data and custom microservices.

[0010] Furthermore, the packaged data received by the data recipient are presented in forms including tables, scatter plots, maps, pie charts and curves.

[0011] In a second aspect, the present application proposes a heterogeneous system data interaction system, comprising: The encapsulation module is used to enable the data sender to encapsulate the data to be sent according to the data self-description interaction protocol to obtain encapsulated data; the data self-description interaction protocol includes data overall information, data structure information and data content information; An interaction module, used to interact the encapsulated data to a data receiver; The parsing module is used to enable the data receiver to parse the received encapsulated data according to the data self-description interaction protocol.

[0012] In a third aspect, the present application proposes an electronic device, comprising: a memory and one or more processors; the memory is coupled to the processor; wherein computer program code is stored in the memory, and the computer program code includes computer instructions, and when the computer instructions are executed by the processor, the electronic device performs the steps of the above-mentioned heterogeneous system data interaction method.

[0013] In a fourth aspect, the present application proposes a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned heterogeneous system data interaction method are implemented.

[0014] Compared with the prior art, this application has the following beneficial effects: The present application proposes a heterogeneous system data interaction method. When the data sender sends data, the data to be sent is first encapsulated according to the data self-description interaction protocol, wherein the data self-description interaction protocol includes data overall information, data structure information and data content information. Since the data self-description interaction protocol can self-describe the structure and content of the data, different business modules in actual applications do not need to care about each other's internal data format, and only need to encapsulate and parse the data according to the data self-description interaction protocol, thereby greatly improving the interoperability between systems. At the same time, the data self-description interaction protocol also enables the receiver to parse the data quickly and accurately, reducing the time for data conversion and processing, and improving the speed and efficiency of data processing.

[0015] The present application also proposes a heterogeneous system data interaction system, an electronic device and a computer storage medium, which have all the advantages of the above-mentioned heterogeneous system data interaction method. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0017] Figure 1 A flow chart of a heterogeneous system data interaction method of the present application; Figure 2 A schematic diagram of a data self-description interaction protocol in an embodiment of the present application; Figure 3 A schematic diagram of the heterogeneous system data interaction system of the present application. DETAILED DESCRIPTION

[0018] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0019] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0020] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0021] In the description of the embodiments of the present application, it should be noted that if the terms "upper", "lower", "horizontal", "inner", etc. appear, the orientation or position relationship indicated is based on the orientation or position relationship shown in the drawings, or the orientation or position relationship in which the invented product is usually placed when used. It is only for the convenience of describing the present application and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present application. In addition, the terms "first", "second", etc. are only used to distinguish the description, and cannot be understood as indicating or implying relative importance.

[0022] In addition, if the term "horizontal" appears, it does not mean that the component must be absolutely horizontal, but can be slightly tilted. For example, "horizontal" only means that its direction is more horizontal than "vertical", which does not mean that the structure must be completely horizontal, but can be slightly tilted.

[0023] In the description of the embodiments of the present application, it is also necessary to explain that, unless otherwise clearly specified and limited, the terms "set", "install", "connect", and "connect" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal connection of two components. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0024] With the large-scale entry of new energy and green electricity into the market, the demand for data interaction between various business subsystems has increased dramatically. However, due to the heterogeneity between systems, data parsing efficiency is often low, which has become a problem that needs to be solved urgently. Since these systems may use different technical architectures, data formats, and communication protocols, there is a heterogeneity problem in the data interaction process. This heterogeneity not only increases the complexity of data parsing, but also reduces the efficiency of data interaction. Specifically: (1) Inconsistent data formats: Different systems may use different data formats to store and transmit data, such as JSON, XML, CSV, etc. This increases the complexity of data parsing, and requires writing dedicated parsing code for each format.

[0025] (2) Incompatible communication protocols: Different systems may use different communication protocols for data transmission, such as HTTP, WebSocket, MQTT, etc. This results in the inability of direct communication between systems, and protocol conversion needs to be performed through middleware or gateways.

[0026] (3) Data quality is difficult to ensure: Due to the heterogeneity between systems, data may be lost, duplicated, or formatted incorrectly during transmission, affecting data quality and availability.

[0027] In order to meet the standardization and convenience of data interaction, it is necessary to design a set of self-describing data protocols that are adaptable to heterogeneous systems and realize self-describing parsing of interactive data packets between systems.

[0028] Based on the above situation, the present application proposes a heterogeneous system data interaction method, system, electronic device and storage medium. The present application is described in detail below in conjunction with embodiments and drawings.

[0029] like Figure 1 As shown, a heterogeneous system data interaction method of the present application may include: S101, enabling a data sender to encapsulate data to be sent according to a data self-description interaction protocol to obtain encapsulated data; the data self-description interaction protocol includes data overall information, data structure information and data content information.

[0030] It should be noted that the overall data information can usually include data size, data source, and data update frequency, etc. The specific content contained in the overall data information can be determined according to the specific application scenario. Among them, the data size is used to describe the size of the data set, such as how many records and variables it contains. For example, a data set may contain millions of records and involve dozens of variables. The data source is used to explain the source channel of the data, such as market research, experimental measurement, public database, etc. Different data sources may affect the accuracy and reliability of the data. The data update frequency can indicate how the data is updated over time, such as real-time update, daily update, weekly update, etc., which helps to understand the timeliness and freshness of the data.

[0031] For data structure information, the data sender needs to define the hierarchical structure and constituent elements of the data according to business requirements, such as field name, field type, field length, whether it is required, etc. This information will be embedded in the encapsulated data as data structure information. In practical applications, by adding metadata tags or nested structures, the data sender can clearly describe the overall framework of the data and the meaning of each field.

[0032] For data content information, after determining the data format and data structure, the data sender fills the actual business data into the corresponding fields, and these data constitute the data content information. In practical applications, the data sender can avoid errors during transmission or parsing by ensuring that the filled data conforms to the predefined data structure and type requirements.

[0033] When encapsulating the data to be sent, the data sender can use a predetermined encapsulation protocol (such as HTTP, WebSocket, etc.) to package the formatted data, data structure information, and data content information into a data packet. This data packet is the encapsulated data and will be sent to the data receiver. As an optimization solution, during the encapsulation process, the data sender can also consider the security of the data, such as encrypted transmission, access control, etc., to ensure that the data is not illegally intercepted or tampered with during transmission.

[0034] S102, exchanging the encapsulated data to a data receiver.

[0035] The data sender and receiver can choose the appropriate transmission method according to the actual situation. For example, for data with high real-time requirements, network transmission can be selected, such as transmission through the Internet or local area network. For data with large data volume or low transmission frequency, storage medium transmission can be selected.

[0036] In order to ensure reliable data transmission, the data sender and receiver can follow the same transmission protocol, including the format of the data packet, the transmission order, the error handling mechanism, etc. By complying with the transmission protocol, both parties can ensure that the data is not lost, duplicated or out of order during the transmission process.

[0037] In practical applications, the transmission process can also be monitored during data transmission, for example, including monitoring indicators such as data transmission speed, transmission success rate, error rate, etc. Through monitoring, both parties can promptly discover and solve problems that arise during the transmission process.

[0038] S103, enabling the data receiver to parse the received encapsulated data according to the data self-description interaction protocol.

[0039] When the data receiver parses the received encapsulated data, it first reads the metadata tags in the encapsulated data to understand the format, encoding method, time format and other information of the data, which is part of the data self-description. Based on the overall information of the data read, the data receiver can ensure that the subsequent data parsing process complies with the predetermined rules and requirements. For example, the correct parsing tool or library is selected to parse the data in a specific format. Then, the data receiver continues to read the metadata tags or nested structures in the encapsulated data to obtain the hierarchical structure and component element information of the data, which describes the overall framework of the data and the meaning of each field. By parsing the data structure information, the data receiver can build the same data model or object structure as the sender, which helps to ensure that subsequent data processing or storage operations can be carried out correctly. After understanding the overall structure of the data and the meaning of each field, the data receiver begins to parse the data values ​​actually transmitted, which constitute the data content information. The data receiver needs to correctly map the received data values ​​to the corresponding fields according to the field definitions in the data structure information. At the same time, the data needs to be verified and error-handled to ensure the accuracy and integrity of the data.

[0040] After parsing is completed, the data recipient can use the parsed business data objects for subsequent business processing or storage operations, such as storing the data in a database, performing data analysis or mining, and displaying the data to users.

[0041] In this application, since all business modules follow the same protocol for data encapsulation and parsing, seamless data exchange can be achieved between them without caring about how the other party stores or processes the data. This decoupling greatly enhances the scalability and flexibility of the system. New modules can be easily integrated into existing systems without a lot of modifications or adjustments to the existing systems. Each module only needs to focus on its own data generation and consumption without having to care about the specific implementation of other modules, thereby reducing the coupling degree of the system. The uniformity of the protocol also brings about the universality of data interaction. No matter which business module the data is generated in, as long as it meets the requirements of the protocol, it can be understood and processed by any other module that follows the protocol. This universality greatly simplifies the flow and conversion process of data between different systems or modules. Furthermore, due to the strict definition of the protocol, the data carries all the necessary information during the transmission process to allow the recipient to accurately parse and understand it. This ability enables the recipient to guide the data parsing process without additional metadata or documents, thereby greatly reducing the time for data conversion and processing. The recipient can start processing immediately after receiving the data without complex data format conversion or verification, which not only reduces the delay of data processing, but also improves the accuracy and efficiency of data processing. In addition, since all modules use the same data structure and semantics, the flow of data in the system becomes smoother and more efficient. In addition, the design of the protocol takes into account future scalability, and new business modules or data fields can be easily added to the system without affecting existing modules and data interactions. Data self-describing interaction protocols also help improve the readability and ease of use of data, and can provide a more friendly and intuitive data display interface for front-end users.

[0042] like Figure 2 As shown, it is a schematic diagram of the data self-describing interaction protocol in this application, which may include data overall information, data structure information and data content information.

[0043] The overall data information includes the data success flag, total number of records, data structure, and data. It should be noted that the data success flag is a flag used to indicate whether the data transmission is successful. It can be a simple Boolean value (such as true for success and false for failure) or a more complex status code or message to describe the specific results of the data transmission. When the transmitted data contains multiple records, the total number of records can tell the receiver how many data records are included in this transmission, and the receiver can verify whether the expected amount of data has been received. The overall data information includes the data structure and the overall situation of the data.

[0044] Data structure information can include the English name of the field, the Chinese name of the field, the field type, the field length, and whether it is a primary key. Among them, the English name of the field is usually used for identification in programming and data processing. It is unique and unchanged, and is used to ensure consistency when exchanging data between different systems or modules. The Chinese name of the field is used to provide more intuitive and easy-to-understand information, which is more useful for non-technical personnel or systems that require a Chinese interface. Field types, such as integers, floating-point numbers, strings, dates, Boolean values, etc., determine the form and range of values ​​that can be stored in the data. The length of the field usually refers to the maximum length of the data that the field can store. For example, for a string type field, the maximum number of characters that can be stored is defined. For other types of fields, the length may refer to the size or precision of the data. Whether it is a primary key is represented by a Boolean value, indicating whether the field is used as the primary key of a data table or data set. The primary key is unique and is used to uniquely identify each row in a data table or each record in a data set.

[0045] Data content information is the core part of the data packet, which is organized in a two-dimensional table structure, with each field corresponding to a column and each record corresponding to a row. The English name, Chinese name, type, length and other attribute information of the field are usually defined in the data structure information, while in the data content information, the main focus is on the value of the field. Each record (or data row) is an independent entity in the data table, containing the values ​​of all fields of the entity. Records are distinguished by rows, and each row represents a unique data instance. The two-dimensional data content information can be easily exchanged and shared between different systems or modules. By defining a unified data structure and format, different systems can seamlessly parse and process the data sent to each other. The specification contains information such as data validity flags, field types and lengths, which helps the receiver to verify the data and ensure the integrity and accuracy of the data.

[0046] The data self-description interaction protocol in this application can easily adapt to the data requirements of different business modules, support multiple data interaction methods, and realize unified data transmission and data analysis. It improves the efficiency of data transmission and data analysis, ensures the consistency and accuracy of data, reduces the coupling between systems, and enhances the scalability and maintainability of the system.

[0047] The application scope of this application is wide. For the data sender, the data source includes relational library, label data, file data and custom microservices, etc. Among them, the relational library is a database built based on the relational model, which usually uses tables to store data, and the tables can establish relationships through foreign keys. The data sender can query data from the relational library and then send the query results as part of the data packet to the receiver. Label data usually refers to information with metadata or labels, which provide additional context or description about the data. The data sender can collect, organize and send the labeled data so that the receiver can better understand and use the data. File data is information stored in files, which can be text files, CSV files, Excel files, JSON files, XML files, etc. The data sender can read data from the file and then encapsulate it into a data packet and send it to the receiver. Custom microservices are small, independent services built specifically to implement specific functions or business logic. The data sender can obtain data by calling the API of the custom microservice and send it to the receiver as part of the data packet.

[0048] As a specific example of this application, the relational database may include MySql, Dm, Oracle, OceanBase, Drds, etc. The label data may be three-field labels, four-field labels, statistical analysis results, and table labels, etc. The file data may be Excel data. The custom microservice may be an existing interface conversion, a new R&D interface adaptation, etc.

[0049] At the same time, the data receiving party can receive encapsulated data in the form of tables, scatter plots, maps, pie charts and curves, which facilitates a more intuitive understanding and analysis of the data.

[0050] The protocol designed in this application can adapt to a variety of data interaction methods, including but not limited to databases, message queues, microservice API interfaces, etc., so that the system can be seamlessly connected between different technology stacks. Through the standardization of the protocol, the developers' repeated development work for data interfaces can be reduced, while simplifying the modification and debugging of data interaction modules during system maintenance and upgrades. This application can not only improve the data interaction efficiency of the power trading system, but also enhance the stability and reliability of the system, providing a more efficient, secure and convenient data exchange platform for participants in the power market.

[0051] like Figure 3 As shown, it is a schematic diagram of the heterogeneous system data interaction system of the present application, which may include: The encapsulation module is used to enable the data sender to encapsulate the data to be sent according to the data self-description interaction protocol to obtain encapsulated data; the data self-description interaction protocol includes data overall information, data structure information and data content information; An interaction module, used to interact the encapsulated data to a data receiver; The parsing module is used to enable the data receiver to parse the received encapsulated data according to the data self-description interaction protocol.

[0052] In some embodiments of the heterogeneous system data interaction system of the present application, when the encapsulation module encapsulates the data to be sent, the overall data information includes a data packet success identifier and a total number of records in the data packet in the data self-description interaction protocol.

[0053] In some embodiments of the heterogeneous system data interaction system of the present application, when the encapsulation module encapsulates the data to be sent, the data content information includes data records organized in a row and column table based on the data self-description interaction protocol, wherein each row corresponds to a data record and each column corresponds to a field.

[0054] In some embodiments of the heterogeneous system data interaction system of the present application, when the encapsulation module encapsulates the data to be sent, the data structure information includes the English name of the field, the Chinese name of the field, the field type, the field length and whether the field is the primary key in the data self-description interaction protocol.

[0055] In some embodiments of the heterogeneous system data interaction system of the present application, the data source serving as the data sender in the encapsulation module includes a relationship library, label data, file data, and a custom microservice.

[0056] In some embodiments of the heterogeneous system data interaction system of the present application, the packaged data presentation forms received by the interaction module as a data receiver include tables, scatter points, maps, pie charts and curves.

[0057] It should be noted that in the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the system embodiments described above are merely schematic. For example, the division of each module is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules can be combined or integrated into another device, or some features can be ignored or not executed. The module described as a separate component may or may not be physically separated. The component displayed as a module may be a physical unit or multiple physical units, that is, it may be located in one place, or it may be distributed in multiple different places. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0058] In addition, each module in each embodiment of the present invention may be integrated into a processing unit, each module may exist physically separately, or two or more modules may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0059] An embodiment of the present application also provides an electronic device, which may include one or more processors, a memory, and a communication interface.

[0060] The memory, the communication interface and the processor are coupled, for example, the memory, the communication interface and the processor may be coupled together via a bus.

[0061] The communication interface is used for data transmission with other devices. The memory stores computer program code. The computer program code includes computer instructions, and when the computer instructions are executed by the processor, the electronic device executes the steps of the heterogeneous system data interaction method.

[0062] Wherein, the processor can be a processor or a controller, for example, a central processing unit (CPU), a general processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the present disclosure. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of DSP and microprocessors, and the like. The processor can be used to support electronic devices to execute the method steps provided in the above embodiments.

[0063] The bus may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The above bus may be divided into an address bus, a data bus, a control bus, etc.

[0064] An embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned heterogeneous system data interaction method are implemented.

[0065] The computer-readable storage medium involved in the present application includes random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the technical field.

[0066] For the description of the relevant parts of the heterogeneous system data interaction system, electronic device and computer-readable storage medium provided in the embodiments of the present application, please refer to the detailed description of the corresponding parts in the heterogeneous system data interaction method provided in the embodiments of the present application, and will not be repeated here.

[0067] The above are only preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A heterogeneous system data interaction method, characterized in that: include: The data sender encapsulates the data to be sent according to the data self-description interaction protocol to obtain encapsulated data; The data self-description interaction protocol includes data overall information, data structure information and data content information; Enables the encapsulated data to be exchanged to the data receiver; The data receiver can parse the received encapsulated data according to the data self-description interaction protocol.

2. The heterogeneous system data interaction method according to claim 1, characterized in that: The overall data information includes a data packet success identifier and a total number of records in the data packet.

3. The heterogeneous system data interaction method according to claim 1, characterized in that: The data content information includes data records organized in a row-column table, wherein each row corresponds to a data record and each column corresponds to a field.

4. The heterogeneous system data interaction method according to claim 1, characterized in that: The data structure information includes the English name of the field, the Chinese name of the field, the field type, the field length, and whether the field is a primary key.

5. The heterogeneous system data interaction method according to claim 1, characterized in that: The data sources of the data sender include relationship libraries, tag data, file data, and custom microservices.

6. The heterogeneous system data interaction method according to claim 1, characterized in that: The packaged data received by the data receiver may be presented in the form of tables, scatter plots, maps, pie charts and curves.

7. A heterogeneous system data interaction system, characterized in that: include: The encapsulation module is used to enable the data sender to encapsulate the data to be sent according to the data self-description interaction protocol to obtain encapsulated data; The data self-description interaction protocol includes data overall information, data structure information and data content information; An interaction module, used to interact the encapsulated data to a data receiver; The parsing module is used to enable the data receiver to parse the received encapsulated data according to the data self-description interaction protocol.

8. The heterogeneous system data interaction method according to claim 7, characterized in that: When the encapsulation module encapsulates the data to be sent, the overall data information includes a data packet success identifier and a total number of records in the data packet in the data packet according to the data self-description interaction protocol.

9. The heterogeneous system data interaction method according to claim 1, characterized in that: When the encapsulation module encapsulates the data to be sent, the data content information includes data records organized in a row-column table in accordance with the data self-description interaction protocol, wherein each row corresponds to a data record and each column corresponds to a field.

10. The heterogeneous system data interaction method according to claim 1, characterized in that: When the encapsulation module encapsulates the data to be sent, the data structure information includes the English name of the field, the Chinese name of the field, the field type, the field length and whether the field is a primary key in the data self-description interaction protocol.

11. The heterogeneous system data interaction method according to claim 1, characterized in that: The data sources serving as data senders in the encapsulation module include relationship libraries, tag data, file data, and custom microservices.

12. The heterogeneous system data interaction method according to claim 1, characterized in that: The packaged data received by the interactive module as a data receiver may be presented in the form of tables, scatter points, maps, pie charts and curves.

13. An electronic device, characterized in that: include: A memory and one or more processors; the memory is coupled to the processor; wherein the memory stores computer program code, the computer program code includes computer instructions, and when the computer instructions are executed by the processor, the electronic device executes the steps of the heterogeneous system data interaction method as described in any one of claims 1-6.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the heterogeneous system data interaction method according to any one of claims 1 to 6 are implemented.

Images