CN110430256B - Method, device and computer system for pushing transaction message - Google Patents
Method, device and computer system for pushing transaction message Download PDFInfo
- Publication number
- CN110430256B CN110430256B CN201910706793.1A CN201910706793A CN110430256B CN 110430256 B CN110430256 B CN 110430256B CN 201910706793 A CN201910706793 A CN 201910706793A CN 110430256 B CN110430256 B CN 110430256B
- Authority
- CN
- China
- Prior art keywords
- transaction
- information
- transaction processing
- message
- key information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Development Economics (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
The present disclosure provides a method for pushing a transaction message, which includes: acquiring a transaction request; executing transaction processing corresponding to the transaction request; acquiring key information related to the transaction processing, and storing the key information into a sharing area; when the transaction processing is finished, acquiring result information of the transaction processing, and storing the result information into the sharing area; and generating a transaction message based on the key information and the result information in the sharing area, and pushing the transaction message to a client related to the transaction processing. The disclosure also provides a device and a computer system for pushing the transaction message.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a computer system for pushing a transaction message.
Background
At present, two modes of on-line real-time sending one by one or batch timing sending are generally adopted for the transaction message of transaction processing in a bank system. The online real-time one-by-one transmission is realized, a communication protocol needs to be established for each transaction, the system overhead is high, different data packets need to be established in the system for different transaction messages, and the expansibility is poor. The messages to be sent accumulated in a period of time are required to be packaged and sent to the front-end system at intervals, the messages to be sent are sent one by one after the front-end system is unpacked, and timeliness is poor.
Disclosure of Invention
One aspect of the present disclosure provides a method for pushing a transaction message, including: a transaction request is obtained. And on the one hand, executing transaction processing corresponding to the transaction request, on the other hand, acquiring key information related to the transaction processing, storing the key information into a sharing area, and when the transaction processing is completed, acquiring result information of the transaction processing, and storing the result information into the sharing area. And then generating a transaction message based on the key information and the result information in the sharing area, and pushing the transaction message to a client related to transaction processing.
Optionally, the key information related to transaction processing includes at least one of the following: the system comprises transaction initiator information, transaction receiver information, transaction content information, transaction additional information and auxiliary push information.
Optionally, the result information of the transaction processing includes: an outcome identification for characterizing success or failure of the transaction process.
Optionally, the process of executing the transaction processing corresponding to the transaction request and the process of acquiring the key information related to the transaction processing are executed asynchronously.
Optionally, the acquiring key information related to the transaction processing includes: obtaining static information corresponding to the transaction request before the transaction process is performed. And in the transaction processing execution process, responding to an event for calling a specified interface to generate dynamic information, and acquiring the dynamic information. The static information and/or the dynamic information is then used as the key information.
Optionally, the generating a transaction message based on the key information and the result information in the shared area includes: and constructing a message material packet based on the key information and the result information in the sharing area. And retrieving a message template for a client associated with the transaction processing. And then assembling the message material packet based on the message template to obtain the transaction message.
Optionally, the method further includes: and returning a transaction receipt to a source party of the transaction request while generating a transaction message based on the key information and the result information in the shared area.
Optionally, the method further includes: after obtaining the transaction request, performing security detection on the transaction request. The executing of the transaction process corresponding to the transaction request includes: and executing transaction processing corresponding to the transaction request when the detection result of the safety detection is safety.
Another aspect of the present disclosure provides an apparatus for pushing a transaction message, including: the system comprises a request acquisition module, a transaction processing module, a first information sharing module, a second information sharing module and a message pushing module. The request acquisition module is used for acquiring a transaction request. The transaction processing module is used for executing transaction processing corresponding to the transaction request. The first information sharing module is used for acquiring key information related to the transaction processing and storing the key information into a sharing area. And the second information sharing module is used for acquiring result information of the transaction processing and storing the result information into the sharing area when the transaction processing is finished. The message pushing module is used for generating a transaction message based on the key information and the result information in the sharing area and pushing the transaction message to a client related to the transaction processing.
Another aspect of the present disclosure provides a computer system comprising: memory, a processor and a computer program stored on the memory and executable on the processor for implementing the method as described above when the processor executes the computer program.
Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.
According to the embodiment of the disclosure, after receiving a transaction request, on one hand, corresponding transaction processing is performed, and on the other hand, key information and result information related to the transaction processing are placed in the sharing area, so that fragments capable of forming a transaction message are separately and independently stored in the sharing area from a transaction processing process. After the transaction processing process is completed, the segments in the shared area can be directly formed into a transaction message and pushed to the corresponding client, and the expansibility and the timeliness of the transaction message are considered.
Drawings
For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
fig. 1 schematically illustrates an exemplary system architecture of a method and apparatus for applying a push transaction message according to an embodiment of the present disclosure;
fig. 2 schematically shows a flow chart of a method of pushing a transaction message according to an embodiment of the present disclosure;
fig. 3 schematically illustrates an example schematic diagram of a process of pushing a transaction message according to an embodiment of the disclosure;
fig. 4 schematically illustrates a block diagram of an apparatus for pushing a transaction message according to an embodiment of the present disclosure; and
fig. 5 schematically illustrates a block diagram of a computer system suitable for implementing a method of pushing a transaction message according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
The embodiment of the disclosure provides a method, a device and a computer system for pushing a transaction message. The method comprises a request acquisition process, a transaction processing process, a first information sharing process, a second information sharing process and a message pushing process. The transaction request is obtained in a request obtaining process. And then entering a transaction processing process on one hand to execute transaction processing corresponding to the transaction request. On the other hand, the first information sharing process and the second information sharing process are performed, key information related to the transaction processing is acquired and stored in the sharing area, and when the transaction processing is completed, result information of the transaction processing is acquired and stored in the sharing area. And finally, performing a message pushing process, generating a transaction message based on the key information and the result information in the shared area, and pushing the transaction message to a client related to transaction processing.
Fig. 1 schematically illustrates an exemplary system architecture 100 to which the methods and apparatus for push transaction message messaging may be applied, according to an embodiment of the disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, the system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The terminal devices 101, 102, 103 may have various client applications installed thereon, such as a bank-like application, a shopping-like application, a search-like application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only). The terminal devices 101, 102, 103 may interact with the server 105 through the above various client applications to send various requests to the server 105 or to receive results returned by the server 105.
The terminal devices 101, 102, 103 may be various electronic devices including, but not limited to, smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a background management server (for example only) that provides various service support. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the method for pushing a transaction message provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the apparatus for pushing transaction message provided by the embodiments of the present disclosure may be generally disposed in the server 105. The method for pushing the transaction message provided by the embodiment of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Correspondingly, the device for pushing the transaction message provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired.
Fig. 2 schematically shows a flow chart of a method of pushing a transaction message according to an embodiment of the present disclosure.
As shown in fig. 2, the method may include the following operations S201 to S205.
In operation S201, a transaction request is acquired.
The transaction request may be, for example, a payment transaction request, a transfer transaction request, a deposit transaction request, a withdrawal transaction request, and other various types of transaction requests, which are not limited herein, and the transaction request may be from a client of a transaction initiator or from a client of an agent of the transaction request, which is not limited herein.
In operation S202, a transaction process corresponding to the transaction request is performed.
Therein, a transaction process is performed, illustratively if the transaction request is a payment transaction request, transferring an amount of the transaction amount from an account of the payer to an account of the payee. If the transaction request is a transfer transaction request, a transaction process is performed that transfers an amount of the transaction amount from the account of the transferring party to the account of the transferred party. Similarly, the transaction processing of other types of transaction requests is the processing procedure for achieving the purpose of the transaction request.
In operation S203, key information related to transaction processing is acquired and stored in the shared area.
Among the key information related to the transaction processing may be various information that can be involved in the transaction processing, such as user information of a transaction initiator, user information of a transaction receiver, a transaction amount, a transaction time, and the like. The key information related to the transaction processing may be preset, and the generated additional information may be triggered when the transaction processing satisfies a certain condition. For example, the transaction processing process is a transfer processing process, and when the transfer amount is greater than a predetermined threshold value, preset information is pushed to the client of the transaction initiator, and the like. Some key information may be acquired before the transaction processing is started, some key information may be acquired during the transaction processing, and some key information may be acquired after the transaction processing is completed, so that there is no determined time sequence relationship between the operation S203 and the operation S202, and the setting may be performed according to actual needs.
In operation S204, when the execution of the transaction process is completed, result information of the transaction process is acquired and stored in the shared area.
Wherein, the result information of the transaction processing is obtained after the transaction processing is completed and is stored in the sharing area for storing the key information. As will be appreciated by those skilled in the art, the information stored in the shared area may be gradually increased as the transaction processing proceeds after the transaction request is obtained.
In operation S205, a transaction message is generated based on the key information and the result information in the shared area, and the transaction message is pushed to the client related to the transaction processing.
The client related to transaction processing may be a client of a transaction initiator, a client of a transaction receiver, a client of a transaction agent, and the like, which are not limited herein. The transaction message is used to inform the user participating in the transaction event that the transaction processing is completed and the information related to the transaction processing, such as whether the transaction processing is successful, the detailed content of the transaction processing, whether the transaction processing triggers other preferential mechanisms, and the like, so that the user participating in the transaction event can know the change of the transaction state in time.
Those skilled in the art can understand that, after receiving the transaction request, the method shown in fig. 2, on one hand, performs corresponding transaction processing, and on the other hand, puts the key information and result information related to the transaction processing into the shared area, so that the segments that can form the transaction message are separately and independently stored in the shared area from the transaction processing process. After the transaction processing process is completed, the segments in the shared area can be directly formed into a transaction message and pushed to the corresponding client, and the expansibility and the timeliness of the transaction message are considered.
Illustratively, the key information related to transaction processing may include at least one of: the system comprises transaction initiator information, transaction receiver information, transaction content information, transaction additional information and auxiliary push information. The result information of the transaction processing may include: and a result identifier for characterizing success or failure of the transaction process.
In the embodiment of the present disclosure, for the above-mentioned process of executing the transaction processing corresponding to the transaction request and the above-mentioned process of acquiring the key information related to the transaction processing, because the acquisition timings of different key information are different, the two processes may not be performed according to a fixed timing relationship, and the two processes may be executed asynchronously.
Illustratively, the above process of acquiring the key information related to the transaction processing may include: static information corresponding to the transaction request is obtained prior to execution of the transaction process. The static information may include, for example, transaction amount, user information of both parties to the transaction, transaction initiation time, remark information of the transaction request, and other information that can be determined upon obtaining the transaction request. The process of acquiring the key information related to the transaction processing may also include: and in the transaction processing execution process, responding to an event for calling the specified interface to generate the dynamic information, and acquiring the dynamic information. The dynamic information may be transaction additional information or auxiliary push information, the transaction additional information may be, for example, point information of both parties of the transaction may be additionally added when the transaction processing satisfies a predetermined condition (for example, the transaction amount is greater than a preset threshold), and the point information corresponding to the transaction amount is determined by calling the first designated interface in the transaction processing process, and is used as the transaction additional information. The auxiliary push information may be, for example, some commodity promotion information that is expected to be pushed to the user participating in the transaction event, and the second specified interface is called in the transaction processing process to obtain the commodity promotion information as the auxiliary push information. In other embodiments, the static information is the information that can be determined when the transaction request is obtained, and the dynamic information is the information that is dynamically obtained during the transaction processing. Both of these static and dynamic information may be used as key information related to transaction processing as described above.
In an embodiment of the present disclosure, the generating a transaction message based on the key information and the result information in the shared area may include: and constructing a message material packet based on the key information and the result information in the shared area. A message template for the client associated with the transaction processing is then obtained. And then, assembling the message material packet based on the message template to obtain a corresponding transaction message. The client related to the transaction processing can be the client of the transaction initiator and the transaction receiver, or the client of an operator used by the transaction initiator or the transaction receiver, and in some cases, the transaction message is sent to a specified operator, and then forwarded to the client of the transaction initiator or the transaction receiver by the specified operator.
Further, after the transaction processing process is completed, a transaction message is generated based on the key information and the result information in the shared area, and a transaction receipt can be returned to the source party of the transaction request. The source of the transaction request may be a transaction initiator or a transaction agent, and the transaction agent acts on the transaction initiator to issue the transaction request.
Further, to ensure the security of transaction processing and avoid malicious transactions, the method for pushing a transaction message according to the embodiment of the present disclosure may further include: after the transaction request is obtained, the transaction request is subjected to security detection. And when the detection result of the safety detection is safety, executing the transaction processing corresponding to the transaction request.
Fig. 3 schematically illustrates an example schematic diagram of a process of pushing a transaction message according to an embodiment of the disclosure.
As shown in fig. 3, the above-described process of pushing a transaction message may be applied to a banking system, which may include a receiving and reporting bank accounting system 310 and a receiving and reporting bank message front-end system 320. After receiving the transaction request 330 (remittance message) by the receiving bank, the following operations may be performed: in operation S301, a message check is performed. After checking for errors, on the one hand, transaction processing (e.g., financial processing) is performed in operation S302, and then a message receipt is generated in operation S303. On the other hand, key information sharing is performed in operation S304, and then result information sharing is performed in operation S305, followed by key information and shared information packaging in operation S306. By the gateway bypass operation S307, on one hand, the return receipt is returned to the source of the transaction request 330, and on the other hand, the packaged information packet is transmitted to the receiving and reporting bank message front-end system 320. After receiving the information packet, the receiving and reporting bank message front-end system 320 performs the following operations: the real-time loading of the message about the information package is performed in operation S308, the message template loading is performed in operation S309, and then a message 1 conforming to the standards of the operator 340 (or the client of the transaction initiator) is generated in operation S310, and a message 2 conforming to the standards of the operator 340 (or the client of the transaction recipient) is generated in operation S311. The operator 340 (or the client of the transaction initiator) receives the message 1 in operation S312, and the operator (or the client of the transaction recipient) receives the message 2 in operation S313.
Based on the embodiments in the foregoing, in the method for pushing a transaction message according to the embodiments of the present disclosure, on the design thinking, the key information and the result information in the transaction processing are independent from the service processing system through memory sharing or other methods, so as to construct an independent data packet. After the transaction processing is finished, the data packet is distributed to a corresponding message front-end system through a communication gateway, so that quasi-real-time information synchronization is realized. And the message pre-processing system completes the assembly of the transaction message by combining a message assembly module according to the transaction key information and the result information. Different message styles can be expanded only by adjusting the assembly rule of the assembly module. The method can realize the quasi-real-time transmission of the transaction message only by increasing a small amount of system overhead. Compared with a batch mode in the related technology, the message receiving time efficiency can be shortened to be within 1 minute from 1-2 hours.
Fig. 4 schematically shows a block diagram of an apparatus for pushing a transaction message according to an embodiment of the present disclosure.
As shown in fig. 4, the apparatus 400 for pushing a transaction message may include: the system comprises a request acquisition module 410, a transaction processing module 420, a first information sharing module 430, a second information sharing module 440, and a message pushing module 450.
The request obtaining module 410 is used for obtaining a transaction request.
The transaction processing module 420 is configured to perform transaction processing corresponding to the transaction request.
The first information sharing module 430 is configured to obtain key information related to the transaction processing, and store the key information in a sharing area.
The second information sharing module 440 is configured to, when the transaction processing is completed, obtain result information of the transaction processing, and store the result information in the sharing area.
The message pushing module 450 is configured to generate a transaction message based on the key information and the result information in the shared area, and push the transaction message to a client related to the transaction processing.
It should be noted that the implementation, solved technical problems, implemented functions, and achieved technical effects of each module/unit/subunit and the like in the apparatus part embodiment are respectively the same as or similar to the implementation, solved technical problems, implemented functions, and achieved technical effects of each corresponding step in the method part embodiment, and are not described herein again.
Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.
For example, any plurality of the request obtaining module 410, the transaction processing module 420, the first information sharing module 430, the second information sharing module 440, and the message pushing module 450 may be combined in one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the request obtaining module 410, the transaction processing module 420, the first information sharing module 430, the second information sharing module 440, and the message pushing module 450 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or by a suitable combination of any several of them. Alternatively, at least one of the request obtaining module 410, the transaction processing module 420, the first information sharing module 430, the second information sharing module 440, and the message pushing module 450 may be at least partially implemented as a computer program module, which may perform corresponding functions when executed.
Fig. 5 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method according to an embodiment of the present disclosure. The computer system illustrated in FIG. 5 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.
As shown in fig. 5, a computer system 500 according to an embodiment of the present disclosure includes a processor 501, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. The processor 501 may comprise, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 501 may also include onboard memory for caching purposes. Processor 501 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the disclosure.
In the RAM 503, various programs and data necessary for the operation of the system 500 are stored. The processor 501, the ROM 502, and the RAM 503 are connected to each other by a bus 504. The processor 501 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 502 and/or the RAM 503. Note that the programs may also be stored in one or more memories other than the ROM 502 and the RAM 503. The processor 501 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the present disclosure, system 500 may also include an input/output (I/O) interface 505, input/output (I/O) interface 505 also being connected to bus 504. The system 500 may also include one or more of the following components connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.
According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program, when executed by the processor 501, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It will be understood by those skilled in the art that while the present disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. Accordingly, the scope of the present disclosure should not be limited to the above-described embodiments, but should be defined not only by the appended claims, but also by equivalents thereof.
Claims (9)
1. A method for pushing a transaction message comprises the following steps:
acquiring a transaction request;
executing transaction processing corresponding to the transaction request;
acquiring key information related to the transaction processing, and storing the key information into a sharing area;
when the transaction processing is finished, acquiring result information of the transaction processing, and storing the result information into the sharing area; and
generating a transaction message based on the key information and the result information in the sharing area, and pushing the transaction message to a client related to the transaction processing;
wherein the process of performing transaction processing corresponding to the transaction request and the process of acquiring key information related to the transaction processing are performed asynchronously;
wherein the obtaining key information related to the transaction processing comprises:
the critical information is obtained at least one stage prior to, during, or after completion of the transaction processing.
2. The method of claim 1, wherein,
the key information related to the transaction processing includes at least one of: the system comprises transaction initiator information, transaction receiver information, transaction content information, transaction additional information and auxiliary push information.
3. The method of claim 1 or 2, wherein the result information of the transaction processing comprises: an outcome indication for characterizing success or failure of the transaction process.
4. The method of claim 1, wherein the obtaining key information related to the transaction processing comprises:
obtaining static information corresponding to the transaction request before the transaction processing is executed;
in the transaction processing execution process, responding to an event for calling a specified interface to generate dynamic information, and acquiring the dynamic information; and
and taking the static information and/or the dynamic information as the key information.
5. The method of claim 1, wherein the generating a transaction message based on the key information and the result information in the shared region comprises:
constructing a message material packet based on the key information and the result information in the sharing area;
acquiring a message template of a client related to the transaction processing; and
and assembling the message material packet based on the message template to obtain the transaction message.
6. The method of claim 1, further comprising:
and returning a transaction receipt to a source party of the transaction request while generating a transaction message based on the key information and the result information in the shared area.
7. The method of claim 1, further comprising: after the transaction request is obtained, performing security detection on the transaction request;
the executing the transaction processing corresponding to the transaction request includes: and executing transaction processing corresponding to the transaction request when the detection result of the safety detection is safety.
8. An apparatus for pushing a transaction message, comprising:
the request acquisition module is used for acquiring a transaction request;
the transaction processing module is used for executing transaction processing corresponding to the transaction request;
the first information sharing module is used for acquiring key information related to the transaction processing and storing the key information into a sharing area;
the second information sharing module is used for acquiring result information of the transaction processing when the transaction processing is finished and storing the result information into the sharing area; and
the message pushing module is used for generating a transaction message based on the key information and the result information in the shared area and pushing the transaction message to a client related to the transaction processing;
wherein the process of performing transaction processing corresponding to the transaction request and the process of acquiring key information related to the transaction processing are performed asynchronously;
wherein the obtaining key information related to the transaction processing comprises:
the critical information is obtained at least one stage prior to, during, or after completion of the transaction processing.
9. A computer system, comprising:
a memory storing computer readable instructions;
a processor for executing the computer readable instructions to implement the method of pushing a transaction message according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910706793.1A CN110430256B (en) | 2019-07-31 | 2019-07-31 | Method, device and computer system for pushing transaction message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910706793.1A CN110430256B (en) | 2019-07-31 | 2019-07-31 | Method, device and computer system for pushing transaction message |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110430256A CN110430256A (en) | 2019-11-08 |
| CN110430256B true CN110430256B (en) | 2022-07-05 |
Family
ID=68412075
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910706793.1A Active CN110430256B (en) | 2019-07-31 | 2019-07-31 | Method, device and computer system for pushing transaction message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110430256B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107705204A (en) * | 2017-08-18 | 2018-02-16 | 武汉票据交易中心有限公司 | A kind of user feedback management method and system for bill business |
| CN108960941A (en) * | 2018-05-18 | 2018-12-07 | 北京票通信息技术有限公司 | E-payment billing method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7624112B2 (en) * | 2003-04-03 | 2009-11-24 | Oracle International Corporation | Asynchronously storing transaction information from memory to a persistent storage |
| CN102404389A (en) * | 2011-11-04 | 2012-04-04 | 浪潮齐鲁软件产业有限公司 | Network invoicing method based on cloud compute and data asynchronous transmission technology |
| CN106874267A (en) * | 2015-12-10 | 2017-06-20 | 航天信息股份有限公司 | A kind of method that asynchronous implement invoice is uploaded in real time |
| CN109189835B (en) * | 2018-08-21 | 2021-09-03 | 北京京东尚科信息技术有限公司 | Method and device for generating data wide table in real time |
-
2019
- 2019-07-31 CN CN201910706793.1A patent/CN110430256B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107705204A (en) * | 2017-08-18 | 2018-02-16 | 武汉票据交易中心有限公司 | A kind of user feedback management method and system for bill business |
| CN108960941A (en) * | 2018-05-18 | 2018-12-07 | 北京票通信息技术有限公司 | E-payment billing method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110430256A (en) | 2019-11-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12019652B2 (en) | Method and device for synchronizing node data | |
| CN111382168B (en) | Node group creating method and node group-based transaction method in alliance chain network | |
| EP4421716A1 (en) | Digital currency payment method and apparatus | |
| CN110365491A (en) | Method for processing business, device, equipment, storage medium and data-sharing systems | |
| CN113034118B (en) | Business auditing method, system, readable storage medium and computer program product | |
| CN112329049A (en) | Business data management method, device, electronic equipment and medium | |
| CN110223179B (en) | Data processing method, device, system and medium for fund | |
| CN111950249A (en) | Message generation method and device, electronic equipment and storage medium | |
| CN111580882B (en) | Application program starting method, device, computer system and medium | |
| CN113132400B (en) | Business processing method, device, computer system and storage medium | |
| EP4180985A1 (en) | File sharing method, apparatus, and system | |
| CN112825096A (en) | Data desensitization method and device | |
| CN114004701A (en) | Method and device for generating transaction result, electronic equipment and storage medium | |
| CN112181628B (en) | Resource transfer method, device, system and electronic equipment | |
| CN112732547B (en) | Service testing method and device, storage medium and electronic equipment | |
| CN113190812A (en) | Login method, system, electronic equipment and storage medium | |
| CN110430256B (en) | Method, device and computer system for pushing transaction message | |
| CN114793232B (en) | Service processing method, device, electronic equipment and storage medium | |
| CN114202332A (en) | Digital currency wallet management method, device and system | |
| CN111415245B (en) | Account opening method and device | |
| CN116263926A (en) | Accounting method, device and system based on blockchain | |
| CN113778631A (en) | Distributed transaction compensation method and device, electronic equipment and readable storage medium | |
| CN112182400A (en) | Message processing method, message processing device, electronic device and storage medium | |
| CN112184406A (en) | Data processing method, system, electronic device and computer readable storage medium | |
| CN112150126A (en) | Information processing method, information processing apparatus, electronic device, and medium |
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 |