CN103475721A - System for updating digital assets and method thereof - Google Patents
System for updating digital assets and method thereof Download PDFInfo
- Publication number
- CN103475721A CN103475721A CN2013104166711A CN201310416671A CN103475721A CN 103475721 A CN103475721 A CN 103475721A CN 2013104166711 A CN2013104166711 A CN 2013104166711A CN 201310416671 A CN201310416671 A CN 201310416671A CN 103475721 A CN103475721 A CN 103475721A
- Authority
- CN
- China
- Prior art keywords
- resource
- service end
- client
- list
- digital asset
- 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
Images
Abstract
The invention relates to the technical field of computers, in particular to a system for updating digital assets and a method of the system. The system comprises client sides, a server side, a time server and a database. The client sides can be multiple, each client side has a unique identifier which maintains an index list which belongs to the client side itself, and changed data indexes from the last updating operation until now and final updating time provided by the time server are recorded in the list. The server side provides the database of digital resources. The index lists of the system are stored in the database. The time server provides the accurate and reliable final updating time. The final updating time of all the client sides is jointly provided by the time server, and then the data exception problem caused by time errors is solved. The system and the method can reliably and effectively maintain consistency of multi-terminal data and can be used for maintaining the multi-terminal data.
Description
Technical field
The present invention relates to field of computer technology, especially a kind of renewal system and method thereof of digital asset.
Background technology
In the middle of current renewal technology, much all be based on the online real time datas of carrying out under the scene of single client and upgrade, cause aspect space and network restriction ratio more.But nowadays the type of terminal is no longer single PC end, the mobile terminals such as mobile phone, panel computer are constantly weeded out the old and bring forth the new and are occupied the huge market share.A user need to go to use application software in different terminals, different places, different time, thus the problem that also causes user's data to be difficult to be consistent on a plurality of terminals.Obviously, along with the increase of data itself and the many equipment of user, current renewal technology can not adapt to user's demand.Therefore now increasing software is all realized new renewal technology for the characteristics of the many equipment of user.
Summary of the invention
One of technical problem that the present invention solves is to provide a kind of renewal system of digital asset; Solve in current many equipment, many places, different time situation the more inconsistent problem of new data.
Two of the technical problem that the present invention solves is to provide a kind of update method of digital asset; Can realize that the operation system on a plurality of clients is broken away to on-line environment carries out business operation, and in the situation that operation can be independently upgraded in the network permission, complete and online online same business function, and can safeguard the consistency of each terminal data, make original fixing business no longer be subject to spatial limitation.
The technical scheme that the present invention one of solves the problems of the technologies described above is:
Comprise client, service end, time server and database;
Described client can be for a plurality of, and each client has unique identifier, safeguard a one's own index list, the final updating time that in list, record was updated to the data directory changed so far and was provided by time server from last time;
Described server, provide the database of digital resource; Preserve systematic index list in database;
Described time server, provide accurate, a reliable final updating time; " the final updating time " of all clients is all provided by the time server unification, prevents the data exception problem caused due to time error.
Two the technical scheme that the present invention solves the problems of the technologies described above is:
Each client has a unique identifier, and safeguards a one's own index list, the final updating time that in list, record was updated to the data directory changed so far and was provided by time server from last time; Every data in the index list of service end database all identify these data by identifier and derive from which client;
During renewal, at first carry out Data Update, then upgrade index list; The consistency that keeps each client data and index list; The Data Update operation comprises uploading and downloading of metadata and resource, and each Data Update operation is relatively independent, supports concurrent execution;
In the index upgrade operation, the index list that service end is submitted to by contrast self index list and client, obtain the index upgrade result; The client that comprises these other sources of user in this result is update time operation information up to the present and new final updating time in the end;
Client is according to the response results in the index upgrade operation, and generated data upgrades the solicited message of each operation;
Client sends the Data Update request by multithreading after the left over by history operation is merged to solicited message, finally judge the response results of service end, successful upgrade the related data in the local index list, failed will add in the left over by history operation, be deferred to and upgrade operation next time and carry out.
Digital asset means to belong to the unit carrier of all notes contents of individual subscriber; Article one, digital assets are comprised of metadata and resource two parts; Digital asset and resource are many-one relationships, and many digital assets can be quoted with a resource.
Described index upgrade is:
Client is submitted " index upgrade " request to service end, request comprise a for service end upgrade the user local client carry out deletion action digital asset id list, for judging this resource, in service end, whether exist and the final updating time of resource id list, source, user's unique identifier and the local index list avoiding repeating submitting to;
The respective digital assets are deleted in the digital asset id list that service end is submitted to according to client, then upgrade source and the state of correlated digital assets in index list;
In the server side searches index list " the final updating time " of client up to the present this user at the operation information of the client in other sources, and add in response results;
Service end checks in database whether have identical resource according to resource id list, and will check that judged result adds in response results;
Service end joins the new final updating time in response results, and is sent back to client with the data mode of XML;
The response results of client analysis service end, merge corresponding Data Update operation and left over by history operation, generated data update request information; And " final updating time " that service end is sent is updated in index list.If do not receive response message, be considered as the index upgrade failure, finish whole renewal operation.
Described metadata is downloaded:
If it is digital asset newly-increased or that revise that state is arranged in the index upgrade result; to service end, submit " metadata download " request to; request comprises digital asset list, user's unique identifier of a digital asset id and state, otherwise does not need to submit to request;
Service end obtains " metadata download " request, by state, is that newly-increased digital asset metadata (not comprising resource) and state revised partly and added in response results for the digital asset of revising;
Service end sends it back client by response results with the data mode of XML;
Client obtains the metadata of digital asset and revises part according to response results, after the renewal local data, upgrades the local index list again; If do not obtain response or response abnormality, be considered as " metadata download " operation failure, and this operation is added in the left over by history operation.
Described metadata is uploaded and is:
Using the last final updating time to the current final updating time, during this period of time, local newly-increased digital asset, as solicited message, sends " metadata is uploaded " request to service end;
Service end receives " metadata is uploaded " request, and by the digital asset write into Databasce;
Upgrade the index list of service end;
Send a null response result to service end;
Client means that to the null response result " metadata is uploaded " operates successfully, otherwise is considered as operation failure, and this operation is added in the left over by history operation.
Described resource upload and download is:
Client uploads to needs the Resources list of service end or needs the resource id list of downloading as solicited message, to service end, sends " resource upload and download " request;
According to solicited message, judgement is that resource is uploaded or resource downloading to service end, if resource is uploaded, resource is written in database, then returns to a null response result; If resource downloading, according to resource id, related resource is searched in list, returns after lookup result is added to response results;
The response results of judgement service end, if normal response " resource upload and download " operate successfully, otherwise be considered as " resource upload and download " operation failure, and this operation joined during left over by history operates.
" the final updating time " of all terminals of the present invention is all provided by the time server unification, prevents the data exception problem caused due to time error.Each terminal safeguards that portion belongs to the index list of self, and in list, record was updated to the data directory changed so far from last time; By between individual index list, finally realizing the maintenance of data consistency to recently upgrading data.Each Data Update operation is all relatively independent, supports by concurrent efficient execution.On terminal, in the Data Update operation, any step is failed all can be incorporated into and upgrade in index list next time; Thereby guarantee the final consistency of data.By use of the present invention, can guarantee that each the renewal operates in temporal atomicity, prevents the data exception problem caused due to the time difference between multiple terminals; Can allow the user carry out and online online same business operation breaking away from online environment by Data Update; Can make user's meaning terminal in office obtain the business operation that this user has upgraded in other-end.The invention provides a set of system and method reliable, that effectively the multiple terminals data consistency is safeguarded.
The accompanying drawing explanation
Below in conjunction with accompanying drawing, the present invention is further described:
Fig. 1 is system block diagram of the present invention;
Fig. 2 is the inventive method family end flow chart;
Fig. 3 is that the inventive method is specifically implemented sequential chart.
Embodiment
As Figure 1-3, the present invention:
1. each client has a unique identifier (origin) and safeguards to one's name index list of portion; the final updating time that in list, record record was updated to the data directory changed so far and was provided by server from last time, and every data in the index list of service end all identify these data by origin and derive from which client;
2. first new data more, rear renewal index list.The consistency that keeps each client data and index list.
3. in the index upgrade operation, the index list that service end is submitted to by contrast self index list and client, obtain the index upgrade result.The client that comprises these other sources of user in this result in the end update time to operation information up to the present and new final updating time.
4. client is according to the response results in the index upgrade operation, and generated data upgrades the solicited message of each operation.
5. client sends the Data Update request by multithreading after the left over by history operation is merged to solicited message, finally judge the response results of service end, successful upgrade the related data in the local index list, failed will add in the left over by history operation, be deferred to and upgrade operation next time and carry out.
Digital asset of the present invention: the unit carrier that means to belong to all notes contents of individual subscriber.Article one, digital assets are comprised of metadata and resource two parts.In addition, digital asset and resource are many-one relationships, that is to say that many digital assets can quote with a resource.
Concrete implementation step:
1. index upgrade
1.1 client is submitted " index upgrade " request to service end, request comprises the final updating time of a digital asset id list (for service end, upgrading the deletion action that the user carries out at local client), resource id list (whether exist in service end for judging this resource, avoid repeating to submit to), source (origin), user's unique identifier (owner) and local index list.
1.2 the respective digital assets are deleted in the digital asset id list that service end is submitted to according to client, then upgrade source and the state of correlated digital assets in index list.
1.3 in the server side searches index list " the final updating time " of client up to the present this user at the operation information of the client in other sources, and add in response results.
1.4 service end checks in database whether have identical resource according to resource id list, and will check that judged result adds in response results.
1.5 service end joins the new final updating time in response results, and is sent back to client with the data mode of XML.
1.6 the response results of client analysis service end, merge corresponding Data Update operation and left over by history operation, generated data update request information.And " final updating time " that service end is sent is updated in index list.If do not receive response message, be considered as the index upgrade failure, finish whole renewal operation.
2. metadata is downloaded
2.1 if the digital asset that state is C (increasing newly) or U (modification) is arranged in the index upgrade result, to service end, submit " metadata download " request to, request comprises a digital asset list (digital asset id, state) and user's unique identifier (owner).Otherwise do not need to submit to request.
2.2 service end obtains " metadata download " request, the digital asset that the digital asset metadata that is C (increasing newly) by state (not comprising resource) and state are U (modification) is revised part and is added in response results.
2.3 service end sends it back client by response results with the data mode of XML.
2.4 client obtains the metadata of digital asset and revises part according to response results, after the renewal local data, upgrades the local index list again.If do not obtain response or response abnormality, be considered as " metadata download " operation failure, and this operation is added in the left over by history operation.
3. metadata is uploaded
3.1 during this period of time, local newly-increased digital asset, as solicited message, sends " metadata is uploaded " request to service end using the last final updating time to the current final updating time.
3.2 service end receives " metadata is uploaded " request, and by the digital asset write into Databasce.
3.3 upgrade the index list of service end.
3.4 send a null response result to service end.
3.5 client means that to the null response result " metadata is uploaded " operates successfully, otherwise is considered as operation failure, and this operation is added in the left over by history operation.
4. resource upload and download
4.1 client uploads to needs the Resources list of service end or needs the resource id list of downloading as solicited message, to service end, sends " resource upload and download " request.
4.2 service end is according to solicited message, judgement is that resource is uploaded or resource downloading, if resource is uploaded, resource is written in database, then returns to a null response result; If resource downloading, according to resource id, related resource is searched in list, returns after lookup result is added to response results.
4.3 the response results of judgement service end, if normal response " resource upload and download " operate successfully, otherwise be considered as " resource upload and download " operation failure, and this operation joined during left over by history operates
In addition,
1. need to comprise source (origin) in " index upgrade " and " metadata is uploaded " solicited message and come from which client for differentiating digital asset, because these two requests need service end to upgrade index list.
2. consider that digital asset and resource exist the size issue of many-to-one relation and resource can affect the response time, so the upload and download of resource is separated in the middle of the request of " resource upload and download ".
3. " metadata download ", " metadata is uploaded " and " resource upload and download " ask to send after all needing to merge the left over by history operation before operating in and sending request again.
4. there are not the precedence constraint in " metadata download ", " metadata is uploaded " and " resource upload and download ", can concurrently carry out, thereby increase, upgrade efficiency.
Claims (9)
1. a digital asset upgrades system, it is characterized in that: comprise client, service end, time server and database;
Described client can be for a plurality of, and each client has unique identifier, safeguard a one's own index list, the final updating time that in list, record was updated to the data directory changed so far and was provided by time server from last time;
Described server, provide the database of digital resource; Preserve systematic index list in database;
Described time server, provide accurate, a reliable final updating time; " the final updating time " of all clients is all provided by the time server unification, prevents the data exception problem caused due to time error.
2. the digital asset update method of the described system of claim 1 is characterized in that:
Each client has a unique identifier, and safeguards a one's own index list, the final updating time that in list, record was updated to the data directory changed so far and was provided by time server from last time; Every data in the index list of service end database all identify these data by identifier and derive from which client;
During renewal, at first carry out Data Update, then upgrade index list; The consistency that keeps each client data and index list; The Data Update operation comprises uploading and downloading of metadata and resource, and each Data Update operation is relatively independent, supports concurrent execution;
In the index upgrade operation, the index list that service end is submitted to by contrast self index list and client, obtain the index upgrade result; The client that comprises these other sources of user in this result is update time operation information up to the present and new final updating time in the end;
Client is according to the response results in the index upgrade operation, and generated data upgrades the solicited message of each operation;
Client sends the Data Update request by multithreading after the left over by history operation is merged to solicited message, finally judge the response results of service end, successful upgrade the related data in the local index list, failed will add in the left over by history operation, be deferred to and upgrade operation next time and carry out.
3. digital asset update method according to claim 2, it is characterized in that: digital asset means to belong to the unit carrier of all notes contents of individual subscriber; Article one, digital assets are comprised of metadata and resource two parts; Digital asset and resource are many-one relationships, and many digital assets can be quoted with a resource.
4. according to the described digital asset update method of claim 2 or 3, it is characterized in that: described index upgrade is:
Client is submitted " index upgrade " request to service end, request comprise a for service end upgrade the user local client carry out deletion action digital asset id list, for judging this resource, in service end, whether exist and the final updating time of resource id list, source, user's unique identifier and the local index list avoiding repeating submitting to;
The respective digital assets are deleted in the digital asset id list that service end is submitted to according to client, then upgrade source and the state of correlated digital assets in index list;
In the server side searches index list " the final updating time " of client up to the present this user at the operation information of the client in other sources, and add in response results;
Service end checks in database whether have identical resource according to resource id list, and will check that judged result adds in response results;
Service end joins the new final updating time in response results, and is sent back to client with the data mode of XML;
The response results of client analysis service end, merge corresponding Data Update operation and left over by history operation, generated data update request information; And " final updating time " that service end is sent is updated in index list.If do not receive response message, be considered as the index upgrade failure, finish whole renewal operation.
5. digital asset update method according to claim 4 is characterized in that: described metadata is downloaded and is:
If it is digital asset newly-increased or that revise that state is arranged in the index upgrade result; to service end, submit " metadata download " request to; request comprises digital asset list, user's unique identifier of a digital asset id and state, otherwise does not need to submit to request;
Service end obtains " metadata download " request, by state, is that newly-increased digital asset metadata (not comprising resource) and state revised partly and added in response results for the digital asset of revising;
Service end sends it back client by response results with the data mode of XML;
Client obtains the metadata of digital asset and revises part according to response results, after the renewal local data, upgrades the local index list again; If do not obtain response or response abnormality, be considered as " metadata download " operation failure, and this operation is added in the left over by history operation.
6. digital asset update method according to claim 4, it is characterized in that: described metadata is uploaded and is:
Using the last final updating time to the current final updating time, during this period of time, local newly-increased digital asset, as solicited message, sends " metadata is uploaded " request to service end;
Service end receives " metadata is uploaded " request, and by the digital asset write into Databasce;
Upgrade the index list of service end;
Send a null response result to service end;
Client means that to the null response result " metadata is uploaded " operates successfully, otherwise is considered as operation failure, and this operation is added in the left over by history operation.
7. digital asset update method according to claim 4, it is characterized in that: described resource upload and download is:
Client uploads to needs the Resources list of service end or needs the resource id list of downloading as solicited message, to service end, sends " resource upload and download " request;
According to solicited message, judgement is that resource is uploaded or resource downloading to service end, if resource is uploaded, resource is written in database, then returns to a null response result; If resource downloading, according to resource id, related resource is searched in list, returns after lookup result is added to response results;
The response results of judgement service end, if normal response " resource upload and download " operate successfully, otherwise be considered as " resource upload and download " operation failure, and this operation joined during left over by history operates.
8. digital asset update method according to claim 5, it is characterized in that: described metadata is uploaded and is:
Using the last final updating time to the current final updating time, during this period of time, local newly-increased digital asset, as solicited message, sends " metadata is uploaded " request to service end;
Service end receives " metadata is uploaded " request, and by the digital asset write into Databasce;
Upgrade the index list of service end;
Send a null response result to service end;
Client means that to the null response result " metadata is uploaded " operates successfully, otherwise is considered as operation failure, and this operation is added in the left over by history operation.
9. digital asset update method according to claim 8, it is characterized in that: described resource upload and download is:
Client uploads to needs the Resources list of service end or needs the resource id list of downloading as solicited message, to service end, sends " resource upload and download " request;
According to solicited message, judgement is that resource is uploaded or resource downloading to service end, if resource is uploaded, resource is written in database, then returns to a null response result; If resource downloading, according to resource id, related resource is searched in list, returns after lookup result is added to response results;
The response results of judgement service end, if normal response " resource upload and download " operate successfully, otherwise be considered as " resource upload and download " operation failure, and this operation joined during left over by history operates.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310416671.1A CN103475721B (en) | 2013-09-12 | 2013-09-12 | A kind of digital asset updates the digital asset update method of system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310416671.1A CN103475721B (en) | 2013-09-12 | 2013-09-12 | A kind of digital asset updates the digital asset update method of system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103475721A true CN103475721A (en) | 2013-12-25 |
| CN103475721B CN103475721B (en) | 2016-09-14 |
Family
ID=49800414
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310416671.1A Active CN103475721B (en) | 2013-09-12 | 2013-09-12 | A kind of digital asset updates the digital asset update method of system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103475721B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104166882A (en) * | 2014-08-04 | 2014-11-26 | 武汉金融资产交易所有限公司 | Financial asset transaction method based on P2P technology |
| CN104539655A (en) * | 2014-12-05 | 2015-04-22 | 蓝信工场（北京）科技有限公司 | Method and system for synchronizing and displaying address book in batches |
| CN107016548A (en) * | 2016-12-09 | 2017-08-04 | 阿里巴巴集团控股有限公司 | Client, information processing method and reading/writing method and device |
| CN108306966A (en) * | 2018-01-31 | 2018-07-20 | 腾讯科技（深圳）有限公司 | Document processing method, device, system, terminal and server |
| CN108429732A (en) * | 2018-01-23 | 2018-08-21 | 平安普惠企业管理有限公司 | A kind of method and system obtaining resource |
| WO2018233364A1 (en) * | 2017-06-19 | 2018-12-27 | 华为技术有限公司 | Index updating method and system, and related device |
| CN109658248A (en) * | 2018-12-20 | 2019-04-19 | 姚前 | The system and method that register information updates after a kind of park assets are returned |
| CN109670833A (en) * | 2018-12-20 | 2019-04-23 | 姚前 | The trustship register system and method for assets under a kind of chain to cochain |
| CN111246229A (en) * | 2020-01-07 | 2020-06-05 | 北京字节跳动网络技术有限公司 | Method, device, medium and electronic equipment for updating gift resources of live broadcast room |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1480858A (en) * | 2002-09-03 | 2004-03-10 | 鸿富锦精密工业（深圳）有限公司 | Non Structured data synchronous system and method |
| CN1649432A (en) * | 2003-12-17 | 2005-08-03 | 三星电子株式会社 | Asynchronous mobile communication terminal and asynchronous mobile communication system and method |
| CN1852309A (en) * | 2005-11-16 | 2006-10-25 | 华为技术有限公司 | Data synchronizing processing method and its client end |
| CN102483715A (en) * | 2009-09-04 | 2012-05-30 | Kii株式会社 | Data synchronization system and data synchronization method |
-
2013
- 2013-09-12 CN CN201310416671.1A patent/CN103475721B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1480858A (en) * | 2002-09-03 | 2004-03-10 | 鸿富锦精密工业（深圳）有限公司 | Non Structured data synchronous system and method |
| CN1649432A (en) * | 2003-12-17 | 2005-08-03 | 三星电子株式会社 | Asynchronous mobile communication terminal and asynchronous mobile communication system and method |
| CN1852309A (en) * | 2005-11-16 | 2006-10-25 | 华为技术有限公司 | Data synchronizing processing method and its client end |
| CN102483715A (en) * | 2009-09-04 | 2012-05-30 | Kii株式会社 | Data synchronization system and data synchronization method |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104166882A (en) * | 2014-08-04 | 2014-11-26 | 武汉金融资产交易所有限公司 | Financial asset transaction method based on P2P technology |
| CN104539655A (en) * | 2014-12-05 | 2015-04-22 | 蓝信工场（北京）科技有限公司 | Method and system for synchronizing and displaying address book in batches |
| CN107016548A (en) * | 2016-12-09 | 2017-08-04 | 阿里巴巴集团控股有限公司 | Client, information processing method and reading/writing method and device |
| CN107016548B (en) * | 2016-12-09 | 2022-01-28 | 创新先进技术有限公司 | Client system, information processing method, reading and writing method and device |
| US11308062B2 (en) | 2017-06-19 | 2022-04-19 | Huawei Technologies Co., Ltd. | Index update method and system, and related apparatus |
| WO2018233364A1 (en) * | 2017-06-19 | 2018-12-27 | 华为技术有限公司 | Index updating method and system, and related device |
| CN108429732A (en) * | 2018-01-23 | 2018-08-21 | 平安普惠企业管理有限公司 | A kind of method and system obtaining resource |
| CN108306966B (en) * | 2018-01-31 | 2022-01-21 | 腾讯科技（深圳）有限公司 | Document processing method, device, system, terminal and server |
| CN108306966A (en) * | 2018-01-31 | 2018-07-20 | 腾讯科技（深圳）有限公司 | Document processing method, device, system, terminal and server |
| CN109670833A (en) * | 2018-12-20 | 2019-04-23 | 姚前 | The trustship register system and method for assets under a kind of chain to cochain |
| CN109658248A (en) * | 2018-12-20 | 2019-04-19 | 姚前 | The system and method that register information updates after a kind of park assets are returned |
| CN109658248B (en) * | 2018-12-20 | 2023-01-24 | 姚前 | System and method for updating registration information after return of managed assets |
| CN109670833B (en) * | 2018-12-20 | 2023-06-16 | 姚前 | Escrow registration system and method for under-chain assets to be uplinked |
| CN111246229A (en) * | 2020-01-07 | 2020-06-05 | 北京字节跳动网络技术有限公司 | Method, device, medium and electronic equipment for updating gift resources of live broadcast room |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103475721B (en) | 2016-09-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103475721A (en) | System for updating digital assets and method thereof | |
| CN103067484B (en) | A kind of method and system of auto-update application program | |
| US11379412B2 (en) | Enabling data replication processes between heterogeneous storage systems | |
| CN102307210B (en) | Data downloading system and data management and downloading method thereof | |
| CN102667772B (en) | File level hierarchical storage management system, method, and apparatus | |
| US9229701B2 (en) | Local store data versioning | |
| JP2019517042A (en) | Providing access to hybrid applications offline | |
| CN107193607B (en) | Method and apparatus for updating code file, storage medium, processor, and terminal | |
| CN103443790A (en) | Method and system for synchronization mechanism on multi-server reservation system | |
| CN102349062A (en) | Programming model for synchronizing browser caches across devices and web services | |
| CN102541941A (en) | Version management control method for multiple parties to co-operate file | |
| CN106789249B (en) | Hot updating method, client and server | |
| CN102355503A (en) | Client terminal resource management method, resource management device, system and cloud server | |
| US20120179778A1 (en) | Applying networking protocols to image file management | |
| CN112073994A (en) | Method and device for over-the-air upgrading, electronic equipment and readable storage medium | |
| CN104426955A (en) | Processing method of shared file, and cloud storage server | |
| CN104881454A (en) | Updating method and system of parameter | |
| CN112131177A (en) | Data migration method and device, storage medium and electronic equipment | |
| CN104123160A (en) | Element level updating method for navigation equipment | |
| KR101638689B1 (en) | System and method for providing client terminal to user customized synchronization service | |
| KR101939199B1 (en) | Local terminal and synchronization system including the same | |
| US10185735B2 (en) | Distributed database system and a non-transitory computer readable medium | |
| CN112905676A (en) | Data file importing method and device | |
| US20230126173A1 (en) | Methods, devices and systems for writer pre-selection in distributed data systems | |
| CN113034165A (en) | Data processing method and device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |