Data processing methods, devices, equipment and media

Abstract

This disclosure provides a data processing method, apparatus, device, and storage medium that can be applied to the fields of big data and financial technology. The method includes: determining the business type associated with multiple data tables and the user identifier associated with the multiple data tables based on multiple field names within multiple data tables, wherein the data tables are used to store business data of the same type generated by the business system in the form of field names and field values ​​that have a mapping relationship with the field names; configuring the table structure of a target data table based on the user identifier, business type, and entity attributes associated with the business type, wherein the target data table is a data table merged from multiple data tables; and reading the field values ​​from the multiple data tables according to preset storage rules and storing them in the table structure of the target data table to obtain the target data table.

Description

Technical Field

[0001] This disclosure relates to the fields of big data and financial technology, and in particular to a data processing method, apparatus, device, medium and program product. Background Technology

[0002] With social progress and economic development, the types of financial services have gradually increased, resulting in a large amount of business data, and the relationships between this data have become more complex. To manage this large and complex volume of business data, business institutions typically establish different business entities to manage different types of business data.

[0003] In the process of implementing this disclosure, it was found that there are a large number of business entities in the existing business data management system. In order to adapt to the expansion of business data, new business entities are usually introduced or new business attributes are added to the original business entities. This leads to high complexity in the management of business entities. When adding new business types, it is necessary not only to redesign the relationship between business entities, but also to modify the existing programs, which is inefficient and difficult to maintain. Summary of the Invention

[0004] In view of the above problems, this disclosure provides a data processing method, apparatus, device, medium and program product.

[0005] According to a first aspect of this disclosure, a data processing method is provided, comprising: determining, based on multiple field names in multiple data tables, a business type associated with the multiple data tables and a user identifier associated with the multiple data tables, wherein the data tables are used to store business data of the same type generated by a business system in the form of field names and field values ​​that have a mapping relationship with the field names; configuring a table structure of a target data table based on the user identifier, the business type, and entity attributes associated with the business type, wherein the target data table is a data table merged from the multiple data tables; and reading the field values ​​in the multiple data tables according to a preset storage rule and storing them in the table structure of the target data table to obtain the target data table.

[0006] According to embodiments of this disclosure, the table structure of the target data table includes a horizontal structure and a vertical structure. The vertical structure includes multiple columns with topic names, and the horizontal structure includes multiple rows. Configuring the table structure of the target data table based on the user identifier, the business type, and the entity attributes associated with the business type includes: determining the number of columns based on the user field name representing the user identifier, the type field name representing the business type, and the attribute field name representing the entity attributes associated with the business type; configuring the user field name, the type field name, and the attribute field name as topic names for the multiple columns based on the number of columns; and configuring the multiple rows based on the business type associated with the user identifier.

[0007] According to an embodiment of this disclosure, the above-mentioned method of reading field values ​​from the plurality of data tables according to preset storage rules and storing them in the table structure of the target data table to obtain the target data table includes: repeatedly performing the following operations for each user identifier: according to the matching data table that matches the above-mentioned business type, and in accordance with the order of the topic names in the plurality of columns, reading the field values ​​corresponding to the topic names in the matching data table respectively; and storing the field values ​​corresponding to the topic names in the rows of the column where the topic name is located.

[0008] According to an embodiment of this disclosure, configuring the plurality of rows based on the service type associated with the user identifier includes: determining the number of service types associated with each user identifier based on the user identifier and the service type associated with the user identifier; determining the number of rows based on the number of rows; and configuring the plurality of rows based on the number of rows.

[0009] According to embodiments of this disclosure, the vertical structure further includes reserved columns without subject names; the table structure of the target data table configured based on the user identifier, the business type, and the entity attributes associated with the business type further includes: configuring the reserved columns without subject names according to a preset number of reserved columns.

[0010] According to embodiments of this disclosure, the method further includes: when it is determined that new business data has been generated in the business system, determining a target user identifier associated with the business data; when it is determined that the target user identifier does not exist in the target data table, calling a pre-configured first interface of the target data table for storing new data, so as to store the new business data in the target data table; and when it is determined that the target user identifier exists in the target data table, calling a pre-configured second interface of the target data table for updating data, so as to update the target data table according to the new business data.

[0011] According to embodiments of this disclosure, the method further includes: upon receiving a data query request, invoking a pre-configured third interface of the target data table for querying, so as to return data query results in response to the data query request.

[0012] According to an embodiment of this disclosure, the method further includes: when it is determined that the business system generates deregistration data, determining a deregistered user identifier based on the deregistration data; and marking business data associated with the deregistered user identifier in the target data table based on the deregistered user identifier.

[0013] A second aspect of this disclosure provides a data processing apparatus, comprising: a determining module, configured to determine, based on multiple field names within multiple data tables, a business type associated with the multiple data tables and a user identifier associated with the multiple data tables, wherein the data tables are used to store business data of the same type generated by a business system in the form of field names and field values ​​that have a mapping relationship with the field names; a configuring module, configured to configure a table structure of a target data table based on the user identifier, the business type, and entity attributes associated with the business type, wherein the target data table is a data table merged from the multiple data tables; and a processing module, configured to read the field values ​​within the multiple data tables according to preset storage rules and store them in the table structure of the target data table to obtain the target data table.

[0014] A third aspect of this disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the data processing method described above.

[0015] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the data processing method described above.

[0016] The fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described data processing method.

[0017] According to embodiments of this disclosure, the business type and user identifier are determined based on multiple field names in multiple data tables, and information related to the table structure of the target data table is obtained. The table structure of the target data table is configured based on the user identifier, business type, and entity attributes associated with the business type, making the target data table structure more flexible and scalable, and capable of integrating the table structures of multiple data tables. According to preset storage rules, field values ​​from multiple data tables are stored in the table structure of the target data table using mapping relationships, realizing a one-time asynchronous batch writing of business data to the target data table. This ensures the target data table is complete, covering all business data from multiple data tables, reducing the complexity of business entity management, and facilitating expansion and maintenance. Attached Figure Description

[0018] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0019] Figure 1 The illustrations depict application scenarios of data processing methods, apparatuses, devices, media, and program products according to embodiments of the present disclosure.

[0020] Figure 2 A flowchart illustrating a data processing method according to an embodiment of the present disclosure is shown schematically.

[0021] Figure 3 A flowchart illustrating a method for configuring the table structure of a target data table according to an embodiment of the present disclosure is shown schematically.

[0022] Figure 4 A flowchart illustrating a method for updating a target business data table according to an embodiment of this disclosure is shown schematically.

[0023] Figure 5 A flowchart illustrating a user logout method according to an embodiment of the present disclosure is shown schematically;

[0024] Figure 6 A schematic block diagram of a data processing apparatus according to embodiments of the present disclosure is shown; and

[0025] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing a data processing method according to an embodiment of the present disclosure. Detailed Implementation

[0026] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0027] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0028] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0029] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0030] In the technical solution disclosed herein, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with the relevant laws, regulations, and standards of the relevant countries and regions, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding operation entry points are provided for users to choose to authorize or refuse.

[0031] In the technical solutions of this disclosure, user authorization or consent is obtained before acquiring or collecting user personal information.

[0032] During the implementation of this disclosure, it was discovered that existing business data management systems have low scalability. Expansion can only be achieved by introducing new business entities or adding new business attributes to the existing business entity structure. Therefore, system redesign is required to accommodate new business types, incurring significant time and manpower costs. Furthermore, adding new business entities and attributes necessitates adaptive modifications to existing programs within the system, resulting in low cohesion and maintenance difficulties within the scope of business data management system upgrades.

[0033] Embodiments of this disclosure provide a data processing method, including: determining the business type associated with multiple data tables and the user identifier associated with multiple data tables based on multiple field names in multiple data tables, wherein the data tables are used to store business data of the same type generated by a business system in the form of field names and field values ​​that have a mapping relationship with the field names; configuring the table structure of a target data table based on the user identifier, business type, and entity attributes associated with the business type, wherein the target data table is a data table merged from multiple data tables; and reading the field values ​​in the multiple data tables according to preset storage rules and storing them in the table structure of the target data table to obtain the target data table.

[0034] Figure 1 The illustration shows an application scenario diagram of a data processing method, apparatus, device, medium, and program product according to embodiments of the present disclosure.

[0035] like Figure 1 As shown, application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0036] Users can interact with server 105 via network 104 using at least one of the first terminal device 101, second terminal device 102, and third terminal device 103 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, second terminal device 102, and third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0037] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0038] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0039] It should be noted that the data processing method provided in this embodiment can generally be executed by server 105. Correspondingly, the data processing device provided in this embodiment can generally be located in server 105. The data processing method provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105. Correspondingly, the data processing device provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105.

[0040] For example, data processing instructions can be sent to server 105 through first terminal device 101, second terminal device 102, or third terminal device 103. Server 105 determines the business type associated with multiple data tables and the user identifier associated with multiple data tables based on multiple field names in multiple data tables. Based on the user identifier, business type, and entity attributes associated with the business type, it configures the table structure of the target data table. Finally, according to preset storage rules, it reads the field values ​​in multiple data tables and stores them in the table structure of the target data table to obtain the target data table.

[0041] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0042] The following will be based on Figure 1 The described scene, through Figures 2-5 The data processing method of the disclosed embodiments will be described in detail.

[0043] Figure 2 A flowchart illustrating a data processing method according to an embodiment of the present disclosure is shown schematically.

[0044] like Figure 2 As shown, the data processing method of this embodiment includes operations S201 to S203.

[0045] In operation S201, based on multiple field names in multiple data tables, the business types associated with the multiple data tables and the user identifiers associated with the multiple data tables are determined. The data tables are used to store business data of the same type generated by the business system in the form of field names and field values ​​that have a mapping relationship with the field names.

[0046] According to embodiments of this disclosure, the business system can generate business data of various business types, with different business types stored in different data tables. Business types may include, but are not limited to, ordinary business, syndicated loan business, and sales business, and can be expanded according to actual business needs.

[0047] According to embodiments of this disclosure, multiple data tables may include multiple data tables related to business accounting, and each data table stores business data in the form of field names and field values ​​that have a mapping relationship with the field names. In addition, the field names may also represent the business type.

[0048] According to embodiments of this disclosure, the data table may further include user identifiers, which are used to represent users related to business data. Furthermore, the user identifier may include a total user identifier and sub-user identifiers; a single user can have one total user identifier and multiple sub-user identifiers. The total user identifier is unique within the business system and corresponds one-to-one with a user, while the sub-user identifiers are unique within the data table. A single user can correspond to multiple sub-user identifiers within the same data table. Business data of different business types for the same user is associated through the total user identifier, and multiple sub-user identifiers for the same user within the same data table are used to identify different businesses of the same business type.

[0049] According to embodiments of this disclosure, the server retrieves multiple data tables related to business accounting from the database, parses the field names of each data table to obtain the business type for each table. Simultaneously, it iterates through the user identifiers in the multiple data tables, recording all user identifiers involved in each table.

[0050] In operation S202, the table structure of the target data table is configured based on the user identifier, business type, and entity attributes associated with the business type. The target data table is a data table formed by merging multiple data tables.

[0051] According to embodiments of this disclosure, a target data table can be used to merge and store business data from multiple data tables. In this case, the target data table needs to contain business data of various business types. The table structure of the target data table can be configured using user identifiers, business types, and entity attributes associated with the business types to distinguish business data of different business types.

[0052] According to embodiments of this disclosure, entity attributes associated with different business types have similar characteristics, and each business type is associated with multiple entity attributes. For example, a normal business may include entity attributes such as normal business entity attribute 1, normal business entity attribute 2, normal business entity attribute 3, and normal business entity attribute 4, while a sales business may include entity attributes such as sales-type entity attribute 1, sales-type entity attribute 2, sales-type entity attribute 3, and sales-type entity attribute 4. Therefore, multiple data tables used to store business data for different business types can be merged.

[0053] According to embodiments of this disclosure, the server configures the table structure of the target data table based on the table structures of multiple data tables. After determining the business type, multiple entity attributes associated with the business type are determined, and then the table structure of the target data table is configured in conjunction with the user identifier. The table structure of the target data table differs from the table structures of the multiple data tables.

[0054] In operation S203, according to the preset storage rules, the field values ​​in multiple data tables are read and stored in the table structure of the target data table to obtain the target data table.

[0055] According to embodiments of this disclosure, the preset storage rule can be the pre-defined order of field names in the target data table. For example, field names related to user identifiers and business types can be arranged before field names related to entity attributes. The server can determine the field values ​​corresponding to the field names and user identifiers based on the association between field values ​​and field names, and write the field values ​​to the corresponding positions in the table structure of the target data table. Field values ​​can be stored in the table structure of the target data table in a batch asynchronous manner. After storing all business data from multiple data tables into the table structure of the target data table, a complete target data table is obtained.

[0056] According to embodiments of this disclosure, the business type and user identifier are determined based on multiple field names in multiple data tables, and information related to the table structure of the target data table is obtained. The table structure of the target data table is configured based on the user identifier, business type, and entity attributes associated with the business type, making the target data table structure more flexible and scalable, and capable of integrating the table structures of multiple data tables. According to preset storage rules, field values ​​from multiple data tables are stored in the table structure of the target data table using mapping relationships, realizing a one-time asynchronous batch writing of business data to the target data table. This ensures the target data table is complete, covering all business data from multiple data tables, reducing the complexity of business entity management, and facilitating expansion and maintenance.

[0057] According to embodiments of this disclosure, the table structure of the target data table includes a horizontal structure and a vertical structure. The vertical structure includes multiple columns with subject names, and the horizontal structure includes multiple rows.

[0058] According to embodiments of this disclosure, since the target data table can store business data of multiple business types, while each of the multiple data tables can only store business data of one business type, the table structure of the target data table is different from the table structure of the multiple data tables. The vertical structure of the target data table includes multiple columns with topic names, each column corresponding to a topic name, and the topic name is used to characterize the topic represented by the business data in that column.

[0059] Figure 3 A flowchart illustrating a method for configuring the table structure of a target data table according to an embodiment of the present disclosure is shown.

[0060] like Figure 3 As shown, the method for configuring the table structure of the target data table in this embodiment includes operations S301 to S303.

[0061] In operation S301, the number of columns is determined based on the user field name used to represent the user identifier, the type field name used to represent the business type, and the attribute field name used to represent the entity attributes associated with the business type.

[0062] According to embodiments of this disclosure, the table structure of the target data table is determined by multiple data tables, therefore the number of columns needs to be determined based on these multiple data tables. It should be noted that each of the user field name, type field name, and attribute field name can correspond to one column. Specifically, when the attribute field name includes multiple field names, each field name corresponds to one column.

[0063] For example, the data table storing business data of business type 1 includes three columns: user identifier, entity attribute 1 of business type 1, and entity attribute 2 of business type 1. The data table storing business data of business type 2 also includes three columns: user identifier, entity attribute 1 of business type 2, and entity attribute 2 of business type 2. The target data table should include a column for storing business types in addition to the three columns: user identifier, entity attribute 1, and entity attribute 2.

[0064] In operation S302, based on the number of columns, the user field name, type field name, and attribute field name are configured as the subject names of multiple columns.

[0065] According to embodiments of this disclosure, after determining the number of columns in the table structure of the target data table, the subject names of multiple columns are configured based on the field names of multiple data tables.

[0066] Table 1

[0067] User ID Entity attribute 1 for business type 1 Entity attribute 2 of business type 1 User 1 User 2

[0068] Table 2

[0069] User ID Entity attribute 1 of business type 2 Entity attribute 2 of business type 2 User 1 User 3

[0070] For example, the table structure of the data table storing business data of business type 1 is shown in Table 1 above. The table structure includes business entities associated with business type 1, as well as user identifiers. The table structure of the data table storing business data of business type 2 is shown in Table 2 above. The table structure of the target data table is shown in Table 3 below. The table structure of the target data table can be considered as being jointly determined by Table 1 and Table 2. The table structure not only includes user identifiers and business entities associated with business types, but also includes information about business types.

[0071] According to embodiments of this disclosure, each entity attribute in the table structure of multiple data tables and the target data table may include multiple columns, where each column corresponds to a different sub-attribute. For example, sub-attributes may include subjects, etc., without limitation. When both entity attribute 1 and entity attribute 2 include three topics: sub-attribute A, sub-attribute B, and sub-attribute C, the table structure of the target data table is shown in Table 4 below. Entity attribute 1 includes three columns: sub-attribute 1A, sub-attribute 1B, and sub-attribute 1C, and entity attribute 2 includes three columns: sub-attribute 2A, sub-attribute 2B, and sub-attribute 2C.

[0072] Table 3

[0073] User ID Business type Entity attribute 1 Entity Attribute 2

[0074] Table 4

[0075]

[0076] In operation S303, multiple rows are configured based on the service type associated with the user identifier.

[0077] According to embodiments of this disclosure, the number of rows in the target data table is determined by the combined number of rows in multiple data tables. In the target data table, business data for different service types of the same user can be stored in adjacent rows for easy aggregation and querying.

[0078] According to embodiments of this disclosure, rows associated with each user identifier can be determined by the user identifier, and multiple rows of the target data table can be configured based on the user identifier and the rows associated with each user identifier.

[0079] According to embodiments of this disclosure, without considering storage space saving, the field names corresponding to each business type can be configured as columns in a vertical structure, as shown in Table 5 below. As shown in Table 5, the target data table structure does not include columns for type field names. For each business type, the column corresponding to the field name can be divided into multiple sub-columns based on the entity attributes associated with that business type, where each sub-column corresponds to one entity attribute. Each user identifier corresponds to one row. When a user only handles a portion of all business transactions, it results in a significant waste of storage space. For example, if user 2 only handles business type 1 transactions, the portion corresponding to business type 2 in the table becomes redundant for user 1, leading to a waste of storage space when there is a large amount of business data.

[0080] Table 5

[0081]

[0082] According to embodiments of this disclosure, the table structure of a target data table is determined based on the table structures of multiple data tables and user identification information. The resulting target data table structure can store business data from multiple data tables while possessing flexibility and scalability. Furthermore, by configuring columns containing type field names and configuring multiple rows based on business types associated with user identification, it not only avoids the problem of wasted storage space due to redundancy of multiple business types after configuring business type columns, but also facilitates centralized management of different business data generated by the same user.

[0083] According to embodiments of this disclosure, multiple rows are configured based on the service types associated with a user identifier, including: determining the number of service types associated with each user identifier based on the user identifier and the service types associated with the user identifier; determining the number of rows based on the number of rows; and configuring multiple rows based on the number of rows.

[0084] According to embodiments of this disclosure, each user identifier is traversed through multiple data tables to obtain the number of service types associated with each user identifier. The number of rows occupied by each user identifier in the target data table is the number of service types associated with that user identifier, and the total number of rows in the target data table is the sum of the number of rows occupied by each user identifier. The user identifier and the service types associated with the user identifier are written into the target data table to complete the configuration of the target data table rows.

[0085] For example, as shown in Tables 1 and 2 above, before generating the target data table, each data table stores the business data of users who have already processed the business type. For example, if user 1 has processed both business type 1 and business type 2, both Tables 1 and 2 will store user 1's business data. However, if user 2 has only processed business type 1, Table 2, which stores business data for business type 2, will not contain user 2's business data. Similarly, Table 1, which stores business data for business type 1, will not contain user 3's business data.

[0086] Table 6

[0087]

[0088] According to embodiments of this disclosure, the table structure of the target data table after configuration is shown in Table 6 above. Since the table structure of the target data table is generated based on the business data of multiple data tables, Table 6 is generated based on Table 4, using information from Tables 1 and 2. Because both Tables 1 and 2 contain information about User 1, the table structure of the target data table includes two rows of data about User 1, with one row having a business type of business type 1 and the other a business type of business type 2. Furthermore, the table structure of the target data table also includes one row of data about User 2 with a business type of business type 2, and one row of data about User 3 with a business type of business type 3.

[0089] According to embodiments of this disclosure, rows of a target data table are configured based on a user identifier and the service type associated with the user identifier, enabling unified storage of service data for different service types of the same user, which facilitates management and querying.

[0090] According to embodiments of this disclosure, the vertical structure further includes reserved columns without subject names; configuring the table structure of the target data table based on user identifier, business type, and entity attributes associated with the business type further includes: configuring reserved columns without subject names according to a preset number of reserved columns.

[0091] According to embodiments of this disclosure, reserved columns can be reserved columns configured for reserved sub-attributes or reserved entity attributes. For example, as shown in Table 4 above, entity attribute 1 includes sub-attribute 1A, sub-attribute 1B, and sub-attribute 1C. To enhance the scalability of the target data table, reserved columns such as reserved sub-attribute 1C and reserved sub-attribute 1D can be configured for entity attribute 1. It should be noted that the subject names of reserved columns such as reserved sub-attribute 1C and reserved sub-attribute 1D are empty. Reserved entity attribute columns can also be configured. For example, Table 4 currently only includes columns related to entity attribute 1 and entity attribute 2. By configuring reserved entity attribute columns, the target data table can be expanded when adding entity attributes.

[0092] According to embodiments of this disclosure, the scalability of a target data table is increased by configuring reserved columns for the target data table.

[0093] According to embodiments of this disclosure, based on preset storage rules, field values ​​from multiple data tables are read and stored in the table structure of a target data table to obtain the target data table. This includes repeatedly performing the following operations for each user identifier: based on a matching data table that matches the business type, according to the order of the topic names in multiple columns, the field values ​​corresponding to the topic names in the matching data table are read respectively; and the field values ​​corresponding to the topic names are stored in the rows of the column where the topic name is located.

[0094] According to embodiments of this disclosure, the storage of original business data from multiple data tables can be achieved by using a user identifier to traverse the business data of multiple data tables and writing the corresponding field values ​​into a target data table.

[0095] According to embodiments of this disclosure, a data table arrangement order can be determined for multiple data tables. For each user identifier, according to the business type in the target data table that matches the user identifier, multiple data tables that match the user identifier are determined. In each of the multiple data tables, the corresponding field values ​​in the multiple data tables are determined based on the user identifier and the topic name of the target data table, and the field values ​​are written into the corresponding positions in the target data table.

[0096] According to embodiments of this disclosure, by traversing multiple data tables based on the table structure and user identifier of the target data table, determining the corresponding field values, and writing the field values ​​into the target data table, the storage of existing data from multiple data tables is achieved.

[0097] Figure 4 A flowchart illustrating a method for updating a target business data table according to an embodiment of this disclosure is shown schematically.

[0098] like Figure 4 As shown, the method for updating the target business data table in this embodiment includes operations S401 to S403.

[0099] In operation S401, if it is determined that new business data has been generated in the business system, the target user identifier associated with the business data is determined.

[0100] According to embodiments of this disclosure, the target user identifier may include user identifiers that already exist in the target data table, or user identifiers that do not exist in the target data table.

[0101] According to embodiments of this disclosure, in response to a client sending new business data and a request to store the new business data, the server needs to store the new business data, parse the storage request for the business data, and determine the target user identifier associated with the new business data.

[0102] In operation S402, if it is determined that the target user identifier does not exist in the target data table, the first interface of the pre-configured target data table for storing new data is called so that the new business data is stored in the target data table.

[0103] According to an embodiment of this disclosure, the target data table is pre-configured with a first interface for storing new data of newly added user identifiers.

[0104] According to an embodiment of this disclosure, the server traverses the target user identifier in the target data table. If it is determined that the target user identifier does not exist in the target data table, the server calls the first interface and stores the field values ​​of the new business data into the target data table according to the subject name of the target data table in accordance with the preset storage rules, thereby increasing the number of rows in the target data table.

[0105] According to embodiments of this disclosure, when the user identifier includes a total user identifier and sub-user identifiers, the target user identifier includes a total target user identifier and sub-target user identifiers. The server first iterates through the total target user identifiers in the target data table. If it determines that the total target user identifier does not exist in the target data table, it calls a first interface to store the new business data field value in the target data table according to a preset storage rule and the subject name of the target data table. If it determines that the total target user identifier exists in the target data table, it iterates through the sub-user identifiers. If it determines that the sub-user identifier does not exist in the target data table, it calls the first interface to store the new business data field value in the target data table according to a preset storage rule and the subject name of the target data table.

[0106] In operation S403, if it is determined that the target user identifier exists in the target data table, the second interface of the pre-configured target data table for updating data is called so as to update the target data table according to the new business data.

[0107] According to embodiments of this disclosure, the target data table is pre-configured with a second interface for modifying the business data of the stored target user identifier.

[0108] According to an embodiment of this disclosure, the server traverses the target user identifier in the target data table. If the target user identifier is found in the target data table, the server calls the second interface to determine the corresponding field value based on the subject name of the target data table. The server then updates the original field values ​​in the target data table based on the new business data to obtain the updated target data table.

[0109] According to embodiments of this disclosure, before configuring the target data table, each data table needs to be configured with a first interface and a second interface separately due to different business types. Adding a new business type also requires adding a new interface, resulting in poor scalability. After configuring the target data table, the multiple first interfaces and multiple second interfaces of multiple data tables can be merged into one first interface and one second interface, eliminating the need to add a new interface when adding a new business type, thus improving scalability.

[0110] According to embodiments of this disclosure, by determining the target user identifier, the interface to be called is determined to complete the storage of new business data. Records in the target data table can be added or modified, so that the business data in the target data table has real-time performance.

[0111] According to embodiments of this disclosure, the method for updating a target business data table further includes: upon receiving a data query request, invoking a pre-configured third interface of the target data table for querying, so as to return data query results in response to the data query request.

[0112] According to embodiments of this disclosure, the target data table is further configured with a third interface for querying business data in the target data table. Users can send data query requests to the server via a client. The server parses the data query request, determines the field values ​​corresponding to the data query request, and returns the field values ​​as the data query results to the client.

[0113] According to embodiments of this disclosure, before configuring the target data table, each of the multiple data tables is configured with a third interface for querying business data. After merging the multiple data tables into a target data table, since all data is stored in the target data table, only one third interface is needed to query all business data. There is no need to add a new third interface when adding new business types, resulting in strong scalability.

[0114] According to embodiments of this disclosure, by configuring a third interface, business data stored in the target data table can be queried without adding a new third interface when adding new business types, thus exhibiting strong scalability.

[0115] Figure 5 A flowchart illustrating a user logout method according to an embodiment of this disclosure is shown schematically.

[0116] like Figure 5 As shown, the user logout method in this embodiment includes operations S501 to S502.

[0117] In operation S501, if it is determined that the business system has generated deregistration data, the deregistered user identifier is determined based on the deregistration data.

[0118] According to embodiments of this disclosure, users can interact with the client to select and cancel their user ID. Upon receiving a user's cancellation instruction, the business system traverses the target data table based on the user ID. After determining that all business transactions associated with the user ID have been completed, it generates cancellation data and sends the cancellation data to the server.

[0119] According to an embodiment of this disclosure, the server receives deregistration data generated by the business system, parses the deregistration data, and determines the user identifier to be deregistered.

[0120] In operation S502, based on the deregistered user identifier, mark the business data associated with the deregistered user identifier in the target data table.

[0121] According to an embodiment of this disclosure, the server marks the business data associated with the user identifier based on the obtained user identifier, making the business data associated with the user unavailable, thereby canceling the user identifier.

[0122] According to embodiments of this disclosure, user identification can be deregistered in one go through a target data table, eliminating the need to operate on multiple data tables, thereby improving processing efficiency and enhancing user experience.

[0123] Based on the above data processing method, this disclosure also provides a data processing apparatus. The following will be combined with... Figure 6 The device is described in detail.

[0124] Figure 6 A schematic block diagram of a data processing apparatus according to an embodiment of the present disclosure is shown.

[0125] like Figure 6 As shown, the data processing apparatus 600 of this embodiment includes a determination module 610, a configuration module 620, and a processing module 630.

[0126] The determining module 610 is used to determine the business type associated with multiple data tables and the user identifier associated with multiple data tables based on multiple field names in multiple data tables. The data tables are used to store business data of the same type generated by the business system in the form of field names and field values ​​that have a mapping relationship with the field names. In one embodiment, the determining module 610 can be used to perform the operation S201 described above, which will not be repeated here.

[0127] The configuration module 620 is used to configure the table structure of the target data table based on the user identifier, business type, and entity attributes associated with the business type. The target data table is a merged data table composed of multiple data tables. In one embodiment, the configuration module 620 can be used to perform the operation S202 described above, which will not be repeated here.

[0128] The processing module 630 is used to read field values ​​from multiple data tables according to preset storage rules and store them into the table structure of the target data table to obtain the target data table. In one embodiment, the processing module 630 can be used to perform the operation S203 described above, which will not be repeated here.

[0129] According to embodiments of this disclosure, the configuration module 620 further includes a column number determination submodule, a column name configuration submodule, and a row configuration submodule.

[0130] The column count determination submodule is used to determine the number of columns based on the user field name used to represent the user identifier, the type field name used to represent the business type, and the attribute field name used to represent the entity attributes associated with the business type.

[0131] The column name configuration submodule is used to configure the user field name, type field name, and attribute field name as the subject name of multiple columns, based on the number of columns.

[0132] The row configuration submodule is used to configure multiple rows based on the business type associated with the user identifier.

[0133] According to embodiments of this disclosure, the processing module 630 further includes a field value reading unit and a field value storage unit.

[0134] The field value reading unit is used to read the field values ​​corresponding to the topic names in the matching data table that matches the business type, according to the order of the topic names in multiple columns.

[0135] The field value storage unit is used to store the field values ​​corresponding to the topic name in the row of the column containing the topic name.

[0136] According to embodiments of this disclosure, the row configuration submodule includes a class number determination unit, a row number determination unit, and a row configuration unit.

[0137] The category number determination unit is used to determine the number of service types associated with each user identifier based on the user identifier and the service type associated with the user identifier.

[0138] The row number determination unit is used to determine the number of rows based on the quantity.

[0139] The row configuration unit is used to configure multiple rows based on the number of rows.

[0140] According to embodiments of this disclosure, configuration module 620 further includes a reserved column configuration submodule.

[0141] The reserved column configuration submodule is used to configure reserved columns that do not have a theme name, based on the preset number of reserved columns.

[0142] According to embodiments of this disclosure, the data processing apparatus 600 further includes an identifier determination module, a data storage module, and a data update module.

[0143] The identifier determination module is used to determine the target user identifier associated with the business data when it is determined that new business data has been generated in the business system.

[0144] The data storage module is used to call the first interface of the pre-configured target data table for storing new data when it is determined that the target user identifier does not exist in the target data table, so as to store the new business data in the target data table.

[0145] The data update module is used to call the pre-configured second interface of the target data table for updating data when it is determined that the target user identifier exists in the target data table, so as to update the target data table according to the new business data.

[0146] According to embodiments of this disclosure, the data processing apparatus 600 further includes a data query module.

[0147] The data query module is used to call the pre-configured third interface of the target data table for querying when a data query request is received, so as to return the data query results in response to the data query request.

[0148] According to embodiments of this disclosure, the data processing apparatus 600 further includes a deregistration identifier determination module and an identifier deregistration module.

[0149] The cancellation identifier determination module is used to determine the cancellation user identifier based on the cancellation data when the business system has generated cancellation data.

[0150] The identification and cancellation module is used to mark the business data associated with the cancelled user identifier in the target data table based on the cancelled user identifier.

[0151] According to embodiments of this disclosure, any plurality of modules among the determining module 610, configuration module 620, and processing module 630 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules can be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the determining module 610, configuration module 620, and processing module 630 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. Alternatively, at least one of the determining module 610, configuration module 620, and processing module 630 can be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0152] According to the embodiments of this disclosure, in the centralized business processing flow, there are many types of transactions and vouchers, and many fields are not required. If a large number of blank vouchers after being cut up enter the manual entry stage, it will not only prolong the business processing time, but also increase the workload of tellers. The business voucher processing device provided by the embodiments of this disclosure can automatically process business vouchers and improve the efficiency of centralized business processing.

[0153] Figure 7 A block diagram schematically illustrates an electronic device suitable for implementing a data processing method according to an embodiment of the present disclosure.

[0154] like Figure 7 As shown, an electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage portion 708 into a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0155] RAM 703 stores various programs and data required for the operation of electronic device 700. Processor 701, ROM 702, and RAM 703 are interconnected via bus 704. Processor 701 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 702 and / or RAM 703. It should be noted that the programs may also be stored in one or more memories other than ROM 702 and RAM 703. Processor 701 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0156] According to embodiments of this disclosure, the electronic device 700 may further include an input / output (I / O) interface 705, which is also connected to a bus 704. The electronic device 700 may also include one or more of the following components connected to the I / O interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0157] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0158] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 702 and / or RAM 703 and / or one or more memories other than ROM 702 and RAM 703 described above.

[0159] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this disclosure.

[0160] When the computer program is executed by the processor 701, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0161] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 709, and / or installed from a removable medium 711. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0162] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from the removable medium 711. When the computer program is executed by the processor 701, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0163] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0164] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0165] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0166] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A data processing method, comprising: Based on multiple field names in multiple data tables, determine the business type associated with the multiple data tables and the user identifier associated with the multiple data tables. The data tables are used to store business data of the same type generated by the business system in the form of field names and field values ​​that have a mapping relationship with the field names. The user identifier includes a total user identifier that uniquely corresponds to a single user and a sub-user identifier that uniquely corresponds to different businesses of the same business type for the same user. Based on the user identifier, the business type, and the entity attributes associated with the business type, configure the table structure of the target data table. The target data table is a data table merged from the multiple data tables. The table structure of the target data table includes a horizontal structure and a vertical structure. The vertical structure includes a column for the subject name with business data and a reserved column without a subject name. The horizontal structure is dynamically configured according to the number of business types associated with each user identifier and includes multiple rows. For each user identifier, repeat the following operations: based on the matching data table that matches the business type, read the field values ​​corresponding to the topic names in the matching data table according to the order of the topic names in the topic name column; and store the field values ​​corresponding to the topic names in the row of the topic name column where the topic name is located.

2. The method according to claim 1, wherein, The step of configuring the table structure of the target data table based on the user identifier, the business type, and the entity attributes associated with the business type includes: The number of columns is determined based on the user field name used to represent the user identifier, the type field name used to represent the business type, and the attribute field name used to represent the entity attributes associated with the business type. Based on the number of columns, configure the user field name, the type field name, and the attribute field name as the topic names of the multiple columns; Configure the multiple rows based on the service type associated with the user identifier.

3. The method according to claim 2, wherein, The configuration of the multiple rows based on the service type associated with the user identifier includes: Based on the user identifier and the service type associated with the user identifier, determine the number of service types associated with each user identifier; Based on the stated quantity, determine the number of rows; Configure the multiple rows according to the number of rows.

4. The method according to claim 2, wherein configuring the table structure of the target data table based on the user identifier, the business type, and the entity attributes associated with the business type further includes: Configure the reserved columns without subject names according to the preset number of reserved columns.

5. The method according to claim 1, further comprising: If it is determined that new business data has been generated in the business system, the target user identifier associated with the business data shall be determined. If it is determined that the target user identifier does not exist in the target data table, the first interface of the pre-configured target data table for storing new data is called so that the new business data is stored in the target data table; If the target user identifier is found in the target data table, the second interface for updating data in the pre-configured target data table is invoked to update the target data table according to the new business data.

6. The method according to claim 1, further comprising: Upon receiving a data query request, the pre-configured third interface of the target data table for querying is invoked to return the data query result in response to the data query request.

7. The method according to any one of claims 1 to 6, further comprising: If it is determined that the business system generates cancellation data, the cancellation user identifier is determined based on the cancellation data; Based on the logged-out user identifier, mark the business data associated with the logged-out user identifier in the target data table.

8. A data processing apparatus, comprising: The determination module is used to determine the business type associated with the multiple data tables and the user identifier associated with the multiple data tables based on multiple field names in the multiple data tables. The data tables are used to store business data of the same type generated by the business system in the form of field names and field values ​​that have a mapping relationship with the field names. The user identifier includes a total user identifier that uniquely corresponds to a single user and a sub-user identifier that uniquely corresponds to different businesses of the same business type for the same user. The configuration module is used to configure the table structure of the target data table based on the user identifier, the business type, and the entity attributes associated with the business type. The target data table is a data table merged from the multiple data tables. The table structure of the target data table includes a horizontal structure and a vertical structure. The vertical structure includes a column for the subject name with business data and a reserved column without a subject name. The horizontal structure is dynamically configured according to the number of business types associated with each user identifier and includes multiple rows. The processing module is configured to repeatedly perform the following operations for each user identifier: according to the matching data table that matches the business type, and in accordance with the order of the topic names in the topic name column, read the field values ​​corresponding to the topic names in the matching data table; and store the field values ​​corresponding to the topic names in the row of the topic name column where the topic name is located.

9. An electronic device, comprising: One or more processors; Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 7.

11. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 7.

Images