CN104537110A - Data writing method and device - Google Patents
Data writing method and device Download PDFInfo
- Publication number
- CN104537110A CN104537110A CN201510026045.0A CN201510026045A CN104537110A CN 104537110 A CN104537110 A CN 104537110A CN 201510026045 A CN201510026045 A CN 201510026045A CN 104537110 A CN104537110 A CN 104537110A
- Authority
- CN
- China
- Prior art keywords
- described data
- data
- database
- time period
- client
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2462—Approximate or statistical queries
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Probability & Statistics with Applications (AREA)
- Computational Linguistics (AREA)
- Fuzzy Systems (AREA)
- Mathematical Physics (AREA)
- Software Systems (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a data writing method and device. The method includes the steps of receiving data transmitted by the a client terminal; querying database logs according to attribute information of the data so as to judge whether the data have been stored in a database or not; storing the data into a cache device if the data are not stored in the database; returning successful uploading information to the client terminal. By means of the technical scheme, the data written rate of a user can be improved, and the operation experience of the user is improved.
Description
Technical field
The present invention relates to technical field of data processing, particularly relate to a kind of method for writing data and device.
Background technology
Along with the development of Internet technology, increasing data need to store in a database, carry out statistics and analysis to facilitate user.
In correlation technique, user often needs, first by the data write into Databasce of renewal, then to carry out statistical study by database root according to all data stored, to generate the statistics that user needs to inquire about.In this process, the speed that user writes data will directly affect the experience of user.
Summary of the invention
In view of this, the invention provides a kind of method for writing data and device.
Particularly, the present invention is achieved through the following technical solutions:
A kind of method for writing data, described method comprises:
Receive the data that client sends;
According to the attribute information Query Database daily record of described data, to judge whether stored described data in database;
If do not store described data in database, then described data are preserved in the buffer;
Return to client and upload successful message.
Further, after returning to client and uploading successful message, also comprise:
Described data write into Databasce in the buffer will be preserved.
Further, the attribute information of described data is the time period information of described data;
The described attribute information Query Database daily record according to described data, to judge whether stored described data in database, comprising:
If the time period of the time period of described database journal and described data does not occur simultaneously, then confirm not store described data in database;
If the time period of described database journal comprises the time period of described data, then confirm to store described data in database.
Further, described method also comprises:
If there is common factor the time period of the time period of described database journal and described data, and common factor is not the time period of described data, then described data preserved in the buffer.
Further, described method also comprises:
Receive the Data Statistics Inquiry Through instruction that client sends;
According to described Data Statistics Inquiry Through instruction, from the middle table that database is preset, obtain Query Result, described Query Result is generated by statistics of database after by described data write into Databasce;
Described Query Result is returned client.
A kind of data transfer apparatus, described device comprises:
Data receipt unit, for receiving the data that client sends;
Store judging unit, for the attribute information Query Database daily record according to described data, to judge whether stored described data in database;
Described data, during for not storing described data in a database, are preserved in the buffer by data saving unit;
Successfully returning unit, uploading successful message for returning to client.
Further, described device also comprises:
Data write unit, for after returning to client and uploading successful message, will preserve described data write into Databasce in the buffer.
Further, the attribute information of described data is the time period information of described data;
Described storage judging unit, specifically when the time period of described database journal and the time period of described data do not occur simultaneously, confirms not store described data in database;
When the time period of described database journal comprises the time period of described data, confirm to store described data in database.
Further, described data saving unit, is further used for there is common factor in the time period of described database journal and the time period of described data, and when common factor is not the section time period of described data, described data is preserved in the buffer.
Further, described device also comprises:
Inquire-receive unit, for receiving the Data Statistics Inquiry Through instruction that client sends;
Result acquiring unit, for according to described Data Statistics Inquiry Through instruction, from the middle table that database is preset, obtain Query Result, described Query Result is generated by statistics of database after by described data write into Databasce;
Result returns unit, for described Query Result is returned client.
Described as can be seen from above, service end of the present invention is when receiving the data that client sends, can according to the attribute information Query Database daily record of data, to judge whether stored described data in database, and when not storing described data in a database, described data are preserved in the buffer, then returns to client and upload successful message, and then promote the speed that user writes data, promote the operating experience of user simultaneously.
Accompanying drawing explanation
Fig. 1 is the process flow diagram of a kind of method for writing data shown in the present invention one exemplary embodiment.
Fig. 2 is the method flow diagram of a kind of Data Statistics Inquiry Through shown in the present invention one exemplary embodiment.
Fig. 3 is the structural representation of a kind of service end shown in the present invention one exemplary embodiment.
Fig. 4 is the structural representation of a kind of data transfer apparatus shown in the present invention one exemplary embodiment.
Embodiment
Here will be described exemplary embodiment in detail, its sample table shows in the accompanying drawings.When description below relates to accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawing represents same or analogous key element.Embodiment described in following exemplary embodiment does not represent all embodiments consistent with the present invention.On the contrary, they only with as in appended claims describe in detail, the example of apparatus and method that aspects more of the present invention are consistent.
The term used in the present invention is only for the object describing specific embodiment, and not intended to be limiting the present invention." one ", " described " and " being somebody's turn to do " of the singulative used in the present invention and appended claims is also intended to comprise most form, unless context clearly represents other implications.It is also understood that term "and/or" used herein refer to and comprise one or more project of listing be associated any or all may combine.
Term first, second, third, etc. may be adopted although should be appreciated that to describe various information in the present invention, these information should not be limited to these terms.These terms are only used for the information of same type to be distinguished from each other out.Such as, without departing from the present invention, the first information also can be called as the second information, and similarly, the second information also can be called as the first information.Depend on linguistic context, word as used in this " if " can be construed as into " ... time " or " when ... time " or " in response to determining ".
For the problems referred to above, the invention provides a kind of data writing scheme, effectively may improve the speed that user writes data, and then promote the experience of user.
Fig. 1 is the process flow diagram of a kind of method for writing data shown in the present invention one exemplary embodiment.
Please refer to Fig. 1, the invention provides a kind of method for writing data, described method can be applied in service end, and such as: Web server etc., described method for writing data can comprise the following steps:
Step 101, receives the data that client sends.
In the present embodiment, user can by the client upload data of loading in terminal.The described data that the user that service end receives client transmission uploads.
Step 102, according to the attribute information Query Database daily record of described data, to judge whether stored described data in database.If do not store described data in database, then perform step 103.
In the present embodiment, service end, after receiving described data, obtains the attribute information of described data, then according to the daily record of described attribute information Query Database, to judge whether stored described data in database, the attribute information of described data is the time period information of described data.
Particularly, the described data that client sends have generally included many subdatas, and wherein, every bar subdata all has self temporal information.In the present embodiment, time period of forming of time the earliest and time the latest in the time period information of the described data temporal information that is subdatas all in described data.For example, suppose that described data are the call detailed list of client, the subdata that described data comprise is the message registration in described call detailed list.For each message registration in described call detailed list, all to there being an air time, then in the present embodiment, the attribute information of described data is the time period of client's call detailed list.If the air time of a message registration in described call detailed list is the earliest on March 1st, 2014, the air time of a message registration is on April 1st, 2014 the latest, then the time period of the call detailed list of this client is on April 1,1 day to 2014 March in 2014, and namely the time period information of described data is on April 1,1 day to 2014 March in 2014.
In this step, service end according to the time period information inquiry database journal of described data, to judge whether stored described data in database.Particularly, for database, terminal or service end all can be recorded in database journal the write operation of database, therefore, in the present invention, service end can be occured simultaneously by judging whether the time period of described database journal and the time period of described data exist to judge whether stored described data, the time period of the data write when the time period of described database journal is for writing database in database.Still for described data for call detailed list, suppose that the time period of a certain bar database journal is on February 1,1 day to 2014 January in 2014, then this database journal shows to have stored the call detailed list that time period information is on February 1st, 1 day 1 January in 2014 in database.
In actual applications, the database journal of a client may have many, the time period of the pieces of data storehouse daily record of this client can be carried out gathering and judged whether the time period of described time period and described data exists common factor afterwards by service end, for the time period of pieces of data storehouse daily record, service end also can judge whether the time period of described time period and described data exists common factor respectively, then gather judged result, the present invention does not make particular restriction to this.
Comparatively simple, be judged as example again after being gathered the time period of pieces of data storehouse daily record with service end, described judged result can comprise following three kinds of situations:
Situation one: the time period of described database journal and the time period of described data do not occur simultaneously, then can confirm not store described data in database.Still suppose, the time period of described data is on April 1,1 day to 2014 March in 2014, if the time period of described data logging is on February 1,1 day to 2014 January in 2014, then the time period of described database journal and the time period of described data do not occur simultaneously, confirm not store described data in database, perform step 103.
Situation two: the time period of described database journal comprises the time period of described data, then can confirm to store described data in database.Still suppose, the time period of described data is on April 1,1 day to 2014 March in 2014, if the time period of described data logging is on May 1,1 day to 2014 January in 2014, then the time period of described database journal comprises the time period of described data, confirm to store described data in database, namely the data that user will write have been stored in database, service end can return result according to the processing mode in correlation technique to client, such as: service end can upload complete message etc. to client return data, the present invention does not make particular restriction to this.
Situation three: there are common factor the time period of described database journal and the time period of described data, and common factor is not the time period of described data, then can confirm to store the described data of part in database.Still suppose, the time period of described data is on April 1,1 day to 2014 March in 2014, if the time period of described data logging is on March 15,1 day to 2014 January in 2014, then there are common factor the time period of described database journal and the time period of described data, common factor is: on March 15,1 day to 2014 March in 2014, this common factor is not the time period of described data, can confirm the call detailed list storing this client on March 15th, 1 day 1 March in 2014 in database.For the call detailed list that client sends, the call detailed list on April 1st, 16 days 1 March in 2014 is still had to need to be written in database.So, there is common factor in the time period of described database journal and the time period of described data, and when common factor is not the time period of described data, perform step 103.
Described data are preserved in the buffer by step 103.
In the present embodiment, the described data that client sends by service end are kept in the buffer memory of the machine, such as: MQ buffer memory.Particularly, service end first can carry out duplicate removal process to described data, then the described data after duplicate removal is preserved in the buffer.
Step 104, returns to client and uploads successful message.
Based on abovementioned steps 103, service end, after preserving in the buffer by described data, returns to client and uploads successful message.Particularly, the quantity of the subdata that the described packet after service end can add up duplicate removal contains, uploads in successful message described in then this quantity being carried at.Described message, after uploading successful message described in receiving, is presented to user by client, such as: client can show the message box of " 452 record is uploaded successfully " to user.
In the present embodiment, service end is after preserving in the buffer by described data, will return to client and upload successful message, just return to client after writing data in database relative to service end in correlation technique and upload successful message, for user, greatly improve the speed of write data, and then improve Consumer's Experience.
Step 105, will preserve described data write into Databasce in the buffer.
In the present embodiment, service end will preservation described data write into Databasce in the buffer.Such as: for described data, whether service end can inquire about the subdata comprised in described data successively and store in a database, if described subdata does not store in a database, then by described subdata write into Databasce, if described subdata has stored in a database, then proceed inquiry.Service end by after in described data write into Databasce, can also delete the described data of preserving in the buffer further.Those skilled in the art can according to the data writing mode provided in correlation technique to carry out the write of described data, and this is no longer going to repeat them in the present invention.
Described as can be seen from above, service end of the present invention is when receiving the data that client sends, can according to the attribute information Query Database daily record of data, to judge whether stored described data in database, and when not storing described data in a database, described data are preserved in the buffer, then returns to client and upload successful message, and then promote the speed that user writes data, promote the operating experience of user simultaneously.
In an alternative embodiment of the invention, based on above-mentioned method for writing data, the present invention also provides the method for Data Statistics Inquiry Through, particularly, please refer to Fig. 2, said method comprising the steps of:
Step 201, receives the Data Statistics Inquiry Through instruction that client sends.
In the present embodiment, user by client by after in data write into Databasce, user can also by the statistics of data described in described client query.Still for the call detailed list that described data are client, user can input the name of the client that will inquire about in the client, and user can be sent to service end for the call detailed list statistical query instruction of this client by client.
Step 202, according to described Data Statistics Inquiry Through instruction, from the middle table that database is preset, obtain Query Result, described Query Result is generated by statistics of database after by described data write into Databasce.
Based on abovementioned steps 201, service end, after receiving described Data Statistics Inquiry Through instruction, obtains Query Result in the middle table preset from database.Particularly, database can after service end be by described data write, the described data of write and the data before this with regard to storing are added up, and statistics is stored in described default middle table, so that service end is after receiving described Data Statistics Inquiry Through instruction, the result of statistics directly can be inquired.
Step 203, returns described Query Result to client.
For example, suppose for certain client, service end stores the call detailed list in this client on February 1st, 1 day 1 January in 2014, user uploads again the call detailed list in this client on April 1st, 2 days 1 February in 2014 by client, database can after the call detailed list on April 1st, 1 day 1 March in 2014 be written to database by service end, to this client on February 1,1 day to 2014 January in 2014, and the call detailed list on April 1st, 2 days 1 February in 2014 is added up, namely database is added up in the call detailed list on April 1st, 1 day 1 January in 2014 this client, and statistics is stored in described default middle table.Service end receive client send for the Data Statistics Inquiry Through instruction of this client after, directly can get Query Result from described middle table, then this Query Result be returned to client, greatly improve the speed of Data Statistics Inquiry Through.
Corresponding with the embodiment of method for writing data of the present invention, the application also provides a kind of data transfer apparatus.Device described in the application can pass through software simulating, also can be realized by the mode of hardware or software and hardware combining.For software simulating, the application's data transfer apparatus, as the device on a logical meaning, is by the processor of its place equipment, computer program instructions corresponding in nonvolatile memory is read operation in internal memory to be formed.
Please refer to Fig. 3 and Fig. 4, the application provides a kind of data transfer apparatus 300, described device 300 can be applied in service end, includes: data receipt unit 301, store judging unit 302, data saving unit 303, successfully return unit 304, data write unit 305, inquire-receive unit 306, result acquiring unit 307 and result and return unit 308.
Wherein, described data receipt unit 301, for receiving the data that client sends;
Described storage judging unit 302, for the attribute information Query Database daily record according to described data, to judge whether stored described data in database;
Described data, during for not storing described data in a database, are preserved in the buffer by described data saving unit 303;
Describedly successfully returning unit 304, uploading successful message for returning to client.
Described data write unit 305, for after returning to client and uploading successful message, will preserve described data write into Databasce in the buffer.
Further, the attribute information of described data is the time period information of described data;
Described storage judging unit 302, specifically when the time period of described database journal and the time period of described data do not occur simultaneously, confirms not store described data in database;
When the time period of described database journal comprises the time period of described data, confirm to store described data in database.
Further, described data saving unit 303, is further used for there is common factor in the time period of described database journal and the time period of described data, and when common factor is not the section time period of described data, described data is preserved in the buffer.
Described inquire-receive unit 306, for receiving the Data Statistics Inquiry Through instruction that client sends;
Described result acquiring unit 307, for according to described Data Statistics Inquiry Through instruction, from the middle table that database is preset, obtain Query Result, described Query Result is generated by statistics of database after by described data write into Databasce;
Described result returns unit 308, for described Query Result is returned client.
In said apparatus, the implementation procedure of the function and efficacy of unit specifically refers to the implementation procedure of corresponding step in said method, does not repeat them here.
The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, within the spirit and principles in the present invention all, any amendment made, equivalent replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (10)
1. a method for writing data, is characterized in that, described method comprises:
Receive the data that client sends;
According to the attribute information Query Database daily record of described data, to judge whether stored described data in database;
If do not store described data in database, then described data are preserved in the buffer;
Return to client and upload successful message.
2. method according to claim 1, is characterized in that, after returning to client and uploading successful message, also comprises:
Described data write into Databasce in the buffer will be preserved.
3. method according to claim 1, is characterized in that,
The attribute information of described data is the time period information of described data;
The described attribute information Query Database daily record according to described data, to judge whether stored described data in database, comprising:
If the time period of the time period of described database journal and described data does not occur simultaneously, then confirm not store described data in database;
If the time period of described database journal comprises the time period of described data, then confirm to store described data in database.
4. method according to claim 3, is characterized in that, described method also comprises:
If there is common factor the time period of the time period of described database journal and described data, and common factor is not the time period of described data, then described data preserved in the buffer.
5. method according to claim 2, is characterized in that, described method also comprises:
Receive the Data Statistics Inquiry Through instruction that client sends;
According to described Data Statistics Inquiry Through instruction, from the middle table that database is preset, obtain Query Result, described Query Result is generated by statistics of database after by described data write into Databasce;
Described Query Result is returned client.
6. a data transfer apparatus, is characterized in that, described device comprises:
Data receipt unit, for receiving the data that client sends;
Store judging unit, for the attribute information Query Database daily record according to described data, to judge whether stored described data in database;
Described data, during for not storing described data in a database, are preserved in the buffer by data saving unit;
Successfully returning unit, uploading successful message for returning to client.
7. device according to claim 6, is characterized in that, described device also comprises:
Data write unit, for after returning to client and uploading successful message, will preserve described data write into Databasce in the buffer.
8. device according to claim 6, is characterized in that,
The attribute information of described data is the time period information of described data;
Described storage judging unit, specifically when the time period of described database journal and the time period of described data do not occur simultaneously, confirms not store described data in database;
When the time period of described database journal comprises the time period of described data, confirm to store described data in database.
9. device according to claim 8, is characterized in that,
Described data saving unit, is further used for there is common factor in the time period of described database journal and the time period of described data, and when common factor is not the section time period of described data, described data is preserved in the buffer.
10. device according to claim 7, is characterized in that, described device also comprises:
Inquire-receive unit, for receiving the Data Statistics Inquiry Through instruction that client sends;
Result acquiring unit, for according to described Data Statistics Inquiry Through instruction, from the middle table that database is preset, obtain Query Result, described Query Result is generated by statistics of database after by described data write into Databasce;
Result returns unit, for described Query Result is returned client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510026045.0A CN104537110B (en) | 2015-01-19 | 2015-01-19 | A kind of method for writing data and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510026045.0A CN104537110B (en) | 2015-01-19 | 2015-01-19 | A kind of method for writing data and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104537110A true CN104537110A (en) | 2015-04-22 |
| CN104537110B CN104537110B (en) | 2018-01-12 |
Family
ID=52852638
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510026045.0A Active CN104537110B (en) | 2015-01-19 | 2015-01-19 | A kind of method for writing data and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104537110B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112367408A (en) * | 2021-01-13 | 2021-02-12 | 树根互联技术有限公司 | Management system and method for multi-tenant data of Internet of things |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7487162B2 (en) * | 2003-04-11 | 2009-02-03 | Hitachi, Ltd. | Method and data processing system with data replication |
| CN101561950A (en) * | 2009-05-21 | 2009-10-21 | 北京握奇数据系统有限公司 | Method and device for processing data of intelligent card |
| CN103455575A (en) * | 2013-08-22 | 2013-12-18 | 北京炎黄盈动科技发展有限责任公司 | Method and device for statistic analysis of data |
| CN103927338A (en) * | 2014-03-26 | 2014-07-16 | 网神信息技术（北京）股份有限公司 | Log information storage processing method and log information storage processing device |
| CN103959259A (en) * | 2012-11-20 | 2014-07-30 | 华为技术有限公司 | Data storage method, data storage device and data storage system |
-
2015
- 2015-01-19 CN CN201510026045.0A patent/CN104537110B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7487162B2 (en) * | 2003-04-11 | 2009-02-03 | Hitachi, Ltd. | Method and data processing system with data replication |
| CN101561950A (en) * | 2009-05-21 | 2009-10-21 | 北京握奇数据系统有限公司 | Method and device for processing data of intelligent card |
| CN103959259A (en) * | 2012-11-20 | 2014-07-30 | 华为技术有限公司 | Data storage method, data storage device and data storage system |
| CN103455575A (en) * | 2013-08-22 | 2013-12-18 | 北京炎黄盈动科技发展有限责任公司 | Method and device for statistic analysis of data |
| CN103927338A (en) * | 2014-03-26 | 2014-07-16 | 网神信息技术（北京）股份有限公司 | Log information storage processing method and log information storage processing device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112367408A (en) * | 2021-01-13 | 2021-02-12 | 树根互联技术有限公司 | Management system and method for multi-tenant data of Internet of things |
| CN112367408B (en) * | 2021-01-13 | 2021-08-03 | 树根互联技术有限公司 | Management system and method for multi-tenant data of Internet of things |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104537110B (en) | 2018-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104901997B (en) | System and method for the direct storage access in content center network | |
| CN103248684B (en) | Resource acquiring method and device in a kind of the Internet | |
| US9507821B2 (en) | Mail indexing and searching using hierarchical caches | |
| CN100534071C (en) | System and method for using packed compressed buffers for improved client server communication | |
| US9471610B1 (en) | Scale-out of data that supports roll back | |
| CN111414389B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN106326499B (en) | A kind of data processing method and device | |
| CN104123238A (en) | Data storage method and device | |
| CN104239353B (en) | WEB classification control and log audit method | |
| CN105653198A (en) | Data processing method and device | |
| CN105824902A (en) | Data caching method and device | |
| CN105407013A (en) | User online state statistical system and method | |
| CN101103331A (en) | Implementing application specific management policies on a content addressed storage device | |
| CN106446075A (en) | Page request processing method and apparatus | |
| CN103744975A (en) | Efficient caching server based on distributed files | |
| US20160323136A1 (en) | Capture of web application state | |
| CN104537110A (en) | Data writing method and device | |
| CN107948234A (en) | The processing method and processing device of data | |
| CN106559404A (en) | A kind of client for accessing data, proxy server and system | |
| CN104378396A (en) | Data management device and method | |
| CN104572945A (en) | File search method and device based on cloud storage space | |
| CN114218471A (en) | Data query method, device, system, electronic equipment and storage medium | |
| CN104580276A (en) | Information pushing method, device and system, as well as information access device | |
| US8082334B1 (en) | Providing direct access to managed content | |
| CN105912477A (en) | Directory reading method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |