CN116302681A - File management method, device, equipment and medium of in-vitro diagnosis equipment - Google Patents
File management method, device, equipment and medium of in-vitro diagnosis equipment Download PDFInfo
- Publication number
- CN116302681A CN116302681A CN202310062316.2A CN202310062316A CN116302681A CN 116302681 A CN116302681 A CN 116302681A CN 202310062316 A CN202310062316 A CN 202310062316A CN 116302681 A CN116302681 A CN 116302681A
- Authority
- CN
- China
- Prior art keywords
- file
- backed
- marking
- integrity
- backup
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application relates to a file management method, a device, equipment and a medium based on in-vitro diagnostic equipment, wherein the method comprises the following steps: acquiring a configuration file, and performing head marking and tail marking on the configuration file to obtain a marking file, wherein the marking file comprises head marking marks and tail marking marks; when a file backup condition is triggered, acquiring a file to be backed up as a file to be backed up; based on the head mark marks and the tail mark marks, carrying out integrity judgment on the file to be backed up to obtain a first judgment result; and if the first judgment result shows that the file to be backed up has integrity, backing up the file to be backed up to obtain the backup file. The invention judges the integrity of the configuration file to backup the configuration file with the integrity, thereby avoiding the condition of losing file information when power is off in the process of writing the file.
Description
Technical Field
The present application relates to the field of medical devices, and in particular, to a method, an apparatus, a device, and a medium for file management of an in vitro diagnostic device.
Background
Currently, in the file reading and writing of software in the in-vitro diagnosis industry, there are two main modes at present, one is to read and write in a mode of accessing a database, and the other is to read and write a text type file. In general, if there is a frequent need for modification of data, especially in a scenario where there is a requirement for consistency (e.g., a transaction system), it is more appropriate to use a database; for a scene (such as an analysis system) without data consistency requirement, the file can be used for storing data, the file has no computing capacity, the traditional hard coding mode is complex, and if the computing capacity is enhanced, the file storage is more advantageous by virtue of the efficient reading and writing capacity and the flexible and manageable characteristics of the file.
Therefore, the file storage has great advantages in terms of configuration files, setting items and the like of the existing in-vitro diagnosis equipment, but has a fatal defect of outage damage, the safety of the file storage is possibly sacrificed due to the performance advantage of the file storage, and if the outage condition occurs in the writing process, the file information can be lost.
Disclosure of Invention
The embodiment of the application aims to provide a file management method, device, equipment and medium based on in-vitro diagnosis equipment, which avoid the condition that file information is lost when power failure occurs in the process of writing files.
In order to solve the above technical problems, an embodiment of the present application provides a file management method based on an in vitro diagnostic device, including:
acquiring a configuration file, and performing head marking and tail marking on the configuration file to obtain a marking file, wherein the marking file comprises head marking marks and tail marking marks;
when a file backup condition is triggered, acquiring a file to be backed up as a file to be backed up, wherein the file backup condition comprises any one of when the configuration file is modified, when the in-vitro diagnosis equipment enters a dormancy process and after the configuration file is upgraded;
based on the head mark marks and the tail mark marks, carrying out integrity judgment on the file to be backed up to obtain a first judgment result;
and if the first judging result shows that the file to be backed up has the integrity, backing up the file to be backed up to obtain a backup file.
In order to solve the above technical problems, an embodiment of the present application provides a file management apparatus based on an in vitro diagnostic device, including:
the file marking module is used for obtaining a configuration file, marking the head part and the tail part of the configuration file, and obtaining a marking file;
the module to be backed up is used for acquiring the file to be backed up as the file to be backed up when the file backup condition is triggered;
the integrity judging module is used for carrying out integrity judgment on the file to be backed up based on the head mark marks and the tail mark marks to obtain a first judging result;
and the backup module is used for backing up the file to be backed up to obtain a backup file if the first judgment result shows that the file to be backed up has integrity.
In order to solve the technical problems, the invention adopts a technical scheme that: there is provided an in-vitro diagnostic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the in-vitro diagnostic device-based file management method according to any one of the above when executing the computer program.
In order to solve the technical problems, the invention adopts a technical scheme that: a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the in vitro diagnostic device-based file management method of any one of the above.
The embodiment of the invention provides a file management synchronization method, device, equipment and medium based on in-vitro diagnosis equipment. The method comprises the following steps: acquiring a configuration file, and performing head marking and tail marking on the configuration file to obtain a marking file, wherein the marking file comprises head marking marks and tail marking marks; when a file backup condition is triggered, acquiring a file to be backed up as a file to be backed up, wherein the file backup condition comprises any one of when a configuration file is modified, in-vitro diagnosis equipment enters a dormancy process and after the configuration file is upgraded; based on the head mark marks and the tail mark marks, carrying out integrity judgment on the file to be backed up to obtain a first judgment result; and if the first judgment result shows that the file to be backed up has integrity, backing up the file to be backed up to obtain the backup file. The embodiment of the invention marks the head and the tail of the configuration file, and judges the integrity of the configuration file based on the marking marks of the file so as to backup the configuration file with the integrity, thereby avoiding the condition of file information loss when power is off in the process of writing the file.
Drawings
For a clearer description of the solution in the present application, a brief description will be given below of the drawings that are needed in the description of the embodiments of the present application, it being obvious that the drawings in the following description are some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art.
FIG. 1 is a flowchart of an implementation of a file management method flow based on an in vitro diagnostic device according to an embodiment of the present application;
FIG. 2 is a flowchart of an implementation of a sub-process in an in vitro diagnostic device-based file management method according to an embodiment of the present application;
FIG. 3 is a flowchart of still another implementation of a sub-process in the in-vitro diagnostic device-based file management method provided in an embodiment of the present application;
FIG. 4 is a flowchart of still another implementation of a sub-process in the in-vitro diagnostic device-based file management method provided in an embodiment of the present application;
FIG. 5 is a flowchart of still another implementation of a sub-process in the in-vitro diagnostic device-based file management method provided in an embodiment of the present application;
FIG. 6 is a flowchart of still another implementation of a sub-process in the in-vitro diagnostic device-based file management method provided in an embodiment of the present application;
FIG. 7 is a flowchart of still another implementation of a sub-process in the in-vitro diagnostic device-based file management method provided in an embodiment of the present application;
FIG. 8 is a schematic diagram of a file management apparatus based on an in vitro diagnostic device according to an embodiment of the present application;
fig. 9 is a schematic diagram of an in vitro diagnostic device provided in an embodiment of the present application.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the applications herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having" and any variations thereof in the description and claims of the present application and in the description of the figures above are intended to cover non-exclusive inclusions. The terms first, second and the like in the description and in the claims or in the above-described figures, are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
In order to better understand the technical solutions of the present application, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings.
The present invention will be described in detail with reference to the drawings and embodiments.
It should be noted that, the in vitro diagnostic device-based file management method provided in the embodiments of the present application is generally executed by a server, and accordingly, the in vitro diagnostic device-based file management apparatus is generally configured in the server.
Referring to fig. 1, fig. 1 illustrates one embodiment of a method for file management based on an in vitro diagnostic device.
It should be noted that, if there are substantially the same results, the method of the present invention is not limited to the flow sequence shown in fig. 1, and the method includes the following steps:
s1: and obtaining a configuration file, and performing head marking and tail marking on the configuration file to obtain a marking file, wherein the marking file comprises head marking marks and tail marking marks.
Specifically, the configuration file refers to a file containing configuration information of the in vitro diagnostic device, and the configuration file is marked with a head and a tail so as to be divided into different blocks. The configuration file includes a header section at a header position of the file, a trailer section at a trailer position of the file, and a content section between the header section and the trailer section. The head section is marked with a head mark print, and the tail mark print is marked with a tail mark print. It should be noted that, since the content chunk can be determined only after the header and the trailer of the configuration file are marked, that is, the configuration file is composed of the header chunk, the trailer chunk and the content chunk, and the header chunk and the trailer chunk are determined, and the content chunk is correspondingly determined, marking on the content chunk is not required.
Referring to fig. 2, fig. 2 shows a specific embodiment of step S1, which is described in detail as follows:
s11: and acquiring a configuration file.
S12: the header and trailer of the configuration file are identified.
S13: and marking the head of the configuration file by adopting characters of a front part in the ASCII code, and marking the tail of the configuration file by adopting characters of a rear part in the ASCII code to obtain a marked file.
S14: and storing the mark file in a first preset path.
Specifically, after the configuration file is obtained, the header and the trailer of the configuration file are set according to development habits of a developer, for example, the first 10% of the configuration file is used as the header, and the second 10% is used as the trailer, which is not particularly limited herein.
In a specific embodiment, the head and tail of the configuration file are identified, then the head of the configuration file is marked by the character before "a" in the ASCII code preamble, the tail of the configuration file is marked by the character after "z" in the ASCII code postamble, and then the marked file is stored as a marking file in the first preset path. It should be noted that, the first preset path is a designated path set by a developer according to actual conditions, and the marked configuration file is stored in the designated path, so that detection and search of the head mark print and the tail mark print in subsequent steps are facilitated, and the efficiency of integrity detection is improved.
Furthermore, when marking the head and tail of the configuration file by adopting the characters in the ASCII code, a developer can select one of the characters in the range as marking characters according to the habit, but once the marking characters are selected, the marking characters are not replaced. For example, if "@" before "a" is selected as the head mark print character and "_" after "z" is selected as the tail mark print character, only "@" can be used for head marking and "_" can be used for tail marking in the subsequent head and tail marks.
S2: when the file backup condition is triggered, acquiring a file to be backed up as a file to be backed up, wherein the file backup condition comprises any one of when the configuration file is modified, when the in-vitro diagnosis equipment enters a dormancy process and after the configuration file is upgraded.
Specifically, when the configuration file is modified, the in-vitro diagnosis device enters a sleep process or after the configuration file is updated, the configuration file is a file to be backed up, and the configuration file is used as a file to be backed up.
Further, when the configuration file is modified, if the modification content has errors or improper conditions, the device may not be used normally, so when the modification occurs, the configuration file needs to be backed up, so that the configuration file is restored to restore normal use when the device cannot be used normally. When power is off in the process of using the configuration file, the in-vitro diagnosis equipment enters the dormancy process, and the configuration file is easy to damage, lose and the like, so that the equipment cannot be used normally, and the configuration file needs to be backed up at the moment. After the configuration file is upgraded, if the upgrade is abnormal, the equipment cannot be normally used, and the configuration file needs to be backed up at the moment, so that the configuration file can be restored to restore normal use when the upgrade is abnormal.
Referring to fig. 3, fig. 3 shows a specific embodiment of step S2, which is described in detail as follows:
s21: when the file backup condition is triggered, the files to be backed up are acquired.
S22: and judging whether the file to be backed up is a writable file or not.
S23: if the file to be backed up is a writable file, the file to be backed up is taken as the file to be backed up.
Specifically, when the file backup condition is triggered, a file to be backed up is acquired, and then whether the file to be backed up is a writable file is judged. If the file to be backed up is a writable file, the writable file is used as the file to be backed up, and the subsequent backup operation is carried out. If the file to be backed up is a non-writable file, stopping the backup operation and storing the file to a first preset path.
In a specific embodiment, an is_write () function in PHP may be used to determine whether the file to be backed up is writable, if the function returns a result of "TRUE", the file to be backed up is a writable file, and then the writable file is used as the file to be backed up, and a subsequent backup operation is performed.
Further, by judging whether the file to be backed up is a writable file or not, then carrying out subsequent backup on the writable file and not backing up a non-writable file, the efficiency of backup work is improved.
S3: and based on the head mark marks and the tail mark marks, carrying out integrity judgment on the file to be backed up, and obtaining a first judgment result.
Specifically, because of the computer storage principle, the file content is stored in a logically continuous memory, and the addition, deletion and modification of the general file are performed sequentially, the integrity of the whole file content can be judged as long as the integrity of the file head mark and the file tail mark is ensured.
Referring to fig. 4, fig. 4 shows a specific embodiment of step S3, which is described in detail as follows:
s31: and traversing the files to be backed up in the first preset path for each file to be backed up, and detecting whether head mark marks and tail mark marks exist or not to obtain a detection result.
S32: and based on the detection result, carrying out integrity judgment on the file to be backed up, and obtaining a first judgment result.
Specifically, for each file to be backed up, head mark detection and tail mark detection are performed on the file in a first preset path, and if the head mark marks and the tail mark marks are detected to exist, judging that the file to be backed up has integrity. By directly detecting the head mark marks and the tail mark marks in the designated path, the detection efficiency is improved.
Referring to fig. 5, fig. 5 shows a specific embodiment of step S32, which is described in detail as follows:
s321: if the detection result is that the head mark marks and the tail mark marks exist in the file to be backed up, the first judgment result is that the file to be backed up has integrity.
S322: if the detection result is that the head mark and the tail mark exist in the file to be backed up, or if the detection result is that the head mark and the tail mark do not exist in the file to be backed up, the first judgment result is that the file to be backed up does not have integrity.
Specifically, the file to be backed up is determined to have integrity only if both the head mark print and the tail mark print are detected. It should be noted that, since the writing process of the file is performed sequentially, when the file is damaged, there are only two cases, for example, case one: the method has the advantages that the method lacks both file head and tail blocks; and a second case: only the end-of-file partition is missing. And when the head mark marks and the tail mark marks are detected to exist, the backup file is judged to have the integrity, and the subsequent backup operation is carried out. When the existence of the head mark marks and the existence of the tail mark marks are detected, or the existence of the head mark marks and the tail mark marks is not detected, judging that the file to be backed up does not have integrity, and not carrying out subsequent backup operation.
Referring to fig. 6, fig. 6 shows a specific embodiment after step S3, which is described in detail as follows:
S3A1: and if the first judgment result is that the file to be backed up does not have the integrity, acquiring the last state configuration file corresponding to the file to be backed up.
S3A2: and replacing the file to be backed up with the configuration file of the last state and storing the configuration file to the first preset path.
Specifically, if the file to be backed up does not have integrity, the subsequent backup operation is not performed on the file to be backed up, the last state configuration file corresponding to the file to be backed up is obtained from the first preset path, the last state configuration file is an initial configuration file or a file which is thick after the last time of integrity detection, the file to be backed up is replaced by the last state configuration file and is stored in the first preset path, and the influence of the configuration file which does not have integrity on the normal use of the in-vitro diagnostic equipment is avoided.
Further, the last state configuration file has a head mark and a tail mark, and when the backup is triggered next time, the last state configuration file has integrity, so that the last state configuration file can be backed up, and damage to the last state configuration file is avoided.
And S4, if the first judgment result shows that the file to be backed up has integrity, backing up the file to be backed up to obtain the backup file.
Specifically, if the existence of the head mark marks and the tail mark marks is detected in the file to be backed up, the file to be backed up is judged to have integrity, namely the file to be backed up is backed up, so that the problem that the file information is lost and cannot be recovered due to sudden power failure in the writing process of the file is avoided.
Furthermore, the configuration files are managed in a document mode, so that flexibility and manageability are greatly improved, for example, in the process of changing or upgrading the requirements, the original data structure is easy to modify without great change and change. The lead-in and lead-out are convenient, and the read-write is convenient. Compared with a database mode, the method has the advantages that the importing and exporting are more convenient, the reading and writing are easy, the coupling is much lower, and the reading and writing efficiency is much improved compared with the database mode. And by carrying out backup operation on the writable file, the condition that the information of the file is lost when power failure occurs in the process of writing the file is avoided.
Referring to fig. 7, fig. 7 shows a specific embodiment after step S4, which is described in detail as follows:
S4B1: and carrying out integrity judgment on the backup file to obtain a second judgment result.
S4B2: and if the second judgment result is that the backup file does not have the integrity, deleting the backup file, and re-backing up the file to be backed up until the backup file has the integrity.
S4B3: and storing the backup file in a second preset path.
Specifically, after the backup is completed to obtain the backup file, the integrity of the backup file is judged, if the backup file has the integrity, the backup is completed and the backup file is stored to a second preset path. If the backup file does not have the integrity, deleting the backup file and carrying out the backup again on the file to be backed up until the backup file obtained through the backup again has the integrity. The second preset path is a path set by the developer and dedicated to storing the backup file. By adopting the method, the integrity detection of the files to be backed up and the backed up can be realized, and the integrity of the files is fully ensured.
Further, when the file is used, integrity detection is performed on the file, and if the file is detected to have no integrity, a backup file corresponding to the file is obtained from a second preset path so as to restore the file.
In the embodiment, a configuration file is obtained, and head marking and tail marking are carried out on the configuration file to obtain a marking file, wherein the marking file comprises head marking marks and tail marking marks; when a file backup condition is triggered, acquiring a file to be backed up as a file to be backed up; based on the head mark marks and the tail mark marks, carrying out integrity judgment on the file to be backed up to obtain a first judgment result; and if the first judgment result shows that the file to be backed up has integrity, backing up the file to be backed up to obtain the backup file. The embodiment of the invention judges the integrity of the configuration file to backup the configuration file with the integrity, thereby avoiding the condition of file information loss when power failure occurs in the process of writing the file.
Referring to fig. 8, as an implementation of the method shown in fig. 1, the present application provides an embodiment of a file management apparatus 5 based on an in vitro diagnostic device, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 1, and the apparatus may be specifically applied to an in vitro diagnostic device.
As shown in fig. 8, the in-vitro diagnostic device-based file management apparatus 5 of the present embodiment includes: a file marking module 51, a module to be backed up 52, an integrity judging module 53 and a backup module 54, wherein:
the file marking module 51 is configured to obtain a configuration file, and perform head marking and tail marking on the configuration file to obtain a marked file;
the to-be-backed-up module 52 is configured to obtain a file to be backed up as a file to be backed up when a file backup condition is triggered;
an integrity judging module 53, configured to perform integrity judgment on the file to be backed up based on the head mark print and the tail mark print, so as to obtain a first judgment result;
and the backup module 54 is configured to backup the file to be backed up to obtain a backup file if the first determination result indicates that the file to be backed up has integrity.
Further, the file marking module 51 includes:
the acquisition unit is used for acquiring the configuration file;
an identification unit for identifying the head and tail of the configuration file;
the head-tail marking unit is used for marking the head of the configuration file by adopting characters of a front part in the ASCII code, and marking the tail of the configuration file by adopting characters of a rear part in the ASCII code to obtain a marking file;
and the mark storage unit is used for storing the mark file in the first preset path.
Further, the module to be backed up 52 includes:
the writable file judging unit is used for judging whether the file to be backed up is a writable file or not when the file backup condition is triggered;
and the to-be-backed-up unit is used for taking the file to be backed up as the file to be backed up if the file to be backed up is a writable file.
Further, the integrity determination module 53 includes:
the head-tail mark detection unit is used for traversing the files to be backed up in the first preset path for each file to be backed up, detecting whether head mark marks and tail mark marks exist or not, and obtaining a detection result;
and the integrity judgment unit to be backed up is used for judging the integrity of the file to be backed up based on the detection result and obtaining a first judgment result.
Further, after the integrity judging module 53, the in vitro diagnostic device-based file management apparatus 5 further includes:
the initial configuration unit is used for acquiring a last state configuration file corresponding to the file to be backed up if the first judgment result shows that the file to be backed up does not have integrity;
and the file to be backed up replacing unit is used for replacing the file to be backed up with the last state configuration file and storing the last state configuration file to the first preset path.
Further, after the backup module 54, the in vitro diagnostic device-based file management apparatus 5 further includes:
the secondary judging unit is used for judging whether the head mark marks and the tail mark marks exist in the backup file or not so as to carry out integrity judgment on the backup file and obtain a second judging result;
the re-backup unit is used for deleting the backup file and re-backing up the file to be backed up until the backup file has integrity if the second judgment result is that the backup file does not have integrity;
and the backup file storage unit is used for storing the backup file in the second preset path.
Further, the integrity determination unit to be backed up includes:
the first integrity judging subunit is used for judging that the file to be backed up has integrity if the detection result is that the head mark and the tail mark exist in the file to be backed up;
and the second integrity judging subunit is used for judging that the file to be backed up does not have integrity if the detection result is that the head mark and the tail mark exist in the file to be backed up or if the detection result is that the head mark and the tail mark do not exist in the file to be backed up.
In the embodiment, a configuration file is obtained, and head marking and tail marking are carried out on the configuration file to obtain a marking file, wherein the marking file comprises head marking marks and tail marking marks; when a file backup condition is triggered, acquiring a file to be backed up as a file to be backed up; based on the head mark marks and the tail mark marks, carrying out integrity judgment on the file to be backed up to obtain a first judgment result; and if the first judgment result shows that the file to be backed up has integrity, backing up the file to be backed up to obtain the backup file. The embodiment of the invention judges the integrity of the configuration file to backup the configuration file with the integrity, thereby avoiding the condition of file information loss when power failure occurs in the process of writing the file.
To solve the above technical problems, the embodiment of the present application also provides an in vitro diagnostic device 6. Referring specifically to fig. 9, fig. 9 is a block diagram showing the basic structure of the in vitro diagnostic device 6 according to the present embodiment.
The in-vitro diagnostic device 6 comprises a memory 61, a processor 62, a network interface 63 which are communicatively connected to each other via a system bus. It is noted that only an in vitro diagnostic device 6 having three components memory 61, a processor 62, a network interface 63 is shown in the figures, but it is understood that not all illustrated components are required to be implemented, and that more or fewer components may be implemented instead. The in vitro diagnostic device is a medical instrument device for in vitro diagnosis, and the in vitro diagnostic device is a device capable of automatically performing numerical calculation and/or information processing according to a preset or stored instruction, and the hardware of the in vitro diagnostic device includes, but is not limited to, a microprocessor, an Application SpecificIntegratedCircuit, ASIC, a Field-Programmable gate array (FPGA), a digital processor (DigitalSignalProcessor, DSP), an embedded device, and the like.
The in-vitro diagnosis device can perform man-machine interaction with a user through a keyboard, a mouse, a remote controller, a touch pad or voice control equipment and the like.
The memory 61 includes at least one type of readable storage media including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), programmable Read Only Memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 61 may be an internal storage unit of the in vitro diagnostic device 6, such as a hard disk or a memory of the in vitro diagnostic device 6. In other embodiments, the memory 61 may also be an external storage device of the in vitro diagnostic device 6, such as a plug-in hard disk, a smart memory card (SmartMediaCard, SMC), a Secure Digital (SD) card, a flash card (FlashCard) or the like, which are provided on the in vitro diagnostic device 6. Of course, the memory 61 may also comprise both an internal memory unit of the in vitro diagnostic device 6 and an external memory device thereof. In the present embodiment, the memory 61 is generally used to store an operating system and various types of application software installed in the in-vitro diagnostic device 6, such as program codes based on a file management method of the in-vitro diagnostic device, and the like. Further, the memory 61 may also be used to temporarily store various types of data that have been output or are to be output.
The network interface 63 may comprise a wireless network interface or a wired network interface, which network interface 63 is typically used for establishing a communication connection between the in vitro diagnostic device 6 and other electronic devices.
The present application also provides another embodiment, namely, a computer readable storage medium storing a computer program, where the computer program is executable by at least one processor to cause the at least one processor to perform the steps of a file management method based on an in vitro diagnostic device as described above.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method of the embodiments of the present application.
It is apparent that the embodiments described above are only some embodiments of the present application, but not all embodiments, the preferred embodiments of the present application are given in the drawings, but not limiting the patent scope of the present application. This application may be embodied in many different forms, but rather, embodiments are provided in order to provide a more thorough understanding of the present disclosure. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that modifications may be made to the embodiments described in the foregoing, or equivalents may be substituted for elements thereof. All equivalent structures made by the specification and the drawings of the application are directly or indirectly applied to other related technical fields, and are also within the protection scope of the application.
Claims (10)
1. A method for managing files based on an in vitro diagnostic device, comprising:
acquiring a configuration file, and performing head marking and tail marking on the configuration file to obtain a marking file, wherein the marking file comprises head marking marks and tail marking marks;
when a file backup condition is triggered, acquiring a file to be backed up as a file to be backed up, wherein the file backup condition comprises any one of when the configuration file is modified, when the in-vitro diagnosis equipment enters a dormancy process and after the configuration file is upgraded;
based on the head mark marks and the tail mark marks, carrying out integrity judgment on the file to be backed up to obtain a first judgment result;
and if the first judging result shows that the file to be backed up has the integrity, backing up the file to be backed up to obtain a backup file.
2. The method for managing files based on in-vitro diagnostic device according to claim 1, wherein the obtaining the configuration file, performing header marking and trailer marking on the configuration file to obtain a marked file, comprises:
acquiring the configuration file;
identifying a header and a trailer of the configuration file;
marking the head of the configuration file by adopting characters of a front part in an ASCII code, and marking the tail of the configuration file by adopting characters of a rear part in the ASCII code to obtain the marking file;
and storing the mark file in a first preset path.
3. The method for managing files based on in-vitro diagnostic device according to claim 2, wherein the performing integrity judgment on the files to be backed up based on the head mark print and the tail mark print to obtain a first judgment result comprises:
traversing the files to be backed up in the first preset path for each file to be backed up, and detecting whether the head mark marks and the tail mark marks exist or not to obtain a detection result;
and based on the detection result, carrying out integrity judgment on the file to be backed up, and obtaining the first judgment result.
4. The in-vitro diagnostic device-based file management method of claim 3 wherein said method further comprises:
if the detection result is that the head mark and the tail mark exist in the file to be backed up, the first judgment result is that the file to be backed up has integrity;
and if the detection result is that the head mark and the tail mark are not present in the file to be backed up, or if the detection result is that the head mark and the tail mark are not present in the file to be backed up, the first judgment result is that the file to be backed up does not have integrity.
5. The method for managing files based on in-vitro diagnostic devices according to claim 2, wherein the integrity judgment is performed on the files to be backed up based on the head mark print and the tail mark print, and after obtaining the first judgment result, the method further comprises:
if the first judgment result shows that the file to be backed up does not have integrity, acquiring a last state configuration file corresponding to the file to be backed up;
and replacing the file to be backed up with the last state configuration file, and storing the last state configuration file to the first preset path.
6. The method for managing files based on in-vitro diagnostic equipment according to claim 1, wherein if the first determination result indicates that the file to be backed up has integrity, backing up the file to be backed up, and after obtaining the backed up file, the method further comprises:
judging whether the head mark marks and the tail mark marks exist in the backup file or not so as to carry out integrity judgment on the backup file and obtain a second judgment result;
if the second judgment result shows that the backup file does not have integrity, deleting the backup file, and re-backing up the file to be backed up until the backup file has integrity;
and storing the backup file in a second preset path.
7. The method for managing files based on an in vitro diagnostic device according to any one of claims 1 to 6, wherein when a file backup condition is triggered, acquiring a file to be backed up as a file to be backed up comprises:
when the file backup condition is triggered, acquiring the file to be backed up;
judging whether the file to be backed up is a writable file or not;
and if the file to be backed up is a writable file, taking the file to be backed up as a file to be backed up.
8. A document management apparatus based on an in vitro diagnostic device, comprising:
the file marking module is used for obtaining a configuration file, marking the head part and the tail part of the configuration file, and obtaining a marking file;
the module to be backed up is used for acquiring the file to be backed up as the file to be backed up when the file backup condition is triggered;
the integrity judging module is used for carrying out integrity judgment on the file to be backed up based on the head mark marks and the tail mark marks to obtain a first judging result;
and the backup module is used for backing up the file to be backed up to obtain a backup file if the first judgment result shows that the file to be backed up has integrity.
9. An in-vitro diagnostic device comprising a memory and a processor, said memory having stored therein a computer program, said processor implementing the in-vitro diagnostic device based file management method according to any one of claims 1 to 7 when said computer program is executed.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the in-vitro diagnostic device-based file management method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310062316.2A CN116302681A (en) | 2023-01-13 | 2023-01-13 | File management method, device, equipment and medium of in-vitro diagnosis equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310062316.2A CN116302681A (en) | 2023-01-13 | 2023-01-13 | File management method, device, equipment and medium of in-vitro diagnosis equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116302681A true CN116302681A (en) | 2023-06-23 |
Family
ID=86777038
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310062316.2A Pending CN116302681A (en) | 2023-01-13 | 2023-01-13 | File management method, device, equipment and medium of in-vitro diagnosis equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116302681A (en) |
-
2023
- 2023-01-13 CN CN202310062316.2A patent/CN116302681A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106095620B (en) | A kind of development approach of built-in Linux partition holding | |
| CN108646982B (en) | Automatic data restoration method and device based on UBIFS | |
| EP2386958A1 (en) | Method for incremental anti-tear garbage collection | |
| CN102541676B (en) | Method for detecting and mapping states of NAND FLASH | |
| CN108170495B (en) | BIOS upgrading method, system, equipment and computer readable storage medium | |
| CN107908417B (en) | Firmware upgrading method and electronic equipment | |
| CN1924821A (en) | Firmware renewing system and method | |
| CN115292266A (en) | High-reliability log storage method based on memory | |
| CN108829342B (en) | Log storage method, system and storage device | |
| US6722572B2 (en) | Recording medium control method, data management apparatus, and recording medium | |
| CN116302681A (en) | File management method, device, equipment and medium of in-vitro diagnosis equipment | |
| US8055853B2 (en) | Data storage system and data storage program for atomic transactions | |
| CN116360695A (en) | Data storage method and device based on hybrid energy storage power supply | |
| JP3028055B2 (en) | PC card system and program rewriting method | |
| CN115407943A (en) | Memory dump file generation method, device and equipment and readable storage medium | |
| CN110795155B (en) | System starting method and device, electronic equipment and storage medium | |
| CN110471623B (en) | Hard disk file writing method, device, computer equipment and storage medium | |
| CN113778485A (en) | System operation method and device of electronic chip, electronic chip and storage medium | |
| CN112269531A (en) | Source roll capacity reduction method, device, equipment and medium | |
| CN111857586A (en) | SSD Trim optimization method, system, terminal and storage medium | |
| CN113467698A (en) | Writing method and device based on file system, computer equipment and storage medium | |
| CN112908390B (en) | Data storage method, device, electronic equipment and storage medium | |
| CN114880277B (en) | Block device snapshot method, system and storage medium | |
| CN112905112B (en) | Data processing method and system of embedded equipment | |
| CN113868023B (en) | Snapshot method and device of storage system, electronic equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |