CN115378801B - Multi-server communication method and terminal - Google Patents
Multi-server communication method and terminal Download PDFInfo
- Publication number
- CN115378801B CN115378801B CN202210954092.1A CN202210954092A CN115378801B CN 115378801 B CN115378801 B CN 115378801B CN 202210954092 A CN202210954092 A CN 202210954092A CN 115378801 B CN115378801 B CN 115378801B
- Authority
- CN
- China
- Prior art keywords
- server
- request data
- business process
- business
- fault
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 100
- 230000006854 communication Effects 0.000 title claims abstract description 31
- 238000004891 communication Methods 0.000 title claims abstract description 30
- 238000012545 processing Methods 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims description 8
- 230000003993 interaction Effects 0.000 abstract description 7
- 238000012795 verification Methods 0.000 description 21
- 230000002452 interceptive effect Effects 0.000 description 4
- 241001122767 Theaceae Species 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000011835 investigation Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses a communication method and a terminal of multiple servers, wherein a first server and a second server are configured to jointly receive target request data sent by a client; judging whether a fault query request is received, if yes, acquiring first request data stored in the first server; and obtaining a fault positioning result according to the comparison result of the first request data and the target request data. According to the invention, when the client needs to interact with the servers, the interaction request is sent to different servers, and when one server does not receive the interaction request, the problem is caused when the client sends the interaction request or when the server receives the interaction request is solved, so that the fault finding efficiency is improved, the fault can be located only by calling the record of the server, and the operation is simple and not complicated.
Description
Technical Field
The present invention relates to the field of data communications, and in particular, to a multi-server communication method and a terminal.
Background
In the existing architecture, the terminal equipment generally only establishes a data interaction relation with one server, so that in the communication process of the terminal equipment, even if a server cluster is set in the background, only one server is actually docked with the terminal, and therefore when the data cannot be transmitted due to the problem of connection, a problem generating party cannot be quickly positioned as the server or the terminal equipment, the fault party can be determined by carrying out interaction test again, and an engineer is also required to test the place where the server is located, so that the fault positioning process is complicated.
Disclosure of Invention
The technical problems to be solved by the invention are as follows: the passing method and system for the multiple servers are provided, and quick positioning of communication faults is achieved.
In order to solve the technical problems, the invention adopts a technical scheme that:
a multi-server communication method, comprising the steps of:
configuring a first server and a second server to jointly receive target request data sent by a client;
judging whether a fault query request is received, if yes, acquiring first request data stored in the first server;
and obtaining a fault positioning result according to the comparison result of the first request data and the target request data.
In order to solve the technical problems, the invention adopts another technical scheme that:
a multi-server communication terminal comprising a memory, a processor and a computer program stored in the memory and executed on the processor; when the processor executes the computer program, the implementation steps are as follows:
configuring a first server and a second server to jointly receive target request data sent by a client;
judging whether a fault query request is received, if yes, acquiring first request data stored in the first server;
and obtaining a fault positioning result according to the comparison result of the first request data and the target request data.
The invention has the beneficial effects that: when a client sends target request data, the target request data are sent to a plurality of servers at the same time, the plurality of servers store each target request data sent by the client, if the target request data sent by the client do not receive a reply of a processing result, all request data in one of the servers can be acquired nearby through a geographic position, and if the target request data do not exist in the server, the probability of the client failure is high; if the target request data exists in the server, the client side is successfully sent but is not processed, and the server responsible for processing the target request data has high probability of faults, so that the faults are rapidly positioned.
Drawings
FIG. 1 is a flow chart of steps of a multi-server communication method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a multi-server communication terminal according to an embodiment of the present invention;
description of the reference numerals:
1. a multi-server communication terminal; 2. a processor; 3. a memory.
Detailed Description
In order to describe the technical contents, the achieved objects and effects of the present invention in detail, the following description will be made with reference to the embodiments in conjunction with the accompanying drawings.
Referring to fig. 1, a multi-server communication method includes the steps of:
configuring a first server and a second server to jointly receive target request data sent by a client;
judging whether a fault query request is received, if yes, acquiring first request data stored in the first server;
and obtaining a fault positioning result according to the comparison result of the first request data and the target request data.
From the above description, the beneficial effects of the invention are as follows: when a client sends target request data, the target request data are sent to a plurality of servers at the same time, the plurality of servers store each target request data sent by the client, if the target request data sent by the client do not receive a reply of a processing result, all request data in one of the servers can be acquired nearby through a geographic position, and if the target request data do not exist in the server, the probability of the client failure is high; if the target request data exists in the server, the client side is successfully sent but is not processed, and the server responsible for processing the target request data has high probability of faults, so that the faults are rapidly positioned.
Further, before the first server and the second server are configured to jointly receive the target request data sent by the client, the method includes:
the first server is configured to process a first business process, and the second server is configured to process a second business process;
the first business process and the second business process are not overlapped with each other;
the configuration of the first server and the second server to jointly receive the target request data sent by the client comprises the following steps:
configuring the first server to judge whether the target request data is suitable for the first business process, if so, processing the target request data;
and configuring the second server to judge whether the target request data is suitable for the second business flow, and if so, processing the target request data.
As can be seen from the above description, configuring the first server and the second server to process different service flows can shunt the request data of the user, avoid stacking the request data, and avoid collision of the processing results of the request data, further improve the processing efficiency of the request data.
Further, configuring the first server to process a first business process, and the second server to process a second business process includes:
storing the first business process and the second business process, and a first business rule corresponding to the first business process and a second business rule corresponding to the second business process in the first server and the second server;
the state of the first business process is set to be on-line by the first server, the state of the second business process is set to be off-line by the second server, the state of the second business process is set to be on-line by the second server, and the state of the first business process is set to be off-line by the second server.
As can be seen from the above description, when configuring the service flows, the complete service flows are stored in different servers, and only the different service flows are online in different servers, so that after the server fails, the service flow of the failed server can be online in the normal server, and the client can be continuously provided with service, thereby realizing the noninductivity of the client after the failure.
Further, the obtaining the fault location result according to the comparison result of the first request data and the target request data includes:
judging whether the target request data exists in the first request data, if so, sending a server fault report;
otherwise, sending a client failure report.
From the above description, according to the relationship between the first request data and the target request data, the occurrence position of the fault can be primarily judged, and the efficiency of fault positioning is improved.
Further, if so, sending a server failure report includes:
if yes, second request data stored in the second server are obtained, and a server fault report is sent according to a comparison result of the second request data and the target request data.
As can be seen from the above description, if the first request data and the target request data are identical, the second request data is further obtained and compared with the target request data, so that more accurate fault location can be further obtained, for example, the second request data includes the target request data to indicate the processing fault of the second server, and if the second request does not include the target request data to indicate the channel fault between the second server and the client.
Further, the method further comprises the following steps:
receiving a synchronization request;
acquiring first business data generated by the first business process processed by the first server and second business data generated by the second business process processed by the second server;
synchronizing the first service data to the second server; and synchronizing the second service data to the first server.
As can be seen from the above description, when the service data generated by processing the request data by different servers are synchronized, other servers can continue to process the request data without occurrence of a gear break when there is a server failure.
Further, the method further comprises the following steps:
and after receiving a fault processing completion signal, synchronizing the first request data and the second request data.
As can be seen from the above description, after the fault is detected, the request data in different servers are synchronized, so as to ensure the accuracy of the next fault detection.
Further, judging whether a downtime signal of the first server is received, if yes, setting the state of the first business process to be on-line at the second server;
judging whether a downtime signal of a second server is received, if yes, setting the state of the second business flow to be on-line at the first server.
As can be seen from the above description, when the server is down, the same business processes are arranged on the server when the business processes are arranged, so that the business processes can be mutually taken over, the down of the whole system is avoided, and the whole system can also provide service for clients.
Further, the first server is disposed locally and the second server is disposed remotely.
As can be seen from the above description, the first server is arranged locally, and after receiving the fault inquiry request, the first server can directly acquire data from the local and locate the fault first without remote running for investigation.
Referring to fig. 2, a multi-server communication terminal includes a memory, a processor, and a computer program stored in the memory and executed on the processor; the steps in the multi-server communication method described above are implemented when the processor executes the computer program.
The communication method and the terminal of the multiple servers can be applied to a scene where communication with the servers is required, and the following description is made by specific embodiments:
referring to fig. 1, a first embodiment of the present invention is as follows:
a multi-server communication method, comprising the steps of:
s0, configuring the first server to process a first business process, and configuring the second server to process a second business process; the first business process and the second business process are not overlapped with each other;
the method specifically comprises the following steps: storing the first business process and the second business process, and a first business rule corresponding to the first business process and a second business rule corresponding to the second business process in the first server and the second server; setting the state of the first business process as on-line at the first server, setting the state of the second business process as off-line at the second server, setting the state of the second business process as on-line at the second server, and setting the state of the first business process as off-line;
s1, configuring a first server and a second server to jointly receive target request data sent by a client, wherein the method comprises the following steps:
s11, configuring the first server to judge whether the target request data is suitable for the first business process, and if yes, processing the target request data; configuring the second server to judge whether the target request data is suitable for the second business process, if so, processing the target request data;
s12, receiving a synchronous request, and acquiring first service data generated by the first service flow processed by the first server and second service data generated by the second service flow processed by the second server; synchronizing the first service data to the second server; synchronizing the second service data to the first server;
s2, judging whether a fault query request is received, if yes, acquiring first request data stored in the first server and second request data stored in the second server;
s3, obtaining a fault positioning result according to the comparison result of the first request data and the target request data, wherein the fault positioning result comprises the following steps:
s31, judging whether the target request data exists in the first request data, if so, executing S32; otherwise, sending a client side fault report;
in an alternative embodiment, the client failure comprises a network failure;
s32, acquiring second request data stored in the second server, and sending a server fault report according to a comparison result of the second request data and the target request data;
s33, after receiving a fault processing completion signal, synchronizing the first request data and the second request data;
in an alternative embodiment, the method further comprises the step of: judging whether a first server downtime signal is received, if yes, setting the state of the first business flow to be on line at the second server; judging whether a second server downtime signal is received, if yes, setting the state of the second business flow to be on line at the first server;
in an alternative embodiment, the first server is remotely located and the second server is locally located, so that the fault condition can be known only by looking at the local server;
in summary, the application is provided with two servers, labeled as a first server and a second server, in which the same service is stored, but in reality the online service is different; the method comprises the steps that communication data of a client and a server, such as request data of a request service, are simultaneously sent to two servers, the two servers judge whether to process the request data according to rules corresponding to the service on line, if the corresponding rules are not met, the request data are only saved, and if the corresponding rules are met, the request data are processed and processing results are saved; when the condition that the request data of the user does not have server response occurs, the fault position can be roughly judged by acquiring the request data stored in the other server; for example, the request data sent by the user and processed by the first server is not processed, at this time, whether the request data is received in the second server is acquired, if so, it is indicated that the data sending channel of the client is normal, and the data receiving channel of the first server may be abnormal; if the request data is not received in the second server, the data transmission channel of the client side is indicated to be possibly abnormal, and if the first server is located in a different place, the fault condition can be confirmed without going to the site; the two servers can also synchronize data at regular time to realize mutual backup of data, and meanwhile, under the condition that one server is down, the other server can temporarily access related services, so as to realize service taking over and avoid data accumulation of a user request.
The second embodiment of the invention is as follows:
the multi-server communication method is applied to the actual scene:
s1, a first server and a second server jointly receive a transaction request sent by a client; the client sends a transaction request to a first server and a second server respectively; the first server processes the transaction request, and the second server only stores the transaction request;
in an alternative embodiment, where the transaction request includes card/ticket information and a client identification, the processing of the transaction request by the first server includes: acquiring card/ticket issuing conditions according to the card/ticket information; judging whether the client side identifier meets the card/ticket issuing condition, if so, sending the card/ticket identifier to the client side;
s2, the first server and the second server jointly receive verification requests sent by the client, namely the client respectively sends the verification requests to the first server and the second server; the first server processes the cancellation request, and the second server only stores the cancellation request;
in an alternative embodiment, the verification request includes the card/ticket identification and current customer information; the first server processing the cancellation request includes: acquiring a card/ticket use condition corresponding to the card/ticket identifier; judging whether the current customer information is matched with the card/ticket using conditions, if so, verifying and selling the card/ticket corresponding to the card/ticket identifier;
s3, the first server judges whether a verification request is received or not, if yes, S4 is executed, and if not, S5 is executed;
s4, the first server executes the verification request according to the transaction request;
s5, the second server judges whether a verification request is received or not, a judging result is obtained, and a fault positioning result is obtained according to the judging result; specifically, if the judging result is that the verification request is not received, the fault locating result is a client fault; if the judging result is that the verification request is received, the fault locating result is a first server fault;
in an alternative embodiment, the first server receives the transaction request and the verification request sent by the client through the first port; the second server receives a transaction request and a verification request sent by the client through a second port;
in an alternative embodiment, the first server is remotely located and the second server is locally located;
in an alternative embodiment, the first server is a service logic server, and the second server is an internet of things server.
The third embodiment of the invention is as follows:
a multi-server communication method is used in the actual scenario, which is the scenario of sharing a tea room (i.e. the time of online purchase of a tea room, offline use of a tea room by code scanning):
s1, a first server and a second server jointly receive a transaction request sent by a client; the first server receives the transaction request and sends a door opening code to the client according to the transaction request, the second server stores the transaction request, and the door opening code can be one-dimensional code, two-dimensional code, dynamic password and other data capable of uniquely identifying the transaction.
S2, the first server and the second server jointly receive verification requests sent by the client, namely the client respectively sends the verification requests to the first server and the second server; in this embodiment, the verification request includes a feature value and current client information included in the door opening code, and the first server determines whether the door opening condition is satisfied, if yes, whether the verification is required in the purchased time period, whether the verification is used by the user, and the like;
s3, the first server judges whether a verification request is received or not, if yes, S4 is executed, and if not, S5 is executed; in this embodiment, if the user cannot successfully open the door and does not receive the feedback information (if the door cannot be opened without meeting the door opening condition, the corresponding feedback information is sent), S5 is executed;
s4, the first server executes the verification request according to the transaction request;
s5, the second server judges whether a verification request is received or not, a judging result is obtained, and a fault positioning result is obtained according to the judging result; specifically, if the judging result is that the verification request is not received, the fault locating result is a client fault; if the judging result is that the verification request is received, the fault locating result is a first server fault;
in an alternative embodiment, the second server may be located at a location closer to the technician than the headquarter, and the first server may be located remotely, such as in a chain of stores in other areas, so that the fault location may be initially identified without troubleshooting the chain of stores outside the area, and processing efficiency may be improved.
Referring to fig. 2, a third embodiment of the present invention is as follows:
a multi-server communication terminal 1 comprising a memory 3, a processor 2 and a computer program stored in said memory 3 and executed on said processor 2; the processor 2, when executing the computer program, implements the steps of either embodiment one or embodiment two.
In summary, the present invention provides a multi-server communication method and terminal, when a client communicates with a server, interactive data is sent to a plurality of servers, and only one of the servers processes the interactive data, when an abnormal situation occurs, interactive data receiving conditions of other servers except the server that processes the interactive data are called, and a fault is located according to the conditions, so that whether the fault occurs at a data request end (client) or a data receiving end (server) can be quickly obtained, in a scene of online purchase and offline verification, the problem of quick location can be quickly solved, offline use experience of a user is improved, and at ordinary times, no interaction is performed between the servers, thereby saving cost of data processing.
The foregoing description is only illustrative of the present invention and is not intended to limit the scope of the invention, and all equivalent changes made by the specification and drawings of the present invention, or direct or indirect application in the relevant art, are included in the scope of the present invention.
Claims (9)
1. A method of multi-server communication, comprising the steps of:
configuring a first server and a second server to jointly receive target request data sent by a client;
judging whether a fault query request is received, if yes, acquiring first request data stored in the first server;
obtaining a fault positioning result according to the comparison result of the first request data and the target request data;
the obtaining the fault locating result according to the comparison result of the first request data and the target request data includes:
judging whether the target request data exists in the first request data, if so, sending a server fault report;
otherwise, sending a client failure report.
2. The method for multi-server communication according to claim 1, wherein before configuring the first server and the second server to jointly receive the target request data sent by the client, the method comprises:
the first server is configured to process a first business process, and the second server is configured to process a second business process;
the first business process and the second business process are not overlapped with each other;
the configuration of the first server and the second server to jointly receive the target request data sent by the client comprises the following steps:
configuring the first server to judge whether the target request data is suitable for the first business process, if so, processing the target request data;
and configuring the second server to judge whether the target request data is suitable for the second business flow, and if so, processing the target request data.
3. The method of claim 2, wherein configuring the first server to handle a first business process, and wherein configuring the second server to handle a second business process comprises:
storing the first business process and the second business process, and a first business rule corresponding to the first business process and a second business rule corresponding to the second business process in the first server and the second server;
the state of the first business process is set to be on-line by the first server, the state of the second business process is set to be off-line by the second server, the state of the second business process is set to be on-line by the second server, and the state of the first business process is set to be off-line by the second server.
4. The method of claim 1, wherein if yes, sending a server failure report comprises:
if yes, second request data stored in the second server are obtained, and a server fault report is sent according to a comparison result of the second request data and the target request data.
5. The multi-server communication method according to claim 2, further comprising:
receiving a synchronization request;
acquiring first business data generated by the first business process processed by the first server and second business data generated by the second business process processed by the second server;
synchronizing the first service data to the second server; and synchronizing the second service data to the first server.
6. The multi-server communication method of claim 4, further comprising:
and after receiving a fault processing completion signal, synchronizing the first request data and the second request data.
7. A multi-server communication method according to claim 3, further comprising:
judging whether a first server downtime signal is received, if yes, setting the state of the first business flow to be on line at the second server;
judging whether a downtime signal of a second server is received, if yes, setting the state of the second business flow to be on-line at the first server.
8. A method of multi-server communication according to claim 1, wherein the first server is remotely located and the second server is locally located.
9. A multi-server communication terminal comprising a memory, a processor and a computer program stored in the memory and executed on the processor; the method according to any of claims 1-8, characterized in that said processor, when executing said computer program, implements a multi-server communication method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210954092.1A CN115378801B (en) | 2022-08-10 | 2022-08-10 | Multi-server communication method and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210954092.1A CN115378801B (en) | 2022-08-10 | 2022-08-10 | Multi-server communication method and terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115378801A CN115378801A (en) | 2022-11-22 |
| CN115378801B true CN115378801B (en) | 2024-01-30 |
Family
ID=84063542
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210954092.1A Active CN115378801B (en) | 2022-08-10 | 2022-08-10 | Multi-server communication method and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115378801B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH09293059A (en) * | 1996-04-25 | 1997-11-11 | Hitachi Ltd | Decentralized system and its operation management method |
| CN102790801A (en) * | 2012-06-20 | 2012-11-21 | 浪潮(北京)电子信息产业有限公司 | Asynchronous remote copy system and method for maintaining data consistency thereof |
| CN106856599A (en) * | 2015-12-09 | 2017-06-16 | 中国移动通信集团广西有限公司 | Terminal, detection service device, short message receiving-transmitting fault detection method and system |
| CN109120432A (en) * | 2018-07-18 | 2019-01-01 | 北京奇艺世纪科技有限公司 | A kind of failed server localization method and device |
| CN110933160A (en) * | 2019-11-27 | 2020-03-27 | 北京字节跳动网络技术有限公司 | Data access method, server, terminal and storage medium |
| WO2020150944A1 (en) * | 2019-01-24 | 2020-07-30 | 福建联迪商用设备有限公司 | Service processing method and system |
| CN111786807A (en) * | 2019-12-18 | 2020-10-16 | 北京沃东天骏信息技术有限公司 | Fault prompting system, method, device and storage medium |
| CN113515369A (en) * | 2021-04-23 | 2021-10-19 | 深圳希施玛数据科技有限公司 | Data processing method, system, terminal and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111263386A (en) * | 2020-02-10 | 2020-06-09 | 北京小米移动软件有限公司 | Method, device and medium for processing terminal internet access abnormity |
-
2022
- 2022-08-10 CN CN202210954092.1A patent/CN115378801B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH09293059A (en) * | 1996-04-25 | 1997-11-11 | Hitachi Ltd | Decentralized system and its operation management method |
| CN102790801A (en) * | 2012-06-20 | 2012-11-21 | 浪潮(北京)电子信息产业有限公司 | Asynchronous remote copy system and method for maintaining data consistency thereof |
| CN106856599A (en) * | 2015-12-09 | 2017-06-16 | 中国移动通信集团广西有限公司 | Terminal, detection service device, short message receiving-transmitting fault detection method and system |
| CN109120432A (en) * | 2018-07-18 | 2019-01-01 | 北京奇艺世纪科技有限公司 | A kind of failed server localization method and device |
| WO2020150944A1 (en) * | 2019-01-24 | 2020-07-30 | 福建联迪商用设备有限公司 | Service processing method and system |
| CN110933160A (en) * | 2019-11-27 | 2020-03-27 | 北京字节跳动网络技术有限公司 | Data access method, server, terminal and storage medium |
| CN111786807A (en) * | 2019-12-18 | 2020-10-16 | 北京沃东天骏信息技术有限公司 | Fault prompting system, method, device and storage medium |
| CN113515369A (en) * | 2021-04-23 | 2021-10-19 | 深圳希施玛数据科技有限公司 | Data processing method, system, terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115378801A (en) | 2022-11-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108470298B (en) | Method, device and system for transferring resource numerical value | |
| CN101141301B (en) | Method and apparatus for transaction recovery | |
| US9219660B2 (en) | Self-service terminal | |
| US20060174012A1 (en) | Relay method, relay apparatus, and computer product | |
| EP3118804B1 (en) | Self-service terminal service emergency method and site server | |
| CN110969417A (en) | Government affair item synchronization method, device, system, computer equipment and storage medium | |
| CN112446786A (en) | Abnormal transaction processing method and device, electronic equipment and readable storage medium | |
| US9059908B2 (en) | Method and system for facilitating non-interruptive transactions | |
| CN110765430A (en) | Bank data processing system | |
| CN115378801B (en) | Multi-server communication method and terminal | |
| CN112350990A (en) | Off-line data synchronization method for third-party internet retail cashier system | |
| CN114172821B (en) | Service state synchronization method and device and server | |
| US20070233724A1 (en) | Computer-readable recording medium recorded with performance information collection program, and performance information collection apparatus and method | |
| CN114051059B (en) | IDC transaction cross-domain decision method of remote double-activity system | |
| CN113157615B (en) | Service bus communication method, electronic equipment and computer storage medium | |
| CN113448931B (en) | Data processing method, business transaction platform and business providing platform | |
| CN109684353B (en) | Numerical value transfer request processing method, device, server and storage medium | |
| CN113891263B (en) | Short message service system and synchronous sending method and asynchronous sending method thereof | |
| CN109688198B (en) | Distributed system and fault detection method | |
| CN110266720B (en) | Optimization working method for online management server asset data | |
| CN111327573B (en) | Device and method for maintaining log-in state record to transfer data | |
| CN117173840A (en) | Self-service terminal state reporting method, system, device and storage medium | |
| Kulkarni et al. | Secured and effective approach for remote monitoring of large network of heterogeneous ATMs | |
| CN118101519A (en) | Network connectivity verification method, device, equipment and readable storage medium | |
| CN112115032A (en) | Log generation method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |