Data acquisition method, device, electronic device and storage medium

By receiving and processing the conversion data process of multiple users, the problem of difficulty in data acquisition between different medical platforms is solved, standardized conversion and rapid acquisition of data are realized, and manpower and material resources are saved.

CN114038545BActive Publication Date: 2025-01-21GUAHAO (HANGZHOU) TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202111321587.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-11-09
Publication Date
2025-01-21
Estimated Expiration
2041-11-09

AI Technical Summary

Technical Problem

In the prior art, programmers are required to write different codes for different medical platforms, resulting in increased manpower, material resources and cost.

Method used

Provide a data acquisition method, by receiving the process of converting data from multiple users and generating identification information for them, obtaining the target data according to the current user's access request, converting it into standard data, and sending it to the current user.

Benefits of technology

It avoids repeated coding, saves manpower and material resources, and reduces costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114038545B_ABST
    Figure CN114038545B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a data acquisition method, device, electronic device and storage medium, the method comprising: receiving a process of conversion data of multiple users, generating identification information for the process, the identification information is used to identify the user; receiving an access request of the current user, the access request including the identification information of the current user; acquiring the process of conversion data of the current user according to the identification information of the current user; acquiring target data according to the access request of the current user and the process of conversion data of the current user, converting the target data into standard data; sending the standard data to the current user. The technical problem that programmers need to transform a large amount of code in the prior art is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a data acquisition method, device, electronic device and computer-readable storage medium. Background Art

[0002] At present, each medical platform receives different information due to its own hardware equipment, software architecture, and connected network equipment. When each medical platform obtains information from other medical platforms, programmers are required to write different programs to process data for different medical platforms so that each medical platform can obtain data suitable for local hardware equipment and software architecture. The existing method of obtaining data wastes a lot of manpower and material resources. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a data acquisition method, device, electronic device and computer-readable storage medium, which can solve the problem in the prior art that programmers are required to write different codes specifically for different medical platforms, thereby saving manpower and material resources and reducing costs.

[0004] In a first aspect, an embodiment of the present application provides a data acquisition method, including:

[0005] A process of receiving conversion data of a plurality of users, and generating identification information for the process, wherein the identification information is used to identify the users;

[0006] receiving an access request from a current user, wherein the access request includes identification information of the current user;

[0007] A process of acquiring conversion data of the current user according to identification information of the current user;

[0008] Acquire target data according to the access request of the current user and the process of converting data of the current user, and convert the target data into standard data;

[0009] The standard data is sent to the current user.

[0010] In the above implementation process, the process of receiving the conversion data of multiple users and generating identification information for the process, when each user's access request is received, the obtained data can be processed according to the process of the conversion data corresponding to the current user, so that the final standard data format can be accepted by the current user. Based on the above implementation, it is possible to avoid repeated code writing, saving manpower and material resources.

[0011] Further, the process of converting data of the plurality of users includes a sequence of components;

[0012] The steps of the process of receiving conversion data of multiple users include:

[0013] receiving conversion components used by the plurality of users to convert data and an order in which the plurality of users use the conversion components;

[0014] A component sequence for the multiple users is generated according to the conversion components used by the multiple users to convert data and the order in which the multiple users use the conversion components.

[0015] In the above implementation process, the process of converting data includes a component sequence, the format of the data is limited, and the process of converting data for each user is to use each component to obtain data of different formats and convert the data of different formats. Therefore, the steps of the process of receiving conversion data of multiple users are to receive the conversion components used by multiple users for converting data and the order in which the multiple users use the conversion components, and generate a sequence of components corresponding to each user in the multiple users according to the conversion components and the order in which the multiple users use the conversion components. Based on the above implementation, the process of converting data of multiple users can be quickly received.

[0016] Furthermore, the component sequence includes an acquisition component sequence and a conversion component sequence;

[0017] The step of acquiring target data according to the access request of the current user and the process of converting the data of the current user, and converting the target data into standard data comprises:

[0018] Acquire the target data according to the acquisition component sequence;

[0019] The target data is input into the conversion component sequence to obtain the standard data.

[0020] In the above implementation process, the process of each user obtaining standard data includes obtaining target data and converting the target data. Therefore, the component sequence includes an obtaining component sequence and a converting component sequence. The target data is obtained according to the obtaining component sequence; the target data is input into the converting component sequence to obtain the standard data. Based on the above implementation, standard data can be quickly obtained.

[0021] Further, the process of converting data of the plurality of users includes a sequence of components;

[0022] The steps of the process of receiving conversion data of multiple users include:

[0023] receiving a receivable data format transmitted by the plurality of users;

[0024] Retrieve a plurality of components from the database;

[0025] Generate component sequences for the multiple users according to the receivable data formats of the multiple users and the multiple components.

[0026] In the above implementation process, by receiving the receivable data formats transmitted by multiple users, it is possible to know which components should be applied to convert the data and the order in which these components should be used, thereby generating component sequences for multiple users. Based on the above implementation, component sequences for multiple users can be generated.

[0027] In a second aspect, the present application provides a data acquisition device, comprising:

[0028] A receiving module, configured to receive a process of conversion data of multiple users, generate identification information for the process, wherein the identification information is used to identify the user; receive an access request of a current user, wherein the access request includes the identification information of the current user;

[0029] An acquisition module, configured to acquire the conversion data of the current user according to the identification information of the current user;

[0030] A conversion module, used for acquiring target data according to the access request of the current user and the process of converting data of the current user, and converting the target data into standard data;

[0031] A sending module is used to send the standard data to the current user.

[0032] In the above implementation process, the receiving module receives the conversion data flow of multiple users and generates identification information for the flow. When the receiving module receives the user's access request each time, the conversion module can process the obtained data according to the conversion data flow corresponding to the current user obtained by the acquisition module, so that the final standard data format can be accepted by the current user. The sending module sends the standard data to the current customer. Based on the above implementation, it is possible to avoid repeated code writing, saving manpower and material resources.

[0033] Further, the process of converting data of the plurality of users includes a sequence of components;

[0034] The receiving module is also used to receive the conversion components used by the multiple users to convert data and the order in which the multiple users use the conversion components; and generate the component sequences of the multiple users according to the conversion components used by the multiple users to convert data and the order in which the multiple users use the conversion components.

[0035] In the above implementation process, the process of converting data includes a component sequence, the format of the data is limited, and the process of converting data for each user is to use various components to obtain data of different formats and convert the data of different formats. Therefore, the step of the receiving module receiving the process of converting data of multiple users is to receive the conversion components used by multiple users for converting data and the order in which the multiple users use the conversion components, and generate a sequence of components corresponding to each user in the multiple users according to the conversion components and the order in which the multiple users use the conversion components. Based on the above implementation, the process of converting data of multiple users can be quickly received.

[0036] Furthermore, the component sequence includes an acquisition component sequence and a conversion component sequence;

[0037] Acquire the target data according to the acquisition component sequence;

[0038] The target data is input into the conversion component sequence to obtain the standard data.

[0039] In the above implementation process, the process of each user obtaining standard data includes obtaining target data and converting the target data. Therefore, the component sequence includes an obtaining component sequence, a conversion component sequence, and a conversion module. The target data is obtained according to the obtaining component sequence; the target data is input into the conversion component sequence to obtain the standard data. Based on the above implementation, standard data can be quickly obtained.

[0040] Further, the process of converting data of the plurality of users includes a sequence of components;

[0041] The receiving module is also used to receive receivable data formats transmitted by multiple users; obtain multiple components in the database; and generate component sequences for the multiple users according to the receivable data formats of the multiple users and the multiple components.

[0042] In the above implementation process, the device can know which components should be applied to convert the data and the order in which these components should be used by receiving the receivable data formats transmitted by multiple users, thereby generating component sequences for multiple users. Based on the above implementation, component sequences for multiple users can be generated.

[0043] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in any one of the first aspects when executing the computer program.

[0044] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed on a computer, the computer executes the method as described in any one of the first aspects.

[0045] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a computer, enables the computer to execute the method as described in any one of the first aspects.

[0046] Other features and advantages disclosed in the present application will be described in the following description, or some features and advantages can be inferred or determined without doubt from the description, or can be learned by implementing the above-mentioned technology disclosed in the present application.

[0047] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0049] Figure 1 A flow chart of a data acquisition method provided in an embodiment of the present application;

[0050] Figure 2 A schematic diagram of a process flow for receiving and converting data provided in an embodiment of the present application;

[0051] Figure 3 A schematic diagram of a process for obtaining standard data provided in an embodiment of the present application;

[0052] Figure 4 A schematic diagram of the internal structure of a data acquisition device provided in an embodiment of the present application;

[0053] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0054] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0055] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0056] Example 1

[0057] The present application embodiment provides a data acquisition method, such as Figure 1 As shown, the method includes:

[0058] S1: a process of receiving conversion data of multiple users and generating identification information for the process, the identification information being used to identify the user;

[0059] S2: receiving an access request from the current user, where the access request includes identification information of the current user;

[0060] S3: a process of obtaining conversion data of the current user according to the identification information of the current user;

[0061] S4: acquiring target data according to the access request of the current user and the process of converting data of the current user, and converting the target data into standard data;

[0062] S5: Send the standard data to the current user.

[0063] In the above embodiment, the current user is one of the multiple users. The identification information can be the router address of each user.

[0064] The process of receiving conversion data of multiple users and generating identification information for the process, when each user's access request is received, the obtained data can be processed according to the process of conversion data corresponding to the current user, so that the final standard data format can be accepted by the current user. Based on the above implementation, it is possible to avoid repeated code writing, saving manpower and material resources.

[0065] In a possible implementation, before S1, the method further includes generating a template page, sending the page to the user's client, the page template includes various components, the components are used to convert data formats, and the page template allows multiple users to drag and drop various components to form their own data conversion process. Multiple users can use the data conversion process generated by themselves to obtain target data based on the data they can currently receive, and convert the target data into standard data. If the required standard data can be met, the data conversion process is uploaded.

[0066] For example, multiple users are medical platforms across the country. The above method can integrate interface resources of different data standards provided by local medical institutions, complete heterogeneous data integration, realize the interconnection and sharing of medical information, and facilitate the provision of service applications for hospital operation management, medical clinical decision-making, and convenient medical treatment for patients.

[0067] Business parties or developers can select the data conversion components they want to use in a visible way, and arrange them into a complete data access and conversion process in a visual and automated way, without developing business code, to achieve an efficient access and conversion interface. This implementation method can achieve simple operation and high efficiency.

[0068] In a possible implementation, when each user obtains data of other users, different data conversion processes may be used. Therefore, the identification information of each user may correspond to multiple data conversion processes. Each user's data conversion process also has its own number to facilitate subsequent calls.

[0069] In a possible implementation, Figure 2 As shown, S1 further includes:

[0070] S11: receiving conversion components used by multiple users to convert data and the order in which the multiple users use the conversion components;

[0071] S12: Generate component sequences for multiple users according to the conversion components used by the multiple users to convert data and the order in which the multiple users use the conversion components.

[0072] The process of converting data of multiple users includes a component sequence. The format of the data is limited. The process of converting data of each user is to use each component to obtain data of different formats and convert the data of different formats. Therefore, the steps of the process of receiving conversion data of multiple users are to receive conversion components used by multiple users for converting data and the order in which multiple users use the conversion components, and generate a sequence of components corresponding to each user in the multiple users according to the conversion components and the order in which multiple users use the conversion components. Based on the above implementation, the process of converting data of multiple users can be quickly received.

[0073] In a possible implementation, the component sequence includes obtaining a component sequence and converting a component sequence;

[0074] like Figure 3 As shown, S4 further includes:

[0075] S41: Acquire target data according to an acquisition component sequence;

[0076] S42: Input the target data into the conversion component sequence to obtain standard data.

[0077] In the above implementation process, the process of each user obtaining standard data includes obtaining target data and converting the target data. Therefore, the component sequence includes an acquisition component sequence and a conversion component sequence. The target data is obtained according to the acquisition component sequence; the target data is input into the conversion component sequence to obtain the standard data. Based on the above implementation, the standard data can be quickly obtained.

[0078] In a possible implementation, S1 may further include:

[0079] Receiving receivable data formats transmitted by multiple users;

[0080] Get multiple components in the database;

[0081] According to the receivable data formats of the multiple users and the multiple components, component sequences for the multiple users are generated.

[0082] By receiving the receivable data formats transmitted by multiple users, it is possible to know which components should be applied to convert the data and the order in which these components should be used, thereby generating component sequences for multiple users. Based on the above implementation, component sequences for multiple users can be generated.

[0083] In the above embodiment, the database refers to a component database that is pre-compiled by a programmer.

[0084] Example 2

[0085] The present application also provides a data acquisition device, such as Figure 4 As shown, the device comprises:

[0086] Receiving module 1, used for receiving a process of conversion data of multiple users, generating identification information for the process, the identification information is used to identify the user; receiving an access request of the current user, the access request including the identification information of the current user;

[0087] Acquisition module 2, a process for acquiring conversion data of the current user according to the identification information of the current user;

[0088] A conversion module 3, used to obtain target data according to the access request of the current user and the process of converting data of the current user, and convert the target data into standard data;

[0089] The sending module 4 is used to send the standard data to the current user.

[0090] In the above implementation process, the receiving module 1 receives the conversion data flow of multiple users and generates identification information for the flow. When the receiving module 1 receives the user's access request each time, the conversion module 3 can process the obtained data according to the conversion data flow corresponding to the current user obtained by the acquisition module 2, so that the format of the final standard data can be accepted by the current user. The sending module 4 sends the standard data to the current customer. Based on the above implementation, it is possible to avoid repeated code writing, saving manpower and material resources.

[0091] In one possible implementation, the process of converting data for multiple users includes a sequence of components;

[0092] The receiving module 1 is also used to receive the conversion components used by multiple users to convert data and the order in which the multiple users use the conversion components; and generate component sequences for multiple users according to the conversion components used by multiple users to convert data and the order in which the multiple users use the conversion components.

[0093] In the above implementation process, the process of converting data includes a component sequence, the format of the data is limited, and the process of converting data for each user is to use various components to obtain data of different formats and convert the data of different formats. Therefore, the steps of the process of receiving the conversion data of multiple users by the receiving module 1 are to receive the conversion components used by multiple users to convert data and the order in which the multiple users use the conversion components, and generate a sequence of components corresponding to each user in the multiple users according to the conversion components and the order in which the multiple users use the conversion components. Based on the above implementation, the process of converting data of multiple users can be quickly received.

[0094] In a possible implementation, the component sequence includes obtaining a component sequence and converting a component sequence;

[0095] Acquire target data according to the acquisition component sequence;

[0096] Input the target data into the conversion component sequence to obtain the standard data.

[0097] In the above implementation process, the process of each user obtaining standard data includes obtaining target data and converting the target data. Therefore, the component sequence includes an obtaining component sequence and a converting component sequence. The conversion module 3 obtains the target data according to the obtaining component sequence; inputs the target data into the converting component sequence to obtain the standard data. Based on the above implementation, the standard data can be quickly obtained.

[0098] In one possible implementation, the process of converting data for multiple users includes a sequence of components;

[0099] The receiving module 1 is also used to receive receivable data formats transmitted by multiple users; obtain multiple components in the database; and generate component sequences of multiple users according to the receivable data formats and multiple components of the multiple users.

[0100] In the above implementation process, by receiving the receivable data formats transmitted by multiple users, it is possible to know which components should be applied to convert the data and the order in which these components should be used, thereby generating component sequences for multiple users. Based on the above implementation, component sequences for multiple users can be generated.

[0101] like Figure 5 As shown, an embodiment of the present application also provides an electronic device, which may include a processor 51, a communication interface 52, a memory 53 and at least one communication bus 54. Among them, the communication bus 54 is used to realize the direct connection and communication of these components. Among them, the communication interface 52 of the device in the embodiment of the present application is used to communicate signaling or data with other node devices. The processor 51 can be an integrated circuit chip with signal processing capabilities.

[0102] The processor 51 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor 51 can also be any conventional processor, etc.

[0103] The memory 53 may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electric erasable programmable read-only memory (EEPROM), etc. The memory 53 stores computer readable instructions. When the computer readable instructions are executed by the processor 51, the device can execute the above-mentioned Figure 1-3 The method embodiment involves various steps.

[0104] Optionally, the electronic device may further include a storage controller and an input / output unit. The memory 53, the storage controller, the processor 51, the peripheral interface, and the input / output unit are electrically connected to each other directly or indirectly to achieve data transmission or interaction. For example, these components may be electrically connected to each other via one or more communication buses 54. The processor 51 is used to execute executable modules stored in the memory 53, such as software function modules or computer programs included in the device.

[0105] The input and output unit is used to provide users with the task creation and to create an optional time period or preset execution time for the task to enable interaction between the user and the server. The input and output unit can be, but is not limited to, a mouse and a keyboard.

[0106] Understandably, Figure 5 The structure shown is for illustration only. The electronic device may also include Figure 5 More or fewer components as shown, or with Figure 5 Different configurations are shown. Figure 5 Each component shown in the figure can be implemented by hardware, software or a combination thereof.

[0107] The embodiment of the present application also provides a storage medium having instructions stored thereon. When the instructions are run on a computer, the method of the method embodiment is implemented when the computer program is executed by a processor. To avoid repetition, it will not be described again here.

[0108] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the method of the method embodiment.

[0109] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0110] In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0111] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0112] The above description is only an embodiment of the present application and is not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the scope of protection of the present application. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings.

[0113] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0114] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. A data acquisition method, characterized in that: include: A process of receiving conversion data of a plurality of users, and generating identification information for the process, wherein the identification information is used to identify the users; receiving an access request from a current user, wherein the access request includes identification information of the current user; A process of acquiring conversion data of the current user according to identification information of the current user; Acquire target data according to the access request of the current user and the process of converting data of the current user, and convert the target data into standard data; Sending the standard data to the current user; The process of converting data of the plurality of users includes a sequence of components; The steps of the process of receiving conversion data of multiple users include: receiving conversion components used by the plurality of users to convert data and an order in which the plurality of users use the conversion components; generating component sequences for the multiple users according to the conversion components used by the multiple users to convert data and the order in which the multiple users use the conversion components; The component sequence includes an acquisition component sequence and a conversion component sequence; The step of acquiring target data according to the access request of the current user and the process of converting the data of the current user, and converting the target data into standard data comprises: Acquire the target data according to the acquisition component sequence; The target data is input into the conversion component sequence to obtain the standard data.

2. The data acquisition method according to claim 1, characterized in that: The steps of the process of receiving conversion data of multiple users include: receiving a receivable data format transmitted by the plurality of users; Acquire multiple components in a database; the database is a component database pre-compiled by a programmer; Generate component sequences for the multiple users according to the receivable data formats of the multiple users and the multiple components.

3. A data acquisition device, characterized in that: include: A receiving module, used for receiving a process of conversion data of multiple users, and generating identification information for the process, wherein the identification information is used for identifying the users; receiving an access request from a current user, wherein the access request includes identification information of the current user; An acquisition module, configured to acquire the conversion data of the current user according to the identification information of the current user; A conversion module, used to obtain target data according to the access request of the current user and the process of converting data of the current user, and convert the target data into standard data; A sending module, used for sending the standard data to the current user; The process of converting data of the plurality of users includes a sequence of components; The receiving module is further used to receive the conversion components used by the multiple users to convert data and the order in which the multiple users use the conversion components; generate the component sequences of the multiple users according to the conversion components used by the multiple users to convert data and the order in which the multiple users use the conversion components; The component sequence includes an acquisition component sequence and a conversion component sequence; The conversion module is specifically used for: Acquire the target data according to the acquisition component sequence; The target data is input into the conversion component sequence to obtain the standard data.

4. The data acquisition device according to claim 3, characterized in that: The receiving module is also used to receive the receivable data format transmitted by the multiple users; obtain multiple components in the database; the database is a component database pre-compiled by the programmer; Generate component sequences for the multiple users according to the receivable data formats of the multiple users and the multiple components.

5. An electronic device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the data acquisition method according to claim 1 or 2 when executing the computer program.

6. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the computer is enabled to execute the data acquisition method according to claim 1 or 2.

Citation Information

Patent Citations

  • Message processing method, system and device, equipment and storage medium

    CN112905680A