CN102567670A - Filter drive encryption implementing method for file system - Google Patents
Filter drive encryption implementing method for file system Download PDFInfo
- Publication number
- CN102567670A CN102567670A CN2011104476507A CN201110447650A CN102567670A CN 102567670 A CN102567670 A CN 102567670A CN 2011104476507 A CN2011104476507 A CN 2011104476507A CN 201110447650 A CN201110447650 A CN 201110447650A CN 102567670 A CN102567670 A CN 102567670A
- Authority
- CN
- China
- Prior art keywords
- file
- encryption
- size
- identification structure
- encryption identification
- 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
Landscapes
- Storage Device Security (AREA)
Abstract
The invention discloses a filter drive encryption implementing method for a file system. The encryption method comprises the following steps of: 1, after a drive program is started and when an opened file is returned to an application program, acquiring the name and the size of the file; 2, judging whether the progress of opening the file is a confidential progress; 3, if the size of the file is greater than that of an encryption identification structure, reading information of the same size from the header of the file and comparing the information with the information of the encryption identification structure; and 4, when the file is read and if the file is an encrypted file, performing decryption; and when the file is returned to the application program, judging whether the original file is an encrypted file in write operation, if so, encrypting the file and storing the file into a disc file, otherwise, directly storing the file into the disc file without encryption. Compared with the conventional file filter drive, the method has the advantage that: the kernel developer of Microsoft develops a new drive which is called as a filter manager.
Description
Technical field
The present invention proposes in Drive Layer and realize encryption and decryption scheme, mainly solved process in the transparent encryption and decryption of Drive Layer to file, more safe.
Background technology
Microfiltration drives encryption technology, and it is operated in the inner nuclear layer of Windows based on Windows file system actuation techniques.When application program was opened the process of appointment, this driving can monitor the operation of program, and changed it and open, modes of operation such as read-write, thus reach the effect of transparent encryption and decryption.Compare with traditional application layer encryption, it is because can be more safely and efficiently at bottom.
It is compared with traditional filtration drive, and filtering the manager model has following advantage:
● loading sequence is more easy to control, drives unlike traditional filtering, and minifilter drives and can at any time be loaded and be bound to suitable position because of its Altitude.
● at the offloading capacity of system's run duration.The traditional filtering that the system run duration of being unlike in can not be unloaded drives, and the minifilter driving can be unloaded at any time and it can stop its unloaded itself in case of necessity.The safety that bodies are bound in all minifilter drivings synchronously of filtration manager removes, and it can handle the operation that the unloading of minifilter driving quilt is accomplished afterwards.
● only need handle the ability of necessary operation.In this model, can select the own interested I/O operation types that will filter (based on IRP, fast I/O or FSFilter).Minifilter drives the I/O operation that receives only it and registered callback routines for it.Microfiltration drives can register a unique pre-oper or post-oper callback routine, or both's registration, and it can ignore the operation of some type, such as the I/O of paging I/O and buffer memory.
● the application of kernel stack is more efficient.Filter manager and use " callback " model, filter manager and filter the conflict that initialized I/O (this only can be driven by low layer in the stack and see) has reduced recurrence I/O through supporting non-reentry.
● be easier to add new operation.Microfiltration drives and to be merely its I/O that will handle operation registration, and the support of new operation can existingly be filtered in the manager for being added under the prerequisite of filtration drive not destroying.
● allow micro-filter to have private data information (volume context, instance context, flow context, stream handle context and context) to a system object.
● to the better support of user mode application.Filter manager for general utility functions to be provided with user mode services of working and control program for filtration drive.Filter manager user model storehouse, Filterlib.dll has activated the communication between driving with minifilter of user mode services or control program.Filterlib.dll also provides interface for management tool.
Summary of the invention
Technical matters: the purpose of this invention is to provide a kind of file system filter and drive the encryption implementation method,
Compare with traditional filter Driver on FSD, the kernel developer of Microsoft has developed a new driving, is called the filtration manager, but this driving traditional file system filter driving exactly itself.But this driving provides interface, accepts the kernel module that some were registered.Therefore just given the filtration manager to the operation of basic I RP.
Technical scheme: it is following that file system filter of the present invention drives the concrete performing step of encryption implementation method:
The first step, driver at first obtains filename and file size after starting when open file operation returns to application program,
Second step, judge subsequently whether the process that opens file is that secret process is opened, if secret process further judges so whether the size of file is zero this moment,, and to carry out write operation if the size of file is zero, then at first write the encryption identification head,
In the 3rd step, if the size of file greater than encryption identification structure size, reads onesize information earlier from top of file and encryption identification structure information compares, identical explanation is an encrypt file; If file does not then process less than the encryption identification structure,
The 4th step is when reading file, if the file of having encrypted; At first carry out decryption oprerations, returning to application program, when write operation; Judge at first whether this document was encrypt file originally, if carry out storing in the disk file after the encryption; If not, then do not carry out encryption, directly store on the disk file.
The 3rd step, described elder generation read onesize information and encryption identification structure information compares from top of file, and specifically implementation method is:
According to the size of self-defining encryption identification structure, from top of file, read onesize content, and it is forced to convert to encryption identification structure type, compare content that reads and encryption identification structure information byte-by-byte then.
Beneficial effect: the good managing file system microfiltration of these two structure physical efficiencys drives all information of registration, and the various types of message after can processing registration accurately and timely.The ContextRegistration the most meaningfully in first structure wherein, OperationRegistration, FilterUnloadCallback its objective is InstanceSetupCallback, InstanceQueryTeardownCallback.ContextRegistration is used to register contextual information; Call back function when OperationRegistration is location registration process I/O request; FilterUnloadCallback is used to unload the operation that need do when driving; InstanceSetupCallback calls when new volume is mounted being used for, and its objective is in order Minifilter to be driven can monitor the installation of volume and to remove, thereby dynamic installing M inifilter drives; InstanceQueryTeardownCallback manually removes the user to be called when Minifilter drives.Second structure is to this territory OperationRegistration detailed structure, handles the IRP request of appointment.
Description of drawings
Fig. 1 is the file request procedure chart, and supporting paper layer user model is delivered to the flow process of kernel mode.
Fig. 2 is drive functional module figure.
Fig. 3 is the application communication high-level schematic functional block diagram.
Fig. 4 is a flowchart.
Fig. 5 is little file system registration process figure, FltRegisterFilter wherein, and FltStartMinifilter, FltCreateCommunicationPort are the system library functions.
Fig. 6 creates self-defined input and output request package synoptic diagram, IoGetDeviceAttachmentBaseRef wherein, and IoAllocateIrp, IoSetCompletionRoutine, IoCallDriver are the system library functions.
Embodiment
Filter manager and be mounted, but it only drives at a Minifilter and be loaded Shi Caihui and work, filter manager and be tied on the file system stack of target volume with Windows.Minifilter drives the I/O operation that will filter for it and is tied to indirectly on the file system stack through registering to the filtration manager.
As traditional filtration drive, the binding that Minifilter drives is also according to a specific order.But, the order of binding body is to make the unique identifier of Altitude determine by one.The binding body that Minifilter drives a specific altitude on certain volume is called as the instance that this Minifilter drives.
The Altitude that Minifilter drives guarantees that its instance always is loaded in corresponding position, and its decision is filtered manager and what calls Minifilter with in proper order driven and handle I/O.Altitudes is distributed and management by Microsoft.
Minifilter drives and can filter IRP-I/O operation, Fast I/O and FSFilter Callback operation.But it only can be registered own interested operation, and it can register a pre-oper callback routine I/O operation that can it will filter to each, and post-oper callback routine or the two are all registered.When handling an I/O operation, filter manager and call the callback routine that each Minifilter operates registration for this reason.When this callback routine is returned, filter manager and call next minifilter driving callback routine of operation registration for this reason.
Give an example; Suppose that three Minifilter drivings among Fig. 1 all are that the callback routine has been registered in same I/O operation; Then filtering manager can be with altitude order (A from high to low; B C) calls their pre-oper callback routine, forwards to next more rudimentary driving to this I/O operation then and further handles.When strainer tube reason device received the completion of this I/O request, (C, B A) called the post-oper callback routine that each Minifilter drives promptly from low to high with opposite order for it.
System framework
Encipherment scheme is by two parts, and the filtration drive of first bottom, its function comprise following several main aspect: the 1) judgement of secret process (process that needs are kept watch on); 2) judgement of encryption and decryption point: whether the file that this process is opened is encrypted; 3) filename obtains; Whether 4) the setting of encryption identification is distinguished and is encrypted; 5) encryption and decryption operation.
It two is DLL programs that application layer is set up, and comprises following major function: 1) the connection initialization of COM1; 2) Data transmission is closed this port behind closing application program.
Functional structure
The purpose of filter driving layer is to accomplish the judgement of secret process, obtains filename, the judgement of encryption and decryption point, and with the application layer communication port, encryption identification setting, file encryption-decryption.Concrete functional structure is as shown in Figure 2:
● obtain the filename module
It is carried out when File Open or establishment, is used for obtaining the absolute path of file, for later operation is prepared.
● secret process module
After obtaining filename, can carry out this module, accomplish the judgement of process type, whether be the process (carrying out encryption and decryption handles) that needs special processing.
● the encryption and decryption point module
When being secret process, when carrying out this module, when opening existing file, if file size is non-vanishing; At first, read the front part of file header, size is the size of encryption identification structure; If encryption identification, then explanation is the file of encrypting, and can operate; If not, then be left intact, directly give lower floor and drive.When file size is zero, and write operation will be carried out the time, then at first at first write the encryption identification data at top of file.
● the encryption and decryption identification module
This module is used for the content of initialization encryption identification structure.
● the encryption and decryption module
When file carries out write operation, in writing the pre-operation call back function, automatically file content is carried out encryption and storing in the disk file; When reading file, in reading back operation call back function, automatically this document is carried out decryption oprerations and returning to user program.
● communications port module
Communicating by letter of user's attitude and kernel state for ease, this module is accomplished and is received the information that user's attitude is transmitted into, and to returning to the user after the information processing.
The purpose of the DLL program that application layer is set up is the COM1 of accomplishing with Drive Layer that is connected, Data transmission.The concrete function structural drawing is as shown in Figure 3:
● connect the driving communications port module
This module is accomplished the connection that is established to the bottom layer driving port, for following transmission data are prepared.
● communication module
On the basis of successful connection, the data message that returns after accomplishing downward bottom layer driving transfer data information and accepting processing.
Method flow
Driver at first in the back operation call back function of IRP_MJ_CREATE, obtains the comspec and the file size of file after starting; Judge subsequently whether the process that opens file is that secret process is opened, if, if the size of file is zero, and to carry out write operation, then at first write the encryption identification head; If file size greater than encryption identification structure size, reads onesize file header earlier and the encryption identification head compares, identical explanation is an encrypt file; If file size does not then process less than encryption identification structure size.When reading file,, returning to application program if the file of having encrypted at first carries out decryption oprerations.When write operation, at first carry out after the encryption in storing disk file into.Concrete work is as shown in Figure 4:
Key data structure
When registering filtrator as, we need fill in the data structure of a micro-filter registration structure by name (FLT_REGISTRATION), and it defines as follows:
The Size in first territory representes the size of FLT_REGISTRATION structure.
Second territory Version is version number, for this territory, directly fills in FLT_REGISTRATION_VERSION by convention.
The 3rd territory Flags is zone bit, the operation whether mark will receive this type.Have two kinds to manage: a kind of managing is NULL, uneven any effect; Another kind manages then to be set to FLTFL_REGISTRATION_DO_NOT_SUPPORT_SERVICE_STOP; Representative Minifilter when stopping to serve can not influence and can not call FilterUnloadCallback, even FilterUnloadCallback is not NULL.
The 4th territory
ContextRegistration: context registration, the contextual function of location registration process.
The 5th territory is
OperationRegistration: the operation call back function is focused volume.The file operation call back function that we will filter is write therein, can define the corresponding call back function of all functions code.Use following structure during registration:
MajorFunctionThe I/O operation that the territory explanation will be handled, it can not be sky.
Flags is a zone bit.It has three kinds of literary styles: first kind is a little 0, and this sign only calls useful to read-write; Second kind is to write FLTFL_OPERATION_REGISTRATION_SKIP_CACHED_IO, and the buffering read-write requests is not filtered in expression; The third is FLTFL_OPERATION_REGISTRATION_SKIP_PAGING_IO, and the paging read-write requests is not filtered in expression.Ensuing two territories are pre-operation call back function and back operation call back function.
ReservedlBe for system uses, must be set to NULL.
1) registration of little file system filter
Registration is that registering one is in the entrance function DriverEntry of driver, to carry out to the existence of filtering manager declaration filtrator, and step is illustrated in fig. 5 shown below:
In the FltRegisterFilter registration function, set the various IRP operations that we need handle, concrete structure such as top data structure introduction.
The FltCreateCommunicationPort function prototype is following:
There are three call back functions the inside, is used for and application layer communication, and is as shown in table 1 below:
| ConnectNotifyCallback | It is the function that user's attitude and kernel state can call when connecting |
| DisconnectNotifyCallback | Be that user's attitude is connected the function that can call when finishing with kernel state |
| MessageNotifyCallback | The function that can call when being user's attitude and kernel state Data transmission |
The little file system filter registered callbacks of table 1 function declaration table
2) filename obtains
Obtain filename and generally in the back operation call back function of IRP_MJ_CREATE, carry out, it is the process of when opening file, at first carrying out.Call the structure that FltGetFileNameInformation obtains the file name information of a file.And in this function, can obtain three kinds of file name informations according to the difference of demand, the NameOptions value in the function prototype is as follows:
We need be arranged to FLT_FILE_NAME_NORMALIZED to him in this this program.
3) refresh the progress information tabulation
In this call back function of MessageNotifyCallback, can handle according to application layer message transmitted sign indicating number and to refresh process list, application layer is through the form Data transmission content of self-defined structure body; It comprises process name; Process ID, whether the sign whether process also exists is made as information such as monitoring process; One list structure is arranged in Drive Layer; When receiving this message, can in chained list, check each progress information one by one according to process ID, if do not exist this process just to join this progress information in the chained list node in this chained list; If have, then relatively whether process exists sign, if this process of FALSE explanation does not exist, from chained list this knot removal.
4) how to judge that this process is secret process
Application program transfer data information the time; Will refresh process list at set intervals, and its information stores in a structure, and be the process tag of appointment crypto process; Represent with a BOOLEAN type variable, pass to the driver the inside in bar structure body information.And drive the inside a same structure is arranged also, using the form of chained list is the information representation of each process that a node couples together, and stores the information of all processes.
At first call PsGetCurrentProcessId and obtain ID number of current process, in the process chained list, search this ID then, find the back just can know whether be secret process according to the secret process identification (PID) symbol in the node.
5) how to judge file encryption information
Realize the difficult point that the filtration drive file system is encrypted is exactly how to judge whether this document has been encrypted.Native system has adopted a kind of simple mode; Create a file encryption marking structure body; All fill the structure of same content at the top of file of encrypt file; The partial content that so at first reads file header compares just to judge whether file is encrypted with it, if identical explanation is the file of encrypting, different explanations are the files that do not have encryption.
6) the input and output request package of establishment oneself
When creating the input and output request package request of oneself, have only the filtrator below this filtrator just can receive these I/O requests, concrete implementation is illustrated in fig. 6 shown below:
Application layer procedure is opened and when reading file, in the back operational processes function of the IRP_MJ_CREATE of Drive Layer, uses the data that self-defined input and output request package reads flag information structure size.
Claims (2)
1. a file system filter drives and encrypts implementation method, it is characterized in that the concrete performing step of this encryption method is following:
The first step, driver at first obtains filename and file size after starting when open file operation returns to application program,
Second step, judge subsequently whether the process that opens file is that secret process is opened, if secret process further judges so whether the size of file is zero this moment,, and to carry out write operation if the size of file is zero, then at first write the encryption identification head,
In the 3rd step, if the size of file greater than encryption identification structure size, reads onesize information earlier from top of file and encryption identification structure information compares, identical explanation is an encrypt file; If file does not then process less than the encryption identification structure,
The 4th step is when reading file, if the file of having encrypted; At first carry out decryption oprerations, returning to application program, when write operation; Judge at first whether this document was encrypt file originally, if carry out storing in the disk file after the encryption; If not, then do not carry out encryption, directly store on the disk file.
2. file system filter according to claim 1 drives encrypts implementation method, it is characterized in that the 3rd step described elder generation reads onesize information with encryption identification structure information compares from top of file, and specifically implementation method is:
According to the size of self-defining encryption identification structure, from top of file, read onesize content, and it is forced to convert to encryption identification structure type, compare content that reads and encryption identification structure information byte-by-byte then.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011104476507A CN102567670A (en) | 2011-12-28 | 2011-12-28 | Filter drive encryption implementing method for file system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011104476507A CN102567670A (en) | 2011-12-28 | 2011-12-28 | Filter drive encryption implementing method for file system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102567670A true CN102567670A (en) | 2012-07-11 |
Family
ID=46413053
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011104476507A Pending CN102567670A (en) | 2011-12-28 | 2011-12-28 | Filter drive encryption implementing method for file system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102567670A (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103218575A (en) * | 2013-04-17 | 2013-07-24 | 武汉元昊科技有限公司 | Host file security monitoring method |
| CN104123371A (en) * | 2014-07-25 | 2014-10-29 | 上海交通大学 | Transparent Windows kernel file filtering method based on hierarchical file system |
| CN104360869A (en) * | 2014-12-03 | 2015-02-18 | 飞天诚信科技股份有限公司 | Method for preventing underlying driver from intercepting messages |
| CN104750675A (en) * | 2015-04-01 | 2015-07-01 | 山东省计算中心（国家超级计算济南中心） | Identification method for encrypted file of unknown format |
| CN105701409A (en) * | 2015-12-29 | 2016-06-22 | 北京金山安全软件有限公司 | Method and device for realizing file virtualization |
| CN106599728A (en) * | 2016-12-02 | 2017-04-26 | 山东中创软件商用中间件股份有限公司 | File filtering drive framework-based system file protection method and apparatus |
| CN107292196A (en) * | 2017-06-27 | 2017-10-24 | 北京华云网际科技有限公司 | The reading/writing method and device of I/O data |
| CN108304695A (en) * | 2018-01-30 | 2018-07-20 | 云易天成（北京）安全科技开发有限公司 | Anti-data-leakage control method, the system of object oriented file outgoing |
| CN109144893A (en) * | 2018-09-11 | 2019-01-04 | 郑州云海信息技术有限公司 | A kind of method and apparatus with Nonvolatile memory reservoir process interaction |
| CN109784041A (en) * | 2018-12-29 | 2019-05-21 | 360企业安全技术(珠海)有限公司 | Event-handling method and device and storage medium and electronic device |
| CN111831363A (en) * | 2020-09-16 | 2020-10-27 | 上海二三四五网络科技有限公司 | Control method and device for registry data operation |
| CN112035885A (en) * | 2020-08-26 | 2020-12-04 | 山谷网安科技股份有限公司 | Transparent encryption and decryption file driving method based on minifilter and usbkey |
| CN112100631A (en) * | 2020-08-11 | 2020-12-18 | 福建天泉教育科技有限公司 | Processing method and terminal for judging encryption of PPTX (Power Point X) document |
| CN113221171A (en) * | 2021-05-21 | 2021-08-06 | 杭州弗兰科信息安全科技有限公司 | Encrypted file reading and writing method and device, electronic equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101256570A (en) * | 2008-02-22 | 2008-09-03 | 山东中创软件工程股份有限公司 | File protection technique based on Windows system files filtering drive |
-
2011
- 2011-12-28 CN CN2011104476507A patent/CN102567670A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101256570A (en) * | 2008-02-22 | 2008-09-03 | 山东中创软件工程股份有限公司 | File protection technique based on Windows system files filtering drive |
Non-Patent Citations (3)
| Title |
|---|
| 徐翔: "文件保护系统中透明加解密技术的设计与实现", 《中国优秀硕士学位论文全文数据库（电子期刊）信息科技辑》 * |
| 景征骏等: "基于可信进程的文档加解密系统", 《计算机工程》 * |
| 陈福源: "文档透明加密系统的设计与实现", 《中国优秀硕士学位论文全文数据库（电子期刊）信息科技辑》 * |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103218575A (en) * | 2013-04-17 | 2013-07-24 | 武汉元昊科技有限公司 | Host file security monitoring method |
| CN104123371A (en) * | 2014-07-25 | 2014-10-29 | 上海交通大学 | Transparent Windows kernel file filtering method based on hierarchical file system |
| CN104123371B (en) * | 2014-07-25 | 2017-09-29 | 上海交通大学 | The method of the transparent filtering of Windows kernel files based on hierarchical file system |
| CN104360869A (en) * | 2014-12-03 | 2015-02-18 | 飞天诚信科技股份有限公司 | Method for preventing underlying driver from intercepting messages |
| CN104360869B (en) * | 2014-12-03 | 2017-05-10 | 飞天诚信科技股份有限公司 | Method for preventing underlying driver from intercepting messages |
| CN104750675A (en) * | 2015-04-01 | 2015-07-01 | 山东省计算中心（国家超级计算济南中心） | Identification method for encrypted file of unknown format |
| CN104750675B (en) * | 2015-04-01 | 2017-09-26 | 山东省计算中心（国家超级计算济南中心） | A kind of unknown format encrypts the recognition methods of file |
| CN105701409B (en) * | 2015-12-29 | 2019-05-17 | 珠海豹趣科技有限公司 | A kind of method and device for realizing file virtualization |
| CN105701409A (en) * | 2015-12-29 | 2016-06-22 | 北京金山安全软件有限公司 | Method and device for realizing file virtualization |
| CN106599728A (en) * | 2016-12-02 | 2017-04-26 | 山东中创软件商用中间件股份有限公司 | File filtering drive framework-based system file protection method and apparatus |
| CN107292196A (en) * | 2017-06-27 | 2017-10-24 | 北京华云网际科技有限公司 | The reading/writing method and device of I/O data |
| CN108304695A (en) * | 2018-01-30 | 2018-07-20 | 云易天成（北京）安全科技开发有限公司 | Anti-data-leakage control method, the system of object oriented file outgoing |
| CN109144893A (en) * | 2018-09-11 | 2019-01-04 | 郑州云海信息技术有限公司 | A kind of method and apparatus with Nonvolatile memory reservoir process interaction |
| CN109784041A (en) * | 2018-12-29 | 2019-05-21 | 360企业安全技术(珠海)有限公司 | Event-handling method and device and storage medium and electronic device |
| CN112100631A (en) * | 2020-08-11 | 2020-12-18 | 福建天泉教育科技有限公司 | Processing method and terminal for judging encryption of PPTX (Power Point X) document |
| CN112100631B (en) * | 2020-08-11 | 2022-09-06 | 福建天泉教育科技有限公司 | Processing method and terminal for judging encryption of PPTX (Power Point X) document |
| CN112035885A (en) * | 2020-08-26 | 2020-12-04 | 山谷网安科技股份有限公司 | Transparent encryption and decryption file driving method based on minifilter and usbkey |
| CN112035885B (en) * | 2020-08-26 | 2023-03-28 | 山谷网安科技股份有限公司 | Transparent encryption and decryption file driving method based on minifilter and usbkey |
| CN111831363A (en) * | 2020-09-16 | 2020-10-27 | 上海二三四五网络科技有限公司 | Control method and device for registry data operation |
| CN113221171A (en) * | 2021-05-21 | 2021-08-06 | 杭州弗兰科信息安全科技有限公司 | Encrypted file reading and writing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102567670A (en) | Filter drive encryption implementing method for file system | |
| CN102096625B (en) | Monitor and track application service condition | |
| US11748151B1 (en) | Systems and methods for editing, assigning, controlling, and monitoring bots that automate tasks, including natural language processing | |
| CN101646995B (en) | Data stream filters and plug-ins for storage managers | |
| CN101983380A (en) | Simultaneous collaborative review of a document | |
| CN101840471B (en) | Document right control method and device | |
| US20080016085A1 (en) | Methods and Systems For Simultaneously Accessing Multiple Databses | |
| CN113383330A (en) | Creation and execution of secure containers | |
| CN101499027A (en) | Intelligent memory system based on independent kernel and distributed architecture | |
| CN102469035A (en) | Cross-process communication method and device | |
| EP1622066A4 (en) | Tag, and method and system using the same | |
| CN107329806A (en) | A kind of development environment construction method and device | |
| CN101799853A (en) | Hierarchical information encryption sharing method | |
| CN109743354A (en) | A kind of cloudy tubular container cluster method of boarding at the nursery | |
| CN106775804A (en) | A kind of mobile terminal and its RFID read-write equipment adaptation method and device | |
| CN110134646B (en) | Knowledge platform service data storage and integration method and system | |
| CN102750202A (en) | Data protection method and device | |
| CN105955773A (en) | System upgrading method and device | |
| CN102073553A (en) | File recovery method and device | |
| US9350595B1 (en) | System and method for serializing and deserializing data objects into a single binary stream | |
| CN105550582B (en) | Access the method and system of virtual disk | |
| CN102004653B (en) | Image forming apparatus and installation method | |
| CN102081920B (en) | Method and device for controlling picture display | |
| CN110489060A (en) | A kind of mixed file construction method and its system based on FUSE technology | |
| US8498622B2 (en) | Data processing system with synchronization policy |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20120711 |