CN107770285A - A kind of distributed caching update method and system - Google Patents
A kind of distributed caching update method and system Download PDFInfo
- Publication number
- CN107770285A CN107770285A CN201711115077.3A CN201711115077A CN107770285A CN 107770285 A CN107770285 A CN 107770285A CN 201711115077 A CN201711115077 A CN 201711115077A CN 107770285 A CN107770285 A CN 107770285A
- Authority
- CN
- China
- Prior art keywords
- client
- update message
- buffer update
- clients
- message
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
This application discloses a kind of distributed caching update method and system, this method to include：The buffer update message for the timestamp for carrying any time zone is issued each client by server end；Each client the time corresponding to the first time zone according to where the timestamp calculates this client, performs a thread after the success of order caching new information when being then deferred to same time point, the thread includes renewal and caches and preserve data cached before updating；Server end judges whether all clients all order caching new information successes, if not, rollback message is sent to each client and buffer update message is issued into each client again, is cached successfully if so, judging whether that all clients all update after delay certain time；If at least one client updates cache failure, send rollback message to each client and buffer update message is issued into each client again.The application improves system reliability, and ensure that all clients being capable of synchronized update caching.
Description
Technical field
The present invention relates to distributed caching technical field, more specifically to a kind of distributed caching update method and
System.
Background technology
Existing distributed caching more new system as shown in figure 1, including：Server end, message-oriented middleware and multiple clients
End, server end by same buffer update message transmission to multiple client, make each client executing by message-oriented middleware
Same buffer update operation.
But there is following defect in the more new system of distributed caching shown in Fig. 1：
1) all buffer update message are dependent on message-oriented middleware and transmitted, and are entirely if message-oriented middleware failure
System will paralyse, and system reliability is poor；
2) due to the problem of data transfer delay be present, the time that different clients receive same buffer update message can
Can be inconsistent, it can not ensure that all clients synchronized update caches.
3) because each client is to perform buffer update operation according to the time in the time zone where oneself, as different visitors
When time zone where the end of family is inconsistent, it can not equally ensure that all clients synchronized update caches.
How to overcome drawbacks described above, be those skilled in the art's urgent problem to be solved.
The content of the invention
In view of this, the present invention provides a kind of distributed caching update method and system, to improve system reliability, and protects
Demonstrate,proving all clients being capable of synchronized update caching.
A kind of distributed caching update method, including：
Buffer update message is sent to each client by server end, and the buffer update message carries any time zone
Timestamp；
Wherein, each client calculates according to the timestamp first after the buffer update message success is received
Time corresponding to the time zone gone out where this client, a thread is performed when being then deferred to same time point, the thread includes
Renewal is cached and preserved data cached before updating；
The server end judges whether that all clients all receive the buffer update message success；
If at least one client receives the buffer update message failure, the server end is sent out to each client
Rollback message is sent, and the buffer update message is sent to each client again；
If all clients all receive the buffer update message success, sentence after the server end delay certain time
Breaking, whether all clients, which all update, caches successfully；
If at least one client updates cache failure, the server end sends the rollback to each client and disappeared
Breath, and the buffer update message is sent to each client again.
Optionally, client receives the buffer update message success, including：
Client verifies the legitimacy of the buffer update message when receiving the buffer update message, if institute
It is legal to state buffer update message, then receives the buffer update message success, if the buffer update message is illegal, connects
Receive the buffer update message failure.
Optionally, whether each client succeeds this client new information and whether renewal caching is successful
Record is saved in block chain；
It is corresponding, it is described to judge whether that all clients all receive the buffer update message success, including：Pass through reading
Whether each client new information preserved in the block chain successfully records, and it is described to judge whether that all clients all receive
The success of buffer update message；
It is described to judge whether that all clients all update and cache successfully, including：Preserved by reading in the block chain
Whether each client renewal caching successfully records, and judges whether that all clients all update and caches successfully.
Optionally, the timestamp in any time zone stabs for Greenwich Mean Time.
Optionally, the server end is again exceeding the number that the buffer update message is sent to each client
During preset times, in addition to：Export warning message.
A kind of distributed caching more new system, including server end and multiple client, wherein：
The server end, for buffer update message to be sent into each client, the buffer update message carries
There is the timestamp in any time zone；Judge whether that all clients all receive the buffer update message success；If at least one visitor
Family end receives the buffer update message failure, then sends rollback message to each client, and again by the buffer update
Message is sent to each client；If all clients all receive the buffer update message success, after postponing certain time
Judge whether that all clients all update to cache successfully；If at least one client updates cache failure, to each client
The rollback message is sent, and the buffer update message is sent to each client again；
The client, for after the buffer update message success is received, being calculated first according to the timestamp
Time corresponding to time zone where this client, a thread is performed when being then deferred to same time point, the thread is included more
It is new to cache and preserve data cached before updating.
Optionally, the client verifies the conjunction of the buffer update message when receiving the buffer update message
Method, if the buffer update message is legal, the buffer update message success is received, if the buffer update message
It is illegal, then receive the buffer update message failure.
Optionally, the client is additionally operable to whether succeed this client new information and whether renewal caching succeeds
Record be saved in block chain；
Corresponding, the server end is specifically used for by reading each client new information preserved in the block chain
Whether successfully record, judge whether that all clients all receive the buffer update message success；And by described in reading
Preserved in block chain each client renewal caching whether successfully record, judge whether all clients all update cache into
Work(.
Optionally, the timestamp in any time zone stabs for Greenwich Mean Time.
Optionally, the server end is additionally operable to that the buffer update message is being sent to time of each client again
When number exceedes preset times, warning message is exported.
It can be seen from the above technical scheme that example of the present invention is by decentralization, by server end directly and client
Communicated, avoid the systemic breakdown problem that message-oriented middleware failure is triggered.Moreover, all clients are all according to service
The timestamp that device end is uniformly sent carrys out synchronous local zone time, avoids client and is in different time zone and causes client can not
Synchronized update caches, while all clients avoid data transfer delay to cause client synchronous by postponing thread
Renewal caching, on this basis, server end make all clients synchronized update caching all the time using message rollback mechanism, will not
There is the inconsistent situation of different clients buffer update result.
Brief description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, below will be to embodiment or existing
There is the required accompanying drawing used in technology description to be briefly described, it should be apparent that, drawings in the following description are only this
Some embodiments of invention, for those of ordinary skill in the art, on the premise of not paying creative work, can be with
Other accompanying drawings are obtained according to these accompanying drawings.
Fig. 1 is that a kind of distributed caching updates system structure diagram disclosed in prior art；
Fig. 2 is a kind of distributed caching update method flow chart disclosed in the embodiment of the present invention；
Fig. 3 is that a kind of distributed caching updates system structure diagram disclosed in the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete
Site preparation describes, it is clear that described embodiment is only part of the embodiment of the present invention, rather than whole embodiments.It is based on
Embodiment in the present invention, those of ordinary skill in the art are obtained every other under the premise of creative work is not made
Embodiment, belong to the scope of protection of the invention.
Referring to Fig. 2, the embodiment of the invention discloses a kind of distributed caching update method, is updated applied to distributed caching
Server end in system, the distributed caching update method include：
Step S01：Buffer update message is sent to each client, the buffer update message carries any time zone
Timestamp.
Specifically, the distributed caching updates systems abandon message-oriented middleware, i.e., between server end and client
Decentralization, directly communicated by server end with client, message is dependent on so as to avoid all buffer update message
Middleware is transmitted, and once whole system will paralyse if message-oriented middleware failure the problem of, improves system reliability.
Wherein, each client calculates according to the timestamp first after the buffer update message success is received
Time corresponding to the time zone gone out where this client, a thread is performed when being then deferred to same time point, the thread includes
The caching of this client is updated, and is preserved data cached before renewal.
Specifically, data transfer delay and client be in different time zone, be cause client can not synchronized update delay
The two big reasons deposited.In the case of assuming that each client is all in same time zone, caused by avoiding data transfer from being delayed
Client can not synchronized update caching the problem of, the embodiment of the present invention requires that each client receives the buffer update message
Success after be deferred to same time point perform again buffer update operation, so as to ensure that server end have time enough will cache
New information is sent to each client, and resynchronisation renewal is slow after all clients all receive the buffer update message success
Deposit.
The client caused by avoiding data transfer delay can not synchronized update caching the problem of in the case of, to be real
The client synchronization renewal caching of existing different time zone, the embodiment of the present invention also require that server end stamps one for buffer update message
The timestamp in individual any time zone, such as Greenwich Mean Time stamp, are then then forwarded to each client, then each client will
Time corresponding to time zone according to where the timestamp calculates this client, now each client be synchronized with same ginseng
Examine clock, avoid client that client is in caused by different time zone can not synchronized update caching the problem of.
Step S02：Judge whether that all clients all receive the buffer update message success, if at least one client
End receives the buffer update message failure, into step S03；If all clients all receive the buffer update message into
Work(, into step S04.
Specifically, client receives the buffer update message success, including：Client is receiving the buffer update
During message, the legitimacy of the buffer update message is verified, if the buffer update message is legal, receives the caching more
New information success, if the buffer update message is illegal, receives the buffer update message failure, logical so as to ensure that
The security of letter.
The buffer update message that server end is sent to each client is removed comprising the timestamp, and also including needs to update
Object and update the data.The legitimacy of buffer update message described in client validation, in particular to the checking buffer update
The timestamp that should include in message, need the object that updates and each item data such as update the data all to exist, and institute
After the time for stating time zone where timestamp is converted into client, it is necessary to the current time of this client can not be less than or equal to.
Step S03：Rollback message is sent to each client, afterwards return to step S01.
Specifically, rollback message is used for program or data recovery to last state.When at least one client receives
During the buffer update message failure, server end will send rollback message to all clients, carry out all clients
Rollback is to close the thread, and now the data cached of all clients does not all update, and then server end returns to the step
S01 is retried, until when all clients all receive the buffer update message success, just into step S04, so as to ensure that
There is the synchronism of client.
Step S04：Judge whether that all clients all update after delay certain time to cache successfully, if at least one
Client updates cache failure, return to step S03；Cached successfully if all clients all update, EP (end of program).
Specifically, when all clients all receive the buffer update message success, server end does not send rollback and disappeared
Breath, normally performs the thread when all clients are deferred to same time point.When at least one client updates cache failure
When, server end also can send rollback message to all clients, each client is carried out rollback to recover slow before renewal
Deposit data, to avoid the occurrence of the data cached inconsistent situation of different clients, while server end returns to the step S01
Retry, until all clients are all updated when caching successfully, control terminates, and now all clients is data cached all consistent.
From foregoing description, the embodiment of the present invention is directly led to by decentralization by server end with client
News, avoid the systemic breakdown problem that message-oriented middleware failure is triggered.Moreover, all clients are all united according to server end
One timestamp sent carrys out synchronous local zone time, avoids client and is in different time zone and causes client can not synchronously more
New caching, at the same all clients by postpone thread avoid data transfer delay cause client can not synchronized update delay
Deposit, on this basis, server end makes all clients synchronized update caching all the time using message rollback mechanism, is not in not
With the inconsistent situation of client buffer update result.
Optionally, the record that the embodiment of the present invention is interacted each time using block chain preservation server end with client, with
Ensure that message is safe and reliable.It is described in detail below：
Whether this client new information succeeds each client and whether renewal caching successfully records and protect
It is stored in block chain；
It is corresponding, judge whether that all clients all receive the buffer update message success, bag in the step S02
Include：By reading whether each client new information preserved in the block chain successfully records, judge whether all clients
End all receives the buffer update message success；
Judge whether that all clients all update in the step S04 to cache successfully, including：By reading the block chain
Whether each client renewal caching of middle preservation successfully records, and judges whether that all clients all update and caches successfully.
Optionally, the server end is again exceeding the number that the buffer update message is sent to each client
During preset times (such as more than 3 times), warning message, such as automatic spring warning window etc. are exported, now can directly terminate to control
System.
In addition, referring to Fig. 3, the embodiment of the invention also discloses a kind of distributed caching more new system, including server end
100 and multiple client 200, wherein：
Server end 100, for buffer update message to be sent into each client, the buffer update message carries
The timestamp in any time zone；Judge whether that all clients all receive the buffer update message success；If at least one client
End receives the buffer update message failure, then sends rollback message to each client, and the buffer update disappears again
Breath is sent to each client；If all clients all receive the buffer update message success, sentence after postponing certain time
Breaking, whether all clients, which all update, caches successfully；If at least one client updates cache failure, sent out to each client
The rollback message is sent, and the buffer update message is sent to each client again；
Client 200, for after the buffer update message success is received, calculating this according to the timestamp first
Time corresponding to time zone where client, a thread is performed when being then deferred to same time point, the thread includes renewal
Cache and preserve data cached before updating.
Optionally, client 200 verifies the legal of the buffer update message when receiving the buffer update message
Property, if the buffer update message is legal, the buffer update message success is received, if the buffer update message is not
It is legal, then receive the buffer update message failure.
Optionally, client 200 is additionally operable to whether succeed this client new information and whether renewal caching succeeds
Record be saved in block chain；
Corresponding, server end 100 is specifically used for by reading each client new information preserved in the block chain
Whether successfully record, judge whether that all clients all receive the buffer update message success；And by described in reading
Preserved in block chain each client renewal caching whether successfully record, judge whether all clients all update cache into
Work(.
Optionally, the timestamp in any time zone stabs for Greenwich Mean Time.
Optionally, server end 100 is additionally operable to that the buffer update message is being sent to time of each client again
When number exceedes preset times, warning message is exported.
Each embodiment is described by the way of progressive in this specification, what each embodiment stressed be and other
The difference of embodiment, between each embodiment identical similar portion mutually referring to.For distribution disclosed in embodiment
For formula buffer update system, because it is corresponded to the method disclosed in Example, so description is fairly simple, related part
Referring to method part illustration.
The foregoing description of the disclosed embodiments, professional and technical personnel in the field are enable to realize or using the present invention.
A variety of modifications to these embodiments will be apparent for those skilled in the art, as defined herein
General Principle can be realized in other embodiments in the case where not departing from the spirit or scope of the embodiment of the present invention.Therefore,
The embodiment of the present invention is not intended to be limited to the embodiments shown herein, and be to fit to principles disclosed herein and
The consistent most wide scope of features of novelty.
Claims (10)
- A kind of 1. distributed caching update method, it is characterised in that including：Buffer update message is sent to each client by server end, the buffer update message carry any time zone when Between stab；Wherein, each client calculates this according to the timestamp first after the buffer update message success is received Time corresponding to time zone where client, a thread is performed when being then deferred to same time point, the thread includes renewal Cache and preserve data cached before updating；The server end judges whether that all clients all receive the buffer update message success；If at least one client receives the buffer update message failure, the server end is sent back to each client Message is rolled, and the buffer update message is sent to each client again；If all clients all receive buffer update message success, judge after the server end delay certain time be No all clients, which all update, to be cached successfully；If at least one client updates cache failure, the server end sends the rollback message to each client, And the buffer update message is sent to each client again.
- 2. distributed caching update method according to claim 1, it is characterised in that client receives the buffer update Message success, including：Client verifies the legitimacy of the buffer update message when receiving the buffer update message, if described slow It is legal to deposit new information, then receives the buffer update message success, if the buffer update message is illegal, receives institute State buffer update message failure.
- 3. distributed caching update method according to claim 1, it is characterised in that each client is by this client Whether end new information is successful and whether renewal caching successfully records and be saved in block chain；It is corresponding, it is described to judge whether that all clients all receive the buffer update message success, including：By described in reading Whether each client new information preserved in block chain successfully records, and judges whether that all clients all receive the caching New information success；It is described to judge whether that all clients all update and cache successfully, including：By reading each visitor preserved in the block chain Whether renewal caching in family end successfully records, and judges whether that all clients all update and caches successfully.
- 4. distributed caching update method according to claim 1, it is characterised in that the timestamp in any time zone is Greenwich Mean Time stabs.
- 5. distributed caching update method according to claim 1, it is characterised in that the server end is again by institute When stating buffer update message and being sent to the number of each client and exceed preset times, in addition to：Export warning message.
- A kind of 6. distributed caching more new system, it is characterised in that including server end and multiple client, wherein：The server end, for buffer update message to be sent into each client, the buffer update message, which carries, appoints The timestamp in one time zone；Judge whether that all clients all receive the buffer update message success；If at least one client The buffer update message failure is received, then sends rollback message to each client, and again by the buffer update message It is sent to each client；If all clients all receive the buffer update message success, judge after postponing certain time Whether all clients, which all update, caches successfully；If at least one client updates cache failure, sent to each client The rollback message, and the buffer update message is sent to each client again；The client, for after the buffer update message success is received, calculating this visitor according to the timestamp first Time corresponding to time zone where the end of family, a thread is performed when being then deferred to same time point, it is slow that the thread includes renewal Deposit and preserve data cached before updating.
- 7. distributed caching according to claim 6 more new system, it is characterised in that the client receive it is described During buffer update message, the legitimacy of the buffer update message is verified, if the buffer update message is legal, receives institute The success of buffer update message is stated, if the buffer update message is illegal, receives the buffer update message failure.
- 8. distributed caching according to claim 6 more new system, it is characterised in that the client is additionally operable to this visitor Whether family end new information is successful and whether renewal caching successfully records and be saved in block chain；Corresponding, the server end is specifically used for by whether reading each client new information preserved in the block chain Successfully record, judge whether that all clients all receive the buffer update message success；And by reading the block Whether each client renewal caching preserved in chain successfully records, and judges whether that all clients all update and caches successfully.
- 9. distributed caching according to claim 6 more new system, it is characterised in that the timestamp in any time zone is Greenwich Mean Time stabs.
- 10. distributed caching according to claim 6 more new system, it is characterised in that the server end is additionally operable to When the buffer update message being sent into the number of each client again exceeding preset times, warning message is exported.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711115077.3A CN107770285A (en) | 2017-11-13 | 2017-11-13 | A kind of distributed caching update method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711115077.3A CN107770285A (en) | 2017-11-13 | 2017-11-13 | A kind of distributed caching update method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107770285A true CN107770285A (en) | 2018-03-06 |
Family
ID=61272323
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711115077.3A Pending CN107770285A (en) | 2017-11-13 | 2017-11-13 | A kind of distributed caching update method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107770285A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108600320A (en) * | 2018-03-23 | 2018-09-28 | 阿里巴巴集团控股有限公司 | A kind of data cache method, apparatus and system |
| CN108833610A (en) * | 2018-07-19 | 2018-11-16 | 网宿科技股份有限公司 | A kind of information updating method, apparatus and system |
| CN109254948A (en) * | 2018-08-30 | 2019-01-22 | 郑州云海信息技术有限公司 | The implementation method that client-cache fails after a kind of file system snapshot rollback |
| GB2572387A (en) * | 2018-03-28 | 2019-10-02 | Wirepas Oy | Software-updating method for a wireless communication network |
| CN112783910A (en) * | 2021-01-29 | 2021-05-11 | 浪潮通用软件有限公司 | Data distribution method and system based on message middleware |
| US11080036B2 (en) | 2018-03-28 | 2021-08-03 | Wirepas Oy | Software-updating method for a wireless communication network |
| CN113364822A (en) * | 2020-03-05 | 2021-09-07 | 北京沃东天骏信息技术有限公司 | Cache data updating method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1416387A3 (en) * | 2002-10-31 | 2006-11-22 | Lg Electronics Inc. | System and method for maintaining transaction cache consistency in mobile computing environment |
| CN102073540A (en) * | 2010-12-15 | 2011-05-25 | 北京新媒传信科技有限公司 | Distributed affair submitting method and device thereof |
| CN102413164A (en) * | 2011-08-31 | 2012-04-11 | 北京华电万通科技有限公司 | Web-based three-dimensional scenic visualized editing device and method |
| CN103379159A (en) * | 2012-04-24 | 2013-10-30 | 阿里巴巴集团控股有限公司 | Distributed web site data synchronization method |
| CN106682140A (en) * | 2016-12-20 | 2017-05-17 | 华北计算技术研究所（中国电子科技集团公司第十五研究所） | Multi-system user incremental synchronization method based on timestamps and mapping strategies |
-
2017
- 2017-11-13 CN CN201711115077.3A patent/CN107770285A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1416387A3 (en) * | 2002-10-31 | 2006-11-22 | Lg Electronics Inc. | System and method for maintaining transaction cache consistency in mobile computing environment |
| CN102073540A (en) * | 2010-12-15 | 2011-05-25 | 北京新媒传信科技有限公司 | Distributed affair submitting method and device thereof |
| CN102413164A (en) * | 2011-08-31 | 2012-04-11 | 北京华电万通科技有限公司 | Web-based three-dimensional scenic visualized editing device and method |
| CN103379159A (en) * | 2012-04-24 | 2013-10-30 | 阿里巴巴集团控股有限公司 | Distributed web site data synchronization method |
| CN106682140A (en) * | 2016-12-20 | 2017-05-17 | 华北计算技术研究所（中国电子科技集团公司第十五研究所） | Multi-system user incremental synchronization method based on timestamps and mapping strategies |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108600320A (en) * | 2018-03-23 | 2018-09-28 | 阿里巴巴集团控股有限公司 | A kind of data cache method, apparatus and system |
| GB2572387A (en) * | 2018-03-28 | 2019-10-02 | Wirepas Oy | Software-updating method for a wireless communication network |
| US11080036B2 (en) | 2018-03-28 | 2021-08-03 | Wirepas Oy | Software-updating method for a wireless communication network |
| CN108833610A (en) * | 2018-07-19 | 2018-11-16 | 网宿科技股份有限公司 | A kind of information updating method, apparatus and system |
| CN108833610B (en) * | 2018-07-19 | 2021-08-31 | 网宿科技股份有限公司 | Information updating method, device and system |
| CN109254948A (en) * | 2018-08-30 | 2019-01-22 | 郑州云海信息技术有限公司 | The implementation method that client-cache fails after a kind of file system snapshot rollback |
| CN113364822A (en) * | 2020-03-05 | 2021-09-07 | 北京沃东天骏信息技术有限公司 | Cache data updating method and device |
| CN112783910A (en) * | 2021-01-29 | 2021-05-11 | 浪潮通用软件有限公司 | Data distribution method and system based on message middleware |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107770285A (en) | A kind of distributed caching update method and system | |
| US7349400B2 (en) | Method and system for transport protocol reconstruction and timer synchronization for non-intrusive capturing and analysis of packets on a high-speed distributed network | |
| CN113282603B (en) | Block chain consensus node checking method, device, equipment and storage medium | |
| KR101157100B1 (en) | Time synchronizing device and process and associated products | |
| CN107493340B (en) | Data distribution verification method, device and system in block chain network | |
| EP3367634A1 (en) | Data transmission method and device | |
| CN105912618A (en) | Block chain based charging pile charging transaction communication method and device | |
| CN111510278B (en) | Hyper frame number HFN synchronization method, terminal and storage medium | |
| CA2447821A1 (en) | Synchronization of database data | |
| CN108881231A (en) | The method, apparatus and storage medium of synchronous account information in a kind of group system | |
| CN102014012B (en) | Synchronous alarming method and device | |
| CN108881461A (en) | A kind of data transmission method, apparatus and system | |
| CN109992427A (en) | DPI correlation rule backfills processing method, device, equipment and medium | |
| CN113382011B (en) | Method for preventing replay attack by API interface | |
| WO2008096304A2 (en) | Transmission method, transmitter and data processing system comprising a transmitter | |
| CN113765626B (en) | Data transmission method and device of mobile communication system | |
| CN106850377A (en) | The check system and method for a kind of AFDX bus messages | |
| Neves et al. | Coordinated checkpointing without direct coordination | |
| CN107547160A (en) | A kind of method for synchronizing time and device | |
| CN110457165A (en) | The method and system of the data thermal backup of high reliablity | |
| CN104580488A (en) | Information synchronization method and system | |
| KR101611663B1 (en) | Data communications using connectionless-oriented protocol | |
| CN104954810B (en) | For ensureing the successional switching method of distributed video stream memory system data | |
| CN114760320B (en) | Data synchronization method and system for client and middle server and client | |
| CN110719326B (en) | Data synchronization method in high-availability software system adapting to low-quality communication link |
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: 20180306 |
|
| RJ01 | Rejection of invention patent application after publication |