Data processing method and device, electronic equipment and storage medium

Abstract

The invention provides a data processing method and device, electronic equipment and a storage medium, and the method comprises the steps: traversing a first field in a data table under the condition that the current moment is a daily switching moment, and determining a first record table of which the value of the first field is a first identifier; updating the value of the first field in the first record table as the second identifier; based on the current moment, traversing the business day configuration file, and determining a first business day associated with the current moment and all first natural days associated with the first business day; updating the value of the second field in the first record table as the first business day; and under the condition that the first transaction data in the first natural day is obtained, the first natural day and the first transaction data are associated and recorded in the business information field in the first record table. Automatic business day switching is realized, the efficiency of business day switching and pipeline data management can be improved, increment supply is facilitated, manual intervention is reduced, and then the efficiency of data processing and analysis is improved.

Description

Technical Field

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

[0002] As business competition intensifies, enterprises need more refined and efficient management methods to improve their competitiveness. Business day switching is a sign that clearly marks the end of one trading day and the beginning of the next trading day. In finance, trading or certain specific industries, business operations, instructions or designated actions usually need to be completed within the same business day to ensure the smooth progress of transactions and the accurate arrival of funds. It is an important means to meet corporate regulatory needs and prevent risks.

[0003] Therefore, realizing the system's automatic switching of business days and improving the accuracy and efficiency of business day switching will help promote the development of business data management, help enterprises better understand their business conditions, and improve their competitiveness. Summary of the invention

[0004] The present application aims to solve one of the technical problems in the related art at least to some extent.

[0005] To this end, the first purpose of the present application is to propose a data processing method, device, electronic device and storage medium to achieve more accurate and reliable automatic switching of business days, and improve the efficiency of business day data query, analysis and batch running.

[0006] The second objective of the present application is to provide a data processing device.

[0007] The third objective of the present application is to provide an electronic device.

[0008] A fourth objective of the present application is to provide a computer-readable storage medium.

[0009] A fifth object of the present application is to provide a computer program product.

[0010] To achieve the above-mentioned purpose, the first embodiment of the present application proposes a data processing method, including:

[0011] When the current time is the day-cut time, traverse the first field in the data table to determine a first record table whose value is the first identifier;

[0012] Updating the value of the first field in the first record table to a second identifier;

[0013] Based on the current time, traverse a business day configuration file to determine a first business day associated with the current time and all first natural days associated with the first business day, wherein the business day configuration file includes a mapping relationship between business days and natural days;

[0014] Update the value of the second field in the first record table to the first business day;

[0015] When the first transaction data within the first natural day associated with the first business day is obtained, the first natural day and the first transaction data are associated and recorded in the business information field of the first record table.

[0016] To achieve the above-mentioned purpose, a second aspect of the present application provides a data processing device, including:

[0017] A first determination module is used to traverse the first field in the data table and determine a first record table whose value is a first identifier when the current time is a day-cut time;

[0018] A first updating module, used for updating the value of the first field in the first record table to a second identifier;

[0019] a second determination module, configured to traverse a business day configuration file based on the current time, and determine a first business day associated with the current time, and all first natural days associated with the first business day, wherein the business day configuration file includes a mapping relationship between business days and natural days;

[0020] A second updating module, configured to update the value of the second field in the first record table to the first business day;

[0021] The recording module is used to record the first natural day and the first transaction data in association with each other in the business information field of the first recording table when the first transaction data within the first natural day associated with the first business day is obtained.

[0022] To achieve the above-mentioned purpose, the third aspect embodiment of the present application proposes an electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the data processing method as described in the first aspect embodiment.

[0023] To achieve the above-mentioned purpose, the fourth aspect embodiment of the present application proposes a computer-readable storage medium, in which computer execution instructions are stored. When the computer execution instructions are executed by a processor, they are used to implement the data processing method described in the first aspect embodiment.

[0024] To achieve the above-mentioned purpose, the fifth embodiment of the present application proposes a computer program product, including a computer program, which, when executed by a processor, implements the data processing method described in the first embodiment.

[0025] The data processing method, device, electronic device and storage medium provided by the present application activate the function of storing transaction data in the record table by, when the current time is the day-cut time, changing the value of the corresponding first field in the data table to a record table with a first identifier, and updating the value of the first field to a second identifier, and by querying the next business day date that needs to be switched at the current time in the business day configuration file, updating the value of the second field corresponding to the activated record table, so that the transaction data corresponding to the next business day can be recorded in the business information field of the record table. In this way, automatic business date switching is realized, and data of different business days can be alternately stored in different tables, improving the efficiency and flexibility of business day switching, facilitating incremental data supply, and eliminating the need for manual intervention, thereby improving the efficiency of data processing and management.

[0026] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0028] Figure 1 A flowchart of a data processing method provided in an embodiment of the present application;

[0029] Figure 2a A schematic diagram of updating an identifier in a data table during a business day switching process provided in an embodiment of the present application;

[0030] Figure 2b A schematic diagram of a process for switching business days in a production environment provided in an embodiment of the present application;

[0031] Figure 2c A schematic diagram of a process of switching business days in a test environment provided in an embodiment of the present application;

[0032] Figure 3 A flowchart of another data processing method provided in an embodiment of the present application;

[0033] Figure 4 A flowchart of another data processing method provided in an embodiment of the present application;

[0034] Figure 5A flowchart of another data processing method provided in an embodiment of the present application;

[0035] Figure 6 A flowchart of another data processing method provided in an embodiment of the present application;

[0036] Figure 7 A flow chart of a report data processing process provided in an embodiment of the present application

[0037] Figure 8 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application; and

[0038] Fig. 9 It is a schematic diagram of the structure of an electronic device shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0039] Embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limiting the present application.

[0040] The acquisition, transmission, storage, use, and processing of data in the technical solution of this application comply with the relevant provisions of national laws and regulations.

[0041] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0042] The data processing method and device of the embodiments of the present application are described below with reference to the accompanying drawings.

[0043] Figure 1 A flowchart of a data processing method provided in an embodiment of the present application.

[0044] like Figure 1 As shown, the data processing method includes the following steps:

[0045] Step 101, when the current time is the day-cut time, traverse the first field in the data table to determine the first record table whose value of the first field is the first identifier.

[0046] The day-cut time, i.e., the business day switching time, refers to the time required to switch to the next business day. The day-cut time can be customized according to actual business needs. For example, the day-cut time can be 0:00 every day, etc.

[0047] Among them, the data table is a table provided by the present application for storing data such as names, identifiers, and update times corresponding to two tables respectively, and can store the flow data of the business day by alternately activating one of the two tables.

[0048] It should be noted that, in some embodiments, the data table may be referred to as an "activation flow table", and the two tables in the data table for alternately storing business day data may be respectively "table a" and "table b".

[0049] The first field refers to a value in a data table that is used to describe whether the corresponding record table is currently in an activated state for storing transaction data. In this application, the value of the first field can be a first identifier or a second identifier to respectively identify the current activated state and the inactivated state.

[0050] The first identifier is a character used to mark in the data table a record table that is not currently in an activated state and needs to be activated to store business day data, for example, it may be "N".

[0051] It should be noted that the first record table is a table in which the value of the first field in the data table at any time is the first identifier. Since in the data table, two record tables are activated alternately to store business day data, when the two record tables in the data table are table a and table b, when the business day is switched at a certain time, the first record table may be table a in the data table or table b in the data table.

[0052] For example, the data table may be shown in Table 1 below.

[0053] Table 1

[0054] fileld1 fileld2 current_date enable login_a txn_a 2023 / 12 / 1 0:00:00 N login_b txn_b 2023 / 12 / 2 0:00:00 Y

[0055] In Table 1, file identifier 1 (fileld1) is the name of two tables in the data table, namely table a (login a) and table b (login b), and file identifier 2 (fileld2) is the transaction data corresponding to the two tables, that is, the transaction data corresponding to table a is transaction a (transaction a, txn_a), and the transaction data corresponding to table b is transaction b (transaction a, txn_b). Current_date is the current data update time corresponding to each table, which is composed of the business day date and day cut time corresponding to the table after the update. Enable means to start or activate, which is the first field mentioned above.

[0056] As can be seen from Table 1, the value of the first field corresponding to table a is N (first identifier), so table a is the first record table. When switching business days, table a needs to be activated as the next record table for storing business day data.

[0057] In an embodiment of the present application, when the current time is the day-switch time, the record table that needs to be activated to store the next business day data can be determined by querying the value of the first field in the data table, that is, the first record table whose value of the first field in the data table is the first identifier, so that in the subsequent data processing process, the identifier of the first record table can be updated to activate the table for storing new business day transaction data to complete the business day switch.

[0058] It should be noted that, because the two tables in the data table store business day data alternately, before switching business days and storing the data of new business days, the data of the existing historical business days in the first record table needs to be exported to clear the first record table to avoid confusion of data between different business days. Specifically, the data in the first record table can be unloaded into a file and transferred to other areas, such as a historical database or a historical data table.

[0059] Step 102: Update the value of the first field in the first record table to the second identifier.

[0060] The second mark is a character used to mark in the data table that the corresponding record table has been activated and can be used to store business day data. The second mark corresponds to the first mark and has the opposite effect, so when the first mark is "N", the second mark is "Y".

[0061] In an embodiment of the present application, after determining that a day switch is required at the current moment and traversing to the first record table whose value of the first field corresponds to the first identifier, the value of the first field corresponding to the first record table can be updated from the first identifier to the second identifier, indicating that the first record table is activated, so that the first record table can store the transaction data generated on the next business day to achieve the switching of business days.

[0062] It should be noted that the two tables in the data table are alternately used to store transaction data within a business day. When one of the tables is activated to store data, the other table should be in an inactive state. Therefore, it is not possible for both tables in the data table to correspond to the first identifier or the second identifier at the same time. In other words, when the value of the first field of the first record table is updated, the value of the corresponding first field of another record table in the data table, i.e., the second record table, needs to be updated.

[0063] Optionally, after determining a first record table in which the value of the first field in the data table is the first identifier, a second record table in which the value of the first field in the data table is the second identifier may be determined first, and the value of the first field in the second record table may be updated to the third identifier.

[0064] The third identifier is a character that plays a transitional role in updating the values ​​of the first fields corresponding to the two record tables in the data table during the daily switching process. For example, the third identifier may be "M".

[0065] In an embodiment of the present application, in order to avoid the problem that the values ​​of the first fields corresponding to two record tables in a data table are the same at a certain moment during the daily cutting process, resulting in subsequent first field update failures, a third identifier can be used to transition the update of the first field of the second record table, so that when the first field of the first record table is updated to the second identifier, the problem of the first fields of the two record tables having the same values ​​will not occur.

[0066] Then, after the value of the first field in the first record table is updated to the second identifier, the value of the first field in the second record table may be updated to the first identifier.

[0067] It can be understood that, since the value of the first field in the second record table is the second identifier before the day cut, it can be known that the transaction data generated in the previous business day is recorded in the second record table. When the day cut time is reached and the identifiers corresponding to the two tables in the data table are updated according to the above steps, the first record table is activated, and the value of the first field corresponding to the first record table is the second identifier, and the transaction data generated in the next business day will be recorded in the first record table. Therefore, the business day switch can be completed by updating the identifier of the record table, and the business day data can be alternately stored in the two record tables in the data table.

[0068] Step 103, based on the current time, traverse the business day configuration file to determine the first business day associated with the current time and all first natural days associated with the first business day.

[0069] The business day configuration file includes a mapping relationship between business days and natural days. Business days refer to the dates on which banks, financial institutions or enterprises actually conduct business operations. Each business day may correspond to one or more natural days.

[0070] It should be noted that when switching business days in different environments, the mapping relationship between business days and natural days in the business day configuration file may be different. For example, in a production environment, due to the popularity of online business systems and to meet the needs of customers to enjoy services on both working days and weekends, the mapping relationship between business days and natural days in the business day configuration file can be one-to-one, or multiple non-working natural days can be mapped to the same business day, etc. In a test environment, the business day used for testing may be a historical natural day, or a billing day determined in advance according to the batch plan, or multiple dates can be mapped to the same business day, etc.

[0071] For example, in a business day configuration file, the mapping relationship between business days and natural days may be as shown in Table 2 below.

[0072] Table 2

[0073] Natural Day 20240508 20240509 20240510 20240511 20240512 Test business day 20241229 20241230 20241230 20241230 20241231

[0074] In Table 2, "20240508", "20241229", etc. are the writing formats of dates, that is, "20240508" represents May 8, 2024. It should be noted that in the embodiment of the present application, the date in the business day configuration file can also be in other formats, such as "2024 / 5 / 8", etc., and the present application does not limit this.

[0075] As can be seen from Table 2, the natural days "20240509", "20240510" and "20240511" correspond to the same business day "20241230". In other words, the sum of the transaction data within these three natural days is the total transaction data corresponding to the business day "20241230".

[0076] In an embodiment of the present application, the mapping relationship between natural days and business days in the business day configuration file can be queried according to the current date, and the next business day that needs to be switched after the current day is determined, that is, the first business day and all natural days associated with the first business day in the configuration file, so as to determine which natural days' transaction data need to be recorded after the record table is activated.

[0077] For example, when the current time is 0:00 on May 9, 2024, it can be determined according to Table 2 that the first business day associated with the current time is December 30, 2024, and all the first natural days associated with the first business day include May 9, 2024, May 10, 2024 and May 11, 2024. Therefore, after the first record table is activated, it is necessary to record the transaction data within these three natural days of May 9, 2024, May 10, 2024 and May 11, 2024.

[0078] Therefore, in this application, the mapping relationship between business days and natural days can be flexibly configured through the configuration file, which can meet the business day switching needs in different environments, improve the personalization and applicability of business day switching, and determine the business needs of data recording based on the natural day associated with the next business day, automatically adjust the parameters and strategies of data processing and analysis, and ensure the accuracy and validity of the data.

[0079] Step 104, update the value of the second field in the first record table to the first business day.

[0080] The second field refers to the value of the business day corresponding to the transaction data currently recorded in the corresponding record table in the data table. The value of the second field can be a date in any format, or a date plus a time, such as the current_date field in Table 1 in step 101 above.

[0081] In the embodiment of the present application, by updating the value of the second field in the first record table to the first business day, after the first record table is activated, the business day date corresponding to the transaction data stored in the first record table can be clearly identified, which is conducive to simplifying, more efficiently and reliably exporting, querying and batching data in the data table.

[0082] It should be noted that in some possible embodiments, there may be a situation where no business day configuration file is set, or the business day configuration file is an empty file. In this case, the current date corresponding to the first record table can be increased by 2 to determine the updated date of the first record table.

[0083] Combine the following Figure 2a Explain the update of the identifier in the data table during the business day switching process. Figure 2a The above Table 1 is used as a data table example.

[0084] like Figure 2a As shown, for data table 1, during the daily cutting process, the value of the first field of table b (i.e., the second record table at this time) can be updated to M (i.e., the third identifier) ​​with the value of the first field being identifier Y (i.e., the second identifier), so that the value of the first field of table a (i.e., the first record table at this time) with the value of the first field being identifier N (i.e., the first identifier) ​​can be updated to Y. After the value of the first field corresponding to table a is updated to Y, the value of the first field corresponding to table b can be updated from M to N, thereby completing the update of the first fields corresponding to the two record tables in the data table.

[0085] In the absence of a business day configuration file, each natural day corresponds to a business day by default, and the date currently corresponding to the first record table a can be increased by 2 to complete the update of the corresponding date in table a. As can be seen from Table 1, the current date corresponding to table a is December 1, 2023. After the date is increased by 2, the updated date can be obtained as December 3, 2023. After completing the business day switching process, data table Table 1 can be updated to the following Table 3.

[0086] Table 3

[0087] fileld1 fileld2 current_date enable login_a txn_a 2023 / 12 / 3 0:00:00 Y login_b txn_b 2023 / 12 / 2 0:00:00 N

[0088] When the next business day is switched, the first record table, the first field corresponding to the update record table, and the update date, etc. can be obtained based on Table 3.

[0089] It should be noted that, in some possible embodiments, there may be multiple natural days corresponding to the same business day in the business day configuration file. At this time, the transaction data generated in these multiple natural days are all recorded in the record table corresponding to the same business day date. For example, in the above Table 2, after the date corresponding to the first record table is updated to December 30, 2024, the transaction data of the natural days May 8, May 9 and May 10, 2024 will all be recorded in the first record table with the corresponding date of December 30, 2024. After that, when it is necessary to record the transaction data of May 11, the business day is switched, and the date corresponding to the first record table after the switch is updated to December 31, 2024. In addition, the system can also set up scheduled task scheduling, and update the data table through the end-of-day scheduling program to prevent date update failure.

[0090] Step 105 , when the first transaction data within the first natural day associated with the first business day is obtained, the first natural day and the first transaction data are associated and recorded in the business information field of the first record table.

[0091] The first transaction data refers to the transaction data collected in the system using the data processing method proposed in this application. The first transaction data refers to all transaction data generated within one or more first natural days associated with the updated first business day.

[0092] The business information field refers to a field in a record table used to store transaction data.

[0093] It should be noted that since a business day may contain transaction data generated in multiple natural days, in order to further improve the orderliness of data records in the record table, the date of each natural day can be associated with the transaction data generated in that natural day and stored in the business information field, which is convenient for querying and analyzing data within a single natural day. It should be noted that in this application, the transaction flow data of adjacent business days can be stored alternately in two tables, so that the first record table and the second record table can record the latest two days of transaction data, providing clearer data recording rules, and the sub-table storage can optimize query performance and facilitate data synchronization and backup.

[0094] For example, the two tables in the data table are called table a and table b respectively. Initially, the value of the first field corresponding to table a in the data table is the first identifier "N", and the value of the first field corresponding to table b is the second identifier "Y", then table a is the first record table, and table b is the second record table. When the current moment is the day-cut moment, the value of the first field corresponding to table a can be updated to "Y", and the corresponding date can be updated to the next business day date that needs to be switched corresponding to the current moment in the business day configuration file, so that the transaction data generated in all natural days corresponding to the next business day date can be stored in table a, and at the same time, the value of the first field corresponding to table b is updated to the second identifier "N". Then, at the next day-cut moment, table b is the first record table, and table a is the second record table, and the transaction data of the next business day can be stored in table b, so that different tables can be activated alternately in the data table to complete the switching of business days and data storage.

[0095] It can be understood that when business days are natural days, the storage process of transaction data within multiple business days can be simplified as follows: the transaction data on the first day is recorded in table a, the transaction data on the second day is recorded in table b, the first day's data in table a is cleared on the third day, and the new transaction data on the third day is recorded in table a, the second day's data in table b is cleared on the fourth day, and the new transaction data on the fourth day is recorded in table b, and so on, and the data storage has been circulating in tables a and b.

[0096] In this embodiment, when the current time is the day-cut time, the value of the corresponding first field in the data table is set to the record table of the first identifier, and the value of the first field is updated to the second identifier to activate the function of storing transaction data in the record table, and the value of the second field corresponding to the activated record table is updated by querying the next business day date that needs to be switched at the current time in the business day configuration file, so that the transaction data corresponding to the next business day can be recorded in the business information field of the record table. In this way, automatic business day switching is realized, and data of different business days can be alternately stored in different tables, which improves the efficiency and flexibility of business day switching, facilitates incremental data supply, and does not require manual intervention, thereby improving the efficiency of data processing and management.

[0097] Combine the following Figure 2b and Figure 2c To illustrate the business day switching in different environments, Figure 2b Switching for business days in production environments, Figure 2c Switch for business days in the test environment.

[0098] like Figure 2bAs shown, when scheduling and switching business days in a production environment, the mapping relationship between business days and natural days in the business day configuration file can be read first, and the current time is determined to be the planned date for business day switching according to the business day corresponding to the current time and all natural days corresponding to the business day in the business day configuration file. For example, when the mapping relationship in the business day configuration file is as shown in Table 2, it can be known that the planned dates for business day switching are 20240508, 20240509, and 20240512. When the current time is May 8, 2024, it can be determined that the current business day is the planned date, and when the current time is May 10, 2024, it can be determined that the current business day is not the planned date.

[0099] In the case where the current date is the planned date, the business day switch can be performed, and the application flow data is directed to the activation flow table, that is, in the data table in the above embodiment, the value of the first field is the record table of the first identifier (such as table a). On the contrary, in the case where the current date is not the planned date, the date can be added by 1 and updated to the activation flow table. Then, it is further determined whether the updated date is the planned date. If not, the update continues. If so, the flow data in the table corresponding to the first identifier (table a) in the activation flow table can be moved to the history table, table a is cleared, and the application flow data is directed to table a in the activation flow table to store the transaction data of the business day in table a, and the business day switch is ended.

[0100] For example, as shown in Table 2, when the current date is 20240510, it can be determined that the business day is not a planned date, and the date can be updated to 20240511 in the activation flow table, and then the date is judged whether it is a planned date. When the date is updated to 20240512, it can be determined that the business day is a planned date, and it is necessary to switch to a new table to record transaction data.

[0101] like Figure 2c As shown, when scheduling and switching business days in a test environment, the process is similar to the business day switching process in a production environment. You can also first read the mapping relationship between business days and natural days in the business day configuration file, and determine whether the current time is the planned date for business day switching based on the business day corresponding to the current time in the business day configuration file and all natural days corresponding to the business day.

[0102] When the current date is the planned date, it can be determined that a business day switch is required, and the application flow data is directed to the table (table a) corresponding to the first identifier in the activation flow table. On the contrary, when the current date is not the planned date, the date can be added by 1 and updated to the activation flow table. Then, when the updated date is the planned date, the flow data in the table (table a) corresponding to the first identifier in the activation flow table can be moved to the history table, table a is cleared, and the application flow data is directed to table a in the activation flow table to store the transaction data of the business day, and the business day switch is ended.

[0103] Figure 3 A flowchart of another data processing method provided in an embodiment of the present application.

[0104] like Figure 3 As shown, the data processing method includes the following steps:

[0105] Step 301, when the current time is the day-cut time, traverse the first field in the data table to determine the first record table whose value of the first field is the first identifier.

[0106] For detailed description of the above step 301, please refer to other embodiments of the present disclosure and will not be repeated here.

[0107] It should be noted that because the two tables in the data table store business day data alternately, before switching business days and storing business day data, it is also necessary to export the historical business day data already in the first record table to clear the first record table to store the transaction data of the latest business day to avoid data confusion between different business days.

[0108] Step 302: Convert the data corresponding to the business information field in the first record table into a data file of a preset type.

[0109] The preset type may be a storage format specified by a database for storing data files, or may be a file type that is convenient for querying. For example, the preset type may be a text document (txt) or the like.

[0110] It is understandable that when transferring the data corresponding to the business information field in the first record table to another database, there may be problems such as format incompatibility or data permissions, so it is necessary to convert the data corresponding to the business information field to avoid transfer failure. Therefore, in the embodiment of the present application, the data corresponding to the business information field can be exported, and after converting the format, a data file of a preset type can be obtained, which is convenient for data exchange between different databases.

[0111] Step 303: associate the data file with the second business day currently corresponding to the second field in the first record table and store them in the historical data table.

[0112] The historical data table is used to store daily transaction data within a historical time period. The historical data table can store historical transaction data for the past year or two years, and this application does not limit the time span corresponding to the data stored in the historical data table.

[0113] The second business day is the date corresponding to the second field in the first record table before the current day cut time, that is, the business day date when the data file is generated. For example, in Table 1 of the above embodiment, the second business day corresponding to the first record table a is December 1, 2023.

[0114] In an embodiment of the present application, after the data in the first record table is exported as a data file, the obtained data file can be associated with the first date corresponding to the first record table at this time and stored in the historical data table, thereby ensuring that the data can still be queried after being unloaded from the record table.

[0115] It is understandable that after the data corresponding to the business information field in the first record table is exported as a data file of a specific type, the first record table will be cleared, and then the first field and the second field corresponding to the first record table can be updated and new transaction data can be stored.

[0116] Step 304: Update the value of the first field in the first record table to the second identifier.

[0117] Step 305, based on the current time, traverse the business day configuration file to determine the first business day associated with the current time and all first natural days associated with the first business day.

[0118] Step 306: Update the value of the second field in the first record table to the first business day.

[0119] Step 307: When the first transaction data within the first natural day associated with the first business day is obtained, the first natural day and the first transaction data are associated and recorded in the business information field of the first record table.

[0120] For detailed description of the above steps 304 to 307, reference may be made to other embodiments of the present disclosure and will not be repeated here.

[0121] In this embodiment, the data in the first record table is exported into a data file in a specific format, and the data file is associated with the business day date corresponding to the first record table and stored in the historical data table. This enables the storage and management of historical transaction data, provides conditions for subsequent data query, comparison, and analysis of business growth trends, improves data integration capabilities, and ensures data integrity and reliability.

[0122] Figure 4A flowchart of a data processing method provided in an embodiment of the present application.

[0123] like Figure 4 As shown, the data processing method includes the following steps:

[0124] Step 401: receiving a data query request.

[0125] The query request includes the second natural day to which the target data belongs. The target data is the data requested by the enterprise or individual, and the second natural day is the transaction date corresponding to the target data.

[0126] It should be noted that the target data can be all data of corporate or personal transactions within the next natural day, or data of certain business types, such as deposit records, withdrawal records or transfer records, etc. This application does not limit this.

[0127] In the embodiment of the present application, an enterprise or an individual can query the transaction data of any day in the system as needed, so that the system can receive a request to query the target data of transactions within the second date.

[0128] Step 402, based on the second natural day, traverse the business day configuration file to determine the third business day corresponding to the second natural day.

[0129] In the embodiment of the present application, since the transaction data is stored in the table in units of business days, when a user's request to query the data of a specific natural day is received, it is necessary to determine the third business day corresponding to the second natural day to be queried according to the business day configuration file, and then obtain the target data based on the third business day. The third business day may be the same as the value of the second field in the current data table, or it may be the same as the business day date associated with a data file in the historical data table.

[0130] Step 403, when the time interval between the third business day and the first business day corresponding to the current time is less than 2, obtain the target record table corresponding to the third business day from the data table.

[0131] In the embodiment of the present application, when the time interval between the third business day and the first business day corresponding to the current time is less than 2, it can be determined that the target data corresponding to the second date is either stored in the first record table or in the second record table. Therefore, the first record table or the second record table whose value of the second field in the database is the third business day can be determined as the target record table, so that the target data within the second natural day can be obtained in the target record table.

[0132] Step 404, traverse the target record table to obtain target data.

[0133] In an embodiment of the present application, after obtaining the target record table corresponding to the third business day, since the transaction data will be stored in association with the corresponding natural day when recording the transaction data in the record table, the business data associated with the second natural day can be traversed in the business information field of the target record table to obtain the target data.

[0134] In an embodiment of the present application, since the user identifiers and types corresponding to the data requested for query by different enterprises or individuals may be different, it is possible to further screen the business data associated with the second natural day based on the user identifier and / or type of the target query to obtain the target data corresponding to the user identifier and / or type.

[0135] In this embodiment, by determining the business day corresponding to the natural day to which the target query data belongs, and the time interval between the business day and the current business day, the record table containing the target data can be quickly located, so that the target data can be obtained from the activated flow table, and real-time query of the data managed on the day can be realized, which can improve the efficiency of data query and optimize query performance.

[0136] It should be noted that in the embodiment of the present disclosure, after the third business day corresponding to the second natural day is determined, and when the time interval between the third business day and the first business day is greater than or equal to 2, the target data file corresponding to the third business day can be first obtained from the historical data table. Then, based on the second natural day, the target data file is traversed to obtain the target data.

[0137] In the embodiment of the present application, when the time interval between the third business day and the first business day is greater than or equal to 2, it can be seen from the above embodiment that the transaction data within the second natural day is stored in the form of a data file in the historical data table, so that the data file associated with the third business day can be traversed in the historical data table to obtain the target data file. Then, the target data can be obtained by querying the transaction data associated with the second natural day in the target data file. Thus, it is possible to query historical transaction data with a long time interval. It ensures that enterprises or individuals can quickly obtain the required data, and provides data support for the analysis of transaction data and business decisions.

[0138] It should be noted that the data processing system provided by the present application can also provide a variety of query methods, including by time, by outlet, by business type, etc. As well as query results based on transaction data, it can also provide data statistics and analysis functions, including trend analysis, data comparison, business structure analysis, etc., to help enterprises or individuals better understand their business status and development trends.

[0139] That is to say, in the embodiment of the present application, in addition to completing business day switching and business day data storage, the data processing system can provide users with services such as data query, statistical analysis, and report generation.

[0140] Figure 5 A flowchart of another data processing method provided in an embodiment of the present application.

[0141] like Figure 5 As shown, the data processing method may include the following steps:

[0142] Step 501: receiving a data statistics request sent by a client.

[0143] The statistical request includes the target time period and display style corresponding to the statistical data.

[0144] In the embodiments of the present application, in order to understand the growth trend of the business, quickly understand the business status, and improve the efficiency and accuracy of decision-making, users (such as enterprises or individuals, etc.) usually have the need to perform statistics and analysis on historical transaction data. Therefore, in the present application, the data processing system can provide data statistics and analysis functions, including trend analysis, data comparison, business structure analysis, etc., in addition to completing business day switching and business day data storage, and can display data statistics and analysis results to users in a diversified and personalized visual report. Therefore, the system can receive data statistics requests including target time periods and display styles sent by users through the client.

[0145] It should be noted that the target time period is the time when the data that the user needs to perform statistical analysis is generated. The target time period may include one or more natural days, or may also include one or more business days, and may be determined based on actual statistical needs, and this application does not limit this. For example, when a user wants to count the total amount of expenditure in the past year, the target time period corresponding to the statistical data should be the year before the current date. The display style can be selected by the user according to needs, such as reports, bar charts, trend charts, etc., or it can be determined according to the type of statistical analysis currently required by the user. For example, when the user needs to analyze the data trend within the target time period, the target display style may be a line chart, and when the user needs to analyze the structure of the data within the target time period, the target display style may be a pie chart.

[0146] Step 502: based on the user information corresponding to the client, traverse the data table and / or the historical data table to obtain the to-be-stated data corresponding to the target period.

[0147] Among them, the user information corresponding to the client is information that identifies and describes the current logged-in user of the client, and may include at least one of the user name, mobile phone number, email address, and personal identity information (such as name, gender, age, address, etc.).

[0148] In the embodiment of the present application, since the target period may not only be the two most recent business days, it is necessary to traverse the data table and / or the historical data table when obtaining the to-be-stated data corresponding to the target period. In addition, the transaction data stored daily in the data processing system includes the transaction data of all users, and the data volume is large. Therefore, when traversing the to-be-stated data from the data table and / or the historical data table, it is also necessary to obtain the user information corresponding to the client sending the statistical request as a traversal condition, so as to obtain the to-be-stated data corresponding to the target period.

[0149] Step 503: parse the statistical data to be analyzed, obtain and return display data corresponding to the display style.

[0150] It should be noted that in the embodiments of the present application, tools such as Excel, Tableau, Power BI, etc. can be used to analyze the statistical data, obtain and return the display data corresponding to the display style, and thus generate a visual report.

[0151] In this embodiment, historical transaction data to be statistically analyzed is obtained based on the target time period and display style of the statistical data requested by the user, and highly readable display data is generated. Therefore, the data processing system provided by this application can provide data statistics and analysis functions, help enterprises or individuals better understand their business conditions and development trends, and help plan resources and specify budgets in advance, as well as improve the efficiency and accuracy of decision-making.

[0152] That is, in this application, users can calculate the total daily, weekly or monthly turnover in the data processing system to understand the growth trend of the business. Data can also be segmented by transaction type or customer group to identify which business areas or customer groups contribute the most to the total turnover. The system can also generate various reports according to user needs, including daily, weekly, monthly reports, etc., so that enterprises can conduct more detailed data analysis and management.

[0153] Figure 6 A flowchart of another data processing method provided in an embodiment of the present application.

[0154] like Figure 6 As shown, the data processing method may include the following steps:

[0155] Step 601, when the batch running time is reached, obtain the second transaction data whose value corresponding to the third field is a preset identifier from the data table and / or the historical data table.

[0156] Among them, the batch running time is the time point for running transaction data in batches according to business needs. It can be the same as the daily cutting time, or it can be later than the daily cutting time, such as 8 am, etc. This application does not limit this.

[0157] Among them, the third field is used to mark whether the transaction data in the corresponding record table or data file has completed the batch run. That is to say, in the embodiment of the present application, the value of the third field can be two kinds, which are used to indicate the completed batch run and the uncompleted batch run, and the preset mark is the value of the uncompleted batch run of the transaction data set as needed. For example, the value of the third field can be 0 or 1, and 0 is the preset mark.

[0158] It should be noted that in the embodiment of the present application, the frequency of batching can be set as needed, and batching can be performed every time a business day is switched, or data from multiple business days can be batched together. Therefore, depending on the frequency of batching, it may be necessary to obtain data only from the data table, or it may be necessary to obtain transaction data from the data table and the historical data table respectively.

[0159] For example, the preset flag is 0. When the batch running frequency is once a day, you can obtain a record table in which the value of the corresponding third field in the data table is 0 at a certain time at the same time or after the business day switch is completed (i.e., the batch running time). The data in the business information field is the second transaction data, that is, the transaction data newly stored in the data table when the business day switches.

[0160] Alternatively, when the batch running frequency is once a week, after the batch running time is reached (such as 8 o'clock every Monday), the transaction data of each business day of the previous week can be obtained from the data table and the historical data table, and used as the second transaction data for batch running.

[0161] In the present application, since the transaction data of each business day is stored in the data table and the historical data table, by directly adding a third field in the data table and the historical data table to identify the batch status of the associated transaction data, the batch process can be simplified, the batch efficiency can be improved, and the business day switching and collaboration between batches can be made more convenient.

[0162] Alternatively, in some possible embodiments, batching and business day switching can be completed in different systems. In this case, a business day batching parameter table can be set, and the business day data batching can be completed by calling data between the parameter table and the above data table and the historical data table. The batching parameter table can be shown in Table 4 below. Table 4 records whether the transaction data of each business day has been batched through a batching flag. When it is determined that the data of a certain date has not been batched, the transaction data of the corresponding date is obtained from the data table and / or the historical data table.

[0163] Table 4

[0164]

[0165]

[0166] In Table 4, the update time UpdateTime is the completion time of each batch run corresponding to each batch run. For example, in Table 4, the batch run time is 8 o'clock, and the time for updating the batch run flag after the batch run is completed may be 8 o'clock or 8:01, etc. current_date is the business day date corresponding to the batch run data, and the batch run flag BatchFlag can be 0 or 1. When the preset flag is 0, indicating that the transaction data corresponding to this date has not completed the batch run, it can be seen from Table 3 that the transaction data on December 2, 2023 has not completed the batch run, then the transaction data associated with December 2, 2023 can be obtained in the data table as the second transaction data that needs to be batched at present.

[0167] It should be noted that in the embodiment of the present application, after the end of the business day, summary data of customers logging in on the day, their activity status, and transaction volume and amount of each product, etc. can be generated by region, written into the daily result table, and displayed in the background page. This allows for a more intuitive understanding of the transaction status of the business day.

[0168] Therefore, in this application, the report module in the data processing system can design an automatic batch running method on business days to perform batch screening, calculation, integration and other processing on transaction data to update the data report content and display the transaction data and processing results of the previous business day.

[0169] Step 602, obtaining login information within a third date corresponding to the second transaction data, and user information of the user to whom the second transaction data belongs.

[0170] The login information refers to the data generated when the user logs into the online business system (such as mobile banking, etc.), which may include the number of logins, login time, whether the password is entered incorrectly, etc. The user information is the information that identifies and describes the user to whom the second transaction data belongs, and may include at least one of the following: user name, mobile phone number, email address, and personal identity information (such as name, gender, age, address, etc.).

[0171] In the embodiment of the present application, the user needs to log in to the system before conducting a transaction with the system. The system can not only store the user's login information, but also obtain the user information of the user. Therefore, after the user completes the transaction with the system, the system can associate the generated transaction data with the transaction date and the user information of the user to which it belongs. Thus, after obtaining the second transaction data that needs to be batched, the corresponding login information within the third date and the user information of the user to which the second transaction data belongs can be directly obtained in the system.

[0172] Step 603, processing the login information, user information and second transaction data to obtain processed data.

[0173] In an embodiment of the present application, after obtaining the login information, user information and the second transaction data, the upstream business day data is complete, and these data can be loaded into a temporary table, and then sorted in the temporary table, the data that does not meet the conditions for the report to be generated is cleaned, and the data format is converted so that the processed data can meet the data requirements for generating the report.

[0174] It should be noted that, in the embodiment of the present application, different data processing methods can also be used to process the login information, user information and the second transaction data, so that the data used to generate the report is more personalized.

[0175] Optionally, the data processing method may be determined first according to the type of the system to which the second transaction data belongs.

[0176] It should be noted that different types of systems may have different data processing methods. The data can be organized into the form of reports, or processed into the form of graphics.

[0177] Then, based on the data processing method, the login information, the user information and the second transaction data may be processed to obtain processed data.

[0178] In the embodiment of the present application, by processing the login information, user information and the second transaction data in a processing method suitable for the type of system to which the transaction data belongs, the personalization and reliability of data processing can be improved, and a data basis for subsequent report generation can be provided. In addition, by presenting the analysis results of the transaction data in the form of charts or reports, the data can be displayed more intuitively and help decision makers quickly understand the business situation.

[0179] Step 604, storing the processed data into the historical data table, and updating the batch identifier corresponding to the second transaction data to a non-preset identifier.

[0180] In the embodiment of the present application, the processed data can be stored in the historical data table for generating reports. It can also be determined that the batch run of the second transaction data is completed, and the corresponding batch run flag is updated to a non-preset flag (e.g., "1"), and the update time is recorded.

[0181] It should be noted that by running data in batches, user operations and system operation logs can be recorded for subsequent system maintenance and troubleshooting.

[0182] In this embodiment, when the batching time is reached, the second transaction data corresponding to the batching mark as the preset mark is obtained from the data table and / or the historical data table, and then the second transaction data and its corresponding login information and user information are processed to obtain data for generating reports, complete the batching of the second transaction data, and update the batching mark. Thus, the automatic batching of transaction data can be realized, the efficiency of report generation can be improved, and enterprises or individuals can perform more detailed data analysis and management, and optimize the user experience.

[0183] Combine the following Figure 7 The process of processing report data is explained by example. Figure 7 This is a flowchart for report data processing.

[0184] like Figure 7 As shown, the report module can first determine whether there is a date that needs to be run (i.e. Figure 7 In the first job), if there is no date that needs to be run in batches, there is no need to process the report data and the process ends. Or if there is a date that needs to be run in batches, read multiple transaction data with the run-batch flag of 0. The transaction data can be arranged from small to large according to the transaction date, so that batches can be run in order (i.e. Figure 7 In the third task in the process, transaction flow 1 is the smallest transaction data on the corresponding date). In addition, the login information on the date that needs to be batched can be obtained through task 2, and the user information corresponding to the customer who generated transaction data on the date that needs to be batched can be obtained through task 3. After that, the data in the temporary table can be cleaned up, and the data and information obtained from tasks 2, 3, and 4 can be loaded into the temporary table (i.e. Figure 7 In the fifth step of the process, clean the data that does not meet the report conditions and convert the format of other data to complete the data preprocessing. Finally, the data can be summarized to the basic data layer, classified and calculated to generate the result table of the report. Finally, the batch run flag corresponding to the date that needs to be run can be updated to 1, the batch run time can be updated, and the batch run can be completed.

[0185] It should be noted that Figure 7The report data processing process shown can be combined with the business day switching and data storage process described in the above embodiments to achieve fully automated business day switching and batch running, further improving data processing efficiency, optimizing user experience, and helping to enhance the competitiveness and efficiency of the enterprise.

[0186] It should be noted that the report module may include a temporary data layer, a report summary layer, a report result layer, and a data view display layer.

[0187] The temporary data layer is to load data into temporary tables for data cleaning and format conversion. The report summary layer is to store the data processed by the temporary data layer into the report database, and to perform multi-table association, data summary and classification on the data of the previous business day in the report database. The report result layer is to summarize and classify the data after the report summary layer is classified, calculate the total transaction volume of each type of data, and generate the report result table.

[0188] In the data view display layer, you can use SQL statements to write data views, process the result table data again, and filter out the corresponding report data according to the conditions. For example, the institution number condition can filter out the transaction volume and transaction amount of all products on the day. The transaction report column can include data related to the mobile phone number transfer object (this bank or other banks), transfer time (immediate or delayed), bank card transfer, physical precious metal purchase, foreign exchange trading, foreign exchange settlement and sale, fund purchase, fund subscription, fund fixed investment, fund redemption, replacement, fixed investment change, payment of premiums, notice deposit, zero deposit and full withdrawal, full deposit and full withdrawal, large-denomination certificate of deposit, fixed-term and flexible transfer, scan code transfer, mobile phone number collection, payment code payment, payment of electricity bills, water bills, gas bills and telephone bills, etc.

[0189] In addition, the report module can also process monthly, quarterly and annual reports based on daily upstream incremental data and full data. The activity report supports setting the planned number in advance, such as the number of new customers that an institution needs to add this month. Other columns include the number of logged-in customers, the number of trading customers, the activity rate (number of logged-in customers / number of customers), the trading activity rate (number of trading customers / number of customers), the number of new customers, the number of closed accounts, the planned number of new customers and the completion ratio (number of new customers / planned number of new customers).

[0190] In order to implement the above embodiments, the present application also proposes a data processing device.

[0191] Figure 8 A schematic diagram of the structure of a data processing device provided in an embodiment of the present application.

[0192] like Figure 8 As shown, the data processing device 800 includes:

[0193] The first determination module 801 is used to traverse the first field in the data table and determine the first record table whose value is the first identifier when the current time is the day cutting time;

[0194] A first updating module 802, configured to update the value of the first field in the first record table to a second identifier;

[0195] The second determination module 803 is used to traverse the business day configuration file based on the current time, and determine the first business day associated with the current time, and all first natural days associated with the first business day, wherein the business day configuration file includes a mapping relationship between business days and natural days;

[0196] The second updating module 804 is used to update the value of the second field in the first record table to the first business day;

[0197] The recording module 805 is used to record the first natural day and the first transaction data in association with each other in the business information field of the first record table when the first transaction data within the first natural day associated with the first business day is obtained.

[0198] Furthermore, the first updating module 802 may also be used to:

[0199] Determine a second record table in which the value of the first field in the data table is a second identifier;

[0200] Update the value of the first field in the second record table to the third identifier;

[0201] After the value of the first field in the first record table is updated to the second identifier, the value of the first field in the second record table is updated to the first identifier.

[0202] Furthermore, the first acquisition module 801 may also be used for:

[0203] Converting the data corresponding to the business information field in the first record table into a data file of a preset type;

[0204] The data file is associated with the second business day currently corresponding to the second field in the first record table and stored in the historical data table.

[0205] Furthermore, the data processing device 800 may further include:

[0206] A first receiving module is used to receive a data query request, wherein the query request includes the second natural day to which the target data belongs;

[0207] A third determination module is used to traverse the business day configuration file based on the second natural day to determine the third business day corresponding to the second natural day;

[0208] A first acquisition module, configured to acquire a target record table corresponding to the third business day from a data table when the time interval between the third business day and the first business day corresponding to the current time is less than 2;

[0209] The second acquisition module is used to traverse the target record table to obtain target data.

[0210] Furthermore, the first acquisition module may also be used to:

[0211] When the time interval between the third business day and the first business day is greater than or equal to 2, obtaining a target data file corresponding to the third business day from the historical data table;

[0212] Based on the second natural day, the target data file is traversed to obtain the target data.

[0213] Furthermore, the data processing device 800 may further include:

[0214] The second receiving module is used to receive a data statistics request sent by a client, wherein the statistics request includes a target time period and a display style corresponding to the statistics data;

[0215] A third acquisition module is used to traverse the data table and / or the historical data table based on the user information corresponding to the client to obtain the to-be-stated data corresponding to the target period;

[0216] The parsing module is used to parse the statistical data to obtain and return the display data corresponding to the display style.

[0217] Furthermore, the data processing device 800 may further include:

[0218] A fourth acquisition module is used to acquire, when the batch running time is reached, second transaction data whose value corresponding to the third field is a preset identifier from the data table and / or the historical data table;

[0219] a fifth acquisition module, used to acquire login information within a fourth business day corresponding to the second transaction data, and user information of a user to which the second transaction data belongs;

[0220] A processing module, used for processing the login information, the user information and the second transaction data to obtain processed data;

[0221] The third updating module is used to store the processed data into the historical data table, and update the value of the third field corresponding to the second transaction data to a non-preset identifier.

[0222] Optionally, the processing module may be specifically used for:

[0223] determining a data processing method according to a type of a system to which the second transaction data belongs;

[0224] Based on the data processing method, the login information, the user information and the second transaction data are processed to obtain processed data.

[0225] The functions and specific implementation principles of the above modules in the embodiments of the present application can be referred to the above method embodiments and will not be repeated here.

[0226] In the embodiment of the present application, when the current time is the day-cut time, the value of the corresponding first field in the data table is set to the record table of the first identifier, and the value of the first field is updated to the second identifier to activate the function of storing transaction data in the record table, and by querying the next business day date that needs to be switched at the current time in the business day configuration file, the value of the second field corresponding to the activated record table is updated, so that the transaction data corresponding to the next business day can be recorded in the business information field of the record table. In this way, automatic business date switching is realized, and data of different business days can be alternately stored in different tables, which improves the efficiency and flexibility of business day switching, facilitates incremental data supply, and does not require manual intervention, thereby improving the efficiency of data processing and management.

[0227] In order to implement the above embodiments, the present application also proposes an electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the data processing method provided by the above embodiments.

[0228] As an example, Fig. 9 is a schematic diagram of the structure of an electronic device shown in an exemplary embodiment of the present disclosure, such as Fig. 9 As shown, the electronic device 900 may further include:

[0229] The memory 910 and the processor 920, a bus 930 connecting different components (including the memory 910 and the processor 920), the memory 910 stores a computer program, and when the processor 920 executes the program, the business data processing method of the embodiment of the present disclosure is implemented.

[0230] Bus 930 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0231] The electronic device 900 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by the electronic device 900, including volatile and non-volatile media, removable and non-removable media.

[0232] The memory 910 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 960 and / or cache memory 950. The electronic device 900 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 960 may be used to read and write non-removable, non-volatile magnetic media ( Fig. 9 not shown, usually called a "hard drive"). Although Fig. 9 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 930 via one or more data medium interfaces. The memory 910 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.

[0233] A program / utility 980 having a set (at least one) of program modules 970 may be stored, for example, in the memory 910, such program modules 970 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 970 generally perform the functions and / or methods of the embodiments described in the present disclosure.

[0234] The electronic device 900 may also communicate with one or more external devices 990 (e.g., keyboard, pointing device, display 991, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 900, and / or communicate with any device that enables the electronic device 900 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 992. In addition, the electronic device 900 may also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN) and / or public network, such as the Internet) through a network adapter 993. As shown, the network adapter 993 communicates with other modules of the electronic device 900 through a bus 930. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0235] The processor 920 executes various functional applications and data processing by running the programs stored in the memory 910 .

[0236] It should be noted that the implementation process and technical principles of the electronic device of this embodiment refer to the aforementioned explanation of the data processing method of the embodiment of the present disclosure, and will not be repeated here.

[0237] In order to implement the above embodiments, the present application also proposes a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the data processing method provided by the above embodiments.

[0238] In order to implement the above embodiments, the present application also proposes a computer program product, including a computer program, which implements the data processing method provided by the above embodiments when executed by a processor.

[0239] The collection, storage, use, processing, transmission, provision and disclosure of user personal information involved in this application are in compliance with relevant laws and regulations and do not violate public order and good morals.

[0240] It should be noted that personal information from users should be collected for legitimate and reasonable purposes and should not be shared or sold outside of these legitimate uses. In addition, such collection / sharing should be carried out after receiving the user's informed consent, including but not limited to notifying the user to read the user agreement / user notice and sign the agreement / authorization including authorization of relevant user information before the user uses the function. In addition, any necessary steps should be taken to protect and safeguard access to such personal information data and ensure that others who have access to personal information data comply with its privacy policy and procedures.

[0241] The present application is expected to provide an implementation scheme for users to selectively block the use or access of personal information data. That is, the present disclosure is expected to provide hardware and / or software to prevent or block access to such personal information data. Once the personal information data is no longer needed, the risk can be minimized by limiting data collection and deleting the data. In addition, when applicable, such personal information is de-identified to protect the privacy of the user.

[0242] In the description of the aforementioned embodiments, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0243] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0244] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code comprising one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present application includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present application belong.

[0245] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute the instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0246] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0247] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0248] In addition, each functional unit in each embodiment of the present application may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0249] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present application. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present application.

Claims

1. A data processing method, characterized in that: include: When the current time is the day-cut time, traverse the first field in the data table to determine a first record table whose value is the first identifier; Updating the value of the first field in the first record table to a second identifier; Based on the current time, traverse a business day configuration file to determine a first business day associated with the current time and all first natural days associated with the first business day, wherein the business day configuration file includes a mapping relationship between business days and natural days; Update the value of the second field in the first record table to the first business day; When the first transaction data within the first natural day associated with the first business day is obtained, the first natural day and the first transaction data are associated and recorded in the business information field of the first record table.

2. The method according to claim 1, characterized in that After obtaining the first record table in which the value of the first field is the first identifier, the method further includes: Determine a second record table in which the value of the first field in the data table is a second identifier; Updating the value of the first field in the second record table to a third identifier; After the value of the first field in the first record table is updated to the second identifier, the value of the first field in the second record table is updated to the first identifier.

3. The method according to claim 1, characterized in that After obtaining the first record table in which the value of the first field is the first identifier, the method further includes: Converting the data corresponding to the business information field in the first record table into a data file of a preset type; The data file is associated with the second business day currently corresponding to the second field in the first record table and stored in the historical data table.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: receiving a data query request, wherein the query request includes the second natural day to which the target data belongs; Based on the second natural day, traverse the business day configuration file to determine a third business day corresponding to the second natural day; When the time interval between the third business day and the first business day corresponding to the current time is less than 2, obtaining a target record table corresponding to the third business day from the data table; The target record table is traversed to obtain the target data.

5. The method according to claim 4, characterized in that After determining the third business day corresponding to the second natural day, the method further includes: When the time interval between the third business day and the first business day is greater than or equal to 2, acquiring a target data file corresponding to the third business day from the historical data table; Based on the second natural day, the target data file is traversed to obtain the target data.

6. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Receive a data statistics request sent by a client, wherein the statistics request includes a target time period and a display style corresponding to the statistics data; Based on the user information corresponding to the client, traverse the data table and / or the historical data table to obtain the to-be-stated data corresponding to the target time period; The to-be-stated data is parsed to obtain and return display data corresponding to the display style.

7. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: When the batch running time is reached, second transaction data corresponding to the third field with a value of a preset identifier is obtained from the data table and / or the historical data table; Acquire login information within the fourth business day corresponding to the second transaction data, and user information of a user to whom the second transaction data belongs; Processing the login information, user information and second transaction data to obtain processed data; The processed data is stored in the historical data table, and the value of the third field corresponding to the second transaction data is updated to a non-preset identifier.

8. The method according to claim 7, characterized in that The processing of the login information, the user information and the second transaction data to obtain processed data includes: determining a data processing method according to a type of a system to which the second transaction data belongs; Based on the data processing method, the login information, user information and second transaction data are processed to obtain processed data.

9. A data processing device, characterized in that: include: A first determination module is used to traverse the first field in the data table and determine a first record table whose value is a first identifier when the current time is a day-cut time; A first updating module, used for updating the value of the first field in the first record table to a second identifier; a second determination module, configured to traverse a business day configuration file based on the current time, and determine a first business day associated with the current time, and all first natural days associated with the first business day, wherein the business day configuration file includes a mapping relationship between business days and natural days; A second updating module, configured to update the value of the second field in the first record table to the first business day; The recording module is used to record the first natural day and the first transaction data in association with each other in the business information field of the first recording table when the first transaction data within the first natural day associated with the first business day is obtained.

10. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the data processing method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the data processing method according to any one of claims 1 to 8 when executed by a processor.

12. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the data processing method according to any one of claims 1 to 8.

Images