CN111782718B - Plug-in data reporting system and data reporting method - Google Patents
Plug-in data reporting system and data reporting method Download PDFInfo
- Publication number
- CN111782718B CN111782718B CN202010799238.0A CN202010799238A CN111782718B CN 111782718 B CN111782718 B CN 111782718B CN 202010799238 A CN202010799238 A CN 202010799238A CN 111782718 B CN111782718 B CN 111782718B
- Authority
- CN
- China
- Prior art keywords
- data
- plug
- target
- storage
- verification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title abstract description 21
- 238000003860 storage Methods 0.000 claims abstract description 111
- 238000012795 verification Methods 0.000 claims abstract description 73
- 238000013500 data storage Methods 0.000 claims abstract description 35
- 238000013524 data verification Methods 0.000 claims abstract description 25
- 238000004458 analytical method Methods 0.000 claims abstract description 23
- 238000006243 chemical reaction Methods 0.000 claims abstract description 23
- 238000012384 transportation and delivery Methods 0.000 claims description 12
- 238000002716 delivery method Methods 0.000 claims 1
- 238000007405 data analysis Methods 0.000 abstract 2
- 238000007726 management method Methods 0.000 description 16
- 238000011161 development Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 238000013507 mapping Methods 0.000 description 8
- 230000007246 mechanism Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 238000013461 design Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000001105 regulatory effect Effects 0.000 description 4
- 239000008186 active pharmaceutical agent Substances 0.000 description 3
- 230000007547 defect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 239000003550 marker Substances 0.000 description 3
- 230000004075 alteration Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000004931 aggregating effect Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013506 data mapping Methods 0.000 description 1
- 238000013501 data transformation Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2462—Approximate or statistical queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Probability & Statistics with Applications (AREA)
- Fuzzy Systems (AREA)
- Computational Linguistics (AREA)
- Mathematical Physics (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a plug-in data reporting system and a data reporting method. The data reporting system comprises a plug-in library. The plug-in library includes a plurality of plug-ins. The data reporting system further comprises a data access component, a data analysis and conversion component, a data verification component and a data storage component. When the user reports data through the data reporting system, the data access component, the data analysis and conversion component, the data verification component and the data storage component can call the target plugin in the plugin library to respectively realize the access, analysis and conversion, verification and storage of the data.
Description
Technical Field
The present disclosure relates to the field of information technologies, and in particular, to a pluggable data reporting system and a data reporting method.
Background
In the digital age, the requirements for collecting, reporting and managing various data widely exist in the fields of supervision management, statistical audit and the like. Such as chinese people's banks, need to collect data from the banking institutions under supervision for aggregate statistics and supervision of financial data. Local financial institutions also need to collect data from the administered financial institutions-like to enable supervision of the financial institutions-like. Different fields and different scenes have different data formats, different data reporting modes, different data storage modes and different reporting periods. At present, professional development is basically carried out in each field in a professional customization mode to realize data reporting, so that the development period is long and the labor and financial resources are consumed. For example, in the conventional data reporting scheme, hard coding development is performed according to the data format content of the data reported by the user, and code development is required whenever the user needs to add and modify the data format, add the data reporting mode or the data storage mode, which is time-consuming, laborious and difficult to maintain.
Disclosure of Invention
In order to solve the technical problems of high time and labor cost and difficult maintenance caused by the traditional customized data reporting mode, the application discloses a plug-in data reporting system, which comprises: a plug-in library comprising a plurality of plug-ins; the data access component is configured to receive a message from the reporting end, wherein the message comprises target data; a data parsing conversion component comprising at least one first plug-in interface and configured to: receiving the target data from the data access component, selecting a target analysis plug-in from at least one analysis plug-in, sending the target data to the target analysis plug-in through the at least one first plug-in interface to analyze the target data, receiving the analyzed analysis data of the target data from the target analysis plug-in through the at least one first plug-in interface, and converting the format of the analysis data into a target format; a data verification component configured to verify the parsed data; and a data storage component configured to store the parsed data to a target storage system of a storage medium.
In some embodiments, wherein each of the at least one parsing plug-in comprises: the data input format of the data input interface corresponds to the data format of the output end of the first plug-in interface; and the data output interface outputs a data format corresponding to the data format of the input data end of the first plug-in interface.
In some embodiments, wherein the at least one parsing plug-in comprises at least one of an Excel parsing engine, a CSV streaming parsing engine, an API data transformation engine, and an XML/DAT format parsing engine.
In some embodiments, wherein the data verification component comprises at least one second plug-in interface and is configured to: selecting a target verification plug-in from at least one data verification plug-in; transmitting the parsed data to the target verification plug-in through the at least one second plug-in interface; and receiving a verification result from the target verification plug-in through the at least one second plug-in interface.
In some embodiments, the target verification plug-in verifies the parsed data according to a preset verification rule, wherein the verification rule includes at least one of a format verification rule, an intra-row rule verification rule, a uniqueness verification rule, a script verification rule, and an inter-table verification rule.
In some embodiments, the at least one second plug-in interface selects the target verification plug-in from the at least one verification plug-ins according to configuration information.
In some embodiments, wherein the data storage component comprises at least one third plug-in interface and is configured to: selecting a target storage plugin from at least one data storage plugin; transmitting the verified data to the target storage plugin through the at least one third plugin interface; and receiving a storage result from the target storage plug-in through the at least one third plug-in interface.
In some embodiments, wherein the at least one storage plugin comprises at least one of a MySQL database storage plugin, an OceanBase database storage plugin, a HIVE database storage plugin, an Oracel database storage plugin, a SQL Server database storage plugin, a local file system storage plugin, a network file system NFS storage plugin, a Hadoop file system HDFS storage plugin, and an object storage OSS storage plugin; and the storage result includes a storage path of the target data.
In some embodiments, the at least one third plug-in interface selects the target storage plug-in from the at least one storage plug-in according to configuration information.
In some embodiments, wherein the data access component comprises at least one fourth plug-in interface and is configured to: selecting a target access plug-in from at least one data access plug-in; the message is sent to the target access plug-in through the at least one fourth plug-in interface; and receiving the decrypted and integrity verified data of the target data from the target access plug-in through the at least one fourth plug-in interface.
In some embodiments, the at least one data access plug-in includes at least one of a manual web page upload plug-in, a post-front-end-of-the-line auto-upload plug-in, an OpenAPI call upload plug-in, and a web page fill plug-in.
In some embodiments, the datagram delivery system further comprises: a configuration component includes at least one configuration interface configured to receive configuration information.
The application also discloses a data reporting method, which comprises the following steps: receiving a message from a reporting end through at least one data access plug-in, wherein the message comprises target data; loading a target analysis plug-in according to a preset analysis rule, analyzing the target data and converting the target data into a target format; loading a target verification plug-in according to a preset verification rule, and verifying the analyzed target data; and loading the target storage plug-in according to a preset storage rule, and storing the target data passing the verification into a target storage system.
The data reporting system can flexibly and extendably support different report template formats, different data formats, different reporting modes, different verification modes and different storage modes by adopting layered, plug-in, componentization and configured architecture design, so that the data reporting system can be widely reused in various fields and various scenes, and the defects of long development period, labor and financial consumption, difficult maintenance and the like caused by customized development are avoided.
Drawings
Fig. 1 shows an application scenario schematic diagram of a data reporting system according to an embodiment of the present application;
fig. 2 shows a schematic hardware structure of a datagram system according to an embodiment of the present application; and
fig. 3 shows an architecture block diagram of a datagram system according to an embodiment of the present application.
Detailed Description
The following description provides specific applications and requirements to enable any person skilled in the art to make and use the teachings of the present application. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the application. Thus, the present application is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the claims.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting.
These and other features of the present application, as well as the operation and function of the related elements of structure, as well as the combination of parts and economies of manufacture, may be significantly improved upon in view of the following description. All of which form a part of the present application, reference is made to the accompanying drawings. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the application.
The following description may significantly improve the operation and function of these and other features of the present application, as well as related elements of structure, as well as the economic efficiency of the assembly and manufacture. All of which form a part of the present application with reference to the accompanying drawings. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the application. It should also be understood that the drawings are not drawn to scale.
Fig. 1 shows an application scenario of a datagram system 300 according to an embodiment of the present application. Specifically, the application scenario may include the datagram system 300, the terminal device 130, the network 120, and the database 150.
The user 110 may report the report file to the data reporting system 300 through the terminal 130. The user 110 can report the report file to the data reporting system 300 through the foreground of the data reporting system 300 installed on the terminal 130. By way of example, the foreground may include, but is not limited to, a browser, an application, and the like.
There are a variety of ways in which the user 110 may report the report file to the data reporting system. As an example, the reporting manner may include, but is not limited to, manual web page upload, automatic upload after verification by a front-end processor, web page fill, call a public application program interface (OpenAPI) report integrated in a third party system, and so on.
Terminal device 130 may include an intelligent device that carries a report. For example, the terminal device may be a terminal device of the financial institution branch, or may be a terminal device of the customer 110 served by the financial institution or a regulatory agency of the financial institution. In some embodiments, the terminal device 130 may include a mobile device 130-1, a tablet computer 130-2, a notebook computer 130-3, a built-in device of the motor vehicle 130-4, or the like, or any combination thereof. In some embodiments, the terminal device 130 may be installed with one or more applications. The application is capable of providing the user 110 with the ability to interact with the outside world via the network 120 as well as an interface. The target application may be any application program running on the terminal device 130. For example, the target application may be an application program of the financial service institution having a data statistics function.
The network 120 may facilitate the exchange of information and/or data. As shown in fig. 1, terminal device 130, data delivery system 300, database 150 may be connected to network 120 and communicate information and/or data with each other via network 120. For example, the data reporting system 300 may transmit a data table from the terminal device 130 through the network 120, and may also transmit table data to the terminal device 130. In some embodiments, network 120 may be any type of wired or wireless network, or a combination thereof. For example, network 120 may include a cable network, a wired network, a fiber optic network, a telecommunications network, an intranet, the internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a Public Switched Telephone Network (PSTN), a bluetooth network, a ZigBee network, a Near Field Communication (NFC) network, or the like. In some embodiments, network 120 may include one or more network access points. For example, network 120 may include wired or wireless network access points, such as base stations and/or internet switching points 120-1, 120-2, through which one or more components of terminal device 130, datagram system 300, database 150 may connect to network 120 to exchange data and/or information.
Database 150 may store data mappings or instructions for performing the methods of table content mapping described herein. For example, database 150 may be one or more databases of a data center of the financial institution. Database 150 may be a centralized database or a decentralized database.
Database 150 may store data and/or instructions. In some embodiments, database 150 may store data obtained from terminal device 130. In some embodiments, database 150 may store data and/or instructions that data reporting system 300 may perform or be used to perform the methods of table content mapping described in this application. In some embodiments, database 150 may be a stand-alone storage device or may be part of datagram system 300. In some embodiments, database 150 may be a variety of suitable volatile and/or non-transitory storage media including, for example, mass storage, removable storage, volatile read-write memory, read-only memory (ROM), or the like, or any combination thereof. For example, mass storage may include non-transitory storage media (non-transitory storage medium) such as magnetic disks, optical disks, solid state drives, and the like; removable storage may include flash drives, floppy disks, optical disks, memory cards, zip disks, tape, and the like. Typical volatile read-write memory can include Random Access Memory (RAM). Example RAM may include Dynamic RAM (DRAM), dual date rate synchronous dynamic RAM (DDR SDRAM), static RAM (SRAM), thyristor RAM (T-RAM), zero capacitance RAM (Z-RAM), and the like. Exemplary ROMs may include Mask ROM (MROM), programmable ROM (PROM), virtual programmable ROM (PEROM), electrically and Electronically Programmable ROM (EEPROM), compact disk (CD-ROM), and digital versatile disk ROM, among others. In some embodiments, database 150 may be implemented on a cloud platform. For example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an inter-cloud, or the like, or any combination thereof.
Datagram system 300 may include one or more servers. For example, datagram system 300 may be one or more servers of a data center of a financial institution. For ease of description, in the following description of the present application, a server is taken as an example to describe the data reporting system 300 described in the present application. As an example, fig. 2 shows a schematic hardware structure of a datagram system 300 according to an embodiment of the present application.
As shown in fig. 2, datagram system 300 includes at least one memory 230 and at least one processor 220. In some embodiments, datagram system 300 may also include a communication port 250 and an internal communication bus 210. Meanwhile, datagram system 300 may also include I/O component 260.
Internal communication bus 210 may connect the different system components including memory 230 and processor 220.
I/O component 260 supports input/output between datagram system 300 and other components (e.g., terminal device 130).
The communication port 250 is used for data communication between the data reporting system 300 and the outside. For example, the data reporting system 300 may be connected to the network 120 through the communication port 250, further receive the data table sent by the user 110, further send data to the database 150 through the communication port 250 according to the table mapping relationship, and store the content of the data table in the database 150.
The at least one processor 220 communicates with at least one memory 230 over an internal communication bus 210. The at least one processor 220 is configured to execute the at least one set of instructions, and when the at least one processor 220 executes the at least one set of instructions, the datagram system 300 implements the method for mapping table contents provided herein. The processor 220 may perform all the steps involved in the method of table content mapping. Processor 220 may be in the form of one or more processors, in some embodiments processor 220 may include one or more hardware processors, such as microcontrollers, microprocessors, reduced Instruction Set Computers (RISC), application Specific Integrated Circuits (ASIC), application specific instruction set processors (ASIP), central Processing Units (CPU), graphics Processing Units (GPU), physical Processing Units (PPU), microcontroller units, digital Signal Processors (DSP), field Programmable Gate Arrays (FPGA), advanced RISC Machines (ARM), programmable Logic Devices (PLD), any circuit or processor capable of executing one or more functions, or the like, or any combination thereof. For illustrative purposes only, only one processor 220 is depicted in the datagram system 300 herein. However, it should be noted that the datagram system 300 in the present application may also include multiple processors, and thus, the operations and/or method steps disclosed in the present application may be performed by one processor as described in the present application, or may be performed jointly by multiple processors. For example, if in the present application processor 220 of datagram system 300 performs steps a and B, it should be understood that steps a and B may also be performed jointly or separately by two different processors 220 (e.g., a first processor performing step a, a second processor performing step B, or both first and second processors performing steps a and B).
Memory 230 may include a data storage device. The data storage device may be a non-transitory storage medium or a transitory storage medium. For example, the data storage device may include one or more of a magnetic disk 232, a Read Only Memory (ROM) 234, or a Random Access Memory (RAM) 236. Memory 230 also includes at least one set of instructions stored in the data storage device. The instructions are computer program code that may include programs, routines, objects, components, data structures, procedures, modules, etc. that perform the data processing methods provided herein. In some embodiments, memory 230 may be included in or a portion of database 150.
Memory 230 may store data obtained from terminal device 130 in some embodiments. Such as a table uploaded through the terminal device 130, configuration information entered into a user interface displayed on the terminal device, etc. In some embodiments, memory 230 may store data and/or instructions that processor 220 may perform exemplary methods. Memory 230 may include a data storage unit and an instruction storage unit. The data storage unit may store various data in the system, such as. The instruction storage unit may store various instructions, including one or more sets of table content mapping instructions.
Fig. 3 shows a block diagram of an architecture of a datagram system 300 provided in accordance with an embodiment of the present application. Specifically, datagram system 300 can include a data access component 310, a data parsing conversion component 320, a data verification component 330, and a data storage component 340.
The data access component 310, the data parsing conversion component 320, the data verification component 330, and the data storage component 340 can each be one or more sets of instructions stored within the memory 230.
The datagram system 300 may include one or more plug-in libraries. The plug-in library may comprise several plug-ins. Each of the number of plug-ins may include one or more sets of instructions.
The data access component 310 may be one or more sets of instructions stored within the memory 230. Data access component 310 may be part of a host application of datagram system 300.
The data access component 310 is configured to receive messages from the messaging end. As an example, the reporting end may be the terminal 130 in the application scenario shown in fig. 1.
The data access component 310 can include at least one fourth plug-in interface. The fourth plug-in interface may be a standard interface provided by the data access component 310 as part of the main application of the datagram system 300. The standard interface may allow a third party to write plug-ins to interact with the data access component 310. The third party written plug-ins include programs, routines, objects, components, data structures, procedures, modules, etc. that may be independent of the host application. The host application provides services to the plug-in that can be used, allowing the plug-in to register itself in the host application, as well as the protocol for exchanging data with the plug-in.
The fourth plug-in interface may include one or more interface documents that are predefined and stored in the memory 230. The interface document may define specifications for the data access component 310 to interact with a third party written plug-in. By way of example, the interface document may include, but is not limited to, methods, uri, request parameters, return parameters, and the like. The method may include, but is not limited to, adding (post), modifying (put), deleting (delete), retrieving (get), and so forth.
The fourth plug-in interface may plug in a data access plug-in. The data access plug-in may receive data reported by the user 110 via the terminal 130. In some embodiments, the data access plug-in may also decrypt and verify the integrity of the received data.
The fourth plug-in interface is configured to: selecting a corresponding target access plug-in from at least one data access plug-in; the message is sent to the target access plug-in through the at least one fourth plug-in interface; and receiving the decrypted and integrity verified data of the target data from the target access plug-in through the at least one fourth plug-in interface.
The at least one data access plug-in comprises at least one of a manual webpage uploading plug-in, an automatic uploading plug-in after the front end processor is checked, an OpenAPI call uploading plug-in and a webpage filling plug-in.
The data access component 310 may invoke the target data access plug-in through the fourth plug-in interface to implement the receipt of data.
In some embodiments, the data access component 310 may invoke the target access plug-in corresponding to the reporting mode according to parameters of the reporting mode that are pre-configured. For example, if the report mode is "web page filling" configured in advance through the configuration information, when the user 110 reports the report through the web page displayed on the terminal 130, the data access component 310 automatically invokes the target access plug-in corresponding to the "web page filling" mode according to the configuration information, and receives the message from the report end through the target access plug-in.
In some embodiments, the data access component 310 can automatically invoke the target access plug-in based on the data type of the report submitted by the user 110.
In some embodiments, the data access component 310 may further invoke the target access plug-in according to a parameter that identifies a reporting mode and is carried in a message that is reported from the reporting end.
The at least one data access plug-in refers to instructions implementing a fourth interface specification of the data access component 310. The at least one data access plug-in marks the identity of the at least one data access plug-in through the second interface, and receives an event response from the main program. The data access component 310 identifies the identity of the data access plug-in through the fourth interface.
The data parsing conversion component 320 may be one or more sets of instructions stored within the memory 230. The data parsing component 320 may be part of a host application of the datagram system 300. The data parsing conversion component 320 can receive the target data from the data access component 310. The data parsing conversion component 320 can parse the target data.
The data parsing conversion component 320 can include at least one first plug-in interface. The first plug-in interface allows the data parsing conversion plug-in to interact with the datagram system 300 in compliance with its specifications.
The data resolution conversion component 320 can plug-in one or more resolution plug-ins. The parsing plug-in refers to an instruction implementing the first plug-in interface. The parsing plug-in can parse the target data. In some embodiments, the parsing plug-in may convert the format of the target data to a target data format.
The data parsing conversion component 320 is configured to: receiving the target data from the data access component, selecting a target analysis plug-in from at least one analysis plug-in, sending the target data to the target analysis plug-in through the at least one first plug-in interface to analyze the target data, receiving the analyzed analysis data of the target data from the target analysis plug-in through the at least one first plug-in interface, and converting the format of the analysis data into a target format.
The data parsing conversion component 320 may select a target parsing plug-in from at least one parsing plug-in, load the target parsing plug-in to parse the target data, and convert the format of the parsed data into a target format.
As an example, the at least one parsing plug-in includes at least one of an Excel parsing engine, a CSV streaming parsing engine, an API data conversion engine, and an XML/DAT format parsing engine.
Each of the at least one parsing plug-in includes: the data input interface has a data input format corresponding to the data format of the output end of the first plug-in interface, and the data output interface has a data format corresponding to the data format of the input data end of the first plug-in interface.
In this way, the parsing plug-in can convert the target data received from the data access component 310 into a target data format.
The target analysis plug-in can analyze the data according to a preset analysis rule. As an example, the parsing rules may include a positioning policy for each data item in the report. For example, in some embodiments, for a data item in a one-dimensional mindset report, the data item may be located based on the column number of the column in which the data item is located. For example, in some embodiments, for a data item located in a fixed cell in a two-dimensional report, the data item may be located based on the coordinates of the cell in which the data item is located. For example, in some embodiments, for a data item located in an unfixed cell in a two-dimensional report, the data item may be located based on the paragraph start marker text, end marker text, and left marker text of the data item.
In some embodiments, the data resolution conversion component 320 can select the target resolution plug-in based on the type of data. For example, when the user 110 uploads an Excel report through the terminal 130, the data parsing conversion component 320 automatically selects an Excel parsing engine to parse the data.
In some embodiments, the data resolution conversion component 320 can invoke a target resolution plug-in corresponding to a resolution parameter according to a pre-configured resolution parameter. For example, when the supervision organization configures a certain report parsing mode in the configuration information to be EXCEL parsing, when the user 110 reports the report, the data parsing conversion component 320 may call an EXCEL parsing engine corresponding to the parameter according to the configured parameter, and parse the target data through the EXCEL parsing engine.
The data verification component 330 may be one or more sets of instructions stored within the memory 230. Data verification component 330 may be part of the host application of datagram system 300. The data verification component 330 may receive parsed data from the data parsing conversion component 320. The data parsing conversion component 330 may verify the parsed data.
The data verification component 330 may include at least one second plug-in interface. The second plug-in interface allows the data verification plug-in that meets its specifications to interact with the host application of the datagram system 300.
The data verification component 330 may plug-in one or more verification plug-ins. The verification plug-in refers to an instruction implementing the second plug-in interface. The verification plug-in can verify the parsed data.
The data verification component 330 may select a target verification plug-in from at least one verification plug-in, load the target verification plug-in to verify the parsed data.
The data verification component 330 is configured to: selecting a corresponding target verification plug-in from at least one data verification plug-in; transmitting the parsed data to the target verification plug-in through the at least one second plug-in interface; and receiving a verification result from the target verification plug-in through the at least one second plug-in interface.
In some embodiments, the data verification component 330 may invoke a target verification plug-in corresponding to a pre-configured verification parameter based on the verification parameter. For example, when the supervision organization configures a certain report verification manner including format verification and uniqueness verification in the configuration information, when the user 110 reports the report through the terminal 130, the data verification component 330 may call a verification plug-in corresponding to the parameter according to the configured parameter, and verify the target data through the verification plug-in.
In some embodiments, the target verification plug-in may verify the parsed data according to a preset verification rule. By way of example, the check rules may include, but are not limited to, format check rules, inline rule check rules, uniqueness check rules, script check rules, inter-table check rules, and the like.
As an example, the data verification rules may specify the format, range of values, validity verification rules, etc. of the data items in the report. For example, the data items in the report are in some text format and some are in numerical format; then, whether the format of the data items accords with the preset format. For example, whether the value of the data item is within a preset range of values. For example, the number length of the identity data, the mobile phone number data and the like meets the requirement, and the data is valid data. In addition, the verification rules may also include cross-verification rules between the data items in the report. For example, whether the data items follow a preset rule, for example, whether the product of the data in the 7 th column and the data in the 4 th column is equal to the data in the 6 th column, and so on.
The verification result of the target verification plug-in on the target data may include pass or fail. When the verification result shows that the target data passes the verification, the data verification component 330 transmits the data passing the verification to the data storage component 340. When the verification result shows that the target data does not pass the verification, the data teaching group room 330 may inform the user of the change of the data by displaying notification information on the display device of the terminal 130.
The data storage component 340 may be one or more sets of instructions stored within the memory 230. Data storage component 340 may be part of the host application of datagram system 300. The data storage component 340 may store parsed and verified data to the target storage system 390.
The storage system 390 may include both structured data storage systems and unstructured data storage systems.
By way of example, the structured storage system may include, but is not limited to, a MySQL database, an OceanBase database, a HIVE database, an Oracel database, an SQL Server database, and the like.
By way of example, the unstructured storage system may include, but is not limited to, a local file system, a network file system NFS, a Hadoop file system HDFS, an object store OSS, and the like.
The data storage component 340 may include at least one third plug-in interface. The third plug-in interface allows a data storage plug-in that meets its specifications to interact with the datagram system 300.
The data storage component 340 may plug in one or more storage plugins. The storage plug-in refers to an instruction implementing the third plug-in interface. The storage plugin may store parsed and verified data to a target storage system.
The data storage component 340 may select a target storage plugin from the at least one storage plugin, load the target storage plugin, and store the parsed and verified data to the target storage system. The data storage component 340 may select a target storage plugin from the at least one data storage plugin; transmitting the verified data to the target storage plugin through the at least one third plugin interface; and receiving a storage result from the target storage plug-in through the at least one third plug-in interface.
As an example, the at least one storage plugin may include, but is not limited to, mySQL database storage plugin, oceanBase database storage plugin, HIVE database storage plugin, oracel database storage plugin, SQL Server database storage plugin, local file system storage plugin, network file system NFS storage plugin, hadoop file system HDFS storage plugin, object storage OSS storage plugin, and the like.
In some embodiments, the data storage component 340 may invoke a target storage plugin corresponding to a storage parameter according to a pre-configured storage parameter. For example, if the storage mode is a file storage system configured in advance through the configuration information, when the user 110 reports the report form through the web page displayed on the terminal 130, the data storage component 340 will automatically call the file system storage plugin corresponding to the parameter according to the configuration information, and store the parsed and verified data to the target file system through the file system storage plugin.
The target storage plug-in can store the analyzed and verified data to the target storage system according to a preset storage rule. For example, the target storage rule may include, but is not limited to, a mapping relationship between a report and a database table, a mapping relationship between a data item in a report and a database table data item, and so on.
After the target storage plug-in successfully stores the target data to the target storage system, the storage path of the target data can be returned. Thus, when the report needs to be checked, updated, modified or deleted in the future, the report can be searched according to the storage path.
Thus, data submitted by user 110 is successfully collected into the data storage system by data access component 310, data parsing component 320, data verification component 330, and data storage component 340 via data messaging system 300.
The datagram delivery system 300 retains the core execution framework program of the following components by employing a hierarchical, componentized, and configurable architecture design: the data access component 310 receives messages from the messaging end; a data parsing and converting component 320, configured to convert the message into parsed data in a target format; a data verification component 330 for verifying the parsed data; and a data storage component 340 that stores the parsed data in the target format. The framework program eliminates the difference of the input end data formats, and uniformly converts the input end data formats into preset target formats and processes the data in the preset target formats no matter what the input end data are. The data reporting system 300 described in the present application may access different plugins for messages with different formats through a plugin architecture design, process the messages with different formats into data with a uniform format through the plugin, and then access the data into the core execution framework program for data processing. In this way, when the data reported by the reporting end is in a new data format, the staff does not need to modify the core execution framework program, and only needs to independently write a specific plug-in for the message in the new data format. Therefore, different report template formats, different data formats, different reporting modes, different verification modes and different storage modes can be flexibly and extendably supported, and the method can be widely reused in various fields and various scenes, and the defects of long development period, labor and financial resource consumption, difficult maintenance and the like caused by customized development are avoided.
In some embodiments, the data reporting system 300 may further include a configuration component 350, a reporting management component 360, a rights management component 370, and a data query component 380 to effectively manage and rights isolate the huge amount of data collected, further ensuring efficient use and security of the data.
In some embodiments, data reporting system 300 may also include a reporting management component 360. The report management component 360 can manage report status of the report. For example, reporting status for a report may be categorized into "reported" and "not reported". Report management component 360 can manage the status of the report. The report management component 360 can also issue message notifications to the reporting body based on the report status of the report. The report management component 360 can also manage template delivery, template version, report data, late report, missing report, and urge report of the multi-terminal report mechanism.
In some embodiments, datagram system 300 may also include a configuration component 350. Configuration component 350 includes at least one configuration interface. The at least one configuration interface is configured to receive configuration information. User 110 may configure parameters of the submitted data through a configuration interface displayed on terminal 130. For example, user 110 may configure report types, data formats, reporting mechanisms, etc. for reporting data through a configuration interface. Personnel or developers of the supervision authorities can also configure report forms through configuration interfaces, such as report form reporting modes, analysis rules, verification rules, storage types, authorities, excel templates, APIs, filling data items, global parameters and the like. The configuration interface provides a visual operation interface to the user, so that the data reporting system 300 has good user friendliness.
In some embodiments, datagram system 300 may include a rights management component 370. Rights management component 370 may include a functional rights management module and a data rights management module.
The functional rights management component enables different users to access only the functions that are assigned rights by assigning different roles to the users. For example, a bank in city a as a regulatory agency has jurisdictional rights only to branches in each region/county of city a in its jurisdiction. Therefore, the functional authority management module can be used for configuring the functional authority of a bank in A city, so that the bank in A city can only send the report task and/or the report template to the branch office with the functional authority.
The data rights management module may manage the data rights received by the data reporting system 300. The data rights management module may ensure data isolation between different institutions or departments. For example, by setting the data authority, the a mechanism can only view and change the data of the report issued by itself, and the B mechanism can only view and change the data of the report issued by the B mechanism.
In some embodiments, datagram delivery system 300 may also include a data query component 380. The data query component 380 supports querying of the raw submitted data, the parsed stored data, and the statistical results of the data. For example, the report is uploaded by the regulatory agency via the data reporting system 300, and the data reporting system 300 stores the report in the file storage system. The person under supervision and/or the person under supervision can query the data already submitted by the foreground of the data submitting system 300 displayed on the terminal 130. For example, a regulatory agency can perform detail, report, or statistical queries on the submitted data through a data query module in the data messaging system 300.
In summary, the present application provides a data reporting system. The data reporting system realizes abstraction and multiplexing of functions by aggregating and classifying different functions according to layers. The data system expands the functions of the product by means of plug-in units without modifying the original product codes. The data reporting system multiplexes by packing the functional modules into components. The data reporting system can support the check sum reporting of reports with different formats in a visual configuration modification mode, and avoids code development again.
The data reporting system can flexibly and extendably support different report template formats, different data formats, different reporting modes, different verification modes and different storage modes by adopting layered, plug-in, componentization and configured architecture design, so that the data reporting system can be widely reused in various fields and various scenes, and the defects of long development period, labor and financial consumption, difficult maintenance and the like caused by customized development are avoided.
The application also provides a data reporting method, which comprises the following steps: receiving a message from a reporting end through at least one data access plug-in, wherein the message comprises target data; loading a target analysis plug-in according to a preset analysis rule, analyzing the target data and converting the target data into a target format; loading a target verification plug-in according to a preset verification rule, and verifying the analyzed target data; and loading a target storage plug-in according to a preset storage rule, and storing the target data passing the verification into a target storage system.
Specific steps of the data reporting method may refer to the description of the data reporting system 300, and for brevity, will not be described herein.
In view of the foregoing, it will be evident to a person skilled in the art that the foregoing detailed disclosure may be presented by way of example only and may not be limiting. Although not explicitly described herein, those skilled in the art will appreciate that the present application is intended to embrace a variety of reasonable alterations, improvements and modifications to the embodiments. Such alterations, improvements, and modifications are intended to be proposed by this application, and are intended to be within the spirit and scope of the exemplary embodiments of this application.
Furthermore, certain terms in the present application have been used to describe embodiments of the present application. For example, "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. Thus, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined as suitable in one or more embodiments of the application.
It should be appreciated that in the foregoing description of embodiments of the present application, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the application. Alternatively, the present application is directed to various features that are dispersed throughout a plurality of embodiments of the present application. However, this is not to say that a combination of these features is necessary, and it is entirely possible for a person skilled in the art to extract some of them as separate embodiments to understand them at the time of reading this application. That is, embodiments in this application may also be understood as an integration of multiple secondary embodiments. While each secondary embodiment is satisfied by less than all of the features of a single foregoing disclosed embodiment.
In some embodiments, numbers expressing quantities or properties used to describe and claim certain embodiments of the present application are to be understood as being modified in some instances by the term "about", "approximately" or "substantially". For example, unless otherwise indicated, "about", "approximately" or "substantially" may mean a 20% change in the value it describes. Accordingly, in some embodiments, the numerical parameters set forth in the written description and attached claims are approximations that may vary depending upon the desired properties sought to be obtained by the particular embodiment. In some embodiments, numerical parameters should be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the embodiments of the disclosure are approximations, the numerical values set forth in the specific examples are reported as precisely as possible.
Each patent, patent application, publication of patent application, and other materials, such as articles, books, specifications, publications, documents, articles, etc., cited herein are hereby incorporated by reference. The entire contents for all purposes, except for any prosecution file history associated therewith, may be any identical prosecution file history inconsistent or conflicting with this file, or any identical prosecution file history which may have a limiting influence on the broadest scope of the claims. Now or later in association with this document. For example, if there is any inconsistency or conflict between the description, definition, and/or use of terms associated with any of the incorporated materials, the terms in the present document shall prevail.
Finally, it is to be understood that the embodiments of the application disclosed herein are illustrative of the principles of the embodiments of the present application. Other modified embodiments are also within the scope of the present application. Accordingly, the embodiments disclosed herein are by way of example only and not limitation. Those skilled in the art can adopt alternative configurations to implement the applications herein according to embodiments herein. Accordingly, embodiments of the present application are not limited to those precisely described in the application.
Claims (13)
1. A pluggable datagram delivery system comprising:
a plug-in library comprising a plurality of plug-ins;
the data access component is configured to receive a message from the reporting end, wherein the message comprises target data;
a data parsing conversion component comprising at least one first plug-in interface and configured to:
receiving the target data from the data access component,
a target parsing plug-in is selected from the at least one parsing plug-ins,
sending the target data to the target parsing plug-in through the at least one first plug-in interface to parse the target data,
receiving parsed data of the target data from the target parsing plug-in through the at least one first plug-in interface, and
converting the format of the analysis data into a target format;
a data verification component configured to verify the parsed data; and
a data storage component configured to store the parsed data to a target storage system of a storage medium.
2. The datagram delivery system of claim 1, wherein each of the at least one parsing plug-in comprises:
the data input format of the data input interface corresponds to the data format of the output end of the first plug-in interface; and
And the data output interface outputs a data format corresponding to the data format of the input data end of the first plug-in interface.
3. The datagram system of claim 2, wherein the at least one parsing plug-in comprises at least one of an Excel parsing engine, a CSV streaming parsing engine, an API data conversion engine, and an XML/DAT format parsing engine.
4. The datagram system of claim 1, wherein the data verification component comprises at least one second plug-in interface and is configured to:
selecting a target verification plug-in from at least one data verification plug-in;
transmitting the parsed data to the target verification plug-in through the at least one second plug-in interface; and
and receiving a verification result from the target verification plug-in through the at least one second plug-in interface.
5. The data reporting system of claim 4, wherein the target verification plug-in verifies the parsed data according to a preset verification rule, wherein the verification rule comprises at least one of a format verification rule, an intra-row rule verification rule, a uniqueness verification rule, a script verification rule, and an inter-table verification rule.
6. The datagram delivery system of claim 4, wherein the at least one second plug-in interface selects the target verification plug-in from the at least one verification plug-ins based on configuration information.
7. The datagram system of claim 1, wherein the data storage component comprises at least one third plug-in interface and is configured to:
selecting a target storage plugin from at least one data storage plugin;
transmitting the verified data to the target storage plugin through the at least one third plugin interface; and
and receiving a storage result from the target storage plugin through the at least one third plugin interface.
8. The datagram delivery system of claim 7, wherein the at least one storage plug-in comprises at least one of a MySQL database storage plug-in, an OceanBase database storage plug-in, a HIVE database storage plug-in, an Oracel database storage plug-in, a SQL Server database storage plug-in, a local file system storage plug-in, a network file system NFS storage plug-in, a Hadoop file system HDFS storage plug-in, and an object storage OSS storage plug-in; and
the storage result includes a storage path of the target data.
9. The datagram delivery system of claim 7, wherein the at least one third plug-in interface selects the target storage plug-in from the at least one storage plug-in according to configuration information.
10. The datagram system of claim 1, wherein the data access component comprises at least one fourth plug-in interface and is configured to:
selecting a target access plug-in from at least one data access plug-in;
the message is sent to the target access plug-in through the at least one fourth plug-in interface; and
and receiving the decrypted and integrity verified data of the target data from the target access plug-in through the at least one fourth plug-in interface.
11. The datagram delivery system of claim 10, wherein the at least one data access plug-in comprises at least one of a manual web page upload plug-in, a pre-machine checked auto upload plug-in, an OpenAPI call upload plug-in, and a web page fill plug-in.
12. The datagram delivery system of claim 1, further comprising:
a configuration component includes at least one configuration interface configured to receive configuration information.
13. A datagram delivery method comprising:
receiving a message from a reporting end through at least one data access plug-in, wherein the message comprises target data;
loading a target analysis plug-in according to a preset analysis rule, analyzing the target data and converting the target data into a target format;
Loading a target verification plug-in according to a preset verification rule, and verifying the analyzed target data; and
and loading the target storage plug-in according to a preset storage rule, and storing the target data passing the verification into a target storage system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010799238.0A CN111782718B (en) | 2020-08-11 | 2020-08-11 | Plug-in data reporting system and data reporting method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010799238.0A CN111782718B (en) | 2020-08-11 | 2020-08-11 | Plug-in data reporting system and data reporting method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111782718A CN111782718A (en) | 2020-10-16 |
| CN111782718B true CN111782718B (en) | 2023-12-29 |
Family
ID=72761822
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010799238.0A Active CN111782718B (en) | 2020-08-11 | 2020-08-11 | Plug-in data reporting system and data reporting method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111782718B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112286918B (en) * | 2020-10-23 | 2023-07-14 | 佳都科技集团股份有限公司 | Method and device for fast access conversion of data, electronic equipment and storage medium |
| CN112463885A (en) * | 2020-11-26 | 2021-03-09 | 北京宏景世纪软件股份有限公司 | Data synchronization implementation method and centralized data system |
| CN112948429B (en) * | 2021-02-02 | 2024-04-26 | 中国工商银行股份有限公司 | Data reporting method, device and equipment |
| CN116049293B (en) * | 2023-03-23 | 2024-02-13 | 北京沐融信息科技股份有限公司 | Method, device, equipment and medium for realizing analysis of CSV file based on database configuration |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007068175A1 (en) * | 2005-12-13 | 2007-06-21 | Huawei Technologies Co., Ltd. | A system and method for triggering the rule system |
| CN103150647A (en) * | 2013-04-10 | 2013-06-12 | 中国农业银行股份有限公司 | Report file processing method, server and system |
| CN105469188A (en) * | 2015-11-16 | 2016-04-06 | 国网山东省电力公司经济技术研究院 | Distribution network planning data online intelligent analysis system and distribution network planning data online intelligent analysis method |
| CN109918403A (en) * | 2019-02-02 | 2019-06-21 | 中国银行股份有限公司 | Data verification method, device, computer equipment and storage medium |
| CN110163735A (en) * | 2019-04-09 | 2019-08-23 | 平安科技（深圳）有限公司 | Concerning taxes data processing method, device, computer equipment and storage medium |
| WO2019196304A1 (en) * | 2018-04-09 | 2019-10-17 | 平安科技（深圳）有限公司 | Electronic apparatus, credit feedback message parsing method, and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7111075B2 (en) * | 2000-12-18 | 2006-09-19 | Microsoft Corporation | Method and system for processing data records having multiple formats |
| US10929384B2 (en) * | 2017-08-16 | 2021-02-23 | Walmart Apollo, Llc | Systems and methods for distributed data validation |
-
2020
- 2020-08-11 CN CN202010799238.0A patent/CN111782718B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007068175A1 (en) * | 2005-12-13 | 2007-06-21 | Huawei Technologies Co., Ltd. | A system and method for triggering the rule system |
| CN103150647A (en) * | 2013-04-10 | 2013-06-12 | 中国农业银行股份有限公司 | Report file processing method, server and system |
| CN105469188A (en) * | 2015-11-16 | 2016-04-06 | 国网山东省电力公司经济技术研究院 | Distribution network planning data online intelligent analysis system and distribution network planning data online intelligent analysis method |
| WO2019196304A1 (en) * | 2018-04-09 | 2019-10-17 | 平安科技（深圳）有限公司 | Electronic apparatus, credit feedback message parsing method, and storage medium |
| CN109918403A (en) * | 2019-02-02 | 2019-06-21 | 中国银行股份有限公司 | Data verification method, device, computer equipment and storage medium |
| CN110163735A (en) * | 2019-04-09 | 2019-08-23 | 平安科技（深圳）有限公司 | Concerning taxes data processing method, device, computer equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 一种基于三层架构的财务信息报送平台;元晶;;甘肃农业(11);全文 * |
| 监管报送数据质量平台的设计与实现;曾庆妍;王浩;;信息技术与信息化(01);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111782718A (en) | 2020-10-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111782718B (en) | Plug-in data reporting system and data reporting method | |
| US8346747B2 (en) | Extending database tables in a multi-tenant environment | |
| US9158843B1 (en) | Addressing mechanism for data at world wide scale | |
| US8874600B2 (en) | System and method for building a cloud aware massive data analytics solution background | |
| CN110196971A (en) | Online document edit methods, device, terminal device and storage medium | |
| CN111247550B (en) | Computerized transaction management module for blockchain networks | |
| US20090187879A1 (en) | Architecture for data validation | |
| CN112434015B (en) | Data storage method and device, electronic equipment and medium | |
| US10262055B2 (en) | Selection of data storage settings for an application | |
| US20230244653A1 (en) | Semantic compliance validation for blockchain | |
| US11372826B2 (en) | Dynamic inclusion of custom columns into a logical model | |
| KR20200119176A (en) | System, apparatuses, and methods of processing and managing web traffic data | |
| CN110414259A (en) | A kind of method and apparatus for constructing data element, realizing data sharing | |
| US20200409543A1 (en) | Application custom property framework | |
| CN115544183A (en) | Data visualization method and device, computer equipment and storage medium | |
| US8788533B2 (en) | Read access logging | |
| CN103345527B (en) | Intelligent data statistical system | |
| CN115017182A (en) | Visual data analysis method and equipment | |
| Bellini et al. | Managing Complexity of Data Models and Performance in Broker-Based Internet/Web of Things Architectures | |
| CN112860659B (en) | Data warehouse construction method, device, equipment and storage medium | |
| CN114153910A (en) | Data acquisition method and device, electronic device and computer program product | |
| US11755631B2 (en) | Workflow-based dynamic data model and application generation | |
| CN115481140A (en) | Method and device for index data query based on page configuration | |
| US9652308B2 (en) | Sharing a partitioned data set across parallel applications | |
| EP3759665A1 (en) | Multi-dimensional organization of data for efficient analysis |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |