Image data scheduling method and device, electronic equipment and storage medium

Abstract

The application discloses an image data scheduling method and device, an electronic device and a storage medium, and relates to the technical field of medical data monitoring. The method comprises the following steps: in response to a first acquisition request for target image data, searching for the target image data from a local cache system; if the target image data is not searched for, sending a second acquisition request for the target image data to a central cache system corresponding to the local cache system; the second acquisition request is used for instructing to search for the target image data from the central cache system, and in the case that the target image data is not searched for from the central cache system, instructing the central cache system to send a third acquisition request for the target image data to a central index system; the third acquisition request is used for instructing the central index system to feed back the target image data, and the target image data is obtained from other central cache systems. The application can reduce the storage cost and resource waste of the storage space, and improve the data retrieval efficiency and user experience.

Description

Technical Field

[0001] This application relates to the field of medical data monitoring technology, and in particular to a method, apparatus, electronic device and storage medium for scheduling image data. Background Technology

[0002] Currently, medical imaging data exhibits five major characteristics: explosive growth, long-term storage, high-frequency access, cross-domain scheduling, and security compliance. The data volume of a single image ranges from tens of MB to several GB, requiring storage for decades or even longer. Inpatient images need to be stored for even longer, resulting in significant storage pressure and costs for systems or devices.

[0003] However, traditional medical institutions often use centralized storage for data storage, storing recent high-frequency access data and long-term low-frequency archived data on the same device. This results in a single storage architecture, leading to a large amount of idle data occupying high-performance, high-cost storage space and causing serious waste of resources. Furthermore, when accessing image data, the entire data is directly pulled from a single provincial central storage or even across provinces without caching or acceleration, resulting in slow data retrieval and loading, which seriously affects data retrieval efficiency and consequently impacts user experience. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and storage medium for scheduling image data. The embodiments provided by this application solve the technical problem that the existing storage architecture is simple, resulting in a large amount of idle data occupying high-performance and high-cost storage space, causing serious waste of resources, affecting data retrieval efficiency and user experience. The embodiments provided by this application can reduce storage costs and resource waste, and improve data retrieval efficiency and user experience.

[0005] In a first aspect, this application provides a method for scheduling image data, applied to a local caching system, the method comprising: In response to a first request to acquire target image data, the target image data is retrieved from the local cache system; If the target image data is not found in the local cache system, a second request for the target image data is sent to the central cache system corresponding to the local cache system. The second acquisition request is used to instruct the central cache system to retrieve the target image data, and if the target image data is not retrieved from the central cache system, to instruct the central cache system to send a third acquisition request for the target image data to the central index system; the third acquisition request is used to instruct the central index system to return the target image data, which is obtained from other central cache systems.

[0006] In one feasible implementation, the method further includes: If the target image data is retrieved from the local cache system, the target image data is sent to the target terminal through the cloud server corresponding to the local cache system.

[0007] In one feasible implementation, the method further includes: The system receives the retrieved target image data sent by the central caching system and forwards the target image data to the target terminal through the cloud server corresponding to the local caching system. The target image data retrieved by the central cache system can be either the target image data retrieved by the central cache system itself or the target image data retrieved by other central cache systems.

[0008] In one feasible implementation, the method further includes: The retrieved target image data sent by the central cache system is stored in the local cache system; wherein, one central cache system corresponds to multiple local cache systems.

[0009] In one feasible implementation, the method further includes: When the storage space utilization rate of the local cache system exceeds the preset storage space threshold, delete the historical image data that has not been accessed within the preset time period in the local cache system.

[0010] In one feasible implementation, forwarding the target image data to the target terminal via the cloud server corresponding to the local caching system includes: The target image data is parsed and rendered by the cloud server corresponding to the local caching system to determine the lightweight image corresponding to the target image data; The cloud server is used to segment the lightweight image to determine multiple image blocks; Each of the image blocks is forwarded to the target terminal through the cloud server corresponding to the local caching system; wherein the transmission time of the first image block is not greater than a preset response time.

[0011] In a second aspect, this application provides a method for scheduling image data, applied to a central cache system, wherein the central cache system corresponds to multiple local cache systems, and the method for scheduling image data includes: In response to a second retrieval request sent by any of the local caching systems, target image data is retrieved from the central caching system; wherein the second retrieval request is sent by the local caching system when the target image data is not retrieved from the local caching system. If the target image data is retrieved from the central cache system, the retrieved target image data is sent to the local cache system. If the target image data is not retrieved from the central cache system, a third retrieval request for the target image data is sent to the central index system. The system receives target image data obtained from other central caching systems as feedback from the central indexing system.

[0012] In one feasible implementation, the method further includes: The target image data fed back by the central indexing system is stored in the central cache system; wherein, the preset central indexing system corresponds to multiple central cache systems.

[0013] In one feasible implementation, the central cache system includes a first data storage layer, a second data storage layer, and a third data storage layer, wherein retrieving the target image data from the central cache system includes: Obtain the last historical access time of the target image data; When the last historical retrieval time is less than or equal to a first preset time threshold, the target image data is retrieved from the first data storage layer; When the last historical retrieval time is greater than the first preset time threshold and less than or equal to the second preset time threshold, the target image data is retrieved from the second data storage layer, wherein the second preset time threshold is greater than the first preset time threshold; When the last historical retrieval time is greater than the second preset time threshold, the target image data is retrieved from the third data storage layer.

[0014] In one feasible implementation, the method further includes: When the storage space utilization rate of the central cache system exceeds a preset storage space threshold, historical image data that has not been accessed within a preset time period in the central cache system is deleted.

[0015] In a third aspect, this application provides a local caching system, the local caching system comprising: The first retrieval module is used to retrieve the target image data from the local cache system in response to a first acquisition request for the target image data; The first sending module is configured to send a second acquisition request for the target image data to the central cache system corresponding to the local cache system if the target image data is not retrieved from the local cache system. The second acquisition request is used to instruct the central cache system to retrieve the target image data, and if the target image data is not retrieved from the central cache system, to instruct the central cache system to send a third acquisition request for the target image data to the central index system; the third acquisition request is used to instruct the central index system to return the target image data, which is obtained from other central cache systems.

[0016] In a fourth aspect, this application provides a central cache system, which corresponds to multiple local cache systems. The central cache system includes: The second retrieval module is configured to retrieve target image data from the central cache system in response to a second retrieval request sent by any of the local cache systems; wherein the second retrieval request is sent by the local cache system when the target image data is not retrieved from the local cache system. The second sending module is used to send the retrieved target image data to the local cache system if the target image data is retrieved from the central cache system. The third sending module is used to send a third acquisition request for the target image data to the central indexing system if the target image data is not retrieved from the central cache system. The receiving module is used to receive target image data obtained from other central caching systems, which is fed back by the central indexing system.

[0017] In a fifth aspect of this application, an electronic device is provided, including a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus, and the machine-readable instructions are executed by the processor to perform the steps of the image data scheduling method described above.

[0018] In a sixth aspect of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, performs the steps of the image data scheduling method described above.

[0019] Compared with the prior art, the image data scheduling method, apparatus, electronic device, and storage medium provided in this application respond to a first request for target image data and retrieve the target image data from a local cache system. If the target image data is not found in the local cache system, a second request for target image data is sent to the central cache system corresponding to the local cache system. The second request is used to instruct the retrieval of target image data from the central cache system. If the target image data is not found in the central cache system, the central cache system is instructed to send a third request for target image data to the central index system. The third request is used to instruct the central index system to return the target image data, which is obtained from other central cache systems. This application can reduce the storage cost of different levels of cache systems through distributed storage, and distributed storage can improve data retrieval and storage efficiency, thereby enhancing the user experience. Attached Figure Description

[0020] Figure 1 This paper illustrates one of the flowcharts of an image data scheduling method provided in an embodiment of this application; Figure 2 The second flowchart of an image data scheduling method provided in an embodiment of this application is shown; Figure 3 This paper illustrates a flowchart of the management process for the entire lifecycle of target image data in an image data scheduling method provided in an embodiment of this application. Figure 4 This paper shows a structural block diagram of a local caching system provided in an embodiment of this application; Figure 5 This paper shows a structural block diagram of a central caching system provided in an embodiment of the present application; Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown.

[0021] Figure 5 and Figure 6 The correspondence between the figure labels and figure titles in the accompanying drawings is as follows: 400 Local caching system; 410 First retrieval module; 420 First sending module; 430 Retrieval and sending module; 440 Forwarding module; 450 First storage module; 460 First deletion module; 500 Central caching system; 510 Second retrieval module; 520 Second sending module; 530 Third sending module; 540 Receiving module; 550 Second storage module; 560 Second deletion module; 600 Electronic device; 610 Processor; 620 Memory; 630 Bus. Detailed Implementation

[0022] To better understand the technical solutions provided in the embodiments of this specification, the technical solutions of the embodiments of this specification will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. In the absence of conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.

[0023] In this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, without necessarily requiring or implying any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element. The term "two or more" includes two or more cases.

[0024] First, the applicable application scenarios of this application will be introduced. The embodiments provided in this application are applicable to the field of medical data monitoring technology, and in particular relate to a method, device, electronic device and storage medium for scheduling image data.

[0025] Currently, traditional medical institutions mostly use centralized storage for data storage, storing recent high-frequency access data and long-term low-frequency archived data on the same device. This results in a single storage architecture, leading to a large amount of idle data occupying high-performance, high-cost storage space and causing serious waste of resources. Furthermore, when accessing image data, the entire data is directly pulled from a single provincial central storage or even across provinces without caching or acceleration, resulting in slow data retrieval and loading, which seriously affects data retrieval efficiency and consequently impacts user experience.

[0026] Based on this, the embodiments of this application provide a method, apparatus, electronic device and storage medium for scheduling image data. The embodiments provided by this application solve the technical problem that the single storage architecture in the prior art leads to a large amount of idle data occupying high-performance and high-cost storage space, resulting in serious waste of resources, affecting data retrieval efficiency and user experience. The embodiments provided by this application can reduce the storage cost and resource waste of storage space, and improve data retrieval efficiency and user experience.

[0027] It should be noted that the image data involved in this application (including but not limited to historical image data and target impact data) are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0028] Figure 1 This illustration shows one of the flowcharts of an image data scheduling method provided in an embodiment of this application. Figure 1 As shown, the image data scheduling method includes the following steps: S101. In response to the first request for acquiring target image data, retrieve the target image data from the local cache system.

[0029] In this step, according to the embodiments provided in this application, before scheduling or retrieving medical image data, the medical institution first deploys a local caching system, namely a cloud front-end server for medical images, and connects the aforementioned local caching system to the hospital information system (HIS), radiology information system (RIS), and picture archiving and communication system (PACS) within the medical institution. This enables the passive push and acquisition of image data and diagnostic reports such as digital radiography (DR), computed tomography (CT), magnetic resonance imaging (MRI), and emission computed tomography (ECT). Then, the aforementioned image data undergoes preliminary verification, deduplication, format standardization, missing field completion, and patient privacy anonymization. Subsequently, it is encrypted using national cryptographic algorithms and lossless compressed to reduce the transmission volume.

[0030] It is understood that when medical image data needs to be scheduled or retrieved, the embodiments provided in this application will first receive a doctor's first request for the target image data, and then the local caching system will search for the target image data within itself to determine whether the target image data that matches the first request is cached in the local caching system.

[0031] It should be noted that, in the embodiments provided in this application, the image data will be uploaded to the local caching system within 48 hours after the report is generated, and the local caching system will support real-time upload, scheduled upload, automatic re-upload, and breakpoint resume upload to ensure the integrity of the uploaded image data.

[0032] In the embodiments provided in this application, instead of actively capturing the image data, a passive push method is used for storing and retrieving the image data, which can maximize the stability of other medical systems within the medical institution.

[0033] S102. If the target image data is not retrieved from the local cache system, a second retrieval request for the target image data is sent to the central cache system corresponding to the local cache system. The second retrieval request is used to instruct the central cache system to retrieve the target image data, and if the target image data is not retrieved from the central cache system, the central cache system is instructed to send a third retrieval request for the target image data to the central index system. The third retrieval request is used to instruct the central index system to return the target image data, which is obtained from other central cache systems.

[0034] In this step, in the embodiment provided in this application, if the target image data requested and retrieved in the first retrieval request is not cached in the corresponding local caching system, i.e., the front-end machine, then a central caching system corresponding to the aforementioned local caching system is determined to be matched, and a second retrieval request is sent to the central caching system. If the target image data is retrieved from the central caching system, the central caching system is instructed to send a third retrieval request for the target image data to the central indexing system.

[0035] It is understood that in the embodiments provided in this application, both the local caching system and the central caching system are used to cache image data, and the cache validity period of the central caching system is not less than 30 days, while the cache validity period of the local caching system is not less than 1 day; while the central indexing system is used to store index locations, that is, the central indexing system does not cache or store image data.

[0036] It should be noted that the local caching system in the embodiments provided in this application is deployed at the hospital and is used to cache local and external images that are frequently accessed by doctors in the hospital. The cache validity period of the local caching system can be flexibly extended according to the hospital's workload. The central caching system is used to cache images accessed across provinces, high-frequency shared images in the region, and high-frequency image data mutually recognized by key hospitals.

[0037] The central index system is used to send a third retrieval request to the central index system to determine the data storage location of the target image when the target image data is not retrieved from the central cache system and the local cache system and other central cache systems corresponding to the target image data have not crossed protocols. Then, the central index system determines the other central cache systems where the target image data is located, and the other central cache systems send the corresponding target image data to the central index system, which then feeds back to the central cache system.

[0038] In the above, other central cache systems (central cache systems outside the province) are automatically written into the central cache system after being loaded into the central cache system of this province, and the cache validity period is no less than 30 days.

[0039] For example, if the target patient's target image data is cached in the local cache system, when the same patient visits again within a short period of time and requests the data repeatedly, it will be loaded directly from the local cache system without having to be retrieved from the central cache system.

[0040] Compared with the prior art, the image data scheduling method provided in this application responds to a first request for target image data and retrieves the target image data from the local cache system. If the target image data is not found in the local cache system, a second request for target image data is sent to the central cache system corresponding to the local cache system. The second request is used to instruct the retrieval of target image data from the central cache system. If the target image data is not found in the central cache system, the central cache system is instructed to send a third request for target image data to the central index system. The third request is used to instruct the central index system to return the target image data, which is obtained from other central cache systems. This application can reduce the storage cost of different levels of cache systems through distributed storage, and distributed storage can improve data retrieval and storage efficiency, thereby enhancing the user experience.

[0041] For example, the method further includes: if target image data is retrieved from the local cache system, then the target image data is sent to the target terminal through a cloud server corresponding to the local cache system.

[0042] In the embodiments provided in this application, if the local caching system caches the target image data, the target image data is sent to the cloud server corresponding to the local caching system. Then, the cloud server divides the parsed and rendered image data into blocks and streams the divided image data to the target terminal, so that the target terminal can complete the scheduling of the target image data. It should be noted that the cloud server in the embodiments provided in this application will complete all calculations such as Digital Imaging and Communications in Medicin (DICOM) parsing, windowing, and 3D reconstruction, convert the results into ordinary JPG / PNG images, and then push them to the target terminal in segments like watching short videos. The target terminal only needs a browser to view them, and they are displayed as they are transmitted.

[0043] The type of target terminal can be customized and used according to different application scenarios and usage needs. In the embodiments provided in this application, the type of target terminal can be specifically: personal computer (PC) workstation, mobile phone, tablet and self-service machine, etc.

[0044] In this application, target image data is directly obtained through a local caching system, and the target image data is divided into blocks through a cloud server to enable block-based access on the terminal, thereby improving access efficiency and reducing storage costs.

[0045] For example, the method also includes: The system receives the retrieved target image data sent by the central caching system and forwards the target image data to the target terminal through the cloud server corresponding to the local caching system. The retrieved target image data sent by the central caching system may be the target image data retrieved by the central caching system itself or the target image data retrieved by other central caching systems. The retrieved target image data sent by the central caching system is stored in the local caching system. One central caching system corresponds to multiple local caching systems.

[0046] In the above-mentioned process, if the target image data is not found in the local cache system, this application will continue to send a second request for the target image data to the central cache system. At this time, it is necessary to determine whether the central cache system has further cached target image data. If so, the target image data retrieved by the central cache system will be forwarded to the target terminal through the cloud server; or a third request for the target image data will be sent to the central index system, and then the central index system will forward the target image data retrieved by other central cache systems to the central cache system.

[0047] It should be noted that when retrieving the target image data from the central cache system, the target image data needs to be backed up and cached in the local cache system, and at the same time, it also needs to be uploaded to the cloud server. The cloud server then performs image analysis, window width and window level adjustment, multi-planar reconstruction (MPR) reconstruction, and 3D rendering on the target image data. The rendered target image data is then streamed to the target terminal in a block-by-block manner, enabling users to view the data on the target terminal while it is being uploaded, and displaying it in real time.

[0048] It is understood that each central cache system in the embodiments provided in this application corresponds to multiple local cache systems. For example, each central cache system (i.e., the provincial central cache system) corresponds to multiple municipal or prefecture-level local cache systems. Specifically, the central cache system of Hubei Province corresponds to multiple local cache systems, and each local cache system is deployed in various medical institutions.

[0049] In this application, when scheduling target image data of a target user, such as scheduling medical image data (e.g., hospital X-rays) of a target patient, the system first searches the local cache system to determine if the target image data exists. If the target image data is not found in the local cache system, a second request for the target image data is sent to the central cache system. If the target image data is still not found, a third request for the target image data is sent to the central index system until the target image data is obtained. In other words, the embodiments provided in this application schedule the target image data step by step according to the corresponding cache priority set by itself. After retrieving the target image data from any higher-level cache system, the target image data is backed up and stored in the next-level cache system for easy retrieval next time. That is, this application realizes the management and rapid retrieval of image data through distributed multi-level caching, thereby improving the efficiency of data retrieval.

[0050] For example, the method also includes: When the storage space utilization rate of the local cache system exceeds the preset storage space threshold, delete the historical image data that has not been accessed within the preset time period in the local cache system.

[0051] In the embodiments provided in this application, historical image data that has not been accessed for a long time in the local cache system will be eliminated based on the least recently used strategy, so as to realize the periodic cleaning and deletion of historical image data cached in the local cache system. The specific cleaning and deletion conditions are: when the storage space utilization rate of the local cache system is greater than the preset storage space threshold, the historical image data that has not been accessed within the preset time in the local cache system will be deleted.

[0052] Here, Least Recently Used (LRU) is a eviction algorithm. Its core idea is: the algorithm that hasn't been accessed for the longest time is the one that is evicted first.

[0053] Historical imagery data that has not been accessed within a certain timeframe is used to characterize imagery data that has not been accessed for a long time.

[0054] It should be noted that the preset duration in the local caching system in the embodiments provided in this application can be customized and used according to different application scenarios and usage conditions. Here, the preset duration in the embodiments provided in this application can be specifically set to 1 day, and the preset duration can be manually extended or appropriately extended according to the special characteristics of the target application scenario.

[0055] The preset storage space threshold in the embodiments provided in this application can be customized and used according to different application scenarios and usage conditions. Here, the preset storage space threshold in the embodiments provided in this application can be specifically set to 70%.

[0056] In this application, by automatically adjusting the cache capacity and validity period, the storage space of the local cache system is automatically reorganized periodically, which greatly reduces the time spent on data retrieval.

[0057] For example, forwarding the target image data to the target terminal via a cloud server corresponding to the local caching system includes: The target image data is parsed and rendered by a cloud server corresponding to the local caching system to determine the lightweight image corresponding to the target image data; the lightweight image is segmented by the cloud server to determine multiple image blocks; each image block is forwarded to the target terminal by the cloud server corresponding to the local caching system; the transmission time of the first image block is no greater than the preset response time.

[0058] In the above-described embodiments provided in this application, the process of parsing the target image data by the cloud server is as follows: adjusting the window width and window level and reconstructing multiple planes of the original file of the target image data; rendering after parsing, obtaining a lightweight image corresponding to the target image data after rendering, and then pushing the lightweight image to the target terminal in a block-by-block streaming manner.

[0059] It should be noted that the process of parsing the target image data on the cloud server is as follows: adjusting the window width and window level of the original target image data file and reconstructing multiple planes; and rendering is performed after the parsing is completed.

[0060] It is understood that this application forwards each image block to the target terminal via a cloud server by using a streaming protocol to send it to the target user using the aforementioned target terminal.

[0061] In the embodiments provided in this application, the preset response time can be customized and used according to different application scenarios and usage conditions. In the embodiments provided in this application, the preset response time can be specifically, but is not limited to, 3 seconds.

[0062] This application solves the cost and capacity issues through intelligent hierarchical storage, solves the data access speed and bandwidth issues through a dual-layer caching system, and solves the problem of ultra-fast video viewing on multiple terminals through cloud-based rendering and streaming. Furthermore, this invention adopts a cloud-based centralized rendering mode, which avoids complex data parsing on the target terminal, thereby reducing the performance dependency between the plugin and the terminal.

[0063] This application will deploy a cloud rendering service cluster, image analysis service, and streaming service on a cloud server, and configure response thresholds, concurrency limits, and multi-terminal adaptation rules to enable rapid access to target image data.

[0064] This application will establish a provincial-level image index library (i.e., a local caching system) and connect to the National Medical Insurance Image Cloud Index Sharing Center (i.e., the central index system) to realize cross-provincial index query and scheduling of target image data. Furthermore, this application can meet the clinical standards of rapid response of the first image of the target image data and smooth loading of the sequence.

[0065] The local caching system in this application, i.e., the cache scheduling of the front-end machine, follows a unified priority: first, the local caching system takes priority, then the central caching system's caching layer, then the first data storage layer, the second data storage layer, and finally the third data storage layer. Upon a cache hit at any layer, the cache is automatically written back to the next higher layer, accelerating subsequent access. Furthermore, the cached image data is encrypted throughout the process and maintains the same access control policy as the central caching system, preventing unauthorized users from reading the cached image data.

[0066] Figure 2 This is a second flowchart illustrating an image data scheduling method provided in an embodiment of this application. Figure 2 As shown, the image data scheduling method includes the following steps: S201. In response to a second retrieval request sent by any local caching system, retrieve target image data from the central caching system; wherein the second retrieval request is sent by the local caching system when no target image data is retrieved from the local caching system.

[0067] In this step, in the embodiments provided in this application, if the central cache system receives a second acquisition request sent from the local cache system, it needs to query the aforementioned target image data from its own central cache system.

[0068] Understandably, the target image data stored in the central cache system is transmitted to the central cache system via the medical insurance image private network in an encrypted manner, and is backed up in the local cache system in real time to ensure that the target image data is not lost.

[0069] It should be noted that, in the embodiments provided in this application, the storage period of the target image data stored in the central cache system can be customized and set according to different application scenarios (such as image data types) and usage conditions. For example, in the embodiments provided in this application, the storage period of outpatient image data is specifically set to 15 years, and the storage period of inpatient image data is specifically set to 30 years.

[0070] S202. If the target image data is retrieved from the central cache system, the retrieved target image data is sent to the local cache system.

[0071] In this step, in the embodiments provided in this application, if the target image data can be retrieved directly from the central cache system, it is necessary to send the retrieved target image data to the next level cache system of the central cache system, namely the local cache system, and cache it synchronously in the local cache system.

[0072] S203. If the target image data is not retrieved from the central cache system, a third retrieval request for the target image data is sent to the central index system.

[0073] In this step, in the embodiment provided in this application, if the target image data is not retrieved from the central cache system, a third retrieval request for the target image data needs to be sent to the upper-level cache system of the central cache system, namely the central index system, to request cross-province retrieval of the target user's target image data.

[0074] S204. Receive target image data obtained from other central cache systems as feedback from the central indexing system.

[0075] In this step, in the embodiment provided in this application, after sending the third acquisition request for target image data to the central indexing system, the central indexing system will index to other central cache systems that cache or store the target image data according to the information in the third acquisition request, and then the other central cache systems will send the target image data to the central cache system that made the third acquisition request.

[0076] It is understood that the central index system provided in this application can be customized and used according to different application scenarios and usage conditions. For example, in the embodiments provided in this application, the central index system is specifically, but not limited to, a medical insurance image cloud index sharing center.

[0077] S205. Store the target image data fed back by the central indexing system in the central cache system; wherein, the preset central indexing system corresponds to multiple central cache systems.

[0078] In this step, in the embodiments provided in this application, if the central index system queries the index of other central cache systems and receives target image data sent from other central cache systems, the central index system will feed back the target image data to the central cache system and all the next-level central cache systems within the jurisdiction of the central index system, and then the current central cache system will synchronously cache the corresponding target image data in the local cache system.

[0079] Compared with the prior art, the image data scheduling method provided in this application retrieves target image data from the central cache system in response to a second retrieval request sent by any of the local cache systems. When the target image data is retrieved from the central cache system, the retrieved target image data is sent to the local cache system. When the target image data is not retrieved from the central cache system, a third retrieval request for the target image data is sent to the central index system, and the target image data obtained from other central cache systems is received from the central index system. This application can reduce the storage cost of different levels of cache systems through distributed storage, and distributed storage can improve data retrieval and storage efficiency, thereby enhancing the user experience.

[0080] For example, the central caching system includes a first data storage layer, a second data storage layer, and a third data storage layer. Retrieving target image data from the central caching system includes: The system retrieves the last historical access time of the target image data; when the last historical access time is less than or equal to a first preset time threshold, it retrieves the target image data from the first data storage layer; when the last historical access time is greater than the first preset time threshold and less than or equal to a second preset time threshold, it retrieves the target image data from the second data storage layer, wherein the second preset time threshold is greater than the first preset time threshold; when the last historical access time is greater than the second preset time threshold, it retrieves the target image data from the third data storage layer.

[0081] In the process of retrieving target image data from the central cache system, if the target image data is not found in the cache layer of the central cache system, it is necessary to enter the storage layer of the central cache system. The storage layer of the central cache system mainly includes a first data storage layer for storing hot data, a second data storage layer for storing warm data, and a third data storage layer for storing cold data.

[0082] It is understood that the embodiments provided in this application will scan the last historical retrieval time of image data in each data storage layer according to a preset period, and migrate or store target image data whose last historical retrieval time is less than or equal to a first preset time threshold to the first data storage layer, migrate or store target image data whose last historical retrieval time is greater than the first preset time threshold and less than or equal to a second preset time threshold to the second data storage layer, and migrate or store target image data whose last historical retrieval time is greater than the second preset time threshold to the third data storage layer.

[0083] It should be noted that in the first data storage layer used to store hot data, the target image data is stored using all-flash storage, and the storage period is less than or equal to 2 years. The stored hot data is high-frequency access data, mainly supporting daily clinical access, follow-up visits, emergency care, and referrals. This layer provides low latency, high concurrency, and high read / write performance, ensuring that the first image opens instantly and can be browsed smoothly. The capacity of the hot data layer is planned according to annual increments and supports elastic expansion.

[0084] In the second data storage layer used to store temperature data, target image data is stored using SAS hard drives with a storage period of 2 to 5 years. The stored temperature data is medium-frequency access data, mainly used for follow-up, re-examination, departmental quality control, and medical insurance auditing. This layer uses a large-capacity NL-SAS disk array, balancing performance and cost, and providing stable and reliable medium-speed access.

[0085] In the third data storage layer used to store cold data, target image data is stored using object storage with a storage period of more than 5 years. The stored cold data is low-frequency access data used for compliant archiving, historical tracing, evidence in medical disputes, and scientific research retrospective. This layer uses low-cost object storage, supports massive, long-term, and highly reliable storage, and significantly reduces the unit storage cost.

[0086] This application ensures the security and controllability of long-term image data storage by implementing compliant management of the entire lifecycle of Level 3 data.

[0087] In this application, a three-tiered intelligent hierarchical storage system is planned and allocated for hot data (all-flash), warm data (SAS), and cold data (object storage). Based on the last historical access time and access frequency, layered storage and dynamic migration are performed to configure the data storage layer capacity, set redundancy strategies, and set automatic migration cycles, so as to achieve reasonable protection of target image data and significantly reduce storage costs while ensuring high-performance access.

[0088] For example, when the storage space utilization rate of the central cache system exceeds a preset storage space threshold, historical image data that has not been accessed within a preset time period in the central cache system is deleted.

[0089] In the embodiments provided in this application, historical image data that has not been accessed for a long time in the local cache system will be eliminated based on the least recently used strategy, so as to realize the periodic cleaning and deletion of historical image data cached in the local cache system. The specific cleaning and deletion conditions are: when the storage space utilization rate of the central cache system is greater than the preset storage space threshold, the historical image data that has not been accessed within the preset time in the central cache system will be deleted.

[0090] Understandably, the Least Recently Used (LRU) strategy is an eviction algorithm. Its core idea is to evict the device that has not been accessed for the longest time.

[0091] Historical imagery data that has not been accessed within a certain timeframe is used to characterize imagery data that has not been accessed for a long time.

[0092] In this application, by automatically adjusting the cache capacity and validity period, the storage space of the central cache system is automatically reorganized periodically, which greatly reduces the time spent on data retrieval.

[0093] For example, during the rendering of target image data, the cloud server will strictly meet the following metrics when no application scenario is provided: The response time for the first image in JPG / PNG format to be fully displayed is ≤3 seconds; The response time for the first complete display of a DICOM format image is ≤5 seconds. For CT and MRI sequences, the loading time for every 10 images should be ≤1 second. Window rendering supports real-time interactive functions such as scaling, panning, window width and level adjustment, measurement, and annotation.

[0094] The embodiments provided in this application combine a distributed cache on the front-end machine of medical institutions with a three-tiered storage architecture of hot, warm and cold storage that is automatically hierarchically stratified by the last historical retrieval time. This enables the nearest access to target image data and cross-domain data pre-fetching caching, reducing the storage pressure on the central cache system and the bandwidth consumption of the backbone network, and ensuring that multiple medical institutions can access and operate stably at the same time.

[0095] The embodiments provided in this application establish an integrated security mechanism by using national cryptographic encryption, link encryption, cache encryption, and access authentication when acquiring target image data from multiple resources. This ensures the security, privacy, and integrity of the data throughout the entire process, meeting the confidentiality requirements of the medical insurance cloud.

[0096] The following example illustrates the specific scheduling method for the above-described process image data: 1) Complete the authorization and identity authentication of the target user.

[0097] 2) Then query the index of the target image data from the local cache system. If there is no index in the local cache system, query the index of other provinces from the National Medical Insurance Image Cloud Index Center.

[0098] 3) Locate the position of the target image data in other central cache systems based on the index, and schedule the reading according to cache priority.

[0099] 4) Stream rendering is pushed to the target terminal.

[0100] 5) After successful retrieval, the data is automatically written to the two-level cache system.

[0101] 6) Access logs and record records in real time to the cloud, supporting traceability and auditing.

[0102] The aforementioned image data scheduling method enables image data scheduling to be pre-cached through appointment registration and medical visit behavior, caching relevant historical images to the central cache system before the patient arrives at the hospital, realizing "data first before the patient arrives", and further improving the speed of retrieval during medical visits.

[0103] For example, the embodiments provided in this application will implement corresponding data security management throughout the entire lifecycle of image data, as detailed below: During the acquisition phase: image data undergoes verification, anonymization, and encryption; during the transmission phase: image data undergoes dedicated network encryption, link authentication, and tamper-proofing; during the caching phase: image data undergoes encrypted storage, access control, and periodic cleanup; during the storage phase: image data undergoes hierarchical and layered management, redundant backup, and periodic verification; during the application phase: image data undergoes authorized access, operation logging, and privacy protection; during the archiving and destruction phase: image data undergoes expiration reminders, approval processes, and secure destruction.

[0104] As described above, the local caching system in the embodiments provided in this application provides security protection for image data, including security gateway, transmission encryption, storage encryption, cache encryption, identity authentication, fine-grained access control, access auditing, anomaly monitoring, leakage prevention, and tampering prevention, thereby achieving maximum security protection during the image data transmission process.

[0105] In this application, the embodiments provided by this application will comprehensively monitor storage capacity, data distribution, cache hit rate, access response time, network bandwidth and device health, thereby greatly alleviating network bandwidth pressure and automatically optimizing storage methods based on monitoring data.

[0106] The following example illustrates the implementation environment of the above-mentioned image data scheduling method: 1. Deployed on the Hubei Provincial Medical Insurance Imaging Cloud Platform, with the center located in the Wuhan Baowu Data Center, the central caching system carries core business, hot data, warm data, and caching services; the cloud server carries rendering services.

[0107] 2. Network construction covering the provincial, municipal, and county-level medical insurance imaging network: Bandwidth for tertiary medical institutions: 200M~500M; Bandwidth for medical institutions below tertiary level: 100M; Bandwidth for inter-provincial dedicated lines from province to country: 2G~5G; Bandwidth for provincial and municipal backbone dedicated lines: 1G~10G.

[0108] 3. The response time for rendering JPG / PNG images on the cloud server is ≤3 seconds; the response time for DICOM images is ≤5 seconds; and the response time for loading 10 CT / MRI images is ≤1 second.

[0109] Figure 3 This illustration shows a flowchart of the target image data lifecycle management process in an image data scheduling method provided in an embodiment of this application. For example... Figure 3 As shown, image data under any resource undergoes de-identification and encryption during the data acquisition phase. After preprocessing, it is transmitted via a dedicated encrypted network channel. After transmission, the image data is subject to access control and data cleaning. Then, according to the preset storage priority, the image data is stored in a hierarchical and layered manner with redundant backups. During the retrieval phase, access is authorized by verifying the accessor's permissions, thus completing the full lifecycle management of the target image data.

[0110] Here, when the storage space utilization rate of the cache system exceeds the preset storage space threshold, the corresponding historical image data is reminded of its expiration and is securely destroyed. Historical image data that has not been accessed within the preset time period is deleted from the local cache system.

[0111] Figure 4 A structural block diagram of a local caching system provided in an embodiment of this application is shown. Figure 4 As shown, the local caching system 400 includes: The first retrieval module 410 is used to retrieve the target image data from the local cache system in response to a first acquisition request for the target image data; The first sending module 420 is configured to send a second acquisition request for the target image data to the central cache system corresponding to the local cache system if the target image data is not retrieved from the local cache system; wherein the second acquisition request is used to instruct the central cache system to retrieve the target image data, and if the target image data is not retrieved from the central cache system, instruct the central cache system to send a third acquisition request for the target image data to the central index system; the third acquisition request is used to instruct the central index system to return the target image data, which is obtained from another central cache system.

[0112] The retrieval and sending module 430 is used to send the target image data to the target terminal through a cloud server corresponding to the local cache system if the target image data is retrieved from the local cache system.

[0113] The forwarding module 440 is used to receive the retrieved target image data sent by the central caching system, and forward the target image data to the target terminal through the cloud server corresponding to the local caching system; wherein, the retrieved target image data sent by the central caching system is target image data retrieved by the central caching system, or target image data retrieved by other central caching systems.

[0114] The first storage module 450 is used to store the retrieved target image data sent by the central cache system in the local cache system; wherein, one central cache system corresponds to multiple local cache systems.

[0115] The first deletion module 460 is used to delete historical image data that has not been accessed within a preset time period in the local cache system when the storage space utilization rate of the local cache system is greater than the preset storage space threshold.

[0116] For example, the retrieval and sending module 430 is specifically used for: The target image data is parsed and rendered by the cloud server corresponding to the local caching system to determine the lightweight image corresponding to the target image data; the lightweight image is segmented by the cloud server to determine multiple image blocks; each image block is forwarded to the target terminal by the cloud server corresponding to the local caching system; wherein the transmission time of the first image block is not greater than a preset response time.

[0117] The local image data caching system 400 provided in this application embodiment, compared with the prior art, responds to a first request for obtaining target image data and retrieves the target image data from the local cache system. If the target image data is not found in the local cache system, a second request for obtaining the target image data is sent to the central cache system corresponding to the local cache system. This application can reduce the storage cost of different levels of cache systems through distributed storage, and distributed storage can improve data retrieval and storage efficiency, thereby enhancing the user experience.

[0118] Figure 5 A structural block diagram of a central caching system provided in an embodiment of this application is shown. Figure 5 As shown, the central cache system 500 corresponds to multiple local cache systems 400, and the central cache system 500 includes: The second retrieval module 510 is configured to retrieve target image data from the central cache system in response to a second retrieval request sent by any of the local cache systems; wherein the second retrieval request is sent by the local cache system when the target image data is not retrieved from the local cache system.

[0119] The second sending module 520 is used to send the retrieved target image data to the local cache system if the target image data is retrieved from the central cache system.

[0120] The third sending module 530 is used to send a third acquisition request for the target image data to the central indexing system if the target image data is not retrieved from the central cache system.

[0121] The receiving module 540 is used to receive the target image data obtained from other central cache systems as feedback from the central indexing system.

[0122] The second storage module 550 is used to store the target image data fed back by the central indexing system in the central cache system; wherein, the preset central indexing system corresponds to multiple central cache systems.

[0123] The second deletion module 560 is used to delete historical image data that has not been accessed within a preset time period in the central cache system when the storage space utilization rate of the central cache system is greater than a preset storage space threshold.

[0124] For example, the central caching system includes a first data storage layer, a second data storage layer, and a third data storage layer, and the second sending module 520 is specifically used for: The system retrieves the last historical access time of the target image data; when the last historical access time is less than or equal to a first preset time threshold, it retrieves the target image data from the first data storage layer; when the last historical access time is greater than the first preset time threshold and less than or equal to a second preset time threshold, it retrieves the target image data from the second data storage layer, wherein the second preset time threshold is greater than the first preset time threshold; when the last historical access time is greater than the second preset time threshold, it retrieves the target image data from the third data storage layer.

[0125] Compared with the prior art, the image data central caching system 500 provided in this application retrieves target image data from the central caching system in response to a second retrieval request sent by any of the local caching systems. When the target image data is retrieved from the central caching system, the retrieved target image data is sent to the local caching system. When the target image data is not retrieved from the central caching system, a third retrieval request for the target image data is sent to the central indexing system, and the central indexing system sends back the target image data retrieved from other central caching systems. This application can reduce the storage cost of different levels of caching systems through distributed storage, and distributed storage can improve data retrieval and storage efficiency, thereby enhancing the user experience.

[0126] Please see Figure 6 , Figure 6 This application provides a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 6 As shown, the electronic device 600 includes a processor 610, a memory 620, and a bus 630.

[0127] Memory 620 stores machine-readable instructions executable by processor 610. When electronic device 600 is running, processor 610 and memory 620 communicate via bus 630. When the machine-readable instructions are executed by processor 610, they can perform the operations described above. Figures 1 to 2 The steps of the image data scheduling method in the method embodiment shown are described in detail in the method embodiment, and will not be repeated here.

[0128] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the above-described actions. Figures 1 to 2 The steps of the image data scheduling method in the method embodiment shown are described in detail in the method embodiment, and will not be repeated here.

[0129] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0130] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0131] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-readable program code.

[0132] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0133] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0134] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0135] This application also provides a computer program product, which includes computer software instructions that, when executed on a processing device, cause the processing device to execute a process of scheduling image data.

[0136] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. 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, 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, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0137] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0138] In the several embodiments provided in this application, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between devices or units, and may be electrical, mechanical, or other forms.

[0139] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0140] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0141] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0142] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

[0143] Although preferred embodiments have been described in this specification, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this specification.

[0144] Obviously, those skilled in the art can make various modifications and variations to this specification without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims and their equivalents, this specification is also intended to include such modifications and variations.

Claims

1. A method for scheduling image data, applied to a local caching system, characterized in that, The method for scheduling the image data includes: In response to a first request to acquire target image data, the target image data is retrieved from the local cache system; If the target image data is not found in the local cache system, a second request for the target image data is sent to the central cache system corresponding to the local cache system. The second acquisition request is used to instruct the central cache system to retrieve the target image data, and if the target image data is not retrieved from the central cache system, to instruct the central cache system to send a third acquisition request for the target image data to the central index system; the third acquisition request is used to instruct the central index system to return the target image data, which is obtained from other central cache systems.

2. The image data scheduling method according to claim 1, characterized in that, The method further includes: If the target image data is retrieved from the local cache system, the target image data is sent to the target terminal through the cloud server corresponding to the local cache system.

3. The image data scheduling method according to claim 1, characterized in that, The method further includes: The system receives the retrieved target image data sent by the central caching system and forwards the target image data to the target terminal through the cloud server corresponding to the local caching system. The target image data retrieved by the central cache system can be either the target image data retrieved by the central cache system itself or the target image data retrieved by other central cache systems.

4. The image data scheduling method according to claim 3, characterized in that, The method further includes: The retrieved target image data sent by the central cache system is stored in the local cache system; wherein, one central cache system corresponds to multiple local cache systems.

5. The method for scheduling image data according to any one of claims 1-4, characterized in that, The method further includes: When the storage space utilization rate of the local cache system exceeds the preset storage space threshold, delete the historical image data that has not been accessed within the preset time period in the local cache system.

6. The method for scheduling image data according to claim 2 or 3, characterized in that, The step of forwarding the target image data to the target terminal via the cloud server corresponding to the local caching system includes: The target image data is parsed and rendered by the cloud server corresponding to the local caching system to determine the lightweight image corresponding to the target image data; The cloud server is used to segment the lightweight image to determine multiple image blocks; Each of the image blocks is forwarded to the target terminal through the cloud server corresponding to the local caching system; wherein the transmission time of the first image block is not greater than a preset response time.

7. A method for scheduling image data, applied to a central cache system, wherein the central cache system corresponds to multiple local cache systems, characterized in that, The method for scheduling the image data includes: In response to a second retrieval request sent by any of the local caching systems, target image data is retrieved from the central caching system; wherein the second retrieval request is sent by the local caching system when the target image data is not retrieved from the local caching system. If the target image data is retrieved from the central cache system, the retrieved target image data is sent to the local cache system. If the target image data is not retrieved from the central cache system, a third retrieval request for the target image data is sent to the central index system. The system receives target image data obtained from other central caching systems as feedback from the central indexing system.

8. The image data scheduling method according to claim 7, characterized in that, The method further includes: The target image data fed back by the central indexing system is stored in the central cache system; wherein, the preset central indexing system corresponds to multiple central cache systems.

9. The method for scheduling image data according to claim 7 or 8, characterized in that, The central cache system includes a first data storage layer, a second data storage layer, and a third data storage layer. Retrieving the target image data from the central cache system includes: Obtain the last historical access time of the target image data; When the last historical retrieval time is less than or equal to a first preset time threshold, the target image data is retrieved from the first data storage layer; When the last historical retrieval time is greater than the first preset time threshold and less than or equal to the second preset time threshold, the target image data is retrieved from the second data storage layer, wherein the second preset time threshold is greater than the first preset time threshold; When the last historical retrieval time is greater than the second preset time threshold, the target image data is retrieved from the third data storage layer.

10. The method for scheduling image data according to any one of claims 8-10, characterized in that, The method further includes: When the storage space utilization rate of the central cache system exceeds a preset storage space threshold, historical image data that has not been accessed within a preset time period in the central cache system is deleted.

11. A local caching system, characterized in that, The local caching system includes: The first retrieval module is used to retrieve the target image data from the local cache system in response to a first acquisition request for the target image data; The first sending module is configured to send a second acquisition request for the target image data to the central cache system corresponding to the local cache system if the target image data is not retrieved from the local cache system. The second acquisition request is used to instruct the central cache system to retrieve the target image data, and if the target image data is not retrieved from the central cache system, to instruct the central cache system to send a third acquisition request for the target image data to the central index system; the third acquisition request is used to instruct the central index system to return the target image data, which is obtained from other central cache systems.

12. A central caching system, wherein the central caching system corresponds to multiple local caching systems, characterized in that, The central cache system includes: The second retrieval module is configured to retrieve target image data from the central cache system in response to a second retrieval request sent by any of the local cache systems; wherein the second retrieval request is sent by the local cache system when the target image data is not retrieved from the local cache system. The second sending module is used to send the retrieved target image data to the local cache system if the target image data is retrieved from the central cache system. The third sending module is used to send a third acquisition request for the target image data to the central indexing system if the target image data is not retrieved from the central cache system. The receiving module is used to receive target image data obtained from other central caching systems, which is fed back by the central indexing system.

13. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. The machine-readable instructions are executed by the processor to perform the steps of the image data scheduling method as described in any one of claims 1-7 or the image data scheduling method as described in any one of claims 8-14.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, performs the steps of the image data scheduling method as described in any one of claims 1-7 or the image data scheduling method as described in any one of claims 8-14.

Images