A multi-storage medium adaptation image file management method and device

Abstract

This paper relates to the field of data storage and provides a method and apparatus for image file management that adapts to multiple storage media. It pre-configures an image storage strategy table that records the association between image attribute information and storage strategy data. The method includes: determining the image operation type based on the image operation interface of received image transaction data; parsing the received image transaction data to obtain image metadata or image metadata and image files, where the image metadata includes transaction information, image document information, image attribute information, and image file information; performing operations on the image metadata according to the image operation type; querying the image storage strategy table based on the image attribute information to obtain target storage strategy data; and performing operations on the image files based on the image file information, image operation type, target storage strategy data, and their corresponding image operation tools. This paper can decouple the image system from the underlying storage media, achieving adaptation to various storage media.

Description

Technical Field

[0001] This article relates to the field of data storage, and in particular to a method and apparatus for managing image files that are compatible with multiple storage media. Background Technology

[0002] This section is intended to provide background or context for the embodiments of the invention set forth in the claims. The description herein is not an admission that it is prior art simply because it is included in this section.

[0003] In some existing technology scenarios, such as banking operations, it is necessary to reserve customers' personal image data, such as on-site facial photos, ID photos, and photocopies of contracts. These image files are generally stored in dedicated storage media within the information system. However, in some scenarios or with different requirements, such as the use of different storage media in the imaging systems of bank headquarters and branches, the existing imaging system only supports access to one underlying storage medium. When the storage medium is replaced or updated, or when other media are added, the underlying logic for image storage access needs to be redeveloped.

[0004] Therefore, the existing technology suffers from severe coupling between the imaging system and the underlying storage medium, which brings great inconvenience to the development, testing and maintenance of the imaging system. Summary of the Invention

[0005] This paper addresses the problem of severe coupling between existing imaging systems and underlying storage media. When the storage media is replaced or new media are added, the imaging system needs to be redeveloped to adapt to the new storage media.

[0006] To address the aforementioned technical issues, this paper provides a method for managing image files that adapts to multiple storage media. This method pre-configures an image storage strategy table, which records the association between image attribute information and storage strategy data. The storage strategy data includes information about the storage vendor, storage medium, storage unit, and server, including:

[0007] The image operation type is determined based on the image operation interface that receives the image transaction data;

[0008] The received image transaction data is parsed to obtain image metadata or image metadata and image files. The image metadata includes transaction information, image document information, image attribute information, and image file information.

[0009] Operate on the image metadata according to the image operation type;

[0010] The target storage strategy data is obtained by querying the image storage strategy table based on the image attribute information.

[0011] Based on the image file information, the image operation type, the target storage strategy data, and the corresponding image operation tool, the image files related to the image transaction data are operated.

[0012] As a further embodiment of this article, the image operation types include: image upload operation, image deletion operation, and image retrieval operation;

[0013] For image upload operations, the received image transaction data is parsed to obtain image metadata and image files; for image deletion and retrieval operations, the received image transaction data is parsed to obtain image metadata.

[0014] Based on the image file information, the image operation type, the target storage strategy data, and the corresponding image operation tool, operations are performed on the image files related to the image transaction data, including:

[0015] Generate an image file storage path based on the target storage strategy data and the image file information;

[0016] For image upload operations, based on the target storage strategy data, the association between the image file storage path and the storage area is established, and the image operation tool corresponding to the target storage strategy data uploads the image file to the storage area associated with the image file storage path.

[0017] For image deletion and retrieval operations, the image operation tool corresponding to the storage strategy data is used to perform deletion and retrieval operations on the image files in the storage area associated with the image file storage path.

[0018] In a further embodiment of this article, the transaction information includes a transaction serial number and a transaction number;

[0019] The image document information includes a document number;

[0020] The image attribute information includes image type and image library identifier;

[0021] The image file information includes the image file name and the image file number.

[0022] In a further embodiment of this paper, the image storage strategy table includes a file storage strategy master table, a storage medium table, and a storage medium service cluster table;

[0023] The file storage strategy master table is used to store image attribute information, storage manufacturer, storage medium and first primary key number;

[0024] The storage medium table is used to store the first primary key number, storage unit information, and the second primary key number;

[0025] The storage medium service cluster table is used to store the second primary key number and server information.

[0026] In a further embodiment of this paper, the target storage strategy data is obtained by querying the image storage strategy table based on the image attribute information, including:

[0027] Based on the image attribute information, the storage manufacturer, storage medium, and first primary key number are obtained by querying the file storage strategy master table;

[0028] Based on the first primary key number retrieved, the storage unit information and the second primary key number of the image transaction are obtained from the storage medium table;

[0029] Based on the second primary key number obtained from the query, the server-side information for image transactions can be retrieved from the storage media service cluster table.

[0030] In a further embodiment of this document, the storage strategy data also includes an encrypted storage identifier;

[0031] If the encrypted storage identifier in the storage policy data indicates that encryption is required, then before uploading the image file to the storage area associated with the image file storage path using the image operation tool corresponding to the target storage policy data, the method further includes: encrypting the image file and setting the encryption attribute of the image file to encrypted.

[0032] In another aspect, this article also provides an image file management device that adapts to multiple storage media, including:

[0033] A storage unit is used to store image storage strategies. The image storage strategy table records the association between image attribute information and storage strategy data. The storage strategy data includes storage vendor, storage medium, storage unit information, and server information.

[0034] The parsing unit is used to determine the image operation type based on the image operation interface of the received image transaction data; and to parse the received image transaction data to obtain image metadata or image metadata and image files, wherein the image metadata includes transaction information, image document information, image attribute information and image file information.

[0035] Metadata operation unit, used to operate on the image metadata according to the image operation type;

[0036] The query unit is used to query the image storage strategy table based on the image attribute information to obtain target storage strategy data;

[0037] The image operation unit is used to operate on the image files related to the image transaction data according to the image file information, the image operation type, the target storage strategy data and the corresponding image operation tool.

[0038] In another aspect, this document also provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in any embodiment.

[0039] In another aspect, this document also provides a computer storage medium having a computer program stored thereon, which, when run by a processor of a computer device, executes instructions for the method according to any of the foregoing embodiments.

[0040] In another aspect, this document also provides a computer program product comprising a computer program that, when executed by a processor, implements the method described in any of the foregoing embodiments.

[0041] The image file management method and apparatus for multi-storage media adaptation provided in this paper pre-configures an image storage strategy table. This table stores the association between image attribute information and storage strategy data. The storage strategy data includes storage vendor, storage medium, storage unit information, and server information. Image transaction data is parsed to obtain image metadata, which includes transaction information, image document information, image attribute information, and image file information. The image storage strategy table is queried based on the image attribute information to obtain target storage strategy data. Based on the image file information, image operation type, target storage strategy data, and corresponding image operation tools, operations are performed on the image files related to the image transaction data. This method decouples the image system from the underlying storage medium, enabling adaptation to various storage media. When the storage medium of the image system is replaced, only the image storage strategy table needs to be modified to access the replaced storage medium.

[0042] To make the above and other objects, features and advantages of this document more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0043] To more clearly illustrate the technical solutions in the embodiments or prior art described herein, the accompanying drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this article. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0044] Figure 1This document shows a structural diagram of the image file management system with multi-storage media adaptation according to an embodiment of the invention;

[0045] Figure 2 This paper presents a structural diagram of the image file management method with multi-storage media adaptation according to the embodiments of this paper;

[0046] Figure 3 This document illustrates a flowchart of the image file upload process in an embodiment of the invention.

[0047] Figure 4 The flowchart illustrating the image deletion and retrieval process in the embodiments of this article is shown.

[0048] Figure 5 A flowchart illustrating the target storage strategy data determination process in the embodiments of this article is shown;

[0049] Figure 6 This document shows a structural diagram of an image file management device with multi-storage media adaptation according to an embodiment of the invention;

[0050] Figure 7 A structural diagram of an image file management device with multi-storage media adaptation according to an embodiment of this paper is shown.

[0051] Explanation of symbols in the attached drawings:

[0052] 110. Front-end business platform;

[0053] 120. Imaging system platform;

[0054] 121. Database;

[0055] 122. Server;

[0056] 601. Storage unit;

[0057] 602. Analysis Unit;

[0058] 603. Metadata Operation Unit;

[0059] 604. Query Unit;

[0060] 605. Image Operation Unit;

[0061] 702. Image file management equipment;

[0062] 704, Processor;

[0063] 706. Memory;

[0064] 708. Drive mechanism;

[0065] 710. Input / Output Module;

[0066] 712. Input devices;

[0067] 714. Output devices;

[0068] 716. Presentation equipment;

[0069] 718. Graphical User Interface;

[0070] 720. Network interface;

[0071] 722. Communication link;

[0072] 724. Communication bus. Detailed Implementation

[0073] The technical solutions in the embodiments described below will be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments described herein, and not all of the embodiments. Based on the embodiments described herein, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this document.

[0074] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings herein are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, apparatus, product, or device that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0075] This specification provides the operational steps of the methods described in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only possible execution order. In actual system or device products, the methods shown in the embodiments or drawings can be executed sequentially or in parallel.

[0076] It should be noted that the image file management method and device adapted to multiple storage media described in this paper can be used in the financial field, or in any field other than the financial field. The application field of the image file management method and device adapted to multiple storage media described in this paper is not limited.

[0077] It should be noted that the information involved in this application (including but not limited to transaction information, image document information, image attribute information, and image file information) is all information and data authorized by the user or fully authorized by all parties.

[0078] In one embodiment of this document, an image file management system adaptable to multiple storage media is provided, such as... Figure 1 As shown, it includes a front-end business platform 110 and an imaging system platform 120. In some embodiments of this specification, the front-end business platform 110 can be a desktop computer, tablet computer, laptop computer, smartphone, digital assistant, smart wearable device, etc. The smart wearable device can include smart bracelets, smartwatches, smart glasses, smart helmets, etc. Of course, the client is not limited to the above-mentioned physical electronic devices; it can also be software running on the aforementioned electronic devices.

[0079] The front-end business platform 110 is used to send image transaction data to the image system platform 120. Image transaction data includes: initiator system identifier, image library identifier, transaction serial number, transaction number, document number, image type, image file number, and image file name. The initiator system identifier indicates the platform sending the image transaction data. The image library identifier indicates the database where the images are stored; different types of images are stored in different image libraries, such as ID card images stored in an ID card image library and face images stored in a face database. The transaction serial number and transaction number are generated by the front-end business platform when executing a business transaction and are used to indicate the transaction information to which the image belongs. The document number is the number of the image group; multiple images form a document, such as loan contract images or guarantee contract images. The image type indicates the type of the image, such as an ID card image or a face image. The image file number is used to uniquely identify the image; each image identifier corresponds to a different image number. The image file name is the name of the image file defined by the front-end user, such as 1.jpg. A single transaction can contain multiple document numbers, and each document number corresponds to multiple image numbers and image file names. For example, in the image file upload operation of loan transactions, the document number includes various document information such as loan contract, guarantee contract, front and back of borrower's ID card, and front and back of guarantor's ID card. Correspondingly, the loan contract and guarantee contract include multiple images.

[0080] The imaging system platform 120 includes a database 121 and a server 122.

[0081] Database 121 pre-configures an image storage strategy table. This table records the association between image attribute information and storage strategy data. The storage strategy data includes storage vendor, storage medium, storage unit information, and server information. The storage vendor refers to the manufacturer of the storage medium, for example, 01-vendor 1, 02-vendor 2, 03-vendor 3. Storage medium indicates the type of storage medium, for example, 01-object storage, 02-NAS (Network Attached Storage). Object storage is a high-efficiency storage system capable of storing massive amounts of unstructured data. NAS storage is a network storage system that uses standard network protocols to achieve data transmission, providing file sharing and data backup for various operating system devices on the network. Storage unit information indicates the storage unit information corresponding to the storage medium from the specified vendor, including the storage unit name prefix and the number of storage units. Server information includes the connection domain name and connection port, used to indicate the location of the storage medium. Image attribute information includes image type and image library identifier.

[0082] Server 122 provides multiple image operation interfaces, each receiving image transaction data of a specific operation type. Image operation types include: image upload, image deletion, and image retrieval. For image modification operations, they can be broken down into image deletion and image upload operations.

[0083] Specifically, server 122 is used to determine the image operation type based on the image operation interface of the received image transaction data; parse the received image transaction data to obtain image metadata or image metadata and image files, whereby the image metadata includes transaction information, image document information, image attribute information, and image file information; perform operations on the image metadata according to the image operation type; query the image storage strategy table according to the image attribute information to obtain target storage strategy data; and perform operations on the image files related to the image transaction data according to the image file information, image operation type, target storage strategy data, and their corresponding image operation tools.

[0084] This paper proposes a method to decouple the imaging system from the underlying storage media by setting an image storage strategy table, thereby enabling adaptation between different storage media. When the storage media of the imaging system is replaced, only the image storage strategy table needs to be modified to enable access to the replaced storage media.

[0085] In one embodiment of this paper, an image file management method adaptable to multiple storage media is also provided, which is applied to an image system. Before the implementation of this method, an image storage strategy table is pre-configured, as shown in Table 1. The image storage strategy table records the association between image attribute information and storage strategy data. The image attribute information includes image type and image library identifier, and the storage strategy data includes storage manufacturer, storage medium, storage unit information and server information.

[0086] Table 1

[0087]

[0088] Specifically, such as Figure 2 As shown, the image file management method adaptable to multiple storage media includes:

[0089] Step 201: Determine the image operation type based on the image operation interface for receiving image transaction data.

[0090] This step can be implemented by querying the mapping relationship between image operation interfaces and image operation types. Image operation types include at least: image upload, image deletion, and image retrieval. For other types of image operations, they can be broken down into multiple of the above-mentioned image operations; for example, an image modification operation can be broken down into an image deletion operation and an image upload operation.

[0091] Step 202: Parse the received image transaction data to obtain image metadata or image metadata and image files. The image metadata includes transaction information, image document information, image attribute information, and image file information.

[0092] Specifically, for image upload operations, the received image transaction data is parsed to obtain image metadata and image files; for image deletion and retrieval operations, the received image transaction data is parsed to obtain image metadata.

[0093] Image attribute information in image metadata can also be subordinated to image document information. Each type of information included in image metadata is stored in a different data table.

[0094] Transaction information includes the transaction serial number and transaction ID. Image document information includes the document ID. Image attribute information includes the image type and image library identifier. Image file information includes the image file name and image file ID.

[0095] Image metadata is structured data stored in a relational database. It is descriptive information about image files and is used to record the relationship between images and transactions, making it easier to find image files based on transactions.

[0096] Step 203: Perform operations on the image metadata according to the image operation type. Specifically, if the image operation type is upload, then upload the image metadata. If the image operation type is delete, then delete the existing identical image metadata in the database. If the image operation type is retrieval, then read the existing identical image metadata in the database.

[0097] Step 204: Query the image storage strategy table based on the image attribute information to obtain the target storage strategy data.

[0098] For image upload operations, the target storage policy data indicates the upload location for the image file to be uploaded. For image deletion and retrieval operations, the target storage policy data indicates the storage location for the image files to be deleted and retrieved, respectively.

[0099] Step 205: Perform operations on the image files related to the image transaction data based on the image file information, image operation type, target storage strategy data, and corresponding image operation tools.

[0100] In detail, image manipulation tools are software development kits provided by various storage media manufacturers to enable operations such as uploading, deleting, and retrieving image files. This article does not limit the specific implementation methods.

[0101] In practice, steps 204 and 205 can be encapsulated as an image storage access service layer. This image storage access service layer interfaces with the underlying storage medium access interface, allowing upper-layer services to access image storage services without needing to understand the underlying implementation logic.

[0102] For image upload operations, the image files associated with the image transaction data are the image files parsed from the image transaction data. For image deletion and retrieval operations, the image files associated with the image transaction data are the image files linked to the image metadata in the storage medium.

[0103] Specifically, regarding image uploading operations, such as Figure 3 As shown, the implementation process of step 205 includes:

[0104] Step 301: Generate the image file storage path based on the target storage strategy data and image file information. In practice, the image file storage path can be obtained by concatenating the target storage strategy data and image file information. The image file storage path can uniquely indicate the storage location of the image file to be uploaded, avoiding image file overwriting due to duplicate image file names.

[0105] Step 302: Based on the target storage strategy data, establish the association between image file storage paths and storage areas. The association between image file storage paths and storage areas is stored in the database. During this step, the storage areas where data can be stored are first determined based on the target storage strategy data, and then the association between image file storage paths and storage areas is established.

[0106] Step 303: Upload the image file to the storage area associated with the image file storage path using the image operation tool corresponding to the target storage strategy data.

[0107] For operations such as deleting and retrieving images, Figure 4As shown, the implementation process of step 205 includes:

[0108] Step 401: Generate an image file storage path based on the target storage strategy data and image file information. The image file storage path generated in this step can locate the image file from the storage unit of the corresponding storage medium.

[0109] Step 402: Based on the image operation tool corresponding to the storage strategy data, perform deletion and reading operations on the image files in the storage area associated with the image file storage path.

[0110] In one embodiment of this paper, in order to improve the reading efficiency of image storage strategy data, the image storage strategy table is divided into multiple sub-tables, including a file storage strategy master table, a storage medium table, and a storage medium service cluster table.

[0111] Specifically, the file storage policy master table stores image attribute information, storage vendor, storage medium, and primary key number. The primary key number, also known as the storage policy number, is used to establish a relationship with the storage medium table.

[0112] The storage medium table stores the first primary key number, storage unit information (storage unit name prefix, number of storage units), and the second primary key number. The storage medium represents the configuration table of storage media in the file storage policy master table. Taking object storage as an example, the storage unit name prefix `storage_name` and the storage quantity `storage_count` can specify a unified bucket name prefix and number for this type of image. For example, if the prefix is ​​`bucket-xxx-` and the storage quantity is 2, then the bucket information is `bucket-xxx-0` and `bucket-xxx-1`. The second primary key number can also be called the storage medium service cluster number, used to establish the association relationship with the storage medium service cluster table.

[0113] The storage medium service cluster table is used to store the secondary primary key number and server information.

[0114] Furthermore, such as Figure 5 As shown, step 204 queries the image storage strategy table based on image attribute information to obtain target storage strategy data, including:

[0115] Step 501: Based on the image attribute information, retrieve the storage manufacturer, storage medium, and first primary key number from the file storage strategy master table.

[0116] Step 502: Based on the first primary key number obtained from the query, retrieve the storage unit information and the second primary key number of the image transaction from the storage medium table.

[0117] Step 503: Based on the retrieved second primary key number, retrieve the server information for image transactions from the storage media service cluster table.

[0118] The target storage strategy data is composed of the queried storage vendor, storage medium, storage unit information and server information.

[0119] In one embodiment of this paper, the storage policy data also includes an encrypted storage identifier.

[0120] For image upload operations, if the encrypted storage identifier in the storage policy data indicates that encryption is required, the image operation tool corresponding to the target storage policy data will upload the image file to the storage area associated with the image file storage path before performing the following steps: encrypting the image file, setting the encryption attribute of the image file to encrypted, and uploading the encrypted data to the storage area associated with the image file storage path.

[0121] For image retrieval operations, if the encrypted storage identifier in the storage policy data indicates that encryption is required, then after reading the image file in the storage area associated with the image file storage path, the read image file is decrypted, and the decrypted image file is sent to the front-end business platform.

[0122] In one embodiment of this paper, after receiving image transaction data, the image operation interface also verifies the image transaction data. The verification content includes, for example, format verification and business logic verification. The verification process can identify and ensure the validity of external transaction data so that subsequent functions can be executed smoothly.

[0123] Based on the same inventive concept, this document also provides an image file management device adapted to multiple storage media, as described in the following embodiments. Since the principle and method of solving the problem are similar for the image file management device adapted to multiple storage media, the implementation of the image file management device adapted to multiple storage media can refer to the image file management method adapted to multiple storage media, and repeated details will not be elaborated further.

[0124] Specifically, such as Figure 6 As shown, the image file management device with multi-storage media adaptation includes:

[0125] Storage unit 601 is used to store image storage strategies. The image storage strategy table records the relationship between image attribute information and storage strategy data. The storage strategy data includes storage vendor, storage medium, storage unit information and server information.

[0126] The parsing unit 602 is used to determine the image operation type based on the image operation interface of the received image transaction data; and to parse the received image transaction data to obtain image metadata or image metadata and image files. The image metadata includes transaction information, image document information, image attribute information and image file information.

[0127] Metadata operation unit 603 is used to operate on image metadata according to image operation type.

[0128] The query unit 604 is used to query the image storage strategy table based on image attribute information to obtain target storage strategy data.

[0129] The image operation unit 605 is used to operate on image files related to image transaction data based on image file information, image operation type, target storage strategy data and corresponding image operation tools.

[0130] This embodiment can decouple the image system from the underlying storage medium by pre-configuring the image storage strategy table, thereby enabling adaptation of each storage medium. When the storage medium of the image system is replaced, only the image storage strategy table needs to be modified to enable access to the replaced storage medium.

[0131] In this embodiment, an image file management device adaptable to multiple storage media is also provided, such as... Figure 7 As shown, the image file management device 702 may include one or more processors 704, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The image file management device 702 may also include any memory 706 for storing any kind of information, such as code, settings, data, etc. Non-limitingly, for example, memory 706 may include any type of RAM, any type of ROM, flash memory, hard disk, optical disk, etc. More generally, any memory can use any technology to store information. Furthermore, any memory may provide volatile or non-volatile retention of information. Furthermore, any memory may represent a fixed or removable component of the image file management device 702. In one case, when processor 704 executes associated instructions stored in any memory or combination of memories, the image file management device 702 may perform any operation of the associated instructions. The image file management device 702 also includes one or more drive mechanisms 708 for interacting with any memory, such as hard disk drive mechanisms, optical disk drive mechanisms, etc.

[0132] The image file management device 702 may further include an input / output module 710 (I / O) for receiving various inputs (via input device 712) and providing various outputs (via output device 714). A specific output mechanism may include a presentation device 716 and an associated graphical user interface 718 (GUI). In other embodiments, the input / output module 710 (I / O), input device 712, and output device 714 may be omitted, and the device may function solely as a computer device within a network. The image file management device 702 may also include one or more network interfaces 720 for exchanging data with other devices via one or more communication links 722. One or more communication buses 724 couple the components described above together.

[0133] Communication link 722 can be implemented in any way, such as via a local area network, a wide area network (e.g., the Internet), a point-to-point connection, or any combination thereof. Communication link 722 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

[0134] Corresponding to Figures 2 to 6 In addition to the methods described above, this embodiment also provides a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the above-described methods.

[0135] This embodiment also provides a computer-readable instruction, wherein when a processor executes the instruction, the program therein causes the processor to perform the following: Figures 2 to 6 The method shown.

[0136] This embodiment also provides a computer program product, which includes a computer program that, when executed by a processor, implements the method described in any of the foregoing embodiments.

[0137] It should be understood that in the various embodiments of this document, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.

[0138] It should also be understood that, in the embodiments herein, the term "and / or" is merely a description of the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following associated objects have an "or" relationship.

[0139] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this document.

[0140] 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.

[0141] In the embodiments provided herein, it should be understood that the disclosed systems, 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 couplings or direct couplings or communication connections shown or discussed may be indirect couplings or communication connections through some interfaces, devices, or units, or they may be electrical, mechanical, or other forms of connection.

[0142] 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 the embodiments described herein, depending on actual needs.

[0143] Furthermore, the functional units in the various embodiments of this document 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.

[0144] 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 paper, 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 described in the various embodiments of this paper. 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.

[0145] This document uses specific embodiments to illustrate the principles and implementation methods of this document. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this document. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this document. Therefore, the content of this specification should not be construed as a limitation of this document.

Claims

1. A multi-storage medium adapted image file management method, characterized by, A pre-configured image storage strategy table is provided. This table includes a file storage strategy master table, a storage medium table, and a storage medium service cluster table. The image storage strategy table records the association between image attribute information and storage strategy data. The storage strategy data includes storage vendor, storage medium, storage unit information, and server information. The file storage strategy master table stores image attribute information, storage vendor, storage medium, and a first primary key number. The storage medium table stores the first primary key number, storage unit information, and a second primary key number. The storage medium service cluster table stores the second primary key number and server information. When the storage medium of the image system is replaced, only the image storage strategy table needs to be modified to access the replaced storage medium. The method includes: The image operation type is determined based on the image operation interface that receives the image transaction data; The received image transaction data is parsed to obtain image metadata or image metadata and image files. The image metadata includes transaction information, image document information, image attribute information, and image file information. Operate on the image metadata according to the image operation type; The target storage strategy data is obtained by querying the image storage strategy table based on the image attribute information, including: querying the storage vendor, storage medium, and first primary key number from the file storage strategy master table based on the image attribute information; querying the storage unit information and second primary key number of the image transaction from the storage medium table based on the first primary key number; querying the server information of the image transaction from the storage medium service cluster table based on the second primary key number; and the target storage strategy data is composed of the queried storage vendor, storage medium, storage unit information, and server information. Based on the image file information, the image operation type, the target storage strategy data, and the corresponding image operation tool, the image files related to the image transaction data are operated.

2. The method of claim 1, wherein, The image operation types include: image upload operation, image deletion operation, and image retrieval operation; For image upload operations, the received image transaction data is parsed to obtain image metadata and image files; for image deletion and retrieval operations, the received image transaction data is parsed to obtain image metadata. Based on the image file information, the image operation type, the target storage strategy data, and the corresponding image operation tool, operations are performed on the image files related to the image transaction data, including: Generate an image file storage path based on the target storage strategy data and the image file information; For image upload operations, based on the target storage strategy data, the association between the image file storage path and the storage area is established, and the image operation tool corresponding to the target storage strategy data uploads the image file to the storage area associated with the image file storage path. For image deletion and retrieval operations, the image operation tool corresponding to the storage strategy data is used to perform deletion and retrieval operations on the image files in the storage area associated with the image file storage path.

3. The method of claim 2, wherein, The transaction information includes the transaction serial number and the transaction number; The image document information includes a document number; The image attribute information includes image type and image library identifier; The image file information includes the image file name and the image file number.

4. The method of claim 1, wherein, The storage strategy data also includes encrypted storage identifiers; If the encrypted storage identifier in the storage policy data indicates that encryption is required, then before uploading the image file to the storage area associated with the image file storage path using the image operation tool corresponding to the target storage policy data, the method further includes: encrypting the image file and setting the encryption attribute of the image file to encrypted.

5. A multi-storage medium adapted image file management apparatus, characterized by comprising: include: The storage unit stores image storage strategies. The image storage strategy table includes a file storage strategy master table, a storage medium table, and a storage medium service cluster table. The image storage strategy table records the association between image attribute information and storage strategy data. The storage strategy data includes storage vendor, storage medium, storage unit information, and server information. The file storage strategy master table stores image attribute information, storage vendor, storage medium, and a first primary key number. The storage medium table stores the first primary key number, storage unit information, and a second primary key number. The storage medium service cluster table stores the second primary key number and server information. When the storage medium of the image system is replaced, only the image storage strategy table needs to be modified to access the replaced storage medium. The parsing unit is used to determine the image operation type based on the image operation interface of the received image transaction data; and to parse the received image transaction data to obtain image metadata or image metadata and image files, wherein the image metadata includes transaction information, image document information, image attribute information and image file information. Metadata operation unit, used to operate on the image metadata according to the image operation type; The query unit is used to query the image storage strategy table based on the image attribute information to obtain target storage strategy data, including: querying the file storage strategy master table to obtain the storage vendor, storage medium, and first primary key number based on the image attribute information; querying the storage unit information and second primary key number of the image transaction from the storage medium table based on the first primary key number; querying the server information of the image transaction from the storage medium service cluster table based on the second primary key number; and constructing the target storage strategy data from the queried storage vendor, storage medium, storage unit information, and server information. The image operation unit is used to operate on the image files related to the image transaction data according to the image file information, the image operation type, the target storage strategy data and the corresponding image operation tool.

6. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 4.

7. A computer storage medium having stored thereon a computer program, characterized in that When the computer program is run by the processor of the computer device, it executes the instructions of the method according to any one of claims 1 to 4.

8. A computer program product, characterised in that, The computer program product includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 4.

Images