Financial information management method and system
Through the intelligent classification transfer mechanism, the server is dynamically adjusted according to the type of financial data and the frequency of access, solving the problem of waste and maintenance costs of traditional financial information management systems, and achieving efficient and flexible financial data processing and system stability.
Patent Information
- Application Number
- CN202411032846.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-30
- Publication Date
- 2024-11-12
AI Technical Summary
Due to the centralized storage and unified processing methods, traditional financial information management systems have wasted resources, high maintenance costs and low efficiency, making it difficult to cope with the needs of expanding enterprise scale and increasing business complexity.
Through the intelligent classification transfer mechanism, financial data is dynamically transferred to servers with different response rates according to type and access frequency, ensuring that high priority or high access data is processed on high response rate servers, and low priority or low access is allowed. Transfer the quantity data to a server with a slightly lower response rate to optimize resource allocation.
It improves the flexibility and efficiency of data processing, reduces operating costs, enhances the scalability and stability of the system, and improves the response speed and user experience of the overall financial information management system.
Smart Images

Figure CN118939197A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure belongs to the technical field of information management, and more specifically, to a financial information management method and system. Background Art
[0002] In the current financial information management field, with the expansion of enterprise scale and the increase of business complexity, traditional financial management systems are facing the problem of rising maintenance costs. These systems often adopt centralized storage and unified processing methods, and all data are processed on servers with the same configuration. This "one-size-fits-all" processing method not only leads to waste of resources, but also increases equipment maintenance costs and inefficiency. Summary of the invention
[0003] The purpose of the present disclosure is to provide a financial information management method and system to solve the problems of high maintenance cost and low efficiency of existing financial information management.
[0004] A first aspect of the embodiments of the present disclosure provides a financial information management method, including: In response to receiving the financial data, storing the financial data in a temporary server; If the data type of the financial data in the temporary server is the first data type, or the number of times the target user accesses the financial data within the first period is greater than a first threshold, transferring the financial data from the temporary server to the first server; If the data type of the financial data in the temporary server is the second data type, or the number of times the target user accesses the financial data within the first period is less than or equal to the first threshold, transferring the financial data from the temporary server to the second server; The response rate of the first server is greater than the response rate of the second server.
[0005] A second aspect of the embodiments of the present disclosure provides a financial information management device, including: A receiving module, configured to store the financial data in a temporary server in response to receiving the financial data; A first judgment module is used to transfer the financial data from the temporary server to the first server if the data type of the financial data in the temporary server is the first data type, or the number of times the target user accesses the financial data within a first period of time is greater than a first threshold; The second judgment module is used to transfer the financial data from the temporary server to the second server if the data type of the financial data in the temporary server is the second data type, or the number of times the target user accesses the financial data within a first period of time is less than or equal to a first threshold; and the response rate of the first server is greater than the response rate of the second server.
[0006] According to a third aspect of an embodiment of the present disclosure, a financial information management system is provided, comprising an electronic device, wherein the electronic device comprises a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor implements the steps of the above-mentioned financial information management method when executing the computer program.
[0007] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned financial information management method are implemented.
[0008] The beneficial effects of the financial information management method and system provided by the embodiments of the present disclosure are: On the one hand, the present disclosure improves the flexibility and efficiency of data processing through an intelligent classification transfer mechanism. Financial data of different types or access frequencies are transferred to servers with different response rates, ensuring that high-priority or high-access financial data can be processed more quickly, thereby improving the response speed and user experience of the overall financial information management system.
[0009] On the other hand, the present disclosure optimizes resource allocation and reduces operating costs. By transferring financial data with less access or low priority to servers with a slightly lower response rate, server resources can be reasonably allocated to avoid resource waste and unnecessary cost expenditure. At the same time, this differentiated processing method also enhances the scalability and stability of the system, leaving room for future business growth and changes in data processing requirements. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0011] Figure 1 A flowchart of a financial information management method provided by an embodiment of the present disclosure; Figure 2 A structural block diagram of a financial information management device provided by an embodiment of the present disclosure; Figure 3 A schematic block diagram of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION
[0012] In the following description, specific details such as specific system structures and technologies are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present disclosure. However, it should be clear to those skilled in the art that the present disclosure may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obstructing the description of the present disclosure with unnecessary details.
[0013] In order to make the purpose, technical solutions and advantages of the present disclosure more clear, specific embodiments will be described below in conjunction with the accompanying drawings.
[0014] Please refer to Figure 1 , Figure 1 A flowchart of a financial information management method provided by an embodiment of the present disclosure, the method comprising: S101: In response to receiving financial data, storing the financial data in a temporary server.
[0015] In this embodiment, financial data refers to all types of data related to financial activities, including but not limited to income, expenditure, assets, liabilities, profits, costs, etc. These data are usually used to record, analyze and report the company's financial status and operating results.
[0016] A temporary server refers to a server that is temporarily used to store, process or transmit data. Unlike a long-term server, a temporary server can only run for a specific period of time, or be shut down or deleted after completing a specific task. In this embodiment, the temporary server is used as a place to store received financial data. Temporary servers have the characteristics of low cost, easy configuration and management, and are suitable for handling temporary, high-traffic data storage needs.
[0017] When the system receives financial data, it will first store the data in a temporary server in order to determine the data type of the financial data and count the frequency of users accessing different types of data. Based on the confirmed data type and access frequency of the financial data, the system will transfer the financial data in the temporary server to other fixed servers for long-term storage and to meet the user's access needs.
[0018] S102: If the data type of the financial data in the temporary server is the first data type, or the number of times the target user accesses the financial data within the first period is greater than a first threshold, the financial data is transferred from the temporary server to the first server.
[0019] In this embodiment, the financial data mainly includes basic financial statement data, detailed financial statement data, and other related data. Among them, the basic financial statement data includes the balance sheet, income statement, and cash flow statement. These statements reflect the comprehensive information of the company's financial status, operating results, and cash flow.
[0020] Detailed financial statements include asset and liability data, profit data, cash flow data, financial indicator data, etc. Asset and liability data: including total assets, total liabilities, total owner's equity, etc., reflecting the financial status of the enterprise. Profit data: including operating income, operating costs, taxes and surcharges, sales expenses, administrative expenses, financial expenses, investment income, operating profit, total profit, net profit, etc., reflecting the profitability of the enterprise. Cash flow data: including cash flow from operating activities, cash flow from investment activities, cash flow from financing activities, etc., reflecting the cash flow of the enterprise. Financial indicator data: such as current ratio, quick ratio, debt-to-asset ratio, inventory turnover rate, accounts receivable turnover rate, operating profit margin, net profit margin, return on total assets, etc., are used to evaluate the financial health and operating efficiency of the enterprise.
[0021] Other relevant data include: budget data, equity structure data, tax data and financial statement notes data, etc. Financial data covers the company's assets and liabilities, profits, cash flow, financial indicators, budget, equity structure, taxation and financial statement notes. Through these data, the company's management can fully understand the company's financial status and operating results and adjust the company's decisions in a timely manner.
[0022] Compared with the temporary server, the first server can store important financial data of the first data type, such as cash flow data, profit data, etc. The first server can also store data whose number of times the target user accesses the financial data within a first time period is greater than a first threshold. The first time period can be any predefined time period, such as a day, a week, or a month, depending on the data access pattern and business needs. The first threshold is set based on historical data and business rules to determine whether the data should be transferred to a higher performance or more secure storage server.
[0023] Because the number of accesses to the financial data in the first time period is greater than the first threshold, it reflects that the data is important, so it can be stored in the first server. The first server can be a hot server that is always on and has a fast response rate.
[0024] In this embodiment, the system first checks the data type of the financial data in the temporary server. The first data type generally refers to data types that require higher security, more frequent access, or more stable storage, such as transaction records, bill details, financial statements, etc. If the data type is the first data type, the data will be stored in the first server, otherwise the data will remain in the temporary server unless other transfer criteria are met. Alternatively, if the number of times the target user accesses the financial data in the temporary server within the first time period is greater than the first threshold, the financial data that meets the conditions in the temporary server can also be transferred to the first server.
[0025] S103: If the data type of the financial data in the temporary server is the second data type, or the number of times the target user accesses the financial data within the first period of time is less than or equal to the first threshold, the financial data is transferred from the temporary server to the second server; the response rate of the first server is greater than the response rate of the second server.
[0026] In this embodiment, financial data is initially stored in a temporary server for preliminary processing, updating or short-term storage needs. This embodiment provides an intelligent data storage strategy based on financial data characteristics and user access patterns, the core of which is to dynamically adjust the storage location of data according to the characteristics of the data and the frequency of user access to optimize resource utilization and response performance.
[0027] First, the system determines the data type of the financial data in the temporary server. If the data type is the second data type, this indicates that the data does not need to be accessed or processed as frequently as the first data type, or does not need to have a high response time.
[0028] Secondly, when the data type of the financial data is the second data type, or the number of accesses is less than or equal to the first threshold, the system migrates the qualified financial data from the temporary server to the second server. The second server has different characteristics from the first server, such as a lower response rate, but can provide more economical storage costs, and is suitable for storing data with low access frequency or low response time requirements.
[0029] In the intelligent data storage strategy, the response rate of the first server is greater than that of the second server, which means that the first server is more suitable for processing data that requires a fast response, while the second server may be more suitable for storing data that has a low access frequency and does not require a high response time.
[0030] It can be concluded from the above that, on the one hand, the present disclosure improves the flexibility and efficiency of data processing through an intelligent classification transfer mechanism. Financial data of different types or access frequencies are transferred to servers with different response rates respectively, ensuring that high-priority or high-access financial data can be processed more quickly, thereby improving the response speed and user experience of the overall financial information management system.
[0031] On the other hand, the present disclosure optimizes resource allocation and reduces operating costs. By transferring financial data with less access or low priority to servers with a slightly lower response rate, server resources can be reasonably allocated to avoid resource waste and unnecessary cost expenditure. At the same time, this differentiated processing method also enhances the scalability and stability of the system, leaving room for future business growth and changes in data processing requirements.
[0032] In one embodiment of the present disclosure, the financial information management method further includes: In response to the number of times the financial data in the second server is accessed within a second time period being greater than a second threshold, data of the same data type as the financial data in the second server is transferred to the first server; the second time period is greater than the first time period.
[0033] In this embodiment, the response rate of the second server is lower than that of the first server and is not in a long-term power-on state. If the number of times the financial data in the second server is accessed within the second time period is greater than the second threshold, it means that some infrequently accessed key financial data stored in the second server has received attention from managers within the second time period. Therefore, in order to facilitate managers to quickly and accurately export such key financial data in the later stage, such financial data can be transferred to the first server with a higher response rate.
[0034] For example, the first duration is set to one week. The second duration is set to one month, and the second threshold is set to 5. Various financial data, such as monthly sales reports and quarterly cost analysis, are stored in the temporary server. Relatively infrequently accessed data, such as financial audit reports of some historical years, are stored in the second server. Within one month, the finance department accessed the financial audit reports from three years ago stored in the second server more than five times. Since the number of accesses exceeds the threshold, this indicates that such data has received attention from management personnel during this period. In order to facilitate subsequent rapid access and export, these financial audit reports will be transferred from the second server to the first server, which has a higher response rate and is powered on for a long time.
[0035] It can be concluded from the above that this embodiment not only ensures that commonly used data can be quickly responded to, but also can flexibly adjust the storage location of infrequently accessed but periodically important data according to actual access conditions, thereby improving the efficiency of data management and use.
[0036] In one embodiment of the present disclosure, transferring data of the same data type as financial data in the second server to the first server includes: The data of the same data type as the financial data in the second server are all transferred to the first server at one time, or the data of the same data type as the financial data in the second server are transferred to the first server in batches.
[0037] In this embodiment, there are two transfer methods for transferring data of the same data type as the financial data in the second server to the first server. The first is to transfer all the data at once, and the second is to transfer the data in batches.
[0038] Transfer all at once: If the system resources are sufficient, the network bandwidth allows, and the data volume is not extremely large, a single full transfer can quickly complete the data migration and reduce the overall migration time. In addition, a single transfer does not require the design of a complex batch strategy, which simplifies the migration process and reduces the risk of errors. A single transfer can also reduce the additional maintenance burden caused by batch migration.
[0039] Transfer in batches: When the amount of data is very large or system resources are limited, transferring in batches can avoid excessive load pressure on the second and first servers and ensure the normal operation of the system; the amount of data and migration time of each batch can also be adjusted according to actual conditions to adapt to changing factors such as network bandwidth fluctuations and system maintenance windows. During the migration process, if problems occur (such as network interruptions, server failures, etc.), transferring in batches can make it easier to recover, and only the affected batches need to be re-migrated, reducing the risk of overall data migration. For data that needs to be continuously updated, transferring in batches can make it easier to achieve incremental migration, that is, only migrate the data that has changed since the last migration, thus saving time and resources.
[0040] From the above, we can conclude that the choice of transferring all data at once or transferring data in batches needs to be weighed according to the actual situation. If the amount of data is moderate, the system resources are sufficient, and there are strict requirements for the migration time, you can transfer all data at once; if the amount of data is huge, the system resources are limited, or higher flexibility and risk control capabilities are required, transferring data in batches is more appropriate. In some cases, these two methods can also be combined, such as migrating most of the data at once, and then migrating the remaining small part of the data in batches.
[0041] In one embodiment of the present disclosure, transferring data of the same data type as financial data in the second server to the first server in batches includes: The data in the second server having the same data type as the financial data is marked as target data, and the target data is transferred to the first server in batches based on the data volume of the target data.
[0042] In this embodiment, when transferring data in batches, first identify data of the same data type as the financial data in the second server, and mark these data as "target data". This step is to ensure that only financial-related data can be selected for migration. Evaluate the data volume of the marked target data. Determine its scale by calculating the total amount of files or memory of the target data. Based on the total data volume of the target data, combined with factors such as network bandwidth, system load, and migration time window, the target data is reasonably divided into multiple batches. The data volume of each batch should be moderate, which can ensure the efficiency of migration without placing too much burden on the system.
[0043] Secondly, the target data of each batch is transferred from the second server to the first server in order according to the divided batch order. During the migration process, security measures such as data compression and encryption need to be considered to ensure the security and integrity of the data.
[0044] Finally, after each batch of data is migrated, a verification operation is performed to ensure that the migrated data is complete and correct, and that the data on the first server is consistent with the original data on the second server. When all batches of target data have been successfully migrated and verified, the entire migration process is complete. At this point, the first server already contains the same type of financial data as the second server, and subsequent data processing or analysis can be performed.
[0045] From the above, it can be concluded that transferring the financial data to the first server in batches, marking the target data and reasonably dividing the batches based on the data volume, ensures the efficiency and security of the migration process, reduces the system load, improves the flexibility and success rate of migration, and ensures the integrity and availability of the financial data.
[0046] In one embodiment of the present disclosure, transferring data of the same data type as financial data in the second server to the first server in batches includes: The data in the second server having the same data type as the financial data is marked as target data, and the target data is transferred to the first server in batches based on the import date of the target data.
[0047] In this embodiment, the financial data may also be transferred in batches according to the import date.
[0048] First, identify the data of the same data type as the financial data in the second server, sort them according to the import date, and then mark them as "target data". This step ensures that the data is processed in chronological order. Divide them into multiple batches based on the import date of the target data. You can set the time period included in each batch according to actual needs and system processing capabilities, such as monthly batches, weekly batches, or daily batches, etc.
[0049] Secondly, prepare a migration script or configure a migration task for each batch of data to ensure that the target data within the specified time period can be accurately extracted from the second server. Execute the migration tasks in sequence according to the divided batches to transfer the target data of each batch from the second server to the first server. During the migration process, security measures such as data compression and encryption need to be considered to ensure the security and integrity of the data. After each batch of data is migrated, perform a verification operation to check whether the migrated data is complete and accurate, and whether the data on the first server is consistent with the original data on the second server within the specified time period.
[0050] Finally, when all batches of target data are successfully migrated and verified, the entire migration process is complete. At this point, the first server contains the same type of financial data as the second server in the order of import date, and subsequent data processing or analysis can be performed.
[0051] From the above, it can be concluded that this embodiment transfers financial data in batches based on the import date, effectively manages the data migration order, ensures the orderly migration of historical data, improves data consistency and availability, and at the same time reduces system pressure to ensure an efficient and stable migration process.
[0052] In one embodiment of the present disclosure, storing financial data in a temporary server includes: Add tag information to the financial data, determine access permission information of the financial data according to the tag information; store the financial data and the access permission information corresponding to the financial data in a temporary server.
[0053] In this embodiment, in order to ensure the security and compliance of financial data, before storing the financial data in the temporary server, the system first adds specific tag information to the financial data. The tag information may include but is not limited to the data owner, data type, sensitivity level, timestamp, etc., which together determine the access rights of the data.
[0054] Secondly, the system determines the detailed access permission information for each piece of financial data based on this tag information, such as which users or roles can read, edit, or delete this data.
[0055] Finally, the system stores the financial data and its corresponding access permission information as a whole on a temporary server. This not only facilitates centralized data management, but also enhances data access security, ensuring that only users with corresponding permissions can access specific financial data.
[0056] For example, suppose a company needs to store the financial report data for the quarter in a temporary server for subsequent analysis at the end of the quarter. First, the system will add tag information to these financial report data, such as "Financial Data-2023Q3-High Sensitivity-Finance Department Only". Based on this tag information, the system further determines the access rights, such as only senior managers and supervisors in the Finance Department can view, edit and export these data, while employees in other departments or positions can only have limited access or no access. After that, the system packages these financial report data and their access rights information and uploads them together to the company's temporary server.
[0057] It can be concluded from the above that this embodiment achieves secure fine-grained control of financial data by adding tag information to financial data and determining access rights. Storing financial data and its access rights together in a temporary server not only facilitates centralized management, but also enhances the security of data access, effectively prevents unauthorized access, and ensures the confidentiality and integrity of financial data.
[0058] In one embodiment of the present disclosure, the financial information management method further includes: In response to the data volume of the financial data stored in the first server being greater than a preset data volume, determining a first capacity of the first server that needs to be expanded according to the data volume stored in the first server and the number of accesses; Alternatively, in response to the data volume of the financial data stored in the second server being greater than a preset data volume, the second capacity of the second server that needs to be expanded is determined according to the data volume stored in the second server and the number of accesses.
[0059] In this embodiment, when the amount of financial data stored in the first server exceeds a preset data volume threshold (e.g., 80%), the system starts to evaluate whether capacity expansion is required. If capacity expansion is required, the system can calculate the first capacity that needs to be expanded for the first server or the second capacity that needs to be expanded for the second server based on the amount of data stored in the server and the number of visits to the server. This capacity can not only meet the storage needs in the current and future period of time, but also avoid unnecessary waste of resources.
[0060] The expansion method in this embodiment is highly flexible and scalable. With the development of business and the growth of data, the expansion method can provide continuous support and expansion capabilities for the financial information management system, ensuring that it can adapt to the ever-changing business needs. It can be concluded from the above that the expansion of the first server and the second server in this embodiment is not a simple linear superposition (expanding as much capacity as required), but a nonlinear expansion based on the amount of data stored in the server and the number of accesses. This nonlinear expansion strategy effectively balances storage requirements and resource utilization, improves system response speed and stability, and avoids resource waste.
[0061] In one embodiment of the present disclosure, the expansion capacity of the first server or the second server may be calculated using a first formula.
[0062] The first formula includes:
[0063] in, is the capacity to be expanded, C is the storage capacity of the current server, and D is the amount of data stored in the current server. is the scaling factor for the amount of data exceeding the current capacity, is the ideal ratio of data volume to capacity, F is the number of visits to the current server, is the average number of visits, is the factor affecting the expansion demand due to the number of accesses, R is the data growth rate, The growth rate affects the demand for expansion. G is the expected business growth. It is the factor that affects the demand for capacity expansion due to business growth.
[0064] In this embodiment, the current server may be the first server or the second server. is the ideal ratio of data volume to capacity, which is used to determine when to consider capacity expansion, R can be a periodic growth rate or a compound growth rate, and G reflects the direct impact of business expansion on storage demand. The first formula provided in this embodiment takes into account the proportion of data volume exceeding the current capacity, the abnormal increase in the number of accesses, the growth rate of data, and the impact of expected business growth on the server storage capacity. By adjusting the factors λ, μ, ν, and γ, the capacity expansion requirements in different situations can be more accurately reflected.
[0065] Corresponding to the financial information management method of the above embodiment, Figure 2 This is a structural block diagram of a financial information management device provided by an embodiment of the present disclosure. For ease of explanation, only the parts related to the embodiment of the present disclosure are shown. Figure 2 The financial information management device 20 includes: a receiving module 21, a first judgment module 22 and a second judgment module 23.
[0066] The receiving module 21 is used to store the financial data in a temporary server in response to receiving the financial data; A first judgment module 22 is configured to transfer the financial data from the temporary server to the first server if the data type of the financial data in the temporary server is the first data type, or the number of times the target user accesses the financial data within the first period is greater than a first threshold; The second judgment module 23 is used to transfer the financial data from the temporary server to the second server if the data type of the financial data in the temporary server is the second data type, or the number of times the target user accesses the financial data within the first time period is less than or equal to the first threshold; and the response rate of the first server is greater than the response rate of the second server.
[0067] In one embodiment of the present disclosure, the financial information management device 20 further includes a third judgment module; The third judgment module is used to transfer data with the same data type as the financial data in the second server to the first server in response to the number of times the financial data in the second server is accessed within a second time period being greater than a second threshold; the second time period is greater than the first time period.
[0068] In one embodiment of the present disclosure, the third judgment module is specifically used to: The data of the same data type as the financial data in the second server are all transferred to the first server at one time, or the data of the same data type as the financial data in the second server are transferred to the first server in batches.
[0069] In one embodiment of the present disclosure, the third judgment module is specifically used to: The data in the second server having the same data type as the financial data is marked as target data, and the target data is transferred to the first server in batches based on the data volume of the target data.
[0070] In one embodiment of the present disclosure, the third judgment module is specifically used to: The data in the second server having the same data type as the financial data is marked as target data, and the target data is transferred to the first server in batches based on the import date of the target data.
[0071] In one embodiment of the present disclosure, the receiving module 21 is specifically used for: Add tag information to the financial data, determine access permission information of the financial data according to the tag information; store the financial data and the access permission information corresponding to the financial data in a temporary server.
[0072] In one embodiment of the present disclosure, the financial information management device 20 further includes an expansion module; An expansion module, configured to determine a first capacity of the first server that needs to be expanded according to the amount of data stored in the first server and the number of accesses in response to the amount of financial data stored in the first server being greater than a preset amount of data; Alternatively, in response to the data volume of the financial data stored in the second server being greater than a preset data volume, the second capacity of the second server that needs to be expanded is determined according to the data volume stored in the second server and the number of accesses.
[0073] The present disclosure also provides a financial information management system, which includes an electronic device. Figure 3 , Figure 3 A schematic block diagram of an electronic device provided by an embodiment of the present disclosure. Figure 3The electronic device 300 in the embodiment shown may include: one or more processors 301, one or more input devices 302, one or more output devices 303 and one or more memories 304. The processors 301, input devices 302, output devices 303 and memories 304 communicate with each other via a communication bus 305. The memory 304 is used to store computer programs, which include program instructions. The processor 301 is used to execute the program instructions stored in the memory 304. The processor 301 is configured to call the program instructions to execute the functions of each module / unit in the above-mentioned device embodiments, such as Figure 2 The functions of modules 21 to 23 are shown.
[0074] It should be understood that in the embodiment of the present disclosure, the processor 301 may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
[0075] The input device 302 may include a touch panel, a fingerprint collection sensor (for collecting the user's fingerprint information and fingerprint direction information), a microphone, etc., and the output device 303 may include a display (LCD, etc.), a speaker, etc.
[0076] The memory 304 may include a read-only memory and a random access memory, and provide instructions and data to the processor 301. A portion of the memory 304 may also include a non-volatile random access memory. For example, the memory 304 may also store information about the device type.
[0077] In a specific implementation, the processor 301, input device 302, and output device 303 described in the embodiments of the present disclosure can execute the implementation methods described in the first and second embodiments of the financial information management method provided in the embodiments of the present disclosure, and can also execute the implementation methods of the electronic device described in the embodiments of the present disclosure, which will not be repeated here.
[0078] In another embodiment of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by the processor, all or part of the processes in the above-mentioned embodiment method are implemented, and the computer program can also be completed by instructing the relevant hardware through the computer program. The computer program can be stored in a computer-readable storage medium, and when the computer program is executed by the processor, the steps of each of the above-mentioned method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form, etc. The computer-readable medium can include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium, etc.
[0079] The computer-readable storage medium may be an internal storage unit of the electronic device of any of the aforementioned embodiments, such as a hard disk or memory of the electronic device. The computer-readable storage medium may also be an external storage device of the electronic device, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device. Furthermore, the computer-readable storage medium may also include both an internal storage unit of the electronic device and an external storage device. The computer-readable storage medium is used to store computer programs and other programs and data required by the electronic device. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.
[0080] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this disclosure.
[0081] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the electronic devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0082] In the several embodiments provided in the present application, it should be understood that the disclosed electronic devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces or units, or it can be an electrical, mechanical or other form of connection.
[0083] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present disclosure.
[0084] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0085] The above are only specific embodiments of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present disclosure, and these modifications or replacements should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.
Claims
1. A financial information management method, characterized in that: include: In response to receiving the financial data, storing the financial data in a temporary server; If the data type of the financial data in the temporary server is the first data type, or the number of times the target user accesses the financial data within the first period is greater than a first threshold, transferring the financial data from the temporary server to the first server; If the data type of the financial data in the temporary server is the second data type, or the number of times the target user accesses the financial data within the first period is less than or equal to the first threshold, transferring the financial data from the temporary server to the second server; The response rate of the first server is greater than the response rate of the second server.
2. The financial information management method according to claim 1, characterized in that: Also includes: In response to the number of times the financial data in the second server is accessed within a second time period being greater than a second threshold, data of the same data type as the financial data in the second server is transferred to the first server; the second time period is greater than the first time period.
3. The financial information management method according to claim 2, characterized in that: The transferring the data having the same data type as the financial data in the second server to the first server includes: The data of the same data type as the financial data in the second server are all transferred to the first server at one time, or the data of the same data type as the financial data in the second server are transferred to the first server in batches.
4. The financial information management method according to claim 3, characterized in that: The transferring the data of the same data type as the financial data in the second server to the first server in batches includes: The data in the second server having the same data type as the financial data is marked as target data, and the target data is transferred to the first server in batches based on the data volume of the target data.
5. The financial information management method according to claim 3, characterized in that: The transferring the data of the same data type as the financial data in the second server to the first server in batches includes: The data in the second server having the same data type as the financial data is marked as target data, and the target data is transferred to the first server in batches based on the import date of the target data.
6. The financial information management method according to claim 1, characterized in that: The storing of the financial data into a temporary server comprises: Adding marking information to the financial data, determining access permission information of the financial data according to the marking information; and storing the financial data and the access permission information corresponding to the financial data in a temporary server.
7. The financial information management method according to claim 1, characterized in that: Also includes: In response to the data volume of the financial data stored in the first server being greater than a preset data volume, determining a first capacity of the first server that needs to be expanded according to the data volume stored in the first server and the number of accesses; Alternatively, in response to the data volume of the financial data stored in the second server being greater than a preset data volume, the second capacity of the second server that needs to be expanded is determined according to the data volume stored in the second server and the number of accesses.
8. A financial information management device, characterized in that: include: A receiving module, configured to store the financial data in a temporary server in response to receiving the financial data; A first judgment module is used to transfer the financial data from the temporary server to the first server if the data type of the financial data in the temporary server is the first data type, or the number of times the target user accesses the financial data within a first period of time is greater than a first threshold; The second judgment module is used to transfer the financial data from the temporary server to the second server if the data type of the financial data in the temporary server is the second data type, or the number of times the target user accesses the financial data within a first period of time is less than or equal to a first threshold; and the response rate of the first server is greater than the response rate of the second server.
9. A financial information management system, comprising an electronic device, the electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
