Data bridge, data communication method and system based on data bridge

Abstract

The application discloses a data bridge, a data communication method and system based on the data bridge. The method comprises the following steps: a sending end packs to-be-sent data into metadata, wherein the metadata comprises an information type and to-be-sent information; the data bridge receives the metadata from the sending end through a communication port, analyzes the metadata to identify the information type of the metadata, and performs a conversion operation on the to-be-sent information according to a pre-configured information conversion rule and the information type, and then sends the converted information back to the communication port; and a receiving end acquires required information through the communication port and makes a response. Through the application, efficient data communication between heterogeneous modules can be realized, so that rapid integration of a large software system is realized.

Description

Technical Field

[0001] This invention relates to the field of petroleum geophysical exploration technology, specifically to a data bridge, a data communication method and system based on the data bridge. Background Technology

[0002] Geophysical exploration software is characterized by numerous resources, complex application logic, and access to massive amounts of data, thus requiring a scalable and highly open software architecture and integration platform. Common integration models include source code-level integration, plug-in integration, and integration through data exchange between modules via databases, file systems, and network interfaces. However, as is well known, a large software project often consists of a series of different functional modules forming a complete business process, requiring collaborative development by dozens or even hundreds of people. If a source code-level integration model is adopted, every small change will lead to the recompilation and deployment of the entire system, which is time-consuming, labor-intensive, and difficult to test and maintain. At the same time, the software will integrate functional modules provided by different vendors. These modules have different business processes, data models, and software architectures. Regardless of the integration model adopted, functional integration and interface reconstruction are required, which is not only time-consuming and costly but also a tortuous process. Existing systems mostly adopt a data exchange-based integration model, which allows for smooth data exchange and interactive control within modules, but information exchange between modules is quite limited. Without good concurrency control and synchronization processing, irreversible damage or impact on data can occur. Therefore, it is necessary to explore an integration technology suitable for large or heterogeneous software systems to eliminate the silo effect between modules and applications and achieve seamless connection and integrated application of the entire system.

[0003] However, there is currently no integration technology suitable for large or heterogeneous software systems. Summary of the Invention

[0004] In view of this, the present invention provides a data bridge, a data communication method and system based on the data bridge, to solve at least one of the aforementioned problems.

[0005] According to a first aspect of the present invention, a data communication method based on a data bridge is provided, the method comprising:

[0006] The communication port receives metadata from the sender, including: information type and information to be sent;

[0007] The metadata is parsed to identify the information type of the metadata, and the information to be sent is converted according to the pre-configured information conversion rules and the information type.

[0008] The converted information is sent to the communication port so that the corresponding receiving end can obtain the required information through the communication port.

[0009] According to a second aspect of the present invention, a data bridge is provided, the data bridge comprising:

[0010] The receiving unit is used to receive metadata from the sending end through a communication port. The metadata includes: information type and information to be sent.

[0011] The parsing unit is used to parse the metadata to identify the information type of the metadata;

[0012] A conversion unit is used to convert the information to be sent according to pre-configured information conversion rules and the information type;

[0013] The transmitting unit is used to send the converted information to the communication port so that the corresponding receiving end can obtain the required information through the communication port.

[0014] According to a third aspect of the present invention, a data communication system based on a data bridge is provided. The system includes: the aforementioned data bridge, a receiver, a transmitter, and a communication port, wherein the transmitter sends metadata to the communication port, the data bridge listens to the communication port and obtains the metadata, the data bridge sends converted metadata to the communication port, and the transmitter listens to the communication port and obtains the required data.

[0015] According to a fourth aspect of the present invention, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the above-described method.

[0016] According to a fifth aspect of the present invention, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method.

[0017] As can be seen from the above technical solution, metadata from the sending end is received through the communication port, and then the metadata is parsed to identify the information type, so that the information to be sent can be converted according to the information type and information conversion rules. After that, the converted information is sent to the communication port so that the corresponding receiving end can obtain the required information through the communication port. In this way, efficient data communication between heterogeneous modules can be achieved. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a structural block diagram of a data communication system based on a data bridge according to an embodiment of the present invention;

