CN106209948A - A kind of data push method and device - Google Patents
A kind of data push method and device Download PDFInfo
- Publication number
- CN106209948A CN106209948A CN201510230741.3A CN201510230741A CN106209948A CN 106209948 A CN106209948 A CN 106209948A CN 201510230741 A CN201510230741 A CN 201510230741A CN 106209948 A CN106209948 A CN 106209948A
- Authority
- CN
- China
- Prior art keywords
- business datum
- client
- incremental data
- service end
- synchronizing information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 70
- 102100037060 Forkhead box protein D3 Human genes 0.000 claims description 17
- 101001029308 Homo sapiens Forkhead box protein D3 Proteins 0.000 claims description 17
- 238000004321 preservation Methods 0.000 claims description 4
- 230000008569 process Effects 0.000 description 28
- 238000010586 diagram Methods 0.000 description 10
- 230000007246 mechanism Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 241001269238 Data Species 0.000 description 7
- 238000004590 computer program Methods 0.000 description 7
- 230000001360 synchronised effect Effects 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 239000000284 extract Substances 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
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 Transfer Between Computers (AREA)
Abstract
This application discloses a kind of data push method and device, the method service end obtains the synchronizing information of the business datum in client, then, according to described synchronizing information, by being connected, to the incremental data of business datum described in described client push with the length set up between described client.Pass through said method, owing to service end is according to described synchronizing information, can determine that the business datum having had in client, and not yet synchronize the incremental data of business datum in the past, therefore, service end can be pushed to client by not yet synchronizing incremental data in the past in an orderly manner, even and if incremental data loses in transmitting procedure, service end is follow-up can also be known by described synchronizing information, and then retransmit the incremental data lost, thus, improve the reliability of the business datum that client gets from service end.
Description
Technical field
The application relates to field of computer technology, particularly relates to a kind of data push method and device.
Background technology
At present, the Internet is the most universal, and user can be various by using in terminal
The client of application, carries out service interaction with corresponding service end, to obtain the business service that service provider provides.
Wherein, described terminal can be personal computer, mobile phone, panel computer, intelligent watch, vehicle-mounted mobile platform
Etc. terminal, described business can be instant messaging business, net purchase business, on network finance businessinternet, Online Video
The operational lines such as business.
In the prior art, in interaction, in terminal, the client of application is generally basede on Hyper text transfer
Agreement (Hyper Text Transfer Protocol, HTTP) agreement, sends request of data, clothes to service end
Business end then responds this request of data, and corresponding business datum is sent to client.
But, under some application scenarios, time as poor in the communication quality between client and service end, or
Person, during the process exception of client, above-mentioned business datum is in the transmitting procedure from service end to client
A part may be lost, thus the business datum causing client to get is not complete, and service end is the most not
Know.Therefore, in these cases, the reliability of the business datum that client gets is relatively low.
Summary of the invention
The embodiment of the present application provides a kind of data push method, in order to solve in prior art in some applied field
Under scape, the problem that the reliability of the business datum that client gets from service end is relatively low.
The embodiment of the present application provides a kind of data-pushing device, in order to solve in prior art in some applied field
Under scape, the problem that the reliability of the business datum that client gets from service end is relatively low.
A kind of data push method that the embodiment of the present application provides, including:
Service end obtains the synchronizing information of the business datum in client；
Described service end is according to described synchronizing information, by being connected with the length set up between described client, to
The incremental data of business datum described in described client push.
A kind of data push method that the embodiment of the present application provides, including:
Client, for from business datum with it, generates the synchronizing information of described business datum；
Described synchronizing information is reported service end by described client, in order to described service end is according to described same
Step information, to the incremental data of business datum described in described client push.
A kind of data-pushing device that the embodiment of the present application provides, including:
Acquisition module, for obtaining the synchronizing information of the business datum in client；
Pushing module, for according to described synchronizing information, by being connected with the length set up between described client,
To the incremental data of business datum described in described client push.
A kind of data-pushing device that the embodiment of the present application provides, including:
Generation module, for for the business datum in client, generates the synchronizing information of described business datum；
Reporting module, for reporting service end by described synchronizing information, in order to described service end is according to institute
State synchronizing information, to the incremental data of business datum described in described client push.
The embodiment of the present application is by least one technical scheme above-mentioned, owing to service end synchronizes letter according to described
Breath, it may be determined that the business datum having had in client, and not yet synchronize business datum in the past
Maintain between incremental data, and service end with client and have long connection, therefore, service end can in an orderly manner by
Not yet synchronize incremental data in the past and be pushed to client, even and if incremental data lose in transmitting procedure,
Service end is follow-up can also be known by described synchronizing information, and then retransmits the increment number lost to client
According to, thus, improve the reliability of the business datum that client gets from service end.
Accompanying drawing explanation
Accompanying drawing described herein is used for providing further understanding of the present application, constitutes of the application
Point, the schematic description and description of the application is used for explaining the application, is not intended that to the application not
Work as restriction.In the accompanying drawings:
The data-pushing process that Fig. 1 provides for the embodiment of the present application；
Fig. 2 shows, under a kind of actual application scenarios, the data-pushing that the embodiment of the present application provides is detailed
Process；
Fig. 3 shows, under another kind of actual application scenarios, the data-pushing that the embodiment of the present application provides is detailed
Thin process；
The data-pushing process corresponding to Fig. 1 that Fig. 4 provides for the embodiment of the present application；
The data-pushing apparatus structure schematic diagram that Fig. 5 provides for the embodiment of the present application；
The another kind of data-pushing apparatus structure schematic diagram that Fig. 6 provides for the embodiment of the present application.
Detailed description of the invention
For making the purpose of the application, technical scheme and advantage clearer, specifically real below in conjunction with the application
Execute example and technical scheme is clearly and completely described by corresponding accompanying drawing.Obviously, described
Embodiment is only some embodiments of the present application rather than whole embodiments.Based on the enforcement in the application
Example, the every other enforcement that those of ordinary skill in the art are obtained under not making creative work premise
Example, broadly falls into the scope of the application protection.
The data-pushing process that Fig. 1 provides for the embodiment of the present application, specifically includes following steps:
S101: service end obtains the synchronizing information of the business datum in client.
The executive agent of the method for the Information Authentication that the embodiment of the present application provides may is that on terminal or server
The service end of application.Wherein, described service end can be client-side/server-side (Client/Server, C/S)
Service end in structure, it is also possible to be the clothes in browser/service end (Brower/Server, B/S) structure
Business end, accordingly, described client can be the client in C/S structure, it is also possible to be in B/S structure
Browser；Described terminal includes but not limited to: personal computer, mobile phone, panel computer, intelligent watch,
Vehicle-mounted mobile platform etc.；Described server includes but not limited to: personal computer, big-and-middle-sized computer, calculating
Machine cluster etc..
In the embodiment of the present application, described business datum can be the business under arbitrary business scenario determined
Data, such as, for the client of instant messaging application, it may comprise multiple business scenario, for pipe
The business scenario of reason address list, described business datum is the number information etc. of the user in address list, for pipe
Manage the business scenario of short message of transmitting-receiving between specific user, described business datum be with this specific user it
Between transmitting-receiving short message, etc..
General, user is when using the types of applications in terminal, it is possible, firstly, to log in the client of application,
Then, by the various operations carried out on the client, (described service end can position with corresponding service end
On above-mentioned server or on other-end) interact, thus, it is thus achieved that under corresponding business scenario
Business datum.
In actual applications, the business datum under major part business scenario is ordered, such as, for net
The client of upper shopping application, user can perform to inquire about order, add business in shopping cart on the client
The various operation such as product, accordingly, service end according to the operation of user, according to predetermined service logic to
Client sends corresponding business datum, and as when user performs to inquire about order operation, service end then will inquiry
To the details (that is, business datum) of each order descended of user send to client,
Under this business scenario, described business datum is the details of each order, it is clear that each order detailed
Information is ordered into each other, and can place an order the time with comprise in the details of order, represents
The order of the details of each order, the order of the details of the time order more early that places an order is the most forward.
The operation performed on the client for user, if service end would correspond to the complete of this operation every time
The business datum of amount sends to client, like this, adds the processing load of service end.Therefore, exist
In the embodiment of the present application, service end only can send the increasing of the business datum relevant to user operation to client
(incremental data of business datum, that is, belong to the newly-increased of same business scenario with this business datum for amount data
Business datum).Continue to illustrate by example, it is assumed that user had been inquired about by client and once ordered
Single, the details caching of each order that client can send over after service end being inquired about, then, under
When one time user inquires about order again, it is assumed that have the order of this newly-increased user, then service end can be only to client
End returns the details of order that this user increases newly, and need not detailed by each order of being transmitted across
Thin information sends once to client again, thus, reduce the processing load of service end, improve service end
Treatment effeciency.Wherein, in the embodiment of the present application, the form of described business datum and described business datum
The form of incremental data, can be arranged in advance by between client and service end, the application does not do
Limit.
Further, at present, under some application scenarios, such as the communication quality between client and service end
Time poor, or, during the process exception of client, above-mentioned business datum from service end to client
Transmitting procedure may be lost, cause these partial service data lacking loss in client, and service end
And be unaware of, or, above-mentioned business datum from the transmitting procedure of service end to client, transmission sequence
Possible entanglement, causes client to get out of order business datum, affects follow-up use.
In the embodiment of the present application, service end can be connected based on the length set up between client, Yi Jike
The synchronizing information of the business datum on the end of family, solves the problems referred to above.Concrete, based on described long connection, clothes
After business end can send operation requests without waiting for client, then send business datum to client, but can
With actively to the incremental data of client push business datum, this improves the place of client and service end
Reason efficiency；And based on described synchronizing information, service end may determine that existing business datum in client, enter
And in an orderly manner to the incremental data of this existing business datum of client push, wherein, the order of business datum
Can be determined according to the service logic of business datum by service end and/or client.
In the embodiment of the present application, business datum is synchronized to client by service end, and described is same
Step information can reflect the synchronous point of the business datum in client and the business datum in service end, that is,
The business datum (including this synchronous point) before this synchronous point for order, service end has synchronized to give
Client, and the business datum that order is after this synchronous point, service end is not yet synchronized to client.Therefore,
Service end when will to client synchronization business datum time, or, client is actively to service end requested service number
According to time, service end can obtain the synchronizing information of the business datum in client, in order to determine to client with
Walk which business datum, and how to these business datums of client synchronization.
S102: described service end, according to described synchronizing information, is connected by the length set up between described client
Connect, to the incremental data of business datum described in described client push.
In the embodiment of the present application, service end can be set up and maintain long in advance and be connected with client, follow-up base
In this long incremental data connecting transmission service data, like this, one period of this long persistent period connected
In section, client can actively to service end acquisition request from the incremental data of business datum the most with it,
But, by service end actively to these incremental datas of client push, further, service end is according to described
Synchronizing information, can be in an orderly manner to these incremental datas of client push.
It should be noted that described long connection can be the length of arbitrary communication protocol used based on transport layer
Connecting, such as transmission control protocol (Transmission Control Protocol, TCP) is long to be connected, etc..
Described long connection can use prior art to realize, and such as, uses heartbeat packet mode to realize, concrete, visitor
Initially setting up a TCP between family end and service end to be connected, then, client is every prefixed time interval
Just sending a heartbeat packet to service end, this heartbeat packet is then responded by service end, and client judges whether
The service end response to heartbeat packet is have received within the time of regulation, if, it is determined that the TCP of foundation is even
Connecing still effective, otherwise, again set up a TCP with service end and be connected, above-mentioned TCP connects permissible
It is referred to as TCP length to connect.
By said method, owing to service end is according to described synchronizing information, it may be determined that having in client
Business datum, and not yet synchronize the incremental data of business datum in the past, and service end and client it
Between maintain and have long connection, therefore, service end can be pushed to not yet synchronizing incremental data in the past in an orderly manner
Client, accordingly, client can also receive these incremental datas in an orderly manner, even and if incremental data exist
Losing in transmitting procedure, service end is follow-up can also be known by described synchronizing information, and then to client weight
Pass the incremental data lost, thus, improve the reliability of the business datum that client gets from service end.
And, client can obtain the incremental data of business datum the most continually to service end active request, and
It is can to wait that service end pushes these incremental datas passively, therefore, also mitigates the place of client
Reason burden.
In the embodiment of the present application, for above-mentioned steps S101, service end can obtain in several ways
The synchronizing information of the business datum in client, these acquisition modes include but not limited to following two mode:
The first, service end obtains the synchronizing information of the business datum in client, specifically includes: service end
Receive client reports, the synchronizing information of business datum in described client, and preserve described synchronization letter
Breath.
The second, service end, when receiving for the synchronization request of the business datum in client, is searched certainly
That body preserves or that preserve in other positions, the synchronizing information of business datum in described client.Wherein,
Described synchronization request both can by be in service end be responsible for management and control business datum module sent, it is also possible to
Sent by client.
The synchronizing information of the business datum in client can be generated by client, and carries out safeguarding renewal, right
The synchronization letter of the business datum in the above-mentioned second way, client that service end preserves at self, described
Breath, it is clear that be also in former mutual with client, is sent to service end by client and preserves.Enter
And, when the synchronizing information that service end gets, when differing with the synchronizing information self preserved, service end is entered
Should operate based on the synchronizing information got during the follow-up push operation of row, and preserve get same
Step information, to replace the synchronizing information preserved before, like this, can improve what service end was used
The real-time of synchronizing information and reliability.
In actual applications, above-mentioned first kind of way is typically relatively specific for user's real-time query on the client
The application scenarios of up-to-date business datum, or, client is just being opened and is being used the account of user to log in clothes
The application scenarios of business end, or, client application scenarios when the business scenario that service end registration is new.And
The above-mentioned second way is relatively specific for the business datum of service end and updates (that is, generate client
On the incremental data of business datum), and be necessary in time to the application of these incremental datas of client synchronization
Scene.
In the embodiment of the present application, the business datum in client can be made up of multiple business datum blocks, class
As, the incremental data of described business datum can also be made up of multiple incremental data blocks accordingly, and these
Business datum block and incremental data block are ordered into.Follow-up each incremental data block is pushed to client,
Can be used as in client a newly-increased business datum block, like this, service end can be according to for each industry
The sequence identification that business data block and each incremental data block generate, is pushed to client in an orderly manner by each incremental data block
Hold, and service end can determine active client according to the synchronizing information of the business datum in the client obtained
The progress of upper reception incremental data block, and then determine whether that the incremental data block sent is lost in transmission way
Lose, the most then the incremental data block that server can be lost to client push again.
According to the above description, in above-mentioned steps S102, described service end is according to described synchronizing information, logical
Cross the length set up between described client to be connected, to the increment number of business datum described in described client push
According to, specifically include: the sequence identification that described service end comprises according to described synchronizing information, and be described industry
The sequence identification that each incremental data block of comprising of incremental data of business data generates, by with described client it
Between the long connection set up, to incremental data block each described in described client push.
Further described business datum and described business datum block are described in detail.For application
Speech, application can safeguard different business datums for the different user logged in, and business datum may belong to again not
Same business scenario, therefore, in order to distinguish corresponding to different user, and corresponding to different business scene
Business datum, can be identified business datum with ID and business scenario type identification.Concrete,
Described business datum specifically includes ID, business scenario type identification, and at least one orderly industry
Business data block, wherein, each business datum block order in described business datum, described service end give birth to
The sequence identification of this business datum block become represents.
Described business datum block can be the minimum logic unit in described business datum, at this still with immediately
Illustrate as a example by communication applications.Assuming that user A logs in this instant messaging application by the ID of oneself,
And using the short message function in this instant messaging application, then corresponding business scenario is SMS service field
Scape, that this instant messaging application is safeguarded for user A and transmitting-receiving between certain communication contact people all short
Information, can be described as the business datum under SMS service scene, and then, it is every that this business datum is comprised
Individual business datum block corresponds to a short message.Obviously, being ordered between each short message, the transmitting-receiving time is more
The order of forward short message is the most forward.For each business datum block in client traffic data, permissible
The sequence identification being generated this business datum block for it in advance by service end, is used for representing that this business datum block is respectively
Order in business datum block.Accordingly, described synchronizing information can include described ID, described industry
Business scene identity, described business datum comprise, order is positioned at the sequence identification of last business datum block.
In the embodiment of the present application, described service end can be the increment of described business datum as follows
Each incremental data block genesis sequence that packet contains mark: described service end determine preservation, corresponding to described
ID that synchronizing information comprises and the data block of business scenario mark, as the increment of described business datum
The incremental data block that packet contains, and the order mark of each business datum block comprised according to described business datum
Know, and the service logic order between described each business datum block and each incremental data block, the most each
Incremental data block genesis sequence identifies, and wherein, the sequence identification of each incremental data block illustrates this increment number
According to block order in described each business datum block and each incremental data block.
Wherein, service logic order can reflect each business datum block in client and service end is follow-up to push away
In operational order between each incremental data block brought.Still say as a example by SMS service scene
Bright, it is assumed that to have two business datum blocks (that is, two short messages) on active client, according to short message
General service logic, receives and/or sends the order of time forward short message, it should than receiving and/or
Send the front of time short message rearward, then it is believed that: the former service logic order is than the latter
Forward.
Further, the sequence identification that described service end comprises according to described synchronizing information, and be described
The sequence identification that each incremental data block that the incremental data of business datum comprises generates, by with described client
Between the long connection set up, to incremental data block each described in described client push, specifically include: described clothes
Business end, in each incremental data block, determines the industry that the sequence identification sequentially comprised is corresponding in described synchronizing information
Incremental data block after business data block, and the order of incrementally data block, each increment number that will determine
According to block by with between described client set up long connection be pushed to described client, make described client exist
After receiving each incremental data block that described service end pushes, using this incremental data block as business datum block
Add in described business datum, and update described synchronizing information.
In actual applications, service end can be to define corresponding to the incremental data block that client carries out pushing
Data structure as container, for each incremental data block, would correspond to the use that described synchronizing information comprises
Family mark and business scenario identify, and this incremental data block, the sequence identification of this incremental data block of generation
It is placed in same container pushing, like this, the treatment effeciency of service end can be improved, the most just
Process after client receives.Hereinafter citing illustrates.
Such as, service end be the container of incremental data block definition can be the number of entitled Operation Log OPLOG
According to structure, OPLOG is including at least 4 field: PAYLOAD (representing incremental data block), USER ID
(expression ID), BIZ_TYPE (representing business scenario type identification), OPLOG ID (represent
The sequence identification of incremental data block).Then increasing an incremental data block whenever service end, service end can be right
Should ground generate an OPLOG, when service end will to client synchronization business datum time, it is only necessary to by sequential bits
Each OPLOG after the sequence identification that the synchronizing information obtained comprises is pushed to client.Accordingly
, client is after receiving OPLOG, and each incremental data block comprised extracts, then,
And according to the sequence identification of each incremental data, each incremental data is added self as newly-increased business datum block
On business datum in, then the sequence identification in synchronizing information is updated to: after adding each incremental data, from
Order sequence identification the most rearward in business datum with it.If it should be noted that adding each incremental data
After, the sequence identification of each business datum block in client is discontinuous, that is, each sequence identification lacks to
A few sequence identification, then can deduce some incremental data block that service end sent (corresponding to lacking
The incremental data block of sequence identification) may lose in transmitting procedure, in this case, client
Sequence identification in synchronizing information can be updated to: after adding each incremental data, from business datum with it
The sequence identification of order business datum block the most rearward on the premise of keeping continuously.Like this, service end can
With according to the synchronizing information after updating, the incremental data block again lost to client push.
In addition, it is necessary to explanation, for each business datum block on active client, at these business numbers
When pushing to client according to end the most not serviced before block, the sequence identification of these business datum blocks is also by taking
Business end, is adopted as the method generation of each incremental data block genesis sequence mark.
Concrete methods of realizing that some are feasible in order to make it easy to understand, illustrate at this, that genesis sequence identifies:
Service end can be by positive integer as sequence identification, then the order of the sequence identification that numerical value is the least is more leaned on
Before.Assuming that the sequence identification of each business datum block in business datum in client is 1～8, in service end
In addition to having these business datum blocks, the most some incremental data blocks (suppose there is 8), then client
On the sequence identification that comprises of the synchronizing information of business datum be 8, then service end is according to these 8 incremental datas
Service logic relation between block, for these 8 incremental data blocks genesis sequences mark 9～16 respectively, wherein,
The sequence identification of the incremental data block that order is the most forward is the least.That is, each business datum block in client with
The sequence identification of each incremental data block that the follow-up propelling movement of service end comes, is according to service logic sequentially
's.Being similar to, in addition to positive integer, service end can also be by other orderly character set as order mark
Know, such as, English alphabet etc..
It addition, under Distributed Application scene, owing to same client likely corresponds to multiple service end,
Multiple service ends may perform the operation of genesis sequence mark simultaneously, and the most multiple service ends may be different
Incremental data block generates same sequence identification, thus affects the reliability of follow-up propelling movement process.In the application
In embodiment, lock mechanism can be used to solve this problem, wherein, described lock mechanism includes but not limited to happy
See lock mechanism and Pessimistic Locking mechanism.Concrete, when using optimistic lock mechanism, service end is being submitted to data base
Before genesis sequence identification request, from data base, first obtain the up-to-date sequence identification preserved (the most current
Value), then, carry this currency when submitting genesis sequence identification request to, data base receives this generation
After sequence identification request, the currency phase that this currency is actual with sequence identification in data base can be judged
With, the most then it is successfully processed this genesis sequence identification request, otherwise, returns failure response to service end,
Accordingly, server can retry after receiving failure response, such that it is able to prevent sequence identification from repeatedly generating.
And when using Pessimistic Locking mechanism, when certain service end submits genesis sequence identification request to data base,
Will lock by sequence identification, and other service ends need in database maintenance waiting list, wait lock release
After could continue genesis sequence mark, such that it is able to prevent sequence identification from repeatedly generating.Obviously, both locks
Mechanism is respectively arranged with pluses and minuses, and optimistic lock mechanism need not database maintenance waiting list, the response speed to requesting party
Degree is fast, will not blocking request side, but requestor processes pattern is relative complex, Pessimistic Locking requestor processes pattern
Simply, but database overhead is relatively large.More applicable lock mechanism can be selected according to different application scenarios.
According to above-mentioned explanation, Fig. 2 shows, under a kind of actual application scenarios, the embodiment of the present application
The data-pushing detailed process provided.Wherein, described client is specifically divided into three functional modules: industry
Business client modules, synchronization (Synchronization, SYNC) client modules, long connection client
Module；Described service end is the most specifically divided into three functional modules: business service end module, SYNC take
Business end module, long Connection Service end module.Specifically include following steps:
S201:SYNC client modules generates the synchronizing information of the business datum in client, and hands to
Long connection client modules.
S202: the long client modules that connects in advance or in real time and is built between long Connection Service end module
Vertical long connection, and by this long connection, this synchronizing information is reported long Connection Service end module.
When setting up long connection, concrete, long connection client modules and long Connection Service end module can be built
A vertical TCP both-way communication connects, and after being successfully established, the long client modules that connects is every preset time period
Sending a heartbeat packet to long Connection Service end module, long Connection Service end module then responds in Preset Time
This heartbeat packet, such that it is able to maintain this TCP both-way communication to connect, this TCP both-way communication connects and can claim
Connect for long.
S203: this synchronizing information is handed to SYNC server module by long Connection Service end module.
S204:SYNC server module, according to this synchronizing information, determines the increment number of described business datum
According to.
This incremental data is handed to long Connection Service end module by S205:SYNC server module.
S206: long Connection Service end module, by this incremental data, by the long connection set up, is pushed to long company
Connect client.
S207: this incremental data is handed to SYNC client modules by the long client that connects.
S208:SYNC client modules extracts each incremental data block from incremental data, hands to business
Client modules.
S209:SYNC client modules is according to the sequence identification of each incremental data block extracted, to self
The synchronizing information of upper business datum is updated, and notice SYNC server module updates the synchronization preserved
Information.
Fig. 3 shows, under another kind of actual application scenarios, the data-pushing that the embodiment of the present application provides
Detailed process.Wherein, described client and the functional module of described service end, still enter according to the explanation of Fig. 2
Row divides.Specifically include following steps:
S301: business service end module sends incremental data synchronization request to SYNC server module.
S302:SYNC server module, according to the synchronizing information preserved in service end, is determined in client
The incremental data of business datum.
This incremental data is handed to long Connection Service end module by S303:SYNC server module.
S304: long Connection Service end module, by this incremental data, by the long connection set up, is pushed to long company
Connect client.
S305: this incremental data is handed to SYNC client modules by the long client that connects.
S306:SYNC client modules extracts each incremental data block from incremental data, hands to business
Client modules.
S307:SYNC client modules is according to the sequence identification of each incremental data block extracted, to self
The synchronizing information of upper business datum is updated, and notice SYNC server module updates the synchronization preserved
Information.
It will be seen that the data-pushing process in Fig. 2 is actively to be triggered by client, and the data in Fig. 3
Propelling movement process is actively to be triggered by service end end, and this is the data push method provided described in the embodiment of the present application
Two kinds of typical practical applications scenes.
Further, in actual applications, it is also possible to do not divide client and service according to Fig. 2 and Fig. 3
The functional module of end, and it is divided into other functional module.The application is to described client and described service
The functional module of end divides and framework tissue does not limit.
The data-pushing process corresponding to Fig. 1 that Fig. 4 provides for the embodiment of the present application, executive agent is this Shen
Please the client described in embodiment, specifically include following steps:
S401: client, for from business datum with it, generates the synchronizing information of described business datum.
S402: described synchronizing information is reported service end by described client, in order to described service end according to
Described synchronizing information, to the incremental data of business datum described in described client push.
The data push method provided for the embodiment of the present application above, based on same thinking, the application implements
Example also provides for corresponding data-pushing device, as shown in Figure 5, Figure 6.
The data-pushing apparatus structure schematic diagram that Fig. 5 provides for the embodiment of the present application, specifically includes:
Acquisition module 501, for obtaining the synchronizing information of the business datum in client；
Pushing module 502, for according to described synchronizing information, by the length set up between described client
Connect, to the incremental data of business datum described in described client push.
Described acquisition module 501 specifically for, receive client reports, business number in described client
According to synchronizing information, and preserve described synchronizing information.
Described acquisition module 501 specifically for, when receive for the business datum in client synchronization please
When asking, search the synchronizing information of business datum that preserve, in described client.
The incremental data of described business datum comprises at least one incremental data block；
Described pushing module 502 is specifically for, the sequence identification comprised according to described synchronizing information, Yi Jiwei
The sequence identification that each incremental data block that the incremental data of described business datum comprises generates, by with described visitor
The long connection set up between the end of family, to incremental data block each described in described client push.
Described business datum specifically includes ID, business scenario type identification, and orderly at least one
Individual business datum block, wherein, each business datum block order in described business datum, by described service
The sequence identification of this business datum block that end generates represents；
Described synchronizing information specifically includes described ID, described business scenario mark, described business datum
Comprise, order is positioned at the sequence identification of last business datum block.
Described pushing module 502 is additionally operable to each incremental data comprised for the incremental data of described business datum
Block genesis sequence identifies；
Described pushing module 502 is specifically for, use that determine preservation, that comprise corresponding to described synchronizing information
Family mark and the data block of business scenario mark, the increment number comprised as the incremental data of described business datum
According to block, and the sequence identification of each business datum block comprised according to described business datum, and described each business
Service logic order between data block and each incremental data block, the most each incremental data block genesis sequence
Mark, wherein, the sequence identification of each incremental data block illustrates this incremental data block at described each business number
According to the order in block and each incremental data block.
Described pushing module 502 specifically for, in each incremental data block, determine order in described synchronization
Incremental data block after the business datum block that sequence identification that information comprises is corresponding, and incrementally data block
Order, by each incremental data block determined by with between described client set up be pushed to long connection
Described client, makes described client after receiving each incremental data block that described service end pushes, incites somebody to action
This incremental data block adds in described business datum as business datum block, and updates described synchronizing information.
Concrete above-mentioned device as shown in Figure 5 may be located in service end.
The another kind of data-pushing apparatus structure schematic diagram that Fig. 6 provides for the embodiment of the present application, specifically includes:
Generation module 601, for for the business datum in client, generates the synchronization of described business datum
Information；
Reporting module 602, for reporting service end by described synchronizing information, in order to described service end root
According to described synchronizing information, to the incremental data of business datum described in described client push.
Concrete above-mentioned device as shown in Figure 6 may be located in client.
The embodiment of the present application provides a kind of data push method and device, and the method service end obtains in client
The synchronizing information of business datum, described service end according to described synchronizing information, by with described client it
Between the long connection set up, to the incremental data of business datum described in described client push.By said method,
Owing to service end is according to described synchronizing information, it may be determined that the business datum having had in client, and
Not yet synchronize the incremental data of business datum in the past, and between service end with client, maintenance have long connection,
Therefore, service end can be pushed to client by not yet synchronizing incremental data in the past in an orderly manner, even and if increasing
Amount data are lost in transmitting procedure, and service end is follow-up can also be known by described synchronizing information, Jin Erxiang
Client retransmits the incremental data lost, thus, improve the business datum that client gets from service end
Reliability.
Those skilled in the art are it should be appreciated that embodiments of the invention can be provided as method, system or meter
Calculation machine program product.Therefore, the present invention can use complete hardware embodiment, complete software implementation or knot
The form of the embodiment in terms of conjunction software and hardware.And, the present invention can use and wherein wrap one or more
Computer-usable storage medium containing computer usable program code (include but not limited to disk memory,
CD-ROM, optical memory etc.) form of the upper computer program implemented.
The present invention is with reference to method, equipment (system) and computer program product according to embodiments of the present invention
The flow chart of product and/or block diagram describe.It should be understood that can by computer program instructions flowchart and
/ or block diagram in each flow process and/or flow process in square frame and flow chart and/or block diagram and/
Or the combination of square frame.These computer program instructions can be provided to general purpose computer, special-purpose computer, embedding
The processor of formula datatron or other programmable data processing device is to produce a machine so that by calculating
The instruction that the processor of machine or other programmable data processing device performs produces for realizing at flow chart one
The device of the function specified in individual flow process or multiple flow process and/or one square frame of block diagram or multiple square frame.
These computer program instructions may be alternatively stored in and computer or the process of other programmable datas can be guided to set
In the standby computer-readable memory worked in a specific way so that be stored in this computer-readable memory
Instruction produce and include the manufacture of command device, this command device realizes in one flow process or multiple of flow chart
The function specified in flow process and/or one square frame of block diagram or multiple square frame.
These computer program instructions also can be loaded in computer or other programmable data processing device, makes
Sequence of operations step must be performed to produce computer implemented place on computer or other programmable devices
Reason, thus the instruction performed on computer or other programmable devices provides for realizing flow chart one
The step of the function specified in flow process or multiple flow process and/or one square frame of block diagram or multiple square frame.
In a typical configuration, calculating equipment includes one or more processor (CPU), input/defeated
Outgoing interface, network interface and internal memory.
Internal memory potentially includes the volatile memory in computer-readable medium, random access memory
(RAM) and/or the form such as Nonvolatile memory, such as read only memory (ROM) or flash memory (flash
RAM).Internal memory is the example of computer-readable medium.
Computer-readable medium includes that removable media permanent and non-permanent, removable and non-can be by appointing
Where method or technology realize information storage.Information can be computer-readable instruction, data structure, program
Module or other data.The example of the storage medium of computer includes, but are not limited to phase transition internal memory
(PRAM), static RAM (SRAM), dynamic random access memory (DRAM), its
The random access memory (RAM) of his type, read only memory (ROM), electrically erasable are read-only
Memorizer (EEPROM), fast flash memory bank or other memory techniques, read-only optical disc read only memory
(CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tape, tape magnetic
Disk storage or other magnetic storage apparatus or any other non-transmission medium, can be used for storage can be calculated
The information that equipment accesses.According to defining herein, computer-readable medium does not include temporary computer-readable matchmaker
Body (transitory media), such as data signal and the carrier wave of modulation.
Also, it should be noted term " includes ", " comprising " or its any other variant are intended to non-
Comprising of exclusiveness, so that include that the process of a series of key element, method, commodity or equipment not only wrap
Include those key elements, but also include other key elements being not expressly set out, or also include for this process,
The key element that method, commodity or equipment are intrinsic.In the case of there is no more restriction, statement " include
One ... " key element that limits, it is not excluded that including the process of described key element, method, commodity or setting
Other identical element is there is also in Bei.
It will be understood by those skilled in the art that embodiments herein can be provided as method, system or computer journey
Sequence product.Therefore, the application can use complete hardware embodiment, complete software implementation or combine software and
The form of the embodiment of hardware aspect.And, the application can use and wherein include calculating one or more
The computer-usable storage medium of machine usable program code (include but not limited to disk memory, CD-ROM,
Optical memory etc.) form of the upper computer program implemented.
The foregoing is only embodiments herein, be not limited to the application.For this area skill
For art personnel, the application can have various modifications and variations.All institutes within spirit herein and principle
Any modification, equivalent substitution and improvement etc. made, within the scope of should be included in claims hereof.
Claims (16)
1. a data push method, it is characterised in that including:
Service end obtains the synchronizing information of the business datum in client；
Described service end is according to described synchronizing information, by being connected with the length set up between described client, to
The incremental data of business datum described in described client push.
2. the method for claim 1, it is characterised in that service end obtains the business in client
The synchronizing information of data, specifically includes:
Service end receives client reports, the synchronizing information of business datum in described client；And
Preserve described synchronizing information.
3. the method for claim 1, it is characterised in that service end obtains the business in client
The synchronizing information of data, specifically includes:
Service end, when receiving for the synchronization request of the business datum in client, searches preserve, institute
State the synchronizing information of business datum in client.
4. the method for claim 1, it is characterised in that the incremental data bag of described business datum
Containing at least one incremental data block；
Described service end is according to described synchronizing information, by being connected with the length set up between described client, to
The incremental data of business datum described in described client push, specifically includes:
The sequence identification that described service end comprises according to described synchronizing information, and be the increasing of described business datum
The sequence identification that each incremental data block that amount packet contains generates, by the length set up between described client
Connect, to incremental data block each described in described client push.
5. the method as described in Claims 1 to 4 is arbitrary, it is characterised in that described business datum is specifically wrapped
Include ID, business scenario type identification, and at least one orderly business datum block, wherein, often
Individual business datum block order in described business datum, described service end this business datum block generated
Sequence identification represents；
Described synchronizing information specifically includes described ID, described business scenario mark, described business datum
Comprise, order is positioned at the sequence identification of last business datum block.
6. method as claimed in claim 5, it is characterised in that described service end is as follows
Each incremental data block genesis sequence mark that the incremental data of described business datum comprises:
ID that described service end determines preservation, that comprise corresponding to described synchronizing information and business scenario
The data block of mark, the incremental data block comprised as the incremental data of described business datum；And
According to the sequence identification of each business datum block that described business datum comprises, and described each business datum
Service logic order between block and each incremental data block, the most each incremental data block genesis sequence mark
Knowing, wherein, the sequence identification of each incremental data block illustrates this incremental data block in described each business datum
Order in block and each incremental data block.
7. method as claimed in claim 6, it is characterised in that described service end synchronizes letter according to described
The sequence identification that comprises of breath, and each incremental data block comprised for the incremental data of described business datum generates
Sequence identification, by long being connected with set up between described client, to described in described client push respectively
Incremental data block, specifically includes:
Described service end, in each incremental data block, determines the order mark that order comprises in described synchronizing information
Know the incremental data block after corresponding business datum block；And
The incrementally order of data block, by each incremental data block of determining by described client between
The long connection set up is pushed to described client, makes described client receive the every of described service end propelling movement
After individual incremental data block, this incremental data block is added in described business datum as business datum block, and more
New described synchronizing information.
8. a data push method, it is characterised in that including:
Client, for from business datum with it, generates the synchronizing information of described business datum；
Described synchronizing information is reported service end by described client, in order to described service end is according to described same
Step information, to the incremental data of business datum described in described client push.
9. a data-pushing device, it is characterised in that including:
Acquisition module, for obtaining the synchronizing information of the business datum in client；
Pushing module, for according to described synchronizing information, by being connected with the length set up between described client,
To the incremental data of business datum described in described client push.
10. device as claimed in claim 9, it is characterised in that described acquisition module specifically for, connect
Receive client reports, the synchronizing information of business datum in described client, and preserve described synchronizing information.
11. devices as claimed in claim 9, it is characterised in that described acquisition module specifically for, when
When receiving for the synchronization request of the business datum in client, search that preserve, in described client
The synchronizing information of business datum.
12. devices as claimed in claim 9, it is characterised in that the incremental data bag of described business datum
Containing at least one incremental data block；
Described pushing module is specifically for, the sequence identification comprised according to described synchronizing information, and is described
The sequence identification that each incremental data block that the incremental data of business datum comprises generates, by with described client
Between the long connection set up, to incremental data block each described in described client push.
13. as arbitrary in claim 9～12 as described in device, it is characterised in that described business datum is concrete
Including ID, business scenario type identification, and at least one orderly business datum block, wherein,
Each business datum block order in described business datum, described service end this business datum block generated
Sequence identification represent；
Described synchronizing information specifically includes described ID, described business scenario mark, described business datum
Comprise, order is positioned at the sequence identification of last business datum block.
14. devices as claimed in claim 13, it is characterised in that described pushing module is additionally operable to as institute
State each incremental data block genesis sequence mark that the incremental data of business datum comprises；
Described pushing module is specifically for, user's mark that determine preservation, that comprise corresponding to described synchronizing information
Know and the data block of business scenario mark, the incremental data comprised as the incremental data of described business datum
Block, and the sequence identification of each business datum block comprised according to described business datum, and described each business number
According to the service logic order between block and each incremental data block, the most each incremental data block genesis sequence mark
Knowing, wherein, the sequence identification of each incremental data block illustrates this incremental data block in described each business datum
Order in block and each incremental data block.
15. devices as claimed in claim 14, it is characterised in that described pushing module specifically for,
In each incremental data block, determine the business number that the sequence identification sequentially comprised is corresponding in described synchronizing information
According to the incremental data block after block, and the order of incrementally data block, each incremental data block that will determine
By with between described client set up long connection be pushed to described client, make described client receive
After each incremental data block that described service end pushes, this incremental data block is added as business datum block
In described business datum, and update described synchronizing information.
16. 1 kinds of data-pushing devices, it is characterised in that including:
Generation module, for for the business datum in client, generates the synchronizing information of described business datum；
Reporting module, for reporting service end by described synchronizing information, in order to described service end is according to institute
State synchronizing information, to the incremental data of business datum described in described client push.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510230741.3A CN106209948B (en) | 2015-05-07 | 2015-05-07 | A kind of data push method and device |
| PCT/CN2016/079820 WO2016177285A1 (en) | 2015-05-07 | 2016-04-21 | Data pushing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510230741.3A CN106209948B (en) | 2015-05-07 | 2015-05-07 | A kind of data push method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106209948A true CN106209948A (en) | 2016-12-07 |
| CN106209948B CN106209948B (en) | 2019-07-05 |
Family
ID=57218060
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510230741.3A Active CN106209948B (en) | 2015-05-07 | 2015-05-07 | A kind of data push method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106209948B (en) |
| WO (1) | WO2016177285A1 (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106648994A (en) * | 2017-01-04 | 2017-05-10 | 华为技术有限公司 | Method, equipment and system for backup operation on log |
| CN107040576A (en) * | 2016-12-08 | 2017-08-11 | 阿里巴巴集团控股有限公司 | Information-pushing method and device, communication system |
| CN107704607A (en) * | 2017-10-17 | 2018-02-16 | 武汉楚鼎信息技术有限公司 | A kind of method of database in phase |
| CN108156253A (en) * | 2018-01-05 | 2018-06-12 | 中汇信息技术（上海）有限公司 | A kind of data transmission method, apparatus and system |
| CN108391242A (en) * | 2018-02-26 | 2018-08-10 | 青岛海信移动通信技术股份有限公司 | A kind of long-range control method and remote control apparatus |
| WO2018166373A1 (en) * | 2017-03-15 | 2018-09-20 | 阿里巴巴集团控股有限公司 | Data synchronization system and method, and server, client and electronic device |
| CN109379446A (en) * | 2018-12-24 | 2019-02-22 | 杭州复杂美科技有限公司 | Block method for pushing, block acquisition methods, equipment and storage medium |
| CN110097102A (en) * | 2019-04-22 | 2019-08-06 | 上海车轮互联网服务有限公司 | Data configuration method and device suitable for different business scene |
| CN110769053A (en) * | 2019-10-21 | 2020-02-07 | 深圳震有科技股份有限公司 | Data pushing method, system and storage medium |
| CN110795288A (en) * | 2019-11-06 | 2020-02-14 | 杭州复杂美科技有限公司 | Data acquisition method, device and storage medium |
| CN111569413A (en) * | 2020-05-14 | 2020-08-25 | 北京代码乾坤科技有限公司 | Data synchronization method and device |
| CN112492044A (en) * | 2020-12-09 | 2021-03-12 | 恒生电子股份有限公司 | Cache data sharing method and device, equipment and computer readable storage medium |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110324370B (en) * | 2018-03-29 | 2023-05-30 | 北京京东尚科信息技术有限公司 | Method and device for pushing data to client by server |
| CN109040326A (en) * | 2018-11-02 | 2018-12-18 | 北京京东金融科技控股有限公司 | The method and apparatus of PUSH message |
| CN111737029A (en) * | 2020-06-23 | 2020-10-02 | 中国建设银行股份有限公司 | Server, data pushing method and data pushing system |
| CN114500630A (en) * | 2020-10-27 | 2022-05-13 | 航天信息股份有限公司 | Message pushing method, device, system, storage medium and electronic equipment |
| CN112650606B (en) * | 2020-12-30 | 2023-09-01 | 北京奇艺世纪科技有限公司 | Message processing method, device, system, electronic equipment and storage medium |
| CN112765276A (en) * | 2021-01-27 | 2021-05-07 | 云账户技术(天津)有限公司 | Incremental data synchronization method and device |
| CN113316190B (en) * | 2021-05-10 | 2023-08-01 | 上海仝心电子科技有限公司 | Wisdom cloud box and system |
| CN113590719B (en) * | 2021-09-27 | 2022-03-22 | 北京奇虎科技有限公司 | Data synchronization method, device, equipment and storage medium |
| CN115361442B (en) * | 2022-10-18 | 2023-03-07 | 北京京东拓先科技有限公司 | Message pushing method and device, storage medium and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101159764A (en) * | 2007-11-21 | 2008-04-09 | 中国电信股份有限公司 | Method and system to access door data of mobile service |
| CN102761861A (en) * | 2011-04-27 | 2012-10-31 | 中国移动通信集团广东有限公司 | Information updating method, server and information updating system |
| CN103338144A (en) * | 2013-05-30 | 2013-10-02 | 华为软件技术有限公司 | Session data synchronization method and session data synchronization device |
| CN103442042A (en) * | 2013-08-14 | 2013-12-11 | 福建天晴数码有限公司 | Incremental data synchronization method and system |
| CN104580454A (en) * | 2014-12-31 | 2015-04-29 | 乐视网信息技术（北京）股份有限公司 | Data synchronizing method, device and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102938788B (en) * | 2012-11-15 | 2016-03-30 | 易程科技股份有限公司 | The processing method of event and device |
-
2015
- 2015-05-07 CN CN201510230741.3A patent/CN106209948B/en active Active
-
2016
- 2016-04-21 WO PCT/CN2016/079820 patent/WO2016177285A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101159764A (en) * | 2007-11-21 | 2008-04-09 | 中国电信股份有限公司 | Method and system to access door data of mobile service |
| CN102761861A (en) * | 2011-04-27 | 2012-10-31 | 中国移动通信集团广东有限公司 | Information updating method, server and information updating system |
| CN103338144A (en) * | 2013-05-30 | 2013-10-02 | 华为软件技术有限公司 | Session data synchronization method and session data synchronization device |
| CN103442042A (en) * | 2013-08-14 | 2013-12-11 | 福建天晴数码有限公司 | Incremental data synchronization method and system |
| CN104580454A (en) * | 2014-12-31 | 2015-04-29 | 乐视网信息技术（北京）股份有限公司 | Data synchronizing method, device and system |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107040576B (en) * | 2016-12-08 | 2020-03-10 | 阿里巴巴集团控股有限公司 | Information pushing method and device and communication system |
| CN107040576A (en) * | 2016-12-08 | 2017-08-11 | 阿里巴巴集团控股有限公司 | Information-pushing method and device, communication system |
| CN106648994A (en) * | 2017-01-04 | 2017-05-10 | 华为技术有限公司 | Method, equipment and system for backup operation on log |
| CN106648994B (en) * | 2017-01-04 | 2020-09-11 | 华为技术有限公司 | Method, equipment and system for backing up operation log |
| WO2018166373A1 (en) * | 2017-03-15 | 2018-09-20 | 阿里巴巴集团控股有限公司 | Data synchronization system and method, and server, client and electronic device |
| CN107704607A (en) * | 2017-10-17 | 2018-02-16 | 武汉楚鼎信息技术有限公司 | A kind of method of database in phase |
| CN108156253A (en) * | 2018-01-05 | 2018-06-12 | 中汇信息技术（上海）有限公司 | A kind of data transmission method, apparatus and system |
| CN108391242A (en) * | 2018-02-26 | 2018-08-10 | 青岛海信移动通信技术股份有限公司 | A kind of long-range control method and remote control apparatus |
| CN108391242B (en) * | 2018-02-26 | 2021-10-19 | 青岛海信移动通信技术股份有限公司 | Remote control method and remote control device |
| CN109379446A (en) * | 2018-12-24 | 2019-02-22 | 杭州复杂美科技有限公司 | Block method for pushing, block acquisition methods, equipment and storage medium |
| CN110097102A (en) * | 2019-04-22 | 2019-08-06 | 上海车轮互联网服务有限公司 | Data configuration method and device suitable for different business scene |
| CN110769053A (en) * | 2019-10-21 | 2020-02-07 | 深圳震有科技股份有限公司 | Data pushing method, system and storage medium |
| CN110769053B (en) * | 2019-10-21 | 2022-04-19 | 深圳震有科技股份有限公司 | Data pushing method, system and storage medium |
| CN110795288A (en) * | 2019-11-06 | 2020-02-14 | 杭州复杂美科技有限公司 | Data acquisition method, device and storage medium |
| CN110795288B (en) * | 2019-11-06 | 2023-02-10 | 杭州复杂美科技有限公司 | Data acquisition method, device and storage medium |
| CN111569413A (en) * | 2020-05-14 | 2020-08-25 | 北京代码乾坤科技有限公司 | Data synchronization method and device |
| CN111569413B (en) * | 2020-05-14 | 2023-06-13 | 北京代码乾坤科技有限公司 | Data synchronization method and device |
| CN112492044A (en) * | 2020-12-09 | 2021-03-12 | 恒生电子股份有限公司 | Cache data sharing method and device, equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106209948B (en) | 2019-07-05 |
| WO2016177285A1 (en) | 2016-11-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106209948A (en) | A kind of data push method and device | |
| CN112288097B (en) | Federal learning data processing method, federal learning data processing device, computer equipment and storage medium | |
| CN103457905B (en) | Method of data synchronization, system and equipment | |
| CN108898390A (en) | Intelligent contract call method and device, electronic equipment based on block chain | |
| RU2004131856A (en) | METHODS AND DEVICE FOR SYNCHRONIZING HOW DATA IS STORED IN VARIOUS DATA STORAGES | |
| CN103297459B (en) | The synchronization system of application configuration information, access server, client and method | |
| CN104184832B (en) | Data submission method and device in network application | |
| CN105915612A (en) | Push message acquisition method, message push method and device | |
| CN101340371A (en) | Session keeping method and load balance apparatus | |
| CN103297529A (en) | Timestamp-based tree structure data synchronization method | |
| CN107465722A (en) | The implementation method and device of web access | |
| CN110197075A (en) | Resource access method, calculates equipment and storage medium at device | |
| AU2019380380B2 (en) | Taking snapshots of blockchain data | |
| CN107241451B (en) | Interference method, apparatus and system are distorted based on content distributing network | |
| CN107992489A (en) | A kind of data processing method and server | |
| CN110535815A (en) | A kind of method and apparatus identifying URL | |
| CN110661851A (en) | Data exchange method and device | |
| US20220239713A1 (en) | Computer-based systems configured to adjust data capacity in a data stream generated from multiple data producer applications and methods of use thereof | |
| KR20120073799A (en) | Data synchronizing and servicing apparatus and method based on cloud storage | |
| CN114422538B (en) | Multi-cloud storage system, multi-cloud data reading and writing method and electronic equipment | |
| CN105933352B (en) | Method of data synchronization, client and system between client-based server | |
| CN2929830Y (en) | Search engine server and search system | |
| CN105791350B (en) | Project data processing method and system | |
| CN114793244A (en) | Resource processing method, device, equipment and medium for block chain | |
| CN106407452A (en) | Method and device for server data access |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1231270 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200925 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Ltd. |
|
| TR01 | Transfer of patent right |