CN110990359A - Method and system for cleaning useless data in synchronous framework - Google Patents
Method and system for cleaning useless data in synchronous framework Download PDFInfo
- Publication number
- CN110990359A CN110990359A CN201911312541.7A CN201911312541A CN110990359A CN 110990359 A CN110990359 A CN 110990359A CN 201911312541 A CN201911312541 A CN 201911312541A CN 110990359 A CN110990359 A CN 110990359A
- Authority
- CN
- China
- Prior art keywords
- data
- uploaded
- client
- file server
- synchronous
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- 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/174—Redundancy elimination performed by the file system
- G06F16/1748—De-duplication implemented within the file system, e.g. based on file segments
-
- 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/178—Techniques for file synchronisation in file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method and a system for data management in a synchronous framework, wherein the method comprises the following steps: the client stores the data to be uploaded containing the non-text data created by the user and generates a storage address; the client sends the non-text data to a file server; the file server receives the non-text data sent by the client and generates recording information of the non-text data; the recording information includes an identification characteristic of the non-text data; the file server returns the identification characteristics to the client; the client receives the identification characteristics returned by the file server, and updates the storage address of the data to be uploaded according to the identification characteristics; and the client uploads the data to be uploaded to the synchronous server according to the updated storage address. The method and the device can quickly position the files to be deleted, improve the searching efficiency, simultaneously accurately clear the files to be deleted, and save the storage space and the cost.
Description
Technical Field
The invention relates to the technical field of data synchronization, in particular to a method and a system for cleaning useless data in a synchronization framework.
Background
In the mobile phone application app, a lot of places are used for synchronization. The synchronization function functions to: after a user uses an application app to change data on a certain mobile phone device, if the data are added, deleted and modified, the changes can be uploaded (uploading refers to transmitting the data from the device to a server) to a synchronization server through a synchronization function; when the user uses the app by other devices, the latest data on the synchronization server can be pulled down (the data of the synchronization server is downloaded to the devices) through the synchronization function, so that the data on different devices are unified.
For example, a user opens a notepad app on a mobile phone a, writes an article, and uploads the article to the server through synchronization. When he changes to another mobile phone B, which has not been recorded before, the user can apply the app via the note book on the mobile phone B, and the note is downloaded from the server to the mobile phone. Thus, both handsets a and B have this in-time record. This avoids the loss of the handset due to loss or erasure of data. That is, any mobile phone with the app installed can pull down the data stored on the server in the case of networking.
Synchronization works in units of each piece of data in the database. For example, schedule data is synchronized, each piece of data corresponds to one schedule in the database, and the schedule includes the content, time, reminding mode and the like of the schedule; synchronizing the telephone directory, wherein each piece of data corresponds to a telephone number record in the database, and each piece of data comprises a telephone number, a contact name, an address and the like; the synchronous notepad is characterized in that each piece of data corresponds to one notepad record in the database, and the piece of data can comprise written characters, inserted pictures, voice, video files and the like in the notepad. Therefore, the user synchronizes each piece of data, and all elements in the notepad, including characters, pictures, voice, video files and the like, need to be synchronized to the server.
Although many types may be included in the data. But can be generalized to both textual and non-textual types. Taking the note book as an example, the text part in the note book is the first text type, and other pictures, voice, video and the like are all the second non-text types. Non-text types are typically in the form of files.
The text type synchronization is simple, and the corresponding character string of the text data is uploaded to a database DBNote of the synchronization server ServerM. But the non-text type synchronization needs to firstly convert the non-text data into a file stream to be transmitted to a server ServerF, the non-text data does not exist in the synchronization of the synchronization server, only a url network address corresponding to the non-text data exists, the address is inserted into a synchronous data record, and the address is uploaded to a database DBNote of the synchronization server ServerM to be displayed as a part of one data.
For example, a mobile phone application client converts a picture file into a stream, uploads the stream to a file server, generates a url address, and returns the url address to the client. The client stores the url address in the notepad data that needs to use this picture to the location where it is located.
Note: url (Uniform Resource Locator), which is a Uniform Resource Locator of WWW, refers to a network address. By entering this address, the corresponding resource, such as a photograph, can be accessed.
For example, there is a piece of event data, and before synchronization, this record in the database of the mobile phone client is represented as:
<text1><imgadd1><text2><imgadd2><text3><imgadd3><text4>
wherein, imgadd1, imgadd2 and imgadd3 respectively represent the local addresses of pictures img1, img2 and img3 in the storage unit (such as sd card) of the mobile phone.
After the file is uploaded successfully, the synchronous data form is as follows:
<text1><url1><text2><url2><text3><url3><text4>
after the synchronization is successful, the data on the server ServerM is synchronized, and when the user changes a mobile phone, the newly synchronized data is the event data, and the client downloads and stores the pictures corresponding to url1, url2 and url3 in the data, and displays the pictures at the correct positions. That is, what is stored in the data is the url address of the picture.
In the prior art, data synchronization can be completed, and one problem can be that of clearing useless data.
For example, there is a piece of memo data, which has 3 pictures img1, img2 and img3, and correspondingly, there are three corresponding url addresses, url1, url2 and url3 on the file server. This note data is the same:
<text1><url1><text2><url2><text3><url3><text4>…
text1 represents a story and is a character string.
When the user deletes the p2 picture, the piece of memo data becomes:
<text1><url1><text2><text3><url3><text4>
after uploading the data again, the server records the state of the data.
However, the useless picture file imgp2 still exists in the file server.
These files, pictures, videos, and audios are generally large, and after a long time, the file server has a lot of useless data, and occupies valuable disk space, and the hardware cost is also increased. In addition, when searching for a file, the useless files participate in the search, so that the efficiency of the search is also reduced.
Disclosure of Invention
To address at least one of the above issues, the present disclosure provides a method and system for garbage cleaning in a synchronous framework.
In a first aspect, the present application provides a method for cleaning useless data in a synchronization framework, including:
receiving upload data sent by a client;
storing the uploaded data and generating record information of the uploaded data; the record information comprises identification characteristics of the uploaded data;
and returning the identification characteristics to the client.
Preferably, the record information further includes a network address and a data state of the uploaded data, and the data state includes a normal state and a to-be-deleted state.
Preferably, the method further comprises:
receiving identification characteristics corresponding to deleted data sent by a client;
and modifying the data state corresponding to the identification characteristic into a state to be deleted.
In a second aspect, the present application provides a method for data management in a synchronous framework, the method comprising:
storing data to be uploaded containing non-text data created by a user and generating a storage address;
sending non-text data in the data to be uploaded to a file server;
receiving identification characteristics of the non-text data returned by the file server;
updating the storage address of the data to be uploaded according to the identification characteristics;
and uploading the data to be uploaded to a synchronous server according to the updated storage address.
Preferably, when the user modifies the data to be uploaded, whether the data to be uploaded has non-text data deleted is judged, and if not, the modified data to be uploaded is sent to the synchronous server; and if so, sending the identification characteristics corresponding to the deleted data to the file server.
In a third aspect, the present application provides a method for data management in a synchronization framework, where the method includes:
the client stores the data to be uploaded containing the non-text data created by the user and generates a storage address;
the client sends the non-text data in the data to be uploaded to a file server;
the file server receives non-text data in the data to be uploaded sent by a client, stores the non-text data in the data to be uploaded and generates record information of the non-text data in the data to be uploaded; the record information comprises identification characteristics of non-text data in the data to be uploaded;
the file server returns the identification characteristics to the client;
the client receives the identification characteristics returned by the file server, and updates the storage address of the data to be uploaded according to the identification characteristics;
and the client uploads the data to be uploaded to the synchronous server according to the updated storage address.
Preferably, the method further comprises:
when the user modifies the data to be uploaded, the client judges whether the data to be uploaded has non-text data deleted, if not, the modified data to be uploaded is sent to the synchronous server; if so, sending the identification characteristics corresponding to the deleted data to a file server;
and the file server modifies the data state corresponding to the identification characteristic into a to-be-deleted state.
Preferably, the method further comprises:
and when the preset conditions are met, deleting the non-text data with the data state to be deleted by the file server.
In a fourth aspect, the present application provides a system for data management in a synchronization framework, where the system includes a client, a synchronization server, and a file server, which are capable of implementing the method of any one of the first, second, and third aspects.
In a fifth aspect, the present application provides a readable medium comprising executable instructions, which when executed by a processor of an electronic device, cause the electronic device to perform a method for data management in a synchronization framework as claimed in any one of claims 1 to 8.
In a sixth aspect, the present application provides an electronic device comprising a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the method of any one of the first, second and third aspects.
Compared with the prior art, the invention has at least the following beneficial effects:
the synchronization server and the file server are decoupled, the logic is reasonable, the data can be effectively synchronized, the files to be deleted can be quickly positioned, the searching efficiency is improved, the files to be deleted can be accurately and clearly found, and the storage space and the cost are saved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart illustrating a method for cleaning useless data in a synchronization framework according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer and more complete, the technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention, and based on the embodiments of the present invention, all other embodiments obtained by a person of ordinary skill in the art without creative efforts belong to the scope of the present invention.
As shown in fig. 1, an embodiment of the present invention provides a method for data management in a synchronous framework, where the method may include the following steps:
step 1, a client creates a note which comprises word text data and non-text data such as pictures, and before synchronization, the local address (address on a memory card on a mobile phone) of the picture is represented in the record. For example: imgadd1 denotes the local address of img1, imgadd2 denotes the local address of img2, imgadd3 denotes the local address of img3,
<text1><imgadd1><text2><imgadd2><text3><imgadd3><text4>
step 2: the client sends a request to the file server to store non-textual data such as imgadd1, imgadd2, imgadd3, etc.
And step 3: the file server stores non-text data, inserts a record in the file database of the file server, and each record needs to include an identification feature, a network address and a data state, which can be respectively expressed by a fileID, url and status. The fileID is a unique mark of each non-text data on the file server, url is a network address capable of accessing the non-text data, status is expressed in terms of data state, and can be assigned with different data states, for example, status-0 indicates that the data is in a normal state, and status-1 indicates that the data is in a to-be-deleted state.
And 4, step 4: and after the file server finishes file storage, returning the identification characteristic fileID of the non-text data to the client.
And 5: the client updates the piece of recording data to < text1> < fileID1> < text2> < fileID2> < text3> < fileID 3> < text4>, wherein the fileID1 represents the network address of img1, the fileID2 represents the network address of img2, and the fileID3 represents the network address of img 3.
The url is replaced by the fileID in the application, the file server uses the unique fileID for positioning, the files needing to be deleted can be found out rapidly, the storage space and the cost are saved, and the efficiency is improved.
Step 6: the client uploads the note data to the synchronization server.
And 7: the synchronization server stores the note data in a database of the synchronization server.
The synchronous server is only responsible for synchronous logic, is decoupled from the function of the file server, is reasonable in function division, and works in a mutually matched mode, so that quick positioning and high-speed synchronization are realized.
And 8: and after the synchronization is finished, the data is fed back to the client, and the client updates the state of the data to be synchronized.
Here, the note newly created by the user is uploaded, and the user can download the note in different devices.
And step 9: the user modifies some content in an uploaded note through the client.
Step 10: the client judges whether the picture is deleted, if so, the identification characteristic file ID of the deleted picture is transmitted to the file server, and step 11 is executed, and if not, step 12 is executed.
In this application, it is described that only pictures are included in the event record, so that only whether pictures are deleted is determined in this step. The actual situation is not only pictures, but also all operations related to non-text data are judged. And whether pictures are added or not is judged, and then the newly added non-file data is uploaded to the file server.
Step 11: the file server sets the data state status corresponding to the identification feature fileID of the deleted picture to 1.
In this application, a status of 0 means that the data is in a normal state, a status of 1 means that the data is in a to-be-deleted state, and a status of a deleted picture is 1.
Step 12: and uploading the modified note data to a synchronization server through a synchronization service.
If only the picture img2 is deleted without other modification in the application, the modified event data is < text1> < fileID1> < text2> < text3> < fileID 3> < text4 >.
Step 13: and the synchronous server synchronizes to a database of the synchronous server according to the data uploaded by the client.
And 14, performing data cleaning when needed, and deleting the data with status of 1.
Considering that the user needs to respond quickly when operating on the client, the client can only modify the status value of the corresponding data on the file server after deleting the non-text data, and the data cannot be deleted immediately. The data can be deleted by running the script at a preset time without affecting the online user. But the data in the file server can also be deleted immediately.
Step 15: the process is finished and the subsequent operation of the user is waited.
The method modifies a synchronous framework, introduces the concept of fileID, and newly establishes a database table for marking the file state in the file server ServerF, thereby achieving the purpose of quickly cleaning data. The introduced fileID is a unique ID on the file server, each fileID uniquely corresponds to a file, and is also a unique value which is unique and unreproducible in the DBfile.
As shown in fig. 1, an embodiment of the present invention further provides a system for data management in a synchronization framework, where the system includes a client, a synchronization server, and a file server, which are capable of implementing a data management method in any synchronization framework provided in the present application.
The contents of information interaction, execution process and the like among the client, the synchronization server and the file server in the system are based on the same conception as that of the embodiment of the method of the invention, and specific contents can be referred to the description in the embodiment of the method of the invention, and are not described herein again.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a" does not exclude the presence of other similar elements in a process, method, article, or apparatus that comprises the element.
Those of ordinary skill in the art will understand that: all or part of the steps for realizing the method embodiments can be completed by hardware related to program instructions, the program can be stored in a computer readable storage medium, and the program executes the steps comprising the method embodiments when executed; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it is to be noted that: the above description is only a preferred embodiment of the present invention, and is only used to illustrate the technical solutions of the present invention, and not to limit the protection scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (10)
1. A method for data management in a synchronous framework, the method comprising:
receiving upload data sent by a client;
storing the uploaded data and generating record information of the uploaded data; the record information comprises identification characteristics of the uploaded data;
and returning the identification characteristics to the client.
2. The method for data management in a synchronous framework according to claim 1, wherein the log information further comprises a network address and a data status of the uploaded data, and the data status comprises a normal status and a status to be deleted.
3. A method for data management in a synchronous framework as claimed in claim 2, characterized in that the method further comprises:
receiving identification characteristics corresponding to deleted data sent by a client;
and modifying the data state corresponding to the identification characteristic into a state to be deleted.
4. A method for data management in a synchronous framework, the method comprising:
storing data to be uploaded containing non-text data created by a user and generating a storage address;
sending non-text data in the data to be uploaded to a file server;
receiving identification characteristics of the non-text data returned by the file server;
updating the storage address of the data to be uploaded according to the identification characteristics;
and uploading the data to be uploaded to a synchronous server according to the updated storage address.
5. A method for data management in a synchronous framework as claimed in claim 4,
when the user modifies the data to be uploaded, judging whether the data to be uploaded has non-text data deletion, if not, sending the modified data to be uploaded to a synchronous server; and if so, sending the identification characteristics corresponding to the deleted data to the file server.
6. A method for data management in a synchronous framework, the method comprising:
the client stores the data to be uploaded containing the non-text data created by the user and generates a storage address;
the client sends the non-text data in the data to be uploaded to a file server;
the file server receives non-text data in the data to be uploaded sent by a client, stores the non-text data in the data to be uploaded and generates record information of the non-text data in the data to be uploaded; the record information comprises identification characteristics of non-text data in the data to be uploaded;
the file server returns the identification characteristics to the client;
the client receives the identification characteristics returned by the file server, and updates the storage address of the data to be uploaded according to the identification characteristics;
and the client uploads the data to be uploaded to the synchronous server according to the updated storage address.
7. The method for data management in a synchronous framework as recited in claim 6, the method further comprising:
when the user modifies the data to be uploaded, the client judges whether the data to be uploaded has non-text data deleted, if not, the modified data to be uploaded is sent to the synchronous server; if so, sending the identification characteristics corresponding to the deleted data to a file server;
and the file server modifies the data state corresponding to the identification characteristic into a to-be-deleted state.
8. The method for data management in a synchronous framework as recited in claim 7, the method further comprising:
and when the preset conditions are met, deleting the non-text data with the data state to be deleted by the file server.
9. A system for data management in a synchronization framework, characterized in that the system comprises a client, a synchronization server and a file server which are able to implement the method for data management in a synchronization framework according to any of claims 1-8.
10. A readable medium, characterized in that it comprises executable instructions, which when executed by a processor of an electronic device, perform a method for data management in a synchronization framework as claimed in any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911312541.7A CN110990359A (en) | 2019-12-18 | 2019-12-18 | Method and system for cleaning useless data in synchronous framework |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911312541.7A CN110990359A (en) | 2019-12-18 | 2019-12-18 | Method and system for cleaning useless data in synchronous framework |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110990359A true CN110990359A (en) | 2020-04-10 |
Family
ID=70095695
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911312541.7A Pending CN110990359A (en) | 2019-12-18 | 2019-12-18 | Method and system for cleaning useless data in synchronous framework |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110990359A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112788152A (en) * | 2021-01-28 | 2021-05-11 | 重庆周游科技有限公司 | Picture uploading method capable of saving hard disk space |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1988535A (en) * | 2005-12-23 | 2007-06-27 | 腾讯科技（深圳）有限公司 | Synchronous method, system for file storage and customer terminal |
| CN101075864A (en) * | 2007-07-16 | 2007-11-21 | 腾讯科技（深圳）有限公司 | Method for synchronizing and processing data, customer terminal equipment and servo |
| CN101888395A (en) * | 2009-05-13 | 2010-11-17 | 华为技术有限公司 | Method for synchronizing data, widget terminal and server |
| JP2012221317A (en) * | 2011-04-11 | 2012-11-12 | Kii corp | Data synchronization device, data synchronization system, data synchronization method and program |
| CN103457973A (en) * | 2012-06-01 | 2013-12-18 | 深圳市腾讯计算机系统有限公司 | Image uploading method and system, image uploading client terminal and network server |
| CN104778214A (en) * | 2015-03-20 | 2015-07-15 | 四川长虹电器股份有限公司 | Distributed file system on basis of jump of resource locator and data synchronization method thereof |
-
2019
- 2019-12-18 CN CN201911312541.7A patent/CN110990359A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1988535A (en) * | 2005-12-23 | 2007-06-27 | 腾讯科技（深圳）有限公司 | Synchronous method, system for file storage and customer terminal |
| CN101075864A (en) * | 2007-07-16 | 2007-11-21 | 腾讯科技（深圳）有限公司 | Method for synchronizing and processing data, customer terminal equipment and servo |
| CN101888395A (en) * | 2009-05-13 | 2010-11-17 | 华为技术有限公司 | Method for synchronizing data, widget terminal and server |
| JP2012221317A (en) * | 2011-04-11 | 2012-11-12 | Kii corp | Data synchronization device, data synchronization system, data synchronization method and program |
| CN103457973A (en) * | 2012-06-01 | 2013-12-18 | 深圳市腾讯计算机系统有限公司 | Image uploading method and system, image uploading client terminal and network server |
| CN104778214A (en) * | 2015-03-20 | 2015-07-15 | 四川长虹电器股份有限公司 | Distributed file system on basis of jump of resource locator and data synchronization method thereof |
Non-Patent Citations (1)
| Title |
|---|
| 贾兆拢: ""基于SyncML协议的云数据安全同步技术研究"" * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112788152A (en) * | 2021-01-28 | 2021-05-11 | 重庆周游科技有限公司 | Picture uploading method capable of saving hard disk space |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11074396B2 (en) | Animating edits to documents | |
| US9864736B2 (en) | Information processing apparatus, control method, and recording medium | |
| KR101026604B1 (en) | Method and system for hosted mobile management service architecture | |
| US8176061B2 (en) | Tracking digital assets on a distributed network | |
| US8620861B1 (en) | Preserving file metadata during atomic save operations | |
| US7680067B2 (en) | Peer-to-peer data synchronization architecture | |
| CN1799051B (en) | Method for browsing contents using page storing file | |
| EP2378437A1 (en) | Data synchronization methods in communication systems | |
| CN105608134A (en) | Multithreading-based web crawler system and web crawling method thereof | |
| CN105991398A (en) | Instant message IM chatting records storage method and apparatus | |
| JP2016539401A (en) | Hierarchical data archiving | |
| US9934240B2 (en) | On demand access to client cached files | |
| US20130046935A1 (en) | Shared copy cache across networked devices | |
| JP4719732B2 (en) | Backup server, mobile device, communication system using these, and backup method | |
| US9703848B2 (en) | Caching linked queries for optimized compliance management | |
| CN111324483B (en) | Data recovery method and device and related equipment | |
| CN110990359A (en) | Method and system for cleaning useless data in synchronous framework | |
| CN111596933B (en) | File processing method, device, electronic equipment and computer readable storage medium | |
| JP5186880B2 (en) | File management system, file management method, and file management program | |
| US11023418B2 (en) | Keyword-based data management system and method | |
| US20080059538A1 (en) | Method and system for synchronizing offline records | |
| KR101471522B1 (en) | System for providing personal information based on generation and consumption of content | |
| CN109086304A (en) | A kind of update method of c bookmart, device and storage medium | |
| JP5063877B2 (en) | Information processing apparatus and computer program | |
| CN106874486A (en) | Method and mobile terminal that a kind of Folder Name shows |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200410 |
|
| RJ01 | Rejection of invention patent application after publication |