Data storage method, computer device, and computer-readable storage medium

Abstract

The present application relates to a data storage method, computer device, and computer-readable storage medium. The method includes: providing multiple physically isolated storage areas to store data for multiple cases; dividing the multiple cases into a first case group and a second case group based on their respective priorities, wherein the priority of any case in the first case group is not lower than the priority of any case in the second case group; storing the cases of the first case group in a first storage area subset of the multiple storage areas and storing the cases of the second case group in a second storage area subset of the multiple storage areas during initial allocation; and selectively changing the distribution of the multiple cases between the first storage area subset and the second storage area subset after initial allocation through data transfer or storage pointers based on association information of a change request, wherein the association information of the change request is additional information relative to the content of the change request. This improves storage efficiency.

Description

Technical Field

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

[0002] Credit approval refers to the evaluation of credit requests from applicants of the same or similar nature based on risk policies, credit policies, approval policies, etc., and the provision of a series of financial credit services, such as credit inquiries and anti-fraud risk warnings. With the development of the domestic financial industry and the increase in investment in high-tech industries, enterprises, individuals and institutions are increasingly relying on financial credit services to obtain funds for operations and research and development, and therefore place higher demands on the credit approval services of financial institutions. On the one hand, for the purpose of data security and privacy protection, the execution resources of different cases related to credit approval should meet security isolation requirements. On the other hand, for the sake of overall operational efficiency, cases with higher priority should be given priority. The data storage technology in existing technologies is difficult to meet the above requirements.

[0003] To this end, the present application provides a data storage method, a computer device, and a computer-readable storage medium. Summary of the Invention

[0004] The embodiments of the present application provide a data storage method, a computer device, and a computer-readable storage medium to solve the problems existing in the prior art.

[0005] In a first aspect, the present application provides a data storage method. The data storage method includes: providing multiple storage areas to store data of multiple cases, wherein the multiple storage areas are physically isolated from each other; dividing the multiple cases into a first case group and a second case group according to their respective priorities, wherein the priority of any case in the first case group is not lower than the priority of any case in the second case group; storing the cases of the first case group in a first storage area subset of the multiple storage areas and storing the cases of the second case group in a second storage area subset of the multiple storage areas during initial allocation; and selectively changing the distribution of the multiple cases between the first storage area subset and the second storage area subset after initial allocation through data transfer or storage pointers according to association information of a change request, wherein the association information of the change request is additional information relative to the content of the change request.

[0006] In a possible implementation of the first aspect of the present application, the associated information of the change request includes at least one of the following: the scenario of the change request, the predictability of the change request, and the source of the change request.

[0007] In a possible implementation of the first aspect of the present application, the associated information of the change request includes the predictability of the change request, and when the predictability of the change request is higher than a first threshold, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by data transfer; and when the predictability of the change request is lower than a second threshold, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by storage pointers.

[0008] In a possible implementation of the first aspect of the present application, the associated information of the change request includes the scenario of the change request, and the scenario of the change request includes industry, geographical location, and cultural characteristics.

[0009] In a possible implementation of the first aspect of the present application, the associated information of the change request includes the source of the change request. When the source of the change request is a regulatory agency or a customer, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed through data transfer; and when the source of the change request is an emergency response unit, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed through storage pointers.

[0010] In a possible implementation of the first aspect of the present application, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by data movement, including: re-dividing the respective storage areas of the first storage area subset and the second storage area subset, or moving data at the physical level according to the content of the change request.

[0011] In a possible implementation of the first aspect of the present application, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed through storage pointers, including: changing the storage pointer of the storage area associated with the content of the change request according to the content of the change request or redefining the storage pointer.

[0012] In a possible implementation of the first aspect of the present application, after the storage pointer is changed or the storage pointer is redefined, the storage area directed by the changed storage pointer or the redefined storage pointer is set as imported.

[0013] In a second aspect, an embodiment of the present application further provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements a method according to any one of the implementation methods of any of the above aspects when executing the computer program.

[0014] In a third aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer device, the computer device executes a method according to any one of the implementation methods of any of the above aspects.

[0015] In a fourth aspect, an embodiment of the present application further provides a computer program product, characterized in that the computer program product includes instructions stored on a computer-readable storage medium, and when the instructions are executed on a computer device, the computer device executes a method according to any one of the implementation methods of any of the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0017] Figure 1 A schematic diagram of an approval system provided in an embodiment of the present application;

[0018] Figure 2 A schematic diagram of a data storage device provided in an embodiment of the present application;

[0019] Figure 3 A flowchart of a data storage method provided in an embodiment of the present application;

[0020] Figure 4 A schematic diagram of the structure of a computing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] The embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

[0022] The embodiments of the present application provide a data storage method, a computer device, and a computer-readable storage medium for solving problems existing in the prior art. The methods and devices provided in the embodiments of the present application are based on the same inventive concept. Since the methods and devices solve problems based on similar principles, the embodiments, implementations, examples, or implementations of the methods and devices may refer to each other, and any repetitions will not be repeated.

[0023] It should be understood that, in the description of this application, "at least one" means one or more, and "a plurality" means two or more. In addition, unless otherwise specified, the terms "first" and "second" are used only for descriptive purposes and are not to be construed as indicating or implying relative importance or order.

[0024] Figure 1 This is a schematic diagram of an approval system provided in an embodiment of the present application. Figure 1 As shown, approval system 104 is connected to user interface 102, which is used to obtain user credit requests, such as applications for mortgages, business loans, and export acceptance guarantees. User interface 102 can be a computer, server, or host computer located in a fixed location, such as a work computer at a bank branch, or a user terminal, such as a self-service bank terminal, or a program, code, or user interface running on a portable computer or smart terminal. User interface 102 obtains user credit requests, which may include necessary contracts, agreements, and user identification information. User interface 102 transmits the obtained credit requests and related information to approval system 104. Approval system 104 is also communicatively connected to a business system set 106. Business system set 106 includes one or more business systems that provide financial services, such as loan systems, joint loan transaction systems, risk control systems, manual operation platforms, and any other possible financial service platforms. Approval system 104 provides the credit requests and related information obtained from user interface 102 to the corresponding business system for execution. For example, when the credit request obtained by the user interface 102 is for a loan application, the approval system 104 can be connected to the loan system in the business system set 106 and perform operations such as querying loan amounts and opening accounts; for another example, when the credit request obtained by the user interface 102 is for a joint loan transaction, the approval system 104 can be connected to the joint loan transaction system in the business system set 106 and perform operations such as joint approval; for another example, when the credit request obtained by the user interface 102 is for risk control, the approval system 104 can be connected to the risk control system in the business system set 106 and perform operations such as risk control assessment and risk control events; for another example, when the credit request obtained by the user interface 102 is suitable for manual approval, such as a pilot project, the approval system 104 can be connected to the manual operation platform in the business system set 106 and perform operations such as manual approval.

[0025] Please continue reading Figure 1The approval system 104 is also communicatively connected to an auxiliary system 108, which is used to collaborate with the business system set 106. The auxiliary system 108 may include a cooperative payment transaction system, an application front desk, a business operation management system, or other auxiliary or additional function-providing systems, thereby providing the approval system 104 with auxiliary functions such as risk policy configuration, customer product strategy configuration, and operation strategy configuration, thereby better executing the approval process. The approval system 104 is also communicatively connected to the approval result output interface 110 and sends the approval result to the approval result output interface 110. The approval result output interface 110 can be displayed to the user externally or connected to other internal systems for subsequent process processing. It should be understood that the approval system 104 can obtain relevant information about the credit request from external systems and platforms, such as obtaining the user's personal integrity report and confirming whether the user is on the whitelist or blacklist. These can be achieved through the user interface 102 or through additional interfaces.

[0026] Please continue reading Figure 1 The approval system 104 is typically connected to multiple user interfaces. Institutions responsible for credit approval typically use a centralized credit approval system to aggregate and process credit requests received from numerous user interfaces. For example, a financial institution may aggregate various types of credit requests from its branches, outlets, and business halls into its central server or data center for unified processing. This centralized storage and processing approach also facilitates security oversight, reduces energy consumption, and improves resource utilization. However, centralized storage and processing also require the central server housing the approval system to handle a massive volume of credit requests, potentially interfacing with a large number of various business systems, and the associated interactive data, communication data, and message data. Data storage requires efficient and high storage efficiency. To this end, cases of the same priority level are preferably stored in the same or adjacent storage areas to improve data access efficiency. Furthermore, cases of different priorities should be stored in different storage areas, with security isolation mechanisms implemented between these storage areas. This satisfies the performance requirements of physically isolating resources used to execute case processes. Furthermore, storage resources related to case process execution can be physically isolated. However, the priority of cases may change, such as changes in priority standards, policies, models, and scenario requirements. The resulting changes in case priorities need to be reflected in the division and adjustment of storage areas. Figure 2 The improvements in data storage in the embodiments of the present application are described in detail.

[0027] Figure 2 This is a schematic diagram of a data storage provided in an embodiment of the present application. Figure 2As shown, the case manager 202 is connected to the data storage 204. The case manager 202 is used to manage pending cases and send data and storage operation instructions to the data storage 204. The data storage 204 is used to store data related to pending cases and execute storage operation instructions. The case manager 202 can be deployed in Figure 1 In the approval system 104 shown, or as an external device connected to the approval system 104, data storage 204 is used to store approval data obtained by the approval system 104 from various user interfaces and business systems, such as reference information for user credit requests. As mentioned above, a centralized credit approval system aggregates and processes credit requests imported from numerous user interfaces, potentially interfacing with numerous business systems, and related interaction data, communication data, and message data. Therefore, data storage requires efficient and effective storage. Figure 2 The data storage 204 in the system includes multiple storage areas, each of which is divided into multiple storage area subsets. Cases of the same priority level are preferably stored in the same or adjacent storage areas, thereby improving data access efficiency. Furthermore, cases of different priorities are preferably stored in different storage areas, and security isolation mechanisms can be implemented between different storage areas. This satisfies the performance requirement of "physically isolating resources for case process execution."

[0028] Specifically, Figure 2 The data storage 204 shown provides multiple storage areas for storing data for multiple cases, wherein the multiple storage areas are physically isolated from each other. The case manager 202 divides the multiple cases into a first case group and a second case group based on their respective priorities, wherein the priority of any case in the first case group is not lower than the priority of any case in the second case group. During initial allocation, the data storage 204 stores the cases of the first case group in a first storage area subset 210 of the multiple storage areas and stores the cases of the second case group in a second storage area subset 220 of the multiple storage areas. Figure 2 In the example, the first storage area subset 210 includes storage area 212, storage area 214, and storage area 216; the second storage area subset 220 includes storage area 222, storage area 224, and storage area 226. It should be understood that the data storage 204 and the data storage method provided in the embodiments of the present application can be applied to any number of storage areas and storage area subsets divided in any manner, or a storage area subset can include any number of storage areas.

[0029] Continue reading Figure 2By dividing the multiple storage areas in the data storage 204 into multiple storage area subsets, each storage area is physically isolated from each other, and thus each storage area subset is also physically isolated from each other. Furthermore, the storage areas within the same storage area subset are distributed in adjacent locations, such as adjacent physical storage spaces or consecutive physical storage addresses. This facilitates the rapid completion of data storage operations assigned to the storage area subset. Furthermore, by requiring the data storage 204 to store cases of the first case group in the first storage area subset 210 of the multiple storage areas and the second case group in the second storage area subset 220 of the multiple storage areas during initial allocation, and requiring that the priority of any case in the first case group be no lower than the priority of any case in the second case group, cases with similar priorities are stored in the same storage area subset, that is, cases of different priorities are stored in different storage areas as much as possible, thereby utilizing the physical isolation of the multiple storage areas to provide physical isolation between different cases. Furthermore, the first storage area subset 210 used to store cases in the first case group can have higher data security measures than the second storage area subset 220 used to store cases in the second case group, such as more advanced access password restrictions, more difficult-to-crack encryption algorithms, or kernel-security-level access restrictions. This helps provide more reliable security for high-priority cases and better meets the performance requirement of "physically isolating resources for case process execution."

[0030] Continue reading Figure 2In practice, case priorities may change, for example, due to changes in priority standards, policies, models, and scenario requirements. These changes in case priorities need to be reflected in the division and adjustment of storage areas. As described above, the first storage area subset and the second storage area subset are physically isolated from each other. In some embodiments, the first storage area subset and the second storage area subset each utilize different access restriction mechanisms, encryption mechanisms, and data storage structures, or the first storage area subset utilizes kernel security-level access restrictions while the second storage area subset does not. When a case's priority changes, causing it to be assigned to one case group and then to another, the storage area subset corresponding to the case's data may also change, from one storage area subset to another. Considering that data storage 204 and related approval systems in practice handle massive amounts of data, that is, they need to store and process data related to a large number of pending cases, the changes in priority of these numerous cases after initial assignment are complex and variable. In some cases, changes in regulatory policies, industry trends, or laws and regulations can cause a large number of cases to shift in priority. For example, a change in regulatory regulations could cause a case previously identified as high-risk (which would have been prioritized) to be designated low-risk (which would have been prioritized). Such changes are considered to be regular or predictable. In other cases, sudden events or accidents can also cause case priorities to shift, but such changes are considered unpredictable.

[0031] to this end, Figure 2 The data storage device selectively changes the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation through data transfer or storage pointers according to the associated information of the change request, wherein the associated information of the change request is additional information relative to the content of the change request. In this way, high storage efficiency is provided at the data storage level, and the demand for different execution resources for cases of different priorities can be flexibly responded to. This point is combined with Figure 3 Detailed description.

[0032] It should be understood that Figure 3 The storage area subsets shown are only exemplary. The embodiments of the present application may include any number of storage area subsets, and each storage area subset may include any number of storage areas. The case manager may also divide the pending cases into any number of case groups, and each case group may include any number of cases.

[0033] Figure 3A flow chart of a data storage method provided in an embodiment of the present application. Figure 3 As shown, the data method includes the following steps.

[0034] Step S302: providing multiple storage areas to store data of multiple cases.

[0035] Step S304: Divide the multiple cases into a first case group and a second case group according to their respective priorities.

[0036] Step S306: During initial allocation, the cases of the first case group are stored in a first storage area subset of the plurality of storage areas, and the cases of the second case group are stored in a second storage area subset of the plurality of storage areas.

[0037] Step S308: According to the association information of the change request, selectively change the distribution of the plurality of cases between the first storage area subset and the second storage area subset after the initial allocation through data movement or storage pointers.

[0038] The plurality of storage areas are physically isolated from one another. The priority of any case in the first case group is not lower than the priority of any case in the second case group. The associated information of the change request is additional information relative to the content of the change request.

[0039] As mentioned above, the reasons for changes in priority after the initial assignment are complex and varied. In some cases, changes in regulatory policies, industry trends, or laws and regulations may cause the priority of a large number of cases to change. For example, changes in regulatory regulations may cause cases that were originally identified as high-risk activities (high-risk cases may be handled first as high-priority cases) to now be identified as low-risk activities (low-risk cases may be handled as low-priority cases). Such changes are considered to have a certain regularity or are predictable. In some cases, the priority of a case may also change due to emergencies, accidents, etc., and such changes are considered difficult to predict. Therefore, a change request represents the relevant instructions, applications, requests, or orders for changing the priority of the case and the related storage area. By considering the associated information of the change request rather than the associated request itself or its own content, it is helpful to selectively reflect the impact of the change request on the storage area through data movement or storage pointers.

[0040] Specifically, based on the associated information of the change request, the distribution of the multiple cases between the first storage area subset and the second storage area subset after initial allocation is selectively changed through data movement or storage pointers. Here, data movement means moving the actual physical data, while storage pointers means simply changing the pointer direction without moving the actual physical data. For changes that have a certain regularity or can be predicted, it is appropriate to reflect the impact of these changes through data movement, while for sudden and unpredictable changes, it is appropriate to reflect the impact of these changes through storage pointers. In other words, data movement or pointer changes are selectively adopted based on the associated information of the change request, rather than the change request itself. Associated information is auxiliary information that is different from the request itself but is associated with the request, such as how the change request was generated, whether it is a type that is easy to predict or a type that is difficult to predict, etc. In this way, the impact of change requests on process operations can be minimized, especially the interference caused by unpredictable changes, while taking into account predictable and regular change requests.

[0041] In one possible implementation, the associated information of the change request includes at least one of the following: the scenario of the change request, the predictability of the change request, and the source of the change request. As described above, the content of the change request itself is different from the associated information of the change request. It is difficult to determine whether the change request is regular or predictable based solely on the content of the change request itself. By referring to the associated information of the change request, such as the scenario of the change request, the predictability of the change request, and the source of the change request, it is possible to better choose whether to use data transfer or storage pointer to respond to the change request.

[0042] In one possible embodiment, the associated information of the change request includes the predictability of the change request. When the predictability of the change request is higher than a first threshold, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by data transfer. When the predictability of the change request is lower than a second threshold, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by storage pointers. Here, predictability can be a quantitative indicator, such as a probability value predicted by a machine learning model or a value calculated by a probability estimation function. By comparing the predictability with the first threshold and the second threshold, it is selected whether to use data transfer or storage pointers to respond to the change request.

[0043] In one possible implementation, the associated information of the change request includes the scenario of the change request, which includes industry, geographic location, and cultural characteristics. Here, the scenario of the change request can be understood as background information related to the change request, such as the industry and geographic location associated with the case related to the change request, as well as cultural characteristics such as population distribution. These factors are used to better assess whether the change request is regular or predictable, so as to respond to the change request by using data transfer or storage pointers.

[0044] In one possible embodiment, the associated information of the change request includes the source of the change request, and when the source of the change request is a regulatory agency or a customer, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by data transfer, and when the source of the change request is an emergency response unit, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by storage pointers. Here, when the source of the change request is, for example, a regulatory agency or a user of a credit system, such a source of change is considered to be predictable and routine, and in some embodiments may be pre-arranged. When the source of the change request is an emergency response unit, such as an agency that responds to emergencies or sudden crises, the change request from such a source is considered to be sudden and difficult to predict.

[0045] In one possible implementation, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by data movement, including: re-dividing the storage areas of the first storage area subset and the second storage area subset, or moving data at the physical level according to the content of the change request. Here, re-dividing the storage areas means re-dividing the storage areas under each storage area subset. Because the storage area subsets are physically isolated, the storage areas of each re-divided storage area subset are also physically isolated. On the other hand, data can be moved directly at the physical level, and the data can be moved from one storage area to another according to the content of the change request.

[0046] In one possible implementation, changing the distribution of the plurality of cases between the first storage area subset and the second storage area subset after initial allocation via storage pointers includes: changing a storage pointer of a storage area associated with the change request or redefining the storage pointer based on the change request. Here, changing the distribution of the plurality of cases between the first storage area subset and the second storage area subset after initial allocation via storage pointers may be achieved by directly modifying the original storage pointer to change its direction or redefining the storage pointer.

[0047] In one possible implementation, after the storage pointer is changed or redefined, the storage area pointed to by the changed or redefined storage pointer is set to imported. Here, when the distribution of the multiple cases between the first storage area subset and the second storage area subset after initial allocation is changed using storage pointers, since only the pointer direction is changed and no actual data is moved, the storage area pointed to by the changed or redefined storage pointer is set to imported to prevent misoperation.

[0048] See also Figure 4 , Figure 4 4 is a structural diagram of a computing device provided in an embodiment of the present application, wherein the computing device 400 includes: one or more processors 410, a communication interface 420, and a memory 430. The processor 410, the communication interface 420, and the memory 430 are interconnected via a bus 440. Optionally, the computing device 400 may further include an input / output interface 450, the input / output interface 450 being connected to an input / output device for receiving parameters set by a user, etc. The computing device 400 can be used to implement some or all of the functions of the device embodiment or the system embodiment in the above-mentioned embodiment of the present application; the processor 410 can also be used to implement some or all of the operating steps of the method embodiment in the above-mentioned embodiment of the present application. For example, the specific implementation of the various operations performed by the computing device 400 can refer to the specific details in the above-mentioned embodiments, such as the processor 410 is used to perform some or all of the steps in the above-mentioned method embodiment or some or all of the operations in the above-mentioned method embodiment. For another example, in an embodiment of the present application, the computing device 400 may be used to implement part or all of the functions of one or more components in the above-mentioned apparatus embodiment. In addition, the communication interface 420 may be specifically used to perform the communication functions necessary to implement the functions of these apparatuses and components, and the processor 410 may be specifically used to perform the processing functions necessary to implement the functions of these apparatuses and components.

[0049] It should be understood that Figure 4The computing device 400 may include one or more processors 410, and the multiple processors 410 may be connected in parallel, serially, serially, or in parallel with each other, or in any other manner to collaboratively provide processing capabilities. Alternatively, the multiple processors 410 may form a processor sequence or a processor array, or the multiple processors 410 may be divided into a main processor and an auxiliary processor, or the multiple processors 410 may have different architectures, such as a heterogeneous computing architecture. In addition, Figure 4 The computing device 400 shown, and the related structural and functional descriptions are exemplary and non-limiting. In some exemplary embodiments, the computing device 400 may include Figure 4 More or fewer components may be shown, some components may be combined, some components may be separated, or there may be a different arrangement of components.

[0050] The processor 410 can have a variety of specific implementation forms. For example, the processor 410 can include a central processing unit (CPU), a graphics processing unit (GPU), a neural-network processing unit (NPU), a tensor processing unit (TPU) or a data processing unit (DPU), etc., and the embodiments of the present application are not specifically limited. The processor 410 can also be a single-core processor or a multi-core processor. The processor 410 can be a combination of a CPU and a hardware chip. The above-mentioned hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general-purpose array logic (GAL) or any combination thereof. The processor 410 may also be implemented solely using a logic device with built-in processing logic, such as an FPGA or a digital signal processor (DSP). The communication interface 420 may be a wired interface or a wireless interface for communicating with other modules or devices. The wired interface may be an Ethernet interface, a local interconnect network (LIN), etc., and the wireless interface may be a cellular network interface or a wireless local area network interface.

[0051] The memory 430 may be a non-volatile memory, such as a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The memory 430 may also be a volatile memory, such as a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). The memory 430 can also be used to store program code and data, so that the processor 410 can call the program code stored in the memory 430 to perform some or all of the operating steps in the above-mentioned method embodiments, or perform the corresponding functions in the above-mentioned device embodiments. In addition, the computing device 400 may include a plurality of memory modules, such as a plurality of memory modules, and a plurality of memory modules. Figure 4 Show more or fewer components, or configure components differently.

[0052] The bus 440 may be a peripheral component interconnect express (PCIe) bus, an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The bus 440 may be divided into an address bus, a data bus, a control bus, etc. In addition to the data bus, the bus 440 may also include a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0053] The embodiment of the present application also provides a system, which includes multiple computing devices, and the structure of each computing device can refer to the structure of the above-mentioned computing device. The functions or operations that can be implemented by the system can refer to the specific implementation steps in the above-mentioned method embodiment and / or the specific functions described in the above-mentioned device embodiment, and will not be repeated here. The embodiment of the present application also provides a computer-readable storage medium, in which computer instructions are stored, and when the computer instructions are run on a computer device (such as one or more processors), the method steps in the above-mentioned method embodiment can be implemented. The processor of the computer-readable storage medium can refer to the specific operations described in the above-mentioned method embodiment and / or the specific functions described in the above-mentioned device embodiment when executing the specific implementation of the above-mentioned method steps, and will not be repeated here. The embodiment of the present application also provides a computer program product, which includes instructions stored on a computer-readable storage medium, and when the instructions are run on a computer device, the computer device executes the method steps in the above-mentioned method embodiment.

[0054] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. The present application may take the form of a fully hardware embodiment, a fully software embodiment, or an embodiment combining software and hardware. The embodiments of the present application may be implemented in whole or in part through software, hardware, firmware, or any other combination. When implemented using software, the above embodiments may be implemented in whole or in part as a computer program product. The present application may take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. Computer-readable storage media can be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that contains a collection of one or more available media. Available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media, or semiconductor media. Semiconductor media can be solid-state drives, random access memory, flash memory, read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, or any other suitable storage medium.

[0055] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. Each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including the instruction device, which implements the function specified in the process. Figure 1a process or multiple processes and / or boxes Figure 1 These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0056] In the above embodiments, the descriptions of each embodiment have different emphases. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. The steps in the method of the embodiment of the present application can be adjusted in sequence, merged or deleted according to actual needs; the modules in the system of the embodiment of the present application can be divided, merged or deleted according to actual needs. If these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims

1. A data storage method, characterized in that: The data storage method includes: providing a plurality of storage areas for storing data of respective cases, wherein the plurality of storage areas are physically isolated from each other; dividing the plurality of cases into a first case group and a second case group according to respective priorities of the plurality of cases, wherein the priority of any case in the first case group is not lower than the priority of any case in the second case group; storing the cases of the first case group in a first subset of the plurality of storage areas and storing the cases of the second case group in a second subset of the plurality of storage areas during initial allocation; selectively changing the distribution of the plurality of cases between the first storage area subset and the second storage area subset after initial allocation by data movement or storage pointers based on association information of the change request, wherein the association information of the change request is additional information relative to the content of the change request; The associated information of the change request includes at least one of the following: the scenario of the change request, the predictability of the change request, and the source of the change request. The associated information of the change request includes the predictability of the change request. When the predictability of the change request is higher than a first threshold, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by data movement; and when the predictability of the change request is lower than a second threshold, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed by storage pointers.

2. The data storage method according to claim 1, wherein: The associated information of the change request includes the scenario of the change request, and the scenario of the change request includes industry, geographical location, and human characteristics.

3. The data storage method according to claim 1, wherein: The associated information of the change request includes the source of the change request. When the source of the change request is a regulatory agency or a customer, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed through data transfer. When the source of the change request is an emergency response unit, the distribution of the multiple cases between the first storage area subset and the second storage area subset after the initial allocation is changed through storage pointers.

4. The data storage method according to any one of claims 1 to 3, characterized in that: Changing the distribution of the multiple cases between the first storage area subset and the second storage area subset after initial allocation through data movement includes: re-dividing the respective storage areas of the first storage area subset and the second storage area subset, or moving data at the physical level according to the content of the change request.

5. The data storage method according to claim 4, characterized in that: Changing the distribution of the multiple cases between the first storage area subset and the second storage area subset after initial allocation through storage pointers includes: changing the storage pointer of the storage area associated with the content of the change request or redefining the storage pointer according to the content of the change request.

6. The data storage method according to claim 5, characterized in that: After the storage pointer is changed or the storage pointer is redefined, the storage area pointed to by the changed storage pointer or the redefined storage pointer is set as imported.

7. A computer device, characterized in that: The computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the method according to any one of claims 1 to 6 is implemented. 8 . A computer-readable storage medium storing computer instructions, which, when executed on a computer device, cause the computer device to execute the method according to claim 1 .

Images