Multi-terminal message synchronization push method and device

Abstract

The application discloses a multi-terminal message synchronization push method and device, which can be used in the financial field or other fields, and the method comprises the following steps: after a transaction instruction is acquired, an enterprise mobile bank application interface is called, and a plurality of message push identifiers corresponding to an electronic certificate are inquired according to the electronic certificate; the message push identifiers are generated by the enterprise mobile bank after terminal identifiers are bound with the electronic certificate; the transaction instruction comprises the electronic certificate; a to-be-pushed list is generated according to the plurality of message push identifiers corresponding to the electronic certificate; and the to-be-pushed list is sent to a message center so that the message center pushes a plurality of push messages to each terminal corresponding to each message push identifier according to the to-be-pushed list. According to the application, the message push identifiers are generated by the enterprise mobile bank after the terminal identifiers are bound with the electronic certificate, and the to-be-pushed list is generated according to the plurality of message push identifiers corresponding to the electronic certificate, so that the work efficiency of the enterprise user can be improved, and work delay or errors caused by untimely message push can be avoided.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of finance, in particular to a multi-terminal message synchronous push method and device. BACKGROUND

[0002] This section is intended to provide background or context to the embodiments of the application recited in the claims. The description herein does not constitute admission of prior art.

[0003] The client can conveniently push real-time messages such as account information and business progress information. However, unlike individuals, an enterprise can have multiple cashiers, accountants, and financial supervisors in different roles, and there is a demand for multiple roles to understand the enterprise's account changes and financial transaction progress. The current process is that the client uses an identity unique identifier electronic certificate to form a binding relationship with the mobile phone. Through the binding relationship code, one-to-one push of the push message is completed. However, there are multiple cashiers, multiple financial supervisors, and multiple financial directors in an enterprise, and the existing method cannot achieve one-to-many sending under the same electronic certificate. SUMMARY

[0004] Embodiments of the present application provide a multi-terminal message synchronous push method for realizing multi-terminal message synchronous push, which comprises:

[0005] After obtaining the transaction instruction, the enterprise mobile banking application interface is called, and the corresponding multiple message push identifiers are queried according to the electronic certificate; the message push identifier is generated by the enterprise mobile banking after the terminal identifier is bound with the electronic certificate; the transaction instruction includes the electronic certificate;

[0006] A to-be-pushed list is generated according to the multiple message push identifiers corresponding to the electronic certificate;

[0007] The to-be-pushed list is sent to the message center so that the message center pushes multiple push messages to each terminal corresponding to the message push identifier according to the to-be-pushed list.

[0008] Embodiments of the present application also provide a multi-terminal message synchronous push device for realizing multi-terminal message synchronous push, which comprises:

[0009] A to-be-pushed list generation module is configured to, after obtaining the transaction instruction, call the enterprise mobile banking application interface, and query the corresponding multiple message push identifiers according to the electronic certificate; the message push identifier is generated by the enterprise mobile banking after the terminal identifier is bound with the electronic certificate; the transaction instruction includes the electronic certificate; and a to-be-pushed list is generated according to the multiple message push identifiers corresponding to the electronic certificate;

[0010] The push module is configured to send the to-be-pushed list to the message center so that the message center pushes the multiple push messages to the terminals corresponding to the multiple message push identifiers respectively according to the to-be-pushed list.

[0011] The embodiment of the present application further provides a computer device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, and the processor implements the multi-terminal message synchronous push method when executing the computer program.

[0012] The embodiment of the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executable on a processor to implement the multi-terminal message synchronous push method.

[0013] The embodiment of the present application further provides a computer program product, which comprises a computer program, and the computer program is executable on a processor to implement the multi-terminal message synchronous push method.

[0014] In the embodiment of the present application, after the transaction instruction is acquired, the enterprise mobile bank application interface is called, and the multiple message push identifiers corresponding to the electronic certificate are inquired according to the electronic certificate; the message push identifiers are generated by the enterprise mobile bank after the terminal identifier is bound with the electronic certificate; the transaction instruction comprises the electronic certificate; the to-be-pushed list is generated according to the multiple message push identifiers corresponding to the electronic certificate; and the to-be-pushed list is sent to the message center so that the message center pushes the multiple push messages to the terminals corresponding to the multiple message push identifiers respectively according to the to-be-pushed list. Compared with the prior art, the message push identifiers are generated by the enterprise mobile bank after the terminal identifier is bound with the electronic certificate, and the to-be-pushed list is generated according to the multiple message push identifiers corresponding to the electronic certificate, so that the multiple terminals can synchronously receive the same push message, which not only can improve the work efficiency of the enterprise user, but also can avoid the work delay or error caused by the untimely message push. BRIEF DESCRIPTION OF DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor. In the drawings:

[0016] Figure 1 The flowchart of the multi-terminal message synchronous push method provided by the present application is shown in the figure;

[0017] Figure 2 The flowchart of the multi-terminal message synchronous push method provided by the present application is shown in the figure;

[0018] Figure 3 A flowchart of a multi-terminal message synchronization push method provided by the present application is shown in the figure.

[0019] Figure 4 A flowchart of a multi-terminal message synchronization push method provided by the present application is shown in the figure.

[0020] Figure 5 A structural diagram of a multi-terminal message synchronization push device provided by the present application is shown in the figure. DETAILED DESCRIPTION

[0021] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, further detailed description of the embodiments of the present application is given below in conjunction with the accompanying drawings. Here, the illustrative embodiments of the present application and the description thereof are used to explain the present application, but not to limit the present application.

[0022] Figure 1 A flowchart of an interface mapping method provided by the embodiments of the present application is shown in the figure, and the method comprises: Figure 1

[0023] Step 101, after obtaining a transaction instruction, an enterprise mobile bank application interface is called, and a plurality of message push identifiers corresponding to the electronic certificate are queried according to the electronic certificate.

[0024] The message push identifier is generated by the enterprise mobile bank after the terminal identifier is bound with the electronic certificate; and the transaction instruction comprises the electronic certificate.

[0025] It should be noted that the transaction instruction comprises the electronic certificate, instruction number, etc.

[0026] In the embodiments of the present application, before obtaining the transaction instruction, the enterprise user logs in the enterprise mobile bank client using the electronic certificate, binds the terminal identifier with the electronic certificate whose mobile phone number has been bound, generates a message push identifier for message push, and sends the binding relationship to the enterprise mobile bank for storage.

[0027] It should be noted that the message push identifier is generated by the enterprise mobile bank after the terminal identifier is bound with the electronic certificate.

[0028] In the embodiments of the present application, the electronic certificate is taken as a primary key, a terminal binding table is queried, and the corresponding message push identifier is obtained.

[0029] The enterprise mobile bank application interface is called, and the plurality of message push identifiers corresponding to the electronic certificate are queried.

[0030] Step 102, a to-be-pushed list is generated according to the plurality of message push identifiers corresponding to the electronic certificate.

[0031] ​In a possible implementation, the plurality of message push identifiers corresponding to the electronic certificate are spliced to obtain the to-be-pushed list. The one-to-many splicing is performed between the unique element (electronic certificate) and the non-unique element (message push identifier). The to-be-pushed list is generated and sent to the message center.

[0032] In step 103, the to-be-pushed list is sent to the message center, so that the message center pushes the plurality of push messages to the terminal corresponding to each message push identifier according to the to-be-pushed list.

[0033] After the message center receives the to-be-pushed list, the message center pushes the plurality of push messages to the terminal corresponding to each message push identifier according to the to-be-pushed list.

[0034] The above scheme is that the enterprise mobile bank generates the message push identifier after the terminal identifier is bound with the electronic certificate, and generates the to-be-pushed list according to the plurality of message push identifiers corresponding to the electronic certificate, so that the plurality of terminals can synchronously receive the same push message. This can not only improve the work efficiency and collaboration efficiency of enterprise users, but also avoid work delay caused by untimely message push.

[0035] Before the to-be-pushed list is sent to the message center, the step flow is as shown in Figure 2 , and specifically as follows:

[0036] In step 201, after the account movement message is acquired, the enterprise mobile bank application interface is called, and the plurality of message push identifiers corresponding to the mobile phone number are queried.

[0037] The account movement message is a balance change reminder message of a public account; the account movement message includes a mobile phone number and account movement detail information; the message push identifier is generated by the enterprise mobile bank after the terminal identifier is bound with the electronic certificate; and the electronic certificate is one-to-one corresponding to the mobile phone number.

[0038] It should be noted that the account movement message is a balance change reminder message of a public account; the account movement message includes a mobile phone number and account movement detail information.

[0039] In a possible implementation, the account movement message is acquired from an MQ queue of a distributed message platform.

[0040] In the embodiment of the application, before the account movement message is acquired, the enterprise user logs in to the enterprise mobile bank client by using the electronic certificate, binds the terminal identifier with the electronic certificate of the mobile phone number that has been bound, generates the message push identifier for message push, and sends the binding relationship to the enterprise mobile bank for storage.

[0041] The balance change reminding message generated by the public account is synchronized to a distributed message platform and stored in the form of an MQ queue. The main storage contents are a mobile phone number, account change detail information, and the like.

[0042] It should be noted that the message push identifier is generated by the enterprise mobile bank after the terminal identifier is bound to the electronic certificate; the electronic certificate and the mobile phone number are in one-to-one correspondence.

[0043] In the embodiment of the application, the mobile phone number in the account change message is used as a primary key to query whether the corresponding mobile phone number exists in the enterprise mobile bank. The terminal binding table is queried according to the mobile phone number.

[0044] If the mobile phone number exists, the mobile phone number and the corresponding message push identifier are returned.

[0045] In step 202, a to-be-pushed list is generated according to the multiple message push identifiers corresponding to the mobile phone number and the account change detail information.

[0046] In step 203, the to-be-pushed list is sent to the message center so that the message center pushes multiple push messages to the terminal corresponding to each message push identifier according to the to-be-pushed list.

[0047] The above scheme, after obtaining the account change message, generates a to-be-pushed list according to the multiple message push identifiers corresponding to the mobile phone number and the account change detail information, so that the same push message is synchronously received by multiple terminals, and the same push message can be synchronously received by multiple terminals. This not only improves the work efficiency and collaboration efficiency of enterprise users, but also avoids work delay caused by untimely message pushing.

[0048] After the application interface of the enterprise mobile bank is called in the embodiment of the application, the step process is as shown in Figure 3 and is specifically as follows:

[0049] In step 301, when the message push identifier corresponding to the mobile phone number does not exist in the enterprise mobile bank application cache, the corresponding electronic certificate is queried according to the mobile phone number.

[0050] In step 302, the multiple message push identifiers corresponding to the electronic certificate are queried.

[0051] In the embodiment of the application, if the corresponding data cannot be queried from the terminal binding table according to the mobile phone number, the enterprise login ID authority data table in the enterprise mobile bank application database is queried through the mobile phone number. The electronic certificate corresponding to the mobile phone number is queried, the terminal device binding table is queried through the electronic certificate, and the query result is written into the cache.

[0052] The scheme solves the problem of delayed push caused by the absence of the mobile phone number in the enterprise mobile bank application cache, improves the accuracy and efficiency of message push.

[0053] In a possible implementation, the message push identifier comprises a push parameter, and the push parameter is used to indicate whether to push.

[0054] After the electronic certificate is used to query the corresponding multiple message push identifiers in the embodiment of the application, the step flow is as shown in Figure 4 , and the specific process is as follows:

[0055] In step 401, the message push identifier indicated by the push parameter is determined.

[0056] In step 402, the message push identifier indicated by the push parameter is used to generate a to-be-pushed list.

[0057] The push parameter is used to indicate whether to push, so that the pushed message is more accurate and convenient.

[0058] The embodiment of the application also provides a multi-terminal message synchronization push device, which is described in the following embodiment. The device is as shown in Figure 5 , and the device comprises:

[0059] The to-be-pushed list generation module 501 is used to call an enterprise mobile bank application interface after a transaction instruction is acquired, query the corresponding multiple message push identifiers according to an electronic certificate, generate a to-be-pushed list according to the multiple message push identifiers corresponding to the electronic certificate, wherein the message push identifier is generated by the enterprise mobile bank after a terminal identifier is bound to the electronic certificate, and the transaction instruction comprises the electronic certificate.

[0060] The push module 502 is used to send the to-be-pushed list to a message center, so that the message center pushes multiple push messages to the terminal corresponding to each message push identifier according to the to-be-pushed list.

[0061] In the embodiment of the application, the to-be-pushed list generation module 501 is also used to:

[0062] After an account movement message is acquired, the enterprise mobile bank application interface is called, the corresponding multiple message push identifiers are queried according to the mobile phone number, the account movement message is a balance change reminder message of a public account, the account movement message comprises a mobile phone number and account movement detail information, the message push identifier is generated by the enterprise mobile bank after a terminal identifier is bound to an electronic certificate, and the electronic certificate is one-to-one corresponding to the mobile phone number.

[0063] The to-be-pushed list is generated according to the multiple message push identifiers corresponding to the mobile phone number and the account movement detail information.

[0064] The to-be-pushed list is sent to the message center, so that the message center pushes the plurality of push messages to the terminals corresponding to the plurality of message push identifiers respectively according to the to-be-pushed list.

[0065] In the embodiment of the application, the to-be-pushed list generation module 501 is further configured to:

[0066] After the application interface of the enterprise mobile bank is called for query, when the message push identifier corresponding to the mobile phone number does not exist in the cache of the enterprise mobile bank application, the electronic certificate corresponding to the mobile phone number is queried according to the mobile phone number;

[0067] The plurality of message push identifiers corresponding to the electronic certificate are queried.

[0068] In the embodiment of the application, the to-be-pushed list generation module 501 is specifically configured to:

[0069] The account update message is obtained from the MQ queue of the distributed message platform.

[0070] In the embodiment of the application, the to-be-pushed list generation module 501 is specifically configured to:

[0071] The plurality of message push identifiers corresponding to the electronic certificate are spliced to obtain the to-be-pushed list.

[0072] In the embodiment of the application, the to-be-pushed list generation module 501 is specifically configured to:

[0073] The message push identifier comprises a push parameter, and the push parameter is used to indicate whether to push.

[0074] Since the principle of solving the problem of the device is similar to the multi-terminal message synchronous push method, the implementation of the device can be referred to the implementation of the multi-terminal message synchronous push method, and the repeated parts will not be described again.

[0075] The embodiment of the application further provides a computer device, which comprises a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor implements the multi-terminal message synchronous push method when executing the computer program.

[0076] The embodiment of the application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the multi-terminal message synchronous push method.

[0077] The embodiment of the application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the multi-terminal message synchronous push method.

[0078] In the embodiment of the present application, after the transaction instruction is acquired, the enterprise mobile bank application interface is called, and the corresponding multiple message push identifiers are queried according to the electronic certificate; the message push identifier is generated by the enterprise mobile bank after the terminal identifier is bound with the electronic certificate; the transaction instruction comprises the electronic certificate; the to-be-pushed list is generated according to the multiple message push identifiers corresponding to the electronic certificate; and the to-be-pushed list is sent to the message center so that the message center pushes multiple push messages to the terminal corresponding to each message push identifier according to the to-be-pushed list. Compared with the prior art, the message push identifier is generated by the enterprise mobile bank after the terminal identifier is bound with the electronic certificate, the to-be-pushed list is generated according to the multiple message push identifiers corresponding to the electronic certificate, and the same push message is synchronously received by multiple terminals, which not only can improve the work efficiency of the enterprise user, but also can avoid work delay or error caused by untimely message push.

[0079] Those skilled in the art will understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0080] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system), and computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device that implements the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that carries out the function specified in one or more blocks.

[0081] These computer program instructions can also be stored in a computer-readable memory that can direct the computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product comprising instruction apparatus, which implements the flowcharts and / or block diagrams. Figure 1 one or more flows and / or blocks Figure 1 an apparatus that carries out the function specified in one or more blocks.

[0082] These computer program instructions can also be loaded into a computer or other programmable data processing devices, so that a series of operational steps are performed on the computer or other programmable data processing devices to generate a computer implemented process, so that the instructions executed on the computer or other programmable data processing devices provide a process for implementing the flowchart Figure 1 one flow or multiple flows and / or the functions specified in the block Figure 1 one flow or multiple flows and / or the functions specified in the block

[0083] The above-described specific embodiments, the purpose, technical solutions and beneficial effects of the present application are further described in detail, it should be understood that the above-described is only a specific embodiment of the present application, and is not used to limit the protection scope of the present application, any modification, equivalent replacement, improvement, etc. within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A method for synchronous message push across multiple terminals, characterized in that, include: After obtaining the transaction instruction, the system calls the enterprise mobile banking application interface to query multiple corresponding message push identifiers based on the electronic certificate. The message push identifier is generated by the enterprise mobile banking app after the terminal identifier is bound to the electronic certificate; transaction instructions include the electronic certificate; A list of messages to be pushed is generated based on multiple message push identifiers corresponding to the electronic certificate; The list of messages to be pushed is sent to the message center so that the message center can push multiple messages to the terminal corresponding to each message push identifier according to the list. The push messages pushed to the terminal corresponding to each message push identifier are the same messages.

2. The multi-terminal message synchronous push method as described in claim 1, characterized in that, Also includes: After obtaining the transaction information, the system calls the enterprise mobile banking application interface to query multiple corresponding message push identifiers based on the mobile phone number. Transaction notifications are alerts to balance changes in corporate accounts; transaction notifications include the mobile phone number and transaction details. The electronic certificate corresponds one-to-one with the mobile phone number; A push notification list is generated based on multiple message push identifiers and transaction details corresponding to the mobile phone number; The list of messages to be pushed is sent to the message center so that the message center can push multiple push messages to the terminal corresponding to each message push identifier according to the list.

3. The multi-terminal message synchronous push method as described in claim 2, characterized in that, Also includes: If the message push identifier corresponding to the mobile number is not found in the enterprise mobile banking application cache, the corresponding electronic certificate is queried based on the mobile number. The electronic certificate can be used to query multiple message push identifiers.

4. The multi-terminal message synchronous push method as described in claim 2, characterized in that, Also includes: Retrieve transaction messages from the MQ queue of the distributed messaging platform.

5. The multi-terminal message synchronous push method as described in claim 1, characterized in that, A list of messages to be pushed is generated based on multiple message push identifiers corresponding to the electronic certificate, including: By concatenating multiple message push identifiers corresponding to the electronic certificate, a list of messages to be pushed is obtained.

6. The multi-terminal message synchronous push method as described in claim 1, characterized in that, The message push identifier includes push parameters, which indicate whether to push a message.

7. The multi-terminal message synchronous push method as described in claim 6, characterized in that, After querying the corresponding message push identifiers based on the electronic certificate, it also includes: Determine the push parameters to indicate the message push identifier to be pushed; A list of messages to be pushed is generated based on the push parameters and the push identifier.

8. A multi-terminal message synchronization and push device, characterized in that, include: The pending push list generation module is used to call the enterprise mobile banking application interface after obtaining the transaction instruction, and query the corresponding multiple message push identifiers based on the electronic certificate; The message push identifier is generated by the enterprise mobile banking after the terminal identifier is bound to the electronic certificate; the transaction instruction includes the electronic certificate; a list of messages to be pushed is generated based on multiple message push identifiers corresponding to the electronic certificate; The push module is used to send a list of messages to be pushed to the message center so that the message center can push multiple push messages to the terminal corresponding to each message push identifier according to the list of messages to be pushed. The push messages pushed to the terminal corresponding to each message push identifier are the same messages.

9. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of any one of claims 1 to 7.

Images