Multi-terminal data interaction method, device and equipment

Abstract

The present invention discloses a multi-terminal data interaction method, device and equipment. Among them, the multi-terminal data interaction method applied to an adapter includes: obtaining the original data of a data access end; performing data encoding on the original data to obtain intermediate data; and transmitting the intermediate data to a data bus, so that when the data bus receives a query request and / or a subscription request from a data acquisition end, corresponding target data is matched from the intermediate data for different keywords to execute a response. Obtaining the original data of the data access end and performing data encoding on the original data according to a preset data format to generate intermediate data in a unified format and transmitting it to the data bus is beneficial to realizing data interaction between multiple data access ends and data acquisition ends. During the access process, only the adapter is used to perform unified data encoding on the original data to complete the interaction of data between the data access end and the data acquisition end, improving the interaction between multiple data access ends and data acquisition ends.

Description

Technical Field

[0001] The present invention relates to the technical field of data interaction, and in particular, to a multi-terminal data interaction method, device, equipment, and storage medium. Background Art

[0002] With the development of computer technology, more work within an enterprise is efficiently achieved through various applications or systems, resulting in various applications, systems, and corresponding data storage services existing within the enterprise.

[0003] When there is a need for data sharing among various applications, systems, and corresponding data storage services within an enterprise, since various applications, systems, and corresponding data storage services may not be compiled based on the same development technology and development environment, the data sharing among various applications, systems, and corresponding data storage services within the enterprise becomes uncontrollable, resulting in obstacles to data sharing among various applications, systems, and corresponding data storage services within the enterprise. Furthermore, it causes the enterprise to need to conduct targeted development to enable query requests and calls for a certain piece of data between different systems and applications. However, most of these solutions are for the rapid implementation of business in a few scenarios. Even if linkages are established, they are only limited connections, and the problem of data islands has not been fundamentally changed, unable to adapt to flexible business adjustments, let alone rapidly expand business and scale up. When other applications or systems need to be connected, targeted development still needs to be carried out.

[0004] In the prior art, the data structures among various applications, systems, and corresponding data storage services are different, resulting in uncontrollable data sharing among various applications, systems, and corresponding data storage services within the enterprise, causing obstacles to data sharing among various applications, systems, and corresponding data storage services within the enterprise, hindering the data integration and invocation of various applications, systems, and corresponding data storage services within the enterprise, and increasing the development difficulty of various applications, systems, and corresponding data storage services within the enterprise. Summary of the Invention

[0005] The present invention provides a multi-terminal data interaction method, device, and equipment to solve the problem of data intercommunication among multiple applications, systems, and corresponding data storage services within an enterprise.

[0006] According to one aspect of the present invention, there is provided a multi-terminal data interaction method applied to an adapter, including:

[0007] Obtaining the original data of the data access end;

[0008] Encoding the original data to obtain intermediate data;

[0009] Transfer the intermediate data to the data bus so that when the data bus receives a query request and / or a subscription request from a data acquisition end, corresponding target data is matched from the intermediate data for different keywords and a response is executed.

[0010] Optionally, the encoding the original data to obtain intermediate data includes:

[0011] Obtain the universal unique identifier of the data access end corresponding to the original data;

[0012] Parse the original data to obtain the corresponding group and object ID of the original data;

[0013] Based on the universal unique identifier, the group, and the object ID, encapsulate them into intermediate data in a preset format.

[0014] Optionally, after obtaining the original data of the data access end, it further includes:

[0015] Perform a desensitization operation and data integrity check on the original data.

[0016] According to another aspect of the present invention, a multi-end data interaction method is provided, which is applied to a data bus and includes:

[0017] Obtain the intermediate data sent by the adapter;

[0018] Manage the data access end list, the group list, and the API interface list based on the intermediate data;

[0019] When receiving a query request and / or a subscription request initiated by a data acquisition end, parse the query request and / or the subscription request to obtain a target keyword;

[0020] Match corresponding target information from the data access end list, the group list, and the API interface list based on the target keyword;

[0021] Match corresponding target data from the data bus or the data access end based on the target information and feedback the target data to the data acquisition end.

[0022] Optionally, the managing the data access end list, the group list, and the API interface list based on the intermediate data includes:

[0023] Parse the intermediate data to obtain the data access end, the group, and the included API interface corresponding to the intermediate data;

[0024] Update the pre-established access terminal list, group list, and API interface list based on the data access terminal, the group, and the API interface.

[0025] Optionally, after updating the pre-established access terminal list, group list, and API interface list based on the data access terminal, the group, and the API interface, the method further includes:

[0026] Perform priority sorting on the data access terminal, the group, and the API interface based on a preset priority sorting table.

[0027] Optionally, the query request and / or the subscription request includes data access terminal, group, and / or API interface keywords.

[0028] According to another aspect of the present invention, there is provided a multi-terminal data interaction device applied to an adapter, including:

[0029] A first acquisition module for acquiring the original data of the data access terminal;

[0030] An encoding module for performing data encoding on the original data to obtain intermediate data;

[0031] A transmission module for transmitting the intermediate data to the data bus, so that when the data bus receives a query request and / or a subscription request from a data acquisition terminal, corresponding target data is matched from the intermediate data for different keywords to perform a response.

[0032] According to another aspect of the present invention, there is provided a multi-terminal data interaction device applied to a data bus, including:

[0033] A second acquisition module for acquiring the intermediate data sent by the adapter;

[0034] A management module for managing a data access terminal list, a group list, and an API interface list based on the intermediate data;

[0035] An analysis module for analyzing the query request and / or the subscription request to obtain target keywords when receiving a query request and / or a subscription request initiated by a data acquisition terminal;

[0036] A matching module for matching corresponding target information from the data access terminal list, the group list, and the API interface list based on the target keywords;

[0037] A feedback module for matching corresponding target data from the data bus or the data access terminal based on the target information and feeding back the target data to the data acquisition terminal.

[0038] According to another aspect of the present invention, there is provided a multi-terminal data interaction device, the device comprising:

[0039] at least one processor; and

[0040] a memory communicatively connected to the at least one processor; wherein,

[0041] the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute the multi-terminal data interaction method according to any embodiment of the present invention.

[0042] The technical solution of the embodiment of the present invention is to obtain the original data of the data access end, perform data encoding on the original data according to a preset data format, generate intermediate data in a unified format and transmit it to the data bus, which is conducive to realizing data interaction between multiple data access ends and data acquisition ends. During the access process, only an adapter is needed to perform unified data encoding on the original data to complete the data interaction between the data access end and the data acquisition end, greatly improving the interaction between multiple data access ends and data acquisition ends. The intermediate data sent by the adapter is used to manage and update the data access end list, grouping list and API interface list stored in the data bus, and then based on the query request or subscription request of the data acquisition end, the corresponding data access end, group, object or API is matched, and then the target data required by the data acquisition end is fed back to the data acquisition end, realizing the data interaction between the data acquisition end and the data access end, avoiding the interaction obstacles caused by different data formats between the data access end and the data acquisition end, and thus facilitating the flexible adjustment and rapid expansion of services.

[0043] It should be understood that the content described in this part is not intended to identify the key or important features of the embodiments of the present invention, nor is it used to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0045] Figure 1 is a flowchart of a multi-terminal data interaction method provided according to Embodiment 1 of the present invention;

[0046] Figure 2It is a flowchart of a multi - terminal data interaction method provided in Embodiment 2 of the present invention;

[0047] Figure 3 It is a schematic structural diagram of a multi - terminal data interaction device provided in Embodiment 3 of the present invention;

[0048] Figure 4 It is a schematic structural diagram of a multi - terminal data interaction device provided in Embodiment 4 of the present invention;

[0049] Figure 5 It is a schematic structural diagram of a multi - terminal data interaction device for implementing the multi - terminal data interaction method of the embodiments of the present invention. Detailed implementation manners

[0050] In order to enable those skilled in the art to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0051] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above - mentioned drawings are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments of the present invention described here can be implemented in an order different from those illustrated or described here. In addition, the terms "include" and "have" and any variations thereof are intended to cover non - exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those clearly listed steps or units, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0052] Embodiment 1

[0053] Figure 1 This is a flowchart of a multi - terminal data interaction method provided in Embodiment 1 of the present invention. This embodiment is applicable to the situation of realizing data interaction between multiple applications, systems or corresponding data storage services inside and outside an enterprise. This method can be executed by a multi - terminal data interaction device, which can be implemented in the form of hardware and / or software, and the multi - terminal data interaction device can be configured in an adapter.

[0054] In the embodiments of the present invention, the data formats of different data access ends and data acquisition ends are different. To realize the data interaction between different data access ends and data acquisition ends, certain processing needs to be performed on the interacting data. In the embodiments of the present invention, an adapter and a data bus are provided between the data access end and the data acquisition end. The data access end and the data acquisition end are connected to the data bus through the adapter. The multi-end data interaction method provided by the embodiments of the present invention can be applied to the adapter and the data bus, thereby realizing the data interaction between different data access ends and data acquisition ends.

[0055] As Figure 1 shown, the multi-end data interaction method applied to the adapter includes:

[0056] S110. Obtain the original data of the data access end.

[0057] In the embodiments of the present invention, the data access end can be an application, service, system, etc. that needs to realize data interconnection, on which the data to be sent to the data acquisition end is generated or stored. The data generated or stored on the data access end is the original data mentioned in the embodiments of the present invention. The original data can be a single data or a collection of multiple data.

[0058] For the data access end, there is at least one group (or item) on it, and one or more data objects are generated or stored corresponding to each group. That is to say, there is at least one group and one data object under the group under a single data access end. In actual implementation, the data of the data access end is a multi-layer structure. Usually, a single data access end is provided with multiple groups, and multiple data objects are provided under each group.

[0059] Exemplarily, the original data of the data access end can be multiple data generated during the operation under a single group (or item), or the result of a single operation, etc., or the data stored on the data access end, etc.

[0060] It should be noted that the acquisition of the original data in S110 can be active acquisition or passive acquisition. That is to say, it can be to receive the original data sent by the data access end, or directly read the data from the data access end. In the embodiments of the present invention, no specific limitation is made on this, and the passive acquisition or active acquisition, or a combination of active acquisition and passive acquisition can be selected based on the actual situation.

[0061] S120. Perform data encoding on the original data to obtain intermediate data.

[0062] In the foregoing steps, the original data of the data access end is obtained. The data format of the obtained original data is the data format of the data access end itself. During the transmission of the adapter and the data bus, the accuracy and integrity of the transmitted data cannot be guaranteed, and it is not convenient to implement the scheduling of the original data, and it is impossible to conveniently and quickly implement the data interaction between the data access end and the data acquisition end. Therefore, in the embodiments of the present invention, it is necessary to perform data encoding on the obtained original data so that the original data is transmitted through the adapter and the data bus in a unified form.

[0063] Exemplarily, after obtaining the original data, the original data can be parsed to obtain keyword information such as the grouping and object ID of the original data, and a universally unique identifier corresponding to the data access end is added to ensure the independence of the data and avoid the occurrence of data confusion caused by the association and coupling of the data of multiple data access ends. At the same time, it also provides an index for the query and acquisition of the original data, so as to more quickly respond to the request of the data acquisition end when obtaining data and find the corresponding data to be transmitted to the data acquisition end.

[0064] S130. Transmit the intermediate data to the data bus so that when the data bus receives a query request and / or a subscription request from the data acquisition end, corresponding target data is matched from the intermediate data for different keywords to execute a response.

[0065] In the embodiments of the present invention, after the adapter encodes the original data of the obtained data access end to obtain intermediate data in a unified data format, it is then transmitted to the data bus for operations such as caching, distribution, and persistence.

[0066] Exemplarily, the data acquisition end accesses the data bus and sends a query request containing a query keyword to the data bus. The data bus then matches the corresponding intermediate data from the intermediate data based on the query keyword and transmits it to the data acquisition end, or matches the corresponding data access end from the intermediate data based on the query keyword, then sends a query request to the data access end to request the corresponding data content, and then transparently transmits it to the data acquisition end, etc.

[0067] In the embodiments of the present invention, by obtaining the original data of the data access end and encoding the original data according to a preset data format to generate intermediate data in a unified format and transmitting it to the data bus, it is beneficial to realize the data interaction between multiple data access ends and data acquisition ends. During the access process, only the adapter needs to perform unified data encoding on the original data to complete the data interaction between the data access end and the data acquisition end, which greatly improves the interaction between multiple data access ends and data acquisition ends, avoids secondary development when the data access end and the data acquisition end are docked, and facilitates the format of the data transmitted through the adapter and the data bus uniformly, and is convenient for realizing data management.

[0068] In an embodiment of the present invention, the data encoding of the original data in S120 may include:

[0069] S121. Obtain the universally unique identifier of the data access end corresponding to the original data.

[0070] In an embodiment of the present invention, a universally unique identifier is also defined for each data access end, which is used to identify the data access end, avoid the confusion of multiple data access ends, effectively ensure the independence of data, avoid data coupling in the case where multiple data access ends have the same grouping, and facilitate subsequent identification and positioning of the identity of the data access end, improving data reliability and accuracy.

[0071] Among them, the universally unique identifier (English: Universally Unique Identifier, abbreviated as UUID) is a standard constructed by software. The standard form of UUID can contain 32 hexadecimal digits, divided into five segments by hyphens, in the form of 32 characters of 8-4-4-4-12.

[0072] S122. Parse the original data to obtain the corresponding grouping and object ID of the original data.

[0073] In an embodiment of the present invention, the data access end needs to group the original data and sort the objects within the group and assign corresponding object IDs. The purpose of grouping is to distinguish the data corresponding to different items, services, applications, and parameters of the data access end, and the object ID is to distinguish different data under different items, services, applications, and parameters. Exemplarily, the grouping and object ID can be serial numbers of preset rules, etc.

[0074] S123. Encapsulate the data into intermediate data in a preset format based on the universally unique identifier, grouping, and object ID.

[0075] Specifically, the intermediate data can be set as an array. The first digit of it is the universally unique identifier of the data access end, the second digit is the grouping number at the data access end, the third digit is the object ID at the data access end, and the fourth digit is the form of the object data for data encoding, or data encoding of the original data is implemented in other ways to generate intermediate data.

[0076] It should be noted that the definition of the size and number of digits of the array in the above example is not unique. It is only a specific example of one implementation. In other examples, the positions can be swapped with each other, spliced, etc.

[0077] Specifically, the encapsulated intermediate data can be encapsulated in forms such as JSON, XML, YAML formats, etc.

[0078] Optionally, after obtaining the original data of the data access end in S110, it may further include performing data desensitization operations and data integrity verification on the original data.

[0079] Data desensitization refers to the transformation of certain sensitive information through desensitization rules to achieve reliable protection of sensitive privacy data. In cases involving customer security data or some commercially sensitive data, without violating system rules, the real data is transformed and provided for testing use. Personal information such as ID numbers, mobile phone numbers, card numbers, and customer numbers all need to be desensitized. By desensitizing the data, the leakage of sensitive data can be avoided, and the security of data transmission can be improved.

[0080] Data integrity verification is a verification operation to ensure data integrity. Usually, a check value is calculated for the original data using a specified algorithm. The receiving party calculates the check value again using the same algorithm. If the two calculated check values are the same, it indicates that the data is complete.

[0081] Embodiment 2

[0082] Figure 2 The present invention provides a flowchart of a multi-terminal data interaction method for Embodiment 2. This embodiment is applicable to the situation of realizing data interaction between multiple applications, systems, or corresponding data storage services inside and outside an enterprise. This method can be executed by a multi-terminal data interaction device, which can be implemented in the form of hardware and / or software, and the multi-terminal data interaction device can be configured in a data bus.

[0083] In the embodiment of the present invention, an adapter and a data bus are provided between the data access end and the data acquisition end. The data access end and the data acquisition end are connected to the data bus through the adapter. After the multi-terminal data interaction method applied to the adapter provided in the foregoing embodiment is processed, intermediate data is obtained and transmitted to the data bus, and then data interaction between different data access ends and data acquisition ends is realized through the data bus.

[0084] As Figure 2 shown, the multi-terminal data interaction method applied to the data bus includes:

[0085] S210. Obtain the intermediate data sent by the adapter.

[0086] In the embodiment of the present invention, a part of the data received by the data bus is the intermediate data in a unified format transmitted during the adapter processing. For the processing and obtaining of the intermediate data, reference can be made to the description in Embodiment 1 above, and no further elaboration will be made here.

[0087] S220. Manage the data access end list, grouping list, and API interface list based on intermediate data.

[0088] As can be known from the data encoding of the intermediate data in the foregoing embodiments, the intermediate data may include the universally unique identifier of the data access end, the grouping corresponding to the original data, and the object ID, and may also include the API interface provided by the data access end. What needs to be done in this step is to generate corresponding data indexes based on the universally unique identifier, grouping, object ID, and API interface. Specifically, it may be a data access end list, a grouping list, and an API interface list, or a database, which stores information corresponding to the universally unique identifier, grouping, object ID, and API interface of the data access end, and specific intermediate data or original data can be retrieved based on this information.

[0089] Optionally, the intermediate data may further include an information update request for the data access end, which is used to update, delete, and add requests for the original universally unique identifier, grouping, object ID, and API interface in the data access end, so as to facilitate the management of the data access end list, grouping list, and API interface list.

[0090] S230. When a query request and / or subscription request initiated by the data acquisition end is received, parse the query request and / or subscription request to obtain the target keyword.

[0091] In the embodiments of the present invention, there are many ways for the data acquisition end to obtain the target data. For example, the target data is obtained from the data access end through query, or through subscription, when there is an update of the corresponding target data at the data access end, the data bus pushes the corresponding target data to it, or it may also be to passively receive the data pushed by the data access end, etc.

[0092] When the data acquisition end actively queries or subscribes, it needs to send a query request and / or subscription request with the target keyword to the data bus. Among them, the target keyword may be information such as the universally unique identifier, grouping, object ID, and API of the data access end.

[0093] What needs to be done in this step is to parse the corresponding target keyword from the query request or subscription request.

[0094] S240. Match the corresponding target information from the data access end list, grouping list, and API interface list based on the target keyword.

[0095] In an embodiment of the present invention, the data bus stores at least a data access end list, a grouping list, and an API interface list corresponding to the data access end. In the previous step, the target keyword corresponding to the query request and / or subscription request of the data acquisition end is obtained. In this step, the target keyword can be used to match in the data access end list, the grouping list, and the API interface list stored in the data bus to find the corresponding data access end, grouping, object ID, or API interface as the target information.

[0096] S250. Match the corresponding target data from the data bus or the data access end based on the target information, and feedback the target data to the data acquisition end.

[0097] When the target information is obtained, it is possible to confirm the data access end, grouping, object ID, or API where the data to be queried or subscribed by the data acquisition end is located. In this step, only a data acquisition request needs to be sent to the determined data access end according to the target information, and then the acquired data is transparently transmitted to the data acquisition end.

[0098] In an embodiment of the present invention, the data access end list, the grouping list, and the API interface list stored in the data bus are managed and updated through the intermediate data sent by the adapter, and then the corresponding data access end, grouping, object, or API is matched based on the query request or subscription request of the data acquisition end, and further the target data required by the data acquisition end is fed back to the data acquisition end, realizing the data interaction between the data acquisition end and the data access end, avoiding the interaction obstacle caused by the different data formats between the data access end and the data acquisition end, and thus facilitating the flexible adjustment and rapid expansion of the service.

[0099] In an embodiment of the present invention, the data access end, the grouping, and the API interface can also be sorted according to a preset priority ranking table.

[0100] Sorting the data access end, the grouping, and the API interface by priority can preferentially respond to the query and subscription requests for the data access end, the grouping, and the API interface with higher priority when receiving query and subscription requests for different data access ends, groupings, and API interfaces simultaneously, so as to ensure that important operations and data can be processed faster.

[0101] In an embodiment of the present invention, in addition to responding to the requests of the data access end and the data acquisition end to update, query, and subscribe to data, the data bus can also cache some data to the database in the data persistence layer corresponding to the data bus based on the requests of the data access end and the data acquisition end for data persistence storage. And perform operations such as authentication on the access, query, and subscription requests of the data access end and the data acquisition end.

[0102] Embodiment III

[0103] Figure 3 This is a schematic structural diagram of a multi - terminal data interaction device provided in Embodiment 3 of the present invention. As Figure 3 shown, the device includes a first acquisition module 31, an encoding module 32, and a transmission module 33, where:

[0104] The first acquisition module 31 is configured to acquire the original data of the data access end;

[0105] The encoding module 32 is configured to perform data encoding on the original data to obtain intermediate data;

[0106] The transmission module 33 is configured to transmit the intermediate data to the data bus, so that when the data bus receives a query request and / or a subscription request from the data acquisition end, corresponding target data is matched from the intermediate data for response according to different keywords.

[0107] Optionally, the encoding module 32 includes:

[0108] An identification code acquisition unit, configured to acquire the universally unique identification code of the data access end corresponding to the original data;

[0109] A first parsing unit, configured to parse the original data to obtain the group and object ID corresponding to the original data;

[0110] An encapsulation unit, configured to encapsulate the data into intermediate data in a preset format based on the universally unique identification code, group, and object ID.

[0111] Optionally, it further includes:

[0112] A desensitization verification module, configured to perform desensitization operations and data integrity verification on the original data.

[0113] The multi - terminal data interaction device provided in the embodiments of the present invention can execute the multi - terminal data interaction method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0114] Embodiment 4

[0115] Figure 4 This is a schematic structural diagram of a multi - terminal data interaction device provided in Embodiment 4 of the present invention. As Figure 4 shown, the device includes a second acquisition module 41, a management module 42, an analysis module 43, a matching module 44, and a feedback module 45, where:

[0116] The second acquisition module 41 is configured to acquire the intermediate data sent by the adapter;

[0117] The management module 42 is used to manage the data access end list, the grouping list, and the API interface list based on the intermediate data;

[0118] The parsing module 43 is used to parse the query request and / or subscription request when receiving the query request and / or subscription request initiated by the data acquisition end, and obtain the target keyword;

[0119] The matching module 44 is used to match the corresponding target information from the data access end list, the grouping list, and the API interface list based on the target keyword;

[0120] The feedback module 45 is used to match the corresponding target data from the data bus or the data access end based on the target information, and feedback the target data to the data acquisition end.

[0121] Optionally, the management module 42 may include:

[0122] The second parsing unit is used to parse the intermediate data to obtain the data access end, the grouping, and the included API interfaces corresponding to the intermediate data;

[0123] The updating unit is used to update the pre-established access end list, grouping list, and API interface list based on the data access end, the grouping, and the API interfaces.

[0124] It further includes:

[0125] The priority unit is used to perform priority sorting on the data access end, the grouping, and the API interfaces based on a preset priority sorting table.

[0126] Optionally, the query request and / or subscription request includes data access end, grouping, and / or API interface keywords.

[0127] The multi-end data interaction device provided by the embodiments of the present invention can execute the multi-end data interaction method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method.

[0128] Embodiment Five

[0129] Figure 5FIG. 0 shows a schematic structural diagram of a multi-terminal data interaction device 10 that can be used to implement embodiments of the present invention. The multi-terminal data interaction device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The multi-terminal data interaction device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or claimed herein.

[0130] As Figure 5 shown, the multi-terminal data interaction device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc. The memory stores a computer program executable by the at least one processor. The processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 into the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the multi-terminal data interaction device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0131] Multiple components in the multi-terminal data interaction device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disc, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the multi-terminal data interaction device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0132] The processor 11 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the multi-terminal data interaction method.

[0133] In some embodiments, the multi - terminal data interaction method can be implemented as a computer program tangibly embodied in a computer - readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed onto the multi - terminal data interaction device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by the processor 11, one or more steps of the multi - terminal data interaction method described above can be performed. Alternatively, in other embodiments, the processor 11 can be configured to execute the multi - terminal data interaction method by any other suitable means (e.g., by means of firmware).

[0134] The various embodiments of the systems and techniques described above in this document can be implemented in digital electronic circuitry, integrated circuit systems, field - programmable gate arrays (FPGA), application - specific integrated circuits (ASIC), application - specific standard products (ASSP), systems - on - a - chip (SOC), complex programmable logic devices (CPLD), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special - purpose or general - purpose programmable processor that receives data and instructions from a storage system, at least one input device, and at least one output device, and transmits the data and instructions to the storage system, the at least one input device, and the at least one output device.

[0135] The computer programs for implementing the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general - purpose computer, a special - purpose computer, or other programmable data - processing apparatus, such that when the computer programs are executed by the processor, the functions / operations specified in the flowchart and / or block diagram are implemented. The computer programs can be executed entirely on the machine, partially on the machine, as a stand - alone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0136] In the context of the present invention, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer-readable storage medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium can be a machine-readable signal medium. More specific examples of the machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0137] In order to provide interaction with a user, the systems and techniques described herein can be implemented on a multi-terminal data interaction device having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the multi-terminal data interaction device. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0138] The systems and techniques described herein can be implemented in a computing system including a backend component (e.g., as a data server), or a computing system including a middleware component (e.g., an application server), or a computing system including a frontend component (e.g., a user computer having a graphical user interface or a web browser through which the user can interact with an implementation of the systems and techniques described herein), or a computing system including any combination of such backend components, middleware components, or frontend components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local area network (LAN), wide area network (WAN), blockchain network, and the Internet.

[0139] A computing system may include a client and a server. The client and the server are generally far from each other and usually interact via a communication network. The client-server relationship is created by computer programs running on respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or a cloud host, which is a host product in the cloud computing service system, solving the defects of difficult management and weak business scalability existing in traditional physical hosts and VPS services.

[0140] It should be understood that various forms of processes shown above can be used, with steps reordered, added or deleted. For example, the steps recited in the present invention can be executed in parallel, sequentially or in a different order, as long as the desired results of the technical solution of the present invention can be achieved, and no limitation is made herein.

[0141] The above specific embodiments do not constitute a limitation on the protection scope of the present invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A multi-terminal data interaction method, applied to an adapter, characterized in that including: Obtaining the original data of the data access end; Performing data encoding on the original data to obtain intermediate data; Transmitting the intermediate data to the data bus so that when the data bus receives a query request and / or a subscription request from the data acquisition end, it matches corresponding target data from the intermediate data for different keywords and executes a response; Wherein, the performing data encoding on the original data to obtain intermediate data includes: Obtaining the universally unique identifier of the data access end corresponding to the original data; Parsing the original data to obtain the group and object ID corresponding to the original data; Encapsulating the intermediate data in a preset format based on the universally unique identifier, the group, and the object ID; Wherein, setting the intermediate data as an array; the first position of the array is the universally unique identifier of the data access end, the second position is the number of the group at the data access end, the third position is the object ID at the data access end, and the fourth position is the object data.

2. The multi-terminal data interaction method according to claim 1, wherein After obtaining the original data of the data access end, it further includes: Performing a desensitization operation and data integrity check on the original data.

3. A multi-terminal data interaction method, applied to a data bus, characterized in that, including: Obtaining the intermediate data sent by the adapter; Managing the data access end list, the group list, and the API interface list based on the intermediate data; When receiving a query request and / or a subscription request initiated by the data acquisition end, parsing the query request and / or the subscription request to obtain a target keyword; Matching corresponding target information from the data access end list, the group list, and the API interface list based on the target keyword; Matching corresponding target data from the data bus or the data access end based on the target information and feeding back the target data to the data acquisition end; The intermediate data further includes an information update request for the data access end to update the data access end list, the group list, and the API interface list.

4. The multi-terminal data interaction method according to claim 3, wherein The managing the data access end list, the group list, and the API interface list based on the intermediate data includes: Parsing the intermediate data to obtain the data access end, the group, and the included API interface corresponding to the intermediate data; Updating the pre-established access end list, group list, and API interface list based on the data access end, the group, and the API interface.

5. The multi-terminal data interaction method according to claim 4, wherein After updating the pre-established access end list, group list, and API interface list based on the data access end, the group, and the API interface, it further includes: Performing a priority sorting on the data access end, the group, and the API interface based on a preset priority sorting table.

6. The multi-terminal data interaction method according to claim 3, wherein The query request and / or the subscription request includes data access end, group, and / or API interface keywords.

7. A multi-terminal data interaction device, characterized in that, Applied to the adapter, including: A first acquisition module for executing the acquisition of the original data of the data access end; An encoding module for executing data encoding on the original data to obtain intermediate data; A transmission module for transmitting the intermediate data to a data bus so that when the data bus receives a query request and / or a subscription request from a data acquisition end, corresponding target data is matched from the intermediate data for different keywords to execute a response; Among them, the encoding module includes: An identification code acquisition unit for acquiring the universal unique identification code of the data access end corresponding to the original data; A first parsing unit for parsing the original data to obtain the corresponding group and object ID of the original data; An encapsulation unit for encapsulating into intermediate data in a preset format based on the universal unique identification code, group and object ID; Among them, the intermediate data is set as an array; the first bit of the array is the universal unique identification code of the data access end, the second bit is the number of the group at the data access end, the third bit is the object ID at the data access end, and the fourth bit is the object data.

8. A multi-terminal data interaction device is applied to a data bus, characterized in that, It includes: A second acquisition module for acquiring the intermediate data sent by the adapter; A management module for managing the data access end list, group list and API interface list based on the intermediate data; A parsing module for parsing the query request and / or the subscription request to obtain a target keyword when receiving a query request and / or a subscription request initiated by a data acquisition end; A matching module for matching corresponding target information from the data access end list, the group list and the API interface list based on the target keyword; A feedback module for matching corresponding target data from the data bus or the data access end based on the target information and feeding back the target data to the data acquisition end; Among them, the intermediate data further includes an information update request for the data access end to update the data access end list, the group list and the API interface list.

9. A multi-terminal data interaction device, characterized in that, The device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the multi-terminal data interaction method according to any one of claims 1-2 or 3-6.

Images