[0020] Figure 2 This is a structural block diagram of the data bridge 1 according to an embodiment of the present invention;

[0021] Figure 3 This is an example architecture diagram of a software integration scheme based on a data bridge according to an embodiment of the present invention;

[0022] Figure 4 This is a schematic diagram illustrating the expansion of system functional modules according to an embodiment of the present invention;

[0023] Figure 5 This is a schematic diagram illustrating the interaction and synchronization between functional modules according to an embodiment of the present invention;

[0024] Figure 6 This is a schematic diagram of data conversion between heterogeneous software according to an embodiment of the present invention;

[0025] Figure 7 Based on the embodiments of the present invention Figure 3 The example system architecture shown is a schematic diagram illustrating its working principle.

[0026] Figure 8 This is a flowchart illustrating the synchronous update and access of large amounts of data between modules according to an embodiment of the present invention.

[0027] Figure 9 It is a base map display of the work area data;

[0028] Figure 10 This is a seismic profile diagram according to an embodiment of the present invention;

[0029] Figure 11 This is the image displayed by the seismic attribute cross-analysis module;

[0030] Figure 12 The image is displayed by the attribute profile display module according to an embodiment of the present invention;

[0031] Figure 13 The image is displayed by the attribute plane display module according to an embodiment of the present invention;

[0032] Figure 14The image is displayed by the attribute three-dimensional display module according to an embodiment of the present invention;

[0033] Figure 15 This is a flowchart of a data communication method based on a data bridge according to an embodiment of the present invention;

[0034] Figure 16 This is a detailed flowchart of a data communication method based on a data bridge according to an embodiment of the present invention;

[0035] Figure 17 This is a schematic block diagram illustrating the system configuration of an electronic device 600 according to an embodiment of the present invention. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0037] Existing petroleum geophysical exploration software systems mostly adopt an integration model based on data exchange. While data exchange and interactive control within modules are smooth, information exchange between modules is quite limited. Without proper concurrency control and synchronization, irreversible damage or impact on data can occur. Therefore, there is a need to explore an integration technology suitable for large or heterogeneous software systems to eliminate the silo effect between modules and applications, achieving seamless integration and unified application of the entire system. However, currently, there is no suitable integration technology for large or heterogeneous software systems.

[0038] Based on this, embodiments of the present invention provide a data communication scheme based on a data bridge. This scheme is suitable for the integration technology of large-scale or heterogeneous software systems, and can eliminate the silo effect between modules and applications, achieving seamless connection and integrated application of the entire system. This scheme can solve the problem of efficient integration between large-scale geophysical software or heterogeneous software modules, while also addressing the problems of complex interfaces, system expansion, and maintenance difficulties associated with other integration methods. The embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0039] Figure 1 This is a structural block diagram of a data communication system based on a data bridge according to an embodiment of the present invention, such as... Figure 1As shown, the system includes: a data bridge 1, a receiver 2 (e.g., a functional module), a transmitter 3 (e.g., a functional module), and a communication port 4. The transmitter packages the information to be sent into metadata and sends it to the communication port. The data bridge listens to the communication port and obtains the metadata. The data bridge sends the converted metadata to the communication port. The transmitter listens to the communication port and obtains the required data.

[0040] Figure 2 This is a block diagram of data bridge 1, as shown below. Figure 2 As shown, the data bridge 1 includes: a receiving unit 11, a parsing unit 12, a conversion unit 13, and a transmitting unit 14, wherein:

[0041] The receiving unit 11 is used to receive metadata from the sending end through the communication port. The metadata includes: information type and information to be sent.

[0042] In practice, metadata can also include: receiver information and sender information.

[0043] The parsing unit 12 is used to parse the metadata to identify the information type of the metadata.

[0044] The conversion unit 13 is used to perform conversion operations on the information to be sent according to the pre-configured information conversion rules and the information type.

[0045] The information conversion rules here can be pre-configured classification, hierarchical, and grouping information of communication information, which are used by the conversion unit to convert the received metadata.

[0046] The sending unit 14 is used to send the converted information to the communication port so that the corresponding receiving end can obtain the required information through the communication port.

[0047] In one embodiment, when the information type is synchronous operation, the sending unit broadcasts the converted information to the communication port.

[0048] The receiving unit 11 receives metadata from the sending end based on the communication port. Then, the parsing unit 12 parses the metadata to identify the information type, so that the conversion unit 13 can perform conversion operations on the information to be sent according to the information type and information conversion rules. After that, the sending unit 14 sends the converted information to the communication port so that the corresponding receiving end can obtain the required information through the communication port. In this way, efficient data communication between heterogeneous modules can be achieved.

[0049] In actual operation, the above-mentioned data bridge 1 further includes: a channel establishment unit and a monitoring unit, wherein: the channel establishment unit is used to establish a full-duplex communication channel with the sending end and the receiving end for data transmission; the monitoring unit is used to periodically monitor the communication port to obtain data from the sending end.

[0050] To better understand this invention, the following is combined with... Figure 3 The system architecture shown is used to describe the embodiments of the present invention in detail.

[0051] like Figure 3 As shown, the architecture includes: a main control program module, a data bridge, and multiple modules (i.e., functional modules), among which:

[0052] The main control program module is responsible for configuring information classification, hierarchical and grouped information, as well as starting the data bridge and various functional modules;

[0053] A data bridge (with a data service program) is responsible for receiving, converting, packaging and sending information or data. It acts as a data transmission and communication bridge between modules, connecting the entire system into an organic and collaborative whole.

[0054] Each functional module that needs to communicate and transmit data has a communication management component (which can be called a communication program client), which is responsible for listening to the channel and completing communication and data exchange with the data bridge.

[0055] In one embodiment, the communication program client, embedded in each functional module, is used to listen to the data communication channel, receive information from the server, and perform corresponding operations or discard the received data according to the information type and level.

[0056] In practical implementation, the data bridge is also responsible for managing the communication channels (shown as channels in the diagram) that connect to each module. These communication channels can be implemented using named pipes, network sockets, or other local communication methods. Listening to the communication ports can be done by setting a timer.

[0057] In this embodiment of the invention, a broadcast information communication mode is adopted. The interface logic between the main control program module and each module and the data bridge is relatively simple. Especially for heterogeneous systems, the application program does not need to be modified on a large scale. In this way, a lot of time and labor costs can be saved for the integration of large software systems.

[0058] The software system integrated using the embodiments of this invention has high system scalability and good maintainability. During later maintenance and upgrades, new integrated modules only require expansion of communication information and data types and reconstruction of communication interfaces. The following describes... Figure 4The flowchart shown describes the process of expanding functional modules.

[0059] like Figure 4 As shown, the system functional module expansion process includes the following steps:

[0060] (1) Define the message or data type that the new module will transmit;

[0061] (2) Add data packaging, sending, receiving and response functions to the new module;

[0062] (3) Add communication channel management function with data bridge;

[0063] (4) Place the new module into the system and start or call it by the main control program module.

[0064] In practical implementation, the channel management, information, and data transmission programs from each module can be extracted to form a shared library. When integrating new or optimized modules, only minor expansions or modifications to this library are needed, and the library can be linked during module compilation, thereby further improving integration efficiency.

[0065] Figure 5 This is a schematic diagram of the interaction and synchronization between functional modules according to an embodiment of the present invention, such as... Figure 5 As shown, the process includes:

[0066] (1) Module 1 packages the information that needs to be synchronized and sends it to the data bridge through the communication port;

[0067] (2) The data bridge receives information and broadcasts it.

[0068] (3) Module 2 listens to the communication port and recognizes that it is a module that needs to be synchronized, then receives the information and responds.

[0069] Figure 6 This is a schematic diagram of data conversion between heterogeneous software according to an embodiment of the present invention, such as... Figure 6 As shown, the process includes:

[0070] (1) Module 1 packages the data to be transmitted into metadata format and sends it to the data bridge through the communication port;

[0071] (2) The data bridge listens to the communication port to detect information, identifies the information, obtains the sender, receiver, data type and conversion relationship, and after converting the data, sends it back through the communication port;

[0072] (3) Module 2 listens to the communication port and finds that it is the receiver. Then it receives the data, converts the data from the metadata format to the format it needs, and processes the data.

[0073] Through this process, each functional module only needs to process the data relevant to itself, while the data bridge handles a large amount of data format conversion, thus separating the communication function from the business processing module and reducing the complexity of the functional modules.

[0074] Figure 7 Based on Figure 3 The system architecture shown is a working principle diagram, as follows: Figure 7 As shown, the workflow of this system includes:

[0075] Step 701: The main control program module configures the hierarchical and grouping information of communication information and transmitted data, and saves it as an XML file.

[0076] In one embodiment, during installation, deployment, or initial startup, the main control module categorizes system communication data based on the data exchange type and call relationship between modules, and manages the communication data hierarchically and in groups according to the call and collaboration relationships between services. The categorization, hierarchical, and grouping information is stored in an external XML file (corresponding to the information conversion rules in the aforementioned conversion unit 13).

[0077] Step 702: The main control program module starts the main control program and the data bridge.

[0078] Step 703: After the data bridge starts, it automatically establishes a full-duplex communication channel and keeps listening to the communication port.

[0079] Step 704: The main control program starts each functional module.

[0080] Step 705: When the functional module starts, it loads the communication information hierarchy and grouping information, establishes a connection with the data bridge, and keeps listening to the communication port.

[0081] Step 706: When modules need to interact, synchronize, or transfer data, the sending module encapsulates and packages the information into metadata format and sends it to the communication port.

[0082] Step 707: When the data bridge detects new information or data being transmitted, it reads from the communication port, parses the header to obtain the sender, receiver, information type, and type to be converted. After converting the information or data, the data bridge sends it back to the communication port.

[0083] In one embodiment, the data bridge uses a timer or other synchronization measures to synchronize and concurrently process the sending and receiving of information.

[0084] Step 708: If other modules detect new information or data being transmitted through the communication port, they will first read the header information.

[0085] In one embodiment, each functional module provides a connection interface and communication component to the channel provided by the data bridge. This communication component reads the communication data classification, hierarchical, and grouping information stored in the aforementioned XML file when the module starts.

[0086] Step 709: Determine if you are the receiver. If not, proceed to step 710; otherwise, proceed to step 711.

[0087] In step 710, modules that are not the receiver will automatically discard the information and will not respond.

[0088] Step 711: The receiver reads the information or data, processes it according to the type of information or data, and responds.

[0089] Specifically, the receiver extracts the header data and filters, receives, processes, and responds to the received data based on classification and grouping information.

[0090] Step 712: Each module continues to listen to the communication port.

[0091] During system operation, steps 706-712 are repeated to achieve interactive synchronization, data transmission, and collaborative operation of the entire system.

[0092] This invention, through the construction of a data communication service program, acts as a data bridge between different or heterogeneous modules of large-scale geophysical exploration software. It establishes full-duplex channels between the main program and functional modules, and between modules themselves, enabling data conversion and real-time interaction. Since each module is only responsible for sending its own data and receiving data relevant to itself, the interfaces between modules are relatively simple, and there is no need for extensive modifications to the original program architecture and data structure. The integration workload is mainly concentrated on the data server side, thus enabling rapid integration of large-scale geophysical exploration software systems or heterogeneous software modules. Furthermore, as the software scales up, only minor modifications to the data bridge and data communication interface are needed by expanding the classification, hierarchical, and grouping information of the communication data through the main control program, without requiring extensive modifications to the data model, program structure, and access interfaces of the main control program and functional modules. This results in an integrated software system with excellent scalability and interactive performance, and also facilitates system maintenance.

[0093] In one embodiment, for large volumes of data, to conserve system and communication resources, data transmission can be achieved without a data bridge. In this case, data can be shared between modules via disk or database.

[0094] Figure 8 This is a flowchart illustrating the process of synchronizing and updating large amounts of data between modules, such as... Figure 8 As shown, the process includes:

[0095] Step 801: After the data generation module generates the data, verify whether the data has been successfully saved to the database or disk;

[0096] Step 802: The generation module submits a synchronization request, packages the synchronization information, and sends it. The synchronization information includes data storage information (e.g., storage link).

[0097] Step 803: The data bridge broadcasts and forwards the information.

[0098] Step 804: The modules that need to be synchronized listen for synchronization information, parse out the data storage information that needs to be synchronized, read it from the database or disk, and perform synchronized display or processing.

[0099] To further understand the present invention, two examples are given below.

[0100] Example 1

[0101] Figure 9 It is a screenshot of the base map display of work area data, equivalent to... Figure 5 The image displayed in the synchronous application module (i.e., module 1) is proposed. Figure 10 This is a seismic profile diagram, equivalent to... Figure 5 The synchronous response module, namely module 2 (profile display module), displays the image. When in... Figure 9 When a survey line is picked on the base map, the module sends an interactive synchronization request and packages the current seismic data name, survey line number, etc., into a communication information packet represented by metadata. This packet is then sent to the communication port via the channel for the data bridge to acquire. The data bridge recognizes the header as survey line display synchronization information between the base map and profile display modules and then directly broadcasts the information. For example... Figure 10 As shown, when the profile display module detects new information arriving at the communication port, it first parses the header to confirm that it is the receiver, reads the information, and displays the survey line in the currently displayed seismic data that matches the survey line number picked from the base map, while maintaining the relevant display parameters, thus achieving interactive synchronization between the two modules.

[0102] Example 2

[0103] Figure 11 This is an image displayed by a seismic attribute cross-plot analysis module. Figure 12 , Figure 13 , Figure 14 These are the images displayed by the attribute profile display module, the planar display module, and the 3D display module, respectively. For example... Figure 11As shown, after the attribute intersection analysis module performs interactive interpretation, it requests to transmit the interpretation result data to other modules. Simultaneously, it packages the interpretation result and sends it to the communication port via the channel for the data bridge to receive. When the data bridge detects new information, it first reads and parses the header, identifying it as the intersection interpretation result sent by the attribute intersection analysis module. Since format conversion is required, it reads, converts, and sends the data according to the header settings. If the profile display module, planar display module, and 3D display module are already running, when they detect new information arriving at the communication port, they select to read the data packet sent to them and project the received intersection interpretation result onto the corresponding display area. This achieves interactive synchronization and data conversion between one sending module and multiple receiving modules.

[0104] In practice, the above-mentioned units and modules can be combined or set up individually, and the present invention is not limited thereto.

[0105] Based on a similar inventive concept, embodiments of the present invention also provide a data communication method based on a data bridge, which is preferably applicable to the aforementioned data bridge.

[0106] Figure 15 This is a flowchart of a data communication method based on a data bridge according to an embodiment of the present invention, as shown below. Figure 15 As shown, the method includes:

[0107] Step 1501: Receive metadata from the sender through the communication port. The metadata includes: information type and information to be sent.

[0108] In practice, metadata can also include: sender information and receiver information.

[0109] Step 1502: Parse the metadata to identify the information type of the metadata, and perform a conversion operation on the information to be sent according to the pre-configured information conversion rules and the information type.

[0110] Step 1503: Send the converted information to the communication port so that the corresponding receiving end can obtain the required information through the communication port.

[0111] When the information type is synchronous operation, the converted information can be sent to the communication port in a broadcast manner.

[0112] When the information to be sent is data storage information (e.g., storage link), the corresponding receiving end finds the data storage location based on the data storage information and obtains the corresponding data from the data storage location.

[0113] In this embodiment of the invention, metadata from the sending end is received through a communication port. The metadata is then parsed to identify the information type, so that the information to be sent can be converted according to the information type and information conversion rules. The converted information is then sent to the communication port so that the corresponding receiving end can obtain the required information through the communication port. In this way, efficient data communication between heterogeneous modules can be achieved.

[0114] In one embodiment, before step 1501, a full-duplex communication channel needs to be established between the sending end and the receiving end for data transmission; at the same time, the communication port is periodically monitored to obtain the data sent by the sending end in a timely manner. Figure 16 This is a detailed flowchart of a data communication method based on a data bridge, such as... Figure 16 As shown, the sending end packages the data to be sent into metadata. The data bridge receives the metadata from the sending end through the communication port, parses the metadata to identify the information type, and performs a conversion operation on the information to be sent according to the pre-configured information conversion rules and information type. Then, it sends the converted information back to the communication port. Subsequently, the receiving end obtains the required information through the communication port and responds. In this way, efficient data communication between heterogeneous modules can be achieved, thereby enabling rapid integration of large-scale software systems.

[0115] The specific execution flow of each of the above steps can be found in the description in the above device / system embodiments, and will not be repeated here.

[0116] This embodiment also provides an electronic device, which may be a desktop computer, tablet computer, or mobile terminal, etc., and this embodiment is not limited thereto. In this embodiment, the electronic device can be implemented with reference to the above method embodiment and the embodiment of the data communication system based on the data bridge, the contents of which are incorporated herein, and repeated parts will not be described again.

[0117] Figure 17 This is a schematic block diagram illustrating the system configuration of an electronic device 600 according to an embodiment of the present invention. Figure 17 As shown, the electronic device 600 may include a central processing unit 100 and a memory 140; the memory 140 is coupled to the central processing unit 100. It is worth noting that this figure is exemplary; other types of structures may be used to supplement or replace this structure to achieve telecommunications functions or other functions.

[0118] In one embodiment, the data communication function based on the data bridge can be integrated into the central processing unit 100. The central processing unit 100 can be configured to perform the following control:

[0119] The communication port receives metadata from the sender, including: information type and information to be sent;

[0120] The metadata is parsed to identify the information type of the metadata, and the information to be sent is converted according to the pre-configured information conversion rules and the information type.

[0121] The converted information is sent to the communication port so that the corresponding receiving end can obtain the required information through the communication port.

[0122] As can be seen from the above description, the electronic device provided in this application embodiment receives metadata from the sending end through a communication port, then parses the metadata to identify the information type, so as to perform a conversion operation on the information to be sent according to the information type and information conversion rules, and then sends the converted information to the communication port so that the corresponding receiving end can obtain the required information through the communication port. In this way, data communication between heterogeneous modules can be realized.

[0123] In another embodiment, the data communication system based on the data bridge can be configured separately from the central processing unit 100. For example, the data communication system based on the data bridge can be configured as a chip connected to the central processing unit 100, and the data communication function based on the data bridge can be implemented through the control of the central processing unit.

[0124] like Figure 17 As shown, the electronic device 600 may further include: a communication module 110, an input unit 120, an audio processing unit 130, a display 160, and a power supply 170. It is worth noting that the electronic device 600 does not necessarily need to include these components. Figure 17 All components shown; in addition, the electronic device 600 may also include Figure 17 For components not shown, please refer to existing technologies.

[0125] like Figure 17 As shown, the central processing unit 100, sometimes also referred to as a controller or operating control, may include a microprocessor or other processor device and / or logic device. The central processing unit 100 receives inputs and controls the operation of various components of the electronic device 600.

[0126] The memory 140 may be, for example, one or more of a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store the aforementioned failure-related information, and also store a program for executing that information. The central processing unit 100 may execute the program stored in the memory 140 to perform information storage or processing, etc.

[0127] Input unit 120 provides input to central processing unit 100. Input unit 120 may be, for example, a keypad or touch input device. Power supply 170 provides power to electronic device 600. Display 160 displays images and text. Display may be, for example, an LCD display, but is not limited thereto.

[0128] The memory 140 can be a solid-state memory, such as a read-only memory (ROM), random access memory (RAM), a SIM card, etc. It can also be a memory that retains information even when power is off, can be selectively erased, and contains more data; examples of this type of memory are sometimes referred to as EPROMs. The memory 140 can also be some other type of device. The memory 140 includes a buffer memory 141 (sometimes referred to as a buffer). The memory 140 may include an application / function storage unit 142 for storing application programs and function programs or processes for executing the operation of the electronic device 600 via the central processing unit 100.

[0129] The memory 140 may also include a data storage unit 143 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 144 of the memory 140 may include various drivers for the electronic device's communication functions and / or for performing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0130] The communication module 110 is a transmitter / receiver 110 that transmits and receives signals via antenna 111. The communication module (transmitter / receiver) 110 is coupled to the central processing unit 100 to provide input signals and receive output signals, which can be the same as in a conventional mobile communication terminal.

[0131] Based on different communication technologies, multiple communication modules 110 can be configured in the same electronic device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) 110 is also coupled to a speaker 131 and a microphone 132 via an audio processor 130 to provide audio output via the speaker 131 and receive audio input from the microphone 132, thereby enabling typical telecommunications functions. The audio processor 130 may include any suitable buffer, decoder, amplifier, etc. Additionally, the audio processor 130 is coupled to a central processing unit 100, enabling on-device recording via the microphone 132 and on-device playback of stored audio via the speaker 131.

[0132] This invention also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the above-described data communication method based on a data bridge.

[0133] In summary, the software system integration method based on a data bridge provided in this invention is based on computer system communication technology. It provides a data bridge between various software modules as a full-duplex communication and data transmission channel, forming a geophysical software integration scheme based on a data bridge to solve the integration problems between large-scale geophysical software or heterogeneous modules. The software system integrated using this scheme features loose coupling, easy expansion, and good maintenance, providing a practical and effective approach and method for saving software development costs and improving team efficiency.

[0134] Preferred embodiments of the invention have been described above with reference to the accompanying drawings. Many features and advantages of these embodiments are apparent from this detailed description, and therefore the claims are intended to cover all such features and advantages of these embodiments that fall within their true spirit and scope. Furthermore, since many modifications and alterations will readily occur to those skilled in the art, the embodiments of the invention are not intended to be limited to the precise structures and operations illustrated and described, but rather to encompass all suitable modifications and equivalents falling within their scope.

[0135] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0136] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0137] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0138] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0139] Specific embodiments have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this invention. Therefore, the content of this specification should not be construed as a limitation of this invention.

Claims

1. A data communication method based on a data bridge, characterized in that, The method includes: The communication port receives metadata from the sender, including: information type and information to be sent; The metadata is parsed to identify the information type of the metadata, and the information to be sent is converted according to the pre-configured information conversion rules and the information type. The converted information is sent to the communication port so that the corresponding receiving end can obtain the required information through the communication port. The information type is a synchronous operation, and sending the converted information to the communication port includes: sending the converted information to the communication port in a broadcast manner; Each functional module determines whether it is the receiving end. If so, it processes the data based on the converted information; otherwise, it automatically discards the converted information. Each functional module continues to periodically monitor the communication port.

2. The method according to claim 1, characterized in that, Before receiving metadata from the sender via the communication port, the method further includes: Establish a full-duplex communication channel between the sending and receiving ends for data transmission; The communication port is periodically monitored.

3. The method according to claim 1, characterized in that, The information to be sent is data storage information, and the corresponding receiving end obtains the required information through this communication port, including: The corresponding receiving end locates the data storage location based on the data storage information and retrieves the corresponding data from that data storage location.

4. A data bridge, characterized in that, The data bridge includes: The receiving unit is used to receive metadata from the sending end through a communication port. The metadata includes: information type and information to be sent. The parsing unit is used to parse the metadata to identify the information type of the metadata; A conversion unit is used to convert the information to be sent according to pre-configured information conversion rules and the information type; A transmitting unit is used to send the converted information to the communication port so that the corresponding receiving end can obtain the required information through the communication port. The information type is a synchronous operation, and the sending unit is specifically used to: send the converted information to the communication port in a broadcast manner; Each functional module determines whether it is the receiving end. If so, it processes the data based on the converted information; otherwise, it automatically discards the converted information. Each functional module continues to periodically monitor the communication port.

5. The data bridge according to claim 4, characterized in that, The data bridge also includes: The channel establishment unit is used to establish a full-duplex communication channel between the transmitter and receiver for data transmission. A monitoring unit is used to periodically monitor the communication port.

6. A data communication system based on a data bridge, characterized in that, The system includes: a data bridge, a receiver, a transmitter, and a communication port as described in any one of claims 4 to 5, wherein the transmitter sends metadata to the communication port, the data bridge listens to the communication port and obtains the metadata, the data bridge sends converted metadata to the communication port, and the transmitter listens to the communication port and obtains the required data.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method according to any one of claims 1 to 3.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 3.

Images