CN106034148B - Rapid information interaction method, local server, remote server and system - Google Patents

Rapid information interaction method, local server, remote server and system Download PDF

Info

Publication number
CN106034148B
CN106034148B CN201510112072.XA CN201510112072A CN106034148B CN 106034148 B CN106034148 B CN 106034148B CN 201510112072 A CN201510112072 A CN 201510112072A CN 106034148 B CN106034148 B CN 106034148B
Authority
CN
China
Prior art keywords
associated data
data
request
update
updating request
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.)
Active
Application number
CN201510112072.XA
Other languages
Chinese (zh)
Other versions
CN106034148A (en
Inventor
王俊
张自平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Advanced New Technologies Co Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201510112072.XA priority Critical patent/CN106034148B/en
Publication of CN106034148A publication Critical patent/CN106034148A/en
Application granted granted Critical
Publication of CN106034148B publication Critical patent/CN106034148B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

The application discloses a quick information interaction method, a local server, another quick information interaction method, a remote server and a quick information interaction system. The quick information interaction method comprises the following steps: the local server receives a data updating request sent by the client; the local server side updates corresponding data stored in local client information according to the data updating request; if the data is updated, the local server generates an associated data updating request for requesting to update associated data related to the data according to the data updating request, sends the associated data updating request to a remote server storing the associated data, and feeds back data updating success information to the client. By adopting the method provided by the application, the remote server can complete the update of the associated data by sending the associated data update request to the remote server, so that the time-consuming interaction operation is avoided, the information interaction is rapidly completed, and the information interaction efficiency is improved.

Description

Rapid information interaction method, local server, remote server and system
Technical Field
The application relates to the technical field of communication, in particular to a quick information interaction method, a local server, a remote server and a system.
Background
With the continuous development of network technology, the number of network applications is increasing, and information interaction through the network is also becoming more and more frequent. The information interaction is of various types, including data update type information interaction, that is, data update is realized through information interaction. For example, in the process of processing a transaction by using a network application, existing data often needs to be updated according to a changing condition, and at this time, data update needs to be realized through information interaction. Generally, data updating type information interaction can be completed quickly, but in some cases, for example, in order to improve system capacity and remote disaster tolerance capability, the same application is deployed to different machine rooms in remote places, and a database corresponding to the application is also deployed in remote places, because of the data updating type information interaction process, in the same flow, related data operation has the condition of spanning the remote machine rooms, so that delay can be generated in the data updating type information interaction, namely, under the condition of spanning the remote machine rooms, the completion time of the data updating type information interaction is longer than that under the normal condition; and generally, the data to be updated must be updated simultaneously in the shortest time, so that information interaction must be completed quickly.
In summary, in the prior art, a time-consuming interactive operation problem exists, which causes a delay in information interaction, that is, the information interaction completion time is too long, and the information interaction efficiency is reduced.
Disclosure of Invention
The application provides a quick information interaction method, a local server, a remote server and a system, which aim to solve the problem of time-consuming interaction operation in the prior art.
The application provides a quick information interaction method, which comprises the following steps:
the local server receives a data updating request sent by the client;
the local server side updates corresponding data in the client information stored locally according to the data updating request;
if the data is updated, the local server generates an associated data updating request for requesting to update associated data related to the data according to the data updating request, sends the associated data updating request to a remote server storing the associated data, and feeds back successful data updating information to the client.
Optionally, the local server generates, according to the data update request, an associated data update request for requesting to update associated data related to the data, and sends the associated data update request to a remote server storing the associated data, where the specific steps include:
the local server generates an associated data updating request for requesting to update associated data related to the data according to the data updating request;
the local server side judges whether the associated data updating request is generated or not;
if yes, the local server sends the associated data updating request to a remote server storing the associated data;
if not, the local server returns to execute the step of generating an associated data updating request for requesting to update associated data related to the data according to the data updating request by the local server.
Optionally, the sending the associated data update request to the remote server storing the associated data includes:
the local server side sends the associated data updating request to a local message middleware;
the local message middleware receives the associated data updating request;
and the local message middleware sends the associated data updating request to the remote server.
Optionally, the method further includes:
the local server judges whether the associated data updating request is generated or not;
if yes, the local server side judges whether the local message middleware receives the associated data updating request;
if not, the local server returns to execute the step that the local server sends the associated data updating request to the local message middleware.
Optionally, the method further includes:
the local server side judges whether the local message middleware finishes sending the associated data updating request to the remote server side;
if the request is finished, the local server judges whether the local message middleware receives the information which is fed back by the remote server and successfully receives the associated data updating request;
if not, the local server returns to execute the step of sending the associated data updating request to the remote server by the local message middleware.
Optionally, if the associated data is stored in at least two different location servers, the sending of the associated data update request to the different location server storing the associated data specifically includes:
and the local server selects one of the remote servers for storing the associated data, and sends the associated data updating request to the selected remote server for storing the associated data.
Correspondingly, the present application further provides a local server, including:
the data updating request receiving unit is used for receiving a data updating request sent by a client;
the data updating unit is used for updating corresponding data in the client information stored locally according to the data updating request;
and the information sending unit is used for generating an associated data updating request for requesting to update associated data related to the data according to the data updating request if the data is updated, sending the associated data updating request to a remote server for storing the associated data, and feeding back successful data updating information to the client.
Optionally, the generating, according to the data update request, an associated data update request requesting to update associated data related to the data, and sending the associated data update request to a remote server storing the associated data includes:
generating an associated data updating request for requesting to update associated data related to the data according to the data updating request;
judging whether the associated data updating request is generated or not;
if yes, sending the associated data updating request to a remote server storing the associated data;
if not, returning to the step of executing the associated data updating request for generating the associated data which requests to update the associated relation with the data according to the data updating request.
Optionally, the sending the associated data update request to the remote server storing the associated data includes:
sending the associated data updating request to local message middleware;
the local message middleware receives the associated data updating request;
and the local message middleware sends the associated data updating request to the remote server.
Optionally, the method further includes:
a related data update request generation result judgment unit for judging whether the related data update request is generated;
a related data update request receiving result judging unit, configured to receive a judgment result of the related data update request generation result judging unit, and if the judgment result is yes, determine whether the local message middleware receives the related data update request;
and the first returning unit is used for receiving the judgment result of the associated data updating request receiving result judging unit, and if the judgment result is not received, returning to execute the step of sending the associated data updating request to the local message middleware.
Optionally, the method further includes:
a related data updating request sending result judging unit, configured to judge whether the local message middleware completes sending the related data updating request to the remote server;
a remote server side feedback information receiving result judging unit, configured to receive a judgment result of the association data update request sending result judging unit, and if the judgment result is complete, determine whether the local message middleware receives information that the association data update request has been successfully received and is fed back by the remote server side;
and the second returning unit is used for receiving the judgment result of the remote server feedback information receiving result judging unit, and if the judgment result is not received, returning to the step of executing the local message middleware to send the associated data updating request to the remote server.
Optionally, if the associated data is stored in at least two different location servers, the sending of the associated data update request to the different location server storing the associated data specifically includes:
and selecting one of the remote service terminals for storing the associated data, and sending the associated data updating request to the selected remote service terminal for storing the associated data.
The application also provides a quick information interaction method, which comprises the following steps:
the remote server side stores the associated data, and receives a data updating request which is generated by the local server side according to the data updating request received from the client side and requests to update the associated data related to the data;
and the remote server completes the corresponding update operation of the associated data according to the associated data update request.
Optionally, the receiving, by the remote server storing the associated data, the data update request requesting to update the associated data related to the data according to the data update request received by the local server from the client includes:
and the message middleware of the remote server storing the associated data receives the associated data updating request of the local server for requesting to update the associated data related to the data according to the data updating request received by the local server from the client.
Optionally, the remote server completes the corresponding update operation of the associated data according to the associated data update request, and the specific steps include:
the remote server receives the associated data updating request sent by the message middleware;
the remote server analyzes the associated data updating request to obtain a change value of the associated data;
and the remote server side updates the associated data according to the change value of the associated data.
Optionally, the method further includes:
the remote server side judges whether the updating operation of the associated data is finished or not corresponding to the associated data ID in the associated data updating request;
if not, the remote server returns to execute the step of updating the associated data by the remote server according to the change value of the associated data.
Optionally, if the associated data is stored in at least two different location servers, the different location server storing the associated data receives a data update request received by a local server from a client to generate an associated data update request requesting to update the associated data related to the data, specifically:
and receiving an associated data updating request of requesting to update the associated data related to the data according to a data updating request received by the local server from a client by the local server through the message middleware of the remote server selected by the local server and storing the associated data.
Optionally, the remote server completes the corresponding update operation of the associated data according to the associated data update request, specifically:
and the selected allopatric server storing the associated data completes the corresponding updating operation of the associated data according to the associated data updating request.
Optionally, the selected remote server storing the associated data completes the corresponding update operation of the associated data according to the associated data update request, and the specific steps include:
the selected allopatric server end storing the associated data receives the associated data updating request sent by the message middleware;
the selected allopatric server side storing the associated data analyzes the associated data updating request to obtain a change value of the associated data;
the selected allopatric server side for storing the associated data updates the associated data stored locally according to the change value of the associated data;
the selected allopatric server side storing the associated data calls an update data function of the unselected allopatric server side storing the associated data according to the associated data update request;
and the selected allopatric server storing the associated data updates the associated data which is not updated through the update data function according to the change value of the associated data.
Correspondingly, the application also provides a remote server for the rapid information interaction method, which comprises the following steps:
the associated data updating request receiving unit is used for receiving an associated data updating request of a local server for generating a request for updating the associated data related to the data according to a data updating request received by the local server from a client;
and the associated data updating unit is used for finishing the corresponding updating operation of the associated data according to the associated data updating request.
Optionally, the receiving local server generates, according to the data update request received from the client, an associated data update request for requesting to update the associated data related to the data, specifically:
the message middleware receives a data updating request which is generated by the local server according to the data updating request received from the client and requests to update the associated data which has the associated relationship with the data.
Optionally, the step of completing the corresponding update operation of the associated data according to the associated data update request includes:
the associated data updating request sent by the message middleware is received;
analyzing the associated data updating request to obtain a change value of the associated data;
and updating the associated data according to the change value of the associated data.
Optionally, the method further includes:
an update operation completion result determination unit configured to determine whether an update operation of the associated data is completed, corresponding to the associated data ID in the associated data update request;
and the step returning unit is used for receiving the judgment result of the updating operation completion result judging unit, and if the judgment result is incomplete, returning to the step of executing the change value according to the associated data and updating the associated data.
Optionally, if the associated data is stored in at least two remote servers, the update operation of the associated data is completed according to the associated data update request, and the specific steps include:
receiving the associated data updating request sent by the message middleware;
analyzing the associated data updating request to obtain a change value of the associated data;
updating the associated data stored locally according to the change value of the associated data;
calling an update data function of a remote server storing the non-updated associated data according to the associated data update request;
and updating the associated data which is not updated through the updating data function according to the change value of the associated data.
In addition, this application still provides a quick information interaction system, includes: client, the local server and the remote server.
Compared with the prior art, the method has the following advantages:
according to the rapid information interaction method, the local server, the remote server and the system, the data updating request sent by the client is received through the local server; the local server side updates corresponding data in the client information stored locally according to the data updating request; if the data is updated, the local server generates an associated data updating request for requesting to update associated data related to the data according to the data updating request, sends the associated data updating request to a remote server storing the associated data, and feeds back successful data updating information to the client. According to the technical scheme, the associated data updating request is sent to the remote server, so that the remote server can update the associated data, time-consuming interaction operation is avoided, information interaction can be completed quickly, and the information interaction efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a flowchart of an embodiment of a method for rapid information interaction according to the present application;
FIG. 2 is a schematic diagram of an embodiment of a local server of the present application;
FIG. 3 is a flow chart of another embodiment of a method for rapid information interaction according to the present application;
FIG. 4 is a schematic diagram of an embodiment of an offsite server of the present application;
fig. 5 is a schematic diagram of an embodiment of a rapid information interaction system according to the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
In the present application, a fast information interaction method and a local server, another fast information interaction method and a remote server, and a fast information interaction system are provided, respectively, and the following are specific embodiments:
fig. 1 is a flowchart illustrating an embodiment of a method for fast information interaction according to the present application. The method comprises the following steps:
step S101: the local server receives a data updating request sent by the client.
When a client needs to provide data updating service by a local server, a data updating request needs to be sent to the local server through the client, and the local server needs to receive the data updating request so as to execute corresponding data updating operation according to the data updating request. Specifically, the local server may receive a data update request initiated by the client by clicking or pressing a key or the like.
Taking a payment service as an example for explanation, in this embodiment, the local server stores payer account information, where the payer account information includes balance information of a payment account, electronic bill information, and the like; the electronic bill can be an electronic red packet, an electronic discount card and the like; when a payer pays by using an electronic bill in an account of the payer, the payer sends an electronic bill payment request to a local server through a client, such as a mobile phone, a Pad or a PC (personal computer), wherein the electronic bill payment request is a data updating request, and the data requested to be updated comprises electronic bill data in account information of the payer; the local server needs to receive the electronic bill payment request sent by the client, so as to execute the corresponding data updating operation according to the electronic bill payment request.
Step S102: and the local server side updates the corresponding data in the client information stored locally according to the data updating request.
The data update request information may include the data ID requested to be updated and an updated value of the data, i.e., a value of the data requested to be updated after being updated, or include information such as a changed value of the data, i.e., a value to which the data requested to be updated should be increased or decreased. After the local server receives the data updating request sent by the client, corresponding data needs to be searched from the client information stored in the local server according to the data ID requested to be updated in the data updating request information, and corresponding data in the client information stored in the local server is updated according to the updating value or the change value of the data requested to be updated in the data updating request information.
In this embodiment, when the payer pays by using the electronic ticket in the account of the payer, the data requested to be updated by the electronic ticket payment request includes the electronic ticket data in the account information of the payer, and accordingly, the electronic ticket payment request information includes the electronic ticket data ID and the updated value or the changed value of the electronic ticket data. After the electronic bill application of the local service end receives an electronic bill payment request sent by a payer through a client, corresponding electronic bill data are searched from the information stored in the local service end according to the electronic bill data ID requested to be updated in the electronic bill payment request information, and if the numerical value of the electronic bill data in the found payer account information is 3; then, the electronic bill data stored in the local payer account information is updated according to the updated value or the changed value of the electronic bill data requested to be updated in the electronic bill payment request information, that is, the selected electronic bill in the payer account is verified, for example, in the current payment service, the payer pays by using one electronic bill in the payer account, so that the updated value of the electronic bill data is 2, and the changed value is 1, that is, the electronic bill application of the local service end needs to replace the numerical value 3 of the electronic bill data with the updated value 2, or change the numerical value 3 of the electronic bill data into 2 according to the changed value 1, and the verification operation on the selected electronic bill is completed.
Step S103: if the data is updated, the local server generates an associated data updating request for requesting to update associated data related to the data according to the data updating request, sends the associated data updating request to a remote server storing the associated data, and feeds back successful data updating information to the client.
Usually, there is associated data associated with a certain item of data, and after the data is updated, the associated data is also updated, for example, in the student end result table, the associated data of a certain student single item of subject result data is the total result data of the student, and after the single item of subject result data is updated, the corresponding total result data is also updated.
In this embodiment, the payer chooses to pay the transaction amount to the payee using the electronic ticket. Before the electronic ticket is issued, the issuer stores the deposit corresponding to the total amount of the electronic ticket issued in the deposit account. Therefore, the deposit data of the deposit account information and the collection account balance data of the payee account information are data having an association relationship with the electronic ticket data. When the electronic bill is used for payment, after the selected electronic bill is checked and sold, the corresponding deposit is deducted from the deposit account corresponding to the electronic bill, and the corresponding collection account balance is added to the account of the collection party, namely after the electronic bill data is updated, the deposit data and the collection account balance data are also updated.
It should be noted that, in some cases, a certain item of data and associated data having an association relationship with the certain item of data may be stored in different remote servers, and after the certain item of data stored in the local server is updated, the associated data stored in the different remote servers also needs to be updated. For example, in this embodiment, in order to improve system capacity and remote disaster recovery capability, the electronic bill payment application is deployed to a different remote server, where the electronic bill payment application includes an electronic bill application and an accounting application, after the remote deployment, the local server has the electronic bill application and the accounting application, and the remote server also has the electronic bill application and the accounting application. In this case, there is a case where the payer account information is stored in the local server, and the deposit account information and the payee account information are stored in the remote server. After the electronic bill data stored in the local server is updated, the deposit data and the balance data of the collection account stored in the remote server are also updated.
In this case, the existing manner of updating some data and associated data stored in different remote servers is that, taking electronic bill payment as an example, after the electronic bill application at the local server checks and sells the selected electronic bill, that is, after the electronic bill data is updated, it will call the accounting application at the different remote server storing the deposit account information, and complete the deduction operation of the deposit, that is, the update operation of the deposit data. For the update of the balance data of the collection account, if the account information of a collection party is also stored in the remote server, the financial application of the remote server can simultaneously complete the update operation of the balance data of the collection account, if the account information of the collection party is stored in another remote server, after the electronic bill application of the local server completes the update operation of the electronic bill data, the financial application of the remote server storing the deposit account information can be called to complete the deduction operation of the deposit, the financial application of the remote server storing the account information of the collection party is called to complete the increase operation of the balance of the collection account, and after all the data are updated, the local server can feed back successful payment information to the client.
Because the operation of calling the accounting application of the remote server by the electronic bill application of the local server belongs to the operation of crossing the remote server, the operation will generate a long delay, for example, if the operation completion time of calling the accounting application of the local server is 10ms and the distance between the local server and the remote server is more than 1500 km, the operation of calling the accounting application of the remote server by the electronic bill application of the local server will generate a delay of more than 30ms, that is, the completion time of the operation of crossing the remote server is more than 40 ms. Due to the time-consuming interactive operation in the information interaction process, the payment is delayed, namely the payment completion time is too long.
In order to avoid the delay of information interaction, in the method provided by the present application, if the data update operation is completed in step S102, in this step, the local server further needs to generate an associated data update request requesting to update associated data related to the data according to the data update request, send the associated data update request to a remote server storing the associated data, and feed back the successful data update information to the client. After the local server finishes updating the data requested to be updated, which is stored locally, the local server only needs to generate a related data updating request, send the related data updating request to the remote server, and feed back the data updating success information to the client, so that the operation of updating the related data stored in the remote server by calling a function across the remote server is not needed, and the operation of updating the related data can be finished by the remote server storing the related data. Finally, the method and the system are realized by sending the associated data updating request to the remote server to update the associated data, so that time-consuming interactive operation is avoided, information interaction is quickly completed, and the information interaction efficiency is improved. It should be noted that, in the process of information interaction by applying the method provided by the present application, it is required to ensure that the associated data update request is delivered to a remote server, so that the correctness of the successful data update information fed back to the client can be ensured.
In this embodiment, the local server generates, according to the data update request, an associated data update request requesting to update associated data related to the data, and sends the associated data update request to a remote server storing the associated data, where the specific steps include: the local server generates an associated data updating request for requesting to update associated data related to the data according to the data updating request; the local server side judges whether the associated data updating request is generated or not; if yes, the local server sends the associated data updating request to a remote server storing the associated data; if not, the local server returns to execute the step of generating an associated data updating request for requesting to update associated data related to the data according to the data updating request by the local server.
Specifically for the payment service, in this embodiment, if the updating operation of the electronic ticket data is completed in step S102, in this step, the electronic ticket application of the local server further needs to generate an associated data updating request for requesting to update associated data related to the electronic ticket data according to the electronic ticket payment request. Since the associated data of the electronic bill data is the deposit data and the balance data of the collection account, the associated data update request can pay the bill for the electronic bill. In order to ensure consistency of the state of the electronic bill and the electronic bill payment bill, the electronic bill payment bill must be successfully created in the case that the electronic bill data has been updated, i.e., the electronic bill has been verified and sold. Therefore, after the step of generating the electronic bill document is executed, the electronic bill application of the local server needs to judge whether the electronic bill payment document is generated; if yes, the electronic bill application of the local server sends an electronic bill document to a remote server storing deposit data and collection account balance data; if not, returning to the step of executing the associated data updating request of the electronic bill application of the local server for generating the request for updating the associated data related to the electronic bill data according to the electronic bill payment request.
It should be noted that, in this embodiment, the sending the association data update request to the remote server storing the association data includes the specific steps of: the local server side sends the associated data updating request to a local message middleware; the local message middleware receives the associated data updating request; and the local message middleware sends the associated data updating request to the remote server. If so, the electronic bill application of the local service end sends the electronic bill payment document to the local message middleware application; receiving an electronic bill payment document by the local message middleware application; the local messaging middleware application sends the electronic bill payment document to the remote server.
It should be noted that, in this embodiment, after the data is updated, the local server may first perform feedback of the successful data update information to the client, then perform generation of an associated data update request requesting to update associated data related to the data according to the data update request, and send the associated data update request to the remote server storing the associated data. In some cases, the client sending the data update request through the client feels only the change of the data requested to be updated stored in the local server at the client, but does not feel the change of the associated data having an association relation with the data stored in the remote server. Therefore, in this step, after the data requested to be updated is updated, the local server does not need to first execute an associated data update request for requesting to update associated data related to the data according to the data update request, and send the associated data update request to the remote server storing the associated data, so that the local server can first execute feedback of successful data update information to the client. .
In the payment service in this embodiment, the payer only feels the verification and cancellation of the electronic ticket in the payer account during the actual payment process, and the operations of deducting the deposit of the deposit account and increasing the balance of the collection account of the payee account are not aware. Therefore, after the electronic bill is checked and sold, the local server side can feed back successful payment information to the client side without waiting for finishing deduction of the deposit and increase of the balance of the collection account. After the electronic bill is checked and sold, the electronic bill payment bill is sent to the remote server, and the remote server completes deduction of the deposit and increase of the balance of the collection account. The operation of crossing different-place service terminals is not executed in the synchronous payment process, time-consuming interactive operation is avoided, the payment process is quickly completed, and the payment efficiency is improved. Meanwhile, the remote server can immediately execute asynchronous fund processing operation after receiving the electronic bill payment document, thereby ensuring the timeliness of collection of the payee.
It should be noted that, in order to ensure that the message middleware must receive the associated data request after the associated data request is generated, for example, after the electronic bill payment document is generated, the message middleware must ensure that the document information is received, in this embodiment, the method further includes: the local server judges whether the associated data updating request is generated or not; if yes, the local server side judges whether the local message middleware receives the associated data updating request; if not, the local server returns to execute the step that the local server sends the associated data updating request to the local message middleware.
In order to ensure that the associated data request can be delivered to the remote server even after the message middleware receives the associated data request, in this embodiment, the method further includes: the local server side judges whether the local message middleware finishes sending the associated data updating request to the remote server side; if the request is finished, the local server judges whether the local message middleware receives the information which is fed back by the remote server and successfully receives the associated data updating request; if not, the local server returns to execute the step of sending the associated data updating request to the remote server by the local message middleware.
It should be further noted that, in this embodiment, if the associated data is stored in at least two different location servers, the sending of the associated data update request to the different location server storing the associated data specifically includes: and the local server selects one of the remote servers for storing the associated data, and sends the associated data updating request to the selected remote server for storing the associated data. For example, in an electronic bill payment service, the associated data includes a fund data and a balance data of a collection account, which may be stored in different remote servers. Under the condition, the local server can select a remote server storing the deposit, send the electronic bill payment document to the remote server, and call the account application of the remote server storing the balance of the collection account after the remote server completes deduction operation of the deposit, so as to complete increase operation of the balance of the collection account. In this case, the local server may also send the electronic bill payment document to the remote server storing the deposit and the remote server storing the balance of the collection account, and the two remote servers respectively complete the corresponding data updating operations.
In the foregoing embodiment, a method for fast information interaction is provided, and correspondingly, the present application further provides a local server. Fig. 2 is a schematic diagram of an embodiment of a local server according to the present application. Since the apparatus embodiments are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for relevant points. The device embodiments described below are merely illustrative.
A local server in this embodiment is used in any one of the above fast information interaction methods, and includes:
a data update request receiving unit 201, configured to receive a data update request sent by a client;
a data updating unit 202, configured to update, according to the data updating request, corresponding data in the client information stored locally;
an information sending unit 203, configured to generate, according to the data update request, an associated data update request requesting to update associated data related to the data if the data is updated, send the associated data update request to a different-location server storing the associated data, and feed back the data update success information to the client.
Optionally, the generating, according to the data update request, an associated data update request requesting to update associated data related to the data, and sending the associated data update request to a remote server storing the associated data includes:
generating an associated data updating request for requesting to update associated data related to the data according to the data updating request;
judging whether the associated data updating request is generated or not;
if yes, sending the associated data updating request to a remote server storing the associated data;
if not, returning to the step of executing the associated data updating request for generating the associated data which requests to update the associated relation with the data according to the data updating request.
Optionally, the sending the associated data update request to the remote server storing the associated data includes:
sending the associated data updating request to local message middleware;
the local message middleware receives the associated data updating request;
and the local message middleware sends the associated data updating request to the remote server.
Optionally, the method further includes:
a related data update request generation result judgment unit for judging whether the related data update request is generated;
a related data update request receiving result judging unit, configured to receive a judgment result of the related data update request generation result judging unit, and if the judgment result is yes, determine whether the local message middleware receives the related data update request;
and the first returning unit is used for receiving the judgment result of the associated data updating request receiving result judging unit, and if the judgment result is not received, returning to execute the step of sending the associated data updating request to the local message middleware.
Optionally, the method further includes:
a related data updating request sending result judging unit, configured to judge whether the local message middleware completes sending the related data updating request to the remote server;
a remote server side feedback information receiving result judging unit, configured to receive a judgment result of the association data update request sending result judging unit, and if the judgment result is complete, determine whether the local message middleware receives information that the association data update request has been successfully received and is fed back by the remote server side;
and the second returning unit is used for receiving the judgment result of the remote server feedback information receiving result judging unit, and if the judgment result is not received, returning to the step of executing the local message middleware to send the associated data updating request to the remote server.
Optionally, if the associated data is stored in at least two different location servers, the sending of the associated data update request to the different location server storing the associated data specifically includes:
and selecting one of the remote service terminals for storing the associated data, and sending the associated data updating request to the selected remote service terminal for storing the associated data.
Corresponding to the quick information interaction method, the application also provides another quick information interaction method. Please refer to fig. 3, which is a flowchart illustrating an embodiment of another method for fast information interaction according to the present application, wherein the same parts as those in the first embodiment are not repeated, please refer to the corresponding parts in the first embodiment. Another fast information interaction method provided by the present application includes:
step S301: and the remote server side stores the associated data, and receives a data updating request which is generated by the local server side according to the data updating request received from the client side and requests to update the associated data related to the data.
When the local server implementing the above-mentioned fast information interaction method of the present application completes an operation of updating the data requested to be updated stored locally, that is, the data requested to be updated stored locally is updated, it generates an associated data update request requesting to update associated data related to the data according to the data update request received from the client, and sends the associated data update request to a remote server storing the associated data. At this time, the remote server storing the associated data needs to receive a data update request which is generated by the local server according to the data update request received from the client and requests to update the associated data related to the data.
For example, in the payment service, if the electronic bill payment application is deployed at a different service end in different places, where the electronic bill payment application includes an electronic bill application and an accounting application, after the remote deployment, the local service end has the electronic bill application and the accounting application, and the remote service end also has the electronic bill application and the accounting application. And the payer account information is stored in the local server, and the deposit account information and the payee account information are stored in the remote server. Under the condition, when the local server implementing the rapid information interaction method completes the operation of verifying and selling the selected electronic bill, the local server generates an electronic bill payment receipt according to the electronic bill payment request and sends the electronic bill payment receipt to a remote server storing deposit data and collection account balance data. The remote server side needs to receive the information of the electronic bill payment document.
It should be noted that, in this embodiment, the remote server that stores the associated data receives an associated data update request that is generated by the local server according to a data update request received from the client and requests to update the associated data related to the data, specifically, the remote server that stores the associated data receives a message middleware of the remote server that stores the associated data and generates an associated data update request that requests to update the associated data related to the data according to a data update request received by the local server from the client.
Step S302: and the remote server completes the corresponding update operation of the associated data according to the associated data update request.
The remote server receives the associated data request through step S301, and in this step, the remote server needs to complete the corresponding update operation of the associated data according to the associated data update request. For example, in the payment service, after receiving the electronic bill payment receipt at the remote service end, deduction of the deposit and increase of the balance of the collection account need to be completed according to the receipt.
In this embodiment, the remote server completes the corresponding update operation of the associated data according to the associated data update request, and the specific steps include: the remote server receives the associated data updating request sent by the message middleware; the remote server analyzes the associated data updating request to obtain a change value of the associated data; and the remote server side updates the associated data according to the change value of the associated data. If the payer selects an electronic bill with a face value of 5 yuan for payment, the remote server analyzes the electronic bill payment document, the change value of the obtained associated data is 5, the remote server deducts 5 yuan from the deposit account according to the change value, and adds 5 yuan of collection account balance to the payee account.
In order to ensure that after receiving the association data request, the remote server must complete the update operation of the association data, and complete the update operation of the association data only once according to the request, in this embodiment, the method further includes: the remote server side judges whether the updating operation of the associated data is finished or not corresponding to the associated data ID in the associated data updating request; if not, the remote server returns to execute the step of updating the associated data by the remote server according to the change value of the associated data; if so, the operation is ended. For example, in the payment service, after receiving the information of the electronic bill payment document at the remote service end, the remote service end must complete deduction of the deposit and increase of the balance of the collection account, and when any system abnormality is encountered in the process, retry is required to be carried out when the abnormality is processed until the result is obtained; because the electronic ticket has been certified for sale at the local server, the ultimate consistency of electronic ticket certification and asynchronous funds handling must be ensured. And the remote server only needs to successfully perform one-time fund processing aiming at the same electronic bill payment receipt, so that the remote server can perform idempotent control according to the receipt number of the electronic bill payment receipt to ensure the correctness of fund processing.
It should be noted that, in this embodiment, if the associated data is stored in at least two different servers, the different server storing the associated data receives, according to a data update request received from a client, a data update request that is generated by a local server and requests to update the associated data related to the data, and specifically includes: and receiving an associated data updating request of requesting to update the associated data related to the data according to a data updating request received by the local server from a client by the local server through the message middleware of the remote server selected by the local server and storing the associated data. Of course, in other embodiments, if the associated data is stored in at least two of the remote service terminals, the local service terminal may also send associated data requests to different remote service terminals, and the remote service terminals storing the associated data receive the associated data requests.
In this embodiment, the remote server completes the corresponding update operation of the associated data according to the associated data update request, specifically: and the selected allopatric server storing the associated data completes the corresponding updating operation of the associated data according to the associated data updating request.
Correspondingly, in this embodiment, the selected remote server storing the associated data completes the corresponding update operation of the associated data according to the associated data update request, and the specific steps include: the selected allopatric server end storing the associated data receives the associated data updating request sent by the message middleware; the selected allopatric server side storing the associated data analyzes the associated data updating request to obtain a change value of the associated data; the selected allopatric server side for storing the associated data updates the associated data stored locally according to the change value of the associated data; the selected allopatric server side storing the associated data calls an update data function of the unselected allopatric server side storing the associated data according to the associated data update request; and the selected allopatric server storing the associated data updates the associated data which is not updated through the update data function according to the change value of the associated data.
For example, in the payment service, the local server selects to send the electronic bill payment receipt information to the remote server storing the deposit account information, and the message middleware application of the remote server storing the deposit data receives the receipt information and sends the receipt information to the electronic bill application. The electronic bill application of the remote server storing the deposit data receives the payment bill information sent by the message middleware application, and analyzes the payment bill information to obtain payment amount; the electronic bill application of the remote server storing the deposit data calls a local accounting application, and the accounting application deducts the deposit in the deposit account according to the payment amount; and then the electronic bill application of the remote server storing the deposit data calls the account application of the remote server storing the balance data of the collection account, and the account application increases the balance of the collection account in the account of the collection party according to the payment amount.
In the embodiment, another quick information interaction method is provided, and correspondingly, the application also provides a remote server. Please refer to fig. 4, which is a schematic diagram of an embodiment of an offsite server according to the present application. Since the apparatus embodiments are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to some of the descriptions of the method embodiments for relevant points. The device embodiments described below are merely illustrative.
The remote server of this embodiment is used in the another fast information interaction method described above, and includes: an associated data update request receiving unit 401, configured to receive a data update request that is generated by a local server according to a data update request received from a client and requests to update the associated data related to the data; an associated data updating unit 402, configured to complete an updating operation of the associated data according to the associated data updating request.
Optionally, the receiving local server generates, according to the data update request received from the client, an associated data update request for requesting to update the associated data related to the data, specifically:
the message middleware receives a data updating request which is generated by the local server according to the data updating request received from the client and requests to update the associated data which has the associated relationship with the data.
Optionally, the step of completing the corresponding update operation of the associated data according to the associated data update request includes:
the associated data updating request sent by the message middleware is received;
analyzing the associated data updating request to obtain a change value of the associated data;
and updating the associated data according to the change value of the associated data.
Optionally, the method further includes:
an update operation completion result determination unit configured to determine whether an update operation of the associated data is completed, corresponding to the associated data ID in the associated data update request;
and the step returning unit is used for receiving the judgment result of the updating operation completion result judging unit, and if the judgment result is incomplete, returning to the step of executing the change value according to the associated data and updating the associated data.
Optionally, if the associated data is stored in at least two remote servers, the update operation of the associated data is completed according to the associated data update request, and the specific steps include:
receiving the associated data updating request sent by the message middleware;
analyzing the associated data updating request to obtain a change value of the associated data;
updating the associated data stored locally according to the change value of the associated data;
calling an update data function of a remote server storing the non-updated associated data according to the associated data update request;
and updating the associated data which is not updated through the updating data function according to the change value of the associated data.
An embodiment of the present application further provides a rapid information interaction system, as shown in fig. 5, the system includes a client 501, a local server 502 according to the foregoing embodiment, and a remote server 503 according to the foregoing embodiment.
The above embodiments of the method for fast information interaction, the local server, the remote server and the system provided by the present application are introduced in detail, and a specific example is applied in the present application to explain the principle and the implementation manner of the present application, and the description of the above embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, the specific embodiments and the application range may be changed. In view of the above, the description should not be taken as limiting the application.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
1. Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Claims (25)

1. A method for fast information interaction is characterized by comprising the following steps:
the local server receives a data updating request sent by the client;
the local server side updates corresponding data in the client information stored locally according to the data updating request;
if the data is updated, the local server generates an associated data updating request for requesting to update associated data related to the data according to the data updating request, sends the associated data updating request to a remote server storing the associated data, and feeds back successful data updating information to the client.
2. The method according to claim 1, wherein the local server generates an associated data update request requesting to update associated data related to the data according to the data update request, and sends the associated data update request to a remote server storing the associated data, and the specific steps include:
the local server generates an associated data updating request for requesting to update associated data related to the data according to the data updating request;
the local server side judges whether the associated data updating request is generated or not;
if yes, the local server sends the associated data updating request to a remote server storing the associated data;
if not, the local server returns to execute the step of generating an associated data updating request for requesting to update associated data related to the data according to the data updating request by the local server.
3. The method for rapid information interaction according to claim 1 or 2, wherein the step of sending the associated data update request to the remote server storing the associated data comprises the following steps:
the local server side sends the associated data updating request to a local message middleware;
the local message middleware receives the associated data updating request;
and the local message middleware sends the associated data updating request to the remote server.
4. The method for rapid information interaction according to claim 3, further comprising:
the local server judges whether the associated data updating request is generated or not;
if yes, the local server side judges whether the local message middleware receives the associated data updating request;
if not, the local server returns to execute the step that the local server sends the associated data updating request to the local message middleware.
5. The method for rapid information interaction according to claim 4, further comprising:
the local server side judges whether the local message middleware finishes sending the associated data updating request to the remote server side;
if the request is finished, the local server judges whether the local message middleware receives the information which is fed back by the remote server and successfully receives the associated data updating request;
if not, the local server returns to execute the step of sending the associated data updating request to the remote server by the local message middleware.
6. The method according to claim 1, wherein if the associated data is stored in at least two different location servers, the sending of the associated data update request to the different location server storing the associated data specifically comprises:
and the local server selects one of the remote servers for storing the associated data, and sends the associated data updating request to the selected remote server for storing the associated data.
7. A local server for the method of rapid information interaction according to any one of claims 1 to 6, comprising:
the data updating request receiving unit is used for receiving a data updating request sent by a client;
the data updating unit is used for updating corresponding data in the client information stored locally according to the data updating request;
and the information sending unit is used for generating an associated data updating request for requesting to update associated data related to the data according to the data updating request if the data is updated, sending the associated data updating request to a remote server for storing the associated data, and feeding back successful data updating information to the client.
8. The local server according to claim 7, wherein the generating of the associated data update request requesting update of the associated data related to the data according to the data update request, and sending the associated data update request to the remote server storing the associated data, specifically comprises:
generating an associated data updating request for requesting to update associated data related to the data according to the data updating request;
judging whether the associated data updating request is generated or not;
if yes, sending the associated data updating request to a remote server storing the associated data;
if not, returning to the step of executing the associated data updating request for generating the associated data which requests to update the associated relation with the data according to the data updating request.
9. The local server according to claim 7 or 8, wherein the step of sending the associated data update request to the remote server storing the associated data comprises:
sending the associated data updating request to local message middleware;
the local message middleware receives the associated data updating request;
and the local message middleware sends the associated data updating request to the remote server.
10. The local server of claim 9, further comprising:
a related data update request generation result judgment unit for judging whether the related data update request is generated;
a related data update request receiving result judging unit, configured to receive a judgment result of the related data update request generation result judging unit, and if the judgment result is yes, determine whether the local message middleware receives the related data update request;
and the first returning unit is used for receiving the judgment result of the associated data updating request receiving result judging unit, and if the judgment result is not received, returning to execute the step of sending the associated data updating request to the local message middleware.
11. The local server of claim 10, further comprising:
a related data updating request sending result judging unit, configured to judge whether the local message middleware completes sending the related data updating request to the remote server;
a remote server side feedback information receiving result judging unit, configured to receive a judgment result of the association data update request sending result judging unit, and if the judgment result is complete, determine whether the local message middleware receives information that the association data update request has been successfully received and is fed back by the remote server side;
and the second returning unit is used for receiving the judgment result of the remote server feedback information receiving result judging unit, and if the judgment result is not received, returning to the step of executing the local message middleware to send the associated data updating request to the remote server.
12. The local server according to claim 7, wherein if the associated data is stored in at least two of the remote servers, the sending of the associated data update request to the remote server storing the associated data specifically comprises:
and selecting one of the remote service terminals for storing the associated data, and sending the associated data updating request to the selected remote service terminal for storing the associated data.
13. A method for fast information interaction is characterized by comprising the following steps:
the remote server side stores the associated data, and receives a data updating request which is generated by the local server side according to the data updating request received from the client side and requests to update the associated data related to the data;
and the remote server completes the corresponding update operation of the associated data according to the associated data update request.
14. The method according to claim 13, wherein the remote server storing the associated data receives an associated data update request from a local server, which is generated according to a data update request received from a client, requesting to update the associated data related to the data, specifically:
and the message middleware of the remote server storing the associated data receives the associated data updating request of the local server for requesting to update the associated data related to the data according to the data updating request received by the local server from the client.
15. The method for rapid information interaction according to claim 14, wherein the remote server completes the update operation of the associated data according to the associated data update request, and the specific steps include:
the remote server receives the associated data updating request sent by the message middleware;
the remote server analyzes the associated data updating request to obtain a change value of the associated data;
and the remote server side updates the associated data according to the change value of the associated data.
16. The method for rapid information interaction according to any one of claims 13 to 15, further comprising:
the remote server side judges whether the updating operation of the associated data is finished or not corresponding to the associated data ID in the associated data updating request;
if not, the remote server returns to execute the step of updating the associated data by the remote server according to the change value of the associated data.
17. The method according to claim 13, wherein if the associated data is stored in at least two of the remote servers, the remote server storing the associated data receives an associated data update request that a local server generates to update the associated data related to the data according to a data update request received from a client, specifically:
and receiving an associated data updating request of requesting to update the associated data related to the data according to a data updating request received by the local server from a client by the local server through the message middleware of the remote server selected by the local server and storing the associated data.
18. The method for rapid information interaction according to claim 17, wherein the remote server completes the update operation of the associated data according to the associated data update request, specifically:
and the selected allopatric server storing the associated data completes the corresponding updating operation of the associated data according to the associated data updating request.
19. The method according to claim 18, wherein the selected remote server storing the associated data completes the corresponding update operation of the associated data according to the associated data update request, and the specific steps include:
the selected allopatric server end storing the associated data receives the associated data updating request sent by the message middleware;
the selected allopatric server side storing the associated data analyzes the associated data updating request to obtain a change value of the associated data;
the selected allopatric server side for storing the associated data updates the associated data stored locally according to the change value of the associated data;
the selected allopatric server side storing the associated data calls an update data function of the unselected allopatric server side storing the associated data according to the associated data update request;
and the selected allopatric server storing the associated data updates the associated data which is not updated through the update data function according to the change value of the associated data.
20. An off-site server for the method of rapid information interaction according to any one of claims 13 to 19, comprising:
the associated data updating request receiving unit is used for receiving an associated data updating request of a local server for generating a request for updating the associated data related to the data according to a data updating request received by the local server from a client;
and the associated data updating unit is used for finishing the corresponding updating operation of the associated data according to the associated data updating request.
21. The remote server according to claim 20, wherein the receiving local server generates an associated data update request for requesting to update the associated data related to the data according to a data update request received from a client, specifically:
the message middleware receives a data updating request which is generated by the local server according to the data updating request received from the client and requests to update the associated data which has the associated relationship with the data.
22. The remote server according to claim 21, wherein the step of completing the corresponding associated data update operation according to the associated data update request comprises:
receiving the associated data updating request sent by the message middleware;
analyzing the associated data updating request to obtain a change value of the associated data;
and updating the associated data according to the change value of the associated data.
23. The off-site server of any of claims 20 to 22, further comprising:
an update operation completion result determination unit configured to determine whether an update operation of the associated data is completed, corresponding to the associated data ID in the associated data update request;
and the step returning unit is used for receiving the judgment result of the updating operation completion result judging unit, and if the judgment result is incomplete, returning to the step of executing the change value according to the associated data and updating the associated data.
24. The remote server according to claim 20, wherein if the associated data is stored in at least two of the remote servers, the step of completing the corresponding associated data update operation according to the associated data update request comprises:
receiving the associated data updating request sent by message middleware;
analyzing the associated data updating request to obtain a change value of the associated data;
updating the associated data stored locally according to the change value of the associated data;
calling an update data function of a remote server storing the non-updated associated data according to the associated data update request;
and updating the associated data which is not updated through the updating data function according to the change value of the associated data.
25. A rapid information interaction system, comprising: a client, a local server as claimed in any one of claims 7 to 12 and an off-site server as claimed in any one of claims 20 to 24.
CN201510112072.XA 2015-03-13 2015-03-13 Rapid information interaction method, local server, remote server and system Active CN106034148B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510112072.XA CN106034148B (en) 2015-03-13 2015-03-13 Rapid information interaction method, local server, remote server and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510112072.XA CN106034148B (en) 2015-03-13 2015-03-13 Rapid information interaction method, local server, remote server and system

Publications (2)

Publication Number Publication Date
CN106034148A CN106034148A (en) 2016-10-19
CN106034148B true CN106034148B (en) 2019-12-31

Family

ID=57150667

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510112072.XA Active CN106034148B (en) 2015-03-13 2015-03-13 Rapid information interaction method, local server, remote server and system

Country Status (1)

Country Link
CN (1) CN106034148B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108597160B (en) * 2018-04-13 2019-09-06 北京三快在线科技有限公司 A kind of method, apparatus and system managing order information
CN109783534A (en) * 2018-12-25 2019-05-21 浙江口碑网络技术有限公司 The processing method and processing device of statistical data evaluates the processing method and processing device of data

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101907998A (en) * 2010-08-17 2010-12-08 中兴通讯股份有限公司 Update system and method of embedded systems
CN102054204A (en) * 2009-11-09 2011-05-11 阿里巴巴集团控股有限公司 Method, system and device for automatically booking ticket
CN102387204A (en) * 2011-10-21 2012-03-21 中国科学院计算技术研究所 Method and system for maintaining consistency of cluster caching
CN103188140A (en) * 2011-12-31 2013-07-03 国民技术股份有限公司 Service request processing system
CN103812849A (en) * 2012-11-15 2014-05-21 腾讯科技(深圳)有限公司 Local cache updating method and system, client and server

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102054204A (en) * 2009-11-09 2011-05-11 阿里巴巴集团控股有限公司 Method, system and device for automatically booking ticket
CN101907998A (en) * 2010-08-17 2010-12-08 中兴通讯股份有限公司 Update system and method of embedded systems
CN102387204A (en) * 2011-10-21 2012-03-21 中国科学院计算技术研究所 Method and system for maintaining consistency of cluster caching
CN103188140A (en) * 2011-12-31 2013-07-03 国民技术股份有限公司 Service request processing system
CN103812849A (en) * 2012-11-15 2014-05-21 腾讯科技(深圳)有限公司 Local cache updating method and system, client and server

Also Published As

Publication number Publication date
CN106034148A (en) 2016-10-19

Similar Documents

Publication Publication Date Title
JP6490071B2 (en) Launching a client application based on a message
CN105099688A (en) Operation method for electronic account, display method and apparatus for payment page
CN107038560B (en) System, method and device for executing payment service
US20210081910A1 (en) Systems, methods and apparatus for variable settlement accounts
CN105335847A (en) Operation method and device of electronic account
CN107070858B (en) Service processing method and device
JP2018500681A (en) Transaction information processing method and apparatus
CN108446905B (en) Payment method and device and electronic equipment
CN106034148B (en) Rapid information interaction method, local server, remote server and system
CN107392582B (en) Method and device for realizing resource transfer and method and device for realizing collection and payment
US20190045029A1 (en) Service processing method and device
CN110599330A (en) Bank universal anti-transaction device, method and system
EP3306544A1 (en) Proxy payment device and operation method therefor
US9232388B2 (en) Initiation of wireless service
CN110310196A (en) Product demand application method, device, computer equipment and storage medium
CN111415146A (en) Resource data processing method, device and equipment
CN111222869A (en) Transaction data processing method, device, computer equipment and medium
CN112950355A (en) Transaction data processing method and device
CN113822676A (en) Repeated payment control method and device for aggregated payment cashier desk
CN113988844A (en) Service subscription method, device and system
CN111178858A (en) Transaction data processing method, device, equipment and storage medium
CN113822661A (en) Payment method, device and system
CN112184248A (en) Card organization payment refusal bill data processing method and device
CN112163946A (en) Accounting processing method and device based on distributed transaction system
CN111415245A (en) Account opening method and device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20200918

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.

Effective date of registration: 20200918

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