CN103955528B - The method of writing in files data, the method for file reading data and device - Google Patents
The method of writing in files data, the method for file reading data and device Download PDFInfo
- Publication number
- CN103955528B CN103955528B CN201410197109.9A CN201410197109A CN103955528B CN 103955528 B CN103955528 B CN 103955528B CN 201410197109 A CN201410197109 A CN 201410197109A CN 103955528 B CN103955528 B CN 103955528B
- Authority
- CN
- China
- Prior art keywords
- data
- file
- burst
- write
- fragment
- 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.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- 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
Abstract
The invention provides a kind of method of writing in files data, the method for file reading data and device.The method of said write file data comprises: obtain the file write request comprising file identification and memory buffer regional address; According to the file data that described core buffer address acquisition will write; Described file data is partitioned into two or more data fragmentation; Predetermined partition in first fragment data write local disk of a part for the two or more data fragmentations be divided into will be comprised; Second fragment data of the remainder comprising the two or more data fragmentations be divided into is sent to server; The event memory of described second fragment data is received from described server; In the file that described file identification indicates, write the file storage data of data-bias value, burst size and the memory address comprising each data fragmentation, wherein, in described second fragment data, the memory location of each data fragmentation is the precalculated position on server.
Description
Technical field
The present invention relates to a kind of art file management technology, particularly relate to a kind of method of writing in files data, the method for file reading data and realize the device of described method.
Background technology
Existing art file management technology, is complete file stored in a hard disk, when writing in files data, directly the complete file data after write is kept at the path of specifying; When file reading data, because file intactly stores in a hard disk, the complete content of this file is directly supplied to user by system.
But this art file management technology exists can not the problem of safeguard file safety, and file is easy to intactly be stolen, even if to its encryption, also still there is the risk be cracked.
Summary of the invention
The object of the present invention is to provide a kind of method of writing in files data, the method for file reading data and device, by carrying out burst process to file data, slicing files data scatter is stored on local and server, thus make file data be difficult to intactly be stolen, the safety of safeguard file data to a great extent.
According to an aspect of the present invention, a kind of method of writing in files data is provided, comprises, perform following steps in computer systems, which: obtain the file write request comprising file identification and memory buffer regional address; According to the file data that described core buffer address acquisition will write; Described file data is partitioned into two or more data fragmentation; Predetermined partition in first fragment data write local disk of a part for the two or more data fragmentations be divided into will be comprised; Second fragment data of the remainder comprising the two or more data fragmentations be divided into is sent to server; The event memory of described second fragment data is received from described server; In the file that described file identification indicates, write the file storage data of data-bias value, burst size and the memory address comprising each data fragmentation, wherein, in described second fragment data, the memory location of each data fragmentation is the precalculated position on server.
According to a further aspect in the invention, a kind of method of file reading data is provided, comprises, perform following steps in computer systems, which: obtain the file read request comprising file identification; The file file reading indicated from described file identification stores data, described file storage data comprises the data-bias value of at least two data fragmentations, burst size and memory address, wherein, to the data fragmentation of memory address in the predetermined partition of local disk be comprised as the first fragment data, will the data fragmentation in memory address precalculated position on the server be comprised as the second fragment data; Corresponding first data fragmentation described first fragment data is read from described memory address respectively according to the data-bias value of each data fragmentation in described first fragment data, burst size and memory address; According to the data-bias value of each data fragmentation in described second fragment data, burst size and memory address to server request second fragment data; Described second fragment data is received from described server; Described file data is built in core buffer according to the file storage data read, the first fragment data of reading and the second fragment data of reception.
According to a further aspect in the invention, a kind of method of store file data is provided, comprises, perform following steps at server end: receive the fragment data comprising data fragmentation from client; Store the fragment data received; Event memory about described fragment data is sent to described client.
According to a further aspect in the invention, a kind of method providing file data is provided, comprises, perform following steps at server end: receive memory address and burst size from client; The fragment data of described burst size is read from described memory address; The fragment data of reading is sent to described client.
According to a further aspect in the invention, a kind of device for writing in files data is provided, comprises: write request receiving element, for obtaining the file write request comprising file identification and memory buffer regional address; File data acquiring unit, for the file data that will write according to described core buffer address acquisition; Data partitioning unit, for being partitioned into two or more data fragmentation by described file data; First fragment data storage unit, for the predetermined partition in the first fragment data write local disk of the part by comprising the two or more data fragmentations be divided into; Second fragment data storage unit, for the second fragment data of the remainder comprising the two or more data fragmentations be divided into is sent to server, and receives the event memory of described second fragment data from described server; File write unit, the file storage data of the data-bias value of each data fragmentation, burst size and memory address is comprised for write in the file that indicates at described file identification, wherein, in described second fragment data, the memory location of each data fragmentation is the precalculated position on server.
According to a further aspect in the invention, a kind of device of store file data is provided, comprises: fragment data receiving element, for receiving the fragment data comprising data fragmentation from client; Fragment data storage unit, for storing the fragment data of reception; Event memory transmitting element, for sending to described client by the event memory about described fragment data.
According to a further aspect in the invention, a kind of device of file reading data is provided, comprises: read requests receiving element, for obtaining the file read request comprising file identification; Document reading unit, file file reading for indicating from described file identification stores data, described file storage data comprises the data-bias value of at least two data fragmentations, burst size and memory address, wherein, to the data fragmentation of memory address in the predetermined partition of local disk be comprised as the first fragment data, will the data fragmentation in memory address precalculated position on the server be comprised as the second fragment data; First fragment data reading unit, reads corresponding first data fragmentation described first fragment data from described memory address respectively for the data-bias value according to each data fragmentation in described first fragment data, burst size and memory address; Second fragment data reading unit, for the data-bias value according to each data fragmentation in described second fragment data, burst size and memory address to server request second fragment data, and receives described second fragment data from described server; File data construction unit, for building described file data according to the file storage data read, the first fragment data of reading and the second fragment data of reception in core buffer.
According to a further aspect in the invention, a kind of device providing file data is provided, comprises: fragment data request reception unit, for receiving memory address and burst size from client; Fragment data reading unit, for reading the fragment data of described burst size from described memory address; Fragment data transmitting element, for sending to described client by the fragment data of reading.
Beneficial effect
The device comprising the file management methods such as file write, file reading and implement described method according to the present invention carries out burst process by file user write, a part is wherein stored in the predetermined partition of local disk, and another part is wherein stored on the server, all files data can be reduced by the possibility revealed; And the fragment data being stored in this locality is stored in the hidden partition of local disk, invisible to user, the security of file data can be improved.According to file management method of the present invention, by file is divided into two parts, and two parts dispersion is stored in the mode in local disk and another system, even if the situation of divulging a secret appears in certain computer, also cannot obtains complete file.
In addition, before burst process is performed to file data, can to described file data executive software or hardware encipher process, to guarantee the security of file data further.
Accompanying drawing explanation
Fig. 1 is the integrated stand composition of the file management method according to exemplary embodiment of the present invention;
Fig. 2 is the schematic diagram stored according to the file fragmentation of exemplary embodiment of the present invention;
Fig. 3 is the process flow diagram of the method for writing in files data according to exemplary embodiment of the present invention;
Fig. 4 is the process flow diagram of the method for store file data according to exemplary embodiment of the present invention;
Fig. 5 be according to the file reading data of exemplary embodiment of the present invention the process flow diagram of method;
Fig. 6 is the process flow diagram providing the method for file data according to exemplary embodiment of the present invention;
Fig. 7 is the logic diagram of the device of writing in files data according to exemplary embodiment of the present invention;
Fig. 8 is the logic diagram of the device of store file data according to exemplary embodiment of the present invention;
Fig. 9 is the logic diagram of the device of file reading data according to exemplary embodiment of the present invention;
Figure 10 is the logic diagram providing the device of file data according to exemplary embodiment of the present invention.
Embodiment
Present general inventive concept of the present invention is, in computer systems, which, there is provided a kind of file management method: the file that user writes is carried out burst process, be divided into two parts, a part is wherein stored in the predetermined partition of local disk, and another part is wherein stored on the server, and the described two-part storage information of file is stored in the file that user will write; When user view reads the file data previously write in the foregoing manner, from the storage information being written to the file file reading that user indicates, read the partial document data in the predetermined partition of local disk according to described storage information and from server request storage another part file data on the server, then carry out the file data of the actual write of reconstructing user according to the partial document data of reading and another part file data of request.The predetermined partition of the described local disk for storing fragment data can be the hidden partition of pre-configured local disk, invisible to user, to improve the security of file data.According to file management method of the present invention, by file is divided into two parts, and two parts dispersion is stored in the mode in local disk and another system, even if the situation of divulging a secret appears in certain computer, also cannot obtains complete file.
In order to keep compatible with existing file management system, can at the inner nuclear layer of computer system using the form of driver component as the process entrance of file management method of the present invention, to catch the file write that upper strata drives and the request of reading at inner nuclear layer, after this can in process such as the reading of systematic difference layer execute file data, write, storage and reconstruct.In addition, before burst process is performed to file data, can to described file data executive software or hardware encipher process, to guarantee the security of file data further.Store and encryption by performing burst to file data, the generation of the event that can prevent file from divulging a secret to a great extent.
On this basis, also difference management can be performed to the file of user.Such as, the file operation blacklist of the information allowing the file operation white list of the information of the file carrying out burst storage or comprise the file not allowing burst to store can pre-configuredly be comprised.In this article, described file operation white list and file operation blacklist are referred to as file operation permissions data.When processing file write request, the file write request of reception is mated with the file operation permissions data prestored, to determine whether to allow burst store file data.For the file write allowing burst store file data, can continue to perform burst stores processor; And for not allowing the file of burst store file data to write, can according to the needs of file management, write described file data according to general document management mode at the Disk Locality of the file write request instruction received, or drive the information returning write error to prevent file copy directly to upper strata.Like this, can such as to being construed to the file of important information or forcing to carry out burst storage to the file of regulation write disk particular zones, or forbid carrying out burst store and management etc. to the file data of Application-Specific Processing operation.
Fig. 1 is the integrated stand composition of the file management method according to exemplary embodiment of the present invention.
With reference to Fig. 1, when the write of user's input requirements F: the instruction of 1.txt file time, the driver component 10 being positioned at system kernel layer catches the file write request bag driven from upper strata, described file write request bag can comprise file identification and memory buffer regional address, still can comprise initial write off-set value and write size of data.Operation 1 in FIG, described memory buffer regional address is passed to the documentor 20 of application layer by described driver component 10, and documentor 20 obtains the file data that will write according to described memory buffer regional address (and initial write off-set value and write size of data) and described file data is partitioned into two or more data fragmentation.In operation 3, documentor 20 by comprise a part for the two or more data fragmentations be divided into first fragment data write local disk in predetermined partition G:; In operation 4, the second fragment data of the remainder comprising the two or more data fragmentations be divided into is sent to server by documentor 20, and receives the event memory of described second fragment data from described server.After this, the file that documentor 20 indicates at described file identification F: in 1.txt write comprise the file storage data of the data-bias value of each data fragmentation, burst size and memory address, wherein, in described second fragment data, the memory location of each data fragmentation is the precalculated position on server.
On the other hand, when user's input requirements read F: the instruction of 1.txt file time, the driver component 10 being positioned at system kernel layer catches the file read request bag driven from upper strata, described file read request bag can comprise file identification, also can comprise start read offset value further and read size of data.Operation 1 in FIG, described file identification (and start read offset value and read size of data) is passed to the documentor 20 of application layer by described driver component 10.In operation 2, the file that documentor 20 indicates from described file identification F: 1.txt file reading store data, described file storage data comprises the data-bias value of at least two data fragmentations, burst size and memory address, wherein, to the data fragmentation of memory address in the predetermined partition of local disk be comprised as the first fragment data, will the data fragmentation in memory address precalculated position on the server be comprised as the second fragment data.In operation 3, documentor 20 reads corresponding first data fragmentation described first fragment data from described memory address respectively according to the data-bias value of each data fragmentation in described first fragment data, burst size and memory address; In operation 4, documentor 20 to server request second fragment data, and receives described second fragment data from described server according to the data-bias value of each data fragmentation in described second fragment data, burst size and memory address.After this, documentor 20 according to the file storage data read in operation 2, operation 3 read the first fragment data and operation 4 receive the second fragment data build described file data in core buffer.
Fig. 2 is the schematic diagram stored according to the file fragmentation of exemplary embodiment of the present invention.
With reference to Fig. 2, user use word.exe editing files data and the file data of editor is stored as F: 1.txt.Through aforesaid file write process, the first fragment data is stored as G: on file a, and the second fragment data is stored as file b by precalculated position on the server.According to the size of file data, can be also two or more files by the first fragment data and the second fragment data distributed store.
Fig. 3 is the process flow diagram of the method for writing in files data according to exemplary embodiment of the present invention.
With reference to Fig. 3, in step S310, obtain the file write request comprising file identification and memory buffer regional address.Described file identification comprises file path and file name.According to an alternative embodiment of the invention, described file write request also can comprise the initial write off-set value in file data further and write size of data, divides the write of file data with enforcement division.
In step S320, according to the file data that described core buffer address acquisition will write.According to an alternative embodiment of the invention, in step S320, the initial write off-set value that can be obtained from memory buffer regional address according to described memory buffer regional address, initial write off-set value and write size of data plays the data of said write size of data as the described file data that will write, to read the partial document data of specifying and will write.
In step S330, described file data is partitioned into two or more data fragmentation.Here, simply described file data can be divided into two, also as required described file data can be divided into two or more equal and opposite in direction or data fragmentation not etc.
In step S340, the predetermined partition in the first fragment data write local disk of a part for the two or more data fragmentations be divided into will be comprised.According to a preferred embodiment of the invention, the predetermined partition of described local disk is the hidden partition separated in local disk, thus user directly cannot obtain described first fragment data, to improve data security.
In step S350, the second fragment data of the remainder comprising the two or more data fragmentations be divided into is sent to server.
In step S360, receive the event memory of described second fragment data from described server.The event memory of described second fragment data can comprise the memory location of the file storing described second fragment data.
In step S370, in the file that described file identification indicates, write the file storage data of data-bias value, burst size and the memory address comprising each data fragmentation.Wherein, in described second fragment data, the memory location of each data fragmentation can be the precalculated position on server, also can be the memory location that the server obtained from the event memory of described second fragment data received stores the file of described second fragment data.Memory location mentioned here can be the logical place of the file for storing described fragment data, as the file path in file system and file name.
In order to keep and the compatibility of existing file way to manage and the leakage-preventing management supporting the different levels to file, the pre-configured file operation permissions data comprising the information of the file allowing the information of the file carrying out burst storage or do not allow burst to store.Described allow the information of the file carrying out burst storage to comprise to allow the information of the file type of carrying out burst storage and allow to carry out burst storage the disk partition of file place information at least one; The information of the described file not allowing burst to store can comprise the information of the file type not allowing burst to store and not allow at least one in the information of the process of burst storage file to it.
Before execution step S320 or S330, the file write request of reception is mated with the file operation permissions data prestored, to determine whether to allow burst store file data.If determine to allow burst store file data according to mating of described file operation permissions data, then continue to perform step S330 ~ 370.
If determine not allow burst store file data according to mating of described file operation permissions data, the information returning write error is then driven to upper strata, to prevent unwarranted file copy, or according to common file writing mode, write described file data at the Disk Locality of the file write request instruction received.
According to a preferred embodiment of the invention, in order to improve the security of file data further, before execution step S330, the file data obtained in step S320 is encrypted, and in step S370, also write for the information by described file data encrypt/decrypt in the file that described file identification indicates.
According to a preferred embodiment of the invention, in step S310, catch the described file write request driven from upper strata at system kernel layer, perform step S320 ~ S370 at systematic difference layer, and the pointer of file that described file identification also indicates by system kernel layer returns to upper strata drives.Fig. 4 is the process flow diagram of the method for store file data according to exemplary embodiment of the present invention.
With reference to Fig. 4, in step S410, receive the fragment data comprising data fragmentation from client.
In step S420, store the fragment data received.In precalculated position, the fragment data of described reception can be stored as file.
In step S430, the event memory about described fragment data is sent to described client.According to an alternative embodiment of the invention, the described event memory about described fragment data comprises the memory location of the file storing described fragment data.
Fig. 5 be according to the file reading data of exemplary embodiment of the present invention the process flow diagram of method.
With reference to Fig. 5, in step S510, obtain the file read request comprising file identification.Described file identification can comprise file path and file name.According to an alternative embodiment of the invention, described file read request also can comprise the start read offset value in described file data and read size of data.
In step S520, the file file reading indicated from described file identification stores data, described file storage data comprises the data-bias value of at least two data fragmentations, burst size and memory address, wherein, to the data fragmentation of memory address in the predetermined partition of local disk be comprised as the first fragment data, will the data fragmentation in memory address precalculated position on the server be comprised as the second fragment data.According to a preferred embodiment of the invention, the predetermined partition of described local disk is the hidden partition separated in local disk.
In step S530, read corresponding first data fragmentation described first fragment data from described memory address respectively according to the data-bias value of each data fragmentation in described first fragment data, burst size and memory address.
In step S540, according to the data-bias value of each data fragmentation in described second fragment data, burst size and memory address to server request second fragment data, be specially, the size of the memory address of the second fragment data and the second fragment data is sent to server, the size of described second fragment data be the burst size of each data fragmentation in the second fragment data and.
In step S550, receive described second fragment data from described server.
In step S560, build described file data according to the file storage data read, the first fragment data of reading and the second fragment data of reception in core buffer.If the described file read request obtained in step S510 also can comprise the start read offset value in described file data and read size of data, then in step S560, build the file data of described reading size of data from start read offset value in core buffer according to the file storage data read, the first fragment data of reading and the second fragment data of reception.
According to an alternative embodiment of the invention, before execution step S520, the file read request of reception is mated with the file operation permissions data prestored, to determine whether to need burst to assemble file data.Described file operation permissions data comprises the information allowing the information of the file carrying out burst storage or do not allow the file carrying out burst storage.Described allow the information of the file carrying out burst storage to comprise to allow the information of the file type of carrying out burst storage and allow to carry out burst storage the disk partition of file place information at least one, the information of the described file not allowing burst to store comprises the information of the file type not allowing burst to store and does not allow at least one in the information of the process of burst storage file to it.If determine to need burst to assemble file data, then continue to perform the operation that the file file reading indicated from described file identification stores data; If determine not need burst to assemble file data, then read described file data at the Disk Locality of the file identification instruction received.
According to a preferred embodiment of the invention, also with for the information by described file data encrypt/decrypt in the file of described file identification instruction, and structure described file data after, use described by the information of described file data encrypt/decrypt by described decrypt file data.
According to a preferred embodiment of the invention, step S510, the file read request driven from upper strata is caught at system kernel layer, perform step S520 ~ S560 at systematic difference layer, and described file data is also returned to upper strata driving by system kernel layer in the address of core buffer and the size of described file data.
Fig. 6 is the process flow diagram providing the method for file data according to exemplary embodiment of the present invention.
With reference to Fig. 6, in step S610, receive memory address and burst size from client.
In step S620, read the fragment data of described burst size from described memory address.Such as, the fragment data of described burst size is read from the file being stored in described memory address.
In step S630, the fragment data of reading is sent to described client.
Fig. 7 is the logic diagram of the device of writing in files data according to exemplary embodiment of the present invention.
With reference to Fig. 7, comprise write request receiving element 710, file data acquiring unit 720, data partitioning unit 730, first fragment data storage unit 740, second fragment data storage unit 750 and File write unit 760 according to the device of the writing in files data of exemplary embodiment of the present invention.
Write request receiving element 710 comprises the file write request of file identification and memory buffer regional address for obtaining.Described file identification comprises file path and file name.According to an alternative embodiment of the invention, described file write request also can comprise the initial write off-set value in file data further and write size of data, divides the write of file data with enforcement division.
The file data of file data acquiring unit 720 for writing according to described core buffer address acquisition.According to an alternative embodiment of the invention, the initial write off-set value that file data acquiring unit 720 can be obtained from memory buffer regional address according to described memory buffer regional address, initial write off-set value and write size of data plays the data of said write size of data as the described file data that will write, to read the partial document data of specifying and will write.
Data partitioning unit 730 is for being partitioned into two or more data fragmentation by described file data.
First fragment data storage unit 740 is for the predetermined partition in the first fragment data write local disk of the part by comprising two or more data fragmentations that data partitioning unit 730 is divided into.Predetermined partition in described local disk is the hidden partition separated in local disk.
Second fragment data storage unit 750 for the second fragment data of the remainder comprising the two or more data fragmentations be divided into is sent to server, and receives the event memory of described second fragment data from described server.The event memory of described second fragment data can comprise the memory location of the file storing described second fragment data.
File write unit 760 comprises the file storage data of the data-bias value of each data fragmentation, burst size and memory address for write in the file that indicates at described file identification, wherein, in described second fragment data, the memory location of each data fragmentation is the precalculated position on server.Also can be the memory location that the server obtained from the event memory of described second fragment data received stores the file of described second fragment data.
According to a preferred embodiment of the invention, described data partitioning unit 730 is before being partitioned into two or more data fragmentation by described file data, the file write request of reception is mated with the file operation permissions data prestored, to determine whether to allow burst store file data, described file operation permissions data comprises the information of the file allowing the information of the file carrying out burst storage or do not allow burst to store.Described allow the information of the file carrying out burst storage to comprise to allow the information of the file type of carrying out burst storage and allow to carry out burst storage the disk partition of file place information at least one, the information of the described file not allowing burst to store can comprise the information of the file type not allowing burst to store and not allow at least one in the information of the process of burst storage file to it.
If described data partitioning unit 730 is determined to allow burst store file data according to mating of described file operation permissions data, then described data partitioning unit continuation performs and described file data is partitioned into two or more data fragmentation, and the first fragment data storage unit 740, second fragment data storage unit 750 and File write unit 760 can continue the write process performing data storage and file storage data; If described data partitioning unit 730 is determined not allow burst store file data according to mating of described file operation permissions data, then described data partitioning unit 730 drives the information returning write error to upper strata, or File write unit 760 writes described file data at the Disk Locality of the file write request instruction received.
According to a preferred embodiment of the invention, the device of said write file data also comprises DEU data encryption unit (not shown), described DEU data encryption unit is used for before described file data is partitioned into two or more data fragmentation by described data partitioning unit, is encrypted by described file data.According to another preferred embodiment of the invention, also write for the information by described file data encrypt/decrypt in the file that File write unit 760 indicates at described file identification, wherein, described DEU data encryption unit uses the described information by described file data encrypt/decrypt to be encrypted by described file data by during described file data encryption.
According to a preferred embodiment of the invention, write request receiving element 710 catches the described file write request driven from upper strata at system kernel layer; File data acquiring unit 720, DEU data encryption unit (if any), data partitioning unit 730, first fragment data storage unit 740, second fragment data storage unit 750 and File write unit 760 perform at systematic difference layer.
According to a preferred embodiment of the invention, described device is also included in the write request response unit of system kernel layer, and the pointer that said write request-response unit is used for the file indicated by described file identification after described File write unit 760 is complete returns to upper strata driving.
Fig. 8 is the logic diagram of the device of store file data according to exemplary embodiment of the present invention.
With reference to Fig. 8, comprise fragment data receiving element 810, fragment data storage unit 820 and event memory transmitting element 830 according to the device of the store file data of exemplary embodiment of the present invention.
Fragment data receiving element 810 is for receiving the fragment data comprising data fragmentation from client.
Fragment data storage unit 820 is for storing the fragment data of reception.According to the specified embodiment of the present invention, the fragment data of described reception is stored as file in precalculated position by fragment data storage unit 820.
Event memory transmitting element 830 is for sending to described client by the event memory about described fragment data.The described event memory about described fragment data can comprise the memory location of the file storing described fragment data.
Fig. 9 is the logic diagram of the device of file reading data according to exemplary embodiment of the present invention.
With reference to Fig. 9, comprise read requests receiving element 910, document reading unit 920, first fragment data reading unit 930, second fragment data reading unit 940 and file data construction unit 950 according to the device of the file reading data of exemplary embodiment of the present invention.
Read requests receiving element 910 comprises the file read request of file identification for obtaining.Described file identification can comprise file path and file name.
Document reading unit 920 stores data for the file file reading indicated from described file identification, described file storage data comprises the data-bias value of at least two data fragmentations, burst size and memory address, wherein, to the data fragmentation of memory address in the predetermined partition of local disk be comprised as the first fragment data, will the data fragmentation in memory address precalculated position on the server be comprised as the second fragment data.According to a preferred embodiment of the invention, the predetermined partition of described local disk is the hidden partition separated in local disk.
First fragment data reading unit 930 reads corresponding first data fragmentation described first fragment data from described memory address respectively for the data-bias value according to each data fragmentation in described first fragment data, burst size and memory address.
Second fragment data reading unit 940 to server request second fragment data, and receives described second fragment data from described server for the data-bias value according to each data fragmentation in described second fragment data, burst size and memory address.
File data construction unit 950 is for building described file data according to the file storage data read, the first fragment data of reading and the second fragment data of reception in core buffer.
According to an alternative embodiment of the invention, the described file read request received also comprises the start read offset value in described file data and reads size of data, and described file data construction unit 950 is for building the file data of described reading size of data from start read offset value in core buffer according to the file storage data read, the first fragment data of reading and the second fragment data of reception.
According to a preferred embodiment of the invention, after read requests receiving element 910 acquisition comprises the file read request of file identification, the file read request of reception also mates with the file operation permissions data prestored by document reading unit 920, to determine whether to need burst to assemble file data, described file operation permissions data comprises the information allowing the information of the file carrying out burst storage or do not allow the file carrying out burst storage.Described allow the information of the file carrying out burst storage to comprise to allow the information of the file type of carrying out burst storage and allow to carry out burst storage the disk partition of file place information at least one, the information of the described file not allowing burst to store can comprise the information of the file type not allowing burst to store and not allow at least one in the information of the process of burst storage file to it.
If document reading unit 920 is determined to need burst to assemble file data, then the file file reading that document reading unit 920 indicates from described file identification stores data; If document reading unit 920 is determined not need burst to assemble file data, then document reading unit 920 reads described file data at the Disk Locality of the file identification instruction received.
According to a preferred embodiment of the invention, described device also comprises data decryption unit (not shown), and described data decryption unit is used for the described decrypt file data built file data construction unit.According to another preferred embodiment of the invention, also read for the information by described file data encrypt/decrypt in the file that document reading unit 920 indicates at described file identification, wherein, described data decryption unit use described by the information of described file data encrypt/decrypt by described decrypt file data.
According to a preferred embodiment of the invention, read requests receiving element 910 catches the file read request driven from upper strata at system kernel layer, document reading unit 920, first fragment data reading unit 930, second fragment data reading unit 940 and file data construction unit 950 perform at systematic difference layer; Described device also comprises: at the read requests response unit of system kernel layer, and described read requests response unit is used for described file data being returned to upper strata in the address of core buffer and the size of described file data and drives.
Figure 10 is the logic diagram providing the device of file data according to exemplary embodiment of the present invention.
With reference to Figure 10, described in provide the device of file data to comprise: fragment data request reception unit 1010, fragment data reading unit 1020 and fragment data transmitting element 1030.
Fragment data request reception unit 1010 is for receiving memory address and burst size from client.
Fragment data reading unit 1020 is for reading the fragment data of described burst size from described memory address.Such as, fragment data reading unit 1020 can read the fragment data of described burst size from the file being stored in described memory address.
Fragment data transmitting element 1030 is for sending to described client by the fragment data of reading.
The device comprising the file management methods such as file write, file reading and implement described method according to the present invention carries out burst process by file user write, a part is wherein stored in the predetermined partition of local disk, and another part is wherein stored on the server, all files data can be reduced by the possibility revealed; And the fragment data being stored in this locality is stored in the hidden partition of local disk, invisible to user, the security of file data can be improved.According to file management method of the present invention, by file is divided into two parts, and two parts dispersion is stored in the mode in local disk and another system, even if the situation of divulging a secret appears in certain computer, also cannot obtains complete file.
In addition, before burst process is performed to file data, can to described file data executive software or hardware encipher process, to guarantee the security of file data further.
On this basis, mated with file operation permissions data by the fileinfo that will write/read, also can perform difference management to the file of user, can such as to being construed to the file of important information or forcing to carry out burst storage to the file of regulation write disk particular zones, or forbid carrying out burst store and management etc. to the file data of Application-Specific Processing operation.
The above; be only the specific embodiment of the present invention, but protection scope of the present invention is not limited thereto, is anyly familiar with those skilled in the art in the technical scope that the present invention discloses; change can be expected easily or replace, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection domain of described claim.
Claims (48)
1. a method for writing in files data, comprises, and performs following steps in computer systems, which:
Step S310: obtain the file write request comprising file identification and memory buffer regional address;
Step S320: the file data that will write according to described core buffer address acquisition;
Step S330: described file data is partitioned into two or more data fragmentation;
Step S340: will the predetermined partition in the first fragment data write local disk of a part for the two or more data fragmentations be divided into be comprised;
Step S350: the second fragment data of the remainder comprising the two or more data fragmentations be divided into is sent to server;
Step S360: the event memory receiving described second fragment data from described server;
Step S370: the file storage data writing data-bias value, burst size and the memory address comprising each data fragmentation in the file that described file identification indicates,
Wherein, in described second fragment data, the memory location of each data fragmentation is the precalculated position on server;
Predetermined partition in described local disk is the hidden partition separated in local disk;
Described file write request also comprises initial write off-set value in described file data and write size of data, and the process of the described file data that will write according to described core buffer address acquisition comprises: the initial write off-set value being obtained from memory buffer regional address according to described memory buffer regional address, initial write off-set value and write size of data plays the data of said write size of data as the described file data that will write.
2. method according to claim 1, also comprise: before described file data is partitioned into two or more data fragmentation, the file write request of reception is mated with the file operation permissions data prestored, to determine whether to allow burst store file data, described file operation permissions data comprises the information of the file allowing the information of the file carrying out burst storage or do not allow burst to store.
3. method according to claim 2, it is characterized in that, described allow the information of the file carrying out burst storage to comprise to allow the information of the file type of carrying out burst storage and allow to carry out burst storage the disk partition of file place information at least one, the information of the described file not allowing burst to store comprise the file type not allowing burst to store information and do not allow burst storage file process information at least one.
4. method according to claim 3, is characterized in that, if determine to allow burst store file data according to mating of described file operation permissions data, then continues to perform the operation described file data being partitioned into two or more data fragmentation.
5. method according to claim 4, is characterized in that, if determine not allow burst store file data according to mating of described file operation permissions data, then drives the information returning write error to upper strata.
6. method according to claim 4, is characterized in that, if determine not allow burst store file data according to described file operation permissions data, then writes described file data at the Disk Locality of the file write request instruction received.
7. the method according to any one of claim 1 ~ 6, also comprises: before described file data is partitioned into two or more data fragmentation, is encrypted by described file data.
8. method according to claim 7, is characterized in that, also writes for the information by described file data encrypt/decrypt in the file that described file identification indicates,
Wherein, described the process that described file data is encrypted to be comprised: use the described information by described file data encrypt/decrypt to be encrypted by described file data.
9. method according to claim 8, is characterized in that, described acquisition comprises file identification, the process of file write request of memory buffer regional address comprises: catch the described file write request driven from upper strata at system kernel layer.
10. method according to claim 9, is characterized in that, performs step S320 to step S370 at systematic difference layer.
11. methods according to claim 10, also comprise: perform in the file indicated at described file identification the step of the file storage data writing the data-bias value, burst size and the memory address that comprise each data fragmentation at systematic difference layer after, the pointer of the file that described file identification indicates by system kernel layer returns to upper strata and drives.
12. methods according to claim 11, is characterized in that, described file identification comprises file path and file name.
13. methods according to claim 12, is characterized in that, obtain the memory location of each data fragmentation described second fragment data from the event memory of the second fragment data received.
The method of 14. 1 kinds of file reading data, comprises, and performs following steps in computer systems, which:
Step S510: obtain the file read request comprising file identification;
Step S520: the file file reading indicated from described file identification stores data, described file storage data comprises the data-bias value of at least two data fragmentations, burst size and memory address, wherein, using the data fragmentation of memory address in local disk predetermined partition as the first fragment data, using the data fragmentation of memory address in server precalculated position as the second fragment data;
Step S530: read corresponding first data fragmentation described first fragment data from described memory address respectively according to the data-bias value of each data fragmentation in described first fragment data, burst size and memory address;
Step S540: according to the data-bias value of each data fragmentation in described second fragment data, burst size and memory address to server request second fragment data;
Step S550: receive described second fragment data from described server;
Step S560: build described file data in core buffer according to the file storage data read, the first fragment data of reading and the second fragment data of reception;
Wherein, described local disk predetermined partition is the hidden partition separated in local disk;
Described file read request also comprises the start read offset value in described file data and reads size of data, and the process that described file storage data, the first fragment data of reading and the second fragment data of reception according to reading builds described file data in core buffer comprises: the file data building described reading size of data from start read offset value according to the file storage data read, the first fragment data of reading and the second fragment data of reception in core buffer.
15. methods according to claim 14, also comprise: after acquisition comprises the file read request of file identification, the file read request of reception is mated with the file operation permissions data prestored, to determine whether to need burst to assemble file data, described file operation permissions data comprises the information allowing the information of the file carrying out burst storage or do not allow the file carrying out burst storage.
16. methods according to claim 15, is characterized in that, if determine to need burst to assemble file data, then continue to perform the operation that the file file reading indicated from described file identification stores data.
17. methods according to claim 16, is characterized in that, if determine not need burst to assemble file data, then read described file data at the Disk Locality of the file identification instruction received.
18. methods according to claim 17, it is characterized in that, described allow the information of the file carrying out burst storage to comprise to allow the information of the file type of carrying out burst storage and allow to carry out burst storage the disk partition of file place information at least one, the information of the described file not allowing burst to store comprise the file type not allowing burst to store information and do not allow burst storage file process information at least one.
19. methods according to any one of claim 14 ~ 18, also comprise: after the described file data of structure, by described decrypt file data.
20. methods according to claim 19, is characterized in that, also with for the information by described file data encrypt/decrypt in the file of described file identification instruction,
Wherein, the described process by described decrypt file data comprises: use described by the information of described file data encrypt/decrypt by described decrypt file data.
21. methods according to claim 20, is characterized in that, the process that described acquisition comprises the file read request of file identification comprises: catch the file read request driven from upper strata at system kernel layer.
22. methods according to claim 21, is characterized in that, perform from step S520 to step S560 at systematic difference layer.
23. methods according to claim 22, also comprise: after performing at systematic difference layer the step building described file data according to the second fragment data of the file storage data read, the first fragment data of reading and reception in core buffer, described file data is returned to upper strata and drives by system kernel layer in the address of core buffer and the size of described file data.
24. methods according to claim 23, is characterized in that, described file identification comprises file path and file name.
25. 1 kinds, for the device of writing in files data, comprising:
Write request receiving element, for obtaining the file write request comprising file identification and memory buffer regional address;
File data acquiring unit, for the file data that will write according to described core buffer address acquisition;
Data partitioning unit, for being partitioned into two or more data fragmentation by described file data;
First fragment data storage unit, for the first fragment data write local disk predetermined partition of the part by comprising the two or more data fragmentations be divided into;
Second fragment data storage unit, for the second fragment data of the remainder comprising the two or more data fragmentations be divided into is sent to server, and receives the event memory of described second fragment data from described server;
File write unit, the file storage data of the data-bias value of each data fragmentation, burst size and memory address is comprised for write in the file that indicates at described file identification, wherein, in described second fragment data, the memory location of each data fragmentation is server precalculated position;
Described local disk predetermined partition is the hidden partition separated in local disk;
Described file write request also comprises the initial write off-set value in described file data and writes size of data, and the initial write off-set value that described file data acquiring unit is obtained from memory buffer regional address according to described memory buffer regional address, initial write off-set value and write size of data plays the data of said write size of data as the described file data that will write.
26. devices according to claim 25, it is characterized in that, described data partitioning unit is before being partitioned into two or more data fragmentation by described file data, the file write request of reception is mated with the file operation permissions data prestored, to determine whether to allow burst store file data, described file operation permissions data comprises the information of the file allowing the information of the file carrying out burst storage or do not allow burst to store.
27. devices according to claim 26, it is characterized in that, described allow the information of the file carrying out burst storage to comprise to allow the information of the file type of carrying out burst storage and allow to carry out burst storage the disk partition of file place information at least one, the information of the described file not allowing burst to store comprise the file type not allowing burst to store information and do not allow burst storage file process information at least one.
28. devices according to claim 27, it is characterized in that, if described data partitioning unit is determined to allow burst store file data according to mating of described file operation permissions data, then described data partitioning unit continuation performs and described file data is partitioned into two or more data fragmentation.
29. devices according to claim 28, it is characterized in that, if described data partitioning unit is determined not allow burst store file data according to mating of described file operation permissions data, then described data partitioning unit drives the information returning write error to upper strata.
30. devices according to claim 28, it is characterized in that, if described data partitioning unit is determined not allow burst store file data according to described file operation permissions data, then File write unit writes described file data at the Disk Locality of the file write request instruction received.
31. devices according to any one of claim 25 ~ 30, also comprise: DEU data encryption unit, for before described file data is partitioned into two or more data fragmentation by described data partitioning unit, are encrypted by described file data.
32. devices according to claim 31, is characterized in that, also write for the information by described file data encrypt/decrypt in the file that File write unit indicates at described file identification,
Wherein, described DEU data encryption unit uses the described information by described file data encrypt/decrypt to be encrypted by described file data by during described file data encryption.
33. devices according to claim 32, is characterized in that, said write request reception unit catches the described file write request driven from upper strata at system kernel layer.
34. devices according to claim 33, it is characterized in that, described file data acquiring unit, described DEU data encryption unit, described data partitioning unit, described first fragment data storage unit, described second fragment data storage unit and described File write unit perform at systematic difference layer.
35. devices according to claim 34, also comprise: at the write request response unit of system kernel layer, and for after described File write unit is complete, the pointer of the file indicated by described file identification returns to upper strata and drives.
36. devices according to claim 35, is characterized in that, described file identification comprises file path and file name.
37. devices according to claim 36, is characterized in that, the event memory of the second fragment data received from described second fragment data storage unit is obtained the memory location of each data fragmentation in described second fragment data by File write unit.
The device of 38. 1 kinds of file reading data, comprising:
Read requests receiving element, for obtaining the file read request comprising file identification;
Document reading unit, file file reading for indicating from described file identification stores data, described file storage data comprises the data-bias value of at least two data fragmentations, burst size and memory address, wherein, using the data fragmentation of memory address in local disk predetermined partition as the first fragment data, using the data fragmentation of memory address in server precalculated position as the second fragment data;
First fragment data reading unit, reads corresponding first data fragmentation described first fragment data from described memory address respectively for the data-bias value according to each data fragmentation in described first fragment data, burst size and memory address;
Second fragment data reading unit, for the data-bias value according to each data fragmentation in described second fragment data, burst size and memory address to server request second fragment data, and receives described second fragment data from described server;
File data construction unit, for building described file data according to the file storage data read, the first fragment data of reading and the second fragment data of reception in core buffer;
Described local disk predetermined partition is the hidden partition separated in local disk;
Described file read request also comprises the start read offset value in described file data and reads size of data, and described file data construction unit builds the file data of described reading size of data from start read offset value in core buffer according to the file storage data read, the first fragment data of reading and the second fragment data of reception.
39. according to device according to claim 38, it is characterized in that, after described read requests receiving element acquisition comprises the file read request of file identification, the file read request of reception also mates with the file operation permissions data prestored by described document reading unit, to determine whether to need burst to assemble file data, described file operation permissions data comprises the information allowing the information of the file carrying out burst storage or do not allow the file carrying out burst storage.
40., according to device according to claim 39, is characterized in that, if described document reading unit is determined to need burst to assemble file data, then the file file reading that described document reading unit indicates from described file identification stores data.
41. devices according to claim 40, is characterized in that, if described document reading unit is determined not need burst to assemble file data, then described document reading unit reads described file data at the Disk Locality of the file identification instruction received.
42. devices according to claim 41, it is characterized in that, described allow the information of the file carrying out burst storage to comprise to allow the information of the file type of carrying out burst storage and allow to carry out burst storage the disk partition of file place information at least one, the information of the described file not allowing burst to store comprise the file type not allowing burst to store information and do not allow burst storage file process information at least one.
43. devices according to any one of claim 38 ~ 42, also comprise: data decryption unit, for the described decrypt file data built file data construction unit.
44. devices according to claim 43, is characterized in that, also read for the information by described file data encrypt/decrypt in the file that document reading unit indicates at described file identification,
Wherein, described data decryption unit use described by the information of described file data encrypt/decrypt by described decrypt file data.
45. devices according to claim 44, is characterized in that, described read requests receiving element catches the file read request driven from upper strata at system kernel layer.
46. devices according to claim 45, is characterized in that, described document reading unit, described first fragment data reading unit, described second fragment data reading unit and described file data construction unit perform at systematic difference layer.
47. devices according to claim 46, also comprise: at the read requests response unit of system kernel layer, drive for described file data to be returned to upper strata in the address of core buffer and the size of described file data.
48. devices according to claim 47, is characterized in that, described file identification comprises file path and file name.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410197109.9A CN103955528B (en) | 2014-05-09 | 2014-05-09 | The method of writing in files data, the method for file reading data and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410197109.9A CN103955528B (en) | 2014-05-09 | 2014-05-09 | The method of writing in files data, the method for file reading data and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103955528A CN103955528A (en) | 2014-07-30 |
| CN103955528B true CN103955528B (en) | 2015-09-23 |
Family
ID=51332803
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410197109.9A Expired - Fee Related CN103955528B (en) | 2014-05-09 | 2014-05-09 | The method of writing in files data, the method for file reading data and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103955528B (en) |
Families Citing this family (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105631347B (en) * | 2014-10-27 | 2018-11-09 | 鸿富锦精密工业（深圳）有限公司 | File access method and client terminal device |
| CN104881466B (en) * | 2015-05-25 | 2018-09-07 | 百度在线网络技术（北京）有限公司 | The processing of data fragmentation and the delet method of garbage files and device |
| CN105208005B (en) * | 2015-08-25 | 2019-10-11 | 宇龙计算机通信科技(深圳)有限公司 | A kind of fingerprint verification method, connection equipment and terminal device |
| CN105117306A (en) * | 2015-08-31 | 2015-12-02 | 联想(北京)有限公司 | Information processing method and electronic apparatus |
| CN105335463B (en) * | 2015-09-23 | 2018-09-25 | 广州市中崎商业机器股份有限公司 | A kind of date storage method and method for quickly reading for cashing machine |
| EP3376394B1 (en) * | 2015-12-30 | 2022-09-28 | Huawei Technologies Co., Ltd. | Method and device for processing access request, and computer system |
| EP3385846B1 (en) | 2015-12-30 | 2020-02-12 | Huawei Technologies Co., Ltd. | Method and device for processing access request, and computer system |
| CN107436725B (en) | 2016-05-25 | 2019-12-20 | 杭州海康威视数字技术股份有限公司 | Data writing and reading methods and devices and distributed object storage cluster |
| CN106657213B (en) * | 2016-09-14 | 2020-04-07 | 深圳峰创智诚科技有限公司 | File transmission method and device |
| CN107957919A (en) * | 2016-10-14 | 2018-04-24 | 北京京东尚科信息技术有限公司 | Data disaster tolerance system, method and apparatus |
| CN107066890B (en) * | 2017-04-25 | 2020-12-25 | 腾讯科技（深圳）有限公司 | Method and device for encrypting file by using obfuscation processing |
| CN110321727A (en) | 2018-03-29 | 2019-10-11 | 阿里巴巴集团控股有限公司 | The storage of application information, processing method and processing device |
| WO2020006715A1 (en) * | 2018-07-04 | 2020-01-09 | 华为技术有限公司 | Data storage method and apparatus, and related device |
| CN109871698B (en) * | 2019-01-14 | 2021-10-26 | 深圳市奥特尔软件技术有限公司 | Data processing method, data processing device, computer equipment and storage medium |
| CN110018999B (en) * | 2019-04-15 | 2023-07-11 | 深信服科技股份有限公司 | File management method and system, electronic equipment and storage medium |
| CN110727639B (en) * | 2019-10-08 | 2023-09-19 | 深圳市网心科技有限公司 | Fragment data reading method, electronic device, system and medium |
| CN111078653B (en) * | 2019-10-29 | 2023-03-24 | 厦门网宿有限公司 | Data storage method, system and equipment |
| CN111858746A (en) * | 2020-05-27 | 2020-10-30 | 武汉瞬付科技有限公司 | Personal data storage system based on cloud platform |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101504670A (en) * | 2009-03-04 | 2009-08-12 | 成都市华为赛门铁克科技有限公司 | Data operation method, system, client terminal and data server |
| CN103607393A (en) * | 2013-11-21 | 2014-02-26 | 浪潮电子信息产业股份有限公司 | Data safety protection method based on data partitioning |
-
2014
- 2014-05-09 CN CN201410197109.9A patent/CN103955528B/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN103955528A (en) | 2014-07-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103955528B (en) | The method of writing in files data, the method for file reading data and device | |
| US10409990B2 (en) | Encryption and decryption method and apparatus in virtualization system, and system | |
| EP2751734B1 (en) | Sector map-based rapid data encryption policy compliance | |
| US20100217977A1 (en) | Systems and methods of security for an object based storage device | |
| JP5648209B2 (en) | Storage system having encryption key selection device and encryption key selection method | |
| US20210157797A1 (en) | Method and system for data storage and retrieval | |
| US8689279B2 (en) | Encrypted chunk-based rapid data encryption policy compliance | |
| EP2161673A1 (en) | Method and system for protecting data | |
| EP2759943A1 (en) | File encryption method and device, file decryption method and device | |
| US20100169672A1 (en) | Encryption program operation management system and program | |
| US20110264925A1 (en) | Securing data on a self-encrypting storage device | |
| EP2631833A1 (en) | Method, device and system for verifying binding data card and mobile host | |
| EP1983461A3 (en) | External storage apparatus and method of preventing information leakage | |
| US20090296937A1 (en) | Data protection system, data protection method, and memory card | |
| US20080076355A1 (en) | Method for Protecting Security Accounts Manager (SAM) Files Within Windows Operating Systems | |
| US9098713B2 (en) | Clipboard protection system in DRM environment and recording medium in which program for executing method in computer is recorded | |
| US20100205460A1 (en) | Encryption method for digital data memory card and assembly for performing the same | |
| US20070239996A1 (en) | Method and apparatus for binding computer memory to motherboard | |
| JP6511161B2 (en) | Data file protection | |
| TW201234210A (en) | Method for loading a code of at least one software module | |
| CN110650191A (en) | Data read-write method of distributed storage system | |
| CN101169971A (en) | Electronic hard disk | |
| US20180314837A1 (en) | Secure file wrapper for tiff images | |
| CN112711764A (en) | Data reading and writing method and device and electronic equipment | |
| JP5971820B2 (en) | Method and apparatus for using data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent for invention or patent application | ||
| CB02 | Change of applicant information |
Address after: 100103, Beijing, Chaoyang District, Cui Zhuang Township, home village, 1 West Road, row 1 hospital Applicant after: BEIJING HUAXINBOYAN TECHNOLOGY CO., LTD. Address before: 100103, Beijing, Chaoyang District, Cui Zhuang Township, home village, 1 West Road, row 1 hospital Applicant before: BEIJING HUAXINBOYAN TECHNOLOGY CO., LTD. |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: APPLICANT; FROM: BEIJING HUAXINBOYAN TECHNOLOGY CO., LTD. TO: BEIJING HUAXIN ANTIAN INFORMATION TECHNOLOGY CO., LTD. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150923 Termination date: 20180509 |