DICOM file processing method and device, electronic equipment and storage medium

Abstract

The invention discloses a DICOM file processing method and device, electronic equipment and a storage medium. The DICOM file processing method comprises the following steps: acquiring a DICOM file, and carrying out standardized preprocessing and compression demand detection on the DICOM file; under the condition that the DICOM file has a compression requirement, data features of the DICOM file are identified, and the data features comprise at least one of modal features, window positions, bit depths, image frame numbers and pixel-level features of the image data; determining a compression strategy adaptive to the DICOM file based on the data characteristics of the DICOM file; according to the method, the data content in the DICOM file is compressed based on the compression strategy to obtain the compressed data, and the compressed data is subjected to layered packaging and encrypted transmission, so that lossless compression of the DICOM file is realized, the quality of the DICOM file is ensured, and comprehensive data support is provided for subsequent decision making.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a DICOM file processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] In scenarios such as medical image diagnosis, remote consultation, remote surgical guidance, and medical image data archiving and sharing, Digital Imaging and Communications in Medicine (DICOM) files play a crucial role. DICOM files are characterized by their large size and quantity, and direct transmission of DICOM files can easily lead to transmission delays, stuttering, or even interruptions. Therefore, DICOM files need to be compressed.

[0003] In existing technologies, DICOM files are transmitted after being subjected to lossy compression. While lossy compression can improve the transmission efficiency of DICOM files, it can lead to the loss of details in the medical image data within the DICOM file, resulting in poor quality DICOM files. Summary of the Invention

[0004] This invention provides a DICOM file processing method, apparatus, electronic device, and storage medium to achieve lossless compression of DICOM files and ensure the quality of DICOM files.

[0005] According to one aspect of the present invention, a DICOM file processing method is provided, comprising:

[0006] Obtain the DICOM file, and perform standardized preprocessing and compression requirement detection on the DICOM file;

[0007] When there is a need to compress DICOM files, identify the data characteristics of the DICOM files. The data characteristics include at least one of the following: modal characteristics of image data, window level, bit depth, number of image frames, and pixel-level characteristics.

[0008] Determine the appropriate compression strategy for DICOM files based on their data characteristics;

[0009] The data content in the DICOM file is compressed based on the compression strategy to obtain compressed data. The compressed data is then layered, encapsulated, and encrypted before transmission.

[0010] According to another aspect of the present invention, a DICOM file processing apparatus is provided, comprising:

[0011] The detection module is used to acquire DICOM files, perform standardized preprocessing on the DICOM files, and detect compression requirements.

[0012] The data feature recognition module is used to identify the data features of DICOM files when compression is required. The data features include at least one of the following: modal features of image data, window level, bit depth, number of image frames, and pixel-level features.

[0013] The compression strategy determination module is used to determine the appropriate compression strategy for DICOM files based on their data characteristics.

[0014] The layered encapsulation and encrypted transmission module is used to compress the data content in the DICOM file based on the compression strategy to obtain compressed data, and then to perform layered encapsulation and encrypted transmission of the compressed data.

[0015] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0016] At least one processor; and

[0017] A memory that is communicatively connected to at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by at least one processor, such that the at least one processor is able to perform the DICOM file processing method provided in any embodiment of the present invention.

[0019] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the DICOM file processing method provided in any embodiment of the present invention.

[0020] The technical solution of this invention, by acquiring DICOM files and performing standardized preprocessing and compression requirement detection on them, achieves the unification of DICOM files, providing unified data support for subsequent analysis and processing. When compression is required for DICOM files, the system identifies their data characteristics, including at least one of the following: modal characteristics of image data, window level, bit depth, image frame count, and pixel-level features, providing comprehensive data support for subsequent analysis and processing. Based on these data characteristics, the system determines the appropriate compression strategy for the DICOM file, achieving precise determination of the compression strategy and providing accurate data support for lossless compression of DICOM files. Based on the compression strategy, the system compresses the data content in the DICOM file to obtain compressed data. This compressed data is then layered, encapsulated, and encrypted for transmission, solving the problem of poor DICOM file quality caused by lossy compression in existing technologies. This achieves lossless compression of DICOM files, ensuring their quality and providing comprehensive data support for subsequent decision-making.

[0021] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

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

[0023] Figure 1 This is a flowchart of a DICOM file processing method provided in Embodiment 1 of the present invention;

[0024] Figure 2 This is a flowchart of a DICOM file processing method provided in Embodiment 2 of the present invention;

[0025] Figure 3 This is a schematic diagram of the structure of a DICOM file processing device provided in Embodiment 3 of the present invention;

[0026] Figure 4 This is a schematic diagram of the structure of an electronic device provided in Embodiment 4 of the present invention. Detailed Implementation

[0027] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention 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 of the invention 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, system, product, or apparatus 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 apparatus.

[0029] Example 1

[0030] Figure 1 This is a flowchart of a DICOM file processing method provided in Embodiment 1 of the present invention. This embodiment is applicable to the compression of DICOM files. The method can be executed by a DICOM file processing device, which can be implemented in hardware and / or software. This DICOM file processing device can be configured in the electronic device provided in this embodiment of the invention. The electronic device can be a server, computer, or mobile terminal, such as a mobile phone or tablet computer. Figure 1 As shown, the method specifically includes the following steps:

[0031] S110. Obtain the DICOM file, and perform standardized preprocessing and compression requirement detection on the DICOM file.

[0032] DICOM files are medical image files conforming to the Digital Imaging and Communications in Medicine 3.0 international standard. DICOM files can be obtained through image acquisition devices, including but not limited to computed tomography (CT) equipment, ultrasound equipment, and magnetic resonance imaging (MRI) equipment. For example, images of the subject being examined are acquired using an image acquisition device to obtain a DICOM file. DICOM files may also carry a first unique identifier; different DICOM files correspond to different first unique identifiers, which may consist of at least one character selected from numbers, letters, and special symbols. DICOM files can also be obtained from a DICOM file database, which may store multiple DICOM files. The corresponding DICOM file is obtained by matching the first unique identifier of the DICOM file in the database. Optionally, DICOM files may include metadata and medical image data. Metadata includes, but is not limited to, the unique identification information of the subject being examined, information about the image acquisition device, and examination parameters. Optionally, DICOM files may include multiple frames of medical image data.

[0033] Standardization preprocessing of DICOM files can include removing redundant metadata. Since medical image data contains noisy pixels and black borders, a grayscale threshold and a preset number of consecutive pixels can be set. When the grayscale value is less than or equal to the grayscale threshold and the number of consecutive pixels is greater than or equal to the preset number of consecutive pixels, the area corresponding to the consecutive pixels is considered invalid and removed. Because different models and brands of image acquisition devices use different encoding formats for DICOM files, the encoding format of the DICOM file can be converted to a preset encoding format, achieving a unified encoding format for DICOM files and providing a unified data foundation for subsequent analysis. Since medical image data in DICOM files may contain missing pixels, these pixels can be replaced, for example, through neighbor pixel interpolation. Standardization preprocessing of DICOM files can also include converting the metadata format to 8-bit Unicode Transformation Format (UTF-8) encoding to achieve format uniformity. Standardization preprocessing of DICOM files may further include assigning a second unique identifier to the medical image data. This second unique identifier may include at least one of the following: the unique identification information of the examined object, the acquisition time of the DICOM file, and the first unique identifier information of the DICOM file. Compression requirements include whether the DICOM file has compression requirements and whether it does not. Compression requirement detection for DICOM files can be achieved using a compression requirement detection model. For example, the DICOM file can be input into a trained compression requirement detection model to determine its compression requirements. The compression requirement detection model includes, but is not limited to, neural network models.

[0034] Specifically, images of the object under inspection are acquired using image acquisition equipment to obtain DICOM files; the DICOM files are then preprocessed for standardization; and the DICOM files are input into a trained compression requirement detection model for compression requirement detection to obtain the compression requirements of the DICOM files. This achieves the standardization of DICOM files and provides unified data support for subsequent analysis and processing.

[0035] S120. When there is a need to compress DICOM files, identify the data characteristics of the DICOM files. The data characteristics include at least one of the modal characteristics of image data, window level, bit depth, number of image frames, and pixel-level characteristics.

[0036] Data features are used to characterize the pixel distribution of medical image data. Data features include at least one of the following: modal features, window level, bit depth, number of image frames, and pixel-level features. Modal features characterize the imaging type of the medical image data, including but not limited to CT, ultrasound, MRI, and X-ray types. The number of image frames characterizes the quantity of medical image data in the DICOM file. Pixel-level features include, but are not limited to, texture features, resolution, noise level, pixel correlation, and grayscale range. To identify the data features of a DICOM file, the DICOM file can be input into a data feature recognition model for processing to obtain the data features of the DICOM file. The data feature recognition model includes, but is not limited to, neural network models.

[0037] Specifically, when there is a need to compress DICOM files, the DICOM files are input into a data feature recognition model for processing to obtain the data features of the DICOM files, providing comprehensive data support for subsequent analysis and processing.

[0038] S130. Determine the compression strategy for DICOM files based on their data characteristics.

[0039] The compression strategy refers to the lossless compression method used to compress DICOM files. The compression strategy may include a compression model, which includes, but is not limited to, a neural network model. For example, the compression model may include the JPEG Lossless Compression for Continuous-tone Images (JPEG-LS) model and the JPEG 2000 Lossless Compression Algorithm (JPEG 2000) model. Different data characteristics of DICOM files correspond to different compression strategies. The compression strategy can be determined based on the mapping relationship between the data characteristics of the DICOM file and the compression strategy. For example, the appropriate compression strategy for the DICOM file can be obtained by matching the data characteristics of the DICOM file with a mapping table of data characteristics and compression strategies.

[0040] Specifically, by matching the data characteristics of DICOM files with a mapping table of data characteristics and compression strategies, the appropriate compression strategy for DICOM files is obtained, thus achieving accurate determination of the compression strategy and providing accurate data support for lossless compression of DICOM files.

[0041] Optionally, determining the compression strategy adapted to the DICOM file based on the data characteristics of the DICOM file includes: matching the data characteristics of the DICOM file with the data characteristic conditions corresponding to each compression strategy in the first compression configuration file to determine the compression strategy adapted to the DICOM file, wherein the data characteristic conditions corresponding to the compression strategy include at least one data characteristic adapted to the compression strategy.

[0042] The first compression configuration file is a file that stores compression strategies and matching rules for those strategies. The first compression configuration file can be pre-set. Data feature conditions are matching criteria adapted to the compression strategy. Data feature conditions may include at least one data feature corresponding to each compression strategy. For example, when data features include bit depth and modal features, the corresponding data feature conditions are: bit depth greater than or equal to a preset bit depth, modal feature is MRI type, and the corresponding compression strategy is JPEG 2000 model.

[0043] Specifically, the data characteristics of the DICOM file are matched with the data characteristic conditions corresponding to each compression strategy in the first compression configuration file. When the data characteristics of the DICOM file match the data characteristic conditions, the compression strategy corresponding to the data characteristic conditions is used as the compression strategy adapted to the DICOM file. This achieves accurate determination of the compression strategy adapted to the DICOM file, improves the compatibility between the DICOM file and the compression strategy, and thus helps to improve the compression efficiency and accuracy of the DICOM file.

[0044] For example, for a DICOM file with modal features of type CT, the corresponding compression strategy can be to sequentially perform predictive coding and arithmetic coding on the DICOM file. The formula for calculating predictive coding is as follows: ;in, This represents the predicted pixel value in the i-th row and j-th column obtained through predictive encoding; This represents the actual pixel value in the (i-1)th row and jth column; This represents the prediction coefficient for the true value pixel in the (i-1)th row and jth column, and can be 0.4. This represents the actual pixel value in the i-th row and j-1-th column; This represents the prediction coefficient for the true value pixel in the i-th row and (j-1)-th column, and can be 0.3. This represents the actual pixel value in the (i-1)th row and (j-1)th column; The prediction coefficient represents the true value pixel in the (i-1)th row and (j-1)th column, and can be 0.3; This represents the offset, which can be 0.8.

[0045] For example, for a DICOM file with MRI-type modal characteristics, the corresponding compression strategy can be to sequentially perform inter-frame predictive coding and entropy coding on the DICOM file. The calculation formula for inter-frame predictive coding is as follows: ;in, This represents the predicted pixel value in the i-th row and j-th column obtained through inter-frame predictive coding; This represents the actual pixel value in the (i-1)th row and jth column; This represents the prediction coefficient for the true value pixel in the (i-1)th row and jth column, and can be 0.4. This represents the actual pixel value in the i-th row and j-1-th column; This represents the prediction coefficient for the true value pixel in the i-th row and (j-1)-th column, and can be 0.3. This represents the actual pixel value in the (i-1)th row and (j-1)th column; The prediction coefficient represents the true value pixel in the (i-1)th row and (j-1)th column, and can be 0.3; This represents the actual pixel value in the i-th row and (j-2)-th column; This represents the prediction coefficient for the true value pixel in the i-th row and (j-2)-th column, and can be 0.15. This represents the offset, which can be 0.8.

[0046] For example, for a DICOM file with X-ray modal characteristics, the corresponding compression strategy can be to sequentially perform Lempel-Ziv 77 (LZ77) compression and arithmetic encoding on the DICOM file. The compression window for LZ77 compression can be set to 2048 bytes.

[0047] S140. Based on the compression strategy, the data content in the DICOM file is compressed to obtain compressed data. The compressed data is then layered, encapsulated, and encrypted before transmission.

[0048] The compressed data refers to the lossless compression of data content from a DICOM file. A DICOM file can be input into a compression model for compression processing to obtain compressed data. The compressed data can be layered and encapsulated according to a preset layering and encapsulation protocol. The compressed data can also be encrypted during transmission using a preset encryption protocol. Furthermore, the layered and encapsulated compressed data can be encrypted during transmission, for example, by transmitting the layered and encapsulated compressed data according to an encryption protocol.

[0049] Specifically, the DICOM file is input into the compression model for compression processing to obtain compressed data. The compressed data is then encapsulated according to a preset layered encapsulation protocol and transmitted through a preset encryption protocol, achieving lightweight transmission of compressed data and improving the transmission efficiency and security of compressed data.

[0050] Optionally, the method further includes: obtaining the data source of the DICOM file, the performance indicators of the device, and the service priority; and matching the configuration conditions corresponding to each compression strategy in the second compression configuration file based on the data characteristics of the DICOM file, the data source of the DICOM file, the performance indicators of the device, and the service priority to determine the compression strategy adapted to the DICOM file.

[0051] The data source represents the origin of the DICOM file. Different DICOM files can originate from different image acquisition devices. Device performance metrics include, but are not limited to, the memory usage and CPU load of the image acquisition device. Service priority represents the urgency of the DICOM file. Service priority can be determined based on the service type. For example, the service priority for emergency cases is high, while the service priority for general outpatient cases is low. The second compression configuration file stores the compression strategy and the matching rules for those strategies. The second compression configuration file can be pre-configured. Configuration conditions are the matching rules adapted to the compression strategy. The compression strategy adapted to the DICOM file can also be determined based on the second compression configuration file. For example, the data characteristics of the DICOM file, the data source of the DICOM file, the device performance metrics, and the configuration conditions corresponding to each compression strategy in the second compression configuration file can be matched. When the data characteristics of the DICOM file, the data source of the DICOM file, the device performance metrics, and the service priority meet the configuration conditions, the compression strategy corresponding to those configuration conditions is used as the compression strategy adapted to the DICOM file.

[0052] Specifically, the data characteristics of the DICOM file, the data source of the DICOM file, the performance indicators of the device, and the service priority are matched with the configuration conditions corresponding to each compression strategy in the second compression configuration file. When the data characteristics of the DICOM file, the data source of the DICOM file, the performance indicators of the device, and the service priority meet the configuration conditions, the compression strategy corresponding to the configuration conditions is used as the compression strategy adapted to the DICOM file. This achieves accurate determination of the compression strategy and helps improve the compatibility between DICOM files and compression strategies.

[0053] The technical solution of this embodiment achieves the unification of DICOM files by acquiring them, performing standardized preprocessing and compression requirement detection, thus providing unified data support for subsequent analysis and processing. When compression is required for DICOM files, the solution identifies their data characteristics, including at least one of the following: modal characteristics of image data, window level, bit depth, image frame count, and pixel-level features, providing comprehensive data support for subsequent analysis and processing. Based on these data characteristics, the solution determines the appropriate compression strategy for the DICOM file, achieving precise strategy determination and providing accurate data support for lossless compression. Finally, the solution compresses the data content within the DICOM file based on the compression strategy, obtaining compressed data. This compressed data is then layered, encapsulated, and encrypted for transmission, achieving lossless compression of the DICOM file, ensuring its quality, and providing comprehensive data support for subsequent decision-making.

[0054] Example 2

[0055] Figure 2 This is a flowchart of a DICOM file processing method provided in Embodiment 2 of the present invention. This embodiment is a refinement of the above embodiments. Based on the foregoing embodiments, it provides a more detailed explanation of the standardized preprocessing and compression requirement detection of DICOM files. For specific implementation details, please refer to the technical solution of this embodiment. Technical terms that are the same as or corresponding to those in the above embodiments will not be repeated here. Figure 2 As shown, the method specifically includes the following steps:

[0056] S210. Obtain the DICOM file; parse the transmission identifier in the DICOM file, which includes a device identifier and a status identifier. The device identifier represents the data source of the DICOM file that produced it, and the status identifier represents the compression status of the data content in the DICOM file. Based on the device identifier, match it in the mapping relationship between devices and encoding rules to determine the standardized encoding rule corresponding to the DICOM file. Based on the standardized encoding rule, standardize the data content of the DICOM file and perform compression requirement detection on the DICOM file based on the status identifier.

[0057] The transmission identifier is a structured identifier representing the transmission attributes of a DICOM file. The transmission identifier includes a device identifier and a status identifier. The device identifier represents the data source that generated the DICOM file, including but not limited to core image acquisition equipment and image processing equipment. The device identifier can use different types of identifiers; for example, it can include numeric identifiers and alphabetic identifiers. For example, the device identifier for a CT device data source can be 1, for an MRI device data source can be 2, and for an ultrasound device data source can be 3. The status identifier represents the compression status of the data content in the DICOM file, which can include uncompressed and compressed. The status identifier includes at least one of numbers, letters, and special characters. Different compression statuses correspond to different status identifiers. For example, the status identifier for an uncompressed state is 'a', and the status identifier for a compressed state is 'b'. The transmission identifier can be obtained by parsing the DICOM file. For example, the DICOM file can be input into a trained transmission identifier parsing model for processing to obtain the transmission identifier in the DICOM file. The transmission identifier parsing model includes, but is not limited to, a neural network model. The standardized encoding rules are the encoding specifications for the DICOM file. Different data sources correspond to different standardized encoding rules. The standardized encoding rule corresponding to the device source is determined by matching the device identifier with the mapping relationship between devices and encoding rules. The data content of the DICOM file is then standardized and encoded according to the standardized encoding rule, achieving standardized preprocessing of the DICOM file. Compression requirement detection of the DICOM file can be performed by matching the status identifier with the compression status mapping relationship to determine the corresponding compression status of the DICOM file, and by matching the compression status with the compression requirement mapping relationship to determine the compression requirements of the DICOM file.

[0058] Specifically, images of the inspected object are acquired using image acquisition equipment to obtain DICOM files. These DICOM files are then input into a trained transmission identifier resolution model for processing, yielding transmission identifiers within the DICOM files. Device identifiers are matched against the device-to-encoding rule mapping to determine the standardized encoding rule corresponding to the device source. The data content of the DICOM files is then standardized according to the standardized encoding rule, achieving standardized encoding of the DICOM files and providing a unified data foundation for subsequent analysis. Finally, the compression status of the DICOM file is determined by matching the status identifier against the compression status mapping, and the compression requirements of the DICOM file are determined by matching the compression status against the compression requirement mapping, providing data support for subsequent processing.

[0059] Optionally, the compression requirement detection of the DICOM file is performed based on the status identifier, including: if the status identifier is the first identifier, it is determined that the DICOM file has a compression requirement, the first identifier indicating that the data content of the DICOM file is not compressed; if the status identifier is the second identifier, the second identifier indicating that the data content of the DICOM file has been compressed, the compression ratio and / or compression type of the DICOM file are determined, and if the compression ratio of the DICOM file is less than the target compression ratio and / or the compression type is lossy compression, it is determined that the DICOM file has a compression requirement.

[0060] The first identifier indicates that the DICOM file's data content is uncompressed. When the first identifier is present, the DICOM file requires compression. The second identifier indicates that the DICOM file's data content has been compressed. The compression ratio indicates the degree of data reduction after compression. The compression ratio can be determined by calculating the ratio between the compressed data volume and the uncompressed data volume. When the second identifier is present, the ratio between the compressed and uncompressed data volumes is used as the compression ratio. The compression type indicates the integrity of the compressed DICOM file. Compression types include lossy compression and lossless compression. When the DICOM file's data content has been compressed, the DICOM file carries a compression type identifier, and the compression type is determined based on this identifier. The target compression ratio is a pre-set compression ratio threshold. When the DICOM file's compression ratio is less than the target compression ratio, the DICOM file requires compression. When the DICOM file's compression type is lossy compression, the DICOM file requires compression.

[0061] Specifically, when the status identifier is the first identifier, the DICOM file requires compression; when the status identifier is the second identifier, the ratio between the compressed data volume and the uncompressed data volume of the DICOM file is calculated, and this ratio is used as the compression ratio of the DICOM file. Alternatively, if the data content of the DICOM file has already been compressed, the DICOM file carries a compression type identifier, and the compression type of the DICOM file is determined based on this identifier. When the compression ratio of the DICOM file is less than the target compression ratio, the DICOM file requires compression. Furthermore, when the compression type of the DICOM file is lossy compression, the DICOM file requires compression. This process implements DICOM file compression requirement detection, providing comprehensive data support for subsequent DICOM file compression.

[0062] S220. When there is a need to compress DICOM files, identify the data characteristics of the DICOM files. The data characteristics include at least one of the following: modal characteristics of image data, window level, bit depth, number of image frames, and pixel-level characteristics.

[0063] S230. Determine the compression strategy suitable for DICOM files based on the data characteristics of DICOM files.

[0064] S240. Based on the compression strategy, the data content in the DICOM file is compressed to obtain compressed data. The compressed data is then layered, encapsulated, and encrypted before transmission.

[0065] Optionally, the compressed data is encapsulated in layers, including: encapsulating the compressed data based on a layered encapsulation protocol to obtain encapsulated data packets, wherein the inner layer of the encapsulated data packet is the data payload layer, which includes compressed data, integrity check code, compression algorithm identifier and data length; the middle layer of the encapsulated data packet is the information header layer, which includes sequence number, total number of packets, data type and target transmission syntax; and the outer layer of the encapsulated data packet is the transport protocol layer, which includes network transmission information.

[0066] The layered encapsulation protocol can be pre-configured. The encapsulated data packet is the data packet obtained by layering compressed data. The encapsulated data packet can include inner, middle, and outer layers. Optionally, the inner layer of the encapsulated data packet is the data payload layer, which includes compressed data, an integrity checksum, a compression algorithm identifier, and the data length. The data payload layer is the innermost layer of the encapsulated data packet. The integrity checksum is information indicating whether the compressed data is complete. The integrity checksum can be obtained by processing the compressed data according to a preset checksum algorithm. The compression algorithm identifier is used to characterize the compression strategy used to compress the data content in the DICOM file. Different compression strategies correspond to different compression algorithm identifiers. The data length is the total length of the compressed data in bytes.

[0067] The information header layer is the intermediate layer encapsulating data packets. It wraps around the inner data payload layer. The information header layer includes the sequence number, total number of packets, data type, and target transmission syntax. When the number of encapsulated data packets exceeds a preset threshold, to improve the stability of the encapsulated data packet transmission, the encapsulated data packet needs to be split into multiple sub-encapsulated data packets, each corresponding to a sequence number. The total number of packets represents the number of sub-encapsulated data packets after splitting the encapsulated data packet. The data type is used to represent the imaging type of the medical image data in the compressed data. The target transmission syntax is the parsing rule for the encapsulated data packets.

[0068] The transport protocol layer is the interface for encapsulating data packets and the transmission environment. It wraps around the header layer. The transport protocol layer includes network transmission information, which includes, but is not limited to, the transport protocol version number, the sender's unique identification information, the receiver's unique identification information, the transmission timeout, the network protocol identifier, and the transport protocol checksum.

[0069] Specifically, encapsulating compressed data according to a preset layered encapsulation protocol helps improve the reliability of compressed data transmission and the accuracy of parsing.

[0070] Optionally, the method further includes: obtaining the network bandwidth status of the device; dynamically fragmenting the encapsulated data packets according to the network bandwidth status; setting a fragment identifier for each fragment of the encapsulated data packet; and sequentially transmitting the fragments of the encapsulated data packet to the receiving end; recording the first transmission status of the fragments of the encapsulated data packet and receiving the second transmission status of the fragments of the encapsulated data packet fed back by the receiving end; and resuming interrupted transmission of abnormal fragments according to the first and second transmission statuses until the transmission of the encapsulated data packet is completed.

[0071] The network bandwidth status refers to the real-time bandwidth of the image acquisition device. This status can be obtained through real-time bandwidth monitoring of the device. Since the device's network bandwidth status is variable, to improve the stability of encapsulated data packet transmission, the encapsulated data packets can be dynamically sliced ​​into multiple fragments. Each fragment corresponds to a fragment identifier, which can be used to distinguish different fragments. For example, the fragment size of the encapsulated data packet can be determined based on the network bandwidth status and fragmentation rules. For instance, when the network bandwidth status is greater than or equal to a first preset bandwidth, the fragment size can be 10 Mbps, and the first preset bandwidth can be set to 10 Mbps; when the network bandwidth status is less than the first preset bandwidth but greater than or equal to a second preset bandwidth, the fragment size can be 5 Mbps, and the first preset bandwidth can be set to 2 Mbps; when the network bandwidth status is less than the second preset bandwidth, the fragment size can be 1 Mbps, and the first preset bandwidth can be set to 2 Mbps. The first and second preset bandwidths can be set according to requirements, with the second preset bandwidth being less than the first preset bandwidth. The fragments of the encapsulated data packet are transmitted sequentially to the receiving end, which can be done in the order of the fragments. The receiving end includes, but is not limited to, a server. A first transmission state represents the transmission status of the encapsulated data packet fragments. The first transmission state includes, but is not limited to, successful transmission. The first transmission state of the encapsulated data packet fragments is recorded when they are transmitted. A second transmission state represents whether the receiving end has successfully received the encapsulated data packet fragments. The second transmission state can include successful reception and reception failure. After receiving the encapsulated data packet fragments, the receiving end triggers the second transmission state feedback logic, generates a second transmission state, and feeds it back to the sending end, which includes, but is not limited to, a front-end processor. When the receiving end successfully receives the encapsulated data packet fragments, the second transmission state of the encapsulated data packet fragments fed back by the receiving end is successful reception; when the receiving end fails to successfully receive the encapsulated data packet fragments, the second transmission state of the encapsulated data packet fragments fed back by the receiving end is reception failure. Abnormal fragments are encapsulated data packet fragments that failed to transmit. Abnormal fragments include, but are not limited to, encapsulated data packet fragments that were not completely received by the receiving end and encapsulated data packet fragments that were not correctly received by the receiving end. Abnormal fragments can be determined based on a first transmission state and a second transmission state. For example, for any fragment of an encapsulated data packet, if the first transmission state is "successful transmission" and the second transmission state is "failed reception," the fragment of the encapsulated data packet is considered an abnormal fragment. The breakpoint resume logic is triggered, and the fragment of the encapsulated data packet is retransmitted until the entire encapsulated data packet has been transmitted.

[0072] Specifically, the network bandwidth status of the device is obtained through real-time bandwidth monitoring; the fragment size of the encapsulated data packet is determined based on the network bandwidth status and fragmentation rules; a fragment identifier is set for each fragment of the encapsulated data packet; the fragments of the encapsulated data packet are transmitted to the receiving end in the order of fragmentation; the first transmission status of the fragment of the encapsulated data packet is recorded when it is sent; after the receiving end receives the fragment of the encapsulated data packet, it triggers the second transmission status feedback logic to generate a second transmission status and feeds the second transmission status back to the sending end; abnormal fragments are identified based on the first and second transmission statuses, triggering the breakpoint resume logic to resend the fragment of the encapsulated data packet until the entire encapsulated data packet is transmitted. This eliminates the need to transmit all fragments of the encapsulated data packet, effectively reducing transmission latency and improving transmission efficiency.

[0073] Based on the above embodiments, the method further includes: generating a first target integrity check code based on the compressed data; determining a first check result based on the integrity check code and the first target integrity check code, wherein the first check result characterizes the consistency between the compressed data and the DICOM file.

[0074] Based on the above embodiments, the method further includes: determining a decompression strategy based on a compression algorithm identifier; and decompressing the compressed data based on the decompression strategy to obtain a target DICOM file, wherein the target DICOM file is a DICOM file obtained after decompressing the compressed data.

[0075] Based on the above embodiments, the method further includes: the receiving end generating a second target integrity check code based on the target DICOM file; determining a second check result based on the integrity check code and the second target integrity check code, wherein the second check result characterizes the consistency between the target DICOM file and the DICOM file.

[0076] Based on the above embodiments, the method further includes: the receiving end transmitting the target DICOM file to the cloud; the cloud generating a third target integrity check code based on the received target DICOM file, determining a third check result based on the third target integrity check code and the integrity check code, and the third check result characterizing the consistency between the DICOM file and the target DICOM file in the cloud.

[0077] The technical solution of this embodiment involves acquiring a DICOM file; parsing the transmission identifier in the DICOM file, which includes a device identifier and a status identifier. The device identifier represents the data source of the DICOM file, and the status identifier represents the compression status of the data content in the DICOM file. Based on the device identifier, a matching process is performed in the device-to-encoding rule mapping relationship to determine the standardized encoding rule corresponding to the DICOM file. The data content of the DICOM file is then standardized and encoded based on the standardized encoding rule, providing a unified data foundation for subsequent analysis. Compression requirement detection is performed on the DICOM file based on the status identifier, providing data support for subsequent processing. The solution also addresses the issue of compression requirements in the DICOM file. When required, the system identifies the data characteristics of DICOM files, including at least one of the following: modal characteristics of image data, window level, bit depth, image frame count, and pixel-level characteristics. This provides comprehensive data support for subsequent analysis and processing. Based on the data characteristics of DICOM files, the system determines the appropriate compression strategy, achieving precise determination of the compression strategy and providing accurate data support for lossless compression of DICOM files. Based on the compression strategy, the system compresses the data content in the DICOM files to obtain compressed data. The compressed data is then layered, encapsulated, and encrypted for transmission, achieving lossless compression of DICOM files and ensuring their quality. This provides comprehensive data support for subsequent decision-making.

[0078] Example 3

[0079] Figure 3 This is a schematic diagram of the structure of a DICOM file processing device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes a detection module 310, a data feature recognition module 320, a compression strategy determination module 330, and a layered encapsulation and encrypted transmission module 340.

[0080] The system includes: a detection module 310 for acquiring DICOM files, performing standardized preprocessing and compression requirement detection on the DICOM files; a data feature recognition module 320 for identifying the data features of DICOM files when compression is required, including at least one of the following: modal features of image data, window level, bit depth, image frame count, and pixel-level features; a compression strategy determination module 330 for determining the appropriate compression strategy for the DICOM file based on its data features; and a layered encapsulation and encrypted transmission module 340 for compressing the data content in the DICOM file based on the compression strategy to obtain compressed data, and then performing layered encapsulation and encrypted transmission on the compressed data.

[0081] The technical solution of this embodiment obtains DICOM files through a detection module, performs standardized preprocessing and compression requirement detection on the DICOM files, and achieves uniformity of DICOM files, providing unified data support for subsequent analysis and processing. Through a data feature recognition module, when DICOM files have compression requirements, it identifies the data features of the DICOM files. These data features include at least one of the following: modal features of image data, window level, bit depth, image frame count, and pixel-level features, providing comprehensive data support for subsequent analysis and processing. Through a compression strategy determination module, it determines the appropriate compression strategy for the DICOM file based on its data features, achieving accurate determination of the compression strategy and providing accurate data support for lossless compression of DICOM files. Through a layered encapsulation and encrypted transmission module, it compresses the data content of the DICOM file based on the compression strategy to obtain compressed data. The compressed data is then layered encapsulated and encrypted for transmission, achieving lossless compression of the DICOM file, ensuring the quality of the DICOM file, and providing comprehensive data support for subsequent decision-making.

[0082] Optionally, based on the above embodiments, the detection module 310 is further configured to: parse the transmission identifier in the DICOM file, the transmission identifier including a device identifier and a status identifier, the device identifier representing the data source of the DICOM file that produced the DICOM file, and the status identifier representing the compression status of the data content in the DICOM file; match the device identifier in the mapping relationship between devices and encoding rules to determine the standardized encoding rule corresponding to the DICOM file; perform standardized encoding on the data content of the DICOM file based on the standardized encoding rule; and perform compression requirement detection on the DICOM file based on the status identifier.

[0083] Optionally, the detection module 310 is further configured to: determine that the DICOM file has a compression requirement when the status identifier is the first identifier; the first identifier indicates that the data content of the DICOM file is not compressed; when the status identifier is the second identifier, the second identifier indicates that the data content of the DICOM file has been compressed, determine the compression ratio and / or compression type of the DICOM file, and if the compression ratio of the DICOM file is less than the target compression ratio and / or the compression type is lossy compression, then determine that the DICOM file has a compression requirement.

[0084] Optionally, the compression strategy determination module 330 is further configured to: match the data characteristics of the DICOM file with the data characteristic conditions corresponding to each compression strategy in the first compression configuration file to determine the compression strategy adapted to the DICOM file, wherein the data characteristic conditions corresponding to the compression strategy include at least one data characteristic adapted to the compression strategy.

[0085] Optionally, the compression strategy determination module 330 is also used to: obtain the data source of the DICOM file, the performance indicators of the device, and the service priority; and match the configuration conditions corresponding to each compression strategy in the second compression configuration file based on the data characteristics of the DICOM file, the data source of the DICOM file, the performance indicators of the device, and the service priority to determine the compression strategy adapted to the DICOM file.

[0086] Optionally, the layered encapsulation and encrypted transmission module 340 is further configured to: encapsulate compressed data based on a layered encapsulation protocol to obtain encapsulated data packets, wherein the inner layer of the encapsulated data packet is a data payload layer, which includes compressed data, integrity check code, compression algorithm identifier, and data length; the middle layer of the encapsulated data packet is an information header layer, which includes sequence number, total number of packets, data type, and target transmission syntax; and the outer layer of the encapsulated data packet is a transmission protocol layer, which includes network transmission information.

[0087] Optionally, the device further includes a packet encapsulation transmission module, used to: acquire the network bandwidth status of the device; dynamically fragment the packet encapsulation according to the network bandwidth status; set a fragment identifier for each fragment of the packet encapsulation; and sequentially transmit the fragments of the packet encapsulation to the receiving end; record the first transmission status of the fragments of the packet encapsulation, and receive the second transmission status of the fragments of the packet encapsulation fed back by the receiving end; and resume transmission of abnormal fragments according to the first and second transmission statuses until the transmission of the packet encapsulation is completed.

[0088] The DICOM file processing device provided in this embodiment of the invention can execute a DICOM file processing method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the method.

[0089] Example 4

[0090] Figure 4 This is a schematic diagram of the structure of an electronic device provided in Embodiment 4 of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0091] like Figure 4As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0092] Multiple components in electronic device 10 are connected to input / output (I / O) interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of monitors, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0093] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as a DICOM file processing method.

[0094] In some embodiments, a DICOM file processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via read-only memory (ROM) 12 and / or communication unit 19. When the computer program is loaded into random access memory (RAM) 13 and executed by processor 11, one or more steps of the DICOM file processing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform a DICOM file processing method by any other suitable means (e.g., by means of firmware).

[0095] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transferring data and instructions to the storage system, the at least one input device, and the at least one output device.

[0096] A computer program for implementing a DICOM file processing method of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer program causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer program can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0097] Example 5

[0098] Embodiment 5 of the present invention also provides a computer-readable storage medium storing computer instructions for causing a processor to execute a DICOM file processing method, the method comprising:

[0099] The process involves acquiring a DICOM file, performing standardized preprocessing and compression requirement detection, identifying data characteristics of the DICOM file (including at least one of the following: image data modal characteristics, window level, bit depth, image frame count, and pixel-level features), determining a suitable compression strategy based on the data characteristics, compressing the data content of the DICOM file according to the compression strategy, obtaining compressed data, and then performing layered encapsulation and encrypted transmission of the compressed data.

[0100] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0101] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0102] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0103] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0104] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0105] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for processing DICOM files, characterized in that, include: Obtain the DICOM file, and perform standardized preprocessing and compression requirement detection on the DICOM file; When the DICOM file requires compression, the data characteristics of the DICOM file are identified. The data characteristics include at least one of the modal characteristics of the image data, window level, bit depth, number of image frames, and pixel-level characteristics. The compression strategy adapted to the DICOM file is determined based on the data characteristics of the DICOM file; The data content in the DICOM file is compressed based on the compression strategy to obtain compressed data, and the compressed data is then layered, encapsulated, and encrypted before transmission.

2. The method according to claim 1, characterized in that, The standardization preprocessing and compression requirement detection of the DICOM file includes: The transfer identifier in the DICOM file is parsed. The transfer identifier includes a device identifier and a status identifier. The device identifier represents the data source that produced the DICOM file, and the status identifier represents the compression status of the data content in the DICOM file. Based on the device identifier, a matching is performed in the device-to-encoding rule mapping relationship to determine the standardized encoding rule corresponding to the DICOM file, and the data content of the DICOM file is standardized and encoded based on the standardized encoding rule; Compression requirements are detected for the DICOM file based on the status identifier.

3. The method according to claim 2, characterized in that, The step of detecting the compression requirement of the DICOM file based on the status identifier includes: If the status identifier is the first identifier, it is determined that the DICOM file requires compression; the first identifier indicates that the data content of the DICOM file is not compressed. When the status identifier is the second identifier, the second identifier indicates that the data content of the DICOM file has been compressed. The compression ratio and / or compression type of the DICOM file are determined. If the compression ratio of the DICOM file is less than the target compression ratio and / or the compression type is lossy compression, it is determined that the DICOM file has a compression requirement.

4. The method according to claim 1, characterized in that, The step of determining the compression strategy adapted to the DICOM file based on the data characteristics of the DICOM file includes: The data characteristics of the DICOM file are matched with the data characteristic conditions corresponding to each compression strategy in the first compression configuration file to determine the compression strategy that the DICOM file is adapted to. The data characteristic conditions corresponding to the compression strategy include at least one data characteristic that is adapted to the compression strategy.

5. The method according to claim 1, characterized in that, The method further includes: Obtain the data source, device performance metrics, and service priority of the DICOM file; Based on the data characteristics of the DICOM file, the data source of the DICOM file, the performance indicators of the device, and the service priority, the configuration conditions corresponding to each compression strategy in the second compression configuration file are matched to determine the compression strategy that the DICOM file is adapted to.

6. The method according to claim 1, characterized in that, The layered encapsulation of the compressed data includes: The compressed data is encapsulated using a layered encapsulation protocol to obtain an encapsulated data packet. The inner layer of the encapsulated data packet is the data payload layer, which includes the compressed data, integrity check code, compression algorithm identifier, and data length. The middle layer of the encapsulated data packet is the information header layer, which includes sequence number, total number of packets, data type, and target transmission syntax. The outer layer of the encapsulated data packet is the transport protocol layer, which includes network transmission information.

7. The method according to claim 6, characterized in that, The method further includes: The network bandwidth status of the device is obtained, and the encapsulated data packet is dynamically fragmented according to the network bandwidth status. A fragmentation identifier is set for each fragment of the encapsulated data packet, and the fragments of the encapsulated data packet are transmitted to the receiving end in sequence. Record the first transmission status of the fragments of the encapsulated data packet, and receive the second transmission status of the fragments of the encapsulated data packet fed back by the receiving end; resume transmission of abnormal fragments according to the first transmission status and the second transmission status until the transmission of the encapsulated data packet is completed.

8. A DICOM file processing device, characterized in that, include: The detection module is used to acquire the DICOM file, perform standardized preprocessing and compression requirement detection on the DICOM file; The data feature recognition module is used to identify the data features of the DICOM file when the DICOM file has a compression requirement. The data features include at least one of the modal features of the image data, window level, bit depth, number of image frames, and pixel-level features. A compression strategy determination module is used to determine the compression strategy suitable for the DICOM file based on the data characteristics of the DICOM file; The layered encapsulation and encrypted transmission module is used to compress the data content in the DICOM file based on the compression strategy to obtain compressed data, and to perform layered encapsulation and encrypted transmission on the compressed data.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the DICOM file processing method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the DICOM file processing method according to any one of claims 1-7.

Images